## 4 Conclusion
In addition, generated i* dependencies can be converted to BDI agents to be executable on appropriate agent platforms such as JACK. However, implementation of the required transformations and code generation are not included in the study. [PERSON] et al. [15] propose a language, called JADEL, for the MDD of agents on JADE platform. Instead of covering all features of JADE, JADEL only provides high-level agent-oriented abstractions, namely agents, behaviors, communication ontologies, and interaction protocols. JADEL is supported with a compiler which enables source code generation for implementing agents on JADE platform. However, the related code generation feature of JADEL is not currently functional enough to fully implement JADE agents as also indicated in [15]. The new MAS development methodology, introduced in this paper, differentiates from many of the above MAS development approaches with presenting a complete development process including analysis, design and implementation phases according to MDD principles. In most of these studies (e.g., [8; 9; 13; 15; 56]) only the derivation of metamodels and/or DSMLs is considered without a guide for how those metamodels/DSMLs can be utilized within a structural development process. Only the remaining works in [11; 12; 59] and can be said to describe some sort of MDD processes along with the proposed DSMLs. Benefiting from the features of SEA_ML, the development process, discussed in this paper, enables both modeling and automatic generation of semantic constructs required for the discovery and execution of semantic web services by the agents. Such a development opportunity for agent-semantic web services interactions is not considered in those MDD processes. On the other hand, there are some studies in literature addressing the development of E-barter systems with different approaches. Generally, these studies aim at formalizing the domain and increasing its effectiveness. For example, [PERSON] et al., performed two consecutive studies to create a formal framework for E-barter systems [62; 63]. In their first study [62], they propose a formal framework in which customers are grouped in local markets according to their location, so that a global market takes a tree-like shape. While all these processes are identified, algebraic notation and some microeconomic theory concepts have been used. In addition, a utility function has been defined to indicate the valuation of customers in the exchange of goods. The use of algebra and micro-economy help to eliminate ambiguity and get the scheme of the system. The second study [63] focuses on transactions and shipping costs which are not considered in the first study. The early framework has been extended to include these concepts. Another study to formalize E-barter systems is the study of [PERSON] et al. [64]. This study presents a classical algebra-based language to identify and analyze E-barter systems. This framework also suggests a hierarchical market structure. Product exchanges are made using the agents representing the customers. It is shown that the barter balance of the goods provides a Pareto optimum. These studies focus on the formal representation of E-barter systems while our study mostly focuses on the efficient development of these systems. The market structure in our system is adopted from [64]. However, any other structure and formalism can be integrated into our study. [PERSON] and [PERSON] [65] have developed an approach and its supporting tool that generates test scenarios suitable for the E-Barter system. These scenarios are intended to test the compatibility of the system with the intended functions. System specs were implemented using the Specification and Description Language (SDL) [66]. With this method, design mistakes are prevented in the early stages of development. However, test case generation is not the aim of our study. In the study by [PERSON] et al. [23], an E-barter system have been designed using multi-agent architecture with web services. In this design, BPEL4 WS [67] web services are used.