Department of Computer Science   University of Southern California
CSCI588  
CS588 Home |  Contact Information |  Class Materials |  Assignments |  Projects |  References |  CS Department |  DEN
 
Assignments
Assignment 1
Assignment 2
Assignment 3
Assignment 4
Assignment 5
Assignment 6
Assignment 7
Assignment 8
Assignment 9
Assignment 7: Requirements Verification and Usability Analysis
CSCI-588: Specification and Design of User Interface Software
Fall 2004
7A: Requirements Verification (Due: 6.30 pm. PST, November 9, 2004)

This homework will aid you in determining if your system met (or will meet) its requirements. You can use the IADT method (Inspection, Analysis, Demonstration, Test) by developing a matrix of your project requirements (rows) vs. which IADT methods (columns) apply (Reference: class notes page 2-66 to 2-67). A add a column for comments and explanation. Make a clear explanation of how the system will meet its requirements. (Assignment 2A and plus the matrix). Remember these guidelines discussed in the original requirements assignment (Assignment 2A).

When you generate your system requirements, use full sentences to describe them. Although you will use full sentences, keep them simple, readable, and grammatical. We only need the high level requirements. Make your requirements "testable". Try to avoid a broad description. The requirements are for your system, not for your users.
Use precise and direct language to write your requirements, for example, use the word "shall" instead of vague or confusing words like "should" or "could" or "may".
v = Completed satisfactorily. You are heading down the right path
v- means resubmit this homework
v+ = all possible requirements for your system are covered. The requirements are written in the correct format as described above and the verification steps are clearly addressed.
COURSE NOTES referral: See Pages 2-56 to 2-68
**Remember to write your names and team number, if you have received it, plus your location ("Campus" or off-campus-location-name).
7B: Usability Analysis (Due: 6.30 pm. PST, November 9, 2004)
The project team needs to select method(s) to evaluate their user interface. The project team conducted a survey (like the QUIS) of Ben Shneiderman discussed in class or used a Usability Specification (like from the paper by Whiteside, Bennett and Holtzblatt), discussed in class, for their project. Both references (QUIS and Usability Specification article) were left by the Professor to be scanned into the class DEN website on 11/2/04.
V+ means the students completed both a Usability Specification and customized survey of >5 persons, analyzed and summarized the results of the surveys and specification, and discussed the changes that will be made in the class project as the result of this analysis. The completed surveys are included in the homework submittal.
V means that the project team did develop Usability Specifications or copied relevant portions of the QUIS survey (one or the other). The project team had 2-3 persons complete the rudimentary survey. Cursory analysis of the results was included.
V - means the project team only specified a sparse Usability Specification and did not take it further. Or, the project team copied a page or two from the QUIS survey right from the course notes/textbook and had 1-2 persons fill it out. Little or no analysis of the results was included. Resubmit this homework.
COURSE NOTES referral: Course textbook (Shneiderman) reference is Pages 153-161. Course notes references are Pages 5-54 to 5-58.