Process Hierarchy/Dependency Analysis

Objectives

Process hierarchy analysis and process dependency analysis are integrated into a single task. This task continues efforts begun in the Inventory/Analysis function hierarchy and function dependency analysis tasks. The purpose is to further excavate processes within the existing system(s) as documentation of current capability and as input to top-down redesign efforts. Specific objectives include:

· Outline current process hierarchies in order to re-document current functional breakdown

· Define links between process hierarchy analysis model(s) and current physical source modules

· Based on the scenario, develop an integrated process hierarchy encompassing one or more bottom-up hierarchies

· Based on the scenario, assess similarities and differences between bottom-up derived hierarchies and top-down derived hierarchies

· Re-document current process flows and dependencies

· Expand processes defined in process hierarchy analysis steps into bottom-up process dependency diagrams

· Assess/reconcile differences between various bottom-up process dependency diagrams

· Assess/reconcile differences between bottom-up and top-down process dependency diagrams

Entrance Criteria

The entrance criteria for the process hierarchy/dependency analysis task are listed below.

· Completion of the function hierarchy analysis of the functional assessment

· Completion of the function dependency analysis of the functional assessment

· Specific scenario to drive either a bottom-up and/or top-down functional integration effort

· Completion of code stabilization & re-aggregation tasks based on the scenario driving this effort

The following is required if goal includes top-down/bottom-up model comparison or integration based on redevelopment scenario.

· Completion of top-down process hierarchy and process dependency diagrams

The following is desirable, especially if no functional SME is available.

· Completion of the general system architecture assessment system level and system/sub-system data flow diagrams

Optional - based on availability:

· Population of LTM repository model as completed in entrance criteria tasks

Roles/Skills

The personnel and skill requirements necessary to meet the process hierarchy/dependency analysis task are identified below.

· Redevelopment Expert

- Ability to determine best mix of top-down/bottom-up analysis and how to integrate these techniques

- Expertise in capturing, building, merging bottom-up models & integrating models with top-down views

· Function Modeling Expert

- Expertise in building and merging bottom-up function dependency/hierarchy models related bottom-up and/or top-down models

· Current Systems Expert

- Knowledge of existing system source environment

- Knowledge of the functionality of current system(s)

· Target System Functional Expert

- Knowledge of target functional requirements and access to user as required

· User Requirements Analyst

- Ability to provide input to strategic model

· Repository Administrator

- Ability to access and update LTM repository

Input Requirements

The system components and related inputs required to initiate and complete the process hierarchy/dependency analysis task are listed below.

· Current function hierarchy(ies) diagrams developed in function hierarchy analysis or revised version created during Positioning re-aggregation task

· Completed/updated Functional mapping Form 004 for each system entering this task

· Completed/updated Functional assessment Form 005 for each system entering this task

· Blank versions of Transformation Process Mapping Form 031 - one for each system hierarchy being derived

· Existing system components - particularly source code

· Top-down function hierarchy (if required by the scenario driving this process)

· Current function dependency diagram and narrative assessing current functional flows

· System flow (DFD) diagrams created during the general system architecture assessment for each system being modeled - if available

· System/sub-system interface flow (DFD) diagrams created during the general system architecture assessment for all systems being modeled - if available

Optional - based on results of the Inventory/Analysis function dependency analysis.

· Narrative gap analysis between current and target function dependency diagrams

Optional - where available to support transition planning for systems that contain functions being replaced by this effort but also for systems having functions that must stay intact under current architecture.

· Business Area/Business Function Matrix Form 042, (Enterprise Redevelopment Planning stage) defining major functions that cross business boundaries

Optional - where available:

· Legacy transition meta-model (LTM) populated with system components and relationships from prior tasks

Tool/Technology Support

Technologies supporting the process hierarchy/dependency analysis task include I-CASE modeling, spreadsheet and open system repository tools. These tools are used to represent information as required by this task.

I-CASE Modeling Tools

Tool support for this area is currently limited to the I-CASE analysis workstations. These tools provide a mechanism for specifying current process hierarchies and dependencies and integrating these models with target application hierarchies. Specifically required tools include:

· Bottom-up/top-down process hierarchy diagramming tool

· Bottom-up/top-down process dependency diagramming tool

Spreadsheet

This tool is used to record metric results for this task.

Open systems repository

A repository provides an important, yet optional, capability to link business areas, systems and components using the legacy transition meta-model. In this task, repository is used to trace the flow of current processes as input to bottom-up process hierarchy modeling effort.

Task Steps

The process hierarchy/dependency analysis task is comprised of the following task steps:

Derive Bottom-Up Process Hierarchy Model
Redesign Bottom-Up Process Hierarchy(ies)
Merge Bottom-Up Process Hierarchies
Integrate Bottom-Up & Top-Down Hierarchies
Finalize Target Process Hierarchy
Develop Bottom-Up Process Dependencies
Merge Bottom-Up Process Dependencies
Merge Current & Target Process Dependency Models
Finalize Target Process Dependency Model