2015 IEEE 19th International Enterprise Distributed Object Computing Conference 2015
DOI: 10.1109/edoc.2015.17
|View full text |Cite
|
Sign up to set email alerts
|

Fundamental Realization Strategies for Multi-view Specification Environments

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
3
3
2

Relationship

2
6

Authors

Journals

citations
Cited by 19 publications
(12 citation statements)
references
References 9 publications
0
12
0
Order By: Relevance
“…It is visible to internal and external clients through the endpoint EP + , and behaves as a regular GraphQL endpoint. In [ATM15], the authors distinguish between projective and synthetic multi-view modeling. The projective approach assumes a pre-existing all-encompassing system model.…”
Section: Problem Statement: Federationmentioning
confidence: 99%
“…It is visible to internal and external clients through the endpoint EP + , and behaves as a regular GraphQL endpoint. In [ATM15], the authors distinguish between projective and synthetic multi-view modeling. The projective approach assumes a pre-existing all-encompassing system model.…”
Section: Problem Statement: Federationmentioning
confidence: 99%
“…Criterion C2 (Pureness) relates to the absence of internal redundancy in the SUM under construction. An essential SUM is "completely free of any internal redundancy" (Atkinson et al, 2015) and dependencies by design. A pragmatic SUM contains redundant information (e.g., because it contains different metamodels that define concepts more than once) that has to be interrelated and kept consistent, and thus only behave as if it was free of dependencies due to internal consistency preservation mechanisms.…”
Section: Design Criteriamentioning
confidence: 99%
“…In order to support the complete life-cycle of a system, ranging from requirements analysis to deployment, the internal structure of the SUM must be able to store all required data in a clean and uniform way. The data in the SUM should thus be free from dependencies and capture all relationships between its inner elements in a redundancy-free way using approaches like Information Compression and Information Expansion (Atkinson et al, 2015). Figure 2 shows an example of an OSM-oriented SUMM corresponding to the information presented in Figure 1.…”
Section: Main Ideasmentioning
confidence: 99%
“…The author wishes to thank the reviewers whose comments helped improve this paper. Some of the insightful references provided [3,4,8,11,13,18] could not be integrated due to lack of time, but will be in an extended version.…”
Section: Acknowledgmentsmentioning
confidence: 99%