We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set...

27
All Rights Reserved, Copyright Mikio Aoyama, 2005 1 Mikio Aoyama Nanzan University [email protected] http://www.nise.org/ We are NISE: Network Information and Software Engineering Paris, Sep. 31, 2005 Mikio Mikio Aoyama Aoyama Nanzan Nanzan University University [email protected] [email protected] http:// http:// www. www. nise nise .org .org / / We are We are NISE NISE : : N N etwork etwork I I nformation and nformation and S S oftware oftware E E ngineering ngineering Paris, Sep. 31, 2005 Paris, Sep. 31, 2005 RE 2005 RE 2005

Transcript of We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set...

Page 1: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20051

Mikio AoyamaNanzan University

[email protected]://www.nise.org/

We are NISE: Network Information and Software Engineering

Paris, Sep. 31, 2005

MikioMikio AoyamaAoyamaNanzanNanzan UniversityUniversity

[email protected]@nifty.comhttp://http://www.www.nisenise.org.org//

We areWe are NISENISE: : NNetworketwork IInformation and nformation and SSoftwareoftware EEngineeringngineering

Paris, Sep. 31, 2005Paris, Sep. 31, 2005

RE 2005 RE 2005

Page 2: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20052

ScenarioScenarioScenario

Problem and ApproachHanako MethodologyField StudiesDiscussions and ChallengesConclusions

Problem and ApproachProblem and ApproachHanakoHanako MethodologyMethodologyField StudiesField StudiesDiscussions and ChallengesDiscussions and ChallengesConclusionsConclusions

Page 3: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20053

Problem and ApproachDeep Gap Between Users and Developers

Problem and ApproachProblem and ApproachDeep Gap Between Users and DevelopersDeep Gap Between Users and DevelopersDigital Consumer Products are Ubiquitous in Our Life

Mobile Phone, Digital Camera, TV, Car Navigation SystemPerspective Gap: Do We Provide What Users Want ?

Digital Consumer Products are Ubiquitous in Our LifeDigital Consumer Products are Ubiquitous in Our LifeMobile Phone, Digital Camera, TV, Car Navigation SystemMobile Phone, Digital Camera, TV, Car Navigation System

Perspective Gap: Do We Provide What Users Want ?Perspective Gap: Do We Provide What Users Want ?

No more feature. No more feature. I like cute design!I like cute design!

Mobile phones are too Mobile phones are too complex to use. It comes with complex to use. It comes with very thick and heavy manuals very thick and heavy manuals

which I canwhich I can’’t carry with me.t carry with me.

We spent millions We spent millions dollars for developing dollars for developing

many new features, many new features, but ...but ...

Developers = Professional Engineers

Users = Non Technical People

Page 4: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20054

Problem and ApproachEvolution of Mobile Phones

Problem and ApproachProblem and ApproachEvolution of Mobile PhonesEvolution of Mobile Phones

From Mobile Phones (C) to Mobile Terminals (3C)Used at Every Scenes of Our Daily Life From Mobile Phones (C) to Mobile Terminals (3C)From Mobile Phones (C) to Mobile Terminals (3C)Used at Every Scenes of Our Daily Life Used at Every Scenes of Our Daily Life

Wallet, Security(Finger Print Sensor)Full Music PlayerWireless LAN04

GPS/NavigationFlash BrowserVideo(TV) Phone03

Location ServiceVideo High Speed Data3G

02Java AppsSD Card01

Camera00Web Browser, Color DisplayE-mail2.

5G

9998

Music Tone9796

Voice

2G

95Commerce/App.Contents/MediaCommunicationGYr

Page 5: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20055

0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Eng. Student Male

Emg. Student Female

Non-Eng. Student Male

Non-Eng. Student Female

Business over 35

Business under 35

House Wife

More Functionality Just Right Simpler Other

Problem and ApproachOur User Survey [Summer 2004]

Problem and ApproachProblem and ApproachOur User Survey [Summer 2004]Our User Survey [Summer 2004]

A Survey of Our Field Study ShowsMost of Users Prefer “Simpler and Usable”A Survey of Our Field Study ShowsA Survey of Our Field Study ShowsMost of Users Prefer Most of Users Prefer ““Simpler and UsableSimpler and Usable””

Response: 15 People/Cluster * 7 Cluster= 105Response: 15 People/Cluster * 7 Cluster= 105

Page 6: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20056

Problem and ApproachDo We Know Our Users ?Problem and ApproachProblem and Approach

Do We Know Our Users ?Do We Know Our Users ?

Developer, Catch Me if You Can!Developer, Catch Me if You Can!Developer, Catch Me if You Can!

Akihabara and Akihabara and YokohamaYokohamaAug 28, 2005Aug 28, 2005

Page 7: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20057

Problem and ApproachProblems of RE for Digital Consumer Products

Problem and ApproachProblem and ApproachProblems of RE for Digital Consumer ProductsProblems of RE for Digital Consumer Products

Problems of RE for Digital Consumer ProductsUnknown Many UsersWide Variety of Users and Usages (3C)Unexplored New World in RERequirements Acquisition in Practice: Matter of Marketing without Engineering Basis or “Let Smart People Do it”

Conventional ApproachesUser-Centered RE and User-Centered DesignPersonaMarketing Engineering

Lack of Integrated Methodology

Problems of RE for Digital Consumer ProductsProblems of RE for Digital Consumer ProductsUnknown Many UsersUnknown Many UsersWide Variety of Users and Usages (3C)Wide Variety of Users and Usages (3C)Unexplored New World in REUnexplored New World in RERequirements Acquisition in Practice: Matter of Requirements Acquisition in Practice: Matter of Marketing without Engineering Basis or Marketing without Engineering Basis or ““Let Smart Let Smart People Do itPeople Do it””

Conventional ApproachesConventional ApproachesUserUser--Centered RE and UserCentered RE and User--Centered DesignCentered DesignPersonaPersonaMarketing EngineeringMarketing Engineering

Lack of Integrated Methodology Lack of Integrated Methodology

Page 8: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20058

StrategyUser FocusIntegrated Methodology with Engineering ToolsQuantitative Measure

Assumption: Incremental Development

StrategyStrategyUser FocusUser FocusIntegrated Methodology with Engineering ToolsIntegrated Methodology with Engineering ToolsQuantitative MeasureQuantitative Measure

Assumption: Incremental DevelopmentAssumption: Incremental Development

Telcom. Operator

Users Engineering

Hanako Methodology Our Strategy

HanakoHanako Methodology Methodology Our StrategyOur Strategy

GoalGoalGoalFrom System-Centered to User-CenteredFrom SystemFrom System--Centered to UserCentered to User--CenteredCentered

From Product-Out to Market-InFrom ProductFrom Product--Out to MarketOut to Market--InIn

Marketing

Bridging Gap between Users, Bridging Gap between Users, Marketing and EngineeringMarketing and Engineering

Conventional Way ofConventional Way ofRequirements Acquisition Requirements Acquisition

Page 9: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 20059

Hanako MethodologyFind a User by Persona, Hnako

HanakoHanako MethodologyMethodologyFind a User by Persona, Find a User by Persona, HnakoHnako

Hanako: Popular Name of Japanese Women, Like Mary*Find Hanako in Unknown Many Users HanakoHanako: Popular Name of Japanese Women, Like Mary*: Popular Name of Japanese Women, Like Mary*Find Find HanakoHanako in Unknown Many Users in Unknown Many Users

Dis

trib

utio

n of

Req

uire

men

ts(N

umbe

r of F

eatu

res)

Target Users

Cast

Elicitation Strategy of Hanako Method

User Profile(Ex.: Computer Literacy)Conventional

Elicitation Strategy

Dis

trib

utio

n of

Valu

e of

Req

uire

men

ts

(Num

ber o

f Use

rs)

Pers

ona

Pers

ona

Han

ako

= Pr

imar

y Pe

rson

a

Pers

ona

Prof

essi

onal

D

evel

oper

s

*Source: http://www.namestatitics.com

Page 10: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200510

Problem and Approach Persona

Problem and Approach Problem and Approach PersonaPersona

Persona: Social Role of People (Mask) = Model of Target Users

Psychology by C. G. JungPersona Method: Design Based on Persona

Proposed by A. Cooper“Design for One”

Cast: A Set of Personas3~13 Personas per SystemPrimary Persona

Problem: No Methodology

Persona: Social Role of People Persona: Social Role of People (Mask) = Model of Target Users(Mask) = Model of Target Users

Psychology by C. G. JungPsychology by C. G. JungPersona Method: Design Based Persona Method: Design Based on Personaon Persona

Proposed by A. CooperProposed by A. Cooper““Design for OneDesign for One””

Cast: A Set of PersonasCast: A Set of Personas3~13 Personas per System3~13 Personas per SystemPrimary PersonaPrimary Persona

Problem: No MethodologyProblem: No Methodology

Page 11: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200511

Hanako MethodologyProcess

HanakoHanako MethodologyMethodologyProcessProcess

2 Stages: Persona Identification and Persona-Scenario Analysis2 Stages: Persona Identification and 2 Stages: Persona Identification and PersonaPersona--Scenario AnalysisScenario Analysis

1. Disjoint Clustering of Target Users 1. Disjoint Clustering of Target Users

2. Identification of Personas by (Inverse) Conjoint Analysis

2. Identification of Personas by (Inverse) Conjoint Analysis

3. Identification/Synthesis of Primary Persona

3. Identification/Synthesis of Primary Persona

Persona Pattern

4. Description of Primary Persona and Cast

4. Description of Primary Persona and Cast

Questionnaireon Features Questionnaire

on Scenarios

PersonaIdentification 5. Persona-Scenario

Analysis: Identification of Requirements Hot Spots

5. Persona-Scenario Analysis: Identification of Requirements Hot Spots

PersonaScenarioAnalysis

Page 12: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200512

Preferred Users

Hanako Methodology(Inverse) Conjoint Analysis

HanakoHanako MethodologyMethodology(Inverse) Conjoint Analysis(Inverse) Conjoint Analysis

Conjoint Analysis from Mathematical Psychology (1964)Ask Known-Users on Preferred Attributes of ProductsFind a Set of Preferred Attributes of Products: Features, Cost, Design, …

Conjoint Analysis from Mathematical Psychology (1964)Conjoint Analysis from Mathematical Psychology (1964)Ask KnownAsk Known--Users on Preferred Attributes of ProductsUsers on Preferred Attributes of ProductsFind a Set of Preferred Attributes of ProductsFind a Set of Preferred Attributes of Products: Features, Cost, : Features, Cost, Design, Design, ……

Preference

A Set of Candidate User Clusters

Known Attributes

PreferenceA Set of Known Users

CandidateAttributes

Preferred Attributes

(Inverse) Conjoint AnalysisAsk a Set of Candidate Clusters of Users on Preferred and Target Attributes of ProductsFind a Set of User Clusters Sensitive to a Set of Attributes

(Inverse) Conjoint Analysis(Inverse) Conjoint AnalysisAsk a Set of Candidate Clusters of Users on Preferred and Ask a Set of Candidate Clusters of Users on Preferred and Target Attributes of ProductsTarget Attributes of ProductsFind a Set of User ClustersFind a Set of User Clusters Sensitive to a Set of AttributesSensitive to a Set of Attributes

Preferred User Clusters

Page 13: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200513

Field Studies1st Field Study: Overview

Field StudiesField Studies11stst Field Study: OverviewField Study: Overview

Time: Summer 2003Goal: To Validate Hanako Methodology Participants: 14-17 Person * 4 Groups = 60Measure: Usage Frequency of Services

Time: Summer 2003Time: Summer 2003Goal: To Validate Goal: To Validate HanakoHanako Methodology Methodology Participants: 14Participants: 14--17 Person * 4 Groups = 6017 Person * 4 Groups = 60Measure: Usage Frequency of ServicesMeasure: Usage Frequency of Services

Calculator, Alarm Clock, Schedule, Secret Memory, Navigation

Commerce/Application

Image (Photo), Video (Movie), Web AccessContents/Multimedia

E-mail, Face Characters, Image Sign, Copy & Paste, AttachmentE-mail

Redialing, Vibrator, Personal Calling Tone, Call Directory, Call GroupVoice

Communi-cation

ServicesService Groups606029293131TotalTotal323215(PS F)15(PS F)17(ES F)17(ES F)FemaleFemale282814(PS M)14(PS M)14(ES M)14(ES M)MaleMale

TotalTotalPS (Policy Studies Students)PS (Policy Studies Students)ES (Engineering Students)ES (Engineering Students)CategoryCategory

Page 14: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200514

Field Studies1st Field Study: 3 Usage Patterns

Field StudiesField Studies11stst Field Study: 3 Usage PatternsField Study: 3 Usage Patterns

Variant Service: Users’ Preference Varies (High SD)Common Services: Most Users Use (High Ave. Low SD)Marginal Services: Few Users Use (Low Ave. Low SD)

Variant Service: UsersVariant Service: Users’’ Preference Varies (High SD)Preference Varies (High SD)Common Services: Most Users Use (High Ave. Low SD)Common Services: Most Users Use (High Ave. Low SD)Marginal Services: Few Users Use (Low Ave. Low SD)Marginal Services: Few Users Use (Low Ave. Low SD)

Marginal Services

Common Services

VariantServices

0

1

2

3

4

5Redial

Calculator

Vibrator

Personal Calling Tone

User Directory

Directory Group

Alarm Clock

Scheduler

Secret MemoryE-mail AttachmentE-mail Copy & Paste

Symbols

Face Characters

Receive Folders

Image

Movie

Web Access

Jave App(i-Appli)

Navigation

ES FES MPS FPS M

0

1

2

3

4

5Redial

Calculator

Vibrator

Personal Calling Tone

User Directory

Directory Group

Alarm Clock

Scheduler

Secret MemoryE-mail AttachmentE-mail Copy & Paste

Symbols

Face Characters

Receive Folders

Image

Movie

Web Access

Jave App(i-Appli)

Navigation

ES FES MPS FPS M

Page 15: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200515

Field Studies1st Field Study: Persona Identification

Field StudiesField Studies11stst Field Study: Persona IdentificationField Study: Persona IdentificationFinding Persona as the Highest Responding User Category

Service Coverage (Total Score of Usage)= Sum (Vi)Vi: Average Usage Ratio for Each Service per Clusteri: For All Services per User Cluster

Simple Primary Persona: Female Engineering Students (ES F)

Identified as the Significantly Outperforming Single Cluster of Users

Finding Persona as the Highest Responding User Finding Persona as the Highest Responding User CategoryCategory

Service Coverage (Total Score of Usage)= Sum (VService Coverage (Total Score of Usage)= Sum (Vii))VVii: Average Usage Ratio for Each Service per Cluster: Average Usage Ratio for Each Service per Clusteri: For All Servicesi: For All Services per User Clusterper User Cluster

SimpleSimple Primary Persona: Female Engineering Primary Persona: Female Engineering Students (ES F)Students (ES F)

Identified as the Significantly Outperforming Single Identified as the Significantly Outperforming Single Cluster of UsersCluster of Users

55.8 [0.872] (PS F)55.8 [0.872] (PS F)64.0[1.00] (ES F)64.0[1.00] (ES F)FemaleFemale53.4[0.834] (PS M)53.4[0.834] (PS M)55.5[0.867] (ES M)55.5[0.867] (ES M)MaleMale

PS (Policy Studies Students)PS (Policy Studies Students)ES (Eng. Students)ES (Eng. Students)CategoryCategory

Note: [] Denotes RatioNote: [] Denotes Ratio

Page 16: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200516

Field Studies1st Field Study: Persona Description

Field StudiesField Studies11stst Field Study: Persona DescriptionField Study: Persona Description

1) Personal Profile1) Personal Profile-- Come to school 5 days a week, works part time job at a restauraCome to school 5 days a week, works part time job at a restaurant during nt during weekendweekend-- Study computer eng., and working for a term paper on software eStudy computer eng., and working for a term paper on software eng.ng.-- Play tennis once a weekPlay tennis once a week-- Working with her personal Web pageWorking with her personal Web page

2) Profile of Mobile Phone Usage2) Profile of Mobile Phone Usage-- Daily use of eDaily use of e--mail, browsing the webmail, browsing the web-- Use the phone to some extent without reading manualUse the phone to some extent without reading manual-- Buy new phone at every one year and a halfBuy new phone at every one year and a half-- Send or receive some 15 eSend or receive some 15 e--mail per day(4lines/email per day(4lines/e--mail)mail)-- Call 3 times a week (less than 10 min. per call)Call 3 times a week (less than 10 min. per call)

3) Specific Requirements to Mobile Phone3) Specific Requirements to Mobile Phone-- To make eTo make e--mail bettermail better

PersonaPersonaName: Hiroko Name: Hiroko NiwaNiwaGroup: Senior Female Student Major in EngineeringGroup: Senior Female Student Major in Engineering

Page 17: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200517

Field Studies2nd Field Study: Overview

Field StudiesField Studies22ndnd Field Study: OverviewField Study: Overview

Time: Summer 2004Goal: To Analysis New Features of 3G Mobile PhonesParticipants: 15 Persons * 7 Groups = 105

Time: Summer 2004Time: Summer 2004Goal: To Analysis New Features of 3G Mobile PhonesGoal: To Analysis New Features of 3G Mobile PhonesParticipants: 15 Persons * 7 Groups = 105Participants: 15 Persons * 7 Groups = 105

Java Application (i-Appli), Navigation, WalletCommerce/App.Image(Photo), Video(Movie), Web AccessContents/MultimediaE-mail, Face Characters, Mail Inquiry, AttachmentE-mail

Redialing, Vibrator, Drive Mode, Call History, Call Hold, Personal Calling Tone, Call Directory, Call GroupVoiceCommuni-

cation

ServicesService Groups

10510515151515151530303030TotalTotal151515(PS F)15(PS F)15 (ES F)15 (ES F)FemaleFemale001515

(BP 35(BP 35--))1515

(BP35+)(BP35+)15 (PS M)15 (PS M)15 (ES M)15 (ES M)MaleMale

TotalTotalHouse House WifeWife

BusinessBusiness(<35)(<35)

BusinessBusiness(>=35)(>=35)

PolPol. Stud.. Stud.StudentsStudents

Eng. Eng. StudentsStudentsCategoryCategory

Page 18: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200518

Field Studies2nd Field Study: Distribution of Preference

Field StudiesField Studies22ndnd Field Study: Distribution of PreferenceField Study: Distribution of Preference

Overview of Preference Distribution

Overview of Overview of Preference Preference DistributionDistribution

Redial

ing

Call H

istory

Call H

old

Face C

haracte

rs

Mail Inq

uiryIm

age

VideoWeb

Java

Applic

ation

Naviga

tion

Vibrator

Drive M

ode

Calcula

tor

Alarm C

lock

ES Male

ES Female

PS Male

PS Female

BP over 35

BP under 35

House Wife

0.001.002.00

3.004.00

5.00

ES MaleES FemalePS MalePS FemaleBP over 35BP under 35House Wife

Page 19: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200519

Field Studies2nd Field Study: Persona Identification

Field StudiesField Studies22ndnd Field Study: Persona IdentificationField Study: Persona Identification

Composite Persona: Female Students = Engineering Female Students + Policy Study Female Students

No Single Leading Cluster Identified but 2 Clusters of Female Students can Covers Most

CompositeComposite Persona: Persona: Female Students = Engineering Female Students + Female Students = Engineering Female Students + Policy Study Female StudentsPolicy Study Female Students

No Single Leading Cluster Identified No Single Leading Cluster Identified but 2 Clusters of Female Students can Covers Mostbut 2 Clusters of Female Students can Covers Most

46.4 [1.00]46.4 [1.00]27.927.9

[0.601][0.601]46.3 (PS F)46.3 (PS F)46.4 (ES F)46.4 (ES F)

FemaleFemale

NANA38.438.4[0.828][0.828]

(BP 35(BP 35--))

30.030.0[0.647][0.647]

(BP35+)(BP35+)

41.9 [0.903]41.9 [0.903](PS M)(PS M)

40.5[0.873]40.5[0.873](ES M)(ES M)MaleMale

House WifeHouse WifeBusinessBusiness(<35)(<35)

BusinessBusiness(>=35)(>=35)

PolPol. Stud.. Stud.StudentsStudents

Eng. Eng. StudentsStudentsCategoryCategory

Page 20: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200520

Field Studies2nd Field Study: 3 Usage Patterns

Field StudiesField Studies22ndnd Field Study: 3 Usage PatternsField Study: 3 Usage Patterns

3 Usage Patterns 3 Usage Patterns 3 Usage Patterns

Marginal Services

Common Services

VariantServices

0.00

1.00

2.00

3.00

4.00

5.00Redialing

Call History

Call Hold

Face Characters

Mail Inquiry

Image

Video

Web

Java Application

Navigation

Vibrator

Drive Mode

Calculator

Alarm Clock

ES Male ES Female PS Male PS Female

BP over 35 BP under 35 House Wife

0.00

1.00

2.00

3.00

4.00

5.00Redialing

Call History

Call Hold

Face Characters

Mail Inquiry

Image

Video

Web

Java Application

Navigation

Vibrator

Drive Mode

Calculator

Alarm Clock

ES Male ES Female PS Male PS Female

BP over 35 BP under 35 House Wife

Page 21: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200521

Field Studies2nd Field Study: Persona-Scenario Analysis

Field StudiesField Studies22ndnd Field Study: PersonaField Study: Persona--Scenario AnalysisScenario Analysis

GoalTo Find out Obstacles of Slow Acceptance of 3G Mobile Phones and Possible Extension Points

ApproachScenario Analysis with Primary Persona on the Usages of New Features of 3G Mobile PhonesTrial Use & Benchmarking with Various 3G Phones

Targeted Scenarios in Features for 3G PhonesFeatures for Called Parties: Unique to Mobile PhonesDeco-Mail: Mail with Decorations: For FemaleWallet Feature: Brand New Features to 3GMenu-Guided Feature: Usability Improvement

GoalGoalTo Find out Obstacles of Slow Acceptance of 3G To Find out Obstacles of Slow Acceptance of 3G Mobile Phones and Possible Extension PointsMobile Phones and Possible Extension Points

ApproachApproachScenario Analysis with Primary Persona on the Scenario Analysis with Primary Persona on the Usages of New Features of 3G Mobile PhonesUsages of New Features of 3G Mobile PhonesTrial Use & Benchmarking with Various 3G PhonesTrial Use & Benchmarking with Various 3G Phones

Targeted Scenarios in Features for 3G PhonesTargeted Scenarios in Features for 3G PhonesFeatures for Called Parties: Unique to Mobile PhonesFeatures for Called Parties: Unique to Mobile PhonesDecoDeco--Mail: Mail with Decorations: For FemaleMail: Mail with Decorations: For FemaleWallet Feature: Brand New Features to 3GWallet Feature: Brand New Features to 3GMenuMenu--Guided Feature: Usability ImprovementGuided Feature: Usability Improvement

Page 22: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200522

Field Studies2nd Field Study: Persona-Scenario Analysis

Field StudiesField Studies22ndnd Field Study: PersonaField Study: Persona--Scenario AnalysisScenario Analysis

Analysis of Scenarios of Services for Called PartiesFinding:

A Set of Caller Identification Features are Hot Spot to Female Users, Primary Persona, Opportunity of ValueSpeed Dialing is Replaced by Dictionary Service

Analysis of Scenarios of Services for Called PartiesAnalysis of Scenarios of Services for Called PartiesFinding: Finding:

A Set of Caller Identification Features are Hot Spot to A Set of Caller Identification Features are Hot Spot to Female Users, Primary Persona, Opportunity of ValueFemale Users, Primary Persona, Opportunity of ValueSpeed Dialing is Replaced by Dictionary ServiceSpeed Dialing is Replaced by Dictionary Service

0.00

0.10

0.20

0.30

0.40

0.50

0.60

0.70

0.80

0.90

1.00

Absence PersonalCalling Tone

PersonalCalling Image

Don't Disturb Speed Dialing

Men E SWomen E SMen GA SWomen GA SBP 35 or OverBP under 35House Wife

Page 23: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200523

Field Studies2nd Field Study: Persona-Scenario Analysis

Field StudiesField Studies22ndnd Field Study: PersonaField Study: Persona--Scenario AnalysisScenario AnalysisAnalysis of Deco-Mail Scenarios: Targeted to FemaleFinding: Hot Spot of Single Usage Patterns

70% Users Use Only One Scenario: Input Text First, then Make Decoration: Intuitive Pattern of Human (Affordance)Other Scenarios are Not Preferred

Analysis of DecoAnalysis of Deco--Mail Scenarios: Targeted to FemaleMail Scenarios: Targeted to FemaleFinding: Hot Spot of Single Usage Patterns Finding: Hot Spot of Single Usage Patterns

70% Users Use Only One Scenario: Input Text First, then Make 70% Users Use Only One Scenario: Input Text First, then Make Decoration: Intuitive Pattern of Human (Affordance)Decoration: Intuitive Pattern of Human (Affordance)Other Scenarios are Not PreferredOther Scenarios are Not Preferred

S0

Decoration

Enter Text

Select DecoType

EndSelect Range

DecorationChange Decoration

Enter Text

Change Decoration

SelectRange

90%

20%20%20%

70%

70%90%

10%

10% 10%

10%100% 100%

70%

Select DecoType

Select DecoType

Page 24: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200524

Field Studies2nd Field Study: Verification of Field Studies

Field StudiesField Studies22ndnd Field Study: Verification of Field Studies Field Study: Verification of Field Studies

Consistency Checking of 10 Common Features Same Trend Observed in both 2003 and 2004Consistency Checking of 10 Common Features Consistency Checking of 10 Common Features Same Trend Observed in both 2003 and 2004Same Trend Observed in both 2003 and 2004

0.01.02.03.04.05.0

Redial

Face C

har.

Imag

e

Video

WebJa

va A

ppNav

igation

Vibrator

Calculat

orAlar

m Clock

2004 2003

Snake Graph

Page 25: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200525

Discussions and ChallengesDiscussions and ChallengesDiscussions and Challenges

Effectiveness of Hanako MethodEffective to Identify Persona and Hot Spots

“Not Effective” Experience without a Method for Finding Persona [K. Rönkkö, et al., 2004]

Rich Context of PersonaIntuitive Understanding of Context by Calling Name, Like Design PatternsRisk of Rich Subjective Contextual Information

LimitationWith Some Heuristics, Needs Tool Support

Response from Developers at a Workshop (Jan. 2005)Some 20 Developers & a Few Marketing People from FujitsuSome Expected, Some Surprises, Some Need Further Proof

Effectiveness of Effectiveness of HanakoHanako MethodMethodEffective to Identify Persona and Hot SpotsEffective to Identify Persona and Hot Spots

““Not EffectiveNot Effective”” Experience without a Method for Finding Experience without a Method for Finding Persona [K. Persona [K. RRöönkknkköö, et al., 2004], et al., 2004]

Rich Context of PersonaRich Context of PersonaIntuitive Understanding of Context by Calling Name, Like Intuitive Understanding of Context by Calling Name, Like Design PatternsDesign PatternsRisk of Rich Subjective Contextual InformationRisk of Rich Subjective Contextual Information

LimitationLimitationWith Some Heuristics, Needs Tool SupportWith Some Heuristics, Needs Tool Support

Response from Developers at a Workshop (Jan. 2005)Response from Developers at a Workshop (Jan. 2005)Some 20 Developers & a Few Marketing People from FujitsuSome 20 Developers & a Few Marketing People from FujitsuSome Expected, Some Surprises, Some Need Further ProofSome Expected, Some Surprises, Some Need Further Proof

Page 26: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200526

ConclusionsConclusionsConclusionsProblems and Opportunities

Requirements Engineering for Software Embedded in Digital Consumer Products

Hanako MethodologyFinding User First: Finding Persona with (Inverse) Conjoint AnalysisFinding Requirements Hot Spots with Persona-Scenario Analysis

2 Field Studies in 2 YearProof of the Effectiveness of MethodologySome Findings

Integration of RE with Marketing Engineering

Problems and OpportunitiesProblems and OpportunitiesRequirements Engineering for Software Requirements Engineering for Software Embedded in Digital Consumer ProductsEmbedded in Digital Consumer Products

HanakoHanako MethodologyMethodologyFinding User First: Finding Persona with Finding User First: Finding Persona with (Inverse) Conjoint Analysis(Inverse) Conjoint AnalysisFinding Requirements Hot Spots with PersonaFinding Requirements Hot Spots with Persona--Scenario Analysis Scenario Analysis

2 Field Studies in 2 Year2 Field Studies in 2 YearProof of the Effectiveness of MethodologyProof of the Effectiveness of MethodologySome FindingsSome Findings

Integration of RE with Marketing EngineeringIntegration of RE with Marketing Engineering

Page 27: We are NISE: Network Information and Software Engineering ... · *“Design for One”)Cast: A Set of Personas *3~13 Personas per System *Primary Persona)Problem: No Methodology Persona:

All Rights Reserved, Copyright Mikio Aoyama, 200527

Merci and Thank You !

Questions and Comments ?

MerciMerci and Thank You !and Thank You !

Questions and Questions and Comments ?Comments ?