2018 6th International Conference in Software Engineering Research and Innovation (CONISOFT) 2018
DOI: 10.1109/conisoft.2018.8645899
|View full text |Cite
|
Sign up to set email alerts
|

Adapting Bloom's Taxonomy for an Agile Classification of the Complexity of the User Stories in SCRUM

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 15 publications
(6 citation statements)
references
References 20 publications
0
6
0
Order By: Relevance
“…[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%
See 3 more Smart Citations
“…[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%
“…Ecar et al [63] proposed a functional size measurement method based on user stories and COSMIC methods. Meanwhile, Castillo-Barrera et al [62] used bloom's taxonomy to classify the complexity of user stories.…”
Section: ) Identifying the Key Abstractionsmentioning
confidence: 99%
See 2 more Smart Citations
“…Furthermore, agile practices differ in context and level of detail. For example, they are described in the context of requirements engineering (e.g., User Stories [10]), estimating project effort (e.g., [11]) or product management (e.g., Definition of Done). Also, the variety of agile practices, artifacts, and roles in practice is reflected in the literature, where a different understanding of agile practices prevails, which is shown by different definitions (e.g., [12], [13]).…”
Section: Introductionmentioning
confidence: 99%