STRUCTURE OF THE TEAM
Position Assignments
Team Leader -- Justin Tumlinson
  Coordinates the group effort and direction, while keeping everyone organized and disciplined
Assistant Team Leader -- John Aichholz
  Assists the Team Leader with his efforts
Team Liaison -- Brian Mecham
  Communicates directly with the customer and team technical advisor
Team Recorder -- David Todd
  Responsible for keeping all record of events
Team Communicator -- Darold Litzin
  Responsible for communicating with group members and Dr. Collier
Team Technical Advisor – John Placer
 
Decision Making
A decision will consist of a unanimous vote.  If an argument persists, it will be resolved with 
  a closed ballet with at least a four out of five votes needed to pass.

Communications
Project related mail will not be made public to the group account, unless it is relevant to the 
  rest of the group.
Personal messages will not be sent out to the group account, they will instead be sent out 
  individually.
Documents of importance will be mailed to the group account.
Desired questions to be asked of Dr. Mullens will be mailed personally to the Team Liaison.
No changes in code planning can be made without the team consent.
Any outside communication from the group will be hard-copied and placed in record.

Meeting Requirements
Attendance will be mandatory. 
If a group member is unable to come he will send e-mail to the other group members and 
  contact by phone if possible.
The group meeting time will be 6:30 p.m. on Mondays.
The Team Leader will provide the agenda for the meeting to follow.
If the Team Leader is unable to come, the responsibility of presiding and preparing for the 
  meeting falls to the Assistant Team Leader.

Dead-Lines
At each meeting every group member will bring in a hard copy of their accomplished work, 
  or a summary of  their research work.
All code delivered will be tested and do exactly what is planned of it.
Action to be taken against a group member with late work will be judged in light of the 
  circumstance by the other group members.  Options concerning the work to be done will be 
  discussed.

Word Processor
Final documents turned in will be written in Microsoft Word.
Status reports will only be in text format for e-mail.
 

Status Reports
Status reports will be turned in on Thursday to the Team Communicator, who will then turn 
  in the team status report on Friday.
When a group member fails to turn a status report, his section of the team status report will 
  remain blank.
Status reports for each individual will include:

1. Task Completed
2. Tasks Started
3. New Tasks Assigned
4. Problems Encountered
5. Time Spent Working
Team status reports will follow the guidelines handout and put all individual team status 
  reports together in a summarized form.


RISK ANALYSIS

Introduction
Risks are identified by brainstorming and are addressed according to the formula:
  Risk = ( Probability of Occurrence ) * Impact
  The risks are then organized and placed accordingly into a chart showing the greatest 
  concerning risk along the least concerning ones.  With each value ranging from zero to one.



Risk Analysis

Identification
1. Java - Encountering tasks that we do not know how to accomplish in Java?
   Probability = 0.60, Impact = 0.90, Risk = 0.54
2. Schedule - Will an incorrect schedule hinder the project?
   Probability = 0.50, Impact = 0.70, Risk = 0.35
3. Independence - Will we not be able to create objects that are completely independent of 
   each other?
   Probability = 0.50, Impact = 0.75, Risk = 0.38
4. Generic - Will we be able to keep all classes truly generic?
   Probability = 0.20, Impact = 0.75, Risk = 0.15
5. Hierarchy - Will we be able to establish a correct hierarchy structure?
   Probability = 0.10, Impact = 0.75, Risk = 0.08
6. Integration  - Will the control panel completely integrate with everything?
   Probability = 0.30, Impact = 0.90, Risk = 0.27
7. Platform - Will different platforms be a problem?
   Probability = 0.05, Impact = 0.40, Risk = 0.02
8. Translator - Will we be able to have the translator correctly translate all existing 
   code to the new format?
   Probability = 0.30, Impact = 0.80, Risk = 0.24
9. Missed requirements- Will we get all the needed requirements?
   Probability = 0.40, Impact = 0.90, Risk = 0.36
10. Time constraints- Will time be a problem with having to give time for other classes and job interviews?
   Probability = 0.40, Impact = 0.60, Risk = 0.24
11. Team cohesion- How well the team works with each other?
   Probability = 0.40, Impact = 0.50, Risk = 0.20
12. Technology changes- Will the control panel work with new versions of browsers, Operating systems, etc?
   Probability = 0.60, Impact = 0.30, Risk = 0.18


 
 ·Risk Estimation


IMPACT

LOW
MED
HIGH
(0.0-0.60)
(0.60-0.80)
(0.80-1.0)

LOW
(0.0-0.20)
-
5,7
4
PROBABILITY
MED
(0.20-0.30)
-
12
6,8
HIGH
(0.30-0.50)
11
10
1, 2, 3, 9




Page 2



Document Index



Page 4