This week lecturer talks about requirement. What is requirement?
- statement about an intended product that specifies what it should do or how it should perform.
- should be specify,unambiguos and clear as possible
- time to download any complete web page is less than 5seconds vs teenage girl should find the site appealing.
- must know how to tell when they have been fulfilled.
Types of Requirement
- Functional (what the system should do)
- Non-functional (constraints and development)
Interaction Design
- Functional Requirement
- Data Requirement
- Environmental Requirement
- User Characteristics Requirement
- Usability goals and user experience goal
Functional Requirement
Capture what the product should do.
Data Requirement
- capture the type
- volatility
- size or amount
- persistence
- accuracy
- value of the required data.
Environmental Requirement
The circumstances in which the interactive product will be expected to operate.
There are 4 characteristics of environmental requirements.
- Physical Environmental
- Social Environmental
- Organisational Environmental
- Technical Environmental
Usability goals
- effectiveness
- efficiency
- safety
- utility
- learn ability
- tracking which is the user's performance.
User experience goal
- fun, enjoyable, pleasurable, aesthetically pleasing and motivating which is the user's perception.
Data Gathering for Requirements
There are difference type of data requirements
- Interviews
- Focus Groups
- Questionnaires
- Direct observation
- Indirect observation
- Studying documentation
- Researching similar products
Contextual Inquiry
Contextual inquiry is an approach that follows an apprenticeship model: the designer works as an apprentice to the user. There are 4 main principles of contextual inquiry.
Context-Emphasize on going to workplace and seeing what happens.
Partnership-Developer and user should collaborate in understanding the work.
Interpretation-Observations must be interpreted in order to be used in the design and the interpretation should be in cooperation between user and developer.
Focus-Keeping the data gathering focused on your goals.
Data Gathering Guidelines for Requirements
- Focus on identifying the stakeholder's needs.
- Involve all the stakeholder groups.
- Have more than one representative from each stakeholder group involve.-Support data gathering sessions with suitable props
- task descriptions, prototypes.
Data Analysis, Interpretation and Presentation
- Requirement activity is iterated a number of times before a set of stable requirements evolves, the description will expand and clarify.
- 4 techniques that have a user-centered focus and are used to understand user's goals and tasks:
a] Scenarios
b] Uses cases
c] Essential use cases
d] Task analysis
No comments:
Post a Comment