Glossary

Overview

The glossary is intended to provide a common vocabulary for all project participants and to ensure clarity and consistency in the use of terminology across the project.

It includes definitions for terms related to the building blocks concept, development phases, roles, work products, and other relevant concepts.

Terms

Table 78 Process Description Glossary

Term	Definition	Comment/Link
Assumptions of Use (AoU)	Constraints and conditions under which a component, feature, or platform element can be safely and correctly used. AoUs must be documented and considered by users of the element.	Building blocks concept
Building Blocks	Fundamental structural elements of the platform including Features, Components, Units, and Dependable Elements that form the basis of the system architecture.	Building blocks concept
Change Request (CR)	A formal request to modify, add, or remove features or components in the platform. Change requests drive the development lifecycle and must be tracked and approved.	Process change management
Committer	A developer role who reviews and accepts contributions (pull requests) to the main codebase. Committers maintain code quality and enforce project processes.	Roles
Component	A major building block of the platform consisting of one or more Units. Components are defined by Component Requirements and Component Architecture, and are tested through Component Integration Tests.	Building blocks concept
Component Architecture	The design specification that defines how a component is structured, including its internal organization, interfaces, and relationships with other components.	Building blocks concept
Component Integration Tests	Verification tests that verifies component requirements and architecture, as well as the integration of multiple Units into a single Component.	Building blocks concept
Component Safety/Security Analysis	Systematic analysis performed on component architecture to verify compliance with safety and security requirements, documenting any violations or potential faults.	Building blocks concept
Concept Phase	Initial development phase where feasibility and decision criteria are established for a new feature or component request. Only Change Management is mandatory in this phase.	Lifecycle concept
Contributor	An individual who contributes to the project by submitting code, documentation, processes, or other work products. Contributors work within defined workflows and processes.	Roles
Delivery Container	A packaging mechanism for delivering Dependable Elements (e.g., executable code or libraries) to users or integrators of the platform.	Building blocks concept
Dependable Element	The highest abstraction level in the building blocks model. A Dependable Element consists of one or more Components and can be developed as a Safety Element out of Context (SEooC). It is delivered in a Delivery Container.	Building blocks concept
Dependable Element View	Documentation that maps components to Dependable Elements, showing how components are grouped for delivery.	Building blocks concept
Detailed Design	The comprehensive design specification for a Unit, including implementation details and algorithms. Verified through Unit Tests.	Building blocks concept
Development Phase	The phase where accepted features or components are planned, implemented, and verified according to defined project processes. May include iterative implementation cycles.	Lifecycle concept
Feature	A collection of related components that provide a specific capability to the platform. Features are defined by Feature Requirements and Feature Architecture.	Building blocks concept
Feature Architecture	The design specification that defines how a feature is structured, including its components, interfaces, and logical architecture interfaces.	Building blocks concept
Feature Integration Tests	Verification tests that verifies feature requirements and architecture, ensuring proper integration of multiple components within the feature.	Building blocks concept
Feature Requirements	Specifications defining what a feature must accomplish, derived from higher-level stakeholder requirements and allocated to components.	Building blocks concept
Feature Safety/Security Analysis	Systematic analysis performed on feature architecture to verify compliance with safety and security requirements at the feature level, documenting any violations or potential faults.	:Building blocks concept
Impact Analysis	The process of evaluating the effects and consequences of proposed changes on work products.	Process change management
Inspection	A formal review of work products supported by a checklist with documented conduct and outcome. Inspections verify quality and compliance of requirements, architecture, and implementation.	:Review concept
Logical Architecture Interfaces	Abstract interfaces defined at the feature level that specify how components communicate and interact within a feature.	:Building blocks concept
Maintenance Phase	Development phase following the first major release, where released features and components are maintained. Triggered by problem reports requiring fixes.	Lifecycle concept
Module	An synonym term for Dependable Element	Building blocks concept
Module Team	Cross-functional team responsible for all artifacts within a Module, including development, quality, safety, and security activities.	Roles
Platform	The complete software platform consisting of features, components, and supporting infrastructure.	Building blocks concept
Platform Integration Tests	Verification tests performed on reference hardware platforms to test stakeholder requirements and overall platform functionality.	Building blocks concept
Platform Safety/Security Analysis	Systematic analysis of the complete platform architecture to verify compliance with stakeholder-level safety and security requirements, documenting any violations or potential faults.	:Building blocks concept
Problem Report	A report documenting issues found in released features or components, including bugs, quality issues, or safety/security anomalies. Initiates the Maintenance Phase.	Workflows
Project Lead	Executive role responsible for strategic decisions, approving feature requests, performing project management, and high-level coordination between software modules.	Roles
Quality Manager	Role responsible for quality assurance, process compliance, work product reviews, quality audits, and continuous process improvement.	Process quality management
Role	A defined position within the project with specific responsibilities, authorities, and required competencies. Examples include Project Lead, Developer, Tester, Safety Manager.	Roles
Safety Element out of Context (SEooC)	A software element developed and analyzed independently but intended to be integrated into specific applications, as defined by functional safety standards.	Building blocks concept
Safety Manager	Role responsible for ensuring functional safety compliance (e.g., ISO 26262), conducting safety analyses, approving safety work products, and providing safety guidance.	Process safety management
Security Manager	Role responsible for security management, vulnerability handling, cybersecurity compliance (e.g., ISO SAE 21434), and security analysis approvals.	Process security management
Source Code	The actual implementation of a Unit, typically written in a programming language and version-controlled in the repository.	Building blocks concept
Stakeholder Requirements	High-level requirements specified at the platform level that define what the platform must accomplish for its intended users.	Building blocks concept
SW Platform Assumptions of Use	Constraints and conditions defined at the platform level that must be considered by users integrating the platform into their applications.	Building blocks concept
Traceability	The documented relationship between work products at different levels (requirements, architecture, design, code, tests) enabling impact analysis and coverage determination.	Traceability concept
Unit	The lowest level in the building blocks model, representing source code that implements a specific function or feature. Units are verified through Unit Tests.	Implementation process
Unit Tests	Verification tests that verifies the detailed design and implementation of individual Units.	Verification process
Verification	The process of confirming that work products (requirements, architecture, design, code) correctly implement and satisfy higher-level specifications through testing and analysis.	Verification process
Work Product	Any tangible output produced during development, including requirements, architecture documents, design specifications, source code, test cases, and analysis reports.	Work products
Workflow	A defined sequence of activities with inputs, outputs, responsible roles, and supporting guidance. Workflows form the central building blocks of the process description.	Workflows