1. Multi-agent Systems Product Lines Camila Nunes, Elder Cirilo, Ingrid Nunes {cnunes,ecirilo,ioliveira}@inf.puc-rio.br

2. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Outline Introduction Background Related Work Case Studies –EC –OLIS MAS-PL Research Work in LES –Domain Engineering Process –Empirical Studies –SPL For Self-Adaptive Systems

3. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Introduction Agent-oriented Software Engineering (AOSE) –New software engineering paradigm –Development of distributed complex applications Software Reuse –Benefits Lower costs Reduced time-to-market Quality improvement –AOSE methodologies Failed to adequately capture the reuse potential since many of the developed methodologies center on the development of specific software applications

4. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Introduction Software product lines (MAS) –New trend of software reuse –Build family of applications in a systematic method Only recent research has explored the integration between SPL and Multi-agent Systems (MAS) –Multi-agent Systems Product Lines (MAS-PL) –SPL + MAS benefits –Help on the industrial exploitation of agent technology

5. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Background Reuse: From Ad-Hoc to Systematic Focus was small-grained and opportunistic. Results always fell short of expectations.

6. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Background A software product line is a set of software-intensive systems sharing a common, managed set of features that satisfy the specific need of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. Software product line engineering is a paradigm to develop software applications (software-intensive systems and software products) using platforms and mass customization. A software platform is a set of software subsystems and interfaces that form a common structure from which a set of derivative products can be efficiently developed and produced.

7. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Background Market Strategy / Application Domain pertain to Architecture share an Components are built from is satisfied by used to structure Products Product Lines: Take economic advantage of commonality Bound variability

8. © LES/PUC-Rio Background set of related products to product Core Asset (Components) Scope Definition Production Plans Architecture

9. 7/6/20149 Elder © LES/PUC-Rio Background

10. © LES/PUC-Rio Background

11. Feature Model –Describe a SPL in terms of common and variable features Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio

12. Background SPL Implementation –Framework OO Abstract Classes, Intefaces –Components Intefaces –Aspect Oriented Development Code composition –Pre-processing Coditional Compilation Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio

13. SPL Adoption Strategies Proactive –Development of product lines considering all the products in the foreseeable horizon –A complete set of artifacts to address the product line is developed from scratch Extractive –SPL is developed starting from existing software systems –Common and variable features are extracted from these systems to derive an initial version of the SPL Reactive –Incremental development of SPLs –SPL artifacts address only a few products. When there is a demand to incorporate new requirements or products, the common and variable artifacts are incrementally extended in reaction to them

14. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio SPL Development Approaches SPL Product 1 Product 2 Product 3 Proactive Approach Domain Analysis Architecture Project

15. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio SPL Development Approaches Product 1 Product 2 Product 3 SPL Product 1 Product 2 Product 3 Extractive Approach

16. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio SPL Development Approaches SPL Product 1 Product 2 Product 3 Reactive Approach SPL Product 1 Product 2 Product 3 Product 4 Requirements for a new product instance, Product 4 + React Iterate

17. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio SPL and MAS-PL Approaches MethodologyDomain AnalysisDomain Design FORM Feature diagram with composition rules Subsystem, Process Model and Module Models [Pohl 2005] Framework Reusable, textual and model-based requirements, variability model Reference architecture, refined variability model, mapping from design artifacts to requirements artifacts PLUS Requirements model consisting of a use case model and feature model Static and dynamic models, feature/class dependencies, design of component-based software architecture MacMAS Extension Feature Model (features are goals) Acquaintance Organization, Traceability and Role Models [Dehlinger 2007] Role Schema, Role Variation Point - For the complete study, refers to http://www.inf.puc-rio.br/~ioliveira/maspl/http://www.inf.puc-rio.br/~ioliveira/maspl/

18. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio MAS-PL Variability Types Variability Types –What can vary in a MAS-PL Besides the common variabilities of SPLs –Alternative / Optional Agents Alternative / Optional Roles Alternative / Optional Capabilities Agent also accomplish their goals by communicating with other agents; thus, it is common that inserting new capabilities affects other agents Believes Goals Plans

19. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Related Work Josh Dehlinger and Robyn R. Lutz –A Product-Line Requirements Approach to Safe Reuse in Multi- Agent Systems Extensible agent-oriented requirements specification template for distributed systems that supports safe reuse –Software Product Line Approach –Dynamically changing configurations of agents can be captured and reused for future similar systems Consistency with the Gaia methodology Requirements area documented in two phases –Role Schema –Role Variation Point Schema

20. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Related Work Joaquin Pena et al –Designing and managing evolving systems using a MAS product line approach Evolving system: multiple versions of the same system –Extension of MaCMAS

21. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Case Studies

22. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio ExpertCommittee (EC) Conference Management System Typical web-based application Functionalities to support the complete process of the management of conferences and workshops –Paper submission –Reviewing processes Examples –EasyChair (http://www.easychair.org/)http://www.easychair.org/ –JEMS (https://submissoes.sbc.org.br/)https://submissoes.sbc.org.br/

23. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio EC Feature Model

24. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio EC Architecture Chair Actions BaseAction Database Author ServiceImpl ConferenceDAO Hibernate PaperDAO Hibernate Author Actions Deadline Agent GUI Layer Chair ServiceImpl Data Layer Business Layer Chair Role Coordinator Role Author Role Committee Member Role Observable Observer User Data Agent > Observable Service User Agents Environment Agent Task Agent TaskAction Task ServiceImp l TaskDAO Hibernate Notifier Agent SMSMAIL … Reviewer Actions Reviewer ServiceImpl Reviewer Role

25. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio EC Configuration File

26. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio OLIS OLIS (OnLine Intelligent Services) –Software product line of web-based systems –Services (mandatory or optional) User Management Calendar Events Announcement Weather –Handles different event types Generic Academic Travel –Addition of Autonomous behavior to Provide Intelligent Services

27. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio OLIS Feature Model Feature Dependencies

28. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio OLIS Architecture

29. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio OLIS Configuration struts.xml applicationContext.xml

30. MAS-PL Research Work in LES Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio

31. Domain Engineering Process for MAS-PLs Definition of a domain engineering process for developing MAS-PLs –Detailing its activities and their respective artifacts Notations to model and document agent variability Models to capture agent features traceability Modeling agent features independently –Incorporation of agents into existing systems designed with other technologies with a low impact Design and implementation guidelines to help on the development of MAS-PL

32. Domain Engineering Process for MAS-PLs Key characteristics –Feature-oriented –Systematic –Incorporation of notations and activities of existing SPL and MAS approaches Process Structure –Structured according to SPEM –Three main levels Phases Activities Tasks

33. Domain Engineering Process for MAS-PLs Future work includes –Dealing with Fine-grained Features –Use of Aspect-oriented Analysis and Design Approaches –Experimental Studies to Evaluate our Process –Framework for Integrating Web-applications and Software Agents –Tool Support

34. Empirical Study Evolving MAS-PL: An Empirical Study –Motivation Increase several approaches of SPL –MAS growing in size and complexity Evolution Scenarios of MAS Combining OO and OA –Problem Definition MAS concerns may not no very well separated by existing OO abstractions Evolution requirements of product line Construction of reusable and maintainable large MAS

35. Empirical Study Problem –There are recent research and empirical studies exploring the use of AOP to modularize features –However, none of them analyzes the impact of adding agency features in evolution scenarios of a MAS-PL. –How to deal with the MAS-PL evolution? Implementation of variability mechanisms: –Conditional Compilation –Configuration Files –Aspect-Oriented Programming (AOP)

36. Empirical Study We compared two different versions of the Expert Committee MAS-PL implemented using the following technologies: –(i) JADE with conditional compilation using the Java language –(ii) JADE and AOP using the AspectJ language. OLIS MAS-PL –(i) JADE platform and Spring configuration files; –(ii) Jadex platform and Spring configuration files; –(iii) JADE and AOP with the AspectJ language

37. SPL Approach to Support Self-Adaptation in MAS Autonomic computing –Ability to manage themselves and dynamically adapt to changes in the environment Challenge –How to provides non intrusive and expected evolutions in an automatic and autonomic way? Proposed Solution –Variability management approach based on SPL –Feature model + multi-level models = Autonomic Feature Reconfiguration Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio

38. Feature Model Represent variability from the SPL architecture –Feature model models dependencies between variable features by means of constraints –Specify valid and invalid feature combinations. Feature Model reasoning techniques allow us –the number of products available; –filter some configuration give a context constraint –Valid and the optimum configuration give a context constraint Modeling as Mata-Level Features Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio

39. Multi-Level Models Classes, Aspectos... JADE Model Files Feature Model

40. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Product Derivation in ASPL Adaptation Points –Data Adaptation –Intra-Agent Adaptation –Resource Adaptation –Agent-level Adaptation Feature Derivation - constructing a feature from the set of assets specified or implemented for a SPL

41. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Feature Derivation - Manual Runtime Environment 1 :: Developer select a new Feature 5 :: Delivery feature interface Feature 3 :: Derivate 4 :: Deployment 6 :: Bind Feature Model (FMP) Feature Model (FMP) GenArch ML Models +

42. Camila Nunes, Elder Cirilo e Ingrid Nunes © LES/PUC-Rio Feature Derivation – Autonomic Runtime Environment 1 :: Obtain Feature Metadata Feature 4 :: Derivate 5 :: Deployment 7 :: Bind 2 :: Request a New Feature Feature Model (FMP) Feature Model (FMP) GenArch ML Models +

43. References NUNES, I. O.; NUNES, C.; KULESZA, U.; LUCENA, C. Developing and Evolving a Multi-Agent System Product Line: An Exploratory Study. In: 9th International Workshop on Agent-Oriented Software Engineering (AOSE08), 2008, Estoril. p. 177-188. NUNES, I. O.; KULESZA, U.; NUNES, C.; LUCENA, C. Documenting and Modeling Multi-agent Systems Product Lines. In: International Conference on Software Engineering and Knowledge Engineering (SEKE08), 2008, San Francisco. p. 745-751. NUNES, C.; KULESZA, U..; SANT'ANNA, C.; NUNES, I.; LUCENA, C. On the Modularity Assessment of Aspect-Oriented Multi-Agent Systems Product Lines: a Quantitative Study. In Simpósio Brasileiro de Componentes, Arquiteturas e Reutilização de Software (SBCARS 2008), 2008. p. 122-135

44. References NUNES, I. O.; KULESZA, U.; NUNES, C.; CIRILO E.; LUCENA, C. Extending Web-Based Applications to Incorporate Autonomous Behavior. In: WebMedia, 2008, Vila Velha. NUNES, I. O.; KULESZA, U.; NUNES, C.; CIRILO E.; LUCENA, C. Extending PASSI to Model Multiagent Systems Product Lines. Poster, Symposium on Applied Computing (SAC09), 2008, Honolulu. CIRILO E.; NUNES, I. O.; KULESZA, U.; NUNES, C.; LUCENA, C. Automatic Product Derivation of Multi-agent Systems Product Lines. Poster, Symposium on Applied Computing (SAC09), 2008, Honolulu.

45. References NUNES, I. O.; NUNES, C.; KULESZA, U.; LUCENA, C. Developing and Evolving a Multi-Agent System Product Line: An Exploratory Study. In: Agent-Oriented Software Engineering IX: 9th International Workshop, AOSE 2008. Lecture Notes in Computer Science, Springer-Verlag, 2009. To appear. NUNES, C.; KULESZA, U.; SANT'ANNA, C.; NUNES, I.; GARCIA, A.; LUCENA, C. Comparing stability of implementation techniques for multi-agent system product lines (to appear). In: 13 th European Conference on Software Maintenance and Reengineering (CSMR 2009), Kaiserslautern, Germany, 2009 NUNES, I. O.; KULESZA, U.; NUNES, C.; CIRILO E.; LUCENA, C. A domain analysis approach for multi-agent systems product lines In 11th International Conference on Enterprise Information Systems (ICEIS 2009), Milan, Italy, 2009. To appear.

46. References NUNES, I. O.; KULESZA, U.; NUNES, C.; LUCENA, C. A Domain Engineering Process for Developing Multi-agent Systems Product Lines. In: 8th Autonomous Agents and Multiagent Systems (AAMAS09), 2009, Budapest. To appear. NUNES, I. O.; LUCENA, C.; KULESZA, U.; NUNES, C. On the Development of Multi-Agent System Product Lines: A Domain Engineering Process. In: 10th International Workshop on Agent- Oriented Software Engineering (AOSE09), 2009, Budapest. To Appear.

47. Questions? Camila Nunes cnunes@inf.puc-rio.br Elder Cirilo ecirilo@inf.puc-rio.br Ingrid Nunes ioliveira@inf.puc-rio.br