7

Chapter 7

The University Lab: Conceptual

Design

Hachim Haddouti
 7

In this chapter, you will learn:

• how to conduct a database initial study.
• to identify and develop business rules for
database design.
• to learn how to develop a conceptual database
design.
• How to translate the business rules into ERD
segments
• To develop an initial E-R model.
• How to put the ERD segments together to create
the initial ERD

Hachim Haddouti and Rob & Coronel, Ch7 2

 7

Database Initial Study

• Checklist
– Organizational
• Objectives
• Structure
• Operations
• Problems
– System
• Objectives
• Scope and boundaries
• Information sources and users
• End-user requirements

Hachim Haddouti and Rob & Coronel, Ch7 3

 7

UCL Database Initial Study

• Users
– Assistant Dean, College of Business
– Computer Lab Director
– Computer Lab Assistants
– Computer Lab Secretary
– Computer Lab Graduate Assistants
• Objectives
– Provide users with controlled access to UCL
assets
– Guide users working with assets and provide
problem-solving services

Hachim Haddouti and Rob & Coronel, Ch7 4

 7
UCL’s Organizational Structure

Hachim Haddouti and Rob & Coronel, Ch7 5

 7

UCL Description of Operations

• Inventory, storage, order management
– Classifications: hardware, software, literature,
supplies
– Serialized vs. nonserialized items

Hachim Haddouti and Rob & Coronel, Ch7 6

 7
UCL Description of Operations (con’t.)

• Equipment maintenance and repair management

– Information kept in Bad Equipment Log and Hardware
Returned for Service Log
• Equipment check-out and check-in management
– Form completed when equipment checked out
– Notice sent for late equipment
• Lab assistant payroll management
– Time sheets used to track assistants
– Hourly basis for a fourteen day period
• Lab reservation management
– Faculty member completes reservation form with date, time,
department, and course number
• Computer lab access management
– Lab users sign users’ log and leave University ID card

Hachim Haddouti and Rob & Coronel, Ch7 7

 7

Common Problems and

Constraints in Current System
• Never up to date and error-ridden
• Too much data duplication and inconsistency
• Does not generate useful information
• Does not allow ad hoc queries
• CLD spends too much time processing data
manually
• Lack of computerization makes inventory
management difficult

Hachim Haddouti and Rob & Coronel, Ch7 8

 7

Specific Problems

• Inventory/Storage/Order Management
– No access to crucial inventory management data
for CLD
– UCL needs available stock figures & average use
of supplies
– CLD does not know item location
• Equipment maintenance and repair management
– CLD cannot generate history for equipment
– CLD determine the status of items subject to
maintenance procedures

Hachim Haddouti and Rob & Coronel, Ch7 9

 7
Specific Problems (con’t.)
• Equipment check-out/check-in management
– CLD lacks information about lab assets
• Lab assistant payroll management
– CLD spends too much time summarizing hours
worked LAs
– CLD cannot estimate work loads
• Lab reservations management
– Manual reservation system inadequate
– No statistical information for scheduling lab
reservations
• Computer lab access management
– User log not properly maintained
– Certain items not returned
– Security problems
Hachim Haddouti and Rob & Coronel, Ch7 10
 7
Constraints for UCL
• Time Frame
– Operational within 3 months
• Hardware and Software
– Use existing UCL hardware and software
• Distributed Aspects and Expandability
– Operate in multiuser environment
– Independent of existing administrative systems
• Cost
– Development costs must be minimal
– Use no more than two additional terminals
– Operate without additional personnel
– $9,500 is available

Hachim Haddouti and Rob & Coronel, Ch7 11

 7

System Objectives for UCL

• General System Objectives
– Improve operational efficiency
– Provide useful information for planning,
control, and security
• Specific Objectives
– Inventory/Storage/Order Management
• Better purchase order control
• Monitor supply item stock
• Control inventory by type and item
• Quick information about item location
• Timely information about use of supplies and
generate stats to aid in future purchases
Hachim Haddouti and Rob & Coronel, Ch7 12
 7

Specific Objectives for UCL (con’t.)

• Equipment maintenance and repair management

– Monitor maintenance histories
– Track items returned to vendor
• Equipment check-out/check-in management
– Tracks items checked out
– Monitor item check-out time
– Generate usage statistics
• Lab assistant payroll management
– Scheduling and work loads
– Work summaries

Hachim Haddouti and Rob & Coronel, Ch7 13

 7

Specific Objectives for UCL (con’t.)

• Lab reservations management

– Decrease reservation processing time
– Produce reservation schedules
– Generate statistical summaries
• Computer lab access management
– Control users and lab resources
– Reduce sign-in time
– Provide peak use information for scheduling

Hachim Haddouti and Rob & Coronel, Ch7 14

 7

Scope and Boundaries

• What will be system’s extent?
– UCL portion of organizational chart
– Independent of other systems
• What operational areas are covered by system?
– Limited to six areas addressed earlier
• What design/ implementation strategy to use?
– Organization into system modules
• What modules should be included in system?
– Lab management
– Inventory management
• How do modules interface?
– Through CHECK_OUT module

Hachim Haddouti and Rob & Coronel, Ch7 15

 7
Modules and Interfaces

Hachim Haddouti and Rob & Coronel, Ch7 16

 7
Conceptual Design Phase
Confirmation of good data sources

Hachim Haddouti and Rob & Coronel, Ch7 17

 7

Conceptual Design:
General Systems Requirements
• Easy to use
• Provide security measures
• Fully integrated
• Able to access system concurrently
• Perform various functions
– Personnel, inventory, order, maintenance,
reservation, Check_out, and access
• Input driven by output

Hachim Haddouti and Rob & Coronel, Ch7 18

 7
Conceptual Design Phase: User Needs

Hachim Haddouti and Rob & Coronel, Ch7 19

 7
Conceptual Design
Phase: Initial Entities

Hachim Haddouti and Rob & Coronel, Ch7 20

 7

Business Rule 1

Hachim Haddouti and Rob & Coronel, Ch7 21

 7
Business Rule 2

Hachim Haddouti and Rob & Coronel, Ch7 22

 7
Business Rule 3

Hachim Haddouti and Rob & Coronel, Ch7 23

 7

Business Rule 4

Hachim Haddouti and Rob & Coronel, Ch7 24

 7

Business Rule 5

Hachim Haddouti and Rob & Coronel, Ch7 25

 7

Business Rule 6

Hachim Haddouti and Rob & Coronel, Ch7 26

 7

Business Rule 7

Hachim Haddouti and Rob & Coronel, Ch7 27

 7
Business Rule 8

Hachim Haddouti and Rob & Coronel, Ch7 28

 7
Business Rule 9

Hachim Haddouti and Rob & Coronel, Ch7 29

 7

Business Rule 10

Hachim Haddouti and Rob & Coronel, Ch7 30

 7
Business Rule 11

Hachim Haddouti and Rob & Coronel, Ch7 31

 7

Business Rule 12

Hachim Haddouti and Rob & Coronel, Ch7 32

 7
Business Rule 13

Hachim Haddouti and Rob & Coronel, Ch7 33

 7
Business Rule 14

Hachim Haddouti and Rob & Coronel, Ch7 34

 7

Business Rule 15

Hachim Haddouti and Rob & Coronel, Ch7 35

 7
UCL Entities Considering Business
Rules

Hachim Haddouti and Rob & Coronel, Ch7 36

 7
Initial ERD for UCL

Hachim Haddouti and Rob & Coronel, Ch7 37