Week 8 Requirement

What are requirements?

• Statements of an intended product which specifies what it should do or how it should perform.
• Must be specific, unambiguous (not open to more than 1 interpretations) and clear.
• Must know how to tell when they have been fulfilled.

In Software Engineering, there are 2 types of requirements:-

• Functional requirements -what does the system do
• Non-functional requirements -what are the constraints there are on the system and its development

Interaction design

• Functional requirement -capture what the product should do)
• Data requirement -capture the type, volatility, size/amount, accuracy and value of the required data
  
• Environmental requirement -context of use
• User characteristics -capture the key attributes of an intended user group
• Usability and user experience goals -how well the user perform to achieve applications goals and their perceptions

User Characteristics

- Capture the key attributes of the intended user group

• user's ability, skills, nationality, educational background, preferences, personal circumstances, physical or mental disabilities.
• the collection of attributes "a typical user" is called a User Profile.
• any one product may have different user profiles.
• to bring user profile to life, they turned it into a number of personas.
• Persona are rich descriptions of typical users of the product under development that the designers can focus on and design the product for.

Usability Goals and User Experience Goal

• Effectiveness, Efficiency, Safety, Utility, Tracking ------------------> User's Performance
• Fun, Enjoyable, Pleasurable, Aesthetically, Motivating-------------> User's Perception

Data Gathering for Requirement

• Interviews- getting people to explore issues; important to meet stake holders and for users to feel involved.
• Focus group- helps stakeholders to meet designers and each other to express their views in public.
  
• Questionnaires- gather initial responses.
• Direct observation- looking at the user using old platform as we make a new application but might be influence by the old platform
• Indirect observation
• Studying documentation- existing documentations
• Researching similar products- compare different product with the same function

Contextual Inquiry

• Context:- Emphasize on going to workplace and see what happen.
• Partnership:- Developer and user collaborate in understanding the work
• Interpretation:- Observations must be interpreted.
  
• Focus:- Data gather focus on user.

Data Gathering Guild lines for requirement

• focus on identifying the stakeholders needs
• involved all the stakeholder groups
• have more than 1 representative
• 4 techniques that have a user-centered focus.
  a. Scenarios
  
  • help users to describe
  • like storytelling method from the user
  • extract what they like and dislike
  b. Use Cases
  
  • user-system interaction
  • users are called an "actor"
  • form of text or graphical
  c. Essential use care
  
  • to combat limitations by scenarios and use cases.
  • does not restrict to technology
  d. Task analysis
  
  • to investigate an existing situation, not to envision new products
  • based on existing system rather than new ones

What are we trying to achieve?

Understand User + Produce a set of stable requirements = Design

A design and it's processes is mostly based on the "Users".

Lecture by: Mdm Mastura.