BibSonomy publications for /tag/i-starTue Jul 21 20:48:45 CEST 2009Using i* Models for Evaluation2006evaluation i-star model Tue Jun 30 17:48:42 CEST 2009Val Paraiso, ChileIbero-American Workshop of Engineering of RequirementsJulyComparing GORE Frameworks: i-star and KAOS 2009i-star kaos requirements Goal-Oriented Requirements Engineering (GORE) is an approach to requirements engineering dealing with intentionality in accordance with the relations among different actors. KAOS and i* (i-star) frameworks have been receiving many references as being important GORE proposals. This paper presents an conceptual analysis comparing characteristics of those methods giving examples related to actors’ relations definition, goal organizational model, tasks representation, risk analysis, and non-functional requirements. The aim of this work is to show both frameworks benefits and drawbacks. We believe that this analysis helps the understanding of the core concepts of GORE as well as it draws attention to key representation issues for both KAOS and i*.Wed May 21 10:06:29 CEST 2008Boston/Dordrecht/LondonNon-Functional Requirements in Software Engineering20002000 RE book engineering i-star requirement to-read Tue May 13 09:35:42 CEST 2008Requirements Engineering Conference, 2007. RE '07. 15th IEEE International53-56Tracing and Validating Goal Aspects20072007 RE engineering goals i-star requirement Aspects promote a clear separation of concerns so that tangled and scattered concerns are modularized throughout software development. We propose a framework to trace aspects identified during goal-oriented requirements analysis to code and testing. Two types of checks are performed to validate the resulting system in light of stakeholders’ crosscutting concerns. One ensures that systems with and without aspects have the same functionality defined by the hard goals. The other checks whether the weaved system with aspects indeed improves system qualities in terms of the degree of softgoal satisfaction. We demonstrate the approach using an open-source e-commerce platform.Wed Oct 31 22:26:57 CET 2007Los AngelesConference on Systems Engineering ResearchAprilIntegrating requirements engineering and cognitive work analysis: A case study2006complexity i-star openome personal systems Fri Mar 02 22:56:50 CET 2007Annapolis, MarylandInternational Symposium on Requirements Engineering226--235Towards modelling and reasoning support for early-phase requirements engineering1997i-star model requirements software 1406 Requirements are usually understood as stating what a system is supposed to do, as apposed to how it should do it. However, understanding the organizational context and rationales (the “Whys”) that lead up to systems requirements can be just as important for the ongoing success of the system. Requirements modelling techniques can be used to help deal with the knowledge and reasoning needed in this earlier phase of requirements engineering. However most existing requirements techniques are intended more for the later phase of requirements engineering, which focuses on completeness, consistency, and automated verification of requirements. In contrast, the early phase aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives. This paper argues, therefore, that a different kind of modelling and reasoning support is needed for the early phase. An outline of the i* framework is given as an example of a step in this direction. Meeting scheduling is used as a domain exampleMon Sep 18 06:26:07 CEST 2006Using Meta-model Driven Views to Address Scalability in i*2004i-star modeling openome requirements visualization This thesis proposes an extension to the i* framework to address scalability issues. The notion of “viewâ€� is exploited to selectively present portions of an i* “baseline modelâ€�, which contains all modeled objects for a given application using i* notations. We first reformulate the i* framework and define four types of views—Actor Class, Strategic Dependency, Strategic Rationale, and Evaluation Results. Next, we define sub view types based on the four types of views and supply a view management framework. The views and sub-views are defined using meta-models, and formalized using the Telos conceptual modeling language. Each view type is associated with a formally defined “selection ruleâ€� so that the projection of a specific view from a baseline model can be automated. Relationships among views are depicted in View Maps. Illustrative examples are taken from the London Ambulance Service and the Trusted Computing Group case studies.Mon Sep 18 06:26:07 CEST 2006Porto, PortugalWorkshop em Engenharia de Requisitos (WER)June148--160A Survey of Good Practices and Misuses for Modelling with i* Framework2005goal modeling survey i-star requirements The i* framework has been increasingly used by the requirements engineering community. However, good practices are not always followed. Many papers have presented the use of i* constructs in such ways that results are not coherent with their original specifications. Some cases attempt to adapt the framework to specific needs by misusing its elements. In other situations, misuses are due to wrong interpretations of i* syntax and semantic. Unfortunately, many of these misuses may lead to wrong interpretations of the models by other people using i*. This work carried out a survey on several published papers to collect both good practices and misuses of the framework. It aims to help requirements engineers to use the i* framework in its full capacity.Mon Sep 18 06:26:07 CEST 2006San Francisco, CA, USAInternational Conference on Software Engineering and Knowledge EngineeringJulyA Comparative Analysis of i* Agent-Oriented Modelling Techniques2006modeling i-star empirical Mon Sep 18 06:26:07 CEST 2006Software, IEEE326--33e-Service Design Using i* and e3value Modeling232006evolution i-star complexity e-Services are intangible products, provisioned via the Internet. Examples include Internet access and Internet radio. Because most e-services involve multiple enterprises, creating a shared understanding of the service under development is an issue. Such an e-service is more difficult to understand than a proposition just consisting of goods because services lack easily observable physical properties. Consequently, software engineers must first understand the e-service itself before they can build effective systems and support for these services. The authors present the complementary use of two requirements engineering techniques. Using i* modeling, they explore strategic goals that enterprises have, and using e3value modeling, they understand how these goals can result in profitable services for enterprises. They demonstrate their approach using a case study on Internet radio.This article is part of a special issue on requirements engineering.Sun Sep 17 06:41:48 CEST 2006Software, IEEE326--33e-Service Design Using i* and e3value Modeling232006evolution i-star complexity e-Services are intangible products, provisioned via the Internet. Examples include Internet access and Internet radio. Because most e-services involve multiple enterprises, creating a shared understanding of the service under development is an issue. Such an e-service is more difficult to understand than a proposition just consisting of goods because services lack easily observable physical properties. Consequently, software engineers must first understand the e-service itself before they can build effective systems and support for these services. The authors present the complementary use of two requirements engineering techniques. Using i* modeling, they explore strategic goals that enterprises have, and using e3value modeling, they understand how these goals can result in profitable services for enterprises. They demonstrate their approach using a case study on Internet radio.This article is part of a special issue on requirements engineering.Sat Sep 09 19:26:51 CEST 2006Washington, DC, USARE '01: Proceedings of the Fifth IEEE International Symposium on Requirements Engineering (RE '01)Requirements Engineering for Complex Collaborative Systems2001engineering i-star hci requirements complexity Fri Mar 24 16:34:33 CET 2006Seattle, WAEighth International Workshop on Agent Theories, Architectures, and Languages (ATAL-2001)AugustA Goal-Based Organizational Perspective on Multi-Agent Architectures2001goal i-star cognition 1406 Fri Mar 24 16:34:33 CET 2006Portland, USAProceedings of Second International Workshop From Software Requirements to Architectures (STRAW'03)MayIntegrating Organizational Requirements and Socio-Intentional Architectural Styles2003goal i-star requirements 1406 organization Fri Mar 24 16:34:33 CET 2006Proceedings 7th Intl. Workshop on Principles of Software EvolutionSoftware Evolution, 2004. Proceedings. 7th International Workshop on Principles of159--164Co-evolution of complementary formal and informal requirements2004formal i-star requirements Agent-oriented Conceptual Modelling (AoCM, as exemplified by the i* notation by E. Yu (1995)), represents an interesting approach to modelling early phase requirements that is particularly effective in capturing organizational contexts, stake-holder intentions and rationale. There are significant benefits in using formal methods for the development of computer systems and improving their quality. We propose a methodology which permits the use of these two otherwise disparate approaches in a complementary and synergistic fashion for requirements engineering.Fri Mar 24 16:34:33 CET 2006TorontoInternational Conference on Advanced Information Systems EngineeringLecture Notes in Computer ScienceMay328--343SNet: A modeling and simulation environment for agent networks based on i* and ConGolog32482002agent modeling i-star requirements simulation SNet is a prototype environment supporting the representation and dynamic evaluation of designs for social networks comprising human, hardware, and software agents. The environment employs metadata management technology to integrate an extended version of the i* formalism for static network modeling with the ConGolog logicbased activity simulator. The paper de nes the formal mappings necessary to achieve the integration and describes an operational prototype demonstration. SNet's...i-starCommunity for tag(s) i-star