Enterprise Architecture Practice 10 - How to do EA Impact Analysis in Casewise 7

- Object Type Chain Mathematics Model
Based on previous 2 articles about Object Type Chains for OOB POLDAT  and User Defined.
Here is the programmable Casewise Object Type Chain Mathematics Model which was developed based on the unlimited layers and real time reporting to do Impact Analysis in Casewise through Casewise Corporate Modeler physical Database.
/*
/* Purpose: one for all PoC (Proof of Concept) approach (Mathematics Model) for Object Type Chain
/* Inputs:
/* modelName: Casewise Model Name
/* (Source) objectType: Casewise Object Type
/* (Target) anoObjectType: an optional parameter,the return results will be filtered based on the AnoObjectType
/* resultMode: asc - Source to Target or desc - Target to Source
/* Returns:
/* (a table valued) ObjectTypeChain (unlimited layers)
/*
Loop Start:
  If objectType belongs to OOB POLDAT (POLAT, OLDAT, PROCESS <-> ENTITY, PROCESS <-> ATTRIBUTE, ENTITY -> ATTRIBUTE, DOMAIN -> ATTRIBUTE)
    parse all of the possible next layer objectTypes based on the resultMode with OOB POLDAT
  Else
    parse all of the possible next layer objectTypes based on the resultMode with User Defined
  End
  If next layer objectType has another next layer objectType (not the previous one)
    continue the loop
  Else
    exit the Loop
  End
Loop End
If anoObjectType is defined
   filter the Loop returnResults (objectTypeChains)
End
Return returnResults (objectTypeChains)

Enterprise Architecture Practice 9 - How to do EA Impact Analysis in Casewise 6

- Object Type Chains for User Defined Object Types
For User Defined Object Types, the Mathematics Model will be:

• Source to Target or Target to Source mode between Object Type and another Object Type.
• Each of Object Types inter link togeher.

This Mathematics Model also covers all of User Defined POLDAT cases (for example, OOB POLDAT Application associated with User Defined Object Type through an User Defined Association Type).

Enterprise Architecture Practice 8 - How to do EA Impact Analysis in Casewise 5

- Object Type Chains for OOB POLDAT
Object Type Chain existence had been explained in my previous article.
What kind of Object Types should be included into Object Type Chains? Since talking about Impact Analysis, both of POLDAT Object Type and User Defined Object Type should be included.
For OOB (Out of the Box) POLDAT, the Mathematics Model will be:

• POLAT
• OLDAT
• PROCESS <-> ENTITY, PROCESS <-> ATTRIBUTE
• ENTITY -> ATTRIBUTE, DOMAIN -> ATTRIBUTE

Note: Expanding Data from Entity to Entity, Data Usage (PROCESS <-> ENTITY, PROCESS <-> ATTRIBUTE), Attribute (ENTITY -> ATTRIBUTE, DOMAIN -> ATTRIBUTE) because of some of OOB associations existed in OOB already.

Enterprise Architecture Practice 7 - How to do EA Impact Analysis in Casewise 4

- Does Object Type Chain exist in Casewise?
An Source Object Type could be associated with a Target Object Type (if the target Object Type is same as the Source Object Type, then becomes a self-reference association) through an Association Type.
The Association Type could be Source to Target, Target to Source or both of Source to Target and Target to Source. It could be expressed as Swim Lane or Object Type Connector.
For instance, based on Casewise out of the box multiple one layer bi-dimensional Reporting Mechanism, if Object Type OT_1 has an association with Object Type OT_2 through Association Type AT_1, Object Type OT_2 has an association with Object Type OT_3 through Association Type AT_2, and then definitely there will be a Object Type Chain (an Mathematics Model) exists as always. In this case, the Object Type Chains from OT_1 to OT_3 will be:
Source to Target mode: OT_1 -> OT_2 -> OT_3
Target to Source mode: OT_3 -> OT->2 -> OT_1
Actually this kind of Mathematics Model could calculate out all of possible Object Type Chains based on a Source Object Type (with or without a Target Object Type will be a option) precisely.