University of Central Punjab - Faculty of Information Technology

Human Computer Interaction

Spring 2024
PD Phase 1 (Group Work)
PROJECT TITLE
Due Date: 30April 2024

Submission on Horizon (Student Portal)

__________________________________________________________
CLO 4: Through collaborative group work, students are expected to engage in meaningful
discussions (argue and discuss all the points – in groups) which lead to enhanced level of
appreciation/understanding of the topic by completing all the steps of the project phase 1.

1. Guidelines
1. Title Page
2. Group members
3. Be careful about font structure and alignment of text.
2. Grading
1. There is a strict policy against plagiarism and cheating. The penalty can be an F grade.
2. Your report will be judged on the following rubrics.

 Completeness: Don't omit a dimension of usability, and don't overlook an

obvious usability issue that even the reader notices.
 Depth: "Efficiency is good, because it feels fast to use" is not deep analysis. "I've
never made any errors with it" is not deep analysis.
 Clarity: The reader should not struggle to understand what you're talking about.
 Human Computer Interaction

 Usability of presentation: Your report is itself a user interface whose purpose is

to convey ideas to a reader. If your report is not readable then it will be harder
for the reader to use, and it will not demonstrate an ability to apply the ideas of
this class.
3. In class presentations- display of your work followed by Q and A session.
_____________________________________________________________________________________

The amount of good luck coming your way depends on your willingness to act. Good Luck

2
 Human Computer Interaction

Project Title
Abstract
An abstract is an outline/brief summary of your whole project. It should have an intro, body and
conclusion. It is a well-developed paragraph, should be exact in wording, and must be
understandable to a wide audience. Abstracts should be no more than 250 words.

1. Introduction
Brief introduction of the system or project that you are working on.

1.1 Idea Generation

 You have to provide justification on how you choose an idea for your application. For
that you have to provide the following
 Write down the details of all the ideas/ problems you had on individual basis. (At least
one idea/member). Also provide rough storyboard sketches for each idea/problem.
 Briefly explain your brainstorming activity, illustrating how you conducted each step.
 Selected Idea: Mention the idea/problem that has been selected during the brainstorming
session/ activity conducted in class. Also provide neatly drawn sketches of the selected
idea/problem. Provide reasons/attributes for acceptance of this idea and rejection of
others.

1.2 Problem Statement

A problem statement is a concise description of an issue to be addressed or a condition to be

improved upon (Write problem statement for your final idea selected during brainstorming
activity. It identifies the gap between the current (problem) state and desired (goal) state of a
process or product. Focusing on the facts, the problem statement should be designed to address
the Five W’s (Who, What, When, Why, Where).

1.3 Objectives

List all the objectives to be achieved after the completion of this project.

1.4 Motivation

What is motivation or inspiration behind your application? Which factors motivated you to
develop an application like this?

1
 Human Computer Interaction

2. Target market Identification

A description of important characteristics of the users of the system.

2.1 Target Market

Identification of a particular group of consumers at which a product or service is aimed.

2.2 User Classes and Characteristics

Identify the various user classes extracted from your target market that you anticipate will use
this product. User classes may be differentiated based on frequency of use, subset of product
functions used, technical expertise, security or privilege levels, educational level, or experience.

2.3 Primary and Secondary User Classes

Differentiate your user classes as primary and secondary users. Write down the tasks of primary
and secondary users. A justification on how and why you have made separate class is also
required.

3. Exploratory Study
3.1 Analysis

An analysis of the similar existing system (automated or manual) including the strengths and
weaknesses of the system.

3.2 Requirements

Identify the functional, non-functional and quality requirements of your system.

3.2.1 Functional Requirements

The major services provided by the product.

3.2.2 Nonfunctional Requirements

Describe the non-functional requirements if required.

3.3 Usability Goals

An initial list of usability criteria, or principles that should be used in the eventual evaluation of
your system, including a high-level description of how could you conduct the experiment on

2
 Human Computer Interaction

your system for evaluation of those goals and how could you measure the successful adherence
to these goals and

4. Need Finding (Interviews)

Identify 3 users whom you want to interview (It will be good if you choose at least one user
from each class). Introduce your users whom you want to interview and yourself.

4.1 Goals of Interview

Explain the goals of the interview

4.2 Process of interview

Write down the whole interview process that you have used for this activity e.g.:

1. Introduce yourself

2. Reassure about the ethical issues - privacy, rights to information

3. Ask to record.

4. Make first questions easy & non-threatening.

5. Phrase the questions in an open or neutral way. Also, encourage the user to reply with
full sentences, rather than a simple "yes" or "no". For example, ask, "What do you think
of this feature?" and not "Did you like this new feature?"

6. Do not ask leading questions. For example, "how did that poorly designed dialog affect
you?"

7. Include a few easy questions to defuse tension at the end

8. Thank interviewee

4.3 User Photos and Captions

Take a picture of your potential user and mention his/her goals in the caption.

4.4 User Needs

Identify the user needs by extracting them from the interviews.

3
 Human Computer Interaction

4.5 Class profiles

Make class profiles of your user classes (primary or secondary).

4.6 Personas

Make personas for your user classes (It can be one or more personae for each user class
depending on your application and satisfactory level).

4.7 Scenarios

Write scenarios for the personae you have created covering all the main goals of your desired
system.