|
|
|
There are three classifications of UML diagrams:
-
Behavior diagrams:
A type of diagram that depicts behavioral features of a system or business process. This includes activity, state machine, and use case diagrams as well as the four interaction diagrams.
-
Interaction diagrams:
A subset of behavior diagrams which emphasize object interactions. This includes communication, interaction overview, sequence, and timing diagrams.
-
Structure diagrams:
A type of diagram that depicts the elements of a specification that is irrespective of time. This includes class, composite structure, component, deployment, object, and package diagrams.
|
|
|
In the first version of ModelCVS by APG we realized two of those 14 diagrams. Those are class diargram and state machine chart. In addition to that we can use our SWT generation model and model the GUI. In the figures below you see some diagrams and their corresponding charts in CA Gen.
|
|
Commercial available: on 1st September, 2008
|
UML and CA Gen
The Unified Modeling Language™ - UML - is OMG's most-used specification, and the way the world models not only application structure, behavior, and architecture, but also business process and data structure.
UML, along with the Meta Object Facility (MOF™), also provides a key foundation for OMG's Model-Driven Architecture®, which unifies every step of development and integration from business modeling, through architectural and application modeling, to development, deployment, maintenance, and evolution.
The OMG's Unified Modeling Language™ (UML®) helps you specify, visualize, and document models of software systems, including their structure and design, in a way that meets all of these requirements. (You can use UML for business modeling and modeling of other non-software systems too.) Using any one of the large number of UML-based tools on the market, you can analyze your future application's requirements and design a solution that meets them, representing the results using UML 2.0's thirteen standard diagram types.
What's new in UML 2.0: We've already integrated the new features into this writeup, but here's a summary:
Nested Classifiers: This is an extremely powerful concept. In UML, almost every model building block you work with (classes, objects, components, behaviors such as activities and state machines, and more) is a classifier. In UML 2.0, you can nest a set of classes inside the component that manages them, or embed a behavior (such as a state machine) inside the class or component that implements it. This capability also lets you build up complex behaviors from simpler ones, the capability that defines the Interaction Overview Diagram. You can layer different levels of abstraction in multiple ways: For example, you can build a model of your Enterprise, and zoom in to embedded site views, and then to departmental views within the site, and then to applications within a department. Alternatively, you can nest computational models within a business process model. OMG's Business Enterprise Integration Domain Task Force (BEI DTF) is currently working on several interesting new standards in business process and business rules.
Improved Behavioral Modeling: In UML 1.X, the different behavioral models were independent, but in UML 2.0, they all derive from a fundamental definition of a behavior (except for the Use Case, which is subtly different but still participates in the new organization).
Improved relationship between Structural and Behavioral Models: As we pointed out under Nested Classifiers, UML 2.0 lets you designate that a behavior represented by (for example) a State Machine or Sequence Diagram is the behavior of a class or a component.
That is, the new language goes well beyond the Classes and Objects well-modeled by UML 1.X to add the capability to represent not only behavioral models, but also architectural models, business process and rules, and other models used in many different parts of computing and even non-computing disciplines.
During the upgrade process, several additions to the language were incorporated into it, including the Object Constraint Language (OCL) and Action Semantics.
|
| Diagram |
Description |
| Activity Diagram |
Depicts high-level business processes, including data flow, or to model the logic of complex logic within a system. . |
| Class Diagram |
Shows a collection of static model elements such as classes and types, their contents, and their relationships. . |
| Communication Diagram |
Shows instances of classes, their interrelationships, and the message flow between them. Communication diagrams typically focus on the structural organization of objects that send and receive messages. Formerly called a Collaboration Diagram. . |
| Component Diagram |
Depicts the components that compose an application, system, or enterprise. The components, their interrelationships, interactions, and their public interfaces are depicted. . |
| Composite Structure Diagram |
Depicts the internal structure of a classifier (such as a class, component, or use case), including the interaction points of the classifier to other parts of the system. |
| Deployment Diagram |
Shows the execution architecture of systems. This includes nodes, either hardware or software execution environments, as well as the middleware connecting them. . |
| Interaction Overview Diagram |
A variant of an activity diagram which overviews the control flow within a system or business process. Each node/activity within the diagram can represent another interaction diagram. |
| Object Diagram |
Depicts objects and their relationships at a point in time, typically a special case of either a class diagram or a communication diagram. |
| Package Diagram |
Shows how model elements are organized into packages as well as the dependencies between packages. . |
| Sequence Diagram |
Models the sequential logic, in effect the time ordering of messages between classifiers. |
| State Machine Diagram |
Describes the states an object or interaction may be in, as well as the transitions between states. Formerly referred to as a state diagram, state chart diagram, or a state-transition diagram. |
| Timing Diagram |
Depicts the change in state or condition of a classifier instance or role over time. Typically used to show the change in state of an object over time in response to external events. |
| Use Case Diagram |
Shows use cases, actors, and their interrelationships. |
CA Gen diagrams are depicted under / spektrum / model based development on www.arikan.at.
In the figure below you see a possible assignment of UML diagrams to CA Gen diagrams. This assignment is not unique but can be used to generate code in Gen.
|
|
Using those assignments of UML to gen applications can be designed by UML and generated in Gen.
|
Mapping between AllFusion Gen & UML2
|
Instead oft he Activity Diagram also the state chart machine can be used to generate dialog flow informations.
In the examples below you see sompe possible conversions, done by ModelCVS from APG.
|
*) Part of this text has been taken from some sites in Internet includy the OMG UML Homepage.
|
CA Gen' Datamodel to UML2's Class Diagramm
|
CA Gen' Navigation to UML2's State Machine
|
Gen - UML Mapping Example
Process Hierarchy -- Use Case Diagram
Data model -- Class Diagram
Dialog design -- 1 or more Activity Diagram
Action Diagram -- Activity Diagram
|
|
|
|