Requirements Elicitation and Specification Using the Agent Paradigm: The Case Study of an Aircraft Turnaround Simulator

Abstract

In this paper, we describe research results arising from a technology transfer exercise on agent-oriented requirements engineering with an industry partner. We introduce two improvements to the state-of-the-art in agent-oriented requirements engineering, designed to mitigate two problems experienced by ourselves and our industry partner: (1) the lack of systematic methods for agent-oriented requirements elicitation and modelling; and (2) the lack of prescribed deliverables in agent-oriented requirements engineering. We discuss the application of our new approach to an aircraft turnaround simulator built in conjunction with our industry partner, and show how agent-oriented models can be derived and used to construct a complete requirements package. We evaluate this by having three independent people design and implement prototypes of the aircraft turnaround simulator, and comparing the three prototypes. Our evaluation indicates that our approach is effective at delivering correct, complete, and consistent requirements that satisfy the stakeholders, and can be used in a repeatable manner to produce designs and implementations. We discuss lessons learnt from applying this approach.

Emotion-led modelling for people-oriented requirements engineering: The case study of emergency systems

“…Abstraction and hierarchy. Consistent with our previous work [28], the higher-level graphical goal models were more useful as shared artifacts in meetings and discussions than the more detailed role models. Further, the hierarchical nature of the goal models allowed us to focus on the highest-level models for the most part, and then drill down into more detail at the lower level for more specific discussions.…”

“…In much of our previous work [28,27,36], our focus has been on the use of agent-oriented models as shared communication tools between stakeholders. In our experience, the lightweight notation and focus on high-level concepts make them useful in early-phase requirements engineering.…”

Teaching Motivational Models in Agile Requirements Engineering

“…This is not the case in an industry setting, where a team may need to present a case to management arguing why the proposed project should go ahead. To mirror this in an educational setting, our students produce a motivational model as part of the business brief to motivate and scope the project [10].…”

“…The models capture roles of all stakeholders involved in the system, the functional goals of the system, the quality goals of the system, and emotional goals, which represent how people want to feel when interacting with the system. Over the past ten years, the elicitation methods for the models have been streamlined from those described in Sterling and Taveter's book [16], for example [10], [11].…”

Combining PosoMAS Method Content with Scrum: Agile Software Engineering for Open Self-Organising Systems

“…The Practice: Agent Environment Design has been updated in response to these necessities. Miller et al [29] advocate-based on their own experiences-to delay the decisions of defining system boundary as long as possible and at least to wait until the stakeholders have formed a shared understanding of the problem. PosoMAS-Scrum supports delaying the decision.…”