Modelado de DatosModelado de Datos

Juan Bernardo QuinteroJuan Bernardo Quintero

NotacionesNotaciones

1.1. Peter Peter ChensChens (original (original EntityEntity//RelationshipRelationship DiagramDiagram))

2.2. InformationInformation EngineeringEngineering (IE)(IE)

3.3. Richard Richard BarkersBarkers notationnotation ((usedused byby thethe Oracle Corp.) Oracle Corp.) 3.3. Richard Richard BarkersBarkers notationnotation ((usedused byby thethe Oracle Corp.) Oracle Corp.)

4.4. IDEF1X IDEF1X

5.5. ObjectObject Role Role ModelingModeling (ORM) (ORM)

6.6. TheThe UnifiedUnified ModelingModeling LanguageLanguage (UML) (UML)

7.7. Extensible Extensible MarkupMarkup LanguageLanguage (XML) (XML)

1. Peter Chen 1. Peter Chen (1977)(1977)

2. Information Engineering2. Information Engineering

James Martin & Clive Finkelstein James Martin & Clive Finkelstein (1981(1981--1992)1992)

3. Richard Barker 3. Richard Barker (1990)(1990)

4. IDEF 1X 4. IDEF 1X --Thomas Bruce Thomas Bruce (1992)(1992)

5. ORM 5. ORM Terry Halpin Terry Halpin (1995)(1995)

6. UML 6. UML OMG OMG (1998)(1998)

7. XML 7. XML (1997)(1997)

ComparativoComparativo

ComparativoComparativo

ConclusionesConclusiones

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 Barker 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 IHerramientas I

Oracle Oracle DesignerDesigner (Oracle)(Oracle)

http://www.oracle.com/technology/products/dhttp://www.oracle.com/technology/products/designer/index.htmlesigner/index.html

ERwinERwin (CA)(CA)

http://www.ca.com/us/datahttp://www.ca.com/us/data--modeling.aspxmodeling.aspxhttp://www.ca.com/us/datahttp://www.ca.com/us/data--modeling.aspxmodeling.aspx

SQL Power Architect Data Modeling Tool (SQL Power Architect Data Modeling Tool (SQLPowerSQLPower Software)Software)

http://www.sqlpower.ca/page/architecthttp://www.sqlpower.ca/page/architect

SQL Developer Data Model (Oracle)SQL Developer Data Model (Oracle)

http://www.oracle.com/technology/products/database/datamodeler/index.htmlhttp://www.oracle.com/technology/products/database/datamodeler/index.html

ER/Studio (Embarcadero)ER/Studio (Embarcadero)

http://www.embarcadero.com/products/erhttp://www.embarcadero.com/products/er--studiostudio

Herramientas IIHerramientas II

SybaseSybase PowerPower DesignerDesigner ((SybaseSybase))

http://www.sybase.com/products/modelingdevelopment/powerdesignerhttp://www.sybase.com/products/modelingdevelopment/powerdesigner

ClayClay Mark II Mark II forfor Eclipse (Eclipse (AzzurriAzzurri))

http://www.azzurri.jp/en/clay/index.htmlhttp://www.azzurri.jp/en/clay/index.htmlhttp://www.azzurri.jp/en/clay/index.htmlhttp://www.azzurri.jp/en/clay/index.html

DBDesignerDBDesigner 4 (fabFORCE.net)4 (fabFORCE.net)

http://www.fabforce.net/dbdesigner4/http://www.fabforce.net/dbdesigner4/

MySQLMySQL WorkbenchWorkbench ((MySQLMySQL Inc.)Inc.)

http://wb.mysql.com/http://wb.mysql.com/

Notacin Barker(De las ms usada hasta ahora)

Modelo Lgico

Modelo Fsico

XML y Herramientas de XML y Herramientas de representacin grfica de los modelosrepresentacin grfica de los modelos

Mapeo XML Mapeo XML Diagramas Diagramas de Clases de Clases --SQLSQL

BibliografaBibliografa

Hay, David C. 1999. A Comparison of Data Modeling Techniques, Essential Strategies, Inc. (October Hay, David C. 1999. A Comparison of Data Modeling Techniques, Essential Strategies, Inc. (October 1999 )1999 )

Barker, Richard. 1990. CASE*Method: Entity Relationship Modeling. Wokingham, England: AddisonBarker, Richard. 1990. CASE*Method: Entity Relationship Modeling. Wokingham, England: Addison--WesleyWesley

Bruce, Thomas. 1992. Designing Quality Databases with IDEF1X Information Models. New York: Bruce, Thomas. 1992. Designing Quality Databases with IDEF1X Information Models. New York: Dorset House. Dorset House.

Chen, Peter. 1977. "The EntityChen, Peter. 1977. "The Entity--Relationship Approach to Logical Data Base Design". The Q.E.D. Relationship Approach to Logical Data Base Design". The Q.E.D. Monograph Series: Data Management. Wellesley, MA: Q.E.D. Information Sciences, Inc. Monograph Series: Data Management. Wellesley, MA: Q.E.D. Information Sciences, Inc. Monograph Series: Data Management. Wellesley, MA: Q.E.D. Information Sciences, Inc. Monograph Series: Data Management. Wellesley, MA: Q.E.D. Information Sciences, Inc.

Finkelstein, Clive. 1989. An Introduction to Information Engineering : From Strategic Planning to Finkelstein, Clive. 1989. An Introduction to Information Engineering : From Strategic Planning to Information Systems. Sydney: AddisonInformation Systems. Sydney: Addison--Wesley.Wesley.

HalpinHalpin, Terry. 2001. Information Modeling and Relational Databases. San , Terry. 2001. Information Modeling and Relational Databases. San Francisco:MorganFrancisco:MorganKaufmann.Kaufmann.

Jacobson, Jacobson, IvarIvar, Grady , Grady BoochBooch, and James , and James RumbauchRumbauch. 1999. The Unified Software Development . 1999. The Unified Software Development Process. Reading, MA: AddisonProcess. Reading, MA: Addison--Wesley.Wesley.

Martin, James and Clive Finkelstein. Nov 1981. "Information Engineering", Technical Report, two Martin, James and Clive Finkelstein. Nov 1981. "Information Engineering", Technical Report, two volumes, volumes, LancsLancs, UK : Savant Institute, , UK : Savant Institute, CarnforthCarnforth..

Object Management Group (OMG) 1998. Unified Modeling Language Specification. Framingham, 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 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.often available. For the latest version, see http://www.omg.org.

XML. 1997. XML Metadata Interchange (XMI) Proposal to the OMG OA&DTF RFP3: StreamXML. 1997. XML Metadata Interchange (XMI) Proposal to the OMG OA&DTF RFP3: Stream--based based Model Interchange Format. Framingham, MA: Object Management Group., page 4Model Interchange Format. Framingham, MA: Object Management Group., page 4--3333

MUCHAS GRACIAS !!!MUCHAS GRACIAS !!!MUCHAS GRACIAS !!!MUCHAS GRACIAS !!!