15 Years of Enterprise Architecting at HICSS: Revisiting the Critical Problems

Abstract

The Enterprise Architecture (EA) minitrack has been a mainstay of HICSS for the past 15 years. The methodology, tools, and processes of enterprise architecting have evolved during that period. In 2005, Kaisler and Armour identified some critical challenges in modeling, management, and maintenance for EA that needed attention to ensure a viable technical discipline. Over 15 years, we have accepted 93 papers for presentation. Reviewing these papers and drawing up on our experience over the past 15 years, we conclude that some progress has been made, some challenges remain to be addressed, and some new challenges have emerged. This paper revises existing challenges and identifies additional challenges to be addressed in the next 10 years.

Enhancing Information Governance with Enterprise Architecture Management: Design Principles Derived from Benefits and Barriers in the GDPR Implementation

“…Moreover, we extend this list by revealing the specific barriers of EAM in supporting GDPR implementation. While our results empirically confirm the need to closer align EAM with aspects of analytics, security and privacy, as highlighted by several scholars [6,26,28], they also underline that EAM as an organizational function and its architectural models have to be more lightweight and pragmatic in order to create more value for other departments. This complies with the idea of architectural thinking, which is about moving EAM forward to a less formalized and utility-centered approach to support non-architects and people outside the IT function to understand, transform and communicate fundamental structures [25].…”

“…In their paper "15 Years of Enterprise Architecting at HICSS: Revisiting the Critical Problems" from 2017, Kaisler and Armour state that "security and privacy are critical and mandatory at many layers of IT architecture and business architecture" and that "there is a need for EAs of the future to allocate more resources to these areas, and that the architects be more creative in developing protective schemes" [26]. However, research that integrates EAM with security, privacy and analytics aspects, not to mention information governance, is still rather scarce [6,26]. Karjoth et al, for instance, portray IBM's enterprise privacy architecture as "a methodology that allows enterprises to maximize the business use of personal information while respecting privacy concerns and regulations" [27].…”

“…To conclude, research on the interplay of EAM and information governance is still at an early stage, even though researchers explicitly underline this need [26]. While there are some architectural models that intend to provide first steps to address this research gap [6,27,28], there is a great lack of understanding the specific benefits and barriers of EAM in the context of GDPR implementation.…”

The Uncertain Path to Enterprise Architecture (EA) Maturity in the South African Financial Services Sector

“…This was the question that provided the focus for this study. Limited research has been conducted to explore the relationship between EA capabilities and organisational business value, and there is also minimal research which examines EA as an intangible resource and basis for business value (see Kaisler & Armour, 2017;Ross et al, 2006;Tamm, Reynolds, Seddon, Framption, & Shanks, 2015). Furthermore, available EA maturity studies (see Alwadain, Fielt, Korthaus, & Rosemann, 2014;Tamm et al, 2015;Vallerand et al, 2017) have not specifically focused on the way that EA affects business value outcomes at different maturity levels.…”

Method Framework for Developing Enterprise Architecture Security Principles

“…As an example, since May 2018 the enterprises operating in Europe have been obligated to comply with the General Data Protection Regulation (GDPR); and failing to guarantee organizational security and privacy of their customers' personal data may lead to substantial fines. It has been argued that nowadays the security and privacy considerations should be embedded in all the areas of organizational activities instead of only relying on technical security mechanisms that underlying systems and software provide [1], [2].…”