Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
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.

Phase 4 - Design Increment

From MIKE2.0 Methodology

Jump to: navigation, search

Phase 4 finalises the design of the overall solution by building on the architecture, modelling and data re-engineering work from the Foundation Activities. It also "hardens" the design in areas where prototyping and initial design has occurred.


User Support & Operational Procedures DesignBusiness Intelligence DesignInfrastructure Management Process DesignInformation Security DesignData Integration Logical DesignData Integration Physical DesignUser Collaboration DesignUser Interface DesignServices Oriented Architecture DesignTest Design
The overall set of activities for Phase 4About this image

At the completion of Phase 4, the functional and technical requirements for all software components will be complete for infrastructure management design, Business Intelligence applications and integration components. The test design will also be complete, allowing the team to conduct the final implementation work that will occur in the next phase.

In many cases the Foundation Activities will be running in parallel with the design activities in Phase 4. In the MIKE2.0 approach, many design activities tend to follow a more parallel path than on traditional software delivery engagements.


Major Deliverables

  • User Support and Operational Procedure Guides
  • BI Application Detailed Design
  • Information Security Design
  • Infrastructure Management Procedures Design (backup, recovery, archiving, security, operations, monitoring)
  • Data Integration Logical and Physical Design
  • SOA Design (if required this would be an aspect of the ETL design)
  • Test Requirements
  • Design of all test cases
Wiki Contributors
Collapse Expand Close