Given the issues between object-oriented modeling in UML and entity/relationship modeling, how do we set out to create an architectural entity/relationship model using the UML notation? This chapter provides the answer. We begin with a summary of the approach, followed by a detailed description of each step.[(]
To create a conceptual (semantic or architectural) entity/relationship model using a UML diagramming tool, follow these guidelines:
1. Show domain-specific entity cases only. Consider only classes that are collections of things of significance to the enterprise or the domain being addressed. These are referred to here as entity classes.
2. Use Symbols Selectively.
Ø Use only appropriate ...