Exploring an Ontological Approach for User Requirements Elicitation in the Design of Online Virtual Agents

Ossowska, Katarzyna; Szewc, Liliana; Weichbroth, Paweł; Garnik, Igor; Sikorski, Marcin

doi:10.1007/978-3-319-46642-2_3

Cited by 15 publications

(7 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is ontologies that have provided detection of duplications and gaps in knowledge based on representation of missing logical links through visualization of cause-and-effect relations between notions and domain conceptualization by fixation of essences and relations. Such visualization of missing logical links reflects which attributes are not enough in the specification, which nonfunctional component characteristics of software quality are influenced by the lack of certain attri- Unlike the agents developed in [15][16][17][18][19][20], the implemented intelligence agent was specially aimed at automation of evaluation of information sufficiency as regards the nonfunctional component characteristics of software quality in the specifications of requirements. Thus, it represents development of the concept of assessing information sufficiency given in [5,13].…”

Section: Discussion Of Results Obtained In Functioning Of the Developmentioning

confidence: 99%

“…Study [16] is dedicated to elimination of uncertainty in software requirements and improvement of communication between the parties concerned through introduction of intelligent agents based on the ontological approach. Authors of [17] propose development of an ontology-based intelligent agent to minimize existing semantic uncertainty when developing a specification of software requirements in a natural (Spanish) language.…”

Section: Literature Review and Problem Statementmentioning

confidence: 99%

“…The proposed agent is also used for automatic generation of main specification elements and automatic plotting of objectives. The agents presented in [16] and [17] are designed for elimination of uncertainty in the existing requirement specifications but they do not check whether all user requirements were represented or whether these requirements are sufficient.…”

Section: Literature Review and Problem Statementmentioning

confidence: 99%

See 2 more Smart Citations

Development of an intelligent agent for analysis of nonfunctional characteristics in specifications of software requirements

Hovorushchenko

Pavlova

Bodnar

2019

EEJET

View full text Add to dashboard Cite

one third of all software projects are successful, reliable and worth spending. Multitudes of errors creep into software at the initial stages of its lifecycle. Vast majority of software-related accidents occur because of errors in specifications of requirements [2]. Software projects with requirement specifications containing insufficiently accurate, incomplete and contradictory information cannot be successful in realization [3]. In addition, the earlier the defect (error, violation, drawback, malfunction) is revealed the cheaper its correction. There-6

show abstract

Section: Discussion Of Results Obtained In Functioning Of the Developmentioning

confidence: 99%

Section: Literature Review and Problem Statementmentioning

confidence: 99%

Section: Literature Review and Problem Statementmentioning

confidence: 99%

See 1 more Smart Citation

Development of an intelligent agent for analysis of nonfunctional characteristics in specifications of software requirements

Hovorushchenko

Pavlova

Bodnar

2019

EEJET

View full text Add to dashboard Cite

show abstract

“…The most common practices such as interviews [46], user stories [47], observations [48], workshops [49] are frequently embedded in iteration-based agile methods. Moreover, the course toward promoting active user participation and involvement has been frequently documented in recent reports and reviews that discuss agile requirements engineering [47], [49], [50].…”

Section: Research Background and Motivationmentioning

confidence: 99%

A Qualitative Study on Non-Functional Requirements in Agile Software Development

Jarzębowicz

Weichbroth

2021

IEEE Access

View full text Add to dashboard Cite

Widespread use of agile software development (ASD) methods can be observed nowadays. Non-functional requirements (NFRs) are often reported to be a problematic issue for agile projects, since ASD methods tend to neglect NFRs while focusing on incremental delivery of functional features. Despite that, only very few studies have explored the requirements engineering practices used in ASD and dedicated particularly to NFRs. Objective: We aimed to identify and investigate the practices used in industrial ASD projects to identify, elicit and document NFRs. Method: We conducted a systematic literature review (SLR) and used its findings to prepare an interview guide. We then conducted a series of semi-structured interviews with 10 experienced practitioners. Results: The SLR revealed a number of strategies related to the timing of NFR identification as well as 13 elicitation practices and 20 documentation techniques. At least some of these findings show discrepancies between ASD theory and practice. The interviews provided a more in-depth understanding of the practices used, and their context. The main findings from the interviews include: practitioners' attempts to start identifying NFRs early in the project, a lack of elicitation techniques aimed at NFRs only, and different choices about documentation techniques, including the additional techniques introduced to cope specifically with NFRs. Conclusions: It was not confirmed that requirements engineering activities related to NFRs are perceived by ASD practitioners as a problem, as they developed effective practices to deal with this issue. Moreover, our findings show that different approaches to NFRs can be used and give satisfactory results.

show abstract

“…We developed a web portal (http://153. 19.52.168) which provides online versions of 8 collaborative games. In these games, a team or a group of stakeholders participates in a collocated session and plays a game to discover requirements, prioritize requirements, or provide feedback related to the development process or the software system being implemented.…”

Section: Introductionmentioning

confidence: 99%

Utilizing online collaborative games to facilitate Agile Software Development

Przybyłek

Kowalski

2018

Proceedings of the 2018 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

Effective collaboration and interaction among the development team and between the team and the customer as well as proactive attitude in initiating and implementing improvements play vital roles in the success of agile projects. The challenge is how to address these social aspects since neither the Agile Manifesto nor the Scrum Guide specify techniques that aid the human side of software development. To fill this gap, we developed a web portal which provides 8 collaborative games to be used in agile software development. The feedback received from a Scrum team, who leveraged the games in an industrial project conducted in OKE Poland, indicates that our approach improves participants' communication, motivation, commitment, and creativity.

show abstract

Exploring an Ontological Approach for User Requirements Elicitation in the Design of Online Virtual Agents

Cited by 15 publications

References 14 publications

Development of an intelligent agent for analysis of nonfunctional characteristics in specifications of software requirements

Development of an intelligent agent for analysis of nonfunctional characteristics in specifications of software requirements

A Qualitative Study on Non-Functional Requirements in Agile Software Development

Utilizing online collaborative games to facilitate Agile Software Development

Contact Info

Product

Resources

About