|
Determine appropriate notations for software architectural design
The notation that a design is expressed in
has a bearing on the understandability of the design. The typical forms of
expression are Informal (such as hand drawn flow diagrams or visio
diagrams) , Semi-Formal, (such as UML where the design is developed in a
consistent manner in a well defined language, in a model based
process) and Formal (such as Z, CSP or VDM, where the design is expressed
as sets of complex predicate logic and formulas). The notations
applicable for software architectural design the are dependent on the ASIL
of the item being
developed.
Informal Notations are highly recommended for Items of ASIL A
or B and recommended for items of ASIL C or
D,
Semi-Formal notations
are
highly recommended for
Items of ASIL B,C and recommended for items of ASIL
A
Formal notations
are
recommended for Items of
ASIL A,B,C or
D and
This information is a summary of the information taken
from ISO 26262 vol 6 clause 7.4.1 table 2- Methods to verify the
correctness of safety
requirements.
|
Determine appropriate principles for software architectural design
A number of best practices are referred to
in "Table 3 - Principles for software architectural design"
located in ISO 26262 vol 6, clause 7.4.3, to help the developer decide on
the principle design methods that are applicable to a particular ASIL
level. This covers the following guiding principles.
Hierarchical structure of software components (highly recommended for
items of all ASILs) Restricted size of software
components (highly recommended for items of all ASILs)
Restricted size of software components (recommended for items of
all ASILs) High cohesion within each software
component (recommended for items of ASIL A highly
recommended for items of ASIL B, C or D)
Restricted coupling between software components (recommended for
items of ASIL A highly recommended for items of ASIL B,
C or D) Appropriate scheduling properties
(highly recommended for all ASILs) Restricted use of
interrupts (recommended for ASILs A-C highly recommended for ASIL D)
These principles help define the properties
that the architecture should exhibit, such as modularity, encapsulation,
and simplicity It is noted that a compromise of methods listed in the
table can be selected as they are not necessarily mutually exclusive.
This
information is a summary of the information taken from ISO 26262
vol 6 clause 7.4 .3, Table 3- Principles for
software architectural
design
It is recommended that the user refers to ISO 26262, vol 6,
clause 7.4.3 for further guidelines on the principles for software
architecture design. |
Develop SW architectural design
The software architectural
specification/design shall capture the static and dynamic aspects
of the architecture (see ISO 26262, vol 6, clause 7.4.5). In the case of
model based development capturing the structure and behavior of the item
under development is an inherent part of the overall modeling activities.
When developing the software architectural design the
following concerns need to be considered That the software
architecture needs to be verifiable, this implies bi-directional
traceability between the software architectural design and the software
safety requirements Whether it is suitable
to use configurable software How feasible is it to
implement the design and software units The
maintainability of the software architectural design
The software design shall be
developed down to the level where all the software units are identified
and it shall describe the static (structural) and dynamic
(behavioral) aspects of the software. If
software partitioning is used, as described in ISO 26262, vol 6, annex D
to prevent interference between software components then it shall be
ensured that If employing shared resources that the software partitions do
not interfere with one another and that the part of the software that
implements the software partitioning shall have the same or higher ASIL
than the highest ASIL associated with the component.
A technique highly recommended for ASIL D and recommended for ASILS A,B
and C is that software partitioning is supported by dedicated hardware
features. The software partitions shall be verified
correctly during software integration and testing.
ASIL decomposition if used shall be applied according to ISO 26262. vol 9,
clause 5. |
Trace SW architectural design back to SW requirements
There shall be a categorization of
every safety related component as being either Newly
developed Reused with modifications
Reused without modifications
If the category is newly
developed or reused with modifications then they shall be developed in
accordance with ISO 26262. If the category
is reused without modifications then the component shall be qualified in
accordance with ISO 26262, vol 8 clause 12.
|
Determine appropriate methods for error detection and error handling at the software architectural level
Mechanisms for error detection and error
handling are based upon the results of the safety analysis. These
mechanisms are applicable to specific ASILs Please
refer to Table 4 - Mechanisms for error detection at the software
architectural level located at ISO 26262 vol 6, clause, 7.4.14, to see the
complete mapping of mechanism, detailed below to ASIL levels.
Range
checks of input and output data is highly recommended for items of all
ASILs Plausibility check, including assertion checks
and using reference models of desired behavior for complex checks
is highly recommended for items of ASIL D and
recommended for items of ASILS A B or C
Detection of data errors, such as error detection
codes and multiple data storage, is recommended for items
of all ASIL levels External monitoring
facility is highly recommended for items of ASIL D and
recommended for items of ASIL B or C, with an unbiased opinion on its usage for items of ASIL
A Control flow monitoring
is highly recommended for items of ASIL C or D and
recommended for items of ASIL B, with an unbiased opinion on its usage for items of ASIL
A Diverse software design (not intended
to imply n-version programming) is highly
recommended for items of ASIL D and recommended
for items of ASIL C, with an
unbiased opinion on its usage for items of ASIL A or B
Please refer to
Table 5 - Mechanisms for error handling at the software
architectural level located at ISO 26262 vol 6, clause, 7.4.15, to see the
complete mapping of mechanism, detailed below to ASIL levels. These
mechanisms are recommended for items of ASIL A or B and required for items
of ASIL C or D Static recovery mechanisms, (such as,
recovery blocks, backward and forward recovery and recovery through
repetition) are recommended for items of all ASIL levels
Graceful degradation, this refers to prioritizing
functions to reduce the adverse affects of possible failures on the
functional safety of the item, are highly recommended for items of ASIL C
or D and recommended for items of ASIL A or B.
Independent parallel redundancy, for this mechanism to be successful there
has to be dissimilar software in each parallel path, are
highly recommended for items of ASIL D and recommended for items
of ASIL C, with an unbiased opinion on its usage for
items of ASIL A or B Correcting
codes for data (this mechanism is recommended for items of all ASIL
levels) .
This information is a summary of the information
taken from ISO 26262 vol 6
clause 7.4.14/15 detailing the Mechanisms
for error detection at the software architectural
level and the Mechanisms for error
handling at the software architectural
level. .
|
Estimate SW resources
Finally, an upper estimation of the required
resources for the embedded software should be made, these should cover
aspects such as execution time, storage space and communication resources.
|
|