[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]
Monash University

FIT3036 Computer science project - Semester 2, 2013

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.

Mode of Delivery

  • Clayton (Day)
  • Sunway (Day)

Contact Hours

1 hr project meeting/week

Workload requirements

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.

Unit Relationships


CSE3301, FIT3144


FIT2004 or FIT3140

Chief Examiner

Campus Lecturer


Ingrid Zukerman

Consultation hours: One hour meeting per week

Marc Cheong

Consultation hours: One hour meeting per week

Sid Ray

Consultation hours: One hour meeting per week


Loke Kar Seng

Consultation hours: One hour meeting per week

Academic Overview

Learning Outcomes

At the completion of this unit students will have -A knowledge and understanding of:
  • strategies for developing a non-trivial programming, hardware, or theory-based project.
  • how to locate and utilise prior research and methods on a particular topic;
  • how to cite bibliographic references the student has used to understand various components of the project, support claims on knowledge, events, hypotheses and theories;
  • how to document software development from a user and application programming perspective;
  • software development methods: analysis, design, implementation and testing applied to the design and development of a non-trivial project.
Developed attitudes that enable them to:
  • acknowledge the importance of attending and contributing to meetings as a method of gaining important information and ideas about the project;
  • understand the basic requirements of software development from both user and developer perspectives;
  • appreciate the importance of correctly acknowledging the work of others in researching solutions to problems;
  • value the role of work books in documenting a projects progress and keeping track of its development.
Developed the skills to:
  • search, access, and analyse research literature as part of the process of developing solutions to problems;
  • understand the importance of analysis, design, documentation, and testing in developing a non-trivial software project;
  • write a moderately detailed report explaining methodology, outlining their contributions and the contributions of others, documenting the developed project from developer and user perspectives.
Demonstrated the communication skills necessary to:
  • understand the role of the client (or user) in the software development process;
  • appreciate the importance of written communication in documenting project development;
  • understand the importance of assessing time and resource requirements in the successful completion of non-trivial projects;
  • appreciate the importance of time and resource management in order to deliver non-trivial projects to deadlines.

Unit Schedule

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 Project Specification due Friday 6 September 2013
7 Test Plan  
8 Implementation & Testing  
9 Implementation & Testing  
10 Implementation & Testing  
11 Presentations Final Presentation / Demonstration due: Week 11 (for students allocated in week 11)
12 Presentations Final Presentation / Demonstration due: Week 12 (for students allocated in week 12); Test Report due: 3pm, Friday, End of Week 12; Workbook due: 3pm, Friday, End of Week 12; Final Report due: Friday, 3pm, End of Week 12
  SWOT VAC No formal assessment is undertaken in SWOT VAC
  Examination period LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/

*Unit Schedule details will be maintained and communicated to you via your learning system.

Assessment Summary

Projects are assessed by individual project supervisors.

Assessment Task Value Due Date
Project Specification 20 marks 3pm, Friday, End of week 6
Final Demonstration / Presentation 10 marks Week 11 or Week 12 (students to be allocated)
Test Report 10 marks 3pm, Friday, End of Week 12
Workbook 10 marks 3pm, Friday, End of Week 12
Final Report 50 marks 3pm, Friday, End of Week 12

Teaching Approach

Problem-based learning
Students are encouraged to take responsibility for organising and directing their learning with support from their supervisors.

Assessment Requirements

Assessment Policy

Faculty Policy - Unit Assessment Hurdles (http://www.infotech.monash.edu.au/resources/staff/edgov/policies/assessment-examinations/unit-assessment-hurdles.html)

Academic Integrity - Please see the Demystifying Citing and Referencing tutorial at http://lib.monash.edu/tutorials/citing/

Assessment Tasks


  • Assessment task 1
    Project Specification
    Includes a project plan, external and internal specifications, and a test plan.
    20 marks
    Criteria for assessment:

    Correctness and completeness of the project plan, external and internal specifications and test plan.

    Due date:
    3pm, Friday, End of week 6
  • Assessment task 2
    Final Demonstration / Presentation
    A demonstration of the software in a working environment.
    10 marks
    Criteria for assessment:

    Quality of working demonstration being presented.

    Due date:
    Week 11 or Week 12 (students to be allocated)
  • Assessment task 3
    Test Report
    Report detailing the outcomes of testing.
    10 marks
    Criteria for assessment:

    Completeness of report.

    Due date:
    3pm, Friday, End of Week 12
  • Assessment task 4
    A notebook (or computer file) containing weekly entries describing what has been accomplished through the week. Details on how the workbook should be organised are supplied with the project details.
    10 marks
    Criteria for assessment:

    Completeness of workbook, including at least 10 weekly entries.

    Due date:
    3pm, Friday, End of Week 12
  • Assessment task 5
    Final Report
    This provides a complete description of the project, the code, its results and interpretation of the results.
    50 marks
    Criteria for assessment:

    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.

    Due date:
    3pm, Friday, End of Week 12

Learning resources

Reading list

Any required or recommended textbooks will be determined by individual project supervisors on a case-by-case basis.

Monash Library Unit Reading List

Feedback to you

Types of feedback you can expect to receive in this unit are:
  • Informal feedback on progress in labs/tutes
  • Other: Informal feedback on progress in project meetings, and marked project reports

Extensions and penalties

Returning assignments

Assignment submission

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). Please note that it is your responsibility to retain copies of your assessments.

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Required Resources

Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.

For projects students will normally need access to a computer and programming environment.

Individual requirements will be identified by project supervisors.

Other Information


Graduate Attributes Policy

Student services

Monash University Library

Disability Liaison Unit

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.

Your feedback to Us

Previous Student Evaluations of this Unit

Student responses to FIT3036 have been positive and no changes are currently planned.

If you wish to view how previous students rated this unit, please go to

[an error occurred while processing this directive]