Proceedings of the 8th International Conference on Intellectual ...

Mohd Zali Mohd Nor et al.
Domain Knowledge Agent – manages <strong>the</strong> domain knowledge ontology and data. When new
knowledge is added, this agent shall inform relevant users and maintainers. When a new version
is applied, <strong>the</strong> domain knowledge is updated with new best practices and old practices are
deprecated.
Helpdesk Agent – represents <strong>the</strong> role <strong>of</strong> helpdesk staff, by generating new call tickets based on
error reported by User Agent, and assigning <strong>the</strong>m to available helpdesk personnel. If bugs is
valid, Helpdesk Agent shall liaise with MR Agent to create new MR.
MR Agent – O<strong>the</strong>r than creating new MRs, this agent shall also assist planner to approve/reject
MRs, monitor <strong>the</strong> progress <strong>of</strong> MRs and assign MRs to maintainers, via Maintainer Agent.
Maintainer Agent – represents maintainers (analysts, programmers and testers) to monitor MR
statuses and assign to maintainer groups for development. This agent also liaises with Domain
Knowledge Agent and SM Knowledge Agent to obtain information to assist analysts and tester in
<strong>the</strong>ir works.
SM Process Agent – For new artifacts and object changed, SM Knowledge Agent shall update <strong>the</strong>
SM knowledge base, as well as <strong>the</strong> Domain knowledge.
Sample web-based application screen is shown in Figure 3below.
Figure 3: SmCAT sample screen
2. Related works
Agent technology in SM has been used in a few research prototypes such as <strong>the</strong> KM-Mantis (Viscaino
et al.,2003). KM-Mantis uses experience factory concept to capture and reuse knowledge and
expertise generated during SM process. KM-Mantis has five s<strong>of</strong>tware agents (product, activity, client,
user and staff) to support <strong>the</strong> 3 different communities (product, activities and people).
Figure 4: Rodriguez KMS
376