From MIKE2 Methodology
|
| This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
|
| This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
|
| Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.
|
The Current State and Future State Architecture Gap Analysis task uses the current-state architecture and future-state conceptual architecture and identifies key capability gaps where there will be new product decisions required.
Examples
Listed below is an example Gap Analysis:
Example of a Current state Gap Analysis
- The current infrastructure will be difficult to maintain scalability for the new product and related customers
- The connectivity level to the Host System is a bottleneck which needs to be addressed for the new volumes expected
- The current infrastructure is not incorporate robust solutions for High Availability and Security and has no solution to Disaster Recovery