System Emergency Week

System Emergency Week: 7/28 through 8/1

Here are the rules for the System Emergency week:

Scheduling

Select from your classmates two other people to form a three-person team (more than likely there will be a final group that can't form an entire group of three; I will take that into account. I STRONGLY prefer groups of three people.)

Have each group select a Team Leader. The purpose of the Team Leader is only to simplify scheduling.

The Team Leader will coordinate with me via email, phone, or in-person and schedule a two hour time slot during the last week of classes (July 28th through August 1st). Any two hour time slot is acceptable, starting at 8:30 AM until 4:30 PM on Monday through Friday. Time slots cannot be scheduled during class lecture, however.

Method

Each team will be given 3 problems.
Each person on a team will solve 1 problem (teams members can decide who solves which problem).
The primary problem-solver will "think out loud", describing steps for problem resolution. They will attempt to solve the problem by themselves as much as possible.
I will give access to any room, machine, manuals, root access, etc (within reason :).
The primary problem-solver, if having trouble, may use other team members as consultants. Realize, however, that your grade for the problem resolution is based on how well and how much of it you resolve it by yourself.
The problem resolution period ends after a hard time limit (40 minutes). Your grade is based on:
- Did the primary problem solver initiate resolution or did he/she rely too much on their partners?
- Orderly elimination of potential diagnoses and fixes
- Use of skills and knowledge obtained in this course
- Getting the right answer

IMPORTANT: NO DISCUSSION OF THE PROBLEMS AND HOW YOUR TEAM RESOLVED THEM IS ALLOWED AFTER YOUR TEAM HAS FINISHED! The problems will be unique, but similar enough in composition and resolution to give future teams an unfair advantage if you divulge the information.