Foundations for the Integration of Enterprise Wikis and Specialized - PowerPoint PPT Presentation

Fakultät für Informatik Technische Universität München Foundations for the Integration of Enterprise Wikis and Specialized Tools for Enterprise Architecture Management 11th International Conference on Wirtschaftsinformatik 2013 Student Track, Leipzig, Germany Max Fiedler, Matheus Hauder, Alexander Schneider (Technical University Munich, Germany) 2013-02-27: Automated Enterprise Architecture Documentation 1

EAM – information-heavy management function à relies on structured & unstructured information à Business Governance Application IT- requirements landscape infrastructure e.g., solution, e.g., exception e.g., names, e.g., names, information Structured target procedures, relationships & storage architecures guidelines, release dates of capacities, access rights applications bandwidths e.g., business e.g., e.g., information e.g., Unstructured information strategy papers background on comparison background information on studies information on governance procurement decisions decisions/ negotiations 2013-02-27: Automated Enterprise Architecture Documentation 2

Interdependencies between all sorts of structured and unstructured information! Business Governance Application IT- requirements landscape infrastructure e.g., solution, e.g., exception e.g., names, e.g., names, information Structured target procedures, relationships & storage architecures guidelines, release dates of capacities, access rights applications bandwidths e.g., business e.g., e.g., information e.g., Unstructured information strategy papers background on comparison background information on studies information on governance procurement decisions decisions/ negotiations 2013-02-27: Automated Enterprise Architecture Documentation 3

Support of collection, maintenance, availability and organization of these information crucial Dedicated EAM-tool Wiki Strengths: Strengths: § modeling and retrieving § Web-based, enable online architectural knowledge collaboration concepts § Communication via notices, RSS § Adjustable rich meta-model feeds, news, Email updates § Availability and navigation: Weaknesses: functionality to link, tag, index, cross- reference and search § Low accessibility for EA à especially useful for unstruct. Info. stakeholders outside central § Easy to learn, fun to use team § Little support for collaboration, Weaknesses: communication, navigation in wider document space § Little/no functionality for visualization and modeling EA concepts § No meta-model 2013-02-27: Automated Enterprise Architecture Documentation 4

Our hypothesis: integration of both Wiki and EAM- tool will improve mgmt. of EA-relevant information The use of both, Wiki and EAM-tool, and their integration will improve the inclusion and management of relevant structured and unstructured information within the EAM-function Practitioners survey Literature review § 178 participants from 105 § Some findings on the use of organizations a Wiki for EAM instead of an § 7 countries EAM-tool § About half Enterprise § First attempt of integration of architects a Wiki and a visual software § 0 -10 years of experience tool 2013-02-27: Automated Enterprise Architecture Documentation 5

Survey – Participants from many different industries and mostly with expertise on EAM Industry Sector Job Title n % of all n % of all Enterprise Architect 54 51.43% IT Consulting 24 22.86% IT Architect 15 14.29% Finance 18 17.14% Consultant 12 11.43% IT Products and Services 9 8.57% Business Architect 6 5.71% Telecommunications 6 5.71% IT Operations 3 2.86% Public Service 8 7.62% CxO 6 5.71% Education 5 4.76% Software Engineer 1 0.95% Production and Manufacturing 6 5.71% Solution Architect 1 0.95% Transportation and Logistics 3 2.86% Business Analyst 1 0.95% Health 2 1.90% EA Analyst 1 0.95% Management Consulting 4 3.81% Other 1 0.95% Other 20 19.05% 2013-02-27: Automated Enterprise Architecture Documentation 6

Survey – Results show significant interest in the research topic among practitioners Which tools does your organization use for EAM? Tools for EAM n % of all EA Tool 36 34.29% Wiki & EA Tool separately 37 35.24% Wiki & EA Tool integrated 6 5.71% Wiki 9 8.57% None of these 14 13.33% No response 3 2.86% Do you think a Wiki can be useful (in addition to another Do you plan to use a Wiki for EA tool) for EAM? management in the future? Wiki for EAM useful Wiki for EAM in future n % of all n % of all Yes Yes 63 60.00% 98 93.33% No No 13 12.38% 7 6.67% No answer No answer 29 27.62% 0 0.00% 2013-02-27: Automated Enterprise Architecture Documentation 7

Literature – Much on EAM-tools, much on Wikis, little on Wikis for EAM, very little on integration (Farenhorst et al. 2008) (Hirsch et al. 2009) Wiki for EAM instead of Integration of Wiki and visualization dedicated EAM-tool software Advantages: support for online communication, managing non-architectural knowledge, collaboration support and involving and integrating knowledge and communication needs of other functions within the company Disadvantages: lacking out-of-the-box support for modeling and retrieving (Picture from Hirsch et al. 2009) architectural knowledge concepts 2013-02-27: Automated Enterprise Architecture Documentation 8

How to best combine the respective strengths of Wiki and EAM-tool for EAM Dedicated EAM-tool Wiki Strengths: Strengths: § modeling and retrieving § Web-based, enable online architectural knowledge collaboration concepts § Communication via notices, RSS § Adjustable rich meta-model feeds, news, Email updates Integration § Availability and navigation: Weaknesses: functionality to link, tag, index, cross- reference and search § Low accessibility for EA à especially useful for unstruct. Info. stakeholders outside central § Easy to learn, fun to use team § Little support for collaboration, Weaknesses: communication, navigation in wider document space § Little/no functionality for visualization and modeling EA concepts § No meta-model 2013-02-27: Automated Enterprise Architecture Documentation 9

Differentiate EA-scenarios by: better supported by Wiki vs. by EAM-tool Definition of nine EA scenarios Definition of terms: glossary Providing references to EA Document guidelines and of terms to create a common relevant documents: EA- FAQs: need to distribute EA terminological basis. information stored in central stakeholders throughout repository à additional info. organization à improve distributed over many comm. with mgmt. and documents in organization operations processes Annotating visualizations: Discussion of business and Import, edit and validate EA support stakeholder specific EA requirements: Major goal information: Import of ata views, annotated with detail or of EAM business-IT alignment. collected in spreadsheets or background information on discussion about requirements from productive systems, also application landscape preserved with unstructured data transformations information linked to EA model Analyze EA information: Simulate impacts of EA EAM Activities and analysis of EA information by decisions: formalized theory Workflows: support architects various visualizations, metrics, to describe and compare alter- and stakeholders tasks, as Stakeholders are architects or native EA decisions , impacts documentation of EA, the management board documented and analyzed development of planned states, or architecture reviews 2013-02-27: Automated Enterprise Architecture Documentation 10

Differentiate EA-scenarios – Relatively clear results of practitioners survey 2013-02-27: Automated Enterprise Architecture Documentation 11

Some cases of EA-processes touch more that one scenario, some scenarios more than one tool Tool involvement to be identified Flow of information to be specified Four cases identified: § Case 1: information creation and storage is done in Wiki § Case 2: information is created with Wiki but later transferred to EAM tool § Case 3: information is created with EAM tool but later transferred to Wiki § Case 4: information creation and storage is done in the EAM tool 2013-02-27: Automated Enterprise Architecture Documentation 12

Four cases differentiated by the flow of information – Categorization of 9 EA-scenarios 2013-02-27: Automated Enterprise Architecture Documentation 13

Future research – Next steps Validation of results in real-life EA-initiatives Specifications on realization of integration of Wiki and EAM-tool … 2013-02-27: Automated Enterprise Architecture Documentation 14