HCI - Chapter 5 - Interaction Design and HCI in SW Process

Chapter 5: Interaction Design and
HCI in the Software Process
 Interaction Design
What is Design?
Understanding Users
Process of Design
 HCI in the Software Process
Software Life Cycle

Usability Engineering
What is design?
 Is achieving goals within constraints

 Goals: purpose, intended user
 Constraints: materials, standards, cost, time, …
required
 One of the most important things about design is trade-offs
 trade-offs: Choosing which goals or constraints can be
relaxed(less strict) so that others can be met
 It is a creative activity or a plan for development
 HCI study also about doing and making things
What is design?...
 Golden rule of design

 In HCI, obvious materials are human &
computer.
 Understand computers
 limitations, capacities, tools, platforms

 Understand people
 psychological, social aspects, human error
 and their interaction …
Understanding Users
 Who are the users?
 Those who interact directly with the product , manage
users, receive output from the product, make the
purchasing decision, use competitor’s products
 Three categories of user:
 primary: frequent hands-on
 secondary: occasional or via someone else;
 tertiary: affected by its introduction, or will

influence its purchase.
Wider term: stakeholders
The process of design
 four main iterative phases

scenarios
what is task analysis
wanted guidelines
principles
interviews analysis precise
ethnography specification
design
what is there
vs. dialogue implement
notations and deploy
what is wanted
evaluation prototype
heuristics architectures
documentation
help
Steps …
 1. Requirements
 what is wanted …
 Obtained by interviewing people, videotaping, observing directly.
 2. Analysis
 ordering and understanding the result of observation and interview
 3. Design
 is a central stage you move from what you want, to how to do it
 4. Iteration and prototyping
 getting it right … and finding what is really needed!
 5. Implementation and deployment
 making it and getting it out there
User-Centered Design (UCD)
 Best practices in design process

 Focus on
 understanding users,
 their goals,
 their strengths and limitations,
 their work processes
 all user attributes that impact how users will interact
with a software development.
 The goal of UCD is to achieve users’ success and
satisfaction by incorporating the users’ perspective into
design.
HCI in Software Engineering…
 HCI is discipline concerned with
 thedesign, implementation and evaluation of interactive
computing systems for human use and with the study of major
phenomena surrounding them
 Software Engineering
 is the “application of a systematic, disciplined, quantifiable approach
to the development, operation, and maintenance of
software
 Produces quality software products tackling time, cost and other
constraints
 Usability engineering /HCI: defines usability through the
attributes of users’ interactions with software use: efficiency,
effectiveness, and user satisfaction.
 International Organization for Standardization (ISO) sets standards
HCI in Software Engineering…
 Integrating usability engineering into

software Engineering
 They have the common goal of delivering quality
Software development, on time and on budget, to
satisfied users
 Both occur in parallel because their activities and
outputs are compatible
 UE provides usability principles and consider
knowledge of users, to aid in the development of
usable Software development
Software lifecycle
 Software engineering
 Addresses the management and technical issues in SW systems development.
 Deals with Software life cycle which describes the activities that take place from
the initial concept formation until eventual phasing out and replacement of
software systems.
 Various types of software life cycle models are there which
could be categorized as
 Sequential e.g. Water fall
 Iterative e.g. Spiral,
 Incremental e.g. Evolutionary Prototyping
 In most models designing for usability occurs at all stages of
the life cycle, not as a single isolated activity
Software Lifecycle
Requirements
specification
Architectural
design
Detailed
design
Coding and
unit testing
Integration
and testing
The waterfall model-sequential Operation and

maintenance
The software lifecycle…
 Requirements specification
 Eliciting information from the customer about what SW
functionality
 Designer and customer capture what the system is expected to
provide
 Architectural design
 High-level description of how the system will provide the services
required
 how they are interrelated needs to satisfy both functional and non-
functional requirements
 Detailed design
 Refinement of architectural components and interrelations to
identify modules to be implemented separately the refinement
The software lifecycle…
 Coding – converting design to executable solution
 Integration and Testing
 Integration- each component will be combined to whole
 Verification
 Evaluates the intermediary products to check whether it
meets the specific requirements of the particular phase
 Validation
 Evaluates the final product to check whether it meets the
business needs. Designing the right product
 Maintenance
 Changing a system after it is delivered
Life cycle for interactive systems
Requirements Iteration in the waterfall model
specification
Architectural
design
Detailed
design
Coding and
unit testing
Integration
and testing
lots of feedback!
Operation and
maintenance
Usability engineering
 Usability  User experience goals of usability

May refer Satisfying
Effective to use Fun and Enjoyable
Efficient to use Entertaining
Safe to use Helpful
Have good utility Motivating
Easy to learn Rewarding
Easy to remember support creativity
ISO usability standard 9241
 Main goal of usability engineering
 Effectiveness
 can you achieve what you want to?
 Efficiency
 can you do it without wasting effort?
 Satisfaction
 do you enjoy the process?

HCI - Chapter 5 - Interaction Design and HCI in SW Process

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

HCI - Chapter 5 - Interaction Design and HCI in SW Process

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HCI - Chapter 5 - Interaction Design and HCI in SW Process

Uploaded by

Copyright:

Available Formats

Chapter 5: Interaction Design and

HCI in the Software Process

 HCI in the Software Process

Software Life Cycle

 Is achieving goals within constraints

 Golden rule of design

 limitations, capacities, tools, platforms

 primary: frequent hands-on

 secondary: occasional or via someone else;

 tertiary: affected by its introduction, or will

 four main iterative phases

 Best practices in design process

 Integrating usability engineering into

The waterfall model-sequential Operation and

 Usability  User experience goals of usability

 Main goal of usability engineering

You might also like