The document outlines the project life cycle and work efforts for requirements analysis where documentation is already available. It involves analysis of existing documents by an analysis team along with business stakeholders and PMO. Key deliverables include a requirements management plan, functional requirements document, use case documents, and data and non-functional requirements documents. Metrics are used to track scope, progress, issues and risks. Stakeholder reviews are conducted and feedback is logged.

1. Project Life Work Effort Tools
Cycle
• Project Charter Analysis Team
Project Initiation • Integrated Plan • Functional Requirement
• Draft Requirements Management Plan Documents
• Review Log
• Business Problem Identification • Use Cases
• Integrated Plan • Activity Diagrams/ Process
Requirements • Requirements Management Plan Maps
Analysis • Traceability metrics • Change management log
• Stakeholder Analysis Design Team/ Development Team
Analysis Team
• Data Dictionary
• Design Review log
Design • Tech Design Specs • Non Functional Requirements
• User Interface Mock ups metrics
• Technical design Specification
Development • Development Plan Documents
• Integrated service requirements Testing Team
• Test Cases
• Unit Testing Plan • Defect Log
Testing • Integration Testing Plan
• User Acceptance testing Plan
• Create Repeatable & reusable Capability model of business functional areas
• Create project artifacts that are reusable across the project life cycle
Objectives
• Requirements analysis that is technology agnostic
• Manage Scope of deliverables against a documented benchmark
• Efficient Use of people time and Resources
• Track Scope Changes
• Track Rework and overall effort

2. Approach for Requirements Analysis Where Documentation Is Available
Analysis Team
Team
Analysis Team+ Analysis Team +Business
+Business Stakeholders
PMO Stakeholders
+PMO
Stage Pre Work Playback and Review Signoff
• Identification of List of Validate with Business users • Approval of Business
stakeholders • Capabilities requirements by Business
• List of • Functionalities SME and stakeholders
• Capabilities • Detailed process maps •
Analysis of Existing Documents
List of Out of scope Item if
• Functionalities • Use cases any
Work Effort
Rework based on review
• High level process maps • Requirements Transition • Closure of any Parking lot
• Use cases by Analysis team to issues
• High level Business Design team • Requirements Transition by
Requirements • Update traceability Analysis team to Design
• Steps to use cases based on Metric team
analysis of existing • Create a parking lot for
documentation any unresolved issues
• Draft traceibility Metrics
Draft Documents of Interim Documents for Signoff by Business SME
• Requirements Management • Functional Requirement • Functional Requirement
Plan Documents Documents
Deliverables
• Functional Requirement • Use case Documents Signoff By Client Architect &
Documents • Data Dictionary Design team
• Use case Documents • Non Functional • Use case Documents
• Data Dictionary Requirement Documents • Data Dictionary
• Non Functional Requirement • Non Functional Requirement
Documents Documents
The Requirements Management Plan is updated across the duration of Requirements & Analysis Phase

3. Document Coverage Objective
List of ,Capabilities Functionality and Use • Track Scope
cases with Milestones to complete tasks • Track progress
Requirements
and deliverables during the requirements • Stakeholder
Management
analysis phase including detailed list of
Plan
business SME’s that will be engaged with
visibility into time needed
Functional Decomposition of high level business • Signoff tool for the business to validate coverage
Requirements requirements detailing a business view of of business goals
Document the problem statement • Track any changes in the functional scope
Steps to Business transactions • Artifact providing design, development and testing
teams the details need for downstream activities
Use case • Operational overview and inputs for any
Document organizational change management
Data objects, Entities , Attributes, • Artifact needed by the design team to create
Data Enumerators and Enumerator Values appropriate User Interface mock ups and
Dictionary • Input document for creating data marts for any
data analysis initiatives
Non Functional SLA’s and system related behavior • Identify and track system technical requirements
Requirements expected , should cover aspects of
Document performance, SLA’s

4. Metrics Coverage Objective
Parking Lot Any unresolved issues during • Prevent long requirement sessions on topics that
Requirements Sessions to be documented can be resolved offline
with item owner and a target resolution • Track turn around time for outstanding discussion
date, also stating priority of items that points
would impact the momentum of the
requirements analysis phase
Issues Log Known Issues that need Project sponsor • Track decisions that need Project sponsor inputs
validation • Turn around time needed to resolve open items
Risk Log List of risks due to project or outside • Identify and manage know project and external
factors risks
• Track ageing of the risks
Review Log Feedback on published documents from • Identify feedback from stakeholders
review teams • Use the data to analyze the efficiency of the
analysis process
• Identify areas where business point of view is
fluid and needs to executive leadership to make
decisions