diff --git a/process/_assets/score_process_area_overview.drawio.svg b/process/_assets/score_process_area_overview.drawio.svg index 28fe4a2c65..080675985a 100644 --- a/process/_assets/score_process_area_overview.drawio.svg +++ b/process/_assets/score_process_area_overview.drawio.svg @@ -1,4 +1,916 @@ - - - -


Process Areas - Development










 
Process Areas - Development...
Introduction
Introduction


Process Areas - Management










 
Process Areas - Management...
Requirements
Enngineering





Requirements...
Safety
Management
Safety...


Change Management

Change Managem...
Documentation
Management
Documentation...
General Concepts
General Concepts
Standards
Standards
Roles
Roles

Architecture





Architectur...
Imple-mentation

(Detailed Design,
Coding)
Imple-menta...
Problem Resolution
Problem Resolu...
ML 4
ML 4
ML 2
ML 2
ML 1
ML 1


Verification






Verificatio...
Configuration
Management
Configuration...
Tool
Management
Tool...
Quality
Management
Quality...
Project
Management
Project...
Maturity Level
Maturity Level
ML 0
ML 0
Safety
Analysis




Safety...
Work Products
Work Products
Workflows
Workflows
ML 3
ML 3
Plan - 
Process definition planned
Documents not available or most empty
Plan -...
Initial - 
Process definition in place, but not yet compliant, consistency across S-CORE platform, modules and repeatability of processes may not be possible.
Documents are mostly available, main parts done, principles clear, all top level questions addressed, well structured.
Initial -...
Managed -
Process definition in place but not yet deployed in S-CORE, but execution would allow consitency across S-CORE platform and modules, repeatability of processes possible
Documents are complete, documented on a comprehensible systematic approach, verified, only minor questions open, Process requirements enforced by implemented Tool Requirements.
Managed -...
Defined/Practiced - 
Deployed (at least once) in S-CORE platform or one Module, The processes have been practiced, and evidence exists to demonstrate that this has occurred. 
Document are complete, verified and released, Initial Safety Audit passed.
Defined/Practiced -...
Improving - 
Deployed on S-CORE platform and various S-CORE Modules and constantly improving, using suitable process metrics, S-CORE commiter control the effectiveness and performance of the platform and modules and demonstrate continuous improvement in these areas.
Improving -...
Release
Management
Release...
Trustable
Trustable
Folder Templates
Folder Templates
Security
Management
Security...Text is not SVG - cannot display \ No newline at end of file + + + + + + + + + + +
+
+
+ +
+
+ Process Areas - Development +
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+ + + Process Areas - Development... + + + + + + + + + + + +
+
+
+ + Introduction + +
+
+
+ + + Introduction + + + + + + + + + + + +
+
+
+ +
+
+ Process Areas - Management +
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+ + + Process Areas - Management... + + + + + + + + + + + +
+
+
+ Requirements +
+ Engineering +
+
+
+
+ + + Requirements... + + + + + + + + + + + +
+
+
+ Safety +
+ Management +
+
+
+ + + Safety... + + + + + + + + + + + +
+
+
+
+ Change Management +
+
+
+
+
+
+ + + Change Managem... + + + + + + + + + + + +
+
+
+ Documentation +
+ Management +
+
+
+ + + Documentation... + + + + + + + + + + + +
+
+
+ + General Concepts + +
+
+
+ + + General Concepts + + + + + + + + + + + +
+
+
+ + Standards + +
+
+
+ + + Standards + + + + + + + + + + + +
+
+
+ + Roles + +
+
+
+ + + Roles + + + + + + + + + + + +
+
+
+ Architecture +
+
+
+ + + Architecture + + + + + + + + + + + +
+
+
+ Imple-mentation +
+
+ (Detailed Design, +
+ Coding) +
+
+
+ + + Imple-mentatio... + + + + + + + + + + + +
+
+
+ Problem Resolution +
+
+
+ + + Problem Resolu... + + + + + + + + + + + +
+
+
+ ML 4 +
+
+
+ + + ML 4 + + + + + + + + + + + +
+
+
+ ML 2 +
+
+
+ + + ML 2 + + + + + + + + + + + +
+
+
+ ML 1 +
+
+
+ + + ML 1 + + + + + + + + + + + +
+
+
+ Verification +
+
+
+ + + Verification + + + + + + + + + + + +
+
+
+ Configuration +
+ Management +
+
+
+ + + Configuration... + + + + + + + + + + + +
+
+
+ Tool +
+ Management +
+
+
+ + + Tool... + + + + + + + + + + + +
+
+
+ Quality +
+ Management +
+
+
+ + + Quality... + + + + + + + + + + + +
+
+
+ Project +
+ Management +
+
+
+ + + Project... + + + + + + + + + + + +
+
+
+ + Maturity Level + +
+
+
+ + + Maturity Level + + + + + + + + + + + +
+
+
+ ML 0 +
+
+
+ + + ML 0 + + + + + + + + + + + +
+
+
+ Safety +
+ Analysis +
+
+
+ + + Safety... + + + + + + + + + + + +
+
+
+ + Work Products + +
+
+
+ + + Work Products + + + + + + + + + + + +
+
+
+ + Workflows + +
+
+
+ + + Workflows + + + + + + + + + + + +
+
+
+ ML 3 +
+
+
+ + + ML 3 + + + + + + + + + + + +
+
+
+ + Plan + + - +
+ + Process definition planned. +
+ Documents not available + + or most empty. +
+
+
+ + + Plan -... + + + + + + + + + + + +
+
+
+ + Initial + + - +
+ + Process definition in + + + place, but not yet compliant, + + + consistency across S-CORE platform, modules and repeatability of processes may not be possible. +
+ Documents are mostly available, main parts done, principles clear, all top level questions addressed, well structured. +
+ +
+
+
+ + + Initial -... + + + + + + + + + + + +
+
+
+ + Managed + + - +
+ + Process definition in place but not + + + yet deployed in S-CORE, but + + + execution would allow consitency across S-CORE platform and modules, repeatability of processes possible +
+ Documents are complete, documented on a comprehensible systematic approach, verified, only minor questions open, Process requirements enforced by implemented Tool Requirements. +
+ +
+
+
+ + + Managed -... + + + + + + + + + + + +
+
+
+ + Defined/Practiced + + - +
+ + Deployed (at least once) in S-CORE platform or one Module, + + + + The processes have been practiced, and evidence exists to demonstrate that this has occurred. + +
+ + Document are complete, verified and released, Initial Safety Audit passed. + +
+ +
+
+
+ + + Defined/Practiced -... + + + + + + + + + + + +
+
+
+ Improving - +
+ + Deployed on S-CORE platform and various S-CORE Modules and + + + constantly improving, u + + + sing suitable process metrics, S-CORE commiter control the effectiveness and performance of the platform and modules and demonstrate continuous improvement in these areas. + +
+
+
+ + + Improving -... + + + + + + + + + + + +
+
+
+ Release +
+ Management +
+
+
+ + + Release... + + + + + + + + + + + +
+
+
+ + Trustable + +
+
+
+ + + Trustable + + + + + + + + + + + +
+
+
+ + Folder Templates + +
+
+
+ + + Folder Templates + + + + + + + + + + + +
+
+
+ Security +
+ Management +
+
+
+ + + Security... + + + + + + + + + + Text is not SVG - cannot display + + + + diff --git a/process/process_areas/implementation/guidance/implementation_process_reqs.rst b/process/process_areas/implementation/guidance/implementation_process_reqs.rst index b8d4c35ab3..96b21844ed 100644 --- a/process/process_areas/implementation/guidance/implementation_process_reqs.rst +++ b/process/process_areas/implementation/guidance/implementation_process_reqs.rst @@ -20,7 +20,7 @@ Process Requirements :status: valid :tags: manual_prio_1, mandatory :satisfies: wf__sw_detailed_design - :complies: std_req__iso26262__software_843 + :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 The static diagram shall represent the unit and their relationships using UML notations. @@ -29,7 +29,7 @@ Process Requirements :status: valid :tags: manual_prio_2, mandatory :satisfies: wf__sw_detailed_design - :complies: std_req__iso26262__software_843 + :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP2 The dynamic diagram shall represent the unit and their relationships using UML notations. @@ -38,7 +38,7 @@ Process Requirements :status: valid :tags: prio_1_automation, mandatory :satisfies: wf__sw_detailed_design - :complies: std_req__iso26262__software_843 + :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP3, std_req__aspice_40__SWE-3-BP4 The detailed design (units and interfaces in DD document) shall be linked to the source code which implements the units and interfaces in the DD. diff --git a/process/process_areas/implementation/guidance/index.rst b/process/process_areas/implementation/guidance/index.rst index 145d1ca077..2f9f547614 100644 --- a/process/process_areas/implementation/guidance/index.rst +++ b/process/process_areas/implementation/guidance/index.rst @@ -18,8 +18,8 @@ Guidance .. toctree:: :maxdepth: 1 - implementation_guideline implementation_checklist detailed_design_template + implementation_guideline implementation_process_reqs software_development_template diff --git a/process/process_areas/implementation/implementation_concept.rst b/process/process_areas/implementation/implementation_concept.rst index 1a6ee8f04f..5e3c18e2d3 100644 --- a/process/process_areas/implementation/implementation_concept.rst +++ b/process/process_areas/implementation/implementation_concept.rst @@ -54,21 +54,26 @@ The goal is to ensure that the decomposition supports **reusability** , **mainta The detailed design and implementation should follow an **iterative approach**, allowing for continuous improvements in quality through multiple cycles of refinement. -Specification of Detailed Design --------------------------------- +Definition of a Unit +-------------------- A **unit** is a **granular, independent entity** of a component that can be **tested separately** during the unit testing phase. Each unit represents a **self-contained functionality** and is derived from the decomposition of a component. -**Draft: Characteristics of a Unit** +**Characteristics of a Unit:** - **Independent** – Can be tested in isolation. - **Granular** – Represents a small, well-defined part of the system. - **Relational** – Has associations with other units, defined using **UML 2.0 notations** such as aggregation, composition, and generalization. -**Units in UML Diagrams** +**Examples:** +The definition of a unit depends on the used programming language. Examples for a unit are +a source file, a definition file (e.g. c++ header), classes, structs, and functions. +This list is not complete or exclusive. + +**Units in UML Diagrams:** - For **Rust development**, a **unit** is modeled using a **combination of `struct` and `trait`**, as Rust does not have traditional classes. diff --git a/process/process_areas/implementation/implementation_roles.rst b/process/process_areas/implementation/implementation_roles.rst index a6ba7dbd57..06664ab252 100644 --- a/process/process_areas/implementation/implementation_roles.rst +++ b/process/process_areas/implementation/implementation_roles.rst @@ -21,3 +21,7 @@ Contributing Roles: * :need:`Contributor ` * :need:`Committer ` + +A detailed overview of the responsibility for the steps of the requirement process is listed here: + +:ref:`workflow_implementation` diff --git a/process/process_areas/implementation/implementation_workflow.rst b/process/process_areas/implementation/implementation_workflow.rst index b6f7aa2447..77a207a7bf 100644 --- a/process/process_areas/implementation/implementation_workflow.rst +++ b/process/process_areas/implementation/implementation_workflow.rst @@ -12,6 +12,9 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* +.. _workflow_implementation: + + Workflow Implementation ####################### @@ -26,10 +29,10 @@ Workflow Implementation :contains: gd_temp__software_development_plan :has: doc_concept__imp_concept, doc_getstrt__imp_getstrt - The Software Development Plan shall descirbe - - methods - - Guidelines - - development environment + The Software Development Plan shall describe + - Design and programming language selection + - Guidelines for design and coding + - Development tools .. workflow:: Create/Maintain Implementation :id: wf__sw_detailed_design diff --git a/process/process_areas/implementation/implementation_workproducts.rst b/process/process_areas/implementation/implementation_workproducts.rst index 855e87adf0..d67e54770d 100644 --- a/process/process_areas/implementation/implementation_workproducts.rst +++ b/process/process_areas/implementation/implementation_workproducts.rst @@ -19,7 +19,7 @@ Workproducts Implementation :id: wp__sw_implementation :status: valid :tags: safety - :complies: std_wp__iso26262__software_851, std_wp__iso26262__software_852, std_wp__iso26262__software_app_c_53 + :complies: std_wp__iso26262__software_851, std_wp__iso26262__software_852, std_wp__iso26262__software_app_c_53, std_req__aspice_40__iic-04-05, std_req__aspice_40__iic-11-05, Implementation includes source code and detailed design (e.g. in form of comments or linked graphical representations) and SW configuration (e.g. #ifdef) The "how to" is described in the SW Development Plan guidelines @@ -43,7 +43,6 @@ Workproducts Implementation - design guideline - coding guideline (e.g. MISRA, can also include style guide or naming convention) - SW configuration guideline - - Method selection (e.g. for Architecture Verification) - development tools .. needextend:: docname is not None and "process_areas/implementation" in docname diff --git a/process/process_areas/implementation/index.rst b/process/process_areas/implementation/index.rst index 26bb067a0d..a58e0ebe49 100644 --- a/process/process_areas/implementation/index.rst +++ b/process/process_areas/implementation/index.rst @@ -23,7 +23,7 @@ Implementation implementation_getstrt implementation_concept guidance/index + implementation_roles implementation_workflow implementation_workproducts - implementation_roles _assets/detailed_design_example.rst