3.6.2 Next Generation Requirements Engineering

Adoption of the most suitable requirements engineering (RE) process and selection of the most appropriate RE techniques for a given project are challenging issues for industry. In order to alleviate the problems, a framework for RE process development (FRERE) was developed based on our research in the last six years. The overall architecture of the framework and a brief case study are presented in the paper. The framework addresses several core issues of the RE process: engineering issues, domain issues, characteristics of the software project, and issues of conformity to software process standards. FRERE consists of three parts: (1) The RE process knowledge base (REPKB) which contains RE process knowledge, (2) methodologies which provide guidance to develop a customized software process model in an iterative way; and (3) assessment models which provide information about the suitability of the newly developed RE process model for the software project under development.

Usability and requirements engineering both provide means for discovering, analyzing, and fulfilling users' needs. In practice, it is difficult to manage and control user-centered design and system development processes separately. Based on a case study conducted in two software product companies, we have aimed to understand the role of usability specialists in the requirements engineering (RE) process. Our findings indicate that usability is still often seen as user interface design instead of a more comprehensive characteristic of a software product. Therefore, usability specialists had difficulties participating in early RE activities. To integrate usability as a natural part of the RE process, the usability teams have started to organize training in their companies. The main purpose of the training is to ensure that usability is not relying solely on the work of specialists but becomes a common responsibility for the whole product development organization.

Requirements engineering (RE) process improvement methods typically work with explicit process models describing activities and document flow between the stakeholders involved, and with explicit document definitions. In complex, multi-project contexts, however, the RE process is better characterized as intertwining of design, negotiation, and sense-making. In the first part of This work, we present the concepts of a workshop-based RE process improvement technique suitable for a multi-project context. In the second part, we show the experiences made in an industrial case study conducted with Nokia smart traffic products. The major innovations of our approach are: (i) instead of a process model, an information model is created, which focuses solely on the responsibilities of stakeholders with regard to the major documents; (ii) instead of document details, only the major point of view of the documents is defined.

The first argument presented is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second argument is that a key objective of the RE process is to specify a system which will ultimately be successful. Three common types of failure are examined: process failure, expectation failure and interaction failure. The third argument is that if the causes of each type of failure can be described then we will be able to identify what techniques are needed to help us avoid failure. The five common causes are described: the requirements engineering process itself, human communication within requirements, knowledge development, documentation of requirements and management. A discussion of each cause is followed by a list of the RE techniques needed. The paper concludes with a 'wish list' of seventy requirements for RE techniques, and a brief discussion of the strengths and weaknesses of the RE community in meeting those requirements.

This paper identifies the essential components of a requirements engineering (RE) process and provides alternatives to the requirements analyst when deciding on a particular set of RE methods. Existing methods of choosing RE techniques are discussed, and a new technique is proposed specifically for choosing RE techniques for projects with critical time-to-market projects. The components of the essential RE process as well as many other insights into the practice of RE were identified by examining the current literature and by analyzing the data from 25 completed surveys concerning the area of RE. The survey data provides insight into the state of the practice in requirements engineering.

The aim of this tutorial is to explain in an accessible manner the psychology of people in the context of misunderstandings, politics and social issues that affect software development. It focuses on user-stakeholder interaction techniques for analysis and interpretation of human behaviour, and how psychological knowledge can be used to improve the requirements engineering (RE) process as well as interpreting the implications of human motivations and values for requirements and software systems architecture. Soft issues, such as politics and people's feelings, are often cited as problems in the RE process and as key causes of system failure. It is clear from the RE literature that understanding user beliefs and values is vital for the success of software development. The London Ambulance service is a canonical example of system failure caused, in part, by inadequate understanding of ambulance crews' motivations, values of self esteem and autonomy, and the emotional reaction to lack of involvement in the requirements process, leading to technology failure.

In global software development (GSD), teams from different geographies are involved in software development activities from requirement till management phase. There are many potential benefits associated with GSD environment such as development cost, round the clock development, accessibility to better skilled people and many others. Although, organizations are achieving the benefits of GSD but its challenging nature such as cultural and language differences, trust relationship, coordination and communication is introducing numerous challenges that cannot be ignored. These challenges are significantly influencing requirement engineering (RE) process in GSD. One of the reasons behind challenging nature of RE in GSD is varying situational contexts such as social, communication and cultural contexts, language, human, technical and management related contexts. This necessitate for a comprehensive framework that demonstrates the perspective of situational contexts. This study aims to review the existing situational RE frameworks, highlights the reported situational contexts and provide future research directions. The literature revealed that the situational contexts are commonly related to twelve categories that include stakeholders, organization, requirements, project, management, risk, culture, standard, task, communication, technique and methods, and innovation. The situational contexts related to these categories show the main standpoint of situational software development in GSD. These situational contexts are significant for improving competencies of the team members while performing RE process in GSD environment. This study also draws attention towards some imperative research directions for further studies in line of situational software engineering.

European Cooperation for Space Standardization (ECSS) is an initiative established to develop a coherent, single set of user-friendly standards for use in all European space activities. In the autumn of 1993, several national space agencies in Europe, ESA and the European space industry joined forces to start developing space standards. ECSS standards must improve industrial efficiency and competitiveness, and satisfy European and international clients. The standards will apply as needed to any party participating in the definition, development, manufacturing, verification or operation of any assembly, equipment, subsystem or service used for any space mission. 1. INTRODUCTION ECSS, which stands for European Cooperation for Space Standardization, is an initiative designed to develop a coherent single set of user-friendly standards for the European space community which in this case means ESA and its member states, including their space industries. The European space business suffers from the multiplicity of standards and requirements used by the different space agencies in Europe. Although these requirements are essentially similar, the impact of the differences is nonetheless serious, leading in particular to high costs, lower effectiveness, a less compelitive industry and possible errors. This situation is expected to last until ECSS produces its standards, which will in turn help to solve the aforementioned problems. Back in 1988, in an attempt to improve the situation, Eurospace asked the director-generals of both ESA and CNES to make their organizations' product assurance requirements consistent. Efforts were pursued from 1991 to 1993 to meet this objective. By the end of that period, the European space community was in a position to meet this challenge. Based on a commercially oriented strategy, forces were joined to build a more comprehensive, coherent system to encompass space business activities as a whole rather than dealing only with product assurance aspects. The European space industry was therefore fully associated with ECSS from the outset. ECSS was actually born in the autumn of 1993, when the partners signed the ECSS terms of reference (TOR), which define the basic rules of the system. At this point, the partners jointly undertook the development of the system, designed to meet the main objective of providing a single coherent set of standards for use in all European space activities and particularly projects. 2. IMPORTANCE OF STANDARDS Today, standards are no longer considered as just impressive stacks of dusty papers containing unjustified requirements or constraints. Standardization is generally viewed as a process driving commercial viability and success. Successful companies recognise that developing and using standards is the path to remaining competitive and producing quality products In the first ECSS-industry meeting in October 1993, the ESA Director General stated that the time had come to harmonise existing space standards and to implement a system of common standards to enable the European space industry to become more efficient, more capable and more competitive in general. He stressed several points: • These standards must satisfy all European and international clients; Copyright © 1996 by CNES. Published by the American Institute of Aeronautics and Astronautics, Inc. with permission 1 El Gammal • Existing standards which satisfy the require-ment should be retained, and new ones should be developed on the basis of solid reasoning and experience; • The European space industry must be a full partner in the preparation, writing and validation of these standards. Globally accepted European and international standards can promote the development, manufacture and sale of high-quality space products, which are not only demanded by the domestic clients, but also meet the needs of international customers. By abolishing the multiplicity of project requirements of the various partners in ECSS, and concentrating on a single set of standards from which all generic requirements of future space projects would be derived this initiative should drive an increase in industrial efficiency. This policy will generate more recurring products or services at reduced cost with consistently high quality. Standardization is an important tool during all programme phases to both reduce costs and enhance quality and communications. The goal of the ECSS standardization initiative system is to minimise life-cycle costs, while continually improving the quality, functional integrity and compatibility of all elements of a project. This will be achieved by applying common standards to hardware, software, information and all activities within a given project, and between different projects. 3. SCOPE OF ECSS STANDARDS ECSS standards are being drawn up for space projects and applications within the following categories: • project management requirements; • requirements for design, development, manufacturing, and verification of space systems and their constituent parts; • technical requirements for assemblies, equipment, subsystems and systems used for space missions. The ECSS standards will apply as needed to any party participating in the definition, development, manufacturing, verification or operation of any assembly, equipment, subsystems, system or service used for a European element of any space mission.

The relationship between system theory and the product design, the process of product development has been described. It compared the merits and demerits of serial and parallel product development processes and, with the guidelines of system theory, put forward and analyzed the planning actions and corresponding necessity existed in the indistinct initial phase in product development process. It also analyzed the optimizing effect of planning actions in product design & development process. Thus, it obtained the model of product design & development process based on system theory so as to clarify the indistinct initial phase, shorten product development time and, improve the effectiveness of enterprise's product development.

Most researchers agree that the quality of real-life data archives is often very poor, and this makes the definition and realisation of automatic techniques for cleansing data a relevant issue. In such a scenario, the Universal Cleansing framework has recently been proposed to automatically identify the most accurate cleansing alternatives among those synthesised through model-checking techniques. However, the identification of some values of the cleansed instances still relies on the rules defined by domain-experts and common practice, due to the difficulty to automatically derive them (e.g. the date value of an event to be added).

XYZ is a telemedicine startup company that uses Scrum, an Agile methodology, as a software development method. The company uses Scrum to deliver good products and services to customers on time, even with limited requirements. However, the company faced problems in product development, so the company could not release the product on time. Based on interviews with internal experts, the company has issues determining the priority scale of requirements and change requirement management, where both problems are part of requirement engineering. This study discusses the problems of the company XYZ regarding the requirement engineering process, especially the problem of determining the priority scale of requirements and change requirement management. This research uses the CMMI-Dev 1.3 specific process area to assess the requirement engineering process in the company using sub-specific practices in the Requirement Development (RD) and Requirement Management (REQM) process areas. Researchers conducted interviews with product managers to appraise sub-specific RD and REQM practices with current activities in the company. The results of this study are recommendations to improve the quality of the requirement engineering process by using Objective Key Result (OKR) and Action Priority Matrix (APM).

Simulation modelling techniques (SMTs) are computational methods that imitate or replicate real-world processes, systems, or phenomena to gain insights, test hypotheses, make predictions, or optimise decision-making without needing real-world experimentation. These mathematical modelling techniques have risen to prominence as indispensable tools in insect pest management, enabling the modelling, prediction, and optimisation of pest management strategies. They are pivotal in ensuring the effective implementation of insect pest management by empowering researchers and practitioners to simulate and forecast pest population dynamics, evaluate control measures' effectiveness, and make informed decisions. Applications of simulation techniques in insect pest management are diverse. They include predicting the potential risks of invasion and geographical range expansion of invasive pests, understanding population dynamics of pests under future climate change scenarios, predicting insect pest outbreaks, optimising management strategies, monitoring insect pest resistance, conserving biological control, understanding insect pest behaviour, and assessing economic injury levels of pests and yield losses. Their multifaceted applications empower stakeholders to proactively manage insect pests, minimise environmental impacts, and allocate resources efficiently. In this review, we report the present status of the key simulation techniques used in insect pest management, their construction and validation processes, and explore the potential and prospects of SMTs in advancing modern insect pest management paradigms for sustainable crop protection. © 2025 Society of Chemical Industry.

<div class="section abstract"><div class="htmlview paragraph">In this case study, a human factors analysis was carried out in the preliminary design phase of the Cupola, a European Space Agency (ESA) module for manned space flights for the International Space Station (ISS). The manikin software Jack<sup>®</sup> was used early in the design process before any flight hardware production. All Cupola astronaut tasks were evaluated in a virtual environment of the Cupola. Methodological aspects concerning the analysis are described, e.g. file processing, use of coordinate systems and the use of a prior task analysis. Results show that the thorough manikin analysis supported with the hierarchical task analysis results, was an important help in the design process.</div></div>

In a world of fast changing environments for business, the need for innovation is one of the most stable items. On the other hand, innovation is influenced by more and more factors, like increasing products and service complexity ore growing numbers of partners, involved into a single product innovation. This paper introduces interoperability problems related to simultaneous business and product development.Purpose – This paper introduces the L-modelAgile, an advancement of the V-model. Due to interoperability is essential during the product development process, overall aim of the L-modelAgile is to improve the quality and rate of innovation within complex systems during the early stages of a stable and simultaneously agile innovation process.Design/methodology/approach – The basis of the L-modelAgile consists of the interoperability between the innovation process and the requirements management & engineering process (RM&E process) as well as the agile method Scrum. To link these processes, a best practice model inclusive a capability model and a performance measurement system has been developed. Findings – An increase of innovation quality and innovation speed at complex systems during the early stage of a reliable and simultaneous agile innovation process.Originality/value – The paper focuses on the innovation process during the product development and how to improve its quality.

In the framework of the European Copernicus programme, the European Space Agency (ESA) has launched the Sentinel-2 (S2) Earth Observation (EO) mission which provides optical high spatial resolution imagery over land and coastal areas. As part of this mission, a tool (named S2-RUT, from Sentinel-2 Radiometric Uncertainty Tool) has been developed. The tool estimates the radiometric uncertainty associated with each pixel in the top-of-atmosphere (TOA) reflectance factor images provided by ESA. This paper describes the design and development process of the initial version of the S2-RUT tool. The initial design step describes the S2 radiometric model where a set of uncertainty contributors are identified. Each of the uncertainty contributors is specified by reviewing the pre- and post-launch characterisation. The identified uncertainty contributors are combined following the guidelines in the ‘Guide to Expression of Uncertainty in Measurement’ (GUM) model and this combination model is further validated by comparing the results to a multivariate Monte Carlo Method (MCM). In addition, the correlation between the different uncertainty contributions and the impact of simplifications in the combination model have been studied. The software design of the tool prioritises an efficient strategy to read the TOA reflectance factor images, extract the auxiliary information from the metadata in the satellite products and the codification of the resulting uncertainty image. This initial version of the tool has been implemented and integrated as part of the Sentinels Application Platform (SNAP).