Enhancing Requirements Engineering in Agile Methodologies by Agent-Oriented Goal Models: Two Empirical Case Studies

Tenso, Tanel; Norta, Alex; Rootsi, Hannes; Taveter, Kuldar; Vorontsova, Irina P.

doi:10.1109/rew.2017.24

Cited by 18 publications

(25 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Almost every source mentions either Use Cases or User Stories, or conjunction of both. Modelling such structures and leaving other models as an optional choice are characteristic of Agile methodologies [12], [13], [8]. Some suggest identifying Epics -large User Stories -and dividing them into smaller ones [12], [8].…”

Section: Advanced Approaches To Object-oriented System Analysis (mentioning

confidence: 99%

“…This form is simple and can assist in recognising actors, their role and value of the activities. T. Tenso et al offer a similar template using different terminology [8].…”

Section: Advanced Approaches To Object-oriented System Analysis (mentioning

confidence: 99%

“…Requirements can be gathered by conducting interviews with customers, creating surveys, analysing the existing business processes, other relevant data and structuring results in such forms as use cases, user stories, software requirements specification, activity diagrams, sequence diagrams etc. [6]- [8]. Thus, it can be concluded that methods to elicit, analyse, specify requirements vary.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Mapping of Activities for Object-Oriented System Analysis

Leimane

Nikiforova

2018

Applied Computer Systems

View full text Add to dashboard Cite

Even though object-oriented approach exists for more than 20 years, there are many issues regarding objectoriented system analysis: ambiguity, incompleteness and redundancy in requirements, difficulties with definition and traceability of non-functional requirements, requirements ignorant of business processes that are important for business operations and others. Although software can be engineered using many methodologies, different approaches to the analysis should be considered as they can provide a solution to the known issues. The paper describes the result of the research on object-oriented system analysis in a form of mapping activities offered in advanced software development methods.

show abstract

Section: Advanced Approaches To Object-oriented System Analysis (mentioning

confidence: 99%

“…This form is simple and can assist in recognising actors, their role and value of the activities. T. Tenso et al offer a similar template using different terminology [8].…”

Section: Advanced Approaches To Object-oriented System Analysis (mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Mapping of Activities for Object-Oriented System Analysis

Leimane

Nikiforova

2018

Applied Computer Systems

View full text Add to dashboard Cite

show abstract

“…5) Motivational Models Leading to User Stories: Part of the inception period in agile is the generation of user stories. Having the motivational model gives us a direct mechanism for deriving user stories (in the spirit of the work presented in [17] • As an academic, I want to meet other academics in an informal and engaging environment, so that I help promoting a positive culture in the department These user stories will be very high level, as the motivational model is intended to capture the motivation of the project. As the student development team move into working in a particular user story, they will have to decompose it into finer grain ones that will become part of the sprint backlog.…”

Section: Motivational Models Within Agile Development Teachingmentioning

confidence: 99%

Teaching Motivational Models in Agile Requirements Engineering

Lorca¹,

Burrows²,

Sterling³

2018

2018 IEEE 8th International Workshop on Requirements Engineering Education and Training (REET)

View full text Add to dashboard Cite

Software engineering courses continually strive to maintain an excellent teaching curriculum that provides students with the agile skills as per industry needs. A particular challenge of teaching requirements engineering is capturing and communicating software requirements without killing team agility with excessive documentation. In many projects, requirements can be ambiguous and inconsistent. It is important to find a middle ground between completely by-passing requirements documentation and writing a complete Software Requirements Specification. In this paper, we report our experiences, presenting a guideline for students and educators who wish to adopt motivational modelling, a lightweight approach to requirements elicitation and modelling, for agile requirements engineering. Motivational modelling is an efficient technique that also represents a good boundary object to support discussions between developers and non-technical clients. Finally, we outline discussion points regarding where motivational models could fit into other agile practices.

show abstract

“…Goal‐oriented requirements engineering has been paid much attention since it emerged, and goal model (GM) is proved to be an effective way to describe requirements and capture the interactions between them [1, 2]. In recent years, GM was broadly adopted for supporting different kinds of software and achieved good results, such as information system [3], self‐adaptive system [4], as well as Apps [5].…”

Section: Introductionmentioning

confidence: 99%

Combining goal model with reviews for supporting the evolution of apps

Liu

et al. 2020

IET softw.

View full text Add to dashboard Cite

To support the iterative development process of Apps, the goal model is not only established to describe the requirements at the early stage but also used for identifying the updating strategy in every iteration. In this process, reviews from users provide valuable information for developers to analyse the model with users sentiments. In this study, the authors combine the goal model with reviews for supporting the evolution of Apps. First, the authors introduce the reviews into the goal model as a new factor by comparing keywords. Second, the users sentiments in reviews are mined, and two kinds of information are gained by analysing the model to help developers make decisions on which goals to be improved in next version: one kind of information is about users sentiments on the goals to evaluate whether users like them; another kind is the impact of updating one goal to others. To validate the proposed approach, they conducted experiments and a survey based on the Apps in Google Play. The results show that the proposed approach can establish relationships between goals and reviews reasonably and further provide useful information for optimising the evolution strategy of the App.

show abstract

Enhancing Requirements Engineering in Agile Methodologies by Agent-Oriented Goal Models: Two Empirical Case Studies

Cited by 18 publications

References 12 publications

Mapping of Activities for Object-Oriented System Analysis

Mapping of Activities for Object-Oriented System Analysis

Teaching Motivational Models in Agile Requirements Engineering

Combining goal model with reviews for supporting the evolution of apps

Contact Info

Product

Resources

About