-
a. In section 4.1, the description of the context in which the software engineering standard operates,
together with the explanation of the importance of following standards to get proper
engineering.
-
b. In section 4.2, elaboration on key concepts that are essential to get compliance with the Standard,
such as the roles, the software characteristics, the criticality, the tailoring and
the contractual aspects.
-
c. In section 5, following the table of content of the ECSS‑E‑ST‑40C Standard, discussion on the topics addressed in the Standard, with the view of addressing
the issues that have been reported in projects about the interpretation, the application
or the feasibility of the requirements. This includes in particular:
-
1. Requirement engineering and the relationship between system and software
-
2. Implementation of the requirements of ECSS‑E‑ST‑40 when different life-cycle paradigms are applied (e.g., waterfall, incremental, evolutionary,
agile) and at different levels of the Customer-Supplier Network
-
3. Architecture, design and implementation, including real-time aspects
-
4. Unit and integration testing considerations, testing coverage
-
5. Validation and acceptance, including software validation facility and ISVV implementation
-
6. Verification techniques, requirements and plan
-
7. Software operation and maintenance considerations.
-
d. In section 6 and 7, more information about selected topics addressed in section 5 such as (in section 6) use cases, life cycle, model based engineering, testing, automatic code generation,
and (in section 7) technical budget and margin, computational model and schedule analysis.
NOTE In order to improve the readability of the Handbook, the following logic has been
selected for sections 5, 6, and 7:
-
•
section 5 follows the table of content of ECSS‑E‑ST‑40C at least up to level 3 and generally up to level 4. For each sub clause of ECSS‑E‑ST‑40C:
-
+ either information is given fully in section 5,
-
+ or there is a pointer into section 6 or section 7
-
+ or the paragraph has been left intentionally empty for consistency with the ECSS‑E‑ST‑40C table of content, in this case, only “ -“ is mentioned.
-
•
section 6 expands selected parts of section 5 when:
-
+ either the volume of information was considered too large to stay in section 5,
-
+ or the topic is addressed in several places of section 5
In any case, there is a pointer from section 5 to section 6, and section 6 mentions the various places in ECSS‑E‑ST‑40C where the topic is addressed.
-
•
section 7 follows the same principles as section 6, but gathers the topics related to margins and to real-time.
-
e. In Annex A, as a complement to the ECSS‑E‑ST‑40C Annex A called Document Requirement List [DRL], the documents expected at the Technical Reviews
such as SWRR, DDR, TRR and TRB.
-
f. In Annex B, software engineering techniques appropriate for the implementation of specific ECSS‑E‑ST‑40C clauses and their selection criteria, covering most of the software lifecycle.
-
g. In Annex C, an example of the Document Requirement Definition of the Software Maintenance Plan.