COMP SCI 2005 - Systems Programming
North Terrace Campus - Semester 1 - 2019
General Course Information
Course Code COMP SCI 2005 Course Systems Programming Coordinating Unit School of Computer Science Term Semester 1 Level Undergraduate Location/s North Terrace Campus Units 3 Contact Up to 2.5 hours per week Available for Study Abroad and Exchange Y Prerequisites One of COMP SCI 1007, COMP SCI 1009, COMP SCI 1102, COMP SCI 1202, COMP SCI 2202 or COMP SCI 2202B Course Description Introduction to C for C++ programmers. UNIX tools; design philosophy, command line options, combining programs using pipes and I/O redirection. File systems and memory. Profiling tools, binary tools, debugging tools. Basic shell scripting. Build tools. Signal and handling, synchronous and asynchronous I/O. Introduction to threads and concurrency. Timers and their uses.
Course Coordinator: Dr Anthony Dick
The full timetable of all activities for this course can be accessed from Course Planner.
Course Learning OutcomesOn successful completion of this course students will be able to:
1 Write and debug programs in the C programming language; 2 Explain how the Unix command shell processes commands; 3 Write simple shell scripts; 4 Explain how the Unix file system stores information; 5 Explain how concurrent processes are used in Unix; 6 Explain how asynchronous I/O and signals operate; 7 Apply the above knowedge to solve programming problems.
University Graduate Attributes
This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:
University Graduate Attribute Course Learning Outcome(s) Deep discipline knowledge
- informed and infused by cutting edge research, scaffolded throughout their program of studies
- acquired from personal interaction with research active educators, from year 1
- accredited or validated against national or international standards (for relevant programs)
1-7 Critical thinking and problem solving
- steeped in research methods and rigor
- based on empirical evidence and the scientific approach to knowledge development
- demonstrated through appropriate and relevant assessment
Required ResourcesThere is no required text-book. Each lecture will be recorded, and any examples used during the lecture will be made available on-line afterwards. We will attempt to provide updated formal notes shortly after each lecture.
Recommended ResourcesYou can perform all the exercise work required for the course in the University computer Labs. However, if you want to be able to work at home, you could consider installing Linux on your system. Unfortunately,the school cannot offer assistance or advice in doing this.
- Shells by Example : 4th Edition (By EllieQuigley)
- Bash Guide for Beginners. (By Machtelt Garrels)
- Advanced Bash Scripting Guide. (By Mendel Cooper)
- Tutorial: programming in C, UNIX system calls and subroutines using C. (By A. D. Marshall)
Learning & Teaching Activities
Learning & Teaching ModesThe course will be taught with lecture/demonstration sessions interspersed with quiz/question time sessions. There will also be tutorial classes, and practical exercises.
You are expected to attend the lectures and take part in the activities, and attempt tutorial questions before the scheduled tutorial session.
The information below is provided as a guide to assist students in engaging appropriately with the course requirements.You are expected to attend all scheduled classes.
In addition to the schedule contact hours, you are expected to spend an additional 1-2 hours per week after each lecture to consolidate your understanding of it.
You will need to allocate up to 5 hours per week to work on the assignments and tutorials.
Learning Activities SummaryThere is an approximate schedule of the topics that will be covered on the course website.
The University's policy on Assessment for Coursework Programs is based on the following four principles:
- Assessment must encourage and reinforce learning.
- Assessment must enable robust and fair judgements about student performance.
- Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
- Assessment must maintain academic standards.
Assessment Task Weighting (%) Individual/ Group Formative/ Summative Due (week)* Hurdle criteria Learning outcomes CBOK Alignment** Assignment Practical 1 10 Individual Summative Week 4 1. 2. 3. 4. 5. 6. 7. 1.1 1.2 4.1 4.3 Assignmant Practical 2 15 Individual Summative Week 8 1. 2. 3. 4. 5. 6. 7. 1.1 1.2 4.1 4.3 Assignmant Practical 3 15 Individual Summative Week 12 1. 2. 3. 4. 5. 6. 7. 1.1 1.2 4.1 4.3 Workshop participation 5 Individual Formative 1.1 1.2 Written Examination 55 Individual Summative min 40% 1. 2. 3. 4. 5. 6. 1.1 1.2 4.1 Total 100
This assessment breakdown complies with the University's Assessment for Coursework Programs Policy.
This course has a hurdle requirement. Meeting the specified hurdle criteria is a requirement for passing the course.
**CBOK is the Core Body of Knowledge for ICT Professionals defined by the Australian Computer Society. The alignment in the table above corresponds with the following CBOK Areas:
1. Problem Solving1.1 Abstraction1.2 Design
2. Professional Knowledge2.1 Ethics2.2 Professional expectations2.3 Teamwork concepts & issues2.4 Interpersonal communications2.5 Societal issues2.6 Understanding of ICT profession
3. Technology resources3.1 Hardware & Software3.2 Data & information3.3 Networking
4. Technology Building4.1 Programming4.2 Human factors4.3 Systems development4.4 Systems acquisition
5. ICT Management5.1 IT governance & organisational5.2 IT project management5.3 Service management5.4 Security management
Assessment Related RequirementsTo pass the course you must achieve:
- at least 40% in the exam, and
- 50% overall to pass the course.
If your mark for the exam is less than 40% your final mark will be capped at 44F.
Assessment DetailAll practical assignments requre you to write programs, which will be marked either by an automatic testing script or manually.
You are strongly encouraged to begin the exercises early, to allow time for seeking help when needed.
You will find that the test scripts are very good at finding bugs in your programs.
However, the test scripts do not tell you exactly what was being tested --- they just offer a general hint of where you should look.
If you submit your exercise at the last minute, and hope to use the automated test script to help you debug your program, you will be seriously disappointed, and will probably end up submitting late.
You should build your program in small stages, and test it thoroughly.
The testing regime is like this because, as a programmer, you must learn how to test your own programs.
Once you graduate, there will be no automatic tester available --- you will need to write your own.
You are expected to participate in each workshop session. This will involve bringing along answers in preparation and filling in worksheet answers from this preparation. If you have not prepared adequately for your workshop sessions and have not been able to properly address the questions in the worksheets then you will not get the marks for the workshops!
SubmissionDetails of assignment submission will be on the MyUni course pages.
Practical assignments will primarily use the School's web submission system.
Grades for your performance in this course will be awarded in accordance with the following scheme:
M10 (Coursework Mark Scheme) Grade Mark Description FNS Fail No Submission F 1-49 Fail P 50-64 Pass C 65-74 Credit D 75-84 Distinction HD 85-100 High Distinction CN Continuing NFE No Formal Examination RP Result Pending
Further details of the grades/results can be obtained from Examinations.
Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.
Final results for this course will be made available through Access Adelaide.
The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.
SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.You can find the latest SELT survey results on the course website, here:
- Academic Support with Maths
- Academic Support with writing and speaking skills
- Student Life Counselling Support - Personal counselling for issues affecting study
- International Student Support
- AUU Student Care - Advocacy, confidential counselling, welfare support and advice
- Students with a Disability - Alternative academic arrangements
- Reasonable Adjustments to Teaching & Assessment for Students with a Disability Policy
- LinkedIn Learning
Policies & Guidelines
This section contains links to relevant assessment-related policies and guidelines - all university policies.
- Academic Credit Arrangement Policy
- Academic Honesty Policy
- Academic Progress by Coursework Students Policy
- Assessment for Coursework Programs
- Copyright Compliance Policy
- Coursework Academic Programs Policy
- Elder Conservatorium of Music Noise Management Plan
- Intellectual Property Policy
- IT Acceptable Use and Security Policy
- Modified Arrangements for Coursework Assessment
- Student Experience of Learning and Teaching Policy
- Student Grievance Resolution Process
Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.
The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.