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

Members
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.

Technology Architecture Guiding Principles Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
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.

Guiding Principles are used to help formulate the initial architecture and governance model and provide a framework for decision making. Within MIKE2.0 they are used to:

  • Provide a clear linkage to business priorities
  • Guide the technology organization
  • Facilitate communication of our initiatives to business users
  • Help to simplify our decision-making process
  • Define initial best practices for implementation

Overview

Technology Architecture Principles

  • Define a solution framework and a vision that can be applied to evolving technologies
  • Define how technology will be implemented as a solution to meet the needs of the business

Example 1 - Technology Architecture Guiding Principles

Listed below are example Technology Architecture Guiding Principles

Technology Architecture Guiding Principles define a framework and a vision that can be applied to evolving technologies in the integration hub environment. They also define how technology will be implemented as a solution to meet the needs of the business. The Technology Architecture principles for the Integration Hub are as follows:

  • The solutions must be scalable

The architecture provides a baseline to support future business volume growth requirements. The architecture is able scale both horizontally and vertically to meet system requirements that are defined based on business volumes. Whilst scale is needed, solutions are not be “over-sized” to account for lack of planning.

  • The solution builds a strong foundation for the future

The architecture establishes the building blocks on which future capabilities can be built. Skills must exist with operations staff to manage implemented software. The architecture framework should provide capabilities that can accommodate existing solutions. Implementations should be well-defined and documented.

  • The solution is implemented through an approach that minimises complexity

The architecture should be no more complex than it needs to be to satisfy business' needs. The solution must be supportable through staff skill sets; if there are gaps in staff skill sets to support the technology these should be identified. Although it builds a framework for the future, business requirements must drive the solution definition and technology should not be implemented for technology’s sake.

  • The solution provides an approach that lets systems share common functionality for integration

The solution provides common integration and data management services across the group. Software is developed in a reusable, well-documented fashion and stored in a common asset repository.

  • The architecture minimises custom development

The architecture leverages off-the-shelf solutions when they meet core business requirements and use the core capabilities of the integration and data management products as much as possible (e.g. use of mapping functions within the ETL as opposed to custom code). As new business requirements develop the team will look for off-the-shelf solutions to meet business needs as opposed to custom development.

  • The architecture is based on common standards

The solution will define consistent standards for integration that can be applied throughout group, whereby definitions are understandable and available to all users. Standards will be defined for reusable software components, software delivery and managing information.

  • The solution provides a secure environment

Confidential data will be kept secure, both at rest and in motion, as it flows across the gateway. In scope systems are secured, at both a physical and technical level. Access to production systems is limited and traceable.

Wiki Contributors
Collapse Expand Close