[PPT]Database Systems: Design, Implementation, and …H.Haddouti/DB_Implementation_case... · Web viewTitle Database Systems: Design, Implementation, and Management Subject Chapter

8

Chapter 8

The University Lab: Conceptual Design Verification, Logical Design,

and Implementation

Hachim Haddouti

2

8

Hachim Haddouti and Rob & Coronel, Ch7

In this chapter, you will learn:• How the Lab Management System modules are defined and

refined• How attributes and domains are identified and defined for

each of the entities defined in the initial E-R model• How the database transactions are identified and defined

within the system modules• That the design verification process uses modeling and

normalization techniques concurrently to find and eliminate data redundancies

• Review the steps of database implementation• Review the steps of database testing and evaluation• Review the steps of database operation

3

8


Completing Conceptual and Logical Design

• Detail Matters!– Tasks

• Entity relationship modeling and normalization• Data model verification• Logical design• Physical design• Implementation• Testing and Evaluation• Operation

– Primary modules• Lab Management System• Inventory Management System

4

8


Entities Identified

5

8


Completion of Conceptual Design• Refine module definition

– Entities– Attributes

• Normalization process– Discover new entities– Revise attributes

6

8


Lab Management System Module E-R Segment

7

8


USER Entity

8

8


LOG Entity

9

8


LAB_ASSISTANT Entity

10

8


WORK_SCHEDULE Entity

Table 8.7

11

8


HOURS_WORKED Entity

12

8


RESERVATION Entity

Table 8.9

13

8


Revised RESERVATION Entity

14

8


RES_SLOT (Weak) Entity

15

8


Inventory Management Module E-R Segment

16

8


INV_Type Entity

17

8


ITEM Entity

18

8


STORAGE Entity

19

8


LOCATION Entity

20

8


REPAIR Entity

21

8


VENDOR Entity

22

8


ORDER Entity

23

8


ORDER_ITEM Entity

24

8


WITHDRAW Entity Revision

25

8


WITHDRAW Entity and Revision

26

8


WD_ITEM (Weak) Entity

27

8


CHECK_OUT Design Revision

28

8


CHECK_OUT Entity

29

8


CHECK_OUT_ITEM (Weak) Entity

30

8


E-R Model Verification• Establishes

– Design reflects end user views of database– Database transactions defined and modeled so design

supports related requirements– Design meets output requirements– Design supports required input screens and data entry

forms– Design flexible to support future enhancements

• Verification identifies– Central entity– Each module and its components– Each module transaction requirement

31

8


Inventory Management Reporting Problems

• Generates three reports; one is inventory movement report– Inventory movements spread across different entities– Difficult to generate output and reduces performance

• Item “quantity on hand” updated with different inventory movements – Purchase, withdraw, check-out, check-in, or inventory

adjustment– Only withdrawals and check-outs represented in

model

32

8


Inventory Management Reporting Problems Solution

• Create new entity as common movement entry point

• INV_TRANS created– Standardizes inventory module interfaces– Facilitates control and generation of required

outputs

33

8


Inventory Transaction Process

Figure 8.25

34

8


INV_TRANS Entity

Table 8.26

35

8


TR_ITEM (Weak) Entity

36

8


Revised University Computer Lab ERD

37

8


Logical Design• Translates conceptual model to format for

selected DBMS• Sets stage for creating table structures, indexes,

and views• Table structures can be created with CREATE

TABLE SQL commands• Views created with CREATE VIEW SQL

Commands• Indexes created with CREATE INDEX SQL

Commands

38

8


Physical Design• Defines specific storage or access methods used by database• Includes estimate of storage space • Characteristics are function of DBMS and

operating systems

39

8


Implementation• Database administrator (DBA)

– Controls database management function– Defines standards and procedures required to interact with

the database– Adopts appropriate plan

• Plan elements– Definitions of processes and standards– Chronology of required activities

• Database creation• Loading and Conversion

– Documentation standards– Responsibilities for continued development and maintenance

40

8


Testing and Evaluation• Determine how well database meets goals• Ongoing process• Considerations

– Performance measures– Security– Backup and recovery procedures

41

8


Operation• Provides support for daily operations • Maintains operational procedures• Database maintenance and evolution

– DBA performs technical and managerial duties to ensure proper operation of database to support organizational mission

Documents

[PPT]Database Systems: Design, Implementation, and …H.Haddouti/DB_Implementation_case... · Web viewTitle Database Systems: Design, Implementation, and Management Subject Chapter