Please enable JavaScript.
Coggle requires JavaScript to display documents.
Establishing Requirements (Data gathering (The overall purpose of data…
Establishing Requirements
Why?
The aim is ti producte a set off stable requirements that form a sound basis to star designing
After all finding and fixing a sotware after delivery is often 100 times more expensive than finding and fixing it during the requirements and design phase
What?
Is a statement about an intended product that specifies what it should do or how it should perform
We need to make sure that requirements are as clear as possible
Types
Functional requirements
Say what the system should do
Non-functional requirements
Say what constraints there are on the system and its development
Enviromental requirements
Refer to the circumstances in which the interactive product will operate
Physical enviroment
lighting,noise, movement
Social enviroment
Interaction design, such as collaboration
Organizational enviroment
how good is user support likely to be, how easily can it be obtained
Technical enviroment
What technologies will th product run or need to be compatible with
Personas
users profiles
Rich descriptions of typical users of the product under development that the designers can focus on and design the product for
Goals
Usability goals and user experience goals
Data gathering
The overall purpose of data gathering in the requirements activity is to collect sufficient relevant and appropiate data so that a set of stable requiremnts can be produced
Interviews
Questionnaires
Observation
Contextual inquiry
Part of contextual design,is a structured approach to the collection and interpretation of data from fieldwork with the intention of building a software-based product
Contextual interview
A combination of observation, discussion and reconstruction of past events
Context
Partnership
Interpretation
focus
Brainstorming
Task description
Scenarios
Concrete stories that concentrate on realistic and specific activities
Use cases
Contain certain assumptions incluiding the fact that there is a piece of technology to interct with
Essential use cases
Represent abstractions from scenario
Task analysis
Mainly to investigate an existing situation no to envision new product
Hierarchical task analysis
It involves breaking a task down into subtasks and then into sub-subtasks and so on these are then grouped together as plans that specify how the tasks might be performed in a real situation
Tips & tricks
focus on identifying the stakeholders needs
involve all the stakeholder groups
involving only one representative from each stakeholder group is no enogh
Support the data gathering sessions with suitable props