Arthur, James D.Groener, Markus K.2013-06-192013-06-191999-11-01http://hdl.handle.net/10919/20024Product quality is a direct reflection of how well it meets the cutomer's needs. Hence, the ability to capture customer requirements correctly and succinctly is paramount. Unfortunately, within software development frameworks the gathering of requirements is one of the more ill-defined and least structured processes. To address this inadequacy, our paper (a) proposes a refinement (or decomposition) to the requirements generation phase that admits to detailed examination and promotes a better understanding of where requirements generation goes wrong,(b) using the results of a preliminary study, identifies where and how miscommunication and requirements omission occur, and (c) outlines a more structured process that can be applied early in the requirements generation process to minimize requirement faults.application/postscriptenIn CopyrightTechnical reportTR-99-05http://eprints.cs.vt.edu/archive/00000509/01/TR-99-05.ps