Separation of concerns for dependable software design
For ‘mixed-criticality’ systems that have both critical and non-critical functions, the greatest leverage on dependability may be at the design level. By designing so that each critical requirement has a small trusted base, the cost of the analysis required for a dependability case might be dram...
| Main Authors: | , |
|---|---|
| Other Authors: | |
| Format: | Article |
| Language: | en_US |
| Published: |
Association for Computing Machinery
2011
|
| Online Access: | http://hdl.handle.net/1721.1/62030 https://orcid.org/0000-0002-0194-3989 https://orcid.org/0000-0003-4864-078X |
| Summary: | For ‘mixed-criticality’ systems that have both critical and
non-critical functions, the greatest leverage on dependability
may be at the design level. By designing so that each
critical requirement has a small trusted base, the cost of the
analysis required for a dependability case might be dramatically
reduced. An implication of this approach is that
conventional object-oriented design may be a liability, because
it leads to ‘entanglement’, and an approach based on
separating services may be preferable. |
|---|