Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/CodeGenerationAndDeployment"

(Created page with "This page is there to discuss the naming of the plugins related to code generation, analysis and deployment. Currently, the following structure is proposed Papyrus designer...")
 
Line 14: Line 14:
 
** C++
 
** C++
 
*** Profile and model libraries
 
*** Profile and model libraries
 +
** C
 +
** Java library
 +
** ...
  
 
* Analysis & Architecture exploration (oep.designer.analysis)
 
* Analysis & Architecture exploration (oep.designer.analysis)
 +
** Schedulability analysis
  
 
* Component based designer (oep.designer.components)
 
* Component based designer (oep.designer.components)
** existing plugins of qompass designer with new prefix
+
** existing plugins of qompass designer with new prefix, i.e.
 +
** FCM profile (maybe UCM - Unified component model) in the future
 +
** M2M transformation core
 +
** model libraries with container services and interaction components

Revision as of 06:59, 19 January 2016

This page is there to discuss the naming of the plugins related to code generation, analysis and deployment.

Currently, the following structure is proposed

Papyrus designer (oep.designer)

  • Code generators (oep.designer.codegen)
    • C++ code generator
      • Includes profile and model libraries? or in Programming language below?
    • C code generator
    • Java code generator
    • ...
  • Programming languages (oep.designer.proglang)
    • C++
      • Profile and model libraries
    • C
    • Java library
    • ...
  • Analysis & Architecture exploration (oep.designer.analysis)
    • Schedulability analysis
  • Component based designer (oep.designer.components)
    • existing plugins of qompass designer with new prefix, i.e.
    • FCM profile (maybe UCM - Unified component model) in the future
    • M2M transformation core
    • model libraries with container services and interaction components

Back to the top