|
|
| (2 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | <div style="border-left:1px dotted silver;margin-left:2px;margin-right:20px;padding-bottom:25px;padding-left:12px;"> | + | <div style="border-left:1px dotted silver;margin-left:2px;margin-right:20px;padding-bottom:25px;padding-left:12px;"><br></div> |
| − | <div style="line-height: 140%;">
| + | |
| − | <p> </p>
| + | |
| − | <table>
| + | |
| − | <tr title="">
| + | |
| − | <td>Title:</td>
| + | |
| − | <td>BPMN view for the JWT Workflow Editor</td>
| + | |
| − | </tr>
| + | |
| − | <tr title="">
| + | |
| − | <td>Student:</td>
| + | |
| − | <td>Ilshat Khasanov</td>
| + | |
| − | </tr>
| + | |
| − | <tr title="">
| + | |
| − | <td></td>
| + | |
| − | <td>The goal of this project is to implement the BPMN [1] view for the Workflow Editor of the<br/>Java Workflow Tooling project [2] on top of the JWT meta-model (which should therefore be extended with JWT's aspect oriented mechanism) to provide native support of the popular BPMN standard.
| + | |
| − | </td>
| + | |
| − | </tr>
| + | |
| − | <tr style="border-bottom:1px dotted silver;">
| + | |
| − | <td></td>
| + | |
| − | <td><p> </p>
| + | |
| − | <p><strong>Abstract</strong></p>
| + | |
| − | <p>The JWT Workflow Editor is designed as an extensible toolset which provides possibilities to extend the editor with additional elements and this already been shown in a UML activity diagram view and an event-driven process chain view.<br/>As more and more developers as well as business analysts are heading towards BPMN it is only natural that there should also be an own view for BPMN in the JWT editor [3]. This will allow developers to switch between models to work with a view which they are familiar with.</p>
| + | |
| − | <p><strong>Detailed Information</strong></p>
| + | |
| − | <p>At the present the JWT contains modules to transform the JWT-model into BPMN and vice versa [4] but there's no view for BPMN. General idea is to use JWT's view mechanism to realize the BPMN view as an additional option to the existing views. The project can be formulated in the following steps:</p>
| + | |
| − | <p>1. <span><em><span><span>Redesign Metamodel</span></span></em><br/></span> a) Map JWT elements to BPMN elements where possible<br/> b) Define additional elements through aspects (e.g. Events)<br/> c) Extend/Refactor JWT metamodel where a) and b) are not possible<br/><br/>2. <span><em><span><span>Extend Editor</span></span></em><br/></span> a) Allow a flexible hierarchy of graphical (Draw2d) elements (e.g. JWT Action Figures are currently contained in Scope Figures but for should probably be contained in JWT Roles which may correspond to BPMN swimlanes). This hierarchy is determined by the editparts. Also commands for creating elements may need to be adjusted to support this structure. It would be a mapping that allows to define an arbitrary tree hierarchy for JWT elements which is then used for graphical representation, EMF commands (create child, ...), tree representation (e.g. outline view) etc.<br/><br/>3. <span><em><span><span>Create Graphical View</span></span></em></span><br/> a) Define visual representation of meta model elements for BPMN (Figures, Icons)<br/> b) Allow GEF to correctly draw the visual representation (e.g. layouting of the swimlanes)</p>
| + | |
| − | <p> </p>
| + | |
| − | <p><strong>Background</strong></p>
| + | |
| − | <p>I checked out the source tree of the JWT project from CVS repository and prepared all necessary environment for further development. During the time leading up to the start of the GSoC programme I'll study the BPMN specifications, difference between BPMN 1.2 and BPMN 2, JWT metamodel and implementation of the existing views. All required information can be obtained by me from my mentor (Christian Saad) and projects' mailing list [5].</p>
| + | |
| − | <p><strong>Deliverables</strong></p>
| + | |
| − | <ul>
| + | |
| − | <li>BPMN view for the JWT Workflow Editor (including source code)</li>
| + | |
| − | <li>Unit tests / example diagrams</li>
| + | |
| − | <li>Documentation of the project including user guides and manuals</li>
| + | |
| − | </ul><br />
| + | |
| − | <p><strong>Schedule</strong><br/>
| + | |
| − | </p>
| + | |
| − | <table cellpadding="2">
| + | |
| − | <tr>
| + | |
| − | <td><strong>Time Interval </strong></td>
| + | |
| − | <td><strong>Duration </strong></td>
| + | |
| − | <td><strong>Description</strong></td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">Apr 26 - May 24</td>
| + | |
| − | <td>4 weeks</td>
| + | |
| − | <td>Community bonding; study JWT and BPMN metamodels;<br />
| + | |
| − | study usage of aspects in JWT</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">May 24 - Jun 13</td>
| + | |
| − | <td>3 weeks</td>
| + | |
| − | <td>Create initial BPMN view prototype<sup>*</sup></td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">Jun 13 - Jun 27</td>
| + | |
| − | <td>2 weeks</td>
| + | |
| − | <td>Extend/Refactor JWT metamodel</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">Jun 27 - Jul 12</td>
| + | |
| − | <td>2 weeks</td>
| + | |
| − | <td>Extend Workflow Editor</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#efe;"><em>Jul 14</em></td>
| + | |
| − | <td>–</td>
| + | |
| − | <td><em>Mid-term evaluation</em></td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">Jul 16 - Jul 26</td>
| + | |
| − | <td>1.5 weeks</td>
| + | |
| − | <td>Implement visual representation of metamodel elements for BPMN</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">Jul 26 - Aug 6</td>
| + | |
| − | <td>1.5 weeks</td>
| + | |
| − | <td>Test the project, correct bugs</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#ffffe6;">Aug 6 - Aug 13</td>
| + | |
| − | <td>1 week</td>
| + | |
| − | <td>Write documentaton and user manual</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td style="background-color:#fee;"><em>Aug 18</em></td>
| + | |
| − | <td>–</td>
| + | |
| − | <td><em>Final evaluation</em></td>
| + | |
| − | </tr>
| + | |
| − | </table>
| + | |
| − | <p><span>* I would like to work in an iterative manner, producing a working prototype with the specified feature at the end of each milestone.</span></p>
| + | |
| − | <p><strong>Expectations</strong></p>
| + | |
| − | <p> I expect one of our main issues to discuss during the project will be extending the JWT-metamodel to fit into BPMN specifications.</p>
| + | |
| − | <p><strong>Contact Information</strong></p>
| + | |
| − | <p>My name is Ilshat Khasanov and I'm an undergraduate CS student at Ufa State<br/>Technical University of Aviation (Russian Federation).</p>
| + | |
| − | <p>I have an expirience working with Eclipse as java developer since 2006<br/>and as Eclipse plugin developer since 2009 (DDL-generator plugin for Eclipse using DTP). Also I worked with the Eclipse's jBPM-designer plugin to create reglaments (such as security emission process) and deploy them to JBoss for the federal agency. Also I have an expirience using the web services technology in Java, XML, XSD, SVN, Maven.</p>
| + | |
| − | <table>
| + | |
| − | <tr>
| + | |
| − | <td>Email</td>
| + | |
| − | <td>mo.ais2010 [at] gmail.com</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>Skype</td>
| + | |
| − | <td>ilshat.khasanov</td>
| + | |
| − | </tr>
| + | |
| − | <tr>
| + | |
| − | <td>IM</td>
| + | |
| − | <td>362144694 (ICQ)</td>
| + | |
| − | </tr>
| + | |
| − | </table>
| + | |
| − | <p><strong>References</strong></p>
| + | |
| − | <p>[1] http://wikipedia.org/wiki/BPMN<br/>
| + | |
| − | [2] http://www.eclipse.org/jwt/<br/>
| + | |
| − | [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=298288<br/>
| + | |
| − | [4] http://www.eclipse.org/jwt/components/transformations/<br/>
| + | |
| − | [5] http://dev.eclipse.org/mhonarc/lists/jwt-dev/maillist.rss
| + | |
| − | </p>
| + | |
| − | <p> </p>
| + | |
| − | </td>
| + | |
| − | </tr>
| + | |
| − | </table>
| + | |
| − | </div> | + | |
