|
/
Zope
/
gocept svn checkins
/
Archive
/
2005
/
2005-08
/
SVN: r3305 - in misc/trunk/WorkflowEditor/docbook: . src/requirements src/tables stylesheets
[
SVN: r3295 - branches / Roman Joost ... ]
[
SVN: r3319 - in glome/tags/glome-0_9_3-rel: . ... ]
SVN: r3305 - in misc/trunk/WorkflowEditor/docbook: . src/requirements src/tables stylesheets
Roman Joost <rj(at)gocept.com> |
2005-08-25 14:22:11 |
[ FULL ]
|
Author: roman
Date: Thu Aug 25 14:22:26 2005
New Revision: 3305
Modified:
misc/trunk/WorkflowEditor/docbook/ (props changed)
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/requirements/mandatory-features.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-editors.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-engines.xml
misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl
Log:
2005-08-25 Roman Joost <rj(at)gocept.com>
*.: set a ignore property
* src/requirements/mandatory-features.xml
* src/tables/table-technologies-comparison.xml: more
description about the rating
* src/tables/table-workflow-engines.xml
* src/tables/table-workflow-editors.xml: added widths to
colspecs
* stylesheets/plainpdf.xsl: disabled the use of tabularx,
which breaks the footnotes unfortunately. Don't have a clue why
this happens now.
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Thu Aug 25 14:22:26 2005
(at)(at) -1,3 +1,18 (at)(at)
+2005-08-25 Roman Joost <rj(at)gocept.com>
+
+ *.: set a ignore property
+ * src/requirements/mandatory-features.xml
+ * src/tables/table-technologies-comparison.xml: more
+ description about the rating
+
+ * src/tables/table-workflow-engines.xml
+ * src/tables/table-workflow-editors.xml: added widths to
+ colspecs
+
+ * stylesheets/plainpdf.xsl: disabled the use of tabularx,
+ which breaks the footnotes unfortunately. Don't have a clue why
+ this happens now.
+
2005-08-24 Roman Joost <rj(at)gocept.com>
* src/introduction/workflow-patterns.xml
Modified:
misc/trunk/WorkflowEditor/docbook/src/requirements/mandatory-features.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/requirements/mandatory-features.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/requirements/mandatory-features.xml Thu
Aug 25 14:22:26 2005
(at)(at) -40,4 +40,12 (at)(at)
</listitem>
</itemizedlist>
+ <para>
+ Besides these features, pieces of software can provide additional
+ things, which makes them easy to adopt, easy to learn or in any
+ other way attractive. <xref
+ linkend="table-technologies-comparison" /> reviews the
+ introduced technologies from <xref linkend="technologies" /> and the
+ described mandatory features here.
+ </para>
</sect1>
Modified:
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml Thu
Aug 25 14:22:26 2005
(at)(at) -1,8 +1,6 (at)(at)
<?xml version='1.0' encoding="UTF-8" ?>
<para>
- <table frame='all' orient="land" id='table-technologies-comparison'>
-
<indexterm>
<primary>Zope</primary>
</indexterm>
(at)(at) -63,10 +61,11 (at)(at)
<indexterm>
<primary>ActionScript</primary>
</indexterm>
+ <table frame='all' orient="land" id='table-technologies-comparison'>
<title>
- A comparison between different technologies mentioned in
- <xref linkend="technologies" />.
+ A review between different technologies mentioned in <xref
+ linkend="technologies" />.
</title>
<tgroup cols='7' colsep='1' rowsep='1'>
<colspec colname='empty' align='left' />
(at)(at) -95,12 +94,27 (at)(at)
</entry>
<entry>
<emphasis role='bold'>
- Python Bindings
+ Python Bindings<footnote>
+ <para>
+ Python bindings mean in this context, that a piece of
+ software provides an interface or a library, which
+ provides native access by a different programming
+ language to the programs internal routines.
+ </para>
+ </footnote>
</emphasis>
</entry>
<entry>
<emphasis role="bold">
- Learnability
+ Learnability<footnote>
+ <para>
+ How fast would a developer be able to learn this
+ technology? <quote>+++</quote> would be really
easy to
+ learn because it's widely in use and rundimentary
+ known, whereas <quote>+</quote> means, that the
+ technology is very hard to learn.
+ </para>
+ </footnote>
</emphasis>
</entry>
<entry>
Modified:
misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-editors.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-editors.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-editors.xml Thu
Aug 25 14:22:26 2005
(at)(at) -6,10 +6,10 (at)(at)
Comparison between existing graphical workflow editors.
</title>
<tgroup cols='5' colsep='1' rowsep='1'>
- <colspec colname='empty' align='justify' />
- <colspec colname='zms' align='justify'/>
- <colspec colname='jawe' align='justify'/>
- <colspec colname="yawl" align="justify" />
+ <colspec colname='empty' align='justify' colwidth="3cm" />
+ <colspec colname='zms' align='justify' colwidth="4cm"/>
+ <colspec colname='jawe' align='justify' colwidth="4cm"/>
+ <colspec colname="yawl" align="justify" colwidth="4cm"/>
<thead>
<row>
<entry></entry>
(at)(at) -69,7 +69,7 (at)(at)
</entry>
<entry>
<link linkend='glossary-jre'>JRE</link> supported
- platforms<footnote> <para>
+ platforms<footnote id="jredep"> <para>
The JRE is developed and maintained by Sun
Microssystems. Other implementations by third party
projects are available as well. In that respect, the
(at)(at) -78,11 +78,7 (at)(at)
</footnote>
</entry>
<entry>
- JRE supported platforms<footnote>
- <para>
- ebd.
- </para>
- </footnote>
+ JRE supported platforms<footnoteref linkend="jredep" />
</entry>
</row>
<row>
Modified:
misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-engines.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-engines.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-workflow-engines.xml Thu
Aug 25 14:22:26 2005
(at)(at) -1,117 +1,17 (at)(at)
<?xml version="1.0" encoding="UTF-8" ?>
<para>
-<table orient="land" frame='all' id='table-workflow-engines' lang="de">
- <title lang="de">
- Vergleich zwischen den zur Verfügung stehenden Workflow Engines
- in Zope und AlphaFlow.
- </title>
- <tgroup cols='5' colsep='1' rowsep='1'>
- <colspec colname='empty' align='justify' />
- <colspec colname='dcworkflow' align='justify' />
- <colspec colname='openflow' align='justify' />
- <colspec colname='alphaflow' align='justify'/>
- <colspec colname='enhydra' align='justify' />
- <thead>
- <row>
- <entry></entry>
- <entry><emphasis role='bold'>DC
Workflow</emphasis></entry>
- <entry><emphasis
role='bold'>OpenFlow</emphasis></entry>
- <entry><emphasis
role='bold'>AlphaFlow</emphasis></entry>
- <entry><emphasis role='bold'>Enhydra
Shark</emphasis></entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Hersteller/Anbieter</entry>
- <entry>Zope Corporation, Fredericksburg, USA</entry>
- <entry>Icube srl, Pisa, Italien</entry>
- <entry role='html'>gocept GmbH und Co KG., Köthen,
Deutschland</entry>
- <entry role='tex'>
- <latex><![CDATA[gocept GmbH \& Co KG, Köthen,
Deutschland ]]></latex>
- </entry>
- <entry>Together Teamlösungen GmbH, Wien,
Österreich</entry>
- </row>
- <row>
- <entry>Webseite</entry>
- <entry>
- <ulink url='http://www.zope.com'>http://www.zope.com</ulink>
- </entry>
- <entry>
- <ulink url='http://www.openflow.it'>http://www.openflow.it</ulink>
- </entry>
- <entry>
- <ulink url='http://www.gocept.com'>http://www.gocept.com</ulink>
- </entry>
- <entry>
- <ulink url='http://shark.objectweb.org/'>http://shark.objectweb.org/</ulink>
- </entry>
- </row>
- <row>
- <entry>Lizenz</entry>
- <entry>ZPL<footnote>
- <para>Die ZPL ist eine BSD Lizenz</para>
- </footnote>
- </entry>
- <entry>GPL</entry>
-
<entry>ZPL<footnote><para>Ebd.</para></footnote></entry>
- <entry>LGPL</entry>
- </row>
- <row>
- <entry>Modellierung paralleler Aktivitäten</entry>
- <entry>nein</entry>
- <entry>nein</entry>
- <entry>ja</entry>
- <entry>?</entry>
- </row>
- <row>
- <entry>
- Import/Export<footnote>
- <para>
- Da Zope-Objekte per se in Binär- als auch XML-Format
- exportierbar sind, könnte dieser Vergleich immer mit
- <quote>Ja</quote> beantwortet werden. Jedoch ist es
- bei dem Export via Zope nicht mehr möglich die
- definierten Workflows zu bearbeiten. Damit sei hier
- der Export in ein Textformat gemeint, in dem ein
- späteres bearbeiten des Workflows weiterhin möglich
- ist.
- </para>
- </footnote> der definiierten Workflows
- </entry>
- <entry>ja/ja</entry>
- <entry>ja/ja</entry>
- <entry>ja/nein<!-- XXX --></entry>
- <entry>ja/ja</entry>
- </row>
- <row>
- <entry>XPDL Konformität</entry>
- <entry>nein</entry>
- <entry>ja</entry>
- <entry>nein</entry>
- <entry>ja</entry>
- </row>
- <row>
- <entry>grafischer Editor</entry>
- <entry>nein</entry>
- <entry>nein</entry>
- <entry>nein</entry>
- <entry>ja</entry>
- </row>
- </tbody>
- </tgroup>
-</table>
<table frame='all' id='table-workflow-engines' lang="en">
<title lang="en">
Comparison between existing Workflowengines for Zope (incl.
AlphaFlow).
</title>
<tgroup cols='5' colsep='1' rowsep='1'>
- <colspec colname='empty' align='justify' />
- <colspec colname='dcworkflow' align='justify' />
- <colspec colname='openflow' align='justify' />
- <colspec colname='alphaflow' align='justify'/>
- <colspec colname='enhydra' align='justify' />
+ <colspec colname='empty' align='justify' colwidth="4cm"/>
+ <colspec colname='dcworkflow' align='justify' colwidth="3cm" />
+ <colspec colname='openflow' align='justify' colwidth="3cm"/>
+ <colspec colname='alphaflow' align='justify' colwidth="3cm" />
+ <colspec colname='enhydra' align='justify' colwidth="3cm"/>
<thead>
<row>
<entry></entry>
Modified: misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl (original)
+++ misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl Thu Aug 25
14:22:26 2005
(at)(at) -13,7 +13,7 (at)(at)
<xsl:param name="section.autolabel" select="1" />
<xsl:param
name="latex.titlepage.file">../../stylesheets/titlepage.tex</xsl:param>
<xsl:param name="latex.document.font">palatino</xsl:param>
- <xsl:param name="latex.use.tabularx">1</xsl:param>
+ <xsl:param name="latex.use.tabularx">0</xsl:param>
<xsl:param name="latex.use.ltxtable">0</xsl:param>
<xsl:param name="latex.use.overpic">1</xsl:param>
<xsl:param name="latex.documentclass">scrreprt</xsl:param>
|
SVN: r3312 - in misc/trunk/WorkflowEditor/docbook: . src/alphaflow src/requirements
Roman Joost <rj(at)gocept.com> |
2005-08-26 14:18:54 |
[ FULL ]
|
Author: roman
Date: Fri Aug 26 14:19:30 2005
New Revision: 3312
Modified:
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/alphaflow/activities.xml
misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml
Log:
2005-08-26 Roman Joost <rj(at)gocept.com>
* src/requirements/considered-problems.xml
* src/alphaflow/activities.xml
* src/alphaflow/process-state.xml: fixed remaining spelling
errors
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Fri Aug 26 14:19:30 2005
(at)(at) -1,3 +1,10 (at)(at)
+2005-08-26 Roman Joost <rj(at)gocept.com>
+
+ * src/requirements/considered-problems.xml
+ * src/alphaflow/activities.xml
+ * src/alphaflow/process-state.xml: fixed remaining spelling
+ errors
+
2005-08-25 Roman Joost <rj(at)gocept.com>
*.: set a ignore property
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/activities.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/alphaflow/activities.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/activities.xml Fri Aug 26
14:19:30 2005
(at)(at) -27,19 +27,14 (at)(at)
</figure>
<para>
- <!--Despite the fact that the term <quote>activity</quote>
might be
- missleading in some cases<footnote>
- <para>
- see therefore <xref linkend="term-activity" />
- </para>
- </footnote>, AlphaFlow uses activities to emphazise
- <remark> emphasize what?</remark> -->
AlphaFlow has more than ten pre-defined activities. It is possible
- to model nearly every workflow the user wants. The base classes
- are <classname>BaseActivity</classname>,
<classname>BaseAutomaticActivity</classname>,
<classname>BaseTalesActivity</classname> and
+ to model nearly every workflow the user wants. The base classes are
+ <classname>BaseActivity</classname>,
+ <classname>BaseAutomaticActivity</classname>,
+ <classname>BaseTalesActivity</classname> and
<classname>BaseAssignableActivity</classname>. I'll elaborate
only
the three most relevant of them. This is important to understand,
- because they're the fundamentals of the activities I'm speaking
+ because they're these fundamentals of any other activities I'm speaking
about in the next pages.
</para>
(at)(at) -117,7 +112,7 (at)(at)
</sect2>
- <sect2>
+ <sect2 id="baseautomaticactivity">
<title>BaseAutomaticActivity</title>
<indexterm>
<primary>AlphaFlow</primary>
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml Fri Aug
26 14:19:30 2005
(at)(at) -10,7 +10,15 (at)(at)
<para>
As I already mentioned in <xref linkend="alphaflow-what-is" />, a
process instance is a characteristic type of the process definition.
- The instances can change into one of the following states:
+ There can be several activities defined for a process startup. These
+ activites are defined by the
+ <parameter>startActivity</parameter><footnote>
+ <para>
+ cp. <xref linkend="alarm_review" />
+ </para>
+ </footnote>
+ and executed by the order of the given
<paramter>id</paramter>s on
+ start. The instances can change into one of the following states:
</para>
<variablelist>
Modified:
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml Fri
Aug 26 14:19:30 2005
(at)(at) -12,26 +12,26 (at)(at)
During the requirements analysation, I was considering two problem
fields I have to deal with for the workflow editor: visualization of
the process definition and the user interface. The technologies I
- discussed in <xref linkend="technologies" /> should be able to
- provide the functionality to solve this problems technically. There
- are several individual problems for the visualization and user
- interface part. I'll introduce them in the following with their
- problem and list possible solutions if there were any considered at
- that point. Note though, that I mean the graphical representation of
- the activity in the user interface with the used term
- <emphasis>activity</emphasis> in the following list.
+ discussed in <xref linkend="technologies" /> provide a basis to
+ tackle the problem fields down to a minimum. There are several
+ individual problems for the visualization and user interface part.
+ The following list introduces each individual problems facing when
+ building user interfaces with a possible solution came to my mind.
+ It's worth to note, that the term <quote>activity</quote>
describes
+ the visualisation of an AlphaFlow activity.
</para>
<variablelist>
<varlistentry>
<term>
- Howto distinguish between myriads of
<emphasis>activities</emphasis>?
+ What will be the best approach to distinguish between myriads of
+ activities?
</term>
<listitem>
<para>
- The workflow definition is visualized as a graph. The more
- activities the graph contains the less overviewable is it. The
+ The workflow definition will be visualised as a graph. The more
+ activities the graph contains the less overviewable it is. The
goal should be, that the rendered graph is overviewable as
possible. To achieve that goal, I considered two possible
solutions:
(at)(at) -45,7 +45,7 (at)(at)
<listitem>
<para>
using icons, colors or different forms to distinguish
- <emphasis>activities</emphasis>
+ between activities.
</para>
</listitem>
</itemizedlist>
(at)(at) -54,16 +54,16 (at)(at)
</varlistentry>
<varlistentry>
- <term>Who positions
<emphasis>activities?</emphasis></term>
+ <term>Who positions activities?</term>
<listitem>
<para>
- The position of <emphasis>activities</emphasis> in the
user
+ The position of activities in the user
interface is important for orientation. Either the user
- places the <emphasis>activities</emphasis> manually or
the
+ places the activities manually or the
system does this for him automatically. The latter approach
would avoid broken references and the better usage of the
layout machinery, but could also lead into moving <!-- XXX -->
- <emphasis>activities</emphasis> after the graph is
rerendered.
+ activities after the graph is rerendered.
</para>
</listitem>
</varlistentry>
(at)(at) -71,52 +71,55 (at)(at)
<varlistentry>
<term>
How to visualize the association between
- <emphasis>activities</emphasis>?
+ activities?
</term>
<listitem>
<para>
- An association between two activities means, that one
- <emphasis>activity</emphasis> is the continue activity
of
- another <emphasis>activity</emphasis>. This can be
easily
- visualized by arrows in the direction to the continue
- activity. So, basically, the user tells the system which
- continue activities an <emphasis>activity</emphasis>
have and
- the problematic part is both the interaction and visualization
- with the editor here. Should the user be able to draw a
- connection between activities by himself or should the
- layouting system take care of visualizing associated
- <emphasis>activities</emphasis>.
+ An association between two activities means, that one activity
+ is the
<parameter>continue_activity</parameter><footnote>
+ <para>cp. <xref linkend="baseautomaticactivity"
/></para>
+ </footnote> of another activity. This can be easily visualized
+ by arrows in the direction to the successeding activity. So,
+ basically, the user enters a list of
+ <parameter>id</parameter>s for successeding activities.
The
+ problematic part is both the interaction and visualization
+ with the editor here. I need to decide wether the user draws
+ connections between activities or the backend system takes
+ care of the visualisation.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>How to define Startactivities?</term>
+ <term>How to define start activities?</term>
<listitem>
<para>
- Startactivities are defined globally for each workflow
- definition and executed on start of executing the workflow
- definition<footnote>
+ Activities<footnote>
<para>
- see <xref linkend="alphaflow-pdl" /> for more information
+ cp. <xref linkend="alphaflow-process-state" />
</para>
- </footnote>. The order of the Startactivities is substantial
+ </footnote> which are executed on process instance start are
+ defined globally for each workflow definition and executed on
+ start of executing the workflow definition<footnote>
+ <para>
+ cp. <xref linkend="alphaflow-pdl" />
+ </para>
+ </footnote>. The order of the start activities is substantial
for the AlphaFlow process definition.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>How can <emphasis>activities</emphasis> be
deleted?</term>
+ <term>How can activities be deleted?</term>
<listitem>
<para>
- If the user want to delete an
<emphasis>activity</emphasis>,
- what will happen with other associated activities? Should the editor
- care about them automatically (e.g. delete the reference
- representation) or should the user do this manually? If the
- user have to care about every reference, the effort to remove
- a well connected <emphasis>activity</emphasis> in the
process
- definition will be enormous.
+ If the user want to delete an activity, what will happen with
+ other associated activities? Should the editor care about them
+ automatically (e.g. delete the reference representation) or
+ should the user do this manually? If the user have to care
+ about every reference pointing to the deleted activity, the
+ effort of removing each reference will be enormous.
</para>
</listitem>
</varlistentry>
(at)(at) -126,38 +129,39 (at)(at)
<listitem>
<para>
If the user creates an assocition by hand between activities
- (e.g. by drawing arrows) should the user interface provide
- some sort of help by e.g. help lines?
+ (e.g. by drawing arrows), how can the user interface provide
+ help?
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
- How will the UI behave for adding reflexive transitions?
+ Reflexive transitions
</term>
<listitem>
<para>
- If the user models a reflexive transition for an
- <emphasis>activity</emphasis><footnote>
+ will be quite a chellange for the UI. If there are any reflexive
+ transitions<footnote>
<para>
The <emphasis>activity</emphasis> has its own id as
the
continue activity.
</para>
- </footnote> how will the user interface respond to him and how
- will this be visualized during editing?
+ </footnote>
+ considered in the process definition, how can the
+ UI provide a helpful way to add and edit them.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>How to visualize a currently edited
<emphasis>activity</emphasis>?</term>
+ <term>How to visualize a currently edited activity?</term>
<listitem>
<para>
The user interface should give some sort of a feedback to the
- user that he currently edits an
<emphasis>activity</emphasis>.
+ user that he currently edits an activity.
This can be done by emphasizing this
- <emphasis>activity</emphasis> with colors or masking all
other
+ activity with colors or masking all other
non-relevant graph data.
</para>
</listitem>
(at)(at) -168,7 +172,7 (at)(at)
<para>
Unfortunately, each solution above have his own disadvantage. For
example, using icons, different forms or colors wouldn't help to
- achieve and overviewable graph if the number of activities increases
+ achieve an overviewable graph if the number of activities increases
significantly. To gain the best effect and to fulfill the goals a
combination of various solutions is needed.
</para>
|
SVN: r3314 - in misc/trunk/WorkflowEditor/docbook: . src src/bibliography src/usability
Roman Joost <rj(at)gocept.com> |
2005-08-26 15:13:21 |
[ FULL ]
|
Author: roman
Date: Fri Aug 26 15:13:49 2005
New Revision: 3314
Added:
misc/trunk/WorkflowEditor/docbook/src/bibliography/
misc/trunk/WorkflowEditor/docbook/src/bibliography/bibliography.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/misc.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/softwaredesign.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/workflow.xml
Removed:
misc/trunk/WorkflowEditor/docbook/src/bibliography.xml
Modified:
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/diplom.xml
misc/trunk/WorkflowEditor/docbook/src/usability/engineering.xml
Log:
2005-08-26 Roman Joost <rj(at)gocept.com>
* src/bibliography.xml: moved to bibliography dir
* src/diplom.xml
* src/usability/engineering.xml
* src/bibliography
* src/bibliography/technologies.xml
* src/bibliography/softwaredesign.xml
* src/bibliography/usability.xml
* src/bibliography/workflow.xml
* src/bibliography/bibliography.xml
* src/bibliography/misc.xml: splitted bibliography into
seperate pieces and ordered them by more subjects
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Fri Aug 26 15:13:49 2005
(at)(at) -1,4 +1,19 (at)(at)
2005-08-26 Roman Joost <rj(at)gocept.com>
+
+ * src/bibliography.xml: moved to bibliography dir
+
+ * src/diplom.xml
+ * src/usability/engineering.xml
+ * src/bibliography
+ * src/bibliography/technologies.xml
+ * src/bibliography/softwaredesign.xml
+ * src/bibliography/usability.xml
+ * src/bibliography/workflow.xml
+ * src/bibliography/bibliography.xml
+ * src/bibliography/misc.xml: splitted bibliography into
+ seperate pieces and ordered them by more subjects
+
+2005-08-26 Roman Joost <rj(at)gocept.com>
* src/requirements/considered-problems.xml
* src/alphaflow/activities.xml
Added: misc/trunk/WorkflowEditor/docbook/src/bibliography/bibliography.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/bibliography.xml Fri Aug
26 15:13:49 2005
(at)(at) -0,0 +1,20 (at)(at)
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<bibliography id="bibliography" xmlns:xi="http://www.w3.org/2001/XInclude">
+ <title lang="de">Bibliographie</title>
+ <title lang="en">Bibliography</title>
+
+ <indexterm>
+ <primary lang="de">Bibliographie</primary>
+ <primary lang="en">Bibliography</primary>
+ </indexterm>
+
+
+ <xi:include href="misc.xml" />
+ <xi:include href="softwaredesign.xml" />
+ <xi:include href="technologies.xml" />
+ <xi:include href="usability.xml" />
+ <xi:include href="workflow.xml" />
+
+
+</bibliography>
Added: misc/trunk/WorkflowEditor/docbook/src/bibliography/misc.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/misc.xml Fri Aug 26
15:13:49 2005
(at)(at) -0,0 +1,108 (at)(at)
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<bibliodiv>
+ <title lang='en'>Miscellaneous</title>
+
+ <biblioentry>
+ <abbrev>Wikipedia05</abbrev>
+ <author>
+ <othername>Wikipedia.org</othername>
+ </author>
+ <copyright>
+ <year>2001-2005</year>
+ <holder>Wikipedia</holder>
+ </copyright>
+ <title>
+ Wikipedia, The Free Encyclopedia.
+ </title>
+ <releaseinfo>
+ <ulink
+ url="http://www.wikipedia.org"
+ /> [accessed 2005-04-18]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>DBGuide04</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Norman</firstname>
+ <surname>Walsh</surname>
+ </author>
+ <author>
+ <firstname>Leonard</firstname>
+ <surname>Müller</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>2004</year>
+ <holder>O'Reilly & Associates, Inc.</holder>
+ </copyright>
+ <title>Docbook: The Definitive Guide</title>
+ <isbn>1-565-92580-7</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>XSLGuide03</abbrev>
+ <author>
+ <firstname>Bob</firstname>
+ <surname>Stayton</surname>
+ </author>
+ <copyright>
+ <year>2003</year>
+ <holder>Sagehill Enterprises</holder>
+ </copyright>
+ <title>DocBook XSL: The Complete Guide</title>
+ <subtitle>Second Edition</subtitle>
+ <isbn>0-974-15211-0</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Hathaway01</abbrev>
+ <author>
+ <firstname>Shane</firstname>
+ <surname>Hathaway</surname>
+ </author>
+ <copyright>
+ <year>2001</year>
+ <holder>Shane Hathaway</holder>
+ </copyright>
+ <title>DCWorkflow Introduction</title>
+ <releaseinfo>
+ <ulink url="http://hathawaymix.org/Writings/DCWorkflow_docs"
/>
+ [accessed 2005-03-14]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Latteier04</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Amos</firstname>
+ <surname>Latteier</surname>
+ </author>
+ <author>
+ <firstname>Michel</firstname>
+ <surname>Pelletier</surname>
+ </author>
+ <author>
+ <firstname>Chris</firstname>
+ <surname>McDonough</surname>
+ </author>
+ <author>
+ <firstname>Peter</firstname>
+ <surname>Sabaini</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>2004</year>
+ <holder>Zope Corporation</holder>
+ </copyright>
+ <title>The Zope Book (2.6 edition)</title>
+ <releaseinfo>
+ <ulink url="http://www.zope.org/Documentation/Books/ZopeBook"
/>
+ (PDF version)
+ [accessed 2005-15-03]
+ </releaseinfo>
+ </biblioentry>
+</bibliodiv>
Added: misc/trunk/WorkflowEditor/docbook/src/bibliography/softwaredesign.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/softwaredesign.xml Fri
Aug 26 15:13:49 2005
(at)(at) -0,0 +1,68 (at)(at)
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<bibliodiv>
+ <title>Software Design</title>
+
+ <biblioentry>
+ <abbrev>Riehle96</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Heinz</firstname>
+ <surname>Züllighoven</surname>
+ </author>
+ <author>
+ <firstname>Dirk</firstname>
+ <surname>Riehle</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>1996</year>
+ <holder>UBILAB and University of Hamburg</holder>
+ </copyright>
+ <title>Understanding and Using Patterns in Software
Development</title>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Gamma96</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Erich</firstname>
+ <surname>Gamma</surname>
+ </author>
+ <author>
+ <firstname>Richard</firstname>
+ <surname>Helm</surname>
+ </author>
+ <author>
+ <firstname>Ralph</firstname>
+ <surname>Johnson</surname>
+ </author>
+ <author>
+ <firstname>John</firstname>
+ <surname>Vlissides</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>1995</year>
+ <holder>Addison-Wesley Publishing Company</holder>
+ </copyright>
+ <title>Design Patterns</title>
+ <isbn>0-201-63361-2</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Balzert01</abbrev>
+
+ <author>
+ <firstname>Helmut</firstname>
+ <surname>Balzert</surname>
+ </author>
+ <copyright>
+ <year>2001</year>
+ <holder>Spektrum Akademischer Verlag GmbH, Heidelberg,
Berlin</holder>
+ </copyright>
+ <title>Lehrbuch der Software Technik</title>
+ <isbn>3-8274-0480-0</isbn>
+ </biblioentry>
+
+</bibliodiv>
Added: misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml Fri Aug
26 15:13:49 2005
(at)(at) -0,0 +1,42 (at)(at)
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<bibliodiv>
+ <title>Technologies</title>
+
+ <biblioentry>
+ <abbrev>Cagle05</abbrev>
+ <author>
+ <firstname>Kurt</firstname>
+ <surname>Cagle</surname>
+ </author>
+ <copyright>
+ <year>2005</year>
+ <holder>Kurt Cagle</holder>
+ </copyright>
+ <title>Understanding XML (transcript)</title>
+ <releaseinfo>
+ <ulink
+ url="http://www.understandingxml.com/archives/2005/08/the_future_of_s.html"
+ /> [accessed 2005-08-18]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Gd05</abbrev>
+ <author>
+ <othername>graphdrawing.org</othername>
+ </author>
+ <copyright>
+ <year>2004-2005</year>
+ <holder>graphdrawing.org</holder>
+ </copyright>
+ <title>
+ The Wiki for Open Problems in Graph Drawing.
+ </title>
+ <releaseinfo>
+ <ulink
+ url="http://problems.graphdrawing.org/index.php/Main_Page"
+ /> [accessed 2005-03-29]
+ </releaseinfo>
+ </biblioentry>
+</bibliodiv>
Added: misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml Fri Aug 26
15:13:49 2005
(at)(at) -0,0 +1,199 (at)(at)
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<bibliodiv>
+ <title>Usability, User Interface Design</title>
+
+
+ <biblioentry>
+ <abbrev>Duesterloh05</abbrev>
+ <author>
+ <firstname>Karsten</firstname>
+ <surname>Düsterloh</surname>
+ </author>
+ <copyright>
+ <year>2005</year>
+ <holder>Heise Zeitschriften Verlag GmbH & Co.
KG</holder>
+ </copyright>
+ <title>Schachtelsatz</title>
+ <subtitle>XUL-Tutorial 1: Basiselemente der
Browsererweiterung</subtitle>
+ <releaseinfo>
+ Published by <emphasis>iX – Magazin für professionelle
+ Informationstechnik</emphasis>, Issue 7/2005
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Beyer98</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Hugh</firstname>
+ <surname>Beyer</surname>
+ </author>
+ <author>
+ <firstname>Karen</firstname>
+ <surname>Holtzblatt</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>1998</year>
+ <holder>Academic Press</holder>
+ </copyright>
+ <title>
+ Contextual Design – Defining Customer-Centered Systems
+ </title>
+ <isbn>1-55860-411-1</isbn>
+ </biblioentry>
+ <biblioentry>
+ <abbrev>Gnome04</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Calum</firstname>
+ <surname>Benson</surname>
+ </author>
+ <author>
+ <firstname>Adam</firstname>
+ <surname>Elman</surname>
+ </author>
+ <author>
+ <firstname>Seth</firstname>
+ <surname>Nickell</surname>
+ </author>
+ <author>
+ <firstname>Colin</firstname>
+ <surname>Z Robertson</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>2004</year>
+ <holder>The GNOME Usability Project</holder>
+ </copyright>
+ <title>GNOME Human Interface Guidelines 2.0</title>
+ <releaseinfo>
+ <ulink url="http://developer.gnome.org/projects/gup/hig/2.0/"
/>
+ [accessed 2005-08-17]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Raskin02</abbrev>
+ <author>
+ <firstname>Jef</firstname>
+ <surname>Raskin</surname>
+ </author>
+ <copyright>
+ <year>2002</year>
+ <holder>Jef Raskin</holder>
+ </copyright>
+ <title>A nearly one page summary of design rules</title>
+ <releaseinfo>
+ <ulink
+ url="http://www.mprove.de/script/02/raskin/designrules.html"
/>
+ [accessed 2005-04-11]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>KDE05</abbrev>
+ <author>
+ <firstname>Ellen</firstname>
+ <surname>Reitmayr</surname>
+ </author>
+ <copyright>
+ <year>2005</year>
+ <holder>KDE project</holder>
+ </copyright>
+ <title>The KDE Guidelines Collection</title>
+ <releaseinfo>
+ <ulink
+ url="http://www.kde.org/areas/guidelines/html/"
+ />, <ulink
+ url="http://developer.kde.org/documentation/standards/kde/style/basics/index.html"
+ /> [accessed 2005-08-17]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Apple05</abbrev>
+ <author>
+ <othername>Apple Computer</othername>
+ </author>
+ <copyright>
+ <year>1992,2001-2003,2005</year>
+ <holder>Apple Computer Inc.</holder>
+ </copyright>
+ <title>Apple Human Interface Guidelines</title>
+ <releaseinfo>
+ <ulink
+ url="http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/OSXHIGuidelines.pdf"
+ /> (PDF version) [accessed 2005-08-17]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>UsabNet03</abbrev>
+ <author>
+ <firstname>Bevan</firstname>
+ <surname>Nigel</surname>
+ </author>
+ <copyright>
+ <year>2003</year>
+ <holder>UsabilityNet</holder>
+ </copyright>
+ <title> Methods table</title>
+ <releaseinfo>
+ <ulink url="http://www.usabilitynet.org/tools/methods.htm"
/>
+ [accessed 2005-04-26]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Horn03</abbrev>
+ <author>
+ <firstname>James</firstname>
+ <surname>Horn</surname>
+ </author>
+ <copyright>
+ <year>1996-2003</year>
+ <holder>James Horn</holder>
+ </copyright>
+ <title>The Usability Methods Toolbox</title>
+ <releaseinfo>
+ <ulink url="http://jthom.best.vwh.net/usability/usable.htm"
/>
+ [accessed 2005-04-13]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Nielsen93</abbrev>
+ <author>
+ <firstname>Jakob</firstname>
+ <surname>Nielsen</surname>
+ </author>
+ <copyright>
+ <year>1993</year>
+ <holder>Academic Press.</holder>
+ </copyright>
+ <title>Usability Engineering</title>
+ <isbn>0-12-518406-9</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>id05</abbrev>
+ <author>
+ <firstname>Mads</firstname>
+ <surname>Soegaard</surname>
+ </author>
+ <copyright>
+ <year>2003 - 2005</year>
+ <holder>Mads Soegaard</holder>
+ </copyright>
+ <title>
+ Interaction-Design.org–HCI, Information Architecture, User
+ Experience and more
+ </title>
+ <releaseinfo>
+ <ulink url="http://www.interaction-design.org"
/> [accessed
+ 2005-08-26]
+ </releaseinfo>
+ </biblioentry>
+</bibliodiv>
Added: misc/trunk/WorkflowEditor/docbook/src/bibliography/workflow.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/workflow.xml Fri Aug 26
15:13:49 2005
(at)(at) -0,0 +1,230 (at)(at)
+<?xml version="1.0" encoding="UTF-8" ?>
+
+<bibliodiv>
+ <title>Workflow</title>
+
+ <biblioentry>
+ <abbrev>Fischer01</abbrev>
+ <author>
+ <firstname>Lanya</firstname>
+ <surname>Fischer</surname>
+ </author>
+ <copyright>
+ <year>2001</year>
+ <holder>Future Strategies Inc.</holder>
+ </copyright>
+ <title>The Workflow Handbook 2001</title>
+ <isbn>0-9703-5096-1</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Aalst03</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>W.M.P</firstname>
+ <surname>van der Aalst</surname>
+ </author>
+ <author>
+ <firstname>A.H.M</firstname>
+ <surname>ter Hofstede</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>2003</year>
+ <holder>Queensland University of Technology</holder>
+ </copyright>
+ <title>YAWL: Yet Another Workflow Language</title>
+ <releaseinfo>
+ <ulink url="http://www.yawl.fit.qut.edu.au/yawldocs/yawl.pdf"
/>
+ (PDF version) [accessed 2005-07-05]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Stolp99</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Bernd</firstname>
+ <surname>Müller</surname>
+ </author>
+ <author>
+ <firstname>Patrick</firstname>
+ <surname>Stolp</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>1999</year>
+ <holder>Springer-Verlag Berlin Heidelberg</holder>
+ </copyright>
+ <title>Workflow-Managment in der industriellen Praxis</title>
+ <subtitle>Vom Buzzword zum High-Tech-Instrument</subtitle>
+ <isbn>3-540-54662-0</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Lehmann99</abbrev>
+ <author>
+ <honorific>Dr</honorific>
+ <firstname>Frank R.</firstname>
+ <surname>Lehmann</surname>
+ </author>
+ <copyright>
+ <year>1999</year>
+ <holder>B.G. Teubner Stuttgart Leipzig</holder>
+ </copyright>
+ <title>Fachlicher Entwurf von
Workflow-Managment-Anwendungen</title>
+ <isbn>3-519-00258-2</isbn>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Kiep02</abbrev>
+ <author>
+ <firstname>Bartosz</firstname>
+ <surname>Kiepuszewski</surname>
+ </author>
+ <copyright>
+ <year>2002</year>
+ <holder>Centre for Cooperative Information Systems</holder>
+ </copyright>
+ <title>
+ Expressiveness and Suitability of Languages for Control Flow
+ Modelling in Workflows.
+ </title>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Aalst02</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>W.M.P.</firstname>
+ <surname>van der Aalst</surname>
+ </author>
+ <author>
+ <firstname>A.H.M</firstname>
+ <surname>ter Hofstede</surname>
+ </author>
+ <author>
+ <firstname>B.</firstname>
+ <surname>Kiepuszewski</surname>
+ </author>
+ <author>
+ <firstname>A.P.</firstname>
+ <surname>Barros</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>2002</year>
+ <holder>Queensland University of Technology</holder>
+ </copyright>
+ <title>Workflow Patterns</title>
+ <releaseinfo>
+ <ulink
+ url='http://tmitwww.tm.tue.nl/research/patterns/report.htm'
/>
+ [accessed 2005-02-13]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Mettraux04</abbrev>
+ <author>
+ <firstname>John</firstname>
+ <surname>Mettraux</surname>
+ </author>
+ <copyright>
+ <year>2004</year>
+ <holder>John Mettraux</holder>
+ </copyright>
+ <title>OpenWFE book</title>
+ <releaseinfo>
+ <ulink url="http://www.openwfe.org/docbook/build/index.html"
/>
+ [accessed 2005-03-14]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Baeyens04</abbrev>
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Baeyens</surname>
+ </author>
+ <copyright>
+ <year>2004</year>
+ <holder>Tom Baeyens</holder>
+ </copyright>
+ <title>The state of workflow</title>
+ <releaseinfo>
+ <ulink url="http://www.jbpm.org/state.of.workflow.html"
/>
+ [accessed 2005-02-20]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Muehlen03</abbrev>
+ <author>
+ <firstname>Michael</firstname>
+ <surname>zur Muehlen</surname>
+ </author>
+ <copyright>
+ <year>2003</year>
+ <holder>Michael zur Muehlen</holder>
+ </copyright>
+ <title>Process managment standards overview</title>
+ <releaseinfo>
+ <ulink
+ url="http://www.wfmc.org/standards/docs/Process_Management_Standards_files/frame.htm"
+ /> [accessed 2005-02-22]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Guillaume02</abbrev>
+ <author>
+ <firstname>Florent</firstname>
+ <surname>Guillaume</surname>
+ </author>
+ <copyright>
+ <year>2002</year>
+ <holder>Florent Gauillaume</holder>
+ </copyright>
+ <title>Trying to unify Entity-based and Activity-based
workflows</title>
+ <releaseinfo>
+ <ulink
+ url="http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/TryingToUnifiyWorkflowConcepts"
+ /> [accessed 2005-03-18]
+ </releaseinfo>
+ </biblioentry>
+ <biblioentry>
+ <abbrev>Wfmc05</abbrev>
+ <author>
+ <othername>Workflow Managment Coalition</othername>
+ </author>
+ <copyright>
+ <year>2005</year>
+ <holder>Workflow Managment Coalition</holder>
+ </copyright>
+ <title>
+ Workflow Managment Coalition Homepage
+ </title>
+ <releaseinfo>
+ <ulink url='http://www.wfmc.org'
/> [accessed 2005-03-25]
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>WfmcGlos99</abbrev>
+ <author>
+ <othername>Workflow Managment Coalition</othername>
+ </author>
+ <copyright>
+ <year>1999</year>
+ <holder>Workflow Managment Coalition</holder>
+ </copyright>
+ <title>
+ Terminology and Glossary
+ </title>
+ <releaseinfo>
+ <ulink url='http://www.wfmc.org/standards/standards.htm'
/>
+ [accessed 2005-03-25]
+ </releaseinfo>
+ </biblioentry>
+</bibliodiv>
Modified: misc/trunk/WorkflowEditor/docbook/src/diplom.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/diplom.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/diplom.xml Fri Aug 26 15:13:49 2005
(at)(at) -120,7 +120,7 (at)(at)
<xi:include href="appendix-screenshots.xml" />
<xi:include href="tables/appendix-tables.xml" />
<xi:include href="glossary/glossary.xml" />
- <xi:include href="bibliography.xml" />
+ <xi:include href="bibliography/bibliography.xml" />
<index />
</book>
Modified: misc/trunk/WorkflowEditor/docbook/src/usability/engineering.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/usability/engineering.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/usability/engineering.xml Fri Aug 26
15:13:49 2005
(at)(at) -10,7 +10,7 (at)(at)
<para>
There are various usability methods available for application
- development. <citation>UsabilityNet03</citation>
+ development. <citation>UsabNet03</citation>
offers a lot of usability methods outlined and summarized nicely.
According to the listed methods, I used filters to sort out the
necessary methods according to my resources and usability
|
SVN: r3324 - in misc/trunk/WorkflowEditor/docbook: . src/introduction src/tables src/technologies src/usability stylesheets
Roman Joost <rj(at)gocept.com> |
2005-08-29 14:10:06 |
[ FULL ]
|
Author: roman
Date: Mon Aug 29 14:11:11 2005
New Revision: 3324
Modified:
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-flash.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-png.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/animation-interaction.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/fileformats.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/frontend.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/proc-definition.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/renderingpipeline.xml
misc/trunk/WorkflowEditor/docbook/src/usability/context-of-use.xml
misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl
Log:
2005-08-29 Roman Joost <rj(at)gocept.com>
* src/introduction/workflow-types.xml
* src/technologies/frameworks.xml
* src/technologies/renderingpipeline.xml
* src/technologies/graph-components.xml
* src/technologies/proc-definition.xml
* src/technologies/fileformats.xml
* src/technologies/intro.xml
* src/technologies/animation-interaction.xml
* src/technologies/frontend.xml
* src/usability/context-of-use.xml
* src/tables/table-editor-graphviz.xml
* src/tables/table-editor-jgraph.xml
* src/tables/table-editor-flash.xml
* src/tables/table-editor-gef.xml
* src/tables/table-editor-png.xml: added fixes submitted by Jan
* stylesheets/plainpdf.xsl: fixes issue, that the sidewaystable
generates an additional label, which is not wanted
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Mon Aug 29 14:11:11 2005
(at)(at) -1,3 +1,24 (at)(at)
+2005-08-29 Roman Joost <rj(at)gocept.com>
+
+ * src/introduction/workflow-types.xml
+ * src/technologies/frameworks.xml
+ * src/technologies/renderingpipeline.xml
+ * src/technologies/graph-components.xml
+ * src/technologies/proc-definition.xml
+ * src/technologies/fileformats.xml
+ * src/technologies/intro.xml
+ * src/technologies/animation-interaction.xml
+ * src/technologies/frontend.xml
+ * src/usability/context-of-use.xml
+ * src/tables/table-editor-graphviz.xml
+ * src/tables/table-editor-jgraph.xml
+ * src/tables/table-editor-flash.xml
+ * src/tables/table-editor-gef.xml
+ * src/tables/table-editor-png.xml: added fixes submitted by Jan
+
+ * stylesheets/plainpdf.xsl: fixes issue, that the sidewaystable
+ generates an additional label, which is not wanted
+
2005-08-26 Roman Joost <rj(at)gocept.com>
* src/bibliography.xml: moved to bibliography dir
Modified: misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml Mon
Aug 29 14:11:11 2005
(at)(at) -9,8 +9,8 (at)(at)
<para lang="en">
It seems, that the term <quote>Workflow Type</quote> is not
commonly
- used either by the Workflow Management Coalition or by book authors
- covering that topic. I guess, that types of workflows are an
+ used either by the Workflow Management Coalition or by authors
+ covering the topic. I guess, that types of workflows are an
implementation detail and currently not covered by the
standardization process of the Workflow Management Coalition. The
only <quote>documentation</quote> about Workflow types I
found, was
(at)(at) -54,7 +54,7 (at)(at)
<figure id='figure-document-based-workflow'>
<title>
- Illustration of a content-oriented Workflow type.
+ Illustration of a content-oriented Workflow type
</title>
<mediaobject>
<imageobject role='tex'>
(at)(at) -70,7 +70,7 (at)(at)
so that only author and reviewer are able to see the
document. The reviewer checks the document and passes it to
the publisher if it's ready for publishing. In case the
- document contains to many errors, it'll be passed back to
+ document contains too many errors, it'll be passed back to
the author. The reviewer passes the document to the
publisher for publishing. Through this process, the
documents state changes from unpublished to published. The
(at)(at) -90,39 +90,36 (at)(at)
</indexterm>
<para>
- Activity-oriented Workflow types are going a different approach
- like the previously discussed content-oriented. The central
- point is not the document, but rather a task. This has the
- obvious advantage, that process definitions can describe
- other cases without documents. For example, if you need a
- passport for traveling to a foreign country, what will the
- Workflow process definition in a content-oriented Workflow type
- be? Without a document – the passport – no process definition can
- be setup, but thinking in terms of <quote>activities</quote>
we
- can easily model tasks like: <quote>obtain passport
- photographs</quote>, <quote>take a birth
certificate</quote>
- etc. Therefore, it's possible to use activity based Workflow types
- to <quote>simulate</quote> a document based workflow.
+ Activity oriented workflow types have a different approach to the
+ previously discussed content oriented workflow types. The central
+ point is not the document, but a task. The advantage is, that
+ process definitions can describe cases without documents.
+ For example, if you need a passport for traveling to a foreign
+ country, what will the Workflow process definition in a
+ content-oriented Workflow type be? Without a document – the
+ passport – no process definition can be setup, but thinking in
+ terms of <quote>activities</quote> we can easily model tasks
like:
+ <quote>obtain passport photographs</quote>,
<quote>take a birth
+ certificate</quote> etc. Therefore, it's possible to use activity
+ based Workflow types to <quote>simulate</quote> a document
based
+ workflow.
</para>
<para>
The implementation of activity based Workflow systems can be
- differentiated<!--XXX--> into two approaches: activity- and
- controller based respectively. The main difference between both
- implementation concepts are the self-sustaining work items for
- the activity based concept. A more flexible flow control than a
- monolithic approach – like the controller based would be – is the
result. <xref
- linkend="figure-workflow-implementation-concepts" /> illustrates
- both concepts.
- </para>
- <para>
+ differentiated into activity and controller based approaches. The
+ main difference between concepts is the self sustaining work items
+ for the activity based concept. The result is a more flexible flow
+ control than the monolithic controller based approaches would be.
+ <xref linkend="figure-workflow-implementation-concepts" />
+ illustrates both concepts.
AlphaFlow uses the activity based concept, which
leads to:
<itemizedlist>
<listitem>
<para>
- more scalability of defining workflows. In fact you can
- describe every Workflow you want, from small to big,
- everything works.
+ greater scalability to define workflow. You can accurately
+ describe every possible workflow from a small scale to a
+ large scale project.
</para>
</listitem>
<listitem>
(at)(at) -147,7 +144,7 (at)(at)
implementation.
The communication between work items is managed by the
controller, illustrated by a PC. The controller manages the
- work items it creates. Work items for them self can only
+ work items it creates. Work items can only
communicate through the controller. The authors are writing
a news item and an article (document). The controller
generates two work items for both reviewers: one is about
(at)(at) -175,9 +172,9 (at)(at)
<title>
The figure illustrates an activity-based Workflow
implementation.
- Lets assume, that the Workflow process definition is the
- same as described in (a). So, everything works completely
- same as in the controller based implementation, except that
+ The Workflow process definition is the
+ same as described in (a). Everything works
+ the same as the controller based implementation, except that
each work item has it's own decision space where it can
create or destroy work items (provided that it has the
correct rights). This concept allows building complex workflows
Modified: misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-flash.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-flash.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-flash.xml Mon Aug
29 14:11:11 2005
(at)(at) -74,7 +74,7 (at)(at)
<itemizedlist>
<listitem>
<para>
- not distributed unter a OpenSource license
+ not distributed under a OpenSource license
</para>
</listitem>
<listitem>
Modified: misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml Mon Aug
29 14:11:11 2005
(at)(at) -2,7 +2,8 (at)(at)
<para>
<table frame='all' id='table-editor-gef'>
- <title>Graphical Editing Framework features</title>
+ <title>Features of the GEF, discussed in <xref
+ linkend="editor-technologies-gef" />.</title>
<tgroup cols='2' colsep='1' rowsep='1'>
<colspec colname='empty' align='left' />
<colspec colname='description' align='justify'/>
(at)(at) -45,7 +46,7 (at)(at)
</row>
<row>
<entry>License fees</entry>
- <entry>nothing</entry>
+ <entry>none</entry>
</row>
<row>
<entry>implemented in</entry>
Modified:
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml Mon
Aug 29 14:11:11 2005
(at)(at) -2,16 +2,19 (at)(at)
<para>
<table frame='all' id='table-editor-graphviz'>
- <title>Graphviz features</title>
+ <title>
+ Features of AT & T Labs' GraphViz package discussed in <xref
+ linkend="editor-technologies-graphviz" />.
+ </title>
<tgroup cols='2' colsep='1' rowsep='1'>
- <colspec colname='empty' align='left' />
- <colspec colname='description' align='justify'/>
+ <colspec colname='empty' align="left"/>
+ <colspec colname='description' colwidth="11cm" />
<thead>
<row>
<entry></entry>
<entry>
<emphasis role='bold'>
- description
+ Description
</emphasis>
</entry>
</row>
(at)(at) -42,7 +45,7 (at)(at)
</row>
<row>
<entry>License fees</entry>
- <entry>nothing</entry>
+ <entry>none</entry>
</row>
<row>
<entry>implemented in</entry>
Modified: misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml Mon
Aug 29 14:11:11 2005
(at)(at) -2,7 +2,10 (at)(at)
<para>
<table frame='all' id='table-editor-jgraph'>
- <title>JGraph features</title>
+ <title>
+ Features of JGraph discussed in <xref
+ linkend='editor-technologies-jgraph' />.
+ </title>
<tgroup cols='2' colsep='1' rowsep='1'>
<colspec colname='empty' align='left' />
<colspec colname='description' align='justify'/>
(at)(at) -43,7 +46,7 (at)(at)
</row>
<row>
<entry>License fees</entry>
- <entry>nothing</entry>
+ <entry>none</entry>
</row>
<row>
<entry>implemented in</entry>
Modified: misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-png.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-png.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-png.xml Mon Aug
29 14:11:11 2005
(at)(at) -53,7 +53,7 (at)(at)
<itemizedlist>
<listitem>
<para>
- open format, changes to the format can be easier
+ open format, changes to the format can be easily
achieved through the world wide web consortium instead
of a single company
</para>
Modified:
misc/trunk/WorkflowEditor/docbook/src/technologies/animation-interaction.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/animation-interaction.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/technologies/animation-interaction.xml Mon
Aug 29 14:11:11 2005
(at)(at) -11,16 +11,15 (at)(at)
</indexterm>
<para>
- The user need to be informed about every state of the program and even
- he need to tell the program, how it should behave in specific cases.
+ The user needs to be informed about every state of the program and
+ needs to tell the program, how it should behave in specific cases.
Thus, the editor should provide an interaction facility between user
and editor backend. The animation capabilities of the previously
discussed SVG and Macromedia Flash formats are in the technical
- sense most likely the same. Both formats provide a technical basis
+ sense similar. Both formats provide a technical basis
for animating objects. Common differences are already
discussed in <xref linkend="fileformats" />. I'll elaborate the
- interaction facilities a bit more here, which is much more
- relevant.
+ relevant interaction facilities next.
</para>
<sect2>
(at)(at) -47,21 +46,19 (at)(at)
slightly different but compatible language – called JScript – is
in use. JavaScript and JScript are both standardized in the
ECMAScript specification in order to achieve much more
- compatibility between both languages with a completely different
- origin.
+ compatibility between these languages.
</para>
<para>
- The scripting support for SVG on the web is very rare, but seem to
- change nowadays. The SVG Plugin from Adobe Systems is currently
- the best viewer application for the web browser available as a
- plugin. This plugin has some difficulties with
- its scripting capabilities. The plugin uses it's own JavaScript
- implementation and not the ones provided by browsers, which is
- considered by the fact, that the current scripting implementations
- of major web browsers not work with SVG documents.
- Unfortunately, JavaScript statements for SVG objects rendered with
- the Adobe plugin are only executed by the
- Microsoft Internet Explorer<footnote>
+ Scripting support for SVG on the web is very rare. This is
+ changing. The SVG Plugin from Adobe Systems is currently the best
+ viewer application for the web browser available as a plugin. This
+ plugin has some difficulties with its scripting capabilities. The
+ plugin uses it's own JavaScript implementation and not the ones
+ provided by browsers, because the current scripting
+ implementations of major web browsers do not work with SVG
+ documents. Unfortunately, JavaScript statements for SVG objects
+ rendered with the Adobe plugin are only executed by Microsoft
+ Internet Explorer<footnote>
<para>
I tested it for myself on Microsoft Windows XP with Microsoft
Internet Explorer 6 and Mozilla Firefox. The test page calls
(at)(at) -86,7 +83,7 (at)(at)
allows its developers to easily translate the syntax. The client
model however is completely different. JavaScript uses windows,
documents and forms and ActionScript uses movie-clips and sounds.
- Newly versions of ActionScript, Version 2.0 in particular, adds
+ Newer versions of ActionScript, Version 2.0 in particular, adds
more object-oriented features such as explicit class declarations,
inheritance and interfaces. ActionScript is tightly bound to it's
Flash authoring environment, which can be used to write
Modified: misc/trunk/WorkflowEditor/docbook/src/technologies/fileformats.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/fileformats.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/fileformats.xml Mon Aug
29 14:11:11 2005
(at)(at) -10,14 +10,14 (at)(at)
and providing interactivity for image elements. Vector based image
fileformats like Macromedias Flash
provide a rendering, video, audio and an
- animation facility. SVG can handle graphical data likewise, but
+ animation facility. SVG can handle graphical data as well, but
provides an open API, which let you access every element in the
image file through a scripting language like JavaScript. Besides
vector-based image formats, there is also one pixel-based format
called PNG. The multimedia facilities are provided by third-party
solutions like image maps handled by a web server.
The following sections introduce several graphic formats which may
- suitable for using them as a canvas.<!-- XXX describe minor formats
+ suitable to use them as a canvas.<!-- XXX describe minor formats
here as well? -->
</para>
(at)(at) -28,15 +28,15 (at)(at)
</indexterm>
<para>
- XML is a markup language purposed by the W3C. All succeeding
+ XML is a markup language approved by the W3C. All succeeding
markup languages I describe are based on XML. Most applications
- support XML nowadays. The language has advantages and
+ now support XML. The language has advantages and
disadvantages <footnote>
<para>
cp. <ulink url="http://en.wikipedia.org/wiki/XML"
/> section
Strengths and weaknesses [accessed 2005-07-21]
</para>
- </footnote>, though it is supported by most applications nowadays.
+ </footnote>, it is supported by most applications nowadays.
The primary goal of XML is to facilitate the sharing of data
across different platforms. The syntax consists of elements with
attributes and content. Each element consists of two tags, which
(at)(at) -78,14 +78,14 (at)(at)
The plugin is available for Microsoft Windows, Linux and Solaris.
</para>
</footnote> for Web browsers available: a plugin, implemented by
- Adobe Systems, provides fast rendering, animation and scripting
+ Adobe Systems, providing fast rendering, animation and scripting
capabilities.
</para>
<para>
The Mozilla project is working on a native SVG implementation,
- which has the advantages to access SVG elements as DOM objects
- directly via JavaScript. This pushes the Mozilla platform as a
- whole web application framework forward. Unstable development
+ which has the advantage of accessing SVG elements as DOM objects
+ directly via JavaScript. This pushes forward the Mozilla platform as a
+ whole web application framework forward. Early unstable development
builds of Mozilla Firefox have support for native SVG
rendering<footnote>
<para>
(at)(at) -97,7 +97,7 (at)(at)
</footnote>.
</para>
<para>
- Besides Mozilla, there are more organisations and companies
+ Apart from Mozilla there are other organisations and companies
implementing SVG. The newest Opera browser<footnote>
<para>
Opera 8 was the latest release during writing this thesis. For
(at)(at) -118,7 +118,7 (at)(at)
For more information about the KSVG project, look at: <ulink
url="http://svg.kde.org/" />
</para>
- </footnote> like Mozilla, which will probably pushed forward by
+ </footnote> as Mozilla, which was probably pushed forward by
the Apple Corportation. The project and the company using the same
codebase for their browser, which is known as Konqueror for KDE
and Safari for Mac OS X.
(at)(at) -139,7 +139,7 (at)(at)
<para>
Unlike SVG, Flash is a binary
- format which leads into problems with search engines indexing
+ format which leads to problems with search engines indexing
flash pages.
The great advantage of Flash over other vector based graphics
formats is the platform independent viewer application. According
(at)(at) -151,10 +151,12 (at)(at)
</para>
</footnote>, which is the most supported vector-based graphic
format with animation capabilities in the World Wide Web. The
- format was several years closed and is opened after Adobe Systems
+ format was several years closed and was opened after Adobe Systems
pushed the SVG format forward. Macromedia however, retains the
control of Flash. That means, developers of editors which support
- Flash in any way need to buy a license from Macromedia.
+ Flash in any way need to buy a license from Macromedia. Note, that
+ Adobe and Macromedia amalgamated during writing of this diploma
+ thesis, which may lead into a change of the license agreements.
</para>
<xi:include href="../tables/table-editor-flash.xml" />
</sect2>
(at)(at) -174,7 +176,7 (at)(at)
<para>
The PNG format was created in early 1995, after Unisys announced
- his software patent enforcement on the LZW data compression used
+ its software patent enforcement on the LZW data compression used
in GIF and other data compression tools. It is a bitmap image
format, which deals with some of the shortcomings of GIF. It
supports alpha transparency and up to 48-bit colors. It is widely
(at)(at) -191,7 +193,7 (at)(at)
are two approaches for handling click events on Image maps:
client-based and server-based handling.
The latter solution uses server side program logic and the
- first uses a scripting language like JavaScript. I've to note, that the
+ first uses a scripting language like JavaScript. The
possibilities with PNG and Image maps are limited and probably not
suitable for building a fully interactive graphical editor. It can
be considered as a fallback solution, if a client doesn't support
Modified: misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml Mon Aug
29 14:11:11 2005
(at)(at) -11,8 +11,8 (at)(at)
implement a specific scope. They can be separated by their operative
range (eg. Application or Class Frameworks) and provide a large set
of reusable code. Developers can save a huge amount of time by using
- this code set, which provides most of standard code (e.g. displaying
- an application window on a screen) and is customizable at one time.
+ this code set. It provides most of standard code (e.g. displaying
+ an application window on a screen) and is customizable.
</para>
<para>
The succeeding introduction of frameworks are based on two
(at)(at) -39,10 +39,10 (at)(at)
</para>
<para>
I'll introduce a few frameworks here, which provide basic
- functionality for every part of the rendering pipeline. AlphaFlow is
- bound to the Zope Application Framework; the choice between the
- Mozilla Application Framework and the specification from the WHATWG
- will affect the application frontend.
+ functionality for each part of the rendering pipeline. AlphaFlow
+ uses the Zope Application Framework for the backend. The frontend
+ may be the choice between the Mozilla Application Framework and the
+ specification from the WHATWG.
</para>
<sect2 id="zope">
(at)(at) -62,7 +62,7 (at)(at)
<para>
Zope (Z Object Publishing Environment) is an application server,
which provides a web application framework. Most of Zope is
- written in Python; only performance-critical pieces are written in
+ written in Python; only performancecritical pieces are written in
C. The framework is very modular and allows developers to add self
written Zope objects bundled as products into the Zope machinery
as well as removing them, without touching any Zope internal
(at)(at) -74,7 +74,7 (at)(at)
once to users and they define what users can do (e.g. Manager,
Editor, Author). Permissions are defined by Zope objects and
describe what users or other objects can do with them (e.g. View,
- Delete objects, Manage properties). In that turn, permissions can
+ Delete objects, Manage properties). Permissions can
be assigned to various roles by the administrator to allow or
disallow what users can do in Zope.
</para>
(at)(at) -94,15 +94,13 (at)(at)
substitute alternate tool implementations. Eight tools are shipped
with the CMF distribution and building the basis of a
content management system.
- I'm only listing the most important
- tools<footnote>
+ The most relevant tools<footnote>
<para>
For a detailed list, look at <ulink
url="http://www.zope.org/Products/CMF/docs/design/system_architecture/view"
/> [accessed 2005-03-15]
</para>
- </footnote>, which are
- relevant for a graphical workflow editor.
+ </footnote> for a graphical workflow editor are:
</para>
<variablelist>
<varlistentry>
(at)(at) -135,7 +133,7 (at)(at)
<secondary>Plone</secondary>
</indexterm>
<para>
- A new user-friendly Content Management System was build upon CMF
+ A user-friendly Content Management System was build upon CMF
called Plone<footnote>
<para>
In fact, there are a bit more Content Management Systems build
(at)(at) -145,8 +143,8 (at)(at)
/>). Silva is today much more Zope based
than relying on CMF.
</para>
- </footnote>. This system is only mentioned here for the sake of
- completeness and the most used Content Management System on the
+ </footnote>. This system is mentioned here for the sake of
+ completeness and is the most used Content Management System on the
Zope platform. Most of the applications gocept develops are based
on Plone.
</para>
(at)(at) -172,24 +170,24 (at)(at)
</indexterm>
<para>
- After Netscape released his browser under an open source
+ After Netscape released its browser under an open source
license<footnote>
<para>
The release under the <ulink
url="http://www.opensource.org/licenses/mozilla1.1.php">Mozilla
Public License</ulink> was a bit controversial in the free
- software community, because Netscape reserved his right to
+ software community, because Netscape reserved its right to
close the source in the future which in turn conflicts with
- <quote>free software</quote>. Therefore, free software
+ <quote>free software</quote>. Free software
projects emphasised the freedom of use of their code, instead
of just an <quote>open sourced</quote> code with
restrictions.
</para>
- </footnote> the Mozilla Foundation spend time into implementing a
+ </footnote> the Mozilla Foundation spend time implementing a
new browser suite as well as a new application framework. The
Mozilla browser suite is now based on a platform independent
network and rendering framework, which made it easier to port the
browser suite to other platforms than Microsofts Windows,
- GNU/Linux and a few Unix operating systems. The core library set of the
+ GNU/Linux and a some Unix operating systems. The core library set of the
framework is build on several libraries, like Gecko, Necko and
others<footnote>
<para>
(at)(at) -202,10 +200,10 (at)(at)
newest web technologies for displaying images (PNG, SVG),
aggregating news feeds through RDF or supporting scripting
languages such as the ECMAScript dialect JavaScript. The release
- cycle for the browser suite is very fast, everyone is able to
- submit bugs and can join the development. Development builds
- assembling newest web technologies like the support for XForms or
- SVG, but more about this later.
+ cycle for the browser suite is very fast, anyone is able to
+ submit bugs and can join the development. The development
+ assembles the newest web technologies like the support for XForms or
+ SVG. I will cover this in more detail later.
</para>
</sect2>
(at)(at) -228,13 +226,13 (at)(at)
role="bold">G</emphasis>roup is a vendor-driven working group
with
the greatest contributors Mozilla Foundation, Opera Software and
Apple Computers. It aims to extend existing web technologies like
- HTML to allow authors to write and deploy them easily. Either this
- working group nor their specifications are frameworks. The reason
- why I list this group under the
<emphasis>Frameworks</emphasis>
- topic, is that the technologies like XHTML and JavaScript the WHATWG
- is dealing with, can be considered as a Framework. The working
- group setup three specifications drafts which will lead into
- recommendations for the used technologies. The drafts compass:
+ HTML to allow authors to write and deploy them easily. Neither
+ this working group nor their specifications are frameworks. The
+ reason this group is listed here, is that technologies like XHTML,
+ JavaScript and the WHATWG can be considered as a Framework. The
+ working group setup three specifications drafts which will lead
+ into recommendations for the used technologies. The drafts
+ compass:
</para>
<variablelist>
Modified: misc/trunk/WorkflowEditor/docbook/src/technologies/frontend.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/technologies/frontend.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/frontend.xml Mon Aug 29
14:11:11 2005
(at)(at) -4,10 +4,10 (at)(at)
<para>
The user interface is the face of the application which interacts
- with the user and the other way around. To create a user friendly
- interface, it needs certain technologies for making it attractive.
- I'll discuss in the following technologies which are based on the
- previously discussed application frameworks.
+ with the user and the other way around. To create an attractive user
+ friendly interface needs certain technologies. I'll discuss in the
+ following technologies which are based on the previously discussed
+ application frameworks.
</para>
(at)(at) -32,8 +32,8 (at)(at)
which became the Mozilla browser. Although XUL is not a W3C
standard, it uses a lot of standardized
technologies, such as CSS, JavaScript, DTD and RDF. Therefore it
- is easily learnable by developers with a web development
- background with it's key features of XHTML and JavaScript. XUL
+ is easily learnt by developers with a web development
+ background. With its key features of XHTML and JavaScript. XUL
interfaces split up into three components:
<variablelist>
<varlistentry>
Modified:
misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml Mon
Aug 29 14:11:11 2005
(at)(at) -19,7 +19,7 (at)(at)
</para>
<sect2 id="editor-technologies-graphviz">
- <title>Graphviz - Graph Visualization Software</title>
+ <title>GraphViz - Graph Visualization Software</title>
<indexterm>
<primary>GraphViz</primary>
(at)(at) -97,20 +97,20 (at)(at)
<para>
The Graphical Editing Framework was primary developed for the
- eclipse development plattform<footnote>
+ Eclipse development plattform<footnote>
<para>
see <ulink url="http://www.eclipse.org/" />
</para>
</footnote>. It splits into two plug-ins, providing the
rendering toolkit for displaying graphics and a controller
framework for mapping the business model to a view. The main
- purpose for using the GEF ist to develop applications which deal
- with diagrams, like a flow chart editor. Thus, it's a possible
+ purpose for using the GEF is to develop applications which deal
+ with diagrams, such as a flow chart editor. Thus, it's a possible
aspirant for building a graphical workflow editor.
</para>
<para>
- The main drawback of the GEF is the layout machinery, which is not
- powerfull enough as the GraphViz tools described in <xref
+ The main drawback of the GEF is the layout machinery which is not
+ as powerfull as the GraphViz tools described in <xref
linkend="editor-technologies-graphviz" />.
</para>
<xi:include href="../tables/table-editor-gef.xml" />
(at)(at) -132,8 +132,9 (at)(at)
for more information see <ulink
url="http://www.jgraph.com/jgraph.html"
/>
</para>
- </footnote>. Thus, much more suitable for generating graphs
- compared to the GEF, but not as powerful as GraphViz.
+ </footnote>
+ It is more suitable for generating graphs than the GEF but it is
+ not as powerful as GraphViz.
</para>
<para>
A company behind the opensource product offers
Modified: misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml Mon Aug 29
14:11:11 2005
(at)(at) -4,8 +4,8 (at)(at)
<para lang="en">
Based on a rendering pipeline, I'll introduce several frameworks,
technologies and products which provide the necessary functionality
- for building a graphical editor. The chellange is off course, a
- combination between one of those to achieve a platform which is
+ for building a graphical editor. The challenge is to
+ combine these to achieve a platform which is
future proof and provide a rich set of functionality to build upon.
</para>
</highlights>
Modified:
misc/trunk/WorkflowEditor/docbook/src/technologies/proc-definition.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/proc-definition.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/proc-definition.xml Mon
Aug 29 14:11:11 2005
(at)(at) -1,28 +1,27 (at)(at)
<?xml version="1.0" encoding="UTF-8" ?>
<sect1 id="proc-definition" xmlns:xi="http://www.w3.org/2001/XInclude">
- <title>Prozessdefinition Components</title>
+ <title>Components for Process Definition</title>
<indexterm>
<primary>Technologies</primary>
<secondary lang="en">Modeling languages</secondary>
</indexterm>
<para>
- The processdefinition components are responsible for storing
- process definitions created by the user.
- In 1993, the Workflow Management Coalition was the first group,
- which standardised the workflow modeling. They defined interfaces
- between Workflow Managment Systems and actors, as well as new
- workflow definition formats like XPDL. Till then, various other
- specifications were developed by other groups and companies like
- Microsoft, IBM, SAP etc. to fulfil their needs.
+ The processdefinition components are responsible for storing process
+ definitions created by the user. In 1993, the Workflow Management
+ Coalition was the first group, standardize the workflow modeling.
+ They defined interfaces between Workflow Managment Systems and
+ actors, as well as new workflow definition formats like XPDL. Until
+ then, specifications were developed by other groups and companies
+ like Microsoft, IBM, SAP etc. to fulfil their needs.
<citation>Aalst03</citation> describes in his work four groups
of
different Workflow specification perspectives.
</para>
<para>
Those specs, although very specific in their scope, have one primary
base – XML, which is described in detail in <xref
- linkend="fileformat-xml" />. The following sections summarizing
+ linkend="fileformat-xml" />. The following sections summarises
existing specifications, formerly described by
<citation>Baeyens04</citation>.
</para>
(at)(at) -34,7 +33,7 (at)(at)
</indexterm>
<para lang="en">
- The XML Process Definition Language is a XML based format
+ The XML Process Definition Language is an XML based format
developed by the Workflow Management Coalition<footnote>
<para>
<ulink url='http://www.wfmc.org' /> [accessed
2005-01-27].
(at)(at) -49,7 +48,7 (at)(at)
Unfortunately this means, that every workflow definition has to
specify the whole environment (applications, functions, software
to use, code snippets) in which it runs. XPDL becomes a
- boulder to customize, which is possible with a huge effort.
+ boulder to customize which is possible only with huge effort.
<citation>Baeyens04</citation> statet on the website of
JBPM<footnote>
<para>
(at)(at) -58,13 +57,14 (at)(at)
</footnote>:
<blockquote>
<para>
- Using one of these specification<footnote>
+ Using one of these specifications<footnote>
<para>
Specifications for process definition languages developed
in the past, like WfMC's XPDL, BPML, ebXML, BPEL4WS,
XLANG, WSCI etc.
</para>
- </footnote> would have been problematic for various reasons:
+ </footnote>[process definition languages] would have been
+ problematic for various reasons:
<itemizedlist>
<listitem>
<para>
(at)(at) -118,8 +118,8 (at)(at)
The <quote>JSR 207: Process Definition for Java</quote> was
an
initiative of the Java Community Process, that standardizes
how business processes on a J2EE server can be automated. The
- specification was in 2003 still in an early stage. Till then,
- nothing seems to have happened.
+ specification was in 2003 still in an early stage. There has been
+ no recent development.
</para>
</sect2>
(at)(at) -155,7 +155,7 (at)(at)
activity diagram (example shown in <xref linkend="figure-uml"
/>), included in this set, can be used to show how
business processes should be visually represented.
- <citation>Baeyens04</citation> statet, that a process
definition
+ <citation>Baeyens04</citation> stated, that a process
definition
is more then just its visual representation<footnote>
<para>
cp. <citation>Baeyens04</citation>, The state layer
(at)(at) -198,8 +198,8 (at)(at)
state machines; both using states and transitions for the process
description. An example is shown in <xref
linkend="figure-petri-net" />.
- According to <citation>Aalst03</citation>, there are several
good
- reasons Petri nets provide for using them to describe a business
+ According to <citation>Aalst03</citation>, there are several
+ reasons to use Petri nets to describe a business
process:
<orderedlist>
<listitem>
Modified:
misc/trunk/WorkflowEditor/docbook/src/technologies/renderingpipeline.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/renderingpipeline.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/technologies/renderingpipeline.xml Mon
Aug 29 14:11:11 2005
(at)(at) -8,12 +8,12 (at)(at)
</indexterm>
<para>
- The editor can be easily seperated between a frontend and backend
- application. The backend, which is probably taken by a server
- application, will care about layouting the graph, which is the most
- resource intensive part. The frontend, will
+ The graphical editor can be separated into a frontend and backend
+ application. The backend, which in this case is a server
+ application will do the most resource intensive part – laying out
+ the graph. The frontend, will
render the graphical data and take care of the user interaction.
- Note though, that possible frontend and backend technologies are
+ Note, that possible frontend and backend technologies are
discussed in <xref linkend="frameworks" /> and <xref
linkend="fileformats" />.
</para>
Modified: misc/trunk/WorkflowEditor/docbook/src/usability/context-of-use.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/usability/context-of-use.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/usability/context-of-use.xml Mon Aug
29 14:11:11 2005
(at)(at) -14,7 +14,7 (at)(at)
The analysis of the context is proposed to be made in several
steps of the
development process.
- <citation>UsabilityNet03</citation> proposes such a "review"
+ <citation>UsabNet03</citation> proposes such a "review"
method in <quote>Planning & Feasibility</quote>,
<quote>Requirements</quote> and the
<quote>Design</quote> phase,
although the table offers for every step a different name.
Modified: misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl (original)
+++ misc/trunk/WorkflowEditor/docbook/stylesheets/plainpdf.xsl Mon Aug 29
14:11:11 2005
(at)(at) -92,7 +92,9 (at)(at)
<xsl:text>{\caption{</xsl:text>
<xsl:apply-templates select="title" mode="caption.mode"/>
<xsl:text>}</xsl:text>
- <xsl:call-template name="label.id"/>
+ <!-- XXX leads to multiple defined labels
+ <xsl:call-template name="label.id"/>
+ -->
<xsl:text>}} </xsl:text>
</xsl:for-each>
</xsl:template>
|
SVN: r3332 - in misc/trunk/WorkflowEditor/docbook: . images src src/alphaflow src/bibliography src/conclusions src/editor src/glossary src/introduction src/requirements src/tables src/technologies stylesheets
Roman Joost <rj(at)gocept.com> |
2005-08-30 15:27:02 |
[ FULL ]
|
Author: roman
Date: Tue Aug 30 15:26:33 2005
New Revision: 3332
Added:
misc/trunk/WorkflowEditor/docbook/images/gimp-panel.png (contents, props
changed)
misc/trunk/WorkflowEditor/docbook/src/conclusions/not-discussed.xml
Modified:
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml
misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml
misc/trunk/WorkflowEditor/docbook/src/alphaflow/work-item-state.xml
misc/trunk/WorkflowEditor/docbook/src/appendix-screenshots.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml
misc/trunk/WorkflowEditor/docbook/src/diplom.xml
misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml
misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml
misc/trunk/WorkflowEditor/docbook/src/editor/intro.xml
misc/trunk/WorkflowEditor/docbook/src/glossary/d.xml
misc/trunk/WorkflowEditor/docbook/src/glossary/p.xml
misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml
misc/trunk/WorkflowEditor/docbook/stylesheets/titlepage.tex
Log:
2005-08-30 Roman Joost <rj(at)gocept.com>
* src/appendix-screenshots.xml
* images/gimp-panel.png: new screenshot
* src/introduction/workflow-types.xml
* src/diplom.xml
* src/technologies/frameworks.xml
* src/technologies/graph-components.xml
* src/requirements/considered-problems.xml
* src/editor/implementation.xml
* src/editor/intro.xml
* src/editor/conclusions.xml
* src/conclusions/not-discussed.xml
* src/glossary/d.xml
* src/glossary/p.xml
* src/tables/table-technologies-comparison.xml
* src/tables/table-editor-graphviz.xml
* src/tables/table-editor-jgraph.xml
* src/tables/table-editor-gef.xml
* src/bibliography/technologies.xml
* src/bibliography/usability.xml
* src/alphaflow/intro.xml
* src/alphaflow/process-state.xml
* src/alphaflow/work-item-state.xml: fixed spelling and rephrased
some of the paragraph, motivated by Prof. Fissgus criticism
* stylesheets/titlepage.tex: remark to use advisor
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Tue Aug 30 15:26:33 2005
(at)(at) -1,3 +1,32 (at)(at)
+2005-08-30 Roman Joost <rj(at)gocept.com>
+
+ * src/appendix-screenshots.xml
+ * images/gimp-panel.png: new screenshot
+
+ * src/introduction/workflow-types.xml
+ * src/diplom.xml
+ * src/technologies/frameworks.xml
+ * src/technologies/graph-components.xml
+ * src/requirements/considered-problems.xml
+ * src/editor/implementation.xml
+ * src/editor/intro.xml
+ * src/editor/conclusions.xml
+ * src/conclusions/not-discussed.xml
+ * src/glossary/d.xml
+ * src/glossary/p.xml
+ * src/tables/table-technologies-comparison.xml
+ * src/tables/table-editor-graphviz.xml
+ * src/tables/table-editor-jgraph.xml
+ * src/tables/table-editor-gef.xml
+ * src/bibliography/technologies.xml
+ * src/bibliography/usability.xml
+ * src/alphaflow/intro.xml
+ * src/alphaflow/process-state.xml
+ * src/alphaflow/work-item-state.xml: fixed spelling and rephrased
+ some of the paragraph, motivated by Prof. Fissgus criticism
+
+ * stylesheets/titlepage.tex: remark to use advisor
+
2005-08-29 Roman Joost <rj(at)gocept.com>
* src/introduction/workflow-types.xml
Added: misc/trunk/WorkflowEditor/docbook/images/gimp-panel.png
==============================================================================
Binary file. No diff available.
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml Tue Aug 30
15:26:33 2005
(at)(at) -28,7 +28,12 (at)(at)
<para>
On the basis of <xref linkend="alphaflow-concept" />, i'll explain
the concept in short. An instance of a process definition is a
- characteristic type with a various amount of work items. Each work
+ characteristic type<footnote>
+ <para>
+ Implemented as a folder in Zope, which holds all activity
+ objects defined by the process definition.
+ </para>
+ </footnote> with a various amount of work items. Each work
item is an instance of an activity. Process instances and work items
can fall into different states, which are more elaborated in the
succeeding sections. The user, who defines the process or workflow
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml Tue Aug
30 15:26:33 2005
(at)(at) -8,8 +8,14 (at)(at)
</indexterm>
<para>
- As I already mentioned in <xref linkend="alphaflow-what-is" />, a
- process instance is a characteristic type of the process definition.
+ As I already mentioned in the introduction of
+ AlphaFlow<footnote>
+ <para>
+ cp. <xref linkend="alphaflow-what-is" />
+ </para>
+ </footnote>, a
+ process instance is an instance of the process definition object.
+ The instance is created during the import of the process definition.
There can be several activities defined for a process startup. These
activites are defined by the
<parameter>startActivity</parameter><footnote>
(at)(at) -17,7 +23,7 (at)(at)
cp. <xref linkend="alarm_review" />
</para>
</footnote>
- and executed by the order of the given
<paramter>id</paramter>s on
+ and executed by the order of the given
<parameter>id</parameter>s on
start. The instances can change into one of the following states:
</para>
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/work-item-state.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/alphaflow/work-item-state.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/work-item-state.xml Tue Aug
30 15:26:33 2005
(at)(at) -52,8 +52,10 (at)(at)
<listitem>
<para>
- The work item stopped manually by an
- administrative user.
+ The work item was stopped prematurely. This state can only be
+ triggered manually and has an administrative purpose. Work
+ items change to active state if the process instance is
+ restartet. <!-- XXX -->
</para>
</listitem>
</varlistentry>
Modified: misc/trunk/WorkflowEditor/docbook/src/appendix-screenshots.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/appendix-screenshots.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/appendix-screenshots.xml Tue Aug 30
15:26:33 2005
(at)(at) -56,4 +56,24 (at)(at)
</imageobject>
</mediaobject>
</figure>
+
+ <figure id='figure-gimp-panel'>
+ <title>
+ A screenshot showing panels which are collected in container
+ widgets called <quote>dock</quote>. Panels can be dragged
out of
+ the container and hold in their own window. They only show a
+ specific set of information, dependend on the user and what he
+ want like to see. Screenshot taken from TheGIMP; CVS TRUNK Build on
+ 2005-08-30, <ulink url="http://www.gimp.org" />.
+ </title>
+ <mediaobject>
+ <imageobject role='tex'>
+ <imagedata fileref='images/gimp-panel.png'
+ width="6cm" scalefit='1' />
+ </imageobject>
+ <imageobject role='html'>
+ <imagedata fileref='images/gimp-panel.png' scalefit="1" />
+ </imageobject>
+ </mediaobject>
+ </figure>
</appendix>
Modified: misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml Tue Aug
30 15:26:33 2005
(at)(at) -39,4 +39,45 (at)(at)
/> [accessed 2005-03-29]
</releaseinfo>
</biblioentry>
+
+ <biblioentry>
+ <abbrev>Behrens05</abbrev>
+ <authorgroup>
+ <author>
+ <firstname>Heiko</firstname>
+ <surname>Behrens</surname>
+ </author>
+ <author>
+ <firstname>Sebastian</firstname>
+ <surname>Zarnekow</surname>
+ </author>
+ </authorgroup>
+ <copyright>
+ <year>2005</year>
+ <holder>Heise Zeitschriften Verlag GmbH & Co. KG
</holder>
+ </copyright>
+ <title>
+ Blickpunkte – Eclipse GEF bei der Darstellung von Schienennetzen
+ </title>
+ <releaseinfo>
+ iX – Magazin für professionelle Informationstechnik, Issue 9/2005
+ </releaseinfo>
+ </biblioentry>
+
+ <biblioentry>
+ <abbrev>Duesterloh05</abbrev>
+ <author>
+ <firstname>Karsten</firstname>
+ <surname>Düsterloh</surname>
+ </author>
+ <copyright>
+ <year>2005</year>
+ <holder>Heise Zeitschriften Verlag GmbH & Co.
KG</holder>
+ </copyright>
+ <title>Schachtelsatz</title>
+ <subtitle>XUL-Tutorial 1: Basiselemente der
Browsererweiterung</subtitle>
+ <releaseinfo>
+ iX – Magazin für professionelle Informationstechnik, Issue 7/2005
+ </releaseinfo>
+ </biblioentry>
</bibliodiv>
Modified: misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/usability.xml Tue Aug 30
15:26:33 2005
(at)(at) -4,23 +4,6 (at)(at)
<title>Usability, User Interface Design</title>
- <biblioentry>
- <abbrev>Duesterloh05</abbrev>
- <author>
- <firstname>Karsten</firstname>
- <surname>Düsterloh</surname>
- </author>
- <copyright>
- <year>2005</year>
- <holder>Heise Zeitschriften Verlag GmbH & Co.
KG</holder>
- </copyright>
- <title>Schachtelsatz</title>
- <subtitle>XUL-Tutorial 1: Basiselemente der
Browsererweiterung</subtitle>
- <releaseinfo>
- Published by <emphasis>iX – Magazin für professionelle
- Informationstechnik</emphasis>, Issue 7/2005
- </releaseinfo>
- </biblioentry>
<biblioentry>
<abbrev>Beyer98</abbrev>
Added: misc/trunk/WorkflowEditor/docbook/src/conclusions/not-discussed.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/conclusions/not-discussed.xml Tue Aug
30 15:26:33 2005
(at)(at) -0,0 +1,30 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1>
+ <title>Aspects not coverd by this thesis</title>
+
+ <para>
+ Some theoretical and technical
+ aspects become interesting, during writing this diploma thesis.
+ Although not relevant for mentioning and reviewing, it'll be
+ definitly worth to look at in the future.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Ruby on Rails</term>
+ <listitem>
+ <para>
+ is a framework based on ruby ...
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>...</term>
+ <listitem>
+ <para>
+ ...
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+</sect1>
Modified: misc/trunk/WorkflowEditor/docbook/src/diplom.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/diplom.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/diplom.xml Tue Aug 30 15:26:33 2005
(at)(at) -67,6 +67,12 (at)(at)
</chapter>
<chapter>
+ <title>Existing Products</title>
+ <xi:include href="existing/engines.xml" />
+ <xi:include href="existing/editors.xml" />
+ </chapter>
+
+ <chapter id="alphaflow">
<title>AlphaFlow</title>
<xi:include href="alphaflow/intro.xml" />
<xi:include href="alphaflow/activities.xml" />
(at)(at) -96,13 +102,6 (at)(at)
</chapter>
<chapter>
- <title>Existing Products</title>
- <xi:include href="existing/engines.xml" />
- <xi:include href="existing/editors.xml" />
- </chapter>
-
-
- <chapter>
<title>Editor Prototype</title>
<xi:include href="editor/intro.xml" />
<xi:include href="editor/first-mockup.xml" />
(at)(at) -115,6 +114,7 (at)(at)
<chapter>
<title>Conclusions</title>
<xi:include href="conclusions/technicalbasis.xml" />
+ <xi:include href="conclusions/not-discussed.xml" />
</chapter>
<xi:include href="appendix-screenshots.xml" />
Modified: misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml Tue Aug 30
15:26:33 2005
(at)(at) -1,7 +1,7 (at)(at)
<?xml version='1.0' encoding="UTF-8" ?>
<sect1 id="usability-conclusions">
- <title>Conclusions for a Prototype Implementation</title>
+ <title>Conclusions for Implementing a Prototype</title>
<para>
Based on the requierements, usability methods and test
results<footnote>
<para>
(at)(at) -17,67 +17,55 (at)(at)
following features necessary for implementing a prototype of the
graphical Workflow editor.
</para>
-
+
<variablelist>
- <title>Workfloweditor Requirements</title>
<varlistentry>
- <term>tool tips</term>
+ <term>Tool Tips</term>
<listitem>
<para>
- If the user is hovering over a state, he should be able to
- see a tool tip containing the information about the
- attributes the state has.
+ When hovering over an activity, the editor shows a tool tip
+ containing the information about the activity properties.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Icons for Activities</term>
-
<listitem>
<para>
- Icons should make the included AlphaFlow activities
- distinguishable, because a user can't memorize more than seven forms
or
- colors indicating different activities.
+ The graphical editor uses icons to help users to distinguish
+ between various activities.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>Grouping Panels</term>
-
+ <term>Panels</term>
<listitem>
<para>
- Not relevant panels in the workflow editor should hide the
- options. A click on an icon makes the panel properties
- visible.
+ are a technique mostly used by filesystem applications.
+ <remark><!-- XXX -->FS Applications the correct term
here?</remark>
+ They hold an exact piece of information. The prototype won't
+ implement the entire panel concept used by other applications.
+ It should be possible to minimize and maximize panels (either
+ by the user or by the system).
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Important Parts Stay in Focus</term>
-
<listitem>
<para>
The workflow overview and toolbox should always be visible
during workflow editing. Popups should be avoided, because
they distract the user from his flow creating or editing
- workflows. To quote <citation>Raskin02</citation>:
- <blockquote>
- <attribution>Jef Raskin</attribution>
- <para>
- When using a product to help you do a task, the
- product should only help and never distract you from
- the task.
- </para>
- </blockquote>
+ workflows.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Statusbar</term>
-
<listitem>
<para>
A statusbar keeps the user up to date with information. It
(at)(at) -90,18 +78,16 (at)(at)
<varlistentry>
<term>Drag'n Drop</term>
-
<listitem>
<para>
- If technically possible, the editor should support a
- drag'n drop mechanism for connecting the activities.
+ A Drag'n Drop mechanism should help users to connect
+ activities as well as helping in other use cases.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Template Support</term>
-
<listitem>
<para>
The user should be able to import complex workflow
(at)(at) -113,10 +99,23 (at)(at)
</variablelist>
<para>
+ The backend consists of the Zope Application Framework which
+ provides the data storage and AlphaFlow functionality. The frontend
+ requires a Mozilla Firefox 2 compatible browser which supports
+ rendering SVG graphics nativly. The interaction is provided by
The technical basis will be an XHTML page including SVG statements.
- Interaction is processed by Javascript.<remark>
- <!-- XXX --> more details.
- </remark>
+ Javascript provides interaction between the frontend and the
+ user. The JavaScript library
+ <emphasis>Sarissa</emphasis><footnote>
+ <para>
+ <ulink
+ url="http://sarissa.sourceforge.net/doc/overview-summary.html"
+ /> [accessed 2005-08-30]
+ </para>
+ </footnote> will be
+ used to achieve the asynchronous communication between frontend and
+ backend. Objects resieved and send to the server need to be
+ serialized to XML.
</para>
<figure id='figure-usability-interface-concept'>
<title>
Modified: misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml Tue Aug 30
15:26:33 2005
(at)(at) -9,7 +9,7 (at)(at)
</indexterm>
<para>
- ...
+ I spent approx. five weeks for implementing the prototype.
</para>
</sect1>
Modified: misc/trunk/WorkflowEditor/docbook/src/editor/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/editor/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/intro.xml Tue Aug 30 15:26:33
2005
(at)(at) -7,11 +7,14 (at)(at)
Graphs are usually represented pictorially by dots and arcs. The
dots represent the vertexes and the arcs represent the connection
between vertexes. Directed graphs can be indicated using arrows on
- the end of the arcs. <!-- XXX As I described in <xref
- linkend="technologies-workflow-modeling" />, workflows are best
- represented in the way they are modelled - Why? -->. That means,
- the visualisation should be able to draw graphs like the one in UML
- diagrams and petri nets.
+ the end of the arcs.
+ <remark>
+ <!-- XXX--> As I described in <!--<xref
+ linkend="technologies-workflow-modeling" />-->, workflows are best
+ represented in the way they are modelled - Why?
+ </remark>
+ That means, the visualisation should be able to draw graphs like the
+ one in UML diagrams and petri nets.
</para>
<indexterm>
Modified: misc/trunk/WorkflowEditor/docbook/src/glossary/d.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/glossary/d.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/glossary/d.xml Tue Aug 30 15:26:33
2005
(at)(at) -11,7 +11,8 (at)(at)
<glossdef>
<para>
The Document Object Model is an application programming
- interface (API) for HTML and XML documents.
+ interface (API) for acessing node objects in XML compatible
+ documents.
</para>
</glossdef>
</glossentry>
Modified: misc/trunk/WorkflowEditor/docbook/src/glossary/p.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/glossary/p.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/glossary/p.xml Tue Aug 30 15:26:33
2005
(at)(at) -3,6 +3,34 (at)(at)
<glossdiv>
<title>P</title>
+ <glossentry id="glossary-panel">
+ <glossterm>Panel</glossterm>
+ <indexterm>
+ <primary>Panel</primary>
+ </indexterm>
+ <glossdef>
+ <para>
+ Panels are widely in use by Applications which deal with
+ manipulation of graphical data like
+ Adobes<trademark>Photoshop</trademark><footnote>
+ <para>
+ <ulink
+ url="http://www.adobe.com/products/photoshop/main.html"
/>
+ [accessed 2005-08-30]
+ </para>
+ </footnote> or
+ TheGIMP<footnote>
+ <para>
+ <ulink url="http://www.gimp.org" /> [accessed 2005-08-30]
+ </para>
+ </footnote>. A panel shows a specific information. Most panels
+ are stored in a container widget. The user can decide which
+ information the container shows him by adding or removing
+ panels. <xref linkend="figure-gimp-panel" /> shows a screenshot
+ of a container including a set of panels.
+ </para>
+ </glossdef>
+ </glossentry>
<glossentry id='glossary-petri-net'>
<glossterm lang="de">Petri-Netz</glossterm>
<glossterm lang="en">Petri nets</glossterm>
Modified: misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/introduction/workflow-types.xml Tue
Aug 30 15:26:33 2005
(at)(at) -8,18 +8,21 (at)(at)
</indexterm>
<para lang="en">
- It seems, that the term <quote>Workflow Type</quote> is not
commonly
+ It seems, that the term <quote>workflow type</quote> is not
commonly
used either by the Workflow Management Coalition or by authors
covering the topic. I guess, that types of workflows are an
implementation detail and currently not covered by the
standardization process of the Workflow Management Coalition. The
- only <quote>documentation</quote> about Workflow types I
found, was
+ only <quote>documentation</quote> about workflow types I
found, was
an old proposal on zope.org, where
<citation>Guillaume02</citation>
describes content-oriented and activity-oriented workflows with the
- goal to unify both concepts. The following two sections will
- discuss two types of Workflows which are in use by two Zope
- products: DCWorkflow and OpenFlow. Both are described in full detail
- in <xref linkend="workflow-engines" />.
+ goal to unify both concepts. While the following two sections
+ discuss two types of workflows which are in use by two Zope products
+ (DCWorkflow and OpenFlow), AlphaFlow shares the ground with the
+ activity-oriented workflow type. It goes a bit further, by
+ giving activities more responsibilities to achieve more scalibility.
+ AlphaFlow is described in full detail in <xref linkend="alphaflow"
+ />, DCWorkflow and OpenFlow in <xref linkend="workflow-engines"
/>.
</para>
<remark><!-- XXX -->Just shortly introduce OpenFlow and
DCWorkflow?</remark>
(at)(at) -34,10 +37,10 (at)(at)
</indexterm>
<para>
- Content-oriented Workflow systems place the content-object, a
- document for example, in the center of the Workflow process. Each
- Workflow step will alter the content-object in a certain way –
- without a content-object no Workflow would be possible. Every
+ Content-oriented workflow systems place the content-object, a
+ document for example, in the center of the workflow process. Each
+ workflow step will alter the content-object in a certain way –
+ without a content-object no workflow would be possible. Every
content-object managed by DCWorkflow has an initial state, as well
as triggers, scripts and a destination state for each transition.
Guards are checking permissions, roles and Python expressions to
(at)(at) -46,15 +49,15 (at)(at)
state dependent.
</para>
<para>
- The Workflow definitions for this type are mostly adapted from
+ The workflow definitions for this type are mostly adapted from
write-and-review processes in publishing companies. <xref
linkend="figure-document-based-workflow" /> illustrates the
- content-oriented Workflow type with an example document.
+ content-oriented workflow type with an example document.
</para>
<figure id='figure-document-based-workflow'>
<title>
- Illustration of a content-oriented Workflow type
+ Illustration of a content-oriented workflow type
</title>
<mediaobject>
<imageobject role='tex'>
(at)(at) -95,23 +98,24 (at)(at)
point is not the document, but a task. The advantage is, that
process definitions can describe cases without documents.
For example, if you need a passport for traveling to a foreign
- country, what will the Workflow process definition in a
- content-oriented Workflow type be? Without a document – the
+ country, what will the workflow process definition in a
+ content-oriented workflow type be? Without a document – the
passport – no process definition can be setup, but thinking in
terms of <quote>activities</quote> we can easily model tasks
like:
<quote>obtain passport photographs</quote>,
<quote>take a birth
certificate</quote> etc. Therefore, it's possible to use activity
- based Workflow types to <quote>simulate</quote> a document
based
+ based workflow types to <quote>simulate</quote> a document
based
workflow.
</para>
<para>
- The implementation of activity based Workflow systems can be
+ The implementation of activity based workflow systems can be
differentiated into activity and controller based approaches. The
main difference between concepts is the self sustaining work items
for the activity based concept. The result is a more flexible flow
control than the monolithic controller based approaches would be.
<xref linkend="figure-workflow-implementation-concepts" />
illustrates both concepts.
+ <remark><!-- XXX --> possible candidate beeing
removed</remark>
AlphaFlow uses the activity based concept, which
leads to:
<itemizedlist>
(at)(at) -140,7 +144,7 (at)(at)
<figure id="figure-workflow-implementation-concepts">
<title>
- This figure illustrates a controller-based Workflow
+ This figure illustrates a controller-based workflow
implementation.
The communication between work items is managed by the
controller, illustrated by a PC. The controller manages the
(at)(at) -149,7 +153,7 (at)(at)
a news item and an article (document). The controller
generates two work items for both reviewers: one is about
reviewing the article and one about reviewing the news item.
- It is now Workflow depended how the audit proceeds. For
+ It is now workflow depended how the audit proceeds. For
example: both people need to review the document, before the
controller creates a work item for the publisher indicating
the object is ready for publishing.
(at)(at) -170,9 +174,9 (at)(at)
<figure id="figure-workflow-implementation-controller-based">
<title>
- The figure illustrates an activity-based Workflow
+ The figure illustrates an activity-based workflow
implementation.
- The Workflow process definition is the
+ The workflow process definition is the
same as described in (a). Everything works
the same as the controller based implementation, except that
each work item has it's own decision space where it can
Modified:
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/requirements/considered-problems.xml Tue
Aug 30 15:26:33 2005
(at)(at) -31,7 +31,7 (at)(at)
<listitem>
<para>
The workflow definition will be visualised as a graph. The more
- activities the graph contains the less overviewable it is. The
+ activities the graph contains the less concise it is. The
goal should be, that the rendered graph is overviewable as
possible. To achieve that goal, I considered two possible
solutions:
(at)(at) -174,6 +174,15 (at)(at)
example, using icons, different forms or colors wouldn't help to
achieve an overviewable graph if the number of activities increases
significantly. To gain the best effect and to fulfill the goals a
- combination of various solutions is needed.
+ combination of various solutions is needed. To quote
+ <citation>Raskin02</citation>:
+ <blockquote>
+ <attribution>Jef Raskin</attribution>
+ <para>
+ When using a product to help you do a task, the
+ product should only help and never distract you from
+ the task.
+ </para>
+ </blockquote>
</para>
</sect1>
Modified: misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-gef.xml Tue Aug
30 15:26:33 2005
(at)(at) -6,7 +6,7 (at)(at)
linkend="editor-technologies-gef" />.</title>
<tgroup cols='2' colsep='1' rowsep='1'>
<colspec colname='empty' align='left' />
- <colspec colname='description' align='justify'/>
+ <colspec colname='description' colwidth="10cm" />
<thead>
<row>
<entry></entry>
(at)(at) -49,6 +49,10 (at)(at)
<entry>none</entry>
</row>
<row>
+ <entry>Visualization component</entry>
+ <entry>Draw2D</entry>
+ </row>
+ <row>
<entry>implemented in</entry>
<entry>Java</entry>
</row>
(at)(at) -57,18 +61,9 (at)(at)
<entry>none</entry>
</row>
<row>
- <entry>supported vector-based formats</entry>
- <entry>not by GEF, possible with external Java
libraries</entry>
- </row>
- <row>
- <entry>supported pixel-based formats</entry>
+ <entry>supported graphic formats</entry>
<entry>not by GEF, possible with external Java
libraries</entry>
</row>
- <row>
- <entry>other provided formats</entry>
- <entry>not by GEF, depends on external Java libraries
- </entry>
- </row>
</tbody>
</tgroup>
</table>
Modified:
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-graphviz.xml Tue
Aug 30 15:26:33 2005
(at)(at) -8,7 +8,7 (at)(at)
</title>
<tgroup cols='2' colsep='1' rowsep='1'>
<colspec colname='empty' align="left"/>
- <colspec colname='description' colwidth="11cm" />
+ <colspec colname='description' colwidth="10cm" />
<thead>
<row>
<entry></entry>
(at)(at) -48,6 +48,10 (at)(at)
<entry>none</entry>
</row>
<row>
+ <entry>Visualization component</entry>
+ <entry>internal</entry>
+ </row>
+ <row>
<entry>implemented in</entry>
<entry>C</entry>
</row>
(at)(at) -62,20 +66,13 (at)(at)
</entry>
</row>
<row>
- <entry>supported vector-based formats</entry>
- <entry>PostScript, SVG, FIG, Mif, HPGl, PCL
- </entry>
- </row>
- <row>
- <entry>supported pixel-based formats</entry>
- <entry>PNG, GIF, JPEG</entry>
- </row>
- <row>
- <entry>other provided formats</entry>
- <entry>IMAP (imagemap files for httpd servers that mark out
- rectangles for each node that has a non-null
- <quote>href</quote> attribute), CMAPX (client-side
imagemap
- for use in HTML and XHTML)
+ <entry>supported graphic formats</entry>
+ <entry>
+ PostScript, SVG, FIG, Mif, HPGl, PCL, PNG, GIF, JPEG, IMAP
+ (imagemap files for httpd servers that mark out rectangles
+ for each node that has a non-null <quote>href</quote>
+ attribute), CMAPX (client-side imagemap for use in HTML and
+ XHTML)
</entry>
</row>
</tbody>
Modified: misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/tables/table-editor-jgraph.xml Tue
Aug 30 15:26:33 2005
(at)(at) -8,7 +8,7 (at)(at)
</title>
<tgroup cols='2' colsep='1' rowsep='1'>
<colspec colname='empty' align='left' />
- <colspec colname='description' align='justify'/>
+ <colspec colname='description' align="left"/>
<thead>
<row>
<entry></entry>
(at)(at) -49,6 +49,10 (at)(at)
<entry>none</entry>
</row>
<row>
+ <entry>Visualization component</entry>
+ <entry>internal</entry>
+ </row>
+ <row>
<entry>implemented in</entry>
<entry>Java</entry>
</row>
(at)(at) -57,15 +61,7 (at)(at)
<entry>none</entry>
</row>
<row>
- <entry>supported vector-based formats</entry>
- <entry>not by JGraph, depends on external Java
libraries</entry>
- </row>
- <row>
- <entry>supported pixel-based formats</entry>
- <entry>not by JGraph, depends on external Java
libraries</entry>
- </row>
- <row>
- <entry>other provided formats</entry>
+ <entry>supported graphic formats</entry>
<entry>not by JGraph, depends on external Java
libraries</entry>
</row>
</tbody>
Modified:
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/tables/table-technologies-comparison.xml Tue
Aug 30 15:26:33 2005
(at)(at) -89,7 +89,15 (at)(at)
</entry>
<entry>
<emphasis role="bold">
- Platform Dependencies
+ Platform Dependencies<footnote>
+ <para>
+ This parameter messures, how dependent a technology on
+ a platform is. <quote>+++</quote> means totally
+ independent and therefore available on a wide range of
+ platforms, <quote>+</quote> dependents only on
+ one platform.
+ </para>
+ </footnote>
</emphasis>
</entry>
<entry>
(at)(at) -245,7 +253,7 (at)(at)
<entry>++</entry>
<entry>+++</entry>
- <entry>+</entry>
+ <entry>—</entry>
<entry>++</entry>
<entry>+</entry>
(at)(at) -256,7 +264,7 (at)(at)
<entry>++</entry>
<entry>+++</entry>
- <entry>+</entry>
+ <entry>—</entry>
<entry>+</entry>
<entry>+</entry>
Modified: misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/frameworks.xml Tue Aug
30 15:26:33 2005
(at)(at) -241,7 +241,15 (at)(at)
<listitem>
<para>
an extended set of form features provided by the HTML 4.01
- specification by the W3C. It provides new DOM interfaces,
+ specification by the W3C. It provides new
+ DOM<footnote>
+ <para>
+ The <emphasis>D</emphasis>ocument <emphasis
+ role="bold">O</emphasis>bject <emphasis
+ role="bold">M</emphasis>odell is a programming
interface
+ for accessing XML node objects.
+ </para>
+ </footnote> interfaces,
events, XML submission and initialization of forms. <!-- XXX
Xforms -->
</para>
Modified:
misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/graph-components.xml Tue
Aug 30 15:26:33 2005
(at)(at) -102,16 +102,24 (at)(at)
see <ulink url="http://www.eclipse.org/" />
</para>
</footnote>. It splits into two plug-ins, providing the
- rendering toolkit for displaying graphics and a controller
+ rendering toolkit for displaying graphics (Draw2D) and a controller
framework for mapping the business model to a view. The main
purpose for using the GEF is to develop applications which deal
with diagrams, such as a flow chart editor. Thus, it's a possible
aspirant for building a graphical workflow editor.
</para>
<para>
- The main drawback of the GEF is the layout machinery which is not
- as powerfull as the GraphViz tools described in <xref
- linkend="editor-technologies-graphviz" />.
+ Unfortunately neither the homepage nor other documentation
+ describes the feature set of the graph Draw2D visualization
+ component. The main strengths of the GEF are the provided
+ functionality to develop interactive editors based on common
+ diagrams vor the visualization (e.g. UML diagrams).
+ <citation>Behrens05</citation> states<footnote>
+ <para>
+ cp. p. 118 first paragraph.
+ </para>
+ </footnote> difficulties the developer faces if there is the need
+ of drawing complex graphs.
</para>
<xi:include href="../tables/table-editor-gef.xml" />
</sect2>
Modified: misc/trunk/WorkflowEditor/docbook/stylesheets/titlepage.tex
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/stylesheets/titlepage.tex (original)
+++ misc/trunk/WorkflowEditor/docbook/stylesheets/titlepage.tex Tue Aug 30
15:26:33 2005
(at)(at) -16,6 +16,7 (at)(at)
Abteilung Köthen\\
Institute for Computer Sience} \\[3 cm]
\normalsize{
+ % Advisor
\begin{tabular}{p{6cm}p{4cm}p{6cm}}
R\'oman Joost & & {\sc Prof. Dr. Breitschuh} \\
Matrikelnummer: 2002900 & & {\sc Prof. Dr. Fissgus}\\
|
SVN: r3336 - in misc/trunk/WorkflowEditor/docbook: . src src/alphaflow src/bibliography src/editor
Roman Joost <rj(at)gocept.com> |
2005-08-31 12:54:06 |
[ FULL ]
|
Author: roman
Date: Wed Aug 31 12:53:48 2005
New Revision: 3336
Added:
misc/trunk/WorkflowEditor/docbook/src/alphaflow/zope-integration.xml
Modified:
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/abstract.xml
misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml
misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml
misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml
misc/trunk/WorkflowEditor/docbook/src/diplom.xml
misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml
misc/trunk/WorkflowEditor/docbook/src/editor/first-mockup.xml
misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml
Log:
2005-08-31 Roman Joost <rj(at)gocept.com>
* src/abstract.xml: added remark
* src/editor/first-mockup.xml: removed the figure, which don't
have any surplus for the reader IMHO
* src/editor/implementation.xml
* src/editor/conclusions.xml
* src/bibliography/technologies.xml
* src/alphaflow/intro.xml
* src/alphaflow/process-state.xml: corrected the way the process
instance is described, which was wrong
* src/diplom.xml
* src/alphaflow/zope-integration.xml: a few words about the
AlphaFlow Zope integration
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Wed Aug 31 12:53:48 2005
(at)(at) -1,3 +1,21 (at)(at)
+2005-08-31 Roman Joost <rj(at)gocept.com>
+
+ * src/abstract.xml: added remark
+
+ * src/editor/first-mockup.xml: removed the figure, which don't
+ have any surplus for the reader IMHO
+
+ * src/editor/implementation.xml
+ * src/editor/conclusions.xml
+ * src/bibliography/technologies.xml
+ * src/alphaflow/intro.xml
+ * src/alphaflow/process-state.xml: corrected the way the process
+ instance is described, which was wrong
+
+ * src/diplom.xml
+ * src/alphaflow/zope-integration.xml: a few words about the
+ AlphaFlow Zope integration
+
2005-08-30 Roman Joost <rj(at)gocept.com>
* src/appendix-screenshots.xml
Modified: misc/trunk/WorkflowEditor/docbook/src/abstract.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/abstract.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/abstract.xml Wed Aug 31 12:53:48 2005
(at)(at) -13,4 +13,8 (at)(at)
these findings, the subject of this thesis now covers the
feasibility of implementing a graphical editor.
</para>
+ <remark>
+ Thesis is build on a technical examination instead of a theoretical
+ e.g. graph drawing problems.
+ </remark>
</abstract>
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml Wed Aug 31
12:53:48 2005
(at)(at) -27,17 +27,18 (at)(at)
</para>
<para>
On the basis of <xref linkend="alphaflow-concept" />, i'll explain
- the concept in short. An instance of a process definition is a
- characteristic type<footnote>
+ the concept in short. An instance of a process definition<footnote>
<para>
- Implemented as a folder in Zope, which holds all activity
- objects defined by the process definition.
+ To be more precise: The process definition is implemented as a
+ folderish object for Zope, which holds all activity objects
+ defined by the process definition.
</para>
- </footnote> with a various amount of work items. Each work
- item is an instance of an activity. Process instances and work items
- can fall into different states, which are more elaborated in the
- succeeding sections. The user, who defines the process or workflow
- definition, modells the workflow with activity
+ </footnote> is a object with a various amount of activities. After
+ executing the process definition, the instanciation process creates
+ a process instance including it's work items. Process instances and
+ work items can fall into different states, which are more elaborated
+ in the succeeding sections. The user, who defines the process or
+ workflow definition, modells the workflow with activity
definitions<footnote>
<para>
cp. <xref linkend='alarm_review' />
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/process-state.xml Wed Aug
31 12:53:48 2005
(at)(at) -8,16 +8,10 (at)(at)
</indexterm>
<para>
- As I already mentioned in the introduction of
- AlphaFlow<footnote>
- <para>
- cp. <xref linkend="alphaflow-what-is" />
- </para>
- </footnote>, a
- process instance is an instance of the process definition object.
- The instance is created during the import of the process definition.
- There can be several activities defined for a process startup. These
- activites are defined by the
+ Process instances are created by executing the process definition,
+ which is either imported or defined via the Zope Management
+ Interface. There can be several activities defined for a process
+ startup. These activites are defined by the
<parameter>startActivity</parameter><footnote>
<para>
cp. <xref linkend="alarm_review" />
Added: misc/trunk/WorkflowEditor/docbook/src/alphaflow/zope-integration.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/zope-integration.xml Wed
Aug 31 12:53:48 2005
(at)(at) -0,0 +1,23 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1 id="alphaflow-zope-integration">
+ <title lang='en'>Zope Integration</title>
+ <indexterm>
+ <primary>AlphaFlow</primary>
+ <secondary lang="en">Zope Integration</secondary>
+ </indexterm>
+
+ <para>
+ AlphaFlow is coupled very close to Zope. It provides a workflow
+ manager, where developers or administrators can import process
+ definitions written in AlphaFlows process definition language. The
+ workflow manager divides in several parts:
+ <quote>Definitions</quote>, <quote>Import</quote>
and an
+ <quote>Instances</quote> view makes it easier for developers
to keep
+ an overview. Each process definition can be administrated through
+ it's smallest pieces – the activity definitions. This applies to
+ process instances with it's work-items as well. The There is already
+ a graphical overview implemented provided by the process definition
+ and the process instance.
+ </para>
+</sect1>
Modified: misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/bibliography/technologies.xml Wed Aug
31 12:53:48 2005
(at)(at) -80,4 +80,21 (at)(at)
iX – Magazin für professionelle Informationstechnik, Issue 7/2005
</releaseinfo>
</biblioentry>
+
+ <biblioentry>
+ <abbrev>Sarissa05</abbrev>
+ <author>
+ <firstname>Emmanuil</firstname>
+ <surname>Batsis</surname>
+ </author>
+ <copyright>
+ <year>2004,2005</year>
+ <holder>Emmanuil Batsis</holder>
+ </copyright>
+ <title>Sarissa – API specification</title>
+ <releaseinfo>
+ <ulink url="http://sarissa.sourceforge.net/doc/"
/> [accessed
+ 2005-08-31]
+ </releaseinfo>
+ </biblioentry>
</bibliodiv>
Modified: misc/trunk/WorkflowEditor/docbook/src/diplom.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/diplom.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/diplom.xml Wed Aug 31 12:53:48 2005
(at)(at) -7,11 +7,6 (at)(at)
<bookinfo>
<title lang="en">Diploma thesis</title>
<title lang="de">Diplomarbeit</title>
- <subtitle lang="de">
- Entwicklung eines grafischen Werkzeugs zur Definition von
- Prozessen zur Verwendung in der Workflow Engine
- <emphasis>AlphaFlow</emphasis>
- </subtitle>
<subtitle lang="en">
Feasability study on a graphical Workflow Editor based on
the Workflow Management System <quote>AlphaFlow</quote>
(at)(at) -75,6 +70,7 (at)(at)
<chapter id="alphaflow">
<title>AlphaFlow</title>
<xi:include href="alphaflow/intro.xml" />
+ <xi:include href="alphaflow/zope-integration.xml" />
<xi:include href="alphaflow/activities.xml" />
<xi:include href="alphaflow/built-in-activities.xml" />
<xi:include href="alphaflow/pdl.xml" />
Modified: misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/conclusions.xml Wed Aug 31
12:53:48 2005
(at)(at) -97,26 +97,8 (at)(at)
</listitem>
</varlistentry>
</variablelist>
-
- <para>
- The backend consists of the Zope Application Framework which
- provides the data storage and AlphaFlow functionality. The frontend
- requires a Mozilla Firefox 2 compatible browser which supports
- rendering SVG graphics nativly. The interaction is provided by
- The technical basis will be an XHTML page including SVG statements.
- Javascript provides interaction between the frontend and the
- user. The JavaScript library
- <emphasis>Sarissa</emphasis><footnote>
- <para>
- <ulink
- url="http://sarissa.sourceforge.net/doc/overview-summary.html"
- /> [accessed 2005-08-30]
- </para>
- </footnote> will be
- used to achieve the asynchronous communication between frontend and
- backend. Objects resieved and send to the server need to be
- serialized to XML.
- </para>
+
+ <remark><!-- XXX --> a possible aspirant for beeing
removed</remark>
<figure id='figure-usability-interface-concept'>
<title>
The picture shows the interface gained from the usability tests.
Modified: misc/trunk/WorkflowEditor/docbook/src/editor/first-mockup.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/editor/first-mockup.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/first-mockup.xml Wed Aug 31
12:53:48 2005
(at)(at) -17,9 +17,8 (at)(at)
<para>
After working with AlphaFlow a while, I started – during a discussion
with Christian Theune – sketching out how the Workflow Editor would
- look alike. <xref linkend="figure-editor-first-mockup" /> shows the
- sketch in ASCII art with its features and how it would visualize the
- diagrams.
+ look alike. The sketch was a simple ASCII art figure with its
+ features and how it would visualize the diagrams.
</para>
<para>
The editor allows limited interaction with the workflow diagram. An
(at)(at) -38,7 +37,7 (at)(at)
"global" conclusion section??? XXX -->
</para>
- <figure id="figure-editor-first-mockup">
+ <!--<figure id="figure-editor-first-mockup">
<title>A first mockup of the graphical Workflow
Editor.</title>
<screenco>
<areaspec units="linerange">
(at)(at) -59,7 +58,7 (at)(at)
<callout arearefs="panel">
<para>
The panel which holds the AlphaFlow activities, grouped by
- appropriateness.<!-- XXX -->
+ appropriateness.
</para>
</callout>
(at)(at) -78,5 +77,5 (at)(at)
</calloutlist>
</screenco>
- </figure>
+ </figure> -->
</sect1>
Modified: misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/implementation.xml Wed Aug 31
12:53:48 2005
(at)(at) -8,8 +8,112 (at)(at)
<secondary>Implementation</secondary>
</indexterm>
+ <figure id='figure-prototype-concept'>
+ <title>
+ The figure shows the concept of the Prototype and the intended
+ savings potential of development time.
+ </title>
+ <mediaobject>
+ <imageobject role='tex'>
+ <imagedata fileref='images/prototype-concept.pdf'
+ width="10cm" scalefit='1' />
+ </imageobject>
+ <imageobject role='html'>
+ <imagedata fileref='images/prototype-concept.pdf' scalefit="1"
/>
+ </imageobject>
+ <caption>
+ AlphaFlow generates a dot file format for GraphViz by traversing
+ through all defined activities. The dot file is converted to a
+ SVG format and rendered by the frontend: Mozilla Firefox. The
+ only development effort is to create the user interface with
+ Javascript. The development of the user interface proves to be
+ easy because of SVG's modularity and the native SVG support by
+ Mozilla Firefox. The browser provides full access to every
+ displayed node in the browser; either XHTML or SVG elements.
+ That makes it easy for small changes by the user to re-render
+ only parts of the user interface.
+ </caption>
+ </mediaobject>
+ </figure>
+
+ <para>
+ I've chosen a mix of the introduced technologies
+ in <xref linkend="technologies" /> for the implementation of the
+ graphical editor, which are in short:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>The Backend</term>
+ <listitem>
+ <para>
+ is driven by the Zope Application Framework and AlphaFlow. The
+ latter one generates a GraphViz format, which in turn creates a
+ GIF or an SVG file for the graphical editor.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>The Frontend</term>
+ <listitem>
+ <para>
+ builds upon the native SVG implementation of Mozilla Firefox
+ 2<footnote>
+ <para>
+ During writing of this thesis, there were only developer
+ builds available. A stable version of Mozilla Firefox 2
+ should be available in 2006.
+ </para>
+ </footnote>. This will
+ save development time, because the user interface interaction is
+ easily provided by JavaScript and the Mozilla Firefox 2 APIs.
+ They provide access to XHTML and SVG elements easily.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ I'll describe the JavaScript component in more detail here, because
+ that is actually the most work for the developer. Please consult
+ <xref linkend="figure-prototype-concept" /> as well, which should
+ make the intended result more clear. The Mozilla DOM API provides
+ methods for synchronous and asynchronous loading of XML documents.
+ In conjunction with the JavaScript library
<quote>Sarissa</quote> the
+ following items are implemented:
+ <itemizedlist>
+ <listitem>
+ <para>
+ an asynchronous download of XML data
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the transformation of the XML data to HTML via XSLT
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ methods for collecting user changes. Those changes need to be
+ encapsulated in XML as well and send back to the server.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
<para>
- I spent approx. five weeks for implementing the prototype.
+ I spent approx. three weeks on implementing these methods.
+ The current JavaScript implementation
+ in Mozilla is rather unstable. I invested much time to hack around
+ the implementation holes and spend additionally time to add
+ workorounds provided by third-party JavaScript
+ projects<footnote>
+ <para>
+ A great help was the Kupu project here. I appreciate espially
+ the help from Guido Wesdorp from Infrae.
+ </para>
+ </footnote> This makes the user
+ interface error-prone unfortunately. Writing unittests for the
+ implemented JavaScript methods is limited and therefore quality
+ assurance have lacks of correct JavaScript implementation.
</para>
</sect1>
|
SVN: r3341 - in misc/trunk/WorkflowEditor/docbook: . src src/alphaflow src/editor src/existing src/introduction src/requirements src/technologies src/usability
Roman Joost <rj(at)gocept.com> |
2005-08-31 15:16:49 |
[ FULL ]
|
Author: roman
Date: Wed Aug 31 15:16:28 2005
New Revision: 3341
Added:
misc/trunk/WorkflowEditor/docbook/src/alphaflow/summary.xml
misc/trunk/WorkflowEditor/docbook/src/editor/summary.xml
misc/trunk/WorkflowEditor/docbook/src/existing/intro.xml
misc/trunk/WorkflowEditor/docbook/src/introduction/summary.xml
misc/trunk/WorkflowEditor/docbook/src/requirements/intro.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/summary.xml
misc/trunk/WorkflowEditor/docbook/src/usability/summary.xml
misc/trunk/WorkflowEditor/docbook/src/usability/usability-intro.xml
Modified:
misc/trunk/WorkflowEditor/docbook/ChangeLog
misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml
misc/trunk/WorkflowEditor/docbook/src/diplom.xml
misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml
misc/trunk/WorkflowEditor/docbook/src/usability/cognitivewalkthrough.xml
misc/trunk/WorkflowEditor/docbook/src/usability/intro.xml
Log:
2005-08-31 Roman Joost <rj(at)gocept.com>
* src/introduction/summary.xml
* src/diplom.xml
* src/technologies/intro.xml
* src/technologies/summary.xml
* src/requirements/intro.xml
* src/editor/summary.xml
* src/existing/intro.xml
* src/usability/cognitivewalkthrough.xml
* src/usability/intro.xml
* src/usability/summary.xml
* src/usability/usability-intro.xml
* src/alphaflow/intro.xml
* src/alphaflow/summary.xml: added and rephrased introduction and
summarizing sections to each chapter
Modified: misc/trunk/WorkflowEditor/docbook/ChangeLog
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/ChangeLog (original)
+++ misc/trunk/WorkflowEditor/docbook/ChangeLog Wed Aug 31 15:16:28 2005
(at)(at) -1,5 +1,22 (at)(at)
2005-08-31 Roman Joost <rj(at)gocept.com>
+ * src/introduction/summary.xml
+ * src/diplom.xml
+ * src/technologies/intro.xml
+ * src/technologies/summary.xml
+ * src/requirements/intro.xml
+ * src/editor/summary.xml
+ * src/existing/intro.xml
+ * src/usability/cognitivewalkthrough.xml
+ * src/usability/intro.xml
+ * src/usability/summary.xml
+ * src/usability/usability-intro.xml
+ * src/alphaflow/intro.xml
+ * src/alphaflow/summary.xml: added and rephrased introduction and
+ summarizing sections to each chapter
+
+2005-08-31 Roman Joost <rj(at)gocept.com>
+
* src/abstract.xml: added remark
* src/editor/first-mockup.xml: removed the figure, which don't
Modified: misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/intro.xml Wed Aug 31
15:16:28 2005
(at)(at) -6,7 +6,8 (at)(at)
<primary>AlphaFlow</primary>
<secondary lang="en">Introduction</secondary>
</indexterm>
-
+
+ <remark><!--XXX--> highlights?</remark>
<para lang="en">
AlphaFlow was designed from the beginning to be as simple,
flexible and customizable as possible. The concept of AlphaFlow
Added: misc/trunk/WorkflowEditor/docbook/src/alphaflow/summary.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/alphaflow/summary.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,16 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1>
+ <title>Summary</title>
+ <para>
+ This chapter discussed the workflow management system AlphaFlow for
+ Zope in every detail. I firstly introduced you upon which concept the
+ system is build on. AlphaFlow provides a rich set of predefined
+ activities, which become to work-items visible by the user during
+ instanciation. The instances, either the process instance and the
+ work items can fall into various states. This makes it possible to
+ control each particular state of the process runtime. I covered also
+ in short AlphaFlow's own process definition language, which tries to
+ be as concise as possible.
+ </para>
+</sect1>
Modified: misc/trunk/WorkflowEditor/docbook/src/diplom.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/diplom.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/diplom.xml Wed Aug 31 15:16:28 2005
(at)(at) -47,6 +47,7 (at)(at)
<xi:include href="introduction/terms.xml" />
<xi:include href="introduction/workflow-patterns.xml" />
<xi:include href="introduction/workflow-types.xml" />
+ <xi:include href="introduction/summary.xml" />
</chapter>
<chapter id="technologies">
(at)(at) -59,10 +60,12 (at)(at)
<xi:include href="technologies/fileformats.xml" />
<xi:include href="technologies/frontend.xml" />
<xi:include href="technologies/animation-interaction.xml" />
+ <xi:include href="technologies/summary.xml" />
</chapter>
<chapter>
<title>Existing Products</title>
+ <xi:include href="existing/intro.xml" />
<xi:include href="existing/engines.xml" />
<xi:include href="existing/editors.xml" />
</chapter>
(at)(at) -73,15 +76,17 (at)(at)
<xi:include href="alphaflow/zope-integration.xml" />
<xi:include href="alphaflow/activities.xml" />
<xi:include href="alphaflow/built-in-activities.xml" />
- <xi:include href="alphaflow/pdl.xml" />
<xi:include href="alphaflow/process-state.xml" />
<xi:include href="alphaflow/work-item-state.xml" />
<xi:include href="alphaflow/special-work-items.xml" />
+ <xi:include href="alphaflow/pdl.xml" />
+ <xi:include href="alphaflow/summary.xml" />
<!-- XXX <xi:include href="alphaflow/editor-benefits.xml" />
-->
</chapter>
<chapter>
<title>Requirements</title>
+ <xi:include href="requirements/intro.xml" />
<xi:include href="requirements/mandatory-features.xml" />
<xi:include href="requirements/considered-problems.xml" />
</chapter>
(at)(at) -89,12 +94,14 (at)(at)
<chapter>
<title>Usability Aspects</title>
<xi:include href="usability/intro.xml" />
+ <xi:include href="usability/usability-intro.xml" />
<xi:include href="usability/gestalt.xml" />
<xi:include href="usability/engineering.xml" />
<xi:include href="usability/context-of-use.xml" />
<xi:include href="usability/tasks.xml" />
<xi:include href="usability/papermockups.xml" />
<xi:include href="usability/cognitivewalkthrough.xml" />
+ <xi:include href="usability/summary.xml" />
</chapter>
<chapter>
(at)(at) -105,6 +112,7 (at)(at)
<xi:include href="usability/papermockup-results.xml" />
<xi:include href="editor/conclusions.xml" />
<xi:include href="editor/implementation.xml" />
+ <xi:include href="editor/summary.xml" />
</chapter>
<chapter>
Added: misc/trunk/WorkflowEditor/docbook/src/editor/summary.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/editor/summary.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,8 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1>
+ <title>Summary</title>
+ <para>
+ This chapter described the way up...
+ </para>
+</sect1>
Added: misc/trunk/WorkflowEditor/docbook/src/existing/intro.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/existing/intro.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,12 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<highlights>
+ <para>
+ This chapter introduces the reader to existing workflow editors and
+ workflow components. The latter section deals only with workflow
+ components, which is necessary to understand the current situation
+ of available workflow engines. The lack of a scalable workflow
+ managment system for Zope was one of the motivation points to build
+ AlphaFlow.
+ </para>
+</highlights>
Added: misc/trunk/WorkflowEditor/docbook/src/introduction/summary.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/introduction/summary.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,12 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1>
+ <title>Summary</title>
+ <para>
+ By now you should have a basic understanding of what workflow,
+ workflow management means. I introduced you to the standardization
+ process of workflows by describing patterns and types. The latter
+ one in particular are necessary to understand the concept behind
+ AlphaFlow.
+ </para>
+</sect1>
Added: misc/trunk/WorkflowEditor/docbook/src/requirements/intro.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/requirements/intro.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,9 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<highlights>
+ <para>
+ I will discuss the features which are mandatory for every piece of
+ software. The chapter also covers a section of considered problems
+ which came up before any line of code had been written.
+ </para>
+</highlights>
Modified: misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/intro.xml Wed Aug 31
15:16:28 2005
(at)(at) -1,7 +1,7 (at)(at)
<?xml version='1.0' encoding="UTF-8" ?>
<highlights>
- <para lang="en">
+ <para>
Based on a rendering pipeline, I'll introduce several frameworks,
technologies and products which provide the necessary functionality
for building a graphical editor. The challenge is to
Added: misc/trunk/WorkflowEditor/docbook/src/technologies/summary.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/technologies/summary.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,12 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1>
+ <title>Summary</title>
+ <para>
+ You should have a basic understanding of the parts involved for a
+ graphical editor. I introduced you in the rendering pipeline and
+ based upon the technologies which provide a development basis. The
+ technologies divide into frameworks and languages for modelling
+ processes and user interfaces.
+ </para>
+</sect1>
Modified:
misc/trunk/WorkflowEditor/docbook/src/usability/cognitivewalkthrough.xml
==============================================================================
---
misc/trunk/WorkflowEditor/docbook/src/usability/cognitivewalkthrough.xml (original)
+++
misc/trunk/WorkflowEditor/docbook/src/usability/cognitivewalkthrough.xml Wed
Aug 31 15:16:28 2005
(at)(at) -15,7 +15,7 (at)(at)
Based on tasks, see <xref
linkend="usability-tasks" />, users are walking through a user
interface and try to solve these tasks. This walkthrough can be
- applied to a prototype as well as on working user interfaces. Each
+ applied to a prototype as well as on a working user interfaces. Each
step which is performed by the user is recorded to find out,
where the interface blocks the user from completing his task.
A too convoluted function sequence indicates, that the interface
Modified: misc/trunk/WorkflowEditor/docbook/src/usability/intro.xml
==============================================================================
--- misc/trunk/WorkflowEditor/docbook/src/usability/intro.xml (original)
+++ misc/trunk/WorkflowEditor/docbook/src/usability/intro.xml Wed Aug 31
15:16:28 2005
(at)(at) -1,134 +1,15 (at)(at)
<?xml version='1.0' encoding="UTF-8" ?>
-<sect1 id="usability-intro">
- <title lang='en'>Introduction to Usability</title>
-
+<highlights>
<para>
- The editor should provide an opportunity for creating process
- definitions visually, instead of writing XML code. To get a usable
- product, we used Usability methods and the expertise from Ellen
- Reitmayr (Releventive AG, Berlin).
+ After the previous introductorily chapters of terms, technologies
+ and even AlphaFlow, usability covers the more social part of the
+ graphical editor development. Once the reader already used software,
+ he probably faced the situation of not beeing able to use the
+ software. It felt unintuitive to use, it behaved oddly and was
+ near impossible to use. Usability provides methods to develop
+ software by including users in the development process. I'll
+ introduce shortly the usability term, which methods it provides and
+ which I used during the development of the graphical editor.
</para>
-
- <indexterm>
- <primary>Usability</primary>
- <secondary>Components</secondary>
- </indexterm>
- <para>
- What <quote>Usability</quote> actually is, can not be better
- described as by <citation>Nielsen93</citation>:
- <blockquote>
- <attribution>Jakob Nielsen</attribution>
- <para>
- [...] Usability has multiple components and is traditionally
- associated with these five usability attributes<footnote>
- <para>
- cp. <citation>Nielsen93</citation> at page 26
- </para>
- </footnote>:
- <variablelist>
- <varlistentry>
- <term>Learnability</term>
- <listitem>
- <para>
- The system should be easy to learn so that the user can
- rapidly start getting some work done with the system.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Efficiency</term>
- <listitem>
- <para>
- The system should be efficient to use, so that once the
- user has learned the system, a high level of
- productivity is possible
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Memorability</term>
- <listitem>
- <para>
- The system should be easy to remember, so that the
- casual user is able to return to the system after some
- period of not having used it, without having to learn
- everything all over again.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Errors</term>
- <listitem>
- <para>
- The system should have a low error rate, so that users
- make few errors during the use of the system, and so
- that if they do make errors they can easily recover from
- them. Further, catastrophic errors must not occur.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Satisfaction</term>
- <listitem>
- <para>
- The system should be pleasant to use, so that users are
- subjectively satisfied when using it; they like it.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </para>
- </blockquote>
- </para>
-
- <indexterm>
- <primary>Usability</primary>
- <secondary>Benefits</secondary>
- </indexterm>
- <para>
- The benefits of using usability methods in the development
- lifecycle are:
- <itemizedlist>
- <listitem>
- <para>
- usable software increases user acceptance
- </para>
- </listitem>
- <listitem>
- <para>
- saves time and money
- </para>
- </listitem>
- <listitem>
- <para>
- generates new ideas
- </para>
- </listitem>
- <listitem>
- <para>
- leads into a better usable product
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- Integrating the usability methods, which are described in <xref
- linkend="usability-engineering" />, are not made once; it is an
- iterative process which helps that the implementation of the product
- is made with a minimum on errors. <!-- XXX yuck! wtf is that? -->
- To quote <citation>Nielsen93</citation>:
- <blockquote>
- <attribution>Jakob Nielsen</attribution>
- <para>
- Usability engineering is not a one-shot affair where the user
- interface is fixed up before the release of a product. Rather,
- usability engineering is a set of activities that ideally take
- place throughout the lifecycle of the product, with significant
- activities happening at the early stages before the user
- interface has even been designed.
- </para>
- </blockquote>
- </para>
-
-</sect1>
+</highlights>
Added: misc/trunk/WorkflowEditor/docbook/src/usability/summary.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/usability/summary.xml Wed Aug 31
15:16:28 2005
(at)(at) -0,0 +1,14 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1>
+ <title>Summary</title>
+ <para>
+ I introduced the reader to the <quote>usability</quote> term
as well
+ the basic principles of the Gestalt laws. Most of the user interface
+ creation has references to them. I elaborated the various methods of
+ usability engineering which we considered as worth to look at. I
+ setup a set of usability tasks which are used in the scenarious of
+ use and cognitive walkthroughs I've done. The results of the
+ usability tests are more elaborated in the succeeding chapter.
+ </para>
+</sect1>
Added: misc/trunk/WorkflowEditor/docbook/src/usability/usability-intro.xml
==============================================================================
--- (empty file)
+++ misc/trunk/WorkflowEditor/docbook/src/usability/usability-intro.xml Wed Aug
31 15:16:28 2005
(at)(at) -0,0 +1,134 (at)(at)
+<?xml version='1.0' encoding="UTF-8" ?>
+
+<sect1 id="usability-intro">
+ <title lang='en'>Introduction to Usability</title>
+
+ <para>
+ The editor should provide an opportunity for creating process
+ definitions visually, instead of writing XML code. To get a usable
+ product, we used Usability methods and the expertise from Ellen
+ Reitmayr (Releventive AG, Berlin).
+ </para>
+
+ <indexterm>
+ <primary>Usability</primary>
+ <secondary>Components</secondary>
+ </indexterm>
+ <para>
+ What <quote>Usability</quote> actually is, can not be better
+ described as by <citation>Nielsen93</citation>:
+ <blockquote>
+ <attribution>Jakob Nielsen</attribution>
+ <para>
+ [...] Usability has multiple components and is traditionally
+ associated with these five usability attributes<footnote>
+ <para>
+ cp. <citation>Nielsen93</citation> at page 26
+ </para>
+ </footnote>:
+ <variablelist>
+ <varlistentry>
+ <term>Learnability</term>
+ <listitem>
+ <para>
+ The system should be easy to learn so that the user can
+ rapidly start getting some work done with the system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Efficiency</term>
+ <listitem>
+ <para>
+ The system should be efficient to use, so that once the
+ user has learned the system, a high level of
+ productivity is possible
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Memorability</term>
+ <listitem>
+ <para>
+ The system should be easy to remember, so that the
+ casual user is able to return to the system after some
+ period of not having used it, without having to learn
+ everything all over again.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Errors</term>
+ <listitem>
+ <para>
+ The system should have a low error rate, so that users
+ make few errors during the use of the system, and so
+ that if they do make errors they can easily recover from
+ them. Further, catastrophic errors must not occur.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Satisfaction</term>
+ <listitem>
+ <para>
+ The system should be pleasant to use, so that users are
+ subjectively satisfied when using it; they like it.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
+ </blockquote>
+ </para>
+
+ <indexterm>
+ <primary>Usability</primary>
+ <secondary>Benefits</secondary>
+ </indexterm>
+ <para>
+ The benefits of using usability methods in the development
+ lifecycle are:
+ <itemizedlist>
+ <listitem>
+ <para>
+ usable software increases user acceptance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ saves time and money
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ generates new ideas
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ leads into a better usable product
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Integrating the usability methods, which are described in <xref
+ linkend="usability-engineering" />, are not made once; it is an
+ iterative process which helps that the implementation of the product
+ is made with a minimum on errors. <!-- XXX yuck! wtf is that? -->
+ To quote <citation>Nielsen93</citation>:
+ <blockquote>
+ <attribution>Jakob Nielsen</attribution>
+ <para>
+ Usability engineering is not a one-shot affair where the user
+ interface is fixed up before the release of a product. Rather,
+ usability engineering is a set of activities that ideally take
+ place throughout the lifecycle of the product, with significant
+ activities happening at the early stages before the user
+ interface has even been designed.
+ </para>
+ </blockquote>
+ </para>
+
+</sect1>
|
|
