Publication Details

Brown, R. B. K. & Piper, I. C. (2013). What users do: SA&D with the ATSA Method. In R. Pooley, J. Coady, H. Linger, C. Barry, M. Lang & C. Schneider (Eds.), Information Systems Development: Reflections, Challenges and New Directions (pp. 305-316). United States: Springer.


Incomplete or inefficient elicitation, comprehension and transmission of client requirements are all sources of information system (IS) failure rates. Requirements may be missed, misunderstood or miscommunicated for the lack of a single, consistent, informing theory. Structured requirements elicitations techniques impose time delays. Cursory techniques can fail to reach any mutual understanding with the stakeholder. Formal methods can fail to cope with non-functional requirements and coder-oriented methods can put the cart before the horse, delivering something other than required. Agile methods can deliver hasty product, cobbled to meet first-cut requirements, perhaps justified by a notion that users cannot reach stable conclusions.



Link to publisher version (DOI)