Farhan Aadil
COMSATS Institute of Information Technology
Lecture 18
Goal-Directed Design Methodology
In the Last Lecture
• Software Lifecycle Models
• HCI Lifecycle Models
In Today’s Lecture
Success Factors for Technology Products
Product
D
es
ira
bi
lit
y
C
ap
ab
ility
1. What will sustain a
business?
(Viability)
3. What do people
desire?
(Desirability)
2. What can we
build?
(Capability)
Objective:
A product that is:
Viable
Buildable
Desirable
User Model
a)
Context
•
Historical
•
Social
•
Economic
b)
User
•
Demographics
•
Psychographics
•
Technographics
c)
Values
d)
Goals
e)
Scenarios
User Plan
a)
Design schedule
b)
Form and
Success Factors for Technology Products
User Model
1.
Context
•
Historical
•
Social
•
Economic
2.
User
•
Demographics
•
Psychographics
•
Technographics
3.
Values
4.
Goals
5.
scenarios
User Plan
1.
Design
2.
schedule
3.
Form and
behavior
spec
Technology Model
1.
Technology components
2.
Competitors
3.
Build vs buy
buy vs open source
Technology Planl
1.
Engineering schedule
2.
Engineering spec
Business Model
1.
Funding model
2.
Income/expense projections etc.
Business Plan
1.
Marketing plan
2.
Launch plan
3.
Distribution plan
Probability of customer
adoption (once the product
has launched)
Probability of
sustaining business
(up to launch and
Long enough after
to build revenue)
Probability of
technical completion
(delivery)
Software Development Process
Initiate
Design
Code
Test
Ship
Managers
Designers
programmers
QA
Primary responsibility:
Ensure financial success
Ensure customer satisfaction
Ensure performance
Ensure reliability
Provide mandate to Provide spec to Provide code to Certify product for release
Users
Provide input to Provide feedback on usability toUsers
Provide bug report to
Goal-Directed Design Model
Research
User and the
domain
Modeling
Users and
use context
Requirements
Definition of user,
business& technical needs
Framework
Definition of design
structure & flow
Refinement
Goal-Directed Design Methodology
Define intent and Constraints of project
Review what exists (e.g. documents)
Discuss values, Issues, expectations
Apply ethnographic
Research techniques Define typicalusers
Deduce what users want
Imagine a system To help users reach goals
Tell stones about
Using the system Derive components based on users Organize the components
Refine detail, describe models
Scope
Audit
interviews
Observations personas
Goals
Requirements Scenarios Elements Framework
Spec
Business plan Marketing plan Branding strategy Market research Product plan Competition Related technology Summary Insights Desired outcomes Time constraints Financial constraints General process Milestones (scope may be Loose or tight)
Project Brief Briefing Management Domain experts Customers Partners Sales channel (this step leads to a project mandate)
Tapes Transcripts Summary Insights Interview Usage patterns Potential users Their activities Their environments Their interactions Their objects(tools) Aeiou framework from Rick Robinson, sapient) Tapes Transcripts Summary Insights Chalk Talk (Early findings) Primary Secondary Supplemental negative] Served(indirectly) Partner Customer Organizational Notes Life End Experience Business Technical Notes
Chalk talk with management
Problem definition vision definition Design imperatives Functional & data needs Environmental factors Business requirements Technical constraints (may require changes in scope)
Problem statement Vision statement Cost of persons Formal decimations Presentation
Context Key-path Validation key path variants necessary use edge case use
Notes Storyboards
Information objects Functional objects Functional actions Contexts of use
Lists Sketches Diagrams High-level data models Object relationship Conceptual groupings Principles Patterns Logic/narrative flow Navigation structure Sketches Flow diagrams
Chalk talk with Programmers Appearance Language Flow/behavior Product character Product story Format document Demonstration Prototype Presentation
Research and Modeling
Opportunities, Constraints, and
Context
Requirements, Framework
and Refinement
Form, Content, and Behavior
Initiate
Design
Code
Test
Ship
Managers
Designers
programmers
QA
Primary responsibility:
Ensure financial success
Ensure customer satisfaction
Ensure performance
Ensure reliability
Provide mandate to Provide spec to Provide code to Certify product for release
Users
Provide input to Provide feedback on usability toUsers
Provide bug report to
Research and Modeling - 1
Define intent and constraints of project
Scope
Desired outcomes
Time constraints
Financial constraints
General process
Milestones
(scope may be loose or tight)
Activity:
Result:
Artifact:
Project Brief
Goal-Directed Design Methodology
Define intent and Constraints of project
Review what exists (e.g. documents)
Discuss values, Issues, expectations
Apply ethnographic
Research techniques Define typicalusers
Deduce what users want
Imagine a system To help users reach goals
Tell stones about
Using the system Derive components based on users Organize the components
Refine detail, describe models
Scope
Audit
interviews
Observations personas
Goals
Requirements Scenarios Elements Framework
Spec
Business plan Marketing plan Branding strategy Market research Product plan Competition Related technology Summary Insights Desired outcomes Time constraints Financial constraints General process Milestones (scope may be Loose or tight)
Project Brief Briefing Management Domain experts Customers Partners Sales channel (this step leads to a project mandate)
Tapes Transcripts Summary Insights Interview Usage patterns Potential users Their activities Their environments Their interactions Their objects(tools) Aeiou framework from Rick Robinson, sapient) Tapes Transcripts Summary Insights Chalk Talk (Early findings) Primary Secondary Supplemental negative] Served(indirectly) Partner Customer Organizational Notes Life End Experience Business Technical Notes
Chalk talk with management
Problem definition vision definition Design imperatives Functional & data needs Environmental factors Business requirements Technical constraints (may require changes in scope)
Problem statement Vision statement Cost of persons Formal decimations Presentation
Context Key-path Validation key path variants necessary use edge case use
Notes Storyboards
Information objects Functional objects Functional actions Contexts of use
Lists Sketches Diagrams High-level data models Object relationship Conceptual groupings Principles Patterns Logic/narrative flow Navigation structure Sketches Flow diagrams
Chalk talk with Programmers Appearance Language Flow/behavior Product character Product story Format document Demonstration Prototype Presentation
Research and Modeling
Opportunities, Constraints, and
Context
Requirements, Framework
and Refinement
Form, Content, and Behavior
Initiate
Design
Code
Test
Ship
Managers
Designers
programmers
QA
Primary responsibility:
Ensure financial success
Ensure customer satisfaction
Ensure performance
Ensure reliability
Provide mandate to Provide spec to Provide code to Certify product for release
Users
Provide input to Provide feedback on usability toUsers
Provide bug report to
Research and Modeling - 2
Review what exists (e.g. documents)
Audit
Business plan
Marketing plan
Branding strategy
Market research
Product plan
Competition
Related technology
Activity:
Result:
Artifact:
Summary
Insights
Goal-Directed Design Methodology
Define intent and Constraints of project
Review what exists (e.g. documents)
Discuss values, Issues, expectations
Apply ethnographic
Research techniques Define typicalusers
Deduce what users want
Imagine a system To help users reach goals
Tell stones about
Using the system Derive components based on users Organize the components
Refine detail, describe models
Scope
Audit
interviews
Observations personas
Goals
Requirements Scenarios Elements Framework
Spec
Business plan Marketing plan Branding strategy Market research Product plan Competition Related technology Summary Insights Desired outcomes Time constraints Financial constraints General process Milestones (scope may be Loose or tight)
Project Brief Briefing Management Domain experts Customers Partners Sales channel (this step leads to a project mandate)
Tapes Transcripts Summary Insights Interview Usage patterns Potential users Their activities Their environments Their interactions Their objects(tools) Aeiou framework from Rick Robinson, sapient) Tapes Transcripts Summary Insights Chalk Talk (Early findings) Primary Secondary Supplemental negative] Served(indirectly) Partner Customer Organizational Notes Life End Experience Business Technical Notes
Chalk talk with management
Problem definition vision definition Design imperatives Functional & data needs Environmental factors Business requirements Technical constraints (may require changes in scope)
Problem statement Vision statement Cost of persons Formal decimations Presentation
Context Key-path Validation key path variants necessary use edge case use
Notes Storyboards
Information objects Functional objects Functional actions Contexts of use
Lists Sketches Diagrams High-level data models Object relationship Conceptual groupings Principles Patterns Logic/narrative flow Navigation structure Sketches Flow diagrams
Chalk talk with Programmers Appearance Language Flow/behavior Product character Product story Format document Demonstration Prototype Presentation
Research and Modeling
Opportunities, Constraints, and
Context
Requirements, Framework
and Refinement
Form, Content, and Behavior
Initiate
Design
Code
Test
Ship
Managers
Designers
programmers
QA
Primary responsibility:
Ensure financial success
Ensure customer satisfaction
Ensure performance
Ensure reliability
Provide mandate to Provide spec to Provide code to Certify product for release
Users
Provide input to Provide feedback on usability toUsers
Provide bug report to
Research and Modeling - 3
Discuss values, issues, expectations
Interviews
Management
Domain experts
Customers
Partners
Sales channel
(this step leads to
a project mandate)
Activity:
Result:
Goal-Directed Design Methodology
Define intent and Constraints of project
Review what exists (e.g. documents)
Discuss values, Issues, expectations
Apply ethnographic
Research techniques Define typicalusers
Deduce what users want
Imagine a system To help users reach goals
Tell stones about
Using the system Derive components based on users Organize the components
Refine detail, describe models
Scope
Audit
interviews
Observations personas
Goals
Requirements Scenarios Elements Framework
Spec
Business plan Marketing plan Branding strategy Market research Product plan Competition Related technology Summary Insights Desired outcomes Time constraints Financial constraints General process Milestones (scope may be Loose or tight)
Project Brief Briefing Management Domain experts Customers Partners Sales channel (this step leads to a project mandate)
Tapes Transcripts Summary Insights Interview Usage patterns Potential users Their activities Their environments Their interactions Their objects(tools) Aeiou framework from Rick Robinson, sapient) Tapes Transcripts Summary Insights Chalk Talk (Early findings) Primary Secondary Supplemental negative] Served(indirectly) Partner Customer Organizational Notes Life End Experience Business Technical Notes
Chalk talk with management
Problem definition vision definition Design imperatives Functional & data needs Environmental factors Business requirements Technical constraints (may require changes in scope)
Problem statement Vision statement Cost of persons Formal decimations Presentation
Context Key-path Validation key path variants necessary use edge case use
Notes Storyboards
Information objects Functional objects Functional actions Contexts of use
Lists Sketches Diagrams High-level data models Object relationship Conceptual groupings Principles Patterns Logic/narrative flow Navigation structure Sketches Flow diagrams
Chalk talk with Programmers Appearance Language Flow/behavior Product character Product story Format document Demonstration Prototype Presentation
Research and Modeling
Opportunities, Constraints, and
Context
Requirements, Framework
and Refinement
Form, Content, and Behavior
Initiate
Design
Code
Test
Ship
Managers
Designers
programmers
QA
Primary responsibility:
Ensure financial success
Ensure customer satisfaction
Ensure performance
Ensure reliability
Provide mandate to Provide spec to Provide code to Certify product for release
Users
Provide input to Provide feedback on usability toUsers
Provide bug report to
Research and Modeling - 4
Apply ethnographic research techniques
Observations
Activity:
Result:
Artifact:
Tapes
Transcripts
Summary
Insights
Goal-Directed Design Methodology
Define intent and Constraints of project
Review what exists (e.g. documents)
Discuss values, Issues, expectations
Apply ethnographic
Research techniques Define typicalusers
Deduce what users want
Imagine a system To help users reach goals
Tell stones about
Using the system Derive components based on users Organize the components
Refine detail, describe models
Scope
Audit
interviews
Observations personas
Goals
Requirements Scenarios Elements Framework
Spec
Business plan Marketing plan Branding strategy Market research Product plan Competition Related technology Summary Insights Desired outcomes Time constraints Financial constraints General process Milestones (scope may be Loose or tight)
Project Brief Briefing Management Domain experts Customers Partners Sales channel (this step leads to a project mandate)
Tapes Transcripts Summary Insights Interview Usage patterns Potential users Their activities Their environments Their interactions Their objects(tools) Aeiou framework from Rick Robinson, sapient) Tapes Transcripts Summary Insights Chalk Talk (Early findings) Primary Secondary Supplemental negative] Served(indirectly) Partner Customer Organizational Notes Life End Experience Business Technical Notes
Chalk talk with management
Problem definition vision definition Design imperatives Functional & data needs Environmental factors Business requirements Technical constraints (may require changes in scope)
Problem statement Vision statement Cost of persons Formal decimations Presentation
Context Key-path Validation key path variants necessary use edge case use
Notes Storyboards
Information objects Functional objects Functional actions Contexts of use
Lists Sketches Diagrams High-level data models Object relationship Conceptual groupings Principles Patterns Logic/narrative flow Navigation structure Sketches Flow diagrams
Chalk talk with Programmers Appearance Language Flow/behavior Product character Product story Format document Demonstration Prototype Presentation
Research and Modeling
Opportunities, Constraints, and
Context
Requirements, Framework
and Refinement
Form, Content, and Behavior
Initiate
Design
Code
Test
Ship
Managers
Designers
programmers
QA
Primary responsibility:
Ensure financial success
Ensure customer satisfaction
Ensure performance
Ensure reliability
Provide mandate to Provide spec to Provide code to Certify product for release
Users
Provide input to Provide feedback on usability toUsers
Provide bug report to
