Радіоелектронні і комп'ютерні системи (Apr 2020)
SOFTWARE INDIVIDUAL REQUIREMENT QUALITY MODEL
Abstract
The basis of the specification for software development is the requirements profile, which takes into account functionality, features, limitations, risks, etc. of future software. The requirements profile is a product of the profiling process and is a taxonomic structure that links together many of the requirements for the software being developed. An indivisible unit of the requirements profile is a separate software requirement. Formally, the software requirement is a set of related requirements, but it is a more complex object, the quality of the software as a whole depends on its quality. The implementation of insufficient quality requirements in software entails resource losses. Existing works related to this issue do not fully propose the presentation of the quality model of a particular requirement. The purpose of this article is to develop a quality model of an individual software requirement. The object of research is the software requirement. The article is devoted to the development of a quality model of an individual software requirement. The idea of developing the designated model came about after analyzing the following standards: ISO / IEC / IEEE 29148: 2011 (E), ISO / IEC / IEEE 29148: 2018 (E) and ISO / IEC 25012: 2008. The provisions that are presented in the designated standards and formed the basis of this article. It considers the requirement as a separate, unrelated element of the software requirements profile. The requirement is represented in the form of elements of facet-hierarchical structures and consists of a semantic classification attribute and a semantic taxon. A five-component model of the quality of an individual software requirement is proposed, it includes structure, properties, attributes, syntax, and semantics requirements. The combination of such elements in one model allows us to formally describe the quality of an individual software requirement. As a result, this article proposes a formal description and presentation of the quality model of an individual software requirement.
Keywords
