CSE2305 - Object-Oriented Software Engineering
assessment

 

Assessment


Assessed Course Components

Assessment for this course consists of the following components:

Exam (80%) and 4 Assignments (20%):

Assignment # questions Marks Due Date Submission
Code
Marks
Make, gcc, gdb Hurdle requirement By the end of your first lab session
Assignment 1 5 questions 50 marks (5% of assessment) Friday, 11 August ( ) ass1 / late1 available here
Assignment 2 2 questions 50 marks (5% of assessment) Friday, 1 September( ) ass2 / late2 available here
Assignment 3 1 question 50 marks (5% of assessment) Friday, 22 September ( ) ass3 / late3 available here
Assignment 4 1 question 50 marks (5% of assessment) Friday, 13 October ( ) ass4 / late4 available here
Sup Assignment 1 question 50 marks Wednesday, 20 December ( ) sup1 N/A

All assignment submission is electronic. See the submit page for details on how to submit assignments (including late submissions).


Sample solutions

Sample solutions will be available after the due date for each assignment. Please note if you are accessing these solutions outside Monash you will need to be currently enrolled in this subject and supply your authcate username and password.


Self assessment Questions

Multiple choice self assessment questions are posted at the beginning of each week and relate to the current lecture topics. You should attempt these questions each week to make sure you understand the topics under discussion in the lectures. Similar questions often appear in the exam.


Your Opportunity to Assess Us

An anonymous course survey form is available here.

Students are encouraged to fill the form out completely and submit it. Your feedback will help us improve the course.


Sample Exam Material

The following sample exam material is available:

You are strongly advised to revise the entire course material, not just these questions.

Note also that sample answers will not be made available (with the exception of the design question).


Assessment Requirements

The practical assignment component is worth 20% of your final mark. Assignments are submitted electronically by the due date. The remaining 80% of your marks will be assessed in the final exam (3 hours duration).

Note, however, that you must pass both the assignment and the exam components to pass the subject.  If you do not pass both the assignment and the exam the highest mark you can receive is 44 N.

Assessment for CSE2305 is based on an assignment (20%) and an exam (80%), although these percentages are somewhat misleading as the exam will be heavily based on the work completed in the assignment.

You must pass both the assignment and the exam to pass the subject.


Assessment Criteria for Assignments

The assignments will be assessed using the following criteria:

OO Design:
The appropriateness of your use of OO design principles, techniques, and tools, and the consistency of the resultant OO design.
Code:
The structure and correctness of your C++ code, how well it meets the specified requirements of the assignment, and how well you have adhered to good programming practices (e.g. naming schemes, commenting, layout, etc.) Be aware that all submissions will routinely be checked for "excessive collaboration" (see below).
Testing and Support:
The provision of support code (a testing harness) and data files, with a clear explanation of the testing which was carried out. Provision of a correct Makefile.

Assessment-related Policies

Failure to submit work / lab attendance

If you have an illness or emergency and miss a prac you must complete an Absentee Form with medical certificate or a letter of explanation attached and hand it in to the CSSE General Office (Bldg 75, ground floor) on the day you return to university.

All components of the practical assessment should be submitted electronically by the due date. If you have an illness (covered by medical certificate) or other serious problem that prevents you from submitting assignments on time please contact the lecturer as soon as possible. Information about assignment extensions.

Failure to follow this procedure may result in a fail result for the practical work not supplied, and hence possibly a fail result for the entire course.

None of the following reasons is considered valid for late submission of assessed materials:

Citation

All external sources used in the preparation of assignment submissions must be appropriately acknowledged and referenced in the normal manner. Failure to acknowledge the source of material actually incorporated in an assignment constitutes a form of plagiarism (see below).

Plagiarism & Cheating

Note that all materials submitted for assessment must include this student declaration which acknowledges what you are submitting is your own work.

Plagiarism is considered a serious offence by the university. Students caught copying someone else's work (e.g. fellow students or off the Internet) and submitting it as their own will face disiplinary action.

Students should consult University materials on cheating, in particular:

  1. Statute 4.1 on Discipline at http://www.monash.edu.au/pubs/calendar/statutes/statutes04.html#Heading102
  2. Student Resource Guide at http://www.monash.edu.au/pubs/handbooks/srg/ , particularly the section on Cheating at http://www.monash.edu.au/pubs/handbooks/srg/srg0073.htm .
  3. Student Resource Guide - section on Student Rights and Responsibilities at http://www.monash.edu.au/pubs/handbooks/srg/srg0059.htm .
  4. Faculty policies at http://www.infotech.monash.edu.au/resources/policies.html

It is each student's responsibility to make themselves familiar with the contents of these documents.

Collaboration

You are encouraged to consult each other and study together if you so desire. However, you are not permitted to collaborate in the preparation of materials for submission for the practical assessment.
This means students may discuss the details of the assignment/lab exercises with one another, but may not jointly develop solutions, actual code, documentation, or test data.

Development Platform

All software for this subject is to be written in C++ in Linux environment, using the g++ compiler. A tutorial on debugger gdb and build tool make can be found on the resources page of the subject web site. Students should study this tutorial in their own time before their first lab session (in which you will complete the tutorial).


Warning

Most students will find it difficult or impossible to complete the assignment work during the prac classes themselves. It is expected that significant amounts of work will have to be completed outside scheduled prac times (in the nominal 6-8 hours per week of "non-contact" study you are expected to devote to this subject).


This material is part of the CSE2305 - Object-Oriented Software Engineering course.
Copyright © Jon McCormack, 2005, Alan Dorin 2006. All rights reserved.

Last Modified: October 5, 2006