Mimir - The Professional Project Guide



API API is the abbreviation for Application Programmer Interface, i.e. the set of public functions of a component.
Black Box Test Case Design Technique See Black Box Test Case Design Technique.
Branch Coverage Branch coverage is the measurement (as a percentage number) of the branches in a certain code section which have executed during a test test execution.
Bug A bug is the non-fulfillment of a specified requirement.
Generic term for error, fault and failure.
C0 Coverage C0 coverage is a synonym for "Statement Coverage". See statement coverage.
C1 Coverage C1 coverage is a synonym for "Branch Coverage". See branch coverage.
Change Request A change request is a demand (issue) to modify a project work product, for example a document or the code.
CM Abbreviation for Configuration (and Change) Management
CMM Capability Maturity Model: a process maturity model maintained by the SEI (http://www.sei.cmu.edu/)
CMMI CMM Integrated, see CMM
Component Test See Component Test.
Decision Coverage Decision coverage is a synonym for "Branch Coverage". See branch coverage.
Defect See fault.
Defect Masking After IEEE 610: An occurrence in which one defect prevents the detection of another.
Deficiency A deficiency is the non-fulfillment of a requirement related to an intended or specified use
(ISO 9000:2000).
Error After IEEE 610: "Human action that produces an incorrect result." See fault.
Erroneous Action See error.
Fault A fault is an incorrect result within a project work product. It can cause the project work product to fail to perform its specified function.
A fault encountered during execution, may cause a failure of the component or system.
Failure A failure is an effect of a fault during the execution of the test object. Deviation between the actual result or behaviour is not the expected result or behaviour. 
A failure can also be caused by the environment, for example electromagnetic fields.
IDE Integrated Development Environment: tool or environment to develop software like MS VisualStudio or Eclipse.
Integration Test See Integration Test.
Issue An issue can be tracked within a project as "new demand", "change request", or "modification request".
MISRA Motor Industry Software Reliability Association
Mistake See error.
Modification Request See Change Request.
Module Test See Component Test.
Non-functional Test Design Technique Procedure to derive test cases for non-functional attributes on an analysis of the Test Basis of a component or system without reference to its internal structure.
See also black box test design technique.
Non-functional Testing That means testing the attributes of a component or system that do not refer to the functionality, for example reliability, usability, efficiency, maintainability, and portability.
PDS Project Drive Structure - Standardized directory structure for projects and components
Peer A peer, as used for example in the term peer review, is a colleague on the same hierarchical level.
Product Owner A product owner's main responsibility is getting the most valued functionality at a certain date within a certain budget. The product owner therefore must be able to prioritize work and decide what functionality to put into a release, maybe removing obsolete functionality and adding new functionality. The product owner also has to answer questions about functionality that arise during the course of the project, signing off sprint results, and reporting to upper management. In order to do his job properly the product owner needs the right authority and knowledge about the business, the problem domain and the envisioned product.
Repository Data structure to store project relevant data like documents, source code etc. Tools which offer version management functionality often use some kind of database as repository.
Requester Any stakeholder in the development process or at customer side who is enabled to formulate issues.
Smoke Test An informal test performed by the developer to ensure that the major functionality of the component is operational. This test is performed before the formal testing process starts.
Software Component A software component is set of code files or classes representing a certain functionality. Usually a component is within the responsibility of a single developer.
Software System A software system is a compileable and linkable set of software components, i.e. a program.
Stakeholder Any person or institution with interest in the project, e.g. customer.
Statement Coverage Statement coverage is the measurement (as a percentage number) of the statements in a certain code section which have executed during a test execution.
Statement of Problem  
SOP Start of production. Milestone indicating that the development phase is finished and the product is ready for production and / or shipment.
System Test See System Test.
Test Basis Testing means comparison: Documents describe the test object and specified the requirements. The Test Basis consists of all documents from which the requirements of a component or system can be inferred. The test cases are derived from the Test Basis.
The quality of the Test Basis is significant for the quality the test case design.
Test Completeness Criterion See Test Completeness and Test End Criterion.
Test End Criterion See Test Completeness and Test End Criterion.
Test Level See Test Levels.
Unit Test See Component Test.
White Box Test Case Design Technique See White Box Test Case Design Technique.

Mimir v01.20rel © H-DA / HOOD / Windhoff / Bär, Pfitzer & Partner 2011. All rights reserved. $Revision: 903 $