Risk Assessment

Risk Description	Likelihood	Consequence	Impact	Comments
Unavailability of hardware	1	6	6	Hardware already available
Unavailability of software	1	6	6	Software already available
Bad Time Management	2	8	7	Project plan has already been created
Requirements Change	2	3	3	Project is very flexible
Harsh Learning Curve	2	4	8	PHP should not be too difficult to learn
Hardware Malfunction	2	4	8	Laptops could crash

Proposal

Students: Ben Stockdale, Jon Pasquino

Project: Home Depot Inventory System

Date: Friday, May 29, 2009

Version: 1.0

Background: One of the nation’s leading providers of home and construction materials, Home Depot, is using an outdated inventory management system. Customers and employees cannot use the system easily, and information regarding other locations is not available.

Objectives: Our updated system will provide a modern day web solution for this obsolete legacy system. The system will be user-friendly, responsive, and allow customers to check the stock of items in other stores, an important functionality that doesn’t currently exist.

Outline: The system will be web-based, and will provide an employee with a company login and a home screen. From here, the employee will be able to checkout customers, check and change the prices of items, and check item availability for other stores.

Deliverables: Upon completion, we will provide a web application written in PHP which leverages a MySQL database. The database will be populated with store and item information, and several logins to simulate a real-world Home Depot store.

Evaluation Criteria:

· The ability to check out customers

· The ability to manage stock levels and item information

· The ability to check item availability in other stores

Resources: Software for development has been provided by Wentworth. Hardware for hosting the solution will be provided by Wentworth’s BCOS department. We have no foreseeable need for financial assistance.

Project Plan:

June 12^th – Requirements Analysis Document

June 26^th – System Analysis Document

July 10^th – Acquire Server space

July 17^th – Implementation

August 7^th – Testing and Post-Release