Towards requirements-driven information systems engineering: the Tropos project

Abstract

Information systems of the future will have to perform well within ever-changing organizational environments. Unfortunately, existing software development methodologies (object-oriented, structured or otherwise) have traditionally been inspired by programming concepts, not organizational ones, leading to a semantic gap between the software system and its operational environment. To reduce this gap, we propose a software development methodology named Tropos which is founded on concepts used to model early requirements. Our proposal adopts the i n organizational modeling framework, which offers the notions of actor, goal and (actor) dependency, and uses these as a foundation to model early and late requirements, architectural and detailed design. The paper outlines Tropos phases through an e-business example, and sketches a formal language which underlies the methodology and is intended to support formal analysis. The methodology seems to complement well proposals for agent-oriented programming platforms. r

Modeling Mental States in Agent-Oriented Requirements Engineering

“…One of the main features of this approach is that goals (and knowledge) are assigned to particular agents thus becoming their subjective attributes as opposed to being objective system properties as in many other approaches (e.g., Tropos [1] and KAOS [3]). This allows for the modeling of conflicting goals, agent negotiation, information exchange, complex agent interaction protocols, etc.…”

“…Suppose that we are employing an approach like Tropos [1], a requirements-driven agent-oriented software development methodology that uses the i* modeling notation, to model a simple goal delegation involving two agents. Fig.…”

The First Contest on Multi-agent Systems Based on Computational Logic

“…The first part is a description of analysis, design and implementation of a MAS for the above application. Existing MASs methodologies such as Gaia [16], Prometheus [15] and Tropos [10] can be used (not demanded) to describe the analysis and design of the system. For the description of the implementation, it should be explained how the design is implemented.…”

Quality-Based Software Reuse

“…We call these aspects, goal aspects, since they simplify the V-graph by removing the correlation links and putting functional and non-functional issues into separate AND/OR decomposition hierarchies. We have used it in the Media Shop case study [26]. The advantage of having a systematic process for discovering goal aspects is that finding them early on, makes it easier to trace quality concerns to aspect-oriented implementations.…”