From MIKE2 Methodology
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
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:
- Project Artifacts such as:
- Architecture diagrams
- Key Business functions
- Functional specifications
Output:
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 such as:
- Logical and Physical Data Models
- Information Process Models
- Key Business functions
- Functional specifications
- Data Quality processes
Output:
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:
Project Artifacts such as:
- Architecture diagrams
- Process Models
- Key Business functions
- Interface Specifications
- Network diagrams
- Functional specifications
Output:
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:
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 artefacts documenting:
- Development tools
- Configuration management strategy
- Defect tracking approach
- Testing tools
Output:
Core Supporting Assets
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
Key Resource Requirements
BlogMarks
del.icio.us
digg
Furl
Simpy
smarking
