Yanja Dajsuren, Eindhoven University of Technology, The Netherlands
Harald Altinger, Audi, Germany
Miroslaw Staron, Chalmers | University of Gothenburg, Sweden
More than a decade ago, the term automotive software engineering was officially introduced in the software community addressing research challenges and technical issues encountering software development in automotive domain. Today automotive vehicles are complex systems with millions of lines of code, dozens of microcontrollers, and intertwined networking system. Self driving cars, (fully) electric vehicles, Car-to-X communications are all enabled by software and new features require more advanced software architecture and engineering approaches suitable for automotive domain. Therefore, to bring together researchers and practitioners in the area of automotive software engineering, the international Workshop on Automotive Software Architecture (WASA) is being organized with the 12th Working IEEE/IFIP Conference on Software Architecture (WICSA) and the 9th CompArch federated conference series, the premier gatherings of software architecture and component based software engineering practitioners and researchers.
Roger Champagne, École de technologie supérieure, Canada
Anne Koziolek, Karlsruhe Institute of Technology, Germany
Designing the software architecture of a non-trivial system is not an easy task, and it requires highly skilled and experienced people. Over the years, researchers have proposed various approaches and tools to try and help software architects with this task. One category of such approaches and tools is that of so-called “design assistants”. This term loosely includes any tool that takes as input some form of requirements for the system to be architected, and potentially an initial design, and interacts with the architect to help him/her concentrate on areas of the design that could use improvement to satisfy the requirements or could be optimized to improve quality or reduce costs. The idea is to assist the architect in a partially automated way. This workshop invites researchers and practitioners interested in the topic of software architecture design assistants in general, to gather feedback on the current status and usage of such tools, and to identify areas requiring more research, thus defining a road map. The workshop organizers also hope to build a community around this topic.
Kung-Kiu Lau, The University of Manchester, United Kingdom
Elisa Yumi Nakagawa, University of São Paulo, Brazil
While WICSA is mainly concerned with software architecture, including architecture description and documentation, variability in architecture, architectures for software product lines, CBSE is concerned with component-based software development, mainly component models, techniques, and supporting tools.
In the context of software architecture, reference architecture refers to a special type of software architecture, which contains the essence of the software architectures of software systems of a given application domain. Reference architectures have been widely explored as a basis for development, standardization, and evolution of software systems. They can also be used as a basis for building product line architectures in the context of software product line engineering.
Component-based techniques for software development create software architectures alongside software systems. So it would seem that such techniques, when based on suitable component models, may be able to enhance the practical significance of reference architectures, by providing techniques for constructing reference architectures, or their key elements, as software artefacts.
The main goal of CobRA 2015 is to bring together researchers and practitioners from both WICSA and CBSE to examine and discuss this challenge and related issues, with a view to identifying directions for future research.