Software Requirements Using the Unified Process

Software Requirements Using the Unified Process : A Practical Approach

3 (2 ratings by Goodreads)
By (author)  , By (author) 

List price: US$49.99

Currently unavailable

We can notify you when this item is back in stock

Add to wishlist

AbeBooks may have this title (opens in new window).

Try AbeBooks


A Practical Approach to Software Requirements using the Unified Process will provide an end-to-end process to ensure that requirements are correct, complete, consistent, and effectively documented. It will provide information on how to effectively gather requirements, how to present them to the user to ensure a complete understanding, and how to capture the requirements in software architecture. Gathering, analyzing, and specifying requirements are among the most important steps in building a quality software system. Yet, many software development teams do not accomplish these tasks very well. The resulting systems often do not meet customers' expectations and eventually require major rework. This book includes a discussion on how to use and document Use Cases and how to use storyboarding to reflect the requirements back to the user as well as a thorough discussion of Object Oriented modeling to include Class Diagrams, State Transition Diagrams, and Interaction Diagrams. The authors also provide a description of how to represent the Class Diagram in an IEEE standard Software Requirements Specification and a description of how to build a set of test cases based on the requirements. A case study to illustrate the use of this process.
show more

Product details

  • Paperback | 288 pages
  • 177.8 x 235.2 x 20.6mm | 548.86g
  • Prentice Hall
  • Upper Saddle River, United States
  • English
  • 0130969729
  • 9780130969729

Back cover copy

Effective requirements development: An end-to-end process that works.

How to build requirements that can easily be transformed into high-quality software Easy-to-apply, start-to-finish methodology based on the Unified ProcessPractical solutions for requirements gathering, analysis, specification, and maintenance

This book presents a systematic, easy-to-apply methodology for creating effective requirements. The authors present practical solutions for the full requirements lifecycle: gathering, analysis, specification, verification, and maintenance. Working in the context of the Unified Process, they cover process flows, present detailed diagrams, and offer insights that draw on their extraordinary mission-critical project experience, which ranges from the floor of the New York Stock Exchange to the U.S. Air Force's most advanced Command and Control Systems.

The key characteristics of good software requirementsUnderstanding the requirements analysis process and artifactsBuilding user requirements problem domains, actors, use cases, activity diagrams, and storyboardingBuilding the requirements architecture entities and events, class diagrams, state transition diagrams, and sequence diagramsBuilding the specifications software requirements, interface requirements, and verificationUsing the requirements architecture you've built

Whether you're an analyst, architect, developer, tester, manager, or software customer, this book will help you define requirements that precisely reflect your needs--and can be transformed into working software faster and more cost-effectively than ever before.
show more

Table of contents

Preface. Acknowledgments. I. INTRODUCING GOOD REQUIREMENTS. 1. The Importance of Good Requirements. Rationale for Good Requirements. Approach to Good Requirements. Benefits of Good Requirements. Impact of Good Requirements on Development and Productivity. Impact of Good Requirements on Testing and Quality. Impact of Good Requirements on the Organization. Identification of a Good Requirement.2. Characteristics of Good Requirements. Characteristics of a Good Requirement. Characteristics of a Good Set of Requirements. Language of Good Requirements. Communicability of Good Requirements.3. Overview of the Artifacts and the Process. Introduction to the Artifacts. Introduction to the Process. Moving from Requirements to Design.II. BUILDING THE USER REQUIREMENTS. 4. Getting to Know the Problem Domain. Researching the Area. Reading, Reading, Reading. Interviewing the Customer and Users. Building the Use Cases.5. Actors and Use Cases. Defining the Boundaries of the System. Moving from Steady State to Steady State. Identifying Use Cases. Introducing the Change Management System Example.6. Modeling Use Cases. Diagramming Use Cases. Generalizing Use Cases. Generalizing Use Cases for the Change Management System. Relationships Among Use Cases. Diagramming Change Management System Use Cases. Packaging Use Cases. Packaging the Change Management System Use Cases.7. Using Activity Diagrams to Represent Use Cases. Elements of Activity Diagrams. Change Management System Activity Diagram.8. Writing Use Cases. Template Use. Step-by-Step Description. Alternative Courses. Exceptions and Issues. Change Management Use Case.9. Using Storyboards to Validate the Use Cases. Presentation of Storyboards to the User. Evolutionary Graphical User Interface Presentations. Other Diagrams and Pictures. Presentation of Use Cases to the User. Change Management Systems Storyboards.III. BUILDING THE REQUIREMENTS ARCHITECTURE. 10. Entities and Events as Objects. Classes and Objects. Remembered Events as Classes. Change Management System Classes.11. Building a Class Diagram. Generalization. Polymorphism. Aggregation. Association. Packaging Classes. Change Management System Examples.12. Using State Transition Diagrams. Introduction to State Transition Diagrams. Class-Level State Transition Diagrams. Use-Case-Level State Transition Diagrams. System-Level State Transition Diagrams. Change Management System State Transition Diagram.13. Use Case Realization by Means of Sequence Diagrams. Introduction to Sequence Diagrams. Realizing Use Cases in Sequence Diagrams. Example Sequence Diagram for the Change Management System.IV. BUILDING THE SPECIFICATIONS. 14. Developing a Software Requirements Specification. Tailoring the Standard to Meet Your Needs. Specifying Functional Requirements from the Class Diagram. Specifying Nonfunctional Requirements. Identifying Dependencies Between Requirements.15. Developing an Interface Requirement Specification. The IRS Template. Front Matter of the IRS. Reference Section of the IRS. Requirement Section of the IRS. Protocol and Messages Section of the IRS.16. Verifying the Software Requirements Specification. Using the Process to Ensure Good Requirements. Using Peer Reviews to Ensure Good Requirements. Specifying a Test Tree. Analyzing the Test Tree. Requirements Verification Checklist.V. USING THE REQUIREMENTS ARCHITECTURE. 17. Maintaining the System. Receiving the Change Request. Analyzing the Change. Analyzing User Needs. Identifying New and Changed Use Cases. Identifying New and Changed Requirements. Implementing a Release.18. Ensuring Maximum Benefits from the Requirements. Benefits to Development and Productivity Revisited. Benefits to Testing and Quality Revisited. Benefits to the Organization Revisited.VI. APPENDICES. Appendix A. Planning Model for Requirements Development. Model Work Breakdown Structure. Model Effort Allocation. Model Schedule Allocation. Standard Major Milestones.Appendix B. Change Management System Artifacts. Change Management System Use Cases. Change Management System Class Diagrams. Change Management System State Diagrams. Change Management Software Requirements Specification.Bibliography. Index.
show more

About Daniel R. Windle

DANIEL R. WINDLE has extensive experience applying the object-oriented paradigm to all facets of software development. As Managing Director of Requirements Development at SIAC in New York City, he led the development of a requirements architecture for the specialist system on the floor of the New York Stock Exchange. He has more than 20 years' experience in the IT industry. L. RENE ABREO leads a team of requirements analysts developing requirements for major equity trading systems using UML and the Unified Process. Rene has participated in major projects as project/program manager, team lead, developer, requirements analyst, and test director.
show more

Rating details

2 ratings
3 out of 5 stars
5 0% (0)
4 0% (0)
3 100% (2)
2 0% (0)
1 0% (0)
Book ratings by Goodreads
Goodreads is the world's largest site for readers with over 50 million reviews. We're featuring millions of their reader ratings on our book pages to help you find your new favourite book. Close X