An object-oriented model (OOM)
helps you analyze an information system through use cases, structural and
behavioral analyses, and in terms of deployment, using the Unified Modeling
Language (UML). You can model, reverse-engineer, and generate for Java, .NET
and other languages.
Creating an Object-Oriented Model
- To create a new, empty OOM - Select , and choose Object Oriented Model.
- To reverse engineer a new OOM from a object language files - Select .
- To import a Rational Rose model into an OOM - Select .
- To import an XMI file into an OOM - Select .
The following types of diagrams are available:
-
A use case
diagram is a UML diagram that provides a graphical view
of the requirements of your system, and helps you identify how users
interact with it.
-
A class
diagram is a UML diagram that provides a graphical view
of the classes, interfaces, and packages that compose a system, and
the relationships between them.
-
An object
diagram is a UML diagram that provides a graphical view
of the structure of a system through concrete instances of classes
(objects), associations (instance links), and dependencies.
-
A composite
structure diagram is a UML diagram that provides a
graphical view of the classes, interfaces, and packages that compose
a system, including the ports and parts that describe their internal
structures.
-
A package
diagram is a UML diagram that provides a high-level
graphical view of the organization of your application, and helps
you identify generalization and dependency links between the
packages.
-
A sequence
diagram is a UML diagram that provides a graphical view
of the chronology of the exchange of messages between objects and
actors for a use case, the execution of an operation, or an
interaction between classes, with an emphasis on their
chronology.
-
A
communication diagram is a UML diagram that
provides a graphical view of the interactions between objects for a
use case scenario, the execution of an operation, or an interaction
between classes, with an emphasis on the system structure.
-
An
interaction diagram is a UML diagram that provides
a high-level graphical view of the control flow of your system as it
is decomposed into sequence and other interaction diagrams.
-
An activity
diagram is a UML diagram that provides a graphical view
of a system behavior, and helps you functionally decompose it in
order to analyze how it will be implemented.
-
A statechart
diagram is a UML diagram that provides a graphical view
of a State Machine, the public behavior of a classifier (component
or class), in the form of the changes over time of the state of the
classifier and of the events that permit the transition from one
state to another.
-
A component
diagram is a UML diagram that provides a graphical view
of the dependencies and generalizations among software components,
including source code components, binary code components, and
executable components.
-
A deployment
diagram is a UML diagram that provides a graphical view
of the physical configuration of run-time elements of your
system.
Generating Other Models
You can generate other PowerDesigner models from an OOM by selecting
Tools >:
- Generate Conceptual Data Model (or press Ctrl+Shift+C)
- Generate Physical Data Model (or press Ctrl+Shift+P)
-
Generate Object-Oriented Model (or press Ctrl+Shift+O)
- Generate XML Model (or press Ctrl+Shift+M)
Working with Object Language Definitions
The object language definition file defines features specific to the language being modeled:
- To open the object language definition file in the Resource Editor, select .
- To change the process language to model with, select .
Documentation
For detailed documentation, see Object-Oriented Modeling.