Automated classification of non-functional requirements

被引:180
作者
Cleland-Huang, Jane [1 ]
Settimi, Raffaella [1 ]
Zou, Xuchang [1 ]
Solc, Peter [1 ]
机构
[1] Depaul Univ, Sch Comp Sci Telecommun & Informat Syst, Ctr Requirements Engn, Chicago, IL 60604 USA
关键词
non-functional requirements; quality requirements; classification; early aspects;
D O I
10.1007/s00766-007-0045-1
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
This paper describes a technique for automating the detection and classification of non-functional requirements related to properties such as security, performance, and usability. Early detection of non-functional requirements enables them to be incorporated into the initial architectural design instead of being refactored in at a later date. The approach is used to detect and classify stakeholders' quality concerns across requirements specifications containing scattered and non-categorized requirements, and also across freeform documents such as meeting minutes, interview notes, and memos. This paper first describes the classification algorithm and then evaluates its effectiveness through reporting a series of experiments based on 30 requirements specifications developed as term projects by MS students at DePaul University. A new and iterative approach is then introduced for training or retraining a classifier to detect and classify non-functional requirements (NFR) in datasets dissimilar to the initial training sets. This approach is evaluated against a large free-form requirements document obtained from Siemens Logistics and Automotive Organization. Although to the NFR classifier is unable to detect all of the NFRs, it is useful for supporting an analyst in the error-prone task of manually discovering NFRs, and furthermore can be used to quickly analyse large and complex documents in order to search for NFRs.
引用
收藏
页码:103 / 120
页数:18
相关论文
共 31 条
[1]   STATISTICS NOTES - DIAGNOSTIC-TESTS-1 - SENSITIVITY AND SPECIFICITY .3. [J].
ALTMAN, DG ;
BLAND, JM .
BRITISH MEDICAL JOURNAL, 1994, 308 (6943) :1552-1552
[2]   Recovering traceability links between code and documentation [J].
Antoniol, G ;
Canfora, G ;
Casazza, G ;
De Lucia, A ;
Merlo, E .
IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 2002, 28 (10) :970-983
[3]   Discovering early aspects [J].
Baniassad, E ;
Clements, PC ;
Araújo, J ;
Moreira, A ;
Rashid, A ;
Tekinerdogan, B .
IEEE SOFTWARE, 2006, 23 (01) :61-+
[4]   An evaluation of clone detection techniques for identifying crosscutting concerns [J].
Bruntink, M ;
van Deursen, A ;
Tourwé, T ;
van Engelen, R .
20TH IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE, PROCEEDINGS, 2004, :200-209
[5]  
Chung L., 2000, Non-functional Requirements in Software Engineering
[6]  
Clarke S., 2005, ASPECT ORIENTED ANAL
[7]  
Cleland-Huang J, 2005, PROC INT CONF SOFTW, P362
[8]   Utilizing supporting evidence to improve dynamic requirements traceability [J].
Cleland-Huang, J ;
Settimi, R ;
Duan, C ;
Zou, XC .
13TH IEEE INTERNATIONAL CONFERENCE ON REQUIREMENTS ENGINEERING, PROCEEDINGS, 2005, :135-144
[9]  
Cleland-Huang J, 2006, RE'06: 14TH IEEE INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE, PROCEEDINGS, P39
[10]   A framework for integrating non-functional requirements into conceptual models [J].
Cysneiros L.M. ;
Leite J.C.S.D.P. ;
Neto J.D.M.S. .
Requirements Engineering, 2001, 6 (2) :97-115