How to find non-functional requirements in system developments

被引:8
作者
Gomez Sotelo, K. I. [1 ]
Baron, C. [1 ]
Esteban, P. [1 ]
Gutierrez Estrada, C. Y. A. [2 ]
Laredo Velazquez, L. de J. [2 ]
机构
[1] Univ Toulouse, CNRS, INSA, UPS,LAAS, Toulouse, France
[2] Inst Tecnol Toluca, Toluca, Estado De Mexic, Mexico
来源
IFAC PAPERSONLINE | 2018年 / 51卷 / 11期
关键词
Systems engineering; requirements; non-functional requirements; requirement taxonomy;
D O I
10.1016/j.ifacol.2018.08.272
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
The current complexity of systems requires a full understanding of stakeholder needs in system design. Later, these needs will become requirements of the system: functional requirements are quite easy to describe for the customer, but finding the non-functional requirements is an actual challenge; however, they are essential to design the system. The objective of this research work is to provide support when defining non-functional requirements. The proposal consists in a requirement classification and a questionnaire that progressively guides the elicitation of stakeholder needs. This method is applied to three case studies, demonstrating its interest and indicating opportunities for improvement. (C) 2018, IFAC (International Federation of Automatic Control) Hosting by Elsevier Ltd. All rights reserved.
引用
收藏
页码:1573 / 1578
页数:6
相关论文
共 21 条
[1]  
Akbayrak B., 2000, HACHETTE U EGITIM FA, V18, P1
[2]  
Badreau S., 2014, INGENIERIE EXIGENCES
[3]  
Blanchard Benjamin S., 2011, Systems Engineering and Analysis
[4]  
Bouchereau V., 2000, BENCHMARKING, V7, P8, DOI DOI 10.1108/14635770010314891
[5]  
Brahm C., 1996, Team Performance Management, V2, P30, DOI DOI 10.1108/13527599610105538
[6]  
De Weck OL., 2012, ESD WORKING PAPER SE
[7]  
Faisandier A., 2015, ENG ARCHITECTING MUL, V1
[8]  
Faisandier A., 2012, Engineering and Architecting Multidisciplinary Systems, V2
[9]  
Glinz M., 2005, Pro- ceedings of the Third World Congress for Software Quality 3WCSQ'05, P55
[10]  
Grispos G., 2017, 11 IEEE INT C RES CH