Skip to content

Commit

Permalink
process: add aspice standard
Browse files Browse the repository at this point in the history
Tailored processes of APSICE PAM 4.0 are added

Resolves: #318
  • Loading branch information
masc2023 committed Feb 16, 2025
1 parent 046083f commit 7b5bdfd
Show file tree
Hide file tree
Showing 42 changed files with 4,288 additions and 0 deletions.
431 changes: 431 additions & 0 deletions docs/process/standards/aspice/aspice.rst

Large diffs are not rendered by default.

51 changes: 51 additions & 0 deletions docs/process/standards/aspice/iic/iic-01.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************
01-xx
~~~~~

.. std_req:: 01-03 Software Component
:id: STD_BP_ASPICE-40__IIC-01-03
:status: valid

Software Component may have the following characteristics:

- Software element in the software architecture above the software unit
level.
- Represented by a design model element or executable code such as
libs or scripts and a configuration description, if applicable.


.. std_req:: 01-50 Integrated Software
:id: STD_BP_ASPICE-40__IIC-01-50
:status: valid

Integrated Software may have the following characteristics:

- Software executable (e.g, simulator with stubbing, debug-able, object
code) including:

- application parameter files (being a technical implementation solution for configurability-oriented requirements)
- all configured software elements

.. std_req:: 01-52 Configuration item list
:id: STD_BP_ASPICE-40__IIC-01-52
:status: valid

Configuration item list may have the following characteristics:

- Items under configuration control
- The name of work products and an associated reference (to file, to tool artifact)
- Configuration item attributes and properties

31 changes: 31 additions & 0 deletions docs/process/standards/aspice/iic/iic-02.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************
02-xx
~~~~~

.. std_req:: 02-01 Commitment / agreement
:id: STD_BP_ASPICE-40__IIC-02-01
:status: valid

Commitment / agreement may have the following characteristics:

- Signed off by all parties involved in the commitment/agreement
- Establishes what the commitment is for
- Establishes the resources required to fulfill the commitment, such as:
- time
- people
- budget
- equipment
- facilities
61 changes: 61 additions & 0 deletions docs/process/standards/aspice/iic/iic-03.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************
03-xx
~~~~~

.. std_req:: 03-06 Process performance information
:id: STD_BP_ASPICE-40__IIC-03-06
:status: valid

Process performance information may have the following characteristics:

- Measurements about defined quantitative or qualitative measurable indicators, that match defined information needs.
- Measurement metrics for the calculation of the quantitatively or qualitatively measurable indicators
- Data comparing process performance against expected levels
- Examples for project performance information:
- resource utilization against established target
- time schedule against established target
- activity or task completion criteria met
- defined input and output work products available
- process quality against quality expectations and/or criteria
- product quality against quality expectations and/or criteria
- highlight product performance issues, trends
- Examples for service level performance information:
- references any goals established
- real time metrics related to aspects such as:
- capacity
- throughput
- operational performance
- operational service
- service outage time
- up time
- job run time

.. std_req:: 03-50 Verification Measure Data
:id: STD_BP_ASPICE-40__IIC-03-50
:status: valid

Verification Measure Data may have the following characteristics:

- Verification measure data are data recorded during the execution of a
verification measure, e.g.:

- for test cases: raw data, logs, traces, tool generated outputs
- measurements: values
- calculations: values
- simulations: protocol
- reviews such as optical inspections à findings record
- analyses: values

78 changes: 78 additions & 0 deletions docs/process/standards/aspice/iic/iic-04.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************
04-xx
~~~~~

.. std_req:: 04-02 Domain architecture
:id: STD_BP_ASPICE-40__IIC-04-02
:status: draft

Definition not available yet in PAM4.0 document.

.. std_req:: 04-04 Software Architecture
:id: STD_BP_ASPICE-40__IIC-04-04
:status: draft

Software Architecture may have the following characteristics:

- A justifying rationale for the chosen architecture.
- Individual functional and non-functional behavior of the software
component
- Settings for application parameters (being a technical implementation
solution for configurability-oriented requirements)
- Technical characteristics of interfaces for relationships between software components such as:

- Synchronization of Processes and tasks
- Programming language call
- APIs
- Specifications of SW libraries
- Method definitions in an object- oriented class definitions or
UML/SysML interface classes
- Callback functions, “hooks”

- Dynamics of software components and software states such as:

- Logical software operating modes (e.g, start-up, shutdown, normal
mode, calibration, diagnosis, etc.)
- intercommunication (processes, tasks, threads) and priority
- time slices and cycle time
- interrupts with their priorities
- interactions between software components

- Explanatory annotations, e.g, with natural language, for single elements
or entire diagrams/models.

.. std_req:: 04-05 Software detailed design
:id: STD_BP_ASPICE-40__IIC-04-05
:status: draft

Software detailed design may have the following characteristics:

- Elements of a software detailed design:

- Control flow definition
- Format of input/output data
- Algorithms
- Defined data structures
- Justified global variables
- Explanatory annotations, e.g, with natural language, for single
elements or entire diagrams/models

- Examples for expression languages, depending on the complexity or criticality of a software unit:

- natural language or informal languages
- semi-formal languages (e.g, UML, SysML)
- formal languages (e.g, model-based approach)

60 changes: 60 additions & 0 deletions docs/process/standards/aspice/iic/iic-06.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************
06-xx
~~~~~

.. std_req:: 06-04 Training material
:id: STD_BP_ASPICE-40__IIC-06-04
:status: valid

Training material may have the following characteristics:

- Updated and available for new releases
- Coverage of system, application, operations, maintenance as appropriate to the application
- Course listings and availability

.. std_req:: 06-50 Integration Sequence Instruction
:id: STD_BP_ASPICE-40__IIC-06-50
:status: valid

Integration Sequence Instruction may have the following characteristics:

- Identification of required physical elements (e.g., hardware,
mechanical, wiring elements), and software executables and
application parameters (being a technical implementation solution for
configurability-oriented requirements)
- necessary sequence or ordering of integration
- preconditions for starting system integration

.. std_req:: 06-51 Tailoring guideline
:id: STD_BP_ASPICE-40__IIC-06-51
:status: valid

Tailoring guideline may have the following characteristics:

- Criteria for tailoring,
- Proceeding of tailoring describing how to derive and document the defined process from the standard process
including responsibility for tailoring and corresponding approval
- Requirements for the defined process to ensure integrity and consistency of the defined process
- Subset of process assets that is essential for the defined process

.. std_req:: 06-52 Backup and recovery mechanism information
:id: STD_BP_ASPICE-40__IIC-06-52
:status: valid

Backup and recovery mechanism information may have the following characteristics:

- Description / confirmation of existing backup and recovery mechanisms
- References to corresponding procedures or regulations
Loading

0 comments on commit 7b5bdfd

Please sign in to comment.