2004
DOI: 10.1007/978-3-540-30203-2_5
|View full text |Cite
|
Sign up to set email alerts
|

Composition of Relations in Enterprise Architecture Models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
21
0

Year Published

2005
2005
2018
2018

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 20 publications
(23 citation statements)
references
References 8 publications
0
21
0
Order By: Relevance
“…As described by Lankhorst et al [32], the language was created following an extensive collection of requirements both from practitioners and from the literature. Furthermore, care has been taken to construct the language in such a way that relations between concepts are transitive [32,60], which is very useful in the context of fault tree analysis.…”
Section: Modeling Availability From Componentsmentioning
confidence: 99%
“…As described by Lankhorst et al [32], the language was created following an extensive collection of requirements both from practitioners and from the literature. Furthermore, care has been taken to construct the language in such a way that relations between concepts are transitive [32,60], which is very useful in the context of fault tree analysis.…”
Section: Modeling Availability From Componentsmentioning
confidence: 99%
“…Archisurance is an enterprise architecture and modeling case study referred to in [9,16,17,24,25]. It concerns a recent merger of three insurance companies dealing in homeowners' and travel insurance, auto insurance, and legal expense insurance formed to take advantage of synergies between three organizations.…”
Section: Case Study and Instantiated Ea Ontologymentioning
confidence: 99%
“…It is in turn usedBy a BusinessService called PremiumPaymentService which is usedBy a BusinessRole called Customer to obtain information about some claim. A total of 109 individuals are defined similarly to capture most of Archisurance case study from several resources [9,16,17,24,25].…”
Section: Case Study and Instantiated Ea Ontologymentioning
confidence: 99%
See 1 more Smart Citation
“…This is due to the fact abstraction rules may be used to create simplified views on the architecture. These abstractions have a formal basis in an operator that has been derived for the composition of relations (see [20] for the details). For instance, a 'realisation' relation with a consecutive used by' relation may be replaced by a new 'used by' relation that short-circuits a service.…”
Section: Discussionmentioning
confidence: 99%