< Previous | Contents | Next >
Annex C lists the applicable terminology references from ISO/IEC/IEEE 24765 and ISO/IEC/IEEE 29119. It also provides terms which are specifically defined within Automotive SPICE. Some of these definitions are based on ISO/IEC/IEEE 24765.
Term | Origin | Description |
Acceptance testing | ISO/IEC/IEEE 24765 | Formal testing conducted to enable a user, customer, or authorized entity to determine whether to accept a system or component. |
Application parameter | Automotive SPICE V3.1 | An application parameter is a parameter containing data applied to the system or software functions, behavior or properties. The notion of application parameter is expressed in two ways: firstly, the logical specification (including name, description, unit, value domain or threshold values or characteristic curves, respectively), and, secondly, the actual quantitative data value it receives by means of data application. |
Architecture element | Automotive SPICE V3.1 | Result of the decomposition of the architecture on system and software level: The system is decomposed into elements of the system architecture across appropriate hierarchical levels. The software is decomposed into elements of the software architecture across appropriate hierarchical levels down to the software components (the lowest level elements of the software architecture). |
Baseline | ISO/IEC/IEEE 24765 | A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and can be changed only through formal change control procedures. |
Black-box testing | Automotive SPICE V3.1 | Method of requirement testing where tests are developed without knowledge of the internal structure and mechanisms of the tested item. |
Code review | Automotive SPICE V3.1 | A check of the code by one or more qualified persons to determine its suitability for its intended use and identify discrepancies from specifications and standards. |
Coding | ISO/IEC/IEEE 24765 | The transforming of logic and data from design specifications (design descriptions) into programming language. |
Consistency | Automotive SPICE V3.1 | Consistency addresses content and semantics and ensures that work products are not in contradiction to each other. Consistency is supported by bidirectional traceability. |
Defect | → [FAULT] | |
Dynamic analysis | ISO/IEC/IEEE 24765 | A process of evaluating a system or component based on its behavior during execution. |
Element | Automotive SPICE V3.1 | Elements are all structural objects on architectural and design level on the left side of the "V". Such elements can be further decomposed into more fine-grained sub-elements of the architecture or design across appropriate hierarchical levels. |
Error | ISO/IEC/IEEE 24765 | The difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. |
Fault | ISO/IEC/IEEE 24765 | A manifestation of an error in software. |
Functional requirement | ISO/IEC/IEEE 24765 | A statement that identifies what a product or process must accomplish to produce required behavior and/or results. |
Functional specification | ISO/IEC/IEEE 24765 | A document that specifies the functions that a system or component must perform. Often part of a requirements specification. |
Functional testing | ISO/IEC/IEEE 24765 | Testing conducted to evaluate the compliance of a system or component with specified functional requirements. |
Hardware | ISO/IEC/IEEE 24765 | Physical equipment used to process, store, or transmit computer programs or data. |
Hardware item | Automotive SPICE V3.1 | A physical representation of a hardware element. |
Integration | Automotive SPICE V3.1 | A process of combining items to larger items up to an overall system. |
Integrated software item | Automotive SPICE V3.1 | A set of software units or items that are integrated into a larger assembly for the purpose of integration testing. |
Integration testing | Automotive SPICE V3.1 | Testing in which items (software items, hardware items, or system items) are combined and tested to evaluate the interaction among them. |
Integrated system item | Automotive SPICE V3.1 | A set of items that are integrated into a larger assembly for the purpose of integration testing. |
Quality assurance | ISO/IEC/IEEE 24765 | A planned and systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements. |
Regression testing | Automotive SPICE V3.1 | Selective retesting of a system or item to verify that modifications have not caused unintended effects and that the system or item still complies with its specified requirements. |
Requirement | Automotive SPICE V3.1 | A property or capability that must be achieved or possessed by a system, system item, product, or service to satisfy a contract, standard, specification or other formally imposed documents. |
Requirements specification | Automotive SPICE V3.1 | A document that specifies the requirements for a system or item. Typically included are functional requirements, performance requirements, interface requirements, design requirements, and development standards. |
Software | ISO/IEC/IEEE 24765 | Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system. |
Software component | Automotive SPICE V3.1 | In Automotive SPICE V3.1 the term "software component" is used for the lowest level elements of the software architecture for which finally the detailed design is defined. A software "component" consists of one or more software "units". → [Architecture element], [Unit] |
Software element | → [Architecture element] | |
Software item | ISO/IEC/IEEE 24765 | Identifiable part of a software product. |
Software unit | → [UNIT] |
Static analysis | Automotive SPICE V3.1 | A process of evaluating an item based on its form, structure, content, or documentation. |
System | Automotive SPICE V3.1 | A collection of interacting items organized to accomplish a specific function or set of functions within a specific environment. |
System item | Automotive SPICE V3.1 | Identifiable part of the system. |
System test | ISO/IEC/IEEE 24765 | Testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. |
Testing | Automotive SPICE V3.1 | Activity in which an item (system, hardware, or software) is executed under specific conditions; and the results are recorded, summarized and communicated. |
Traceability | ISO/IEC/IEEE 24765 | The degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another. |
Unit | Automotive SPICE V3.1 | Part of a software component which is not further subdivided. → [Software component] |
Unit test | Automotive SPICE V3.1 | The testing of individual software units or a set of combined software units. |
Validation | ISO/IEC/IEEE 29119 | Validation demonstrates that the work item can be used by the users for their specific tasks. |
Verification | ISO/IEC/IEEE 29119 | Verification is confirmation, through the provision of objective evidence, that specified requirements have been fulfilled in a given work item. |
White-box testing | Automotive SPICE V3.1 | Method of testing where tests are developed based on the knowledge of the internal structure and mechanisms of the tested item. |