COMP SCI 2005 - Systems Programming

North Terrace Campus - Semester 1 - 2017

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, debuging tools. Basic shell scripting. Build tools. Signal and handling, synchronous and asynchronous I/O. Introduction to threads and concurrency. Timers and their uses.

  • General Course Information
    Course Details
    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 1009, COMP SCI 1007, COMP SCI 1102, COMP SCI 1202, or COMP SCI 2202
    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, debuging tools. Basic shell scripting. Build tools. Signal and handling, synchronous and asynchronous I/O. Introduction to threads and concurrency. Timers and their uses.
    Course Staff

    Course Coordinator: Dr Sergey Polyakovskiy

    Co-lecturer: Dr. Rui Zhou
    Course Timetable

    The full timetable of all activities for this course can be accessed from Course Planner.

  • Learning Outcomes
    Course Learning Outcomes
    On 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
    1,3,7
  • Learning Resources
    Required Resources
    There 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 Resources
    You 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.

    Recommended textbooks:
    - 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)
    Online Learning
    You can find the general information about this course at https://myuni.adelaide.edu.au/courses/24065/. Specific information about previous years' offerings can be found at www.cs.adelaide.edu.au/~second/spc.
    at www.cs.adelaide.edu.au/~second/spc
  • Learning & Teaching Activities
    Learning & Teaching Modes
    The 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.
    Workload

    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 Summary
    There is an approximate schedule of the topics that will be covered on the course website.

  • Assessment

    The University's policy on Assessment for Coursework Programs is based on the following four principles:

    1. Assessment must encourage and reinforce learning.
    2. Assessment must enable robust and fair judgements about student performance.
    3. Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
    4. Assessment must maintain academic standards.

    Assessment Summary
    The assessment will comprise two parts:
    - Written examination, worth 60%;
    - Three assignments, worth 40%.


    Assessment Related Requirements
    To 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 Detail
    All 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.
    Submission

    No information currently available.

    Course Grading

    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.

  • Student Feedback

    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:
    www.cs.adelaide.du.au/~second/spc
  • Student Support
  • Policies & Guidelines
  • Fraud Awareness

    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.