Software Requirements Using the Unified Process

Daniel R. Windle, L. Rene Abreo

  • 出版商: Prentice Hall
  • 出版日期: 2002-08-26
  • 售價: $1,570
  • 貴賓價: 9.5$1,492
  • 語言: 英文
  • 頁數: 280
  • 裝訂: Paperback
  • ISBN: 0130969729
  • ISBN-13: 9780130969729

已絕版

買這商品的人也買了...

商品描述

Software Requirements Using the Unified Process: A Practical Approach presents an easy-to-apply methodology for creating requirements. Learn to build user requirements, requirements architecture, and the specifications more quickly and at a lower cost. The authors present realistic solutions for the entire requirements process: gathering, analysis, specification, and maintenance.

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.