Skip to content

add aspice 4 ml3 architecture #702

Open
RolandJentschETAS wants to merge 3 commits into
eclipse-score:mainfrom
etas-contrib:improvement_architecture_ml3
Open

add aspice 4 ml3 architecture #702
RolandJentschETAS wants to merge 3 commits into
eclipse-score:mainfrom
etas-contrib:improvement_architecture_ml3

Conversation

@RolandJentschETAS

Copy link
Copy Markdown
Contributor

This pull request updates the architecture design process documentation to improve compliance with ASPICE requirements, clarify process monitoring, and provide additional guidance on tailoring architectural documentation for component complexity and safety classification. It also clarifies the division of responsibilities between the middleware platform and system-level integration, and expands the required skills for project development roles.

Compliance and Process Monitoring:

  • Expanded the list of compliance requirements in the architecture_guideline.rst and architecture_inspection_checklist.rst to include additional ASPICE process and base practice references. [1] [2]
  • Added a new section on process monitoring, including a needtable for process monitoring activities, and introduced a process requirement for monitoring and improving the architecture process in architecture_guideline.rst and architecture_process_reqs.rst. [1] [2]

Guidance and Tailoring for Architectural Documentation:

  • Added guidance on reusing documentation for proven-in-use components, requiring a delta analysis for deviations and changes in application conditions.
  • Provided tailoring guidance for component complexity: internal decomposition may be omitted for simple components, but the external interface view remains mandatory.
  • Clarified tailoring for safety classification: dynamic views may be omitted for QM components if the static view is sufficient, but are required for safety-relevant components (ASIL B or higher).

Scope and Responsibilities:

  • Added a new section clarifying that system-level integration, HSI design, application-specific scheduling, and system-level safety architecture are out of scope for the platform architecture process, and must be addressed by platform users. Also, specified that Assumptions of Use (AoU) must be documented and communicated.

Project Roles and Skills:

  • Expanded the required skills and knowledge for project development roles, emphasizing experience with architectural review, ASPICE SWE.2, traceability, software design principles, relevant tooling, safety/security, and modeling notations.

@github-actions

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant