Chicago Cars Case Study – Requirements

DESIGN AN APPLICATION FOR A COMPANY, “CHICAGO CARS”:

The company will:

– Sell Cars
– Run an Auto\Mechanic Shop
– Sell Parts (they have a database of parts)

SPECIFICATIONS

Sales Price, Date Sold, Customer #, Car ID (VIN #)
– Track Inventory of Cars
Car Info (VIN #, Stock #, Model, Make, Year, Color, Mileage, Location) [no images]
Two types of cars – Pre-owned and New
Multiple Locations
Requirement: Never delete car info once it is recorded (mark it as “not available”, track it with a “state”).

You do not have to implement the online forms – there is a website already for this dealer, someone fills in this form and it goes to a guy that enters the information into the database. It could be automated but we don’t have to. We are NOT building a web application (but we can, if we want to…).

TYPES OF USERS

1. Managers – Can do and see every record in the database [No access restrictions] Managers can do sales, and only they can enter sales information
2. Sales Reps can only:
o View and add customers [enter information]
o View inventory information [Can’t change it!]
Specifically: They can view everything, but can only add customer info

PARTS (INVENTORY)

Part #, Cost, Quantity (Don’t implement a “shopping cart” – Just want an inventory of parts).
Add, update, and delete parts
Add/update/delete customers, sales records, and inventory records (CRUD: Create, Read, Update, Delete on everything – given the security information we have!)

SAMPLE QUESTIONS

Can a customer update their own information?
When a sales record is registered, do we have to mark the car as sold?
Are there any states besides pre-owned and new?
Can a car be available for sale or not for sale (i.e. in the shop)?

Leave a Reply