Analysis Team

Project Initiation

Requirements Analysis

Design

Development

Testing

• Project Charter• Integrated Plan• Draft Requirements Management Plan

• Business Problem Identification• Integrated Plan• Requirements Management Plan• Traceability metrics• Stakeholder Analysis

• Tech Design Specs• User Interface Mock ups

• Development Plan• Integrated service requirements

• Unit Testing Plan• Integration Testing Plan• User Acceptance testing Plan

Analysis Team• Functional Requirement

Documents• Review Log• Use Cases• Activity Diagrams/ Process

Maps• Change management logDesign Team/ Development Team• Data Dictionary• Design Review log• Non Functional Requirements

metrics• Technical design Specification

DocumentsTesting Team• Test Cases• Defect Log

• Create Repeatable & reusable Capability model of business functional areas• Create project artifacts that are reusable across the project life cycle• 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

Tools

Obj

ectiv

es

Work EffortProject Life Cycle

Approach for Requirements Analysis Where Documentation Is Available

TeamAnalysis of Existing

Documents

Analysis Team+PMO

Analysis Team +Business Stakeholders

Rework based on review

Analysis Team +Business Stakeholders

+PMO

Stage Pre Work Playback and Review Signoff

Work Effor

t

• Identification of List of stakeholders

• List of• Capabilities• Functionalities• High level process maps• Use cases

• High level Business Requirements

• Steps to use cases based on analysis of existing documentation

• Draft traceibility Metrics

Validate with Business users• Capabilities• Functionalities• Detailed process maps• Use cases • Requirements Transition

by Analysis team to Design team

• Update traceability Metric

• Create a parking lot for any unresolved issues

• Approval of Business requirements by Business SME and stakeholders

• List of Out of scope Item if any

• Closure of any Parking lot issues

• Requirements Transition by Analysis team to Design team

Deliverabl

es

Draft Documents of • Requirements Management

Plan• Functional Requirement

Documents• Use case Documents• Data Dictionary• Non Functional Requirement

Documents

Interim Documents for • Functional Requirement

Documents• Use case Documents• Data Dictionary• Non Functional

Requirement Documents

Signoff by Business SME• Functional Requirement

DocumentsSignoff By Client Architect & Design team• Use case Documents• Data Dictionary• Non Functional Requirement

Documents

The Requirements Management Plan is updated across the duration of Requirements & Analysis Phase

Document Coverage Objective

Requirements Management Plan

List of ,Capabilities Functionality and Use cases with Milestones to complete tasks and deliverables during the requirements analysis phase including detailed list of business SME’s that will be engaged with visibility into time needed

• Track Scope• Track progress• Stakeholder

Functional Requirements Document

Decomposition of high level business requirements detailing a business view of the problem statement

• Signoff tool for the business to validate coverage of business goals

• Track any changes in the functional scope

Use case Document

Steps to Business transactions • Artifact providing design, development and testing teams the details need for downstream activities

• Operational overview and inputs for any organizational change management

Data Dictionary

Data objects, Entities , Attributes, Enumerators and Enumerator Values

• Artifact needed by the design team to create appropriate User Interface mock ups and

• Input document for creating data marts for any data analysis initiatives

Non Functional Requirements Document

SLA’s and system related behavior expected , should cover aspects of performance, SLA’s

• Identify and track system technical requirements

Metrics Coverage Objective

Parking Lot Any unresolved issues during Requirements Sessions to be documented with item owner and a target resolution date, also stating priority of items that would impact the momentum of the requirements analysis phase

• Prevent long requirement sessions on topics that can be resolved offline

• Track turn around time for outstanding discussion points

Issues Log Known Issues that need Project sponsor validation

• Track decisions that need Project sponsor inputs • Turn around time needed to resolve open items

Risk Log List of risks due to project or outside factors

• Identify and manage know project and external risks

• Track ageing of the risks

Review Log Feedback on published documents from review teams

• Identify feedback from stakeholders• 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