Unit Outline
School of Information and Communication Technology
College of Sciences and Engineering
KIT202
Web Programming Fundamentals
Semester 2, 2023
Lawrence Sambrooks
CRICOS Provider Code: 00586B
 
Unit Coordinator
Lawrence Sambrooks
Email: lawrence.sambrooks@utas.edu.au
 
 
What is the Unit About?
Unit Description
This unit provides students with the knowledge, understanding and skills required to develop an application system that uses a web interface to a backend database. The unit assumes a sound basic knowledge of programming and database concepts and skills as developed in the introductory units in these areas. The emphasis in the unit is on mastery of the key concepts and the basic knowledge and skills required to build this kind of application. The unit will provide students with an awareness of the wide range of technologies that are used to support this kind of application, but will examine only a limited number of these technologies to demonstrate the key concepts and their application. The unit explores the purposes and approaches in using scripting and markup languages in relation to the client-server paradigm. The role of both server-side (backend) and client-side (frontend) code are examined. Students will study the use of markup and scripting programming languages to connect to databases via a network. Students are introduced to some of the most common security issues involved in the development of web-based software, including secure coding practices, secure database access, secure data communications, and the security of web applications. Students are provided with a range of practical exercises to reinforce their skills, including authenticating and authorising users programmatically, performing user input validation, and developing secure data-driven web applications.
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
Assignment and Tutorial weightings have been revised to better reflect the effort involved in producing task deliverables. Additional interactive activities have been added to online lectures to provide further opportunities for student engagement.
 
 
Teaching arrangements
ATTENDANCE MODE
TEACHING TYPE
LEARNING ACTIVITY
CONTACT HOURS
FREQUENCY
On Campus
Lecture (Online)
A real-time (i.e. synchronous) interactive activity involving the whole class whose primary purpose is the presentation and structuring of information/ideas/skills to facilitate student learning. All students are expected to attend.
2
Weekly
Tutorial
A structured real-time (i.e. synchronous) 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 reliant on student-teacher and student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the tutorial are expected to attend.
2
Weekly
Attendance/Engagement Expectations
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 miss a learning activity for a legitimate reason (e.g., illness, family commitments) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.
 
If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.
 
 
 
 
How will I be Assessed?
Assessment schedule
ASSESSMENT TASK #
ASSESSMENT TASK NAME
DATE DUE
WEIGHT
LINKS TO INTENDED LEARNING OUTCOMES
ASSESSMENT TASK 1:
Assignment 1
Week 6
25 %
LO1, LO2, LO3
ASSESSMENT TASK 2:
Assignment 2
Week 12
35 %
LO1, LO2, LO3
ASSESSMENT TASK 3:
Test
Refer to Assessment Description
20 %
LO1, LO2
ASSESSMENT TASK 4:
Weekly Tutorial Tasks
Refer to Assessment Description
20 %
LO1, LO2
Assessment details
Assessment Task 1: Assignment 1
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:
Source code
DUE DATE:
Week 6
WEIGHT:
25 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
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
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:
Source Code
DUE DATE:
Week 12
WEIGHT:
35 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
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: Test
TASK DESCRIPTION:
A one (1) hour online test delivered via MyLO in week 6 and week 13. Each test will assess the student's knowledge and understanding of the principles, processes, and practices used in developing functional web sites/applications. The first test will cover material from weeks 1-5 and the second test material from weeks 6-12.

 
TASK LENGTH:
2 x 1 hour
DUE DATE:
Refer to Assessment Description
WEIGHT:
20 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
1
Describe technical terms and techniques related to web site development
LO1, LO2
2
Compare frontend and backend web concepts
LO1, LO2
3
Justify implementation strategies for given scenarios using relevant examples
LO1, LO2
4
Explain secure data management techniques
LO2
 
Assessment Task 4: Weekly Tutorial Tasks
TASK DESCRIPTION:
Weekly tutorial tasks related to concepts discussed in lectures. Tasks will be assessed during scheduled tutorial classes in the week after the tutorial handout is released.

TASK LENGTH:
2 hour tutorial
DUE DATE:
Refer to Assessment Description
WEIGHT:
20 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
1
Design and implement solutions to given tasks
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.