System Transformation

Home    Site Map
About Tactical Strategy Group

Organizational Transformation    IT Architecture Transformation
Contingency Planning / Risk Management    Transformation Solutions

The Legacy Transition Meta-model or LTM is an entity relationship model representing current and target system components that can be depicted in a repository. LTM defines attributes and relationships for each entity or object in the repository model. Physical object types include job, step, proc, source module, copy member, screen, report, record and other implementation specific components. Logical object types include entity, function, event, process/business rule and various other models and diagrams. External objects include change request, location and other user added types as required. Relationship examples include step executes load module, process/business rule maps to procedure and record maps to entity.

The LTM model allows organizations, based on various factors, to customize the baseline by adding or eliminating object types as needed. Physical object attributes vary based on implementation factors, while logical object types vary depending on development paradigm. It is unlikely, for example, that a given project would use all of the Information Engineering and object / event representations within LTM. Customization can also occur if a enterprise view is used to store high level meta-data collected during Enterprise Redevelopment Planning stage of Ulrich-SRM. This enterprise model can then feed business area related information into project specific models.

Legacy Transition Meta-model or LTM supports many tasks within Ulrich-SRM. While no Ulrich-SRM task requires the LTM, experience has shown that large scale transition from legacy to strategic architectures requiring a paradigm shift requires a sophisticated vehicle to:

· Manage vast amounts of meta-data collected across many tasks

· Establish an audit trail to track and verify step related activities

· Track legacy to target relationships as they evolve

· Track redundant data and processes by having objects map to themselves

· Flag items for deactivation or reuse in target or legacy systems

· Establish a comprehensive vehicle for integrating disparate activities

across a wide range of tools, techniques or platforms

LTM was developed in cooperation with certain Ulrich-SRM compliant vendors, repository and redevelopment experts, and user organizations. LTM maps to underlying models used in environmental and system wide interactive analysis tools. This simplifies population and other interface requirements between these tools and repositories. Because the LTM represents a superset of physical, logical and external component objects, development platforms and CASE tool cannot serve as transition model repositories.

LTM is best implemented under an open repository where organizations can add or remove object types, relationships and attributes as required by the environment or project. Ulrich-SRM defines how to load, update and utilize LTM across all four stages. Reciprocal relationships are defined where applicable. Again, while not required, LTM does turn difficult or impossible management assignments into projects that will succeed using a defined audit trail for tracking activity and results. Certain scenarios, such as the client/server migration scenarios, century date change and any large scale migration efforts, strongly encourage the use of LTM.

One requirement for implementing LTM in a repository is to populate and refresh the model. Some repository vendors offer these facilities. Others link to commercial tools. Organizations should consider certain features in a repository population facility. Do parsers scan all required physical components in a given environment? Do parsers run on the host or workstation? Do the loaders recognize and update only modified components to avoid a complete reload when updating is required? Does the population vendor have an agreement with the repository vendor to provide a "robust" link? Ulrich-SRM tool guidelines will continue to evolve to reflect repository and third party population tool support.

It is important to note that not all objects or relationships are used within Ulrich-SRM. Conversely, a relationship or attribute may be established within Ulrich-SRM that may not be defined in the baseline model in the next section. Because each project will have to adjust the LTM for project specific requirements, there is a degree of leeway in how the LTM is used. Analysts should note this as they plan a given project.

For example, a technical assessment, applied either as a first phase of a large assessment effort or as a standalone analysis project, would only utilize physical objects within the LTM. Additional object types could be added in subsequent project phases. Similarly, if target architecture mapping is not required, target entity and function relationships would not be created. Furthermore, modeling paradigms that do not apply to a given environment should be eliminated completely. For example, analysts would exclude Event and Object from the LTM if an Information Engineering paradigm was being used. The bottom line is that analysts should use good judgment in applying the LTM to various redevelopment efforts.

Once the LTM is initially populated, an infrastructure must be created to maintain its relevancy. This includes deploying a customized repository users and administrator guide and establishing roles and responsibilities to manage the evolution of the LTM. The LTM, over time, becomes outdated if it is not refreshed with changes in the physical, logical and business environment. Guidelines to establish and maintain this infrastructure can be found in the Create Infrastructure Management Procedures step.

Defines an attribute within an entity relationship or logical data model.

ATTRIBUTE_DESCRIBES_ENTITY ATTRIBUTE ENTITY

ATTRIBUTE_DESCRIBES_RELATIONSHIP ATTRIBUTE RELATIONSHIP

ATTRIBUTE_MAPS_TO_ATTRIBUTE ATTRIBUTE ATTRIBUTE

ATTRIBUTE_MAPS_TO_ELEMENT ATTRIBUTE ELEMENT

SUBJECT_AREA_CONTAINS_ATTRIBUTE SUBJECT_AREA ATTRIBUTE

NAME

DESCRIPTION

CURRENT_TARGET_INDICATOR

TYPE (ERD or Logical Data Model)

Subject Area / Entity Type Analysis

Logical Data Analysis

Defines a cross section of the organization that is comprised of one or more information systems.

ER_DIAGRAM_REPRESENTS_BUSINESS_AREA ER_DIAGRAM BUSINESS_AREA

LOCATION_IS_LOC_FOR_BUSINESS_AREA LOCATION BUSINESS_AREA

OBJECT_DIAG_REPRESENTS_BUS_AREA OBJECT_DIAGRAM BUSINESS_AREA

SYSTEM_SUPPORTS_BUSINESS_AREA SYSTEM BUSINESS_AREA

NAME

DESCRIPTION

BUSINESS_OWNER

Technical Architecture Assessment

These are manually entered requests to upgrade the system. Relation to system is implied through related object relationships. If used, relationships must be maintained as the request backlog changes.

CHANGE_REQUEST_AFFECTS_COPYBOOK CHANGE_REQUEST COPYBOOK

CHANGE_REQUEST_AFFECTS_ELEMENT CHANGE_REQUEST ELEMENT

CHANGE_REQUEST_AFFECTS_FILE CHANGE_REQUEST FILE

CHANGE_REQUEST_AFFECTS_JOB CHANGE_REQUEST JOB

CHANGE_REQUEST_AFFECTS_PROGRAM CHANGE_REQUEST SOURCE_PROGRAM

CHANGE_REQUEST_AFFECTS_PROCESS CHANGE_REQUEST PROCESS_BUS/RULE

CHANGE_REQUEST_AFFECTS_RECORD CHANGE_REQUEST RECORD

NAME

DESCRIPTION

DATE_OPENED

CR_EFFORT_ESTIMATED

RESPONSIBLE_NAME

SUBMITTED_BY_NAME

SUBMITTED_BY_USER_ID

RESPONSIBLE_USER_ID

CR_STATUS

CR_TYPE

RESPONSIBLE_BUSINESS_AREA

SUBMITTED_BY_BUSINESS_AREA

SUBMITTED_BY_TELEPHONE

RESPONSIBLE_TELEPHONE

CR_PRIORITY

DATE_SUBMITTED

CR_ACTUAL_EFFORT

DATE_CLOSED

User Backlog Requirements Analysis

Interim Support Planning

Constant defines a literal that may be embedded in a program, on a form or other system object. Users may select to rename this as a LITERAL depending on in-house terminology.

CONSTANT_MAPS_TO_ELEMENT CONSTANT ELEMENT

FORM_CONTAINS_CONSTANT FORM CONSTANT

PROGRAM_USES_CONSTANT SOURCE_PROGRAM CONSTANT

NAME

DESCRIPTION

SCAN_DATE

SCAN_ID

CONSTANT_VALUE

CONSTANT_LENGTH

CONSTANT_TYPE (numeric, non-numeric, other)

Data Definition Analysis

Literal Externalization

Defines reusable component accessible through features in compiler such as the COBOL COPY library and related reference. Is preferable to hard coded, non-reusable definitions - particularly for data records.

COPYBOOK_DEFINES_RECORD COPYBOOK RECORD

COPYBOOK_INCLUDES_COPYBOOK COPYBOOK COPYBOOK

COPYBOOK_IS_USED_BY_PROGRAM COPYBOOK SOURCE_PROGRAM

COPYBOOK_IS_CONTAINED_IN_LIBRARY COPYBOOK LIBRARY

CHANGE_REQUEST_AFFECTS_COPYBOOK CHANGE_REQUEST COPYBOOK

PROC_INCLUDES_COPYBOOK PROC COPYBOOK

RECORD_INCLUDES_COPYBOOK RECORD COPYBOOK

DESCRIPTION

NAME

PROGRAMMING_LANGUAGE

SCAN_DATE

SCAN_ID

Data Definition Analysis

Data Name Rationalization

Field & Record Size Expansion

Defines physical and logical data base structures including IMS, DB/2 and other physical objects required to define physical DBMS. If this is an IMS database, this object represents a DBD. A relationship to a segment (PSB) object serves as a pointer to a logical view of this physical definition.

DATABASE_DEFINITION_DEFINES_SEGMENT DATABASE_DEF SEGMENT

DATABASE_DEFINITION_DEFINES_FILE DATABASE_DEF FILE

DATABASE_DEF_MAPS_TO_DATABASE_DEF DATABASE_DEF DATABASE_DEF

DATABASE_DEF_IS_CONTAINED_IN_LIBRARY DATABASE_DEF LIBRARY

NAME

MEMBER_NAME

DATABASE_TYPE

DESCRIPTION

LENGTH

SCAN_DATE

SCAN_ID

TYPE (Physical / Logical)

Environmental Analysis

Data Access Layer Assessment

Field & Record Size Expansion

Represents existence of a data flow diagram (DFD) that supports logical documentation of a system or subsystem. Typically, the DFD represents high level data store flow and usage across and between systems and subsystems.

DFD_DEFINES_SUBSYSTEM DFD SUBSYSTEM

DFD_DEFINES_SYSTEM DFD SYSTEM

DFD_MAPS_TO_DFD DFD DFD

DFD_REFERENCES_FILE DFD FILE

DESCRIPTION

CURRENT_TARGET_INDICATOR

DFD_TYPE

NAME

MEMBER_NAME

DATE_CREATED

LAST_UPDATED

Business Architecture Assessment

General Systems Architecture Assessment

Defines physical element within current application. Initial analysis will lead to redundantly defined definitions being repeated under differing names. These are represented using an element points to element relationship. Rationalization would reduce number of element instances. Records or other group definitions are considered special cases of an element. Users may choose to refine this relationship, based on in-house repository standards. Automated population, given that this level of detail is applied, is required for this LTM object.

ELEMENT_CONTAINS_ELEMENT ELEMENT ELEMENT

ELEMENT_MAPS_TO_ELEMENT ELEMENT ELEMENT

CHANGE_REQUEST_AFFECTS_ELEMENT CHANGE_REQUEST ELEMENT

CONSTANT_MAPS_TO_ELEMENT CONSTANT ELEMENT

ATTRIBUTE_MAPS_TO_ELEMENT ATTRIBUTE ELEMENT

FIELD_REPRESENTS_ELEMENT FIELD ELEMENT

FILE_CONTAINS_ELEMENT FILE ELEMENT

RECORD_HAS_KEY_ELEMENT RECORD ELEMENT

RECORD_USES_REC_TYPE_ELEMENT RECORD ELEMENT

RECORD_REPRESENTS_ELEMENT RECORD ELEMENT

SEGMENT_CONTAINS_DATA_ELEMENT SEGMENT ELEMENT

PROGRAM_DEFINES_ELEMENT SOURCE_PROGRAM ELEMENT

PROGRAM_NEEDS_PARAMETER_ELEMENT SOURCE_PROGRAM ELEMENT

TABLE_CONTAINS_ELEMENT TABLE ELEMENT

TABLE_DEFINES_ELEMENT TABLE ELEMENT

EXTERNAL_NAME

DESCRIPTION

CURRENT_TARGET_INDICATOR

SOURCE_TYPE

SOURCE_NAME

SOURCE_PICTURE

SCAN_DATE

SCAN_ID

RESTRICTION

PHYSICAL_LENGTH

LOGICAL_LENGTH

GROUP_IMPLEMENTATION

VALUES

MAXIMUM_VALUES

NUMBER_OF_VALUES

INDEX

INTERNAL_NAMES

COBOL_DEPENDING

SOURCE_CONDITIONAL

ALIGNED

ASSEMBLER_NAME

CONSTRUCT

OCCURS

DEFAULT_VALUE

ROUNDED

MINIMUM_VALUES

BOOLEAN_OPERATORS

BINARY_DATA

DATE_FORMAT

Data Definition Analysis

Data Name Rationalization

Field & Record Size Expansion

Entity represents an entity, as defined in an entity relationship diagram or logical data model. This may have been extracted from a current application or created as a top down component of a target model.

ENTITY_MAPS_TO_RECORD ENTITY RECORD

ENTITY_MAPS_TO_ENTITY ENTITY ENTITY

ENTITY_MAPS_TO_OBJECT ENTITY OBJECT

ATTRIBUTE_DESCRIBES_ENTITY ATTRIBUTE ENTITY

ER_DIAGRAM_CONTAINS_ENTITY ER_DIAGRAM ENTITY

FUNCTION_USES_ENTITY FUNCTION ENTITY

PROCESS_USES_ENTITY PROCESS/BUS_RULE ENTITY

RELATIONSHIP_FROM_ENTITY RELATIONSHIP ENTITY

RELATIONSHIP_TO_ENTITY RELATIONSHIP ENTITY

SUBJECT_AREA_CONTAINS_ENTITY SUBJECT_AREA ENTITY

NAME

DESCRIPTION

TYPE

CURRENT_TARGET_INDICATOR

Subject Area / Entity Type Analysis

Logical Data Analysis

This object defines a collection of entities and relationships, as defined in an entity relationship model.

ER_DIAGRAM_CONTAINS_ENTITY ER_DIAGRAM ENTITY

ER_DIAGRAM_MAPS_TO_ER_DIAGRAM ER_DIAGRAM ER_DIAGRAM

ER_DIAGRAM_REPRESENTS_SYSTEM ER_DIAGRAM SYSTEM

ER_DIAGRAM_REPRESENTS_BUSINESS_AREA ER_DIAGRAM BUSINESS_AREA

DESCRIPTION

TYPE

NAME

MEMBER_NAME

CURRENT_TARGET_INDICATOR

DATE_CREATED

LAST_UPDATED

Subject Area / Entity Type Analysis

An event is a happening in the business that changes the state of an object through invocation of a business rule operation. Events are linked through an event diagram which could be recreated using event precedes event relationship.

EVENT_DIAG_ DEFINES_EVENT EVENT_DIAG EVENT

EVENT_TRIGGERS_BUS_RULE EVENT PROCESS/BUS_RULE

EVENT_ PRECEDES_EVENT EVENT EVENT

EVENT_IMPACTS_OBJECT_STATE EVENT OBJECT

FORM_DETERMINES_EVENT FORM EVENT

JOB_INITIATES_EVENT JOB EVENT

JOBSTEP_INITIATES_EVENT JOBSTEP EVENT

DESCRIPTION

TYPE

NAME

Event Derivation Analysis

Event diagram is the physical diagram that connects a series of events defining an event driven system.

EVENT_DIAG_ DEFINES_EVENT EVENT_DIAG EVENT

DESCRIPTION

DIAGRAM_ID

TYPE

NAME

MEMBER_NAME

DATE_CREATED

LAST_UPDATED

Event Derivation Analysis

A field represents a user view of an element on a screen or report (FORM). It is, typically, physically defined in an on-line map macro. Normally, only a subset of the attributes apply.

FIELD_REPRESENTS_ELEMENT FIELD ELEMENT

FORM_CONTAINS_FIELD FORM FIELD

NAME

DESCRIPTION

CURRENT_TARGET_INDICATOR

IMAGE_IN_LAYOUT

NUMERIC_LOCK

TEMPLATE_LOCK

COLUMN

BLINKING

COLOR

INVERSE

JUSTIFY

UNDERLINE

ROW

TABLE_DESCRIPTION

PROTECTED

MUST_ENTER

ALIAS

MUST_FILL

DYNAMIC_ATTRIBUTES

DETECTABILITY

PROCESS_MODE

HIDDEN

BOLD

LENGTH

SCAN_DATE

SCAN_ID

Presentation Layer Assessment

Presentation Analysis

Field & Record Size Expansion

File represents the data definition name for a physical data set within a system. A file may interface directly with programs or may be the underlying file structure for a data base.

FILE_CONTAINS_ELEMENT FILE ELEMENT

FILE_MAPS_TO_FILE FILE FILE

FILE_IS_CONTAINED_IN_LIBRARY FILE LIBRARY

CHANGE_REQUEST_AFFECTS_FILE CHANGE_REQUEST FILE

DATABASE_DEFINITION_DEFINES_FILE DATABASE_DEF FILE

DFD_REFERENCES_FILE DFD FILE

RECORD_DEFINES_FILE RECORD FILE

PROGRAM_USES_FILE SOURCE_PROGRAM FILE

SYSTEM_USES_FILE SYSTEM FILE

BUSINESS_NAME

MEMBER_NAME

DESCRIPTION

TYPE (permanent / temporary)

PERCENT_FREE

FILE_USAGE

SEGMENT_SIZE

LOCK_SIZE

VSAM_TYPE

GENERATION_DATASET

RECORD_FORMAT

TARGET_NAME

NUMBER_OF_ORG_BLOCKS

MAXIMUM_RECORD_LENGTH

MINIMUM_RECORD_LENGTH

LONG_DESCRIPTION

MOD_DATE

DB2_BUFFER_POOL

COMPRESSED

PARTITION

ERASE

BLOCK_SIZE

MIRROR

MOD_BY_ID

SCAN_DATE

SCAN_ID

Data Architecture Assessment

Environmental Analysis

Data Access Layer Assessment

Field & Record Size Expansion

Physical Data Upgrade

Form can represent an on-line screen or a report. This includes GUI definitions, as well. If a physical screen map is defined outside an actual program, this should be the source of this object. A user may choose to define separate REPORT and SCREEN objects in place of the FORM object in a customized LTM model.

FORM_CONTAINS_CONSTANT FORM CONSTANT

FORM_CONTAINS_FIELD FORM FIELD

FORM_DETERMINES_EVENT FORM EVENT

FORM_IS_INPUT_TO_SOURCE_PROGRAM FORM SOURCE_PROGRAM

FORM_IS_OUTPUT_FROM_SOURCE_PROGRAM FORM SOURCE_PROGRAM

FORM_DEF_CONTAINED_IN_LIBRARY FORM LIBRARY

NAME

DESCRIPTION

CURRENT_TARGET_INDICATOR

MOD_DATE

USER_INTERFACE_TYPE

LAYOUT_FORMAT

MEMBER_NAME

MULTI_PAGE

GENERATION_DATE

FORM_TYPE (BMS, MFS, REPORT, etc.)

ENVIRONMENT_DRIVER

SCAN_DATE

SCAN_ID

Presentation Layer Assessment

Presentation Analysis

A function may be interpreted as a planning level entity used in Information Engineering methodology (IE). Alternate development methods may define a function slightly differently.

FUNCTION_MAPS_TO_FUNCTION FUNCTION FUNCTION

FUNCTION_MAPS_TO_SOURCE_PROGRAM FUNCTION SOURCE_PROGRAM

FUNCTION_PRECEDES_FUNCTION FUNCTION FUNCTION

FUNCTION_USES_ENTITY FUNCTION ENTITY

FDD_CONTAINS_FUNCTION FDD FUNCTION

FHD_CONTAINS_FUNCTION FHD FUNCTION

DESCRIPTION

CURRENT_TARGET_INDICATOR

NAME

TYPE (IE based / other methodology)

Business Architecture Assessment

Function Hierarchy Analysis

Business Area / Entity Type Analysis

FDD represent the sequential relationships among many functions within an IE development environment.

FDD_CONTAINS_FUNCTION FDD FUNCTION

FDD_IS_PART_OF_SYSTEM FDD SYSTEM

FDD_DECOMPOSES_INTO_PDD FDD PDD

FDD_IS_PART_OF_SUBSYSTEM FDD SUBSYSTEM

DESCRIPTION

NAME

DATE_CREATED

LAST_UPDATED

Function Dependency Analysis

FHD represents the hierarchical relationships among many functions within an IE development environment.

FHD_CONTAINS_FUNCTION FHD FUNCTION

FHD_IS_PART_OF_SYSTEM FHD SYSTEM

FHD_DECOMPOSES_INTO_PHD FHD PHD

FHD_IS_PART_OF_SUBSYSTEM FHD SUBSYSTEM

FHD_MAPS_TO_FHD FHD FHD

DESCRIPTION

TYPE

CURRENT_TARGET_INDICATOR

NAME

DATE_CREATED

LAST_UPDATED

Function Hierarchy Analysis

Business Area / Entity Type Analysis

This is a special case situation of a Copy and is used as a means of reusing code within library management systems.

INCLUDE_DEFINES_RECORD INCLUDE RECORD

INCLUDE_IS_CONTAINED_IN_LIBRARY INCLUDE LIBRARY

INCLUDE_IS_INCLUDED_IN_SOURCE_PROGRAM INCLUDE SOURCE_PROGRAM

DESCRIPTION

MEMBER_NAME

PROGRAMMING_LANGUAGE

SCAN_DATE

SCAN_ID

LIBRARY_TYPE

Data Definition Analysis

Data Name Rationalization

Field & Record Size Expansion

A JOB defines a group of execution steps within a batch system and may define IBM MVS Job streams or other types of environmental execution control language run streams.

JOB_USES_PROC JOB PROC

JOB_CONTAINS_JOBSTEP JOB JOBSTEP

JOB_IS_CONTAINED_IN_LIBRARY JOB LIBRARY

JOB_IS_PART_OF_SUBSYSTEM JOB SUBSYSTEM

JOB_IS_PART_OF_SYSTEM JOB SYSTEM

JOB_PRECEDES_JOB JOB JOB

JOB_INITIATES_EVENT JOB EVENT

CHANGE_REQUEST_AFFECTS_JOB CHANGE_REQUEST JOB

PROC_STARTS_JOB PROC JOB

DESCRIPTION

SCAN_DATE

TARGET_NAME

SCAN_ID

Environmental Analysis

This delineates steps within a job stream and is a key indicator of the sequence of batch system processes.

JOBSTEP_EXECUTES_LOAD_MODULE JOBSTEP LOAD_MODULE

JOBSTEP_PRECEDES_JOBSTEP JOBSTEP JOBSTEP

JOBSTEP_INITIATES_EVENT JOBSTEP EVENT

JOB_CONTAINS_JOBSTEP JOB JOBSTEP

PROC_CONTAINS_JOBSTEP PROC JOBSTEP

DESCRIPTION

SCAN_DATE

SCAN_ID

TARGET_NAME

Environmental Analysis

Library defines the cataloged name of a physical system component. It is the key link between various physical objects and location. If a physical, catalogued object is being used within the LTM and library applies, link library with that object using applicable relationship.

LOCATION_IS_LOCATION_FOR_LIBRARY LOCATION LIBRARY

LIBRARY_USES_LIBRARY LIBRARY LIBRARY

COPYBOOK_IS_CONTAINED_IN_LIBRARY COPYBOOK LIBRARY

DATABASE_DEF_IS_CONTAINED_IN_LIBRARY DATABASE_DEF LIBRARY

FILE_IS_CONTAINED_IN_LIBRARY FILE LIBRARY

FORM_DEF_CONTAINED_IN_LIBRARY FORM LIBRARY

INCLUDE_IS_CONTAINED_IN_LIBRARY INCLUDE LIBRARY

JOB_IS_CONTAINED_IN_LIBRARY JOB LIBRARY

LOAD_MODULE_IS_CONTAINED_IN_LIBRARY LOAD_MODULE LIBRARY

MACRO_IS_CONTAINED_IN_LIBRARY MACRO LIBRARY

CONTROL_TBL_FOUND_IN_LIBRARY ONLINE_CONTROL_TABLE LIBRARY

PROC_IS_CONTAINED_IN_LIBRARY PROC LIBRARY

SEGMENT_DEF_CONTAINED_IN_LIBRARY SEGMENT LIBRARY

PROGRAM_IS_CONTAINED_IN_LIBRARY SOURCE_PROGRAM LIBRARY

DESCRIPTION

TARGET_NAME

ACCESS_RIGHTS

GENERATION_DATE

VOLUME_ID

TARGET_NAME

CATALOG

MOD_DATE

ENVIRONMENT

MOD_BY_ID

SCAN_DATE

SCAN_ID

Environmental Analysis

Load module is the executable program and is typically comprised of one to many source modules.

LOAD_MODULE_CONTAINS_SOURCE_MODULE LOAD_MODULE SOURCE_PROGRAM

LOAD_MODULE_IS_CONTAINED_IN_LIBRARY LOAD_MODULE LIBRARY

JOBSTEP_EXECUTES_LOAD_MODULE JOBSTEP LOAD_MODULE

CONTROL_TBL_EXECS_LOAD_MOD ONLINE_CONTROL_TABLE LOAD_MODULE

PROC_EXECUTES_LOAD_MODULE PROC LOAD_MODULE

DESCRIPTION

EXECUTION_ENVIRONMENT

PHYSICAL_TRANSACTION_ID

LINK_JCL_MEMBER_NAME

MULTI_ENTRY_POINT_NAME

RETURN_STATUS

GENERATION_DATE

PHYSICAL_TRANSACTION_NAME

EXE_ENTRY_POINT_NAME

DYNAMIC_LINK

MEMBER_NAME

SCAN_DATE

SCAN_ID

Environmental Analysis

Location implies physical location. This is particularly applicable for organizations with multiple computer sites or distributed environments. Objects are linked to location via library objects.

LOCATION_IS_LOCATION_FOR_LIBRARY LOCATION LIBRARY

LOCATION_IS_LOCATION_FOR_SYSTEM LOCATION SYSTEM

LOCATION_IS_LOC_FOR_BUSINESS_AREA LOCATION BUSINESS_AREA

NAME

DESCRIPTION

ACCESS_RIGHTS

GENERATION_DATE

TARGET_NAME

Environmental Analysis

Technical Architecture Assessment

Defines reusable code accessible through features in assembler compiler. May be standard or user defined, based on environment.

MACRO_IS_USED_BY_PROGRAM MACRO SOURCE_PROGRAM

MACRO_IS_CONTAINED_IN_LIBRARY MACRO LIBRARY

DESCRIPTION

NAME

MEMBER_NAME

CUSTOM_STD_TYPE_INDICATOR

SCAN_DATE

PROGRAMMING_LANGUAGE

SCAN_DATE

SCAN_ID

Environmental Analysis

An abstraction of certain business information, within a specific problem domain, that encompasses both data and processes associated with that information.

OBJECT_IS_ASSOCIATED-WITH_OBJECT OBJECT OBJECT

ENTITY_MAPS_TO_OBJECT ENTITY OBJECT

EVENT_IMPACTS_OBJECT_STATE EVENT OBJECT

OBJECT_DIAGRAM_CONTAINS_OBJECT OBJECT_DIAGRAM OBJECT

BUS_RULE_IMPACTS_OBJECT PROCESS/BUS_RULE OBJECT

NAME

DESCRIPTION

SUBTYPE

COMPOSITION

SPECIALIZATION_RELATIONSHIPS

Object Derivation Analysis

Object diagrams define each object and associations among these objects. This object modeling approach is based on the Martin/Odell object modeling paradigm.

OBJECT_DIAGRAM_CONTAINS_OBJECT OBJECT_DIAGRAM OBJECT

OBJECT_DIAG_REPRESENTS_BUS_AREA OBJECT_DIAGRAM BUSINESS_AREA

NAME

DESCRIPTION

DATE_CREATED

LAST_UPDATED

Object Derivation Analysis

On-line control tables (for example CICS PCT or IMS ACB definitions) control the execution of system load modules based on on-line transaction invocation.

CONTROL_TBL_EXECS_LOAD_MOD ONLINE_CONTROL_TABLE LOAD_MODULE

CONTROL_TBL_FOUND_IN_LIBRARY ONLINE_CONTROL_TABLE LIBRARY

CONTROL_TBL_PART_OF_SYSTEM ONLINE_CONTROL_TABLE SYSTEM

DESCRIPTION

MEMBER_NAME

TABLE_TYPE (IMS, CICS TYPE, CLIST, etc.)

EXECUTION_TYPE

GENERATION_DATE

MEMBER_NAME

SCAN_DATE

SCAN_ID

Environmental Analysis

A PROC is an IBM JCL term that allows for the reuse of control language statements with a substitution facility. PROCs are recognized since they are a physical component of the system that impacts analysis. Non-IBM environments likely use a similar construct and this should be reflected where applicable.

PROC_CONTAINS_PROC PROC PROC

PROC_EXECUTES_LOAD_MODULE PROC LOAD_MODULE

PROC_INCLUDES_COPYBOOK PROC COPYBOOK

PROC_IS_CONTAINED_IN_LIBRARY PROC LIBRARY

PROC_CONTAINS_JOBSTEP PROC JOBSTEP

PROC_STARTS_JOB PROC JOB

JOB_USES_PROC JOB PROC

PROC_NAME

DESCRIPTION

MEMBER_NAME

TYPE

SCAN_DATE

SCAN_ID

Environmental Analysis

A procedure represents a block of code delineated by a paragraph name or label (depending on source type). Business rules are generally mapped to current source code procedures, depending on the project and paradigm being used.

PROCEDURE_DEFINED_IN_PROGRAM PROCEDURE SOURCE_PROGRAM

PROCEDURE_RELATED_TO_PROCEDURE PROCEDURE PROCEDURE

PRAD_DEFINES_PROCEDURE PRAD PROCEDURE

PROCESS_MAPS_TO_PROCEDURE PROCESS/BUS_RULE PROCEDURE

SOURCE_LANGUAGE

NAME

DESCRIPTION

LINES_OF_CODE

SCAN_DATE

SCAN_ID

USES_COPY

Code Reconciliation & Re-aggregation

Business Rule Derivation Analysis

Process Action Analysis

PRAD is an IE based diagram showing procedures defined at the design level. Because IE procedures are very close to implementation level representations, they are not defined as objects within the LTM. If an IE procedure is to be traced back to an existing system for derivation purposes, the process action diagram (PAD) mapping to PRAD can be used to identify processes and their respective links to legacy source code.

PRAD_DEFINES_PROCEDURE PRAD PROCEDURE

PRAD_REPRESENTS_SYSTEM PRAD SYSTEM

PRAD_REPRESENTS_SUBSYSTEM PRAD SUBSYSTEM

PAD_DECOMPOSES_INTO_PRAD PAD PRAD

NAME

MEMBER_NAME

DESCRIPTION

DATE_CREATED

LAST_UPDATED

Program Specification

A PAD is an IE based decomposition of analysis level business rule representations. This diagram explodes a process, as defined in the IE methodology. Links back to legacy source code may be traced through the PROCESS/BUS_RULE object mapping to source code procedure logic.

PAD_DEFINES_PROCESS PAD PROCESS/BUS_RULE

PAD_DECOMPOSES_INTO_PRAD PAD PRAD

PAD_REPRESENTS_SYSTEM PAD SYSTEM

PAD_REPRESENTS_SUBSYSTEM PAD SUBSYSTEM

NAME

MEMBER_NAME

DESCRIPTION

DATE_CREATED

LAST_UPDATED

Process Action Analysis

This object may represent an IE based analysis object called a process, an event driven business rule implementation or other instantiations of business rules, as defined by other development paradigms. This is a key component of the LTM for redevelopment transition mapping. Redundancy is defined by the mapping relationship between PROCESS/BUS_RULE objects with the same current_target_indicator setting.

BUS_RULE_MAPS_TO_BUS_RULE PROCESS/BUS_RULE PROCESS/BUS_RULE

BUS_RULE_MAPS_TO_SOURCE_PROGRAM PROCESS/BUS_RULE SOURCE_PROGRAM

PROCESS_USES_ENTITY PROCESS/BUS_RULE ENTITY

BUS_RULE_IMPACTS_OBJECT PROCESS/BUS_RULE OBJECT

BUS_RULE_DECOMPOSES_INTO_BUS_RULE PROCESS/BUS_RULE PROCESS/BUS_RULE

BUS_RULE_MAPS_TO_PROCEDURE PROCESS/BUS_RULE PROCEDURE

CHANGE_REQUEST_AFFECTS_PROCESS CHANGE_REQUEST PROCESS_BUS/RULE

EVENT_TRIGGERS_BUS_RULE EVENT PROCESS/BUS_RULE

PAD_DEFINES_PROCESS PAD PROCESS/BUS_RULE

PDD_CONTAINS_PROCESS PDD PROCESS/BUS_RULE

PHD_CONTAINS_PROCESS PHD PROCESS/BUS_RULE

DESCRIPTION

TYPE

NAME

DEACTIVATION_INDICATOR

REDUDANCY_INDICATOR

CURRENT_TARGET_INDICATOR

Business Rule Derivation Analysis

Process Action Analysis

Process Hierarchy/Dependency Analysis

A PDD is an IE based dependency representation of analysis level business rule representations. This diagram is a collection of processes, as defined in the IE methodology.

PDD_CONTAINS_PROCESS PDD PROCESS/BUS_RULE

PDD_REPRESENTS_SYSTEM PDD SYSTEM

PDD_REPRESENTS_SUBSYSTEM PDD SUBSYSTEM

FDD_DECOMPOSES_INTO_PDD FDD PDD

DESCRIPTION

MEMBER_NAME

NAME

DATE_CREATED

LAST_UPDATED

Process Hierarchy/Dependency Analysis

A PDD is an IE based hierarchical representation of analysis level business rules. This diagram is a collection of processes, as defined in the IE methodology.

PHD_CONTAINS_PROCESS PHD PROCESS/BUS_RULE

PHD_REPRESENTS_SUBSYSTEM PHD SUBSYSTEM

PHD_REPRESENTS_SYSTEM PHD SYSTEM

PHD_MAPS_TO_PHD PHD PHD

FHD_DECOMPOSES_INTO_PHD FHD PHD

DESCRIPTION

CURRENT_TARGET_INDICATOR

NAME

MEMBER_NAME

DATE_CREATED

LAST_UPDATED

Process Hierarchy/Dependency Analysis

Record defines a group of data elements that are input to or output from a program. A record may define one or more physical files and be defined identically to other records (duplicate records). A record can be a record because it has direct correlation to an input or output record, even if it is not used directly in I/O.

RECORD_CONTAINS_RECORD RECORD RECORD

RECORD_HAS_KEY_ELEMENT RECORD ELEMENT

RECORD_USES_REC_TYPE_ELEMENT RECORD ELEMENT

RECORD_INCLUDES_COPYBOOK RECORD COPYBOOK

RECORD_IS_DEFINED_IN_PROGRAM RECORD SOURCE_PROGRAM

RECORD_REDEFINES_RECORD RECORD RECORD

RECORD_REPRESENTS_ELEMENT RECORD ELEMENT

RECORD_DEFINES_FILE RECORD FILE

RECORD_DEFINES_SEGMENT RECORD SEGMENT

CHANGE_REQUEST_AFFECTS_RECORD CHANGE_REQUEST RECORD

COPYBOOK_DEFINES_RECORD COPYBOOK RECORD

ENTITY_MAPS_TO_RECORD ENTITY RECORD

INCLUDE_DEFINES_RECORD INCLUDE RECORD

PROGRAM_HAS_PARAMETER_RECORD SOURCE_PROGRAM RECORD

PROGRAM_USES_RECORD SOURCE_PROGRAM RECORD

GROUP_ELEMENT_NAME

DESCRIPTION

RECORD_FORMAT (fixed or variable)

GENERATION_DATE

SOURCE_TYPE

SOURCE_NAME

MAXIMUM_RECORD_LENGTH

ASSEMBLER_NAME

LENGTH

SCAN_DATE

SCAN_ID

Data Definition Analysis

Data Name Rationalization

Field & Record Size Expansion

This defines the connection between entities within an entity relationship diagram or logical data model.

RELATIONSHIP_FROM_ENTITY RELATIONSHIP ENTITY

RELATIONSHIP_MAPS_TO_RELATIONSHIP RELATIONSHIP RELATIONSHIP

RELATIONSHIP_TO_ENTITY RELATIONSHIP ENTITY

ATTRIBUTE_DESCRIBES_RELATIONSHIP ATTRIBUTE RELATIONSHIP

SUBJECT_AREA_CONTAINS_RELATIONSHIP SUBJECT_AREA RELATIONSHIP

DESCRIPTION

TYPE

NAME

CURRENT_TARGET_INDICATOR

Subject Area / Entity Type Analysis

Logical Data Analysis

This is a data base specific term that applies to hierarchical (i.e. IMS), network (i.e. IDMS) or other data base structures and defines a logical view of a group of elements. It would be defined by an IMS PSB, for example. Other data base definitions should use this object to represent a logical view of a physical data structure, as required. Renaming this object, to be more specific, is an option open to the user analyst.

SEGMENT_CONTAINS_DATA_ELEMENT SEGMENT ELEMENT

SEGMENT_DEF_CONTAINED_IN_LIBRARY SEGMENT LIBRARY

DATABASE_DEFINITION_DEFINES_SEGMENT DATABASE_DEF SEGMENT

RECORD_DEFINES_SEGMENT RECORD SEGMENT

NAME

DESCRIPTION

CURRENT_TARGET_INDICATOR

MEMBER_NAME

LOGICAL_LENGTH

PSB_NAME

PHYSICAL_LENGTH

TYPE (PSB, other)

SCAN_DATE

SCAN_ID

Data Definition Analysis

Data Access Layer Assessment

A source program is a delineated block of production source code, represented in a variety of language types, that can be compiled into an object module. One or more object modules are generally linked into an executable load module.

PROGRAM_CALLS_PROGRAM_ENTRY_POINT SOURCE_PROGRAM SOURCE_PROGRAM

PROGRAM_DEFINES_ELEMENT SOURCE_PROGRAM ELEMENT

PROGRAM_HAS_PARAMETER_RECORD SOURCE_PROGRAM RECORD

PROGRAM_IS_CONTAINED_IN_LIBRARY SOURCE_PROGRAM LIBRARY

PROGRAM_NEEDS_PARAMETER_ELEMENT SOURCE_PROGRAM ELEMENT

PROGRAM_USES_CONSTANT SOURCE_PROGRAM CONSTANT

PROGRAM_USES_FILE SOURCE_PROGRAM FILE

PROGRAM_USES_RECORD SOURCE_PROGRAM RECORD

BUS_RULE_MAPS_TO_SOURCE_PROGRAM PROCESS/BUS_RULE SOURCE_PROGRAM

CHANGE_REQUEST_AFFECTS_PROGRAM CHANGE_REQUEST SOURCE_PROGRAM

COPYBOOK_IS_USED_BY_PROGRAM COPYBOOK SOURCE_PROGRAM

FORM_IS_INPUT_TO_SOURCE_PROGRAM FORM SOURCE_PROGRAM

FORM_IS_OUTPUT_FROM_SOURCE_PROGRAM FORM SOURCE_PROGRAM

FUNCTION_MAPS_TO_SOURCE_PROGRAM FUNCTION SOURCE_PROGRAM

INCLUDE_IS_INCLUDED_IN_SOURCE_PROGRAM INCLUDE SOURCE_PROGRAM

LOAD_MODULE_CONTAINS_SOURCE_MODULE LOAD_MODULE SOURCE_PROGRAM

MACRO_IS_USED_BY_PROGRAM MACRO SOURCE_PROGRAM

PROCEDURE_DEFINED_IN_PROGRAM PROCEDURE SOURCE_PROGRAM

RECORD_IS_DEFINED_IN_PROGRAM RECORD SOURCE_PROGRAM

SYSTEM_CONTAINS_SOURCE_PROGRAM SYSTEM SOURCE_PROGRAM

NAME

MEMBER_NAME

DESCRIPTION

PROGRAM_CONTROL_FLOW

LINES_OF_CODE

MOD_BY_ID

ENVIRONMENT

PROGRAMMING_LANGUAGE

COMPILE_DATE

PROGRAM_CONTROL_TRACE

DEFECT_METRIC

MAINTAINABILITY_METRIC

STRUCTURE_METRIC

COMPLEXITY_METRIC

GENERATION_DATE

MOD_DATE

SCAN_DATE

SCAN_ID

CHECKED_OUT_BY

Technical Architecture Assessment

Environmental Analysis

Process Flow Analysis

Function Hierarchy Analysis

Code Reconciliation & Re-aggregation

Subject area is a very high level definition of data within the IE methodology. Addition of a SUBJECT_AREA_DIAGRAM object may be warranted based on situation.

SUBJECT_AREA_CONTAINS_ATTRIBUTE SUBJECT_AREA ATTRIBUTE

SUBJECT_AREA_CONTAINS_ENTITY SUBJECT_AREA ENTITY

SUBJECT_AREA_CONTAINS_RELATIONSHIP SUBJECT_AREA RELATIONSHIP

SUBJEC_AREA_MAPS_TO_SUBJEC_AREA SUBJECT_AREA SUBJECT_AREA

DESCRIPTION

CURRENT_TARGET_INDICATOR

NAME

TYPE

Data Architecture Assessment

Subject Area / Entity Type Analysis

This describes a delineated group of physical components that an organization defines as belonging to a larger group called a system. For example, pay processing may be a subsystem within a human resources system. This is user defined and not a requirement to use LTM.

SUBSYSTEM_INTERFACES_WITH_SUBSYSTEM SUBSYSTEM SUBSYSTEM

DFD_DEFINES_SUBSYSTEM DFD SUBSYSTEM

FDD_IS_PART_OF_SUBSYSTEM FDD SUBSYSTEM

FHD_IS_PART_OF_SUBSYSTEM FHD SUBSYSTEM

JOB_IS_PART_OF_SUBSYSTEM JOB SUBSYSTEM

PRAD_REPRESENTS_SUBSYSTEM PRAD SUBSYSTEM

PAD_REPRESENTS_SUBSYSTEM PAD SUBSYSTEM

PDD_REPRESENTS_SUBSYSTEM PDD SUBSYSTEM

PHD_REPRESENTS_SUBSYSTEM PHD SUBSYSTEM

SYSTEM_CONTAINS_SUBSYSTEM SYSTEM SUBSYSTEM

SYSTEM_INTERFACES_WITH_SUBSYSTEM SYSTEM SUBSYSTEM

SSC_REPRESENTS_SUBSYSTEM SSC SUBSYSTEM

NAME

CURRENT_TARGET_INDICATOR

DESCRIPTION

FUNCTION_POINT_FACTOR

ENVIRONMENT

DATA_MAINT_FACTOR_TDM_250

FUNTIONAL_QLTY_FACTRE_FQM_150

Technical Architecture Assessment

Environmental Analysis

This describes a delineated group of physical components that an organization defines as belonging to or being maintained by a specifically defined group within the enterprise. For example, human resources is an example of a system. System is the key delineator within a business area or enterprise.

SYSTEM_CONTAINS_SOURCE_PROGRAM SYSTEM SOURCE_PROGRAM

SYSTEM_CONTAINS_SUBSYSTEM SYSTEM SUBSYSTEM

SYSTEM_INTERFACES_WITH_SUBSYSTEM SYSTEM SUBSYSTEM

SYSTEM_INTERFACES_WITH_SYSTEM SYSTEM SYSTEM

SYSTEM_SUPPORTS_BUSINESS_AREA SYSTEM BUSINESS_AREA

SYSTEM_USES_FILE SYSTEM FILE

DFD_DEFINES_SYSTEM DFD SYSTEM

ER_DIAGRAM_REPRESENTS_SYSTEM ER_DIAGRAM SYSTEM

FDD_IS_PART_OF_SYSTEM FDD SYSTEM

FHD_IS_PART_OF_SYSTEM FHD SYSTEM

JOB_IS_PART_OF_SYSTEM JOB SYSTEM

LOCATION_IS_LOCATION_FOR_SYSTEM LOCATION SYSTEM

CONTROL_TBL_PART_OF_SYSTEM ONLINE_CONTROL_TABLE SYSTEM

PRAD_REPRESENTS_SYSTEM PRAD SYSTEM

PAD_REPRESENTS_SYSTEM PAD SYSTEM

PDD_REPRESENTS_SYSTEM PDD SYSTEM

PHD_REPRESENTS_SYSTEM PHD SYSTEM

SSC_REPRESENTS_SYSTEM SSC SYSTEM

LOCATION_IS_LOCATION_FOR_SYSTEM LOCATION SYSTEM

NAME

CURRENT_TARGET_INDICATOR

DESCRIPTION

FUNCTION_POINT_FACTOR

ENVIRONMENT

DATA_MAINT_FACTOR_TDM_250

FUNTIONAL_QLTY_FACTRE_FQM_150

Technical Architecture Assessment

Environmental Analysis

An SSC defines an overall structural decomposition of a system within an IE based environment.

SSC_REPRESENTS_SUBSYSTEM SSC SUBSYSTEM

SSC_REPRESENTS_SYSTEM SSC SYSTEM

SSC_MAPS_TO_SSC SSC SSC

NAME

MEMBER_NAME

DESCRIPTION

CURRENT_TARGET_INDICATOR

DATE_CREATED

LAST_UPDATED

System Structure Analysis

A table defines a relational DBMS based table definition. Program record tables are defined in RECORD objects with repeating groups.

TABLE_CONTAINS_ELEMENT TABLE ELEMENT

TABLE_DEFINES_ELEMENT TABLE ELEMENT

TYPE (DB/2 or other RDBMS type)

DESCRIPTION

NUMBER_OF_REPEATING_GROUPS

MEMBER_NAME

NAME

SCAN_DATE

SCAN_ID

Data Access Layer Assessment

Physical Data Analysis & Migration