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

- Physical database
What kind of Enterprise Architecture Impact Analysis are we expecting from Casewise? Is there an out of the box solution from Casewise ready to use for Impact Analysis? ...

Before answering these kind of questions, we'd better to understand some basic concepts of Casewise Corporate Suite.

Out of the box, Casewise has:

Object Types (i.e. Process, Organization, Location, Attribute, Domain, Entity, Application, Technology, etc)

Association Types between Source and Target Object Types (i.e. Source -> Target, Application -> Location, Organization -> Process, etc). Association Types are also part of Object Types.

Each of Object Type has its own Property Type (i.e. Id, Name, Category, Description, etc), and also might have multiple Objects.

After Casewise implementation, new Object Types (with associated Objects), new Association Types, new Properties (i.e, Single-line text, Multi-line text, Drop-down list, Check-box, etc), new Property Types for Out of the box Property Types, new Objects for Out of the box Object Types are defined, all of these are User Defined.

POLDAT is the abbreviation of Process, Organization, Location, Data, Application, Technology, which maps to Casewise Object Types: Process, Organization, Location, Attribute, Domain, Entity, Application and Technology.
In the hierarchy rule based diagram, Hierarchy Link only link 2 Objects on the diagram, doesn't provide any hierarchy associations from the database. But you could create an User Defined Association Type to enable this kind of associations (i.e. Used by, Using for) since Casewise's bi-dimensional associations feature dynamic make it possible.