John Mylopoulos (University of Toronto): Agent-oriented Software Engineering
Julio Cesar Leite (PUC-Rio): A goal/scenario approach to software customization
Software Engineering: Resumo
We are developing a methodology, called Tropos, for building agent-oriented software systems. The methodology covers five software development phases: early requirements analysis, late requirements analysis, architectural design, detailed design, and implementation. Throughout, the concepts offered by i* [Yu95] are used to model both the stakeholders in the systemís environment, and the system itself. These concepts include actors, who can be (social) agents (organizational, human or software), positions or roles, also social dependencies for defining the obligations of actors to other actors (called dependees and dependers respectively.) Dependencies may involve a goal, to be fulfilled by the dependee on behalf of the depender, a task to be carried out by the dependee, or a resource to be delivered.
The presentation sketches on-going research on the Tropos methodology, a formal language we have designed founded on i*, formal analysis techniques under development, as well as design pattern ideas we are exploring inspired by organizational theory. This is joint work with colleagues at the Universities of Toronto (Canada), Trento (Italy), Louvain (Belgium) and the Federal University of Pernambuco.
[Yu95] 17. Eric Yu, Modelling Strategic Relationships for Process Re-Engineering, Department of Computer Science, University of Toronto, 1995.
goal/scenario approach to software customization: Resumo
New applications related to proactive ubiquitous computing will start to be demanded in the future. Take for instance, smart homes, a complex network of computers sensors and activators that will be embedded in homes. It is natural to thing that these kinds of systems will have to be customized according to the people that will be living there. One kind of such customization is aimed at cognitive impairment people. These customizations require very fine grain variability, not just of interfaces but of functional aspects as well.
We are starting to apply goal models with different perspectives to try to map variability early on the requirements definition process. We will show a first sketch of the integration of the goal, skills and preferences model with a scenario model. This integration allows for fine grain variability. Perceived advantages of the strategy are related to its modeling organization, but it's inherently complexity is a key question.