Está en la página 1de 11

FINAL REPORT OF PIE MENU

COMSATS INSTITUTE OF INFORMATION TECHNOLOGY,


ISLAMABAD

FINAL REPORT OF PROJECT


PIE MENU
Human Computer Interaction

NAME: NAWAL RASHID, KHADIJA IFZAAL


REG NO: SP13-BCS-219, FA12-BCS-063
1

FINAL REPORT OF PIE MENU

PROJECT TITLE:
Pie Menu

IDEA:
Its a concept to improve user interaction.

TOOL:

Visual studio
Visual C#

ABOUT PROJECT:
Pie menu is simply a circular menu made of pie slices. It works well with the mouse clicks. We
have shown 8 items in a menu which will appear on windows just by right click of mouse.
The goal of pie menu is to provide smooth, reliable gestural style of interaction between the user
and a system. It is faster and more reliable to select the menu from pie menu by just on one click.
We also use different colors in the menu which provide friendly interface for the user.

NEED FINDING TECNIQUE FOR PIE MENU:


We use need finding technique: Interviewing
The purpose of interviewing is to discover what is on/in someone's mind, as our application is
PIEMENU by choosing this technique we can have survey of questions and by performing
interview technique we can have better understanding of our application. As The type of
questions that the one asks in an interview is instrumental in determining the value of data
collected in interviews. Consequently, the quality of information gained in an interview is based
very much on the skills of the interviewer. So the type of question will ask during interview will
give better results.

FINAL REPORT OF PIE MENU

INTERVIEW 1:Q1: What kind of requirements do you want your interface to work in?
Q2: Whats the need of facilitating the user with such interactive interface?
Q3: Is the interface you are working on is very time consuming?
Q4: Would you need any mathematical tools regarding this?

INTERVIEW 2:Q1: What is the use of pie menu in desktop application?


Q2:-What happens to your application when menu size is small and when the menu size is large?
Q3:-How the menu size of your application will increase?
Q4: How the performance on Hidden menu will affect your application?

JUSTIFICATION ABOUT SELECTING TECHNIQUE:


The research that we are working on is global and the participants were not only restricted to one
area and the observation done are based on culture and its not important for our system and
since its not only restricted to one area so its not compulsory to depend on observation because
our system can work without observation technique.
We are making User Interactive system and its not required by the system to deliver daily
reports and also time is not specified that is why we are not chosen diary studies for our project.
Interview technique could give us better results.

FINAL REPORT OF PIE MENU

PERSONA SCENARIOS AND STORY BOARD:

FINAL REPORT OF PIE MENU

FINAL REPORT OF PIE MENU

PROTOTYPE:
In prototype we are going to represent our design using graphs and sketches develop at the
beginning of design process.

INITIAL IDEAS AND SKETCHES:


Before starting low-fidelity prototypes, we decided to do some initial sketches based on our
research.

FINAL REPORT OF PIE MENU

EVALUATIONS:
We start evaluating the early sketches and then as the project progresses we keep improving our
prototypes and evaluate those. We use heuristic approach for low fidelity paper prototype
evaluation

PROTOTYPE (1) EVALUATION:


Visibility of system status:
Feedbacks are provided to the user in the form of graphs and text.
User control and freedom:
User will have full control over menu to click through mouse and move menu through pointer of
mouse anywhere on the screen.
Consistency:
The layout remains the same on each activity.
Flexibility:
Menu should be easy to use when list appear it should be more flexible.
We pointed out the following changes:
When user click and menu appear it is in listed form which is very common and user
wants something new and exciting that make menu attractive and user friendly so we
decided to change the shape of pie menu

FINAL REPORT OF PIE MENU

PROTOTYPE (2) EVALUATION:


We again make low fidelity prototype to overcome the problem. By using heuristic approach we
have asked these four questions for each action of the Task.

What is the user goal and why? (Is effect of current action same as user goal?)

Is the action obviously available? (Is the action visible?)

Does the action or label match the goal? Will the user recognize the action as the correct
one?

Is there good feedback?

HIGH FEDLITY PROTOTYPE:


After carrying out research about computer menus and there importance according to field of
HCI, we are able to develop a prototype based on the feedback gathered from users. Before
designing this prototype it is necessary to get and analyze the detailed feedback from test users.
Our pie menu prototype reflects the feedback received from users and also our purposed
requirements.
Below are some images of our prototypes.
8

FINAL REPORT OF PIE MENU

FINAL REPORT OF PIE MENU

Figure 1 Pie Menu

Figure 2 Pie Menu with selection

Above created pie menu prototype designs are designed and created in Visual Studio using C#.
At this stage is very important to gather as much feedback as possible before moving onto the
final prototype stage.
To help me gather feedback, we developed an Evaluation Plan to outline the goal of the Pie
Menu and what I wanted to find out.

10

FINAL REPORT OF PIE MENU

Feedback Received:
Add more details to the Pie Menu to increase the user interactivity with selection of options
rather then moving down in drop down menus.
Pie menu given in Figure 1 and Figure 2 is built for novice users.
Target and Goals of pie menu is iteratively changing with users feedback. Instead of fixing
the requirement and design, we use heuristic approach by taking suggestions and feedback to
change our GUI.
This detailed feedback has helped us to gain a better understanding of how the computer users
want to view menu. Now, we can improve our prototype in the light of feedback.

11

También podría gustarte