1. TM 1 Dr. Chen, Business Database Systems Data Modeling Professor Chen School of Business Administration Gonzaga University Spokane, WA 99258

2. A Relationship Between the Organization and the DataBase Organization 1. Hardware 2. Software 3. Data 4. Procedures 5. People Picture Or Model Old State Events New State Activities DataBase Management Systems D.B. Transactions (Add, modify, delete, …) Correspond with the processing of the events Information must be: 1. Timely, 2. Accurate, relevant, and verifiable. 3. Presented in a useable form. User

3. TM 3 Dr. Chen, Business Database Systems Data Modeling The data model is a cornerstone for every information system, because it describes the entities that the system will create and maintain during its lifetime.

4. MODELING ENTERPERISE DATA Enterprise View Conceptual Data Models Business Needs Logical Models Physical Models ProductionSystem Congruent Satisfy Coporate strategies/ goals etc. Implement Maintenance

5. TM 5 Dr. Chen, Business Database Systems Data Modeling (Cont.) Building the data model is probably the most important activity during requirements definition, because in the process of understanding how the data is organized and identifying the relationships that exist between entities, you can discover most of the functionality that the system will satisfy.

6. TM 6 Dr. Chen, Business Database Systems Business Area of Data Model The data model of a business area tends to be relatively stable, compared, for example, to the set of operational procedures or organizational structure, which changes frequently. Therefore, basing the implementation of the future system upon a well-defined data model is a good first step towards developing a system that meets the real requirements of the users.

7. TM 7 Dr. Chen, Business Database Systems Techniques and Approaches Two techniques are used interchangeably to model the data of a system: –Entity relationship model (E-R/M) –Data normalization

8. TM 8 Dr. Chen, Business Database Systems E-R/M and Normalization E-R/M (and EE-R/M) aims at identifying the entities that are part of the system, the attributes that make up these entities, and the dependencies between entities. Normalization makes the data model created using the E-R more robust and extends the life of systems based on the model.

9. TM 9 Dr. Chen, Business Database Systems E-R and Normalization (Cont.) These two techniques go hand in hand and should be applied conscientiously during data modeling activities.

10. TM 10 Dr. Chen, Business Database Systems Approaches to Data Modeling Two approaches to data modeling: Ê Top-down Ë Bottom-up

11. TM 11 Dr. Chen, Business Database Systems Top-Down vs. Bottom-Up Approach Identify Entities Discover Relationship Define Attributes Identify Entities Discover Relationship Define Attributes Collect Data Analyze/synthesize Data TOP-DOWN Bottom-Up

12. TM 12 Dr. Chen, Business Database Systems Top-Down vs. Bottom-Up Approach Identify Entities Discover Relationship Define Attributes Identify Entities Discover Relationship Define Attributes Collect Data Analyze/synthesize Data TOP-DOWN Bottom-Up

13. TM 13 Dr. Chen, Business Database Systems Why Normalization? Remove the anomalies due to –lack of flexibility –ineffectiveness of data storage –inefficiency of data manipulation operations 3inserts (additions) 3deletes (deletion) 3updates (modification)

14. TM 14 Dr. Chen, Business Database Systems Denormalization and Why? Denormalization is the process of transforming normalized relations into unnormalized physical record specifications. A normalized form (e.g., 3NF) presents many important features, however, it may required that queries join terms from different entities more often than in a less normalized data model.

15. TM 15 Dr. Chen, Business Database Systems An example of Denormalization CUSTOMER... CITY STATEZIP CustID CITY ZIPSTATEZIP ? Normalization NO! STATEZIPCITY

16. TM 16 Dr. Chen, Business Database Systems Denormalization : CUSTOMER In a denormalized version of the CUSTOMER entity, ZIP, CITY, and STATE may be defined as attributes of the entity whose value is derived from entity ZIP and stored redundantly with the other address properties of each CUSTOMER.

17. TM 17 Dr. Chen, Business Database Systems New Business Rules To maintain the data consistency, new business rules should be implemented: ¶the values of attributes CITY and STATE will be updated only in the entity ZIP. In all other entities where these attributes are denormalized, applications may insert and select but not modify these attributes.

18. TM 18 Dr. Chen, Business Database Systems New Business Rules (cont.) · when the attributes CITY and STATE of entity ZIP are modified, the changes will be propagated in all the denormalized CITY and STATE attributes of other entities.

19. TM 19 Dr. Chen, Business Database Systems Un-normalization vs. De-normalization Unnormalized data model is little or no analysis is performed. Denormalized data model is derived from a model in the 3NF, after the reasons and impact of denormalizing some entities are identified and weighed.

20. TM 20 Dr. Chen, Business Database Systems Conclusion When parts of the data model are denormalized, the rules for maintaining the redundant data must be defined clearly and implemented programmatically, in order to avoid the anomalies discussed before.

21. TM 21 Dr. Chen, Business Database Systems Are you still...