BN314 - System Architecture

Credit points: 15 credit points

Workload: 48 hours

Prerequisite: N/A

Co-requisite: N/A

Aims & objectives

This is an elective unit out of a total of 24 units in the Bachelor of Networking (BNet). This unit addresses the BNet course learning outcomes and complements other courses in a related field by developing students’ specialised knowledge in system architecture and applying critical skills in software: Enterprise Architecture. For further course information refer to: https://www.mit.edu.au/study-with-us/programs/bachelor-networking . This unit is part of the AQF Level 7 (BNet) course.

This unit provides students with an in depth discussion of the foundation concepts, methods and principles of System Architecture (SA) and Software Engineering. The focus is on Software Engineering methods and techniques to describe how to plan, design, implement and govern a program of work to improve the function by aligning IT with business requirements.  This is the role of System Architect.  Students will describe and apply System Architect concepts and techniques within the context of case studies. Students will gain the knowledge and skills to understand and describe an Application program.
This unit will cover the following topics:
1. System Architecture.
2. Service Oriented Architecture and Service Design.
3. Requirement Engineering, Reverse Engineering.
4. Architectural Patterns.
5. System Test Plans.
6. Current Trends in System Architecture.

Learning outcomes

On successful completion of this unit, students should be able to:
a. Create specifications for the design and development of software systems.
b. Analyse and model business practices, system functionality and behaviour.
c. Compare and contrast different approaches to system analysis and design, such as object oriented, agile, and service oriented techniques.
d. Produce, adopt and implement system test plans.
e. Analyse and model the Cloud Infrastructure (SaaS, PaaS, IaaS).
f. Design and deploy functional solutions, such as initiating, analysing, and implementing system plans.
g. Investigate, and analyse system processes, procedures and work practices.

Assessment

Assessment Task Unit Learning Outcomes Weighting
1. Midterm Test c-f* 10%
2. Assignment 1 c-g* 15%
3. Assignment 2 [Group] c-g* 25%
4. Laboratory participation & submission a-g* 10%
5. Final Examination [2 hours] a-g* 40%
TOTALS   100%

*refer to learning outcomes above.

Teaching method

Lecture: 2 hours
Tutorial/Workshop: 2 hours
Face to Face

Textbook and reference materials

Textbook

  • J. W. Satzinger, R. B. Jackson, S. D. Burd, Systems Analysis and Design in a Changing World, Cengage Learning, 7th Edition, 2016.
  • S. Tilley , H. J. Rosenblatt, Systems Analysis and Design, Cengage Learning, 11th Edition,  2017.

Reference reading

  • S. D. Burd, Systems Architecture, 7th ed., Cengage Learning, 2015.
  • E. Thomas, Service Oriented Architecture: Concept, Technology and Design, Prentice Hall, 2016.
  • P. Wik, Service-oriented Architecture: Principles and Applications, Kindle Ed. A Blue Kitten Book, 2016.
  • B. Michael, Incremental Software Architecture: A Method for Saving Failing IT Implementations, 1st ed. Wiley, 2016.
  • S. Tilley and H. J. Rosenblatt, System Analysis and Design, 11th ed. Course Technology, 2016.

Graduate attributes

MIT is committed to ensure the course is current, practical and relevant so that graduates are “work ready” and equipped for life-long learning. In order to accomplish this, the MIT Graduate Attributes identify the required knowledge, skills and attributes that prepare students for the industry.
The level to which Graduate Attributes covered in this unit are as follows:

Ability to communicate Independent and lifelong learning Ethics Analytical and problem solving Cultural and global awareness Team work Specialist knowledge of a field of study

Legend

Levels of attainment Extent covered
The attribute is covered by theory and practice, and addressed by assessed activities in which the students always play an active role, e.g. workshops, lab submissions, assignments, demonstrations, tests, examinations.
The attribute is covered by theory or practice, and addressed by assessed activities in which the students mostly play an active role, e.g. discussions, reading, intepreting documents, tests, examinations.
The attribute is discussed in theory or practice; it is addressed by assessed activities in which the students may play an active role, e.g. lectures and discussions, reading, interpretation, workshops, presentations.
The attribute is presented as a side issue in theory or practice; it is not specifically assessed, but it is addressed by activities such as lectures or tutorials.
The attribute is not considered, there is no theory or practice or activities associated with this attribute.