2013
DOI: 10.1007/978-3-642-45260-4_7
|View full text |Cite
|
Sign up to set email alerts
|

Supporting Agile Software Development by Natural Language Processing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(5 citation statements)
references
References 11 publications
0
5
0
Order By: Relevance
“…Other artifacts related to a particular methodology could also enhance the performance of the developed tool. For example, if the Scrum context is considered, we could consider the sprints and the backlog information [22] to enhance the quality of the data used to generate or transform artifacts. More studies may be needed to explore the impact of context with NLP.…”
Section: Approaches To Improve the Agile Documentation Process Using ...mentioning
confidence: 99%
See 1 more Smart Citation
“…Other artifacts related to a particular methodology could also enhance the performance of the developed tool. For example, if the Scrum context is considered, we could consider the sprints and the backlog information [22] to enhance the quality of the data used to generate or transform artifacts. More studies may be needed to explore the impact of context with NLP.…”
Section: Approaches To Improve the Agile Documentation Process Using ...mentioning
confidence: 99%
“…NLP has been used to process requirements, gathering artifacts such as use cases [19] and user stories [20]; in fact, there is a preference for using NLP to process user stories [21]. This preference may be due to the user stories' characteristics [22], i.e., simple texts which are structured so that the most important elements of each requirement can be identified and their quality can be checked [23]. User stories are a method of representing requirements using a simple structure such as "Who?…”
Section: Introductionmentioning
confidence: 99%
“…[33] Identify ambiguous user stories [34] Define and measure quality factors from user stories [4], [35] Obtain a security defect reporting form from user stories [36] Indicate duplication between user stories [37] Generate model/artifact Generate a test case from user stories [38]- [43] Generate a class diagram from user stories [44], [45] Generate a sequence diagram from user stories [46] Generate a use case diagram from user stories [47]- [49] Generate a use case scenario from user stories [50] Generate a multi-agent system from user stories [51] Generate a source code from user stories [40] Generate a BPMN diagram from user stories [40] Identify the key abstractions To understand the semantic connection in user stories [52]- [54] Identify topics and summarizing user stories [55], [56] Construct a goal model from a set of user stories. [57] Define ontology for user stories [58] Extract the conceptual model of user stories [59], [60] To find the linguistic structure of user stories [61] Prioritizing and estimation of user story complexity [62], [63] Extracting user stories from text [64]- [66] Trace links between model/NL requirements Tracking the development status of user stories from software artifacts [67] Identify the type of dependency of user stories [68] Traceability user stories and software artifact [69]…”
Section: Fig 4 Authorship Distribution Per Countrymentioning
confidence: 99%
“…Tracing the relationship between these models and NL requirements can assist during the software development process, particularly in inconsistency checking and change management [72]. Three studies focused on tracing the relationship between models and user stories: Plank et al [67] tracked the development status of user stories from software artifacts; Soni and Gaur [68] identified the dependency type of user stories, and Lucassen et al [69] tracked the traceability of user stories and software artifacts.…”
Section: ) Tracing Links Between Model/nl Requirementsmentioning
confidence: 99%
See 1 more Smart Citation