Book description
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 Process
Practical 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 requirements
Understanding the requirements analysis process and artifacts
Building user requirements problem domains, actors, use cases, activity diagrams, and storyboarding
Building the requirements architecture entities and events, class diagrams, state transition diagrams, and sequence diagrams
Building the specifications software requirements, interface requirements, and verification
Using 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.
Table of contents
- Copyright
- Preface
- Acknowledgments
- 1. Introducing Good Requirements
- 2. Building the User Requirements
- 3. Building the Requirements Architecture
- 4. Building the Specifications
- 5. Using the Requirements Architecture
-
6. Appendices
- A. Planning Model for Requirements Development
-
B. Change Management System Artifacts
-
Change Management System Use Cases
- Change Management Packages
- 1. Administration
- Use Case 1.1 Log in
- Use Case 1.2 Add User Record
- Use Case 1.3 Edit User Record
- Use Case 1.4 Delete User Record
- Use Case 1.5 Add System Record
- Use Case 1.6 Edit System Record
- Use Case 1.7 Delete System Record
- 2. Change Functions
- Use Case 2.1 Submit Work Request
- Use Case 2.2 View/Edit Work Order
- Use Case 2.3 View/Edit Change Order
- Use Case 2.4 Manage Change Order
- Use Case 2.5 Query Work Orders
- 3. Manage Project
- Use Case 3.1 Create Version
- Use Case 3.2 View/Edit Version
- Use Case 3.3 Assign Change Orders to Version
- Use Case 3.4 Remove Change Order from Version
- Use Case 3.5 Approve Version Start
- Use Case 3.6 Approve Version Release
- Change Management System Class Diagrams
- Change Management System State Diagrams
-
Change Management Software Requirements Specification
- 1. Introduction
- 2. Overall Description
-
3. Specific Requirements
-
3.1. External Interface Requirements
-
3.1.1. Graphical User Interfaces
- 3.1.1.1. RN C1000, Login Screen
- 3.1.1.2. RN C1001, Main Screen
- 3.1.1.3. RN C1002, Admin Screen
-
3.1.1.4. RN C1003, User Screen
- 3.1.1.4.1. RN C1003-A1, Name
- 3.1.1.4.2. RN C1003-A2, User Identifier
- 3.1.1.4.3. RN C1003-A3, Password
- 3.1.1.4.4. RN C1003-A4, E-Mail
- 3.1.1.4.5. RN C1003-A5, Administrator
- 3.1.1.4.6. RN C1003-A6, Available Systems
- 3.1.1.4.7. RN C1003-A7, Assigned Systems
- 3.1.1.4.8. RN C1003-A8, System Role
- 3.1.1.4.9. RN C1003-M1, Display
- 3.1.1.4.10. RN C1003-M2, Click Add Person
- 3.1.1.4.11. RN C1003-M3, Click Save Person
- 3.1.1.4.12. RN C1003-M4, Select Person
- 3.1.1.4.13. RN C1003-M5, Click Delete User
-
3.1.1.5. RN C1004, System Screen
- 3.1.1.5.1. RN C1004-A1, Name
- 3.1.1.5.2. RN C1004-A2, Parent
- 3.1.1.5.3. RN C1004-M1, Display
- 3.1.1.5.4. RN C1004-M2, Click Add System
- 3.1.1.5.5. RN C1004-M3, Click Save Changes
- 3.1.1.5.6. RN C1004-M4, Click Delete System
- 3.1.1.5.7. RN C1004-M5, Select System
- 3.1.1.5.8. RN C1004-M6, Click Abandon Changes
-
3.1.1.6. RN C1005, Change Request Screen
- 3.1.1.6.1. RN C1005-A1, Name
- 3.1.1.6.2. RN C1005-A2, System
- 3.1.1.6.3. RN C1005-A3, Problem Type
- 3.1.1.6.4. RN C1005-A4, Description
- 3.1.1.6.5. RN C1005-M1, Display
- 3.1.1.6.6. RN C1005-M2, Click Submit
- 3.1.1.6.7. RN C1005-M3, Click Abandon
- 3.1.1.6.8. RN C1005-M4, Select Change Request
- 3.1.1.6.9. RN C1005-M5, Select Type
- 3.1.1.6.10. RN C1005-M6, Select Work Request
-
3.1.1.7. RN C1006, Manage Release
- 3.1.1.7.1. RN C1006-A1, System
- 3.1.1.7.2. RN C1006-A2, Phase
- 3.1.1.7.3. RN C1006-A3, Estimated Start
- 3.1.1.7.4. RN C1006-A4, Estimated Complete
- 3.1.1.7.5. RN C1006-A5, Start
- 3.1.1.7.6. RN C1006-A6, Complete
- 3.1.1.7.7. RN C1006-A7, Selected Changes
- 3.1.1.7.8. RN C1006-A8, Unassigned Changes
- 3.1.1.7.9. RN C1006-M1, Display
- 3.1.1.7.10. RN C1006-M2, Select Unassigned Orders
- 3.1.1.7.11. RN C1006-M3, Click Assign
- 3.1.1.7.12. RN C1006-M4, Click Save
- 3.1.1.7.13. RN C1006-M5, Select System
- 3.1.1.7.14. RN C1006-M6, Click Add
- 3.1.1.7.15. RN C1006-M7, Select Assigned Change
- 3.1.1.7.16. RN C1006-M8, Select Version
- 3.1.1.7.17. RN C1006-M9, Set Approve Work
- 3.1.1.7.18. RN C1006-M10, Set Approve Release
- 3.1.1.8. RN C1007, Query Change Screen
- 3.1.1.9. RN C1008, Query Results Screen
- 3.1.2. Hardware interfaces
- 3.1.3. Software interfaces
- 3.1.4. Communications interfaces
-
3.1.1. Graphical User Interfaces
-
3.2. Classes/Objects
-
3.2.1. RN C1, System
- 3.2.1.1. RN C1-A1, Name
- 3.2.1.2. RN C1-A2, Parent
- 3.2.1.3. RN C1-M1, Get Systems
- 3.2.1.4. RN C1-M2, Create System
- 3.2.1.5. RN C1-M3, Save System
- 3.2.1.6. RN C1-M4, Remove System
- 3.2.1.7. RN C1-M5, Select System
- 3.2.1.8. RN C1-M6, Get System
- 3.2.1.9. RN C1-M7, Get Releases
- 3.2.1.10. RN C1-M8, New Release
- 3.2.1.11. RN C1-M9, Assign Change to Release
- 3.2.1.12. RN C1-M10, Save Release
- 3.2.1.13. RN C1-M11, Set Release Status
- 3.2.1.14. RN C1-M12, Get Parent
- 3.2.1.15. RN C1-M13, Add Work Request
- 3.2.1.16. RN C1-M14, Remove Work Request
- 3.2.1.17. RN C1-M15, Get Work Requests
-
3.2.2. RN C2, Person
- 3.2.2.1. RN C2-A1, Name
- 3.2.2.2. RN C2-A2, Login Identifier
- 3.2.2.3. RN C2-A3, Password
- 3.2.2.4. RN C2-A4, Administrator
- 3.2.2.5. RN C2-M1, Test Password
- 3.2.2.6. RN C2-M2, Create Person Record
- 3.2.2.7. RN C2-M3, Get Person Record
- 3.2.2.8. RN C2-M4, Get System Roles
- 3.2.2.9. RN C2-M5, Set Person Record
- 3.2.2.10. RN C2-M6, Delete User
- 3.2.2.11. RN C2-M7, Get Persons
- 3.2.2.12. RN C2-M8, Is Administrator
- 3.2.3. RN C3, System Role
-
3.2.4. RN C4, Version/Release
- 3.2.4.1. RN C4-A1, Number
- 3.2.4.2. RN C4-A2, Estimated Start Date
- 3.2.4.3. RN C4-A3, Start Date
- 3.2.4.4. RN C4-A4, Estimated Completion Date
- 3.2.4.5. RN C4-A5, Completion Date
- 3.2.4.6. RN C4-A6, Current Phase
- 3.2.4.7. RN C4-M1, Get Releases
- 3.2.4.8. RN C4-M2, Get Release
- 3.2.4.9. RN C4-M3, Assign Changes
- 3.2.4.10. RN C4-M4, Create Release
- 3.2.4.11. RN C4-M5, Save Release
- 3.2.4.12. RN C4-M6, Set Release Status
- 3.2.4.13. RN C4-M7, Delete Release
- 3.2.4.14. RN C4-M8, Remove Change Order
- 3.2.4.15. RN C4-M9, Get Change Orders
-
3.2.5. RN C5, Work Request
- 3.2.5.1. RN C5-A1, Submitter
- 3.2.5.2. RN C5-A2, Date Of Request
- 3.2.5.3. RN C5-A3, Analyst
- 3.2.5.4. RN C5-A4, Description
- 3.2.5.5. RN C5-A5, Remarks
- 3.2.5.6. RN C5-A6, Date Closed
- 3.2.5.7. RN C5-A7, Priority
- 3.2.5.8. RN C5-M1, Create Work Request
- 3.2.5.9. RN C5-M2, Save Work Request
- 3.2.5.10. RN C5-M3, Get Work Request
- 3.2.5.11. RN C5-M4, Get Work Requests
- 3.2.5.12. RN C5-M5, Delete Work Requests
- 3.2.5.13. RN C5-M6, Check Status
- 3.2.6. RN C6, Change History
- 3.2.7. RN C7, Work Order
- 3.2.8. RN C8, Change Order
- 3.2.9. RN C9, Defect Report
- 3.2.10. RN C10, Change Request
- 3.2.11. RN C11, New System
-
3.2.1. RN C1, System
- 3.3. Performance Requirements
- 3.4. Logical Database Requirements
- 3.5. Design Constraints
- 3.6. Standards Compliance
- 3.7. Software System Attributes
-
3.1. External Interface Requirements
-
Change Management System Use Cases
- Bibliography
Product information
- Title: Software Requirements Using the Unified Process: A Practical Approach
- Author(s):
- Release date: August 2002
- Publisher(s): Pearson
- ISBN: 0130969729
You might also like
book
The Art of Game Design, 3rd Edition
The Art of Game Design guides you through the design process step-by-step, helping you to develop …
book
How to Use Objects: Code and Concepts
While most developers today use object-oriented languages, the full power of objects is available only to …
book
Designing Machine Learning Systems
Machine learning systems are both complex and unique. Complex because they consist of many different components …
book
Infrastructure as Code, 2nd Edition
Six years ago, Infrastructure as Code was a new concept. Today, as even banks and other …