Proceedings of the 2006 ACM Symposium on Applied Computing 2006
DOI: 10.1145/1141277.1141569
|View full text |Cite
|
Sign up to set email alerts
|

Describing dynamic software architectures using an extended UML model

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2008
2008
2021
2021

Publication Types

Select...
4
2
2

Relationship

1
7

Authors

Journals

citations
Cited by 16 publications
(8 citation statements)
references
References 12 publications
0
8
0
Order By: Relevance
“…Agent-internal concepts cover various types of existing agents. However, agent-external concepts 5. While one reviewer recommended splitting analysis from design by adding a third layer, this needs careful thought and testing beyond the constraints imposed for this current paper.…”
Section: Metamodel Creationmentioning
confidence: 99%
See 1 more Smart Citation
“…Agent-internal concepts cover various types of existing agents. However, agent-external concepts 5. While one reviewer recommended splitting analysis from design by adding a third layer, this needs careful thought and testing beyond the constraints imposed for this current paper.…”
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%
“…There is a well developed theory around the extensions of this language and the techniques to achieve it. According to [10] the extension mechanisms in UML 2.0 can be divided into "heavyweight" and "lightweight". The first approach allows modifications on the existing meta-models and creating new meta-models with no restrictions; the second approach preserves the meta-model, but it adds changes by applying constraints, stereotypes and profiles over the concepts of the core meta-model [11].…”
Section: A Language Extension Techniquesmentioning
confidence: 99%
“…The literature reports evidence of the complexity of using formal techniques and languages to represent dynamic software architectures (HAN et al, 2005;KALLEL et al, 2012;SMAALI et al, 2014;OQUENDO, 2016) caused mainly by (KACEM et al, 2006): (i) their difficult learning and use -architects unfamiliar with them must devote considerable efforts and time on their use, and (ii) their uncommon use (e.g., in projects that involve static architecture). Therefore, communication among stakeholders is hampered, since most of them do not know those languages and techniques; besides, formal techniques and languages are rarely understood by those who are not part of the architecture design process.…”
Section: Motivation and Problemmentioning
confidence: 99%
“…One of the ways to mitigate the problem of using formal techniques and language to represent dynamic software architecture is to combine semi-formal techniques/languages (such as UML (MILADI et al, 2008)) with formal ones (e.g., graphs (KACEM et al, 2006) 1.3. Objectives 3 or Petri-nets (HUSSEIN et al, 2017)), thus reducing problems of communication among stakeholders, but not decreasing the efforts and time required.…”
Section: Motivation and Problemmentioning
confidence: 99%