Unit Outline

Today's modern integrated technology is built on ICT systems that run in a range of contexts (e.g. Servers, PCs, mobile computing, robotics) using a range of technological solutions. Students will examine a range of different devices used to build ICT infrastructure. By exploring computing devices students will gain a fundamental understanding of the similarities and differences in modern computer hardware, operating systems, networks, and cloud computing. Throughout the unit, students will develop a set of core competencies related to Unix command line instructions and introductory shell scripting for automation of repetitive tasks, file system navigation, file security and maintenance, and combining commands into pipelines. The key focus of the unit is to provide students with knowledge of operating system fundamentals and practical skills to apply that knowledge. The main operating systems topics covered in this unit include operating systems structure and services, process management and coordination, memory management including modern implementations of virtual memory, operating system security, file systems, device management, and input/output principles. The main focus will be on the Unix operating system but the different approaches in other operating systems will be examined.

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	Apply industry standard techniques to configure and troubleshoot processes running on systems
2	Use tools and commands to navigate file systems and secure and manipulate files
3	Design and author scripts to automate tasks
4	Compare the implementation of operating system features across a range of platforms

Requisites


REQUISITE TYPE	REQUISITES
Pre-requisite	KIT101 OR KIT103 OR KIT107
Anti-requisite (mutual excl)	KIT104

Alterations as a result of student feedback

Tutorial materials related to Unix file system and Unix shell scripting have been revised. Workshop materials on the latest operating system development have been added.

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
	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
	Independent Learning	Involving reading, listening to audio, watching video, and/or completing exercises and/or quizzes, self-study is individual work undertaken when the student chooses (i.e. asynchronous), most likely through engagement with MyLO. The content is examinable, and may need to be completed prior to attending classes and/or attempting assessment tasks.	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 or includes online activities, it is expected you will engage in all those activities as indicated in the Unit Outline or MyLO, 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:	Operating System Report	Week 8	20 %	LO4
Assessment Task 2:	File system competency test	Week 10	10 %	LO2
Assessment Task 3:	UNIX Shell Scripting	Week 13	30 %	LO3
Assessment Task 4:	Skills based quiz	Refer to Assessment Description	10 %	LO1
Assessment Task 5:	Examination	Exam Period	30 %	LO1, LO2, LO3, LO4

Assessment details

Assessment Task 1: Operating System Report

Task Description:

Students are required to write a report that compares the implementation of specified operating system features across multiple given platforms.

Task Length:

No more than 2000 words.

Due Date:

Week 8

Weight:

20 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Describe the specified feature(s)	LO4
2	Analyse the implementation of the feature(s) on each given platform	LO4

Assessment Task 2: File system competency test

Task Description:

A practical demonstration of competency with navigating file systems and manipulating files. This will be a 30-minute test conducted within a tutorial. Students will be given multiple tasks to complete to demonstrate competency.

Task Length:

50-minutes

Due Date:

Week 10

Weight:

10 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Navigate a file system	LO2
2	Edit and secure files and directories	LO2
3	Combine commands into pipelines to filter and manipulate file content	LO2

Assessment Task 3: UNIX Shell Scripting

Task Description:

Several specific system-level tasks will be provided. Students will use Unix shell programming skills to achieve those tasks.

Task Length:

Software code

Due Date:

Week 13

Weight:

30 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Design, write and test a script to achieve a given task	LO3

Assessment Task 4: Skills based quiz

Task Description:

This is continuous assessment that demonstrates completion and understanding of the tutorial tasks. Students must correctly demonstrate Unix command line solutions through quiz questions directly aligned with the practical material.

Task Length:

60-minute tutorial weekly

Due Date:

Refer to Assessment Description

Weight:

10 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Test commands to determine correct solutions to Unix-specific problems	LO1

Assessment Task 5: Examination

Task Description:

Online exam that explores the depth of the student’s knowledge and ability to respond appropriately with the correct file systems commands, identify issues with scripts, and explain operating system features

Task Length:

120 minutes

Due Date:

Exam Period

Weight:

30 %

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.

Academic integrity

Academic integrity is about acting responsibly, honestly, ethically, and collegially when using, producing, and communicating information with other students and staff members.

In written work, you must correctly reference the work of others to maintain academic integrity. To find out the referencing style for this unit, see the assessment information in the MyLO site, or contact your teaching staff. For more detail about Academic Integrity, see Important Guidelines & Support.

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