Jump to: navigation, search

Difference between revisions of "EGF"

(39 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Image:Logo EGF.png|right]]
 +
 
= Introduction  =
 
= Introduction  =
  
The EMFT EGF project is [http://www.eclipse.org/emft/projects/ part of EMFT] (EMF Technology).  
+
[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 9: 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).  
  
{| class="FCK__ShowTableBorders" border="0" cellspacing="10"
+
<br>
 +
 
 +
{| cellspacing="10" border="0" class="FCK__ShowTableBorders"
 
|-
 
|-
| valign="top" | '''Resources'''<br>
+
| valign="top" | '''Documentware'''<br>  
[[EGF FCs|Factory Components]]<br>[[EGF Tutorial and Use Cases|Tutorial and use cases]]<br>
+
[[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>  
  
[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" | '''Development'''<br>
+
| valign="top" | '''Follow up'''<br>  
[[#Roadmap|Roadmap]]<br>[[#Team|Team]]<br>[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMFT Report a bug]<br>
+
[[EGF/Releases|Planned and last releases]]<br>[[EGF/Review|EGF Reviews]]<br>[[#Team|Team]]<br>[[EGF Partners|Partners]]<br>  
 
+
| <br>
+
| <br>
+
| <br>
+
| valign="top" | '''Installation'''<br>
+
[[EGF Installation|Installation of EGF]]<br>
+
  
 
|}
 
|}
  
<br>
+
= Team  =
  
= Roadmap  =
+
The EGF committers are:
  
<br>
+
*[mailto:benoit.langlois@thalesgroup.com Benoit Langlois] ([http://www.thalesgroup.com/ Thales/TGS/SSE]), project lead
 +
*[mailto:thomas.guiu@soyatec.com Thomas Guiu] ([http://www.soyatec.com Soyatec])
 +
*[mailto:boubekeur.zendagui@obeo.fr Boubekeur Zendagui] ([http://www.obeo.fr Obeo])
 +
*[mailto:laurent.goubet@obeo.fr Laurent Goubet] ([http://www.obeo.fr Obeo])
  
''Planned:<br>''
+
<br> Other main EGF contributors are:
  
'''EGF 0.2.3''' - Eclipse 3.5 - March, 2010<br>
+
*[mailto:matthieu.helleboid@thalesgroup.com Matthieu Helleboid] ([http://www.thalesgroup.com/ Thales/TGS/SSE])
  
*Common features: release engineering, JUnit tests
+
<br>  
*Portfolio: EMF patternization for EMF customization (initial version)
+
 
+
&nbsp;
+
 
+
''Last releases:<br>'''EGF 0.2.2''' - Eclipse 3.5 - February 19th, 2010''
+
 
+
*EGF structure: generation workflow - In/Out/Output parameter management
+
*Pattern: Introduction of pattern injection and model-driven pattern strategy
+
*Portfolio: EMF wrapper
+
 
+
<br>'''''EGF 0.2.1''' - Eclipse 3.5 - January 11th, 2010<br>''
+
 
+
*EGF structure: improvement of the generation workflow
+
*Pattern: Introduction of a method template editor and pattern strategy; improvement of pattern call
+
 
+
<br>'''EGF 0.2.0''' - Eclipse 3.5 - December 16th, 2009
+
 
+
*Common features: Storage: in fcore files, dynamic execution of factory component and task, UI improvement
+
*EGF structure: Extensibility of EGF in order to support contributions (e.g. new viewpoints)
+
*Pattern: Introduction of pattern inheritance, pattern call; infrastructure able to support new engines
+
 
+
<br>'''EGF 0.1.0''' - Eclipse 3.5 - July 17th, 2009<br>
+
 
+
*Edition and execution of factory component
+
*Generation Pattern edition and execution with Jet-1<br>
+
 
+
<br>
+
 
+
= Team  =
+
 
+
The component developers are&nbsp;:
+
 
+
*[mailto:benoit.langlois@thalesgroup.com Benoit Langlois] ([http://www.thalesgroup.com/ Thales/TCS/EPM]), project lead
+
*[mailto:xavier.maysonnave@soyatec.com Xavier Maysonnave] ([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])
+
  
 
= Contact  =
 
= Contact  =
  
Any issue should be reported to the [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMFT Bugzilla] You may also contact the team using the EMFT newsgroup.  
+
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:EMFT]]
+
[[Category:Modeling]] [[Category:EMF]]

Revision as of 05:09, 17 May 2013

Logo EGF.png

Introduction

EGF project page

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

New And Noteworthy
Documents
Presentations
Proposal
Contact




Software

Download and Installation
Tutorial and use cases
EGF Portfolio
Report a bug
EMF/EGF newsgroup




Follow up

Planned and last releases
EGF Reviews
Team
Partners

Team

The EGF committers are:


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.