Simplest Enterprise Continuous Integration Solutions

Saturday, February 20, 2010

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

- Impact Analysis Report Capabilities (To Be)
Every Casewise implementation intends to fit the organization's unique needs. With Casewise implementation, lots of User Defined Object Types, Association Types, Property Types and associated Objects are brought into Casewise model, even some other User Defined with the out of the box Object Types, Association Types, Property Types and associated Objects.
Casewise Corporate Modeler Suite Report handles those User Defined Association Types, User Defined Property Types for every Object Types dynamically at one layer base.
For instance, as the diagram below in Model (Casewise Framework Example), a Object Type (Applications) has Properties (i.e. General, Description and etc), Associations (i.e. Entities, Processes, Technologies and etc)

But as you can see, Casewise Corporate Modeler Suite Report only supports Object Type at one layer base, doesn't come out with next layer Object Type, next next layer Object Type, even next n layers Object Type through Association Types.
Is there a simplest best practice approach, which will have unlimited layers (indirect levels) limitation and do Enterprise Architecture Impact Analysis in Casewise in real time besides the currently Casewise Corporate Modeler Intelligence (2009.1) Reporting (which only supports a maximum of seven indirect levels for indirect associations and impact analysis)? If so, what will be a doable mechanism (an Intelligent Mathematics Model) behind this simplest best practice approach with unlimited layers (indirect levels) limitation and do Enterprise Architectur Impact Analysis in Casewise in real time?
This doable mechanism (an Intelligent Mathematics Model
  • should be a real intelligent mechanism, which will handle User Defined Object Types, User Defined Association Types and Userd Define Property Types in one for all reporting pattern automatically. This is the first and the most key point to do Enterprise Architecture Impact Analysis in Casewise.
  • should be able to build all possible Object Types chains via Association Types based on inputs (i.e. Model Name, Ascendant/Descendant, Start Object Type Name, End Object Type Name - optional).
  • based upon the Object Type chains, should be able to build all of possible unlimited layers (indirect levels) Object Type associated Objects if one of Object associated with Start Object Type is given
  • each of Objects should be able to include its own Properties (i.e. General, Description and etc), Associations (i.e. Entities, Processes, Technologies and etc) as Casewise Corporate Modeler Suite Report does.
  • should also be able to flexible display report in specified language as well if bilingual (for instance, English, French) was implemented into Object Type.

No comments:

Post a Comment