Skip to the content | Change text size
PDF unit guide

FIT3140 Advanced programming - Semester 1, 2014

This unit develops the students' ability to design, implement and maintain moderately complex, realistically-sized programs using an Agile software development methodology. It builds upon the basic programming techniques introduced in introductory programming unit and offers the first introduction to the implementation of more complex real-world programs. Examples of such systems include compilers and interpreters, simulations, visualisation tools, drawing packages, database systems, graphical games. Such systems may be implemented in the context of non-traditional computing environments such as smartphone "apps". The unit may offer students the opportunity to get acquainted with a second programming language within the procedural-object oriented paradigm, such as C++, Python or one of their cousins, depending on the scope of the project chosen in a particular semester.

The unit bridges between core programming knowledge and the large-scale software engineering context. It will emphasise the implementation and use of intermediate to advanced data structures (such as search trees, hash structures, graphs and graph algorithms etc.) and the embedding into an actual computing system (i.e. interacting with the O/S, networking components etc).

Mode of Delivery

Clayton (Day)

Workload Requirements

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

  • Two hours of lectures
  • One 3-hour laboratory

(b.) Additional requirements (all students):

  • A minimum of 7 hours independent study per week for completing lab and assignment work, private study and revision

Additional workload requirements

Substantial parts of the project work must be completed in pairs.  Students will need to schedule time to meet with their project partners outside scheduled classes.

Unit Relationships

Prerequisites

FIT1008

Chief Examiner

Campus Lecturer

Clayton

Robert Merkel

Consultation hours: Tuesday 2-4pm

Your feedback to Us

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 the Student Evaluation of Teaching and Units (SETU) survey. 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, see:

www.monash.edu.au/about/monash-directions/ and on student evaluations, see: www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html

Previous Student Evaluations of this Unit

Based on student feedback the assignment submission schedule has been modified so that students can receive better feedback during the later part of the unit.

If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp

Academic Overview

Learning Outcomes

Upon successful completion of the unit, students will have an understanding of:
  • agile software development practices including iteration, test-driven development, spiking, and continuous customer involvement;
  • how to design moderately complex programs where that design will typically incorporate a number of modules and a number of levels of refinement;
  • the role of software architecture in program design and a knowledge of a number of commonly-applied software architectures;
  • how to make use of design patterns, re-usable components and software libraries in designing modular software;
  • how to make design decisions that take into account desirable quality attributes such as flexibility, maintainability and re-usability;
  • how to implement programs in a systematic manner using an integrated testing procedure in such a way that modules are highly likely to function as specified;
  • how to isolate faults within a program in a systematic manner;
  • how to use software tools to aid in the program design and implementation process. These tools might include program design tools, integrated program development environments, configuration management systems, re-factoring tools, automatic testing environments and debuggers;
  • how to adequately document a software project.
They will have developed attitudes that enable them to:
  • evolve a software system in response to feedback over time;
  • recognise the importance of process in achieving quality in a repeatable manner;
  • appreciate the distinction between analysis of program requirements and design that seeks to meet specifications;
  • develop software designs that place appropriate importance to the user experience;
  • adopt an approach to making design decisions that involves considering a range of options for design decisions and evaluating potential design decisions with reference to a system of values;
  • evaluate product and process development with the aim of continuously improving their software development methodology;
  • understand the importance of being able to communicate all aspects of the program development process, and identify the most appropriate medium for that communication.
They will have developed the skills to:
  • design moderately complex, real-world programs where that design involves multiple levels of refinement and the specification of a non-trivial number of modules;
  • learn a new programming language or environment efficiently when that programming language or environment is similar to a programming language the student already knows;
  • develop software in a modern software environment that may include software development tools such as those found in an integrated, programming environment, configuration management systems and automated testing systems;
  • design and implement programs that can interface with complex software systems such as graphical-user interfaces, database systems and mathematical libraries;
  • design and implement programs that may need to communicate via a computer network with software systems on other computer devices;
  • design and implement systems on alternative computing platforms including smartphones and embedded systems;
  • identify performance-critical aspects of a software system and learn to apply their analysis skills in larger systems.
They will have demonstrated the communication skills to:
  • create design documents that can be used to present a view of the software to other stakeholders;
  • identify items that are insufficiently clear from written documentation and proactively seek clarification from stakeholders;
  • create documents or on-line help that enable people to understand how to use the program;
  • create documents that allow a programmer to understand the program in sufficient detail to allow the software to be maintained;
  • produce literate programs, i.e. program source statements that are well commented.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1 The problem domain - image rendering  
2 Introduction to Agile development  
3 Requirements gathering - an Agile approach Assignment 1 due
4 The problem domain - welcome to Android Assignment 2 (pairs) due
5 Design and modeling I  
6 Design and Modeling II Assignment 3 (pairs) due
7 Performance analysis  
8 Agile practices Assignment 4 (pairs) due
9 Testing  
10 Agile practices - refactoring Assignment 5 initial submission (pairs) due
11 User interfaces  
12 Software release; revision Assignment 5 final submission (pairs) , Assignment 6 submission (individual) due
  SWOT VAC No formal assessment is undertaken in 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 learning system.

Teaching Approach

  • Lecture and tutorials or problem classes
    This teaching and learning approach provides facilitated learning, practical exploration and peer learning.
  • Laboratory-based classes
    This learning and teaching approach provides the opportunity for practical experimentation with approaches taught in lectures.

Assessment Summary

Examination (3 hours): 50%; In-semester assessment: 50%

Assessment Task Value Due Date
Introductory programming assignment (individual) 5% Week 3
Vision statement and risk analysis (pairs) 5% Week 4
Spiking (pairs) 10% Week 6
Assignment 4 - design and benchmarking (pairs) 5% Week 8
Assignment 5 - Iterations (pairs) 20% Initial submission due Week 10, informal feedback supplied in labs. Final submission due Week 12
Final report (individual) 5% Week 12
Examination 1 50% To be advised

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

Students are expected to attend lectures and lab classes.

While lab exercises will not be marked, many of the labs will be used for project work in pairs, including assessment.  As such, students will need to attend these.

Students will identify a project partner to work with by the end of the first laboratory, who is enrolled in the same lab class.  Students will work with their partner for subsequent in-semester assessment unless there are exceptional circumstances.

  • Assessment task 1
    Title:
    Introductory programming assignment (individual)
    Description:
    Students will complete an introductory programming assignment which introduces them to the general problem domain of future assignments.
    Weighting:
    5%
    Criteria for assessment:
    • Delivery of required functionality.
    • Quality of program design. 
    • Quality of coding practices. 
    • Layout and documentation.
    Due date:
    Week 3
  • Assessment task 2
    Title:
    Vision statement and risk analysis (pairs)
    Description:
    Project pairs will write a brief, high-level description of the key requirements of the semester-long project which forms the basis for subsequent assignment tasks. They will also identify and analyse key risks to the successful completion of the project.
    Weighting:
    5%
    Criteria for assessment:
    • Effectively capturing key functional requirements.
    • Identification and description of key attributes of system context.
    • Identification and analysis of risks
    • Readability and presentation quality of document.

    This assignment will be completed in pairs.  Pairs are expected to share the workload and will usually receive the same mark.  Individual contributions will be documented, and if workloads are not appropriately shared over the semester marks will be adjusted accordingly.

    Due date:
    Week 4
  • Assessment task 3
    Title:
    Spiking (pairs)
    Description:
    Project pairs will conduct one or more "spiking" exercises, conducting exploratory/prototype coding activities to better characterise and mitigate identified risks to the project. Each individual spike will consist of some exploratory/proof-of-concept coding, and a report which documents the information gained. Students will conduct demonstrations in labs.
    Weighting:
    10%
    Criteria for assessment:
    • Reporing, including:
    •  risk description
    • description of coding tasks
    • clear reporting of outcome
    • assessment of risk after spiking.
    • Effectiveness of coding undertaken to mitigate risk.

    There may be multiple spikes, and students will be responsible for dividing up the work in their pairs.  Pairs will generally receive the same mark. Individual contributions will be documented, and if workloads are not appropriately shared over the semester marks will be adjusted accordingly.

    Due date:
    Week 6
  • Assessment task 4
    Title:
    Assignment 4 - design and benchmarking (pairs)
    Description:
    Project pairs will work together to write a document describing aspects of the architecture and design of their system. As well as structured text, the document will include UML diagrams. To inform their design, pairs will conduct "benchmarking" to measure the performance of alternative designs, and report the results in written form.
    Weighting:
    5%
    Criteria for assessment:
    • Completeness of implementation.
    • Quality of implementation.
    • Appropriateness of functional testing.
    • Rigorousness of performance tuning
    • Correct use of provided tools.
    • Appropriate supply of documentation.

    Pairs are expected to share the workload and will usually receive the same mark.  Individual contributions will be documented, and if workloads are not appropriately shared over the semester marks will be adjusted accordingly.

    Due date:
    Week 8
  • Assessment task 5
    Title:
    Assignment 5 - Iterations (pairs)
    Description:
    Project pairs will complete two iterations of the active development phase of the project. They will deliver working and tested software implementing several "user stories" as developed in earlier assignments. In the first iteration (for initial submission) they will complete initial basic functionality; in the second iteration, as well as adding additional functionality they will conduct performance tuning. The deliverables will also include release notes and user documentation as required.
    Weighting:
    20%
    Criteria for assessment:
    • Completeness of implementation.
    • Quality of implementation.
    • Appropriateness of functional testing.
    • Rigorousness of performance tuning
    • Correct use of provided tools.
    • Appropriate supply of documentation.
    Due date:
    Initial submission due Week 10, informal feedback supplied in labs. Final submission due Week 12
  • Assessment task 6
    Title:
    Final report (individual)
    Description:
    Students will reflect on their project work, including: Reflecting on the overall quality of the deliverables to date. Characterising their individual contribution to the project, and that of their partner. Identifying the strengths and weaknesses of the development processes used in the context of the current project. Determine a realistic timeframe for completion of the full vision as described earlier in semester. Describe the process they would follow to achieve completion.
    Weighting:
    5%
    Criteria for assessment:
    • Quality and depth of reflection.
    • Plausibility of analysis of future prospects.
    • Quality of proposed process.
    • Clarity of written report.
    Due date:
    Week 12

Examinations

  • Examination 1
    Weighting:
    50%
    Length:
    3 hours
    Type (open/closed book):
    Closed book
    Electronic devices allowed in the exam:
    None

Learning resources

Reading list

  • The Scrum Primer.  Free download: http://www.scrumprimer.com/
  •  Scrum and XP from the Trenches by Henrik Kniberg.  Free download: http://www.infoq.com/minibooks/scrum-xp-from-the-trenches

Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html

Faculty of Information Technology Style Guide

Feedback to you

Examination/other end-of-semester assessment feedback may take the form of feedback classes, provision of sample answers or other group feedback after official results have been published. Please check with your lecturer on the feedback provided and take advantage of this prior to requesting individual consultations with staff. If your unit has an examination, you may request to view your examination script booklet, see http://intranet.monash.edu.au/infotech/resources/students/procedures/request-to-view-exam-scripts.html

Types of feedback you can expect to receive in this unit are:

  • Informal feedback on progress in labs/tutes
  • Graded assignments with comments

Extensions and penalties

Returning assignments

Resubmission of assignments

No resubmission of assignments will be permitted.

Referencing requirements

Code based on algorithms or information from third-party sources (such as books or websites) must acknowledge these sources in comments, in sufficient detail for markers to find and check these sources.  Some assignments will explicitly prohibit the use of this - if so, you must not use them.

Where third party material is used in written assignments, they should be cited.  Students may use any of the referencing methods described in the Monash University Library's tutorial on referencing to do so:

http://guides.lib.monash.edu/content.php?pid=88267&sid=656564

Assignment submission

It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/student-academic-integrity-managing-plagiarism-collusion-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.

Recommended Resources

Students will develop for Android using the Google SDK integrated with Eclipse.  Eclipse will be provided in laboratory work, but students may choose to use any Android development setup that they prefer..

Students may choose to use their own laptops if they wish; however, they will be responsible for all technical support and ensuring that their code runs on the specified platform.

Recommended text(s)

Kent Beck, Cynthia Andres, Erich Gamma. (). Extreme Programming explained. (2nd Edition) Addison-Wesley Professional (ISBN: 978-0321278654).

Examination material or equipment

Students should refer to the unit website for details about the exam.

Other Information

Policies

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: www.policy.monash.edu.au/policy-bank/academic/education/index.html

Key educational policies include:

Faculty resources and policies

Important student resources including Faculty policies are located at http://intranet.monash.edu.au/infotech/resources/students/

Graduate Attributes Policy

Student Charter

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.