One advantage of using the agent paradigm for software engineering is that the concepts used for high-level modelling, such as roles, goals, organisations, and interactions, are accessible to many different stakeholders. Existing research demonstrates that including the stakeholders in the modelling of systems for as long as possible improves the quality of the development and final system because inconsistencies and incorrect behaviour are more likely to be detected early in the development process. In this paper, we propose three changes to the typical requirements engineering process found in AOSE methodologies, with the aim of including stakeholders over the requirements engineering process, effectively using stakeholders as modellers. These changes are: withholding design commitment, delaying the definition of the system boundary, and delaying the stakeholder 'sign-off' of the requirements specification. We discuss our application of these changes to a project with an industry partner, and present anecdotal evidence to suggest that these changes can be effective in maintaining stakeholder involvement.
Lecture notes in computer science: Agent-oriented software engineering XI: selected papers from the 11th International Workshop on Agent Oriented Software Engineering (AOSE 2010), Toronto, Canada, 10-11 May 2010 / Danny Weyns and Marie-Pierre Gleizes (eds.),
Vol. 6788, pp. 62-78