1. © 2002 IBM Corporation Confidential | Date | Other Information, if necessary Java Workflow Toolbox (JWT) Release review: Workflow Editor v0.4 & Transformations Florian Lautenbacher (University of Augsburg, DE) Marc Dutoo (Open Wide, FR) Stéphane Drapeau (Obeo, FR) whoever else!?

2. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 2 Overview  Introduction  Features  Non-code aspects  APIs  Architectural issues  Tool usability  End-of-Life  Bugzilla  Standards  UI Usability  Schedule  Communities  IP Issues  Project Plan  Notes

3. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 3 Introduction  JWT is a technology sub-project in Incubation phase (http://www.eclipse.org/projects/dev_process/incubation-phase.php).  This release covers the first release of the Workflow Editor, currently in development version 0.4 as well as model transformations from BPMN to JWT (and vice versa) as well as from JWT to XPDL.  These slides conform to the Eclipse Guidelines for a Release review which can be found under http://www.eclipse.org/projects/dev_process/release-review.php.

4. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 4 Features  This is the first release of the workflow editor. It supports the modeling of processes/workflows in order to execute them afterwards. The modeled workflow can be transformed into executable BPEL-code or XPDL-code or something else afterwards.  If somebody has already created a BPMN model with the Eclipse BPMN modeler (s)he can use a model transformation in order to transform that process into the JWT format.  The WE includes overview pages, several tabs, wizards, etc. to ease the process of modeling.

5. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 5 Non-code aspects  Summarize the state of the non-code aspects of the release including: user documentation, localization/externalization, examples, tutorials, articles, and so on. Have the existing artifacts been updated? Are there new artifacts? Have the obsolete ones been retired or at least marked as pertaining only to older material?

6. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 6 APIs  Certify that the APIs in this release are Eclipse Quality (http://www.eclipse.org/projects/dev_process/eclipse-quality.php). The project lead will personally certify that the requirements for quality have been met and/or discuss any deficiences.Eclipse Quality  Platform quality frameworks.  Platform quality tools.  All exemplary tools are built on platform APIs.  Performance and scalability to enterprise class use.  Automated tests and a quality plan that can be used by any Eclipse developer. We want any Eclipse user to be able to run all the tests and verify that they have a working and correct installation of the frameworks and tools.  A release-to-release migration plan potentially including automated tools for conversions. Release-to-release migration includes not only the APIs, but also the artifacts generated by the tools (e.g., configuration files, persisted tables, etc).  API stability.  Predictable behavior and a predictable rate of change.  Demonstrated community involvement.

7. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 7 Architectural issues  ToDo  Summarize the architectural quality of the release. Discuss the intrinsic nature of being extensible embodied by this project. Discuss issues such as unresolved overlap with other projects, unpaid "merge debt" from incorporating various components, and so on.

8. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 8 Tool usability  The WE allows users to model their business processes in order to execute them afterwards. Therefore, several wizards are available to create new process models (e.g. from templates), add specific information such as applications, data, roles, etc.  An overview page shows the most important information at one glance.  Enables the user to model her process in a graph-based structure (not block-based like BPEL), but nevertheless generate BPEL code afterwards

9. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 9 End-of-Life  Since this is the first release, there is no feature that is end-of-life‘d in this release.

10. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 10 Bugzilla  ToDo  Summarize the bugzilla situation. How many bug records (defects and enhancements) have been opened/closed/deferred/new, etc? How many P1, P2,..., bug records are outstanding?

11. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 11 Standards  No standard, however, transformation to existing standards such as BPMN, BPEL or XPDL is currently ongoing work or already completed.  The model transformations use the standard XXX.

12. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 12 UI Usability  Code supports several languages, currently implemented is German and English.  Summarize the user interface usability and the conformance to the Eclipse User Interface Guidelines. Include section 508 compliance, language pack conformance (does the code support multiple languages), etc. Explain any deviations from the user interface guidelines and standards. Eclipse User Interface Guidelines

13. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 13 Schedule  Project more focused on the editor and transformation part as well as on being a platform for SOA and SCA (together with the current STP projects).  New components planned (jwt-compatibility), several extensions to the workflow editor already developed (e.g. documentation of the process model in html, several views, etc.)  Milestones were not met completely since the structure of the project changed in the last months.

14. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 14 Communities  Active bugzilla by the committers (not by users, since no release available yet)  Many discussions on the mailing list, inside JWT as well as with partners from the STP projects (STP IM, etc.)  Presentation at the Eclipse Summit Europe 2007 in Ludwigsburg  Coordination with OW2 projects ??  Summarize the project's development of its three communities. Consider the interactions on bugzilla, the mailing lists, the newsgroups, public conference calls, blogs, PR activities, code camps, conference tutorials, coordinating with other Eclipse projects and other open source projects (Apache, ObjectWeb, etc),...

15. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 15 IP Issues  The code has been committed by individuals who are either committers of the project themselves or their foundation.  The contribution questionaire for this initial code contribution has been completed.  The legal information is inserted into the source code as described in the Eclipse IP Policy.

16. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 16 Project Plan  To discuss  If there is a Project Plan (full or even a draft) for the next release, the final issue to cover in the Release Review is the unveiling of the new plan.

17. Eclipse Foundation, Inc. | © 2007 by OpenWide / University of Augsburg and made available under the EPL v1.0 17 Notes  The Eclipse development process document and the Guidelines document have been read and approved by the project leads and committers of the JWT project.