Summary

By leveraging the work that was already done in the previous phases of the project (business modeling and requirements definition), the work in the analysis and preliminary design phase is greatly simplified. Instead of beginning with a blank sheet of paper, key elements of the system already exist in the model (as use case, activity, class, sequence, and statechart diagrams and other specifications), waiting to be used. And when rework of previous designs is needed, having a common language (the UML) allows all team members to understand and respond quickly. In this way, the application and database teams, working together, get results faster and of higher quality than would have been typically achieved by working in separate development ...

Get UML for Database Design now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.