170 likes | 296 Views
Towards filling the gap between AOSE methodologies and infrastructures : requirements and meta-model. Fabiano Dalpiaz ¹, Ambra Molesini², Mariachiara Puviani³, Valeria Seidita⁴ ¹ Università degli Studi di Trento ² Alma Mater Studiorum ³ Università degli Studi di Modena e Reggio Emilia
E N D
Towards filling the gap between AOSE methodologies and infrastructures: requirementsand meta-model Fabiano Dalpiaz¹, Ambra Molesini², Mariachiara Puviani³, Valeria Seidita⁴ ¹ Università degli Studi di Trento ² Alma Mater Studiorum ³ Università degli Studi di Modena e Reggio Emilia ⁴ Università degli Studi di Palermo WOA08 - Palermo
Outline • Introduction to MEnSA • Our approach • Assembling a Metamodel • Requirements • Selection of fragments • Conceptual map • Metamodel • Conclusions and future work F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
The MEnSA project: why? • The development of complex systems requires a new software engineering paradigm • Agent-oriented methodologies • Paradigmatic shift (from OO) at conceptual and technical level • No need to reinvent the wheel • There are many agent-oriented methodologies • Each methodology has different specificities and application areas F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
The MEnSA project: what? • MEnSA • “Methodology for the Engineering of complex Software systems: Agent based approach” • Filling the gap • analysis and design, and implementation • methodologies and infrastructures • Metamodel-based approach • Integration of existing fragments • 3+1 partners • Alma Mater Studiorum (Cesena), Università degli Studi di Modena e Reggio Emilia, Università degli Studi di Trento, ICAR-CNR Palermo e Università degli Studi di Palermo. F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
Our Approach • Definition of a set of requirements for the methodology • Generic requirements • Specific requirements derived from the selected methodologies • Elicitation and analysis of a set of fragments that satisfy the requirements • starting from Tropos, GAIA, SODA and PASSI F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
Our Approach • Definition of a semantic conceptual map • To find out synonyms and inter-level relations between concepts from different abstraction levels • Assembly of an integrated metamodel on the base of the selected fragments F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
General Requirements • Transformational approach: from high-level abstraction to low-level concrete entities • Support for traceability • Support for functional and non-functional requirements • Support for goal-oriented and functional-oriented analysis • Precise and compact modeling constructs for the concept of agency • Agent, Agent’s rationale, Situated agent, Social Agent F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
Specific Requirements (1) • Transformational process • Requirement agent → Design agent → Implementation agent • Layering (supported by SODA) • Zooming and Projection mechanisms • Goal oriented analysis (Tropos) before functional-oriented analysis (Passi) • Interaction • Semantic communication + Ontology + compliance with FIPA ACL F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita 8
Specific Requirements (2) • Organizational Rules (Supported by GAIA) • Environment and topology modeling • SODA artifact and workspace • Modeling of non-functional requirements • Tropos soft-goals • Modeling of Agent Plan • Should not constrain to a specific kind of agent F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita 9
Assembling a meta-model • Composition patterns: • Elements from existing meta-models present the same name but have different meanings • Elements have the same meaning but different names • Elements present totally disjoint names and definitions, requiring just a simple composition • Additional concepts and relations act as glue • Outcome: Conceptual map + Glossary of term F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
The Conceptual Map Horizontal relations link synonym concepts Vertical relations define inter-level links (realization) F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita 11
MEnSA metamodel F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
MEnSA metamodel: requirements F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
MEnSA metamodel: design F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
Conclusion • A processtodefineanintegratedagent-orientedmeta-model • Identification of the requirementsfor the target methodology • Selection of a list of fragmentsfrom the fourconsideredmethodologies. • Construction of a glossary • Definition of a conceptualmap of methodologiesabstractions • Initialversion of the meta-model F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita
Future Work • Definition of the meta-model’s implementationphase, extractedfrom a set of MAS infrastructures • Refine the metamodel • as a result of the work on the methodologicalaspects and the validationphaseover a case study • splitting the twophasesintodifferent and more detailedsub-phases F. Dalpiaz, A. Molesini, M. Puviani, V. Seidita 16
Thanks for your attention dalpiaz@disi.unitn.it ambra.molesini@unibo.it mariachiara.puviani@unimore.it seidita@dinfo.unipa.it