8. Personas Requirements, user stories, scenarios and use cases

Question 1

A cosa servono Personas, scenarios, user stories and use case?

Answer 1

4 user research methods to help you create reliable and realistic representations of your target users and design accordingly

Question 2

Cos’è una personas?

Answer 2

A user persona is a character that represents a potential user of your website or app.
In user centered-design, personas help the design team to target their designs around users.

Question 3

Come si raccolgono dati per le personas?

Answer 3

1. task analysis (card sorting, first click testing etc.)
2. feedback (contextual interviews and focus groups)
3. prototyping (experimenting with ideas prior to developing them)

Question 4

Quante e quali personas puoi definire?

Answer 4

1. Proto-personas
2. Qualitative -personas
3. Statistical personas

Question 5

Quante personas?

Answer 5

Segui il pareto principles, design the 20% of users that will use for the 80% your product

Question 6

Che informazioni tiene una user personas?

Answer 6

1.Demographic details
2. Attitudinal and/or cognitive details
3. Goals and motivations for using the product
4. Behavioral details
5. Personal details

Question 7

Cos’è un archetipo?

Answer 7

È una persona però astratto, non è identificato con nessun individuo in particolare

Question 8

Cosa sono i requirments?

Answer 8

a requirement is a service, function or feature that a user needs.
Requirements can be functions, constraints, business rules or other elements that must be present to meet the need of the intended users.

Question 9

Categorie di requirments

Answer 9

Functional requirments and non Functional requirments

Question 10

Cosa sono i Functional requirments ?

Answer 10

Functional Requirements (FRs) express function or feature and define what is required, e.g.
-Visit customer site
-Obtain conference venue
The requirements do not state how a solution will be physically achieved.

Question 11

Cosa sono i Non Functional requirments?

Answer 11

Non-functional Requirements (NFRs) define how well, or to what level a solution needs to behave.
They describe solution attributes such as security, reliability, maintainability, availability (and many other “…ilities”), performance and response time, e.g.
- responding within 2 seconds
- being available 24 hours per day, every day

Question 12

Cosa sono le user stories?

Answer 12

A user story is a short statement or abstract that identifies the user and their need/goal. It determines who the user is, what they need and why they need it.
There is usually one user story per user persona.

Question 13

Cosa sono le user stories in prospettiva dei requirments?

Answer 13

A User Story is a requirement expressed from the perspective of an
end-user goal.

Question 14

Come scrivere una user story?

Answer 14

It’s super simple to write a user story.
“As a [role], I want [feature] because [reason].”

Question 15

Chi scrive le user story?

Answer 15

Over the course of a good agile project, you should expect to have user story examples written by each team member.

Question 16

Come si chiamano le user stories ampie?

Answer 16

epiche

Question 17

Cos’è uno scenario?

Answer 17

A scenario is a situation that captures how users perform tasks on your site or app. It is essentially a development of the user story, and can relate to multiple target users.

Question 18

Uno scenario può esere suddiviso in …

Answer 18

use cases that describe the flow of tasks that any one user takes in a given functionality or path.

Question 19

Come si scrive uno scenario?

Answer 19

answer the following key questions:
-Who is the user? Use the personas that have been developed to reflect the real, major user groups coming to your site.
-Why does the user come to the site? Note what motivates the user to come to the site and their expectations upon arrival, if any.
-What goals does he/she have? Through task analysis, you can better
understand the what the user wants on your site and therefore what the site must have for them to leave satisfied.

Question 20

Cosa sono gli use cases?

Answer 20

A use case is a written description of how users will perform tasks on your app. It outlines, from a user’s point of view, a system’s behavior as it responds to a request.
Each use case is represented as a sequence of simple steps, beginning with a user’s goal and ending when that goal is fulfilled.

Question 21

Scenario vs Use cases?

Answer 21

A Scenario involves a situation that may have single or multiple actors that take a given functionality or path to achieve their goal.

A use case involves an actor and the flow that a particular actor takes in a given functionality or path. These often get grouped so you have a “set” of use cases to account for each scenario.

The main difference is “perspective”.

Question 22

Quali soo gli elementi di uno use case?

Answer 22

actor
stakeholders
Primary actor
Preconditions
Triggers
Main success scenario
Alternatives paths

Question 23

Come scrivere uno use case?

Answer 23

Kenworthy (1997) outlines the following steps:
1. Identify who is going to be using the website.
2. Pick one of those users.
3. Define what that user wants to do on the site. Each thing the use does on the site becomes a use case.
4. For each use case, decide on the normal course of events when that user is using the site.
5. Describe the basic course in the description for the use case.
6. When the basic course is described, consider alternate courses of events and add those to “extend” the use case.
7. Look for commonalities among the use cases. Extract these and note them as common course use cases.
8. Repeat the steps 2 through 7 for all other users.