|
|
School
of Computer Science & Software Engineering
|
Unit Details 2009
Introduction to Graphics (CITS2231)
Outcomes: Students gain technical competence in graphics and are able to apply basic knowledge of graphics systems, graphical techniques and rendering. They become familiar with developing interactive graphics programs using the OpenGL API and C language. Students develop skills in the identification formulation and solution of problems and demonstrate a systems approach in the development of software.
Content: This unit teaches the concepts of graphics programming through development of interactive programs. The ideas presented are further developed with laboratory exercises. Initially, the unit focuses on the OpenGL API and C programming language. Students learn to write interactive programs using OpenGL and GLUT. The unit then covers the basics of lighting, shading, geometric transformations and interactive techniques for developing more complex graphics programs.
Assessment: This consists of one project and a final examination. The project involves problem identification, formulation and solution. Students must demonstrate a systems approach to design and operational performance. The examination tests in-depth technical competence in graphics, and the ability to apply basic fundamentals.
Prerequisites: Java Programming CITS1200 or C Programming CITS 1210.
With regards to formal contact hours, you will be required to attend all lectures and one laboratory per week.
|
Type |
Time |
Day |
Location |
|
Lecture |
11-11:45 |
Tue |
Blakers LT |
|
Lecture |
11-11.45 |
Thu |
Blakers LT |
|
Lab |
2-3:30 |
Wed |
CSSE 2.05 |
|
Lab |
3:30-5:00 |
Wed |
CSSE 2.05 |
|
Lecturer/Coordinator |
Rowan Davies, rowan@csse.uwa.edu.au |
|
Office |
CSSE 2.16 |
|
Lecturer |
Ajmal Mian, ajmal@csse.uwa.edu.au |
|
Office |
CSSE 1.12 |
Please use this web forum for questions and discussions related to this unit. Staff will read and answer questions at least twice a week, but please do contribute your own answers also.
It is recommended that you subscribe to receive the help forum by email or RSS.
The assessment scheme this year consists of a programming project
and a final examination held in November.
|
Assessment |
% of final mark |
Assessment Dates |
|
Project |
40 |
Due week 13 |
|
Examination |
60 |
November Exam Period |
All work submitted for assessment must be the individual students own work. Any instance of plagiarism will be brought to the attention of the School Disciplinary Board and dealt with under the School's and Faculty's plagiarism policies.
Interactive Computer Graphics : A Top-Down Approach Using OpenGL, by, Edward Angel, Fifth Edition, 2009, Addison-Wesley. ISBN : 9780321549433
(Older editions should be fine also, at least back to the third edition.)
The expected set of topics is the following. There may be some minor changes.
Plagiarism is broadly defined to be when any portion of the work presented for assessment, can be attributed to another party. The student making the submission should acknowledge what aspects of the presented work are not directly derived by them. For the purposes of plagiarism it is irrelevant that you have been given permission by someone to copy their work and present it as your own.
You are directed to the School’s Policy on
Plagiarism.
School
of Computer Science Policy on Plagiarism
Introduction to
Graphics CITS2231 Homepage
School of Computer Science and Software
Engineering Homepage
This information is correct as at 21-July-2009, but is subject to change
from time to time. In particular, The University reserves the right to change
the content and/or method of presentation and/or the method of assessment
of any unit of study, to withdraw any unit of study or programme, and/or to
vary arrangements for any programme.
Last updated:21-July-2009.