Project Management

Systems Component Mapping

last edited by: Kwiyuh Michael Wepngong on Mar 2, 2024 11:47 AM login/register to edit this page

1 Applications
2 Procedures
3 Instructions

This technique is used to locate, verify, document, and cross-reference vital, current physical system information. Systems Component Mapping is a first step to assess the current level of systems support, to determine what can be salvaged from existing systems to support reengineering opportunities, to uncover existing business rules, and to build a transition plan. When combined with surveys, questionnaires, workshops, interviews, traditional current system analysis, and system redevelopment methods, this technique provides a powerful result to enable coordinated, managed technical change. (See Structured Interviews, Workshops, Questionnaires and Surveys, and Current System Analysis.)


  • To provide a springboard for conducting a current systems analysis of systems supporting the set of business activities being reengineered.
  • To provide an inventory of existing applications and databases to be included in a current technical assessment.
  • To initiate a study of system redevelopment options for transitioning to a new technical environment.
  • To determine what is being used and what is not being used to facilitate more effective analysis and transition planning.


  1. Confirm scope of assessment or analysis project.
  2. Confirm project objectives, time considerations, and resources available.
  3. Identify physical systems and databases to be included in the assessment/analysis.
  4. Map systems to value stream or process.
  5. Determine all possible sources of information.
  6. Locate source material.
  7. Verify source material content.
  8. Document required information and produce/update systems inventory.
  9. Analyze information to determine what is being used and what is not being used.
  10. Produce a cross-reference of all information, including a physically-based ERD.
  11. Apply next set of appropriate techniques to complete the analysis.


Enterprise change projects can have a wide set of objectives. For example, during an initial assessment of the degree of change required for an enterprise to meet a vision, it is often important to conduct an assessment of current technology capability. During a business reengineering project, it is important not only to know existing business rules, but also to understand the alternative technical implementation options available in order to achieve the opportunities. Prior to applying this technique, confirm the type of enterprise change project, the objectives, and the scope of the analysis. Map the systems to the value stream.

Identify the resources required to conduct the analysis (this might be a rough first guess), and determine the level of resources available. Develop a task plan, and train/orient the technical analysis team (see Project Management for project planning and estimating, and see an appropriate reference listed below). Using the expertise on the team (or other technical resources available as subject matter experts—SMEs), identify the systems and databases to be analyzed.

Locate all system component information from the sources identified previously. Source material typically includes:

  • copy books
  • JCL files
  • data dictionaries
  • system descriptions and related documentation
  • code
Adjust task plans and schedules based on the volume of information collected. Verify all sources, and verify the content (e.g., completeness, consistency, currency). Develop a consolidated set of library information, and document the key variables appropriate to the assessment. Supplement the source material information with questionnaires and/or interviews with knowledgeable technical resources. Conduct a team working session to review the information, determine information/inventory gaps, and brainstorm possible options for gathering the data. Apply automated tools, if available, to support and facilitate the effort. These tools can be extremely useful to perform cross-reference checks on things that are used and not used.

Complete the cross-referencing and compile the final set of materials to be used for subsequent analysis.

last edited by: Kwiyuh Michael Wepngong on Mar 2, 2024 11:47 AM login/register to edit this page

Comments (1)

Login/join to subscribe

"One man alone can be pretty dumb sometimes, but for real bona fide stupidity there ain't nothing can beat teamwork."

- Mark Twain