Maximilian Kögel (Dipl. Inf.) koegel (at) in.tum.de Technische Universität München Institut für Informatik I1 D-85748 Garching b. München Germany Office: 01.07.041 Phone: +49.89.289.18238

Research Interests

• Comparison, Change Tracking and Versioning (SCM) of Software Engineering Artifacts (Models and co.)
  
• Conflict Detection and Model Merging
• Model Evolution
• Change Awareness

Current Projects

• UNICASE, a unified CASE tool
  
• DOLLI 3, in cooperation with Munich Airport
• suitCASE, in cooperation with Munich Airport
• Munich Center for Advanced Computing (MAC)

Past Projects

• DSL modeling, in cooperation with msg systems
• ARGO - Analyze, Ready, GO!, in cooperation with Siemens Corporate Technology, Munich
• Sysiphus, a modeling tool
  
• DOLLI 2, in cooperation with Munich Airport
• DOLLI, in cooperation with Munich Airport
• TEAM, EU project
  
• Unified Requirements Modeling Language (URML), in cooperation with Siemens Corporate Research, Princeton
• TABLET, in cooperation with Hewlett-Packard

Teaching

• Software Development Lab Course SS2010: Eclipse Plugin Development
• Software Development Lab Course WS0910: Eclipse Plugin Development
• Software Development Lab Course WS0910: DOLLI 3
• Lecture Software Engineering for Engineers SS2009 - Teaching Assistent
• Software Development Lab Course SS2009: Eclipse Plugin Development
• Software Development Lab Course WS0809: DOLLI 2
• Software Development Lab Course WS0809: Eclipse Plugin Development
• Software Development Lab Course WS0708: DOLLI
• Software Development Lab Course WS0708: PROT
• Lecture Software Engineering 1 SS2007 - Teaching Assistent
• Lecture Software Engineering 1 WS0607 - Teaching Assistent

Bachelor/Master Thesis, DAs, SEPs

These are some ideas on possible topics, they can be a starting point for a discussion about a topic for your thesis. All topics are somehow related to unicase.
unicase is a CASE tool for developing and collaborating over software engineering models. It integrates very different kinds of software engineering artifacts from two major domains into one central repository: system modeling and project modeling. System models describe the system that is being developed and include UML models, feature and requirement models. Project models describe the project and its resources and include work break down structures, gantt and organizational charts. unicase consists of a server providing the central repository and its services and a client application providing the editors for manipulating the different models. Both are based on Eclipse and the Eclipse technologies RCP (Rich Client Platform), EMF (Eclipse Modeling Framework) and GMF (Graphical Modeling Framework). unicase is developed at the Chair for Applied Software Engineering in cooperation with our academic and industrial partners. See unicase.org for details.

Open Topics

• Task-based Change Tracking: Normally tasks and the changes that are produced to complete a task are managed seperatly. A task is potentially tracked in a bug tracking system while the changes to source code are managed by a version control system such as CVS or SVN. This results in poor tool suport for release maintenance, planning and reviewing of tasks. Other approaches have tried to overcome this by adding additional information to the version control system such as bug numbers in the commit messages. In this thesis we will integrate a technique to annotate source code changes to tasks in UNICASE and thereby facilitate model-based release planning, release maintenance and task reviews. For example it will be possible to configure release as a number of tasks and bug fixes and thereby to automatically assemble the respective release from the changes attached to the respective bug fixes and tasks for the release.
  

• Traceability Visualization: Traceability links allow to trace from requirements to analysis models and down to source code. For an effective use it is important to visualize these links in a graph-based view that allows filitering for selected aspects, roles and use cases. For example it should be possible to use such a view in the use case of change impact analysis where it is important to find related artifacts that need to be updated because another artifact has been changed. This thesis will elicite the requirements for such a view and provide an implementation.
  

Assigned Topics

• Issue-based Model Merging

Completed Topics

• Virtual Whiteboard for UNICASE
• A Project Analysis Framework for Emprical Software Engineering
• Appying Social Network Techniques to Software Engineering
• Operation-based Change Tracking and Conflict Detection
• Model-based Document Export
• Bug tracking for Sysiphus
  
• Web 2.0 Requirements Elicitation for Sysiphus