Skip to the content | Change text size
PDF unit guide

FIT1008 Introduction to computer science - Semester 1, 2013

This unit introduces students to core problem-solving, analytical skills, and methodologies useful for developing flexible, robust, and maintainable software. In doing this it covers a range of conceptual levels, from high level algorithms and data-structures, down to abstract machine models and simple assembly language programming. Topics include data structures; algorithms; object-oriented design and programming; and abstract machines.

Mode of Delivery

Clayton (Day)

Contact Hours

3 hrs lectures/wk, 3 hrs laboratories/wk, 1 hr tutorial/wk

Workload requirements

Students will be expected to spend a total of 12 hours per week during semester on this unit as follows:

  • Lectures: 3 hours per week
  • Tutorial: 1 hour per week
  • Computer Lab Prac: 1.5 hours per week (requiring advance preparation) followed by an extra 1.5 hours for prac marking
  • a minimum of 5 hours of personal study per week in order to satisfy the reading, assignment expectations, including time for newsgroups/discussion groups.

Unit Relationships


CSE1303, CSC1030, FIT1007, FIT1015


(FIT1040 or FIT1002) and FIT1029

Chief Examiner

Campus Lecturer


Aldeida Aleti

Consultation hours: Tuesday 11am - 1pm, Room 133a, Building 63



Aldeida Aleti

Academic Overview

Learning Outcomes

At the completion of this unit, students will haveDeveloped the ability to:
  • understand abstract data types and, in particular, data structures for stacks, queues, lists, and trees, as well as their associated algorithms for creating and manipulating them. Evaluate the appropriateness of different data structures for a given problem;
  • understand basic searching and sorting algorithms and implement them. Understand the concept of algorithmic complexity. Analyse the complexity of these searching and sorting algorithms as well as other basic algorithms. Compare the complexity of different algorithms for solving a given problem;
  • analyse different implementations of abstract data types and determine their implications regarding complexity, functionality, and memory usage;
  • understand the uses of recursive algorithms and data structures, their advantages and disadvantages. Analyse the complexity of simple recursive algorithms, and their relationship with iteration. Understand basic recursive algorithms for lists and trees, and develop new ones;
  • understand the basic concepts in the object-oriented (OO) programming paradigm;
  • understand the basic concepts in testing;
  • understand the requirements for "good programming practice";
  • understand the different compilation targets, including abstract machine code, assembly language, object code, and machine code. Understand the relationship between simple code in a high level imperative language and its low level translation into assembly code;
  • learn the structure and design of a particular processor simulator. Analyse the execution in this simulator of simple iterative algorithms learned before, thus gaining a deeper understanding of the connection between software and hardware, between an algorithm and its execution;
  • understand how the simulator implements function calling, and use it to reinforce the connection between recursion and iteration.
Developed attitudes that enable them to:
  • conform to programming standards when writing software;
  • use good design principles when constructing systems;
  • take a patient and thorough approach to testing;
  • acknowledge any assistance they have received in writing a program;
  • search for information in appropriate places when necessary.
Developed the skills to:
  • implement their own data-structures. Design and implement Java programs using a variety of data structures and algorithms;
  • implement an object-oriented program consisting of several interacting classes requiring not only basic but also advance object-oriented concepts;
  • construct a test harness for testing an object-oriented program;
  • debug and modify an existing program (written by somebody else);
  • use the Java API classes as part of their programs.
Demonstrated the communication skills necessary to:
  • document a program correctly;
  • explain how parts of a program work.

Unit Schedule

Week Activities Assessment
0 Register for tutorials, pracs and lectures No formal assessment or activities are undertaken in week 0
1 Lectures on Revision of BigO and List (arrays). Tute & Prac. Prac 1
2 Lectures on List Sorting & Stacks and Queues (arrays). Tute & Prac. Prac 2
3 Lectures on Lists, Stacks and Queues (linked nodes). Tute & Prac Prac 3
4 Lectures on Basic Object Oriented Programming. Tute & Prac. Prac 4
5 Lectures on Advanced Object Oriented Programming. Tute & Prac. Prac 5
6 Lectures on Recursion and Recursive Sorts. Tute & Prac. Prac 6
7 Lectures on Binary Trees. Tute & Mid-semester Test. No Prac. Mid-semester Test in Tuesday lecture
8 Lectures on Priority Queues and Heaps. Tute & Prac. Prac 7
9 Lectures on Hash Tables & Number Representation. Tute & Prac. Prac 8
10 Lectures on Computer Systems & MIPS. Tute & Prac Prac 9
11 Lectures on MIPS execution of selection and iteration. Tute & Prac. Prac 10
12 Lectures on MIPS function call/return. Tute & Prac Prac 11
  SWOT VAC No formal assessment is undertaken in SWOT VAC
  Examination period LINK to Assessment Policy:

*Unit Schedule details will be maintained and communicated to you via your learning system.

Assessment Summary

Examination (3 hours): 70%; In-semester assessment: 30%

Assessment Task Value Due Date
Mid-semester Test (1 hour) 10% Week 7 in Tuesday lecture
Pracs (1.5 hours each) 20% Weekly except in Week 7
Examination 1 70% To be advised

Teaching Approach

Lecture and tutorials or problem classes
This teaching and learning approach helps students first encounter the information at lectures, discuss and explore them at length during tutorials, and practice them in a hands-on environment during labs.

Assessment Requirements

Assessment Policy

Faculty Policy - Unit Assessment Hurdles (

Academic Integrity - Please see the Demystifying Citing and Referencing tutorial at

Assessment Tasks

Hurdle Requirements

There are four hurdles in this unit:

  • First, students must actively participate in at least 7 out of 12 tutorials. Active participation includes contributing opinions to a discussion, providing an answer to some question/exercise, or posing a unit-related question.
  • Second, students must achieve at least 50% of the total prac marks.
  • Third, students must achieve at least 50% of the exam mark. 
  • Fourth, students must achieve at least 50% of the total marks.

Students who do not meet all these hurdles can get a maximum of 49N for the unit.


Students must actively participate in at least 7 out of the 12 tutorials. Active participation includes contributing opinions to a discussion, providing an answer to some question/exercise, or posing a unit-related question.

  • Assessment task 1
    Mid-semester Test (1 hour)
    This test is performed during the class and covers exam-like questions for the first part of the course. It is intended to give students an idea of how they would perform in the final exam, given their current progress. 
    Criteria for assessment:

    This test will evaluate your understanding of the material provided during the first few weeks of semester, your capability to code simple algorithms given a clear specification, and to analyse the behaviour and complexity of simple fragments of code.

    Due date:
    Week 7 in Tuesday lecture
  • Assessment task 2
    Pracs (1.5 hours each)
    Each week you will need to complete a prac assignment. In some of the pracs, you will need to work together with another student, but will you will be marked individually. Prac assignments are long (they are designed to take about 4 hours). This means that you must have a significant proportion of the prac completed before attending the scheduled computer lab. The aim of the 1.5 hour computer lab practical is to iron out any bugs, ask any questions about the prac you have not been able to solve on your own, and improve the parts that your demonstrator points out as lacking (including comments, algorithms, etc). If you do nothing before the 1.5 hours scheduled,  you will soon realise that you do not have enough time to complete it. The prac sheets will be released every Thursday morning and made available on the unit's web page.
    Criteria for assessment:
    Every prac sheet contains the assessment criteria used to assess that prac. In addition, demonstrators carry with them a marking guide prepared by the lecturer which indicates how exactly to mark each prac question. You can request the demonstrator to show you the marking guide after he/she has marked your prac.
    Due date:
    Weekly except in Week 7


  • Examination 1
    3 hours
    Type (open/closed book):
    Closed book
    Electronic devices allowed in the exam:

Learning resources

Reading list

(1) Data Structures and Algorithms in Java. Robert Lafore, SAMS. This book provides a very simple approach to understanding data structures and algorithms. While the book uses Java to illustrate the implementation, its focus is on the actual data structures and algorithms, rather than on Java, which is very useful for first year students. Very basic and simple.

(2) Data Structures and Algorithms in Java. Adam Drozdek, Brooks/Cole. More advanced but still appropriate for average and high-end students.

(3) Algorithms in Java. Robert Sedgewick. Parts 1-4. This book is a more in-depth book and assumes a strong mathematical background from the reader. It is recommended for advanced students who want to learn more about the complexity of the algorithms and data structures used.

(4) Data Structures and Algorithm Analysis in Java. Third Edition. Mark Allen Weiss. This is one of the books you will also use in FIT2004. It contains very clear discussions of the algorithms and data-structures, but it assumes knowledge of a difficult Java construct (Generics). Very recommended if you can get pass that.

(5) The Java Programming Language. Fourth Edition. Ken Arnold, James Gosling and David Holmes. Prentice Hall. This book is useful for students who have questions about the Java language. The reason for using the fourth edition is because it is the earliest edition that includes parametric polymorphism (called Generics in Java).

Monash Library Unit Reading List

Feedback to you

Types of feedback you can expect to receive in this unit are:
  • Informal feedback on progress in labs/tutes
  • Graded assignments without comments
  • Test results and feedback
  • Other: Detailed solutions to tutes

Extensions and penalties

Returning assignments

Assignment submission

It is a University requirement ( for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz).

Online submission

Please submit your work via Moodle at the time in which you are marked (and, thus, before you leave the lab). You can access Moodle via links in the portal.

Required Resources

Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.

Eclipse Platform. One of the two recommended platforms. It can be downloaded from

NetBeans IDE. The other recommended platform. It can be downloaded fro

Java Development Kit, Version j2sdk-1_5_0_06 or later, Sun Microsystems, Inc. You should download the freeware version as you will have no need for the fuller facilities provided in JCreatorPro, and would have to pay as well.

The MIPS R2000 simulator SPIM S20 (with its new interface QtSpim).

All the above are included as part of the Standard Operating Environment used in Faculty Computer Labs.

Other Information


Graduate Attributes Policy

Student services

Monash University Library

Disability Liaison Unit

Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis.

Your feedback to Us

Previous Student Evaluations of this Unit

As a result of student feedback quizzes have been added to each week to help students practice the concepts being taught.

If you wish to view how previous students rated this unit, please go to