In this paper1, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability, to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature. We report how the majority of the problems attributed to poor requirements traceability are due to inadequate pre-RS traceability and show the fundamental need for improvements here. In the remainder of the paper, we present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which

This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice, and highlights some key open research issues for the future. 1

Requirements engineering (RE) is concerned with the identification of the goals to be achieved by the envisioned system, the operationalization of such goals into services and constraints, and the assignment of responsibilities for the resulting requirements to agents such as humans, devices, and software. The processes involved in RE include domain analysis, elicitation, specification, assessment, negotiation, documentation, and evolution. Getting highquality requirements is difficult and critical. Recent surveys have confirmed the growing recognition of RE as an area of utmost importance in software engineering research and practice. The paper presents a brief history of the main concepts and techniques developed to date to support the RE task, with a special focus on modeling as a common denominator to all RE processes. The initial description of a complex safetycritical system is used to illustrate a number of current research trends in RE-specific areas such as go...

This paper presents a classification scheme for research efforts in requirements engineering. For those readers who are not familiar with requirements engineering, it is intended to provide an overview and a coherent framework for further study.

Abstract. Abstraction identification is named as a key problem in requirements analysis. Typically, the abstractions must be found among the large mass of natural language text collected from the clients and users. This paper motivates and describes a new approach, based on traditional signal processing methods, for finding abstractions in natural language text and offers a new tool, AbstFinder as an implementation of this approach. The advantages and disadvantages of the approach and the design of the tool are discussed in detail. Various scenarios for use of the tool are offered. Some of these scenarios were used in case study of the effectiveness of the tool on an industrial-strength example of finding abstractions in a request for proposals.

We seek to take some initial steps towards a theory of information that is adequate for understanding and designing systems that process information, i.e., information systems in a broad sense. Formal representations of information are needed in designing, using and maintaining such systems, especially when they are computer based. However, it is also necessary to take account of social context, including how information is produced and used, not merely how it is represented; that is, we need a social theory of information. Ideas from ethnomethodology and semiotics, as well as logic and the sociology of science, are used to explore the nature of information.

Ethnography originates from anthropology where anthropologists spend extended periods of time with primitive societies making detailed observations of their practices. In a design context the aim of ethnography is to develop a thorough

The article presents a conceptual framework and a coherent method for design in an organizational context within the participatory design tradition. The MUST method has been developed throughout 10 projects in Danish and American organizations, and it has recently been evaluated and adopted by 3 Danish organizations. The method is based on thorough participation with users and managers, and it combines the use of ethnographic techniques and intervention. The article describes the application area and perspective of the method, presents 6 general principles on which the method is based, and describes 5 main activities providing a stepwise decision-making process in the overall design process. Each of the main activities are illustrated by an example taken from our last project. The article concludes by summing up the

Editor’s Note: The following article is reprinted from the book Software Requirements Engineering, Second Edition, and is provided for readers who want to read a brief tutorial on requirements engineering. The views expressed in this article are the author’s only and do not

Abstract: This paper is an overview of a new approach to requirements � the exposition takes formality and informality as its theme. The approach considers that requirements are information and that information is social. Ethnomethodology and semiotics are used to explore the nature of information and requirements. Some limits of formalization, and the importance of tacit knowledge and evolution motivate new methods for acquiring and tracing requirements. 1