book

Software Requirements Using the Unified Process: A Practical Approach

Name: Software Requirements Using the Unified Process: A Practical Approach
ISBN: 0130969729

by Daniel R. Windle, L. Rene Abreo

August 2002

Intermediate to advanced

288 pages

4h 37m

English

Pearson

Read now

Unlock full access

Copyright
Preface
Acknowledgments
1. Introducing Good Requirements
1. The Importance of Good Requirements
Rationale for Good RequirementsApproach to Good RequirementsBenefits of Good RequirementsImpact of Good Requirements on Development and ProductivityImpact of Good Requirements on Testing and QualityImpact of Good Requirements on the OrganizationIdentification of a Good Requirement
2. Characteristics of Good Requirements
Characteristics of a Good RequirementAmbiguity ConsiderationsModeling LanguagesThe Z Specification LanguageVerifiability ConsiderationsDeterministic ConsiderationsTraceability ConsiderationsCorrectness ConsiderationsCharacteristics of a Good Set of RequirementsLanguage of Good RequirementsCommunicability of Good Requirements
3. Overview of the Artifacts and the Process
Introduction to the ArtifactsIntroduction to the ProcessIterative Nature of the ProcessProcess FlowMoving from Requirements to Design
2. Building the User Requirements
4. Getting to Know the Problem Domain
Researching the AreaReading, Reading, ReadingInterviewing the Customer and UsersBuilding the Use Cases
5. Actors and Use Cases
Defining the Boundaries of the SystemMoving from Steady State to Steady StateIdentifying Use CasesIntroducing the Change Management System Example

6. Modeling Use Cases
Diagramming Use CasesGeneralizing Use CasesGeneralizing Use Cases for the Change Management SystemRelationships Among Use CasesDiagramming Change Management System Use CasesPackaging Use CasesPackaging the Change Management System Use Cases
7. Using Activity Diagrams to Represent Use Cases
Elements of Activity DiagramsChange Management System Activity Diagram
8. Writing Use Cases
Template UseStep-by-Step DescriptionAlternative CoursesExceptions and IssuesChange Management Use Case
9. Using Storyboards to Validate the Use Cases
Presentation of Storyboards to the UserEvolutionary Graphical User Interface PresentationsOther Diagrams and PicturesPresentation of Use Cases to the UserChange Management Systems Storyboards
3. Building the Requirements Architecture
10. Entities and Events as Objects
Classes and ObjectsRemembered Events as ClassesChange Management System Classes
11. Building a Class Diagram
GeneralizationPolymorphismAggregationAssociationPackaging ClassesChange Management System Examples
12. Using State Transition Diagrams
Introduction to State Transition DiagramsClass-Level State Transition DiagramsUse-Case-Level State Transition DiagramsSystem-Level State Transition DiagramsChange Management System State Transition Diagram
13. Use Case Realization by Means of Sequence Diagrams
Introduction to Sequence DiagramsRealizing Use Cases in Sequence DiagramsExample Sequence Diagram for the Change Management System
4. Building the Specifications
14. Developing a Software Requirements Specification
Tailoring the Standard to Meet Your NeedsSpecifying Functional Requirements from the Class DiagramSpecifying Nonfunctional RequirementsIdentifying Dependencies Between Requirements
15. Developing an Interface Requirement Specification
The IRS TemplateFront Matter of the IRSReference Section of the IRSRequirement Section of the IRSProtocol and Messages Section of the IRS
16. Verifying the Software Requirements Specification
Using the Process to Ensure Good RequirementsUsing Peer Reviews to Ensure Good RequirementsSpecifying a Test TreeAnalyzing the Test TreeRequirements Verification Checklist
5. Using the Requirements Architecture
17. Maintaining the System
Receiving the Change RequestAnalyzing the ChangeAnalyzing User NeedsIdentifying New and Changed Use CasesIdentifying New and Changed RequirementsImplementing a Release
18. Ensuring Maximum Benefits from the Requirements
Benefits to Development and Productivity RevisitedBenefits to Testing and Quality RevisitedBenefits to the Organization Revisited
6. Appendices
A. Planning Model for Requirements Development
Model Work Breakdown StructureModel Effort AllocationModel Schedule AllocationStandard Major Milestones
B. Change Management System Artifacts
Change Management System Use CasesChange Management Packages1. AdministrationUse Case 1.1 Log inActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 1.2 Add User RecordActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 1.3 Edit User RecordActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 1.4 Delete User RecordActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 1.5 Add System RecordActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsAssumptionsNotes and IssuesUse Case 1.6 Edit System RecordActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 1.7 Delete System RecordActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and Issues2. Change FunctionsUse Case 2.1 Submit Work RequestActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 2.2 View/Edit Work OrderActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 2.3 View/Edit Change OrderActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 2.4 Manage Change OrderActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 2.5 Query Work OrdersActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and Issues3. Manage ProjectUse Case 3.1 Create VersionActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 3.2 View/Edit VersionActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 3.3 Assign Change Orders to VersionActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 3.4 Remove Change Order from VersionActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 3.5 Approve Version StartActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesUse Case 3.6 Approve Version ReleaseActor(s)DescriptionPreconditionsPostconditionsPriorityNormal Course of EventsAlternative CoursesExceptionsIncludesNotes and IssuesChange Management System Class DiagramsChange Management System State DiagramsChange Management Software Requirements Specification1. Introduction1.1. Purpose1.2. Scope1.3. Definitions, Acronyms, and Abbreviations1.4. References1.5. Overview2. Overall Description2.1. Product Perspective2.1.1. System interfaces2.1.2. User interfaces2.1.3. Hardware interfaces2.1.4. Software interfaces2.1.5. Communications interfaces2.1.6. Memory2.1.7. Operations2.1.8. Site adaptation requirements2.2. Product Functions2.3. User Characteristics2.3.1. User2.3.2. Analyst2.3.3. Project Manager2.3.4. Change Control Board2.3.5. Administrator2.4. Constraints2.5. Assumptions and Dependencies2.6. Apportioning of Requirements3. Specific Requirements3.1. External Interface Requirements3.1.1. Graphical User Interfaces3.1.1.1. RN C1000, Login Screen3.1.1.1.1. RN C1000-A1, User Name3.1.1.1.2. RN C1000-A2, Password3.1.1.1.3. RN C1000-M1, Display3.1.1.1.4. RN C1000-M2, Click Login3.1.1.1.5. RN C1000-M3, Click Cancel3.1.1.2. RN C1001, Main Screen31.1.2.1. RN C1001-M1, Startup3.1.1.2.2. RN C1001-M2, Display3.1.1.2.3. RN C1001-M3, Click Admin3.1.1.2.4. RN C1001-M4, Click Enter Request3.1.1.2.5. RN C1001-M5, Click Edit Change Request3.1.1.2.6. RN C1001-M6, Click Manage Release3.1.1.2.7. RN C1001-M7 Click Query Changes3.1.1.3. RN C1002, Admin Screen3.1.1.3.1. RN C1002-M1, Display3.1.1.3.2. RN C1002-M2, Click Maintain Persons3.1.1.3.3. RN C1002-M3, Click Maintain Systems3.1.1.4. RN C1003, User Screen3.1.1.4.1. RN C1003-A1, Name3.1.1.4.2. RN C1003-A2, User Identifier3.1.1.4.3. RN C1003-A3, Password3.1.1.4.4. RN C1003-A4, E-Mail3.1.1.4.5. RN C1003-A5, Administrator3.1.1.4.6. RN C1003-A6, Available Systems3.1.1.4.7. RN C1003-A7, Assigned Systems3.1.1.4.8. RN C1003-A8, System Role3.1.1.4.9. RN C1003-M1, Display3.1.1.4.10. RN C1003-M2, Click Add Person3.1.1.4.11. RN C1003-M3, Click Save Person3.1.1.4.12. RN C1003-M4, Select Person3.1.1.4.13. RN C1003-M5, Click Delete User3.1.1.5. RN C1004, System Screen3.1.1.5.1. RN C1004-A1, Name3.1.1.5.2. RN C1004-A2, Parent3.1.1.5.3. RN C1004-M1, Display3.1.1.5.4. RN C1004-M2, Click Add System3.1.1.5.5. RN C1004-M3, Click Save Changes3.1.1.5.6. RN C1004-M4, Click Delete System3.1.1.5.7. RN C1004-M5, Select System3.1.1.5.8. RN C1004-M6, Click Abandon Changes3.1.1.6. RN C1005, Change Request Screen3.1.1.6.1. RN C1005-A1, Name3.1.1.6.2. RN C1005-A2, System3.1.1.6.3. RN C1005-A3, Problem Type3.1.1.6.4. RN C1005-A4, Description3.1.1.6.5. RN C1005-M1, Display3.1.1.6.6. RN C1005-M2, Click Submit3.1.1.6.7. RN C1005-M3, Click Abandon3.1.1.6.8. RN C1005-M4, Select Change Request3.1.1.6.9. RN C1005-M5, Select Type3.1.1.6.10. RN C1005-M6, Select Work Request3.1.1.7. RN C1006, Manage Release3.1.1.7.1. RN C1006-A1, System3.1.1.7.2. RN C1006-A2, Phase3.1.1.7.3. RN C1006-A3, Estimated Start3.1.1.7.4. RN C1006-A4, Estimated Complete3.1.1.7.5. RN C1006-A5, Start3.1.1.7.6. RN C1006-A6, Complete3.1.1.7.7. RN C1006-A7, Selected Changes3.1.1.7.8. RN C1006-A8, Unassigned Changes3.1.1.7.9. RN C1006-M1, Display3.1.1.7.10. RN C1006-M2, Select Unassigned Orders3.1.1.7.11. RN C1006-M3, Click Assign3.1.1.7.12. RN C1006-M4, Click Save3.1.1.7.13. RN C1006-M5, Select System3.1.1.7.14. RN C1006-M6, Click Add3.1.1.7.15. RN C1006-M7, Select Assigned Change3.1.1.7.16. RN C1006-M8, Select Version3.1.1.7.17. RN C1006-M9, Set Approve Work3.1.1.7.18. RN C1006-M10, Set Approve Release3.1.1.8. RN C1007, Query Change Screen3.1.1.8.1. RN C1007-A1, Request Number3.1.1.8.2. RN C1007-A2, System3.1.1.8.3. RN C1007-A3, Release3.1.1.8.4. RN C1007-A4, Submitted By3.1.1.8.5. RN C1007-A5, Phase3.1.1.8.6. RN C1007-M1, Display3.1.1.8.7. RN C1007-M2, Select Criteria3.1.1.8.8. RN C1007-M3, Click Retrieve Changes3.1.1.9. RN C1008, Query Results Screen3.1.1.9.1. RN C1008-A1, Name3.1.1.9.2. RN C1008-A2, System3.1.1.9.3. RN C1008-A3, Problem Type3.1.1.9.4. RN C1008-A4, Submitter3.1.1.9.5. RN C1008-M1, Display3.1.1.9.6. RN C1008-M2, Click Retrieve Request3.1.2. Hardware interfaces3.1.3. Software interfaces3.1.4. Communications interfaces3.2. Classes/Objects3.2.1. RN C1, System3.2.1.1. RN C1-A1, Name3.2.1.2. RN C1-A2, Parent3.2.1.3. RN C1-M1, Get Systems3.2.1.4. RN C1-M2, Create System3.2.1.5. RN C1-M3, Save System3.2.1.6. RN C1-M4, Remove System3.2.1.7. RN C1-M5, Select System3.2.1.8. RN C1-M6, Get System3.2.1.9. RN C1-M7, Get Releases3.2.1.10. RN C1-M8, New Release3.2.1.11. RN C1-M9, Assign Change to Release3.2.1.12. RN C1-M10, Save Release3.2.1.13. RN C1-M11, Set Release Status3.2.1.14. RN C1-M12, Get Parent3.2.1.15. RN C1-M13, Add Work Request3.2.1.16. RN C1-M14, Remove Work Request3.2.1.17. RN C1-M15, Get Work Requests3.2.2. RN C2, Person3.2.2.1. RN C2-A1, Name3.2.2.2. RN C2-A2, Login Identifier3.2.2.3. RN C2-A3, Password3.2.2.4. RN C2-A4, Administrator3.2.2.5. RN C2-M1, Test Password3.2.2.6. RN C2-M2, Create Person Record3.2.2.7. RN C2-M3, Get Person Record3.2.2.8. RN C2-M4, Get System Roles3.2.2.9. RN C2-M5, Set Person Record3.2.2.10. RN C2-M6, Delete User3.2.2.11. RN C2-M7, Get Persons3.2.2.12. RN C2-M8, Is Administrator3.2.3. RN C3, System Role3.2.3.1. RN C3-A1, Role3.2.3.2. RN C3-M1, Add System Role3.2.3.3. RN C3-M2, Get System Roles3.2.3.4. RN C3-M3, Set System Roles3.2.3.5. RN C3-M4, Delete System Role3.2.4. RN C4, Version/Release3.2.4.1. RN C4-A1, Number3.2.4.2. RN C4-A2, Estimated Start Date3.2.4.3. RN C4-A3, Start Date3.2.4.4. RN C4-A4, Estimated Completion Date3.2.4.5. RN C4-A5, Completion Date3.2.4.6. RN C4-A6, Current Phase3.2.4.7. RN C4-M1, Get Releases3.2.4.8. RN C4-M2, Get Release3.2.4.9. RN C4-M3, Assign Changes3.2.4.10. RN C4-M4, Create Release3.2.4.11. RN C4-M5, Save Release3.2.4.12. RN C4-M6, Set Release Status3.2.4.13. RN C4-M7, Delete Release3.2.4.14. RN C4-M8, Remove Change Order3.2.4.15. RN C4-M9, Get Change Orders3.2.5. RN C5, Work Request3.2.5.1. RN C5-A1, Submitter3.2.5.2. RN C5-A2, Date Of Request3.2.5.3. RN C5-A3, Analyst3.2.5.4. RN C5-A4, Description3.2.5.5. RN C5-A5, Remarks3.2.5.6. RN C5-A6, Date Closed3.2.5.7. RN C5-A7, Priority3.2.5.8. RN C5-M1, Create Work Request3.2.5.9. RN C5-M2, Save Work Request3.2.5.10. RN C5-M3, Get Work Request3.2.5.11. RN C5-M4, Get Work Requests3.2.5.12. RN C5-M5, Delete Work Requests3.2.5.13. RN C5-M6, Check Status3.2.6. RN C6, Change History3.2.6.1. RN C6-A1, Old State3.2.6.2. RN C6-A2, New State3.2.6.3. RN C6-A3, Date Time Of Change3.2.6.4. RN C6-M1, Create Change History3.2.7. RN C7, Work Order3.2.7.1. RN C7-A1, Problem Area3.2.7.2. RN C7-M1, Check Status3.2.8. RN C8, Change Order3.2.8.1. RN C8-M1, Check Status3.2.9. RN C9, Defect Report3.2.9.1. RN C9-A1, Release Introduced3.2.9.2. RN C9-A2, Phase Introduced3.2.9.3. RN C9-A3, Test Description3.2.9.4. RN C9-A4, Severity3.2.10. RN C10, Change Request3.2.10.1. RN C10-A1, Requirements Affected3.2.11. RN C11, New System3.3. Performance Requirements3.3.1. Transaction time3.3.2. Concurrent users3.4. Logical Database Requirements3.5. Design Constraints3.6. Standards Compliance3.7. Software System Attributes3.7.1. Reliability3.7.2. Availability3.7.3. Security3.7.4. Maintainability3.7.5. Portability3.8. Other Requirements
Bibliography

Overview

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.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Enterprise Unified Process, The: Extending the Rational Unified Process

Publisher Resources

ISBN: 0130969729Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills