“…By crowd [48,54,72], by textual data analysis [13,20,25,33,41,42,49,51,52,62,64,80,86,88,89], by prototyping [22], sentiment analysis [21,79], image and unstructured data analysis [21,73] 22…”
Section: Analysis and Validationmentioning
confidence: 99%
“…Requirements validation is the process of making sure that requirements gathered are aligned with the stakeholder's actual needs and are correct, consist and testable. As shown in Table 1, quite a few papers acknowledge that requirements validation in CrowdRE is challenging [28,54,68,72,73]. Requirements Prioritization.…”
Software systems are the joint creative products of multiple stakeholders, including both designers and users, based on their perception, knowledge and personal preferences of the application context. The rapid rise in the use of Internet, mobile and social media applications make it even more possible to provide channels to link a large pool of highly diversified and physically distributed designers and end users, the crowd. Converging the knowledge of designers and end users in requirements engineering process is essential for the success of software systems. In this paper, we report the findings of a survey of the literature on crowd-based requirements engineering research. It helps us understand the current research achievements, the areas of concentration, and how requirements related activities can be enhanced by crowd intelligence. Based on the survey, we propose a general research map and suggest the possible future roles of crowd intelligence in requirements engineering.
“…By crowd [48,54,72], by textual data analysis [13,20,25,33,41,42,49,51,52,62,64,80,86,88,89], by prototyping [22], sentiment analysis [21,79], image and unstructured data analysis [21,73] 22…”
Section: Analysis and Validationmentioning
confidence: 99%
“…Requirements validation is the process of making sure that requirements gathered are aligned with the stakeholder's actual needs and are correct, consist and testable. As shown in Table 1, quite a few papers acknowledge that requirements validation in CrowdRE is challenging [28,54,68,72,73]. Requirements Prioritization.…”
Software systems are the joint creative products of multiple stakeholders, including both designers and users, based on their perception, knowledge and personal preferences of the application context. The rapid rise in the use of Internet, mobile and social media applications make it even more possible to provide channels to link a large pool of highly diversified and physically distributed designers and end users, the crowd. Converging the knowledge of designers and end users in requirements engineering process is essential for the success of software systems. In this paper, we report the findings of a survey of the literature on crowd-based requirements engineering research. It helps us understand the current research achievements, the areas of concentration, and how requirements related activities can be enhanced by crowd intelligence. Based on the survey, we propose a general research map and suggest the possible future roles of crowd intelligence in requirements engineering.
“…The authors in [4] employed a methodology which prescribes how different stakeholder use the same set of requirements virtually and validate those requirements. The authors solved the problem of communication and collaboration between client and requirement engineer.…”
Section: Related Workmentioning
confidence: 99%
“…In the RE process, initially, all the requirements are written in natural language and subsequently the experts analyze these requirements and develop specifications [3], [4].…”
Requirement validation contributes significantly toward the success of software projects. Validating requirements is also essential to ensure the correctness of embedded systems in the auto industry. The auto industry emphasizes a lot on the verification of car designs and shapes. Invalid or erroneous requirements lead to inappropriate designs and degraded product quality. Considering the required expertise and time for requirement validation, significant attention is not devoted to verification and validation of requirements in the industry. Currently, the failure ratio of software projects is significantly higher and the key reason for that appears to be the inappropriate and invalidated requirements at the early stages in the projects. To that end, we propose a model-based approach that uses the existing V&V model. Through virtual prototyping, the proposed approach eliminates the need to validate the requirements after each stage of the project. Consequently, the model is validated after the design phase and the errors in requirements are detected at the earliest stage. In this research, we performed two different case studies for requirement validation in the auto industry by using a modeling-based approach and formal technique using Petri nets. A benefit of the proposed modeling-based approach is that the projects in the auto industry domain can be completed in less time due to effective requirements validation. Moreover, the modeling-based approach minimizes the development time, cost and increases productivity because the majority of the code is automatically generated using the approach.
“…Olsson and Grundy [34] implemented an approach that creates models from requirements descriptions, UML-style use case models and black-box test plans, which are later used for change impact analysis. However, their approach lacks automation and does not consider natural language, but formal models only.…”
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.