Requirements to technology with a tool for the development of complex software automation.

The content of the stages and works during the creation of the components and the PS as a whole is defined by the standards and models of the VCPS. The required reliability of objects is formed and ensured during the execution of each stage and finally certified by tests and docs when tested.
To ensure the quality of NPS standards it is recommended to formulate the requirements:
1. To the object of development at this stage, its program and information components, as well as to the interface with them and with the external environment.
2. For the process, technology and organization of performance of the totality of works and documents of each stage.
3. ……

Compliance with these requirements should be monitored at each stage. Quality indicators are recorded and compared with the given. Upon detection of deviations from the requirements, measures should be taken, or to adjust the requirements for indicators ....
Requirements for software development automation tools are most fully set forth in the IEEE 1209 standard. This standard provides guidelines for evaluating and selecting tools supporting the life cycle processes of a software system, including project management processes, development processes, and processes following development.
For evaluation and selection of the instrumental environment and CASE-tools, the standard recommends the use of sets of rules and criteria that are formed taking into account the requirements of std. ISO 9126.
IEEE 1209 formulates requirements for the technological environment and CASE-development tools, for the management tools for complex PS projects and for the support and development tools for the tech. and operational documentation.
Compliance with this standard db. An analysis of the potential correctness and reliability of the components included in the PS component is provided. This analysis includes the procedures:
1. Evaluation of the complexity of the prog., Due to the number of nested cycles, full coverage of tests.
2. Evaluation of the number of remaining errors.
3. Analysis of the source code and presentation to the user of the results of measuring dimensions, calculating complexity metrics.
4. Compliance review using standards.