COMP SCI 2000 - Computer Systems

North Terrace Campus - Semester 1 - 2016

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 weeks
    Available for Study Abroad and Exchange Y
    Prerequisites One of COMP SCI 1007, COMP SCI 1009, COMP SCI 1102, COMP SCI 1202 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: Dr Bradley Alexander

    Lecturers: Fred Brown and Brad Alexander
    Tutor: Daniel Lawson
    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. Demonstrate an understanding of the layered and modular nature of computer systems.
    2. Design the core components of a computer from basic components.
    3. Understand and Apply knowledge of how computers represent programs and data.
    4. Explain how a computer executes a program.
    5. Write assembler and machine code.
    6. Understand the translation process from higher level representations into machine language
    7. Explain how Input/output operations  are implemented, and describe some basic I/O devices
    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
    2,3,5
    Career and leadership readiness
    • technology savvy
    • professional and, where relevant, fully accredited
    • forward thinking and well informed
    • tested and validated by work based experiences
    1-7
    Self-awareness and emotional intelligence
    • a capacity for self-reflection and a willingness to engage in self-appraisal
    • open to objective and constructive feedback from supervisors and peers
    • able to negotiate difficult social situations, defuse conflict and engage positively in purposeful debate
    2,3,5
  • Learning Resources
    Required Resources
    The textbook for the course is: The Elements of Computing Systems, by Noam Nisan and Shimon Shocken, MIT Press, 2008, ISBN13-978-0-262-64068-8.

    It is highly recommended that you buy this book. It is available in soft cover form and available electronically as an e-book.

    The first six chapters of are on the Nand2Tetris website used by the course but we will be using materials in chapters beyond this.

    Online Learning

    The course website can be found here:

            https://forums.cs.adelaide.edu.au

    We will use this to announce all changes to the course, assignments, and workshops. 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

    There will also be weekly workshop classes, and four practical programming exercises.

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

    To get the most out of the workshop sessions you must attempt the questions before the session --- there is often not time to do all questions in these sessions and assume you have already done your solutions. 

    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 scheduled 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 and tutorial work.

    Learning Activities Summary
    There is an approximate schedule of the topics that will be covered on the course website (see forums.cs.adelaide.edu.au to locate the online content of the course). 

    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 four parts:
    • Exam (50%)  (CBOK areas* abstraction, design, hardware and software, data and information, and programming)
    • Four Assignments (30%) (CBOK areas* abstraction, design, hardware and software, data and information, and programming)
    • Ten Quizzes (10%) (CBOK areas* design, hardware and software)
    • 12 Workshops - attendence and participation (10% total) (CBOK areas* abstraction, design, hardware and software, data and information, and programming)
    *For the CBOK See: http://www.acs.org.au/__data/assets/pdf_file/0007/7792/The-ICT-Profession-Body-of-Knowledge.pdf
    Assessment Related Requirements
    To pass the course you must:
    • Score at least 40% for the final exam
    • score at least 50% overall.
    If you fail to achieve the 40% requirement, you mark will be capped at 44F (a fail).

    Assessment Detail
    The written exam is held in the end-of-semester exam period. The exam will test your understanding of the assignment, tutorial and lecture material.

    All practical assignments requre you to write programs, which will be partly marked by an automatic testing script.
    You are strongly encouraged to begin the exercises early, to allow time for seeking help when needed. In all practical assignments you will be required to submit a pdf of a log-book/journal that you maintain during your development of your solution to the assignment. This log-book is a vital part of your assessment - a lack of a log-book with a narrative of your development process will result in a mark of zero for the assignment. The log-book and journal is composed by adding entries for the assignment in the web submission system. For full marks for your logbook you are expected to have entries spanning the time before the handin for the assignment. 

    Assignment details:

    Assignment 1 - Due end of Week 3  - Hardware Introduction 7.5%
    Assignment 2 - Due during Week 5  - Sequential Logic  7.5%
    Assignment 3 - Due end of Week 9 - Assembler Implementation  7.5%
    Assignment 4 - Due end of Week 13 - Compilation/Parsing 7.5%


    The workshops will 0.83% each. Marks will be a combination of preparation and participation. You will be expected to write notes in preparation and during these workshops. 

    There will be 10 quizzes (primarily online) held during the semester.

    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.

    Tutorial submissions will be submitted via the Course's moodle forum.


    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.