From MIKE2 Methodology
Activity: Strategic Requirements for Technology Backplane Development
Objective
The Strategic Requirements for Technology Backplane Development activity defines the functional capabilities that are required for Information Development and Infrastructure Development are mapped against conceptual architecture capabilities as defined by the SAFE Architecture. The team will also use other Supporting Assets of the SAFE framework as a starting point and will gather the requirements that will let them take the architecture from the conceptual to the logical level.
Major Deliverables
- Strategic Functional Requirements for Technology Backplane Architecture
Tasks
Define Foundation Capabilities for Information Development
Objective:
In this task, the baseline capabilities will required for managing information will be determined based on requirements and strategic technology principles.
The SAFE architecture should be used as a starting point for this exercise. It should be noted that clients may have different definitions for these terms or have some additional areas covered. The team should be flexible with this model, whilst still using it as a guide. The architecture should be represented pictorially and also contain high level descriptions of all major components.
Most large-scale projects will require these Foundation Capabilities for Information Development. Foundation Capabilities should provide the first step in the gap analysis process in building the future-state from the current-state.
Input:
Output:
Define Foundation Capabilities for Infrastructure Development
Objective:
In this task, the baseline capabilities that are required for providing infrastructure and integration will be determined based on requirements and strategic technology principles. The SAFE architecture should be used as a starting point for this exercise. It should be noted that clients may have different definitions for these terms or have some additional areas covered. The team should be flexible with this model, whilst still using it as a guide. The architecture should be represented pictorially and also contain high level descriptions of all major components.
Most large-scale projects will require these Foundation Capabilities for Infrastructure Development. Foundation Capabilities should provide the first step in the gap analysis process in building the future-state from the current-state.
Input:
- Infrastructure Maturity Assessment
- Technology Guiding Principles
- Future-State Conceptual Architecture
- High Level Solution Architecture Options
- Source-to-Target Matrix
- Prioritised High-Level Information Requirements
- Prioritised Work Opportunities
Output:
Define Advanced Capabilities for Information Development
Objective:
In this task, the need for more advanced capabilities in the area of Information Management is defined. This includes both architectural implementations (e.g. reusable services) and more enabling technologies (e.g. modeling data in motion). In defining the future-state conceptual architecture, it is important to take note of the timeline when different capabilities will be deployed, as this should be represented in the final blueprint.
The SAFE Architecture should be used as a starting point for this exercise. It should be noted that clients may have different definitions for these terms or have some additional areas covered. The team should be flexible with this model, whilst still using it as a guide. The architecture should be represented pictorially and also contain high level descriptions of all major components.
Input:
Output:
Define Advanced Capabilities for Infrastructure Development
Objective:
In this task, the need for more advanced capabilities in the area of Infrastructure Management is defined. This includes both architectural implementations (e.g. reusable services) and more enabling technologies such as Services Orchestration.
The SAFE architecture should be used as a starting point for this exercise. It should be noted that clients may have different definitions for these terms or have some additional areas covered. The team should be flexible with this model, whilst still using it as a guide. The architecture should be represented pictorially and also contain high level descriptions of all major components.
Input:
Output:
Core Supporting Assets
Yellow Flags
Key Resource Requirements
BlogMarks
del.icio.us
digg
Furl
Simpy
smarking
