2009
DOI: 10.1007/978-3-642-05352-8_5
|View full text |Cite
|
Sign up to set email alerts
|

On the Use of i* for Architecting Hybrid Systems: A Method and an Evaluation Report

Abstract: Abstract. The architectural definition of hybrid software systems is a challenging problem that demands to reconcile stakeholders' strategic needs and components marketplace, whilst defining an appropriate set of services. We have defined a method called DHARMA based on the i* framework. The goal of this paper is to present an experience report about the use of i* in large-scale projects. We provide two different viewpoints: the viewpoint of the stakeholder and the viewpoint of the modeller. Apart from general… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

3
35
0
2

Year Published

2010
2010
2021
2021

Publication Types

Select...
7

Relationship

2
5

Authors

Journals

citations
Cited by 25 publications
(40 citation statements)
references
References 11 publications
(12 reference statements)
3
35
0
2
Order By: Relevance
“…As mentioned above, these changes align with previous work on the use of i* in industrial settings (see e.g. [3]) which points to the fact that in practice some constructs create some confusion and act as an adoption barrier for practitioners. Also, as we will see in the next sections, we adopt three graphical conventions: first, we allow for a tabular representation of i* models, especially useful when models grow; second, we represent direction of dependencies by arrowheads instead of the "D" convention of i*; third, given two dependencies d1 = (n, a1, a2, t) and d2 = (n, a2, a1, t), we can draw these two dependencies using just a single graphical dependency with arrowheads in both directions.…”
Section: Formal Definition Of Patternssupporting
confidence: 81%
See 3 more Smart Citations
“…As mentioned above, these changes align with previous work on the use of i* in industrial settings (see e.g. [3]) which points to the fact that in practice some constructs create some confusion and act as an adoption barrier for practitioners. Also, as we will see in the next sections, we adopt three graphical conventions: first, we allow for a tabular representation of i* models, especially useful when models grow; second, we represent direction of dependencies by arrowheads instead of the "D" convention of i*; third, given two dependencies d1 = (n, a1, a2, t) and d2 = (n, a2, a1, t), we can draw these two dependencies using just a single graphical dependency with arrowheads in both directions.…”
Section: Formal Definition Of Patternssupporting
confidence: 81%
“…It aims at the definition of enterprise architectures using the i* framework [3]. The process resulting from the method (see Fig.…”
Section: The Dharma Methodsmentioning
confidence: 99%
See 2 more Smart Citations
“…In [ 5], the authors report the use of i* for architecting hybrid systems in two industrial experiences at the Etapatelecom Ecuadorian company. One of the cornerstones of the proposed method is the reconciliation of the individual models that the different stakeholders build.…”
Section: Use Of I* In Industrial Projectsmentioning
confidence: 99%