1. Specifying document schema definitions
2. Specifying document transformations
3. Specifying Business Process
4. Specifying messaging methods.
   

1. Document Designer
2. Document Transformation Designer
3. Business Process Designer
4. Messaging Manager
   

The features required in the Document Designer are:

1. Provide a way to load a positional or delimited document and create its generic specification against which other instances of the document can be validated.
2. Load an already created document specification and modify it to suit other document specifications.
3. Create a new schema from scratch.

1. Analysis of positional and delimited document loaded into the module
2. Creation of a XML Schema Document (XSD) from the analysis
3. Saving of XSD document so created into disk media.
   

The features required in the Document Designer are:

1. Provide a way to load two XML Schema documents and provide visual methods to draw the transformation methods.
2. Load an already created Transformation scheme and modify it to suit other document specifications.
3. Create a new transformation from scratch.

1. Analysis of XSD loaded into the module
2. Creation of a basic transformation scheme which suites both the loaded XSDs from the analysis
3. Saving of transformation so created into disk media.
   

The features required in the Business Process Designer are:

1. Provides a 2D drawing canvas for drawing process diagrams
2. Provides a library of pre built shapes denoting special entities like start, stop, branch, condition, document transformation, MTA, notification, application and custom entity.
3. Dragging, adding, deleting, resizing, editing properties of entities to the canvas must be allowed.
4. Creation, saving, loading, editing and modification of diagram must be supported.
5. If an entity (such as a transformation) is required which has not been created, the tool must provide an interface (such as a button) to start the appropriate builder tool (transformation designer in this sample case) to define the entity.
6. Wherever possible, the 2D figure representing the entity should provide a list of available choices for that particular class of entities.

1. Analysis of Business process workflow diagram to avoid infinite looping conditions

The features required in the Document Designer are:

1. Provide a way to specify MTAs into the workflow diagram.
2. Provide a way to draw a pipeline, insert, modify and delete elements.
3. Load an already existing pipeline and modify it to suit other needs.

1. Analysis of message pipeline diagram to avoid infinite looping conditions

The features required in the Process Coordination Server are:

1. It must be able to discover new business processes loaded into the server by the administration tools.
2. It must be able to execute a business process without any user intervention, once the process is loaded.
3. It must maintain a transaction and activity log specifying the messages, recieved, sent and process activity status records.
4. It must support asynchronous communication between applications involved in a process.
5. It must be able to maintain a process state for the time-out period specified without losing any data for a process suspended or waiting for a request or response by a participating application.
6. If the server is shut down for some reason then all running processes should be suspended and their state should be persisted on disk and on regaining execution the server must restore the processes in the same state as before.
7. The server must provide for reliable and secure message transport by utilizing cryptographic services.
8. The server must provide a mechanism for disseminating alert notifications to subscribing applications, in the event of a process suspension or abnormal termination.
9. The server must provide support for correct routing of message as defined in the process diagram's data flow.
10. The server must provide for correlation of messages i.e. the messages recieved into the system must be sent to the correct process instance and correct application instance so that multiple instances of the same process can run in parallel.

1. Polling module for discovery of newly loaded business process.
2. Logging and error notifications without server faliure.
3. Handling of message queues
4. Persistance of suspended processes to disk and recreation of process in memory when state of the process changes to active.
5. Cryptographic functions for securing messages being transported.
6. Dissemination of alert notifications through a publish-subscribe model.
7. Correlation of incoming messages to correct process instance.
8. Parallel processing of different instances of same process and different processes without any interference or concurrency issues.
   

The features required in the Administration tools are:

1. Configure server execution properties such as log file size and other parameters.
2. Configure and manage Message Transport Agents (MTA) including installation and uninstallation of MTAs into the system.
3. View and manage the server database.
4. View and manage the transaction and activity logs.
5. Backup and restore data including scheduling automatic backups.
6. Monitor alert notifications.
7. Provide a Publish-Subscribe model for alert notifications.
8. View performance statistics such as process instances executing per minute, workload division among installed business processes.