Each team member's name is linked to her/his email address. The specialty group mail inks will send carbon copies of all mail to Lloyd and John. The Group mail links for each team only send mail to the team members.
| Project Manager |
|
| Requirements Eng. |
|
| System Architect |
|
| Quality Assurance |
|
There are two categories of roles: Leader and General.
"General" are those that every person on the team fills. They are: Detailed Design, Programming/Coding, Testing, and Documentation. When you have decided on what product you will create, its high-level concept and scope, you should then divide up the general construction areas (or subsystems).
"Leader" roles are those that only one person will fill. They are
listed above. Understand that the leadership roles are not to be
done in a vaccum. As the label suggests, you will 'lead' the effort; it is
your responsibility to make sure that the associated tasks are accomplished,
not that you are soley responsible for getting them done. Because of the
time constraints on the class, outside 'Leader Meetings' will be held. It's
your responsibilty to disseminate information in those meetings to the rest
of the team. Team members, in turn, should be pushing the 'leaders' for
information relative to their area of specialty.
Project Options
Your team's mission is to write one of the following game packages:
At least some of these should be familiar to all of you. If not, they're
pretty easy to find.
Standards/Guidelines for Project Documents
Outlines for the various standards documents (e.g., Project Plan, QA Plan, etc.) are now available on a separate page. (Last updated 02-02-00)