- 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.
Example:- Having to fulfill a requirement of loading time within 3 seconds and teenage children should find the site appealing.
 |
| 3 second loading requirement to log in the game Pockie Ninja. |
 |
| Pockie Ninja Game site. |
In Software Engineering, there are 2 types of requirements:-
1) Functional requirements (what does the system do)
2) Non-functional requirements (what are the constraints there are on the system and its development)
Generally, there are many like:-
1) Functional requirement (capture what the product should do)
2) Data requirement (capture the type, votality, size/amount and persistence of the product)
3) Environmental requirement (context of use)
4) User characteristics (capture the key attributes of an intended user group)
5) Usability and user experience goals (how well the user perform to achieve applications goals and
their perceptions)
Environmental requirements has 4 characteristics:-
a. Physical environment - Lighting, noise and dust.
b. Social environment - Social aspects of interaction design collaboration and coordination (how many user interact with the design)
c. Organizational environment - How good is the user support
d. Technical environment - The different technologies the product will work on (constraints)
User characteristics is to gather samples on:-
- user's ability, skills, nationality, educational background, preferences, personal circumstances, physical or mental disabilities.
- collection of attributes "a typical user" is called a User Profile.
- a product may have different user profiles.
- to bring user profile to life, they turned it into a number of personas.
- Personas are rich descriptions of typical users.
Samples (gathered in large amount) --change to--> Personas (and also given names) like:
Persona A: Joe Persona B: Amy
User Goals (also known as user performance)- effectiveness, efficiency, safety, utility, learnability and tracking.
User Experience Goals (also known as user perceptions)- fun, enjoyable, pleasurable and aesthetically.
Data Gathering
Interviews:
Semi-structured- preset questions
Unstructured- can ask more questions than the given preset questions.
Focus group
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
Data Gathering Method must have more than one technique. Triangulation is the best way to obtain a better results of data.
Contextual Inquiry- an approach that follows apprentice model: designer works as an apprentice to user
1) Context:- Emphasize on going to workplace and see what happen.
2) Partnership:- Developer and user collaborate in understanding the work
3) Interpretation:- Observations must be interpreted.
4) Focus:- Data gather focus on user.
Stockholders: Everyone who is involved in building the application.
From prototypes, task and descriptions all of it is an Iterative process (repeating process)
Four 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 in requirement activity?
Understand User + Produce a set of stable requirements = Design
A design and it's processes is mostly based on the "Users".
User requirements ====> Lots of Research ====> Analyze ====> Categorize ===> Design
No comments:
Post a Comment