Please enable JavaScript.

Coggle requires JavaScript to display documents.

Rapid Prototyping (Scoping a Prototype (1.WHAT NEEDS TO BE PROTOTYPED?…

- - - - Convert the user's description of the solution into mock-ups, factoring in user experience standards and best practices
    - - Share the prototype with users and evaluate whether it meets their needs and expectations
    - - Based on feedback, identify areas that need to be refined or further defined and clarified
- - - - Usually created by tools such as Visio and Omigraffle
      - Prototypers often stay away from visual elements of branding, colours and style
      - The focus is on demonstrating the behaviour of the application
      - Best suited to determining whether user needs are met and whether the user experience is optimal
      - Functional fidelity here is medium at best
      - The speed of medium-fidelity prototyping is achieved with templates, stencils and reusable widgets and elements.
    - - Most realistic. Often mistaken for the final product
      - Usually time-intensive
      - Application-simulation tools for High Fidelity are Axure and iRise
      - Cannot be converted to usable code but serve as a reference to developers
      - Useful for conducting usability testing and training users
    - - Sketching on paper is a low-fidelity approach
      - No special tool or experience required
      - Used during the early stages of a design cycle
      - Ideal during brainstorming and conceptualisation
      - Static and usually have low visual and content fidelity
      - This forces users to focus on how they will use the system instead of what it will look like, and it makes designers more open to changes based on user feedback