PROJECT 4
Evaluation Scheme

*** This project is worth 20% of class total.
    Graded out of 100 and adjusted to 80% later, 
      as the intermediate deadlines were both worth 10% each.

    Late  -20 

    --- allocated points are subtracted for missing info.


*** 100 pts

     10  OVERALL QUALITY
         -- professional presentation of code, diagrams and text

     40  SYSTEM & DESIGN - reqs, code & execution, and interface & interaction

         20 System Requirements, Code, and Execution.
            -- system MUST be working for any of these 20 points!
            -- well constructed/coded & documented
            -- has three (or more) levels
            -- the "main paths" through system working
                 (other buttons etc can just be dummy)
            -- must read info from XML files
            -- no domain info in the code

         20 Interface & Interaction
            -- there must be a working interface for these points,
               or in the worst case a non-working but high-fidelity
               interface that can be viewed. 
            -- must be useful/helpful -- for obvious use cases
            -- good screen design for task/users
                -- appropriate choice of info at each layer/level
                -- design of layers for functionality
                   (e.g., selection of item at each level)
                   (e.g., how to control up/down hierarchy)
                -- clear control actions (e.g., buttons or menu items)
                -- clear/easy text entry (if needed)
                -- clear/readable textual information display
                -- use of grouping and space 
                      -- low layout complexity (design to grid)
                -- consistency across screens & within screens
                -- can it scale? (to hundreds of items?)
                -- system acts as expected, when pressing buttons etc.

     50  REQUIRED DOCUMENTATION

         (Work done for intermediate milestones should be revised 
          and included as appropriate in the final report).

        10  Task-centered design
                 -- User analysis
                 -- Task analysis
                      -- Task Objects, and their Attributes, as well as Task Actions
                      -- concrete, detailed, design-independent
                 -- include error handling analysis

         5  Low-fidelity prototype
                 -- include this regardless
                 -- this may be revised from previous submission:
                    professional rough design for the interface 
                     (professional sketches or storyboards)
                 -- every screen at each level of your interface
                 -- include some error handling
                 -- if there are changes from the previous RD then
                    please point them out. 

        10  Formal Specification
                 -- based on one screen
                 -- diagrammatic (e.g., a state transition network) or
                    textual (e.g., a grammar). 

         5  Initial Testing on paper
                 -- Document the testing and design changes made
                 -- Document any design changes made.

         5  Implementation & Testing of the prototype
                 -- Document the testing and design changes made
                 -- Compare against formal specification 

        10  Design Rationale for interface design & program
                -- why, why, why?
                -- mention user & task
                -- screen design analysis
                    -- choice of layout, icons, buttons, etc. 
                -- analysis of interaction 
                   (i.e., what action does user take? why?
                          how does system respond?    why? )

         5  Content Diagram
                -- flow OK? content OK? 
                -- uses actions and objects