Group Dynamics
You may determine group roles. The groups below are not meant to define
roles that MUST be followed, and people can share the roles. However,
everyone must program and someone must be designated for the roles below.
- leader(s)
one, preferably two people designated to coordinate group meetings,
ensure that load is properly balanced, and have a vision of where the
project is going
- inter-group liason
one person responsible for working on inter-group projects. This may
involve establishing common coding conventions; working on designing,
finding, installing software that all-groups will use; developing
standards for editing/browsing that all groups might want to use
- librarian
responsible for managing all documents, including source code, web
documents, CVS expert, test plan, design document, final documentation,
coding standards
- Test Coordinate/Quality Assurance
responsible for managing test suite, ensuring that specifications and
requirements are being met
- Prototype Lead
might be the Tk expert, responsible for tracking the development of the
first prototype and making the group meet the task of delivering the
prototype
- Web-master/Toolsmith
Responsible for finding/developing tools to help with the project and
maintaining the team web documents
- Programmer
Everyone on the team is a programmer
Schedule for Group Project CPS 108/208
-
March 27: Team Design
-
Your team must have a team name, a team web-page, and a delineation of
tasks/work assignments. The page should be up and active by March 27.
Turn in hard-copy of your page(s), send the URL to the TA, gadde@cs.duke.edu . A preliminary
discussion of design should be included
-
April 1: Project Design
-
A complete design document should be turned in during class. Ideally
some of this information will be available on the web, but this is not
mandatory. You will make a group presentation (10 minutes) about your
design/project.
-
April 8: Test Plan
-
A plan covering how you will test the project should be turned in during
class.
-
April 17: Prototype
-
Your group should have a prototype ready to demo in class, prototypes
will extend through the 19th.
-
April 24: Last in-class Demo
-
The last in-class, group demo will be given.
-
May 1: Project Due
-
Complete projects, test suite, documentation is due. Your group
must have completed a demo to the class CEO (me) by 7:00 pm
on this day. Earlier is fine.