The following list of definitions will be updated as each instalment of the column is published.
Characteristics of the creation, nature and validation of software.
They may be broken down into three groups:
Defined in QM #1.
Characteristics innate to a given software entity.
Defined in QM #1.
Further reading:
Correctness is the degree to which a software entity's behaviour matches its specification.
Defined in QM #1.
Further reading:
Discoverability is how easy it is to understand a component in order to be able to use it.
Defined in QM #1.
Further reading:
Efficiency is the degree to which a software entity executes using the minimum amount of resources.
Defined in QM #1.
Further reading:
Expressiveness is how much of a given task can be achieved clearly in as few statements as possible.
Defined in QM #1.
Further reading:
Flexibility is how easily a software entity lets you do what you need to do, with the types with which you need to do it.
Defined in QM #1.
Further reading:
Modularity is the degree of dependence of a software entity on other software entities.
It tends to have two concerns:
Defined in QM #1.
Further reading:
Portability is how readily you can use a software entity in your chosen operating environment.
Defined in QM #1.
Further reading:
Reliability is the degree to which a software system behaves robustly over time.
Defined in QM #2.
Further reading:
Robustness is the adjudged ability of a software entity to behave according to the expectations of its stakeholders.
Defined in QM #2.
Further reading:
Transparency is how easy it is to understand a component in order to be able to change it.
Defined in QM #1.
Further reading:
A software entity's specification is the sum of all its passing unit-tests.
and
A software entity's specification is the sum of all its unfired active contract enforcements.
Defined in QM #2.
Further reading: