¡GoConqr estrena diseño! Cuéntanos qué te parece.

Fichas

Design Process

dcardosods Inglés 30 fichas

Fichas del conjunto (30)

  1. 1CorrectnessPeople want interfaces to be responsive and "error-free" because they are an integral part of society.
  2. 2An UI is "wrong" if..It doesn't satisfy users needs. Core dump. Incorrect calculations.
  3. 3SpecificationUnderstandable by end users, easy to write down, revise and convert into implementations, precise enough to settle arguments and able to facilitate answering questions.
  4. 4Formal languagesFormalized descriptions that clarify intentions. Provide unambiguous description of a small part of the world.
  5. 5State machinesMethod for formally describe interactions. Diagrams.
  6. 6Finite State Machine (FSM)An abstract representation of a system with states and transitions (events/actions).
  7. 7Central tensionThe bridge between the users' world, non-formal and rich, and the system's world, rigid and formalized.
  8. 8Problems with FSMComplexity of interfaces. Cannot represent some notions, e.g., timed events. Time to create/update model is not inconsequential.
  9. 9Formalized descriptions“Since a complete formalization of the properties of a large system is infeasible, the question is not whether specifications should focus on some details at the expense of others, but rather which details merit the cost of formalization.”
  10. 10Non-formal languagesHave more expressive power.
  11. 11Semi-formal languagesA formal language complemented by a non-formal language.
  12. 12User Centred Design (UCD)User-centred design is a process for figuring out the correct functionality of an application through semi-formal languages. It's all about understanding people, their needs and how they use your software.
  13. 13UCD principlesUnderstand users’ needs. Design the UI first. Iterate. Use it yourself. Observe others using it.
  14. 14ScenariosStories of people using technology, that is easier to understand by developers and users, non-formal, appropriated detailed and with variations.
  15. 15Functions prioritizationCritical: Needed by early users to do something useful.
    Important: Required before shipping the product.
    Nice to Have: Nice, but unnecessary.
  16. 16Usage patternsIs certain task performed by many or few users? Is it frequent or occasional?
  17. 17Designing the UIWidgets identification. Customized or familiar ones?
    Attributes assignment. Model, affordances, presentation.
  18. 18UI attributesModel: what data does it need? Affordances: what can you do with it? Presentation: how does it appear in the UI?
  19. 19Component distribution: TemporalWhen components appear, the flow from one interface to another.
  20. 20Component distribution: SpatialWhere components appear on an individual interface section.
    Use visual design & Gestalt principles.
  21. 21StoryboardsQuick way to sketch out sequence and schematics.
  22. 22Interaction SequencesMacro-structure, convey the "big picture“ of system interaction.
  23. 23Interface SchematicsMicro-structure, convey essential content, and functionality at individual steps of interaction. Includes enough detail so that someone could begin designing and implementing system logic.
  24. 24Visual vocabularyA standard set of graphical symbols and notation to describe something.
  25. 25PrototypesA limited representation of a design that allows people to interact with it and to explore its suitability.
  26. 26Prototype fidelityFaithfulness of prototype appearance and performance to final product.
  27. 27Low fidelity prototypePrototype doesn’t look much like final product, operation of the prototype may be simulated and slower.
  28. 28High fidelity prototypePrototype looks and operates like the real product.
  29. 29Paper prototyping“Usability Testing where representative users perform realistic tasks by interacting with a paper version of the interface that is manipulated by a person playing computer, who doesn’t explain how the interface is intended to work.” (Snyder, 2003, p. 4)
  30. 30Wizard-of-Oz Technique (WoZ)Evaluate unimplemented technology by using a human to simulate the response of a system.

Información

Descripción
Fichas sobre Design Process , creado por dcardosods el 09/04/2015.
Creado por
dcardosods
Visitas
15
Etiquetas
ui
Valoración

Escríbenos

¿Sobre qué es tu mensaje?

¿Qué te parece el nuevo diseño?

¿Te gusta?