最新糖心Vlog

Upon completion of this course students should be able to:

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

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 all course materials, assignment descriptions, announcements, etc. are available on the course website by logging onto

It is your responsibility to regularly check for notices and to participate in online activities. This course does not use myuni.

This course has five contact activities: lectures, tutorials, practicals, workshops 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 to introduce the core theoretical material of the course supported by the tutorials.

The practicals are focussed on developing core programming skills in C++ both individually and collaboratively. They will include a small number of individual practical exams. You should also spend a significant amount of time on programming outside of these sessions.

The workshops are hands on collaborative sessions with groups of students sharing computers working on activities that may reinforce lecture material or introduce key skills required by the practicals.

The small group discovery sessions focus on a guided research experience in an area of ethics relevant to Software Engineering. The small groups will do most of their work outside these sessions.

The topics covered will include:

• Basics of Computer Architecture
• Arrays and Pointers
• Programming Languages, Grammars, Compiling
• Object Oriented Design
• Classes, Objects, Inheritance
• Abstract Classes, Polymorphism
• Planning, Design
• Debugging
• Event Driven Computing, Graphics
• Sorting, Searching
• Theory of Computation
• Algorithmic and Problem Solving Strategies
• Ethics in Software Engineering

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 最新糖心Vlogn Computer Society's Core Bode of Knowledge (CBOK) can be found .

Individual practical exams will take place in the practical sessions of weeks 3, 5, 7 and 12. The first practical exam is for practice only and does not contribute to your final mark for the course. Marks for each practical exam will be awarded by the web submission system based on functionality. In the workshop of weeks 4, 6 and 8, the previous week's practical will also be marked by practical demonstrators who will be able to give some individual feedback. No marks will be awarded if no one in a group attends the workshop in which the additional assessment takes place.

All other practicals can be undertaken individually or in a group of up to three students. A mechanism for registering groups will be provided so that only one student from each group needs to submit the work. Marks for these practicals will be awarded by the web submission system based on functionality. In the workshop in week 12 the practical covering weeks 8 to 11 will also be marked by practical demonstrators who will be able to give some individual feedback. No marks will be awarded if no one in a group attends the week 12 workshop in which the additional assessment takes place.

Workshops will be undertaken in groups of up to three students. A mechanism for registering groups will be provided for each workshop. Marks for workshops will be awarded by the web submission system based on functionality provided that the submission is made whilst attending a workshop session.

If tutorial submissions are made by the Sunday before each tutorial session, some individual feedback will be provided. Tutorials do not contribute to the final mark for the course.

Small Group Discovery projects will be assessed as a group based on participation, presentations and/or 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.

Practicals, Practical Exams and Workshops

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

Practical or Practical Exam Assessment Sessions

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

Missing a Practical or Practical Exam 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 as soon as practicable but 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. The course coordinator will make alternative arrangements for assessing the practical work on a case by case basis.

Penalties for Late Submission of Work

Late submissions will not be accepted for practical exams or workshops. The work must be submitted before leaving the practical exam or workshop.

Unless advised otherwise and where appropriate, all other work is 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.

Late Penalties for Other Assessments

Due to the nature of some assessments, it may not be possible to accept late submissions 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.

Provision of Feedback to Students

Marks for practicals, practical exams and workshops will be automatically awarded by the School of Computer Science Web Submission System for all submissions. For those practicals and practical exams subject to additional assessment, the additional assignment marks and feedback will be also posted to the Web Submission System. Feedback and marks on all assignment work will be available on the course website but there may be some delays because feedback and marks originally published in the Web Submission System must be manually copied to the course website.

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 最新糖心Vlog 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.