Can executable specifications close the gap between software requirements and implementation

Reuven Yagel

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

7 Scopus citations

Abstract

This paper reviews some of the techniques which are considered executable specifications. It explains why, in spite of their apparent benefit, they did not become an industry mainstream (yet) and what might be done about it. At last several future directions, research plans and suggestions are drawn.

Original languageEnglish
Title of host publicationProceedings of the 2nd International Workshop on Software Knowledge, SKY 2011, in Conjunction with IC3K 2011
Pages87-91
Number of pages5
StatePublished - 1 Dec 2011
Externally publishedYes
Event2nd International Workshop on Software Knowledge, SKY 2011, in Conjunction with IC3K 2011 - Paris, France
Duration: 26 Oct 201126 Oct 2011

Publication series

NameProceedings of the 2nd International Workshop on Software Knowledge, SKY 2011, in Conjunction with IC3K 2011

Conference

Conference2nd International Workshop on Software Knowledge, SKY 2011, in Conjunction with IC3K 2011
Country/TerritoryFrance
CityParis
Period26/10/1126/10/11

ASJC Scopus subject areas

  • Information Systems

Fingerprint

Dive into the research topics of 'Can executable specifications close the gap between software requirements and implementation'. Together they form a unique fingerprint.

Cite this