Project Phases

This page details the architecture expectations for each implementation phase of a project.

Discovery

Assets which show the following

Understanding the business problem
Understanding of the current technical capabilities ..* Diagram of the technical landscape for this domain
Alpha backlog (Epics)

Assets which show the following

A business description of the problem domain
- This must focus on understanding all of the services outside of the Apprenticeship Service
A logical diagram of all systems involved in the problem (including external systems)
Description of Alpha technical goals
- This must include a list of the technology problem that are being tested in Alpha
Beta high level technical product backlog (Epics)

Integration catalog (Technical)

Assets describing the following are required through this phase

A business description of the proposed beta solution including any MVS version outlines
Logical business systems diagram
High level business requirements/user needs
- Should only be 5-6 of these as defined by the project
Integration catalogue (technical)
- Diagram showing the technical system and their specific integration points
- Description of the technical implementation of each of the integrations
Solution Components technical description
- Technologies
- Patterns
Non-functional requirements of the service
Understanding how we are going to support the private beta delivery
- Ramping up users/limiting user access

Assets describing the following are required through this phase

Accurate diagram and description of the Live service
Details required to support service
- Processes and fault resolution information
Information showing any issues with the MVS product
Information about how the product will mature
Technical dashboard showing service performance (this should be created/maintained by the team not architect)
Input into the CI readiness plan/pack