REquirements, Aspects and Software Quality: the REASQ model.

This chapter focuses on software engineering conceptual modeling, its current weaknesses, and the alternatives to overcome them. It is clear that software quality has its genesis in the conceptual model and depends on how well this model matches the problem in question. However, this chapter presents a representative study of the analysis approaches that highlights that (i) they have traditionally focused on implementation and have paid little or no attention to the problem domain and (ii) they have omitted the various stakeholders (viewpoints) generally involved in any problem. The proposed alternatives are based on those aspects that are related to a generic conceptualisation, independent of the implementation paradigms.

Aspect oriented software engineering has become a promising domain to address the challenges faced by the procedural and object oriented software development. It has solved the problem of separation of concerns by modularizing the crosscutting concerns that helps in reducing the maintenance cost. AOSE has introduced new features which in turn produces new kind of errors. As the main goal of software development is to produce the best quality product and the quality of software is widely depends on how testing is performed. Hence, testing remains an inescapable task in aspect oriented software development. In this paper an outline of aspect-oriented software engineering, along with the research work done by various authors on testing methods used in the area of aspect-oriented paradigm is presented. It is found that unit testing, integration testing and mutation testing are widely used techniques in aspect oriented software testing. It is also predicted from the approaches that graph based coverage is widely used as compared with other approaches.

AOSD (Aspect Oriented Software Development) is an emerging discipline in Software Engineering. It focuses on the separation of concerns of the ’70s, aiming at improving modularity, to ensure maintainability in the sense of extensibility, changeability and reuse, towards an evolutionary software product responding to a more dynamic environment. The AOP (Aspect Oriented Programming) paradigm of the ’90s focuses on the separation of the crosscutting concerns, which are in general non functional requirements (quality requirements). It is now of general agreement that the entanglement and scattering of concerns must be handled early in the software life cycle. However, these aspects are inherent to all the stages of software development, from requirements elicitation to code implementation. Many concepts and mechanisms have been proposed to handle properly these issues; however terms are in general semantically slightly dierent in each discipline where they have been formulated and used, causing misunderstanding and confusion. This paper presents an AOSD UML core for early aspects (requirements, analysis and design disciplines), constructed gathering dierent modelling elements found in the literature, focusing particularly on the AOSD ontolgy document of the Common Foundation for AOSD of the European Community, and dierent

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 quality engineering (SQE) is essential for ensuring that software applications meet the required standards of functionality, performance, security, and reliability. As software development methodologies evolve, the need for a comprehensive, holistic approach to software quality has become more critical. This paper explores the concept of mastering software quality engineering through a unified, multi-disciplinary approach. It highlights the integration of various techniques, such as test automation, continuous integration (CI), continuous delivery (CD), and defect management, to create a seamless workflow that drives software quality. The research also emphasizes the importance of collaboration between development, testing, and operations teams in achieving optimal software quality. This holistic approach leverages both traditional and modern practices, including agile development and DevOps, to ensure that software is developed, tested, and deployed effectively. The study investigates the tools, methodologies, and frameworks used to implement this approach, along with challenges faced by organizations in achieving high software quality standards. Additionally, the paper presents case studies and performance metrics to demonstrate the effectiveness of a holistic approach to software quality engineering. By addressing the challenges in quality assurance and introducing strategies for overcoming them, this paper provides valuable insights into mastering SQE for modern software development environments.

Within the dynamic domain of software development, achieving excellence relies heavily on the proficient handling of defects and a comprehensive analysis of their root causes. This abstract thoroughly explores the fundamental roles that defect management and root cause analysis play within the realm of software quality engineering. Defect management involves a methodical approach to identifying, monitoring, and resolving flaws that arise during the software development process. On the other hand, root cause analysis delves into the underlying catalysts behind these defects, with the goal of identifying the core reasons for their occurrence. These abstract underscores the remarkable importance of these practices in the pursuit of superior software quality. Through the implementation of robust defect management strategies and rigorous root cause analysis techniques, the field of software quality engineering aims to mitigate risks, amplify customer satisfaction, and continually refine software development procedures. The exploration of these methodologies forms the bedrock for elevating software quality to unprecedented levels of distinction. "The Significance of Defect Management and Root Cause Analysis in Software Quality Engineering" In the intricate realm of software development, two essential pillars, namely defect management and root cause analysis, emerge as foundational elements of effective software quality engineering. Defects, spanning from inconspicuous errors to glaring faults, hold the potential to undermine the reliability and integrity of software systems. Defect management orchestrates a systematic process encompassing identification, categorization, prioritization, and rectification of these imperfections throughout the software development lifecycle. Concurrently, root cause analysis delves profoundly into the origins of defects, uncovering the underlying triggers that give rise to these issues.Collectively, these practices assume pivotal roles in upholding and enriching software quality.

Conceptual model is considered to be essential in simulation development activities. However, there are only a few research studies on how to develop conceptual models, the problems of model's low reusability and lacking management are presented in the conceptual model's development of simulation system. To solve the above problems, the concept of conceptual model (MCM) is presented for realizing the conceptual model's abstract in the higher arrangement. The ontology conception is introduced to design the MCM, and the MCM's architecture and modeling process are given too. By mapping the MCM to conceptual model (CM), the conceptual model's modeling process is realized. Finally, the method is applied in the conceptual model's modeling of equipment support simulation system, and the better validation is obtained. Conceptual Model. Meta means overtaking or basic, which often be used with other nouns such as language, model and data. The concepts of language, model and data are formed. When developing the conceptual models of some specific domains, the meta may be used before CM, and the concept of conceptual model (MCM) is presented. In brief, MCM is the model of CM and has the higher abstract degree. By using the MOF (Meta Object Facility) for reference (3), the four levels MCM architecture is presented, which is shown in Table 1. Table 1 MCM's Architecture

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.

The area of aspect-oriented software development (AOSD) has seen much progress in the past few years towards improving the quality of object-oriented, generative, and component-based software engineering, including some use in large-scale applications. Large-scale AOSD requires tools, paradigms, and methodologies that support multiple aspect models, multiple artifacts and formalisms, and multiple tasks and activities. The Concern Manipulation Environment (CME) is an Eclipse open source project that aims to provide a set of open, extensible components and a set of tools that promote aspect-oriented software development throughout the software lifecycle. This paper provides an overview of this programming environment. It also provides a general discussion of the available tools and the platforms where this environment can be integrated.

Software Quality Engineering is an emerging discipline that is concerned with improving the approach to software quality. It is important that this discipline be firmly rooted in a quality model satisfying its needs. In order to define the needs of this discipline, the meaning of quality is broadly defined by reviewing the literature on the subject. Software Quality Engineering needs a quality model that is usable throughout the software lifecycle and that it embraces all the perspectives of quality. The goal of this paper is to propose the characteristics of a quality model suitable for such a purpose, through the comparative evaluation of existing quality models and their respective support for Software Quality Engineering.

Software development is a greatly multifaceted and intellect-oriented movement. In the early days of program development, developers engraved programs using machine language in which programmers consumed added time, thinking about a particular machine’s instruction set than the difficulty at hand. Progressively, programmers wandered to higher level languages. In order to progress software using higher level languages, there are different approaches and selection of software development approach depending on the type of application to be established. Aspect-oriented software development (AOSD) is a novel paradigm in software development that addresses certain concerns in software development that regards modularization as an important aspect. The practices of AOSD create the possibilities to modularize, crosscutting the concerns of a system. Analogous to objects in object-oriented software development, aspects in AOSD may ascend at any point of time of the software life cycle, containing requirements specification, design, implementation, etc. As this effort is built on empirical validating aspect-oriented metrics, coupling on method call (CMC) metric is selected. This work focuses on empirical validation of the metrics. Novel metric is cognitive weighted metric, which is calculated for CMC to calculate the coupling complexity value of the aspect.

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.

Requirement Engineering (RE) is the branch of Software Engineering concerned with the real-world goals for, functions of, and constraints on software systems; it is also concerned with the relationship of these factors to precise specifications of software behaviour and to their evolution over time and across software families. RE is increasingly recognized as a critical activity in any systems engineering process. Independently of the nature of the software, the elicitation, analysis, negotiation, specification, validation and management of requirements are fundamental for establishing quality in complex software. Only by fully understanding stakeholders' needs, and documenting them in a concise and unambiguous way, can we consistently deliver quality products designed to meet the complexity of our advanced information society. The objective of this track is to explore different advances in RE, its relation with different areas, thereby reducing the gap between software engineering solutions and the way one specific domain of knowledge was seen up to given point.

Evolution and maintainability of legacy systems is all time attention drawing subject for researchers and especially practitioners. Discovering the crosscutting concerns and separating it from core functionalities of a software system may help in evolution of the legacy systems. Aspect-oriented software development (AOSD) tries to achieve the goal. AOSD is new programming paradigm which helps to bring in modularity in the program by writing the crosscutting concerns in the form of ‘aspects'. Modularity brings comprehensibility and hence maintainability of the software system. Tools and techniques, which aid in identifying the crosscutting concerns in such systems and refactoring them into aspects, are needed to apply aspect-oriented techniques to legacy systems at use in industry. This chapter aims to identify issues, problems and approaches used in the migration from legacy systems to aspect-oriented software system.

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