Identify Compliance During Software Development Using System Engineering Principles


Errors made during the requirements collection and analysis phase make it very difficult to maintain the software product and cost the company extra costs. The difficulty of directly collecting requirements from stakeholders is due to inconsistencies between the major stakeholder groups, as well as related factors in the collection of requirements itself, as well as the selected methodology for the process of converting stakeholder requirements into development requirements. As a solution, it is necessary to use a high level of prioritization in order to distinguish among many requirements the necessary for successful implementation of the product, as well as to correctly allocate compliance with the requirements in such a way that each group of stakeholders is satisfied, but at the same time setting the goals of the supersystem more priority  than the goals of the subsystem. This article discusses the methodology of system engineering to solve issues related to the identification of possible contradictions of requirements.

Keywords: System engineering, requirements engineering, business process, requirements, software product, analysis.

[1] Karl I. Vigers, software requirements Development, Moscow: Russian edition, 2004, ISBN 5-7502-0240- 2.

[2] A. A. Sergeevich, ””Information support of process of development of requirements to a hi-tech product”, ” Economics, pp. 59-62, 2017.

[3] Hitchins D. What are the General Principles Applicable to Systems? — INCOSE INSIGHT. — V. 12, Issue 4. — December 2009. — pp. 59–64

[4] ISO/IEC/IEEE 29148:2018 Systems and software engineering — Life cycle processes — Requirements engineering