2017•Unpublished venueOpen access

A Case Study of Stakeholder Concerns on EAM

Simon Hacks, Maximilian Brosius, Stephan Aier

Open full text 11 citations

Abstract

As a result of growing complexities in business processes, information systems, and the technical infrastructure, a key challenge for enterprise architecture management (EAM) is to guide stakeholders from different hierarchical levels with heterogeneous concerns. EA deliverables, such as models or frameworks, are often highly comprehensive and standardized. However, these can hardly be applied without greater adaption. Although the literature selectively covers approaches for tailoring EA deliverables closer to the concerns of affected stakeholders, these approaches are often vague or not very differentiated. In the paper at hand, we aim at introducing a stakeholder perspective to EAM research that considers stakeholder concerns on EAM across hierarchical levels. To this end, we conduct a case study: Our results show homogenous concerns among stakeholders on EA deliverables. In turn, we found different concerns on the role of EAM in applying these deliverables, dependent on the hierarchical level of stakeholders. These findings stress the necessity for a more differentiated understanding of stakeholder concerns on EAM. Finally, we discuss the implications of our findings for an exemplary EAM approach.

About this research paper

What this paper is about

As a result of growing complexities in business processes, information systems, and the technical infrastructure, a key challenge for enterprise architecture management (EAM) is to guide stakeholders from different hierarchical levels with heterogeneous concerns. EA deliverables, such as models or frameworks, are often highly comprehensive and standardized. However, these can hardly be applied without greater adaption. Although the literature selectively covers approaches for tailoring EA deliverables closer to the concerns of affected stakeholders, these approaches are often vague or not very differentiated. In the paper at hand, we aim at introducing a stakeholder perspective to EAM research that considers stakeholder concerns on EAM across hierarchical levels. To this end, we conduct a case study: Our results show homogenous concerns among stakeholders on EA deliverables. In turn, we found different concerns on the role of EAM in applying these deliverables, dependent on the hierarchical level of stakeholders. These findings stress the necessity for a more differentiated understanding of stakeholder concerns on EAM. Finally, we discuss the implications of our findings for an exemplary EAM approach.

Why it matters

OpenAlex reports 11 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

As a result of growing complexities in business processes, information systems, and the technical infrastructure, a key challenge for enterprise architecture management (EAM) is to guide stakeholders from different hierarchical levels with heterogeneous concerns. EA deliverables, such as models or frameworks, are often highly comprehensive and standardized. However, these can hardly be applied without greater adaption. Although the literature selectively covers approaches for tailoring EA deliverables closer to the concerns of affected stakeholders, these approaches are often vague or not very differentiated. In the paper at hand, we aim at introducing a stakeholder perspective to EAM research that considers stakeholder concerns on EAM across hierarchical levels. To this end, we conduct a case study: Our results show homogenous concerns among stakeholders on EA deliverables. In turn, we found different concerns on the role of EAM in applying these deliverables, dependent on the hierarchical level of stakeholders. These findings stress the necessity for a more differentiated understanding of stakeholder concerns on EAM. Finally, we discuss the implications of our findings for an exemplary EAM approach.

Key concepts: Deliverable, Stakeholder, Process management, Key (lock), Knowledge management, Computer science, Perspective (graphical), Sociotechnical system

Related papers

Back to paper searchBrowse research topicsOriginal source
A Case Study of Stakeholder Concerns on EAM — Research Paper | ScholarLens