Once the requirements are gathered. We will start to analyze the requirements, this leads to Gap Analysis. A gap is essentially a “thing” that we need have/use in order to deliver solution in response to the requirements so a gap can fall into one or more following domains:

  1. IT Context
  2. Business and Business Process
  3. Money
  4. Data

High-level Gap Analysis

We do this analysis to create Gap Registry. Gap analysis can be done via listing in a table or mind-map if there are not too many requirements. But normally it is likely to have around hundreds to thousands requirements in medium to large project. We will list the gaps for each project phase:

  1. Analysis and Design
  2. Development, Build, Test
  3. Deployment and Distribution
  4. Life
  5. Migration
  6. Support and Maintenance
Gap ID Requirement ID Gap Description Domain(s) Project Phase(s)

Each gap could leads to Project Dependencies and each gap and each dependency lead to Impact(s) and Risk(s) later.

Dependency ID Gap ID Dependency Description Domain(s) Project Phase(s)

We will use this list of gaps and dependencies that fall into IT Context, Business Process, and Data domains to create Context Diagram.

High-level Impact Analysis

Gap or dependency could lead to one or more changes (either new or modification or even elimination) of one or more things in one or more domains.

Then we will prepare a Impact Registry to list all high level impacts as following table:

Impact ID Gap ID Dependency ID Impact Description Domain(s) Project Phase(s) Note(s)

We will use this created spreadsheet to raise impacts to senior management and project committee. And use the impacts that fall into IT Context, Business Process, and Data domains and the created Context Diagram to do further detailed impact analysis.

High-level Risks Analysis

This steps is to create Risks Registry which will be reviewed with governance team, stakeholders, and project committee as well as using in project management.

Risk ID Gap ID/Dependency ID Risk Description Impact Level (L/M/H) and Description Likelihood (L/M/H) and Description Mitigation Remark(s)

After review, the approved mitigation of each risk will be added into the next revision of the design for implementation.