Gröner, Markus K.2014-03-142014-03-142002-05-10etd-05232002-234024http://hdl.handle.net/10919/27857Product quality is directly related to how well that product meets the customer's needs and intents. It is paramount, therefore, to capture customer requirements correctly and succinctly. Unfortunately, most development models tend to avoid, or only vaguely define the process by which requirements are generated. Other models rely on formalistic characterizations that require specialized training to understand. To address such drawbacks we introduce the Requirements Generation Model (RGM) that (a) decomposes the conventional "requirements analysis" phase into sub-phases which focus and refine requirements generation activities, (b) constrains and structures those activities, and (c) incorporates a monitoring methodology to assist in detecting and resolving deviations from process activities defined by the RGM. We present an empirical study of the RGM in an industrial setting, and results derived from this study that substantiate the effectiveness of the RGM in producing a better set of requirements.In Copyrightsoftware development lifecyclemethodologysoftware engineeringrequirements engineeringDissertationhttp://scholar.lib.vt.edu/theses/available/etd-05232002-234024/