Database Performance Assessment Methodology

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

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.

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.

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

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.

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.

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.

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.

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.

Modeling data quality model is a critical operation to assess the quality of data and fulfill requirements of users. First, several models have been proposed by researchers, and then ISO standards make their apparition to specify quality requirements and evaluate systems and software products. These models have been constructed hierarchically, defined by criteria, sub-criteria and metrics. Studies show the divergence of names and different criteria meaning of such quality model, since there is no universal definition of data quality criteria. Each researcher has its own interpretation and must adapt each model to a specific use field. Faced with this situation, a global data model that contains several data quality models related to each other using equivalence relations is proposed. It offers a generic way to manipulate, explore and quantify any criterion of different data quality models. Our new approach aims at expressing relationships of equivalence among several criteria belonging to different quality models. We use fuzzy logic concepts to evaluate the specified data quality model that was obtained after the application of the equivalent relationships model.

A quantitative approach for assessing the priorities of software quality requirements

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.

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.

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.