|
Published Articles >> Table of Contents >> Abstract
November/December 2004 (Vol. 21, No. 6)
pp. 19-25
A Unified Model of Dependability: Capturing Dependability in Context
Victor Basili, University of Maryland and Fraunhofer Center for Experimental Software Engineering
Paolo Donzelli, University of Maryland
Sima Asgari, University of Maryland
Full Article Text:
   
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2004.30
Send link to a friend
| Abstract |
|
In contemporary societies, individuals and organizations increasingly depend on services delivered by sophisticated software-intensive systems.
Dependability has become a key systems property, which needs to be engineered and guaranteed regardless of continuous, rapid, and unpredictable technological and context changes. But, what is dependability? Dependability relates strictly to the specific goals the system's users want to achieve. So, in different circumstances, dependability implies different system attributes (for example, availability, real-time response, and ability to avoid catastrophic failures and resist adverse conditions), as well as different levels of adherence to such attributes.
Achieving and maintaining dependability can't happen without firmly understanding its meaning. In this perspective, the authors introduce the Unified Model of Dependability, a modeling language that lets you reason about dependability and turn it into clearly defined and implementable system properties. Experience in the NASA High Dependability Computing Program provides a case study for UMD.
|
 References
|
[1] B. Boehm et al., The Nature of Information System Dependability: A Stakeholder/Value Approach, tech. report, Computer Science Dept., Univ. of Southern California, 2003.
[2] B. Bruegge and A.H. Dutoit, Object-Oriented Software Engineering, Prentice Hall, 2004.
[3] I. Rus et al., "Empirical Evaluation Techniques and Methods Used for Achieving and Assessing High Dependability," Proc. Workshop Dependability Benchmarking, 2002, www.ece.cmu.edu/~koopman/dsnwdbwdb02_rus.pdf .
[4] B. Melhart and S. White, "Issues in Defining, Analyzing, Refining, and Specifying System Dependability Requirements," Proc. IEEE Conf. Eng. of Computer Based Systems, IEEE CS Press, 2000, pp. 334–340.
[5] B. Randell, "Dependability— A Unifying Concept," Proc. Workshop Computer Security, Dependability and Assurance: From Needs to Solutions, IEEE CS Press, 1998, pp. 16–25.
[6] MIL-STD-882, System Safety Program Requirements, US Dept. of Defense, 1993.
[7] ISO/IEC 13236, Information Technology: Quality of Service: Framework, ISO/IEC, 1998.
[8] J.-C. Laprie, Dependability: Basic Concepts and Terminology, Dependable Computing and Fault Tolerance, Springer-Verlag, 1992.
[9] S. Asgari et al., "Empirical-Based Estimation of the Effect on Software Dependability of a Technique for Architecture Conformance Verification," Proc. Int'l Conf. Software Eng. 2004 Workshop Architecting Dependable Systems, LNCS 3,069, Springer-Verlag, 2004.
[10] G. Dennis, TSAFE: Building a Trusted Computing Base for Air Traffic Control Software, masters thesis, Computer Science Dept., Massachusetts Inst. Technology, 2003.
[11] N. Jog and B. Shneiderman, "Starfield Information Visualization with Interactive Smooth Zooming," Proc. IFIP 2.6 Visual Databases Systems, Chapman & Hall, 1995, pp. 3–14.
[12] B. Boehm et al., "Using the Win-Win Spiral Model: A Case Study," Computer, July 1998, pp. 33–44.
[13] L.K. Chung et al., Non-Functional Requirements in Software Engineering, Kluwer, 2000.
|
 Additional Information
|
Index Terms- Dependability, availability, real-time response, Unified Model of Dependability
Citation:
Victor Basili, Paolo Donzelli, Sima Asgari,
"A Unified Model of Dependability: Capturing Dependability in Context,"
IEEE Software,
vol. 21,
no. 6,
pp. 19-25,
Nov/Dec,
2004
|
|
RSS Feed