Refine
Has Fulltext
- no (2)
Document Type
- Article (2) (remove)
Language
- English (2) (remove)
Is part of the Bibliography
- yes (2)
Keywords
- ERP system (1)
- VUCA (1)
- database (1)
- enterprise architect (1)
- enterprise architecture management (1)
- enterprise system (1)
- future (1)
- problems (1)
- requirements (1)
- roles (1)
Institute
For the last 20 years, enterprise architecture management (EAM) was primarily an instrument for harmonizing and consolidating IT landscapes and is lived as a transformation and governance discipline. It, however, is rather related to IT strategy than aligned to the actual corporate strategy and the work of the enterprise architect is characterized by tasks like prescribing, monitoring, documenting, and controlling. As digital transformation continues apace, companies are facing new challenges that lead to a volatile, uncertain, complex, and ambiguous (VUCA) world. To face these challenges, vision, understanding, clarity and agility allow to anticipative and implement necessary changes. This, of course, has implications for the role of the enterprise architect. S/he needs to start actively supporting innovation and taking more of an advisory role instead of just being driven by the current state of the enterprise architecture. This paper investigates the role of the enterprise architect in the VUCA world. Based on current literature and expert interviews, a survey was conducted among consultants who work as (or with) enterprise architects. Survey results include the evaluation of statements on current tasks of enterprise architects, their influence on projects and companies as well as future requirements on the roles of the enterprise architect. The results from the survey were synthesized with the findings from literature to derive the roles, tasks and skills of enterprise architect in the VUCA world.
The digital transformation sets new requirements to all classes of enterprise systems in companies. ERP systems in particular, which represent the dominant class of enterprise systems, are struggling to meet the new requirements at all levels of the architecture. Therefore, there is an urgent need to reconsider the overall architecture of the systems and address the root of the related issues. Given that many restrictions ERP pose on their adaptability are related to the standardization of data, the database layer of ERP systems is addressed. Since database serve as the foundation for data storage and retrieval, they limit the flexibility of enterprise systems and the chance to adapt to new requirements accordingly. So far, relational databases are widely used. Using a systematic literature approach, recent requirements for ERP systems were identified. Prominent database approaches were assessed against the 23 requirements identified. The results reveal the strengths and weaknesses of recent database approaches. To this end, the results highlight the demand to combine multiple database approaches to fulfill recent business requirements. From a conceptual point of view, this paper supports the idea of federated databases which are interoperable to fulfill future requirements and support business operation. This research forms the basis for renewal of the current generation of ERP systems and proposes to ERP vendors to use different database concepts in the future.