Carmax Inventory

[DOCUMENT System
TITLE]

PCEDUTECH2
[COMPANY NAME] [Company address]

1
 Table of Contents

Title Page Number

Project Overview 3
Letter of Consent 4
Systems Vision Document 5
Systems Request 6
Feasibility Analysis 7

Preliminary Project Plan 9

I) Project Time Frame 10
II) Work Breakdown Structure 11
III) Responsibility Assignments 12
IV) Gantt Chart 13
V) Staff Plan 14
VI) Project Charter 15
VII) Project Standards 16
VIII) Risk Assessment 17

Preliminary Fact-Finding 18
IX) Existing Systems Review 19
X) Interview Questions 19
XI) Survey Questionnaire 20

Detailed Fact-Finding 21
I) Key Stakeholders 22
II) Interview Questions 23
III) Question Survey 24
IV) Observation of Work Processes 26
V) Use Case Descriptions 28
VI) Systems Diagrams 32
System Acquisition Strategy 37
I) Alternative Matrix 38
Environment Design 39 - 40

Application Architecture 41 - 42

User Interface Design 44

III) User Interface Design Overview 45
IV) Graphical User Interface Design 46
V) Storyboard & Dialog Design 47
VIII) Input and Output Design 51
Software Design 53
IX) Structure Chart 54
X) Program Specification 55
XI) Pseudocode 58
Database Controls & Security Design 59
I) Input Controls 60
II) Output Controls 61
III) Security Controls 61
IV) Disaster & Recovery Plan 62
References 63

2
 Detailed
Fact-Finding

3
I) Key Stakeholders
The key stakeholders are the ones who are greatly affected or have an effect on the new
system. For CarMax the key stakeholders are the Inventory Associate, M.I.S. Department, and
Operation Manager. Each stakeholder affects the system in their own way and this can be seen
in Figure 2A below.
Inventory Associate Overview:
The Inventory Associate uses information from
the system to get a snapshot of the current
inventory volume for the location, also the
current location of the vehicles. It also aids in
future decision making geared towards
improving the facility turnover.

Stakeholder Type:
Internal Assists with internal issues.

Interaction:
Secondary authority figure with interaction at
all levels.

M.I.S. Department Overview:

The M.I.S. Department uses the system daily
to check for errors and to maintain the system.

Stakeholder Type:
External Regularly interacts with system and
overseas internal maintenance of the system
at the corporative level.

Interaction:
Secondary authority figure with interaction at
all levels.

Operations Manager Overview:

The Operation Manger uses information from
the system on a daily basis to create reports
which reflect the current status of the facilitys
operations.

Stakeholder Type:
Internal Regularly interacts with system and
overseas internal operations at the facility.

Interaction:
Total authority figure with interaction at all
levels.

Figure 2-1 Key Stakeholders

4
II) Interview Questions

Interview Questions

1) What are the current needs that you would like us to address with
upgrading your current system?

Answer: The current need for a software update for our company is something
that will allow us to quickly check in vehicles that we receive and see if they have
a processed title or not. This would allow us to know if the vehicle can be sold by
working on right away or needs to be sent to our waiting lot to wait on the title to
clear. We also need a better tracking system for the vehicles while they are on
the lot since they are moved throughout the day to different departments to be
worked on, cleaned, or test drove.

2) What kind of features is your company looking to have for users,

auditing, or tracking vehicles?

Answer: We are looking for a user friendly system for the different departments
can use to quickly check status on the different vehicles by showing title
information so vehicles can be worked on. We would also like a system that
better tracks the movement of vehicles on the lot that will give up to date location
on the vehicle and can show the history of the vehicle movement while on the lot.

3) How often do you want the system to update the location of each
vehicle? Hourly or by movement around the lot?

Answer: We would like to see a real time location on the vehicles. We would like
to be able to pull up the software and see the vehicle moving on the lot if it was
being moved between departments..

4) What are the year cost of maintaining your current system?

Answer: Our current upkeep cost is around $200,000.

5) How much money are you looking to invest in updating the system
Company wide or by location?

Answer: Company Wide we are looking to invest around two million dollars on a
system and around $50,000 per location in hardware installments.

5
6) Would you like a user test base for this project?

Answer: We would like to use a small volume location and a high volume
location. We are going to use about 50 employees and supervisors.

7) How many locations would you use?

Answer: Two locations.

8) What size of location?

Answer: We would like to use a $2 million volume and a $15 million volume size
location.

9) Volume of movements at each location?

Answer: The smaller location repairs and sells about 200 vehicles a month and
the larger location can handle around 1,000 vehicles a month.

10) Who will be your user test base?

Answer: We would like to use test people from all departments at the sites as
well as district managers that would visit the sites for checkups and audit
reasons.

11) Which departments will be involved as users of the system?

Answer: The system for the most part is utilized by the Inventory department but
it has particular elements which affect the Sales and Buying department. Such
implications include the list of newly saleable cars which will automatically be
displayed on the Carmax website. Also it will interact with the prioritizing of cars
purchased by individual customers.
Figure 2-2- Interview Questions

III) Survey Questionnaire

By using a simple survey we can gather information from different user. The users can suggest
improvement to the tracking software, along with what kind of interface users would like to use
when inputting title information.

6
Figure 2-3- Questionnaire

Figure 2-4- Questionnaire Results

7
IV) Detailed Observation of Existing Work Processes
Carmax opens at 6am daily
Monday-Saturday and 11am-7pm
on Sunday. The work processes in
the inventory department which is
the system that we are working to
improve on, begins with a
Reconciliation Report. This online
application consist of an asset
protection virtual inspection of every
item in the system with hopes of
identifying any inconsistencies. This
would include finding all cars which have never been scanned, i.e. newly bought vehicles from
patrons and cars already received which were missed during the last scan. The last phase of
the report includes revisions to locations of current cars and requires any vehicles parked in the
wrong zone or parked correctly, but without necessary work lines, to be updated.

While the Operation managers would normally arrive at 6am he wouldve not have first contact
with the system until around 10am once the Reconciliation Report is complete. After performing
an audit of the report confirming that all information is correct this is presented in a manager
meeting by 11am. Not only is this information used to make sure no vehicle is lost or taken off-
lot without being accounted for, but also so that current vehicles can be prioritized to allow shop
workers to know which vehicles needs which labor.

The changing role being

implemented in the work process
from the existing system does not
come into play until midday during
two important protocols after
vehicles have already been
received. The first change occurs in
the initial inspections which would
determine what work to do on each
vehicle specifically, where the new
system will input updatable location
tags to each vehicle that will follow the car as it travels throughout the lot. The second stage
occurs in the prioritizing process where vehicles in the new system will be analyzed and tested
against the criteria of having completed title and recall work done so that these vehicles can be
worked on first. The issue with the existing system is seen as there is no way of determining
which vehicles have titles, upon coming across a vehicle being flagged for failing this test it will
be then be put into a holding area until the title clears. This outdated process creates
redundancy because then after the information becomes available these cars will 1) Show up as
a concern on the reconciliation report and 2) Will need to be removed to the saleable zone.

8
 After all work has been
completed a final
inspection on each
vehicle is begun to
determine if standards
have been met, this is
done by any inventory
associate and would
only need the
intervention of the
operations manager if
theres a dispute
where standards are
unclear or where any
vehicle damage is
reasonably accepted based upon the age of the car. All failed cars are then sent to be
reworked, while passed cars are sent to the front sale lot where the system simultaneously
updates all information to the online website including newly taken pictures.

9
Use Cases

10
V) Use Cases
The use cases below show the processes that produce the output results. A trigger event is
needed in order to initiate the actions performed by CarMax.

Use Case Name: Vehicle processing

Actors: Employee, Seller, Operations manager

Brief Description: In order to have cars for sale, CarMax either buys cars
from wholesale auctions or individual customers.

Triggering event: CarMax needs inventory of cars to sell.

Pre-conditions: 1. Seller brings their car in for appraisal.

2. CarMax goes to wholesale auctions to look for
vehicles.
3. Seller proves ownership of vehicle.

Normal Course: 1. Customer gets appraisal offer valid for 7 days.

2. Customer will accept or reject offer.
3. Vehicles purchased at auction are shipped to CarMax
location.
4. RFID attached to vehicle.

Post-conditions: Vehicles information is recorded in system database and

inventory is organized.

Exception 1. Seller does not have necessary required

Conditions: documentation and is turned away.
2. Vehicles bought at auction if repairs are too costly
or have unspecified issues are sent to Operations
manager.

11
Use Case Name: Approved vehicles

Actors: Inventory Employee, Mechanic, operations manager.

Brief Description: Before CarMax does anything to the car, the vehicle is
inspected to determine whether it will meet CarMax
standards.

Triggering event: The system needs to know how much work the vehicle
needs.

Pre-conditions: 1. Work order are pulled and prioritized

2. Employee will group the vehicle by price point.
3. Vehicles that require no repair are sent to be
detailed.

Normal Course: 1. Shop department receives work orders and begins

work.
2. Ensures the car has 2 keys.
4. Work that cannot be done in-house are sublet to
outside contractors

Post-conditions: The vehicles are moved to the appropriate repair

location.

Exception Conditions: 1. If vehicle repairs are too costly, sent to operations

manager for final decision
2. Vehicles too old or with too many miles are sent to
operations manager for final decision
3. Vehicles that meet standards but are considered
high risk are designated as value max and set apart
from other vehicles.

12
 Use Case Name: Rejected Vehicles

Actors: Inventory Employee, Mechanic, operations manager.

Brief Description: Vehicles that either do not meet standards or are not
worth the repairs needed are sent to the operations
manager to determine their return or sale at auction.

Triggering event: All open repair lines are closed out.

Pre-conditions: 1. In-depth inspection shows car is too old or has too

many miles to be sold on front lot.
2. Operations managers determine price point and
cap spending on each vehicle.

Normal Course: 1. Vehicles with unspecified repairs are arbitrated with

wholesale vendors.
2. Single patron vehicles are sent to in-house
auctions.
3. Car receives final inspection against CarMax
standards.

Post-conditions: 1. If vehicle has no titles, its placed in a no title zone.

2. Vehicle documentation is sent back to wholesale
vendor.

Exception Conditions: Operation manager overrides failures and initiates

repair work.

Figure 2-5- Use Case Descriptions

13
 Data Flow Diagrams

VI) Context Diagram

The context diagram below shows the entire system overview, outlining the vehicle inventory
process. It also sets up the foundation for the level 0 and level 1 diagram.

Figure 3-1- Context Diagram

14
VII) Level 0 Diagram
The level 0 diagram is based off of the context diagram. It is the typical inventory process
model that is used at the moment by CarMax.

Figure 3-2- Level 0 Diagram

15
VIII) Level 1 Diagram
The level 1 diagram is also based off of the context diagram and the level 0 diagram, but it has
the added information needed for the improved inventory process model.

Figure 3-3- Level 1 Diagram

16
IX) Entity Relationship Diagram
The ERD Diagram below shows the overview of the initial inventory operation for CarMax. It
illustrates the needed information that the system requires in order to be upgraded from the
current system.

Figure 3-4- Entity Relationship Diagram

17
X) Gantt Chart
The Gantt chart which illustrates the start and finish times of each task needed to be complete
for the project. The chart also breaks up each task further by showing the relevant resource(s)
and responsible party for completing each task. The chart also outlines the duration of the entire
project in the terms of days.

Figure 3-5 - Gantt Chart

18
 System
Acquisition
Strategy

19
I) Alternative Matrix
In the figure below, it shows the alternative matrix used to compare and contrast the different
solutions that might be implemented into the new CarMax system. The system that results in the
highest score will be the best one for CarMax to use. After analyzing the matrix, it can be seen
that new system appears to be the best solution for CarMax.

Figure 4-1 - Alternative Matrix

20
Environment
Design

21
I) Environment Design
Everything at CarMax deals with technology. Their daily operations all involve accessing
computers in order to receive the car information, and place all the data into the software for
easy access. Not all employees deal with the receiving cars part of the system so not many
computers will be needed for this system. In order for operations to work well when
implementing the new software, there has to be good wireless connections in place for the
updates on the system to show up immediately. A worker would be able to access the
information about the cars without the Wi-Fi, but would not be convenient because that
information will be considered not up to date due to the fact that it has not updated. Two
desktop computers would be ideal with the inclusion of at least two tablets in order for there not
to be a lack of available systems. Since the new system being integrated will have a tablet
mode, it is a great way to integrate CarMax into the benefits of using tablets in order to be able
to do things remotely. CarMax uses Windows at the moment, but if they were to change to
another operating system they could do so without any loss because the system is reliable on
all other operating systems whether it is Apple OS X, Linux, etc. All the routers, firewalls,
computer servers, and desktops are in place, the only things that would need to be added are
the new tablets.

22
Application
Architecture

23
II) Application Structure
The application structure is used to display how each component of the new system must work
together in sequence in order to perform the desired functional and roles outlined. Also this will
identify necessary hardware security criteria that the system will use.

Figure 4-2 - Application Structure

24
Type of Requirement Definition Example
Motorola MC9090-G -
Technical Environment Special hardware, software and Wi-Fi - 3.8"
Requirements network requirements imposed by System should be able
business requirements to connect to CarMax
network and servers.
System would need a
computer with Windows
2007 or newer to run
application.
All changes made in
database should be
shared with other
computers on network.

System Integration The extent to which the system will The system should be
Requirements operate with other systems able to integrate with
different printer types to
print forms or
automated text.
System can operate
with all computers on
server separated by
department credentials.

Portability The extent to which the system will New system will adopt
Requirements \ need to operate in other portable component to
environments track inventory and
reference vehicle
information.

Maintainability Expected business changes to which Horizontal integration to

Requirements the system should be able to adapt all CarMax stores.
Expansion of security
database to withstand
growth.
Figure 4-3 - Operational Requirements

25
User Interface
Design

26
III) User Interface Design Overview
The figure below describes each portion of the user interface design.

Principle Description

The interface should have areas on the screen that are

Layout used for processing, managing, and updating vehicle
information. There should also be an area towards the
middle of the screen that allows information to be inputted
or outputted.

Content In order for users to effectively utilize the system, they

Awareness should always be aware of where they are in the system
and what type of information is being shown.

The systems visual facets should be easy enough for the

Aesthetics users to navigate their way around but still be functional.
With careful use of coordinated colors, white space and
fonts the system should not lose the user's focus. The
information should all fit on the screen without being too
squished.

Each user of the system will have a different perspective of

the systems design and will have different favor or vice
User Experience about the system. For those who use the system more
frequently would be more inclined for simpler, quicker
system design while those who use the system sparingly
will prefer an easier learning.

Designing the system using familiar layouts from the

Consistency original version will vastly ease the use of the system for
users. This will also make learning to use the new system
easier, since the layout for the new functions is something
they are already familiar with, thus increasing efficiency.

Minimize user The system design should be simple for users. Its design
effort should allow users to have a quick and efficient interaction
with the system regardless of computer experience.
Figure 4-4 User Interface Design Overview

27
IV) User Interface Design
The figure below shows the rough draft for the design of the user interface on the new system.

Figure 4-5 User Interface Design

V) Handheld Device Design

The figure below shows the rough draft for the design of the handheld device interface of the
new system.

Figure 4-6 - Handheld Device Design

28
VI) Storyboard and Dialog Design Add a title check box
in this area. This will
a) Storyboard indicate if the vehicle
has a title or is still
waiting for the title to
come in.

Title

RFID
Locati
on

Figure 4-7 - Storyboard Design

Adding a location box
will help the system
keep check of the
vehicles physical
location on the lot.

29
 This will be the new system
layout, with a titles column that
will indicate if the vehicle has a
title or not. This will help the
employees prioritize the vehicles
that can be worked on.

Vehicle Prod Recd Stock # Status Technician Activity Zone Zone Dur Total Dur RO# CIW Title
12Altima V 13093237 UNA FQC 0D5H 8D20H 618177 X Y
11Cooper V 13093251 UNA FQC 0D0H 13D22H 618262 X N

Figure 4-8 - Second Storyboard Design

30
VII) Dialog
Below is a dialog of the conversation that takes place to start the processes of the new system.

New Patron

Patron: Hi, Im looking for a new car mine has just been causing me too many problems lately.

Receptionist: Hello, were sorry to hear that well we would be happy to help you. First we want
to get your vehicle appraised by one of our trained senior buyers so that you can get the
absolute highest value for your car that its worth. In order to go forward, we need to get some of
your information and the vehicle registration to prove ownership.

Patron: (Turns in application)

So what exactly are the buyers looking at when they are appraising the car, cause I know it's a
little dirty but it's a great car.

Receptionist: (reviews info)

Well sir I can assure you CarMax strives to provide the most mechanically sound and safest
vehicle we possible can to each and every customer we meet. In order to do that we perform all
repair and detailing in-house so that you arent losing value on your car for minor issues. What
we are looking at is the mechanical codes on the car, the year, mileage, and leaks and noises.
Your Application is processed and we have an appraisal price for your vehicle good for 7 days.

Patron Vehicle Search

Situation 1:

Patron: (enters CarMax)

Good Morning, I was looking online and I saw a car I was interested in. It said it
was in stock at this location could I take a look at it.

Receptionist: Good Morning, sure we would be happy to locate that vehicle for you, may I have
your info and the stock number of the car you were interested in.

Patron: (Hands ID)

Yes I do it was a 2015 Corvette and the stock number said 13092412
Receptionist: (Pulls up inventory database)
Great I was able to find that vehicle which we do have here, I have all the vehicle information
along with 20 all around photos of the car if you want to check for a specific feature or if you
want to go check it out it says it was last scanned to row A1 so we can go right there.

31
Prioritizing Inventory Inspection
Situation 2:

Salesman: Good Morning, I have a customer who is having a car transferred to this store today
and I want to know if the car is here and ready to sell?

Inventory Associate: Hey, no problem Ill check it out for you do you have the stock number to
the vehicle that is getting transferred here.

Salesman: Yes I have it right here its 12903455

(Pulls up Inventory database)

Inventory Associate: Ok so I see that car right here which is for customer Williams, Sarah
actually it arrived this morning but it has not been made salable yet so hold off on informing the
customer.

Salesman: Do know how long until I can sell the car?

Inventory Associate: Well Im checking the repair lines and it says the car needs to have a 2nd
key made, but I can override this if the customer wants to come right away.

Salesman: That sounds great Ill tell the customer right away cause I think they leave out of
town today so I know they would want the car as soon as possible.

Inventory Associate: All right Ill put a sale hold on the vehicle so that another customer
doesnt take it on a test drive when Mrs. Williams comes to look at the car.

Salesman: Thanks, Ill call her now.

32
VIII) Input and Output Designs

a) Input
Type of Validation When to use Notes

Completeness When several fields Before moving onto the next

Check must be entered before step all the information
Ensures that all the form can be needs to be filled out.
required data has processed.
been entered

Format Check When fields are numeric The data in the fields should
Ensures that data or contain coded data match the format and be
are of the right checked.
type. Ex: License plates with a
specific amount of letters and
numbers.

Range Check With all numeric data, if Range checks should ensure
Ensures that possible that the numbers being
numeric data are entered are between correct
within correct min values.
and max values.

Check Digit When numeric codes Digit checks are numbers

Check are used added to a code as a way to
Check digits are quickly confirm correctness.
added to numeric
codes

Consistency When data are related Separate fields should be

Checks available for related data to
Ensure that help ensure little confusion.
combinations of Ex: Vehicle type matches
data are valid. brand.

Database Checks When data are available Data inputted should be able
Compare data to be checked. cross-reference information
against a to ensure there is no
database (or file) repetitions or
to ensure that they inconsistencies.
are correct.
Figure 4-9 - Input Design

33
 b) Output

Type of Report When to use Notes

Detail report When user needs full This report is generated

Lists detailed information usually when there is a need
information about about the items to know the full status of the
all the items vehicle.
requested.

Summary report When user needs brief This report is done when
Lists summary information on many items are matching some
information about items criteria, but it can relate back
all items. to the complete database.
Ex: when a batch shipment
comes in for vehicles in the
shipment.

Turnaround When a user (often a This document is used when

document customer) needs to there is need to change or
Outputs that turn return an output to be update information already
around and processed in the system.
become inputs. Ex: when vehicles are
finished with repairs.

Graphs When users need to Detailed graphs are useful to

Charts used in compare data among compare and illustrate the
addition to and several items topics that they are covering.
instead of tables They can show changes that
of numbers. are done throughout the
process.

Figure 4-10 - Output Design

34
Software
Design

35
IX) Structure Chart

Figure 5-1 - Structure Chart

36
X) Program Specification

Listed below are the modules outlines for each module in detail to provide the programmers with
enough detail to write the code for that particular module. The figures below portray this for the
new system.

Program Specification 1.1 CarMax System

Module: 1.1
Name: Single Patron Vehicle Appraisal
Purpose: Gathering vehicle information
Programmer: John Doe
Date Due: October 11, 2016.

Events:
Search box is selected.
Input Vin: Vehicle Vin, Make, Model, Year, Mileage, RFID/Inventory Number, Title
Type: CHAR (16), VARCHAR (30), VARCHAR (30), CHAR (4), CHAR(9), CHAR (8),
VARCHAR(3)
Provided By: Program 1.1

Output Name: Vehicle Vin, Make, Model, Year, Mileage, RFID/Inventory Number, Title
Type: CHAR (16), VARCHAR (30), VARCHAR (30), CHAR (4), CHAR(9), CHAR (8),
VARCHAR(3)
Used By: Program 1.1

Pseudocode:
(Single Patron module)
ENTER vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
READ vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
SAVE vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
DISPLAY vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num,
title
END

37
 Program Specification 1.2 CarMax System
Module: 1.2
Name: Batch Vehicle Inspection
Purpose: Initial Inspection of Auction Purchased Vehicles
Programmer: Jane Smith
Date Due: June 15, 2016.

Events:
Search box is selected.

Input Name: Vehicle Vin

Type: CHAR (16)
Provided By: Program 1.2

Output Name: Vehicle Vin, Make, Model, Year, Mileage, RFID/Inventory Number, Title
Type: CHAR (16),VARCHAR (30), VARCHAR (30), CHAR (4), CHAR(9), CHAR (8),
VARCHAR(3)
Used By: Program 1.2

Pseudocode:
(Batch Vehicle module)
READ vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
FOR all vehicles in inventory database
END FOR
END

38
 Program Specification 1.3 CarMax System
Module: 1.3
Name: Reports
Purpose: Create and print reports
Programmer: Agent Black
Date Due: July 15, 2016.

Events:
Reports button is clicked.
Report type is selected.

Input Name: Report_type

Type: CHAR (20)
Provided By: Program 1.3

Output Name: Report

Type: CHAR (30)
Used By: Program 1.3

Pseudocode:
(Reports module)
READ report_type
IF report_type = Daily New Patron Vehicle THEN
CREATE daily_patron_vehicle_report
ELSE IF report_type = Batch Vehicle Deliver THEN
CREATE batch_deliver_vehicle_report
END IF
SAVE report
DISPLAY report
END

39
XI) Pseudocode

(Single Patron module)

ENTER vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
READ vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
SAVE vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
DISPLAY vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
END

(Batch Vehicle module)

READ vehicle_vin,make, model, model_year, vehicle_mileage, RFID_inventory_num, title
FOR all vehicles in inventory database
END FOR
END

(Reports module)
READ report_type
IF report_type = Daily New Patron Vehicle THEN
CREATE daily_patron_vehicle_report
ELSE IF report_type = Batch Vehicle Deliver THEN
CREATE batch_deliver_vehicle_report
END IF
SAVE report
DISPLAY report
END

40
Database
Controls &
Security
Design
41
I) Input Controls
The figure below shows one of the ways that information could be inputted into the system. The
worker will have to pull up the software and click through the appropriate tabs to reach the
particular search query they are looking for. Once they have reached the indicated area, they
can choose what search method to look up the vehicle information from the available methods;
search by name, company, phone number, repair order number, stock number, license
plate/state, or the last six digits of the vehicles vin number. In the example below, the worker
wants to search by stock number, so the search criteria requires them to put a stock number
and then they can click search.

Figure 5-2 - Input Control

42
II) Output Controls
Once the search is made, a new page pops up with the wanted search. All the information
needed about the vehicle information will be displayed on this page if the search was inputted
correctly. If the information wanted was not the one the worker was looking for, it is most likely
due to human error, therefore a new search should be performed. The system should not take
more than seven seconds to pull up the information being searched.

Figure 5-3 - Output Controls

III) Security Controls

In order to access or place any information into the system, workers needs to log on to the
desktop or tablet with their own credentials. Without these credentials, no one else is able to log
onto the systems. CarMax has to be careful with their system since there are many customers
who need to input their social security number in order to receive the credit report, and when
receiving the vehicles, the previous owners need to place personal information as well. Because
of this, CarMax has a first-rate security system already in place with IT workers who make sure
no one hacks into their servers. All desktop computers have antivirus and malware protection
software that help prevent viruses from going into their systems and eliminating any risk of
having to reboot a computer due to the virus.

43
IV) Disaster and Recovery Plan
For any unpredictable disasters that might occur, CarMax backs up their information into a
secure server offsite. These backups happen as often as every eight hours for newly inputted
information to a mass backup every week to ensure that no data is lost. Although these backups
replace the old data, these old data files can be recovered by logging on to the backup server
and searching for the old files.

44
 V) References

Dennis, A., Wixom, B., & Roth, R. (2014). Systems Analysis and Design (6th ed.). Wiley.

Company Information. (2004, February 4). Retrieved April 25, 2016, from
http://www.carmax.com/enus/company-info/about-us-timeline.html

International Directory of Company Histories, Vol. 55. St. James Press, 2003.

45