Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from what the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.<br /

The conundrum of categorising requirements: managing requirements for learning on the move

This paper reports on the experience of eliciting and managing requirements on a large European-based multinational project, whose purpose is to create a system to support learning using mobile technology. The project used the socio-cognitive engineering methodology for human-centered design and the Volere shell and template to document requirements. We provide details about the project below, describe the Volere tools, and explain how and why we used a flexible categorization scheme to manage the requirements. Finally, we discuss three lessons learned: (1) provide a flexible mechanism for organizing requirements, (2) plan ahead for the RE process, and (3) do not forget 'the waiting room

Exploring Knowledge Engineering Strategies in Designing and Modelling a Road Traffic Accident Management Domain

Formulating knowledge for use in AI Planning engines is currently something of an ad-hoc process, where the skills of knowledge engineers and the tools they use may significantly influence the quality of the resulting planning application. There is little in the way of guidelines or standard procedures, however, for knowledge engineers to use when formulating knowledge into planning domain languages such as PDDL. This paper seeks to investigate this process using as a case study a road traffic accident management domain. Managing road accidents requires systematic, sound planning and coordination of resources to improve outcomes for accident victims. We have derived a set of requirements in consultation with stakeholders for the resource coordination part of managing accidents. We evaluate two separate knowledge engineering strategies for encoding the resulting planning domain from the set of requirements: (a) the traditional method of PDDL experts and text editor, and (b) a leading planning GUI with built in UML modelling tools. These strategies are evaluated using process and product metrics, where the domain model (the product) was tested extensively with a range of planning engines. The results give insights into the strengths and weaknesses of the approaches, highlight lessons learned regarding knowledge encoding, and point to important lines of research for knowledge engineering for planning

Integrating Creativity Workshops into Structured Requirements Processes

Requirements engineering is a creative process in which stakeholders and designers work together to create ideas for new systems that are eventually expressed as requirements. However, many requirements engineering or software development methods do not encourage or support creative thinking, let alone integrate it with existing modeling and analysis processes. This paper describes RESCUE, a scenario-driven requirements engineering process that includes workshops that integrate creativity techniques with different types of use case and system context modelling. It reports a case study in which RESCUE creativity workshops were used to discover stakeholder and system requirements for DMAN, a future air traffic management system for managing departures from major European airports. The workshop was successful in that it provided new and important outputs for subsequent requirements processes. The paper describes the workshop structure and wider RESCUE process, important results and key lessons learned

Human Activity Modelling in the Specification of Operational Requirements: Work in Progress

This paper describes our experience of integrating HCI concepts and techniques into a concurrent requirements engineering process called RESCUE. We focus on the use of a model of current human activity to inform specification of a future system. We show how human activity descriptions, written using a specially designed template, can facilitate the authoring of use case descriptions to be used in the elicitation of requirements for complex socio-technical systems. We describe our experience of using descriptions of human activity, written using the template, to support specification of operational requirements for DMAN, a system to support air traffic controllers in managing the departure of aircraft from airports. We end with a discussion of lessons learnt from our experience and present some ideas for future development of work in this area

Definition and Representation of Requirement Engineering/Management : A Process-Oriented Approach

Requirements are important in software development, product development, projects, processes, and systems. However, a review of the requirements literature indicates several problems. First, there is confusion between the terms ?requirements engineering? and ?requirements management.? Similarities and/or differences between the two terms are resolved through a literature review; resulting in comprehensive definitions of each term. Second, current literature recognizes the importance of requirements but offers few methodologies or solutions for defining and managing requirements. Hence, a flexible methodology or framework is provided for defining and managing requirements. Third, requirements methodologies are represented in various ways, each with their respective strengths and weaknesses. A tabular view and hybrid graphical view for representing the requirements process are provided

Requirements Management Tools: A Quantitative Assessment

This report is primarily aimed at people with some background in Requirements Engineering or practitioners wishing to assess tools available for managing requirements. We provide a starting point for this assessment, by presenting a brief survey of existing Requirements Management tools. As a part of the survey, we characterize a set of requirements management tools by outlining their features, capabilities and goals. The characterization offers a foundation to select and possibly customize a requirements engineering tool for a software project. This report consists of three parts. In Part I we define the terms requirements and requirements engineering and briefly point out the main components of the requirements engineering process. In Part II, we survey the characteristics and capabilities of 6 popular requirements management tools, available in the market. We enumerate the salient features of each of theses tools. In Part III, we briefly describe a Synergistic Environment for Requirement Generation. This environment captures additional tools augmenting the requirements generation process. A description of these tools is provided. In the concluding section, we present a discussion defining the ideal set of characteristics that should be embodied in a requirements management tool. This report is adapted from a compendium of assignments that were prepared by the students in a Requirements Engineering class offered in the Department of Computer Science at Virginia Tech

Managing Requirements Change the Informal Way: When Saying 'No' is Not an Option

© 2016 IEEE. Software has always been considered as malleable. Changes to software requirements are inevitable during the development process. Despite many software engineering advances over several decades, requirements changes are a source of project risk, particularly when businesses and technologies are evolving rapidly. Although effectively managing requirements changes is a critical aspect of software engineering, conceptions of requirements change in the literature and approaches to their management in practice still seem rudimentary. The overall goal of this study is to better understand the process of requirements change management. We present findings from an exploratory case study of requirements change management in a globally distributed setting. In this context we noted a contrast with the traditional models of requirements change. In theory, change control policies and formal processes are considered as a natural strategy to deal with requirements changes. Yet we observed that "informal requirements changes" (InfRc) were pervasive and unavoidable. Our results reveal an equally 'natural' informal change management process that is required to handle InfRc in parallel. We present a novel model of requirements change which, we argue, better represents the phenomenon and more realistically incorporates both the informal and formal types of change