Skip to main content

We are aiming for an incremental return to campus in accordance with guidelines provided by NSW Health and the Australian Government. Until this time, learning activities and assessments will be planned and scheduled for online delivery where possible, and unit-specific details about face-to-face teaching will be provided on Canvas as the opportunities for face-to-face learning become clear.

Unit of study_

COMP5348: Enterprise Scale Software Architecture

This unit covers topics on software architecture for large-scale enterprises. Computer systems for large-scale enterprises handle critical business processes, interact with computer systems of other organisations, and have to be highly reliable, available and scalable. This class of systems are built up from several application components, incorporating existing "legacy" code and data stores as well as linking these through middleware technologies, such as distributed transaction processing, remote objects, message-queuing, publish-subscribe, and clustering. The choice of middleware can decide whether the system achieves essential non- functional requirements such as performance and availability. The objective of this unit of study is to educate students for their later professional career and it covers Software Architecture topics of the ACM/IEEE Software Engineering curriculum. Objective: The objective of this unit of study is to educate students for their later professional career and it covers topics of the ACM/IEEE Software Engineering curriculum.

Code COMP5348
Academic unit Computer Science
Credit points 6
Assumed knowledge:
Experience with software development as covered in SOFT2412 or COMP9103 and also COMP2123 OR COMP2823 OR INFO1105 OR INFO1905 (or equivalent UoS from different institutions).

At the completion of this unit, you should be able to:

  • LO1. produce written evaluation of different architectures and/or of different technologies
  • LO2. work in small teams of people with diverse skills and backgrounds, to complete demanding tasks which are loosely defined and require rapid learning of new concepts
  • LO3. understand the role of a software architect; respect what he/she is doing, and why; know when to involve him/her
  • LO4. recognise the relationship between different software architecture choices, and their impact on various non-functional attributes of the software
  • LO5. demonstrate broad knowledge of common architectural approaches for enterprise software, as well as detailed skills working with some technologies available to implement those approaches
  • LO6. carry out performance analysis, explain performance measurement principles, and identify suitable approaches for state management in face of concurrency.

Unit outlines

Unit outlines will be available 2 weeks before the first day of teaching for 1000-level and 5000-level units, or one week before the first day of teaching for all other units.

There are no unit outlines available online for previous years.