Final Project for CSC440

Team organization:

• Everyone is assigned to a team A, B, C or D. (3 people per team with two teams having only 2)
• Teams A & B will design a business system: a patient appointment scheduling system, and serve on the user team for the finch robot game
• Teams C & D will design a robotic system: a game using the finch robot, and serve on the user team for the patient appointment system.

Finch Game:

Teams A & B will work together to determine the requirements of one game using the Finch. It should make use of the finch sensors, and can make use of a scanner or window that is not on the finch itself. Teams C & D will work with the users together, but will separately write the design specifications.

Patient Appointment System:

Teams C & D will work together to determine the requirements of one patient appointment system for a small doctor's office. The system should be a tool that a receptionist uses to manage the front medical desk work of making appointments and then receiving patients for their appointment. It does not need to handle money transactions. The doctor will be able to see his schedule from this system.

Warehousing System - maybe every team does this:

A company needs a new warehousing system. They already have an order processing and accounting system. Their warehouse is one building with the following physical areas: large box storage, small box storage (picking area), staging, shipping

The warehouse has at least 3 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.

Your user will tell you the four products that are sold in that warehouse. The user will also 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).

Your system has to handle the following functional areas:

• 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.
• Guideline: Always prefer the easiest and closest location. Lower is easier than higher.

Your system will send the robot around the warehouse to get the material. Since the robot cannot climb up levels, it will simply get to a location and announce the location level it is reaching. It will also announce the type of equipment it is using whenever it changes to a new piece of equipment. For the first phase of our project, we will assume only one man works in the warehouse.

The system will need to connect to an order processing database. That database will have an order table, order detail table and customer table. The customer table will hold the customer number, name and address, and route number. The order table will hold the order number and requested ship date. The order detail table will hold the product id, quantity ordered, quantity allocated for picking, quantity picked and quantity shipped. The warehouse system will need to update the allocated for picking, picked and shipped quantities.

The warehouse system will need to at least track the available locations and the stock in each location. It will also need a table to hold the quantity allocated from each pick location for each order.

General Guidelines:

These projects will be fully designed, from scratch, during the course, according to the requirements presented by the student serving as users. These systems will be developed first using a waterfall method, trying to capture and design the entire system. 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. Specific intermediate deliverables will also be required, leading up to the final completed project.