4 External Interface Specifications

4.1. User Interface

Mooshabaya being a workflow composition tool needs to have a rich user interface capable of
drag and drop style modeling. Existing XBaya user interface will be used or extended where
necessary to incorporate operations which will be needed in the course of adding mashup
generation support.
Corresponding to its main functionalities following user interface components will be present as
a minimal requirement.

UI component to register a new web service registry with XBaya.

Registering a new mashup server.

Service component pallet.

Workflow composition editor.

Monitoring component to monitor the status of the running workflows.

UI component to register a Tuple space for the tuples.

UI component to find relevant data feeds.

Tuple space API

The project Mooshabaya may include facilities to talk with server side tuple spaces which project
“Bissa” may provide. A possible use case of the tuple spaces for Mooshabaya would be to act as
another data source for data mashups as well as a web service response cache for performance
improvements. To utilize services provided by the tuple space implementation Mooshabaya
should be able to generate codes with published API s from “Bissa” project.

4.2. Detailed non-functional requirements

In addition to fulfilling functional requirements, a system is supposed to work and perform
under additional constraints and conditions which makes the application useful for real world
use cases. Mooshabaya is no exception to this rule. Since this application is involved with web
services and distributed computing areas several concerns which are typical to web services
domain have to be considered of.


Since the service calls across the network is almost always costly in terms of performance ,
caching of mashup data will be employed where necessary and feasible. In this regard the
mashup server may become vital as the central point in which all the mashup code is being run.
The data may be persisted to a database or a tuple space implementation so that it may be used
across several invocations of the workflow.
Other than that the user can get an idea of the performance of his workflow mashup using
XBaya graphical monitoring facility. By observing the workflow execution users may gain an
insight about any existing bottlenecks in the design.


For any wen considering that , mainly the Internet. Also authentication is necessary to identify
the source and the destination with certainty so that both parties can be asr both of these
transport let, whh provides data security and authentication in the form of encryption and
certificates. This level of security can be provided since related XMLHttpRequest, WSRequest
objects used in mashup data communications has HTTPS capabilities built in.

Ease of use

Since one of the motivations of XBaya project is to make it easier for users to create workflows
using graphical composition tools the same theme will be present in Mooshabaya as well. It will
strive to achieve minimal configuration and no code approach. Users will be able to drag and
drop components and quickly compose a useful workflow with minimal configurations. Then this
workflow can then be exported as a mashup and deployed to a mashup server of choosing. In
order to find services used in the composition XBaya will automatically fetch data from any user
given web service registry. Importing and deployment of mashup to the respective mashup
server can be automated as per the user requirements.

4.3. System Evolution

Mooshabaya will expand XBaya by providing it with mashup generation facilities. In this sense
this is an effort to combine mashup domain with workflow domain. Up until now mashups have
been mostly considered as a web data aggregation tool. But recently there has been some
research and enthusiasm in exploring ways as how to integrate mashup technologies with
business processes. So Mooshabaya will be filling this void by enabling developers to convert
workflows to mashups. So in this regards web service interactions within the generated mashups
will be dominant in carrying outlined workflows. Future directions of Mooshabaya would
possibly include following enhancements.

1 Currently Mooshabaya is a desktop based application. It can be made a web based
application with rich web based UI s. This may enable additional features such
collaborative editing of workflows by a developer team.
2 Business process mashups has been subject to some research recently. [1] Some avenues
can be explored as how Mooshabaya can facilitate use of business process mashups so
that it allows using reusable process fragments to be bundled, unbundled and re bundled
rapidly to model process workflows in innovative ways.
3 Mashup data security is a concern when it comes to enterprise level data interactions.
Currently pretty much most of mashup security is based on one single fact. It is the trust
in the mashup service providers to provide with correct data. It is possible to encrypt and
authenticate to verify the data integrity and the authenticity of the data supplier. But
what if the data supplied by the supplier is no more reliable? Perhaps data supplier on
the other side may have become compromised. This may allow malicious parties to insert
data or codes to sniff or spoof sensitive data or disrupt the process executions. So for
tight security it may be necessary to validate incoming data for security vulnerabilities by
parsing service responses in each stage. Mooshabaya can help by embedding such
vulnerability discovery logic in generated mashups.
4 Another enhancement would be to support high-level constructs like "Map-reduce"
(http://en.wikipedia.org/wiki/MapReduce) as XBaya operators (currently it supports
IF/THEN and For-Loops to name few).

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License