Page 90 - Software and Systems Requirements Engineering in Practice
P. 90
60 S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e
SRS Document
Mgmt
Requirements Repository 10 Generate SRS Document Status report
Requirements 4 Assess Impact with Project Team 9 Review Activities with Mgmt Change control documents Project Library
3 Verify in Scope
Reviewed requirements Mapped requirements Requirements Repository Mapped requirements Impact analysis Risk analysis Repository information Mapped deliverables Requirements Repository
Verify Requirements 8 Map Deliverables to Requirements Mapped requirements
2 Testable
5 Negotiate Changes
Updated requirements Requirements change Change control documents Project Library Data flow diagram for a requirements management process
Failed requirements 1 Capture Stakeholder Requests Updated requirements Requirements Repository Change control information
Request Business requirements
6 Allocate Requirements Design changes CASE Repository 7 Track Change Flow Through
Client
Updated project schedule Manpower allocation Revised Project Library Schedule FIGURE 3.10
