Reference no: EM132339935 , Length: word count : 2500
Assessment Title- Interactive Feedback System
Purpose of the assessment
This assignment is designed to assess students’ knowledge and skills related to the following learning outcomes:
1. Evaluate software user interfaces using heuristic evaluation and user observation techniques
2. Conduct simple formal experiments to evaluate usability hypotheses.
3. Apply user centred design and usability engineering principles as they design a wide variety of software user interfaces
2500 words
Assignment Description - Interactive Feedback System
Many organisations nowadays are focusing on increasing their customer satisfaction and on achieving that; they are investing in developing their technology to collect the customers' feedback to be able to gain new knowledge out of it, to help them in building their future strategies.
Feedback interactive systems having many benefits; for example, it can increase organisation performance and enhance continuous learning.
Select three different organisations and design an interactive feedback system for each one of them. Make sure you are following the below steps.
1- Gather the requirement needed to design your feedback systems and analyse it
2- Conduct a task analysis
3- Design the prototype using the Balsamiq Cloud Mockups ( https://balsamiq.cloud )
4- Conduct a heuristic evaluation for your prototype using the IOS Apple Guidelines
5- Prepare an evaluation report
In Step 1,
You should develop the following items in step 1, and you should communicate them through your report:
- An overview of what the system will do and why it's needed.
- A description of the essential characteristics of the users of the system.
- A task analysis consisting of
• A description of the essential characteristics of the tasks performed by users.
• A description of the essential characteristics of the task environment.
• A simple structured task analysis of the problem in one of the forms described in the textbook.
- An interpretive evaluation (eg., heuristic evaluation, walkthrough, etc.) of the existing system/interface, if one exists.
- A brief description and justification of how the above information was gathered.
- Most important: A discussion of the implications of what you learned above.
The last item in the list above is critical. Don't just describe the target users, tasks, environment, etc. You must also tell us how these attributes should/will influence your design. Are there any implications to be made from the user profiles and other data you learned? We will be cautious to look for this information in your report.
In Step 2,
You should Perform User and Task Analysis for this requirement and present your findings for each task in tabular format
A. User Analysis - Perform user analysis for this system – Profile the users: determine users’ skill levels users’ skills with interfaces, any special requirements, domain-specific abilities and knowledge and frequency of use. You should create a table that identifies different categories of user, e.g. patient, receptionist, dental hygienist, dentist, auditor. Would need to identify the difference in skill level based on age and frequency of use and knowledge of technology, e.g. adults, senior citizens, librarian. Account for people with disabilities, e.g. hearing, eyesight
B. Task Analysis - Identify the tasks that the interactive feedback system will be required to carry out and map them to the users you have identified.
Example
|
TASK
|
Patient
|
Receptionist
|
Dentist ...etc
|
|
Book appointment
|
x
|
x
|
|
|
Search appointment
|
x
|
x
|
x
|
|
Insert/modify/delete clinic
|
|
x
|
|
|
register patient........ etc
|
x
|
x
|
|
Explain how this information will prove useful in designing the interface, giving examples to support your answer. Usability depends on matching the individual ability to tasks to be performed. Need to correlate interface design to ability/age/task etc. in establishing appropriate interface input methods, design, format, alerts, colour, input devices etc.
In Step 3,
In this part of the project, you will develop mock-ups, storyboards, and sketches of your interface designs. That is, you should provide pencil-and-paper or electronic images of the interface at various stages; you do not need to build a working prototype. Your design sketches should be sufficiently detailed for a potential user to provide useful feedback about the design, however.
Along with your design mock-ups, you should provide a brief narrative walk-through of how the system will work. Perhaps most importantly, you should also include your justifications for why design decisions were made, and what you consider to be the relative strengths and weaknesses of your different designs. The design process you follow here is essential.
Your project report should include all the explanatory material mentioned above as well as all the design sketches, drafts, storyboards, etc., that you generated. Make sure that your report adequately reflects the design process that your group undertook. The key in this part of the project is to come up with many different design ideas, not just a small set of wiggles from some basic design. You should plan on turning in at least three different designs.
In Step 4,
You must provide a set of initial usability specifications for your system and a plan for an evaluation of it. To develop usability specifications, consider the objectives of your design. For example, if you are working on a calendar manager, you might specify time limits in which you expect a user to be able to schedule or modify an appointment, or a maximum number of errors that you expect to occur. You should list a set of criteria by which your interface can be evaluated.
Further, this part of the project should include an initial evaluation plan for the system. What kinds of benchmark tasks would you have users perform to help evaluate the interface? What kind of subjective questionnaire would you deploy to have a user critique the interface?
The key here is not to do some exhaustive description of a usability evaluation plan, but to motivate why the plan you propose is appropriate for this interface.
Note that developing an initial evaluation plan is also an excellent way to figure out how much of the interface you need to develop. You should be able to build and connect to enough of the application functionality to be able to conduct an initial usability evaluation with the benchmark tasks as you are proposing here. Your write-up for this part should include a description of your system prototype. You can include screen dumps to help explain it and text to describe how a user would interact with it.
Discuss the implementation challenges you faced. Were there aspects that you wanted to build but were unable to do so? The key component to include in your project report is a justification of why you settled on the design that you chose. What's unique about this design concerning your problem?
The report for this part also must include the usability specifications that you established and a description of the evaluation that you are planning.
In Step 5,
Your group evaluate the prototype developed. You should utilize the evaluation measures that you identified in that part as well. We expect that your evaluation involves sample users interacting with your system. These users likely are your client(s) and maybe other students from class or other people who would fit your target user population. Give the users a few simple benchmark tasks and have them interact
with your interface. Closely study what occurs. Deploy a questionnaire to get subjective feedback about the interface and interaction.
Your write-up for this part should include the following components:
• A description of the evaluation techniques, tasks and users involved in your study
• The design rationale for the evaluation tasks and materials you employed
• Description of the results of the study (data presentation)
• A discussion of the results
• The implication that you make from the results concerning your design
• A description of how the prototype design could be improved in light of the implications
The key to this part of the project is not to describe your evaluation methodology but to rise above that and describe what you learned from it. Explain why you chose the benchmark tasks that you did. Why did you ask users what you asked? What conclusions can you draw from the studies?
What aspects of your design "worked" and what failed to meet your specifications? If you had more time to work on the design, what would you now change and improve? Remember, no designer ever gets a system "just right." Teams who honestly and carefully assess their design and who provide a plan for their improvement will be rewarded.
Write a report that adequately describes and document your feedback interactive system design.
The report should have the following structure:
1. Introduction
2. The design steps 1- 5 mentioned above.
3. Conclusion
4. References