COMP SCI 2000 - Computer Systems

North Terrace Campus - Semester 1 - 2014

Information storage representation, Memory organisation and hierarchy, Processor fundamentals, assembler programming, assembler operation, subroutine calling mechanisms, linking/loading, Input-output and device controllers requirements for supporting an operating system and device drivers.

  • General Course Information
    Course Details
    Course Code COMP SCI 2000
    Course Computer Systems
    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
    Prerequisites One of COMP SCI 1007, COMP SCI 1009, COMP SCI 1103, COMP SCI 1203, COMP SCI 2103 or COMP SCI 2202
    Assumed Knowledge MATHS1012 or MATHS 1008
    Course Description Information storage representation, Memory organisation and hierarchy, Processor fundamentals, assembler programming, assembler operation, subroutine calling mechanisms, linking/loading, Input-output and device controllers requirements for supporting an operating system and device drivers.
    Course Staff

    Course Coordinator: Mr David Knight

    Course Timetable

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

  • Learning Outcomes
    Course Learning Outcomes
    Upon completion of this course you will be able to:
    1. Explain how different types of information are stored as numbers in computer memory;
    2. Explain how a computer executes a program;
    3. Translate simple programs written in a high-level language into equivalent machine instructions;
    4. Explain what information is stored in object-files;
    5. Explain how Input/output operations  are implemented, and describe some basic I/O devices; and
    6. Explain the operation of basic software tools, including an assembler, locator, and linker.
    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)
    Knowledge and understanding of the content and techniques of a chosen discipline at advanced levels that are internationally recognised. 1,2,3,4,5,6
    The ability to locate, analyse, evaluate and synthesise information from a wide variety of sources in a planned and timely manner. 3,4,5,6
    An ability to apply effective, creative and innovative solutions, both independently and cooperatively, to current and future problems. 3,4,5,6
    Skills of a high order in interpersonal understanding, teamwork and communication. 1,2,3,4,5,6
    A proficiency in the appropriate use of contemporary technologies. 2,5,6
  • Learning Resources
    Required Resources
    There is no required textbook. Comprehensive lecture notes (300+ pages) are available online from the course website as a PDF file. Printed copies can be purchased at the Image and Copy Centre (Level 1, Hughes building), for about $25.

    All software tools will be accessible via the course website, which can be found here:
    www.cs.adelaide.edu.au/~second/cs

    Online Learning
    There is an online forum, managed by Moodle, which can be found here:
    http://forums.cs.adelaide.edu.au/course/view.php?name=14s1-cs

    We will use the forum to announce any changes to the course, exercises, or tutorials.
    You are therefore strongly advised to read all mail that comes from this source — do not ignore it!

  • Learning & Teaching Activities
    Learning & Teaching Modes
    The course will be taught using a variation of team-based learning, with lecture/demonstration sessions interspersed with quiz/question time sessions.

    There will also be regular tutorial classes, and thee practical programming exercises.

    You are expected to read the course notes before and after each lecture, and to actively participate in class activities.

    To get the most out of the tutorial sessions you should attempt the questions before the session --- there is often not time to do all questions.

    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 as lecture preparation.
    You will need to allocate 2-5 hours per week to work on the assignment work.

    Learning Activities Summary
    There is an approximate schedule of the topics that will be covered on the course website.
    The exact timing will depend on the times of public holidays and quizzes.

  • 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 three parts:
    • In class quizzes (8%)
    • Three programming exercises (5%+10%+7%); and
    • A final exam (70%).
    Assessment Related Requirements
    To pass the course you must:
    • Score at least 40% for the final exam; AND
    • Score at least 40% for the practical exercises; AND
    • Score at leat 50% overall.
    If you fail to achieve eitehr of the 40% requirements, you mark will be capped at 44f (a fail).

    Assessment Detail
    All practical assignments requre you to write programs, which will be marked by an automatic testing script.
    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 you own.

    Submission
    All practical assignments must be submitted using the School of Computer Science online Submission System.
    Details are included in each assignment description on the course website.

    If you hand in your work late, your mark may be capped, based on how many days late it is, as follows:
    1 day late — mark capped at 75%
    2-3 days late — mark capped at 50%
    4-5 days late — mark capped at 25%
    More than 5 days late — no marks available.

    We expect to be able to return final marks of each exercise within two weeks after
    the exercise late deadline.

    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/cs


  • 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.