Fetching the paper…
Reading the bibliography…
Identifying conflicting requirements is a key challenge in software requirement engineering, often overlooked in automated solutions.
A. P. Felty and K. S. Namjoshi, “Feature specification and automated conflict detection,”
2003
Earlier work this paper cites.
A. Egyed and P. Grunbacher, “Identifying requirements conflicts and cooperation: How quality attributes and automated traceability can help,”
2004
Earlier work this paper cites.
M. Kim, S. Park, V. Sugumaran, and H. Yang, “Managing requirements conflicts in software product lines: A goal and scenario based approach,”
2007
Earlier work this paper cites.
V. Sadana and X. F. Liu, “Analysis of conflicts among non-functional requirements using integrated analysis of functional and non-functional requirements,” in
2007
Earlier work this paper cites.
A. Mavin, P. Wilkinson, A. Harwood, and M. Novak, “Easy approach to requirements syntax (ears),” in
2009
Earlier work this paper cites.
C. Rupp, M. Simon, and F. Hocker, “Requirements engineering und management,”
2009
Earlier work this paper cites.
M. Kamalrudin, J. Grundy, and J. Hosking, “Managing consistency between textual requirements, abstract interactions and essential use cases,” in
2010
Earlier work this paper cites.
W. H. Butt, S. Amjad, and F. Azam, “Requirement conflicts resolution: using requirement filtering and analysis,” in
2011
Earlier work this paper cites.
T. Moser, D. Winkler, M. Heindl, and S. Biffl, “Requirements management with semantic technology: An empirical study on automated requirements categorization and conflict analysis,” in
2011
Earlier work this paper cites.
D. Mairiza, D. Zowghi, and V. Gervasi, “Conflict characterization and analysis of non functional requirements: An experimental approach,” in
2013
Earlier work this paper cites.
Z. Chentouf, “Managing oam&p requirement conflicts,”
2014
Cited alongside, same era.
C. D. Manning, M. Surdeanu, J. Bauer, J. R. Finkel, S. Bethard, and D. McClosky, “The stanford corenlp natural language processing toolkit,” in
2014
Cited alongside, same era.
M. Aldekhail, A. Chikh, and D. Ziani, “Software requirements conflict identification: review and recommendations,”
2016
Cited alongside, same era.
T. Viana, A. Zisman, and A. K. Bandara, “Identifying conflicting requirements in systems of systems,” in
2017
Cited alongside, same era.
A. Ferrari, G. O. Spagnolo, and S. Gnesi, “Pure: A dataset of public requirements documents,” in
2017
Cited alongside, same era.
U. Shah, S. Patel, and D. C. Jinwala, “Detecting intra-conflicts in non-functional requirements,”
2021
Later among the works it cites.
G. Abeba and E. Alemneh, “Identification of nonfunctional requirement conflicts: Machine learning approach,” in
2021
Later among the works it cites.
M. Aldekhail and M. Almasri, “Intelligent identification and resolution of software requirement conflicts: Assessment and evaluation.”
2022
Closest in time.
G. Malik, M. Cevik, S. Bera, S. Yildirim, D. Parikh, and A. Basar, “Software requirement-specific entity extraction using transformer models,” in
2022
Closest in time.
OpenAI, “Introducing gpt-3.5 and chatgpt,”
2023
Closest in time.
——, “Gpt-4 technical report,”
2023
alphaXiv searches the wider corpus for related work and actual follow-ups.
alphaXiv is searching for related work…
2018
Cited alongside, same era.
2018
Cited alongside, same era.
N. Reimers and I. Gurevych, “Sentence-bert: Sentence embeddings using siamese bert-networks,”
2019
Cited alongside, same era.
2021
Cited alongside, same era.
S. Das, N. Deb, A. Cortesi, and N. Chaki, “Sentence embedding models for similarity detection of software requirements,”
2021
Cited alongside, same era.
Closest in time.
Meta, “Llama 3 8b,” 2023. [Online]. Available:
2023
Closest in time.
Anthropic, “Claude-3 sonnet,” 2024. [Online]. Available:
2024
Closest in time.
G. Gemini Team, “Gemini 1.5: Unlocking multimodal understanding across millions of tokens of context,” 2024. [Online]. Available:
2024
Closest in time.