Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

PhD position
by Jannik Laval 11 Sep '19

11 Sep '19

[Apologies for Cross-Posting] Dear all, At DISP Lab, at Lyon, France, we have a PhD opening on « Ensuring Interoperability for "smart" information systems". More information are following. What is important is that all the development will be done using Pharo/Moose. If you are interested, please contact me by answering this mail. ===== Ph.D. thesis (CIFRE) Berger Levrault and DISP Lab, Lyon, France Title: Ensuring Interoperability for "smart" information systems Enterprise: Berger Levrault Research Laboratory: DISP Lab Where: Lyon, France Recruitment date: As soon as possible Application deadline: As soon as possible Function: 3 years PhD candidate position in Berger Levrault (CDI). The position will be part time between Berger Levrault and DISP Lab. Research topic : data interoperability, application exchange protocols, service-oriented architecture, event architecture, semantics, monitoring. Context: The need for sharing, exchanging and promoting information from information systems is constantly increasing and now represents a major concern in the various reforms of the local public sector (consolidation of local authorities, implementation of in place in 2016 Hospital Group Territory, Digital Republic). It is therefore essential to design "platforms" capable of providing answers to the rationalisation and simplification of data exchanges between software applications and with the outside world to promote and simplify the application of all these reforms. In addition, service-oriented architectures and event architectures (SOA, EDA) are mature and widely used. At Berger-Levrault, their implementation ensures the scalability and maintainability of solutions. These architectures are characterised by the flexibility and the loose coupling of the subsystems that compose them (ie services, applications, IS ...) and rely on several means (Hohpe & Woolf, 2004) to route the data within this network of systems communicating. At this stage of maturity, we observe that these data exchanges are operational and meet the requirements of interoperability between heterogeneous systems (Leal, 2019). Nevertheless, the number of standards recognised and used by the French public sector, the privileged sector of Berger-Levrault, increases the level of interconnection difficulties (Kurniawan & Ashari, 2015) of the different solutions developed by Berger-Levrault. This is all the more remarkable when it comes to communicating with external solutions or platforms (partners and / or competitors). This multiplicity of exchanges and types of exchanges generates a great deal of complexity and highlights the need to master the exchange system as effectively as possible. Berger Levraut today lacks visibility on existing exchanges and mechanisms to evaluate them (Leal, Guédria, & Panetto, 2019) which complicates the detection of dysfunctions and the discovery of their origins. Moreover, it is essential for the Berger-Levrault applications to be able to adapt to the new rules and standards while continuing to integrate the dematerialization of the public service. The evolution of these modalities has an almost systematic impact on the exchange of data put in place to ensure interoperability. Hence the need to build flexible and scalable exchange architectures and to follow the evolution of these exchanges. These transformations imply a large volume of data exchanged and subject to variations that can be strong during periods of "high attendance" such as elections by electronic vote. The very nature of exchanges can be affected especially with the multiplicity of connected objects (Buyya & Dastjerdi, 2016). These are increasingly used by public institutions for the benefit of the management of city facilities or user services. The increase in volumes of data exchanged therefore implies the implementation of exchange architectures that are able to support the load but also the great variability of the types and frequencies of data production. This requires distributed architectures (in infrastructure and flow), adaptable or even self-adaptable (Gascon-Samson et al 2015) to promote the system's resistance to faults while avoiding potential congestion phenomena. Based on this reflection, a research project was conducted in partnership by Berger-Levrault and the DISP laboratory (Amokrane et al., 2018). These early works have identified a set of scientific and technical barriers: • Lack of visibility on existing interoperability exchanges. Indeed, the current exchanges are not traced and the existing monitoring mechanisms focus mainly on low level information, such as the performance of the infrastructure or the use of the memory, without correlation with business information. In addition, few methods for evaluating interoperability are concerned with the effective evaluation (a posteriori of the implementation) of the interoperability of the data, and few of them are tooled (Leal, Guédria, & Panetto, 2019). • The complexity of trade maintenance. This is due to the lack of traceability of the exchanges, on the one hand, and that of the evolution of the exchange architecture configurations on the other hand. This complicates the identification of failures or dysfunctions and the analysis of their causes, and poses difficulties for the setting up of mechanisms of alerts or significant notifications. In addition, the lack of capitalisation of information relating to trade does not allow to consider a forecast maintenance. • The development of the different modules of the exchange system is manual and the remediation of malfunctions is done in an ad hoc manner. In addition to the cost of development and correction that this implies, this does not meet the responsiveness requirements of some business areas. Hence the need to build adaptable exchange systems using dynamic interoperability hubs (Agostinho, et al., 2016). The objective of this thesis proposal is to produce an approach to the implementation cycle of application exchanges, from design to maintenance, which will enhance the reliability and resilience of the interoperability exchange system. The solution will ultimately orchestrate all the application and service exchanges to ensure optimisation of the use of software and infrastructure resources of public institutions. To meet the needs in terms of interoperability, the work to be carried out is articulated in two axes that we structure as follows: - A flexible architecture for the implementation of interoperability. Here we consider the basic functionalities reflecting the activities necessary for the establishment of the means of interoperability. - A reflexive architecture for managing interoperability at a meta-level. This axis relates to setting up means of administration, monitoring and maintenance of the exchange network set up for interoperability. The work must also incorporate the concepts of security, scalability and usability. Requirements to be met when developing any solution to lift the locks and meet the objectives of this thesis work. ----- Agostinho, C., Ducq, Y., Zacharewicz, G., Sarraipa, J., Lampathaki, F., Poler, R., & Jardim-Goncalves, R. (2016). Towards a sustainable interoperability in networked enterprise information systems: Trends of knowledge and model-driven technology. Computers in Industry, 79, 64 - 76. doi:10.1016/j.compind.2015.07.001 Al-Dhuraibi, Y., Paraiso, F., Djarallah, N., & Merle, P. (2017). Elasticity in cloud computing: state of the art and research challenges. IEEE Transactions on Services Computing, (pp. 430-447). Amokrane, N., Laval, J., Lanco, P., Derras, M., & Moalla, N. (2018). Analysis of Data Exchanges, Contribution to Data Interoperability Assessment. 9th international Conference on Intelligent Systems 2018. Madeira, Portugal. Andary, J. F., & Sage, A. P. (2010). The role of service oriented architectures in systems engineering. Information Knowledge Systems Management, 9(1), 47-74. Belfadel, A., Laval, J., Cherifi, C., & Moalla, N. (2018). Towards service orchestration through software capability profile. I-ESA Interoperability for Enterprise Systems and Applications 2018. Berlin, Germany. Bernus, P., Goranson, T., Gøtze, J., Jensen-Waud, A., Kandjani, H., Molina, A., . . . Turner, P. (2016). Enterprise engineering and management at the crossroads. Computers in Industry, 79, 87 - 102. doi:10.1016/j.compind.2015.07.010 Buyya, R., & Dastjerdi, A. V. (2016). Internet of Things: Principles and paradigms. Elsevier. Cabot, J., Clarisó, R., Brambilla, M., & Gérard, S. (2017). Cognifying model-driven software engineering. Federation of International Conferences on Software Technologies: Applications and Foundations (pp. pp. 154-160). Springer. Chappell, D. (2004). Enterprise Service Bus. : O'Reilly Media, Inc. Cheung, A. K., & Jacobsen, H. A. (2010). Load balancing content-based publish/subscribe systems. ACM Transactions on Computer Systems (TOCS). Chhun, S., Moalla, N., & Ouzrout, Y. (2016). QoS ontology for service selection and reuse. Journal of Intelligent Manufacturing, 27(1), 187-199. Crosby, M., Pattanayak, P., Verma, S., & Kalyanaraman, V. (2016). Blockchain technology: Beyond bitcoin. Applied Innovation, 2(6-10). Curry, E. (2004). Message-oriented middleware, Middleware for communications,. Czarnecki, K., Eisenecker, U., Glück, R., Vandevoorde, D., & Veldhuizen, T. (2000). Generative programming and active libraries. Generic Programming (pp. pp. 25-39). Berlin, Heidelberg.: Springer. Erl, T. (2005). Service-oriented architecture: concepts, technology, and design. Prentice Hall Professional Technical Reference. Fahad, M., Moalla, N., & Bouras, A. (2012). Detection and resolution of semantic inconsistency and redundancy in an automatic ontology merging system. Journal of Intelligent Information Systems, 39(2), 535-557. Fahad, M., Moalla, N., Bouras, A., Abdul Qadir, M., & Farukh, M. (2011). Towards Classification of Web Ontologies for the Emerging Semantic Web. Journal of Universal Computer Science, 17(7), 1021-1042. Fülöp, L. J., Tóth, G., Rácz, R., Pánczél, J., Gergely, T., Beszédes, A., & Farkas, L. (2010). Survey on complex event processing and predictive analytics. the Fifth Balkan Conference in Informatics, (pp. pp. 26-31). Gascon-Samson, J., Garcia, F. P., Kemme, B., & Kienzle, J. (2015). Dynamoth: A scalable pub/sub middleware for latency-constrained applications in the cloud. In 2015 IEEE 35th International Conference on Distributed Computing Systems , (pp. pp. 486-496). Gokhale, A., Schmidt, D. C., Natarajan, B., & Wang, N. (2002). Applying model-integrated computing to component middleware and enterprise applications. Communications of the ACM, (pp. 65-70). Hachicha, M., Moalla, N., Fahad, M., & Ouzrout, Y. (2015). Performance assessment architecture for collaborative business processes in BPM-SOA based environments. International journal of Data & Knowledge Engineering, 105, 73-89. Hohpe, G., & Woolf, B. (2004). Enterprise integration patterns: Designing,building, and deploying messaging solutions. Addison-Wesley Professional. Khare, S., Sun, H., Zhang, K., Gascon-Samson, J., Gokhale, A., Koutsoukos, X., & Abdelaziz, H. (2018). Scalable edge computing for low latency data dissemination in topic-based publish/subscribe. In 2018 IEEE/ACM Symposium on Edge Computing (SEC) (pp. pp. 214-227). IEEE. Kurniawan, K., & Ashari, A. (2015). Service orchestration using enterprise service bus for real-time government executive dashboard system. 2015 International Conference on Data and Software Engineering (ICoDSE), (pp. 207-212). Yogyakarta. doi:10.1109/ICODSE.2015.7436999 Laval, J., Cherifi, C., & Cheutet, V. (2018). Towards the measurement of Enterprise Information Systems agility to support EIS improving projects. International Journal of Agile Systems and Management, 11(3):222–246. Leal, G. D. (2019). Support à la décision pour l'analyse de l'interopérabilité des systèmes dans un contexte d'entreprises en réseau. (Doctoral dissertation, Université de Lorraine). Leal, G., Guédria, W., & Panetto, H. (2019). Interoperability Assessment: A Systematic Literature Review. Computers in Industry (In Press). Luckham, D. C. (2011). Event processing for business: organizing the real-time enterprise. John Wiley & Sons. Mallek, S. (2012). Contribution au développement de l’interopérabilité en entreprise : vers une approche anticipative de détection de problèmes d’interopérabilité dans des processus collaboratifs. Object Management Group. (2006). Méta Object Facility (MOF) 2.0 Core Specification. Panettoa, H., Zdravkovicc, M., Jardim-Goncalvesd, R., Romeroe, D., Cecilg, J., & Mezgárh, I. (2016). New perspective for the future interoperable enterprise systems. Computers in Industry, s.l. : Elsevier, 79, 47-63. doi:10.1016/j.compind.2015.08.001 WSO2. (2015). The Evolution of Integration: A Comprehensive Platform for a Connected Business. White Paper. Récupéré sur http://wso2.com/ -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet IUT Lumière, Université Lumière Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

1 0

Moose wiki
by badetitou＠gmail.com 05 Sep '19

05 Sep '19

Hello moose developer! First of all, thanks for the little meeting at Esug19! One of the point during the meeting was: do we have documentation about the new features introduced in moose? The answer is: YES! It's still work in progress (as the work on Moose 8). I'm trying to create a moose-wiki (as https://github.com/pharo-open-documentation/pharo-wiki). You can find it here: https://moosetechnology.github.io/moose-wiki/ (w eb version) and here: https://github.com/moosetechnology/moose-wiki (github version). Most of the documentation come from themoosebook and https://github.com/SquareBracketAssociates/Booklet-FamixNG and part of the documentation are new. I'm also trying to collect all the famix parsers (to create mse files) we have and the meta-models. I think we can also create links to great moose-projects (not directly in a moose image but you can load it in moose (like FAST)). I also create linked to blog posts that describes the protocol to analyze projects with moose (as https://fuhrmanator.github.io/2019/07/29/AnalyzingJavaWithMoose.html) If you have one, please send me an email ;-) Benoît Verhaeghe @badetitou PHD student at: RMoD - Inria Lille - Nord Europe R&D developer at Berger-Levrault - France

3 2

Moose meeting @ESUG19?
by Anne Etien 28 Aug '19

28 Aug '19

Hi, I would like to organise a meeting around Moose at ESUG19, to explain you what we have done this year, where we are going and discuss with you what you are expecting and how you can contribute. If we are enough, we can do that either today (Wednesday) just after lunch at 13h or tomorrow Thursday after show us your project. Can you please say if you want to attend and which date you are available? Thanks in advance. Anne

5 4

PetitJSON
by Jannik Laval 19 Aug '19

19 Aug '19

Hi moosers, When loading Moose 7, PetitJson is not included. Is it voluntary ? Cheers, -- ~~Jannik Laval~~ Enseignant-chercheur Responsable Pédagogique Licence Coordonnateur de Projet IUT Lumière, Université Lumière Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

3 4

Using Moose 8.0 with C/C++ (and other languages)
by Galen Tackett 06 Aug '19

06 Aug '19

I’ve yet to try anything significant with Moose, either this new version or the prior. Though I did run some C through Verveine C/C++ over a year ago, I don’t remember doing anything with Moose itself. Does Moose 8.0 change the way that you use it for programs in C (and other languages that needed something that the earlier Moose didn’t do by itself)? Sent from my iPad > On Aug 5, 2019, at 5:25 AM, Benoît Verhaeghe <badetitou(a)gmail.com> wrote: > > Hi, > > It is added on instance side of MooseAbstractGroup, as #allWithSubTypesOf: and, #allWithType: > > Cheers, > Benoit > > >> Le lun. 5 août 2019 à 11:06, Tudor Girba <tudor(a)tudorgirba.com> a écrit : >> Hi, >> >> Interesting. Is this added on the instance side or MooseModel? >> >> Cheers, >> Tudor >> >> >> > On Aug 5, 2019, at 11:00 AM, Benoît Verhaeghe <badetitou(a)gmail.com> wrote: >> > >> > Hi all, >> > >> > We have added the method "allUsing:". >> > It takes a Trait as a parameter and will return all the entities in your model that use the trait. >> > >> > Example: >> > mooseModel allUsing: FamixTClass >> > will return all the FamixJavaClass and FamixJavaInnerClass (if FamixJavaInnerClass --|> FamixJavaClass) >> > >> > It will be the main method if you want to query your model with abstract entities. >> > >> > Benoît >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)list.inf.unibe.ch >> > https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> -- >> feenk.com >> >> "We can create beautiful models in a vacuum. >> But, to get them effective we have to deal with the inconvenience of reality." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

1 0

add allUsing:
by Benoît Verhaeghe 05 Aug '19

05 Aug '19

Hi all, We have added the method "allUsing:". It takes a Trait as a parameter and will return all the entities in your model that use the trait. Example: mooseModel allUsing: FamixTClass will return all the FamixJavaClass and FamixJavaInnerClass (if FamixJavaInnerClass --|> FamixJavaClass) It will be the main method if you want to query your model with abstract entities. Benoît

2 2

Convert browser into html file
by feliks 28 Jul '19

28 Jul '19

Hello I want to execute statement RTHTML5Exporter new export: aRoassalView How?? to download exporter or?? exporter for???? Glamorou browser. I read moose book and want use it for logistic application. Feliks

1 0

Are you using FAMIXGroup?
by Anne Etien 23 Jul '19

23 Jul '19

Hi, We are currently cleaning the traits in FamixNG. Once again, the idea is to remove FamixCompatibility metamodel and to keep only FamixStEntities or FamixJavaEntities (and so on). Obviously, it has incidence on tests. Do you use FamixTypeGroup, FamixClassGroup… and more generally groups in Famix? Thank in advance for your answer. Anne

5 5

[ANN] Moose v7.0.0 release
by Cyril Ferlicot 17 Jul '19

17 Jul '19

Hello everyone! I'm glad to announce the release of Moose v7.0.0. I'll explain the main changes since Moose 6.1 and what are the future plans for Moose 8 in this mail. * What changed? In this version of Moose a lot of things changed from the meta model management point of view. In Moose 6.1 we only had one big metamodel build with inheritance to analyze all languages. This had a lot of limits and a lot of work has been done to improve Moose on those weak points. In Moose 7, you can now have multiple meta-models independant from each others. This mean that we will now have one meta model by parser. We can also create simple meta-models for test purpose. Also those MM are build by composing stateful traits instead of using inheritance. On top of that we now also have the possibility to use generators to manage meta-models. Instead of writing every classes by hand, we can describe a meta-model in a generator and use it to generate the MM. Then we can use it to regenerate it also. Pavel, who did most of the work, wrote some documentation you can find here: https://pavel-krivanek.github.io/famix/ There is still a lot of work to do to make it better but this will come with Moose 8. The reason we release now is that in Moose 7 we started to have split MM for Java, Pharo, and other languages, but we still have a compatibility meta-model. The work needed to improve Moose further will require to break the compatibility MM. Thus we are releasing a stable version now with a compatibility MM and we will work on a Moose 8 version where the compatibility MM will be removed. * Workflow for bugfixes Another change with Moose 6.1 is that now Moose is managed via Github. This will allow use to do patches or minor releases in case the community find bugs or need some new simple features in Moose 7 as long as it only contains backward compatible changes. * Plan for the next release We already stated to work on Moose 8. We plan to work on multiple aspects: - Improve the usability of the generator, especialy while regenerating MMs - Update the Traits contained in Moose to build our MM. Currently, they are a reproduction of what was in Moose 6.1 in order to get the compatibility model. The goal is to remove all the hacks and get cleaner traits. - Start to build new tools to use the full power of this new version of Moose - Fix bugs that will be discovered after such a big change * How to get Moose 7 You can get Moose 7 in two ways. First is to install it in a Pharo 7 image: ``` Metacello new baseline: 'Moose'; repository: 'github://moosetechnology/Moose:v7.x.x/src'; load. ``` The second is to get it via the Pharo Launcher. It now has a Moose 7 entry to get this version and a Moose 8 entry to get the development version. We will also need to update Moose technology website. * Credits Thank to Pavel Krivanek who did most of the work. Thank also to: - Benoit Verhaeghe - Julien Delplanque - George Ganea - Christopher Fuhrman - Stephane Ducasse - Anne Etien - Nicolas Anquetil - Cyril Ferlicot And any other I might have forgot who participated in the development of Moose 7 :) -- Cyril Ferlicot https://ferlicot.fr

4 3

Changes to Metamodel generator
by Cyril Ferlicot 12 Jul '19

12 Jul '19

Hi, Last month we did some changes to the MM generator of the development version of Moose and it might impact people using it. I'll explain the changes and what to do in this mail. Context: In the development version of Moose, we have two ways of building a metamodel. The first is to do as in Moose 6.1 and write it by hand. The second and recommended way is to describe it in a MetaModel generator and to generate it. This generator is also able to regenerate a metamodel. In order to do that, it needs to know the Traits and Slots it generated. This was done by generating two methods on each entity: #generatedSlotNames and #generatedTraitNames. Changes: With Julien Delplanque, we updated Moose to remove the need of those two methods. For Traits, we are now able to just ask an entity for its Traits that are part of the metamodel. Thus, we do not need the #generatedTraitNames method. For Slots, we have two kinds. One that describe a relation between entities and another that store properties. The relations already had a slot specific to Famix. We introduced another one call FMProperty to be used to store the properties. With that change, all slots generated by the generator are specific to Famix, thus we can lust ask a class for its famix slots and we do not need to generate a static method with the slot names in entities. Actions to take after this change: We added some compatibility code to keep things working during a transition period. Two actions are needed if you want a clean MM after those changes: - The first one is to remove the #generatedTraitNames methods from the class side of generated entities. - The second one is to regenerate your metamodel and this will automatically replace InstanceVariableSlot by FMProperty and remove #generatedSlotNames methods. Change in generator behavior: This change as a side effect you need to know. Before, regeneration of MM was updating only the Traits and Slots it generated. Now it will regenerate all Traits that are part of the metamodel (with a #MSEClass:super pragma) and all Famix slots. Thus, if you are managing a MM via a generator, you need to update the generator description to add a Trait or Slot from Famix instead of adding it by hand. Else, it will be removed during the next generation. -- Cyril Ferlicot https://ferlicot.fr

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev