finals Flashcards
This refers to producing an emotional response.
Affective
When this doesnt work properly or crashes, it may cause irritability to the user.
Application
The user might be angry if this doesnt do what the user wants it to do.
System
It may cause problems if this is not met.
User expectation
This pop up as a result of unsuccessful functionalities and are vague, obtuse or condemning.
Error Messages
The ___ of the interface can be an eyesore if its to noisy, garish, gimmicky or patronizing
Appearance
This can happen when clicking on a link to a website only to discover that it is still under construction.
Gimmick
This should be treated as how to fix it messages and should state the cause of the problem and what the user needs to do to fix it.
Error Messages
This is an excessive number of operations, represented at the interface as banks of icons or cascading menus.
Featuritis
a whole new genre of cartoon and life like characters has begun appearing on our computer screens as e commerce assistants that give us information about products.
Vitual Agents
This lifecycle follows a similar thread to our interaction design model but includes considerably more details.
Usability engineering lifecycle
These are those affected by the introduction of the system or who will influence its purchase.
Tertiary Users
used to represent a modelthat captures a set of activities and how they are related. The reasons such model is popular is that they allow developers and particularly
Lifecycle models
this lifecycle emerged from the empirical work they did looking at how interface designers went about their work and has analytic mode and synthetic mode.
star lifecycle method
this development method is only a generic process and must be tailored for a particular organization.
Dynamic systems development model
this development method breaks down a large project into many smaller projects that can deliver products incrementally, and enhances flexibility in terms of the development techniques used in the maintainability of the final system.
Graphic application development
This development method workshops in which user and developers come together to thrash out the requirements of the system where the representatives from each identified stakeholder group should be involved in each workshop so that all the relevant views can be heard.
Joint app development
this model incorporates them in an iterative framework that allows ideas and progress to be repeatedly checked and evaluated
spiral lifecycle model
this lifecycle method was the first model generally known in software engineering, forms the basis of many lifecycles in use today and a linear model in which each step must be completed before the next step can be started
waterfall lifecycle model
this model is not intended to be prescriptive and is based on our observations of interaction design and on information
simple lifecycle model
this implies that the client or users know the requirements and has to tell the developers
elicitation
this is the activity of investigating and analyzing an initial set of requirements that have been gathered, elicited or captured.
requirements analysis
this ensures that a system must be able to run on a variety of platforms
non functional requirements
this capture what the product should do.
functional requirements