@MASTERSTHESIS\{IMM2015-06900,
    author       = "K. R. Christensen",
    title        = "Requirements as test - Automatic generation of test from structured requirements",
    year         = "2015",
    school       = "Technical University of Denmark, Department of Applied Mathematics and Computer Science",
    address      = "Richard Petersens Plads, Building 324, {DK-}2800 Kgs. Lyngby, Denmark, compute@compute.dtu.dk",
    type         = "",
    note         = "{DTU} supervisor: Ekkart Kindler, ekki@dtu.dk, {DTU} Compute",
    url          = "http://www.compute.dtu.dk/English.aspx",
    abstract     = "The world of software has over the years been tainted with stories about failed projects. Almost everyone has his or her own story about a software system, that did not solve the task, which it was designed to. This indicates either a mismatch between requirements and solution, or simply an erroneous requirement specification.

While in the recent decades, a paradigm shift towards agile methods has occurred, focusing on smaller time-boxed iterations intricately containing every development phase: Design, implementation, documentation and validation. Requirement refinement and elicitation, however, have been left dead-in-the-water in this paradigm shift and remained a de facto waterfall phase with neither feed-back from implementation and validation, nor feed-forward to validation.

Adding enough structure, will automatic generation of artifacts such as documentation, diagrams and even tests from requirements. The latter will provide us with the feedback loops needed. The questions are then, how much structure is needed, how much can be generated, and is it feasible?"
}