Show simple item record

dc.contributor.authorCares, Carlos
dc.contributor.authorFranch Gutiérrez, Javier
dc.contributor.authorMayol Sarroca, Enric
dc.contributor.authorQuer, Carme
dc.contributor.otherUniversitat Politècnica de Catalunya. Departament d'Enginyeria de Serveis i Sistemes d'Informació
dc.date.accessioned2013-02-22T10:23:17Z
dc.date.created2011-01-17
dc.date.issued2011-01-17
dc.identifier.citationCares, C. [et al.]. A reference model for i*. A: "Social modeling for requirements engineering". The MIT Press. Massachusetts Institute of Technology, 2011, p. 573-606.
dc.identifier.isbn978-0-262-24055-0
dc.identifier.urihttp://hdl.handle.net/2117/17924
dc.description.abstractAgent-oriented models are frequently used in disciplines such as agent-oriented requirements engineering, requirements engineering and organizational process modelling. i* is currently one of the most widespread notations used for this purpose. Due to both its dissemination and its highly strategic nature, instead of a single definition, several groups have formulated different variants, which define in a slightly different way the basic concepts of the language, as well as propose particular constructs that fit into the particular interests of these groups. In this chapter we first review these proposals and then we present a reference model that establishes the concepts and relationships that are fundamental in i*. The reference model is expressed as a UML class diagram (with OCL constraints) together with a vocabulary of the presented terms. Most of the included concepts are common to the seminal i* proposal, the GRL and the diverse variations used in the context of the Tropos methodology. For those concepts that are not shared by these analysed variants, the reference model tries to reconcile the different views whenever possible. The reference model allows determining the differences of any existing i* variant with respect to the model, and also to know how much different a new variant would be from the core of i*. The variants can be expressed by applying some refactoring operations on the UML class diagram. We illustrate this situation by applying refactoring to some of the analysed proposals.
dc.format.extent34 p.
dc.language.isoeng
dc.publisherThe MIT Press. Massachusetts Institute of Technology
dc.subjectÀrees temàtiques de la UPC::Informàtica::Enginyeria del software
dc.subject.lcshRequirements engineering
dc.subject.lcshObject-oriented methods (Computer science)
dc.titleA reference model for i*
dc.typePart of book or chapter of book
dc.subject.lemacMètodes orientats a l'objecte (Informàtica)
dc.subject.lemacProgramari -- Desenvolupament
dc.contributor.groupUniversitat Politècnica de Catalunya. inSSIDE - integrated Software, Service, Information and Data Engineering
dc.rights.accessRestricted access - publisher's policy
local.identifier.drac9572036
dc.description.versionPostprint (published version)
dc.date.lift10000-01-01
local.citation.authorCares, C.; Franch, J.; Mayol, E.; Quer, C.
local.citation.publicationNameSocial modeling for requirements engineering
local.citation.startingPage573
local.citation.endingPage606


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record

All rights reserved. This work is protected by the corresponding intellectual and industrial property rights. Without prejudice to any existing legal exemptions, reproduction, distribution, public communication or transformation of this work are prohibited without permission of the copyright holder