Building an Agent Methodology from Fragments: the MEnSA experience Mariachiara Puviani & Massimo Cossentino Giacomo Cabri & Ambra Molesini Dipartimento di Ingegneria dell’Informazione, Universit` a di Modena e Reggio Emilia, ICAR, Consiglio Nazionale delle Ricerche – Palermo, Alma Mater Studiorum —Universit` a di Bologna AOMIP@SAC 2010, Sierre, Switzerland, 25th March 2010 Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 1 / 21 MEnSA
The MEnSA Process Requirements 1 The New MEnSA Process 2 Results Assessment 3 Conclusions and Future Works 4 Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 2 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features ◮ MEnSA aim was not to create a new-brand methodology. . . Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features ◮ MEnSA aim was not to create a new-brand methodology. . . ◮ . . . but to reuse “fragments” of existing methodologies (PASSI, Tropos, Gaia and SODA) by composing them through the Situational Method Engineering approach Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features ◮ MEnSA aim was not to create a new-brand methodology. . . ◮ . . . but to reuse “fragments” of existing methodologies (PASSI, Tropos, Gaia and SODA) by composing them through the Situational Method Engineering approach In order to do this we Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features ◮ MEnSA aim was not to create a new-brand methodology. . . ◮ . . . but to reuse “fragments” of existing methodologies (PASSI, Tropos, Gaia and SODA) by composing them through the Situational Method Engineering approach In order to do this we ◮ define the methodology’s requirements Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features ◮ MEnSA aim was not to create a new-brand methodology. . . ◮ . . . but to reuse “fragments” of existing methodologies (PASSI, Tropos, Gaia and SODA) by composing them through the Situational Method Engineering approach In order to do this we ◮ define the methodology’s requirements ◮ select the more suitable fragments Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
The objective of this paper Our work is aimed at building a new methodology in order to fill the existing gap between agent-oriented methodologies and MAS infrastructures This was the objective of the MEnSA (Methodologies for the Engineering of complex software Systems: Agent-based approach) project, where we studied how to build a new methodology that takes into consideration the infrastructures’ features ◮ MEnSA aim was not to create a new-brand methodology. . . ◮ . . . but to reuse “fragments” of existing methodologies (PASSI, Tropos, Gaia and SODA) by composing them through the Situational Method Engineering approach In order to do this we ◮ define the methodology’s requirements ◮ select the more suitable fragments ◮ assemble fragments for creating a new methodology Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 3 / 21 MEnSA
Situational method engineering Each methodology can be decomposed into reusable method fragments A designer can re-use and re-assemble fragments in order to create a new methodology [Cossentino et al., 2007] First step: extraction and storing of method fragments in the method base Second step: selection of the suitable fragments from the method base Third step: fragments assembly Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 4 / 21 MEnSA
Outline The MEnSA Process Requirements 1 The New MEnSA Process 2 Results Assessment 3 Conclusions and Future Works 4 Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 5 / 21 MEnSA
Initial requirements 1 To fill the gap between design and implementation: ◮ a support for traceability ◮ the abstractions adopted in the design phase should be ⋆ powerful enough for properly design the system ⋆ “near” to the abstractions supported by MAS infrastructures Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 6 / 21 MEnSA
Initial requirements 1 To fill the gap between design and implementation: ◮ a support for traceability ◮ the abstractions adopted in the design phase should be ⋆ powerful enough for properly design the system ⋆ “near” to the abstractions supported by MAS infrastructures 2 To adopt a complete requirements analysis phase Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 6 / 21 MEnSA
Initial requirements 1 To fill the gap between design and implementation: ◮ a support for traceability ◮ the abstractions adopted in the design phase should be ⋆ powerful enough for properly design the system ⋆ “near” to the abstractions supported by MAS infrastructures 2 To adopt a complete requirements analysis phase 3 To adopt proper levels of abstraction in order to deal with complex problems Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 6 / 21 MEnSA
Initial requirements 1 To fill the gap between design and implementation: ◮ a support for traceability ◮ the abstractions adopted in the design phase should be ⋆ powerful enough for properly design the system ⋆ “near” to the abstractions supported by MAS infrastructures 2 To adopt a complete requirements analysis phase 3 To adopt proper levels of abstraction in order to deal with complex problems 4 To enable an easy transition towards the new methodology to designers fluent with one or more of the “source” methodologies Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 6 / 21 MEnSA
Extended requirements 5 Domains list (req. 1 and 3): problem, agency and solution domains Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 7 / 21 MEnSA
Extended requirements 5 Domains list (req. 1 and 3): problem, agency and solution domains 6 The layering principle (req. 3) coming from SODA will help in dealing with complexity Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 7 / 21 MEnSA
Extended requirements 5 Domains list (req. 1 and 3): problem, agency and solution domains 6 The layering principle (req. 3) coming from SODA will help in dealing with complexity 7 Tropos experiences: goal-oriented analysis should be performed before functional-oriented analysis Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 7 / 21 MEnSA
Extended requirements 5 Domains list (req. 1 and 3): problem, agency and solution domains 6 The layering principle (req. 3) coming from SODA will help in dealing with complexity 7 Tropos experiences: goal-oriented analysis should be performed before functional-oriented analysis 8 Interactions should include semantic communications Molesini (Univ. Bologna) AOMIP 2010, 25/03/2010 7 / 21 MEnSA
Recommend
More recommend
