Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EGF"
| (32 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [ | + | [[Image:Logo EGF.png|right]] |
= Introduction = | = Introduction = | ||
| − | The | + | [http://eclipse.org/egf EGF project page] |
| + | |||
| + | The EGF project is [http://www.eclipse.org/projects/project.php?id=modeling.emf part of EMF]. | ||
In order to improve the software development industrialization, a major step consists in mass-producing software. This mass-production must be customizable, and must be able to support complex, large-scale and heterogeneous generations. Given the today’s available Eclipse tools, the issue here is not to provide either a new transformation engine (model-to-model, model-to-text, text-to-model, text-to-text) or DSL (Domain-Specific Language) editor but to realize their integration for flexible software mass-production. This is the purpose of EGF. | In order to improve the software development industrialization, a major step consists in mass-producing software. This mass-production must be customizable, and must be able to support complex, large-scale and heterogeneous generations. Given the today’s available Eclipse tools, the issue here is not to provide either a new transformation engine (model-to-model, model-to-text, text-to-model, text-to-text) or DSL (Domain-Specific Language) editor but to realize their integration for flexible software mass-production. This is the purpose of EGF. | ||
| Line 11: | Line 13: | ||
A factory component encapsulates generation know-how. A portfolio is a consistent set of factory components with a common generation objective, valuable for a development team or a user community. The purpose is to create off-the-shelf factory components. For instance, a technical infrastructure factory provides all the needed mechanisms for an application development (e.g., transaction management, persistence policy). | A factory component encapsulates generation know-how. A portfolio is a consistent set of factory components with a common generation objective, valuable for a development team or a user community. The purpose is to create off-the-shelf factory components. For instance, a technical infrastructure factory provides all the needed mechanisms for an application development (e.g., transaction management, persistence policy). | ||
| − | {| | + | <br> |
| + | |||
| + | {| cellspacing="10" border="0" class="FCK__ShowTableBorders" | ||
|- | |- | ||
| − | | valign="top" | ''' | + | | valign="top" | '''Documentware'''<br> |
| − | [[EGF | + | [[EGF New And Noteworthy|New And Noteworthy]]<br>[[EGF Documents|Documents]]<br>[[EGF Presentations|Presentations]]<br> [http://www.eclipse.org/proposals/egf/ Proposal]<br>[[#Contact|Contact]]<br> |
| − | [ | + | | <br> |
| + | | <br> | ||
| + | | <br> | ||
| + | | valign="top" | '''Software'''<br> | ||
| + | [[EGF Installation|Download and Installation]]<br>[[EGF Tutorial and Use Cases|'''Tutorial and use cases''']]<br>[[EGF/Portfolio|'''EGF Portfolio''']]<br>[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMF.EGF Report a bug]<br>[http://www.eclipse.org/forums/eclipse.egf EMF/EGF newsgroup]<br> | ||
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| − | | <br> | + | | <br> |
| − | | valign="top" | ''' | + | | valign="top" | '''Follow up'''<br> |
| − | [[EGF | + | [[EGF/Releases|Planned and last releases]]<br>[[EGF/Review|EGF Reviews]]<br>[[#Team|Team]]<br>[[EGF Partners|Partners]]<br> |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | [[EGF | + | |
|} | |} | ||
| − | = | + | = Team = |
| − | The | + | The EGF committers are: |
*[mailto:benoit.langlois@thalesgroup.com Benoit Langlois] ([http://www.thalesgroup.com/ Thales/TCS/EPM]), project lead | *[mailto:benoit.langlois@thalesgroup.com Benoit Langlois] ([http://www.thalesgroup.com/ Thales/TCS/EPM]), project lead | ||
| Line 40: | Line 42: | ||
*[mailto:thomas.guiu@soyatec.com Thomas Guiu] ([http://www.soyatec.com Soyatec]) | *[mailto:thomas.guiu@soyatec.com Thomas Guiu] ([http://www.soyatec.com Soyatec]) | ||
*[mailto:laurent.goubet@obeo.fr Laurent Goubet] ([http://www.obeo.fr Obeo]) | *[mailto:laurent.goubet@obeo.fr Laurent Goubet] ([http://www.obeo.fr Obeo]) | ||
| + | |||
| + | <br> Other main EGF contributors are: | ||
| + | |||
| + | *[mailto:m.helleboid@soyatec.com Matthieu Helleboid] ([http://www.soyatec.com Soyatec]) | ||
| + | |||
| + | <br> | ||
= Contact = | = Contact = | ||
| − | Any issue should be reported to the [https://bugs.eclipse.org/bugs/enter_bug.cgi?product= | + | Any issue should be reported to the [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMF.EGF Bugzilla] You may also contact the team using the [http://www.eclipse.org/forums/eclipse.egf EMF/EGF newsgroup]. |
| − | [[Category:Modeling]] [[Category: | + | [[Category:Modeling]] [[Category:EMF]] |
Revision as of 08:57, 19 July 2012
Introduction
The EGF project is part of EMF.
In order to improve the software development industrialization, a major step consists in mass-producing software. This mass-production must be customizable, and must be able to support complex, large-scale and heterogeneous generations. Given the today’s available Eclipse tools, the issue here is not to provide either a new transformation engine (model-to-model, model-to-text, text-to-model, text-to-text) or DSL (Domain-Specific Language) editor but to realize their integration for flexible software mass-production. This is the purpose of EGF.
EGF federates generation around the pivotal element of factory component. A factory component is a unit of generation with a clear objective of generation. It has a contract to declare the factory component parameters. Contrary to a classic generation which aggregates all the generation parameters, generation data are organized by viewpoints, such as generation pattern, license description or deployment declaration. Altogether, viewpoints explicitly configure all the generation parameters. The generation orchestration is defined by a production plan. A generation step of the production plan can either be a Java task or, by assembly, an invocation to another factory component. Regarding the lifecycle, a factory component can be edited and executed.
A factory component encapsulates generation know-how. A portfolio is a consistent set of factory components with a common generation objective, valuable for a development team or a user community. The purpose is to create off-the-shelf factory components. For instance, a technical infrastructure factory provides all the needed mechanisms for an application development (e.g., transaction management, persistence policy).
| Documentware |
|
|
|
Software Download and Installation |
|
|
|
Follow up |
Team
The EGF committers are:
- Benoit Langlois (Thales/TCS/EPM), project lead
- Xavier Maysonnave (Soyatec)
- Thomas Guiu (Soyatec)
- Laurent Goubet (Obeo)
Other main EGF contributors are:
Contact
Any issue should be reported to the Bugzilla You may also contact the team using the EMF/EGF newsgroup.