2012 · 26 citations · 18 references
ComputingComputer ScienceDocumentationRequirements EngineeringSoftware EngineeringAgile DevelopmentAgile Software DevelopmentRequirements DocumentationRequirements ManagementSoftware DocumentationSoftware TestingAcceptance Test-driven DevelopmentAcceptance TestingAgile ContextsAgile DocumentationAgile SettingsRequirements Engineering ProcessSoftware Development MethodologyTest-driven Development
This article describes how automated acceptance test‑driven development (ATDD) impacts requirements engineering in software development and highlights the need for a proper domain, rigorous development methods, disciplined developers, and dedicated on‑site customers. The study extends an existing framework of inherent risks in requirements engineering by incorporating literature insights and a case study. The authors extend a framework of inherent risks and illustrate that ATDD combines documentation‑centric RE with agile iterative communication. ATDD can mitigate certain inherent risks in requirements engineering.
This article describes how the use of automated acceptance test-driven development (ATDD) impacts requirements engineering in software development. We extend an existing framework of inherent risks in RE by adding knowledge from literature and a case study. We show how ATDD can be seen as a mix of the traditional RE focus on documentation and the agile focus on iterative communication. ATDD can mitigate some of the inherent risks in RE. It also carries with it the need for a proper domain and a very rigorous development method that requires disciplined developers and dedicated customers, preferably on-site.
18
Bashar Nuseibeh, Steve Easterbrook · 2000 · 1.8K citations · Full text
Engineering, Systems Engineering, Criterion-referenced Assessment +11