~Spring 2017~

CST363 Introduction to Database Systems

Class project

Courtney Dunbar
Jordan Horiuchi
Tejus Nandha
1:
Introduction
The Company we are studying is CodeA++, a small sporting goods chain that is interested in
automating their inventory system. They are a small organization with about 20 employees.
We will Beta test the DB in one store, and if all goes well, solution will be rolled out to the
rest of the stores in the chain. The company not only wants to keep track of
prices/brands/type/number of items in the store, they also want to start keeping what sports
people are most interested. If the problem is solved successfully and in a cost-effective
manner, this solution may be sold to the client for a negotiated price.

Identifying the Problem

There are many steps involved in the process of solving a client’s problem. The first step is to
help them in maintaining inventory, checking inventory, etc. Due to the rapid growth of the
company, many standard procedures used to perform these tasks are becoming insufficient to
meet the needs of the company and their clients. We conducted a Feasibility
Study/Requirements Analysis at CodeA++ and we determined that the inventory system was
the major area of concern. The management agrees that this area of their business requires
immediate attention and are seriously considering the conclusions of our Feasibility Study.
The old system was originally designed for a much smaller workforce, most of the operations
1
are done manually. However, recent growth and workforce expansion are proving the in-
place system inadequate, thus impeding efficiency, and resulting in relatively large project
delays, inventory wastage, and increased cost of maintenance.

Requirements
The first stage in designing a solution to this problem is to determine the requirements of the
new system. A complete analysis was performed and documented, this document is primarily
focused on data storage requirements

Functional Requirements
I. Details of data storage
a. Inventory Items
i. ItemNumber
ii. ItemDescription
iii. Cost of Item
iv. Product Name
v. Brand Name
vi. Total Count
b. Customer Details
i. Customer Id
ii. Last Name
iii. First Name
iv. Phone
v. Email
vi. Favorite Sport
c. Purchase
i. Invoice Number
ii. Invoice Date
iii. Pre-Tax Amount
iv. Customer ID
d. Detailed Order / Purchased Items
i. Invoice Number
ii. Invoice Line Number
ii. Item Number
iii. Retail Price

2
2: E-R Diagram

3: convert the ER diagram into normal form

● The database is well designed
o tables meet entity integrity and referential integrity
o all tables satisfy the third normal forms
● Queries of database provide answers for practical questions