300582 Technologies for Web Applications Autumn 2017Edition: Autumn 2017 Copyright c 2017 University Western Sydney trading as Western Sydney University ABN 53 014 069 881 CRICOS Provider No: 00917K No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without the prior written permission from the Dean of the School of Computing, Engineering & Mathematics. Copyright for acknowledged materials reproduced herein is retained by the copyright holder. All readings in this publication are copied under licence in accordance with Part VB of the Copyright Act 1968. Unit Details Unit Code: 300582 Unit Name: Technologies for Web Applications Credit Points: 10 Unit Level: 2 Assumed Knowledge: Basic programming principles and program control structures equivalent to that covered in Programming Fundamentals. Basic file management and PC operation including how to access and search the World Wide Web. Modes of Delivery Mode Hours Lecture 2 Practical 2 Note: Students with any problems, concerns or doubts should discuss those with the Unit Coordinator as early as they can. Unit Coordinator Name: Paul Davies Phone: 02 4620 3405 Location: Campbelltown Campus, 26.1.24 Email: [email protected] Consultation Arrangement: Consultation details will be published in the unit vUWS site in the Tutor Details link.Teaching Team Name: Dr. Luke Bozzetto Email: [email protected] Consultation Arrangement: Consultation details will be published in the unit vUWS site in the Tutor Details link. Name: Andrew Brunker Email: [email protected] Consultation Arrangement: Consultation details will be published in the unit vUWS site in the Tutor Details link. Name: Rhys Tague Phone: 02 4620 3910 Location: Campbelltown Campus, 26.1.47 Email: [email protected] Consultation Arrangement: Consultation details will be published in the unit vUWS site in the Tutor Details link. Name: Rekha Nachiappan Email: [email protected] Consultation Arrangement: Consultation details will be published in the unit vUWS site in the Tutor Details link. Name: Nathan Poultney Consultation Arrangement: Consultation details will be published in the unit vUWS site in the Tutor Details link.Note: The Learning Guide Companion supplements this document Contents 1 About Technologies for Web Applications 2 1.1 An Introduction to this Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2 What is Expected of You . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.3 Changes to Unit as a Result of Past Student Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Assessment Information 3 2.1 Unit Learning Outcomes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2 Approach to Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3 Contribution to Course Learning Outcomes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4 Assessment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.5 Assessment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.5.1 Web Application Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.5.2 Practical Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.5.3 Practical Quiz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.6 General Submission Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3 Teaching and Learning Activities 16 4 Learning Resources 17 4.1 Recommended Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 11 About Technologies for Web Applications 1.1 An Introduction to this Unit Building on material covered in Programming Fundamentals this unit introduces students to some of the key technologies for developing interactive and dynamic web applications from both the client and server perspective. The unit covers web site design, web site development, web page accessibility and usability, HTML, CSS, client side and server side scripting, database interaction, web site promotion (Search Engine Optimisation) and web security. 1.2 What is Expected of You Study Load A student is expected to study an hour per credit point a week. For example a 10 credit point unit would require 10 hours of study per week. This time includes the time spent within classes during lectures, tutorials or practicals. Attendance This unit consists of a 2-hour Lecture, and a 2-hour Practical class each week. Attendance is not compulsory at the lectures but definitely encouraged. Attendance at the practical programming test during session is compulsory since this is a mandatory component of the assessment. Attendance at the Practical and Assignment checkpoints is not compulsory, however non-attendance will result in a zero mark for the checkpoint. During other weeks attendance at practical classes is not compulsory, however it is strongly encouraged since valuable practical skills are developed during these classes; non-attendance may lead to failing the unit. Online Learning Requirements Unit materials will be made available on the unit’s vUWS (E-Learning) site (https://vuws.westernsydney.edu.au/) You are expected to consult vUWS at least twice a week, as all unit announcements will be made via vUWS. Teaching and learning materials will be regularly updated and posted online by the teaching team. vUWS. Special Requirements Essential Equipment: Not Applicable Legislative Pre-Requisites: Not Applicable 1.3 Changes to Unit as a Result of Past Student Feedback Student feedback pays a vital role in improving the quality and educational effectiveness of Western Sydney University units and in ensuring academic staff keep in touch with student needs. You are welcome to provide feedback that is related to the teaching of this unit. At the end of the semester you will be given the opportunity to complete a Student Feedback on Unit (SFU) questionnaire to assess the unit. If requested by your unit coordinator, you may also have the opportunity to complete a Student Feedback on Teaching (SFT) questionnaire to provide feedback for individual teaching staff. As a result of student feedback, the following changes and improvements have recently been made: { Updated PHP database access { Improve some coding examples 22 Assessment Information 2.1 Unit Learning Outcomes Outcome 1 Create simple web pages demonstrating a working knowledge of HTML and Cascading Style Sheets 2 Create web pages that include appropriate multimedia content to enhance presentation and/or usability. 3 Create web-based forms incorporating client side scripting to validate user input on the browser. 4 Construct simple dynamic web pages with server side database interaction and server side scripting. 5 Create functional and usable web sites using technologies outlined in learning outcomes 1, 3, and 4 and incorporating:- basic principles of human-computer interface design;- current accessibility principles and standards;- current search engine optimisation techniques. 6 Implement appropriate server-side code to provide simple authentication and access control to a web application. 2.2 Approach to Learning Type Approach Lecture Lectures are designed to provide students with the essential building blocks of knowledge required to successfully complete this unit. Lectures will provide students with an understanding of the material covered at a level that is not possible to attain through mere reading of resources alone. Two hours of lecture will be held each week. Lecture slides are downloadable from vUWS on a weekly basis; bring a copy along to the lecture each week to annotate to make review of the notes more beneficial. Also read the relevant chapter from the textbook before attending the lecture each week. Practical This unit is very ’hands-on’. During practicals, students will be exposed to many skills that are best learnt by doing. During practicals, students work at their own pace, but need to meet the deadlines for submission of their practical work. The practicals also include checkpoints, in which students show their work-in-progress to their tutor, who will mark the work. Being a very practically-oriented unit, there is no final written examination at the end of the semester. Instead, a restricted open book practical quiz will be run during a practical session which will assess various coding and other technical skills in a controlled environment. vUWS All lecture slides, code samples, and the specifications for the practical exercises and the major Web Application Assignment will be available on vUWS. The marking for the practical exercises and the assignment will also be conducted via rubrics on vUWS. 32.3 Contribution to Course Learning Outcomes 3639: Bachelor of Information and Communications Technology Course Learning Outcomes ULO 1 ULO 2 ULO 3 ULO 4 ULO 5 ULO 6 1. Explain the complex networks involved when dealing with people, business and government in the context of ICT development, support and service provision. 2. Evaluate the technological and software core of ICT theory and practice analysing and designing applications Developed Developed Developed Developed 3. Apply the knowledge and skills required for the development of new applications and new application areas Developed Developed Developed Developed 4. Innovate by keeping up to date with the rapid development in technology and practice across the ICT domain, as an extension of their current understandings and the ability to find innovative ICT solutions and move the ICT field forward. Introduced 5. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change relating to privacy of information and professional practice. Introduced Introduced 3687: Bachelor of Information Systems Course Learning Outcomes ULO 1 ULO 2 ULO 3 ULO 4 ULO 5 ULO 6 1. Communicate in a professional manner with others at all levels within and beyond the industry and across discipline, cultural and national boundaries, orally, in writing and through presentations. 2. Understand the importance of a strong synergies between people, processes and selected technologies. Developed Developed 3. Research, plan, implement and monitor systems to provide appropriate and ongoing quality assurance in respect to all work undertaken according to current standards in the computing industry. Introduced Developed Developed 4. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change and professional practice Introduced Introduced 5. Work independently and as a member of a team, including cross-discipline teams, and plan, manage and report on personal and project deliverables Introduced Introduced 6. Innovate, research and look for new technologies and tools that can assist businesses when implementing cutting edge information systems. Introduced Introduced 43506: Bachelor of Computer Science Course Learning Outcomes ULO 1 ULO 2 ULO 3 ULO 4 ULO 5 ULO 6 1. Communicate in a professional manner with others at all levels within and beyond the industry and across discipline, cultural and national boundaries, orally, in writing and through presentations. 2. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change and professional practice Introduced Introduced 3. Work independently and as a member of a team, including cross-discipline teams, and plan, manage and report on personal and project deliverables Introduced Developed Developed 4. Plan, implement and monitor systems to provide appropriate and ongoing quality assurance in respect to all work undertaken Introduced Developed Introduced 5. Demonstrate an understanding of a variety of computer systems, their capabilities and limitations Introduced Introduced 52.4 Assessment Summary The assessment items in this unit are designed to enable you to demonstrate that you have achieved the unit learning outcomes. Completion and submission of all assessment items which have been designated as mandatory or compulsory is essential to receive a passing grade. To pass this unit you must: 1. Complete and submit the Web Application Assignment 2. Complete and submit the Practical Exercises 3. Achieve at least 40% in the Practical Quiz 4. Achieve a unit total of at least 50% Item Weight Due Date ULO’s Assessed Threshold Web Application Assignment 30% 7pm Friday 19th May 2017 5,6 No Practical Exercises 40% 1. Set 1 Checkpoint: in week 4 practical class 2. Set 1: 7pm Friday 31st March 2017 3. Set 2 Checkpoint: in week 9 practical class 4. Set 2: 7pm Friday 5th May 2017 1, 2, 3, 4 No Practical Quiz 30% In allocated practical class in week 14 1, 3, 4 Yes Note: Results may be moderated before you receive your results. Moderation is a process whereby the unit coordinator regulates the marking of individual markers to achieve consistency in the application of unit objectives, performance standards and marking criteria. Marks for an individual piece of assessment will not be changed after you have your results. You should note that, consistent with the Assessment Policy - Criteria and Standards-Based Assessment (http://policies.uws.edu.au/view.current.php?id=00227), the final marks for the cohort may also be adjusted if marks are very high or low or there are inconsistencies between groups. Feedback on Assessment Feedback is an important part of the learning process that can improve your progress towards achieving the learning outcomes. Feedback is any written or spoken response made in relation to academic work such as an assessment task, a performance or product. It can be given to you by a teacher, an external assessor or student peer, and may be given individually or to a group of students. As a Western Sydney University student, it is your responsibility to seek out and act on feedback that is provided to you as a resource to further your learning. Written feedback will be provided via vUWS for practical sets and the programming project. This feedback will be made available online as soon after the submission deadline as is practicable; normally this is two weeks. As well as written feedback, another form of feedback known as checkpoints will be implemented as part of the Practical Set assessments; Checkpoints will enable students to receive immediate verbal feedback from their tutor enabling them to learn from their current mistakes and make improvements to their future submission of the practical exercises; checkpoints are discussed in more detail in section 2.5.1 of this learning guide. Students are encouraged to use the verbal feedback provided to improve their understanding of the key concepts and to implement improved solutions in subsequent assessments. 62.5 Assessment Details 2.5.1 Web Application Assignment Weight: 30% Type of Collaboration: Individual Due: 7pm Friday 19th May 2017 Submission: source code via unit web server Format: html, css, js, php source code files Length: Up to 15 interactive and dynamic web pages Curriculum Mode: Professional Task Instructions: The Web Application Assignment will cover web page/site design with HTML5 and CSS, client-side programming with Javascript, and server side programming with PHP. The Assignment will combine and extend the skills that you have learnt via the practical exercises. It is therefore essential that students undertake their practical exercises seriously to gain key skills in web development. Each student will be given a website hosted on a web server set up by the school for the teaching period of this unit. Students need to upload all their source files to their website to test and validate their work. Students also have to upload a ZIP containing their source code to vUWS. This ZIP must contain the exact copy of the source files found on their server. A code similarity program may be used to detect plagiarism. Referencing Requirements When coding practical exercises and the project in this unit it is a requirement that each student submits original work only, however it is understood that students may sometimes use segments of code from other sources as inspiration for their work. These sources may include the lecture notes and practical exercises, a textbook, or tutorial site from the web. In these cases the student must make sure that the work is not copyright and that full acknowledgment of the source of the original work is given in the submitted assessment item. These sources must not be another students work (past or present) and must not be directly pertaining to the assessment item. Students in this unit are not permitted to submit assessment questions or sections of code to Internet coding forums or the like. Students found to have done so will be dealt with under the Western Misconduct Rule. Where inspiration is found in a resource as described above then appropriate acknowledgement of the source must be included in the assessment submission. For coded functions this acknowledgement will take the form of a code comment in the line immediately preceding declaration of the function. For a code segment this acknowledgement will take the form of a code comment in the line immediately preceding the code segment and another code comment in the line immediately after the last line of the code segment. If the source is a resource available on the Internet then it should detail sufficient information such that the marker can directly view the original source without having to delve through a series of links or searches of their own to locate it (i.e., a full URL pointing directly to the resource). If the source is from a text book or similar then insert a code comment as described above but which uses APA (American Psychological Association) referencing style as detailed in the following link to the UWS library site: http://library.uws.edu.au/citing.php Examples of how to implement appropriate referencing within code can be found in the FAQ in the TWA vUWS site. When marking, any non-original work that has not been referenced in this way will have an appropriate mark penalty applied and if considered serious by the Unit Coordinator may be investigated as suspected academic misconduct. Resources: 1. lecture notes 2. sample code 3. textbook 4. http://w3schools.com 5. http://au2.php.net/manual/en/index.php Marking Criteria: 7The following marking criteria will be used to assess the Web Application Assignment; the relative weighting of each criteria will be indicated in the relevant assessment specification document. The program code submitted for marking MUST be submitted in the specified format, comply with file naming standards as defined in the question and must be written in the language required by the question. All web pages must render correctly in the most recent release of Firefox and Chrome web browsers as used in the SCEM labs. CRITERIA Unacceptable (0%) Poor (25%) Satisfactory (50%) Good (75%) Excellent (100%) Code Functionality/Correctness** Functional item(s) does not execute because of errors; Output is correct for less than 25% of marking test cases; No error checking code included as required by question; Output is simply dumped to the screen without any semblance of logic or thought, the user would be confused by this output Functional item(s) executes but with some errors and/or handles some special cases correctly; The Functional item(s) contains very minimal error checking code as required by the question; Functional item(s) output is correct for at least 25% of marking test cases; Output is simply written to the screen without any clear organisation or thought, the user would find it hard to understand Functional item(s) executes without errors and handles some special cases correctly; The Functional item(s) contains most error checking code as required by the question; Output is correct for at least 50% of marking test cases; Output is well organised for some function points and is generally easy for the user to understand Functional item(s) executes without errors and handles most special cases correctly; The Functional item(s) contains most error checking code as required by the question; Output is correct for at least 75% of marking test cases; Output is well organised and is mostly easy for the user to understand Functional item(s) executes without errors and handles all special cases correctly; The Functional item(s) contains thorough error checking code as required by the question; Output is correct for all marking test cases. Output is very well organised and is easy for the user to understand Code Readability Incorrect/ inappropriate use of white space and indentation; The code is poorly organized and very difficult to read. The code is readable only by someone who knows what it is supposed to be doing The code is fairly easy to read but either incorrect/ inappropriate use of white space or indentation. The code is quite well organised and is generally easy to follow; Correct/ appropriate use of white space AND/OR indentation The code is exceptionally well organized and very easy to follow; Correct/ appropriate use of white space and indentation. 8CRITERIA Unacceptable (0%) Poor (25%) Satisfactory (50%) Good (75%) Excellent (100%) Form Design No effort in form design shown; User accessibility standards have not been employed; Inappropriate input devices chosen Limited form design; The form is only usable by someone that knows what is expected; User accessibility standards have been employed in only very minor ways; Some input devices chosen are appropriate but most are not Reasonable form design employed; Some of the applicable user accessibility standards have been employed within the form; Less than 60% of input devices chosen are appropriate Good form design employed; Most applicable user accessibility standards have been employed within the form; Most input devices chosen are appropriate Excellent form design employed; All applicable user accessibility standards have been employed within the form; All input devices chosen are appropriate. Web Page Design No effort in page design shown; User accessibility standards have not been employed where appropriate; Limited page design; The page layout, colours, images, and text artefacts show limited effort and understanding of importance to the user experience; User accessibility standards have been employed in only very minor ways; Reasonable page design employed; The page layout, colours, images, and text artefacts show moderate effort and understanding of importance to the user experience; Some of the applicable user accessibility standards have been employed where appropriate; Good page design employed; The page layout, colours, images, and text artefacts show good effort and understanding of importance to the user experience; Most applicable user accessibility standards have been employed where appropriate Excellent page design employed; The page layout, colours, images, and text artefacts show excellent effort and understanding of importance to the user experience; All applicable user accessibility standards have been employed where appropriate. * As a special case, if a program does not meet the specifications at all / is entirely incorrect, no marks will be received for the other criteria either. ** As a special case, if a program does not render or execute it is still possible to receive partial marks in this criteria at the markers discretion dependant upon clear attempts at functional logic of the code. 92.5.2 Practical Exercises Weight: 40% Type of Collaboration: Individual Due: 1. Set 1 Checkpoint: in week 4 practical class 2. Set 1: 7pm Friday 31st March 2017 3. Set 2 Checkpoint: in week 9 practical class 4. Set 2: 7pm Friday 5th May 2017 Submission: source code via unit web server Format: html, css, js, php source code files Length: Two sets - 6 to 10 web pages each deliverable Curriculum Mode: Professional Task Instructions: There are two (2) sets of practical exercises (called Prac Sets) that will be assessed during session. Each Prac Set will comprise a small number of questions that are designed to build relevant web programming/development skills. Checkpoints Each Prac Set will involve one (1) checkpoint (worth 3 marks) and a final submission (worth 17 marks). Checkpoints are an opportunity for the student to demonstrate their code to their tutor in class to: 1) obtain a progressive mark for the work completed to date; 2) obtain informal verbal feedback from the tutor, which can be used by the student to improve their work, prior to final submission for the Prac Set. Checkpoints are implemented in this unit as a mechanism to: encourage students to actively participate in their learning over a period of several weeks; progressively enhance their skills in the essential building blocks of practical knowledge; learn from their mistakes prior to submitting the work for formal marking; and assist the student to maximize their marks by improving their work, based upon informal verbal feedback given by the tutor, before final submission. Checkpoints will be carried out in designated weeks in the students registered practical class (see table in section 3 of this learning guide and on the Prac Set specification document for checkpoint weeks). Details on how checkpoints are conducted, how marks are achieved, and what to do if you miss a checkpoint can be found in the FAQ in vUWS. Referencing Requirements When coding practical exercises and the project in this unit it is a requirement that each student submits original work only, however it is understood that students may sometimes use segments of code from other sources as inspiration for their work. These sources may include the lecture notes and practical exercises, a textbook, or tutorial site from the web. In these cases the student must make sure that the work is not copyright and that full acknowledgment of the source of the original work is given in the submitted assessment item. These sources must not be another students work (past or present) and must not be directly pertaining to the assessment item. Students in this unit are not permitted to submit assessment questions or sections of code to Internet coding forums or the like. Students found to have done so will be dealt with under the Western Misconduct Rule. Where inspiration is found in a resource as described above then appropriate acknowledgement of the source must be included in the assessment submission. For coded functions this acknowledgement will take the form of a code comment in the line immediately preceding declaration of the function. For a code segment this acknowledgement will take the form of a code comment in the line immediately preceding the code segment and another code comment in the line immediately after the last line of the code segment. If the source is a resource available on the Internet then it should detail sufficient information such that the marker can directly view the original source without having to delve through a series of links or searches of their own to locate it (i.e., a full URL pointing directly to the resource). If the source is from a text book 10or similar then insert a code comment as described above but which uses APA (American Psychological Association) referencing style as detailed in the following link to the UWS library site: http://library.uws.edu.au/citing.php Examples of how to implement appropriate referencing within code can be found in the FAQ in the TWA vUWS site. When marking, any non-original work that has not been referenced in this way will have an appropriate mark penalty applied and if considered serious by the Unit Coordinator may be investigated as suspected academic misconduct. Resources: 1. lecture notes 2. sample code 3. textbook 4. http://w3schools.com 5. http://au2.php.net/manual/en/index.php Marking Criteria: The following marking criteria will be used to assess each question in each Prac Set; the relative weighting of each criteria will be indicated in the relevant assessment specification document. The program code submitted for marking MUST be submitted in the specified format, comply with file naming standards as defined in the question and must be written in the language required by the question. All web pages must render correctly in the most recent release of Firefox and Chrome web browsers as used in the SCEM labs. CRITERIA Unacceptable (0%) Poor (25%) Satisfactory (50%) Good (75%) Excellent (100%) Code Functionality/Correctness** Functional item(s) does not execute because of errors; Output is correct for less than 25% of marking test cases; No error checking code included as required by question; Output is simply dumped to the screen without any semblance of logic or thought, the user would be confused by this output Functional item(s) executes but with some errors and/or handles some special cases correctly; The Functional item(s) contains very minimal error checking code as required by the question; Functional item(s) output is correct for at least 25% of marking test cases; Output is simply written to the screen without any clear organisation or thought, the user would find it hard to understand Functional item(s) executes without errors and handles some special cases correctly; The Functional item(s) contains most error checking code as required by the question; Output is correct for at least 50% of marking test cases; Output is well organised for some function points and is generally easy for the user to understand Functional item(s) executes without errors and handles most special cases correctly; The Functional item(s) contains most error checking code as required by the question; Output is correct for at least 75% of marking test cases; Output is well organised and is mostly easy for the user to understand Functional item(s) executes without errors and handles all special cases correctly; The Functional item(s) contains thorough error checking code as required by the question; Output is correct for all marking test cases. Output is very well organised and is easy for the user to understand 11CRITERIA Unacceptable (0%) Poor (25%) Satisfactory (50%) Good (75%) Excellent (100%) Code Readability Incorrect/ inappropriate use of white space and indentation; The code is poorly organized and very difficult to read. The code is readable only by someone who knows what it is supposed to be doing The code is fairly easy to read but either incorrect/ inappropriate use of white space or indentation. The code is quite well organised and is generally easy to follow; Correct/ appropriate use of white space AND/OR indentation The code is exceptionally well organized and very easy to follow; Correct/ appropriate use of white space and indentation. Form Design No effort in form design shown; User accessibility standards have not been employed; Inappropriate input devices chosen Limited form design; The form is only usable by someone that knows what is expected; User accessibility standards have been employed in only very minor ways; Some input devices chosen are appropriate but most are not Reasonable form design employed; Some of the applicable user accessibility standards have been employed within the form; Less than 60% of input devices chosen are appropriate Good form design employed; Most applicable user accessibility standards have been employed within the form; Most input devices chosen are appropriate Excellent form design employed; All applicable user accessibility standards have been employed within the form; All input devices chosen are appropriate. Web Page Design No effort in page design shown; User accessibility standards have not been employed where appropriate; Limited page design; The page layout, colours, images, and text artefacts show limited effort and understanding of importance to the user experience; User accessibility standards have been employed in only very minor ways; Reasonable page design employed; The page layout, colours, images, and text artefacts show moderate effort and understanding of importance to the user experience; Some of the applicable user accessibility standards have been employed where appropriate; Good page design employed; The page layout, colours, images, and text artefacts show good effort and understanding of importance to the user experience; Most applicable user accessibility standards have been employed where appropriate Excellent page design employed; The page layout, colours, images, and text artefacts show excellent effort and understanding of importance to the user experience; All applicable user accessibility standards have been employed where appropriate. * As a special case, if a program does not meet the specifications at all / is entirely incorrect, no marks will be received for the other criteria either. ** As a special case, if a program does not render or execute it is still possible to receive partial marks in this criteria at the markers discretion dependant upon clear attempts at functional logic of the code. 122.5.3 Practical Quiz Weight: 30% Type of Collaboration: Individual Due: In allocated practical class in week 14 Submission: source code via quiz web server Format: html, css, js, php source code files Length: 90 minutes Curriculum Mode: Quiz Threshold Detail: A minimum mark of 40% is required in this assessment to pass the unit. Instructions: The Practical Quiz is designed to test students knowledge of the unit material covered in lectures, recommended reading, practical exercises and coding skills. The test will require students to solve relatively simple web programming problems and implement solutions in any of the languages covered in the unit in an invigilated environment. The Practical Quiz will contain several short answer coding questions. The quiz will be held in the students registered practical class during week 14, will be 1.5 hours duration and will be partial open-book. Specific restrictions will be placed upon the resources that students will be allowed to use during the quiz. These restrictions will be identified via vUWS leading up to the quiz. The test will cover all material covered in weeks 1 to 13. Attendance at the quiz is compulsory; a penalty (10% per day, for each day after the scheduled date) will be applied to students who do not sit the test in their registered practical class. Prior permission must be sought from the unit coordinator by the student if it is known that they will not be able to attend the quiz, or as soon after the sitting date as practicable, if not. It is the students responsibility to ensure that they are correctly registered for a practical class in Allocate+ for this purpose. It is also the students responsibility to ensure that they have full access to the unit vUWS site for the purpose of undertaking and submitting the quiz. Resources: The following resources will be helpful to prepare for the Practical Quiz: 1. lecture notes 2. sample code 3. textbook 4. http://w3schools.com 5. http://au2.php.net/manual/en/index.php During the Practical Quiz students will be allowed to use limited resources. These will be detailed via vUWS leading up to the Quiz. Marking Criteria: The following marking criteria will be used to assess each question in the Practical Quiz; the relative weighting of each criteria will be indicated in the quiz document. The program code submitted for marking MUST be submitted in the specified format, comply with file naming standards as defined in the question and must be written in the language required by the question. All web pages must render correctly in the most recent release of Firefox and Chrome web browsers as used in the SCEM labs. 13CRITERIA Unacceptable (0%) Poor (25%) Satisfactory (50%) Good (75%) Excellent (100%) Code Functionality/Correctness** Functional item(s) does not execute because of errors; Output is correct for less than 25% of marking test cases; No error checking code included as required by question; Output is simply dumped to the screen without any semblance of logic or thought, the user would be confused by this output Functional item(s) executes but with some errors and/or handles some special cases correctly; The Functional item(s) contains very minimal error checking code as required by the question; Functional item(s) output is correct for at least 25% of marking test cases; Output is simply written to the screen without any clear organisation or thought, the user would find it hard to understand Functional item(s) executes without errors and handles some special cases correctly; The Functional item(s) contains most error checking code as required by the question; Output is correct for at least 50% of marking test cases; Output is well organised for some function points and is generally easy for the user to understand Functional item(s) executes without errors and handles most special cases correctly; The Functional item(s) contains most error checking code as required by the question; Output is correct for at least 75% of marking test cases; Output is well organised and is mostly easy for the user to understand Functional item(s) executes without errors and handles all special cases correctly; The Functional item(s) contains thorough error checking code as required by the question; Output is correct for all marking test cases. Output is very well organised and is easy for the user to understand * As a special case, if a program does not meet the specifications at all / is entirely incorrect, no marks will be received for the other criteria either. ** As a special case, if a program does not render or execute it is still possible to receive partial marks in this criteria at the markers discretion dependant upon clear attempts at functional logic of the code. 142.6 General Submission Requirements Submission { All assignments must be submitted by the specified due date and time, using a completed and signed Assignment Cover Sheet provided in the Learning Guide Companion. { Complete your assignment, attach a completed and signed Assignment Cover Sheet, and follow the individual assessment items instructions on how to submit. Turnitin { The Turnitin plagiarism prevention system may be used within this unit. Turnitin is accessed via logging into vUWS for the unit. If Turnitin is being used with this unit, this means that your assignments have to be submitted through the Turnitin system. { Turnitin from iParadigms is a web-based text-matching software that identifies and reports on similarities between documents. It is also widely utilised as a tool to improve academic writing skills. { Turnitin compares electronically submitted papers against the following: { Current and archived web: Turnitin currently contains over 24 billion web pages including archived pages { Student papers: including Western Sydney University student submissions since 2007 { Scholarly literature: Turnitin has partnered with leading content publishers, including library databases, textbook publishers, digital reference collections and subscription-based publications (e.g. Gale, Proquest, Emerald and Sage) { Turnitin is used by over 30 universities in Australia and is increasingly seen as an industry standard. It is an important tool to assist students with their academic writing by promoting awareness of plagiarism Self-Plagiarising { You are to ensure that no part of any submitted assignment for this unit or product has been submitted by yourself in another (previous or current) assessment from any unit, except where appropriately referenced, and with prior permission form the Lecturer/Tutor/Unit Co-ordinator of this unit. Late Submission { If you submit a late assessment, without receiving approval for an extension of time, (see next item), you will be penalised by 10% per day for up to 10 days. In other words, marks equal to 10% of the assignment’s weight will be deducted from the mark awarded. { For example, if the highest mark possible is 50, 5 marks will be deducted from your awarded mark for each late day. { Saturday and Sunday are counted as one calendar day each. { Assessments will not be accepted after the marked assessment task has been returned to students. { This is consistent with Clause 51 of the Western Sydney University’s Assessment Policy - Criteria and StandardsBased Assessment. Extension of Due Date for Submission Extensions are only granted in exceptional circumstances. To apply for an extension of time: { Locate an application form via the Western Sydney University homepage or copy the following link: http://www.westernsydney.edu.au/currentstudents/current students/forms { Application forms must be submitted to the Coordinator. { Requests for extension should be made no later than 3 working days before the due date of an assignment or other assessment item including web-based quizzes. { Appropriate, supporting documentation must be submitted with the application. { An application for an extension does not automatically mean that an extension will be approved { Assessments will not be accepted after the marked assessment task has been returned to students. Resubmission Resubmission of assessment items will not normally be granted if requested. Application for Special Consideration It is strongly recommended that you attend all scheduled learning activities to support your learning. If you have suffered misadventure, illness, or you have experienced exceptional circumstances that have prevented your attendance at class or your completion and submission of assessment tasks, you may need to apply for Special Consideration via the Western Sydney University website. http://www.westernsydney.edu.au/currentstudents/current students/services and facilities/ special consideration2 or the Student Centre. Special Consideration is not automatically granted. It is your responsibility to ensure that any missed content has been covered. Your lecturer will give you more information on how this must be done. 153 Teaching and Learning Activities Weeks Lecture Prac/Lab Instructions Assessments Due Week 1 20-02-2017 Unit Introduction HTML5 No practicals in week 1 Week 2 27-02-2017 Cascading Style Sheets (CSS) Work on Prac Set 1 Week 3 06-03-2017 JavaScript - DOM Work on Prac Set 1 Week 4 13-03-2017 JavaScript - Forms Work on Prac Set 1 Prac Set 1 checkpoint Prac Set 1 checkpoint in registered prac class - Practical Exercises Week 5 20-03-2017 JavaScript - Client-side validation Work on Prac Set 1 Week 6 27-03-2017 PHP - Introductory Work on Prac Set 1 Prac Set 1 due this week - Practical Exercises Week 7 03-04-2017 PHP - Database Access, Maintaining State Work on Prac Set 2 Week 8 10-04-2017 Week 9 17-04-2017 No lectures on any campus this week due to public holiday 17/04/2017 Web Accessibility (online content) Work on Prac Set 2 Prac Set 2 Checkpoint Prac Set 2 checkpoint in registered prac class - Practical Exercises Week 10 24-04-2017 PHP - Server-side validation Work on Prac Set 2 Campbelltown Tuesday prac students may attend other classes this week (public holiday 25/04/2017). Week 11 01-05-2017 PHP - Authentication and Authorisation Work on Prac Set 2 Prac Set 2 due this week - Practical Exercises Week 12 08-05-2017 Web Security Work on Web Application Assignment Week 13 15-05-2017 Search Engine Optimisation Work on Web Application Assignment Web Application Assignment due this week - Web Application Assignment Week 14 22-05-2017 No Lectures this week. Practical Quiz run in allocated practical class. Practical Quiz run in allocated practical class. - Practical Quiz Week 15 29-05-2017 Week 16 05-06-2017 The above timetable should be used as a guide only, as it is subject to change. Students will be advised of any changes as they become known. 164 Learning Resources 4.1 Recommended Readings Prescribed Textbook { Connolly, R., & Hoar, R. (2015). Fundamentals of Web Development. Harlow: Pearson Additional Reading { Brooks, D. R. (2011). Guide to HTML, JavaScript and PHP: For Scientists and Engineers. London: Springer-Verlag London Limited. { Feorster, K., & eOggl, B. (2011). HTML5 guidelines for Web developers. Upper Saddle River, NJ: Addison-Wesley. { Goodman, D., Morrison, M., Novitski, P., & Rayl, T. G. (2010). JavaScript bible (7th ed.). Hoboken, NJ: Wiley. { Huseby, S. (2004). Innocent Code: A Security Wake-up Call for Web Programmers. West Sussex: John Wiley. { Lazar, J. (2006). Web Usability - A User-Centered Design Approach. Addison Wesley { Lepofsky, R. (2014). The Manager’s Guide to Web Application Security A Concise Guide to the Weaker Side of the Web. Berkeley, CA: Apress. { McCracken, D.D., & Wolfe, R.J. (2004). User-Centered Website Development - A Human-Computer Interaction Approach. Upper Saddle River: Prentice Hall { Meloni, J. C. (2012). Sams Teach Yourself PHP, MySQL and Apache- All in One (5th ed.). Indianapolis: SAMS { Meloni, J. C. (2015). Sams teach yourself HTML, CSS and JavaScript all in one. Indianapolis IN: Sams. { Morris, T. (2013). Web development and design foundations with HTML5. Boston: Pearson. Osborn, J. (2011). Html5. Indianapolis, IN : Wiley { Sikos, L. F. (2011). Web Standards: Mastering HTML5, CSS3, and XML. Berkeley, CA: Apress. { Vodnik, S. (2011). HTML 5 and CSS 3 : illustrated, complete. Boston, Mass. : Course Technology/Cengage Learning { Wellens, P. (2015). Practical Web Development. Birmingham: Packt Publishing. { Yank, K. (2012). PHP & MySQL: novice to ninja. Collingwood, Vic: SitePoint. 17