Anomaly

Term: “anomaly”. It is any condition deviating from the expectations based on requirement specifications, design documents, user documents, standards, someone’s perception or experience, etc. Anomalies can only be found during assessment, tests, analysis, compilation, or use of applicable software products or documentation (although their purposes exceed this goal) ...

read more

Analyzability

Term: “analyzability”. It is the capacity of a software product or its parts to be diagnosed with software deficiencies or causes or failure.. [ISO 9126] Also look up mantainability.

read more

Static analysis

Term: “static analysis”. It is the analysis of the software artifacts, such as requirements or code, without the execution of the aforementioned artifacts.

read more

Test suite

Term: “test suite”. It is a set of test cases for a component or system undergoing testing, for which the post-condition of a test is often used as a pre-condition of the following one.

read more

Baseline

Term: “baseline”. It is a specification of a software product that has been formally reviewed or agreed upon, and that serves as a baseline for later developments and that can only be modified through a formal track change process. [IEEE 610]

read more