The Factory Project

Overview

csci201 will design and build a manufacturing assembly cell. A frontend will be given with a well described API. csci201 will do the backend, while modifying the GUI and animation as they wish. The teams will be managed by students from ENGR499, the project management class.

The Operational Concepts Description                                                                              

Please see The Operation Concepts Description

The Teams

Teams will be formed at random from their labs.

Requirements                                                                             

Please see The Glass Line

Managers

Each team will be managed by a student taking the software management class. The managers will NOT assist with the design, implementation, or integration. Instead, the managers will manage: attend meetings, make sure meetings are effective, check to see if students are on plan, etc. Managers will produce a weekly status report for the professors.

eXtreme Programming

You are to use the eXtreme programming methodology. Details of your meetings, schedule and tasks will be maintained on Pivotal Tracker. Your manager will set up your team on this web-based software.

Subversion       

Subversion is a repository for managing your code. Rather than emailing code around, you will store it, check it out, and update it. More about subversion will be forthcoming.

Deliverables

There will be six deliverables (tentative due dates below):

  1. A design for the v.0 skeleton. This includes interaction diagrams, agent/backend design. The point of v.0 is to get the teams off to a quick start and have some code working without worrying about the full integration.
  2. v.0: A skeleton. This will be stored in the tags part of your repository as "GlassLine-v0". Your skeleton will have 3 non-integrated parts:

a.        Getting glass onto to the conveyor.

b.       Getting glass off and onto the popups into the work centers.

c.        Getting glass to turn the corner from one conveyor to the next.

3.      A final design that includes both v1 and v2. This includes interaction diagrams, agent/backend design (for csci201), and the DoXXX( ) API. The design is a living document for the life of the project. As design decisions change, this document should be updated. The design must handle the non-normative scenarios.

  1.  v.1: A working version of the normative scenario for the cell. This will be stored in the tags part of your repository as "GlassLine-v1".
  2. v.2: A second and full delivery of the cell with all the non-normative cases handled.
    This will be stored in the tags part of your repository as "GlassLine-v2".
  3. Final Presentations during the last week of classes.

Week Number

Sunday

Date

Due on Sunday

Monday Class

Labs

8

Feb. 27

 

Kickoff Meeting- SAL101
Discussion of Subversion, Moodle, Kitting Cell, v.0

Designing of v.0

9

March 4

 

Design/Coding of v.0

Spring Break

10

March 18

v.0 design docs

Code Review of v.0;
Coding v.0;

11

March 25

v.0 is due

 

Coding v.0;
Designing v.1;

12

April 1

 

Design Review of v.1;
Coding v.1

13

April 8

Final design;
v.1 is due

Designing/Coding  v.2

14

April 15

 

 

Coding v.2;
Work on Presentations

15

April 22

v.2 is due

Presentations on Monday and Wednesday

 

 

 

The University of Southern California does not screen or control the content on this website and thus does not guarantee the accuracy, integrity, or quality of such content. All content on this website is provided by and is the sole responsibility of the person from which such content originated, and such content does not necessarily reflect the opinions of the University administration or the Board of Trustees