identification and documentation of the state-of-the …...q3 q4 q1 q2 q3 q4 q1 q2 02.10. 05.12....

Chair of Software Engineering for Business Information Systems (sebis) Faculty of InformaticsTechnische Universität Münchenwwwmatthes.in.tum.de

Identification and Documentation of theState-of-the-Art Enterprise ArchitectureManagement Foundations Using a SemanticWiki Gloria Bondel, 16.01.2017, Munich

Introduction§ Motivation§ eam-initiative.org – a wiki-based knowledge community for EAM

Initial Utility of the eam-initiative.org§ Research Objectives§ Goal Achievement

Evaluation§ User Survey§ Community Activity Metrics§ Further Feedback§ Evaluation Summary

Future Work§ Next Steps

Outline

© sebis170116 Bondel Master Thesis Final Presentation 2

Motivation


[...] there seems to be a mystical mistsurrounding the field of EA. This mist obscuresthe meaning and purpose of this field - not onlyfor the naive observer but also for the maturearchitect.

“

- S. Bente, et al. [1] ”

Motivation

4

Body of knowledge is unstructured and constantly growing.

No Core literature in the area of EAM [5].

Different language communities [3].

No uniform definition of the term [2].

New developments in IT lead shifts of emphasis within EAM topics.

EAM standards are hard to understand, overloaded [4].

EAM

§ No definition of state-of-the-art EAM foundations relevant to practitioners§ High entrance barriers young scholars and other prospects § Call for developing a common understanding / language

© sebis170116 Bondel Master Thesis Final Presentation

eam-initiative.org A wiki-based knowledge community for EAM


EAM foundations are made available in the form of wiki articles.

A concept map is used as navigation tool

“Start small, think big” is a basic directive of the initiative.

The website structure is guided by a wiki-approach.

The community is based on participation.

The goal of the eam-initiative.org is the advancement of the EAM domain.

In order for users to find value in their participation in a wiki-based online community, the wiki has to provide sufficient initial utility [6].





Outline


Goal & Research Questions


Key Objective:Provision of the initial utility for the

eam-initiative.org to enable the success of the knowledge community.

Objective 3:Creation of a concept map to

enable easy navigation through the EAM topics.

Objective 2:Creation of wiki articles

summarizing foundational EAM topics.

Objective 1:Identification and implementation

of a website structure enabling the wiki approach.

Goal AchievementWebsite Structure


Goal AchievementFoundational Wiki Articles


First Iteration -General Overview • Goal: identify first set

of topics relevant in the field of EAM.

Second Iteration -Literature Research • Goal: identify topics can

be categorized as being foundational in the field of EAM.

Third Iteration -Expert Survey • Goal: capture emerging

foundational topics and exclude topic irrelevant in practice.

EAM Topics (29)

Expert Survey

eam-initiative.orgFiles (66)

Foundational EAM Papers (32)

Initiator Books(5)

Sebis Publications(59)

eam-initiative.orgFiles (66)

EAM FoundationalTopics (23)

EAM Foundational Topics (30)

Goal AchievementConcept Map


eam-initiative.org





Outline


Evaluation


User Survey

§ Descriptive Statistics§ Results

Community Activity Metrics

§ Knowledge Posting Activities

§ Viewing Activities Metrics

Further Feedback

§ Feedback received via Email

User Survey Descriptive Statistics


Roles of participants:§ Head of department business (1) § Project manager (1)§ EAM consultant and interims IT manager (1) § CIO (1)§ CEO (1)§ Chief architect completed the survey (1)§ Professor (1)§ Others (2)

4

2

01

0

2

012345

< 1 year 1 - 5 years

6 - 10 years

11 - 15 years

16 - 20 years

> 20 years

Professional EAM Experience

100%

0%

Organization Headquarter

Germany

Other

45%

22%

22%

11%

0%

Organization Size

1-50 FTE

51 - 500 FTE

501 - 5.000 FTE

5.001 - 50.000 FTE

> 50.000 FTE

§ Pros: Majority of practice-oriented participants with different levels of EAM experience§ Cons: Limited geographic distribution and overrepresentation of small organizations.

User SurveyResults


Strongly Disagree Disagree Neutral Agree Strongly Agree

§ Pros: Positive feedback regarding the mission and the structure of the website.§ Cons: The website design could be improved.

100%0% 50% 75%25%50% 25%

Clear mission

Knowledge acquisition source (self)Knowledge acquisition source (others)Platform for sharing own contents

Clear structure

Easy navigation

Appealing design

Meaningful overview of EAM topicsEasy access to the field of EAMAdditional insights into the field of EAM

The website eam-initiative.org provides:

The website eam-initiative.org has:

The concept map enables:

33% 67%

22% 33%45%

67% 33%

22% 33%45%

22%

22%

22%

45%

33% 45%

66% 22%

22% 34% 22%

11% 67% 22%

22% 22%11%

22%45%11% 11%

Community Activity MetricsKnowledge Posting Metrics


§ Pros: The amount of users increased from 34 to 74. § Cons: No changes or creation of wiki articles, new contributions or comments.

Calendar Week

Cumulative registrations

34 36 36 36 36 36 37 37 3739

42 43 43 44

6061

62 63 6365

6771

73 74

30

40

50

60

70

80

29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52

Community Members per Calendar Week

Email Campaign

Email Campaign

Community Activity MetricsViewing Activities Metrics


§ Pros: Increase in session and returning visitors per calendar week.

6029 41

3

5820 26

69 77

53

96 90

2146

269

78 72 7851

64

99134

79 39

0

100

200

300

29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52

Sessions per Calendar Week

Calendar Week

New registrations

Calendar Week

Cumulative registrations

15

32

3

8

5 5

10

4

76 5 4

2017

10 10

57 6

9 7 6

0

5

10

15

20

25

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Returning Visitors per Calendar Week

Email Campaign

Email Campaign

Email Campaign

Email Campaign

Further FeedbackFeedback received via Email


Overall picture: § Good implementation (3)

Community involvement:§ Community needs to be involved more (2)

Website Content: § Should address the current issues and the self-image of EAM (1)§ Website should focus on the expectation of clients (1)

Topics: § Topic structure is considered as fitting (2) § Topics are too fine-grained (1)

Website navigation: § Tree-like structure like the concept map is not fitting for EAM (1)§ Integrating of basic topics in the navigation bar could make the navigation easier (1)

§ Pros: The general approach to of the website received positive feedback.§ Cons: Foster community involvement and enable the integration of current topics.

Evaluation Summary


Positive Feedback

Potential for Improvement

§ Mission is understood and accepted§ Structure is good§ Concept map provides a good means for navigation§ Increasing number of registered users§ Increasing number of sessions and returning users

§ Website design should be improved§ More involvement of community§ Should address the current issues and the self-image of

EAM

Now that the basic utility of the eam-initiative.org is provided, efforts should focus on fostering community building.





Outline


Next Steps


Initiator Meetings PromotionWebsite Design

Improve website design (student assistant,

design contest)

Organize regular initiator meetings

Direct promotion (email, phone, presentations at

expert gatherings)

Member feedback Regularly seek feedback

(surveys, community activity metrics)

Newsletter Regular email newsletters

Technology performance

Ensure availability of features and adequate

performance

Technische Universität MünchenFaculty of InformaticsChair of Software Engineering for Business Information Systems

Boltzmannstraße 385748 Garching bei München

Tel +49.89.289.Fax +49.89.289.17136

wwwmatthes.in.tum.de

Florian MatthesProf. Dr.

17132

[email protected]

Sources


[1] S. Bente, U. Bombosch, and S. Langade. Collaborative Enterprise Architecture: Enriching EA with Lean, Agile, and Enterprise 2.0 Practices. Elsevier, Inc., 2012.

[2] Aier, C. Riege, and R. Winter. “Unternehmensarchitektur - Literaturuberblick und Stand der Praxis.” In: Wirtschaftsinformatik 50(4) (2008), pp. 292–304.

[3] J. Schelp and R. Winter. “Language communities in enterprise architecture research.” In: Proceedings of the 4th International Conference on Design Science Research in Information Systems and Technology. ACM, 2009.

[4] W. Keller. TOGAF 9.1 Quick Start Guide for IT Enterprise Architects. Tech. rep. Wolfgang W. Keller, 2011.

[5] M. Mykhashchuk, S. Buckl, T. Dierl, and C. M. Schweda. “Charting the landscape of enterprise architecture management.” In: 10th International Conference on Wirtschaftsinformatik, 16th-18th February 2011, Zurich, Switzerland. 2011.

[6] A. Kittur, E. H. Chi, B. A. Pendleton, B. Suh, and T. Mytkowicz. “Power of the few vs. wisdom of the crowd: Wikipedia and the riseof the bourgeoisie.” In: Alt.CHI at 25th Annual ACM Conference on Human Factors in Computing Systems (CHI 2007). San Jose, CA, 2007.

[7] T. M. Corporation. EABOK - built by the EA community. http://www.eabok.org/index.html. Accessed: 02.01.2017.

[8] T. A. of Enterprise Architects (AEA). The Association of Enterprise Architects (AEA). https://www.globalaea.org/. Accessed: 02.01.2017.

Backup


eam-initiative.org Timeline


Q3 Q3Q4 Q1 Q4Q2 Q1 Q2

02.10. 05.12. 11.03.

07.04.

28.04.

03.05.

07.07. today

Continuous Improvement of Website

Content Collection

Concept Development

Set up ofTechnical solution

Creation of the initial utility

Promotion of Initiative

Identification of Initiators

17.07.

Meetings

2015 20172016

Timeline


Define Approach

TASKS JUL AUG SEP OCT NOV DEC JAN

Website Structure

EAM Wiki Articles

Concept Map

Evaluation

1st Iteration 2nd

Iteration 3rd Iteration

First Set of EAM Topics


ArchiMate

Architecture Description Language (ADL)

Business Capability & Business Capability Map

Complexity Management

EA and EAM Definition

EA Model

EA Visualization

EAM Activity

EAM Challenge

EAM Driver

EAM Framework

EAM Goal

EAM Information Model

EAM Key Performance Indicator (EAM KPI)

EAM Pattern & Antipattern

EAM Principle

EAM Process

EAM Reference Model & Reference Architecture

EAM Stakeholder & Concern

EAM Standard

EAM Tools

EAM View & Viewpoint

ISO/IEC/IEEE 42010:2011 Systems and software engineering - Architecture description

IT Governance

IT Portfolio Management

Managed Evolution

Organizational Context of EAM

TOGAF®

Zachman Framework

Set of Foundational Topics after the Literature Review


Final Set of Foundational EAM Topics


Initiators


Prof. Dr. Stefan Bente(TH Köln)

Kornelius Fuhrer(EAM Freelancer)

Inge Hanschke(Lean42 GmbH)

Wolfgang Keller(objectarchitects)

Dr. Thomas Mannmeusel(Webasto SE)

Prof. Dr. Florian Matthes(TU München)

Oliver Nandico(Capgemini)

Klaus Niemann(act! Consulting GmbH)

identification and documentation of the state-of-the …...q3 q4 q1 q2 q3 q4 q1 q2 02.10. 05.12....

Documents