Professional Documents
Culture Documents
Notaciones
1. Peter Chens (original Entity/
Entity/Relationship Diagram)
Diagram)
2. Information Engineering (IE)
3. Richard Barkers notation (used by the Oracle Corp.)
4. IDEF1X
5. Object Role Modeling (ORM)
6. The Unified Modeling Language (UML)
7. Extensible Markup Language (XML)
1. Peter Chen
(1977)
2. Information Engineering
James Martin & Clive Finkelstein
(1981--1992)
(1981
3. Richard Barker
(1990)
(1992)
(1995)
6. UML OMG
(1998)
7. XML
(1997)
Comparativo
Comparativo
Conclusiones
Notation
Comments
IE
The IE notation (Finkelstein 1989) is simple and easy to read, and is well suited
for high-level logical and enterprise data modeling. The only drawback of this
notation, arguably an advantage, is that it does not support the identification of
attributes of an entity. The assumption is that the attributes will be modeled with
another diagram or simply described in the supporting documentation.
Barker
The Barker (1990) notation is one of the more popular ones, it is supported by
Oracles toolset, and is well suited for all types of data models. Its approach to
subtyping can become clunky with hierarchies that go several levels deep.
IDEF1X
This notation is overly complex. It was originally intended for physical modeling
but has been misapplied for logical modeling as well. Although popular within
some U.S. government agencies, particularly the Department of Defense (DoD),
this notation has been all but abandoned by everyone else. Avoid it if you can.
UML
This is not an official data modeling notation (yet). Although several suggestions
for a data modeling profile for the UML exist, including Naiburg and Maksimchuks
(2001) and my own (Ambler 2001a), none are complete and more importantly are
not official UML yet. Having said that, considering the popularity of the UML,
the other data-oriented efforts of the Object Management Group (OMG), and the
lack of a notational standard within the data community it is only a matter of time
until a UML data modeling notation is accepted within the IT industry.
Herramientas I
Oracle Designer (Oracle)
http://www.oracle.com/technology/products/designer/index.html
ERwin (CA)
http://www.ca.com/us/data--modeling.aspx
http://www.ca.com/us/data
ER/Studio (Embarcadero)
http://www.embarcadero.com/products/er--studio
http://www.embarcadero.com/products/er
Herramientas II
Sybase Power Designer (Sybase)
Sybase)
http://www.sybase.com/products/modelingdevelopment/powerdesigner
DBDesigner 4 (fabFORCE.net)
http://www.fabforce.net/dbdesigner4/
Notacin Barker
(De las ms usada hasta ahora)
Modelo Lgico
Modelo Fsico
XML y Herramientas de
representacin grfica de los modelos
Bibliografa
Hay, David C. 1999. A Comparison of Data Modeling Techniques, Essential Strategies, Inc. (October
1999 )
Barker, Richard. 1990. CASE*Method: Entity Relationship Modeling. Wokingham, England: AddisonAddisonWesley
Bruce, Thomas. 1992. Designing Quality Databases with IDEF1X Information Models. New York:
Dorset House.
Chen, Peter. 1977. "The EntityEntity-Relationship Approach to Logical Data Base Design". The Q.E.D.
Monograph Series: Data Management. Wellesley, MA: Q.E.D. Information Sciences, Inc.
Finkelstein, Clive. 1989. An Introduction to Information Engineering : From Strategic Planning to
Information Systems. Sydney: AddisonAddison-Wesley.
Halpin,, Terry. 2001. Information Modeling and Relational Databases. San Francisco:Morgan
Halpin
Kaufmann.
Jacobson, Ivar,
Ivar, Grady Booch,
Booch, and James Rumbauch.
Rumbauch. 1999. The Unified Software Development
Process. Reading, MA: AddisonAddison-Wesley.
Martin, James and Clive Finkelstein. Nov 1981. "Information Engineering", Technical Report, two
volumes, Lancs,
Lancs, UK : Savant Institute, Carnforth.
Carnforth.
Object Management Group (OMG) 1998. Unified Modeling Language Specification. Framingham,
MA: Object Management Group. Note that UML is still being developed and new versions are
often available. For the latest version, see http://www.omg.org.
XML. 1997. XML Metadata Interchange (XMI) Proposal to the OMG OA&DTF RFP3: StreamStream-based
Model Interchange Format. Framingham, MA: Object Management Group., page 44-33