CSCI 588

General
   Course Description
   Course Syllabus

Fall 2002

   Contact Information
    Announcements
   Class Materials
    Class Project
   Grading Criteria
   Team Projects
    Links

Previous Terms
   Fall 1998
   Fall 1999
   Fall 2000
   Fall 2001

Last modified on
11/19/2002 

Computer Science 588
(NTU SE 735-SC)

Specification and Design of User Interface Software
Fall 2002

Grading Criteria

  1. Assignment 1: Project Topic Description
  2. Assignment 2: System Requirements and Navigation
  3. Assignment 3: Web site review
  4. Assignment 4: Interaction (Dialogue) Styles and User
  5. Assignment 5: Project Status and Review
  6. Assignment 6: Individual Assigned Reading Assignment
  7. Assignment 7: Color Analysis Team Project
  8. Assignment 8: Usability Analysis
  9. Assignment 9: Usability Study of an existing system
  10. Assignment 10: Final Project Grading Criteria

Assignment #1: { Due @ September 10, 2002, 6:30pm PDT }

  • The names of all members in your team and your location (on campus/ off campus, with off campus site name) are required. Your topic name is included with one paragraph to describe your system. Lack of the description for your system will be seen as incomplete of this assignment.
    •
  • The topic must be a "new idea" and not something already in existence. Teams must be 2 or 3 members. Only remote students can work alone. Students will receive back a "v" (check) implying approval of topic and be assigned a team number to use on future homework submittals.
    •
  • COURSE NOTES referral : See Description of Class Project handout

    • Assignment #2: { Due @ September 17, 2002, 6:30pm PDT }

  • 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".
  • For the site/navigation map, use one page to present your map. It should resemble a web site map, or a menu-tree-like hierarchical structure that shows how a user can move within the system that you plan to design. Include a few words of explanation to describe the main features of the site/navigation map.
    Both the requirements and the site map should change as you learn and discover more as your design matures.

    v = both parts are 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 specified format (specific English usage described above). The site map is clear and easy to follow. You use some words attached to the site map or highlights to explain the contents of the site map.

    Remember to write your names and team number, if you have received it, plus your location ("Campus" or off-campus-location-name).
  • COURSE NOTES referral : See Pages 2-32 to 2-42; 2-47 to 2-51; 2-57

    • Assignment #3: { Due @ September 24, 2002, 6:30pm PDT }

    This is a team assignment. Critique a web site design using what you have learned. Select a web site of a major corporation or government entity (a large city, state, etc., for example, cityofla.org) and comment on what you like or dislike about that web site. Base your critique on what was discussed in class, what is in your supplemental notes regarding web site design, and what is in your class textbook. Point out any comments you have with respect to the source; for instance, Shneiderman's book says --- , Jakob Neilsen's web site suggests --- , usableweb.com gives a better example of --- , it was discussed in class that --- , or such other examples to further justify your critique.
    Limit your comments to approximately one single-spaced, typed page. Comment on amount of "eye-catching" visuals, advertisements, or other astonishing interfaces, as well as appropriateness for basic functions we have discussed such as search, help, site maps, navigation aids, etc. What about icon design, use of color, ability to print, frames? Supply a hardcopy of the home page of the web site also (black & white is OK).

    v = one or two pages web site critique and provided the URL of the web site reviewed. The critique is subjective and does not point to any of the class references.
    v- = resubmit this homework.
    v+ = All important features of your selected web site are included in your critique. All comments are clear and hitting the point. You kept the comments to one page. You used references, as appropriate, to substantiate your assessment of the web site. You made constructive suggestions on how the web site could be improved. You noticed any technology impacts of this site, e.g. too many unproven plug-ins or unreadable in older versions of Windows, etc. You documented any differences of opinion among your team-mates. You experimented with the checklists in your class notes on the referenced pages below. You remembered the hardcopy of the home page of the selected site.

    COURSE NOTES referral : See Pages 2-28A to 2-28D. Also, handout describing the assignment. The handout was distributed in class and is also up on the materials at the DEN link.
    Remember to write your names and team number, if you have received it, plus your location (Campus or off-campus-location-name).

    Assignment #4: { Due @ October 01, 2002, 6:30pm PDT }
    There are two parts to be completed this week: select the Interaction (Dialogue) Styles and perform a User Characterization analysis.

  • Part 1: When you evaluate your project's interaction styles, use Shneiderman's discussion on dialogue styles. In particular, see the class notes referenced below. You are taking this table and modifying it for your project, filling in the elements in the table based on team agreement. You should evaluate based on the user psychology, knowledge and experience, and job and characteristics of your project. You have to present the evaluation in a tabular form. Also, explain the reason for choosing or not choosing certain dialogue style(s) for your project's UI. You have to figure out what the user psychology, knowledge and experience, and job and characteristics of your project are and explain why.
  • Part 2: In the second part, you are asked to perform a user characterization. See class notes, referenced below. You have to identify the following: user characteristics, user tasks, user workload, and user environmental considerations. Much of your analysis was already performed while completing Part 1. Also, complete and/or modify the "User Profile Checklist" (page 3 - 10) for your project.
    •
  • v = both parts are completed satisfactorily. You are heading down the right path. Dialogue Style Summary and User Profile Checklist pages are xeroxed right out of the notes and edited with your project information
    v- means resubmit this homework due to errors or incompleteness.
    v+ = all factors which will affect your decisions on the dialogue style(s) for your system are covered and explained clearly. All possible user characteristics (who is the user), user tasks (what tasks the user performs), user workload (for example life-critical systems vs. casual browsing and information gathering sessions), and user environmental considerations are analyzed and listed. Example environmental considerations are: working environment for your project system, for instance, in a car, handheld computer, standing at the ATM, sitting at home, working alone or with others, etc). v+ homework includes some written explanation to clarify the decision made.
  • COURSE NOTES referral : See Pages 2-112 to 2-115; 3-9 to 3-13

    • Assignment #5: { Due @ October 22, 2002, 6:30pm PDT }

    Your team is required to submit one hard copy of your project status review. The approximate pages (slides) in presentation format for each part is listed on “Project Status Reviews I and II Agenda for October 22 and 29, 2002”. When you generate the slides, previous assignments will be the references. Remember to consider the comments from our Grader, T.A. or Professor. Those comments will definitely help your team to improve your project. You can employ the content of your assignment 1, Project Description, in your Topic Explanation. Address any assumptions you make for building your system. Also, refer to previous grading criteria again to ensure the assignment is complete. For User Analysis Discussion, a Data Flow Diagram of tasks being performed by your system should be added this time. You only have to list what you’ve done so far. Completion of the whole system is not required now. Use about 10 pages for your screen prototypes. Please write some explanation for the screen designs and navigation. Sequence your slides following sample path(s) through your system. Try to create an example of how the system would work when the user is interacting with the system. Write comments, issues, complaints, assumptions, tool(s) used and plans for the rest of the semester. It is expected that you will be copying or repeating portions of your previously completed homework. The reason for the homework is an incremental developmentof your class project. You must include one cover page in the hard copy. You have to list your team number, team member names, and your team location ( write “Campus” or off-site location name).
  • V+ Followed outline explicitly, addressing each item. It is taken into account who presents on 10/22/02 vs 10/29/02 in terms of preparation time allowed. Entire team presents project, each doing a portion. Team addresses screen designs factoring in issues and guidelines discussed in class. Teams illustrate corrections of design and decision made based on feedback of doing homework, class discussion, team discussion, etc. Written explanations of screen designs and navigation included in hardcopy handed in, not just screen dumps.
  • V Interim capability demonstrated, but, a lot of more work to do. Team only follows general topic areas on outline, but does not address everything requested. Only 1 person of 2 or 3 person team presents team project.
  • V- Team presents screens drawn using drawing tools in PowerPoint or handwritten (low fidelity prototype), with only a small subset of the eventual design. Sections missing from the outline. Lack of team cooperation apparent. Did not follow outline in "Project Status Reviews I and II" handout.

    • Assignment #6: { Due @ November 05, 2002, 6:30pm PDT }

    Select a technical journal article (not trade journal) or textbook from the references to read in depth. If you have questions about whether the article or textbook contains sufficient technical detail, e.g. an article that is not from a refereed journal, PLEASE contact Professor Jacobs. If you want to review a "classic" article (i.e. more than or equal to five years old), contact Professor Jacobs for its worthiness. Otherwise, assume the article you review must be less than five years old. "Get into it": truly evaluate the author's thesis, check out the author's references, and "take a stand" (especially if the article is a survey or is controversial). If it is related to your project, state how and why. On 5 November, 2002, hand in a one to two page, single-spaced, typed summary and critique of the article. This is individual (not team) homework. Submit a copy of the article with the paper. Professor Jacobs will return it.
  • V+: truly evaluate the author's thesis, check out the author's references, and "take a stand" (especially if the article is a survey or controversial). You point of view is well-organized and using the material offered in class properly. You commented if the article was applicable to your team project and why. You attached a copy of the article from a technical (trade) journal. Your write-up is 1-2 pages, single-spaced.
  • V: Explain your opinions based on what have taught in class. You digest everything important in the article you choose. You attached a copy of the article from a technical (trade) journal. Your write-up is 1-2 pages.
  • V--: Your personal opinions are generated without referring to the class material. You merely summarize the article without using any analysis or thought behind your summary. You chose an article from a trade journal or an article which is more than 5-years old (without first checking for the article's worthiness from Professor Jacobs). You did not include the article with your homework submission.

    • Assignment #7: { Due @ November 12, 2002, 6:30pm PDT }

    Prepare one to two (1-2) PowerPoint charts (or equivalent tool for developing presentation charts) summarizing your analysis of the colors you are using in your projects. It was obvious to Professor Jacobs that we have NOT yet covered some of the "visual design" or graphics design material (will be covered in November) from the project presentations in October. This exercise will cause each team to view their project more "artistically" and to select colors that make sense from a user interface design perspective. This chart will become part of your final project submittal in the section entitled "Comments/issues/lessons learned".
  • V+: You reviewed the reference material on color in user interface design and clearly described your color combinations and choices. Your presentation is concise and to the point. You point out that the colors you have chosen are acceptable based on the referenced research OR you point out that you have made some design changes based on performing this homework. You included an example screen with commentary on the colors as an example. You kept the homework submittal to 1-2 PowerPoint slides.
  • V: You briefly state that the colors selected meet your user needs without any justification or analysis. You reviewed only the course notes as reference material. Your homework was less than 1 (e.g. 1/2 page) or more than 2 PowerPoint slides.
  • V--: Your analysis is personal opinions not based on any of the above reference material. You have no examples or justification of the colors selected. You did not submit the material in PowerPoint slide format.
    • Remember to write your names and team number, plus your location (Campus or off-campus-location-name) on the submittal! Professor Jacobs is sensitive to the fact that you may not have easy (or inexpensive) access to a high quality color printer for this assignment. He will accept a black & white homework submittal. Just use color pens, handwrite, etc. to make your points. COURSE NOTES referral : Use the information described in class (see class notes Pages 3-24, 3-25, 3-25a), the course text (Page 398-403), and/or the article scanned into the class (DEN) web site entitled "Techniques and Tools for Using Color in Computer Interface Design".

    Assignment #8: { Due @ November 19, 2002, 6:30pm PDT }

    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.
  • V+ means the students completed both a Usability Specification and customized survey of >3 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 136-143. Course notes references are Pages 5-13 to 5-20 & 5-40 to 5-50.

    Assignment #9: { Due @ November 26, 2002, 6:30pm PDT }

    This is a team, not individual assignment. Please review an existing system (must not be your own project and not a web page) and perform the usability study. That system can be a device (e.g. VCR, cell phone, microwave, DVD player, PDA, etc.) or a system (e.g. ATM machine, postage device, gas station pump, etc.) that has some user interface to analyze. If you are developing a user interface for a device for your class project, it may prove beneficial to pick a similar device for this homework. This is a shorter version of the previous weeks homework where you may have developed and conducted a survey (like the QUIS developed by Ben Shneiderman) or use a Usability Specification (like from the paper by Whiteside, Bennett and Holtzblatt). Since you were not the developer of this system, you may need to estimate the requirements of the system you picked to completely evaluate it. State all assumptions. Format for this homework is 1-2 single-spaced typed pages.
  • V - means your team reviewed a web page or reviewed your own project and not a device or system as described above. You did not approach the problem with any of the techniques you learned the previous week. You did not state any assumptions about the requirements for the system. You only handed in about less than 1/2 typed page or more than 2 pages of text that did not cover the requested analysis in a coherent fashion.
  • V means your team made assumptions about system usability requirements, applied some of the things yolearned in performing a detailed usability study on your project the previous week (e.g. you developed a Usability Specification) for this system. Your analysis was not too coherent and did not refer to the things you learnt from the class lectures.
  • V+ means your team completely stated assumptions about usability requirements for the chosen system. You developed a Usability Specification or similar mechanism (e.g. a sample QUIS Survey) to capture how this system should perform. You included a highlighted photo or diagram of your system to make your discussion easy to follow. You discussed your results with a neutral party as a test (user) case to see if they had any observations on your analysis. You discussed the usability of that device or system in a clear, coherent fashion. This team made observations from this second usability homework and compared it briefly with what was performed last week. You noted any changes to your project as a result of this weeks assignment of an evaluation of an existing system or device.

    • Assignment #10: { Due @ December 03, 2002, 6:30pm PDT }

    Each team is required to hand in one hard copy for your final project on December 3, 2002. The date is firm. No delayed submission will be accepted. Remote DEN and NTU students must ship their project to arrive at USC DEN on December 3. No matter if you are presenting the project on December 3 or December 10, you still must hand in this material on December 3. No exceptions. Even numbered teams present on Dec. 3. Odd numbered teams present Dec. 10. NTU or non-LA DEN students can make other arrangements with the professor for presentations during this same time period. The outline is listed at the end of the grading criteria. The number of pages for each subject is not fixed. However, the approximate number of pages is listed in Final Project Outline. Using more pages to include all your hard work is welcome. Dont skip any part. You are also required to submit proof of code, e.g. the hard copy of your code. Posting web-based solutions on our class web page will be an extra credit. Please fasten your project submittal in a way the pages wont get lost (e.g. not just a paperclip). Cover Page [4 points]:
    You have to put your Team number, Team member names, email address(USC email address, or other email address in case you don't have a USC address) and Team location (Campus or off-site location name) on the cover page. The outline for the final project should be followed. Label sections clearly.     Topic Explanation [4 points]:
    Your topic name is included with one paragraph to describe your system. State all assumptions you made if any. (Assignment 1)     System Requirements [8 points]:
    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 have to be written in the specified format. You need to cover all possible requirements for your system in the final project. This is new : include whether your system met (or will meet) these 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-42). A add a column for comments and explanation. Make a clear explanation of how the system will meet its requirements. (Assignment 2 and plus the matrix)     Navigation or Site Map [8 points]:
    For the site/navigation map or menu tree, use approximately one page to present your map. It should resemble a web site map, or a menu-tree-like hierarchical structure that shows how a user can move within the system you plan to design. Include a few words of explanation to describe the main features of the site/navigation map. (2nd part of Assignment 2)     User Analysis Discussion [8 points]:
    For the User Characterization, you have to figure out what the user psychology, knowledge and experience, and job and characteristics of your project are and explain why. For User Analysis Discussion, a Data Flow Diagram of tasks being performed by your system should be added. All possible user characteristics (who is the user), user tasks (what tasks the user performs), user workload (for example life-critical systems vs. casual browsing and information gathering sessions), and user environmental considerations are required to be analyzed and listed. Example environmental considerations are: working environment for your project system, e.g. in a car, handheld computer, standing at the ATM, sitting at home, working alone or with others cooperatively, etc.). Include the discussion of the dialogue styles chosen as you did in the homework. Include some written explanation to clarify the decisions made. (Assignment 4)     Tools/System [8 points]:
    Discuss why and what tools are selected for your prototyping and implementation. Use the tradeoff matrix of tool alternatives. Use a table format to present the tool capabilities (or cost) versus tool(s) used or considered. Include explanations in the table. List the challenges you faced for the final tool decisions, if any. (Not a previous assignment, but started during your October Project Status Reviews.)     Evaluation [8 points]:
    Discuss methods used to evaluate your system. Include a Usability Specification and/or QUIS. Use the survey youve conducted. Include the surveys themselves. Analyze the results and discuss the changes that will be made in the final project as the result of this analysis. (Assignment 8)     Specification [8 points]:
    Specify a small portion of your system, e.g. one screen, using one of the techniques covered. For example, UAN, IRG, or state diagrams discussed in the lecture on 11/26/02 (Reference: class notes Chapter 4). Clear explanations are required. (Not a previous homework)     Screens [24 points]:
    Use about 10 pages for your screen prototypes. Of course, the total number of screens will vary and the number of pages may be more. Please write some explanation for the screen designs and navigation. Sequence your slides following sample path(s) through your system. Try to create an example of how the system would work when the user is interacting with the system. Note improvements made since the October Project Status Reviews expected in this section also. You may want to include those previous screens and how you improved them. Write brief comments for the improvements youve made in the final project. For each screen, specify what inputs caused you to move to the next screen, for example the menu item selected or button pushed. Mark that on the hardcopy.     Comments/ issues/ lessons learned [8 points]:
    Include the material you prepared for your projects color analysis homework here. (Assignment #7) For your team project, state and explain the changes you made. Include the log of design decisions that affected your system design. Comment on any challenges youve encountered. Discuss what youve learned and the possible improvement or new work could be done in the future. Present any design alternatives that may have been rejected during your team discussions. Discuss what you would have done if you had more time. Address how newer UI technologies could enhance your project. Review the V+ sections of the posted grading criteria for previous assignments on the class web site.     Code Hardcopy [12 points]:
    Printouts or CD / diskette required for your code to prove the project was implemented as stated. Please mark or label the printouts or CD / diskette with the team number and submit along with other project materials.

    Class Project

    Final Project Outline

    for December 3, 2002 (FIRM)

    Approximate

    Pages               Subject

     1                      Cover Page

                                    Team Number,

                                    Team Member Names,

                                    Member email addresses,

                                    Team Location (Campus or off-site

                                                            location name)

     1                      Topic explanation

                                    (state assumptions, if any)

     1                      System Requirements

    Top-level system requirements. Also, include from the homework whether your system met (or will meet) these requirements. Discuss IADT test verification methods illustrating how you tested that your requirements were met.

     1                      Navigation or Site Map

                                    (navigation hierarchy, e.g. menu tree)

     3-4                   User Analysis  discussion

                                    User Characterization

                                    Task analysis

                                           Note: do a data flow diagram of

                                                     tasks being performed by

                                                     your system

                                    Workload analysis

                                    Environmental considerations

                                    Dialogue/interaction style(s) selected

                                    I/O device(s) selected

     1                      Tools/system

    Tools selected for prototyping and implementation (if any). Discuss or present tradeoff matrix of tool alternatives explaining why the tools were selected or not selected

     

    1-2                   Evaluation

    Discuss methods used to evaluate your system, e.g. usability matrix, survey, etc. Then, evaluate it.

     

    1-2                   Specification

    Specify a small portion of your system using one of the techniques covered, e.g. UAN, IRG, state diagrams, etc.

     

    10                   Screens

    Include screens with explanation
    Follow sample path(s) through your system, i.e. an example of how the system should work

    1                      Comments/issues/lessons learned. 

    Explain changes. Discuss color. Summarize major decisions that effected your design. Record the design decisions chronologically in a "log". State what new UI or Input/Output technology changes you would make for your system design. Comment on any challenges, e.g. use of the tools described in the tools section above that proved insufficient for your design. What did you learn this time that you would do differently next time.
                                   

    Open                        Code hardcopy

    Comment: I fully understand that you will be resubmitting completed homework as part of this.

     

                     Final Project Grading

              4  Cover page/title/followed directions

              4  Topic explanation

              8  System requirements

              8  Menu tree or equivalent

              8  User Analysis

              8  Tools

              8  Evaluation

              8  Specification

             24  Screen design

             12  Credit for implementation/code

                    8         Comments/issues/lessons learned
            implementation decisions, future improvements

    + Credit for posting web-based solutions on class web page

             + -  Teaming considerations

            100  Total possible points

     

    Projects will be returned. Campus student projects will be left in or near the Computer Science Department Office. Remote students will have their projects returned via the normal process. Anyone who is out of the area (or graduating) and would like the projects returned by mail, please provide a stamped, large envelope to Professor Jacobs and the project will be mailed back to you.




    Remember to write your names and team number, if you have received it, plus your location (Campus or off-campus-location-name)

    Back to Top

     

    Send questions or comments to Steve.Jacobs@trw.com
    The University of Southern California does not screen or control the content on this website and thus does not guarantee the accuracy, integrity, or quality of such content. All content on this website is provided by and is the sole responsibility of the person from which such content originated, and such content does not necessarily reflect the opinions of the University administration or the Board of Trustees