Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 18 Goal-Directed Design Methodology Virtual University Human-Computer Interaction

Virtual University - Human Computer Interaction 2 © Imran Hussain | UMT In the Last Lecture Software Lifecycle Models HCI Lifecycle Models Goal-Directed Design Model

Virtual University - Human Computer Interaction 3 © Imran Hussain | UMT In Today’s Lecture Goal-Directed Design Methodology

Virtual University - Human Computer Interaction 4 © Imran Hussain | UMT Success Factors for Technology Products Product Desirability Capability Viability

Virtual University - Human Computer Interaction 5 © Imran Hussain | UMT 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 Business Plan 1.Marketing plan 2.Launch plan 3.Distribution plan Business Model a)Funding model b)Income/expense projections, etc. 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 behavior spec

Virtual University - Human Computer Interaction 6 © Imran Hussain | UMT 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) Overall probability Of product success

Virtual University - Human Computer Interaction 7 © Imran Hussain | UMT Software Development Process InitiateDesignCodeTest Ship Managers Designers programmers QA Primary responsibility: Ensure financial successEnsure customer satisfaction Ensure reliability Ensure performance Provide mandate to Provide spec toProvide code toCertify product for release Users Provide input to Provide feedback on usability to Provide bug report to Software Development Process

Virtual University - Human Computer Interaction 8 © Imran Hussain | UMT 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 Of behavior, form& content

Virtual University - Human Computer Interaction 9 © Imran Hussain | UMT What is Methodology?

Virtual University - Human Computer Interaction 10 © Imran Hussain | UMT 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 typical users 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 ScopeAuditinterviewsObservations personas GoalsRequirementsScenariosElements 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 InitiateDesignCodeTest Ship Managers Designers programmers QA Primary responsibility: Ensure financial successEnsure customer satisfaction Ensure reliability Ensure performance Provide mandate to Provide spec toProvide code toCertify product for release Users Provide input to Provide feedback on usability to Provide bug report to Software Development Process

Virtual University - Human Computer Interaction 11 © Imran Hussain | UMT 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 Meetings:Briefing

Virtual University - Human Computer Interaction 12 © Imran Hussain | UMT 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 typical users 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 ScopeAuditinterviewsObservations personas GoalsRequirementsScenariosElements 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 InitiateDesignCodeTest Ship Managers Designers programmers QA Primary responsibility: Ensure financial successEnsure customer satisfaction Ensure reliability Ensure performance Provide mandate to Provide spec toProvide code toCertify product for release Users Provide input to Provide feedback on usability to Provide bug report to Software Development Process

Virtual University - Human Computer Interaction 13 © Imran Hussain | UMT 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 Meetings:Briefing

Virtual University - Human Computer Interaction 14 © Imran Hussain | UMT 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 typical users 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 ScopeAuditinterviewsObservations personas GoalsRequirementsScenariosElements 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 InitiateDesignCodeTest Ship Managers Designers programmers QA Primary responsibility: Ensure financial successEnsure customer satisfaction Ensure reliability Ensure performance Provide mandate to Provide spec toProvide code toCertify product for release Users Provide input to Provide feedback on usability to Provide bug report to Software Development Process

Virtual University - Human Computer Interaction 15 © Imran Hussain | UMT 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: Artifact: Tapes Transcripts Summary Insights Meetings:Interviews

Virtual University - Human Computer Interaction 16 © Imran Hussain | UMT 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 typical users 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 ScopeAuditinterviewsObservations personas GoalsRequirementsScenariosElements 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 InitiateDesignCodeTest Ship Managers Designers programmers QA Primary responsibility: Ensure financial successEnsure customer satisfaction Ensure reliability Ensure performance Provide mandate to Provide spec toProvide code toCertify product for release Users Provide input to Provide feedback on usability to Provide bug report to Software Development Process

Virtual University - Human Computer Interaction 17 © Imran Hussain | UMT Research and Modeling - 4 Apply ethnographic research techniques Observations Activity: Result: Artifact: Tapes Transcripts Summary Insights Meetings:Chalk Talk (Early findings) Usage patterns Potential users Their activities Their environments Their interactions Their objects(tools) Aeiou framework from Rick Robinson, sapient)

Virtual University - Human Computer Interaction 18 © Imran Hussain | UMT 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 typical users 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 ScopeAuditinterviewsObservations personas GoalsRequirementsScenariosElements 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 InitiateDesignCodeTest Ship Managers Designers programmers QA Primary responsibility: Ensure financial successEnsure customer satisfaction Ensure reliability Ensure performance Provide mandate to Provide spec toProvide code toCertify product for release Users Provide input to Provide feedback on usability to Provide bug report to Software Development Process

Virtual University - Human Computer Interaction 19 © Imran Hussain | UMT Research and Modeling - 5 Define typical users Personas Activity: Result: Artifact: Notes Meetings:Chalk Talk (Early findings) Primary Secondary Supplemental negative] Served (indirectly) Partner Customer Organizational

Virtual University - Human Computer Interaction 20 © Imran Hussain | UMT Types of Users What does the program do? How do I print? What is the program’s scope? Where do I start? I forgot how to import What new features are in this upgrade? How do I find facility X? What is this control for? Remind me What this does? Oops ! Can I undo?What was the command for X? How do I automate this? What are the shortcuts for this Command? Can this be changed How can I customize this? What is dangerous? Is there keyboard equivalent? BeginnersPerpetual intermediatesExperts

Virtual University - Human Computer Interaction 21 © Imran Hussain | UMT Perpetual Intermediates Most users are intermediates Nobody wants to remain a beginner Programmers are experts Sales people are beginners and lobby for product training Optimize for intermediates Need tool tips, can use reference material

Virtual University - Human Computer Interaction 22 © Imran Hussain | UMT Beginners Nobody wants to remain a beginner Make them understand cause and effect Represented model should follow mental model Guided tours (overviews) instead of references

Virtual University - Human Computer Interaction 23 © Imran Hussain | UMT Experts Experts influence other buyers Internalize the working of interfaces Memorize functions due to frequency of use

Virtual University - Human Computer Interaction 24 © Imran Hussain | UMT What does the program do? How do I print? What is the program’s scope? Where do I start? I forgot how to import What new features are in this upgrade? How do I find facility X? What is this control for? Remind me What this does? Oops ! Can I undo?What was the command for X? How do I automate this? What are the shortcuts for this Command? Can this be changed How can I customize this? What is dangerous? Is there keyboard equivalent? BeginnersPerpetual intermediatesExperts

Virtual University - Human Computer Interaction 25 © Imran Hussain | UMT References Interaction Design