i*

i* (pronounced "i star") or i* framework is a modeling language suitable for an early phase of system modeling in order to understand the problem domain. i* modeling 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 modeling. i* models answer the question WHO and WHY, not what.

In contrast, the UML Use case approach covers only functional goals, with actors directly involved in operations (typically with software). The KAOS approach covers goals of all types but is less concerned with the intentionality of actors.

Elements

The model describes dependencies among actors. There are four elements to describe them: goal, soft goal, task and resource. The central concept in i* is in fact that of the intentional actor. Organizational actors are viewed as having intentional properties such as goals, beliefs, abilities, and commitments (concept of distributed intentionality). Actors depend on each other for goals to be achieved, tasks to be performed and resources to be furnished. By depending on others, an actor may be able to achieve goals that are difficult or impossible to achieve on its own; on the other hand, an actor becomes vulnerable if the depended-on actors do not deliver. Actors are strategic in the sense that they are concerned about opportunities and vulnerabilities, and seek rearrangement of their environments that would better serve their interests by restructuring intentional relationships.

Models

i* framework consists of two main modeling components:

Strategic Dependency model (SD)

An SD model describes a network of dependency relationships among various actors in an organisational context. The actor is usually identified within the context of the model. This model shows who an actor is and who depend on the work of an actor.

An SD model consists of a set of nodes and links connecting the actors. Nodes represent actors and each link represents a dependency between two actors. The depending actor is called Depender and the actor who is depended upon is called the Dependee.

Strategic Rationale model (SR)

An SR model allows modeling of the reasons associated with each actor and their dependencies, and provides information about how actors achieve their goals and soft goals. This model includes only elements considered as important enough to impact the results of a goal.

The SR model shows the dependencies of the actors by including the SD model. Relating to these dependencies, the SR model specifies goals, soft goals, tasks and resources. Compared with SD models, SR models provide a more detailed level of modeling by looking inside actors to model internal, intentional relationships. Intentional elements (goals, soft goals, tasks, resources) appear in the SR model not only as external dependencies, but also as internal elements linked by means-ends relationships and task-decompositions. The means-end links provide understanding about why an actor would engage in some tasks, pursue a goal, need a resource, or want a soft goal; the task-decomposition links provide a hierarchical description of intentional elements that make up a routine. Such a model is used to describe stakeholder interests and concerns, and how they might be addressed by different configurations of systems and environments.

Reasons for using i*

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* models offer a number of levels of analysis, in terms of ability, workability, viability and believability.

Benefits of i* and Use Case Integration

i* provides an early understanding of the organizational relationships in a business domain. The Use Case development from organizational modeling 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 modeling.

Goal modeling

i* can be used in requirements engineering to understand the problem domain. SD models and SR models can then be used to develop use cases. This is an ideal language to express Actors, Tasks, Resources, Goals and Softgoals.

From i* to UML

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:

  • actors: actors can be mapped to class aggregation,
  • tasks: tasks can be mapped to class operations. For example: a task between a dependent actor and a dependence in the SD model corresponds to a public operation in the dependence UML class,
  • resources: resources can be mapped as classes,
  • goals and soft goals: strategic goal and soft goals can be mapped to attributes,
  • task decomposition: the task decomposition can be represented by pre- and post-conditions.
gollark: There's no *known* reason you couldn't get them all the way to human performance. It might not be possible or it might be hilariously inefficient, but as far as I know the lines on the graphs remain straight.
gollark: Apparently this tends to improve with scale. I'm not sure if the details of Delphi are available anywhere.
gollark: Or, well, my rough model of that.
gollark: It's evidently not quite a magic 8 ball because it generally appears to agree with random humans' judgement.
gollark: I'd assume they took some kind of pretrained language model and finetuned it on crowdsourced scenario/response pairs.

See also

References
  • Yu, Eric S. (2009). "Social Modeling and i*" (PDF). In Borgida, Alexander T.; Chaudhri, Vinay K.; Giorgini, Paolo; et al. (eds.). Conceptual Modeling: Foundations and Applications. LNCS. 5600. Springer. pp. 99–121. doi:10.1007/978-3-642-02463-4_7. ISBN 978-3-642-02462-7. ISSN 0302-9743.
  • Yu, Eric; Giorgini, Paolo; Maiden, Neil; et al., eds. (2011). Social Modeling for Requirements Engineering. MIT Press. ISBN 978-0-262-24055-0.
  • Yu, E.S.K. (1997). "Towards modelling and reasoning support for early-phase requirements engineering". IEEE International Symposium on Requirements Engineering. RE'97. pp. 226–235. doi:10.1109/ISRE.1997.566873. ISBN 0-8186-7740-6.
  • Santander, V.F.A.; Castro, J.F.B. (2002). "Deriving use cases from organizational modeling". IEEE Joint International Conference on Requirements Engineering. RE'02. pp. 32–39. doi:10.1109/ICRE.2002.1048503. ISBN 0-7695-1465-0.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.