Kursusgang 6 Oversigt: Kursusforlb: - Forml og evaluering - - - PowerPoint PPT Presentation
Kursusgang 6 Oversigt: Kursusforlb: - Forml og evaluering - Hidtidige kursusgange - Resten af kurset Metoder til HCI-design Modellering af brugere i design Design af brugerflader 6.1 Forml og evaluering Semesterml -
Design af brugerflader 6.1
Oversigt:
Design af brugerflader 6.2
implementation af grafiske brugergrænseflader.
retningslinier.
grafisk brugergrænseflade kan udføres.
Design af brugerflader 6.3
Brugbarhedsevaluering:
processen
Grundlæggende HCI:
informationsbehandling
(udførelse)
Design af brugerflader 6.4
Hidtil Resten
Design af brugerflader 6.5
designprocessen:
anvisninger? To løsninger:
Design af brugerflader 6.6
cycle model
et antal faser
produkt
forhold til bestemte kriterier
udgangspunktet for den næste fase
Design af brugerflader 6.7
Requirements specification Operation and maintenance Architectural design Detailed design Coding and unit testing Integration and testing
Design af brugerflader 6.8
Requirements specification Operation and maintenance Architectural design Detailed design Coding and unit testing Integration and testing
Krav til brug Model Beskrivelse af komponenter Beskrivelse af arkitektur
Design af komponenter Design af arkitektur Analyse af anvendelses-
Analyse af problem-
Design af brugerflader 6.9
Hvorfor?
Design af brugerflader 6.10
Effects (Zuboff)
physical objects (forms, books, etc.) was missing.
humans (customers, supervisors) and more with computers.
their screens came from and what it meant.
because of lack of concreteness (no names, no history, etc.).
claims required (the computer knows it).
specifikationer, men de er vanskelige at lave og forstå
udviklede systemer
brugernes viden om deres arbejde
svære at beskrive
vi vil have, og vi kan beskrive det præcist og utvetydigt
nødvendigt
Design af brugerflader 6.11
Design af brugerflader 6.12
givet projekt
Design af brugerflader 6.13
andet alternativ til life-cycle modellen
bestemte egenskaber ved et system
eksperimentere med den for at illustrere deres krav
for prototyper
tidspunkter i udviklingsprocessen
Early implementation without prior analysis and design. Revised until the users are satisfied. Revisions become complicated and maintenance is very expensive.
Development in order to enquire into and express requirements. Is often described as a ”running” requirements specification.
An implementation of a design which is as close to the final systems as possible. Often used for technical experiments, e.g. with the technical platform.
A cardboard or similar non-executable model of the system.
A modifiable, running model of part of a
final version which becomes the system.
Design af brugerflader 6.14
make-up and image processing.
when computers were introduced.
tool, but that was too abstract for the graphical workers.
computerized system would work.
boxes, overhead projectors and projector screens.
the operations of the computer.
experiences with the mock-ups.
Design af brugerflader 6.15
ud fra kontingensfaktorer:
Kan simpelt defineres ud fra den tingængelige information:
Quantity Too much Too little Quality Too difficult Too unreliable Complexity Uncertainty
Design af brugerflader 6.16
System Life Cycle Prototyping Mixed Methodology Prototyping High Low High Low Complexity Uncertainty
Reference: Burns & Dennis
Design af brugerflader 6.17
prototyping og vandfaldsmodellen
fire typer aktivitet
den samlede indsats på et givet tidspunkt
der er opnået I en enkelt cykel.
(klokken 3) tages en beslutning
risikoanalyse
der ud I en vandfaldsmodel
Design af brugerflader 6.18
Design af brugerflader 6.19
a monthly basis.
calculated manually. Computerization:
manual work in the payroll department.
registered manually and then typed onto a tape.
processing calculates the payment for the month and updates the accumulated information.
hours of work in current month for each employee Typing hours of work in current month for all employees Data processing Information about all employees:
Update Payments
Design af brugerflader 6.20
administrative information systems replaced repetitive manual work (e.g. payroll).
integrated into and used by the department that performed the original manual task.
introduced, often conducted in a separate department or
work.
become superfluous.
is extremely repetitive.
input data are not checked when output data seem unreasonable.
processing.
Design af brugerflader 6.21
administrative systems that modernized the first generation.
to on-line:
source: Employees enter their working hours directly into the system.
are needed.
becomes the communication channel between departments.
date.
into the work that produces the data.
registered in their context.
superfluous.
using computers which may require more training.
departments.
Design af brugerflader 6.22
min SU-ansøgning
web-sted:
hjælp; kun samlinger af regler og bestemmelser
Design af brugerflader 6.23
created by Enid Mumford.
people
efficient and have social characteristics which lead to high job satisfaction.
To be resolved, these conflicts need to be recognised, brought out into the open, negotiated and a solution arrived at which largely meets the interests of all the parties in the situation ... successful change strategies require institutional mechanisms which enable all these interests to be represented, and participation provides these.” Job satisfaction: the attainment of a good 'fit' between
is seeking from his work: job needs, expectations and aspirations
to do in his job: the
requirements which mould his experience. Job satisfaction: the attainment of a good 'fit' between
is seeking from his work: job needs, expectations and aspirations
to do in his job: the
requirements which mould his experience.
Design af brugerflader 6.24
Step 3. Example of input/output analysis of one section of a Purchase Invoice Dept. This department checks and passes for payment the invoices of firms who supply goods and services the Company. Inputs Mail Clerks sort invoices VAT clerks edit invoices Comp operator check invoices Invoice is microfilmed data prep1.
Why Change?
2.
System boundaries
3.
Description of the existing system (5 different levels, operative tasks to whole system)
4.
Definition of key objectives
5.
Definition of key tasks
6.
Definition of key information needs
7.
Diagnosis of efficiency needs
8.
Diagnosis of job satisfaction needs
9.
Future analysis
job satisfaction needs and objectives
system
Step 4 - Examples of key objectives of the Purchase Invoice Dept.
are of the right quality and price and arrive on the date promised. Also to provide a satisfying, stimulating work environment for Purchase Invoice and Treasurer's Dept. staff.
suppliers accounts. This is affecting the quality of the supplier's service. Step 5 - Examples of key tasks of the Purchase Invoice Dept.
financial compensation
Step 6 - Example of key information needs
payment
quality standards
Design af brugerflader 6.25
relatively easily. More importantly, they have the skills of knowing about their own work and system, and have a stake in the design.
welcomed participation and can be convinced of its benefits.
new work systems for themselves in the wake of the introduction of word-processing equipment.
system.
was DECs XSEL, an expert system for their sales offices, used to configure DEC hardware systems for particular customers.
Design af brugerflader 6.26
a three-day seminar where both nurses and system developers participated.
was to establish a detailed and precise understanding of nursing.
participants were trained in making data flow diagrams (Yourdon 1982), and were then supposed to apply this tool to describe their work.
established: A, B, and C.
from three different wards and a systems developer.
extensive development experience circulated between the three groups.
chosen as the starting point. While working with the descriptions it became clear that their experience was different:
Design af brugerflader 6.27
led by the nurses. The systems developer was primarily acting as an advisor.
relations between the manual routines of nursing and it focused
three wards of the participants.
human information processing instead of simple data transformation and the contents of the forms applied.
strictly observed:
communication between various persons was introduced.
the exact way in which the incoming data flows were transformed to the
group focused on criteria that were influencing the major decisions.
were included in the description, even though they were not of direct importance to the data transformation.
nurses’ relation to customers and local management (the manager of the ward).
Design af brugerflader 6.28
much from that of group A.
dominant person.
guidelines of the method, and in this sense the descriptions produced were more correct.
understanding of work in the ward in which she was employed influenced the description very much.
their description gave a more generalized picture of the work in the three wards.
Design af brugerflader 6.29
the descriptions were presented.
three descriptions gave a strongly biased impression of “actual” nursing.
relevant picture of their work.
quality of the description from group C.
developers, who did not participate in the seminar, were presented to the descriptions.
understanding the descriptions.
description produced by group A but also to the descriptions produced by group B and C.
Design af brugerflader 6.30
developed.
at two different hospital wards.
Design af brugerflader 6.31
something by somebody (application domain)
assessing whether a customer should be granted a loan.
something (problem domain)
situation of a person.
based on an understanding of these contexts.
System Problem domain Application domain User
Design af brugerflader 6.32
From
Tacit knowledge Explicit knowledge
To
Tacit knowledge Explicit knowledge
Internalization Converting explicit knowl- edge into tacit knowledge; learning by doing; studying previously captured explicit knowledge (manuals, documentation) to gain technical know-how Socialization Transfering tacit knowledge through shared experiences, apprenticeships, on-the-job training, talking at the water cooler Externalization Articulating and thereby capturing tacit knowledge through use of metaphors, analogies, and models Combination Combining existing explicit knowledge through exchange and synthesis into new explicit knowledge