On completion of this unit, students will be able to:

1. understand basic Computer Structure and Operation and demonstrate use of the associated vocabulary.
2. demonstrate an understanding of the concepts of Data Representation, Computer Arithmetic and Boolean Algebra using appropriate methods of implementation.
3. demonstrate knowledge of Internal Bus, Memory, I/O organisations and interfacing standards.
4. describe the internal operation of the CPU and explain how it is used to execute instructions.
5. demonstrate an understanding of the basics of operating systems and system software.
6. identify factors that affect computer performance.

ASCED Discipline Group Classification: 031305 Computer Engineering.

FIT1001 Computer Systems will introduce students to basic computer hardware and operating systems software with emphasis on the concepts required to understand the low-level and internal operations of computer systems.

In particular, this includes study of data representation, simple digital logic, computer organisation including CPU, memory and input/output devices, as well as system software and operating system concepts. The intention is to provide opportunities for students to relate the hardware knowledge covered in this unit to the concepts learned in their introductory programming and systems analysis classes and to give a more complete understanding of how hardware and software are used to build systems.

This provides opportunities for students to relate the use of programming languages and studies of system design and project management to their implementation on computer hardware.

This unit will introduce students to basic computer hardware and operating systems software with emphasis on the concepts required to understand the low-level and internal operations of computer systems.

1. "Essentials of Computer Organization and Architecture" by Null and Lobur (2003). Jones and Bartlett.
2. "Structured Computer Organization" 5th Edition by Tanenbaum (2006). Pearson:Prentice-Hall.
3. "Computer Organization and Architecture: Designing for Performance" 7th Edition by Stallings (2006). Prentice-Hall.
4. "Systems Architecture" 5th Edition by Burd (2006). Thompson:CourseTechnology
5. "Operating System Concepts" 7th Edition by Silberschatz, Galvin and Gagne (2005). Wiley.

• Lectures
• Tutorials
• Unit also available in OCL mode, involving printed notes and/or on-line materials and internet based discussion groups.

Contact time for on-campus modes will be up to four hours per week. This will be divided into formal lectures and tutorials.

Lectures will be used to present concepts and the relationships between ideas, and so guide the student through a structured outline of the material derived from, but not necessarily identical to that provided by the text books and online resources. Tutorials will be used to link the theory with practice and enhance the students understanding.

Lectures and supporting examples, text references and resources will be used to address all learning objectives. OCL students will be provided with a study guide, tutorial material, and assignments.

Formal Assessment consisting of:

• Final Exam 3 hours duration worth 70%
• Class test 10%
• Tutorial tests 20%

OCL students will undertake the equivalent assessment of theory through an OCL examination process, with on-line submission of assignments.

The final exam and tests will assess understanding of all the learning objectives as presented in the lectures.

2 hours of lectures and 2 tutorial hour per week. On average, the workload is 8 hours per week.

On campus modes will require lecture rooms with data display and internet connection, with a PC and facility to plug in a laptop computer.

Tutorials will normally be scheduled in flexible learning spaces with access to data projectors, overhead projectors and discussion and group-work facilities (flexible desk arrangements, white boards).

None.

Special Interest Group (SIG) to monitor unit and prepare resources. One Lecturer for each campus offering per semester. A tutor per tutorial/practical session for each campus offering per semester. Equivalent requirements for summer semester offerings.

Adequate copies of the texts mentioned above.

Faculty of Information Technology

None.

There is no interfaculty involvement for common core units.

This is a faculty unit and the team responsible for its development has had representatives from all organizational units of the faculty.

ITS and Faculty IT support.

None.

Nil.

Ingrid Zukerman