Description
ebBP Editor User Manual has been also updated to address
the recent improvements in the ebBP Editor (the improved source code is uploaded to https://sourceforge.net/projects/freebxmlbp).
There are some significant improvements to the editor; like importing packages, on-the-fly validation, look and feel support, displaying the business activity sequence in a business collaboration.
The improvements to the ebBP Editor is realized under an European
Commission funded project RIDE (IST-4-027065-CA).
Here is the list of the enhancements to the ebBP Editor:
* XmlStylist, which is a part of the ebBP Editor, has the capability of creating and modifying any valid ebBP instances according to ebBP Technical Specification v2.0.3.
* XmlStylist is made user-friendly.
* Validation procedure in XmlStylist has been strengthened. After each modification and closure of XmlStylist, the available ebBP instance is subjected to a validation check.
* Packages, which are the modular ebBP elements, can be imported to an ebBP instance via XmlStylist.
* From Start to Completion (Success and/or Failure), the flow in a Business Collaboration can be visualized in the ebBP Editor. This version supports displaying Roles, Business Transaction Activities, Completion elements, and the links between those elements in a Business Collaboration "automatically" after XmlStylist generates a Process Specification. The widgets used for visualization are based on BPMN.
* Multiparty Collaborations are handled in this version.
* Look and Feel support is added.
* Splash screen is added.
* Note the difference that, XmlStylist can handle any ebBP instance, but the graphical component pane (tabbed pane) can handle only Process Specifications.
The future work that remains are:
* The visualized ebBP elements should be enriched in type. Collaboration Activity, Complex Business Transaction Activity etc. may be included to the set of displayable elements.
* The current version is tested with ebBP Technical Specification v2.0.3. Usage of another version of this document may cause unhandled exceptions.
* The graphical component pane should be improved in a user-friendly manner and also, the level of coupling between this module and XmlStylist module may be decreased.
* A communication bridge between ebXML Registries and the ebBP Editor can be constructed as a functionality of the ebBP Editor. Over this bridge, one can access ebBP instances in an ebXML Registry or upload a newly created instance to that registry.
* The ebBP Editor should have the web accessibility capability.
* More testing with real-life scenarios will definitely contribute to the overall quality of the tool.
