Supervised Master's theses
- Configuration Management and Continuous Delivery
- Better formalisms for modelling the software variability induced by feature toggles
- Release-as-Code - how to further automate releases based on Continuous Delivery
- Creating better team awareness with SCM
- Continuous Delivery pipeline problematics
- Other things related to Continuous Software Engineering
- Merge of "whatever" (that is not "line-based text")
- Mining Software Repository (or SCM metrics)
- Database Version Control
- Your own ideas - related to SCM ;-)
- Configuration Management and Distributed Development, Softhouse,
starting as soon as possible (description in pdf)
- Making software tangible to developers, internal/external, enquire if interested.
- Seif Al-Shakargi: Continuous Delivery as a Service, started September 2018.
- André Alm, Daniel Dornlöv: Shared code — Underlying causes and how to make it work, started May 2018.
- Daniel Jigin, Oscar Gunnesson: Using Already Existing Data to Answer Questions Asked During Software Change, May 2018.
- Viktor Attoff, Tobias Landelius: Managing and utilizing dependencies between components in component-based systems, August 2017.
- Gustav Ek, Björn Boyd Isacsson: An Evaluation of Dynamic Software Updating Techniques for Embedded Systems in C, June 2017.
- Marcus Hilliges: Remodelling the Software Development Life-Cycle using combinations from Scrum and Extreme Programming, June 2017 (examinator).
- Fredrik Gustafsson: Merging customer relationship management data, June 2016.
- Jakob Svemar: Showstoppers for Continuous Delivery in Small Scale Projects, December 2015.
- Jonathan Klingberg: Piping for Continuous Delivery, August 2015.
- Alexander Haraldsson: Reaching across - managing variants of one application on multiple platforms, August 2015.
- Richard Simko: Automating Traceability in Agile Software Development, June 2015.
- Henrik Gyllensvärd, Niklas Welander: Reducing Double Maintenance for Web-based Application on a code- and logical level, December 2014.
- Johan Thiborg-Ericsson: Filling In Safety Impact Analysis Forms (Quality, Efficiency and Soft Issues), March, 2014.
- Viktor Ekholm, Fredrik Stål: Reaching Software Development Maturity with Continuous Delivery, August 2013.
- Artour Klevin: People, Process and Tools: A Study of Impact Analysis in a Change Process, March 2012.
- Aron Lidé: A state-based 3-way batch merge algorithm for models serialized in XMI, November 2011.
- David Arve: Collaboration Patterns for Software Development, August 2010.
- Antonio Martini: Merge of models: an XMI approach, August 2010.
- Jonathan Thiry: The Software Configuration Management Checkup and Improvement Framework, August 2010.
- Jacob Gradén, Anna Ståhl: Managing product variants in a component-based system, November 2009.
- Carl Orvinder: Business Process in Execution, October 2009.
- Marcus Jacobsson: Implementing Traceability in Agile Software Development, January 2009.
- Andreas Bergström: Software Configuration Management in Scrum projects, November 2008.
- Jacob Kristhammar, Roger Schildmeijer: Tool Assisted Product Configuration in Software Product Lines,
- Vladimir Karadzic, Staffan Thörngren: Modeling Dependencies in Dynamic Software Configurations, March 2007.
- Axel Bengtsson, Ola Olsson: Automatic Software Integration, September 2006.
- Love Johansson, Johan Larsson: A Framework for Extracting Information From a Code Base, February 2006.
- Joakim Persson: Requirements for an Interactive Logging Framework, December 2005.
- Anders Hellström, Björn Pileryd: Controlling the variant explosion - Enforcing stability
in highly configurable large scale software, September 2005.
- Lorenzo Borracci: A Return on Investment Model for Software Configuration Management, May 2005.
- Henrik Munkebo Christiansen: Agile Offshore, May 2005.
- Laura Carvajal: An Architecture for the Integration of Wireless Internet Services, June 2004.
- David Karlsson: Variability Management with a Feature Perspective, March 2004.
- Ola Hansson, Anders Svensson: Automatic code generation with Roundtrip Engineering, October 2003.
I keep six honest serving men
(They taught me all I knew);
Their names are What and Why and When
And How and Where and Who.
Subjektivitet er at aflæse et solur med en lommelygte -
(Subjectivity is like reading a sundial at night with a torch)
x-jobs in Configuration Management:
x-jobs must include (with varying emphasis):
- versioning of information
- programming environments/tools/(methods)
- analysis of a problem (domain)
- evaluation of possible solutions
- design of a solution
- implementation of a prototype for experiments/proof
- all this must of course be documented in a report
- analytical (impl. proof of concept/principle)
- empirical (impl. for experiments)
other areas of interest:
- programming environments
- programming languages
- software processes and improvement
come to my room - or
send me an email - and discuss
your ideas and we might find out something
The discipline of software configuration management (SCM) provides one of the best
success stories in the field of software engineering. With the availability of over
a hundred commercial SCM systems that together form a billion dollar marketplace,
and the explicit recognition of SCM by such standards as the CMM and ISO-9000, the
discipline has established itself as one of the essential cornerstones of software
While SCM is a well-established discipline, innovative software engineering approaches
constitute new challenges that require support in new and in integrated engineering
areas in form of new or improved tools, techniques, and processes.
These challenges emerge in:
An x-job provides a forum for presenting and discussing innovative approaches to SCM.
Moreover, it has a strong interdisciplinary flavor and specifically invites viewpoints
from related disciplines.
- component-based development,
- distributed systems,
- dynamically bound and reconfigured systems,
- embedded systems,
- software architecture,
- web-based systems,
- engineering/product data management,
- system engineering,
- process suppport,
- concurrent and cooperative engineering.
Maintained by email@example.com