RE.3.3.3 Technical Requirements (TReq)
In this product, Technical Requirements for the overall System, the Segments and the SW Units/HW Units are defined. Along with these elements of the product structure, a corresponding functionality will be presented, and the technical requirements for interfaces, quality requirements and the technical requirements for the development and SWMM environment will be defined.
Technical Requirements that could not be allocated to any element of the product structure are documented as general requirements.
1. General Information
2. General Requirements
3. Technical Requirements for the Overall System
4. Technical Requirements for SW Units/HW Units
4.x.1. Identification of the Element
4.x.2. Overall Function of Element
4.x.3. Technical Requirements for the Interfaces
4.x.3.1. Technical Requirements for the User Interface
4.x.3.2. Technical Requirements for Other Interfaces
4.x.4. Quality Requirements
4.x.4.2. Technical Requirements for the IT Security
4.x.4.3. Technical Requirements for Other Quality Characteristics
4.x.5. Technical Requirements for the Development and SWMM Environment
See schema 1. General Information.
This is a list of the technical requirements that could not be allocated to any element of the technical architecture.
Structure: see below
Structure per SW Unit/HW Unit: see below
For each element x (= Segment or SW Unit/HW Unit) of the System Architecture the Technical Requirements must be specified as follows:
The considered architecture element is identified by means of the conventions defined in the CM Plan, and the corresponding long name is given.
The functionality of the element is represented as a whole; in this connection, it is necessary to refer to the task of the element, to operating modes and to application fields.
In the case where the considered element has a direct user interface it will be described how it will be technically implemented. In the case of software interfaces, this might include the definition of masks, windows, and dialog sequences. In the case of hardware interfaces, this might include operating devices for adjustments, parameter settings, and data input. (Contrary to the User Requirements, this chapter does not define the information requirements, but the technical realization.)
The technical requirements for the interfaces of the considered element to other elements are defined. The identification of the interfaces and the corresponding partners result from the System Architecture.
The refinement level of the description required here must chosen so it can be both starting point and decision base for the further development.
The criticality of the entire element is named and justified. The classification of the criticality level must be compatible with the criticality statements of the corresponding User Requirements.
The requirements for the IT security defined within the scope of the User Requirements are converted into technical requirements; they have to be defined in this chapter. (They might include: the requirement for mechanical protecting of floppy disk drives or the requirement for a way to prevent by means of software a new boot procedure by the user.)
This chapter defines requirements with regard to
The basis is /DIN ISO IEC 9126/.
This chapter is necessary for the overall System and for independently and separately developed elements.
- user friendliness
- static and dynamic performance data
- changeability, etc.
This chapter has to describe the requirements for the development, integration and test equipment that are connected with the considered element of the technical architecture during development and SWMM.
In particular, the following requirements have to be defined:
- development computer equipment,
- target computer equipment,
- tools related to the target computer, and
- test equipment.
- The information of SW Units/HW Units belonging to a segment may be combined and edited in one chapter. This way, it is possible to illustrate refinement levels more clearly.
- With regard to allocating the realization of individual technical SW components, the implementor always gets the Technical Requirements belonging to the corresponding element, as well as the relevant set of user-level requirements.
Relevant user-level requirements for higher structure levels have to be decomposed since they cannot be completely allocated to the element in question. Uncertain delimitations from other parts of the System Architecture must be avoided. The coverage of requirements should neither include overlaps (danger of double allocation and unclear interfaces) nor gaps.
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster