Dr Peter Tischer
Senior Lecturer
Phone: +61 3 990 55208
Fax: +61 3 990 55159
Contact hours: 2.00pm - 300pm Thursdays
Associate Professor Bin Qiu
Associate Professor
Phone: +61 3 990 59688
Fax: +61 3 990 55159
Dr Peter Tischer
Senior Lecturer
Phone: +61 3 990 55208
Fax: +61 3 990 55159
Welcome to FIT3036 Third Year Project. It is a 6 credit point unit, offered in first and second semester during 2010. The unit gives you an opportunity to tackle a significantly larger software design and implementation than you have been able to do previously in your course. You will work on a project allocated to you (please remember to identify your preferences) under the supervision of an academic staff member. The nature of the project is largely unconstrained, and will be determined in consultation with your project supervisor.
Weekly project group meetings: 1 hour per week
Individual design, coding, testing: 9 hours per week
For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/
On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.its.monash.edu.au/
CONTRARY TO WHAT IS STATED ABOVE, THERE ARE NO TUTORIALS IN THIS UNIT.
| Week | Date* | Topic | Key dates |
|---|---|---|---|
| 1 | 19/07/10 | Preliminary reading & Project selection | 22 & 23 July |
| 2 | 26/07/10 | Preliminary reading | 31 July |
| 3 | 02/08/10 | Plan of Attack | |
| 4 | 09/08/10 | Milestone 1 | 14 August |
| 8 | 06/09/10 | Milestone 2 | 11 September |
| 10 | 20/09/10 | Milestone 3 | 25 September |
| Mid semester break | |||
| 12 | 11/10/10 | Milestone 4 | 16 October |
| 13 | 18/10/10 | Completion and Submission of report, and final demonstration | 23 October |
*Please note that these dates may only apply to Australian campuses of Monash University. Off-shore students need to check the dates with their unit leader.
Student responses to FIT3036 were positive in 2009 and no changes are currently planned.
Any textbooks required will be determined by individual project supervisors on a case-by-case basis.
Students studying off-campus are required to have the minimum system configuration specified by the Faculty as a condition of accepting admission, and regular Internet access.On-campus students, and those studying at supported study locations may use the facilities available in the computing labs.Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook.You will need to allocate time each week for use of a computer, including time for newsgroups/discussion groups.
You need to be aware that the computing resources that may be supplied to you in order to undertake this unit cost real money, and the university has had to impose limits on the use of the internet for all staff and students. A quota system is to be introduced this year, but in the meantime you must make yourself aware of the "Acceptable Use" policies of both the faculty and the university.
These can be accessed on the web at:
Note that accessing these and other course-related URLs from within Monash is free from within the Monash network, and is not regarded as part of quota.
Study resources we will provide for your study are:
During semester 2, 2010, the unit will be supported by Moodle.
To pass a unit which includes an examination as part of the assessment a student must obtain:
If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit.
The unit is assessed on the basis of a completed project report, and work done during the semester (see below). There is no examination in this unit.
Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.
Assignment submission and return procedures, and assessment criteria will be specified with each assignment.
Assignment submission and preparation requirements will be detailed in each assignment specification. Submission must be made by the due date otherwise penalties will be enforced. You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html.
Attendance = 1 mark
Absence = 0 mark
The contents of the bulk of the report should be organized in a manner which allows the casual reader to quickly identify what you were aiming to achieve and how much has been achieved. At the same time, the serious reader of the report must be able to easily determine how your achievements have been realized.
One suggested organization for your report is given below; obviously the detailed format and contents is a matter of choice depending upon the nature of the project (especially for non-programming projects) and prior agreement between the student and the supervisor.
Unless told otherwise by the supervisor concerned, the report must be printed on A4 stationery with standard margins. It is anticipated that most reports will be between 8 and 16 pages in length.
2.1. Identification(1a) Your Name
(1b) Your Student ID
(2) Project Title
(3) Report Date
(4) Supervisor's Name
(5) Access information for the supervisor/examiner to run the project software, such as, machine on which developed, usercode and password.
2.2. General Description(1) A brief description (in your own words!) of the project task or tasks, including the relationship to other work (by previous students, the supervisor or your peers).
(2) Any theoretical material or reference material relevant to understanding either the task or the solutions to be evaluated and/or employed in the project. It is important to include information on references YOU have consulted and a discussion (where appropriate) of relevant previous work by others (including references to THEIR work). References must include full bibliographic data, e.g. Nurd, Fred J. (1983): "Counting the Vertices of a Circle", Journal of Irreproducible Results, vol. 7, no 5,.pp 13-12.
(3) A discussion of any assumptions made in developing the solution to the problem, and an evaluation of alternative solutions.
(4) An outline of the method of attack.
2.3. AchievementsA summary, with particular emphasis on limitations of the solution and where the achievements are less than was anticipated (based on the statement of the problem) an explanation of why the goals were not reached.
2.4. Project DocumentationThis section should provide a detailed description of the project solution aimed at both users and implementors (modifiers).
2.4.1. User InterfaceEssential components of this section include:
Start with a functional description of what the solution does and a synopsis of how the solution has been structured (e.g. include a call tree or block diagram).
Include a detailed description of all file structures, significant data structures and non-trivial algorithms.
For each substantive module in the solution provide a description of sufficient detail to allow the reader to discover
Describe in general terms the tests which have been performed in an attempt to validate the correct operation of the project solution. The emphasis should be on summarizing the testing procedures that were employed, rather than including a box of listings and claiming this proves the program was tested.
Where practical, include the transcript of one or more invocations of the solution which demonstrate all the supported features. Such a transcript must be self contained to the extent that another person could reproduce the results using your solution (i.e. include all system-level commands, file assignments, input data, option settings and output data.)
2.5. Concluding RemarksWhat has been achieved? Attempt to summarize your own accomplishments, as opposed to the prior achievements of others.
Suggested enhancements to overcome limitations, or to support additional useful facilities.
2.6. ReferencesIt is very rarely that a student completes a project without reference to the literature or the prior work of others. Include all books, articles and notes which you used during the course of the project.
2.7. Appendix AThe actual program listings or circuit diagrams which should be well commented and (where possible) cross-referenced.
REMEMBER, REQUIREMENTS VARY DEPENDING ON THE PROJECT AND YOU MUST CONFIRM WITH YOUR SUPERVISOR WHETHER THE ABOVE SCHEME IS APPROPRIATE FOR YOUR PARTICULAR PROJECT.
Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.
Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.
A copy of the email or other written communication of an extension must be attached to the assignment submission.
Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html
Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.
Please visit the following URL: http://www.infotech.monash.edu.au/units/appendix.html for further information about: