CS 160 Lab #3

1. Look up your buddy group (e.g. buddy7). Your group number is the number after buddy (e.g. 7). Consider the following scenario:

group number even

A grader notes that a student program doesn't compile or work correctly, and that the failure is due to a minor problem for which the student shouldn't be penalized too heavily. The grader makes a small fix to the program and runs the auto-grader again. The grader records the change and makes a small deduction to the score. Keep in mind that there may be more than one grader, and that each of them needs to be able to make independent changes.

group number odd

A student is unhappy about a score and files a challenge.

All scenarios pertain to the course project, as described in Homework 1.

2. Together with your buddy, write a use case, using the template from the Greene/Stellman book, with one modification. I added Open Issues, which is quite useful early in the game. Use a plain text editor (NOT Word or OpenOffice!!!) . Place your file into ~/cs160/lab3/GraderMakesSmallChange.txt ~/cs160/lab3/StudentChallengesScore.txt or One of you types, the other advises.

Use case number and name
Summary
Rationale (AKA Goal in Context)
Users
Preconditions
Basic Course of Events (AKA Happy Day Scenario)
1.
2.
3.
...
Alternative Paths
1.
2.
3.
Postconditions
Open Issues:
1.
2.
3.

3. After 15 minutes, check your report into your buddy group's sandbox.

source ~/cs160.profile
export CVSROOT=:ext:username@oslo.cs.sjsu.edu:/home/cvsroot/sandbox/buddyn
cd ~/cs160/lab3
cvs import -m "message" lab3 vendor release

Here, n is your buddy group number.
I don't expect your use case to be perfect (it can't be after such a short time), but it would be good if you could avoid the most obvious errors that we discussed in class.

4. Odd-numbered buddy groups: Check out the next higher buddy group's work. Even-numbered buddy groups: Check out the next lower buddy group's work. E.g. buddy7 checks out buddy8, buddy8 checks out buddy7.

export CVSROOT=:ext:username@oslo.cs.sjsu.edu:/home/cvsroot/sandbox/buddym
cd ~/cs160
mv lab3 lab3.bak
cvs checkout lab3
cd lab3

Here, m is the other buddy group number.
5. With your buddy, add comments to the other group's file. What do you like? What needs improvement? Switch typist/advisor roles from step 2. Just add the comments to the bottom of the text file. Don't try to fix the writing--just add a critique.
6. Check your work into the other group (i.e. the same place from where you checked it out). Do this by the end of class.

cvs commit -m "message"