UML for Database Design

The Approach

Typically, the approach at this point in the development cycle is straightforward. Similar to the business-level modeling, for each of the system use cases a textual flow of events should be developed (in much more detail than what was done in use case development), followed by a sequence diagram. From these a class diagram will be developed. But how do you go from the use cases and sequence diagrams to a class diagram? Development approaches that start at the system level (that is, no business modeling) usually have very general guidelines to “discover” the candidate classes for the class diagram. While these guidelines can work and are simple to understand (for example, “Pick out all the nouns in the problem statement and make ...