| dc.contributor |
Laurie A. Williams, Committee Chair |
|
| dc.contributor |
Annie I. Antón, Committee Member |
|
| dc.contributor |
Tao Xie, Committee Member |
|
| dc.contributor |
Mladen A. Vouk, Committee Member |
|
| dc.creator |
Ho, Chih-Wei |
|
| dc.date |
2010-04-02T19:17:21Z |
|
| dc.date |
2010-04-02T19:17:21Z |
|
| dc.date |
2008-11-13 |
|
| dc.date.accessioned |
2023-02-28T17:07:46Z |
|
| dc.date.available |
2023-02-28T17:07:46Z |
|
| dc.identifier |
etd-08152008-180315 |
|
| dc.identifier |
http://www.lib.ncsu.edu/resolver/1840.16/5660 |
|
| dc.identifier.uri |
http://localhost:8080/xmlui/handle/CUHPOERS/265580 |
|
| dc.description |
Performance is an important property for a software system. Performance requirements should be specified and validated before detail design starts. However, some factors that can affect the system performance may not be available during early phases of software development. This dissertation proposes Performance Refinement and Evolution Model (PREM), an evolutionary model for performance requirements specification. A development team may use PREM to specify simple PRs early in the software development process, and add more details when the team gains more knowledge of the system performance.
Two performance requirements improvement approaches were designed based based on PREM. The first approach, called Performance Requirement Improvement from Failure Reports (PRIFF), uses the field failure reported by the customers to improve performance requirements. PRIFF was applied on the requirements and field failure reports for a commercial distributed software system. The results demonstrate that the information in the field failure reports was integrated into the requirements that could be used for the next release. The resulting performance requirements are more complete and more specific than the original ones.
The second approach, called DeNaP, improves the PRs with defect reports that are designated as not a problem (NaP). If a defect report is designated as NaP, the development team does not take any action on the defect report. A NaP defect report wastes the time of the development team and other key stakeholders since resources are spent on analyzing the problem but, in the end, the quality of the software is not improved. Reducing the NaP occurrence rate improves the efficiency of the development team. DeNaP was applied on a firmware development project of an embedded control module from ABB Inc and a file processing system from EMC Corporation. After applying DeNaP, we were able to create new performance requirements and refine the original ones from the NaP defect reports. A survey was conducted to examine the development teams’ reaction to the resulting performance requirements. The results show that more than half of the defect reports could have been avoided given the resulting performance requirements from DeNaP. |
|
| dc.rights |
I 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, dis
sertation, 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. |
|
| dc.subject |
requirements engineering |
|
| dc.subject |
requirements improvement |
|
| dc.subject |
performance requirements |
|
| dc.subject |
software performance |
|
| dc.title |
Performance Requirements Improvement with an Evolutionary Model |
|