Ontological analysis of means-end links

The i* community has raised several main dialects and dozens of variations in the definition of the i* language. Differences may be found related not just to the representation of new concepts but to the very core of the i* language. In previous work we have tackled this issue mainly from a syntactic point of view, using metamodels and syntactic-based model interoperability frameworks. In this paper, we go one step beyond and consider the use of foundational ontologies in general, and UFO in particular, as a way to clarify the meaning of core i* constructs and as the basis to propose a normative definition. We focus here on one of the most characteristics i* constructs, namely means-end links.Postprint (published version

Technology representation in i* modules

In current business practice an integrated approach to represent at the design level the technological infrastructure that gives support to business processes is needed. We argue that it is highly complex considering technology in terms of specific functionalities from the beginning because these functionalities depend on new business requirements produced continually by internal and external changes. However, business-technology integration has been largely neglected in the modeling of business processes, including i* models, considering the technological components as highly abstract entities that do not require further description. In this paper, an overview of our approach to deal with technology representation in i* business process models is presented, which focuses on the identification of quality attributes that are offered by specific technologies and the representation of these technologies using a particular class of i* module. This approach has been explored in a previous work developing an example of a library in which an automatic identification technology is required to support some specific business processess.Peer Reviewe

Technology representation in i* modules

In current business practice an integrated approach to represent at the design level the technological infrastructure that gives support to business processes is needed. We argue that it is highly complex considering technology in terms of specific functionalities from the beginning because these functionalities depend on new business requirements produced continually by internal and external changes. However, business-technology integration has been largely neglected in the modeling of business processes, including i* models, considering the technological components as highly abstract entities that do not require further description. In this paper, an overview of our approach to deal with technology representation in i* business process models is presented, which focuses on the identification of quality attributes that are offered by specific technologies and the representation of these technologies using a particular class of i* module. This approach has been explored in a previous work developing an example of a library in which an automatic identification technology is required to support some specific business processess.Peer Reviewe