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.

Current-State Strategic Component Architecture Deliverable Template

From MIKE2.0 Methodology

Jump to: navigation, search
Under review.png
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.


= Overview

The Current-State Conceptual Architecture maps in the capabilities that are available in the current environment. The conceptual architecture is at a very high-level and is presented in a form that can be easily understood by management staff with some level of technology background. comparer forfait rio sosh portabilité calcul IMC rio orange


The SAFE Architecture provide a good framework for examples of conceptual architecture. Some examples using the SAFE Architecture are shown below.

Strategic Component Capabilities

Shown below is an example component area from the SAFE Conceptual Architecture. For a complete list refer to SAFE Strategic Components.

Example of the Security Component Group. These capabilties should be mapped against the current state.

Information Security Component Group


Information Security covers the key aspects of security - access management, single sign on , encryption, etc are required to ensure end-to-end information security. Depending on the architectural scope, some areas become more critical. Data is the most critical asset to be kept secure; securing data often involves a holistic approach that covers data in databases, on the filesystem, in motion between systems and in the presentation layer.


Authentication may involve use of simple password logins or more advanced forms of authentication such as use of security tokens or biometrics. The authentication design may involve single-sign on across a federated systems environment.


Authorization ensures that the user accessing the system is who they claim to be to protect systems from incorrect usage. It also protects users by using the information in a proper fashion and telling them how it will be used.


Monitoring pro-actively and reactively looks for violations of security policies in the environment that may be indications of attempted breaches.

Session Management

Session Management provides the mechanism to maintain state in the event of loss of connectivity or a crash. The system will need to manage sessions to avoid data loss.


Encryption covers keeping information secure in the data store as well as ensuring it is secure as it flows between systems.


Security requirements differ greatly across different customer environments and industries. An integrated security architecture is becoming more critical with the proliferation of increasingly distributed architectures, web channels, and B2X trading partners.

Relationship to other components of the SAFE Architecture

The Information Security goes across the architecture and is considered to be one of the Foundation Capabilities for Infrastructure Development as well as "front end" capability in relation to information access.

Wiki Contributors
Collapse Expand Close