User Interface Development Process

Background

• User Interface Prototype Document Format
• User Interface Prototype Quality Assurance criteria

Process

1. Interview end users to create a set of preliminary requirements.
2. Perform a Task Analysis to determine what UI tasks will need to be performed.
   
3. Develop UI semantics (general tasks and sequencing).
4. Choose interaction style and physical devices.
5. Design draft screen layouts and user interaction syntax.
6. Create a complete pencil and paper storyboard according to class guidelines.
7. Show the storyboard to key end users and solicit their feedback. 
   
8. Revise storyboard using end user feedback.
9. Evolve the storyboard into a complete interactive scripted prototype that demonstrates every functional aspect of software. Use a GUI builder tool to create the actual user interface screens, and incorporate the screenshots into the prototype. Be strategic and put in the minimal effort needed to obtain the feedback you desire.
10. Show the prototype to key end users and solicit their feedback.
11. Repeat steps 8 - 9 until the prototype is sufficiently detailed that there is no ambiguity about the software requirements and the user is excited about the prototype.  Make the prototype broad enough to cover the whole system, but keep it "shallow" as possible.  It only needs to demonstrate the interface behavior not actually implement any underlying functionality. Add requirements numbers to the prototype for cross referencing. Example prototype
12. If there are important software functions that have no visible component, include them in an appendix to the prototype. Examples:
    A payroll calculation: overtime rate = normal rate * 1.5
    Minesweeper game difficulty: #mines = difficulty * 5
    (Be sure to use terms from the Data Dictionary).
13. Obtain customer signoff.
14. (Optional) Present prototype to class or other external reviewers.