Development blog

Chamin TODO - 12/11/08

Chamin TODO - 12/11/08

Currently I'm working in developing the core component of the SAF system, that is the runtime server. In that task I have to address following points.

• WorkflowSchedulerService - Workflow instance threading
• Tracking service - for the use of admin console for the report generation
• persistence service - for optimizing the use of resources by the server
• ExternalDataService + Correlation - workflow communication with its host application
• Invoking web services within workflow
• Workflow dynamin reloading while executing
• Declarative workflows - flexible workflow definitions. allows changing the workflow definition without compililng
• declarative rule service - dynamic rules for workflows
  

Meeting with our supervisor on 06/11/08

We had a meeting with our supervisor at his office. In there we presented our solutions that we thought for the problems we came across and got his comments on those. And also he gave us more ideas about the concept of the system. His thoughts and suggestions given in the discussion are really useful for our work.


Here is a summery on the points we discussed there.

• He suggested us to develop this as an independent system from the interactive components, so that this can be deployed as a separate business of providing business process modeling services to companies. This service enables clients to use the server for their work, but many clients will be using the same server. So in here we may need a mechanism to implement charging for providing the services based on may be the execution of workflow instances.

• When we discussed on additional services that the workflow runtime server could have than what we have already thought of, we came across with providing a service to provide business rules to the server that can dynamically load rules required by the server for execution.

• Regarding the concern we had about sending emails, he suggested using an email server at the client side.

• He also gave a demonstration on their business intelligence module, so that it will help us for giving those features to our system which will be an additional feature to our system.

• We were not really sure about the method we have planned to use for the communication between server and client components. He thought that it was suitable for our problem.

• For the role based human intervention, he suggested us to use the system we use for the human interactions to get the information on the users that workflow runtime requires.

Project Website launched!!!

We launched our project website on 30th October 2008. You can visit it using http:\\project-saf.tk. All the documentation related to the design and implementation of the SoftAutoFlow system and other relavant details about the project can be found there. We will keep that website up to date always, so you can get the latest news of the our project.