2016-09-15 Architecture Committee Minutes

Attendees

• Reibert Arbring (Ericsson)
• Keith Brown (OneFact)
• Simon Delisle (Ericsson)
• Per Jonsson (Saab)
• Philip Langer (EclipseSource)
• Florian Noyrit (CEA)
• Simon Redding (Zeligsoft)

Topics

Status update presented to the steering committee

The work of the architecture committee has been summarized in the steering committee meeting as follows.

Main focus on creation of domain-specific products based on Papyrus

• Review and discussion of DSML creation artifacts (palette configuration, properties)
  • Ease and experience for tool smith persons
  • Reusability and recursive customization
• Review and discussion of UI simplifications
• Presentation of element types framework by Florian N. (current and future state)
• Presentation of diagrammatix framework by Florian N. (very early state --> future plans)

Proposal of a task force regarding DSML creation frameworks

• Task force should consist only of a few people who adopt/evaluate those frameworks
• Use cases: Papyrus-RT, Papyrus-IM, NWA
• Feedback is reported to the Architecture Committee

Other topics being discussed and worked on

• Organization of architecture of the projects, repository, etc (including TLP)
• Migration, API changes, and diagram stability from Neon to Oxygen
• Quality assurance

Topics being discussed in the architecture committee meeting

Presentation by Per about product line management

• PMC to define the base line capabilities
  • Is the UI for defining a profile always there?
  • Is the UI for editing base UML always there?
• Group of product owners have to define "atomic functionality"
• This has an impact on the overall architecture
• Feature model to define those functionalities and how they can be combined

Discussion on P-IM as a continuous showcase

• Changing things in UML (e.g. non-directed relationships)
• Use it to explore the new frameworks (lab bench)
• For extensions, maybe use Papyrus-RT

Investigate workflow support in Papyrus

• Relevant frameworks are architectures framework, viewpoints, etc.
• not direct priority, but to be investigated next year to see if it is useful for existing products

Tasks for 2016/2017

Combining Textual and Graphical Modeling (Lead: Simon)

• Interested parties: Saab/Combitech, Ericsson, OneFact (Validating use cases, reqs, ...)
• Active particpants: Frederico, Simon, Philip, possibly more to add
• Publish preliminary schedule at the next steering committee meeting

DSML Task force (Lead: Philip)

• Result: planned to be delivered for 2017
  • Best practices for architecture, guidelines, documentation, etc.
  • Evaluation regarding dcurrently edisitng use cases (parapyrs-rt)
  • Incremental customization
  • Documentation: Papyrus-IM as a starting point
• Ongoing effort with regular meetings and updates to be provided
  • Preparation of a more detailed list of results and time plan
• Use Cases:
  • Patrik: Ericsson specific DSML
  • Christian Papyrus-RT
  • Philip Papyrus-RT/Papyrus-IM wrt EMF Compare integration
  • Given the resources, Florian will always support

Product line support (Lead: Florian)

• Two perspecitives
  • Splitting of repo (Florian at CEA), moving into TLP
  • Incremental customizations --> DSML Task Force
• Task: Feature model for Papyrus as a starting point (Philip to Per to AC to PMC)

Dependency management when building products (Lead: Per)

• Goal to minimize mandatory dependencies that bring in UI contributions (e.g. PDE UI, JDT UI, ...)
• Investigation of dependencies brought into PIM quite: end of H2 2016 results will be reported

DSML "SDK"

To be defined after DSML Task Force showed results that are inputs for this task.

• Cookbook in the short term (DSML Task Force)
• Packaging
• Good citizen (Composability
• Tooling is long term

Organizational decisions

• Monthly meetings, offset of PMC
• Deadlines for each task, defined by task leader
• At latest until next Steering
• Next meeting of AC -> One week before next steering