|
Wiki Home
Members
To join, please contact us. Improve MIKE 2.0
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.
|
Strategic Requirements for Technology Backplane DevelopmentFrom MIKE2.0 Methodology -> You are here: Open Methodology Compliance > Category:Enterprise Content Management Offering Group > Data Profiling > Category:Template > Strategic Requirements for Technology Backplane Development
Activity: Strategic Requirements for Technology Backplane DevelopmentObjectiveThe 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
TasksDefine Foundation Capabilities for Information DevelopmentObjective: 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.
Define Foundation Capabilities for Infrastructure DevelopmentObjective: 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:
Define Advanced Capabilities for Information DevelopmentObjective: 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:
Define Advanced Capabilities for Infrastructure DevelopmentObjective: 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.
Core Supporting Assets
Yellow Flags
Key Resource Requirements |
Wiki asset search
Toolbox
Views
Wiki Contributors
|

