Application Software Implementation - Requirements Processes

Processes descriptions are numbered for ease of access. These numbers do not necessarily represent the sequence in which they are performed.  Also for ease of access the numbers are prefixed by a letter showing the type of segment or path that it applies to. Below is a list of typical Requirement Processes 

L	Launch (Project Launch & Segment Launch)
R	Requirements
S	Selection
D	Delivery
P	Post-implementation (Post-implementation Management, Post‑implementation review, Business Benefits Assessment)
Q	Quality Audit reviews
T	Terminate Project

Ref	Process	Path Templates
R010	Foundation - “as-is” fact-find	Requirements - Full, Project Model
R020	Business Vision / Objectives / Do-Wells	Requirements - Full, Project Model
R030	External Business Review	Requirements - Full, Project Model
R040	Constraints	Requirements - Full, Requirements - Catalogue, Project Model
R050	Needs for business process change and priorities	Requirements - Full, Project Model
R055	Select package-specific base business model templates	Project Model
R060	External Technical Review	Requirements - Full, Project Model
R065	Create and maintain enterprise business model	Project Model
R067	Schedule process modelling workshops	Project Model
R068	Conduct process modelling workshops	Project Model
R069	Agree initial enterprise business model	Project Model
R070	System Vision: functions, data, volumes, performance, scope, objectives, boundaries / interfaces, technical goals, timescales	Requirements - Full, Requirements - Catalogue, Project Model
R080	Define Topics / IPs	Requirements - Full
R090	Organisational Impact	Requirements - Full, Project Model
R100	Identify requirements	Requirements - Full, Requirements - Catalogue, Project Model
R110	Interfacing review	Requirements - Full, Project Model
R120	Gap Analysis - existing systems vs requirements	Requirements - Full, Project Model
R125	Gap Analysis - requirements vs target solution	Project Model
R130	Establish architectural options	Requirements - Full, Requirements - Catalogue, Requirements - Validate, Project Model
R140	Estimate costs and benefits per option	Requirements - Full, Requirements - Catalogue, Requirements - Validate, Project Model
R150	Collate and agree requirements report	Requirements - Full, Requirements - Catalogue, Requirements - Validate, Project Model
R200	Agree appropriate processes	Requirements - Validate
R210	Agree appropriate deliverables	Requirements - Validate
R220	Review Client’s statement of requirements	Requirements - Validate
R230	Agree and conduct any further work required	Requirements - Validate
R900	Update materials	Requirements - Full