Software Quality Attributes in Requirements Engineering

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

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.

This paper discussed the development of an Online Support Management System to have a centralized system to support the information technology needs of every department of the University of Antique, in effect, to support the needs of the students. The system was developed using the modified Software Development Life Cycle Waterfall Model using six phases – Conceptualization, Technical Feasibility, Development, Pilot Testing, Creation of User’s manual, and Evaluation of Online Support Management System. Each phase must be completed before the next phase can begin and there is no overlapping in the phases. The researcher anchors the study on Research and Development (R&D) which aims to create a new body of knowledge about existing products or processes, or the creation of an entirely new product. Unstructured interviews, document analysis, and modified survey-questionnaire adapted from ISO/IEC 25010: 2011 Systems and Software Quality Requirements and Evaluation (SQuaRE) - System and software quality models had been conducted for data collection. The findings showed that three groups of the respondents were satisfied with the features and capabilities of the Online Support Management System and complied with the requirements or specifications based on ISO/IEC 25010: 2011 standards. Though the respondents are satisfied with their evaluation of the developed Online Support Management System, the result revealed that there was a significant difference noted in the evaluations of the respondents. This result implies that the evaluation made by the three groups of respondents significantly differs from one another in terms of functional suitability, performance efficiency, compatibility, usability, reliability, security, and maintainability.

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.

This article describes empirical research results regarding the "history effect" in software quality evaluation processes. Most software quality models and evaluation processes models assume that software quality may be deterministically evaluated, especially when it is evaluated by experts. Consequently, software developers focus on the technical characteristics of the software product. A similar assumption is common in most engineering disciplines. However, in regard to other kinds of goods, direct violations of the assumption about objective evaluation were shown to be affected by the consequences of cognitive processes limitations. Ongoing discussion in the area of behavioral economics raises the question: are the experts prone to observation biases? If they are, then software quality models overlook an important aspect of software quality evaluation. This article proposes an experiment that aims to trace the influence of users' knowledge on software quality assessment. Measuring the influence of single variables for the software quality perception process is a complex task. There is no valid quality model for the precise measurement of product quality, and consequently software engineering does not have tools to freely manipulate the quality level for a product. This article proposes a simplified method to manipulate the observed quality level, thereby making it possible to conduct research. The proposed experiment has been conducted among professional software evaluators. The results show the significant negative influence (large effect size) of negative experience of users on final opinion about software quality regardless of its actual level.

Microservice architecture (MSA) is a type of software and systems architecture that is based on the modularization principle. It proposes designing systems employing small-scaled, loosely coupled, and independently deployable microservices. There are several benefits of microservices architecture in terms of maintainability, scalability, and productivity which have led to rise in its popularity. Even though there are several studies about development in MSA, the studies on the quality of the microservice-based systems are limited. In this study, we propose a quality model based on fuzzy logic to measure and assess quality attributes of systems in MSA that can be used by software architects, developers, and project managers. We focus on maintainability of microservices because it is one of the most important quality attributes of software systems. We identified sub-characteristics and properties of microservices that affect maintainability, and constructed a hierarchical quality model based on ISO/IEC 250xy standard SQuaRE (System and Software Quality Requirements and Evaluation). Our fuzzy model measures maintainability of microservices in three levels, i.e., low, medium, and high. We provided a basis for the development and application of quality models in industrial practice as well as a basis for further extension. To demonstrate and evaluate our methodology, we used open-source applications designed in MSA. The results show that our method can assess maintainability of microservices realistically.

Systems and software engineering. Systems and software Quality Requirements and Evaluation (SQuaRE). Guide to SQuaRE

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.

Empirical Analysis of Quality Models in Practice in Small IT Companies in SEE Region

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.

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.

Fire safety in remote and geographically isolated regions, such as Bantayan Island, is chronically hindered by fragmented infrastructure, delayed emergency response cycles, and a systemic lack of accessible fire safety education. These vulnerabilities often transform manageable incidents into large-scale disasters. This study introduces the Bantayan Online Fire Report System, a comprehensive web and mobile-based ecosystem engineered to bridge the critical communication gap between residents and emergency personnel. The development process was strictly guided by the ISO/IEC 25010:2011 Systems and Software Quality Requirements and Evaluation (SQuaRE) model, ensuring the platform met rigorous standards for functional suitability, reliability, and the security. The system architecture integrates a centralized administrative dashboard for real-time resource mapping, automated push notifications for rapid dissemination of safety protocols, and a lightweight mobile interface optimized for low-bandwidth environments common in rural areas. By digitizing the reporting pipeline, the platform replaces traditional, high-latency communication methods with instantaneous data transmission and GPS-enabled location tracking. Initial pilot testing and empirical evaluations demonstrated a significant reduction in incident-to-response latency and a measurable increase in community disaster awareness. The system was appraised through usability testing, where it achieved high scores in learnability and user satisfaction among both local authorities and residents. These findings underscore the transformative potential of localized digital interventions in overcoming logistical barriers in underserved communities. Ultimately, the Bantayan Online Fire Report System serves as a scalable prototype for enhancing disaster resilience, proving that integrating technology with civic participation can effectively mitigate fire-related risks and safeguard human life in the remote Maritime Provinces.

Putting Requirements and Quality at the Core of Global Service Delivery: Current Efforts and Future Plans at Pace University

Ontology Software Quality Model for Fuzzy Logic Evaluation Approach

Software Quality Models are a structured software product assessment method. With the rising fashion in software production, new applications are being designed and created daily. This inevitably gives an increase to the need to ensure that the product so constructed meets at least the intended expectations. The software engineering literature includes numerous quality models and each software quality model consisting of various quality attributes or factors or characteristics as some models call them. These quality attributes can be viewed from this feature's perspective to describe the software component or product's quality. A real challenge is to identify which Quality Models to use. The following quality models' content will be presented in this paper by the researcher: McCall's Quality Model, Dromey's Quality Model, Boehm's Quality Model, FURPS Quality Model, and ISO 9126.