chapter9 - PacoReinaCampo/gnumig GitHub Wiki

REQUIREMENTS

.. ....... ........ ........ ....... .. ........... ...... .... .. ...... ..... .. ..... .... ........ ... ...... . ... .... .. ......... ........... .... .... ........ .. .... . ..... ....... .... ... ........ .... ............ .. ... ... ....... .. ...... .... ... .... ....... .. ..... ... .... ....... ... ....... ......... ..... .......... ....... ..... ....... ... ....... ... ....... ..... ..... .... . ........ .. ... ..... ......... .. ........ ..... ....... .......... .......... ... ........ .. ... ..... .. ........ ..... .......... .... ... ...... .. .....

SOFTWARE REQUIREMENTS PROCESS

The software requirements process uses the outputs of the system life cycle process to develop the software high-level requirements. These high-level requirements include functional, performance, interface and safety-related requirements.

Software Requirements Process Objectives

The objectives of the software requirements process are:

a. High-level requirements are developed.

b. Derived high-level requirements are indicated to the system safety assessment process.

Software Requirements Process Activities

Inputs to the software requirements process include the system requirements, the hardware interface and system architecture (if not included in the requirements) from the system life cycle process, and the Software Development Plan and the Software Requirements Standards from the software planning process. When the planned transition criteria have been satisfied, these inputs are used to develop the software high-level requirements.

The primary output of this process is the Software Requirements Data (subsection 11.9).

The software requirements process is complete when its objectives and the objectives of the integral processes associated with it are satisfied. Guidance for this process includes:

a. The system functional and interface requirements that are allocated to software should be analyze for ambiguities, inconsistencies and undefined conditions.

b. Inputs to the software requirements process detected as inadequate or incorrect should be reported as feedback to the input source processes for clarification or correction.

c. Each system requirement that is allocated to software should be specified in the high-level requirements.

d. High-level requirements that address system requirements allocated to software to preclude system hazards should be defined.

e. The high-level requirements should conform to the Software Requirements Standards, and be verifiable and consistent.

f. The high-level requirements should be stated in quantitative terms with tolerances where applicable.

g. The high-level requirements should not describe design or verification detail except for specified and justified design constraints.

h. Each system requirement allocated to software should be traceable to one or more software high-level requirements.

i. Each high-level requirement should be traceable to one or more system requirements, except for derived requirements.

j. Derived high-level requirements should be provided to the system safety assessment process.

LANGUAGES

Software Project Workflow

Software Project Workflow

CONTROL	DEVELOP	OPERATION
certification	model	sim
doc	rtl/src	compilation
quality	configuration	synthesis
requirements	validation
	verification

:Hardware DevOps

Front-End CoDesign Project Workflow

Back-End CoDesign Project Workflow

details(requirements) < details(model) < details(rtl) < details(configuration) < details(synthesis)
details(requirements) < details(model) < details(src) < details(configuration) < details(compilation)
details(validation) < details(verification) < details(sim)

Unified Modeling Language

Structural UML diagrams (for Architecture and Interface)
- Class diagram
- Component diagram
- Composite diagram
- Deployment diagram
- Object diagram
- Package diagram
- Profile diagram
Behavioral UML diagrams (for Functionality and Registers and Interrptions)
- Activity diagram
- Communication diagram
- Interaction diagram
- Sequence diagram
- State diagram
- Timing diagram
- Use diagram

UML Diagrams Overview