Subject Outline PDF
See the schedule for when Subject Outline PDFs are due and when the subject sites are available in Canvas.
What does this table tell you?
The table below shows the fields that comprise the Subject Outline PDF.
The Where to update column indicates if the data is held in CASS (and therefore updates need to be requested via a UTS: Service Connect request to APO Curriculum) or CIS (and depending on your access, updates can be made via 'CIS: CI, Subjects', 'CIS: CI, Course Area', 'CIS: SO, Edit Main tab', or 'CIS: SO, Change Request tab', as specified).
The Note(s) section, if any, in the Description and format column specifies if:
- subject coordinators need to request changes via the 'Change Request' tab in SO
- changes must go through the APO:CIS approval process before they can be published (even if they have been through the workflow approval process).
- the field can contain different data depending on the instance (e.g. default, block, distance, etc.); if not, the data is drawn from the 'default' instance)
The Heading column shows the heading as displayed in the Subject Outline PDF (which made differ to the field name displayed in CIS).
Note: Information must be written in the present tense, third person, using full sentences (unless the field does not require full sentences).
Marketing speak, unsubstantiated non-factual claims, and jargon should be avoided.
| Field name | Where to update | Description and format | Heading |
| CASS subject number | CASS | Uses the official approved subject number | none |
| Subject name | CASS | Uses the official approved subject name | none |
| Course area | CASS | The course area that 'owns' / administers the subject. Stored in CASS as 'Keyword 1' | Course area |
| Teaching responsibility | CASS | The name of the organisational unit recorded on CASS as having teaching responsibility. Could be a faculty, school or department. If not specified on CASS, the default is the owning faculty. | none (follows on from course area, if available) |
| n/a | This data appears in the Subject Outline PDF under the 'Delivery' heading. It comes from the options chosen and the instance you're in when you create the Subject Outline PDF, e.g. If you are in the Default instance and you choose: Mode: 'Standard', Teaching period: 'Autumn', Year: '2011', Location: 'City' the 'Delivery' display on the PDF will be: 'Autumn 2011; standard mode; City'. Full details are available in the documentation at PDF naming conventions. | Delivery | |
| Linked subjects | CIS: CI, Subjects | Specify any other subjects that the description also applies to. Useful when a subject has a 6cp and 8cp offering but you only want to hand out the one outline in class, e.g. 'Note: This subject outline also applies to 50105 Communication and Information Environments.' Use the actual and complete name of the subject, without abbreviations or ampersands. You cannot use heading tags around the sentence. | none |
| Subject classification | CIS: CI, Subjects | Details the category/strand/program/classification that the subject falls into, e.g. 'Engineering Practice', 'Fields of practice: Electrical Engineering program', 'Disciplinary Strand – Communication and Information Studies – 100 level', 'Elective' This field starts on a new line, begins with a capital, and has no full stop at the end. Limit of 20 words (150 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Subject classification |
| CASS credit points | CASS | The credit point value of the subject. | Credit points |
| CASS academic requisites | CASS | This field details the compulsory Academic requisites stored in CASS. The brackets, which have to remain, are a result of parsing the requisite rules to display only the Academic requisites. All requisites are prerequisites unless otherwise indicated; a lower case 'c' after the subject code indicates that the subject is a corequisite. Antirequisites do not form part of CASS Academic requisites. | Requisite(s) |
| CASS other requisites | CASS | This field details the other requisites stored in CASS, e.g. 'Faculty approval required'. | Other requisites |
| Requisite elaboration/waiver | CIS: CI, Subjects CIS: SO, Change Request tab | This field is used if the 'CASS other requisite(s)' need explanation, e.g. to indicate the basis for obtaining Faculty approval, or to explain any circumstances of a requisite waiver. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Requisite elaboration/waiver |
| Result type | CASS | Defines the subject as either 'Graded, no mark', 'Graded, with mark', 'Pass/ Fail, no mark', 'Pass/ Fail, with mark'. | Result type |
| Recommended studies | CIS: CI, Subjects CIS: SO, Change Request tab | Include details of subjects or experience that students would benefit from having completed, but which don't fall into the compulsory CASS requisite category. The following styles apply: (a) when adding recommended subjects, insert the subject number followed by a single space and then insert the name of the subject (note: the faculty is responsible for keeping this data up to date; it cannot be auto-corrected if, for example, a change occurs in a CASS-stored subject name); (b) do not include requisites which should be part of Admission or Other requisites in CASS; (c) separate subjects with a semi-colon; (d) any other recommended studies should begin with a lower case letter, and be separated by a semi-colon if there is more than one; (e) do not include a full stop at the end; (f) note the text 'Recommended studies: ' will be auto-generated in publications so shouldn't be included in the field data; e.g. 013336 Contemporary Issues in Adult Education; 013709 E-Learning Design; a minimum of 80 per cent in the Basic Mathematics Skills Test Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Recommended studies |
| Attendance | CIS: CI, Subjects CIS: SO, Change Request tab | This field covers basic information relating to hours per week, mode of attendance, e.g. 6hpw, distance, on campus, block, weekly First letter must be in lower case (unless referring to session title) and there must be no full stop at the end of the section Information specific to particular teaching periods/modes, e.g. Summer session, tutorial, etc., should appear in brackets, e.g. 6hpw (Spring session), 9hpw (Summer session) 1hpw (lecture), 3hpw (laboratory) If the attendance information is particularly detailed, colons and/or semi-colons may be required for clarity (this should be avoided where possible, however), e.g. lectures (Summer session): 4hpw x 4wks (2hrs face-to-face; 2hrs blended learning), laboratory (Summer session): 6hpw x 4wks Limit of 20 words (150 characters) Minimum attendance expressed as a percentage belongs in the 'Minimum requirements' field, not this field, e.g. 'Students must attend 80 per cent of scheduled classes to pass the subject.' Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. • This is a compulsory CIS field. | Attendance: |
| Field group: Subject coordinator and teaching staff | The name and contact details for the subject coordinator and teaching staff must be provided in each subject outline. When the subject coordinator is the sole member of the teaching staff you can add these details to the 'Subject coordinator and contact details' field and leave the 'Teaching staff and contact details' field blank. Similarly, when the subject coordinator is a member of a larger teaching team, it is acceptable to leave the 'Subject coordinator and contact details' field blank and identify the coordinator instead in the staff listing in the 'Teaching staff and contacts details' field. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | n/a | |
| Subject coordinator and contact details | CIS: CI, Subjects CIS: SO, Edit Main tab | Provide details in the following format, as required; each component optional. [Subject coordinator's name in full, including any academic title, e.g. 'Dr John Smith', 'John Smith (Lecturer)' [Position] UTS: [xxxx] [Building ID location details] telephone (02) 9514 [xxxx] fax (02) 9514 [xxxx] email [xxxx]@uts.edu.au [Descriptive sentence about preferred means of contact.] Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Subject coordinator |
| Teaching staff and contact details | CIS: CI, Subjects CIS: SO, Edit Main tab | Provide details in the following format, as required; each component optional. [Title][first name][surname] [Position] UTS: [xxxx] [Building ID location details] telephone (02) 9514 [xxxx] fax (02) 9514 [xxxx] email [xxxx]@uts.edu.au [Descriptive sentence about each staff member and preferred means of contact.] Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Teaching staff |
| Description | CIS: CI, Subjects CIS: SO, Change Request tab | Write the subject description here. Information must be written in the present tense, third person, using full sentences, e.g. This subject covers ... Students learn to ... (rather than 'You will learn to ...) Limit of 300 words (2,250 characters) Note(s) • Changes must go through the APO:CIS approval process before they can be published. • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. • This is a compulsory CIS field. | Subject description |
| Field group: Subject learning objectives (SLOs) | The subject learning outcomes or objectives (SLOs), i.e. the professional, personal or academic knowledge, skills and values that students are expected to be able to demonstrate on completion of the subject. This data is stored in three fields updated via: CI / [subject code] / Graduate Attributes / Learning objectives: Code; Description; Short description. A standard SLO lead-in sentence can be added in CI / Course Area / SLO lead-in sentence. If it contains data, it will appear above the list of SLOs. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Subject learning objectives (SLOs) | |
| SLO lead-in sentence | CIS: CI, Course Area | Displayed as a lead-in sentence to the list of subject learning objectives (SLOs) in every subject outline PDF within the course area. SLOs appear under the 'Subject objectives' heading. Data in this field takes the form, e.g.: 'Upon successful completion of the subject students should be able to:' If left blank, the SLOs are displayed in the PDF, but without a lead-in sentence. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | |
| Graduate Attributes / Learning objectives / Code | CIS: CI, Subjects, Graduate Attributes tab CIS: SO, Change Request tab | Insert a code for the subject learning objective (SLO). The code should be an whole number or a letter (upper or lower case). Currently there is no system validation on codes but they should obviously be unique and in a sequence with no gaps. There is no limit to the number of SLOs that can be entered. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | |
| Graduate Attributes / Learning objectives / Description | CIS: CI, Subjects, Graduate Attributes tab CIS: SO, Change Request tab | Insert the full subject learning objective Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | |
| Field group: Course intended learning outcomes (CILOs) | The intended learning outcomes (CILOs) of the subject's parent study package that have been linked to via any of the subject's criteria linkage tables (CLTs), i.e. the professional, personal or academic knowledge, skills and values that students are expected to be able to demonstrate on completion of the course. This data is stored in three fields updated via: CI / [course code] / Graduate Attributes / Intended learning outcomes: Code; Description; Short description. A faculty-standard CILO lead-in sentence can be added via: CI / Course Area / CILO lead-in sentence (for display in SO PDF). If it contains data, it will appear above the list of linked CILOs. If the 'CILO lead-in sentence' field is left blank, the CILOs will NOT be displayed in full in the PDF. | Course intended learning outcomes (CILOs) | |
| CILO lead-in sentence (for display in SO PDF) | CIS: CI, Course Area | Displayed as a lead-in sentence to the list of course intended learning outcomes (CILOs) in every subject outline PDF within the course area. It appears under the 'Subject objectives' heading and after the list of SLOs. Data in this field takes the form, e.g.: 'This subject contributes to the following course intended learning outcomes:' If left blank, the CILOs will NOT appear under the 'Subject objectives' heading in the PDF. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | |
| Graduate Attributes / Intended learning outcomes / Description | CIS: CI, Courses, Graduate Attributes tab | Insert the full description for the course intended learning outcome (CILO). | |
| Graduate Attributes / Intended learning outcomes / Graduate attribute | CIS: CI, Courses, Graduate Attributes tab | Choose a graduate attribute from the drop-down list to link the CILO to | |
| Graduate Attributes / Intended learning outcomes / Sub-code | CIS: CI, Courses, Graduate Attributes tab | Insert a code. The sub-code should be an whole number or a letter. The complete code of the CILO is the code of the Graduate Attribute followed by a point followed by the sub-code (e.g.if the Graduate Attribute is '1' and the CILO sub-code is '2', then the automated CILO code is '1.2'). Currently there is no system validation on codes but they should obviously be unique and in a sequence with no gaps. There is no limit to the number of CILOs that can be linked to a Graduate Attribute. | |
| Contribution to the development of graduate attributes | CIS: CI, Subjects CIS: SO, Change Request tab | The format of this field has changed because course intended learning outcomes should now be stored via CIS / Course / Graduate Attributes / Intended learning outcomes. The field can be left blank (or blanked if there is already data in it: this can be done globally by CIS Admin) or can now be used to further explain the list of CILOs, e.g. when a subject is shared across several courses all with different CILOs, and the development of graduate attributes. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Contribution to the development of graduate attributes |
| Teaching and learning strategies | CIS: CI, Subjects CIS: SO, Change Request tab | This information should build on information already given in the Attendance field. What sort of activities will be undertaken in tutorials, practicals, etc. Information should cover all modes of delivery. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. • This is a compulsory CIS field. | Teaching and learning strategies |
| Content (topics): generic | CIS: CI, Subjects CIS: SO, Change Request tab | Indicate the subject content (topics) as a list of headings (topic names or numbers, e.g. 'Topic 1' or 'Management') with a sentence briefly describing the topic, or as a bulleted list. | Content (topics) |
| Field group: Program | It is highly recommended that these fields are filled in to give students as much information as possible to help them to plan their study. Subjects involving large numbers of students with different cohorts following different sequences of activities, can be covered in this table by having headings for each cohort in the 'Description' field and specifying what that cohort does that week/session, e.g. Group1 Lecture on Renal Anatomy Laboratory Group 2 Lecture on Renal Anatomy Tutorial For subjects where it is not appropriate to have a week-by-week/session-by-session table, e.g. in self-directed learning or project subjects, all fields in the table should be left blank. If it is required, instead add a single statement to the 'Content: additional' field. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Program | |
| Program: Week/session | CIS: SO, Program tab | The first column of the Program identifies the week/session described in that row (it is not required, but recommended). Add the session week number for weeks other than VC's week; and a '-' for VC's week. Where a subject has two sessions a week they can be labelled 1A and 1B. For block mode subjects the session number can be given, or the time span of the session (the date should be added in the 'Date' field, not here). Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Week/session |
| Program: Date | CIS: SO, Program tab | The second column of the Program allows the date to be specified. The autofill function can be used, or subject coordinators can manually enter the dates. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Date |
| Program: Description | CIS: SO, Program tab | This field (column 3) describes what the student will experience for this attendance session. It may be appropriate to have headings such as: Lecture; Laboratory; Tutorial; Pre-reading; References; etc., with text under each heading. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Description |
| Program: Notes | CIS: SO, Program tab | Coordinators can use this field (column 3 under 'Description') for the reading list, or for information about tutorials when the description field has been used for lecture descriptions. Assessment task submission dates should not be given here as they should have already been specified under each assessment task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Notes |
| Content: additional | CIS: CI, Subjects CIS: SO, Edit Main tab | The text entered in this field appears without a heading immediately below the Program table or below the heading if no data has been added to the table fields. It can be used, for example, to explain the division of material between the Description and Notes fields, to give a key to abbreviations used in the Program table, to explain why there is no Program table, or to refer students to further documentation. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Program (only appears if the Program table is blank) |
| Additional information for students | CIS: CI, Subjects CIS: SO, Edit Main tab | An entry in this field is not normally necessary and is discouraged given the array of specific information fields available. If required, provide details of any additional information for students that isn't covered by any of the other fields. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Additional information |
| Field trips | CIS: CI, Subjects CIS: SO, Edit Main tab | Outline details of field trips required as a component of this subject. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Field trips |
| Additional subject costs | CIS: CI, Subjects CIS: SO, Edit Main tab | Include a brief sentence about additional costs that students undertaking this subject incur, such as cost of field trips, materials, excursions, travel, accommodation, etc., e.g. Subject notes cost $20 (purchase number: CN12345) and are available from the UTS Union shop, level 3, building 1, City campus. Limit of 60 words (450 characters) Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Additional subject costs |
| Assessment: generic information | CIS: CI, Subjects CIS: SO, Edit Main tab | It is a requirement that subject outlines have a brief description of each assessment task, its percentage worth, and when it is due. The 'Assessment: generic information' field is provided so subject coordinators can use it to avoid repetition of information in the individual task entries that applies to all tasks, e.g. information on the means of submission or the penalty for late submission which may be the same for all tasks. There are also five other assessment-related fields that should be used for specific information that applies to all (relevant) assessment tasks. The five fields are: 'Plagiarism detection software', 'Moderation of marks', 'Assessment feedback', 'Examination material and equipment' and 'Supplementary assessments'. The requirement to have an entry in any of these five fields depends on the nature of the subject and its assessment regime. This field and the five other assessment-related fields should only be used where the arrangements for the subject are different from the default arrangements that apply to all subjects as described in the faculty generic information that is appended to the outline (in some faculties) or published as a faculty study guide (in others). A reference to this study guide should be part of each subject outline disclaimer (the 'Disclaimer' field is editable in CIS). The information in the 'Assessment: generic information' field should not cover topics that are covered by the five other assessment-related fields. Information should cover specific subject requirements on matters such as assignments, late penalties, provisions for student negotiation of assessment tasks, etc., that go beyond or are exceptions to the faculty-specific assessment information. This information should apply to all assessment tasks in the specific subject only. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Assessment |
| Field group: Assessment tasks | Each assessment task is made up of a number of fields. Subject coordinators can edit four of them ('Task', 'Length', 'Due date', 'Further information'). The other fields are approved at faculty board and subject coordinators cannot edit them (changes can be requested via the online workflow process, i.e. via the 'Change request' tab). | Assessment (only appears if 'Assessment: generic information' is blank) | |
| Assessment tasks: Display status checkbox | CIS: SO, Assessment Tasks tab / Manage tasks | The checkbox indicates which of the assessment tasks are included in the subject outline. This allows differences instances of a subject (e.g. default, block, short) to use a different set of assessment tasks. All assessment tasks are displayed on the 'Manage tasks' screen in every instance. Tasks can be ticked on or off depending on the instance. Weight validation occurs on the ticked on tasks, so ticked on tasks must total 100. | |
| Assessment tasks: Heading | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | Add the heading. Note: 'Assessment task #: ' will be automatically inserted before the heading on generation so only add the actual heading, e.g. 'Interactive photo-essay', which will be displayed as, for example, 'Assessment task 2: Interactive photo-essay'. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Assessment task #: [field data] |
| Assessment tasks: Intent | CIS: SO, Assessment Tasks tab CIS: SO, Change Request tab | Add the purpose of the assessment item. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Intent |
| Field group: Assessment tasks: Objectives | Data displayed under the 'Objectives' heading is automatically drawn from data held in the task's 'Criteria linkages' table (SLO and CILO columns) and the 'Assessment task SLO lead-in sentence' and 'Assessment task CILO lead-in sentence' | Objectives | |
| Assessment task SLO lead-in sentence | CIS: CI, Course Area | Displayed as a lead-in sentence above any subject learning objective (SLO) codes linked to in the criteria linkages table. The sentence is common across all subject outline PDFs within the course area, e.g. 'This assessment task addresses the following subject learning objectives:' If left blank, the SLO codes are displayed without a lead-in sentence. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | |
| Assessment task CILO lead-in sentence | CIS: CI, Course Area | Displayed as a lead-in sentence above any course intended learning outcome (CILO) codes linked to in the criteria linkages table. The sentence is common across all subject outline PDFs within the course area, e.g. 'This assessment task addresses the following course intended learning outcomes:' If left blank, the CILO codes are NOT displayed. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | |
| Assessment tasks: Type | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | What type of assessment is the task? Choose a type (i.e. 'Essay', 'Report', 'Exam', 'Test', etc.) from the drop-down list in the 'Type' column, if required. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Type |
| Assessment tasks: Groupwork | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | Does the assessment task involve groupwork? Choose 'Group', 'Individual', or 'Combined', etc., from the drop-down list in the 'Groupwork' column, if required. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Groupwork |
| Assessment tasks: Weight (%) | CIS: SO, Assessment Tasks tab / Manage tasks CIS: SO, Change Request tab | Add the weighting as a whole number, i.e. a percentage out of 100, e.g. '35'. Do not include the percentage symbol. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Weight |
| Assessment tasks: Task | CIS: SO, Assessment Tasks tab | In this field provide details about the nature of the assessment task. Students need to be given enough information so they can undertake the task. This can either be provided in this field, or a reference can be made to an ancillary document that contains the information. The information about the task given in the outline can be split between this field and the 'Further information' field. The 'Task' field should not contain information for which a specific field exists. Information about length and assessment criteria can be given here, provided these fields are blank, i.e. so information isn't duplicated in the subject outline. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Task |
| Assessment tasks: Length | CIS: SO, Assessment Tasks tab | Add the length of the assessment task, as applicable, e.g. '4000 words', '30 minutes', etc. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Length |
| Assessment tasks: Due date | CIS: SO, Assessment Tasks tab | Add the due date by choosing from a series of drop-down lists. Specify the due date type (i.e. 'Custom', 'Date', 'Date/Time', 'Week', 'Week range', 'In Class', 'Exam period', 'Progressive', 'Negotiated', 'Practicum period'); depending on your choice, you'll then be able to specify the date, time, week, etc., and/or add free text data. Ticking the checkbox beside 'See Further information', will add '; see Further information' to the data, e.g. if you choose 'Negotiated' and tick the checkbox, 'Negotiated; see Further information' will be displayed in the PDF. Any substantial further information about the due data can then be added to the 'Further information' field. Alternatively, you can use the 'Free text' field to add further information about the due date. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Due |
| Assessment tasks: Criteria | CIS: SO, Assessment Tasks tab CIS: SO, Change Request tab | If the criteria linkages table is not being used, the assessment criteria can instead be added to this field. Data is often presented as a bulleted list. If the criteria linkages table is being used, this field can be left blank or it can contain data that introduces/explains the criteria linkages table. If there is data in this field it will appear above the 'Criteria linkages' table (if any) in the subject outline PDF. It should therefore not duplicate data held in the criteria linkages table. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Criteria |
| Assessment tasks: Criteria linkages | CIS: SO, Assessment Tasks tab CIS: SO, Change Request tab | The criteria linkages table is where the assessment criteria is set up and then linked to the subject's SLOs and the parent study package's CILOs. Each assessment criterion is entered as a row in the criteria linkages table. There is no maximum number of assessment criteria per assessment task. The criteria linkages table comprises the following columns: 'Criteria', 'Weight (%)', 'SLOs', 'CILOs', 'Level', 'CR' (see the documentation for an explanation of what data is required). If the criteria linkages table is set for display, only the 'Criteria', 'Weight (%)', 'SLOs', and 'CILOs' columns are displayed. If there are linked CILOs in the criteria linkages table and there is a CILO lead-in sentence stored in Course Area, then the CILOs are displayed as a bulleted list with a lead-in sentence, after the SLOs under the 'Subject objectives' heading in the Subject Outline PDF. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. | Criteria linkages |
| Assessment tasks: Further information | CIS: SO, Assessment Tasks tab | This field can be left blank. If required, add any further information that applies to the assessment item, e.g. further information about the details of the due date, which is not covered in the other assessment task fields. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Further information |
| Use of plagiarism detection software | CIS: SO, Edit Main tab CIS: CI, Subjects | If plagiarism detection software is used, there should be a statement to that effect in the outline. It can either be made here to cover all relevant assessment tasks, or it can be made in the 'Further information' field of each relevant task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Use of plagiarism detection software |
| Moderation of marks | CIS: SO, Edit Main tab CIS: CI, Subjects | This field is provided to give subject coordinators a place to make a statement about mark moderation. It can be left blank. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Moderation of marks |
| Assessment feedback | CIS: SO, Edit Main tab CIS: CI, Subjects | Some information should be provided covering when feedback will be given and what form it will take. This field can be used if a generic statement is appropriate, otherwise the information can be provided in the 'Further information' field of each separate task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Assessment feedback |
| Examination material or equipment | CIS: CI, Subjects CIS: SO, Edit Main tab | Students need to be clear about what they are permitted to take into the examination room. This field can be used if a generic statement is appropriate, otherwise the information can be provided in the 'Further information' or 'Task' field of each separate task. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Examination material or equipment |
| Supplementary assessments | CIS: CI, Subjects CIS: SO, Edit Main tab | Use this field to make a statement about supplementary assessments or examinations. It can be left blank. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Supplementary assessments |
| Minimum requirements | CIS: CI, Subjects CIS: SO, Change Request tab | Provide details, covering all modes of attendance, of any minimum requirement to pass the subject, such as attendance, practicals, compulsory assessment items, etc. Note(s) • Subject coordinators can request changes via the 'Change Request' tab in SO (if the faculty uses the workflow function), or via the faculty's existing approval processes. • This is a compulsory CIS field. | Minimum requirements |
| Prize offered | CIS: CI, Subjects CIS: SO, Change Request tab | Indicate the prize(s) available, if any. | Prize offered |
| Field group: Texts and references | There a four fields available for specifying resources that students are either expected to use, or may find useful in undertaking the subject. These fields are: 'Required texts', 'Recommended texts', 'References' and 'Other resources'. At least one of the fields is required to have some content, unless all resource information is specified in the week-by-week 'Program' table in the outline. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | n/a | |
| Required texts | CIS: CI, Subjects CIS: SO, Edit Main tab | This field is for resources that students are expected to use. The resources may take the form of notes prepared by the coordinator, or text books that the student is expected to have access to, either by purchase or through the library. The data in this field is normally a short list of resources, each of which will be of value to students for a substantial part of the subject's coverage. Resources that are relevant to a very specific area of the subject are better placed in the 'References' field. Add the list of set texts and other learning resources required for the subject. Citations must be written using the referencing system preferred by your faculty, e.g. Hill, C, Maritime Law, 3rd edn, Lloyds, 1989 Australian Industrial Law Reports, loose-leaf, CCH Pearson, G & Fisher, S, Commercial Law Commentary and Materials, LBC Information Services, 1999 Van den Berg, J (ed.), Yearbook of Commercial Arbitration, Vol 1 & 2, Kluwer, 1976 Limit of 150 words (1,125 characters) Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Required texts |
| Recommended texts | CIS: CI, Subjects CIS: SO, Edit Main tab | This field is for resources that students may find useful but it is left to the student to decide. The data in this field is normally a short list of resources each of which are of value to students for a substantial part of the subject's coverage. Resources that are relevant to a very specific area of the subject are better placed in the 'References' field. List any recommended texts and other learning resources which students would benefit from buying, but which are available in the UTS: Library, via UTS: Online or as reading materials prepared by the subject coordinator. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Recommended texts |
| References | CIS: CI, Subjects CIS: SO, Edit Main tab | This field is used to list the resources that the student is either expected or may wish to access in order to achieve the subject aims in specific topics or to meet specific objectives. However, there are three acceptable fields in which to specify references: 1. They can be listed with full bibliographic information in this field. The advantage of this method is that a code or abbreviation can be used when specifying what references are to be used in specific weeks in the Program section of the outline. A key to the codes used can be given in the 'Content: additional' field. 2. The 'References' field can be left blank and instead full bibliographic details can be provided in the 'Description' field in the week/session of the Program where the materials will be used. 3. Where the reference list is very long, or there is an extensive array of readings for each week, it is acceptable in this field to refer to a separate document, such as a study guide, where full reference information is provided. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | References |
| Other resources | CIS: CI, Subjects CIS: SO, Edit Main tab | This field can be used in addition to, or instead of, the 'References' field. It is provided to enable the separate listing of text-based and other types of resources, as required. The guidelines for the 'References' field also apply to this field as well. Add the list or details of other resources available for the subject, e.g. websites, journals, library resources, etc. Note(s) • Can contain different data depending on the instance (e.g. default, block, distance, etc.) | Other resources |
| Statement on graduate attributes | CIS: CI, Course Area | Explain the faculty's approach to the development of graduate attributes. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement on graduate attributes |
| Assessment: faculty procedures and advice | CIS: CI, Course Area | Details of faculty/course-specific late submission penalties, policy on late submission/extension availability, special consideration, how and to whom students submit their assessment items, feedback processes, processes for collection and return of assessment items and the estimated date of return, referencing requirements. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Assessment: faculty procedures and advice |
| Academic integrity (faculty specific) | CIS: CI, Course Area | Details of faculty-specific academic integrity and plagiarism statements. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Academic integrity |
| Academic liaison officer contact details | CIS: CI, Course Area | Provide details in the following format, as required; each component optional. [Title][first name][surname] [Position] UTS: [xxxx] [Building ID location details] telephone (02) 9514 [xxxx] fax (02) 9514 [xxxx] email [xxxx]@uts.edu.au [Descriptive sentence about preferred means of contact.] For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Academic liaison officer |
| Support | CIS: CI, Course Area | Provide details of support available to students, such as UTS Library Liaison staff, learning skills programs (BELL, STAR, etc.), support staff, university services, student support centres, computer logins, passwords, etc. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Support |
| Statement about assessment procedures and advice | CIS: CI, Course Area | Standard University statement(s) on assessment to be inserted in all subject outlines as determined by the T+L committee. Includes a reference to the UTS Coursework Assessment Policy and Procedures Manual. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement about assessment procedures and advice |
| Statement on scholarly etiquette | CIS: CI, Course Area | Provides reference to the University's statement on scholarly etiquette. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement on scholarly etiquette |
| Statement on copyright | CIS: CI, Course Area | Provides reference to the University's statement on copyright, if required. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement on copyright |
| Statement on plagiarism | CIS: CI, Course Area | Provides reference to the University's statement on plagiarism. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement on plagiarism |
| Statement on intellectual property | CIS: CI, Course Area | Provides reference to the University's statement on intellectual property, if required. For use as a standard section in each subject outline. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement on intellectual property |
| Retention of student work | CIS: CI, Course Area | Faculties need to be able to retain student work for professional accreditation processes and for demonstrating actual outcomes as part of UTSGAP. As such, this field was created and a standard statement has been added to it (currently only in FEIT but to be added university wide once approval provided at next ADeans meeting), i.e. 'The University reserves the right to retain the original or one copy of any work executed and/or submitted by a student as part of the course including, but not limited to, drawings, models, designs, plans and specifications, essays, programs, reports and theses, for any of the purposes designated in Rule 3.9.2 (www.gsu.uts.edu.au/rules/student/section-3.html#r3.9). Such retention is not to affect any copyright or other intellectual property right that may exist in such student work. Copies of student work may be retained for a period of up to five years for course accreditation purposes. Students are advised to contact their subject coordinator if they do not consent to the University retaining a copy of their work.' This statement is now drawn into all generated FEIT subject outlines. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Retention of student work |
| Statement on UTS email account | CIS: CI, Course Area | At the Council meeting on 13 June 2012, Council approved changes to rule 2.3 Communication. Enrolled students are now required to use only their UTS email account to contact the University. As such, this field was created and a standard statement has been added to it, i.e. 'Email from the University to a student will only be sent to the student's UTS email address. Email sent from a student to the University must be sent from the student's UTS email address. University staff will not respond to email from any other email accounts for currently enrolled students.' This statement is now drawn into all generated subject outlines. Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Statement on UTS email account |
| Disclaimer (subject outline PDF) | CIS: CI, Course Area | Provides the course area-specific disclaimer used as a standard section in each subject outline, under the heading 'Disclaimer'. Can include information on the currency of the outline (e.g. 'This outline was generated on the date indicated in the footer. Minor changes may have been made subsequent to this date.') or details about the availability of other subject information (e.g. 'This outline serves as a supplement to the Faculty's Student Guide. On all matters not specifically covered in this outline, the requirements specified in the Student Guide apply.') Note(s) • Changes must go through the APO:CIS approval process before they can be published. | Disclaimer |