|
|
| |
| |
Metastorm ProVision Modelers-Information
Deliverable Modeler
A Deliverable model is a hierarchy that organizes the deliverables produced by the business. Deliverables are work products produced by the activities of a process.
Deliverable Models show larger aggregate deliverables that consist of smaller component deliverables. A Deliverable Model places an aggregate deliverable at the highest level in the hierarchy. More specific component deliverables are organized below it. A deliverable may be further detailed by building a Business Class model that represents data components of the deliverable.
Business Class Modeler
A Business Class model is a representation of how a class fits into the business domain relative to other classes.
The Business Class model is used as the main inventory of business components and rules. A Business Class model shows the three types of properties for each business class: its associations, attributes, and operations. In total, this enables you to understand the interrelationships of the business classes in the model, and to quickly see all of their components.
Subtype Modeler
A Subtype model is a representation of a general class in a business domain, and of specialized subtype classes that further extend the definition of the supertype class.
The focus of a Subtype model is a business class. Typically, this is the highest-level supertype on the diagram. However, exceptions exist where there are multiple supertypes, and the focus of the model may be the subtype.
Package Modeler
The Package Modeler expresses Package dependencies and components. Its purpose is to visualize the interactions of Packages and present the components (classes, packages, interfaces, associations) of each Package.
Generally, Packages represent implementation level partitioning of system components for construction and deployment by information technology teams.
Statechart Modeler
A Statechart model illustrates the lifecycle for instances of a particular business class. The Statechart model depicts the major stages (states) that an instance of the business class can undergo, the allowable transitions between states, and the operations that transition the class from state to state. As such, Statechart models assist in identifying the "dynamics" of a business class.
The focus of a Statechart model is typically a business class; however, a state may have a component model consisting of its substates. A substate is a partition of a more generic state. Transitions that occur between the superstates (more generic states) are connected at the substate level. For modeling convenience, transitions that are not attached to the substates are assumed to be valid for all substates.
Requirement Modeler
A Requirement model structures the Requirements needed by the enterprise into a hierarchy. A Requirement is a necessary outcome to be delivered by an organization, process, system, etc.
|
|
|
|
|
