Handbook home
Software Design and Architecture (SWEN90007)
Graduate courseworkPoints: 12.5On Campus (Parkville)
About this subject
- Overview
- Eligibility and requirements
- Assessment
- Dates and times
- Further information
- Timetable(opens in new window)
Contact information
Semester 2
Overview
Availability | Semester 2 |
---|---|
Fees | Look up fees |
AIMS
One of the main challenges in developing enterprise-wide distributed systems is in choosing the right software architectures. In this subject students will study software architectures in depth and the principles, techniques and tools for creating, developing and evaluating software architectures
INDICATIVE CONTENT
Topics covered in this subject will be drawn from: design styles and architectural patterns; design strategies; domain specific architectures; evaluation of designs; architectural design for non-functional requirements; and modelling architectures.
Intended learning outcomes
INTENDED LEARNING OUTCOMES (ILO)
On completion of this subject the student is expected to:
- Analyse large scale and distributed systems and select appropriate architectures for them
- Evaluate architectures both qualitatively and quantitatively
- Make suitable trade-offs between different architectures
Generic skills
On completion of this subject students should have the following skills:
- Ability to apply knowledge of science and engineering fundamentals
- Ability to undertake problem identification, formulation, and solution
- Ability to utilise a systems approach to complex problems and to design and operational performance
- Proficiency in engineering design
- Ability to manage information and documentation
- Capacity for creativity and innovation
- Ability to function effectively as an individual and in multidisciplinary and multicultural teams, as a team leader or manager as well as an effective team member.
Last updated: 3 November 2022
Eligibility and requirements
Prerequisites
Code | Name | Teaching period | Credit Points |
---|---|---|---|
SWEN30006 | Software Modelling and Design |
Semester 1 (On Campus - Parkville)
Semester 2 (On Campus - Parkville)
|
12.5 |
AND
One of the following:
433-428 Software Processes and Management
SWEN90003 SWEN90008
Code | Name | Teaching period | Credit Points |
---|---|---|---|
SWEN90016 | Software Processes and Management |
Semester 1 (On Campus - Parkville)
Semester 2 (On Campus - Parkville)
|
12.5 |
Corequisites
None
Non-allowed subjects
Students cannot enrol in and gain credit for this subject and:
Code | Name | Teaching period | Credit Points |
---|---|---|---|
SWEN90002 | Engineering for Internet Applications | Not available in 2024 |
12.5 |
Recommended background knowledge
SWEN40004 Modelling Complex Software Systems
Inherent requirements (core participation requirements)
The University of Melbourne is committed to providing students with reasonable adjustments to assessment and participation under the Disability Standards for Education (2005), and the Assessment and Results Policy (MPF1326). Students are expected to meet the core participation requirements for their course. These can be viewed under Entry and Participation Requirements for the course outlines in the Handbook.
Further details on how to seek academic adjustments can be found on the Student Equity and Disability Support website: http://services.unimelb.edu.au/student-equity/home
Last updated: 3 November 2022
Assessment
Additional details
- A multi-staged, pair-based project in which students propose features of a system with properties commonly found in large-scale distributed enterprise systems, engineer an architectural design for that systems, and implement and evaluate it using industry-standard enterprise tools and frameworks. The project will consist of four reports totalling about 2500 words, requiring approximately 40-45 hours of work (40%). The four stages of the project are due in weeks 3 (nominate features of the system), 7 (architectural design and implementation), 10 (re-factored design and implementation), and 12 (performance evaluation) respectively. ILOs 1, 2, and 3 will be addressed by the pair project.
- A two-hour end-of-semester written examination during the exam period (60%).
Hurdle requirement: To pass the subject, a student must obtain:
- At least 50% overall
- At least 50% (15/30) in project work; and
- At least 50% (35/70) in the written examination.
Intended Learning Outcomes (ILOs) 1-3 will be addressed by both the pair project and the end-of-semester written exam.
Last updated: 3 November 2022
Dates & times
- Semester 2
Principal coordinator Alexi Lopez Lorca Mode of delivery On Campus (Parkville) Contact hours 36 hours, comprising of two 1-hour lectures and one 1-hour workshop per week Total time commitment 200 hours Teaching period 24 July 2017 to 22 October 2017 Last self-enrol date 4 August 2017 Census date 31 August 2017 Last date to withdraw without fail 22 September 2017 Assessment period ends 17 November 2017 Semester 2 contact information
Time commitment details
200 hours
Last updated: 3 November 2022
Further information
- Texts
Prescribed texts
None
- Subject notes
LEARNING AND TEACHING METHODS
The subject will be delivered through a combination of lectures and workshops. Students will also complete the architectural design, implementation, and evaluation of a system with features commonly found in large-scale distributed enterprise systems, which will reinforce the material covered in lectures.
INDICATIVE KEY LEARNING RESOURCES
A book of notes will be made available at the University of Melbourne bookshop at the start of the semester. The two key additional resources for the subject are:
- Fowler, Martin. Patterns of enterprise application architecture. Addison-Wesley Professional, 2003.
- Hohpe, Gregor, and Bobby Woolf. Enterprise integration patterns: Designing, building, and deploying messaging solutions. Addison-Wesley Professional, 2004.
CAREERS / INDUSTRY LINKS
Large-scale enterprise systems are present in almost every modern business. The ability to engineer and integrate such systems is a skill that has ever-increasing demand, and requires different techniques and principles than “programming in the large”.
There will be two lectures from industry-based lecturers who will describe their approaches to architectural design of large-scale distributed enterprise systems.
- Related Handbook entries
This subject contributes to the following:
Type Name Course Doctor of Philosophy - Engineering Course Master of Philosophy - Engineering Course Ph.D.- Engineering Specialisation (formal) Software with Business Informal specialisation Master of Engineering (Mechatronics) Informal specialisation Master of Engineering (Software) Specialisation (formal) Software Informal specialisation Master of Engineering (Software with Business) Specialisation (formal) Mechatronics - Available through the Community Access Program
About the Community Access Program (CAP)
This subject is available through the Community Access Program (also called Single Subject Studies) which allows you to enrol in single subjects offered by the University of Melbourne, without the commitment required to complete a whole degree.
Entry requirements including prerequisites may apply. Please refer to the CAP applications page for further information.
Additional information for this subject
Subject coordinator approval required
Last updated: 3 November 2022