Unit Outline
KIT202
Web Programming Fundamentals
Semester 1, 2024
James Montgomery
School of Information and Communication Technology
College of Sciences and Engineering
CRICOS Provider Code: 00586B

Unit Coordinator
James Montgomery
Email: James.Montgomery@utas.edu.au
 

What is the Unit About?
Unit Description
This unit introduces students to the technologies that make up the fabric of the web—HTML, CSS and JavaScript—as well as standard web models and practices, key web design and usability principles, common security issues and mitigation strategies, and data-driven backend development with PHP and SQL. The unit assumes a sound basic knowledge of programming and database skills as developed in the introductory units in these areas. Working in small teams you will develop an interactive web application, focusing first on the frontend technologies that define the user interface before creating a database-driven backend solution to make the application interactive. Alongside this you will develop your individual skills, compiling a portfolio of web technology demonstrations. The unit serves as an important foundation for further study in web development, including the use of server- and client-side frameworks.
Intended Learning Outcomes
As per the Assessment and Results Policy 1.3, your results will reflect your achievement against specified learning outcomes.
On completion of this unit, you will be able to:
1.
Design frontend web interfaces using industry standard tools and techniques to satisfy user experience requirements in accordance with best practice
2.
Program functional websites that employ secure backend data management techniques
3.
Construct cross-platform secure web applications using collaborative approaches
Requisites
REQUISITE TYPE
REQUISITES
Pre-requisite
KIT101 or KIT107 or KIT103
Alterations as a result of student feedback
The two tests (previously accounting for 40% of the unit's assessment) have been removed, with a greater emphasis placed on the practical products created during tutorials and self-study time (the new semester-long portfolio assessmnet task). At the same time, the order of topics has been adjusted so that there is a more gradual introduction to fundamental skills.
 
 

Teaching arrangements
ATTENDANCE MODE
TEACHING TYPE
LEARNING ACTIVITY
CONTACT HOURS
FREQUENCY
On Campus
Workshop
A structured real-time (i.e. synchronous) activity that involves a mix of presentation of new information/ideas/skills and guided activities related to that information/ideas/skills. All students are expected to attend.
2
Weekly
Computer Laboratory
A structured real-time (i.e. synchronous) computer-based activity in a small-group setting where the primary purpose is the clarification, exploration or reinforcement of subject content presented or accessed at another time or place (e.g. lecture, preparatory work). It is teacher supported and may involve student-teacher and/or student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the class are expected to attend.
2
Weekly
Attendance / engagement expectations
If your unit is offered On campus, it is expected that you will attend all on-campus and onsite learning activities. This is to support your own learning and the development of a learning community within the unit. If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.

If your unit is offered Online, it is expected you will engage in all those activities as indicated in the Unit Outline, including any self-directed learning.

If you miss a learning activity for a legitimate reason (e.g., illness, carer responsibilities) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.
 
 
 
 

How will I be Assessed?
 
For more detailed assessment information please see MyLO.
Assessment schedule
ASSESSMENT TASK #
ASSESSMENT TASK NAME
DATE DUE
WEIGHT
LINKS TO INTENDED LEARNING OUTCOMES
Assessment Task 1:
Assignment 1: Frontend
Week 7
25 %
LO1, LO2, LO3
Assessment Task 2:
Assignment 2: Backend
Week 13
35 %
LO1, LO2, LO3
Assessment Task 3:
Tutorial Portfolio
Refer to Assessment Description
40 %
LO1, LO2
 
Assessment details
    
Assessment Task 1: Assignment 1: Frontend
Task Description:
A group-based assignment in which the frontend interface for a web application will be designed and developed using industry standard tools and techniques.

Peer evaluation will be used as a component of the assignment submission to determine an individual group member's contribution.

Task Length:
4-10 HTML, CSS and JavaScript source files plus an individual contribution document
Due Date:
Week 7
Weight:
25 %
 
CRITERION #
CRITERION
MEASURES INTENDED
LEARNING OUTCOME(S)
1
Design a frontend web interface that satisfies user experience requirements
LO1
2
Implement a web site according to a set of functional requirements
LO2, LO3
 
Assessment Task 2: Assignment 2: Backend
Task Description:
A group-based assignment in which the backend components of a web application, including a database, will be designed and developed incorporating secure data management techniques. This assignment builds on the frontend interface completed in Assignment 1.

Peer evaluation will be used as a component of the assignment submission to determine an individual group member's contribution.

Task Length:
5-10 PHP pages, CSS document, 1-2 JavaScript source files, database documentation (ER diagram and database dictionary) plus an individual contribution document
Due Date:
Week 13
Weight:
35 %
 
 

CRITERION #
CRITERION
MEASURES INTENDED
LEARNING OUTCOME(S)
1
Design and implement a database to support a defined web application
LO2
2
Implement a web application according to a set of functional requirements
LO1, LO2, LO3
 
Assessment Task 3: Tutorial Portfolio
Task Description:
Each tutorial you will produce artefacts that demonstrate core web development skills. Across the semester you will compile a portfolio of examples, accompanied by reflections on what you learned and how your learning progresses across semester. The final submission has a longer reflection report. Components of the portfolio are assessed at regular intervals across the semester

Task Length:
Artefacts produced in and outside the 2 hour tutorial
Due Date:
Refer to Assessment Description
Weight:
40 %
 
CRITERION #
CRITERION
MEASURES INTENDED
LEARNING OUTCOME(S)
1
Design and implement solutions to given tasks
LO1, LO2
2
Provide reflections in response to prompts that summarise your learning experience and identify areas of strength and areas needing further development
LO1, LO2
 
 
 

How your final result is determined
To pass this unit, you need to demonstrate your attainment of each of the Intended Learning Outcomes, achieve a final unit grade of 50% or greater, and pass any hurdle tasks.
 
Submission of assignments
Where practicable, assignments should be submitted to an assignment submission folder in MYLO. You must submit assignments by the due date or receive a penalty (unless an extension of time has been approved by the Unit Coordinator). Students submitting any assignment in hard copy, or because of a practicum finalisation, must attach a student cover sheet and signed declaration for the submission to be accepted for marking.
 
Requests for extensions
If you are unable to submit an assessment task by the due date, you should apply for an extension.
 
A request for an extension should first be discussed with your Unit Coordinator or teaching support team where possible. A request for an extension must be submitted by the assessment due date, except where you can provide evidence it was not possible to do so. Typically, an application for an extension will be supported by documentary evidence: however, where it is not possible for you to provide evidence please contact your Unit Coordinator.
 
The Unit Coordinator must notify you of the outcome of an extension request within 3 working days of receiving the request.
Late penalties
Assignments submitted after the deadline will receive a late penalty of 5% of the original available mark for each calendar day (or part day) that the assignment is late. Late submissions will not be accepted more than 10 calendar days after the due date, or after assignments have been returned to other students on a scheduled date, whichever occurs first. Further information on Late Penalties can be found on the Assessments and Results Procedure.
 
Review of results and appeals
You are entitled to ask for a review of the marking and grading of your assessment task if there is an irregularity in the marking standards or an error in the process for determining the outcome of an assessment. Details on how to request a review of a mark for an assignment are outlined in the Review and Appeal of Academic Decisions Procedure.
 
 
 

Required Resources
Required reading materials
N/A
 
Recommended reading materials
N/A
 
Other required resources
COMPUTING FACILITIES
The Discipline of ICT has PC labs, Mac labs, and special purpose Networking labs at the Newnham and Sandy Bay campuses. All students are provided with logins for Windows, Macintosh and Unix environments. If you have not used these facilities before please contact the ICT Help Desk. If you would like to access these facilities after hours please contact the ICT Help Desk.

USE OF FACILITIES
Use of computing facilities provided by the Discipline of ICT is subject to the Discipline's Ethics Guidelines, details of which are posted at http://www.utas.edu.au/technologyenvironmentsdesign/ict/currentstudentresources/ethicsguidelines.

Copies of the guidelines are also available in all ICT labs. The Discipline's facilities may only be used for study related purposes, and may not be used for personal gain. Antisocial behaviour in labs such as game playing, viewing pornography, loud discussion, audio without the use of headphones, etc is strictly prohibited in all labs at all times.

Eating, drinking, and smoking is not permitted in the labs. Before being granted access to the Discipline's facilities, you will be required to sign a declaration that you have read and understand these guidelines, and that you will abide by them. You will also be required to complete the relevant MyLO course to gain access. Disciplinary action may be taken against students who violate the guidelines. Details about gaining access to the labs can be found at ICT Reception.