On the relation between design contracts and errors: a software development strategy

Nordby, Eivind J; Blom, Martin; Brunström, Anna

doi:10.1109/ecbs.2002.999829

Cited by 2 publications

(6 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Briand et al have studied the impact of contracts for testability of object-oriented systems in [25]. Nordby et al [5] have proposed a development methodology based on contracts and showed that it speeds up the testing and integration phases. Other works have focused on contracts as a means for testing [37], [38] or proving [39].…”

Section: Related Workmentioning

confidence: 99%

“…In [5], Nordby et al propose a methodology to use contracts in the different phases of the development process. They distinguish two types of contracts: weak and strong.…”

Section: Related Workmentioning

confidence: 99%

“…Both types of contracts are used at different moments during the development of the software: Strong contracts help in writing unit components and finding internal errors, while weak contracts are used when the component is released for integration. In [5], the authors propose a systematic method to weaken strong contracts. Then, results are given for an industrial case study.…”

Section: Related Workmentioning

confidence: 99%

“…S EVERAL works advocate the use of assertions to improve software quality [1], [2], [3], [4], [5], but very few are actually interested in measuring this improvement. This paper aims at bridging the gap between intuitive understanding of what assertions improve in software and a quantitative, accurate estimate of these improvements.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Design by Contract to Improve Software Vigilance

Traon

Baudry

Jézéquel

2006

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Abstract-Design by Contract is a lightweight technique for embedding elements of formal specification (such as invariants, pre and postconditions) into an object-oriented design. When contracts are made executable, they can play the role of embedded, online oracles. Executable contracts allow components to be responsive to erroneous states and, thus, may help in detecting and locating faults. In this paper, we define Vigilance as the degree to which a program is able to detect an erroneous state at runtime. Diagnosability represents the effort needed to locate a fault once it has been detected. In order to estimate the benefit of using Design by Contract, we formalize both notions of Vigilance and Diagnosability as software quality measures. The main steps of measure elaboration are given, from informal definitions of the factors to be measured to the mathematical model of the measures. As is the standard in this domain, the parameters are then fixed through actual measures, based on a mutation analysis in our case. Several measures are presented that reveal and estimate the contribution of contracts to the overall quality of a system in terms of vigilance and diagnosability.

show abstract

Section: Related Workmentioning

confidence: 99%

“…In [5], Nordby et al propose a methodology to use contracts in the different phases of the development process. They distinguish two types of contracts: weak and strong.…”

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Design by Contract to Improve Software Vigilance

Traon

Baudry

Jézéquel

2006

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Moreover, DbC contributes to less time spent on writing tests [29]. Blom et al [7] presented a DbC-based development strategy and a case study applying it to an enterprise project. They found that the approach resulted in fewer errors and decreased development time.…”

Section: Related Workmentioning

confidence: 99%

A survey on wind power ramp forecasting.

Ferreira¹,

Gama²,

Matias³

et al. 2011

147

119

View full text Add to dashboard Cite

The increasing use of wind power as a source of electricity poses new challenges with regard to both power production and load balance in the electricity grid. This new source of energy is volatile and highly variable. The only way to integrate such power into the grid is to develop reliable and accurate wind power forecasting systems. Electricity generated from wind power can be highly variable at several different timescales: sub-hourly, hourly, daily, and seasonally. Wind energy, like other electricity sources, must be scheduled. Although wind power forecasting methods are used, the ability to predict wind plant output remains relatively low for short-term operation. Because instantaneous electrical generation and consumption must remain in balance to maintain grid stability, wind power's variability can present substantial challenges when large amounts of wind power are incorporated into a grid system. A critical issue is ramp events, which are sudden and large changes (increases or decreases) in wind power. This report presents an overview of current ramp definitions and state-of-the-art approaches in ramp event forecasting.

show abstract

On the relation between design contracts and errors: a software development strategy

Abstract: Abstract

Cited by 2 publications

References 12 publications

Design by Contract to Improve Software Vigilance

Design by Contract to Improve Software Vigilance

A survey on wind power ramp forecasting.

Contact Info

Product

Resources

About