@inproceedings{CzarneckiWinkelmannSpiliopoulou2011,
  author    = {Czarnecki, Christian and Winkelmann, Axel and Spiliopoulou, Myra},
  title     = {Making business systems in the telecommunication industry more customer-oriented},
  series = {Information Systems Development : Business Systems and Services: Modeling and Development},
  booktitle = {Information Systems Development : Business Systems and Services: Modeling and Development},
  editor    = {Pokorny, Jaroslav and Repa, Vaclav and Richta, Karel and Wojtkowski, Wita and Linger, Henry and Barry, Chris and Lang, Michael},
  publisher = {Springer},
  address   = {New York},
  isbn      = {978-1-4419-9645-9 (Print)},
  doi       = {10.1007/978-1-4419-9790-6_14},
  pages     = {169 -- 180},
  year      = {2011},
  abstract  = {Market changes have forced telecommunication companies to transform their business. Increased competition, short innovation cycles, changed usage patterns, increased customer expectations and cost reduction are the main drivers. Our objective is to analyze to what extend transformation projects have improved the orientation towards the end-customers. Therefore, we selected 38 real-life case studies that are dealing with customer orientation. Our analysis is based on a telecommunication-specific framework that aligns strategy, business processes and information systems. The result of our analysis shows the following: transformation projects that aim to improve the customer orientation are combined with clear goals on costs and revenue of the enterprise. These projects are usually directly linked to the customer touch points, but also to the development and provisioning of products. Furthermore, the analysis shows that customer orientation is not the sole trigger for transformation. There is no one-fits-all solution; rather, improved customer orientation needs aligned changes of business processes as well as information systems related to different parts of the company.},
  language  = {en}
}
@inproceedings{BrockmannSultanowCzarnecki2018,
  author    = {Brockmann, Carsten and Sultanow, Eldar and Czarnecki, Christian},
  title     = {Enterprise architectures between agility and traditional methodologies},
  series = {GI Edition Proceedings Band 285 Workshops der INFORMATIK 2018},
  booktitle = {GI Edition Proceedings Band 285 Workshops der INFORMATIK 2018},
  editor    = {Czarnecki, Christian and Brockmann, Carsten and Sultanow, Eldar and Koschmider, Agnes and Selzer, Annika and Gesellschaft f{\"u}r Informatik e. V.,},
  publisher = {K{\"o}llen},
  address   = {Bonn},
  isbn      = {9783885796794},
  issn      = {1617-5468},
  pages     = {1 Seite},
  year      = {2018},
  abstract  = {For this year's workshop on Enterpirse Architecture in Research and Practice we have received eight submissions from which four have passed the rigorous peer-review. The acceptance quote of 50\% assures that only advancements in the field are included in our workshop.},
  language  = {en}
}
@inproceedings{BrockmannSultanowCzarnecki2019,
  author    = {Brockmann, Carsten and Sultanow, Eldar and Czarnecki, Christian},
  title     = {Is enterprise architecture still relevant in the digital age?},
  series = {GI Edition Proceedings Band 295 INFORMATIK 2019, Workshop-Beitr{\"a}ge},
  booktitle = {GI Edition Proceedings Band 295 INFORMATIK 2019, Workshop-Beitr{\"a}ge},
  editor    = {Draude, Claude and Lange, Martin and Sick, Bernhard},
  publisher = {K{\"o}llen},
  address   = {Bonn},
  isbn      = {9783885796893},
  issn      = {1617-5468},
  doi       = {10.18420/inf2019_ws01},
  pages     = {21 -- 21},
  year      = {2019},
  language  = {en}
}
@inproceedings{AuthCzarneckiBensberg2019,
  author    = {Auth, Gunnar and Czarnecki, Christian and Bensberg, Frank},
  title     = {Impact of robotic process automation on enterprise architectures},
  series = {GI Edition Proceedings Band 295 INFORMATIK 2019, Workshop-Beitr{\"a}ge},
  booktitle = {GI Edition Proceedings Band 295 INFORMATIK 2019, Workshop-Beitr{\"a}ge},
  editor    = {Draude, Claude and Lange, Martin and Sick, Bernhard and Gesellschaft f{\"u}r Informatik e.V. (GI),},
  publisher = {K{\"o}llen},
  address   = {Bonn},
  isbn      = {9783885796893},
  issn      = {1617-5468},
  doi       = {10.18420/inf2019_ws05},
  pages     = {59 -- 65},
  year      = {2019},
  abstract  = {The initial idea of Robotic Process Automation (RPA) is the automation of business processes through the presentation layer of existing application systems. For this simple emulation of user input and output by software robots, no changes of the systems and architecture is required. However, considering strategic aspects of aligning business and technology on an enterprise level as well as the growing capabilities of RPA driven by artificial intelligence, interrelations between RPA and Enterprise Architecture (EA) become visible and pose new questions. In this paper we discuss the relationship between RPA and EA in terms of perspectives and implications. As workin- progress we focus on identifying new questions and research opportunities related to RPA and EA.},
  language  = {en}
}
@inproceedings{RitschelStenzelCzarneckietal.2021,
  author    = {Ritschel, Konstantin and Stenzel, Adina and Czarnecki, Christian and Hong, Chin-Gi},
  title     = {Realizing robotic process automation potentials: an architectural perspective on a real-life implementation case},
  series = {GI Edition Proceedings Band 314 "INFORMATIK 2021" Computer Science \& Sustainability},
  booktitle = {GI Edition Proceedings Band 314 "INFORMATIK 2021" Computer Science \& Sustainability},
  editor    = {Gesellschaft f{\"u}r Informatik e.V. (GI),},
  publisher = {K{\"o}llen},
  address   = {Bonn},
  isbn      = {9783885797081},
  issn      = {1617-5468},
  pages     = {1303 -- 1311},
  year      = {2021},
  abstract  = {The initial idea of Robotic Process Automation (RPA) is the automation of business processes through a simple emulation of user input and output by software robots. Hence, it can be assumed that no changes of the used software systems and existing Enterprise Architecture (EA) is required. In this short, practical paper we discuss this assumption based on a real-life implementation project. We show that a successful RPA implementation might require architectural work during analysis, implementation, and migration. As practical paper we focus on exemplary lessons-learned and new questions related to RPA and EA.},
  language  = {en}
}