Entity objects, view objects and application modules, their attributes and methods, the associations between them and their inheritance relationships can all be modeled graphically on a Business Components diagram. Entity object usages can be modeled on view objects, and view object instances and application module instances can be modeled on application modules. Business Components diagrams can also be used for modeling UML classes, Java classes, UML use cases, offline database objects, Enterprise JavaBeans and web services.
To create a diagram of business components:
Entity Object
Domain
1 to * Association
Directed 1 to 1 Association
Directed 1 to * Association
Directed Strong Association
View Object
Entity Object Usage
View Link
Application Module
View Object Instance
View Link Instance
Application Module Instance
Generalization
For more information on creating nodes and connectors on a diagram, see Creating Nodes on a Diagram and Connecting Nodes on a Diagram.
Tip: You can also annotate your diagram by creating and attaching notes to diagram element, and adding URL links to other locations such as files or web locations. For more information, see Annotating a Diagram.
Getting Started with Business
Component Modeling
How to Read a
Diagram of Business Components
Modeler's Guide
Developing Oracle ADF Business Components
Copyright © 1997, 2004, Oracle. All rights reserved.