$\mathcal{F}_{or}\mathcal{MAAD}$ : Towards a Model Driven Approach for Agent Based Application Design

Graja, Zeineb; Regayeg, Amira; Kacem, Ahmed Hadj

doi:10.1007/978-3-642-22636-6_9

Cited by 2 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…From the different published papers, several have been chosen that meet the three following conditions: to claim a new methodology is presented; to have continued the work in other papers; and being supported by tools. The selected works are ASEME (Spanoudakis & Moraitis, 2011), OperA (van Putten et al ., 2009), GorMAS (Argente et al ., 2008), Dsml4mas (Hahn & Fischer, 2008), and ForMAAD (Graja et al ., 2010). Table 4 shows the results of their analysis.…”

Section: Analyzing Current Methodologiesmentioning

confidence: 99%

“…ForMAAD (Graja et al ., 2010) is a reformulation of an older work (Kacem et al ., 2007) to use a model-driven approach. Original ForMAAD focused on how the Z notation could be used to specify MAS.…”

Section: Analyzing Current Methodologiesmentioning

confidence: 99%

“…ForMAAD (Graja et al, 2010) Requirements: no declared tasks StarUML UML notation: requirements specification model Design: cooperation strategy definition, organization structure definition, collective behavior definition, individual behavior definition, translation instructions to Z notation StarUML + XSLT transformations + Z/EVES AML language using UML notation: role identification diagram, organization structure diagram, precedence order graph, activity diagram, class diagram they all could be produced during a requirements phase, since the information concerns what the system requires and what actors are needed, but not how the system is going to do it. Nevertheless, authors mention the use of transformations to map the information contained within these models into agent frameworks, concretely AgentScape, but details are not given.…”

Section: New Methodologiesmentioning

confidence: 99%

See 2 more Smart Citations

Understanding Agent-Oriented Software Engineering methodologies

Gómez-Sanz

Fuentes-Fernández

2015

The Knowledge Engineering Review

View full text Add to dashboard Cite

For many years, the progress in agent-oriented development has focused on tools and methods for particular development phases. This has not been enough for the industry to accept agent technology as we expected. Our hypothesis is that the Agent-Oriented Software Engineering (AOSE) community has not recognized the kind of development methods that industry actually demands. We propose to analyze this hypothesis starting with a more precise definition of what an AOSE methodology should be. This definition is the first step for a review of the current progress of an illustrative selection of methodologies, looking for missing elements and future lines of improvement. The result is an account of how well the AOSE community is meeting the software lifecycle needs. It can be advanced that AOSE methodologies are far from providing all the answers industry requires and that effort has grounded mainly in requirements, design, and implementation phases.

show abstract

Section: Analyzing Current Methodologiesmentioning

confidence: 99%

Section: Analyzing Current Methodologiesmentioning

confidence: 99%

Section: New Methodologiesmentioning

confidence: 99%

See 1 more Smart Citation

Understanding Agent-Oriented Software Engineering methodologies

Gómez-Sanz

Fuentes-Fernández

2015

The Knowledge Engineering Review

View full text Add to dashboard Cite

show abstract

“…Therefore, to check that a model is consistent to its metamodel, it is required, but it is not sufficient, to ensure the quality of a model if we are not using formal notations. The main advantage of formal methods is that they offer the possibility of carrying out reasoning tasks for verification and validation purposes [32]. In the CIM level, the business is represented by the business process view and the domain view.…”

Section: Rq1 -What Languages/notations Are Used To Represent the Cim ...mentioning

confidence: 99%

Transformation From CIM to PIM: a Systematic Mapping

et al. 2022

View full text Add to dashboard Cite

Model Driven Architecture (MDA) is the most prominent and accepted methodology based on the Model Driven Development (MDD) principles. MDA includes three abstraction levels: Computer Independent Models (CIM), Platform Independent models (PIM) and Platform specific models (PSM). MDA encourages the automatic transformation of models as a means to increase the speed of the software development process and to prevent human errors. There are plenty of solutions to transform PIMs to PSMs, however the CIM to PIM transformation does not receive a similar attention. In that sense, this paper aims to describe a systematic mapping to analyze the main characteristics of the approaches that deal with the CIM to PIM transformation as well as to discuss research directions stemming out from our analysis. The results of this mapping study could be a valuable information source for the scientific community in order to know the real advances in this topic and to avoid unnecessary effort dealing with problems that have already been addressed. For example, this study yielded the models at the CIM level that have already been transformed into models at the PIM level. Hence, with this information, the researchers could focus their attention on finding solutions to transform those models at CIM level that have not been transformed into models at PIM level. Likewise, this mapping study provides information regarding the technological support of this type of transformation. This information could be useful for those software projects interested to adopt MDA.INDEX TERMS Model Driven Architecture (MDA), Computer Independent Models (CIM), Platform Independent models (PIM), systematic mapping.

show abstract

$\mathcal{F}_{or}\mathcal{MAAD}$ : Towards a Model Driven Approach for Agent Based Application Design

Cited by 2 publications

References 7 publications

Understanding Agent-Oriented Software Engineering methodologies

Understanding Agent-Oriented Software Engineering methodologies

Transformation From CIM to PIM: a Systematic Mapping

Contact Info

Product

Resources

About