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.

Current-State Logical Architecture

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Content Model Relationship

Contents

Activity: Current-State Logical Architecture

Objective. The Current-State Logical Architecture activity defines the current state information management architecture at the logical architecture level. This activity involves conducting interviews and reviewing artifacts to ensure there is a properly defined current-state architecture. The activity may significant or fairly minor, depending on the quality of the current artifacts and knowledge of staff. As it is a documentation of the current-state environment that will be used for gap-analysis, it may be helpful to categorise the information environment in similar terms as the future-state, using terms like "Information Development Environment".

In many cases, the logical architecture and requirement for the current-state architecture may not be available. Teams will frequently need to "reverse-engineer" the current-state from the existing physical solution.

Major Deliverables
  • Current-State Logical Architecture
Tasks

Task: Define Current-State Business Architecture

Objective: The Business Intelligence Logical Architecture should illustrate the major capabilities of the user-facing reporting and analytical applications.


Input:

  • Current-State Conceptual Architecture Deliverable Template
  • Current-State Conceptual Architecture
  • Non-Functional Requirements for Application Development
  • Architecture diagrams
  • Functional specifications
  • Project Artifacts
  • Key Business functions


Output:

  • BI Application Development Logical Architecture Deliverable Template
  • BI Application Development Logical Architecture

Task: Define Current-State Information Development Logical Architecture

Objective: This task defines the current state information management architecture at the logical architecture level. Interviews should be conducted with technology staff members to define the current systems, noting any currently planned changes including any constraints that may exist. As it is a documentation of the current-state environment that will be used for gap-analysis, it may be helpful to categorise the information environment in similar terms as the future-state, using terms like “Information Development Environment”.

In many cases, the logical architecture and requirement for the current-state architecture may not be available. Teams will frequently need to "reverse-engineer" the current-state from the existing physical solution.


Input:

  • Project Artifacts
  • Logical and Physical Data Models
  • Information Process Models
  • Key Business functions
  • Functional specifications
  • Data Quality processes


Output:

  • Information Development Logical Architecture Deliverable Template
  • Information Development Logical Architecture

Task: Define Current-State Infrastructure Development Logical Architecture

Objective: This task defines the current state infrastructure development architecture at the logical architecture level. It includes documentation of infrastructure systems, their purpose, constraints, and diagramming the interfaces. Interviews should be conducted with technology staff members to define the current systems, noting any currently planned changes including any constraints that may exist. System interfaces are documented together with “time windows” which may be available to access the systems for data extraction. As it is a documentation of the current-state environment that will be used for gap-analysis, it may be helpful to categorise the infrastructure environment in similar terms as the future-state, using terms like “Information Development Environment”.

In many cases, the logical architecture and requirement for the current-state architecture may not be available. Teams will frequently need to "reverse-engineer" the current-state from the existing physical solution.


Input:

  • Current-State Conceptual Architecture Deliverable Template
  • Current-State Conceptual Architecture
  • Non-Functional Requirements for Infrastructure Development
  • Project Artifacts
  • Architecture diagrams
  • Process Models
  • Key Business functions
  • Interface Specifications
  • Network diagrams
  • Functional specifications


Output:

  • Infrastructure Development Logical Architecture Deliverable Template
  • Infrastructure Development Logical Architecture

Task: Assess Current-State Standards and Infrastructure Management Processes

Objective: During this task, the team will review existing standards and system management controls. If there are any disaster recovery standards or audit controls they must be incorporated into the information management infrastructure.


Input:

  • Infrastructure Development assessment
  • Documentation of the existing systems
  • Software management processes


Output:

  • Summary Report of Existing Development Standards and Processes Deliverable Template
  • Summary Report of Existing Development Standards and Processes

Task: Assess Current-State Capabilities of Supporting Tools for the SDLC

Objective: The purpose of this task is to survey existing tools to support the overall software development lifecycle. This would include:

  • Software development tools
  • Testing tools (including test automation and load testing tools)
  • Configuration management tools
  • Defect tracking tools


Input:

  • Project artifacts
  • Development tools
  • Configuration management strategy
  • Defect tracking approach
  • Testing tools


Output:

  • Summary Report of Existing Tool to Support the SDLC Deliverable Template
  • Summary Report of Existing Tools to Support the SDLC

Role: Solution Architect

Role: Technical Architect

Role: Information Architect

Role: Business Architect

Yellow Flags

  • Artefacts are poorly documented or documentation is very inconsistent with software in production
  • Team is forced to spend very large amounts of time doing current-state documentation
  • Current-state documentation needs to be re-captured and is being done in a fashion that could easily get out of date once again
Wiki Contributors
Collapse Expand Close

View more contributors