mlsanityData to 14 Oct 2026

Unifying Requirements and Code: an Example

arXiv 1602.05395 ↗First posted 17 Feb 2016cs.SEcited by 1

Not on the map. Why?

Abstract (arXiv)

Requirements and code, in conventional software engineering wisdom, belong to entirely different worlds. Is it possible to unify these two worlds? A unified framework could help make software easier to change and reuse. To explore the feasibility of such an approach, the case study reported here takes a classic example from the requirements engineering literature and describes it using a programming language framework to express both domain and machine properties. The paper describes the solution, discusses its benefits and limitations, and assesses its scalability.

Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). First posted on arXiv 17 Feb 2016.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2026: 1.

1 paper.