inproceedings_stammel.bib

@inproceedings{durdik2012c,
  address = {Trento, Italy},
  author = {Zoya Durdik and Benjamin Klatt and Heiko Koziolek and Klaus Krogmann and Johannes Stammel and Roland Weiss},
  booktitle = {Proceedings of the 28th IEEE International Conference on Software Maintenance (ICSM)},
  title = {Sustainability Guidelines for Long-Living Software Systems},
  url = {http://selab.fbk.eu/icsm2012/},
  year = {2012}
}
@inproceedings{klatt2012a,
  abstract = {Integrating 3rd party components in software systems provides promising advantages but also risks due to disconnected evolution cycles. Deciding whether to migrate to a newer version of a 3rd party component integrated into self-implemented code or to switch to a different one is challenging. Dedicated evolution support for 3rd party component scenarios is hence required. Existing approaches do not account for open source components which allow accessing and analyzing their source code and project information. The approach presented in this paper combines analyses for code dependency, code quality, and bug tracker information for a holistic view on the evolution with 3rd party components. We applied the approach in a case study on a communication middleware component for industrial devices used at ABB. We identified 7 methods potentially impacted by changes of 3rd party components despite the absence of interface changes. We further identified self-implemented code that does not need any manual investigation after the 3rd party component evolution as well as a positive trend of code and bug tracker issues.},
  address = {Szeged, Hungary},
  author = {Benjamin Klatt and Zoya Durdik and Klaus Krogmann and Heiko Koziolek and Johannes Stammel and Roland Weiss},
  booktitle = {Proceedings of the 16th Conference on Software Maintenance and Reengineering (CSMR'12)},
  doi = {10.1109/CSMR.2012.59},
  issn = {1534-5351},
  keywords = {Benchmark testing;Computer bugs;Databases;Manuals;Reliability;Software systems;middleware;program debugging;bug tracker information;code dependency;code quality;communication middleware component;disconnected evolution cycles;industrial devices;long-living software systems;open source components;project information;self-implemented code;third party components;},
  month = {March},
  pages = {461--464},
  pdf = {http://sdqweb.ipd.kit.edu/publications/pdfs/klatt2012a.pdf},
  title = {{Identify Impacts of Evolving Third Party Components on Long-Living Software Systems}},
  year = {2012}
}
@inproceedings{koziolek2011c,
  abstract = {Long-living software systems are sustainable if they can be cost-effectively maintained and evolved over their complete life-cycle. Software-intensive systems in the industrial automation domain are typically long-living and cause high evolution costs, because of new customer requirements, technology changes, and failure reports. Many methods for sustainable software development have been proposed in the scientific literature, but most of them are not applied in industrial practice. We identified typical evolution scenarios in the industrial automation domain and conducted an extensive literature search to extract a number of guidelines for sustainable software development based on the methods found in literature. For validation purposes, we map one evolution scenario to these guidelines in this paper.},
  author = {Heiko Koziolek and Roland Weiss and Zoya Durdik and Johannes Stammel and Klaus Krogmann},
  booktitle = {{Proceedings of Software Engineering (Workshops), 3rd Workshop of GI Working Group Long-living Software Systems (L2S2), Design for Future}},
  isbn = {978-3-88579-278-9},
  pages = {47--58},
  pdf = {http://www.koziolek.de/docs/Koziolek2011-DFF-preprint.pdf},
  publisher = {GI},
  series = {LNI},
  title = {{Towards Software Sustainability Guidelines for Long-living Industrial Systems}},
  volume = {184},
  year = {2011}
}
@inproceedings{seng2006a,
  abstract = {A software system's structure degrades over time, a phenomenon that is known as software decay or design drift. Since the quality of the structure has major impact on the maintainability of a system, the structure has to be reconditioned from time to time. Even if recent advances in the fields of automated detection of bad smells and refactorings have made life easier for software engineers, this is still a very complex and resource consuming task.Search-based approaches have turned out to be helpful in aiding a software engineer to improve the subsystem structure of a software system. In this paper we show that such techniques are also applicable when reconditioning the class structure of a system. We describe a novel search-based approach that assists a software engineer who has to perform this task by suggesting a list of refactorings. Our approach uses an evolutionary algorithm and simulated refactorings that do not change the system's externally visible behavior. The approach is evaluated using the open-source case study JHotDraw.},
  address = {Seattle, Washington, USA},
  author = {Seng, Olaf and Stammel, Johannes and Burkhart, David},
  booktitle = {8th Annual conference on Genetic and evolutionary computation},
  isbn = {1-59593-186-4},
  pages = {1909--1916},
  publisher = {ACM Press},
  title = {{S}earch-based determination of refactorings for improving the class structure of object-oriented systems},
  year = {2006}
}
@inproceedings{stammel09a,
  abstract = {In their lifetime software systems usually need to be adapted in order to fit in a changing environment or to cover new required functionality. The effort necessary for implementing changes is related to the maintainability of the software system. Therefore, maintainability is an important quality aspect of software systems. Today Software Architecture plays an important role in achieving software quality goals. Therefore, it is useful to evaluate software architectures regarding their impact on the quality of the program. However, unlike other quality attributes, such as performance or reliability, there is relatively less work on the impact of the software architecture on maintainability in a quantitative manner. In particular, the cost of software evolution not only stems from software-development activities, such as reimplementation, but also from software management activities, such as re-deployment, upgrade installation, etc. Most metrics for software maintainability base on code of object-oriented designs, but not on architectures, and do not consider costs from software management activities. Likewise, existing current architectural maintainability evaluation techniques manually yield just qualitative (and often subjective) results and also do concentrate on software (re-)development costs. In this paper, we present KAMP, the Karlsruhe Architectural Maintainability Prediction Method, a quantitative approach to evaluate the maintainability of software architectures. Our approach estimates the costs of change requests for a given architecture and takes into account re-implementation costs as well as re-deployment and upgrade activities. We combine several strengths of existing approaches. First, our method evaluates maintainability for concrete change requests and makes use of explicit architecture models. Second, it estimates change efforts using semi-automatic derivation of work plans, bottom-up effort estimation, and guidance in investigation of estimation supports (e.g. design and code properties, team organization, development environment, and other influence factors).},
  author = {Stammel, Johannes and Reussner, Ralf},
  booktitle = {Proceedings of the 1. Workshop des GI-Arbeitskreises Langlebige Softwaresysteme (L2S2): "Design for Future - Langlebige Softwaresysteme"},
  editor = {Engels, Gregor and Reussner, Ralf and Momm, Christof and Sauer, Stefan},
  pages = {87-98},
  title = {KAMP: Karlsruhe Architectural Maintainability Prediction},
  url = {http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-537/},
  year = {2009}
}
@inproceedings{StammelTrifu2011,
  author = {Johannes Stammel and Mircea Trifu},
  booktitle = {Joint Proceedings of the First International Workshop on Model-Driven Software Migration (MDSM 2011) and the Fifth International Workshop on Software Quality and Maintainability (SQM 2011)},
  pages = {56--63},
  publisher = {CEUR-WS.org},
  title = {Tool-Supported Estimation of Software Evolution Effort in Service-Oriented Systems},
  urldate = {http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-708/},
  volume = {708},
  year = {2011}
}
@inproceedings{Weiss2010a,
  abstract = {We identified a set of open issues in the context of software aging and long-living systems with respect to the application domain of industrial automation systems, e.g. process control [7] and SCADA (supervisory control and data acquisition) systems. Existing systems in the automation domain suffer from expensive evolution and maintenance as well as from long release cycles. One of the root causes for this is that longevity was not considered during their construction. Most of the solutions that can be found today are not domain-specific, and tend to focus rather on symptoms than on causes. Therefore, we initiated a research project which has the target to define more clearly what domain-specific longevity means, to survey existing approaches, and to derive methods and techniques for addressing the mentioned problem in the industrial automation domain. In this contribution we present the objectives of this project and outline our state of progress.},
  author = {Roland Weiss and Heiko Koziolek and Johannes Stammel and Zoya Durdik},
  booktitle = {Proceedings of 2nd Workshop of GI Working Group "Long-living Software Systems" (L2S2)},
  title = {Evolution problems in the context of sustainable industrial software systems},
  year = {2010}
}
@inproceedings{rostami2015a,
  acmid = {2737198},
  address = {New York, NY, USA},
  author = {Rostami, Kiana and Stammel, Johannes and Heinrich, Robert and Reussner, Ralf},
  booktitle = {Proceedings of the 11th International ACM SIGSOFT Conference on Quality of Software Architectures},
  isbn = {978-1-4503-3470-9},
  location = {Montreal, QC, Canada},
  numpages = {10},
  pages = {21--30},
  pdf = {http://sdqweb.ipd.kit.edu/publications/pdfs/rostami2015a.pdf},
  publisher = {ACM},
  series = {QoSA '15},
  title = {Architecture-based Assessment and Planning of Change Requests},
  url = {http://dl.acm.org/citation.cfm?id=2737198},
  year = {2015},
  tags = {refereed}
}
@inproceedings{rostami2017a,
  author = {Kiana Rostami and Johannes Stammel and Robert Heinrich and Ralf Reussner},
  title = {Change Impact Analysis by Architecture-based Assessment and Planning},
  booktitle = {Software Engineering 2017, Fachtagung des GI-Fachbereichs Softwaretechnik, 21.-24. Februar 2017, Hannover, Deutschland},
  url = {https://www.gi.de/fileadmin/redaktion/2017_LNI/lni-p-267-komplett.pdf},
  pages = {69--70},
  tags = {refereed},
  year = {2017}
}
@inproceedings{heinrich2015architecture,
  author = {Robert Heinrich and Kiana Rostami and Johannes Stammel and Thomas Knapp and Ralf Reussner},
  booktitle = {Softwaretechnik-Trends},
  pdf = {http://pi.informatik.uni-siegen.de/stt/35_2/01_Fachgruppenberichte/22_R_Heinrich.pdf},
  title = {Architecture-based Analysis of Changes in Information System Evolution},
  volume = {35(2)},
  tags = {refereed},
  year = {2015}
}