![]() | ![]() |
|
06-02-2010 01:38 PM
ProVision includes several industry standard modeling languages that users can activate and organize their models according to a certain framework along with assuming the naming conventions that accompany the methodology.
Some of the most frequently used frameworks for BPA are Six Sigma, and BPA (derived from the Object Management Group). The more commonly used EA frameworks are TOGAF (The Open Group Architecture Framework) and Zachman.
The current trend is for users to customize these frameworks and create naming conventions unique to their organization.
This is easily accomplished in the ProVision UI under Tools and Customization Control Panel.
It is important to establish modeling standards for organizational projects because when your models are deployed and viewed on the Knowledge Exchange server those users viewing model content will recognize the structure and naming conventions. Modeling standards also assist in the communication of project deliverables such as reports.
Thanks
Gerry
09-13-2010 10:26 PM
We have taken a different approach and preserve the industry framework as a common reference to which we can trace back, or map our activites, systems, information etc.
We use capabilities (with a stereotype of <<application capability>> with capabilites with a stereotype of <<applicationdomain>>) to model the TMForum Application Map, and use the utlization link to associate these application capabilites with systems. This gives us an industry standard alignment and understanding of our systems.
We have created the TMForum level 2 and level 3 process framework with a naming convention and a stereotype of <<L2 reference>> and <<reference>> and use a custom referencelink to give us an industry standard understanding of our actual processes and activites.
We use technologies to provide a set of referecne technologies for our actual technologies (this is more aligned with the standard approach).
09-14-2010 04:34 AM
The great thing about standards is there are so many to choose from!
![]() |
![]() |
![]() |
|
|
![]() |
![]() |
![]() |
















