Unit Outline

This unit introduces fundamental programming skills, developing students' ability to think algorithmically to solve problems and to express their solutions in well-constructed Python code. Beginning with the fundamental characteristics of computers and how they represent information, the unit develops the concepts of data types, variables, expressions (calculations), statements (actions) and text-based input and output. Building on these low-level constructs the unit examines ways to manage the complexity in a program with control structures (for making decisions), functions and their parameters, built-in and custom data structures, and higher-level organisational mechanisms such as modules.

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 code reading and debugging techniques to analyse, interpret, and describe the purpose of program code, and to identify and correct errors in syntax, logic or style
2	Apply the principles of structured programming to the design and implementation of algorithms as computer programs
3	Construct small programs that include the use and creation of functions, lists, and other data structures
4	Apply functional decomposition to algorithms, document the resulting design, and implement the design as programming modules and functions

Alterations as a result of student feedback

Nil. But assessment tasks have been changed and rubrics altered following semester 1 delivery.

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	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
	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. Begins in Week 2.	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:	Semester Performance	See the MyLO site for the due date	10 %	LO1, LO2, LO3, LO4
Assessment Task 2:	Advanced Portfolio	Refer to Assessment Description	40 %	LO1, LO2, LO3, LO4
Assessment Task 3:	Pass Portfolio	Refer to Assessment Description	50 %	LO1, LO2, LO3, LO4

Assessment details

Assessment Task 1: Semester Performance

Task Description:

Your PP, CR, DN, and HD portfolio engagement and results will be used to provide an adjustment within the grade you earn. Lower marks will be given if work is commenced after the due dates, completed after the deadlines (which must be done with approval of the Unit Coordinator), or if academic misconduct is determined. Higher marks will be awarded if work is submitted early, completed on time, free of academic misconduct, and if the student has attempted higher-level portfolio work.

Task Length:

Not relevant.

Due Date:

See the MyLO site for the due date

Weight:

10 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Completion of portfolio tasks within the time-frame and without unauthorised (or authorised but unacknowledged) use of external resources -- including generative AI	LO1, LO2, LO3, LO4
2	Completion of one or more assessment tasks from the 'next' portfolio.	LO1, LO2, LO3, LO4

Assessment Task 2: Advanced Portfolio

Task Description:

In addition to the pass-level work you have the opportunity to extend your abilities with portfolio tasks at CR, DN and HD levels. These introduce more sophisticated techniques and debugging exercises, as well as the opportunity to design and then implement a program of your own design. Completion of all tasks of a particular level and those below it qualifies you for that final grade. Achieving a High Distinction requires that the HD Program task as well as an additional HD Project and Interview allowing achievement of a higher mark within the HD band.

Task Length:

Varies by task, but typically 1-2 source files (more for DN and HD custom programs), a 5 minute video, and/or 1-5 pages of documentation

Due Date:

Refer to Assessment Description

Weight:

40 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Identify and document faults in more complex code samples and suggest appropriate corrections	LO1
2	Correctly apply structured programming principles of sequence, selection and repetition as required by the task	LO2
3	Implement all required functionality using the full range of programming techniques taught in the unit (in programming tasks)	LO3
4	Implement software as a collection of interacting functions given a plan	LO3, LO4
5	Devise own plan for implementing software as a collection of functions	LO4
6	Prepare external documentation for a program of your own design	LO4
7	Adhere to the unit’s coding style for layout, variable names, and commenting	LO3
8	Demonstrate and discuss the implementation of your custom program	LO4

Assessment Task 3: Pass Portfolio

Task Description:

Throughout the semester you will work on a collection of learning tasks (categorised as PP, CR, DN or HD level), submitting these for feedback at their staggered due dates.

Resubmission is possible any time between the date of release and the deadline (10 days after the due date).

Feedback is provided if the tasks are submitted prior to their due date; if submitted after the due date but before the deadline they will be marked without the opportunity for improvement based upon feedback.

The PP-level tasks demonstrate pass-level achievement in the unit. Tasks are assigned a status to indicate if further revision is required (Revise), the work is nearing completion subject to discussion with your tutor (Discuss), if they are under extended review (Investigating), not submitted prior to the due date (Overdue), not submitted prior to the deadline (Unsubmitted), not completed prior to the deadline (Failed), or they are complete. Completion is categorised as on-time (Complete) or late (Conceded).

The number of Conceded results will affect your mark within the grade of result you earn.

You will need to be submitting (and revising) tasks most weeks.

Task Length:

Varies by task, but typically a single source file, a diagram, or 1-4 pages of text using a provided template

Due Date:

Refer to Assessment Description

Weight:

50 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Describe how program state changes in provided code samples	LO1
2	Select appropriate data types for modelling different phenomena	LO1
3	Identify faults in provided code samples and suggest appropriate corrections	LO1
4	Correctly apply structured programming principles of sequence, selection and repetition as required by the task	LO2
5	Implement all required functionality using specified techniques (in programming tasks)	LO3
6	Implement software as a collection of interacting functions given a plan	LO3, LO4
7	Devise own plan for implementing software as a collection of functions	LO4
8	Adhere to the unit’s coding style for layout, variable names, and commenting	LO2, LO3

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.

Academic progress review

The results for this unit may be included in a review of your academic progress. For information about progress reviews and what they mean for all students, see Academic Progress Review in the Student Portal.

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.