Partial Selection of Software Requirements: A Fuzzy Method
International Journal of Fuzzy Systems, ISSN: 2199-3211, Vol: 23, Issue: 7, Page: 2067-2079
2021
- 5Citations
- 2Usage
- 8Captures
Metric Options: Counts1 Year3 YearSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Citations5
- Citation Indexes5
- Usage2
- Abstract Views2
- Captures8
- Readers8
Article Description
Prioritization and selection of requirements are an essential component of software development. The process, however, often leads to ignoring some requirements due to the budget limitations, without considering the impact of those requirements on the values of the selected requirements. That may lead to user dissatisfaction and financial losses in software projects. To mitigate this problem, we propose a method that allows for partial satisfaction (selection) of software requirements rather than ignoring them, when tolerated. To demonstrate the effectiveness of the proposed method, we have carried out experiments; our initial results suggest that the method mitigates value loss by reducing the chances that requirements with positive influences are ignored.
Bibliographic Details
http://www.scopus.com/inward/record.url?partnerID=HzOxMe3b&scp=85107721500&origin=inward; http://dx.doi.org/10.1007/s40815-021-01093-y; https://link.springer.com/10.1007/s40815-021-01093-y; https://link.springer.com/content/pdf/10.1007/s40815-021-01093-y.pdf; https://link.springer.com/article/10.1007/s40815-021-01093-y/fulltext.html; https://ro.uow.edu.au/test2021/1973; https://ro.uow.edu.au/cgi/viewcontent.cgi?article=2982&context=test2021; https://dx.doi.org/10.1007/s40815-021-01093-y; https://link.springer.com/article/10.1007/s40815-021-01093-y
Springer Science and Business Media LLC
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know