FIT3140 Advanced programming - Semester 2, 2011

This unit develops the students' ability to design, implement and maintain moderately complex, realistically-sized programs. It builds upon the basic programming techniques introduced in FIT1002, FIT1008 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, and graphical games. The unit can 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.

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

Contact Hours

2 hrs lectures/week, 3 hr laboratory/week

Workload

You are expected to spend 12 hours per week during semester on this unit.

This includes 2 hours per week of lectures, 3 hours per week of labs, and an average of 7 hours per week of project work, private study, and exam revision.

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

Academic Overview

Learning Objectives

Upon successful completion of the unit, students will have a solid working knowledge of advanced object oriented concepts, including multiple inheritance and polymorphism, and the ability to apply this knowledge to the construction of non-trivial programs.

They will have an understanding of:

• 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.

• recognise the importance of process in achieving quality in a repeatable manner;

• 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;
• implement a personal software development process 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.

• 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 efficiently when that programming language 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.

• create design documents that can be used to present a view of the software to other 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.

Graduate Attributes

Assessment Summary

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

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.

Feedback

Our feedback to You

• Informal feedback on progress in labs/tutes
• Graded assignments with comments
• Solutions to tutes, labs and assignments

Your feedback to Us

Previous Student Evaluations of this unit

Recommended Resources

Students will be provided with a VMWare virtual machine image, which contains a full development environment for the lab and project work they will be expected to complete through the semester.  Students can download VMWare Player for Linux, Mac OS X and Windows at no charge.

If they wish can also install a Java development environment, the Eclipse Java IDE, and the Android SDK at no cost on their own computer directly, but no support will be provided for this.

Students with Android smartphones may, if they wish, use these to test and debug the software developed throughout the unit.  This, however, is not necessary, as sufficient smartphones have been purchased for the purpose, and a limited number will be available for students to borrow overnight.

Examination material or equipment

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

Unit Schedule

*Unit Schedule details will be maintained and communicated to you via your MUSO (Blackboard or Moodle) learning system.

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 week 3, 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:

  Java programming (individual)

  Description:

  Students will demonstrate their proficiency in basic Java programming by implementing a small Java program.
  
  Students will be expected to independently research some information necessary to complete the task.  It will be expected of students to test the program (including devising their own test data) and adequately document their code.

  Weighting:

  5%

  Criteria for assessment:

  • Completeness of assignment according to specification.
  • Functional correctness of submission.
  • Quality of submitted code, including design, formatting and documentation.

  Due date:

  Friday 5 August 2011

• Assessment task 2

  Title:

  Vision statement (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.

  Weighting:

  5%

  Criteria for assessment:

  • Effectively capturing key functional requirements.
  • Identification and description of key attributes of system context.
  • 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:

  Friday 19 August 2011

• Assessment task 3

  Title:

  Spiking exercises (pairs)

  Description:

  Project pairs will conduct several "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:

  5%

  Criteria for assessment:

  • Quality of report, including risk description, description of coding tasks, clear reporting of outcome, and assessment of risk after spiking.
  • Effectiveness of coding undertaken to mitigate risk.

  There will be multiple spikes.  Some may be conducted by only one member of project pairs, some will be conducted by both members.  Spiking reports will be assessed individually.

  Due date:

  Demonstration in Week 6 Lab, report due 2 September 2011

• Assessment task 4

  Title:

  Design document (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.

  Weighting:

  10%

  Criteria for assessment:

  • Comprehensiveness of design.
  • Quality of design decisions.
  • Readability and layout of report.
  • Correct use of UML notation to document design.

  The assignment will be assessed as a pair. Students will document their individual contributions to the assignment. Generally, students will receive the same mark, unless there are significant discrepancies over the semester in contributions to the pair project work.

  Due date:

  Friday 16 September 2011

• Assessment task 5

  Title:

  Iteration 1 (pairs)

  Description:

  Project pairs will complete their first iteration of the active development phase of the project.
  
  They will demonstrate (in labs) and deliver working and tested software implementing several "user stories" as developed in earlier assignments.
  
  The deliverables will also include release notes and user documentation as required.
  
  The assignment will be assessed as a pair.  Students will document their individual contributions to the assignment.  Generally, students will receive the same mark, unless there are significant discrepancies over the semester in contributions to the pair project work.

  Weighting:

  10%

  Criteria for assessment:

  • Completeness of implementation.
  • Quality of implementation.
  • Appropriateness of testing.
  • Correct use of provided tools.
  • Appropriate supply of documentation.
  • Conduct of pair programming
  • Quality of written reflection on pair programming.

  Due date:

  Demonstration in Week 10 Lab, code and documentation due Friday 7 October 2011

• Assessment task 6

  Title:

  Iteration 2 (pairs)

  Description:

  Students will complete a second iteration of development for the system, implementing additional functionality.  They will use "pair programming" for at least part of this development, and reflect on whether it is useful for them.
  
  Another release will be delivered at the end of the iteration, which will include appropriate testing and documentation for the implemented functionality.
  
  Students will demonstrate this functionality in labs.
  
  The assignment will be assessed as a pair.  Students will document their individual contributions to the assignment.  Generally, students will receive the same mark, unless there are significant discrepancies over the semester in contributions to the pair project work.

  Weighting:

  10%

  Criteria for assessment:

  • Completeness of implementation.
  • Quality of implementation.
  • Appropriateness of testing.
  • Correct use of provided tools.
  • Appropriate supply of documentation.
  • Conduct of pair programming.
  • Quality of written reflection on pair programming.

  The assignment will be assessed as a pair.  Students will document their individual contributions to the assignment.  Generally, students will receive the same mark, unless there are significant discrepancies over the semester in contributions to the pair project work.

  Due date:

  Demonstration in Week 12 Lab, code and documentation due Friday 21 October 2011

• Assessment task 7

  Title:

  Final report (individual)

  Description:

  Students will reflect on their project work, including

  • Reflecting on the overall quality of the deliverables to date.
  • 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:

  Friday 21 October 2011

Examinations

• Examination 1

  Weighting:

  50%

  Length:

  3 hours

  Type (open/closed book):

  Closed book

  Electronic devices allowed in the exam:

  None

Assignment submission

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.

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://www.lib.monash.edu.au/tutorials/citing/

Other Information

Policies

Student services

Recommended texts:

• Object-oriented and Classical Software Engineering (8th edition): Stephen R. Schach.  McGraw-Hill.  ISBN 978-0-07-337618-9
• Hello, Android (3rd edition): Introducing Google's Mobile Development Platform, Ed Burnette.  No Starch Press. ISBN: 978-1-93435-656-2.
• The Scrum Primer.  Free download - http://scrumfoundation.com/library
• Extreme Programming explained, 2nd edition.  Kent Beck; Cynthia Andres; Erich Gamma.Guide to Agile methods.  Addison-Wesley Professional.  ISBN:978-0321278654
•  Scrum and XP from the trenches, by Henrik Kniberg.  Free download: http://www.infoq.com/minibooks/scrum-xp-from-the-trenches