CIS 470 PROJECT PLAN Essay

1098 Words Apr 14th, 2014 5 Pages
CIS 470 PROJECT PLAN
Team:
Team A
Team Members: Melinda Ahmed
Nathan Gruss
Daniel McIntyre
Catherine Roberts
Date:
9/4/11
Project Title:
Williams Specialty Company e-Commerce Web Site. WSC
Team Leader
Daniel McIntyre

1. System Overview
Williams Specialty Company, a small printing and engraving organization, wants a web site developed to enable their customers to enter their order information including but not limited to:
Type of job (print or engraving)
Media (clothing, plague, or trophy)
Media catalog number
Content into the print/engraving request database
Billing and payment options

The company also wishes to provide its entire catalogue online and have two sections one for customers with valid contracts, and
…show more content…
The project may not compile correctly if the programming language is not understood.
Each team member has different background programming language
Solution: Each member will be responsible for the part that he or she is most comfortable with.
5. Software Engineering
This section will define the project’s standards, procedures, development methodology and resources.
5.1. Standards and Procedures 5.2. Development Methodology
UML will be utilized to design the system in conjunction with RAD and the use of prototypes to be able to deploy a working model faster that other methods.
5.3. Development Resources
Tool used will be:
PHP Eclipse
Apache web server
MySQL client version: 5.1.37 phpMyAdmin version: 3.2.0.1
XAMPP – Apache distribution containing MySQL, and PHP
MS Office 2007 to include Access, Excel and Word
MS Visio 2007
MS Project 2007
Unless otherwise stated all tools will be local installations
6. Testing Procedures
Testing procedures will be developed to not only ensure the functionality of the application, but to take in security and vulnerability concerns as well. Component level testing will take place to ensure each component is functional before putting them together. Once constructed the application with then be tested first to ensure there are no problems in functionality and identify problem areas and possible user related errors

Related Documents