成人大片

1. Design object oriented solutions for small systems involving multiple objects.
2. Implement solutions in C++.
3. Test and debug C++ implementations.
4. Effectively use version control for incremental development.
5. Explain the benefits of object oriented design and the types of systems in which it is an appropriate methodology.
6. Identify the relative merits of different algorithmic designs.
7. Apply good programming style and understand the impact of style on developing and maintaining programs. Be able to justify programming style choices.
8. Independently find and interpret discipline related documentation.
9. Manipulate binary patterns and understand the use of binary to represent numbers.
10. Explain the steps in creating an executable program for a computer, including the intermediate representations and their purpose.

The course website provides links to a number of online resources to assist students in learning programming in C and C++. For those students who would also like to have a text book, we would recommend the following:

"Problem Solving with C++", 9e Global Edition, Walter Savitch, ISBN-13:9781292018249, Addison-Wesley, 2015.

Links to the online learning environment are available from

Links to all course materials, assignment descriptions, announcements, etc. are available from the online learning environment. It is your responsibility to regularly check for notices and to participate in online activities. This course does not use myuni.

This course has four contact activities: lectures, workshops, practicals and small group discovery. Each of these activities is used to support and build on each other, they do not repeat material.

Lectures will be used primarily for discussion of common problems identified in other activities, theory and the rationale for programming design and implementation concepts. The lectures aim to be interactive and may involve whole class activities.

Workshops will focus on exploration of computer science tools and concepts. The workshops are hands on collaborative sessions with groups of students sharing computers and working towards solutions to the presented problems. Workshop supervisors are there to guide you in your exploration, but students are expected to attempt to find information and solutions, with the supervisors providing guidance if difficulties arise and to lead the class discussions.

Practical Sessions will focus on encoding in C++ solutions to problems. These sessions are primarily aimed at addressing problems or questions, giving feedback and marking off work. Most of your programming implementation time should be outside of these sessions, and you should come to these sessions with your work mostly completed. Practical sessions will also be used for practical examinations.

The small group discovery sessions are divided into two parts. The even week sessions take the form of traditional tutorials that are the main activity where discussions will strengthen your understanding of the key concepts in the course. The odd week sessions focus on a guided research experience in an area of ethics conducted as part of a small group.

Section 1: Review of basic programming structures, introduction to tools

Section 2: Data representation and memory management, testing and debugging, assessing security of code

Section 3: Object Oriented design and software engineering

Section 4: HCI, Graphics, Ethics, Theory of Computation

A more detailed list of activities is available on the course website.

CBOK Legend

1. Abstraction
2. Design
3. Ethics
4. Interpersonal Communication
5. Societal Issues
6. History & Status of the Discipline
7. Hardware & Software
8. Data & Information
9. Programming
10. Human Computer Interfaces
11. Systems Development

Details of the Australian Computer Society's Core Bode of Knowledge (CBOK) can be found .

Some lecture material will be presented using podcasts supported by marked online quizzes. The deadline for completing quizzes wil be the start of the subsequent lecture.

Practical assignments will need to be completed (or nearly completed) before your practical session. Your work must be submitted to the web submission system by the end of each week and it will be subject to limited automated assessment. The week 4 practical, week 6 practical and the final practical, will be subject to additional assessment during a subsequent practical or workshop by practical demonstrators based on design, implementation, testing and questioning.

Workshops will be assessed based on your participation and your contribution to a group. The first workshop has a practical component that must be submitted by the end of the first week.

Tutorials will need to be completed by the endof the week before the tutorial. Marks will be given for answers to a specific subset of the tutorial questions but all questions should be attempted.

Small Group Discovery projects will be assessed as a group based on participation and a final report.

The final examination will assess all of the skills developed during the course and your ability to apply them as an individual.

Programming Practicals

You are expected to create the specified directory in your svn repository at the start of every practical and do all your work in a checked out working copy of this directory. Every time you stop working on a practical you are expected to commit the changes made so far to your svn repository. Separately, you must submit your work to Computer Science Web Submission System by the due date specified in the practical description. Only work submitted to the Web Submission System will be assessed and late penalties will be calculated using the date/time of the submission.

Practical Assessment Sessions

For those practicals with additional assessment by practical demonstrators, you must attend your first enrolled practical session following the due date or they will not be assessed. If the practical supervisors are unable to mark all students attending their enrolled practical session, alternative arrangements will be made for those students affected.

Missing a Practical Assessment Session

If you are unable to attend a practical assessment session due to medical or compassionate circumstances, you must submit a request to the course coordinator no later than 5 days after the missed session. In your request you must attach supporting documentation – a medical certificate and/or a letter from the student counselling service. Work requirements are not considered grounds for missing assessments. If you are working, please make sure you are available for all activities. If appropriate, the course coordinator will make alternative arrangements for assessing the practical work.

Penalties for Late Submission of Work

All work submitted, with the exception of Online Quizzes and the Peer Reviewed Assessments, are subject to the following late penalty policy:

• The maximum mark that can be awarded will reduce by 25% for each day/part day late,
• Marks in excess of the maximum that can be awarded are discarded.
• Assignment work submitted 4 or more days late will receive 0 marks.

Provision of Feedback to Students

Marks for programming practicals will be automatically awarded by the School of Computer Science Web Submission System for all submissions. For those practicals subject to additional assessment, the additional assignment marks and feedback will be also posted to the Web Submission System. Feedback on other assignment work will be available on the course website where the work was submitted.

Other Assessments

Online Quizzes, Peer Reviewed Assessments, the Final Practical Design, Tutorials and Small Group Reports must be submitted via the course website. The due date for each assessment will be listed in the assessment's description on the course website.

Late Penalties for Other Assessments

Due to the nature of some online assessments such as Online Quizzes and Peer Reviewed Assessments, it may not be possible to accept late submissions for some assessments even if an extension was appropriate. In these cases alternative arrangements will be made on a case-by-case basis.

Extensions for Programming Practicals and Other Assessments

If you are unable to complete an assessment by the due date because of medical or compassionate circumstances, you must submit a request to the course coordinator prior to the due date. In your request you must attach supporting documentation – a medical certificate and/or a letter from the student counseling service. Work requirements are not considered grounds for extensions. If you are working, please make sure you are available for all activities. If appropriate, the course coordinator will provide an extension that will be visible in the Web Submission System or on the course website where the submission is to be made.

Final Examination

The final examination will be scheduled by the examinations office. You will be able to access your exam schedule through Access Adelaide. You must be available during the replacement examination period (check University dates). If you are offered a replacement examination or additional assessment and are unable to attend for any reason, there may be no further opportunity for a replacement examination or additional assessment.