i need to Evaluate, analyse and redesign an existing system. For this
I need to evaluate and analyse the current mobile system and redesign
a future medicine reminder for disabled and elderly people. see the
following guide for more detail.
--------------------------------------------------------------------------------

Evaluation, Analysis and (Re)design of an Existing System

Objectives
The design objectives are to:
a) evaluate an existing system to obtain some user-centred inputs to
design in the form of : (I) analysis of tasks, user knowledge, user
requirements/criteria ; and (II) design rules/guidelines, or desirable
and undesirable features of interaction;
b) design a new version of the system.

The learning objectives are to:
a) develop your ability to assess an interaction with respect to
general purpose usability criteria;
b) develop an explicit, structured, knowledge-based approach to
interface design.

Procedure
Plan Coursework
A. Think of a future system you would like to design, then work back
to identify an existing system from which you could learn something
relevant, if you evaluated it.  For example, if you want to design a
Shopping Reminder Service, and think you need to learn about
interacting with maps to do this, you might evaluate a map site, such
as www.streetmap.co.uk.  Or, if you want to design a position-aware
text messaging service for a Nokia 3670, and think you need to learn
about the styleguide for Nokias, then you might evaluate the Nokia
address book, and configuration menu.
B. Think of an existing system that you know something about and can
access, and then work forward to identify how it could be redesigned.
To be more usable.  For example, if you think the UI to Pegasus Mail
sucks, you might evaluate it, and then apply what you have learned to
design a WAP email service.  Or, perhaps there is a system at your
place of work that needs improving.
Either way, it will help a single analysis of a user task situation
will support both your analysis and design work.  The GUIDE method
provides a good structure to follow.  If you have planned your
coursework correctly, you should be able to complete the table below.

Existing System	User, Task, Situation	Future System	User, Task,
Situation
e.g. Pegasus Mail	Students, organising an evening out, university 	WAP
email on Nokia3670	Students, organising evening out, during commute
home.


A. Evaluation
1. Select a task.  Of all the tasks that users could potentially
perform at this site, which will be most relevant to the service you
are about to design? It is up to you to decide how to focus your
contribution.  But you should give reasons for selecting the task to
design for that you have. N.B. there are marks for this – see Cover
Sheet.
2. Select a user.  How does the user participating in your evaluation
relate to the target user population - typical, representative, an
example?  In what ways is this user similar or different to the target
user population?
3. Prepare.  Explore the system, perform the task yourself and list
some questions for the user.
4. Make Observations.  Ask your user to perform the task, noting
breakdowns and critical incidents.
5. Write a Report. 
Document the procedure you followed (questions asked, materials used).
Describe the service application you evaluated, the user, the task
that was performed.  Report your observations i.e. user breakdowns and
critical incidents.
Make an assessment.  
With the position-aware equivalent of the service/application for
mobile devices that you are about to design in mind:
(a) give some insights into the task, user needs, user criteria;
(b) suggest some desirable and/or undesirable features of interaction.

B. Analysis
1. Describe the users more fully.  This section should specify
critical parameters of user performance.
2. Describe the tasks more fully.  This section should include task
scenarios and a Hierarchical Task Decomposition.
3. Describe the context more fully.

C. Redesign 
1. Focus the redesign.  Select particular types of users, task and
context to design for.  A rule of thumb is the more specific, the
better.  You may not be able to consider all aspects of the service in
depth.  Give reasons for focussing the work the way you have.  N.B.
there are marks for this – see Cover Sheet.
2. Find Some Knowledge to Apply.  Examples include styleguides, design
guidelines/rules, “Qualities of Interaction” (see lecture notes). 
N.B. there are marks for this – see Cover Sheet.
3. Design User Interaction.  The GUIDE method suggests how to do this.
 The minimum is to walk me through interaction with your UI from the
user’s point of view, using annotated screen dumps.
4. Write a Report.  There is no compulsory structure. A default
structure is provided by GUIDE.  At some point, walk me through a task
scenario using your design.  Note that  refer to your diary,
literature review and evaluation, and include them as appendices may
be useful.
 Include diagrams, figures or sketches in the report to
support and summarise your work.  GUIDE notations may be a concise way
of expressing many words.  You may use any prototyping tool to produce
your design – Word, Visual Basic, Java Studio, - or no tool - neat
hand sketches will suffice.
 The redesign follows the previous evaluation, but you may
also want to integrate the outcome of the evaluation explicitly e.g.
with explicit links and references.

5. State Combined Word Length- at the top of the first page (2500
words max.  approximately 1,000 words of evaluation, 500 analysis and
1,000 words of redesign ).

 COVER SHEET – Evaluation and Redesign

Overall					     easy					  difficult
		Level of Difficulty of Problem    
|___________________________________|


Orientation – user centred?


Scoping – good reasons for selection of problem?  focus upon critical
concerns?



Clarity and Detail –eg of what you did/observed, how a user interacts
with your design



		Rationale – reasons for decisions/choices made


Evaluation: 


Balance - appreciation of strengths and weaknesses 


		Empirical Support (Links to Observations)
		

Analysis
Richness (as source of implications and criteria)


Empirical Basis 


Design
		Pull Through of Lit Review, Evaluation, Analysis – did previous
activities benefit design?



Knowledge Applied – relevant, productive?


Presentation
		Spelling/Grammar


		Wording


		Sentence Construction


		Structure


		Communication with Audience (including Illustrations)


		Bound in Folder with Cover Sheet and Word Length