|
|
Topics Covered
Programming in C++, language features
& pitfalls, computer components, object-oriented programming,
pointers, parameter passing, scope, recursion, void functions, classes,
type conversion, arrays & strings, multidimensional arrays,
streams, standard libraries, matrix operations.
|
|
Course Profiles
See links in "In This Section" .
Tutors:
- Mr. Patrick Ross
- Mr. Florian Guldenfels
- Mr. Jeremy Herbert
- Mr. Elliot Smith
Class Website
The website URL is http://www.itee.uq.edu.au/~comp2304 and is maintained
by course coordinator.
Please email
comp2304@itee.uq.edu.au to
contact the course coordinator and tutors.
Noticeboard
It is expected that students will read notices posted to the class
noticeboard within 48 hours. Some notices may be cross-posted to the
newsgroup as a courtesy, but the noticeboard is the canonical site for
official announcements.
Discussion Group
If you wish to discuss assignments, assessment, and other issues
related to this subject, please post to the class discussion group uq.itee.comp2304.
Subversion Interface
Students are expected to maintain all their assignment code in a central
Subversion repository
using TortoiseSVN.
Use of the subversion repository to store and develop the assignment programming solutions is good
programming practice and is mandatory. The code must be checked
into the repository regularly to show evidence of original work and
steady progress in coding. Typically code will be checked in to the
repository at least weekly increasing to several times a day towards
submission. This can easily be done from all ITEE laboratory machines as
well as home machines through the use of the free SVN client software.
Submitted code must be checked into the repository before uploading to
the assignment submission server. Code that is not checked into the
subversion server will be deemed not to exist as far as this
course is concerned.
Plagiarism
All submitted code will be checked by
MOSS antiplagiarism software to detect unreasonable copying and
collaboration on assignments. The subversion respository will be
examined to determine whether students have worked independently and
have made steady individual coding progress. If there is no code or no
evidence of steady coding progress in the repository and an assignment
is excessively similar to another students, this information will be
used as evidence for misconduct proceedings.
Assignment Submission
Electronic submission will be used
Student Marks
Marks for individual parts of the assessment by student number will be posted as
they are entered. Students who have a problem with their assigned marks,
especially apparently unfair computer-based marking or missing marks, must lodge
an appeal within one week of posting. Once the appeals have been considered and
marks adjusted, no more appeals will be considered, but students may be provided
with the option of resubmission.
Appeals Process
Assignments in this course will be marked using an automated marking system. This ensures that marking can be performed quickly, accurately and fairly. The process used also forms an important introduction into automated testing procedures, as used in industry.
It is the responsibility of each student to check their results in a timely fashion, and notify the tutors using the if they believe that there has been an error in the marking of their submission.
In some cases, small errors in your submission (i.e. a missing semicolon) may result in a low (or no) mark. Unfortunately, programming is a precise dicipline, and such cases will not be grounds for appeal. Please ensure that you thoroughly test your assignment before submission to avoid these cases.
|
Timetable
(Note there are no practical sessions P1-P4 in Week 1) |
|
|
|
|
|
|
