From MIKE2 Methodology
Activity: Future-State Logical Architecture and Gap Analysis
Objective
The activity to define the Future-State Logical Architecture and Gap Analysis uses the Conceptual Architecture as a starting point and then takes it to the next level, after more detailed requirements have been gathered for the overall solution. After completion of the Logical Architecture, the team will then have the necessary detail to map directly to vendor product offerings. The Logical Architecture states how the functional and non-functional requirements will be provided by a component in the architecture. Generally, all Logical Architecture capabilities will not be implemented in the first release; the Strategic Logical Architecture should be provided for the overall programme and show a progression in the implementation of technologies.
Major Deliverables
- Future-State Strategic Logical Architecture
Tasks
Map Strategic Requirements to Business (BI Application) Architecture
Objective:
This step takes the functional and non-functional requirements and expresses how a component in the architecture will provide this function. The Business Architecture model is at a logical level that can be understood by business users and contain the major functionality and business processes that will need to be supported by the user-facing system. The detail expressed in this model is at the level to make meaningful decisions between different vendor products.
Input:
- Key Functions Required of Information System
- Business Function End-User Matrix
- Organisation/Location/Association Matrix
- Non-Functional Requirements for Business Intelligence Development
- Future-State Conceptual Architecture
Output:
Map Strategic Requirements to Logical Architecture for Infrastructure Development
Objective:
This step takes the functional and non-functional infrastructure requirements and expresses how a component in the architecture will provide this function. The Logical Architecture model uses the Conceptual Architecture as a starting point. Generally, all Logical Architecture capabilities will not be implemented in the first release; the Logical Architecture should be provided for the overall programme and show a progression in the implementation of technologies.
Input:
- Foundation Capabilities for Information Development
- Foundation Capabilities for Infrastructure Development
- Advanced Capabilities for Information Development
- Advanced Capabilities for Infrastructure Development
- Non-Functional Requirements for Business Intelligence Development
- Non-Functional Requirements for Infrastructure Development
- Non-Functional Requirements for Information Development
- Future-State Conceptual Architecture
Output:
Map Strategic Requirements to Logical Architecture for Information Development
Objective:
This step takes the functional and non-functional requirements for the information development environment and expresses how a component in the architecture will provide this function. The Logical Architecture model uses the Conceptual Architecture as a starting point. Generally, all Logical Architecture capabilities will not be implemented in the first release; the Logical Architecture should be provided for the overall programme and show a progression in the implementation of technologies.
Input:
- Foundation Capabilities for Information Development
- Advanced Capabilities for Information Development
- Non-Functional Requirements for Information Development
Output:
Revise Future-State Conceptual Architecture
Objective:
The Logical Architecture provides the next level of detail below the Conceptual Architecture. The Logical Architecture that is the result of more detailed business requirements may results in revisions that will flow upwards into the Conceptual Architecture and the overall Blueprint.
Input:
Output:
- Revised Conceptual Architecture and overall Blueprint
Conduct Gap Analysis of Current-State and Future-State Logical Architecture
Objective:
Using the current-state architecture and future-state conceptual architecture, identify key capability gaps where there will be new product decisions required. This task will typically need to be revisited a few times, including after the selection of vendor technologies.
Input:
Output:
Core Supporting Assets
Yellow Flags
- Attempts to make current-state technology greatly exceed its native capabilities part of the map-and-gap exercise
- Under-reliance on working technologies – implementing new technology when it is not required and the current solution works well
Key Resource Requirements
Potential Changes to this Activity
The BI Application task should be generalised to not specifically focus on BI to expand this activity's definition to cover a broader information scope.
BlogMarks
del.icio.us
digg
Furl
Simpy
smarking
