This unit builds on introductory units to analysis and design. It provides the professional software engineer with advanced knowledge and skills in high-level architectural design, its theoretical foundations, industrial best practice, and relevant application context. In the software life-cycle, software architecture sits between analysis/specification and design/implementation. The field of software architecture has come of age with a thriving research community and numerous high-level models, methods, tools and practices widely used in industry.
2 hrs lectures/wk, 1 hr laboratory/wk
Workload commitments are:
CSE3308
FIT2001 and (FIT2004 or FIT2024 or CSE2304)
David Squire
Consultation hours: Consultation hours will be announced on the MUSO website. Making an appointment via email is strongly advised.
Ali Ahmed
Minh Ngoc Nhat Huynh
Examination (3 hours): 40%; In-semester assessment: 60%
| Assessment Task | Value | Due Date |
|---|---|---|
| UML Design Assignment | 20% | Week 4, Friday 23 March 2012 |
| Team Software Architecture Assignment | 40% | Week 9, Friday 4 May 2012 (Stage 1); Week 12, Wednesday 23 May 2012 (Stage 2) |
| Examination 1 | 40% | To be advised |
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 SETU, Student Evaluation of Teacher and Unit. 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, and on student evaluations, see:
http://www.monash.edu.au/about/monash-directions/directions.html
http://www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
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.
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
Please check with your lecturer before purchasing any Required Resources. Prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.
You will need access to:
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.
Fowler M.. (2003). UML Distilled. (3rd) Addison-Wesley.
Gamma E., Helm R., Johnson R., Vlissides J. M.. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. (1st) Addison-Wesley.
Fowler M.. (1996). Analysis Patterns: Reusable Object Models. (1st) Addison-Wesley.
Fowler M., Beck K., Brant J., Opdyke W., Roberts D.. (1999). Refactoring: Improving the Design of Existing Code. (1st) Addison-Wesley.
Bass L., Clements P. and Kazman R.. (2003). Software Architecture in Practice. () Addison-Wesley.
Allen, P and Schlamann, H.. (2006). Service Orientation: Winning Strategies and Best Practices. () Cambridge University Press.
| Week | Activities | Assessment |
|---|---|---|
| 0 | No formal assessment or activities are undertaken in week 0 | |
| 1 | Introduction to FIT3077; What is Software Architecture?; Object-Oriented Analysis using UML | |
| 2 | Object-Oriented Analysis using UML | Assignment 1 specification available |
| 3 | Principles of Object-Oriented Analysis and Design; Design Patterns | |
| 4 | Principles of Object-Oriented Design | Assignment 1 due Fri 23 March 2012 |
| 5 | Principles of Object-Oriented Design | Assignment 2, Stage 1 specification available |
| 6 | Design Principles and Design Patterns | |
| 7 | Analysis Patterns; Refactoring | |
| 8 | Software Architecture; Architectural Structures | |
| 9 | Documenting Software Architectures; The Model-View-Controller Architectural Pattern | Assignment 2, Stage 1 due Fri 4 May 2012; Assignment 2, Stage 2 specification available |
| 10 | Architecture and Design with COTS components | |
| 11 | Software Product Lines: Re-using Architectural Assets | |
| 12 | Service Orientation; Service-Oriented Architecture | Assignment 2, Stage 2 due Wed May 23 2012 |
| SWOT VAC | No formal assessment is undertaken 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 MUSO (Blackboard or Moodle) learning system.
Faculty Policy - Unit Assessment Hurdles (http://www.infotech.monash.edu.au/resources/staff/edgov/policies/assessment-examinations/unit-assessment-hurdles.html)
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.
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).
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.
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:
http://policy.monash.edu.au/policy-bank/academic/education/index.html
Key educational policies include:
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at www.monash.edu.au/students. For Sunway see http://www.monash.edu.my/Student-services, and for South Africa see http://www.monash.ac.za/current/
The Monash University Library provides a range of services and resources that enable you to save time and be more effective in your learning and research. Go to http://www.lib.monash.edu.au or the library tab in my.monash portal for more information. At Sunway, visit the Library and Learning Commons at http://www.lib.monash.edu.my/. At South Africa visit http://www.lib.monash.ac.za/.
Academic support services may be available for students who have a disability or medical condition. Registration with the Disability Liaison Unit is required. Further information is available as follows: