Bei der ICSA 2018 in Seattle werden Matthias Naab und Dominik Rost vertreten sein. Am 01.05. halten sie ein Tutorial zur Bewertung von Softwarearchitekturen und am 02.05. einen Vortrag zu Erfahrungen aus dem Aufbau eines Digitalen Ökosystems.
How to Evaluate Software Architectures: Tutorial on Practical Insights on Architecture Evaluation Projects with Industrial Customers
Hier die offizielle Ankündigung und Beschreibung:
„Thorough and continuous architecting is the key to overall success in software engineering, and architecture evaluation is a crucial part of it. This tutorial presents a pragmatic architecture evaluation approach and insights gained from its application in more than 75 projects with industrial customers in the past decade. It presents context factors, empirical data, and example cases, as well as lessons learned on mitigating the risk of change through architecture evaluation.
By providing comprehensive answers to many typical questions and discussing lessons learned, the tutorial allows the audience to not only learn how to conduct architecture evaluations and interpret its results, but also to become aware of risks such as false conclusions, manipulating data, and unsound lines of argument.
The target audience includes both practitioners and researchers. It encourages practitioners to conduct architecture evaluations. At the same time, it offers researchers insights into industrial architecture evaluations, which can inspire future research directions.“
Das Tutorial basiert auf unserem Buch „Pragmatic Evaluation of Software Architectures“.
Wir freuen uns auf viele Teilnehmer und interessante Diskussionen.
Wer nicht zur ICSA kommen kann, hat die Gelegenheit dieses Tutorial auch als Teil des nächsten Architekturseminars im April am IESE zu besuchen.
Architecting a Software-Based Ecosystem for the Automotive Aftermarket:
An Experience Report
Matthias Naab und Dominik Rost präsentieren einen wissenschaftlichen Erfahrungsbericht aus der Kooperation mit unserem Kunden Caruso.
Abstract unseres Papers:
„Software-based ecosystems comprise multiple software systems developed by a multitude of organizations. They are on the one hand technically integrated, often via a dedicated platform forming the center of the ecosystem. On the other hand, the organizations and their systems interact in a way that provides (business) benefits for all participants and leads to new forms of businesses. The ecosystem platform is typically defined, developed and operated by the ecosystem initiator. In the past two years, we have been working on the initiation of an ecosystem and the development of a platform for the automotive aftermarket: a data and service marketplace. As core contributions in this paper, we share the experiences and lessons learned from the early phases from an architect’s point of view. As a background, we first describe our key architecture drivers, the current state of the architecture, and how architecture work is performed. We experienced a substantially extended scope for ecosystem architects, working on the overall ecosystem and the platform. Especially in the beginning, architects have to live with a high degree of uncertainty and fuzziness and have to help shaping and aligning business, technical, and legal aspects. Besides these key insights, we share lessons learned in the following categories: Requirements and Priorities, Architecture and Architecture Work, Platform Releases and Time-to-Market, Partners, Communication, Learning from other Ecosystems.“