Die Zukunft der Software- & Systementwicklung
Herausforderungen und Potenzial der Digitalisierung
Mittwoch, 15. Februar 2017, WKOÖ
In der Software- und Systementwicklung gibt es viele Herausforderungen:
- Wieviel Digitalisierung benötigt Ihr Software-Produktentwicklungsprozess?
- Sind Sie unsicher wie Ihre Software mit der Hardware zusammenhängt? Was ist von Änderungen betroffen und wurde alles getestet?
- Haben Sie noch die Übersicht, welche Softwareteile in welcher Produktvariante aktiv sind?
- Wie erreichen Sie Produkt-Release-Entscheidungen auf solider Basis?
- Wie erzielen Sie kurze Kommunikationswege und nachvollziehbare Entscheidungen?
Wenn Sie diese Fragen beschäftigen, dann sind Sie bei diesem TIM-Expertentag, am 15. Februar 2017 um 14:00 Uhr in der Wirtschaftskammer OÖ richtig.
Experten der Johannes Kepler Universität (JKU) und des Software Competence Center Hagenberg (SCCH) stellen Lösungsansätze vor und berichten aus der Forschung und Anwendung.
Anmeldung bzw. nähere Auskünfte zur kostenpflichtigen Veranstaltung (EUR 39,00/Person) erteilt Frau Theresa Reisinger, TIM – WKO Oberösterreich, T 05/90909-3548, F -3549, E firstname.lastname@example.org. Zusätzliche Informationen stehen im Internet unter http://www.tim.at/32_DEU_HTML.php zum Download bereit.
Exciting news. My proposal “C4S – Coordination-centric Change and Consistency Support” with Alexander Egyed (Co-PI) has been accepted in the FWF (Austrian Science Fund) Matching Funds program.
I will carry out this project at JKU, specifically the Institute for Software Systems Engineering (ISSE), which I will join as Post-Doc and PI beginning of September. I’m very excited to work with the people at ISSE, given also the outstanding ranking of JKU within in the top 16 institutions worldwide by Microsoft Research.
The research proposal addresses change impact analysis in development efforts of complex, safety-critical software (e.g., air traffic control systems). Such software typically exhibits a long lifecycle, involves various engineers (beyond pure software developers) across the entire development lifecycle and is subject to countless changes in the scope of maintenance and evolution activities. Under such conditions proper impact analysis needs to go beyond knowing which artifacts are affected (traditional traceability). Successfully implementing a change requires awareness which engineers to involve and why, how these engineers should be coordinated and communicate, and how these engineers should correctly propagate changes. Hence, what is an efficient and effective way to support engineers in change impact analysis and consistency maintenance? Pure top-down specified processes are insufficient to provide actionable guidance. This proposed work, therefore, investigates methods and techniques for bottom-up determining the underlying communication, coordination, and joint work relations among engineers, artifacts, and tasks. Monitoring such low-level events enables a holistic bottom-up activity view that constitutes the basis for extensive change management support: (i) Dependency Awareness and Consistency Support: provides sophisticated artifact dependencies and recommendations for maintaining artifact consistency beyond core development activities. (ii) Coordination Know-how Learning: generalizes and extracts insight into which coordination structures prevailed, how much collaboration occurred, and which expertise was involved, thus enabling to deduct how these properties affect the duration, quality outcome, and resource utilization of various development activities required for change implementation; and (iii) Coordination Guidance: provides actionable recommendations for a given change management instance based on previously learned best practices. Key research questions address the challenges of dealing with incomplete, incorrect, and uncertain information in detail.
My work on a framwork for model-driven (i.e., hADL driven) execution of collaboration structures was accepted as a full paper at CAiSE 2016.
Mayr-Dorn C., Dustdar S. (2016) A Framework for Model-driven Execution of Collaboration Structures, In Proceedings of the 28th International Conference on Advanced Information Systems Engineering (CAiSE), June, Ljubljana, Slovenia, Springer, (forthcoming, preprint) – [Supporting Online Material]
Abstract: Human interaction-intensive process environments need collaboration support beyond traditional BPM approaches. Process primitives are ill suited to model and execute collaborations for shared artifact editing, chatting, or voting. To this end, this paper introduces a framework for specifying and executing such collaboration structures. The framework explicitly supports the required human autonomy in shaping the collaboration structure. We demonstrate the application of our framework to an exemplary collaboration-intensive hiring process.
As I recently got married, I’ve changed my family name to Mayr-Dorn. I will keep my email addresses (in addition to my new one: email@example.com), twitter handle, and this blog’s name for sake of continuity. Future papers, however, will carry my new family name. DBLP is able to combine papers from multiple names and I believe Google should be intelligent enough to do the same 😉
Over the last years, I have significantly reworked and enhanced the hADL model. It is time to bring all the information (example models, explanations, tutorials etc) together as a single point of reference for the revised hADL model. I’ve started collecting material on a dedicated page on this blog, and will continue to add material over the next weeks.
End of March I had the pleasure to attend my first Dagstuhl seminar. I quite enjoyed the week of inspiring discussions and talks. Many ideas to follow-up in the next weeks and months to come. My connection and approach to NorMAS is outlined in the following position paper:
Position Paper and Talk Title: Collaboration Pattern Modeling in Support of Norm Specification, Monitoring, and Preservation
Abstract: Collaboration-intensive environments call for technical systems that permit flexible user interactions. Rigid workflows are no suitable collaboration paradigm. As users apply various patterns such as shared artifact, social networks, client/principal, or publish/subscribe for interaction, their cooperative behavior becomes largely determined by norms. In this paper, we make the case for explicit modeling of collaboration patterns as the substrate for specifying, monitoring, and preserving norms. Describing collaboration patterns in the form of human-centric component and connector architecture views provides a means for reasoning on collaboration control, flexibility, and ultimately adaptability. We report on recent work targeting executable collaboration patterns and outline resulting synergies with norms.