{"title":"Requirements Engineering Model (REM): An Assessment Model for Software Vendor Organizations","authors":"Muhammad Yaseen, Zara Karamat","doi":"10.1002/smr.70020","DOIUrl":null,"url":null,"abstract":"<div>\n \n <p>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.</p>\n </div>","PeriodicalId":48898,"journal":{"name":"Journal of Software-Evolution and Process","volume":"37 4","pages":""},"PeriodicalIF":1.7000,"publicationDate":"2025-04-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Journal of Software-Evolution and Process","FirstCategoryId":"94","ListUrlMain":"https://onlinelibrary.wiley.com/doi/10.1002/smr.70020","RegionNum":4,"RegionCategory":"计算机科学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q3","JCRName":"COMPUTER SCIENCE, SOFTWARE ENGINEERING","Score":null,"Total":0}
引用次数: 0
Abstract
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.