Separation of concerns for dependable software design

Authors:
Daniel Jackson;Eunsuk Kang
Affiliations:
Massachusetts Institute of Technology, Cambridge, MA, USA;Massachusetts Institute of Technology, Cambridge, MA, USA
Venue:
Proceedings of the FSE/SDP workshop on Future of software engineering research
Year:
2010

Citing 6
Cited 0

Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Some Conservative Stopping Rules for the Operational Testing of Safety-Critical Software

IEEE Transactions on Software Engineering
N degrees of separation: multi-dimensional separation of concerns

Proceedings of the 21st international conference on Software engineering
Composing Requirements Using Problem Frames

RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Designing Software for Ease of Extension and Contraction

IEEE Transactions on Software Engineering
Software for Dependable Systems: Sufficient Evidence?

Software for Dependable Systems: Sufficient Evidence?

Quantified Score

Hi-index	0.00

Visualization

Abstract

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.