Part 3 of a Continuing Series In many ways, architects and database modelers perform very similar roles. Both meet with end users to ascertain their needs and then design a solution. In the case of an architect, the design specifications are called a blueprint. In the case of a database modeler, the design is called a data model.
However, while architects and builders long ago agreed on one universal standard, the IT industry has not been as lucky. Unfortunately, there are numerous data modeling notations including CASE*Method, Chen, IDEF1X, object-role modeling (ORM) and others. While each notation has its pros and cons, they all accomplish the same goal. They display a graphical model of a database.
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access