UML for Database Design

The Workflow

Now we get to the point where the database designers begin to work within their subject matter expertise and the application developers begin working within theirs. Remember that this is an iterative process; the diagrams will not stay stagnant but should be expected to evolve as time passes, as new requirements are uncovered, and as the schedules change, causing feature changes.

There are two basic philosophies on where to go next. One camp says to change the logical design to become the object/class diagram that will represent the application directly, then map that part of the model directly to the data model. We have chosen to follow the second philosophy, which we present in this chapter. The appropriate teams continue to maintain ...