CRIA Les2 Scope

7/31/2019 CRIA Les2 Scope

1/21

Create a Rich Internet Application

Lesson 2

Scope

Informatica Communicatie Academie

Hogeschool Arnhem Nijmegen

1


2/21

Learning aims

After this lesson you:

Know what we mean by a User Analysis

Know what we mean byrequirements

Know what assignment you have to do for the next lesson.

2


3/21

Topics

User Analysis

Userprofiles

Personas

Requirements

Functionality (business, user and technical)

Prioritize requirements

3


4/21

Gebruikersanalyse

Understanding the user(s)

Comparable user(s) are grouped in auserprofile(segmentation)

Determine for every userprofilemeasurable attributes(attributes and values)

User analysis

4


5/21

Hoe onderzoeken?

The most important distinction between behaviour

patterns (read: measurable attributes) are(1):

Activities (what the user does; frequency and volume);Attitudes (How the user thinks about the product domain andtechnology);

Aptitudes (What education and traing the user has;the capability to learn)

Motivations (Why the user is engaged in the product domain);Skills (user capabilities related to the product domain and

technology);

(1) See About Face 3, Cooper, Reinmann and Cronin, page 98.

User analysis

5


6/21

Hoe onderzoeken?

Collect data (to understand the user)

Desk research;Interviewing;Workplace visit;Brainstorming with users.

Always mention you re sources and giveevidence!

User analysis

5


7/21

Gebruikersprofiel opbouw

Userprofile first! Make the userprofile alife with

a Persona

Make the context alife with

a Moodboard

Jeroen van West (34, Davi-Recept-gebruiker) uitVlaardin-gen: "Wij zijnenthousiaste Davilex-

gebruikers. Sinds twee jaarhebben we zon multimedia PCen daar doen we van alles mee.Marlies heeft laatst met Davi-

Tuin onze tuin ontworpen, nou,hartstikke mooi hoor. Koken

vinden we allebei leuk, dustoen we de reclame van Davi-Recept zagen hebben we het

meteen gekocht. Eigenlijkvooral voor die leuke filmpjesmet Cas Spij-kers. Nee, wegebruiken het niet elke dag,alleen af en toe als we wat

meer tijd hebben, want de PCstaat op onze hobbykamer op

zolder en je gaat niet natuurlijksteeds naar boven lopen omeen recept uit te printen. De

lekkerste recepten hebben wedaarom afgedrukt en die liggenin de keuken in een mapje bij

de andere kookboeken."

User analysis

7


8/21

Gebruikersprofiel

Userprofile contains attributes

Activities (what the user does; frequencyand volume);

Attitudes (How the user thinks about theproduct domain and technology);

Aptitudes (What education and traing the user has;capability to learn)

Motivations (Why the user is engaged in theproduct domain);

Skills (user capabilities related to the product domainand technology);

Valuesin the profile gives

A realistic picture of the group,

based on sources which can be

inspected

There are always more userprofiles (novice, new users, experienced users)!

User analysis

8


9/21

Voorbeeld profiel

Attribute Value

Name usergroup Young kitchen buyer

User amount (size of the usergroup) 120.000

Age 25 t/m 35 years

Gender Male and Female

Education University

Culture Dutch

Language Nederlands

Main tasks Searching for kitchens, ordering parts, printing of (self designed) kitchen etc.

Experience with the tasks Little experience*

Experiencewith communication systems Experienced with phones, internet and e-mail

Experience with computers Uses computers less than 4 hours each week

Experience other devices 90% windows, 10% different

Experience with previous versions of the application No experience

Experience with other applications No

Specific knowledge / special skills No

Werk environment 90% Office, 10% home

Live environment Starter in own house (90% renting, 10% owners)

Short description Persons who are searching a new affordable kitchen

Bronnen:

CBS: table kitchenbuyers, url: www.cbs.nl/keukenmarkt/keukenkopers.asp (dd 7-7-2010)*=guess of the executive

User analysis

9

Userprofile:
http://www.cbs.nl/keukenmarkt/keukenkopers.asphttp://www.cbs.nl/keukenmarkt/keukenkopers.asp


10/21

Persona

Apersonais the representation of a group usersIt reads as a report about a fictional person

Based on data from the userprofileIn the Persona is covered: activities, attitude, attitude, environment,

aptitude,motivation, skills and fictional personal details

A persona prohibits an Elastic User

(built whatever you want, and seems convenient)

Completes the User profilePuts the focus on the main points

Makes the User alife

http://wiki.fluidproject.org/display/fluid/Persona+Format

User analysis

10
http://wiki.fluidproject.org/display/fluid/Persona+Formathttp://wiki.fluidproject.org/display/fluid/Persona+Format


11/21

Voorbeeld persona

User analysis

111


12/21

Gebruikersanalyse samengevat

A user analysis contains for each usergroup a userprofile.

Each usergroup contains a persona

The context of the application can be enriched and

captured with a moodboard

User Analysis

112


13/21

Functional requirements

Purpose

The description of the expectations of the functionality

(and content) of the RIA

What functionality do we have to support?

What interaction styles are preferred?http://developer.yahoo.com/ypatterns/

http://www.welie.com/patterns/

What is the difficulty?

What is the importnace?

Which techniques are we going to use?

Which content (reports, movies, pictures, photos, maps) are we goingto support?

Functional Requirements

113
http://developer.yahoo.com/ypatterns/http://www.welie.com/patterns/http://www.welie.com/patterns/http://developer.yahoo.com/ypatterns/


14/21


Method:

Functions:what is it what the user wants to do?

Interaction styles: how does the userwants to do this in an efficientway?

Difficulty: what capabilities does the user possess (or have to learn?) Prioritize: what is most important to the user?

Technique: what are the constraints for success?

On the base of a checklist the definitive lists will exist which can be

prioritized with a MOSCOW method.

(Explanation on the whiteboard)!

Everything has to fit in relation with the user needs and site objectives


14


15/21

Site Objectives

Environment analyses

User Needs

Requirements

Requirements

Requirements

R

e

q

ui

r

e

m

e

nt

s

MOSCOW LIST

Vision &

ScopeDocument

l l


16/21


Functional Requirements example:

15

Site Objectives:

1. Travelers will be able to pick up experiences from other travelers in a

in a certain area;

2. A traveler can leave behind a trail, on a specific time and a specific place

with his mobile device;

3. A trail is a geographical location, a short description and a photo or

video;

4. Travelers can read comments from others on the trails they left behind.

i l i l


17/21


Functional Requirements example:

15

Reference Description Priority

Req-01 Backpackers need to be able to spot trails on their

mobile device in a certain distance.

Must Have

Req-02 The application supports leaving trails on specific

locations. These trails can contain text, foto's and

videos and can be placed with the mobile device.

Must Have

Req-03 Authorized travellers can read and modify their

own trails as they can read the comments on trails

placed by others.

Must Have

F i l R i


18/21


Result:

A document that contains all the information for the

designteam necessary to make a design of the

supported functionality of the application.


15

A i


19/21

Opdracht 1

In a nutshell:

1. Look in the Studyguide for assignment-02;

2. All necessary documents are on Online;3. Work on the parts 1 to 5 (assignment-02) and put them

in the Strategy and Scopedocument according to thegiven structure;

4. Use youre creativity!

Assignment

20

R l


20/21

Inleveren

Strategy and Scope document

Result

21


21/21

Meer weten?

Sources

http://developer.yahoo.com/ypatterns/http://www.welie.com/patterns/

22
http://developer.yahoo.com/ypatterns/http://www.welie.com/patterns/http://www.welie.com/patterns/http://developer.yahoo.com/ypatterns/

Documents

CRIA Les2 Scope