Agents assisted software project management

Abstract

The market opportunities for the field of software engineering have been on the rise for the last three decades. This field of engineering is relatively new and the management of projects in this field, though experiencing greater degrees of assistance from tools, still requires improvements. We present here details of our experiments on how the multi-agent technology can be used to improve the productivity and quality of software project management (SPM) process. We have picked up the quality review management sub-process of SPM and described its modeling using GAIA and its implementation using the JADE framework. We also present a case study and the productivity and quality improvements observed.

Engineering Multi-agent Systems with Statecharts

“…a soccer playing robot for the robocup competition [94], a personal assistant robot [3], production and management in industry 4.0, e.g. safety critical mechatronic systems [29], project management and quality assurance [79], a system integrating IoT (Internet of Things) devices to a MAS-based manufacturing environment [62], simulation, e.g. robotic soccer [61], social simulation [75], playing the wumpus game [68], remote monitoring and health care [1,88].…”

An advanced collaborative environment for software development

“…To support collaborative software development, researchers have proposed different approaches using MAS (Tacla et al [9], Ramos et al [10]). The software agents have been found to be useful in environments where the work load is high, the goal is difficult to achieve and the environment is highly collaborative (Sethuraman et al [11]). According to Tacla et al [9], an MAS can potentially improve the exchange of information among the participants, provide support, improve workflows and procedures controls, and provide convenient user interfaces systems (Paraiso and Barthès [12]).…”

Design of A Multi-Agent System Architecture for the Scrum Methodology

“…Some of the expected outputs from the sprint planning meeting are: the goal of the sprint, the team members that will be involved in the sprint, breakdown of the product backlog items into tasks/sub-tasks that will form the sprint backlog, the estimates of the tasks/sub-tasks for the product backlog items, the sprint backlog and the planned completion date of the sprint. 12 The scrum master then communicates the sprint details to all the other stakeholders.…”