{"user_id":"5786","place":"University of Tartu, Estonia","citation":{"chicago":"Fockel, Markus, Dietrich Travkin, and Markus von Detten. “Interpreting Story Diagrams for the Static Detection of Software Patterns.” In Proceedings of the 8th International Fujaba Days. University of Tartu, Estonia, 2011.","ama":"Fockel M, Travkin D, von Detten M. Interpreting Story Diagrams for the Static Detection of Software Patterns. In: Proceedings of the 8th International Fujaba Days. ; 2011.","bibtex":"@inproceedings{Fockel_Travkin_von Detten_2011, place={University of Tartu, Estonia}, title={Interpreting Story Diagrams for the Static Detection of Software Patterns}, booktitle={Proceedings of the 8th International Fujaba Days}, author={Fockel, Markus and Travkin, Dietrich and von Detten, Markus}, year={2011} }","short":"M. Fockel, D. Travkin, M. von Detten, in: Proceedings of the 8th International Fujaba Days, University of Tartu, Estonia, 2011.","ieee":"M. Fockel, D. Travkin, and M. von Detten, “Interpreting Story Diagrams for the Static Detection of Software Patterns,” 2011.","apa":"Fockel, M., Travkin, D., & von Detten, M. (2011). Interpreting Story Diagrams for the Static Detection of Software Patterns. Proceedings of the 8th International Fujaba Days.","mla":"Fockel, Markus, et al. “Interpreting Story Diagrams for the Static Detection of Software Patterns.” Proceedings of the 8th International Fujaba Days, 2011."},"department":[{"_id":"76"}],"abstract":[{"text":"Software maintenance tasks require knowledge about the software’s design. Several tools help to identify implementations of software patterns, e.g. Design Patterns, in source code and thus help to reveal the underlying design. In case of the reverse engineering tool suite Reclipse, detection algorithms are generated from manually created, formal pattern specifications. Due to numerous variants that have to be considered, the pattern specification is error-prone. Because of this, the complex, step-wise generation process has to be traceable backwards to identify specification mistakes. To increase the traceability, we directly interpret the detection algorithm models (story diagrams) instead of executing code generated from these models. This way, a reverse engineer no longer has to relate generated code to the story diagrams to find mistakes in pattern specifications.\r\n","lang":"eng"}],"year":"2011","language":[{"iso":"eng"}],"_id":"20975","date_updated":"2022-01-06T06:54:42Z","status":"public","author":[{"full_name":"Fockel, Markus","last_name":"Fockel","orcid":"0000-0002-1269-0702","id":"8472","first_name":"Markus"},{"first_name":"Dietrich","last_name":"Travkin","full_name":"Travkin, Dietrich"},{"first_name":"Markus","last_name":"von Detten","full_name":"von Detten, Markus"}],"date_created":"2021-01-13T13:15:48Z","title":"Interpreting Story Diagrams for the Static Detection of Software Patterns","publication":"Proceedings of the 8th International Fujaba Days","type":"conference"}