Requirements elicitation

About: Requirements elicitation is a research topic. Over the lifetime, 4014 publications have been published within this topic receiving 78454 citations. The topic is also known as: requirements gathering & requirement gathering.

Guiding goal modeling using scenarios

Abstract: Even though goal modeling is an effective approach to requirements engineering, it is known to present a number of difficulties in practice. The paper discusses these difficulties and proposes to couple goal modeling and scenario authoring to overcome them. Whereas existing techniques use scenarios to concretize goals, we use them to discover goals. Our proposal is to define enactable rules which form the basis of a software environment called L'Ecritoire to guide the requirements elicitation process through interleaved goal modeling and scenario authoring. The focus of the paper is on the discovery of goals from scenarios. The discovery process is centered around the notion of a requirement chunk (RC) which is a pair . The paper presents the notion of RC, the rules to support the discovery of RCs and illustrates the application of the approach within L'Ecritoire using the ATM example. It also evaluates the potential practical benefits expected from the use of the approach.

Managing software requirements: a unified approach

Abstract: "A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." --Ivar Jacobson "Many projects fail for the simple reason that the developers fail to build the right thing: They either deliver a system that does not meet the expectations of its intended users, or they deliver a system that focuses on secondary functions at the expense of its primary use. Drawing on their extensive experience, Dean and Don demonstrate how to employ an industrial-strength requirements process, one that helps ensure you will build the right thing. Developers of any kind of application should read this book." --Grady BoochDespite the wealth of development knowledge, experience, and tools generally available today, a substantial percentage of software projects continue to fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. Clients do not always know or express their needs precisely, and too often designers and developers do not ask the right questions at the right times. As a result, projects often spin out of control as "feature bloat" and shifting priorities cause budgets and schedules to exceed expectations. Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs--on time and within budget.The authors are skilled practitioners who have spent their careers in the trenches building high-quality applications, including safety-critical, real-time systems. Using an informal, approachable style, their own war stories, and a comprehensive case study they show how designers and developers can effectively identify requirements by employing the power of use cases and more traditional forms of requirements expression. The book illustrates proven techniques for determining, implementing, verifying, and validating requirements. It describes six vital Team Skills for managing requirements throughout the lifecycle of a project: Analyzing the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining the System Definition, and Building the Right System. Managing Software Requirements specifically addresses the ongoing challenge of managing change and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders.Topics covered include: The five steps in problem analysis Business modeling and system engineering Techniques for eliciting requirements from clients, users, developers, and other stakeholders Applying and refining use cases Prototyping Organizing and managing requirements information Establishing project scope and managing customers Using both informal and technical methods for specifying requirements How to measure and improve the quality of your product's requirements Moving from requirements to implementation Verifying and validating the system Managing changeThe book concludes with a step-by-step guide to incorporating these powerful techniques into future projects.0201615932B04062001

Security Requirements Engineering: A Framework for Representation and Analysis

Abstract: This paper presents a framework for security requirements elicitation and analysis. The framework is based on constructing a context for the system, representing security requirements as constraints, and developing satisfaction arguments for the security requirements. The system context is described using a problem-oriented notation, then is validated against the security requirements through construction of a satisfaction argument. The satisfaction argument consists of two parts: a formal argument that the system can meet its security requirements and a structured informal argument supporting the assumptions expressed in the formal argument. The construction of the satisfaction argument may fail, revealing either that the security requirement cannot be satisfied in the context or that the context does not contain sufficient information to develop the argument. In this case, designers and architects are asked to provide additional design information to resolve the problems. We evaluate the framework by applying it to a security requirements analysis within an air traffic control technology evaluation project.

Requirements Elicitation: A Survey of Techniques, Approaches, and Tools

Abstract: Requirements elicitation is the process of seeking, uncovering, acquiring, and elaborating requirements for computer based systems. It is generally understood that requirements are elicited rather than just captured or collected. This implies there are discovery, emergence, and development elements in the elicitation process. Requirements elicitation is a complex process involving many activities with a variety of available techniques, approaches, and tools for performing them. The relative strengths and weaknesses of these determine when each is appropriate depending on the context and situation. The objectives of this chapter are to present a comprehensive survey of important aspects of the techniques, approaches, and tools for requirements elicitation, and examine the current issues, trends, and challenges faced by researchers and practitioners in this field.

Engineering and Managing Software Requirements

Abstract: 1) Requirements Engineering: Setting the Context Part-1: State-of-the-Art Surveys of Requirements Engineering Process Research 2) Requirements Elicitation 3) Specification of Requirements Models 4) Requirements Prioritization 5) Requirements Interdependencies 6) Impact Analysis 7) Requirements Negotiation 8) Quality Assurance in Requirements Engineering Part-2: The Next Practice in Requirements Engineering 9) Modeling Goals and Reasoning with Them 10) Managing Large Repositories of Natural Language Requirements 11) Understanding Ambiguity in Requirements Engineering 12) Decision Support in Requirements Engineering 13) Market-Driven Requirements Engineering for Software Products 14) Requirements Engineering for Agile Methods 15) Requirements Engineering for Web-Based Information Systems Part-3: Studies and Industrial Experience 16) Requirements Engineering: A Case of Developing and Managing Quality Software Systems in the Public Sector 17) Good Quality Requirements in Unified Process 18) Requirements Experience in Practice: Studies of Six Companies 19) An Analysis of Empirical Requirements Survey Data 20) Requirements Engineering: Solutions and Trends