Content tagged with: database
Data modelling is considered a staple in the world of data management. The skill of the data modeler and their knowledge of the business plays a large role in successful Enterprise Information Management across many organizations. Data modeling requires formal accountability, attention to metadata and getting the business heavily involved in data requirement development. These are all traits of solid Data Governance programs.
Data warehousing commonly implies complex data flows, either because of the large number of steps data transformations may consist of, or of the different types of data they carry. These issues rise interesting challenges concerning design-oriented modeling of data warehousing flows with UML.
Some databases have more complex requirements than do the more traditional applications. This led to the development of additional semantic data modeling concepts that were incorporated into conceptual data models such as the Entity-Relationship (ER) model.
In this interview, Michael Blaha discusses the relationship between use cases gathering and database modeling. His opinion is that it is fine to capture requirements with use cases, but they should be dependend of the class model, which defines the domain of knolwedge that can be referenced by use cases. For database applications it is much inferior to start with use cases and afterwards construct a class model, because they need a data approach and not a process approach. As object-oriented programming languages define a class structure to which logic …
Roberto V. Zicari of www.odbms.org asked a few questions to Dr. Michael Blaha about using UML for database conceptual modeling.
This article offers a step by step approach to transform a UML object-oriented class model in a purely relational database.