Presentation 1 for Mis

Embed Size (px)

Citation preview

  • 8/6/2019 Presentation 1 for Mis

    1/20

    BY ROLL NUMBERS: 1001247078

    1001247079

    1001247080

    10012470811001247082

    1001247083

    1001247084

  • 8/6/2019 Presentation 1 for Mis

    2/20

  • 8/6/2019 Presentation 1 for Mis

    3/20

    Conceptual models includeEntity-relationship database model (ERDBM)

    Object-oriented database model (OODBM)

    Implementation models includeHierarchical database model (HDBM)

    Network database model (NDBM)

    Relational database model (RDBM)

    Object-oriented database model (OODBM)

  • 8/6/2019 Presentation 1 for Mis

    4/20

    Hierarchical Model

    Network Model

    Relational Model

    Object-Oriented Model

    Entity-Attribute-Value (EAV) data model

  • 8/6/2019 Presentation 1 for Mis

    5/20

    COMPARISION:y Hierarchical (tree)

    y Data is organized top-down

    y Networky Owner-membership relationship

    y A member can have many owners

    y Relational

    y Uses tabular format with 2-dimensional tables(relations)

    y Relations resemble files

  • 8/6/2019 Presentation 1 for Mis

    6/20

  • 8/6/2019 Presentation 1 for Mis

    7/20

  • 8/6/2019 Presentation 1 for Mis

    8/20

    RELATIONAL DATABASE MODEL:y Data is represented in the form oftables, and the

    modelhas 3 components

    y Data structure dataare organised in the form oftables with rows and columns

    y Data manipulation powerful operations (using theSQL language) are used to manipulate data stored in

    the relationsy Data integrity facilities are included to specifybusiness rules that maintain the integrityof datawhentheyare manipulated

  • 8/6/2019 Presentation 1 for Mis

    9/20

    Entity-Relationship diagrams are useful for modelling dataandthe relationships between the data. Theycan be used when theconstraints between dataare relativelysimple. Theydo notallow specification of interactions between the data or modelhow the data changes (there are no processes in Entity-Relationship).

  • 8/6/2019 Presentation 1 for Mis

    10/20

    Conceptual simplicity:

    Database security:

    Data integrity

    Data independence

    Efficiency in 1:M

  • 8/6/2019 Presentation 1 for Mis

    11/20

    Hierarchical Database Model

    y Disadvantages

    y Complex implementation:

    y Difficult to manage and lack of standards

    y Lacks structural independence

    y

    Applications programming and use complexity(pointer based)

    y Implementation limitations, i.e. especially it onlyhandle 1:M type of model

  • 8/6/2019 Presentation 1 for Mis

    12/20

    NETWORK DATABASE:y Advantages

    y Conceptual simplicity, just lime HDMy Handles more relationship types (but all 1:M

    relationship)y Data access flexibilityy Promotes database integrityy Data independencey Conformance to standards

    y Disadvantagesy System complexityy Lack of structural independence

  • 8/6/2019 Presentation 1 for Mis

    13/20

    Structural independence: data access path isirrelevant to database design;

    change structure will not affect the database

    Improved conceptual simplicity

    Easier database design, implementation,management, and use

    Ad hoc query capability with SQL (4GL isadded)

    Powerful database management system

    u1

  • 8/6/2019 Presentation 1 for Mis

    14/20

    Slide 13

    u1 user, 4/26/2011

  • 8/6/2019 Presentation 1 for Mis

    15/20

    Substantial hardware and system software

    overheadPoor design and implementation is madeeasy

    May promote islands of information

    problems

  • 8/6/2019 Presentation 1 for Mis

    16/20

    ENTITY ATTRIBUTE

    RELATIONSHIP:ADVANTAGEy Conceptual simplicity

    y Visual representation

    y Effective communication

    y Integration withthe relationaldatabase model

    DISADVANTAGESy Limited constraint

    representation

    y Limited relationshiprepresentation

    y No representation of datamanipulation

    y Loss of information

  • 8/6/2019 Presentation 1 for Mis

    17/20

    OLTP vs. OLAP

    We can divide ITsystems intotransactional (OLTP)

    and analytical (OLA

    P).In general we canassume that OLTPsystems provide sourcedatato data

    warehouses, whereasOLAP systems help toanalyze it.

  • 8/6/2019 Presentation 1 for Mis

    18/20

    DIFFERENCE:

    DATA WAREHOUSING DBMS

    y You could think of datawarehousing as an

    environmentthatprovides a vehicle todeliver meaningfulinformation to thebusiness communitytoenable effective

    operations oversightandbusiness decisionsupport.

    y DBMS is a "DatabaseManagement System". Thisis the software that

    manages data on physicalstorage devices. Thesoftware provides the abilityto store, access and modifythe data. Examples ofadbms would be Oracle,

    SQL/Server, DB2 andInformix in the relational(rdbms) world

  • 8/6/2019 Presentation 1 for Mis

    19/20

    FUTURE OF DATABASE MODEL:

  • 8/6/2019 Presentation 1 for Mis

    20/20

    THANK YOU