Abstract
The quality of the software product is a crucial factor that contributes to its success. Therefore, it is important to specify the right software quality requirements that will establish the basis for desired quality of the final system/software product. There are several known methodologies/ processes that support the specification of the system/software functional requirements starting from the user needs to finally obtain the system requirements that the developers can implement through their development process. System/software quality requirements are interdependent with functional requirements, which means that the system/software quality requirements are meant to be specified in parallel with the latter. The ISO/IEC 25000 [1] SQuaRE series of standards include the standard ISO/IEC 25030—Software engineering—Software Quality Requirements and Evaluation—Quality requirements [2], which has as main goal to help specify software quality requirements. As to date, this standard does not offer clear and concise steps that a software quality engineer could follow in order to specify them. This article presents modifications recommended for ISO/IEC 25030 standard, with, among the others, a new requirements definition process that allows for specifying the system/software quality requirements taking into account the existing published system and software quality model ISO/IEC 25010 [3] as well as all the stake- holders of the project.
Highlights
The popularity of a system or software is characterized by the set of functionalities it offers and its quality attributes such as, for example, performance, level of security or usability
This article presents modifications recommended for ISO/IEC 25030 standard, with, among the others, a new requirements definition process that allows for specifying the system/software quality requirements taking into account the existing published system and software quality model ISO/IEC 25010 [3] as well as all the stakeholders of the project
To help IT industry in this effort the ISO/IEC Joint Technical Committee 1 (JTC1) Subcommittee 7 (SC7) has developed the series of quality-dedicated standards known as ISO/IEC 25000 Software Quality Requirements and Evaluation (SQuaRE) [1], with ISO/IEC 25030 [2]—Software engineering—Software product Quality Requirements and Evaluation (SquaRE)— Quality requirements in a prominent place
Summary
The popularity of a system or software is characterized by the set of functionalities it offers and its quality attributes such as, for example, performance, level of security or usability. As ISO/IEC 25030, which should describe the process helping to specify the system/software quality requirements, in its actual form is not exhaustive enough to fulfill its basic objective of applicability in real projects, it would benefit from some modifications. In this paper the authors analyze the actual content of the standard, propose modifications and identify several possible improvements, which, when applied, would render the standard more useful to the IT industry. The rest of the paper is organized as follows: Section 2 describes the methodology of the presented research.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
