Applied software architecture
Describing Software Architecture with UML
WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
Evaluation of the Intel® Core i7 Turbo Boost feature
IISWC '09 Proceedings of the 2009 IEEE International Symposium on Workload Characterization (IISWC)
Practical limits on software dependability: a case study
Ada-Europe'10 Proceedings of the 15th Ada-Europe international conference on Reliable Software Technologies
| Hi-index | 0.00 |
Many systems deliberately manage interference between software components, e.g. through partitioning. When engineers modifying such software determine which items of verification evidence have been invalidated by changes, they consider interference management measures. A complete understanding of interference and its management is crucial when engineers re-use evidence. In prior work, we suggested: (a) a guided process for identifying interference and means of managing it; and (b) a strategy for arguing about interference management. In this paper, we present the results of a case study meant to answer two questions raised by this prior work: (i) which views of the system engineers should consider when identifying interference and its management; and (ii) whether our argument pattern captures a practical way to argue about interference management.