Show simple item record

dc.contributor.authorGröner, Markus K.en_US
dc.date.accessioned2014-03-14T20:12:29Z
dc.date.available2014-03-14T20:12:29Z
dc.date.issued2002-05-10en_US
dc.identifier.otheretd-05232002-234024en_US
dc.identifier.urihttp://hdl.handle.net/10919/27857
dc.description.abstractProduct 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.en_US
dc.publisherVirginia Techen_US
dc.relation.haspartMarkus_K._Groener_Dissertation.pdfen_US
dc.rightsI hereby certify that, if appropriate, I have obtained and attached hereto a written permission statement from the owner(s) of each third party copyrighted matter to be included in my thesis, dissertation, or project report, allowing distribution as specified below. I certify that the version I submitted is the same as that approved by my advisory committee. I hereby grant to Virginia Tech or its agents the non-exclusive license to archive and make accessible, under the conditions specified below, my thesis, dissertation, or project report in whole or in part in all forms of media, now or hereafter known. I retain all other ownership rights to the copyright of the thesis, dissertation or project report. I also retain the right to use in future works (such as articles or books) all or part of this thesis, dissertation, or project report.en_US
dc.subjectsoftware development lifecycleen_US
dc.subjectmethodologyen_US
dc.subjectsoftware engineeringen_US
dc.subjectrequirements engineeringen_US
dc.titleCapturing Requirements Meeting Customer Intent: A Methodological Approachen_US
dc.typeDissertationen_US
dc.contributor.departmentComputer Scienceen_US
dc.description.degreePh. D.en_US
thesis.degree.namePh. D.en_US
thesis.degree.leveldoctoralen_US
thesis.degree.grantorVirginia Polytechnic Institute and State Universityen_US
thesis.degree.disciplineComputer Scienceen_US
dc.contributor.committeechairArthur, James D.en_US
dc.contributor.committeememberRosenberg, Linda H.en_US
dc.contributor.committeememberLee, John A. N.en_US
dc.contributor.committeememberNance, Richard E.en_US
dc.contributor.committeememberRosson, Mary Bethen_US
dc.identifier.sourceurlhttp://scholar.lib.vt.edu/theses/available/etd-05232002-234024/en_US
dc.date.sdate2002-05-23en_US
dc.date.rdate2003-05-29
dc.date.adate2002-05-29en_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record