Requirements Engineering Model (REM): An Assessment Model for Software Vendor Organizations

被引:0
作者
Yaseen, Muhammad [1 ]
Karamat, Zara [1 ]
机构
[1] Riphah Int Univ, Fac Comp, Lahore, Pakistan
关键词
requirements analysis; requirements elicitation; requirements engineering; requirements management; requirements specification; requirements validation; MATURITY MODEL; VERIFICATION; MANAGEMENT; ELICITATION; FRAMEWORK; VALIDATION; IMPROVEMENT;
D O I
10.1002/smr.70020
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Requirements engineering (RE) is important phase of software development life cycle. Among different RE phases include, requirements elicitation, requirements analysis, requirements specification, requirements validation, and requirements management. There is essential need of an assessment model where software organization can measure their level of capability to implement requirements engineering. Besides so much advances in this field, there is no such assessment model where organizations can find their level of maturity towards requirements engineering process. In this research, requirements engineering model (REM) is designed and implemented via case studies from different software organizations. For designing REM, literature review of different models was conducted, and levels of REM were finalized. In the first phase, success factors of successful software requirements implementation were identified via systematic literature review (SLR). Furthermore, the identified CSFs are organized into five levels based on Capability Maturity Model Integration (CMMI) and Software Outsourcing Vendors' Readiness Model (SOVRM). Using Motorola assessment technique, REM was evaluated via case studies from different software organizations. As a result of SLR, total of 50 success factors from different phases of requirements engineering were identified from 191 papers and then mapped to five levels of REM. Three case studies were conducted from different companies to evaluate REM. The outcome analysis of case studies shows that different organizations are on different maturity levels of requirements implementation.
引用
收藏
页数:19
相关论文
共 190 条
[41]   AiOLoS: A model for assessing organizational learning in software development organizations [J].
Chouseinoglou, Oumout ;
Iren, Deniz ;
Karagoz, N. Alpay ;
Bilgen, Semih .
INFORMATION AND SOFTWARE TECHNOLOGY, 2013, 55 (11) :1904-1924
[42]  
CondoriFernandez N., 2009, A Systematic Mapping Study on Empirical Evaluation of Software Requirements Specifications Techniques, P502
[43]  
Coughlan J, 2003, INFORM SOFTWARE TECH, V45, P525, DOI [10.1016/S0950-5849(03)00032-6, 10.1016/SO950-5849(03)00032-6]
[44]  
Cysneiros LM, 2004, SPRING INT SER ENG C, V753, P115
[45]  
Dag JNO, 2005, IEEE SOFTWARE, V22, P32, DOI 10.1109/MS.2005.1
[46]   Stakeholders in global requirements engineering: Lessons learned from practice [J].
Damian, Daniela .
IEEE SOFTWARE, 2007, 24 (02) :21-+
[47]   ACHIEVING HIGHER SEI LEVELS [J].
DASKALANTONAKIS, MK .
IEEE SOFTWARE, 1994, 11 (04) :17-24
[48]  
Davey B., 2008, Science Information Technology, V5, P544
[49]  
Davis A., 1993, Proceedings First International Software Metrics Symposium (Cat. No.93TH0518-1), P141, DOI 10.1109/METRIC.1993.263792
[50]  
Davis A., 2006, Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived From a Systematic Review, P179