1. Entity Modeling Pratt & Adamski, Ch 6

2. The Pratt and Adamski approach is not a standard MIS view. Design Methodology Data Modeling

3. CS zStart with reports and forms zIdentify attributes zIdentify tables zNormalize MIS Approach z Start with a narrative description z Identify entities z Design table structure z Check for normalization

4. MIS Data Modeling zTop-down approach Begins with a model of the firm zFocuses on tables and relationships Begins by modeling entities and adds attributes later zNormalization used as a confirmation rather than design tool

5. Life Cycle zEnterprise Design: major components Entities and relationships in context zConceptual Design: business needs Tables and attributes independent of DBMS zPhysical Design: technology design Entities, attributes, constraints, associative tables, etc. as they will be built

6. Enterprise Design Determine the entities and relationships that interact with the proposed system. Don’t model attributes, constraints or tables necessary to implement relational structures or sub-classes

7. SalesRep Order Customer Supplier Product Enterprise Model

8. Conceptual Design Determine the model of the system independent of the DBMS that will be used for physical implementation. System entities, primary keys, attributes, relationships, constraints. No associative entities, foreign keys or sub-classes.

9. SalesRep SalesRepID (PK) Name Address Order OrderNumber (PK) Date Customer CustomerID (PK) Name Address Product ProductNum (PK) Description Price Category Conceptual Model

10. Relational and Physical Design Produce a detailed model of the ultimate system. Model a complete normalized system. Then denormalize selectively to improve the operational characteristics of the final database.

11. SalesRep SalesRepID (PK) Name Address Order OrderNumber (PK) CustomerID (FK) Date Customer CustomerID (PK) SalesRepID (FK) Name Address Product ProductNum (PK) Description Price Category Relational Model Order-Product ProdNum (PK/FK) OrderNum (PK/FK)

12. Entity Modeling zRepresent each entity as a table zDetermine the attributes for each entity zDetermine the relationships among the entities

13. Definition: Schema Notation zTableName( {attributes} ) yPrimary keys are underlined or denoted “PK” yAlternate keys are denoted “AK” ySecondary keys are denoted “SK” yForeign keys are denoted “FK” Faculty(FacID, Name, Office, Dept (FK))

14. E-R Diagrams (P&A notation) Entities Primary Key (PK) Attributes (FK, SK) Attributes Table Name

15. E-R Diagrams (P&A notation) zRelationships: 1 to many DepartmentEmployee 1m DepartmentEmployee

16. E-R Diagrams (P&A notation) zRelationships: many to many StudentClass mn Student

17. Data Modeling