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 Advanced Capabilities for Infrastructure Development task defines the need for more advanced capabilities in the area of Infrastructure Management. This includes both architectural implementations (e.g. reusable services) and more enabling technologies such as Services Orchestration.
Most large-scale projects will require these Foundation Capabilities for Infrastructure Development.
Examples
Mapping Business Requirements to from Technology Requirements
The goal should not to be to provide an exhaustive list and spend too much time on analysis, but to ensure that the major business requirements map to the functional capabilities.
Foundation Capabilities for Information Development are separated from advanced capabilities MIKE2.0 to ensure there is coverage of the basics.
Requirements Mapping Model
A simple requirements mapping model can be defined as shown to the right although use of a tools-based approach is generally better than the approach shown in this model. This is particularly important to accommodate change control and many-to-many relationship for requirements mapping.
| Factors
| Business Requirement
| Technology Capability
| Evaluation Against Requirement
|
|
|
|
|
|
|
|
|
|
|