Towards knowledge assisted agile requirements evolution

Kumar, Manish; Ajmeri, Nirav; Ghaisas, Smita

doi:10.1145/1808920.1808924

Cited by 10 publications

(8 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Tais resultados estão em conformidade com os encontrados por Chow e Cao [5] que apresenta fatores críticos de sucesso em projetos ágeis de software, tais como falta de capacidades e habilidades da equipe, ausência de trabalho em equipe; requisitos mal definidos e ausência do cliente. Acrescentando a esta lista, o presente estudo identificou ainda que é outros fatores que dificultam o uso das práticas da ER ágil são a grande variedade de técnicas e práticas possíveis a serem usadas na ER ágil ( [14], [16], [25] e [36]) e a importância de se manter a rastreabilidade entre os artefatos criados ( [12], [23] e [43]).…”

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

Belo Horizonte -MG -Brasil mwerneck@pucminas.br RESUMOPor não possuírem características prescritivas, não há, nos métodos ágeis, uma definição formal sobre como as atividades de Engenharia de Requisitos (ER) devem ser executadas. Isso faz com que haja uma variedade de formas de se definir como serão levantados, priorizados, especificados e validados os requisitos. Assim, torna-se necessário compreender como as pesquisas em ER ágil têm caracterizado estas atividades. O objetivo deste trabalho foi, por meio de uma revisão sistemática da literatura, identificar as práticas e técnicas utilizadas para cada processo da ER em projetos ágeis. O trabalho identificou ainda importantes desafios e lições aprendidas que devem direcionar as evoluções nesta área. ABSTRACTSince agile methods do not have prescriptive characteristics, there is not a formal definition on how Requirements Engineering (RE) activities should be executed. This situation leads to a variety of different forms of defining how requirements are elicited, prioritized, documented and validated. So, it is necessary to comprehend how research on RE have characterized such activities. By using a systematic review approach, the objective of this study was to identify practices and techniques that have been used for each RE process in agile projects. The study also identified challenges and lessons learned that should direct improvements in this area. CCS Concepts• Software and its engineering Software creation and management Software development process management Agile software development • Software and its engineering Software creation and management Designing Software Requirements Analysis.

show abstract

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

show abstract

“…Most projects include both a domain analysis phase, in which project stakeholders analyze related software systems to identify, organize, and represent features common to systems within Recommending Requirements Kumar, Ajmeri, and Ghaisas (2010), proposed a conversation-style recommender for use in agile development in which the system recommends a set of basic user stories (that is, brief descriptions of functionality) and tasks in response to an initial project description. The approach utilizes different ontologies that represent the environmental context, agile requirements, general requirements, and the problem domain.…”

Section: Recommender Systems In Requirements Elicitationmentioning

confidence: 99%

Recommender Systems in Requirements Engineering

Mobasher

Cleland‐Huang

2011

AI Magazine

View full text Add to dashboard Cite

Requirements engineering is the practice of eliciting, analyzing, prioritizing, negotiating, and specifying the requirements for a software-intensive system (Robertson and Robertson 1999). These activities engage various stakeholders in the task of identifying and producing an agreed-upon set of requirements that clearly specify the functionality, behavior, and constraints of the proposed system. The importance of the requirements engineering task is illustrated by several studies, which have shown that requirements-related issues, such as poorly specified requirements (Leffingwell 1997) and incomplete and changing requirements and specifications, are the root cause of many failed projects. To address these problems, researchers and practitioners have developed processes for identifying relevant stakeholders; discovering their needs, wants, and desires for the system; prioritizing and negotiating requirements; and specifying them in understandable, measurable, and testable ways (Robertson and Robertson 1999). In this article we focus particularly on recent efforts to use machine learning and recommender systems technologies for automating requirements engineering processes and enabling stakeholder and designer decision support.In general, the task of a recommender system in any domain is to identify items of interest to a given user of which that user may otherwise be unaware. The recommendation problem is Recommender Systems in Requirements EngineeringBamshad Mobasher and Jane Cleland-Huang

show abstract

“…Recommenders systems have especially been applied to the elicitation and specification of requirements. Some approaches focus on recommending a specific type of requirement (e.g., sustainability requirements [11]) and, in a more general way, nonfunctional requirements [12], while others are applicable to any kind of requirement [13,14]. Other approaches focus on identifying stakeholders that could help during the elicitation process [14,15].…”

Section: Introductionmentioning

confidence: 99%

Personal Recommendations in Requirements Engineering: The OpenReq Approach

Palomares

Franch

Fucci

2018

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Context & motivation] Requirements Engineering (RE) is considered as one of the most critical phases in software development but still many challenges remain open. [Problem] There is a growing trend of applying recommender systems to solve open RE challenges like requirements and stakeholder discovery; however, the existent proposals focus on specific RE tasks and do not give a general coverage for the RE process. [Principal ideas/results] In this research preview, we present the OpenReq approach to the development of intelligent recommendation and decision technologies that support different phases of RE in software projects. Specifically, we present the OpenReq part for personal recommendations for stakeholders. [Contribution] OpenReq aim is to improve and speed up RE processes, especially in large and distributed systems.

show abstract

Towards knowledge assisted agile requirements evolution

Cited by 10 publications

References 1 publication

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Recommender Systems in Requirements Engineering

Personal Recommendations in Requirements Engineering: The OpenReq Approach

Contact Info

Product

Resources

About