THE UNIVERSITY OF AZAD JAMMU AND KASHMIR

Assignment NO. 2
Submitted By : Ambreen Qayyum
Submitted To : Sir Ghulam Rabbani Butt
Roll No : 18-SE-04
Course Name: Human Computer Interaction

DEPARTMENT OF SOFTWARE ENGINEERING

1

Question NO.1
Write a detail report on all steps of Goal Directed Design Model?

Ans. Goal-Directed Design

Goal Directed Design is a user-centered methodology developed by Alan Cooper

to address situations where different users of a proposed product express a desire
for different things -- in short, most situations. Often, development teams can
take every user idea at face value and develop a system that tries to satisfy
everybody but manages to satisfy nobody. This can lead to the conclusion that
listening to users has no value and that the only way to know what users will be
happy with is to simply build it and correct it after user testing.
While we fully anticipate having to make small course corrections with future
releases over time, we want to get as close to the right product with our first
iteration. We will therefore be conducting an investigation before development or
even design begins. This investigation will help us to create models of distinct,
archetypical users called personas, which can help decide when a common need
can be met by a common view or when distinct views are necessary.

Process
Goal Directed Design describes a six-step process for talking to users, analyzing
what they say and do, and most importantly, making decisions about whether
different users can be satisfied by the same interface or will require different
interfaces. It includes the following steps.
Research
The research phase employs ethnographic field study techniques (observation an
d
contextual 
interviews) to provide qualitative data about potential and/or actual users
of the product. It also includes competitive product audits, reviews of market rese
arch
and technology white papers, as well as one-on-one interviews with stakeholders,
developers, subject matter experts (SMEs), and technology experts as suits the
2

particular domain.
One of the principles out comes of field observation and user interviews are an
emergent set of usage patterns--identifiable behaviors that help categorize modes 
of
use ofa potential or existing product. These patterns suggest goals and motivatios
(specific and general desired outcomes of using the product). In business and
technical domains, these behavior patterns tend to map to professional roles; for
consumer product, they tend to correspond to lifestyle choices. Usage
patterns and the
goals associated with them drive the creation of personas in the modeling phase.
Market search helps select and filter for valid persons that fit corporate business
models. Stakeholder interviews, literature reviews, and product audits deepen th
edesigners' understanding of the domain and elucidate business goals and technic
al constraints that design must support.
Modeling
Using the modeling phase, usage and workflow patterns discovered through analy
sis
of the field research and interviews are synthesized into domain and user models.
Domain models can include information flow and workflow diagrams. User model
and personnas
or personas, are detailed composite user archetypes that represent distinct group
ings
of behavior patterns, goals, and motivations observed and identified during the
research phase.
Personas serves as the main characters in a narrative scenario-based approach to
design that iterative generates design concepts
in the framework definition phase,
provides feedback that enforces design coherence and appropriateness in the
refinement phase, and represents a powerful communication tool that helps
developers and managers to understand design rationale and to prioritize feature
s
based on user needs. In the modeling phase, designers employ a variety of
3

methodological tools to
synthesize, differentiate, and prioritize personas, exploringdifferent types of goals 
and mapping personas across ranges of behavior to ensure
there are no gaps or duplications.
Specific design targets are chosen from the cast of personas through a process of
comparing goals and assigning a hierarchy of priority based on how broadly each
persona's goals encompass the goals of other personas. A process of designating
persona types determines the amount of influence each persona has on the event
ual
form and behavior of the design.
Possible user persona type designations include:
�  Primary: the persona's needs are sufficiently unique to require a distinct
interface form and behavior
�  Secondary: primary interface serves the needs of the persona with a minor
modification or addition
�  Supplement: the persona's needs are fully satisfied by a primary interface
�  Served: the persona is not an actual user of the product, but is indirectly
affected by it and its use
�  Negative: the persona is created as an explicit, rhetorical example of whom
not to design for.
Requirements Phase

These are the requirements for each persona: the data they need to see and the
functional needs they have for working with this data. (as opposed to detailed
requirements for developers).
 4

This phase begins with research and ends with analysis of user and domain and is
based on methodologies from Goal-Directed Design. At this point, we are hoping
to gather the perspectives of people who

 create activities (instructors, instructional designers)

 take activities (students)
 evaluate activities (instructors, TA)

whether that "activity" is homework, papers, tests, quizzes or some other activity
you identify.  In this way we can identify what they have in common and what
they don't, regardless of the specific activity. However, the actual scope of the
investigation will depend on participation; should we be so lucky as to attract an
overflow of interest, we will discuss whether we need to narrow our focus.
Framework Phase
4. Framework definition:

The framework is like sketching the layout for the house before detailed
blueprints is created; we need to know which rooms need to be near to each
other, which can be on other floors*.* It also pays to know what the future plans
are for the people who are living in the house, even if we don't build out all the
rooms right away. If we are designing a house for a young couple that has one
child but intends to have two more kids and have their in-laws move in later, our
plans may include a clear pathway and plumbing out to the side of the house
where a future extension would be built to minimize disruption during a future
remodel. 
Each primary persona will require their own interface. These will likely break
down by role (instructor, student, and possibly another). For each primary
persona's data and functional needs, we need to define

 Data elements: what are the attributes of these data objects?

 Functional elements: based on the functional needs, what areas do we
need to hold and organize elements and what tools will need to act on data
objects?

A framework shows how those functional elements relate to each other. They
should be organized based on a persona's context scenarios--which elements
need to be accessed sequentially or on the same screen.
5

 Refinement phase

 Proceeds similarly to the Framework Definition phase, but with greater focus on
task coherence, using key path (walkthrough) and validation scenarios focused
on story-boarding paths through the interface in high detail. The culmination of
the Refinement phase is the detailed documentation of the design, a form and
behavior specification, delivered in either paper or interactive media as context
dictates. 
6