SECO-RCR: A Tool to Manage Requirements Change in Software Ecosystems

Software ecosystems (SECO) are becoming a predominant mode of modern software development and can be defined from different perspectives. From a project perspective, SECO are groups of projects that are developed and co-evolved in the same environment. SECO introduced complexity into requirements management, which is a key process of requirements engineering (RE) and an effective way to ensure software quality. There is difficulty in managing requirements change in open and dynamic environments such as SECO due to the existence of multiple stakeholders that can form distinct crowds in the ecosystem. In SECO, a crowd is a large and heterogeneous user base that provides requirements through multiple communication channels. Hence, meeting the expectations of distinct crowds in SECO requires new RE approaches. This paper presents a tool called Software Ecosystems - Requirements Change Request (SECO-RCR) that applies software repository mining, natural language processing techniques, and machine learning to support requirements change management in SECO. SECO-RCR allows requirements managers to define different RCR and consult different crowds to assist them in their decision making. Apresentação (Youtube): https://youtu.be/2OgCRvrA1Ec

Authors

Institutions

Publication Details

Published
2024-09-30
DOI
https://doi.org/10.5753/sbes.2024.3606
Citations
3
Primary Topic
Business Process Modeling and Analysis
Type
article
Field-Weighted Citation Impact
1.59
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

SECO-RCR: A Tool to Manage Requirements Change in Software Ecosystems

Rodrigo Pereira dos Santos, Laura O. Moraes, Davi Viana, Eduardo dos Santos Gonçalves et al.
3 citations
Business Process Modeling and Analysis
1.59
article

SECO-RCR: A Tool to Manage Requirements Change in Software Ecosystems

Rodrigo Pereira dos Santos, Laura O. Moraes, Davi Viana, Eduardo dos Santos Gonçalves, Paulo Malcher
article en
3 citations

Abstract

Software ecosystems (SECO) are becoming a predominant mode of modern software development and can be defined from different perspectives. From a project perspective, SECO are groups of projects that are developed and co-evolved in the same environment. SECO introduced complexity into requirements management, which is a key process of requirements engineering (RE) and an effective way to ensure software quality. There is difficulty in managing requirements change in open and dynamic environments such as SECO due to the existence of multiple stakeholders that can form distinct crowds in the ecosystem. In SECO, a crowd is a large and heterogeneous user base that provides requirements through multiple communication channels. Hence, meeting the expectations of distinct crowds in SECO requires new RE approaches. This paper presents a tool called Software Ecosystems - Requirements Change Request (SECO-RCR) that applies software repository mining, natural language processing techniques, and machine learning to support requirements change management in SECO. SECO-RCR allows requirements managers to define different RCR and consult different crowds to assist them in their decision making. Apresentação (Youtube): https://youtu.be/2OgCRvrA1Ec

Universidad Filadelfia de México (MX), Universidade Federal do Estado do Rio de Janeiro (BR)
Openalex Percentile: Top 13%
Business Process Modeling and Analysis
1.59
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

SECO-RCR: A Tool to Manage Requirements Change in Software Ecosystems — Rodrigo Pereira dos Santos, Laura O. Moraes, et al. · (2024) | TGRS Research Map | TGRS