EPRAM: A Risk Analysis and Mitigation-Based Evolutionary Prototyping Model for Quality Requirements Development.

dc.contributor.advisorAna (Annie) I. Antón, Chairen_US
dc.contributor.advisorAldo Dagnino, Memberen_US
dc.contributor.advisorJulia Earp, Memberen_US
dc.contributor.advisorLaurie Williams, Memberen_US
dc.contributor.authorCarter, Ryan Aldenen_US
dc.date.accessioned2010-04-02T18:10:05Z
dc.date.available2010-04-02T18:10:05Z
dc.date.issued2001-04-05en_US
dc.degree.disciplineComputer Scienceen_US
dc.degree.levelMaster's Thesisen_US
dc.degree.nameMSen_US
dc.descriptionNorth Carolina State University Theses Computer Science.
dc.description.abstractEvolutionary prototyping focuses on the iteration of software planning, implementation, and evaluation while gathering a correct and consistent set of requirements. The process lends particular strength to building quality software due, in part, to the ongoing clarification of existing requirements and the discovery of previously missing or unknown requirements. Traditionally, however, the iterative reexamination of a system's requirements has not been the panacea that practitioners sought due to the predisposition for requirements creep and the difficulty in managing it. This thesis describes the use of evolutionary prototyping in conjunction with an aggressive risk-mitigation strategy. Together, these techniques support successful requirement discovery and clarification and guard against the negative effects of requirements creep; an aspect that general evolutionary prototyping methodologies have not mastered. These techniques are embodied in a comprehensive software development model, which has been christened as the EPRAM (Evolutionary Prototyping with Risk Analysis and Mitigation) model. To ensure that quality is inherent within this process model, the Software Engineering Institute's (SEI) Capability Maturity Model (CMM) was tailored to conform to the development environments of small teams, projects, and organizations and was used as a mature base upon which to build the model. The model was intentionally designed to comply with the Level 2 Key Process Areas (KPA) of the CMM. Validation of the EPRAM model has occurred on several software development efforts employing the model to support the rapid development of electronic commerce applications.en_US
dc.formatThesis (M.S.)--North Carolina State University.
dc.identifier.otheretd-20010404-143113en_US
dc.identifier.urihttp://www.lib.ncsu.edu/resolver/1840.16/2069
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 NC State University 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.titleEPRAM: A Risk Analysis and Mitigation-Based Evolutionary Prototyping Model for Quality Requirements Development.en_US
dcterms.abstractKeywords: EPRAM, evolutionary prototyping, Capability Maturity Model, risk mitigation, agile process.
dcterms.extentxi, 139 pages : illustrations

Files

Original bundle

Now showing 1 - 1 of 1
No Thumbnail Available
Name:
etd.pdf
Size:
391.47 KB
Format:
Adobe Portable Document Format

Collections