-
Notifications
You must be signed in to change notification settings - Fork 22
How to close a design step
This wiki page is intended as a guideline for verification and design answering the question: What is needed to close a design step related to a design phase.
The design phase is defined inside the CENELEC norm EN50126 and EN50128. The design step is defined as the activity required related to a subtopic of a design phase which is needed to close the phase related to this topic. The product scope is the scope of the product intended to be developed.
Within this wiki page a high level overview is translated into a minimum list of activities required to start the closing verification. Underneath the list of activities do not mention all activities needed to close a phase but mention the minimum stet of input data to start verification on the phase in an agile way.
- tarceability on system level
- methods, tools and techniques used
- suporting documents are needed 'on top of the model'
-
Functional Architecture Specification (step 1)
- functional architecture containing the list of initial functions intended to cover all functionalities within the product scope
- for every function a specific description of it's functionality and the traceability to the SRS
- input and output to/ from each function including all overall system interfaces to which the input/ output relates
-
Software Design Specification (step 2)
- component architecture containing the allocation of the functions to the software modules
- for every function a specific description of it's functionality and the traceability to the SRS allocating the functionality to the components
- input and output to/ from each function including all overall system interfaces to which the input/ output relates