ACM Home Page
Please provide us with feedback. Feedback
ReQuEst: Requirements-driven quality estimator
Full text PdfPdf (128 KB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 30 ,  Issue 1  (January 2005) table of contents
SECTION: Article abstracts with full text online table of contents
Page: 4  
Year of Publication: 2005
ISSN:0163-5948
Authors
D. Janakiram  Indian Institute of Technology, Madras, Chennai, India
M. S. Rajasree  Indian Institute of Technology, Madras, Chennai, India
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 10,   Downloads (12 Months): 47,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1039174.1039194
What is a DOI?

ABSTRACT

Estimating quality of software systems has always been a good practice in software engineering. Presently, quality evaluation techniques are applied only as an afterthought to software design process. However, quality of a software system should be stated based on the end-user's requirement for quality. Based on this observation, this paper proposes an estimation model called ReQuEst (Requirements-driven Quality Estimator). ReQuEst is an attempt to quantitatively estimate the quality of a system being designed from its analysis model. The quality is estimated in terms of adaptability and extendibility which are also important parameters in system design. During requirements analysis, evolving requirements are also analyzed to capture a few quality indicators from them. These indicators are used to compute the requirements for the above parameters from the analysis model. Thus, the analyst can quantitatively specify the quality demands of the system to be designed along with the functional requirements. These quality specifications enable the system designer to precisely design systems meeting the values specified. Further, the model can be used to estimate the maintainability of the system in terms of the above parameters.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
 
4
 
5
{IEE93} IEEE. IEEE Standard 1219: Standard for Software Maintenance. IEEE Computer Society Press, IEEE 1993.
 
6
{IFP} IFPUG. The International Function Point Users' Group (IFPUG). http://www.ifpug.org/.
 
7
{IFP99} IFPUG. Function Point Counting Practices Manual Release 4.1. Westerville, Ohio: International Function Point Users Group, 1999.
 
8
{ISO00} ISO-14598. Standard for Information Technology - Software Product Evaluation - Part I: General Overview. ISO/IEC ISO 14598, 2000.
 
9
 
10
{JC88} Jones and Capers. Feature Points (Function Point Logic for Real Time and System Software). In IFPUG Fall 1988 Conference, Montreal, QuEbec, Oct., August 1988.
 
11
{KCH+90} K. S. Kang, J. Cohen, J. Hess, W. Nowak, and S. Peterson. Feature-Oriented Domain Analysis (FODA) Feasibility Study. Technical Report No. CMU/SEI-90-TR-21 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA, 1990.
 
12
13
 
14

Collaborative Colleagues:
D. Janakiram: colleagues
M. S. Rajasree: colleagues