Match!

Managing Software Requirements: A Use Case Approach

Published on Oct 28, 1999
Dean Leffingwell2
Estimated H-index: 2
,
Don Widrig2
Estimated H-index: 2
Abstract
From the Publisher: Despite the wealth of development knowledge, experience, and tools available today, a substantial percentage of software projects fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. This Second Edition of the popular text 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. Using an approachable style, their own war stories and a comprehensive case study, the authors show how analysts and developers can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, 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 customers and stakeholders Establishing and managing project scope Applying and refining use cases Product management Transitioning from requirements to design andimplementation Transitioning from use cases to test cases Agile requirements methods
  • References (0)
  • Citations (191)
📖 Papers frequently viewed together
170 Citations
1999
843 Citations
1997
969 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
References0
Newest
Cited By191
Newest
#1Panagiota Chatzipetrou (Örebro University)H-Index: 7
#2Efi Papatheocharous (Research Institutes of Sweden)H-Index: 1
Last. Tony Gorschek (BTH: Blekinge Institute of Technology)H-Index: 33
view all 6 authors...
Component-based software engineering is a common approach in the development and evolution of contemporary software systems. Different component sourcing options are available, such as: (1) Software developed internally (in-house), (2) Software developed outsourced, (3) Commercial off-the-shelf software, and (4) Open-Source Software. However, there is little available research on what attributes of a component are the most important ones when selecting new components. The objective of this study...
1 CitationsSource
#1Ankita Gupta (JIIT: Jaypee Institute of Information Technology)H-Index: 2
#2Chetna Gupta (JIIT: Jaypee Institute of Information Technology)H-Index: 7
Abstract One of the challenging tasks of requirement engineering is to choose which among the set of requirements are more advantageous than others and ought to be viewed as first for execution. Years of research has established it is vital to capture, analyze and prioritize requirements, which to a great extent relies on acknowledgment acceptance of stakeholder’s requirements, concerns and criteria’s.Proposed method provides interactive support for eliciting stakeholders and developer’s initial...
Source
#1Sabah Al-Fedaghi (Kuniv: Kuwait University)H-Index: 15
Use cases as textual visual modeling techniques have become a key construct and the foundation of the most popular de facto standard technique for performing software requirements analysis and specification. This paper describes use cases in terms of a recently proposed model, the thinging machine (TM) model. Such a link to TM strengthens the notion of use cases and clarifies related concepts. For example, the concept of events is utilized in an unconstrained way in use cases, and TM may contrib...
#1Stacey Omeleze (University of Pretoria)H-Index: 3
#2Hein S. Venter (University of Pretoria)H-Index: 18
AbstractThe requirement to identify the cause of an incident, following the trail of events preceding an incident, as well as proving the consistency of the potential evidence recovered from the al...
Source
May 4, 2019 in ENASE (International Conference on Evaluation of Novel Approaches to Software Engineering)
#1Erika Nazaruka (Riga Technical University)H-Index: 2
Understanding of cause-effect relations is vital for constructing a valid model of a system under development. Discovering cause-effect relations in text is one of the difficult tasks in Natural Language Processing (NLP). This paper presents a survey on trends in this field related to understanding how linguistically causal dependencies can be expressed in the text, what patterns and models exist, which of them are more and less successful and why. The results show that causal dependencies in te...
Source
#1Sajid Anwer (Griffith University)H-Index: 1
#2Lian Wen (Griffith University)H-Index: 9
Last. Zhe Wang (Griffith University)H-Index: 1
view all 4 authors...
Requirements Engineering (RE) is one of the critical phases of any software development life cycle. Business and technology evolution increasingly poses many challenges and becomes a source of continuous change in RE. Changes to software are inevitable in the development process and are a source of project risk. During the last decade many Requirements Change Management (RCM) models have been proposed, but this area appears to remain rudimentary in software process standards. Configuration manag...
1 CitationsSource
#1Chandan R. Rupakheti (RHIT: Rose-Hulman Institute of Technology)H-Index: 7
#2Mark Hays (RHIT: Rose-Hulman Institute of Technology)H-Index: 1
Last. Amanda Stouder (RHIT: Rose-Hulman Institute of Technology)H-Index: 1
view all 5 authors...
Abstract Requirements Engineering (RE) is an essential component of any software development cycle. Understanding and satisfying stakeholder needs and wants is the difference between the success and failure of a product. However, RE is often perceived as a “soft” skill by students and is often ignored by students who prioritize the learning of coding, testing, and algorithmic thinking. This view contrasts with the industry, where “soft” skills are instead valued equal to any other engineering ab...
2 CitationsSource
#1Georgi M. KanchevH-Index: 3
Last. Amit K. ChopraH-Index: 22
view all 3 authors...
A topic of recent interest is how to apply crowdsourced information toward producing better software requirements. A research question that has received little attention so far is how to leverage crowdsourced information toward creating better-informed models of requirements. In this paper, we contribute a method following which information in online discussions may be leveraged toward constructing goal models. A salient feature of our method is that it applies high-level queries to draw out pot...
Source
Abstract Research studies have shown that although the hedonic product feature is more valued by users it is the utilitarian that is favored in acquisition choice situations. Further, the hedonic is more favored in forfeiture choice situations than the utilitarian. In this longitudinal study we examine this phenomenon with actual users of software. The results of the study show that as expected in acquisition situations users explicitly prefer the utilitarian although their implicit choice as re...
5 CitationsSource
#1Sanja Aaramaa (University of Oulu)H-Index: 3
#2Sandun Dasanayake (University of Oulu)H-Index: 2
Last. Samuli Saukkonen (University of Oulu)H-Index: 1
view all 5 authors...
Requirements volatility is a major issue in software (SW) development, causing problems such as project delays and cost overruns. Even though there is a considerable amount of research related to requirement volatility, the majority of it is inclined toward project management aspects. The relationship between SW architecture design and requirements volatility has not been researched widely, even though changing requirements may for example lead to higher defect density during testing. An explora...
Source