Summary

Looking at the business use case and business object models, the database designer can begin to understand the data that is needed to build the database. Of course, this data will need elaboration and more will need to be captured, but this gives a good starting point. Using the UML, the teams can share the information gathered and use it in their jobs. The data analyst can share this information and diagrams with the business analysts and developers. (For example, the data analyst can tell them that the attributes of an auditor will probably include a name, address, phone, specialty, and so on and that an auditor may even become a business entity.) The data will be captured in much more detail later, but it is good to get an understanding ...

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.