The University Lab: Conceptual Design Verification, Logical Design, and Implementation - PowerPoint PPT Presentation

Loading...

PPT – The University Lab: Conceptual Design Verification, Logical Design, and Implementation PowerPoint presentation | free to download - id: 56b144-ODE2M



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

The University Lab: Conceptual Design Verification, Logical Design, and Implementation

Description:

Database Systems: Design ... In this chapter, you will learn: How the Lab Management System modules are defined and refined How attributes and domains are ... – PowerPoint PPT presentation

Number of Views:157
Avg rating:3.0/5.0
Slides: 42
Provided by: RogerM93
Learn more at: http://www.radford.edu
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: The University Lab: Conceptual Design Verification, Logical Design, and Implementation


1
Chapter 8
  • The University Lab Conceptual Design
    Verification, Logical Design, and Implementation
  • Database Systems Design, Implementation, and
    Management, Fifth Edition, Rob and Coronel

2
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
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
Entities Identified
Table 8.2
5
Completion of Conceptual Design
  • Refine module definition
  • Entities
  • Attributes
  • Normalization process
  • Discover new entities
  • Revise attributes

6
Lab Management System Module E-R Segment
Figure 8.1
7
USER Entity
Table 8.3
8
LOG Entity
Table 8.4
9
LAB_ASSISTANT Entity
Table 8.5
10
WORK_SCHEDULE Entity
Table 8.7
11
HOURS_WORKED Entity
Table 8.8
12
RESERVATION Entity
Table 8.9
13
Revised RESERVATION Entity
Table 8.10
14
RES_SLOT (Weak) Entity
Table 8.11
15
Inventory Management Module E-R Segment
Figure 8.9
16
INV_Type Entity
Table 8.13
17
ITEM Entity
Table 8.14
18
STORAGE Entity
Table 8.15
19
LOCATION Entity
Table 8.16
20
REPAIR Entity
Table 8.17
21
VENDOR Entity
Table 8.18
22
ORDER Entity
Table 8.19
23
ORDER_ITEM Entity
Table 8.20
24
WITHDRAW Entity Revision
Figure 8.19
25
WITHDRAW Entity and Revision
Table 8.21
Table 8.22
26
WD_ITEM (Weak) Entity
Table 8.23
27
CHECK_OUT Design Revision
Figure 8.22
28
CHECK_OUT Entity
Table 8.24
29
CHECK_OUT_ITEM (Weak) Entity
Table 8.25
30
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
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
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
Inventory Transaction Process
Figure 8.25
34
INV_TRANS Entity
Table 8.26
35
TR_ITEM (Weak) Entity
Table 8.27
36
Revised University Computer Lab ERD
Figure 8.28
37
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
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
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
Testing and Evaluation
  • Determine how well database meets goals
  • Ongoing process
  • Considerations
  • Performance measures
  • Security
  • Backup and recovery procedures

41
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
About PowerShow.com