Tasks:

Prepare a detailed design document for the user interface for your project. Your design document should be based on your Project Requirements and Scope document and your Project Design proposal. Your design document should include the following sections, as a minimum:

1. Design overview;

2. Project scope;

3. Business and User requirements;

4. Key assumptions;

5. Design process to be used;

6. Interface Design, including the following sections with justification for use:

1. All screen layouts;
2. All components identified, with justification for their use;
3. Workflow diagrams for major tasks (if required);
4. Use of colour, frames and sections;
5. Help and user assistance functions;
6. Use of icons;
7. User task navigation;
7. Usability testing and evaluation, including the following sections with justification for use:
1. Evaluation aims;
2. Evaluation methodology;
3. Test audience selection and ethical considerations;
4. Evaluation experiments;
5. Analysis methodology and procedures.

This is the final design for your project so all the sections in the document should be complete in all detail.

Your design document should not exceed ~25 pages in length, excluding references. You will need to reference all literature, applications and websites using the APA 6th edition referencing style.

This assignment assesses a student's ability to:
o Critically examine and interpret the principles of design that are applicable to the design of an interface;
o Critically examine and evaluate a user interface design to determine if it meets a given set of requirements;
o Interpret, analyse and evaluate usability testing results to plan interface design improvements;

Project Design Proposal

Table of Contents
 Overview
 Design Aims
 Scope
 Design Outline
 Objectives and Outputs
 Key Assumptions
 Proposed Evaluation Methods

Overview

This section should give a brief overview of your design aims and how you propose to meet them. You should be looking at 2 - 3 paragraphs here. This section is best written AFTER you have completed the rest of the document. Remove this text when you have completed the section.

Design Aims

This section is where you outline the aims of your design. This should be reasonably high level and give the AIMS of your design. This tells the reader HOW you propose to meet the user requirements without going into the details of screens, colours, widgets, etc. You need to talk about the CONCEPT that you have for the design and WHY you are doing it this way. This is an extension of your Vision statement and allows you to sell your design concepts. You'll probably want to very briefly refer to the principles of design that you are using here to reinforce your argument.

Scope

If the scope has changed from your project brief, then update it here now and explain what has changed and why.

Design Outline

Here you need to list all the major outcomes of your design project and tell the reader how you will deliver them. You need to describe what you are going to deliver along with an outline of each deliverable. This may include preliminary wireframes for each of the major screens, and should include a brief description of major components and/or task sequences. If the design is to be delivered in phases, make sure that everything is grouped in the correct order in each phase.

Objectives and Outputs

This is a critical section. Here you list your user requirements and objectives and then show how each section of the design meets them. This can be done as a list, a table or even a requirements matrix. I'd suggest a table in the document as it's much cleaner and easier to control.

Key Assumptions

Have your key assumptions changed?These will need to be reviewed as you proceed. List all your key assumptions, and any changes here.

Proposed Evaluation Methods

How are you going to evaluate the design when it is finished? Here you need to outline your evaluation plan and how you will analyse the results. This doesn't need to be a full plan yet, this is an outline, but it should contain enough details that the plan itself can be evaluated for completeness and appropriateness. A list of steps is acceptable at this time, provided that it comes with some explanatory text.