Software Systems Architecture (8745.4)

CLOSED FOR FUTURE ENROLMENT.

Availability

Unit Outlines

To view your Unit Outline, click View to log in to MyUC and access this information, or visit your unit's online teaching site.

• Semester 2, 2018, ON-CAMPUS, GBCA-MELB (182382) - View
• Semester 2, 2018, ON-CAMPUS, BRUCE (182384) - View
• Semester 2, 2017, ON-CAMPUS, SWSI-LVPL (174763) - View
• Semester 2, 2017, ON-CAMPUS, GBCA-MELB (174764) - View
• Semester 2, 2017, ON-CAMPUS, BRUCE (166102) - View
• Semester 2, 2016, FLEXIBLE, UC-MELB (150721) - View
• Semester 2, 2016, FLEXIBLE, SWSI-LVPL (150720) - View
• Semester 2, 2016, FLEXIBLE, BRUCE (150718) - View
• Semester 2, 2015, FLEXIBLE, UC-MELB (147996) - View
• Semester 2, 2015, FLEXIBLE, SWSI-LVPL (147995) - View
• Semester 2, 2015, FLEXIBLE, BRUCE (147993) - View

If a link to your Unit Outline is not displayed, please check back later. Unit Outlines are generally published by Week One of the relevant teaching period.

Syllabus

In this unit, the students will learn how to produce software architecture design from system requirements; The course covers terms, concepts and techniques used in the design of software architectures, including architectural requirements, architectural styles, architecture documentation and architecture evaluation. Students will learn about the role of architecture and architects in software engineering. Modern architectures such as service-oriented and cloud architecture and wireless systems architecture are also covered in detail.

This unit will be co-taught with unit 8746 Software Systems Architecture G.

Learning Outcomes

On successful completion of this unit, students will be able to:

1. Demonstrate a firm understanding of the principles of software architecture, architectural best-practices, and how architecture is used in modern software engineering;

2. Understand the role of a software architect in software engineering practice;

3. Examine and compare various architecture styles and solutions;

4. Design an architecture that reflects and balances the different needs of its stakeholders; and

5. Communicate the architecture to stakeholders and demonstrate that it has met their requirements.

Assessment Items

Contact Hours

Lecture - 2 hrs per week Tutorial - 1 hour per week

Prerequisites

At least 24 credit points of the course.

Corequisites

None.

Assumed Knowledge

Basic understanding of software systems and their types. Some programming experience in a language such as Java or C#.

Equivalent Units

None.