Java and XML data binding
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
The Object Constraint Language: Getting Your Models Ready for MDA
The Object Constraint Language: Getting Your Models Ready for MDA
Eclipse Modeling Framework
IEEE Software
Contributing to Eclipse: Principles, Patterns, and Plugins
Contributing to Eclipse: Principles, Patterns, and Plugins
Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML
Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML
Unified Modeling Language Reference Manual, The (2nd Edition)
Unified Modeling Language Reference Manual, The (2nd Edition)
Eclipse: Building Commercial-Quality Plug-Ins
Eclipse: Building Commercial-Quality Plug-Ins
Model Transformation for Model Driven Development of Semantic Web Enabled Multi-Agent Systems
MATES '07 Proceedings of the 5th German conference on Multiagent System Technologies
From AO Methodologies to MAS Infrastructures: The SODA Case Study
Engineering Societies in the Agents World VIII
Situated process engineering for integrating processes from methodologies to infrastructures
Proceedings of the 2009 ACM symposium on Applied Computing
Towards a DSML for semantic web enabled multi-agent systems
Proceedings of the International Workshop on Formalization of Modeling Languages
Hi-index | 0.00 |
The Model Driven Architecture (MDA) approach uses a platform-independent model to define system functionality, or requirements, using some specification language. The requirements are then translated to a platform-specific model for implementation. An agent architecture based on the human cognitive model of planning, the Cognitive Agent Architecture (Cougaar) is selected for the implementation platform. The resulting Cougaar MDA prescribes certain kinds of models to be used, how those models may be prepared and the relationships of the different kinds of models. Using the existing Cougaar architecture, the level of application composition is elevated from individual components to domain level model specifications in order to generate software artifacts. The software artifacts generation is based on a metamodel. Each component maps to a UML structured component which is then converted into multiple artifacts: Cougaar/Java code, documentation, and test cases.