Roles of Project Members

Each team should select one Manager, one Designer, one Toolsmith, one Quality Controller, one Facilitator, one Editor, and Assistant Programmers as needed.  It may be that one person plays more than one of these roles. 

Project Deliverables

Late deliverables will lose 5% of their total possible grade value for each day or fraction of a day they are late.

Your project plan should include a narrative description of the hardware and environment in which the software runs and of the function of the software; a description of the team organization; a schedule of team activities; a list of team goals for the project; a description of the development strategy and process model being used.

Your requirements document (analysis model) should include a statement of all customer- or team-originated requirements; low-fidelity prototypes; and use cases or scenarios.  Your acceptance test plan should indicate all tests to be performed by me at the end of the semester along with the expected outcomes.

Your draft user's manual should include chapters called "Getting Started", "The Second Experiment", and "Detailed Instructions".

Your architectural design (design model) should include diagrams (UML, etc.); patterns.

Your code should be well commented, including standard headers and appropriate naming; compilable; and complete.

Your test documentation should describe each test executed, including date, person, unit tested, purpose of test, outcome of test, any necessary code corrections, and result of retesting.

Your user’s manual should be an update of the draft manual.

Your executable code must function correctly as described in the specification and the user’s manual.

Your post mortem should describe what went right and what went wrong with your project, and advice to others who might work on a similar project

Potential projects