If a picture is worth a thousand words, a prototype is worth ten thousand words.  At STSI we have learned some best practices about producing rapid prototypes that get users focused on delivering their business needs and away from reams of documentation.

 
 

Outline/Structure of the Talk

  • Why prototype?
    • Better than documents
    • Better than mockups
    • It's easier than you think
  • The basic framework
    • Low fidelity UI communicates this is a prototype
    • AngularJS handles URL/Controller logic
    • JSON files provide the initial "database"
  • Removing the need for a backend
    • Modeling the business domain
    • Generating realistic data
      • People
      • Words
      • Volume
      • Statuses
  • Iteratively designing the back-end
    • Angular Services simulate the needed backend calls
    • JSON files simulate the API results
  • Using the prototype to elicit requirements
    • Laddering
    • A/B testing
    • Usability
    • Establish UI "vocabulary" with users
    • Getting offline feedback

Learning Outcome

  • Know how and why to use prototypes to gather requirements

Target Audience

Business Analysts, Front-End Developers, Designers, Architects

schedule Submitted 5 years ago