A. Senart D. Ayed G. Rey O. Virtanen Continuity A. Senart D. Ayed G. Rey O. Virtanen
Main Issues Adding/subtracting functionality Dependencies Component update is ok Discontinuity in the lifetime, flickering Keeping history might solve this Add more information things should get better (e.g. sofa – person gaining weight) Tradeoff in switching between existing functionality and new functionality (e.g. from voice to display) Real world mapped to system, how to present this?
Scenario: Deployment Plan History must be kept to avoid flickering Component state Adding new features is ok How to support the designer to write deployment plans? Tooling support, e.g. verification, simulation User input taken into account – User studies needed?