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 lessons learned, we also provide some insights about the use of i* in the specific context of architecting hybrid systems using DHARMA.

Peer Reviewed