This unit is intended to provide practical experience in designing, developing and testing a non-trivial computer science project. Projects are generally software-based, although sometimes they may involve hardware development or investigation of theory. Projects cover the whole process of software (or hardware) development, from analysis through design to implementation and testing. Comprehensive written documentation on the project is required. Students are assigned in groups to a project supervisor. There are no lectures in this unit, although students will be expected to attend regular meetings with their project supervisor.
1 hr project meeting/week
This unit requires 12 hours of work per week over a semester. Students must be prepared to commit extra hours of private study to meet this requirement, in addition to the 1 contact hour per week.
CSE3301, FIT3144
Kevin Korb
Andrew Paplinski
Loke Kar Seng
At the completion of this unit students will have -
A knowledge and understanding of:
Projects are assessed by individual project supervisors.
| Assessment Task | Value | Due Date |
|---|---|---|
| Project Specification | 20 marks | Friday 9 September 2011 |
| Final Demonstration / Presentation | 10 marks | Week 11 or Week 12 (to be allocated) |
| Test Report | 10 marks | Friday 21 October 2011 |
| Workbook | 10 marks | Friday 21 October 2011 |
| Final Report | 50 marks | Friday 21 October 2011 |
Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through SETU, Student Evaluation of Teacher and Unit. The University's student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.
For more information on Monash's educational strategy, and on student evaluations, see:
http://www.monash.edu.au/about/monash-directions/directions.html
http://www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
For projects students will normally need access to a computer and programming environment.
Individual requirements will be identified by project supervisors.
| Week | Activities | Assessment |
|---|---|---|
| 0 | No formal assessment or activities are undertaken in week 0 | |
| 1 | Preliminary Reading | |
| 2 | Preliminary Reading | |
| 3 | Project Plan | |
| 4 | Project Plan | |
| 5 | Project Design | |
| 6 | Project Design | |
| 7 | Test Plan | Project Specification due 9 September 2011 |
| 8 | Implementation & Testing | |
| 9 | Implementation & Testing | |
| 10 | Implementation & Testing | |
| 11 | Presentations | Final Presentation / Demonstration due Week 11 (to be allocated) |
| 12 | Presentations | Final Presentation / Demonstration due Week 12 (to be allocated); Test Report due 21 October 2011; Workbook due 21 October 2011; Final Report due 21 October 2011 |
| SWOT VAC | No formal assessment is undertaken SWOT VAC | |
| Examination period | LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/ academic/education/assessment/ assessment-in-coursework-policy.html |
*Unit Schedule details will be maintained and communicated to you via your MUSO (Blackboard or Moodle) learning system.
Correctness and completeness of the project plan, external and internal specifications and test plan.
Quality of working demonstration being presented.
Completeness of report.
Completeness of workbook, including at least 10 weekly entries.
Clarity, organisation and completeness of both the report and the code. The quality of the interpretation and analysis of the results will be a significant factor.
It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/plagiarism-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz).
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.
Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University's academic standards, and to provide advice on how they might uphold them.
You can find Monash's Education Policies at:
http://policy.monash.edu.au/policy-bank/academic/education/index.html
Key educational policies include:
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at www.monash.edu.au/students The Monash University Library provides a range of services and resources that enable you to save time and be more effective in your learning and research. Go to http://www.lib.monash.edu.au or the library tab in my.monash portal for more information. Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis
Reading list
Any required or recommended textbooks will be determined by individual project supervisors on a case-by-case basis.