3rd EA Debts Student Conference

We are happy to conduct the third student conference on enterprise architecture debts. The conference will be online again and take place August 24 from 13:00 to 15:30 CEST. The aim of the conference is to provide the students with the opportunity to present their work to interested practitioners and fellow students as well as gather feedback from the audience. We will have different talks from students presenting their actual state of their thesis and one keynote. The schedule is as follows:

13:00-13:05OpeningConference committee
13:05-13:50Assessing the Severity of EA Debt In the software development industry, it is very common to deviate from the ideal state of enterprise because of various aspects such as miscommunication between different parties, lack of documentation, lack of planning, etc. This deviation is called Enterprise Architecture Debt (EAD) which if not addressed can lead to serious consequences later on. Although, the importance of EAD has been addressed in many research papers before there is still a gap to obtain the severity of EAD in a certain software development system. This is something that needs to be addressed otherwise working without knowing the debt can be disastrous and can cost unaffordable losses. This paper works to fill in the gap by providing an approach to measure EA debt and its severity in proportion to the investment portfolio under defined thresholds. The paper also goes one step further and provides an enterprise-level severity assessment to understand the good and bad investments in more details for better understanding of the EAD in the project overallDaniyal Danish – Master’s student at RWTH Aachen University
13:50-14:35Expert-based Assessment of Solution Architecture Alignment Assessment of Solution Architecture Alignment aims to provide a framework to support Solution Architects to align project architectures with enterprise requirements and constraints. The presentation concentrates on Expert-based assessments, which focus on assessing requirements & constrains that requires domain-knowledge to in the assessment.
Furthermore, the approach tries to tackle common issues that arise when dealing with Solution Architecture alignment. Part of it is grouping common issues into predefined Situations and attach potential Considerations, which classify the Situation, in order to improve the alignment process and to build a knowledge base over time. This concept is called AAA (triple A).
Another aspect is the management of situations, principles and standards at scale by attaching domain specific Tags to them. These tags can be used to precisely filter and search for related Situations or Principles even in larger organisations.
Jonah Schüller – Bachelor’s student at RWTH Aachen University
14:35-15:15Creating a Recommender Plug-In for Enterprise Architecture Models IT has evolved over the decades, where its role and impact have transitioned from being a tactical tool to a more strategic one for driving business strategies to transform organizations. The right alignment between IT strategy and business has become a compelling factor for Chief Information Officers and Enterprise Architecture (EA) in practice is one of the approaches where this alignment can be achieved. Enterprise Modeling complements EA with models that are composed of enterprise components and relationships, that are stored in a repository. Over time, the repository grows which opens up research avenues to provide data intelligence. Recommender Systems is a field that can take different forms in the modeling domain and each form of recommendation can be enhanced with sophisticated models over time. We focus on the latter problem by providing a robust recommender architecture framework that easily integrates with different Recommender Systems. The framework is distributed as a plugin for Archi, a modeling toolkit to create EA models.Sashikanth Raavikanti – Master’s student at KTH Royal Institute of Technology
15:15-15:30ClosingConference committee

Leave a Reply

Your email address will not be published. Required fields are marked *