A practical framework for eliciting and modeling system dependability requirements: Experience from the NASA high dependability computing project

Donzelli, Paolo; Basili, Victor R.

doi:10.1016/j.jss.2005.03.011

Cited by 32 publications

(20 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We turned the problem upside down and asked the nine workshop participants to come up with specific issues related to software quality that should be avoided. To this end, we informally applied the UMD approach [3] for eliciting such requirements, which essentially revolves around asking the stakeholders the following questions: What do you see that should not happen, i.e., what causes you the most trouble? What should be done to mitigate this problem?…”

Section: Workhopmentioning

confidence: 99%

Software quality modeling experiences at an oil company

Lampasona

Heidrich

Basili

et al. 2012

Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement

View full text Add to dashboard Cite

The concept of "software quality" is often hard to capture for an organization. Quality models aim at making the concept more operational by refining the "quality" of software development products and processes into sub-concepts down to the level of concrete metrics and indicators. In practice, it is difficult for an organization to come up with a reliable quality model because quality depends on numerous organizational context factors, and the model as well as the metrics and indicators need to be tailored to the specifics of the organization. This paper presents experiences in developing custom-tailored quality models for an organization, exemplified by Ecopetrol, a Colombian oil and gas company. The general approach taken is illustrated and excerpts from the initial model are presented.

show abstract

Section: Workhopmentioning

confidence: 99%

Software quality modeling experiences at an oil company

Lampasona

Heidrich

Basili

et al. 2012

Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement

View full text Add to dashboard Cite

show abstract

“…Reference [4] stated that quantitative evaluation aids in the analysis of the system behaviour in the presence of faults and provides estimations for the system parameters that provide a higher trustworthiness. But what is needed is to have in mind that dependability is contextually subjective and reflects the particular stakeholders needs [5].…”

Section: The Economic Parameters Of Dependabilitymentioning

confidence: 99%

Hands on Dependability Economics

Tsiakis

Katsaros

2009

2009 Second International Conference on Dependability

View full text Add to dashboard Cite

Abstract-Contemporary societies (from individuals to organizations) depend on services delivered by systems to achieve individual goals, meaning that a system must have engineered and guaranteed dependability, regardless of continuous, rapid and unpredictable technological and context changes. The simplest questions that brought out in the surface are to understand on how to evaluate and how much (money) should we spend on dependability. Dependability risk management is an effective process that with simplicity can determine the likelihood of an accident and the severities of the consequences. On the other hand, we also need quantitative methods, in order to assess the cost of the various measures which can be taken to reduce the dependability risk. In this paper, we survey quantitative methods that can play an important role in Dependability Economics. These methods aim in providing estimations for the economic consequences of lowering dependability levels and the costs to implement dependability.

show abstract

“…From this perspective, we have adopted a requirements engineering approach specially devised to model dependability in context, i.e., the Unified Model of Dependability (UMD) Donzelli and Basili 2006). UMD is both stakeholder-oriented and issue-centered providing a framework that defines a set of dimensions of interest to any stakeholder (i.e., Fig.…”

Section: Modeling Tsafe Dependabilitymentioning

confidence: 99%

“…UMD has been implemented as a web-based tool Donzelli and Basili 2006) organized around two tables: the Table "Scope" (Fig. 3), which allows stakeholders to describe all the services of the system for which dependability could be of concern; and the Table "Issue" (Fig.…”

Section: Modeling Tsafe Dependabilitymentioning

confidence: 99%

Experimenting with software testbeds for evaluating new technologies

et al. 2007

Self Cite

View full text Add to dashboard Cite

The evolution of a new technology depends upon a good theoretical basis for developing the technology, as well as upon its experimental validation. In order to provide for this experimentation, we have investigated the creation of a software testbed and the feasibility of using the same testbed for experimenting with a broad set of technologies. The testbed is a set of programs, data, and supporting documentation that allows researchers to test their new technology on a standard software platform. An important component of this testbed is the Unified Model of Dependability (UMD), which was used to elicit dependability requirements for the testbed software. With a collection of seeded faults and known issues of the target system, we are able to determine if a new technology is adept at uncovering defects or providing other aids proposed by its developers. In this paper, we present the Tactical Separation Assisted Flight Environment (TSAFE) testbed environment for which we modeled and evaluated dependability requirements and defined faults to be seeded for experimentation. We describe two completed experiments that we conducted on the testbed. The first experiment studies a technology that identifies architectural violations and evaluates its ability to detect the violations. The second experiment studies model checking as part of design for verification. We conclude by describing ongoing experimental work studying testing, using the same testbed. Our conclusion is that even though these three experiments are very different in terms of the studied technology, using and re-using the same testbed is beneficial and cost effective.

show abstract

A practical framework for eliciting and modeling system dependability requirements: Experience from the NASA high dependability computing project

Cited by 32 publications

References 12 publications

Software quality modeling experiences at an oil company

Software quality modeling experiences at an oil company

Hands on Dependability Economics

Experimenting with software testbeds for evaluating new technologies

Contact Info

Product

Resources

About