Development of Semantic Web-Enabled BDI Multi-Agent Systems Using SEA_ML: An Electronic Bartering Case Study

• Published in: Applied sciences 2018-05, Vol.8 (5), p.688
• Main Authors: Challenger, Moharram, Tezel, Baris, Alaca, Omer, Tekinerdogan, Bedir, Kardas, Geylani
• Format: Article
• Language: English
• Subjects: agent development methodology; BDI agents; Case studies; Computer science; Content management systems; Internet service providers; Language; Metamodels; model-driven development; multi-agent system; ontology; Semantic web; semantic web service; Semantics; Software development; Software engineering
• ISSN: 2076-3417; 2076-3417
• DOI: 10.3390/app8050688

Researchers developed various metamodels (e.g., [8,9,10]) and DSMLs (e.g., [11,12,13,14,15]) to cope with the challenges encountered on design and implementation of MASs. [...]some fully fledged DSMLs (e.g., [16,17]) exist for developing software agents especially working in semantic web environments where agents can handle the Semantic Web content on behalf of their human users and interact with other semantic web environment entities, such as SWS. According to the experiences gained from the multi-case study [21] conducted by using SEA_ML, the developers can benefit more from this DSML when they use different viewpoints of SEA_ML in a proper way in the development of MAS. [...]in this study, we propose a model-driven MAS development methodology which is based on an extended version of SEA_ML and covers the whole process of analysis, modeling, code generation and fully implementation of a MAS working in the Semantic Web according to the well-known Belief-Desire-Intention (BDI) [22] agent principles. According to OMG’s well-known Model-driven Architecture (MDA) [31], SEA_ML metamodel can be considered as a Platform Independent Metamodel (PIMM) and JACK and OWL-S metamodels can be considered as Platform-specific Metamodels (PSMM). [...]Service Grounding provides information on how to interact with the service. [...]in our study, each SWS modeled in SEA_ML is transformed into an OWL-S Service element and the appropriate Service Profile, Service Model and Service Grounding documents are created for the related SWS. 3.2.1.