Skip to the content | Change text size
PDF unit guide

FIT5151 Object-oriented business application development - Semester 2, 2013

FIT5151 will aim at capitalising on what students have learned in FIT9017 Foundations of programming (or equivalent. The unit covers more in-depth material to enable students to build business applications that follow good Software Engineering principles of maintainability, reusability and expandability. The emphasis will be on helping students acquire solid object-oriented programming knowledge and skills for building business applications. Popular object-oriented design patterns will be introduced whenever appropriate to illustrate effective design process in building larger systems.

Mode of Delivery

Caulfield (Day)

Contact Hours

2 hrs lectures/wk, 2 hrs laboratories/wk

Workload requirements

Students will be expected to spend a total of 12 hours per week during semester on this unit as follows:

For on-campus students:
Lectures: 2 hours per week
Tutorial/Lab Sessions: 2 hours per week per tutorial
and up to an additional 8 hours in some weeks for completing lab and project work, private study and revision.

Off-campus students generally do not attend lecture and tutorial sessions, however, you should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week.

Unit Relationships

Prerequisites

FIT9017 or equivalent

Chief Examiner

Campus Lecturer

Caulfield

Elliott Wilson

Academic Overview

Learning Outcomes

At the completion of this unit, students will have -A knowledge and understanding of:
  • how to produce well-run, well-tested and well-documented object-oriented software by following solid software engineering principles of maintainability, reusability and expandability;
  • effective use of popular object-oriented design patterns in the design process of larger systems;
  • how to effectively and efficiently develop object-oriented application solutions to business-related problem specifications.
Developed attitudes that enable them to:
  • appreciate the responsibility of coming up with well-tested and documented programs;
  • appreciate the need to maintain ethical conducts when programming by making sure the code used my program is their own or taken from a legitimate source with full acknowledgement.
Gained practical skills to:
  • navigate around in an Integrated Development Environment in order to efficiently produce quality applications;
  • develop good software testing strategies.
Demonstrated the communication skills necessary to:
  • work in a team to come up with an integrated business software solution
explain their design and testing strategies in writing and in person through interviews.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1 Programming Concepts and Java - variables, operators, expressions, control structures, recursion, class structure, collections, primitive types, object types, exceptions, I/O, file I/O Tutorial labs commence in Week 1 of semester. This week's exercise is a revision of prerequisite knowledge.
2 Object oriented Concepts - classes, objects, methods, attributes, message passing, constructors, inheritance, polymorphism, encapsulation, visibility, abstraction, packages, interacting classes, association, aggregation, composition  
3 Inheritance - subclasses, subtyping, substitution, overriding, types of inheritance, access modifiers  
4 Inheritance - abstract classes, multiple inheritance, interfaces, inner classes, enumerations  
5 Testing, testing tools (JUnit)  
6 GUI - event handling, components, layout, AWT and Swing libraries  
7 Persistence: Java database connectivity, more file I/O Assignment 1 due Week 7 (Friday 11:55pm)
8 Program Design - design techniques (responsibility driven design), Parnas' principles, design representation (UML)  
9 Program design - coupling and cohesion, Law of Demeter, Design by Contract, Assertions, Refactoring  
10 Design Patterns - decorator, singleton, factory, observer, etc., frameworks  
11 Software development methodologies, agile methods  
12 Bringing it all together - Revision Assignment 2 due Week 12 (Friday 11:55pm)
  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.

Assessment Summary

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

Assessment Task Value Due Date
Assignment 1 20% Week 7 (Friday 11:55pm)
Assignment 2 20% Week 12 (Friday 11.55pm)
Examination 1 60% To be advised

Teaching Approach

Lecture and tutorials or problem classes
Lectures are used to present new concepts and to present example code that uses these concepts.
Practicals are used to give you hands-on experience at programming using the newly taught concepts.

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

Participation

  • Assessment task 1
    Title:
    Assignment 1
    Description:
    The design and implementation of an application employing the principles introduced in the early to mid part of the semester.

    Details will be made available in the assignment specification.
    Weighting:
    20%
    Criteria for assessment:

    This is an individual assignment and must be entirely your own work.

    Submissions will be judged on their compliance with the stated functional requirements, code and design principles presented in the unit.

    Assessment of this assignment may be subject to an interview should the marker feels necessary.

    Due date:
    Week 7 (Friday 11:55pm)
  • Assessment task 2
    Title:
    Assignment 2
    Description:
    The design and implementation of an application employing the principles introduced in the mid to later part of the semester.

    Details will be made available in the assignment specification.
    Weighting:
    20%
    Criteria for assessment:

    This is an individual assignment and must be entirely your own work.

    Submissions will be judged on their compliance with the stated functional requirements, code and design principles presented in the unit.

    Assessment of this assignment may be subject to an interview should the marker feels necessary.

    Due date:
    Week 12 (Friday 11.55pm)

Examinations

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

Learning resources

Reading list

The following may provide useful extra reading for this unit. Copies of these are available in the Library (on reserve, one day loan or in the normal circulation).

Java Foundations, Lewis, De Pasquale & Chase, (Pearson Education), 2008 

Big Java (4th Edition), Cay Horstman (John Wiley & Sons), 2010 

Java Programming - from Problem Analysis to Program Design (3rd Edition), D. S Malik (Thomson), 2008

Thinking in Java (4th Edition), Eckell (Prentice Hall), 2006

Absolute Java (3rd Edition), Savitch (Addison Wesley), 2008

Monash Library Unit Reading List
http://readinglists.lib.monash.edu/index.html

Feedback to you

Types of feedback you can expect to receive in this unit are:
  • Informal feedback on progress in labs/tutes
  • Graded assignments with comments
  • Interviews
  • Other: Staff responses to queries posted on discussion forums

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.

Prescribed Software

You must have the Java SE 6 (or later) Software Development Kit (called the JDK) installed on your computer. This software can be downloaded for free from the internet by going to http://www.oracle.com/technetwork/java/javase/downloads/index.html and clicking on the 'download' button in the JDK column.

Prescribed text(s)

Limited copies of prescribed texts are available for you to borrow in the library.

Barnes and Kolling. (2011). Objects First with Java: A Practical Introduction Using BlueJ. (5th Edition) Prentice Hall (ISBN: 9780132835541).

Recommended Resources

Useful Software

Whilst the JDK provides the compiler and runtime interpreter for the Java language, you will most likely want to make use of an Integrated Development Environment (IDE). You may use any IDE that you are comfortable with. Examples of IDE are BlueJ, Eclipse, JCreator and NetBeans. 

Recommended text(s)

Stuart Reges and Marty Stepp. (2011). Building Java Programs: A Back to Basics Approach. (2nd Edition) Addison Wesley (ISBN: 0-136-09181-4).

Other Information

Policies

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

Based on previous student evaluations, we decided:

  1. To provide more examples in the lecture to help with the understanding of concepts.
  2. To improve the sequencing of certain topics.  
  3. To focus on programming skills rather than the implementation of prototype features in all practical assignments.
  4. To align the assessment requirements with students' undertanding of concepts rather than prototype features. The alignment will be done based on weekly learning objectives.

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