Keeping Continuous Deliveries Safe

December 13, 2016 Β· Declared Dead Β· πŸ› 2017 IEEE/ACM 39th International Conference on Software Engineering Companion (ICSE-C)

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Sebastian VΓΆst, Stefan Wagner arXiv ID 1612.04164 Category cs.SE: Software Engineering Citations 10 Venue 2017 IEEE/ACM 39th International Conference on Software Engineering Companion (ICSE-C) Last Checked 3 months ago
Abstract
Allowing swift release cycles, Continuous Delivery has become popular in application software development and is starting to be applied in safety-critical domains such as the automotive industry. These domains require thorough analysis regarding safety constraints, which can be achieved by formal verification and the execution of safety tests resulting from a safety analysis on the product. With continuous delivery in place, such tests need to be executed with every build to ensure the latest software still fulfills all safety requirements. Even more though, the safety analysis has to be updated with every change to ensure the safety test suite is still up-to-date. We thus propose that a safety analysis should be treated no differently from other deliverables such as source-code and dependencies, formulate guidelines on how to achieve this and advert areas where future research is needed.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted