CP1406/CP5638 Assignment 2 – Full Website Project Overview In
this assignment, students will continue working on from their Fashion
Clothing 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 (Milestone 1 due 5pm Friday Week 8) 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 5 pages listed in Page 2 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 10 to test your
site. This plan will be developed in the Week 9 prac. Milestone 2 – Finished Product (Due 5pm Friday Week 10) 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 9, 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 P2 Finished site components at a minimum are: Home Page with content written to rank well on search engines (including meta data) Specials describes current 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 Powell Fashion and Clothing Shop email list. The form
should ensure that all fields have been filled in correctly (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 Powell Fashion and Clothing Shop Weekly newsletter. We have added the following information to our files regarding your interests: Name:Email: Product interests: Birthday: Usability Testing In week 10 you should follow a prescribed usability testing process involving realistic users, whom you will need to organise for a live testing session. You may undertake this as part of your prac in week 10, or do it outside of class. You will then update and improve the site based on the results of this testing. Milestones 1 & 2 – 40% for CP1406 Due 5pm Friday for both Milestone 1 (week 8) and Milestone 2 (week 10) 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. 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. P3 Items required for Assessment 2 submission 1. Response to Feedback & Design Comps 2. User Testing Report and Further Development Suggestions 3. Updated web site Submission 1. Upload your work to your web server. 2. Upload a zip file containing all the files for this assessment to LearnJCU. Provide a note on the submission page with a link to your published web site and the username/password to view the files . ASSESSMENT TASK 2: CRITERIA SHEET Criteria Exemplary (90%, 100%) Good (70%, 80%) Satisfactory (50%, 60%) Limited (20%, 30%, 40%) Very Limited (0%, 10%) 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 carried out. Website reflects the
changes requested in the feedback, and are complete, suitable and in line with customer brief. 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 carried out. Website reflects some or most of the changes requested in the feedback, and are generally complete, suitable and in line with customer brief. 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 brief. 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 errors 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 correct 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. CSS is mostly used effectively to separate form and function. The HTML content structure is correct. 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 errors. alt attributes are used correctly 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 errors. 15% alt attributes used correctly for all images. Technical Aspects Website performs well, file sizes and names are appropriate (e.g. no spaces). Images are displayed at correct sizes. No technical problems can be found. Website performs well, file sizes and names are mostly appropriate. Images are mostly displayed at correct sizes. Minimal technical problems can be found. Problems with: broken links, images not displayed at correct 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%