130 likes | 255 Vues
This presentation outlines a bachelor’s thesis aimed at developing a visual tool for conflict resolution in enterprise architecture (EA) repositories. The research focuses on providing interactive visualizations to facilitate the understanding and resolution of model conflicts. Key objectives include enhancing conflict resolution processes with relevant background information and employing suitable layout algorithms for visualizing large EA models. The approach includes a meta-information model and mock-ups. The timeline outlines key phases of research and implementation.
E N D
A Visual Tool for Conflict Resolution in EA Repositories Bachelor’s Thesis kick-off presentation, Jul. 08 2013 Tobias Schrade • Software Engineering for Business Information Systems (sebis)wwwmatthes.in.tum.de Bachelor’s Thesis kick-off presentation, 08.07.2013
Agenda • Introduction • Research ObjectiveandQuestions • Approach • Metainformationmodel • Mock-ups • Timeline • References Bachelor’s Thesis kick-off presentation, 08.07.2013
Introduction Bachelor’s Thesis kick-off presentation, 08.07.2013
Research Objective and Questions • Research Objective: Facilitate model conflict tasks with visualizations to provide an easy understanding of the given model and respective conflicts; enhance the process of solving the conflicts with relevant background information and change memory. • Q1: “How to provide (interactive) visual means to communicate and resolve model conflicts?” • Q1.1: “Which (EA) visualizations are scalable for large (<=1K Objects) EA models?” • Q1.2: “Which layout algorithms are suitable to visualize EA model conflicts?” Bachelor’s Thesis kick-off presentation, 08.07.2013
Approach • Meta information model Bachelor’s Thesis kick-off presentation, 08.07.2013
Approach • Mock-ups # ofobjects Object Type <ApplicationComponent> ConceptA (50) Attribute (10):String [1,1] ! DefinedConcept UndefinedConcept DerivedConcept Legend Infrastructure(10): Relationship [1,*] ! 20 % 80 % 20 % 80 % Attribute Name Attribute Type Cardinalities Bachelor’s Thesis kick-off presentation, 08.07.2013
Approach • Mock-ups <ApplicationComponent> ConceptA (50) Attribute (10):String [1,1] ! Infrastructure(10): Relationship [1,*] ! 20 % 80 % <Infrastructure> Concept B (50) <Infrastructure> ConceptC (50) Attribute (10):String [1,1] ! Attribute (10):String [1,1] ! Infrastructure(10): Relationship [1,*] ! Infrastructure(10): Relationship [1,*] ! 20 % 80 % 20 % 80 % Bachelor’s Thesis kick-off presentation, 08.07.2013
Approach • Mock-ups <ApplicationComponent> ConceptA (50) Attribute (10):String [1,1] ! Instance A1 Infrastructure(10): Relationship [1,*] ! 20 80 Instance A2 Instance A3 <Infrastructure> Concept B (50) Instance A4 <infrastructure> ConceptC (50) Attribute (10):String [1,1] ! Instance A5 Attribute (10):String [1,1] ! Infrastructure(10): Relationship [1,*] ! Infrastructure(10): Relationship [1,*] ! Instance A6 20 80 20 80 Instance A7 Instance A8 Bachelor’s Thesis kick-off presentation, 08.07.2013
Approach • Mock-ups <ApplicationComponent> ConceptA (50) Attribute (10):String [1,1] ! Instance A1 Infrastructure(10): Relationship [1,*] ! 20 80 Instance A6 Instance A7 <Infrastructure> Concept B (50) <infrastructure> ConceptC (50) Attribute (10):String [1,1] ! Attribute (10):String [1,1] ! Infrastructure(10): Relationship [1,*] ! Infrastructure(10): Relationship [1,*] ! 20 80 20 80 Bachelor’s Thesis kick-off presentation, 08.07.2013
Approach • Mock-ups <ApplicationComponent> ConceptA (50) Name:„Instance A4“ => „Instance A1“ Name:„Instance A4“ => „Instance A3“ Attribute (10):String [1,1] ! Instance A1 Infrastructure(10): Relationship [1,*] Own Name:„…………………..“ ! 20 80 Instance A6 <ApplicationComponent> Instance A1 ! Instance A7 Attribute : „Attribute A1“ ! Infrastructure : Instance B1, Instance C1 <Infrastructure> Concept B (50) <infrastructure> ConceptC (50) Attribute (10):String [1,1] ! Attribute (10):String [1,1] ! Infrastructure(10): Relationship [1,*] ! Infrastructure(10): Relationship [1,*] ! <Infrastructure> Instance B1 <Infrastructure> Instance C1 20 80 20 80 Attribute : „Attribute B1“ Attribute : „Attribute C1“ Infrastructure : Instance D1 Infrastructure : Instance E1 Legend NoConflict Conflict Bachelor’s Thesis kick-off presentation, 08.07.2013
Timeline Jul. 15Official Start,Literature research, other approaches Sep. 01Start to write thesis Dec. 15Finish thesis Aug. 15Begin implementation Bachelor’s Thesis kick-off presentation, 08.07.2013
References • [Fa13]Farwick, M., Hauder, M., Roth, S., Matthes, F., Breu, R.: Enterprise Architecture Documentation: Empirical Analysis of Information Sources for Automation, 46th Hawaii International Conference on System Sciences (HICSS 46), Maui, Hawaii, 2013.[Ro13a]Roth, S., Hauder, M., Farwick, M., Matthes, F., Breu, R.: Enterprise Architecture Documentation: Current Practices and Future Directions, 11th International Conference on Wirtschaftsinformatik (WI), Leipzig, Germany, 2013.[Ro13b]Roth, S., Matthes, F.: Future Research Topics in Enterprise Architectures Evolution Analysis, Design for Future (DFF) Workshop, 2013. • [Ro13c]Roth, S., Hauder, M., Matthes, F.: Evolution of Enterprise Architecture Models through Stakeholder Engagement: Facilitating Conflict Resolution with Tasks, MRT Workshop, Miami,2013 (in submission) • [HMR12]Hauder, M., Matthes, F., Roth, S.: Challenges for Automated Enterprise Architecture Documentation. In: 7th International Workshop on Trends in Enterprise Architecture Research (TEAR), Barcelona, Spain, 2012. • [Wie12]Wieland, K.. Langer, P., Seidl, M., Wimer, M., Kappel, G.: Turning Conflicts into Collaboration, Computer Supported Cooperative Work: The Journal of Collaborative Computing, tba:1-52, 2012 Bachelor’s Thesis kick-off presentation, 08.07.2013
Any Questions? Bachelor’s Thesis kick-off presentation, 08.07.2013