I am working with software in academia for more than an decade and I had the "Moment" quite often. Palladio appeared just like an ordinary tool to solve my problem. Then, I changed a single parameter of my simulation---some hours later we hunted for a bug in the depths of Palladio. Based on the open source development model of Palladio and a very elegant structure of the source code, we were able to find the root cause of the problem very fast. To start fixing the problem, we "just" had to know when---in simulation time---a measurement of the SimuLizar simulator is valid. This paper summarizes our technical and philosophical discussions that ware needed to make Palladio deliver correct results and not to get lost in the depths of time and duration.
| Identifer | oai:union.ndltd.org:DRESDEN/oai:qucosa.de:bsz:ch1-qucosa-213813 |
| Date | 24 November 2016 |
| Creators | Hilbrich, Marcus, Lehrig, Sebastian, Frank, Markus |
| Contributors | Universität Paderborn, s-lab - Software Quality Lab, Technische Universität Chemnitz, Fakultät für Informatik |
| Publisher | Universitätsbibliothek Chemnitz |
| Source Sets | Hochschulschriftenserver (HSSS) der SLUB Dresden |
| Language | English |
| Detected Language | English |
| Type | doc-type:Other |
| Format | application/pdf, text/plain, application/zip |
Page generated in 0.0023 seconds