header icons

Documentation Questions


Questions are mapped to quality attributes, on one side, and to metrics on the other side. It acts as a generic definition for measurement, allowing users to analyse different types of projects with the same quality tree. Questions also preserve the semantics and consistency of measures regarding the associated quality attribute, see Basili's Goal-Question-Metric approach [Basili1994] for more information on this approach.


  • Access points ( ALL_DATA )

    The average amount of attributes and methods defined on a class, whatever their visibility is.

  • Code cloning ( CODE_CLONE )

    The amount of duplicated lines in the code.

    Duplication makes changes to the code difficult, because the maintainer has to look for all instances of the modified code to propagate a fix.

  • Code documentation ( CODE_DOC )

    The amount of documentation in the code: comment rate, javadoc, etc.

  • Code size ( CODE_SIZE )

    The overall size of the code.

  • Code complexity ( CPX )

    The computational complexity of the code: control, data, inheritance.

  • Control flow complexity ( CPX_CF )

    The computational complexity of the control flow structure in the code functions.

  • Data flow complexity ( CPX_DF )

    The complexity of the data flow structure in the code functions.

  • OO complexity ( CPX_OO )

    The complexity of the object-oriented architecture and structure. Composed of MDIT (maximum depth of inheritance tree).

  • Downloads ( DOWNLOADS )

    What is the amount of downloads?

  • Installations ( INSTALL )

    The level of usage of the product. How much is really used the software? In different contexts, in local or distributed teams, etc.

  • IP Log ( IP_LOG )

    Is the intellectual property of contributions checked and enforced?

  • ITS Reliability ( ITS_REL )

    The reliability assessment of the project regarding registered bugs.

  • ITS usage ( ITS_USAGE )

    How much the ITS system was used recently.

  • Licensing ( LIC )

    Are licensing issues considered? Is there a list of licences used in the product?

  • Marketplace feedback ( MKT_FEEDBACK )

    What is the feedback of users of the Eclipse Marketplace on the product?

    If the product is not registered on the marketplace, the measure is set to zero.

  • Developer ML activity ( MLS_DEV_ACTIVITY )

    Activity on the developer mailing list.

  • Developer ML diversity ( MLS_DEV_DIVERSITY )

    Diversity of users on the developer mailing list.

  • Developer ML responsiveness ( MLS_DEV_RESPONSIVENESS )

    The delay of answers on the developer mailing list.

  • Developer ML support ( MLS_DEV_SUPPORT )

    The quantity of information gathered by questions on the developer mailing list.

  • User ML activity ( MLS_USR_ACTIVITY )

    Activity on the user mailing list.

  • User ML diversity ( MLS_USR_DIVERSITY )

    Diversity of users on the user mailing list.

  • User ML responsiveness ( MLS_USR_RESPONSIVENESS )

    The delay of answers on the developer mailing list.

  • User ML support ( MLS_USR_SUPPORT )

    The quantity of information gathered by questions on the user mailing list.

  • Plan on time ( PLAN_ON_TIME )

    Is the project on time according to its schedule?

  • Milestones ( PLAN_RELEASES )

    Is the project having regular milestones, do they prove to be effective?

  • Analysability practices ( PRACTICES_ANA )

    What practices (rules checked) related to analysability are violated, and how often?

  • Changeability practices ( PRACTICES_CHA )

    What practices (rules checked) related to changeability are violated, and how often?

  • Reliability practices ( PRACTICES_REL )

    What practices (rules checked) related to reliability are violated, and how often?

  • Reusability practices ( PRACTICES_REU )

    What practices (rules checked) related to reusability are violated, and how often?

  • Public access points ( PUBLIC_DATA )

    Average number of public classes, interfaces, methods, constructors, annotations and attributes.

  • Visibility in research ( PUB_CONF )

    How well-known is the software project in the academic field?

  • ITS information access ( PUB_ITS_INFO )

    Measures the availability of information regarding ITS usage, conventions, access.

  • SCM information access ( PUB_SCM_INFO )

    Measures the availability of information regarding SCM usage, conventions, access.

  • SCM activity ( SCM_ACTIVITY )

    Activity on the software configuration management system.

  • SCM diversity ( SCM_DIVERSITY )

    Diversity of users on the software configuration management system.

  • SCM Documentation ( SCM_DOCS )

    Measures the availability of information regarding SCM usage, conventions, access.

  • SCM Stability ( SCM_STABILITY )

    How much the files are stable according to the SCM system. A file which has been heavily modified recently lacks experience, tests and feedback.

  • SCM usage ( SCM_USAGE )

    How much the SCM system was used during last month.

  • Test coverage ( TST_COV )

    What percentage of the product has tests?

  • Test success density ( TST_SUCCESS )

    Are the available tests successful when executed?

  • Number of tests ( TST_VOL )

    The overall amount of tests executed for the project.