An Objectives-Driven Process for Selecting Methods to Support Requirements Engineering Activities

This paper presents a framework that guides the requirements engineer in the implementation and execution of an effective requirements generation process. We achieve this goal by providing a well-defined requirements engineering model and a criteria based process for optimizing method selection for attendant activities. Our model, unlike other models, addresses the complete requirements generation process and consists of activities defined at more adequate levels of abstraction. Additionally, activity objectives are identified and explicitly stated - not implied as in the current models. Activity objectives are crucial as they drive the selection of methods for each activity. Our model also incorporates a unique approach to verification and validation that enhances quality and reduces the cost of generating requirements. To assist in the selection of methods, we have mapped commonly used methods to activities based on their objectives. In addition, we have identified method selection criteria and prescribed a reduced set of methods that optimize these criteria for each activity defined by our requirements generation process. Thus, the defined approach assists in the task of selecting methods by using selection criteria to reduce a large collection of potential methods to a smaller, manageable set. The model and the set of methods, taken together, provide the much needed guidance for the effective implementation and execution of the requirements generation process.Comment: 20 pages, 5 figures, 3 tables, publisheed: 29th Annual IEEE/NASA Software Engineering Workshop, April 200

Requirements engineering: a review and research agenda

This paper reviews the area of requirements engineering. It outlines the key concerns to which attention should be devoted by both practitioners, who wish to "reengineer" their development processes, and academics, seeking intellectual challenges. It presents an assessment of the state-of-the-art and draws conclusions in the form of a research agenda

Multi-User Variability Configuration: a Game Theoretic Approach

Multi-user configuration is a neglected problem in variability-intensive systems area. The appearance of conflicts among user configurations is a main concern. Current approaches focus on avoiding such conflicts, applying the mutual exclusion principle. However, this perspective has a negative impact on users satisfaction, who cannot make any decision fairly. in this work, we propose an interpretation of multi-user configuration as a game theoretic problem. Game theory is a well-known discipline which analyzes conflicts and cooperation among intelligent rational decisionmakers. We present a taxonomy of multi-user configuration approaches, and how they can be interpreted as different problems of game theory. We focus on cooperative game theory to propose and automate a tradeoff-based bargaining approach, as a way to solve the conflicts and maximize user satisfaction at the same time

An approach to estimate the saving from negotiation based on cost- benefit anaylsis model

This paper presents an approach to estimate the savings from implementing negotiation in requirements elicitation process. The aim of implementing negotiation is to minimize the possibility of introducing defects during the creation of requirements and to decrease later effort required to fix requirements defects. An empirical evaluation study is adopted through a role play experiment to evaluate the benefit of exercising negotiation. The net-gain and the return-oninvestment show positive value which suggest that negotiation activities worth an investment. Based on the return-oninvestment of 197 percent in average, this paper suggests that negotiation is a useful prevention activity to inhibit defects from occurring during the creation of requirements

Requirements Negotiation: Does Consensus Reduce Software Development Cost?

The requirements engineering activities within a software project are known to be critical to the successful production of a correctly functioning system. This is particularly so when considering the varying views of multiple stakeholders. One promising approach for improving the outcome is to introduce formal negotiation. Negotiation is beneficial to identify and to resolve conflicts between stakeholders. Consensus achieved through negotiation represents all key stakeholders’ perspectives and perceptions regarding the system to be developed. The aim of implementing negotiation is to minimize the possibility of introducing defects during the creation of requirements and to decrease later effort required to fix requirements’ defects. This paper answers the question of whether consensus gives positive significant impact to the software project as a whole or not. It presents an approach to estimate the savings from implementing negotiation in the requirements elicitation process. An empirical evaluation study is adopted through a role play experiment to evaluate the benefit of exercising negotiation. The net gain and the return on investment show positive values which suggest that negotiation activities are worth an investment. Based on a return on investment of 197 percent on average, this paper suggests that negotiation is a useful prevention activity to inhibit defects from occurring during the requirements creation process

Improving the Requirements Engineering Process: a process oriented approach

The Requirements Engineering (RE) process plays an important role in the software development process. In order to produce quality software greater attention must be given to the improvement of RE process. In this paper five key process areas (KPAs) have been identified from the research literature in order to improve the RE process. Firstly to support a goal-based approach in the RE process; secondly to support the incremental and cyclical behaviours in the RE process; thirdly to encourage stakeholders involvement in the RE process; fourthly, to support the management of RE process and fifthly to define a planning phase for the RE process. This research project aims to show that better results will follow when the RE process supports these five KPAs. To address these KPAs, a requirement elicitation, analysis and validation method (REAVM) is proposed. A case study has been conducted in order to test and evaluate the REAVM in the real world environment

A Simple Set Model of Requirements Representation

A successful information systems development (ISD) depends on a complete, correct, and consistent set of requirements specification. In this paper, we present a set model of requirements representation to present functional and non-functional requirements in a systematic and schematic manner. Because the nature of the set operation is mathematical and methodological, requirements representation becomes scholastic and structured. In this paper, we first describe an incremental and iterative process model of requirements analysis where a spiral of requirements acquisition, articulation, and analysis is defined. We then depict a set-oriented data and process model to abstract the analyzed requirements into a hierarchical structure. We further delineate the set model to represent the abstracted functional and non-functional requirements. The main advantage of the simple set model is that it provides a set of tractable requirements specification that allows developers to test if the specification is complete, correct, and consistent. A simple example is prepared as an illustration of this approach to show the meaning, values, and feasibility