summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-11-02 06:11:04 (EDT)
committerSven Rottstock2012-11-02 06:11:04 (EDT)
commitb593dab4c85e87662947ccd0b29c2cddd48c7d9a (patch)
treef0a8ca5a66bae62569a2213ab813a8ec6325853b
parent42a55d5bfca5dd94a0f5dfea91ae140836b1c970 (diff)
downloadorg.eclipse.stardust.documentation-b593dab4c85e87662947ccd0b29c2cddd48c7d9a.zip
org.eclipse.stardust.documentation-b593dab4c85e87662947ccd0b29c2cddd48c7d9a.tar.gz
org.eclipse.stardust.documentation-b593dab4c85e87662947ccd0b29c2cddd48c7d9a.tar.bz2
CRNT-26515 - Added and Reviewed Restrictions
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@60534 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/analysttoc.xml2
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/control.pngbin0 -> 31366 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html67
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html27
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/toc.html30
7 files changed, 71 insertions, 63 deletions
diff --git a/org.eclipse.stardust.docs.analyst/analysttoc.xml b/org.eclipse.stardust.docs.analyst/analysttoc.xml
index f81d67f..1dfe8bd 100644
--- a/org.eclipse.stardust.docs.analyst/analysttoc.xml
+++ b/org.eclipse.stardust.docs.analyst/analysttoc.xml
@@ -11,7 +11,7 @@
SunGard CSA LLC - initial API and implementation and/or initial documentation
-->
<toc label="Business Process Modeling Handbook" link_to="toc.xml#analysttoc" topic="html/toc.html">
- <topic href="html/handbooks/modelling_analyst/pep-modeler-preface.html" label="Overview">
+ <topic href="html/handbooks/modelling_analyst/pep-modeler-preface.html" label="Introduction">
</topic>
<topic href="html/handbooks/modelling_analyst/pep-modeler-compatibility.html" label="Compatibility and Analogy of Models">
</topic>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/control.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/control.png
new file mode 100644
index 0000000..1ee078d
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/control.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
index d12dab5..d3dca2b 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
@@ -68,8 +68,8 @@ toolbar. The <strong>File Upload</strong> dialog box gets displayed.</p>
<p>Click <strong>Browse</strong> to locate the .XPDL file and click <strong>Upload</strong>.</p>
-<p>Models created in the Eclipse-based modeler should support BPMN drawing mode. When imported, only those models
-are displayed in the Business Modeling Perspective.</p>
+<p>Models created in the Eclipse-based modeler should support BPMN drawing mode (pools and lanes). When imported, only those models
+are displayed in the Business Process Modeling Perspective.</p>
<p>If the model of the same name already exists then the following confirmation dialog is displayed.</p>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
index a128d7e..28ffe68 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
@@ -21,47 +21,48 @@
<p>This chapter covers the following:</p>
<ul>
- <li>Compatibility of Models created in Eclipse-based Modeler with Web-based Modeler
- <ul>
- <li>Pools and Lanes Restrictions</li>
- <li>Representations of Gateways created in Eclipse-based Modeler</li>
- <li>Data Flow</li>
- </ul></li>
+ <li><a href="#comp">Compatibility of Models created in Eclipse-based Modeler with Web-based Modeler</a>
+ </li>
- <li>Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler
+ <li><a href="#analogy">Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler</a>
<ul>
- <li>Supported Elements</li>
- <li>Unsupported Elements</li>
+ <li><a href="#sup">Supported Elements</a></li>
+ <li><a href="#unsup">Unsupported Elements</a></li>
</ul></li>
</ul>
-<h2>Compatibility of Models created in Eclipse-based Modeler with Web-based Modeler</h2>
+<h2 id="comp">Compatibility of Models created in Eclipse-based Modeler with Web-based Modeler</h2>
<p>The <strong>Business Process Modeling</strong> perspective supports web-based modeling.
However, when it comes to importing models created in @productname@'s Eclipse-based modeler to the
web-based modeler, some restrictions are encountered. To ensure smooth deployment of models in
web-based modeler, you need to alter some of the elements in the model before you import.
-These elements are:</p>
-<ul>
- <li>Gateways</li>
- <li>Drawing Mode - Pools and Lanes</li>
-</ul>
+Following elements need special treatment either in Eclipse-based modeler or web-based modeler:</p>
<ul>
- <li>Cross Model support</li>
- <li>Data Flow</li>
+ <li>Gateways
+ <ul><li><a href="#gate">Representations of Gateways created in Eclipse-based Modeler</a></li>
+ <li><a href="#weg">Representation of Gateways created in Web-based Modeler</a></li></ul></li>
+ <li><a href="#swim">Swim Lanes</a></li>
+ <li><a href="#flow">Data Flow</a></li>
+ <li><a href="#cros">Cross-Modeling</a></li>
</ul>
<h3 id="gate">Representation of Gateways created in Eclipse-based Modeler</h3>
<p>Gateways need to have correct interpretation when you import the Eclipse-based model with gateways in
the Business Process Modeling perspective. In the Business Process Modeling perspective
-gateways are first class elements.
-However there is no first class diagram element for gateways in the Eclipse-based modeler.
+gateways are first class elements (you can drag-and-drop gateway symbol from the toolbar).
+However, there is no first class diagram element for gateways in the Eclipse-based modeler.
That's why models created in @productname@'s Eclipse-based modeler and to be imported in web-based modeler should have:</p>
<ul>
<li>route activities to represent gateways</li>
<li>a route activity with ID = Gateway must be used for each gateway</li>
- <li>a Control Flow property must have Join and Split types set to the same value</li>
+ <li>a Control Flow property must have Join and Split types set to the same value</li>
+
+ <p class="image"><img src="images/control.png" alt=""> <br>
+<strong>Figure:</strong> Route Activity - Control Flow</p>
+
+
</ul>
<p>
The model created in Eclipse-based modeler should represent gateways in the following way:
@@ -76,9 +77,9 @@ following figure:</p>
<p class="image"><img src="images/peper-gate.png" alt=""> <br>
<strong>Figure:</strong> Gateways interpreted in Web-based Modeler</p>
-<h3>Representation of Gateways created in Web-based Modeler</h3>
+<h3 id="weg">Representation of Gateways created in Web-based Modeler</h3>
<p>Gateways added in web-based modeler are displayed in Eclipse-based modeler as route activities.
-The control flow properties of the route activity is set according to the following rules:</p>
+The control flow property of the route activity is set according to the following rules:</p>
<ul>
<li>AND/XOR property follows the explicit definition made in web-based modeler</li>
<li>Both Join/Split behavior is set to the gateway type. This means either both are AND or both are XOR.</li>
@@ -87,10 +88,28 @@ The control flow properties of the route activity is set according to the follow
<p class="image"><img src="images/gateway-eclipse.png" alt=""> <br>
<strong>Figure:</strong> Gateways interpreted in Eclipse-based Modeler</p>
+<h3 id="swim">Swim Lanes</h3>
+<p>Models created in the Eclipse-based modeler should support BPMN drawing mode (pools and lanes).
+When imported, only those models are displayed properly in the Business Process Modeling Perspective.
+</p>
+
+<h3 id="flow">Data Flow</h3>
+<p>The web-based modeler allows only:</p>
+<ul>
+ <li>One input data mapping</li>
+ <li>One output data mapping</li>
+ <li>A pair of the two </li>
+</ul>
+
+<h3 id="cros">Cross Modeling</h3>
+<p>In cross modeling, to maintain the references between the models, the imported referenced model should be kept in the
+same project folder. If the imported model resides at any other location then the references are not resolved
+by the Eclipse-based modeler and web-based modeler. </p>
+
-<h2>Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler
+<h2 id="analogy">Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler
</h2>
<p>The @productname@ supports creation of workflow models in two ways.
@@ -100,7 +119,7 @@ in the Business Process Modeling perspective of
some of the model elements are not supported in
web-based modeler. For those unsupported elements, you should use @productname@'s
Eclipse-based modeler. </p>
-<h3>Supported Elements</h3>
+<h3 id="sup">Supported Elements</h3>
<p>Following is the list of supported elements. That means, you can add, edit, delete and rename these elements.</p>
<table width="1%" border="1" id="id_3">
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html
index a03e661..ea0295a 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html
@@ -5,7 +5,7 @@
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1"
type="text/css">
-<title>Overview</title>
+<title>Introduction</title>
<script language="JavaScript" src="../../styles/naviLine.js"
type="text/javascript"></script>
</head>
@@ -17,9 +17,7 @@
"../../toc.html","Business Process Modeling Handbook");
-->
</script>
-<h1>Overview</h1>
-<p>This chapter provides overview of the elements to model processes with the @productname@'s
-Business Process Modeling perspective.</p>
+<h1>Introduction</h1>
<p>The Business Process Modeling perspective uses the <a href="http://www.bpmn.org/">Business Process Model and Notation (BPMN)</a>
standards. The business process modelers' and integrators can use it to create intuitive business
@@ -40,25 +38,8 @@ Installation</a> of the
<a href="PLUGINS_ROOT/com.infinity.bpm.docs.installation/html/installation/ig-preface.htm">
Developer Installation Guide</a>.</p>
</div>
-<h2>Content</h2>
-<p>The Business Process Modeling handbook contains following chapters.</p>
-<ul>
- <li>The chapter <a href="pep-modeler-compatibility.html">Compatibility and Analogy of Models</a>
- provides comparison between @productname@'s Eclipse-based modeler and Business Process Modeling perspective.</li>
- <li><a href="pep-perspective-overview.html">The Business Process Modeling Perspective</a> describes panels and process diagram canvas. </li>
- <li>The <a href="models/model-preface.html">Working with Models</a> guide describes model properties and how to work with models.</li>
- <li><a href="pep-process.htm">Working with Process Definitions</a> </li>
- <li><a href="pep-activities.htm">Specifying Activities</a></li>
- <li><a href="pep-con-sequence.htm">Working with Sequence Flows</a></li>
- <li><a href="pep-application.htm">Specifying Applications</a></li>
- <li><a href="pep-data.htm">Specifying Data</a></li>
- <li><a href="pep-data-flow.htm">Specifying Data Flow</a></li>
- <li><a href="pep-gateways.htm">Working with Gateways</a></li>
- <li><a href="pep-org-struct.htm">Modeling the Organizational Structure</a></li>
- <li><a href="pep-events.htm">Working with Events</a></li>
- <li><a href="pep-pools-lanes.htm">Swim Lanes Usage</a></li>
-
-</ul>
+
+
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
index 69779ca..c7588aa 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
@@ -211,9 +211,9 @@ Perform the following steps to modify the Data Path properties:</p>
<li>Descriptor - Select this check box to define a descriptor for a process definition. </li>
<li>Key Descriptor - Select this check box to define a key descriptor for a process definition.
For more information, please refer to the chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/maodelling/mg-defdesk-9.htm">Working with Data Paths</a>
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-9.htm">Working with Data Paths</a>
of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/maodelling/mg-preface.htm">Modeling Handbook</a>. </li>
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-preface.htm">Modeling Handbook</a>. </li>
</ol>
<h3>Display</h3>
diff --git a/org.eclipse.stardust.docs.analyst/html/toc.html b/org.eclipse.stardust.docs.analyst/html/toc.html
index b877c24..67dedd0 100644
--- a/org.eclipse.stardust.docs.analyst/html/toc.html
+++ b/org.eclipse.stardust.docs.analyst/html/toc.html
@@ -33,20 +33,28 @@ It is intended for business analyst who can use it to create business process fl
<h2>How this Book is organized</h2>
<p>This book is organized in the following chapters:</p>
-<ol>
-
- <li>The chapter Business Process Modeling Perspective provides details about the perspective layout,
- panels and toolbar.</li>
- <li>The chapter Working with Model helps you to view properties of a model, create and deploy models.</li>
-
-</ol>
-
-<h3>Related Documents</h3>
<ul>
- <li class="ipp">The <a href="PLUGINS_ROOT/com.infinity.bpm.docs.installation/html/installation/ig-preface.htm">Installation
- Guide</a> provides instructions on setting up the @productname@ Process Engine.</li>
+ <li>The chapter <a href="pep-modeler-compatibility.html">Compatibility and Analogy of Models</a>
+ provides comparison between @productname@'s Eclipse-based modeler and Business Process Modeling perspective.</li>
+ <li><a href="pep-perspective-overview.html">The Business Process Modeling Perspective</a> describes panels and process diagram canvas. </li>
+ <li>The <a href="models/model-preface.html">Working with Models</a> guide describes model properties and how to work with models.</li>
+ <li><a href="pep-process.htm">Working with Process Definitions</a> </li>
+ <li><a href="pep-activities.htm">Specifying Activities</a></li>
+ <li><a href="pep-con-sequence.htm">Working with Sequence Flows</a></li>
+ <li><a href="pep-application.htm">Specifying Applications</a></li>
+ <li><a href="pep-data.htm">Specifying Data</a></li>
+ <li><a href="pep-data-flow.htm">Specifying Data Flow</a></li>
+ <li><a href="pep-gateways.htm">Working with Gateways</a></li>
+ <li><a href="pep-org-struct.htm">Modeling the Organizational Structure</a></li>
+ <li><a href="pep-events.htm">Working with Events</a></li>
+ <li><a href="pep-pools-lanes.htm">Swim Lanes Usage</a></li>
+
</ul>
+<h3>Related Documents</h3>
+<p>The <a href="PLUGINS_ROOT/com.infinity.bpm.docs.installation/html/installation/ig-preface.htm">Installation
+ Guide</a> provides instructions on setting up the @productname@ Process Engine.</p>
+
<h2>Contact Us</h2>
<p>Your opinions and recommendations are always welcome. Our
technical documentation team relies heavily on your feedback. Feel free