Skip to main content
Jump to: navigation, search

Papyrus IC 2017 Plan

Revision as of 22:08, 8 February 2017 by Francis.bordeleau@ericsson.com (Talk) (Steering Committee)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page contains the current version of the Papyrus IC 2017 Plan has approved by the Papyrus IC Steering Committee during its meeting of January 19th, 2017. The final approval of the plan is still pending on the approval of the overall Polarsys 2017 plan (before the end of February).

Steering Committee

  • Goal: Improve reporting with the publication of quarterly and annual reports to track/communicate progress to both members and the community in general
    • Person Responsible: Chairman -- Francis Bordeleau
    • Plan
      • Reports must be made available before the end of the month that follows the end of a quarter
      • Quarterly report is to be presented during the Papyrus IC Quaterly General Meeting
    • Success factors
      • Publication of the reports on time
    • Milestones
      • Monthly report before the end of the month that follows the end of a quarter
      • Annual report before the end of December
    • Comments
      • To be organize on the Papyrus IC wiki
    • Budget: None
  • Goal: Improve Papyrus IC governance by establishing the required "traceability" between Papyrus IC actions, budget spending, and objectives/goals (from the annual plan)
    • Person Responsible: Stefan Landemoo (Saab)
    • Plan
      • Introduce a Budget with posts for Income part and Cost part enabling traceability
      • Income part with post from each IC workgroup and member
      • Cost prognosis with posts including affected objective, devided in budget areas and IC Workgroups
      • Collect spent costs and report each quarter with adjustments and forecast
      • Collect and report from Half year Contributions Review and Plan
      • Contribution Report of passed half year with posts including affected objective
      • Contribution Plan for next half year with posts including affected objective
    • Success Factors
      • Outcome/result to be provided from Eclipse Controller each Quarter
      • Introduce templates for a common way to manage the data
      • Introduce objective reference number traceability when defining the goals/objectives and use it as a connection between budget, plan and outcome. E.g Contrib type, Contribution , planned/Actual person days, Planned/Actual value/USD, Objective ref.
      • Data must be able to collect, merge and present
    • Budget:Admin time to collect, sort and present report, TBD
  • Goal: Improve the overall management of the Papyrus IC and Papyrus products
    • Person Responsible: Francis Bordeleau, Jordi Cabot
    • Overall objective
      • Contribute to ensure the long-term sustainability of Papyrus
    • Comment
      • Both the Product Management Committee and Architecture Committee will be directly involved in all activities related to this goal
    • Plan
      • Define details of the plan during Q1
      • Propose and evaluate strategies to facilitate the onboarding (and retention) of new contributors (again, not only at the code level, it could be to improve the documentation or any other action valuable for the Papyrus community at large).
      • Discuss and make explicit a governance model for Papyrus (not only describing the rules to become committer but rules regarding all kinds of community interactions)
      • Define and implement automatic analysis techniques to extract useful information about the Papyrus community based on the mining of user interactions on the repository, on Bugzilla or on the forums
      • Provide analysis tools implementing the above points to help the Steering Committee to evaluate (and take action on) the community behind Papyrus.
      • We propose to establish a research project (potentially apply for European funding) to look at different governance aspects
    • Success factors
      • Define the success factors during Q1
    • Budget:TBD
  • Goal: Increase the number of Papyrus IC members
    • Person Responsible: Francis Bordeleau as Chairman
    • Organizations involved: All members must contribute to the recruitment of new members
    • Plan
      • Prepare "one-slide" to describe benefits of joining the Papyrus IC for each member category
        • Note: Slides to be provided by Product Management Committee
      • Work with EMO to define overall Polarsys recruitment strategy
      • Identify new potential members
      • Organize in-person meetings with business and technical leaders from qualified organisations
      • Work with EMO to provide membership information for Polarsys/Papyrus IC
      • Welcome new member
    • Success factors
      • 6 new end-user members
        • At least 2 in US
        • At least 2 in automotive/mechatronics
        • Others?
      • 4 new supplier members
        • At least 1 in US
      • 10 new research/academia members
        • At least 3 in NA
        • At least 2 in Sweden
        • At least 1 in Belgium?
        • At least 2 in Germany?
        • UK?
        • France?
        • Austria?
        • At least 2 in System Engineering
    • Milestones
      • Progress to be reviewwed on a quaterly basis
      • H1
        • at least 1 new end-user members during each quarter
        • 2 new supplier members during H1
      • 5 Research/Academia members per half-year
    • Budget: 25,000 USD for promotion trips

Product Management

Global Product Management Committee Goals

  • Goal: Improve governance for product management, architecture management, and projects
    • Person Responsible: Product Management Committee
    • Key points to be addressed by each product
      • Define and maintain
        • Technical roadmap — With input from Architecture Committee
        • Product line roadmap — Including roadmaps from individual products
        • Development priorities
      • Governance of product/project management
        • Product Management Committee is responsible of publishing policies
        • Guidelines for goals, priorities, features
        • Guidelines for product lifecycle
          • Releases
          • Roadmap
        • Guidelines for bug lifecycle
          • Consider
            • Bugs entered by Papyrus IC members
            • Bugs entered by non-members
          • Bug triage
          • Manage bug list as bugs are aging
          • On top of Eclipse lifecycle
          • On a per-project basis
        • Combine the use of Tuleap for product/project management and Bugzilla
        • Development progress
    • Budget: None
  • Goal: Establish Papyrus as a top level Eclipse Project
    • Person Responsible: Sebastien Gerard (CEA)
    • Notes
      • We want this new structure to be in place as soon as possible, but we need to align with the requirements of the Eclipse Foundation
    • Status
      • A plan for overall project restructuring to enable the new Papyrus project structure is being developed in the Architecture Committee
    • Plan
      • Sebastien to contact the Eclipse Foundation to start the process
      • Write the charter for the Papyrus project
      • Define the project proposal
        • Includes definition the set and hierarchy of Papyrus projects that will be included
        • People involved: Architecture Committee and Product Management Committee
      • Present the proposed new top-level Papyrus project to Eclipse
        • Questions
          • Does it need to be approved by the Modeling project (under which Papyrus is currently sitting)?
          • Who needs to approved the new project? EMO or somebody else?
      • Move/create the sub projects
    • Milestones
      • Confirmation of acceptance by Eclipse Foundation: Jan 31st, 2017?
      • Targeted completion: TBD
    • Note:
      • We should put it in place asap so that new projects can be created, e.g. Papyrus-ArchiMate
    • Budget: None
  • Goal: Improve support and response-time on Papyrus Forums
    • Person Responsible: Each Product Lead is responsible for the Forum associated with their product
    • Notes
      • Each of the different products have their own forum
      • We need to consider this in the context of the different "tools" use to communicate/interact with the community, e.g. wiki and other marketing channels
    • Plan
      • At least one person monitoring (subscribed to) each Papyrus forum
    • Success factors
      • No question unanswered in more than a week
    • Milestones
      • NA
    • Budget: None
  • Goal: Create and manage product roadmap, based on the list of members' requirements and priorities
    • Person Responsible
      • Each Product Lead is responsible for their product's roadmap
      • PMC lead responsible for product line roadmap
    • Plan
      • Establish Tuleap as underlying technology for product/project management
        • Require feedback from Enalean
        • Define and implement Tuleap project structure/hierarchy (Charles R)
        • Create a Tuleap project instance for each of the Papyrus products (??)
        • Get each project to populate their Tuleap project and start using it
      • Establish governance for requirements and their priorities
      • Communicate the use of Tuleap to the Papyrus IC community
    • Milestones
      • Targeted completion: H1, 2017
    • Budget: TBD -- needs to be synchronized with Polarsys

Product Goals

Global Product Requirements/Goals

  • Products MUST be composable
    • Note: Technical aspects to be handled by the Architecture Committee
  • Improve DSL Support to properly support development of DSL's on top of DSL's
    • Note: Technical aspects to be handled by the Architecture Committee
  • Provide proper support for evaluation of the different versions of Papyrus
    • Products must be simple to evaluate from the perspective of a competent, knowledgeable user in the domain/language or in related tools.
  • Improve documentation
    • End user
    • Toolsmith
  • Note: Should consider the possibility to integrate with Eclipse Foundation CI infrastructure

Papyrus Platform

  • Product Lead: Sebastien Gerard (CEA)
  • Organizations involved: Airbus Defence & Space, CEA, EclipseSource, Ericsson, Zeligsoft
  • Scope
    • Support for all of the different UML diagrams
    • Support for customization and DSL -- Toolsmith
  • Status
    • Current version is Papyrus 2.0.2 -- Released in November 2016
    • Planning to release Papyrus 3.0 in June 2017 as part of Eclipse Oxygen
  • 2017 Goals
    • Improve overall stability and usability
      • Improve Papyrus Diagram Editor
      • UML standard diagram editors
      • Introduce automatic diagram layout
        • Note: This is required both for the scalability of sequence diagrams and to support textual/graphical modeling
      • Improve Papyrus Property Editor (PPE)
      • Improve Papyrus Tree-based Editor (PTE)
      • Papyrus User Interactions
      • Miscelleanous
        • Papyrus shall support internationalization of models
        • Papyrus shall continue to improve its performance
        • Papyrus shall support migration from v2.x to v3.x
    • Improve support for customization and DSL
      • Synchronize with the work done by the Architecture Committee on improving support for customization and DSL
    • Improve support for Toolsmiths
      • Provide a set of tools and techniques that can be applied to customize Papyrus or develop DSL on top of Papyrus (including the recursive nature of DSL's)
      • Improved Features
        • Papyrus shall improve its support of viewpoint as defined in ISO42010.
        • Papyrus shall make consistent its various specific editors for toolsmiths.
      • New Features
        • Papyrus shall provide a declarative mean to define and extend the Papyrus diagram editors.
    • Provide platform support for the Papyrus product line offerings
      • Plan is the re responsibility of the Architecture Committee
    • Increase the number of Contributors/Committers
      • Comment
        • We need to focus on adding Contributors/Committers from different organizations and different countries to increase the pool of available development resources, increase development agility, and increase the "bus factor"
        • Plan needs to be defined
      • Questions
        • Where do we want to recruit the new contributors/committers
        • How do we support them in the process of moving towards becoming committers
        • Should we organize events like developer workshops to get people started?
        • Notes:
          • The decomposition of Papyrus into smaller projects (in the context of promoting Papyrus as a top level project) will lower the barrier to entry
          • Increasing the number of committers can't be done at the expense of lowering the competence level
  • Milestones
    • Papyrus 2.0
      • Release of Papyrus 2.0.3 in March 2017
    • Papyrus 3.0
      • Release of Papyrus 3.0 in June 2017 as part of Eclipse Oxygen
      • Release of Papyrus 3.1 in Sept 2017
      • Release of Papyrus 3.2 in Dec 2017

Papyrus for Real Time (RT)

  • Product Lead: Charles Rivet (Zeligsoft)
  • Organizations involved: Zeligsoft, CEA, EclipseSource, Ericsson
  • Scope
    • Support for UML-RT
  • Status
    • Papyrus-RT 0.8 was release on November 2nd, 2016
  • 2017 Goals
    • Main goal for 2017, Promote/market Papyrus-RT as industrial solution for software system development in embedded domains (e.g. Automotive, CPS, and Mechatronics)
      • Develop marketing material, e.g. data sheets
      • Plan for presentation/tutorials at key (commercial) events
      • Plan for meetings and evaluation workshops with potential users
    • Use Papyrus-RT as a basis for the development of an open source (Papyrus based) alternative to Rhapsody
      • Present proposal to interested parties based on Papyrus RT
    • Develop support for hybrid textual/graphical modeling
  • Question
    • Should we also promote the use of UML-RT (Papyrus-RT) for system engineering?
  • Milestones
    • Papyrus-RT 0.9 release planned for mid-to-late February 2017
    • Papyrus-RT 1.0 is planned for June, 2017 (aligned with Oxygen)
  • Comments
    • We need to align with the current Eclipse release, but not part of the release train (at least in 2017)

Papyrus for System Engineering (SE)

  • Product Lead: Gert Johansson (Saab/Combitech)
  • Organizations involved: Combitech, CEA, Ericsson, Flanders Make, Saab, Zeligsoft
  • Scope
    • Support for SysML
    • SysML 1.4
    • Support for SSE in the context of SysML
  • Question
    • What is the status of SSE support (Sofia)?
  • Status
    • SysML profile has been developed for Papyrus (CEA), but no SysML specific DSL tooling yet
    • Gert J organized workshops to evaluate Papyrus for SE and gather requirements with different potential users
      • Initial attempt at requirements (roadmap) has been produced and is on the Google Drive
  • 2017 Goals
    • Develop Papyrus-SE 0.7
      • Develop an RCP version of Papyrus-SE, based on exiting Papyrus with SysML profile and existing additional components
    • Develop a version of Papyrus-SE (as a DSL)
      • Question: Should the Papyrus IC invest in the development of such a version (in a joint investment context)?
      • Identify lead users/stakeholders
        • Also, use this project (development of Papyrus-SE) to attract/recruit new members
      • Define the set of main use cases and requirements for tool usage (simplification from Papyrus Platform with SysML profile)
      • Develop required tool customization for DSL support
    • Increase the value of Papyrus for SE
      • Identify key capabilities to be integrated with Papyrus for SE to increase the value of modeling for SE, e.g. deployment analysis/validation, PLM, co-simulation (OPenCPS project and others),etc
      • Built partnership (recruit as new members) organizations that can bring such value
    • Promote Papyrus in SE communities
      • Package by end of Q2
        • Tutorial
        • Installation instructions
      • Have something in the booth at INCOSE Symposium
        • Datasheet
        • Demonstration scenario (use case)
      • We need to further elaborate on this plan for SE
      • Get formally involved in INCOSE
        • People reponsible: TBD
          • People in different countries/regions
        • INCOSE plan needs to be defined
  • Milestones
    • Release of Papyrus-SE 0.7 by end of June
    • Budget
      • Potential Papyrus IC budget to be invested in a joint-funding of a version of Papyrus for System Engineering? $20,000 USD?
      • If we decide to make this investment, we should also maximize the impact by developing proper marketing around it

Papyrus for Information Modeling (IM)

  • Product Lead: Philip L
  • Organizations involved: EclipseSource, CEA, Ericsson, TM Forum
  • Scope
    • Class modeling
    • Basic associations
    • Documentation
    • Simplified interface
    • reduced menus
    • Getting stared tutorial
    • Installation instructions
    • How it was "DSL'ified"
  • Status
    • Papyrus for Information Modeling (IM) 0.7 was released in June 2016
  • 2017 Goals
    • Maximize the potential usage of Papyrus-IM in different contexts
      • Promote Papyrus for IM in different forums, in particular in SDO's
      • Work with Stakeholders to define requirements, priorities and plan for evolution of Papyrus-IM
    • Apply further simplifications and bug fixing
      • Work with TM-Forum (and TM-Forum members) to identify required increments in Papyrus-IM to foster adoption
    • Continue to use Papyrus for IM as a base example for Customization and DSL support
      • Add documentation/example for adding a DSMLs on top of Papyrus-IM
      • Add documentation/example for adding a textual modeling language alongside Papyrus-IM models
  • Milestones
    • Papyrus IM 0.8 or 1.0?
  • Comments
    • The content (UML concepts) of Papyrus for IM is also essentially what is used by Airbus Defence & Space (Xavier Plavis) and Spacebel (Johan Hardy) for software design with C code gen
    • Papyrus for IM is key for SDO's, e.g. TM Forum, MEF, IETF
  • Budget: TBD

Papyrus for Enterprise Architecture (EA)

  • Product Lead: Thomas Wiman (Adocus)
    • Other people involved:
      • Francis Bordeleau (Ericsson)
      • Juan C (CEA)? - for Papyrus for Process Business Modeling
  • Organizations involved: Adocus, CEA (?), Ericsson
  • Scope
    • Papyrus for ArchiMate has been developed by Adocus. It will released in open source.
    • Business Process Modeling
    • Information Modeling
  • Questions
    • Does it include TOGAF?
    • What is the status of the BPMN profile (CEA)?
  • Status
    • Several pieces required for Papyrus-EA have already been developed, including Papyrus for ArchiMate (developed by Adocus), BPMN (developed by CEA), and Papyrus for IM (EclipseSource, CEA)
  • 2017 Goals
    • Define Papyrus-EA plan by end of 2017Q1?
      • Engage with potential lead users/stakeholders
      • Organize meeting in Sweden in 2017Q3?
    • Grow the Supplier community (for Papyrus-EA)
  • Milestones
    • Plan v1: End of March, 2017?

Papyrus for xtUML

  • Product Lead: Cortland Starrett (OneFact)
  • Organizations involved: OneFact, Saab
  • Scope
    • Support for xtUML
  • Status
    • Plan definition in progress
    • BridgePoint exists in open source as an Eclipse project
  • 2017 Goals
    • Define and publish plan for Papyrus-xtUML
      • Develop advanced type system
      • Hybrid textual/graphical modeling (based on MASL)
      • Provide intelligent OAL editor to support existing user base
      • Provide package references for application modelers
  • Milestones
    • Plan to be published by end of Q1?
  • Comments
    • A main priority consist in providing a migration path from current BridgePoint tool
    • Need to define overlap and opportunity (Charles R and Cort S) based on "overlap" investigation done by Ed Seidewitz, Bran Selic, and John Wolfe

Quality Framework and Testing

  • Charter Responsibility:
    • Ensure quality of the different open source components.
  • Goal: Define and implement strategy to ensure industrial quality of Papyrus and related open source components
    • Person Responsible: TBD
      • Role
        • Manage and monitor overall
        • Report to committee
    • Organizations involved: All members (also open to the Papyrus community in general)
    • Scope
      • Define strategy for test case management
      • Need to address "how to manage the set of test cases/test suites" contributed by developers and users in a scalable fashion (in the context of CI)
      • Need to distinguish
        • What
          • One of the main points is how to enable different people to contribute test cases
        • How
          • The how (testing platform, CI, ...) needs to be develop in collaboration with the Architecture Committee
          • Usage of RCPTT -- we need to encourage using Polarsys tools (e.g. RCPTT) to test Papyrus and related components, and provide test cases (RCPTT and/or SWTBot) with bugs
          • Define a replicable process that can be used by the different members
        • Differentiate between Papyrus Industry Consortium and Eclipse projects
      • Use as a starting point the work already done by CEA, Ericsson, EclipseSource, and others
      • Test the different "ilities"
        • Usability, Scalability, Stability, …
      • Input
        • What is available from Papyrus?
        • Statement on current state of practice
        • Expectations
        • Bug reporting to include test definition/asset
      • Governance of bugs: e.g., triage, lifecycle, etc.
        • E.g., response to bug withing a week.
    • Status
      • A template for description of Papyrus testing and usage has been created on the Product Management page of the Papyrus IC wiki
      • Members need to start entering information in this section so that we have a picture of what is currently being tested and used by users/members
    • Plan: TBD
    • Milestones: TBD
    • Budget: TBD

Marketing

  • Person Responsible: Charles Rivet (Zeligsoft)
  • Goals
    • Provide a clear, consistent branding for the Papyrus Industry Consortium and Papyrus product line
    • Ensure that an active social media presence is grown
    • Improve how Papyrus is perceived in the industry
  • Marketing Materials
    • Goal: Provide a clear, consistent branding for the Papyrus Industry Consortium
      • Plan
        • Branding
            • Logo(s): Ensure that all Papyrus IC products have proper logos
            • Tag line: Create a representative, easily remembered tag line for the Papyrus IC
            • Document Templates: Create templates for Papyrus IC presentations and other documents
            • Usage guidelines: Provide governance for Papyrus IC brand elements
          • Branding Budget: USD 2,000
        • Materials
          • Datasheets
            • Create a Papyrus IC datasheet to highlight the advantages and benefits of a Papyrus IC membership
            • Create a user members datasheet to promote users' leadership and involvement in the consortium
            • Create a supplier datasheet to promote suppliers' expertise provided in the developement of consortium products
            • Create a research and academia datasheet to promote the reseach and academia's contributions to the Papyrus IC
            • Papyrus IC success stories
            • Datasheets Budget: USD 5,000
          • Posters
            • Papyrus IC
            • Papyrus IC products
            • Papyrus-IC Research and Academia
            • Papyrus IC User and Suppliers Members
            • Papyrus IC success stories
            • Poster Budget: USD 1,000
          • Swag
            • Papyrus IC stickers
            • Others, TBD: e.g.Pens, pads
            • Swag Budget: USD 1,000
          • Roll-ups
            • Papyrus IC Rollup
            • Papyrus IC products Rollup
            • Think about geographical distribution for greater and easier availability
            • Roll-Up Budget: USD 2,000
      • Budget (Marketing Materials): USD 9,000
  • Marketing Communications
    • Goal: Ensure that an active media presence is maintained
      • Plan
        • General
          • Established a tagsonomy
          • Governance
        • Channels
          • Social media
          • Traditional media
          • Champions and Influencers
        • Collaboration
        • Governance (Metrics)
      • Budget (Marketing Communications): USD 1,000
  • Conferences
    • Goals
      • Increase visibility and credibility
      • Grow community
      • Governance around collection and usage of contacts
      • List of Conferences
        • TM Forum Live
          • Dates: 2017.05.15-18
          • Comment: We will only go to the TM Forum Live conference if we can schedule 1-on-1 meetings with TM Forum members
          • Budget: No specific budget required
            • Travel to be covered by recruitment budget (~ 3000 USD)
        • Saab Modeling Days
          • Date: TBD March/April in Linköpink, Sweden
          • Budget: No specific budget required
            • Travel to be covered by recruitment budget
        • EclipseCon France
          • Date: 2017.06.21-22
          • Comments
            • Needs to be synchronized with PolarSys
            • Eclipse conference -- Showcase Eclipse offerings
          • Member Presence:
            • CEA
            • EclipseSource
            • Airbus
            • Zeligsoft
          • Budget: PolarSys: TBD; Papyrus IC: $2,500 USD
        • Ericsson Modeling Days
          • Date: 2017.09.12-13 -- TBC
          • Comments: To be organized in collaboration with Papyrus IC Research/Academia
          • Budget: No specific budget required
        • MODELS 2017 - ACM/IEEE 19th International Conference on Model Driven Engineering
          • Date: 2017, 09, 24-29
          • Comments: THE conference for modeling
            • Promote research progress
            • Help large Eclipse community
            • Support members papers and initiatives (?)
          • Co-sponsor evening event with PolarSys ( EUR 2,500)
          • Attendance
            • CEA
            • Zeligsoft
            • EclipseSource?
            • Ericsson?
          • Budget: 5,000 USD (co-sponsored with PolarSys?)
        • EclipseCon Europe 2016
          • Date: 2017.10.25-27 -- TBC
          • Papyrus IC booth
          • Papyrus IC meeting?
          • Eclipse conference -- Showcase Eclipse offerings
          • Organize Papyrus Committers Day? EclipseSource to plan and propose
          • Budget: $10,000 USD for Booth + Papyrus Committer Day
      • Budget (Conferences): $22,500
  • Develop a network of six (6) champions
    • Goal: To recruit vocal thought leaders and work with influencers to promote the Papyrus IC
      • Plan:
        • Directly contact potential champions using members' contacts -- networking, request contributions from members
      • Budget: No budget required

Architecture

  • Goal: Work in collaboration with Papyrus Committers to enhance support for DSL's, including DSL defined on top of other DSL's and DSL composition
    • Sub-goal 1: Improve Papyrus support for composability and extension
      • Person Responsible: Florian Noyrit (CEA)
      • Scope
        • Facilitate the reuse of some part of the tool, by isolating the various components & clearly identify the quality of the various group of plugins (industrial strength / prototype / early developments)
      • Status
        • Phase 1 in progress
      • Plan
        • Phase 1: Identify the sub projects from current repositories
        • Phase 2: Split into the various repositories, have a build environment setup for all contributions
        • Phase 3: After Oxygen release (mid-2017) => start restructuration of Papyrus as a Top Level Project.
      • Milestones
        • End 2016: Completion of Phase 1
        • After Oxygen release (mid-2017): Phase 3
      • Comments
    • Sub-goal 2: Reduce dependencies on the core components
      • Person Responsible: Per Jonsson (Combitech)
      • Scope
        • Simplify the build of products on top of Papyrus, by reducing risks of evolution in dependencies & by reducing UI cluttering
      • Status
      • Plan
        • End 2016: report on Papyrus mailing list
        • Oxygen: Evolution of the implementation (plugin splitting, code move) on Papyrus code base.
      • Milestones
      • Comments
        • Minimize mandatory dependencies bring UI contributions, like Java Dev Tools UI
        • Reduce requirements for building up extensions on top of Papyrus,speed up product buildings and reduce UI cluttering
    • Sub-goal 3: Enhance current documentation on Papyrus customization
      • Person Responsible: Philip Langer (EclipseSource)
      • Scope
      • Documentation existing on how to build a simplified version of Papyrus (Information Modeling - IM), but with no notion of profile support (IM is plain UML only)
      • Status
      • Plan
        • 2017: Add the notion of profile based customization to the current documentation (coming from information modeling)
        • 2018: Help support for implementing customization, providing tools to support the process
      • Milestones
      • Comments
  • Goal: Provide technical expertise to support the development of an hybrid capability for textual/graphical modeling
    • Person Responsible: Simon Redding (Zeligsoft)
    • Scope
      • Provide an hybrid approach for modeling, with ability to work on graphical or textual representations
    • Status
    • Plan
      • 2 years research project => 2018 -- Details to be provided
    • Milestones
    • Comments
  • Goal: Provide technical input for other committees
    • Person Responsible: Remi Schnekenburger (EclipseSource), as Chairman
    • Comments
      • On demand, from other committees
      • Task to be delegated, depending on the topic

Research Academia

Organization

  • Goal: Form a leadership group for the Papyrus IC Research/Academia
    • The list of people that are part of the leadership group will be announced during Q1
  • Goal: Increase industry participation in/to Research/Academia activities
  • Goal: Development of the overall Research/Academia community

Training and Education

  • Goal: Establish Papyrus as the leading platform for teaching in MBE
    • Success factors
      • Number of contributions to wiki
      • Number of courses taught with Papyrus
  • Goal: Support the creation of at least 2 complete teaching material packages using Papyrus
    • Examples
      • Support the creation of a complete education package for UML course
      • Support the creation of a complete education package for UML-RT course
      • Support the creation of a complete education package for basic SysML course
    • Success factor: Creation of two course packages
  • Goal: Distribution of Rovers and Rover contest for education
    • Plan
      • Develop Rover Application Form
      • Get the form approved by Steering Committee
      • Publicize and communicate the process for applying for Papyrus IC rovers
      • Determine if we want to create a contest for courses using with the rovers
        • If yes, than we also need to create the contest (define the context, rules, criteria, and prize)
      • Select professors/instructors to who rovers will be allocated
    • Success factor: Budget exhausted before the beginning of the fall semester
    • Budget: $3,000 USD
  • Goal: Determine whether the IC will organize/support a Rover term project for education in the Fall 2017 (?)
    • Person responsible: TBD
    • Plan
      • Should it be a contest? Perhaps it should be optional
      • We first need to organize it
        • Need to define the Way-of-Working (WoW) together with the Papyrus IC members and professors/instructors involved
        • Need to contact a group of potential professors/instructors
      • Project term definition and management
        • Take into account that each course will have different priorities
        • Define the requirements that the Papyrus IC would be proposing and managing
        • Having a representative of end-users
        • Put in place "Forum" for students to interact with the End-User (Papyrus IC members responsible for the requirements) and among themselves
    • Success factors
      • Number of courses using a rover project
    • Required budget
      • Provide budget for rovers for the courses

Research

  • Goal: Establish Papyrus as a leading platform for research in MBE
    • Plan
      • Reduce the barrier to entry for researchers to use Papyrus as a research platform
        • Look into which is the best medium for communication with users: Eclipse Forums, Stackoverflow, other?
        • Better support postings on Forum?
        • Should we define specific Papyrus packages for Research?
          • Including toolsmith capabilities and support for customization and DSL
        • Tutorials for research purposes (as oppose to tutorials for teaching)?
      • Create a Google group for research discussions
      • Establish dialog with researchers to better understand the needs regarding research platform
      • Increase visibility of the research projects and publications
      • Facilitate the creation of new Papyrus IC research projects
      • Support the creation of collaborative research projects
        • Including supporting financing and application submission
        • Schedule meeting with EU Commission representatives in Brussels to promote the PIC
      • Increase dissemination
      • Establish a presence in a major conference (e.g. MODELS) and increase presence in other events.
    • Success factors
      • Number of papers that use Papyrus
      • Attendance in conference activities
      • How many projects use Papyrus as base technology
  • Goal: Identify Papyrus IC research priorities
    • Person responsible: Ernesto Posse, Juergen Dingel
    • Plan
      • Form committee for the selection of research priorities
      • Industrial members to review the list of proposals and select the ones to elaborate
      • Determine the number of priorities to support for next year
        • We need to make sure that we can properly support the number of selected priorities from a commitment perspective
      • Select the priorities
        • Examples of potential priorities. See list of proposed priorities on wiki
      • Communicate the priorities to both Papyrus IC members and the broader MBE community
      • Establish concrete research projects based on these priorities -- see next Goal
    • Success Factors
      • Publication of research priorities by end of February 2017
  • Goal: Establish concrete collaborative research projects between Papyrus IC members
    • Plan
      • Papyrus IC to take decision on 2017 research priorities -- Still needs to be done, see previous Goal
      • Identify different ways of establishing research projects/colllaborations
        • Need to be creative in establishing key research projects
        • Industrial support of PhD/PostDoc researchers
      • Look for and select research funding programs
      • Work with researchers who have proposed these priorities to identify project collaborators (research team)
      • Identify industrial partners for the project
      • Identify potential funding sources
      • Collaborate on the project proposal
    • Success factors
      • Apply to at least 1 EU research project from Papyrus IC - See next goal.
      • Number of applications at national or international level: ??
      • Number of successful applications at national or international level: ??
  • Goal: Apply to 1 EU research project from Papyrus IC
    • Plan
      • Identify appropriate calls for the next 12 months
      • Identify potential sources of funding
        • Also, look at NA funding
      • Define project topics based on research priorities
        • For each topic
          • Define the leadership
          • Define project draft
    • Success factor
      • Completed application by end od the year
  • Goal: Distribution of Rovers for Papyrus based research
    • Plan
      • Develop Rover Application Form
      • Get the form approved by Steering Committee
      • Publicize and communicate the process for applying for Papyrus IC rovers
    • Success factor: Budget exhausted by the end of the year
    • Budget: $2,000 USD

Other potential goals

  • Goal: Organize student internships/summer visits to industrial partners
  • Goal: Organize Papyrus hackatons

Copyright © Eclipse Foundation, Inc. All Rights Reserved.