• Tidak ada hasil yang ditemukan

Enterprise Architecture Syllabus4

N/A
N/A
Info
Unduh - Bebas
Protected

Academic year: 2025

Membagikan "Enterprise Architecture Syllabus4"

Copied!
6
0
0

Memuat.... (Lihat teks lengkap sekarang)

Unduh sekarang ( 6 Halaman )

Teks penuh

(1)

CPIS352: IT ENTERPRISE ARCHITECTURE

Syllabus Fall 2012

Instructor Information

Instructor: Dr Adnan Mustafa AlBar – Faculty of Computing and Information Technology, IS Dept.,

Office: Building 31, R# 104

Office Hours: 9-10 AM S,M, other times by appointment Web: ambar.kau.edu.sa

E-mail: [email protected]

Course Description

Enterprise Architecture (EA) is the analysis and design of an enterprise in its current and future states from a strategy, business and technology perspective. This course is provides an exposure to the foundational concepts of enterprise architecture. The course will provide students with the foundational knowledge needed to understand how EA serves to integrate strategic, business, and technology planning methods, which support enterprise-wide information technology resource development and governance in the context of business requirements. This course is

designed to cover the theory, frameworks, principles and best practices of enterprise architecture then move to a practical, comprehensive approach to delivering the subject matter involving real-world case studies and project discussions.

Course Objectives

At the conclusion of this course students will be able to:

• Understand the foundational elements of EA

• Discuss and compare contemporary EA frameworks

• Understand EA concepts and practices

(2)

• Articulate how enterprise architecture supports the strategic objectives of the organization

• Understand the fundamentals of enterprise architecture development and maintenance

• Understand the importance of effective governance for successful enterprise architecture development and adoption

Course Materials

All course readings can be found at the course web site at:

Evaluation

Assignments &

Exams Points

(Weight) Description Team Class

Discussions

5 Each team will lead two assigned class discussions

EA Case

Outline 5 Draft of outline for team case project

EA Case Draft 5

Final EA Case 5 Final Class

Presentation

5 Team case presentation to the class Team Member

Evaluation 5 Each student will be evaluated by his or her own team members and assigned a grade based on the quality of their participation and contribution to the team’s efforts.

Lab 20 Lab participation will be evaluated based on activities, attendance, contributions to

project discussions.

Mid Term Exam 25

Final Exam 25

Total 100

Grading Scale

A 94-100; A- 93-90; B+ 89-86; B 85-82; B- 81-79; C+ 78-76; C 75-70; D 69-60; F 59-0

(3)

Course Schedule

Week Topic Assignment

Module: Enterprise

Architectural Concepts 1 Introduction / Foundational

Concepts

Readings:

Topic 1 and Topic 2

2 Team Case Assignments

3 Understanding Organizations and Enterprise Alignment

Readings:

Topic 3 and Topic 4

Read Case Study Development Guidelines 4

The Enterprise Architecture

“Stack”

Readings:

Topic 5 and Topic 6

Module: Initiating Enterprise

Architecture

5

Planning for Enterprise Architecture

Readings:

Topic 7, Topic 8

6 The Enterprise Architecture Governance Process

Do Assigned Readings Prior to Class

Topic 10

7

Enterprise Architecture Change Management

Do Assigned Readings Prior to Class

Topic 11 Module: Enterprise

Architecture Implementation

8

Exam 1 Readings:

Topic 9

(4)

Building and Maintaining Enterprise Architecture

9

Leadership, Decision Making, and Team Formation for Enterprise Architecture

Readings:

Topic 12 and Topic 13

10

Enterprise Architecture Success Factors

Value and Risk Analysis for Enterprise Architecture

Readings:

Topic 14

Readings:

Topic 15

11

Comparative Analysis of Popular EA Frameworks and Methodologies

Readings:

Topic 16

Topic 17, Topic 18

12 Course Summary

Exam 2

13 Team Presentations

Submit Final Team Case Study

Document

EA References:

1. EA @ UC Irvine:

http://apps.adcom.uci.edu/EnterpriseArch/index.html

2. Government of Canada, Federated Architecture, Iteration One:

http://www.tbs-sct.gc.ca/fap-paf/documents/iteration/iteration04_e.asp 3. State of North Carolina: NC statewide Technical Architecture:

http://www.ncsta.gov/

(5)

4. EA @ State of Texas:

http://www.dir.state.tx.us/ace/domains/index.htm 5. EA @ US Federal Government:

http://www.whitehouse.gov/omb/egov/a-1-fea.html 6. Institute for Enterprise Architecture Developments:

http://www.enterprise-architecture.info/

7. Enterprise Information Architecture @ IBM:

http://researchweb.watson.ibm.com/journal/sj/464/vayghan.html 8. Zachman Enterprise Architecture Framework:

http://www.zachmaninternational.com/index.php 9. TOGAF: http://www.opengroup.org/togaf/

10. IBM System Journal special issue on SOA:

http://researchweb.watson.ibm.com/journal/sj44-4.html 11. Enterprise information architecture journey at IBM:

http://www.research.ibm.com/journal/sj/464/vayghan.html 12. The Open Group Service Integration Maturity Model (OSIMM):

https://www.opengroup.org/projects/osimm/uploads/40/17990/OSIM M_v0.3a.pdf

13. An Introduction to Enterprise Architecture, Scott A. Bernard, AuthorHouse, 2005, ISBN: 1-4208-8050-0

14. Enterprise Architecture As Strategy, Jeanne W. Ross et al., Harvard Business School Press, 2006, ISBN:1-59139-839-8

15. Enterprise SOA, D. Krafzig, K. Banke, D. Slama, Prentice Hall, 2005, ISBN: 0-13-146575-9

16. IT Governance, Peter Weill & Jeanne Ross, Harvard Business School

Press, 2004, ISBN: 1-59139-253-5

(6)

17. Corporate Information Strategy and Management: Text and Cases 7th

Ed., Lynda M. Applegate et al., McGraw-Hill, 2007, ISBN: 0-07-

294775-6

Referensi

Unduh sekarang ( PDF - 6 Halaman - 136.92 KB )

Dokumen terkait

ANALISIS DAN PENGEMBANGAN SISTEM INFORMASI AKADEMIK DENGAN PERMODELAN ENTERPRISE ARCHITECTURE ZACHMAN FRAMEWORK PADA POLITEKNIK JAMBI

1) Menganalisis sistem informasi akademik Politeknik Jambi dalam proses bisnis organisasi.. 2) Mengembangan sistem informasi akademik dengan metode Enterprise

New Microsoft Word One-on-ones empower you to unearth issues before they become full-blown problems.

One-on-one meeting frequency. One-on-ones empower you to unearth issues before they become full-blown problems. Imagine these two scenarios: Scenario 1: In the first one, manager Mary meets with her direct reports once a week. She hears from one of her employees that there is some tension arising among the team and this helps Mary address it immediately before it becomes a major problem. Scenario 2: Manager Michael has never scheduled regular one-on-ones. After a couple of months, he realizes that there’s tension in the team, rumours about people, and some clashes between co-workers who aren’t working well together. No one was able to address this with Michael, mainly because he never sat down with each employee to ask about team dynamics and the challenges that he could help overcome as their manager. This is just one of many examples that show how one-on-ones empower you to proactively fix situations before they become big problems. From helping you solve team issues to allowing you to coach employees when they should be focusing on different priorities… one-on-one meetings can help you defuse workplace bombs before they explode. As Andy Grove argues: “The meeting should cover anything important that has happened since the last meeting: current hiring problems, people problems in general, and- very, very important- potential problems. Even when a problem isn’t tangible, even if it’s only an intuition that something’s wrong.” 4 Just like managers in the world’s most innovative companies, you can use one-on-ones as a powerful tool to stay updated about issues and provide your team with ongoing support. 4. One-on-ones provide the ideal environment to exchange feedback Imagine getting an email from your boss saying “we need to talk.” Unsurprisingly, receiving an email like that would cause many of us to freak out a little, and immediately think that we are in trouble (or the feeling of being sent to the principal’s office…). To try and prevent your team from these mini heart attacks, you can exchange feedback during your regularly scheduled one-on-ones. One-on-one meetings are the ideal scenario to ask for feedback about the company, the team, and your management style. Similarly, they’re the perfect moment (a private, face-to-face conversation) to give your employees helpful feedback on their performance. We discuss specific ways to ask for feedback and provide constructive criticism in chapter 5. . . . To sum up, there are many benefits you’re missing out on if you still haven’t scheduled regular one-on-ones. A few of them include increased productivity, better relationships with your teammates, and the ability to address issues proactively and exchange ongoing feedback. If you’re feeling motivated and ready to start scheduling, we think you’ll enjoy reading the next chapter! 2.1 One-on-one meeting frequency: How often do great managers meet with their employees? Before communicating your decision to schedule regular meetings with your teammates, you should spend some time deciding if you want to do it weekly or

Kingdom of Saudi Arabia

In that regard, the assignment contains questions that assess: 1 students’ thorough understanding in the concepts of network layers 2 standards and protocols Assessment Due Date Week

A New Model for Information Security Management in Service-Oriented Enterprise Architecture

The production of this model is shown in the following table: Table 2: Enterprise security architecture products ASSETS What MOTIVATION Why PROCESS How PEOPLE Who