Please enable JavaScript.

Coggle requires JavaScript to display documents.

The process of human-centred UX design -Requirements (P1), Scenarios,…

- - - - concerns with:
        
        what the system has to do
        
        what it has to be like
        
        how it has to fit in with other things
      - Designers need to research the range of people, activities and contexts relevant to the domain they are investigating
      - need to understand the opportunities and constraints provided by technologies
      - Requirements
        
        2 jenis:
        
        a) Functional
        
        concerned with what the system should be able to do
        
        concerned with the functional constraints of a system
        
        Logical and organisational constraints
        
        b) Non-functional
        
        generated through discussions and interactions with people who will use or be affected (the stakeholder) by the proposed system
        
        generated through observations of existing systems
        
        generated through working with people in focus groups, design workshops etc. where different scenarios can be considered
        
        Aim: to collect and analyse the stories people have to tell
        
        in understanding, need to consider all the different stakeholders & how they might be affected - to decide siapa yang akan terlibat dalam discussions about design
    - - concerns with
        
        finding appropriate media to render design ideas
      - Method/technique used
        
        a) Sketches ‘on the back of an envelope'
        
        b) fully functioning prototypes
        
        c) cardboard mock-ups
      - Scenarios, sometimes represented in pictorial form as storyboards, are an essential part of prototyping and envisionment
    - - things have to be engineered and software has to be written and tested
      - Databases have to be designed and populated and programs have to be validated.
      - whole system needs to be checked to ensure that it meets the requirements
      - finally the system can be formally ‘launched’ and signed off as finished
      - developers need to ensure that their system really does meet the specification and does not contain any ‘bugs'
    - - Everything gets evaluated at every step of the process
      - tightly coupled with envisionment because the nature of the representation used will affect what can be evaluated
      - evaluation criteria will also depend on who is able to use the representation
      - It could be:
        
        list of requirements or a high-level design brief that is sent to a client
        
        abstract conceptual model that is discussed with a colleague
        
        formal evaluation of a functional prototype by the future system users
      - Evaluation technique used must be appropriate for the 1) nature of the representation, 2) the questions being asked and 3) the people involved in the evaluation
      - Techniques for evaluation are many and various depending once again on the circumstances
  - - - to avoid making assumptions about how functions and information will be distributed.
    - - 3 components:
        
        operational design (slide 18), representational design (slide 19) and design of interactions-ID (slide 20)
- - - - Discover
      - Define
      - Design
      - Deliver
  - - - to guide the design process
    - - People, Activities, Context, Technologies
        
        People adalah orang yang akan menggunakan system, diwakili oleh Personas
        
        Activities and the contexts in which they will occur are envisioned (dibayangkan) through scenarios of use.
        
        Different concrete scenarios can be used to envision (membayangkan) how different technologies (hardware and software) could function to achieve the overall purpose of the system and deliver a good UX.
- - - - A project will be divided into manageable periods of work (typically 2 weeks long)
    - - Aim
        
        to quickly produce a minimum viable product (MVP).
        
        version of the product or service that does just enough to meet its purpose
        
        can then be evaluated and tested by users
        
        allows the designers to experiment and test their design ideas and assumptions
        
        may result in further development
        
        Additional features can be added through further developments and subsequent versions can be developed and deployed
        
        quite common in interaction design for regular updates of an app or web service to be produced over time
- - - - Abstraction
        
        moving from the details of specific people undertaking specific activities in a specific context using a particular piece of technology to a more general description that still manages to catch the essence of the activity.
        
        Aggregation is the process of treating a whole thing as a single entity
        
        for example, one would aggregate a screen, processor, disc drive, keyboard and mouse and treat this as a single thing –a computer
        
        Classification is the process of recognizing that things can be collected together - dealing with class of things is simpler (lebih abstract)
        
        analyst has to work with the stories that have been gathered and with the users themselves to decide which things belong together and why.
        
        one of the classifications and aggregations
        
        Between them aggregation and classification produce abstractions.
        
        Degree of abstraction (slide 54)
        
        Finding an appropriate level of abstraction at which to describe things for a given purpose is a key skill of the designer
    - - common elements will start to emerge
  - - - from very abstract diagrams to detailed ‘pseudo code’
- - - - If UX designers were architects
        
        well-understood methods and conventions
        
        for specifying the results of the design process
        
        produce various blueprints from different elevations
        
        produce various blueprints from different engineering specifications
      - In UX,
        
        there are a variety of formal, semi-formal and informal methods of specification.
        
        best known of the formal methods is the Unified Modeling Language (UML)
- - - - help the analyst/designer to establish a list of requirements –qualities or functions that any new product or system should have
  - - - in order to get a high-level, abstract view of the main activities that the product is to support
  - - - users need to learn only a limited number of design elements
      - can cope with a large variety of different situa