There is no excerpt because this is a protected post.
By Pavel Dmitriev The idea of the presenters is to create a large experimentation platform to do A/B testing on features, to decide whether a feature should be included in the software or not. It sounds quite simple, but A/B
By Roberto Verdecchia Architectural Technical Debt (ATD) is a serious problem in SA, as debts have potentially a high impact on the overall technical debt of a system. For example, sub-optimal decision result in immature architectural documentation. So, how can
by Jan Tretmans Many hardware systems – even some Dutch dykes! – are actually “just” software. That dyke one has about 40k elements, whereas the software consists of 100M LOC. As such systems need to interact a lot, it becomes
Presented by Tobias Olsson (because the author didn’t get a visa in time) The idea of the paper is that while transforming you can have bad states that you do not want to reacah, maybe because the system is unstable
Presented by Catia Trubiana In the process of architecting (or better requirements elicitation), many software uncertainties exist, for example, because the customer does not yet know these, or some internal parameters of the software may influence the qualities, without knowing
Presented by Federico Giaimo. Faults in a complex system like a car can be very dangerous. Especially nowadays with self-driving cars. The general way of dealing with faults in the automotive is by recalling the cars, and update them. However,
Another brand new day. Last day went very smoothly, and the format really works well. The papers discussed yesterday and today can be found here: http://dl.acm.org/citation.cfm?id=3129790 (or open it directly with the UU proxy!). paper 4 “Modeling Embedded Systems Using