BN315 - Enterprise Architecture
Credit Points: 15 credit points
Workload: 48 hours
Prerequisite: BN331 Software Quality Assurance and Testing
Aims & Objectives
This is a sixth trimester elective unit out of a total of 12 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 enterprise architecture and applying critical skills in enterprise architecture software. For further course information refer to: http://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 Enterprise Architecture (EA). The focus is on EA methods and techniques to describe how to plan, implement and govern a program of work to improve business functions by aligning IT with business drivers. This is the role of enterprise-level architecture. Students will describe and apply EA concepts and techniques within the context of case studies. Students gain the knowledge and skills to understand and describe an EA program.
This unit will cover the following topics:
- EA: definitions, meaning of EA, need for EA.
- The context of EA: business and IT cycles.
- Business-IT alignment.
- The EA process: Align, Elaborate, and Govern.
- IT planning in the context of EA.
- The value of EA.
- Change Management.
- Case studies in Enterprise Architecture.
4.1 Course Learning Outcomes
The Course learning outcomes applicable to this unit are listed on the Melbourne Institute of Technology’s website: www.mit.edu.au
4.2 Unit Learning Outcomes
At the completion of this unit students should be able to:
a. Explain what constitutes value for an organisation.
b. Lead a discussion on the role of EA to support business strategic goals through IT alignment, planning and governance.
c. Describe enterprise-level architectural views for the business, information, technology, and application domains.
d. Report on the relationship between EA and other architectures such as system, solution, data, application and technology.
e. Investigate the appropriate use of industry EA methods and frameworks.
f. Report on the current and future state for a portfolio of IT applications.
g. Interpret a roadmap process for the IT portfolio to support long-term business strategy.
This unit will cover the content below:
|Week #||Lecture Topic||Laboratory and Tutorial|
|1||Enterprise Systems||ERP, XML Technologies, CRM. Communication: Middleware, RPC|
|2||Different Architecture||ORB, MOM, SOA|
|3||Introduction to EA concepts||EA concepts – definition, benefits, challenges, organisational structure, enterprise architecture and solution architectures relationship, domain models (business, information, application, and technology), IT planning and governance, change management, EA principles and standards. The evolution of a city as a metaphor.|
|4||Business strategy, IT assessments and planning||Business strategy, IT assessments and planning – roles of business strategy in enterprise architecture, assessments of current state enterprise architecture, definition of future state enterprise architecture, identification of opportunities for improvement (operational, business processes/functions, etc), IT planning to support transformation to future state enterprise architecture. Business and IT alignment. Strategy maps.|
|5||EA methods and frameworks||Architecture development methods overview, overview of industry methods and frameworks – Open Group Architectural Framework TOGAF, Zachman.|
|6||Mid Term Test|
|7||IT governance and change management||Role of governance and change management, benefits, challenges, governance review board (architectural and solution level) – structure and processes, change management board – structure and processes.|
|9||Applications architecture||Applications architecture: analysis and modelling application software (inventories and diagrams) and interfaces for an organisation.|
|10||Technology architecture||Technology architecture: analysis and modelling middleware, hardware, operating systems, runtime platforms, networks for an organisation.|
|11||Quality, Testing.||Methodology on Quality, Testing Strategies|
|Assessment Task||Due Date||A||B||Learning Outcomes Assessed|
|Formative Assignment 1 Part A||Week 3||8%||b-c|
|Assignment 1 Part B||Week 7||17%||b-c|
|Assignment 2||Week 11||25%||a-b, d-e|
|Laboratory and Problem Based Learning participation & submission||Week 2 – 11||10%||a-e|
|Final Examination (2 hours)||40%||a-e|
Task Type: Type A: unsupervised, Type B: supervised.
Textbook and Reference Materials
- E. Thomas, Service Oriented Architecture: Concept, Technology and Design, Prentice Hall, 2016.
- S. A. Bernard, An Introduction to Enterprise Architecture, 3rd ed., AuthorHouse, 2012.
- 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.
- Federal Enterprise Architecture, http://www.whitehouse.gov/omb/e-gov/fea/
- Handbook of Software Architecture, http://www.handbookofsoftwarearchitecture.com/
- Microsoft Architecture Resource Centre, http://www.microsoft.com/architecture/
- TOGAF Version 9 Enterprise Edition, http://www.opengroup.org/togaf/
Adopted Reference Style: IEEE
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|
|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.|