The Resource Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig
Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig
Resource Information
The item Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig represents a specific, individual, material embodiment of a distinct intellectual or artistic creation found in University of Missouri Libraries.This item is available to borrow from 2 library branches.
Resource Information
The item Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig represents a specific, individual, material embodiment of a distinct intellectual or artistic creation found in University of Missouri Libraries.
This item is available to borrow from 2 library branches.
- Summary
- "Many projects fail because developers fail to build the right thing. Developers of any kind of application should read this book." -Grady Booch "A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." -Ivar Jacobson 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 accessible 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, Second Edition , 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 and implementation Transitioning from use cases to test cases Agile requirements methods 032112247XB05082003
- Language
- eng
- Edition
- 2nd ed.
- Extent
- 1 online resource (xxxvii, 502 pages)
- Contents
-
- Introduction: 1. The requirements problem
- 2. Introduction to requirements management
- 3. Requirements and the software cycle
- 4. The software team
- Team skill 1. Analyzing the problem: 5. The five steps in problem analysis
- 6. Business modeling
- 7. Systems engineering of software-intensive systems
- Team skill 2. Understanding user and stakeholder needs: 8. The challenge of requirements elicitation
- 9. The features of a product or system
- 10. Interviewing
- 11. Requirements workshops
- 12. Brainstorming and idea reduction
- 13. Storyboarding
- Team skill 3. Defining the system: 14. A use case primer
- 15. organizing requirements information
- 16. The vision document
- 17. Product management
- Team skill 4. Managing scope: 18. Establishing project scope
- 19. Managing your customer
- Team skill 5. Refining the system definition: 20. Software requirements, a more rigorous look
- 21. Refining the use cases
- 22. Developing the supplementary specification
- 23. On ambiguity and specificity
- 24. Technical methods for specfiying requirements
- Team skill 6. Building the right system: 25. From use cases to implementation
- 26. From use cases to test cases
- 27. Tracing requirements
- 28. Managing change
- 29. Assessing requirements qulity in iterative development
- Getting started: 30. Agile requirements methods
- 31. Your prescription for requirements management
- Appendixes: A. HOLIS artifacts
- B. Vision document template
- C. Use-case specification template
- D. Supplementary specification template
- E. Requirements management in the rational unified process
- F. Requirements management in the SEI-CMM and withing ISO 90000:2000
- Isbn
- 9780321122476
- Label
- Managing software requirements : a use case approach
- Title
- Managing software requirements
- Title remainder
- a use case approach
- Statement of responsibility
- Dean Leffingwell, Don Widrig
- Subject
-
- Cas d'utilisation (Ingénierie des systèmes)
- Computer Science
- Computer software -- Development | Management
- Computer software -- Development | Management
- Desenvolvimento de software (administração)
- Développement de logiciels
- Engenharia de sistemas de computação
- Engineering & Applied Sciences
- Programdokumentation
- Programutveckling
- Requirements engineering
- Software Engineering
- Spécification du logiciel
- Use cases (Systems engineering)
- Use cases (Systems engineering)
- Language
- eng
- Summary
- "Many projects fail because developers fail to build the right thing. Developers of any kind of application should read this book." -Grady Booch "A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." -Ivar Jacobson 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 accessible 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, Second Edition , 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 and implementation Transitioning from use cases to test cases Agile requirements methods 032112247XB05082003
- Cataloging source
- OCL
- http://library.link/vocab/creatorName
- Leffingwell, Dean
- Dewey number
- 005.1/068
- Illustrations
- illustrations
- Index
- index present
- Language note
- English
- LC call number
- QA76.76.D47
- LC item number
- L45 2003
- Literary form
- non fiction
- Nature of contents
-
- dictionaries
- bibliography
- http://library.link/vocab/relatedWorkOrContributorName
- Widrig, Don
- Series statement
- The Addison-Wesley object technology series
- http://library.link/vocab/subjectName
-
- Computer software
- Use cases (Systems engineering)
- Computer software
- Use cases (Systems engineering)
- Engineering & Applied Sciences
- Computer Science
- Requirements engineering
- Software Engineering
- Desenvolvimento de software (administração)
- Engenharia de sistemas de computação
- Développement de logiciels
- Cas d'utilisation (Ingénierie des systèmes)
- Spécification du logiciel
- Programdokumentation
- Programutveckling
- Label
- Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig
- Bibliography note
- Includes bibliographical references (pages 483-486) and index
- Carrier category
- online resource
- Carrier category code
-
- cr
- Carrier MARC source
- rdacarrier
- Content category
- text
- Content type code
-
- txt
- Content type MARC source
- rdacontent
- Contents
- Introduction: 1. The requirements problem -- 2. Introduction to requirements management -- 3. Requirements and the software cycle -- 4. The software team -- Team skill 1. Analyzing the problem: 5. The five steps in problem analysis -- 6. Business modeling -- 7. Systems engineering of software-intensive systems -- Team skill 2. Understanding user and stakeholder needs: 8. The challenge of requirements elicitation -- 9. The features of a product or system -- 10. Interviewing -- 11. Requirements workshops -- 12. Brainstorming and idea reduction -- 13. Storyboarding -- Team skill 3. Defining the system: 14. A use case primer -- 15. organizing requirements information -- 16. The vision document -- 17. Product management -- Team skill 4. Managing scope: 18. Establishing project scope -- 19. Managing your customer -- Team skill 5. Refining the system definition: 20. Software requirements, a more rigorous look -- 21. Refining the use cases -- 22. Developing the supplementary specification -- 23. On ambiguity and specificity -- 24. Technical methods for specfiying requirements -- Team skill 6. Building the right system: 25. From use cases to implementation -- 26. From use cases to test cases -- 27. Tracing requirements -- 28. Managing change -- 29. Assessing requirements qulity in iterative development -- Getting started: 30. Agile requirements methods -- 31. Your prescription for requirements management -- Appendixes: A. HOLIS artifacts -- B. Vision document template -- C. Use-case specification template -- D. Supplementary specification template -- E. Requirements management in the rational unified process -- F. Requirements management in the SEI-CMM and withing ISO 90000:2000
- Control code
- 54115707
- Dimensions
- unknown
- Edition
- 2nd ed.
- Extent
- 1 online resource (xxxvii, 502 pages)
- Form of item
- online
- Isbn
- 9780321122476
- Media category
- computer
- Media MARC source
- rdamedia
- Media type code
-
- c
- Other control number
-
- 99806526717
- 9780321122476
- 032112247X
- Other physical details
- illustrations.
- Sound
- unknown sound
- Specific material designation
- remote
- System control number
- (OCoLC)54115707
- Label
- Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig
- Bibliography note
- Includes bibliographical references (pages 483-486) and index
- Carrier category
- online resource
- Carrier category code
-
- cr
- Carrier MARC source
- rdacarrier
- Content category
- text
- Content type code
-
- txt
- Content type MARC source
- rdacontent
- Contents
- Introduction: 1. The requirements problem -- 2. Introduction to requirements management -- 3. Requirements and the software cycle -- 4. The software team -- Team skill 1. Analyzing the problem: 5. The five steps in problem analysis -- 6. Business modeling -- 7. Systems engineering of software-intensive systems -- Team skill 2. Understanding user and stakeholder needs: 8. The challenge of requirements elicitation -- 9. The features of a product or system -- 10. Interviewing -- 11. Requirements workshops -- 12. Brainstorming and idea reduction -- 13. Storyboarding -- Team skill 3. Defining the system: 14. A use case primer -- 15. organizing requirements information -- 16. The vision document -- 17. Product management -- Team skill 4. Managing scope: 18. Establishing project scope -- 19. Managing your customer -- Team skill 5. Refining the system definition: 20. Software requirements, a more rigorous look -- 21. Refining the use cases -- 22. Developing the supplementary specification -- 23. On ambiguity and specificity -- 24. Technical methods for specfiying requirements -- Team skill 6. Building the right system: 25. From use cases to implementation -- 26. From use cases to test cases -- 27. Tracing requirements -- 28. Managing change -- 29. Assessing requirements qulity in iterative development -- Getting started: 30. Agile requirements methods -- 31. Your prescription for requirements management -- Appendixes: A. HOLIS artifacts -- B. Vision document template -- C. Use-case specification template -- D. Supplementary specification template -- E. Requirements management in the rational unified process -- F. Requirements management in the SEI-CMM and withing ISO 90000:2000
- Control code
- 54115707
- Dimensions
- unknown
- Edition
- 2nd ed.
- Extent
- 1 online resource (xxxvii, 502 pages)
- Form of item
- online
- Isbn
- 9780321122476
- Media category
- computer
- Media MARC source
- rdamedia
- Media type code
-
- c
- Other control number
-
- 99806526717
- 9780321122476
- 032112247X
- Other physical details
- illustrations.
- Sound
- unknown sound
- Specific material designation
- remote
- System control number
- (OCoLC)54115707
Subject
- Cas d'utilisation (Ingénierie des systèmes)
- Computer Science
- Computer software -- Development | Management
- Computer software -- Development | Management
- Desenvolvimento de software (administração)
- Développement de logiciels
- Engenharia de sistemas de computação
- Engineering & Applied Sciences
- Programdokumentation
- Programutveckling
- Requirements engineering
- Software Engineering
- Spécification du logiciel
- Use cases (Systems engineering)
- Use cases (Systems engineering)
Member of
Library Links
Embed
Settings
Select options that apply then copy and paste the RDF/HTML data fragment to include in your application
Embed this data in a secure (HTTPS) page:
Layout options:
Include data citation:
<div class="citation" vocab="http://schema.org/"><i class="fa fa-external-link-square fa-fw"></i> Data from <span resource="http://link.library.missouri.edu/portal/Managing-software-requirements--a-use-case/R2hGtcFZCRw/" typeof="Book http://bibfra.me/vocab/lite/Item"><span property="name http://bibfra.me/vocab/lite/label"><a href="http://link.library.missouri.edu/portal/Managing-software-requirements--a-use-case/R2hGtcFZCRw/">Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig</a></span> - <span property="potentialAction" typeOf="OrganizeAction"><span property="agent" typeof="LibrarySystem http://library.link/vocab/LibrarySystem" resource="http://link.library.missouri.edu/"><span property="name http://bibfra.me/vocab/lite/label"><a property="url" href="http://link.library.missouri.edu/">University of Missouri Libraries</a></span></span></span></span></div>
Note: Adjust the width and height settings defined in the RDF/HTML code fragment to best match your requirements
Preview
Cite Data - Experimental
Data Citation of the Item Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig
Copy and paste the following RDF/HTML data fragment to cite this resource
<div class="citation" vocab="http://schema.org/"><i class="fa fa-external-link-square fa-fw"></i> Data from <span resource="http://link.library.missouri.edu/portal/Managing-software-requirements--a-use-case/R2hGtcFZCRw/" typeof="Book http://bibfra.me/vocab/lite/Item"><span property="name http://bibfra.me/vocab/lite/label"><a href="http://link.library.missouri.edu/portal/Managing-software-requirements--a-use-case/R2hGtcFZCRw/">Managing software requirements : a use case approach, Dean Leffingwell, Don Widrig</a></span> - <span property="potentialAction" typeOf="OrganizeAction"><span property="agent" typeof="LibrarySystem http://library.link/vocab/LibrarySystem" resource="http://link.library.missouri.edu/"><span property="name http://bibfra.me/vocab/lite/label"><a property="url" href="http://link.library.missouri.edu/">University of Missouri Libraries</a></span></span></span></span></div>