SADM 5/ed – CASE STUDY 4 – Milestone 4: Data Model Normalization
Page: 4-1
MILESTONE 4 – DATA MODEL NORMALIZATION
 Synopsis
I
n this milestone you will normalize the data model created in Milestone 3, along
with additional data requirements, to be in third normal form.
 Objectives
After completing this milestone, you should be able to:
 Normalize a logical data model to remove impurities that can make a database
unstable, inflexible, and non-scalable.
 Prerequisites
1. Data analysis – Chapter 7
2. Milestone 3 Solution
 Assignment
The goal of this project is to normalize our logical data model to remove impurities
that can make a database unstable, inflexible, and non-scalable. Completely
normalize the data structure, ignoring the fact that the purchase order data is readonly data imported from another system and, therefore, could be left in a nonnormalized format.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 4 – Milestone 4: Data Model Normalization
Page: 4-2
 Activities
1. To construct an Entity Relationship Diagram to be in 3 rd Normal form, follow the
normalization procedure outlined in Chapter 7 of the SADM 5th ed. textbook. Use
the ERD solution of Milestone 3 as well as the data dictionary provided at the end
of this milestone to prepare the new data model. Make assumptions where
necessary.
Deliverable format and software to be used are according to your instructor’s
specifications. Deliverables should be neatly packaged in a binder, separated with a
tab divider labeled “Milestone 4.”
References:
Milestone 3 Solution
Provided by your instructor
IT Tracker Data Attribute Dictionary
Provided at the end of this milestone
Deliverables:
Logical Data Model in 3rd Normal Form:
Milestone’s Point Value:
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Due: __/__/__
Time:_______
_______
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 4 – Milestone 4: Data Model Normalization
Page: 4-3
IT Tracker Data Attribute Dictionary
Below is a Data Attribute Dictionary that contains all the attributes and definitions.
Most of the attributes in the dictionary were included in the fully attributed data
model from Milestone 3. However, Frank Baravelli discovered other attributes
during his fact-finding efforts. Note: The attributes below are listed in alphabetical
order, not necessarily by entity.
AssignToDept
ComponentDescription
ComponentID
ComponentNum
DateDelivered
DateInstalled
DateOrdered
DateRemoved
DeptID
DeptName
Description
EmpDept
EmpFirst
EmpID
EmpLast
EquipName
EquipNum
EquipType
InServiceDate
InstalledQuantity
POItem
ProblemDescription
PurchOrderID
PurchQuantity
ReportDate
ReportedBy
ReportedByExt
ReqNum
ResolutionDate
ResponseNum
SerialNum
10-character alphanumeric field holding the code of the department that the piece of
equipment is assigned to.
75-character alphanumeric field fully describing each type of component.
10-character alphanumeric identifier for each type of component (System, CPU, RAM,
Hard Drive, etc.).
A system-generated numeric value unique to each installed component.
Date field holding the date a purchase order was delivered.
Date field consisting of the date a component was installed into a piece of equipment.
Date field holding the date a purchase order was ordered.
Date field consisting of the date a component was removed from a piece of equipment.
10-character alphanumeric field identifying a department or other organizational unit.
30-character alphanumeric field with the department’s full name.
50-character alphanumeric field describing what was purchased with each line item of a
purchase order.
10-character alphanumeric field identifying the department of an employee placing a
purchase order.
30-character alphanumeric field consisting of the first name of an employee placing a
purchase order.
4-character number with leading zeros uniquely identifying each employee who could place
a purchase order.
30-character alphanumeric field consisting of the last name of an employee placing a
purchase order.
15-character alphanumeric field holding the identifying name for the piece of equipment
A system-generated numeric value unique to each piece of equipment.
10-character alphanumeric field identifying the equipment as PC, Printer, Scanner, etc.
Date field consisting of the date the piece of equipment was placed in service.
A numeric field specifying the quantity of items installed as an Equipment Component. An
inspection of past forms shows no quantity exceeding 50.
A system-generated numeric value unique to each line item on a purchase order.
200-character alphanumeric field describing the service request problem.
7-digit numeric field formatted as ####-### uniquely identifying each purchase order.
A numeric field specifying the quantity of items purchased on one line of a purchase order.
An inspection of past forms shows no quantity exceeding 50.
Date field holding the date a service request was reported.
50-character alphanumeric field holding the first and last name of the person reporting a
service request.
4-character number with leading zeros of the telephone extension of the person reporting a
service request.
A system-generated numeric value unique to each service request.
Date field holding the date a service request was resolved.
A system-generated numeric value unique to each response to a service request.
20-character alphanumeric field containing the serial number of an installed component.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001
SADM 5/ed – CASE STUDY 4 – Milestone 4: Data Model Normalization
SupplierAddress
SupplierCity
SupplierContact
SupplierEmail
SupplierFax
SupplierID
SupplierName
SupplierPhone
SupplierPostalCode
SupplierSt
TechFirst
TechID
TechLast
UnitCost
WorkComments
WorkDate
Page: 4-4
50-character alphanumeric field holding the supplier’s street or box address.
20-character alphanumeric field holding the name of the supplier’s city.
50-character alphanumeric field holding the first and last name of the supplier’s contact
person.
50-character alphanumeric field consisting of the supplier contact’s e-mail address.
10-digit field consisting of the supplier’s fax number.
6-character alphanumeric field uniquely identifying each supplier.
30-character alphanumeric field holding a supplier’s company name.
10-digit field consisting of the supplier’s telephone number.
10-character alphanumeric postal code of a supplier.
2-character alphanumeric abbreviation of the supplier’s state.
30-character alphanumeric field consisting of a Tech employee’s first name.
4-character number with leading zeros uniquely identifying each Tech employee.
30-character alphanumeric field consisting of a Tech employee’s last name.
Numeric field holding the per-unit cost of each line item of a purchase order. An inspection
of past forms shows that unit costs must hold data up to 9999.99 and include two places to
the right of the decimal point.
100-character alphanumeric field describing the work done in response to a service request.
Date field consisting of the date of a response to a service request.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 5ed
by J. L. Whitten, L. D. Bentley, & K. C. Dittman
Copyright Irwin/McGraw-Hill 2001