Week 8: Requirement for interactive design

Hi,
Last week lecture our lecturer talked about requirement and I know that most of us knows it but what's actually the requirement?
Requirement is a statement about an intended product that specifies what should it do and how it should perform and it must be very clear and understandable.And we must know how to tell when they have been fullfilled.

Requirements in different field :

In Software engineering, there are functional and non-functional requirements.

Functional requirements : what the system should do (eg. formating, changing font styles etc )
Non-functional requirements : what are the contraints there are on the system and its development ( eg. must be able to run on different platform )

There are a few types of requirement : 
Interaction design
> functional requirements (how the things function)
> data requirements (how the data to be)
> environmental requirements
> user characteristics ( based on user needs)
> usability goals and user experience goals
- capture the key attributes of the intended user group
  - user's abilites and sklls, nationality, educational background, preferences, personal circumstances,      physical or mental disabilities
- The collection of attributes for a 'typical' user is called a user profile
- To bring user profile to life, they are turned into a number of Personas ( rich descriptions of typical users of the product)

Usability goals > effectiveness, efficiency, safe, utility, learnability and tracking > user's performance

User experience goals > fun, enjoyable, pleasurable, aesthetically pleasing and motivating, the product is interesting or not > User's perception

Data gathering for requirements :
- collect sufficient, appropriate data so that stable requirements can be produced
- need to be expanded, clarified and confirmed intial requirements
- types : 
interviews, (get people to explore issus, semi structured/ unstructured interviews often used to elicit scenarios. Important to meet stakeholders )
focus groups, ( gaining consensus view and highlighting areas of conflict and disagreement during the requirements activity, help stakeholders to meet designers and both express their views in public )
questionnaires, (used for getting initial responses that can be analyzed )
direct observation, ( to understand the nature of the tasks and context in how they are performed)
indirect observation, ( used less often)
studying documentation, ( good for understanding legislation and getting some background information )
researching similiar products ( gain understanding of the kind of features and interaction that other package has to offer )

Contextual inquiry 
> context
> partnership
> Interpretation
> Focus


Data analysis, interpretatiom and presentation
- iterated a number of times before a set of stable requirements evolves - descriptions will expand and clarify
- 4 techniques :
> scenarios
> use cases
> essential use cases
> task analysis



Thank you.