Assignment 2 - Website Project
Overview
In this assignment, students will continue working on from their bakery sites. In this assignment, students will ensure that the site is responsive, has web form functionalities and uses JavaScript and PHP, to allow user data validation. In this assignment HTML, CSS, JS and PHP are to be employed.
Because students already have already a simple site and received feedback (A1), they should be able to improve their site accordingly. Also, for this assignment, User testing and Usability testing are performed. The student is required to implement least one item that was specified in the feedback on Assessment 1.
You have two milestones that will be submitted together as part of this one project. These are summarised here with further details below:
Milestone 1 Response to Feedback & Design Comps (10%, show progress to tutor in week 11)
· Part 1: Response to feedback
Copy and paste your feedback into a Word document and specify how you will address the items. You must identify at least one item to focus on for your second submission.
· Part 2: Design Rationalisation
For the 3 pages listed below you must describe each page in detail, specifying colour choices, images, fonts and content. You must specify how you will make any changes needed due to feedback from Assessment 1
· Part 3: Usability test plan
You will create a test plan to be used in the prac in Week 12 to test your site
Milestone 2 - Finished Product (30%, due week 13)
This is the full, finished product website, the result of you going through the complete website design and development process. Use the outputs of Milestone 1 to develop a functional, finished site. Your site should be mostly complete by week 12, so that it is ready for usability testing. Assessment of this milestone is for both completeness and quality.
Milestone 2 items:
· User Testing Report and Further Development Suggestions
· Updated web site
The Usability Testing Report will follow the usability test plan you developed in Milestone 1. It should contain notes from your user testing, and a section discussing what improvements you think should be made to the site given more time
Finished site components at a minimum are:
Important: The requirements here are not specified as pages, but as features or functionality.
The information architecture is up to you to decide for whatever you think is best as a result of careful consideration in your planning.
Home Page with content written to rank well on search engines (including meta data)
Specials describes cu
ent sale items
Product Detail pages give information about each particular item
Contact Us Page gives information about organisers details and contact information
Newsletter Signup contains a form for the user to give their name, email address, product interests, birthday (day and month only) and approval to be added to the Tropical Treats email list. The form should ensure that all fields have been filled in co
ectly (using JavaScript data validation) and display a message on a following page showing the information that was sent.
For example:
Thank you for signing up for the Tropical Treats Weekly newsletter.
We have added the following information to our files regarding your interests:
Name:
Email:
Product interests:
Birthday:
Usability Testing
Follow a prescribed usability testing process involving realistic users, whom you will need to organise for a live testing session. Do 2 usability tests at least and write a report of the results of these tests. You will then update and improve the site based on the results of this testing.
Milestones 1 & 2 – 40%
Due: Week 13, Friday
Please note that it is acceptable to find and use code for parts of your site. You must write the core functionality yourself. You cannot use any existing content management systems or existing templates. The work you submit must be substantially your own.
Please ask on the slack discussion board or Facebook group if you are unsure about what is considered acceptable.
You must reference any code that you use that you did not create in your user testing report.
Items required for Assessment 2 submission
1. Response to Feedback & Design Comps
1. User Testing Report and Further Development Suggestions
1. Updated web site
Submission
1. Upload your work to your web server.
1. Upload a zip file containing all the files for this assessment. Provide a note on the submission page with a link to your published web site and the username/password to view the files using cPanel
ASSESSMENT TASK 2: CRITERIA SHEET
Criteria
Exemplary (9, 10)
Good (7, 8)
Satisfactory (5, 6)
Limited (2, 3, 4)
Very Limited (0, 1)
Weighting
Response to feedback
Document contains a copy of the feedback received in Assessment 1 and a clear response stating how the changes suggested have been ca
ied out.
Website reflects the changes requested in the feedback, and are complete, suitable and in line with customer
ief.
Exhibits aspects of exemplary (left) and satisfactory (right)
Document may contain a copy of the feedback received in Assessment 1 and shows a somewhat clear response stating how the changes suggested have been ca
ied out.
Website reflects some or most of the changes requested in the feedback, and are generally complete, suitable and in line with customer
ief.
Exhibits aspects of satisfactory (left) and very limited (right)
Document either not submitted or of a low quality. Response if given is of limited thought.
Website does not reflect many of the changes requested or may not be in line with the customer
ief.
10%
Content
The content of the website is complete and of a high standard. Content has been written/edited to suit the Web, the audience and site goals. Content is goal-driven.
Exhibits aspects of exemplary (left) and satisfactory (right)
The content of the website is complete and of a decent standard. Content has mostly been written/edited to suit the Web, the audience and site goals. Content is mostly goal-driven.
Exhibits aspects of satisfactory (left) and very limited (right)
Content is incomplete and/or of a low standard, containing e
ors and not being suitable for the Web, audience or site goals. Not goal-driven.
10%
Information Design
Text has been (re)formatted to be suitable for page purposes and for site goals, images enhance meaning of text. Calls-to-action are used appropriately and well designed.
Most text has been (re)formatted to be suitable for page purposes and for site goals, images enhance meaning of text. Calls-to-action are used appropriately. Visual design of content is lacking.
Text appears just copied from client content or is poorly presented, images not used or not used well to enhance communication. Missing calls-to-action.
10%
Interface Design
Design is professional, consistent, and suitable for site goals and audience. Navigation is well presented.
Design is mostly professional but visually lacking, consistent, suitable for site goals and audience. Navigation is fine.
Poor quality design, not suitable for site goals and audience. Navigation is poorly presented.
10%
Information Architecture
Content is very well organised to be suitable for site goals. Good naming of pages/links. Processes are easy to follow due to good design. It is easy to locate all of the important elements.
Content is mostly well organised to be suitable for site goals but with minor problems. Naming of pages/links is fine. Processes are reasonably easy to follow. It is easy to locate all of the important elements.
Content organisation seems illogical. Poor naming of pages/links. Processes are hard to follow due to poor design. It is mostly difficult to locate important elements; or information is missing.
15%
HTML & CSS
CSS is used effectively to separate form and function. The HTML content structure is co
ect and viewable with styles disabled. External style sheet(s) used as appropriate. Selectors are well chosen, class names are meaningful. HTML and CSS code is appropriate and all code is valid. alt attributes used co
ectly for all images.
CSS is mostly used effectively to separate form and function. The HTML content structure is co
ect. External style sheet(s) used as appropriate. Selectors are mostly well-chosen, class names are not all meaningful. HTML and CSS code is mostly appropriate and code has minimal validation e
ors. alt attributes are used co
ectly for most images.
CSS is barely used or poorly used. Class names are not meaningful. Styles are inappropriately embedded in HTML. Content structure is not suitable. HTML code is used inappropriately (e.g. use of deprecated elements or attributes). alt attributes are not used for images. Lots of validation e
ors.
15%
Technical Aspects
Website performs well, file sizes and names are appropriate (e.g. no spaces). Images are displayed at co
ect sizes. No technical problems can be found.
Website performs well, file sizes and names are mostly appropriate. Images are mostly displayed at co
ect sizes. Minimal technical problems can be found.
Problems with:
oken links, images not displayed at co
ect size, slow loading, image file sizes are too big or images are over-compressed (poor quality), spaces in file names.
10%
JavaScript
Good use of JavaScript and PHP including form validation and image gallery. Code used is of a high standard (identifier naming, formatting and commenting).
Sufficient use of JavaScript and PHP including form validation and image gallery. Code used is mostly of a high standard (identifier naming, formatting and commenting) but with some problems.
No or very minimal JavaScript and PHP. Code used is of a low standard (identifier naming, formatting and commenting).
10%
Report
Report is complete with all required information.
Report is complete with sufficient required information.
Report is incomplete and and/or required information is absent.
10%
Assessment2 related files/Feedbacks from Assessment1.docx
· Some of the layout is a bit inconsistent between pages
· The text that goes 100% of the screen should be made more readable.
· Conventions suggest to me that all of the content on this site should be centered instead of having some on the left.
Assessment2 related files/Finished Assessment 1 Small web site/Assessment 1 Small web site/A1.docx
Assignment 1 – Due 5 April, 2019 5pm
Project Plan & Small Website
Task:
This assignment involves two parts, to be implemented as Web pages and submitted as described below.
1. Project Plan (plan.html)
2. Small Website files
Your (fictional) client for the assignment has provided an introductory email containing a description of their goals and some additional information regarding the site they would like you to build.
Your task is to turn this into a clear useful plan and a small functional website.
Project Plan:
Write your project plan so that it is a useful working document to guide your development.
Carefully consider the