Software Quality Requirements: How to Balance Competing Priorities

A quantitative approach for assessing the priorities of software quality requirements

The scale of software is growing rapidly for organizations begin to deploy their business on internet. It is a need of avoid ambiguity between engineers and users and to avoid mistakes in software requirements. And provide automatic requirement analysis techniques for modeling and analyzing requirements formally and save manpower. In this paper proposed cloud service method for automated detection of quality requirement in software requirement specification. This paper also present novel approach for process of automatic classification of software quality requirements based on supervised machine learning technique applied for the classification of training document and predict target document software quality requirements.

Software quality assurance (SQA) must be able to support the practical application. This chapter presents the models as well as the software engineering standards available for correctly defining performance or non‐functional requirements of software. It describes the research carried out over the years that culminated in a definition of a software quality model. Quality assurance, in certain industries and business models overseen by the software developer, requires a more formal management of software quality throughout the software life cycle. Quality is often measured by considering a specific perception of quality. The chapter provides the SQA practitioner with the knowledge to use the ISO 25010 software quality model concepts. It presents the history of the different models and standards designed to characterize software quality. The chapter introduces the concept of quality requirements and presents a process for defining quality requirements.

As software systems continue to grow more complex, evaluating software quality becomes increasingly critical. This study analyzes existing software quality models, including McCall, Boehm, FURPS, and ISO Systems and Software Engineering – Systems and Software Quality Requirements and Evaluation (SQuaRE), with a specific focus on the ISO/IEC 25010:2023 standard. The research aims to assess the completeness of these models and explore interdependencies among key quality attributes relevant to software requirements engineering. The paper identifies key characteristics and associated metrics based on ISO/IEC standards using comparative analysis and a literature review. Findings show that ISO/IEC 25010:2023 provides the most comprehensive structure, with Functional Suitability and Compatibility identified as essential due to their universally recommended metrics. Survey data from 328 practicing analysts in Ukraine and internationally demonstrate a gap between theoretical models and real-world requirements documentation practices, particularly for non-functional requirements. The identified dependencies between quality attributes enable a more integrated and structured approach to identifying and analyzing non-functional requirements in IT projects. The study emphasizes that software quality models must be tailored to project-specific goals and constraints, with attention to trade-offs and stakeholder needs during the requirements specification, prioritization, and validation processes. The findings support the adaptation of quality models to specific project constraints and emphasize the business analyst’s role in tailoring quality criteria for practical use in software development.

System and software quality evaluation is an important method of quality assurance, and its standardization provides quality requirements and evaluation supported by quality measurement. ISO/IEC organizations have also published a series of standards on system and software quality requirements and evaluation, which is significant for assuring the quality of system and software. This paper introduces quality evaluation based on SQuaRE series standards, and analyzes the relationships among quality model, measurement, requirements, evaluation. Besides, considerations and suggestions are given when applying the measurement function to quality evaluation. Finally, comparison with different methods of quantifying quality characteristics and sub-characteristics with the measured values is analyzed.

The goal of any automatic process is to run without human intervention. However, it is not uncommon that unexpected issues recur, requiring repetitive human intervention in order to processes execute successfully. Such situations indicate that those processes were not designed with the necessary quality requirements to achieve the automation goal, and quality needs to be improved. This paper describes a case study of the quality improvements of several automatic ETL processes that required a growing amount of effort to ensure its successful execution. Key to the improvement process was the use of the ISO/IEC 25010 Standard for Systems and Software Quality Requirements and Evaluation to categorize all issues found. This approach proved beneficial in two important ways: first, it created a clear understanding of the overall ETL processes quality problems, second, it made obvious which issues deserved uttermost attention.

The database of the automated control system is an artificial functioning object that provides information services. The process of database functioning occurs with some finite efficiency. To improve the information support of the automated system, it is necessary to obtain an accurate assessment of the efficiency of the basis – the database. Modern approaches to assessing the quality of databases based on the standards ISO / IEC 25012: 2008 "Software engineering – Software product. Quality Requirements and Evaluation (SQuaRE) – Data quality model" and ISO / IEC 25024: 2015 "Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Measurement of data quality" do not provide the ability to obtain objective numerical estimates. There is a contradiction between the need to obtain accurate estimates of the intensity of significant properties of the database and the available tools for solving this problem. Purpose. Development of a template of a parametric database model suitable for forming a list of operational and technical requirements for a database in the process of assessing the effectiveness of its functioning for its intended purpose. Results. A list of significant operational, result and resource properties of a typical database of an automated control system for a complex organizational and technical object has been formulated, using the example of a spacecraft flight control center (MCC). Measurable parameters of database functioning as an artificial object implementing a targeted process of satisfying the information needs of users (applied processes) have been put forward. Proposals have been developed for the structures of convolution of measurable parameters of database functioning, presented in the form of oriented graphs. Interpretations have been developed for formulating private indicators of the effectiveness of the functioning of the automated control system database. A methodological basis has been created for developing procedures for assessing the effectiveness of the database. Practical significance. A set of structural models of private performance indicators of the functioning of the database of an automated control system for an organizational and technical object, provided with measurable parameters, has been developed to form procedures for assessing the effectiveness of its functioning in the task of improving the management cycle.

: The ASQS, a knowledge base software tool, assists software acquisition managers which specify software quality requirements. In the consultation mode, questions are presented to the acquisition manager in terms related to the mission area of interest. Answers are transformed by ASQS into tailored quantitative quality goals based on the thirteen software quality factors of the RADC software quality framework. The current version supports the Intelligence and Satellite mission areas. ASQS serves the purpose of transitioning the Software quality specification methodology found in the RADC final report RADC-TR-85-37, Vol II (of three), Specification of Software Quality Attributes - Software Quality Specification Guidebook, into use in the DOD acquisition process. In so doing, it reduces the amount of time and the expertise required to specify meaningful software quality goals. It bridges the gap between software quality concepts and terminology and the system needs and terminology understood by the acquisition manager. (Author) (kr)

Software stakeholders, including developers, managers, and end users, require high quality software products. Several works have aimed to identify software quality, but the quality of software products is often not comprehensively, specifically, or effectively defined because previous approaches have focused on certain quality aspects. Moreover, the evaluation results of quality metrics often depend on software stakeholders so that it is often hard to compare quality evaluation results across software products. ISO/IEC has tried to define evaluation methods for the quality of software products and provide common standards, called the SQuaRE (Systems and software Quality Requirements and Evaluation) series including ISO/IEC 25022:2016 and ISO/IEC 25023:2016. However, the SQuaRE series include ambiguous metrics so that it is not always easy to apply the series to products and compare results. In this paper, we propose a SQuaRE-based software quality evaluation framework, which successfully concretized many product metrics and quality in use metrics originally defined in the SQuaRE series1. Through a case study targeting a commercial software product, we confirmed that our framework is concretely applicable to the software package/service product.

The comprehension and correct specification of requirements increase with the complexity of present software systems, particularly if they have to respond to requirements going beyond the range of the main system functionality and that must be taken into account early during the development process. The Scientific community focuses now on the requirements engineering discipline, for the importance of nonfunctional or quality requirements with direct impact on the accomplishment of the main system's functionalities. This work models an aspect-oriented quality requirements engineering process (AOQuaRE), based on the treatment of non-functional requirements scattered and/or entangled among the functionalities of the system (crosscutting concerns), from the early steps of the development process. An important contribution of this work is the specification of quality requirements by the new standard ISO/IEC 25010 for software product quality.

Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to define quality requirements more completely and correctly.

Quality measured and evaluated based on organization-specific quality models cannot be compared to the quality of other software products. To alleviate this problem, ISO/IEC defined international standards called the SQuaRE (Systems and software Quality Requirements and Evaluation) series for comprehensive quality measurement and evaluation, however, these standards include ambiguous measurements, making them difficult to apply. Herein an initial comprehensive quality measurement framework, which includes a clear measurement plan based on ISO/IEC 25022 and 25023, is proposed. A case study confirms the usefulness of the framework. As future work, we will introduce the framework to various domains. And then, we revise and refine measurements and evaluation plans to improve feasibility and usefulness.

У статті розкриваються погляди на методологію та порядок оцінювання спеціального програмного забезпечення з урахуванням вимог Національних стандартів України ДСТУ ISO/ІЕС 25010:2016 (ISO/ІЕС 25010:2011, IDT). “Інженерія систем і програмних засобів. Вимоги до якості систем і програмних засобів та її оцінювання. Моделі якості системи та програмних засобівˮ та ДСТУ ІS0/ІЕС 9126-1:2013 (ІS0/ІЕС 9126 1:2001, IDТ). “Програмна інженерія. Якість продукту. Частина 1. Модель якостіˮ. Як приклад розглядається перевірка якості спеціального програмного забезпечення для управління військами.

Software testing is an extremely important work link in software engineering. It runs through the entire life cycle of software engineering to ensure that software development meets requirements and can meet certain software quality requirements. With the continuous expansion of the scale of information systems, simple software testing can no longer meet the requirements of system and software quality assurance. This requires practitioners to gradually begin to think about and improve the testing methods of large-scale information software. For large-scale information software, testing will be embedded in each unit, and the software testing process will be organized in a more macroscopic way of thinking and organization. This article will summarize a series of methods suitable for large-scale information software testing through the research of software testing and the practice of the author. It is hoped that the research in this article can provide some help for the testing of large-scale information software, and also provide help for the precipitation and improvement of the author's own work.

Many computing students do not receive adequate training in software quality management. Some students do not have the opportunity to practice software process improvement activities even if they do see the topics covered in their course lectures and textbooks. Serious games are gaining popularity as a means of instruction in higher education. Some excellent prescriptive software process simulation games have been created, as well as a few software engineering drill and practice games. In general, these games do not allow students to create agile process models or experiment with process improvement strategies. We are creating a serious game that will serve as a virtual learning environment to allow students to explore agile process improvement practices. Our game is designed as a single-player game where the player takes the role of software team leader and plays against an AI (artificial intelligence) opponent representing the customer's interests and needs. Players are rewarded for developing project strategies that allow for completion of projects on time, within budget, and meet the necessary software quality requirements. It is our intention to create a game with sufficiently detailed instructions to allow instructors to introduce hands on practice with agile process improvement activities without requiring additional class time.