Unifying Requirements and Code: an Example
This work addresses the challenge of making software easier to change and reuse for software engineers, but it appears incremental as it builds on existing ideas without introducing a new paradigm.
The paper tackled the problem of unifying requirements and code in software engineering by developing a unified framework, demonstrating its feasibility through a case study that described a classic example using a programming language to express both domain and machine properties, and assessed its scalability.
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.