2008
DOI: 10.1145/1371574.1371576
|View full text |Cite
|
Sign up to set email alerts
|

A metamodel for federation architectures

Abstract: This article proposes a metamodel for describing the architecture of a High Level Architecture (HLA) compliant federation. A salient feature of the Federation Architecture Metamodel (FAMM) is the behavioral description of federates based on live sequence charts. FAMM formalizes the standard HLA Object Model and Federate Interface Specification. FAMM supports processing through automated tools, and in particular through code generation. It is formulated in metaGME, the metamodel for the Generic Modeling Environ… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
26
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 31 publications
(26 citation statements)
references
References 11 publications
(12 reference statements)
0
26
0
Order By: Relevance
“…In FAML, we want to go beyond this OO limitation in modeling runtime objects and provide explicit support for both designtime artefacts (the "classes"-equivalent in AOSE, i.e., agent definitions) and runtime artifacts (the "objects"-equivalent in AOSE, i.e., agents themselves). This differentiation, 6 perhaps considered arbitrary by some, can also add some indication of which stage in the development lifecycle a particular concept is likely to be useful-in comparison with an all-embracing modeling language (ML) like UML [29], which tends to confuse developers simply because it does not give any stage indication of its utility. Concepts in each of the two sets were further designated into two scopes, agent-external and agentinternal-related scopes, since a key differentiator for AOSE is the tight coupling between the software entity (here "agent") and its environment [42].…”
Section: Metamodel Creationmentioning
confidence: 99%
See 1 more Smart Citation
“…In FAML, we want to go beyond this OO limitation in modeling runtime objects and provide explicit support for both designtime artefacts (the "classes"-equivalent in AOSE, i.e., agent definitions) and runtime artifacts (the "objects"-equivalent in AOSE, i.e., agents themselves). This differentiation, 6 perhaps considered arbitrary by some, can also add some indication of which stage in the development lifecycle a particular concept is likely to be useful-in comparison with an all-embracing modeling language (ML) like UML [29], which tends to confuse developers simply because it does not give any stage indication of its utility. Concepts in each of the two sets were further designated into two scopes, agent-external and agentinternal-related scopes, since a key differentiator for AOSE is the tight coupling between the software entity (here "agent") and its environment [42].…”
Section: Metamodel Creationmentioning
confidence: 99%
“…As a result, there are a number of metamodels developed for similar or overlapping domains of software engineering. For instance, there are various metamodels for aspectoriented programming (e.g., [1], [2], [3]), software architectures (e.g., [4], [5], [6]), and multiagent systems (MASs) (main focus of this paper) (e.g., [7], [8]). It would be useful if the different metamodels within the same domain of software engineering (e.g., domain of MAS) could be combined into one, or at least be subsumed by one, metamodel.…”
Section: Introductionmentioning
confidence: 99%
“…Based on the conceptual models that are developed using the metamodels such as BOM, HLA based simulation systems can be designed using the UML (Fowler, 2003) or UML profiles (Guiffard et al, 2006;Ç elik, 2005). Topç u et al (2008) adopt Live Sequence Charts (Brill et al, 2004) to model the behavior of HLA federates in simulation systems. Each of these tools provide support for different aspects of HLA-based simulation development domain.…”
Section: Defined In Sectionmentioning
confidence: 99%
“…More unified solutions are presented by following either the MDA approach [DeAntoni and Babau 2005;Guiffard et al 2006;D'Ambrogio et al 2010;Garro et al 2013;Sarjoughian and Markid 2012] or the MIC approach [Topçu et al 2008;Ç etinkaya et al 2010;Ledeczi et al 2003]. Guiffard et al [2006] provide a study that aims at applying a model driven approach to M&S in the military domain.…”
Section: Introductionmentioning
confidence: 99%
“…The source code can be automatically generated, which results in a significant reduction of programming and implementation efforts. Topçu et al [2008] propose the Federation Architecture Metamodel (FAMM) for describing the architecture of a HLA compliant federation. FAMM supports the behavioral description of federates based on sequence charts and it formalizes the standard HLA object model and federate interface specification.…”
Section: Introductionmentioning
confidence: 99%