BY CAMILLA MAHONGABY KAVANAGHHANNAH ROGERS

ERIKA FISHER

‘Optimising Children’s Outcomes’

(OCO)

Overview of Application

Aimed primarily at teachers and educators,However there are two types of users;

The Educator, The Parent,

Designed as an iPad ‘App’;(Based on requirements gathering) Accessibility

Our users/ use case examples

Two users;•The Educator•The Parent

•1st Use Case example shows the educator emailing a progress report of a child to their parent (Search for child, by name, click progress report, by week, email)

•2nd Use Case example shows the educator adding a student profile

Persona

Use Case 1 – The educator

Persona

Use Case 2 – Parent

Methodology

We conducted a user centred design approach when designing the ‘OCO’ application.

What is user centred design?Why use this and not another?

What is User Centred Design?

User Centred design is a user interface design process in which the needs and wants of the end user are given extensive attention.

Multi stage problem solving process. The difference from other product design is that

user-centred design tries to optimize the product around how users can, want, or need to use the product, rather than forcing the users to change their behaviour to accommodate the product (Bryce, 1996).

But Why User Centred Design?User Centred Design is a well established

process that is used by many organisations to deliver products that meet users expectations (Sugar, 2001).

Ensures that the software is usable to novice users as well as advanced users.Prevents loss of money, due to insurance of use (Cooper, Reimann & Cronin, 2008)

Requirements Gathering

we conducted an online questionnaire for our initial requirements gatheringi.e., “Would you feel comfortable with your child/children/class being monitored by this

technology?”

yes

yes, with properprecusions taken

No

Requirements Gathering

Display of DataDisplay of Data• - How the data would be displayed,

• What criteria you are looking for?• Just dedicated to individual child/ compared against class

average? • Just attention? – incorporate attendance/test results?

grades

attendence

attention

Other

Other = parent teacher forum

Require AnalysisWhat decisions were What decisions were

concluded?concluded?

•iPad application•What to include•Who this is being aimed at•May not have time to give one on one attention•Teacher to parent forum

Decided to focus on individual child's reported data for Use Cases -including emailing to parents

Short Interview (With Primary school teacher,

teaching special needs children)

•Understanding that every child has different needs and every class group has different needs,

•Needing to better understand her class to better plan her class schedule,

•Providing one on one level of education

Use Case ID 1

Version 1.0

Author Camilla Mahon

Use Case Name Emailing Progress report of child to parent

Actor(s) Teacher

Description The teacher wants to view a certain child’s data and email the results to their parents. The system must display data and provide emailing option.

Pre-Conditions Teacher must be logged in. Child must have profile set up. Child must be monitored in order to accumulate data.

Normal Flow Users email is successful•User selects specific child profileSystem accumulates data and interpretations – system displays graphs and percentages User adds comment to the data (optional)System registers data input - system displays data with interpretation and teacher comment.User chooses email functionSystem emails report to associated parent email

Alternative Flow Users email fail User selects specific child profileSystem accumulates data and interpretations – system displays graph and percentagesUser adds comment to data (optional)System registers data input - system displays data with interpretation and teacher comment.User chooses email functionSystem displays error message indicating there are no email accounts registered to the child, the user is prompted to enter the email manually.

Post-Conditions User is prompted to save used email – user is notified that email has been successfully sent

Open-Issues

Use Case ID 2

Version 1.0

Author Camilla Mahon

Use Case Name Adding a student profile

Actor(s) Educator

Description Educator wants to add a profile and upload a picture of the student to the database with all the relevant information. The system must save and display the profile.

Pre-Conditions User should be logged in.

Normal Flow Successful adding of a profileUser selects add student profile System displays registration formUser fills in the details requiredSystem checks that all the fields have been filled out System displays a add image optionUser uploads imagesSystem saves images to profile– system displays message indicating profile has been saved successfully

Alternative Flow Un-Successful adding of a profileUser selects add student profile System displays registration formUser fills in the details requiredSystem checks that all the fields have been filled out System displays error message due to invalid information inputSystem highlights the sections to be corrected

Post-Conditions profile is now viewable – data will be collected

Open-Issues

Interface Design

How I applied interface design rules to my prototype: Nielsen’s Heuristics Nielsen’s Heuristics (They are called "heuristics"

because they are more in the nature of rules of thumb than specific usability guidelines).

Pressman's Principles Pressman's Principles (An agile yet disciplined framework for building web applications).

Other Mobile Design PrinciplesOther Mobile Design Principles

Nielsen’s Heuristics(Examples)

Help users recognize,diagnose, and recoverfrom errors

Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.

Nielsen’s Heuristics(Examples)

User control and freedom

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue.

Pressman's Principles(examples)

Navigability

o The user should be able to understand how to move about the WebApp without having to search for navigational links.

Pressman's Principles(examples)

Anticipation

o The user should be able to anticipate his or her next move

Theresa Neil(Example)

Visibility of system status

(Feedback)

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

Testing(Usability Testing)

Paper Usability testing

Home screen:(Feedback)

bare – colour scheme?

(Changes)create colour scheme to give user a sense of how it will look

Add profile – image page:

(Feedback)where to press?

(Changes)include information on page

Testing(Prototype Testing)

• Created complete working Prototype using Axure

• Performed Prototype testing• Made changes due to feedback

• Gave working prototype• Gave criteria - asked users to navigate through

prototype based on use case criteria• Noted user actions• Asked for user feedback

Log in page

(Before) (After)

Home Page - Linking Icons

(Before) (After)

Typing

(Before) (After)

Navigation

(Before) (After)

References Alan Cooper, Robert Reimann, David Cronin, About Face 3: The

Essentials of Interaction Design, Publishing house of electronics industry, 2008.

Bryce, A. (1996). Information tasks: Toward a user-centered approach to information systems. (1st ed.). Orlando, Florida, USA: Academic Press, Inc.

Neil, T. (2009). Principles and patterns for rich interaction.Designing Web Interfaces,

Nielsen, J., and Molich, R. (1990). Heuristic evaluation of user interfaces, Proc. ACM CHI'90 Conf. (Seattle, WA, 1-5 April), 249-256.

Pressman, R. (2000). Software engineering principles. (5th ed.). Mcgraw Hill Higher Education.

Sugar, W. (2001). What is so good about user-centered design? documenting the effect of usability sessions on novice software designers. Journal of Research on Computing in Education,

Thank you for listening

Any Questions?