Dear Elahe,

Many different types of models are used in various scientific and engineering fields, reflecting the subject matter and the kinds of understanding that is sought in each field. Conceptual modelling techniques in software and information systems engineering have in the past focused mainly on describing and analysing behaviours and structures that are implementable in software. As software systems become ever more complex and densely intertwined with the human social environment, we need models that reflect the social characteristics of complex systems. This chapter reviews the approach taken by the i* framework, highlights its application in several areas, and outlines some open research issues.

In the philosophy of language is any language which arises I* an unpremeditated fashion as the result of the innate facilities for language possessed by the human intellect. A natural language is typical used for communication and may be spoken, signed or written.

i* (pronounced "i star") or i* framework is a modelling language suitable for an early phase of system modelling in order to understand the problem domain. i* modelling language allows to model both as-is and to-be situations. The name i* refers to the notion of distributed intentionality which underlines the framework. It is an approach originally developed for modelling and reasoning about organizational environments and their information systems composed of heterogeneous actors with different, often competing, goals that depend on each other to undertake their tasks and achieve these goals. It covers both actor-oriented and Goal modelling. i* models answer the question WHO and WHY, not what.

i* provides the possibility to achieve information in an early phase of the software engineering process. In former days UML was used to make information visible, but as UML often focuses on organisational objects, which are not so important in the early phase, when the emphasis should be on helping stakeholders gain better understanding of the various possibilities for using information systems in their organizations.

i* provides the possibility to achieve information in an early phase of the software engineering process. In former days UML was used to make information visible, but as UML often focuses on organisational objects, which are not so important in the early phase, when the emphasis should be on helping stakeholders gain better understanding of the various possibilities for using information systems in their organizations.

i* provides an early understanding of the organizational relationships in a business domain. The Use Case development from organizational modelling using i* allows requirement engineers to establish a relationship between the functional requirements of the intended system and the organizational goals previously defined in the organization modelling.

i* is used for the early requirements and UML for late requirements. Thus you have to transform the i* model into a UML model. You can do this by using the following guidelines:

There has been a proliferation of various clones of stakeholder engagement in modelling, or, rather, of the use of modelling in support of a decision-making process that involves stakeholders. In many cases the differences are quite subtle and it may seem that various agencies or groups come up with a new term to serve as a recognised trademark for their efforts. In essence they tend to be doing more or less the same things.have recently proposed literature reviews on participatory modelling: below is a brief overview of various types of stakeholder-based modelling, as well as some stakeholder processes that do not rely on modelling.

regards,

Prem Baboo

http://www.cs.toronto.edu/pub/eric/JMfest09-EY.pdf

http://www3.ischool.utoronto.ca/~yu/SocialModelingBook.html

http://www.cs.toronto.edu/km/istar/#roadmap

http://www.cs.toronto.edu/~eric/#AOIS01talk