Case Project
Williams Specialty Company (WSC)

Williams Specialty Company (WSC) is a medium sized print and engraving organization. The company wants to automate their ordering system.
WSC wants to provide a product catalog that customers can look through and purchase from. (You can if you would like, make this project a complete web based system, make it totally in-house including the catalog, or provide the catalog online and have the rest of the order processed in-house. It is your choice. If the customer walks into the facility or calls the order in from a phone or by using email, then the salesperson will initiate the order on a computer. If the system is completely web based, then the customer will be initiating the order.)
When a customer requests a printing or engraving job from a catalog, the information (1) type of job (print or engraving), (2) media (tee shirts, plaque, or trophy) (3) media catalog number, and (4) text content for the item in the order must be entered into the their database system. The fonts and font sizes must be entered as well. If it is tee shirts, then the sizes of the shirts must be included as well as the color of the tee shirts.
An order will be one item type. So for example, one order could be a printing order that would be 200 tee shirts that have “Go Team A” on it. The font, font size, and font color of the printing must be in the order and they must be the same. The 200 tee shirts can be different sizes but they must be the same color. Or the order can be 50 of the same trophies that say “Best Dad” on it. But if the customer wants both of these examples, then it must be two orders. Any printing order must be for more than 50 units. Any engraving order can be for one or more of the same plaques or trophies that say the same thing.
Customers that order over 200 but less than 500 of a printing order get a 10% discount off the price of the order. Anything over 500 units for a printing order gets a 15% discount. Any mass production engraving order also has a discount. More than 10 trophies or plaques in the order receive a 5% discount.
After any discounts are calculated, the salesperson will show the customer all the final order details, discounts, and costs for the order before it is submitted. If the customer approves of the order, the customer must then put down at least a 50% deposit before processing of the order can begin. If it is a new customer, a new customer account must be added to the database.
The salesperson has the option of assigning a printing/engraving specialist to the order before the order is submitted. If the salesperson does not assign the order to someone, before submitting the order, a specialist can go through the list of new orders and assign himself. The printing/engraving specialist searches the inventory in the database to determine if the media is in stock. If the media is in stock, the printing/engraving specialist marks the media item as sold and decrements the media stock count. If the item is not in stock, the printing/engraving specialist orders the catalog item and records the expected delivery date and puts the order on hold and work on some other order. He must then send a message to the salesperson about the situation.
If the printing/engraving specialist has the product in inventory, then he begins the work. If the order is a printing order or a mass production engraving order, then a proof (example) of the order must be approved by the customer before the order is mass produced. When the proof is completed by the specialist, a message is sent to the salesperson that the proof is competed and the status of the order becomes “customer approval for order pending.” The salesperson then shows the proof to the customer. If the proof is not acceptable to the customer, the salesperson changes the order status to “not approved” and the salesperson records why the work was not approved by the customer. The salesperson then sends a message to the specialist that the order needs to be fixed. The printing/engraving specialist redoes the proof and then changes the status of the order from “order not approved” to “customer approval pending” and again notifies with a message to the salesperson. The salesperson again asks the customer if it is acceptable. If the work is approved by the customer, the salesperson changes the order status to “customer accepts proof” and sends a message to the specialist that is has been accepted by the customer. The specialist then completes the order.
After the order is complete, the specialist sends a message to the salesperson that it is complete. The salesperson then sends a message to the customer that the order is complete and the rest of the payment must be made. Once it is fully paid, it is ready to be shipped or picked up. An invoice is printed out for the customer. The order is then closed.
You must also keep track of the specific product messages between employees for each order as it goes through the production process so that the salespeople and printing/engraving specialists are aware of an order’s progress. Also, salespeople or printing/engraving specialists, when displaying the order on screen at any time, must also be able to see the current status of the order such as “on hold,” “proof ready,” “proof rejected” and “order ready.” The employees must be able to see in some way the history of all messages that describe the progress of the order on screen as well.
Once the customer picks up the order or when it is sent through FedEx, the sales person marks the sales order as closed.
If you want, you can create your catalog as a web application or as an in-house online form using a software product like VB or C# or Dreamweaver. You do not have to connect the application to the database. It would be great to add pictures of the products to your catalog.
An invoice and three year-to-date reports must be generated. A report should show the sales information for the year. The sales information will include some of the customer information, type of media, quantity produced, sales amount, and a description of the product. A second report should the quality control for each order. It should show the history of messages generated for each order. The third report will be a report of your own choosing. If you want to add a fourth report, that will be fine.

Notes:
The database can be done in ACCESS or any database you prefer. I know you didn’t learn ACCESS in your classes but it is simple to learn and use. I will provide the tutorials for you if you want them. I will also provide links to some of my database lectures that will help you with database normalization and SQL.
If you do not use ACCESS, then you must write SQL statements to generate the output for your sales invoice and your two reports. The output does not have to be a formal report. Instead it can be just the output from the SQL. If you decide to use ACCESS, then you can use the Report Wizard to generate the reports. Again, it is up to you. It is your project and the purpose of the project is to review what you learned in previous courses. If you don’t use the Report Wizard for your reports, you can just generate the output using SQL Join statements. The reports do not have to look like formal reports. Their purpose is to make sure you have developed and populated your database correctly.

Project Plan Name

Design and Development Team:
Name1
Name2
Name3
Name4
Name 5

 
Contents
1. System Overview 3
2. Project Development Management 3
2.1. Organization and Resources 4
2.2. Personnel 4
3. Schedule and Milestones 4
3.1. Scheduled Activities, Tasks, and Assignments 5
4. Risk Analysis 8
5. Software Engineering 9
5.1. Standards and Procedures 9
5.2. Development Methodology 10
5.3. Development Resources 10
6. Testing Procedures 11
7. Configuration Management 12

CIS 470 Project Plan
Team: Letter A
Team Members:
Date:
Project Title

1. System Overview 5%

Describe the project. Use your PROJECT OVERVIEW to do this. Put it in your own words. Keep it as an overview. Do not get detailed. Give it about 150-200 words.

2. Project Development Management
2.1. Organization and Resources 1%
Organization and Resources will identify who the Team Leader will be each week. You can assign one person to be it the whole or maybe have one person do it for four weeks and another for the other four weeks.

2.2. Personnel 3%
Personnel will contain a list of everyone on the Team and what skills they bring to the Team.
Customer Contact:
John Doe: Modeling, database skills, web design
Sally Williams: Modeling, Web design, Technical writing

3. Schedule and Milestones
3.1 Scheduled Activities, Tasks, and Assignments (26%)
Scheduled Activities, Tasks, and Assignments ideally should be created in Microsoft Project using the template in Doc Sharing or you can use the format below without using Microsoft Project.
If using Microsoft Project to create a time line, please cut and paste into the Project Plan document under this heading if it will be big enough to easily read, or if not, as an attachment in landscape orientation. If adding as an attachment please integrate the time line into the MS Word Project Plan document and just reference what attachment it is under this heading. Bottom line is please do not send as a separate MS Word document or MS Project file.
Sample:
Task ID Activity Name Start Date Finish Date Assigned To
GPA Shop Center Web Site 4/29/08 6/15/08
1 Project Plan 4/29/08 5/4/08 Whole Team
2 Assign Team Roles 5/1/08 5/2/08 Whole Team
3 Prepare Project Plan 4/30/08 5/4/08 Whole Team
4 Submit Project Plan 5/4/08 5/4/08 Team Leader
5 Requirements Specification Draft
6 Create System Overview 5/4/08 5/4/08 Whole Team
Create Methodology Description 5/4/08 5/4/08 Whole Team
Create Requirements
Team Charter
Design Specification Draft
Create Database Description (ERD)
Create Data Flow Diagram
Create Processing Description
Create User Screen Designs
Create Interface Description

Create Component/Unit Code
Create Database
Create Website (optional)
Create Test Plan
Final Requirements Specification
Final Design Specification
Final Test Plan
Deployment Plan

Application Files
Project Presentation
Project Presentation to Customer
 

The chart below is optional. You can do it and not do the structure above. But the IDs need to be correlated with the names of the activities.

 
4. Risk Analysis 26% Create a table.
Risk Analysis should describe the risks you see with completing the project AND how you will mitigate the effects of those risks in completing your project. Do research on the internet as well as research on your systems analysis textbooks. Also include any risks that you have experienced personally on the job. Give at least 8 risks. Use a table with two or three columns

5. Software Engineering

5.1. Standards and Procedures 26%
5.1. Standards and Procedures
What standards and procedures will you incorporate to manage your project? You can discuss some of the more important models you will be using and why they will help develop the system. Keep it simple and short.
Project management procedures? Meetings? Software change procedures.
What are the naming standards for documentation and the software modules (GUIs, DB tables, DB attribute names, and event/process variables within the GUIs. You can show one or two examples for each type.
What are the internal documentation standards? What will the programmers be required to do?

 
5.2. Development Methodology 5%
Development Methodology should describe what Software Development Life Cycle (SDLC) development method you will be using and why. Waterfall, Spiral, Rapid Application Development (RAD), etc.
5.3. Development Resources 2%
Development Resources should list and briefly describe those software development tools you will be using to build the application. That is, what programming language(s) you are using and what development architecture you will be using. For example,
Programming Language(s)
PHP …. [add description here]
Database
MySQL …. [add description here]
Servers
Apache Web Server …. [add description here]

6. Testing Procedures 7% 150-200 words.
Testing Procedures will just give a brief overview on your unit testing procedures. Later in the term you will be creating a Test Plan that will go into much more detail on your Testing Procedures. The test plan template you will be using is in doc sharing. You can use that information to summarize your testing here.