FIT3077 Software engineering: architecture and design - Semester 2, 2010

Clayton

Prerequisites

Prohibitions

Teaching approach

There will be two one-hour lectures per week in this unit. During lectures, the lecturer will present the theory underlying the topics in the unit, and illustrate this with concrete examples.

 There will also be a one-hour 'practice class' for the unit. The lecturer and tutors (if any) will be present for the practice class. Students are expected to work on example problems or their assignments during the practice class, and ask the teaching staff for assistance when necessary. Teaching staff may occasionally choose to explain a common problem to the whole class.

 Note that a practice class is not a tutorial. It is time for you to work on the example problems provided, with a staff member present to answer any questions you might have. To get value from the practice class, it is vital that you attempt the example problems provided.

 The practice classes are intended to be the primary mechanism for consultation in this unit.

Timetable information

For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/

Tutorial allocation

On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.its.monash.edu.au/

Unit Schedule

*Please note that these dates may only apply to Australian campuses of Monash University. Off-shore students need to check the dates with their unit leader.

Improvements to this unit

The venue for the practice classes has been changed from flat rooms to laboratories. This is so that students can work on their assignments during practice class time, and, more importantly, demonstrate their work in progress to unit staff to receive feedback and advice.

Prescribed text(s) and readings

Recommended text(s) and readings

• Fowler M., UML Distilled: A Brief Guide to the Standard Object Modeling Language, Addison-Wesley, 3rd ed., 2003.
• Gamma E., Helm R., Johnson R., Vlissides J. M., Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley, 1994.
• Martin R. C., Design Principles and Design Patterns, 2000.
  • This and other Robert C. Martin articles are made available through the MUSO site for the unit.
• Fowler M., Analysis Patterns: Reusable Object Models, Addison-Wesley, 1996.
• Fowler M., Beck K., Brant J., Opdyke W., Roberts  D., Refactoring: Improving the Design of Existing Code, Addison-Wesley, 1999.
• Bass L., Clements P. and Kazman R., Software Architecture in Practice, Addison-Wesley, 2nd ed., 2003.
  • full text available electronically through the Monash library
• Allen, P and Schlamann, H., Service Orientation: Winning Strategies and Best Practices, Cambridge University, 2006.
  • full text available electronically through the Monash library

Required software and/or hardware

You will need access to:

• A tool for creating UML diagrams, such as Rational Rose, Visual Paradigm, etc.
• An object-oriented programming language

On-campus students may use the software that is installed in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook.

Equipment and consumables required or provided

Study resources

Study resources we will provide for your study are:

• Weekly detailed lecture notes outlining the learning objectives, discussion of the content, and required readings;
• Regular practice class exercises, with feedback and solutions provided in the practice classes;
• Assignment specifications;
• A sample examination and suggested solutions presented in the week 13 lectures;
• Discussion groups;
• This Unit Guide outlining the administrative information for the unit;
• The unit web site on MUSO, where resources outlined above will be made available.

Overview

Faculty assessment policy

To pass a unit which includes an examination as part of the assessment a student must obtain:

• 40% or more in the unit's examination, and
• 40% or more in the unit's total non-examination assessment, and
• an overall unit mark of 50% or more.

If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit.

Assignment tasks

Assignment coversheets

Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.

Assignment submission and return procedures, and assessment criteria will be specified with each assignment.

Assignment submission and preparation requirements will be detailed in each assignment specification. 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.

• Assignment task 1

  Title:

  UML Design Assignment

  Description:

  Students will be provided with software requirements scenarios for which they must produce a conceptual design for an object-oriented solution. This design must be described using UML diagrams. The purpose of this assignment is to reinforce UML knowledge and ensure that students are ready for the large assignment.

  Weighting:

  20%

  Criteria for assessment:

  Designs will be assessed for completeness with respect to the specification provided, correct use of UML notation, and design quality.

  Due date:

  Friday Week 4

• Assignment task 2

  Title:

  Team Software Architecture Assignment

  Description:

  This is a team assignment. Students will work on it in pairs. This assignment will have two stages, each requiring students to analyse a problem, design a solution, and implement it in an object-oriented programming language. The second stage will build on the first, and the ease with which the students' stage one design can be extended for stage two will depend on appropriate use of architecture and design knowledge presented in this unit.
  
  The main focus of the assignment is on the application of the design patterns and principles presented in lectures. Simply meeting the external functional requirements for the system is not sufficient to pass this assignment.

  Weighting:

  40%

  Criteria for assessment:

  Teams will be assessed on the basis of their submitted design documentation and code, as well as an interview. Both team members will be required to demonstrate knowledge and understanding of all parts of their design.

   Designs and code will be assessed for quality, including extensibility and appropriate use of design patterns. Completeness of code functionality with respect to the problem requirements  will also be assessed.

  Due date:

  Stage1 - Friday Week 9, Stage 2 - Friday Week 12

Examination

• Weighting:

  40%

  Length:

  3 hours

  Type (open/closed book):

  Closed book

  Electronic devices allowed in the exam:

  None

Due dates and extensions

Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.

Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.

A copy of the email or other written communication of an extension must be attached to the assignment submission.

Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html

Late assignment

Return dates

Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.

Feedback

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

Informal feedback on progress in labs/tutes

Graded assignments with comments

Interviews