article_kuester.bib

@article{burger2014b,
  affiliation = {Karlsruhe Institute of Technology},
  author = {Erik Burger and J{\"o}rg Hen{\ss} and Martin K{\"u}ster and Steffen Kruse and Lucia Happe},
  doi = {10.1007/s10270-014-0413-5},
  editor = {Robert France and Bernhard Rumpe},
  issn = {1619-1374},
  journal = {Software \& Systems Modeling},
  pages = {472--496},
  pdf = {https://sdqweb.ipd.kit.edu/publications/pdfs/burger2014b.pdf},
  publisher = {Springer Berlin / Heidelberg},
  title = {{View-Based Model-Driven Software Development with ModelJoin}},
  volume = {15},
  number = {2},
  year = {2014},
  tags = {Vitruv}
}
@article{kuester2013b,
  address = {Karlsruhe, Germany},
  author = {Martin K{\"u}ster and Benjamin Klatt},
  journal = {VKSI Magazin},
  month = {April},
  number = {8},
  pdf = {http://sdqweb.ipd.uka.de/publications/pdfs/kuester2013b.pdf},
  title = {{Generation App - App Generation}},
  url = {http://www.vksi.de},
  year = {2013}
}
@article{kuester2014a,
  abstract = {For the evolution of software, understanding of the context, i.e. history and rationale of the existing artifacts, is crucial to avoid ignorant surgery", i.e. modifications to the software without understanding its design intent. Existing works on recording architecture decisions have mostly focused on architectural models. We extend this to code models, and introduce a catalog of code decisions that can be found in object-oriented systems. With the presented approach, we make it possible to record design decisions that are concerned with the decomposition of the system into interfaces, classes, and references between them, or how exceptions are handled. Furthermore, we indicate how decisions on the usage of Java frameworks (e.g. for dependency injection) can be recorded. All decision types presented are supplied with OCL-constraints to check the validity of the decision based on the linked code model.},
  author = {Martin K{\"u}ster and Klaus Krogmann},
  journal = {Softwaretechnik-Trends},
  month = {May},
  number = {2},
  pages = {58---59},
  title = {{Checkable Code Decisions to Support Software Evolution}},
  url = {http://pi.informatik.uni-siegen.de/stt/34_2/01_Fachgruppenberichte/WSRDFF/wsre_dff_2014-05_submission_d3.pdf},
  volume = {34},
  year = {2014}
}
@article{Kuster2012c,
  author = {K\"{u}ster, Martin and Klatt, Benjamin and Kohnert, Eike and Brandt, Steffen and Tysiak, Johannes},
  journal = {OBJEKTspektrum},
  number = {1},
  title = {Apps aus {K}\"{a}stchen und {L}inien - {M}odellgetriebene {M}ulti-{P}lattformentwicklung mobiler {A}nwendungen},
  url = {http://www.sigs-datacom.de/fachzeitschriften/objektspektrum/archiv/artikelansicht.html?tx_mwjournals_pi1%5Bpointer%5D=0&tx_mwjournals_pi1%5Bmode%5D=1&tx_mwjournals_pi1%5BshowUid%5D=7315},
  year = {2013}
}
@article{klatt2013d-STT,
  abstract = {Change impact analysis aims to provide insights about efforts and effects of a change to be expected, and to prevent missed adaptations. However, the benefit of applying an analysis in a given scenario is not clear. Only a few studies about change impact analysis ap- proaches compare the actual effort spent implement- ing the change with the prediction of the analysis. To gain more insight about change impact analysis benefits, we have performed a case study on chang- ing a software's input data model. We have applied two analyses, using the Java compiler and a depen- dency graph based approach, before implementing the actual change. In this paper, we present the re- sults, showing that i) syntactically required changes have been predicted adequately, iii) changes required for semantical correctness required the major effort but were not predicted at all, and iii) tool support for change impact analysis still needs to be improved.},
  author = {Benjamin Klatt and Martin K\"uster and Klaus Krogmann and Oliver Burkhardt},
  journal = {{Softwaretechnik-Trends}},
  month = {May},
  number = {2},
  pages = {53--54},
  pdf = {http://pi.informatik.uni-siegen.de/stt/33_2/01_Fachgruppenberichte/wsr/17_klatt.pdf},
  publisher = {K{\"o}llen Druck & Verlag GmbH},
  title = {{A Change Impact Analysis Case Study: Replacing the Input Data Model of SoMoX}},
  volume = {33},
  year = {2013}
}