Developing critical software in the modern threat environment
Developing critical software in the modern threat environment
As software becomes ever more embedded into the fabric of society, more systems are becoming critical to large numbers of people, either by design or unintentionally. Even those that may not be considered safety-critical can have a large impact when they fail (e.g. banking systems). Consequently, software can be critical for a number of reasons, including: safety; security; and mission impact of failure. We would expect criticality, along with software requirements, to emerge from coherent, integrated systems-level analyses that include data, security, mission and safety aspects. We have combined software requirements from a number of sources, including those based on the "4+1" software safety principles and those emerging from security considerations, to produce a single list of top-level expectations that any critical software development would be expected to satisfy. This list provides a simple, unified structure that may, for example, be used to organize audits or promote discussion between customer and supplier.
Stevens, Brian
d5eade5b-4533-4580-b7a3-33e638da3b1a
Ashmore, Rob
ced9b20c-79c4-47d7-8463-a01cf256ec54
Margheri, Andrea
4b87c32d-3eaf-445e-8ac0-8207daace2e1
Sassone, Vladimiro
df7d3c83-2aa0-4571-be94-9473b07b03e7
February 2019
Stevens, Brian
d5eade5b-4533-4580-b7a3-33e638da3b1a
Ashmore, Rob
ced9b20c-79c4-47d7-8463-a01cf256ec54
Margheri, Andrea
4b87c32d-3eaf-445e-8ac0-8207daace2e1
Sassone, Vladimiro
df7d3c83-2aa0-4571-be94-9473b07b03e7
Stevens, Brian, Ashmore, Rob, Margheri, Andrea and Sassone, Vladimiro
(2019)
Developing critical software in the modern threat environment.
Safety Critical System Symposium.
05 - 07 Feb 2019.
17 pp
.
Record type:
Conference or Workshop Item
(Paper)
Abstract
As software becomes ever more embedded into the fabric of society, more systems are becoming critical to large numbers of people, either by design or unintentionally. Even those that may not be considered safety-critical can have a large impact when they fail (e.g. banking systems). Consequently, software can be critical for a number of reasons, including: safety; security; and mission impact of failure. We would expect criticality, along with software requirements, to emerge from coherent, integrated systems-level analyses that include data, security, mission and safety aspects. We have combined software requirements from a number of sources, including those based on the "4+1" software safety principles and those emerging from security considerations, to produce a single list of top-level expectations that any critical software development would be expected to satisfy. This list provides a simple, unified structure that may, for example, be used to organize audits or promote discussion between customer and supplier.
Text
SafetyCriticalSystemSymposium_2019
Available under License Other.
More information
Submitted date: 2018
Published date: February 2019
Venue - Dates:
Safety Critical System Symposium, 2019-02-05 - 2019-02-07
Identifiers
Local EPrints ID: 425808
URI: http://eprints.soton.ac.uk/id/eprint/425808
PURE UUID: 8e60860e-49b1-41f5-a3b4-aa2198404f8c
Catalogue record
Date deposited: 05 Nov 2018 17:30
Last modified: 15 Mar 2024 22:29
Export record
Contributors
Author:
Brian Stevens
Author:
Rob Ashmore
Author:
Vladimiro Sassone
Download statistics
Downloads from ePrints over the past year. Other digital versions may also be available to download e.g. from the publisher's website.
View more statistics
