Using guidelines to improve quality in software nonfunctional attributes
Software development aims to produce software systems that satisfy two requirement categories: functional and quality. One aspect of software quality is nonfunctional attributes (NFAs), such as security, performance, and availability. Software engineers can meet NFA requirements by applying suitable...
Saved in:
| Main Authors: | , |
|---|---|
| Format: | Article |
| Published: |
Institute of Electrical and Electronics Engineers (IEEE)
2011
|
| Subjects: | |
| Online Access: | http://eprints.um.edu.my/6804/ http://www.computer.org/csdl/mags/so/2011/06/mso2011060072-abs.html |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Summary: | Software development aims to produce software systems that satisfy two requirement categories: functional and quality. One aspect of software quality is nonfunctional attributes (NFAs), such as security, performance, and availability. Software engineers can meet NFA requirements by applying suitable guidelines during software development. However, this process is complicated by the different effects of different guidelines on NFA quality and the relationships among the guidelines themselves. Thus, finding a suitable set of guidelines is not straightforward. This article introduces a step-by-step approach that gives software engineers a suitable guideline set to apply to improve NFA quality during the software development life cycle. The approach manages the effects different guidelines have on both the attributes and the relationships among the guidelines. |
|---|