Final Project for CSC440

Team organization:

• Everyone is assigned to a development team of 3 people
• Each team will serve as a design/coding group plus also a user group for another team.
• Each team chooses one system to work with throughout the course.
• The system will be partially coded by the end of the course, with an emphasis on good documentation and project control.

Scenario:

The entire class works for one software application firm. You have been asked by two distributors to write a system for their warehousing, inventory, and order processing systems. The users for each distributor can determine what product the distributor is selling.

Inventory System

• Keeps track of how much inventory is available for sale, being sold or being shipped in.
• Follows inventory status throughout the order process, in conjunction with warehouse and order processing modules.
• Keeps track of how much inventory costs, including shipping costs for getting the material, and the cost of the material for each sale.
• Works with the warehouse system to control the physical count inventory that checks for correct system inventory counts.
• Categorizes inventory for lookups.

Order Processing System

• Keeps track of customers and their orders
• Manages the shipping dates, addresses, truck routes, and costs of orders
• Manages order movement from requested order, allocated, picked, staged and shipped through to invoiced

Warehousing System

• Putting deliveries away in the warehouse, mostly into large box storage but occasionally into small box storage.
• Refilling small box storage from large box storage when its contents are low
• Picking orders from small box storage and placing those into the staging area
• Moving staged orders into the correct shipping lane to be loaded onto a specific truck.
• Allocate inventory to orders and then keep tracked of picking, picked, staged and shipped quantities.
• Track the available inventory in each location
• Guideline: Always prefer the easiest and closest location. Lower is easier than higher.

Your user will draw the warehouse layout. The warehouse needs to have at least 4 aisles and at least 2 levels in some places. The shipping area needs at least 3 lanes, with each lane indicating a different shipping route (ex: east coast, west coast, middle).

The warehouse might have the following physical areas: large box storage, small box storage (picking area), staging, shipping

The warehouse might have different types of equipment for moving material:

• push carts that can only reach the low level
• forklifts that can only reach the highest level
• forklifts that can be used for any level from floor to ceiling.

General Guidelines:

These projects will be fully designed, from scratch, during the course, according to the requirements presented by the students serving as users. These systems will be developed first using a waterfall method, trying to capture and design the entire system at a high level. Then, we will move on to Agile Scrum Sprints to dive into a few features. At the end of the semester, each team will deliver requirements specification, technical design specifications, architecture design specs, test plans and hopefully a fully working system portion. Specific intermediate deliverables will also be required, leading up to the final completed project.

Update: The final project will be whatever was defined as sprint 2. That sprint needs to be fully specified using the 5 UML diagrams we have been using, a user acceptance test and a burn down chart. Inside the code, a Junit test and eclipse project file and database are needed. The panther git repository should contain your code.