enterprise architecture management -...

26
Enterprise Architecture Management - Conclusion Knut Hinkelmann

Upload: others

Post on 12-Sep-2019

40 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Enterprise Architecture Management -ConclusionKnut Hinkelmann

Page 2: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 2Prof. Dr. Knut HinkelmannMSc BIS

Students‘ Feedback

„Too much self-study including homework and assignment“

„Less work at home“

■ Module has 6 ECTS à 30 hours

■ Contact lessons are 60 hours

■ Work at home is 120 hours

Page 3: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 3Prof. Dr. Knut HinkelmannMSc BIS

Students‘ Feedback

„Feedback too late“

„Upload slides earlier than 1 hour before lecture“

■ Oops I did it again

■ Sorry!

Page 4: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 4Prof. Dr. Knut HinkelmannMSc BIS

Students‘ Feedback: Topics, Complexity

„reduce complexity“

„less logic“

„I don't see myself ever using the logical expression to the extent weelaborated on them“

„Sometimes a little bit abstract“

„business rules section was too long“

■ Heterogenous requirements and objectives♦ Not too much repetition from bachelor♦ prepare for other modules of the MSc BIS♦ New technologies and trends♦ …

Page 5: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 5Prof. Dr. Knut HinkelmannMSc BIS

Students‘ Feedback: Topics, Complexity

„sometimes discussions become too detailed“

„sometimes we discussed a bit too long about details“

„classroom exercises were good but the following discussionssometimes where too long“

■ Heterogenous group

■ Going into depth sometime is necessary to understand

■ But I will take the critique into consideration for future

Page 6: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 6Prof. Dr. Knut HinkelmannMSc BIS

Material

■ „power point slides were not always enough“

Specifications of Standards: BPMN, UML, SBVR

Page 7: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 7Prof. Dr. Knut HinkelmannMSc BIS

Students‘ Feedback

„Enterprise Architecture as we learned in class is not done on that detail level in more than 90% of the swiss companies“

■ Correct, but♦ A university study is an education not for the present time but for

future♦ Companies have parts of an enterprise architectures

● they do not call it EA but business process management, infrastructure plan, configuration data

● distributed over different tools, files, …

Page 8: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 8Prof. Dr. Knut HinkelmannMSc BIS

Students‘ Feedback

„One more presentation about designing business/processmodel and business rule to compare what I learn and whatactually going on in practice“

■ What about doing it today?

Page 9: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 9Prof. Dr. Knut HinkelmannMSc BIS

Deriving an Enterprise Architecture

Page 10: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 10Prof. Dr. Knut HinkelmannMSc BIS

Perspectives on the Enterprise Architecture

(Hanschke 2010, p. 99)

Page 11: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 11Prof. Dr. Knut HinkelmannMSc BIS

What Benefits does EAM deliver?

■ Potential benefits can be identified by stakeholder analysis♦ Identify stakeholder who will potentially benefit

■ Benefits is largely qualitative

■ Benefits can be illustrated by presenting negative examples♦ „How can we find out the answer to this particular question with

the documentation we have right now?“

Page 12: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 12Prof. Dr. Knut HinkelmannMSc BIS

Planning Levels of the Enterprise Architecture

(Hanschke 2010, p. 108)

Page 13: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 13Prof. Dr. Knut HinkelmannMSc BIS

Best Practice Enterprise Architecture

Page 14: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 14Prof. Dr. Knut HinkelmannMSc BIS

Logical Data Model of the Best PracticeArchitecture

All the buildingblocks can belinked by meansof relationships

(Hanschke 2010, p. 125)

Page 15: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 15Prof. Dr. Knut HinkelmannMSc BIS

IT Landscape Management

Page 16: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 16Prof. Dr. Knut HinkelmannMSc BIS

Example Meta-Model of a Business Landscape

All the building block can be linked by means of relationships(Hanschke 2010, p. 91)

Page 17: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 17Prof. Dr. Knut HinkelmannMSc BIS

Example of a Business Landscape Diagram: RelatingBusiness Functions to Processes and Organisation

Page 18: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 18Prof. Dr. Knut HinkelmannMSc BIS

Example of a Technical Landscape Diagram

Page 19: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 19Prof. Dr. Knut HinkelmannMSc BIS

Mapping Talbe between Business Objects and Business Processes

Page 20: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 20Prof. Dr. Knut HinkelmannMSc BIS

Example of a Process Map

Hierachical relation betweenprocesses: On top-levelthere is a process map. Each of the elementsrepresents either

• a more detailedprocess map or

• a process model

Page 21: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 21Prof. Dr. Knut HinkelmannMSc BIS

Example Business Process Model in BPMN

Mitarbeiter

Hotel buchen

Stornierung Flug‐ oderHotelbuchung einleiten

Mit dem Auto fahren

Reisebüro

Innendienst

AngestellerReisebüro Kundendaten prüfen

Hotelzimmernachfragen

Bestätigung erhalten

Antwort verfassen

Hotel Anfrage erhalten Antwort sendenAnfrage bearbeiten

Flug buchen

Flug stornieren

Reiseanfrage anlegen

Reiseanfrage akzeptiert

Der Schrägstrich der Kantedrückt aus, dass dies der"Standard“‐Verlauf ist.

Reiseanfrage abgelehnt

Hotel stornieren

Subprocess:Weil die Reiseanfrage abgelehnt wurde,werden Flug und Hotel storniert.Deshalb müssen die Mitarbeiter das Auto nehmen.

Das ist derinitiale Startdes Prozesses.

Indem es eine Exception wirft, erzwingtdieses Ereignis die Kompensation von„Flug buchen“ und „Hotel buchen“durch die Stornierung von Flug undHotel.

Nachrichtenfluss:Die Antwort wird vom Telefon‐Agenten des Reisebüros zumMitarbeiter gesandt.

Route prüfen Fahren

Page 22: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 22Prof. Dr. Knut HinkelmannMSc BIS

Enterprise Architecture in Companies

■ Companies have parts of an enterprise architectures♦ they do not call it EA but business process management,

infrastructure plan, configuration data management♦ distributed over different tools, files, …

■ There are tools usually covering parts of the enterprisearchitecture♦ Business Process Management Systems, e.G. Adonis, ARIS♦ Workflow Management Systems, e.g. Xpert.ivy♦ Business Rules Management Systems. e.g. JRules

■ Some very broad tools, e.g. Enterprise Architect

Page 23: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 23Prof. Dr. Knut HinkelmannMSc BIS

Business Process Management deals with partof the Enterprise Architecture

All the building block can be linked by means of relationships(Hanschke 2010, p. 91)

Page 24: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 24Prof. Dr. Knut HinkelmannMSc BIS

Enterprise Content Management: Relating Business Objects and Business Processes

We use this kind of mappingtable to identify documentlifecycles for

• document managementsystems

Page 25: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 25Prof. Dr. Knut HinkelmannMSc BIS

Infrastructure Management relates to Enterprise Architecture to Operational Data

■ Configuration Management Database♦ contains all units of

hardware, software, environment and services

■ Infrastructure landscaperelates these operational-level data with theapplications

ConfiurationManagementData

Page 26: Enterprise Architecture Management - Conclusionknut.hinkelmann.ch/lectures/ISA2010/ISA-9_EAM_Conclusion.pdf · Information Systems Architecture - Enterprise Modeling 3 Prof. Dr. Knut

Information Systems Architecture - Enterprise Modeling 26Prof. Dr. Knut HinkelmannMSc BIS

Relation of Enterprise Architecture to otherModules■ The module can be regarded as setting the ground for many

other modules, e.g.♦ Business Process Management

● modelling and managing business processes and their context

♦ IT-Governance and Compliance Management● IT-Governance: Alignment of Business and IT● Compliance Management: Implementing regulation which can be

modeled with business rules

♦ Knowledge Engineering● Making knowledge operational logic, rules, ontologies