Intelligent Support of Requirements Management in Agile Environment

Ambiguity in user stories: A systematic literature review

“…In addition, Gazzerro et al [31] remarked that languages with a different structure than English could also engender confusion as a different disambiguation logic could apply. All three studies concur that due to vagueness (at the syntactic level), the same user story might be translated into different required system features [31,33,67].…”

“…Vagueness at the level of syntactic ambiguity has been observed in the further fragmentation of user story segments into linguistic structures (e. g., subject, verb, adjective) [31,33]. This problem not only impedes the precise interpretation of the expected system structure and behavior [31,67]. It may also result in failure to generate a single system feature from a user story.…”

“…Studies proposing solutions for syntactic ambiguity address problems of vagueness [31,33,67] and inconsistency [42,47]. For increasing the precision of user story articulation, sentence patterns were introduced in [33].…”

“…For increasing the precision of user story articulation, sentence patterns were introduced in [33]. For the same purpose, a parsing technique was proposed in [67], while [31] suggested a human-assisted analysis technique. Those solutions were classified as frameworks.…”

The detection of conflicts in the requirements specification based on an ontological model and a production rule system

“…The proposed approach can be used as part of the intellectual support of the engineering process based on ontological models. The ontology data of requirements can be processed together with the data of other ontologies in the field of requirements engineering described by us in works [2][3][4].…”