article

Using iDAVE to determine availability requirements

Authors:

LiGuo Huang,

Barry BoehmAuthors Info & Claims

ACM SIGSOFT Software Engineering Notes, Volume 30, Issue 4

Pages 1 - 4

https://doi.org/10.1145/1082983.1083295

Published: 17 May 2005 Publication History

Get Access

Abstract

Different systems have different success-critical stakeholders. Even for the same system, these stakeholders may depend on it in different ways for different scenarios. Therefore a one-size-fits-all dependability metric is unachievable in practice. In order to cost-effectively achieve the stakeholders' desired dependability attribute requirements for a given project, we have to solve such problems as how to define an appropriate level for a particular dependability attribute and how much dependability investment is enough for a particular software/scenario class. However, the answers to those questions are traditionally difficult to obtain. This paper uses a hypothetical Lunar Biological Laboratory (LBL) as an example to illustrate how to use the iDAVE model to determine the appropriate levels of availability requirements for different software/scenario classes based on their different ROI profiles.

References

[1]

B. Boehm, L. Huang, A. Jain, and R. Madachy, "The Nature of Information System Dependability: A Stakeholder/Value Approach" (Draft 6)", USC-CSE, December, 2004.

Google Scholar

[2]

B. Boehm, C. Abts, A. W. Brown, S. Chulani, B. Clark, E. Horowitz, R. Madachy, D. Riefer, and B. Steece, Software Cost Estimation with COCOMO II, Prentice Hall, 2000.

Digital Library

Google Scholar

[3]

B. Steece, S. Chulani, and B. Boehm, "Determining Software Quality Using COQUALMO," in Case Studies in Reliability and Maintenance, W. Blischke and D. Murthy, Eds.: Wiley, 2002.

Google Scholar

[4]

B. Boehm, L. Huang, A. Jain and R. Madachy, "The ROI of Software Dependability: The iDAVE Model", IEEE Software, Vol. 21, No. 3, May/June, 2004, pp. 54--61.

Digital Library

Google Scholar

[5]

D. Reifer, B. Boehm, and M. Gangadharan, "Estimating the Cost of Security for COTS Software," Proceedings Second Intl. Conf. COTS-Based Software Systems, February 2003, pp. 178--186.

Digital Library

Google Scholar

[6]

R. DeMillo, Proceedings of NIAP Government-Industry IT Security Forum, March 2001.

Google Scholar

Cited By

View all

Joblin MMauerer WApel SSiegmund JRiehle DBertolino ACanfora GElbaum S(2015)From developer networks to verified communitiesProceedings of the 37th International Conference on Software Engineering - Volume 110.5555/2818754.2818824(563-573)Online publication date: 16-May-2015
https://dl.acm.org/doi/10.5555/2818754.2818824

Index Terms

Using iDAVE to determine availability requirements
1. Software and its engineering
  1. Software creation and management
    1. Designing software
      1. Requirements analysis
    2. Software verification and validation
      1. Software defect analysis
        Software testing and debugging

Recommendations

Using iDAVE to determine availability requirements
3-WoSQ: Proceedings of the third workshop on Software quality

Different systems have different success-critical stakeholders. Even for the same system, these stakeholders may depend on it in different ways for different scenarios. Therefore a one-size-fits-all dependability metric is unachievable in practice. In ...
Performability analysis method from reliability and availability
ICHIT '09: Proceedings of the 2009 International Conference on Hybrid Information Technology

Availability and reliability are important attributes of dependability. Many dependability analysis methodologies measure and predict availability and reliability separately. However, those methodologies cannot reflect real system characteristics since ...
Resilience and survivability in communication networks: Strategies, principles, and survey of disciplines

The Internet has become essential to all aspects of modern life, and thus the consequences of network disruption have become increasingly severe. It is widely recognised that the Internet is not sufficiently resilient, survivable, and dependable, and ...

Comments

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes

ACM SIGSOFT Software Engineering Notes Volume 30, Issue 4

July 2005

1514 pages

ISSN:0163-5948

DOI:10.1145/1082983

Issue’s Table of Contents

3-WoSQ: Proceedings of the third workshop on Software quality
May 2005
75 pages
ISBN:1595931228
DOI:10.1145/1083292

Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the Owner/Author.

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 17 May 2005

Published in SIGSOFT Volume 30, Issue 4

Check for updates

Author Tags

Qualifiers

Article

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

1
Total Citations
View Citations
276
Total Downloads

Downloads (Last 12 months)0
Downloads (Last 6 weeks)0

Reflects downloads up to 02 Mar 2025

Other Metrics

View Author Metrics

Citations

Cited By

View all

Joblin MMauerer WApel SSiegmund JRiehle DBertolino ACanfora GElbaum S(2015)From developer networks to verified communitiesProceedings of the 37th International Conference on Software Engineering - Volume 110.5555/2818754.2818824(563-573)Online publication date: 16-May-2015
https://dl.acm.org/doi/10.5555/2818754.2818824

View Options

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Abstract

References

Cited By

Index Terms

Recommendations