
Requirements from customers are changing and functionalities have to be added to the
software already created, which may require new technologies. Therefore, to enable the inte-
gration of the old system with the new system and any other system created in the future, meta-
data driven architecture has to be used.
Meta-data driven architecture includes the iterations of deploying, combining and managing
data as well as applications. Meta-data driven architecture is made up of a platform-
independent UML model and one or more potentially platform-specific models. In addition,
the platform independent model contains information about how the UML base model is im-
plemented on the middleware platform.
Meta-data driven architecture utilize Model Driven Architecture (MDA) concepts [OMG
1999]. Currently there are at least 40 tools that incorporate at least one major aspect of MDA:
UML based modeling transformation between the applications over all design models and the
models that are specific to the underlying computing architecture (.NET, EJB and so on); and
the generation of code in a specific language. Williams estimates that MDA generates about
50% to 60% of the application code but it also depends on applications, using this approach we
hope to generate a new workflow system.
6 Conclusion
In this paper, we have discussed the issues faced in collaborative organizations, the develop-
ment of workflow systems based on decisions taken at managerial levels and the adaptation of
these issues in new workflow systems. We have proposed using workflow mining technique
for adaptation to existing workflow and introduced the concept of workflow mining and work-
flow log, where we need to work on the issues and their further role towards adaptation into the
workflow system.
References
Siebert, R 1996..: Adaptive workflow for the German Public Administration. International Conference on
Practical Aspects of Knowledge Management,
Aalst, W.M.P. van der; Basten T.; Verbeek, H.M.W.; Verkoulen, P.A.C.; Voorhoevoe, M March 1999..:
Adaptive Workflow On the Interplay Between Flexibility and Support. Proceedings of the first Interna-
tional Conference on Enterprise Information Systems, Vol 2, pages 353-360, Setubal, Portugal,
Han Y.; She th, A; Bussler,C. , 1998: A Taxanomy of Adaptive Workflow Management, Proceedings of the
CSCW-98 Workshop Towards Adaptive Workflow Systems, Seattle, USA, November 14.
Nutt G 1996..: The evolutions Toward Flexible Workflow Systems, Distributed Systems Engineering, Vol.
3, No. 4, pp. 276-294, December
Aalst, W.M.P van der; Jablonski, S 2000.: Dealing with workflow change: Identification of issues and
solutions, Special
Issue of International Journal of Computer Systems Science and Engineering, September.
Joeris, G 2000..: Modeling of Flexible Workflows and Their Decentralized Enactment in flow.net, Special
Issue of International Journal of Computer Systems Science And Engineering,
Ortner, W., Starty C, 1999.: Virtualization Of Organisations: Consequences for Workflow Modeling,
Proceedings of the 32
nd
Hawaii International Conference on System Sciences.
Stary, C 1996.: Integrating Workflow Representation into User Interface Design Representation, Software –
Concepts and Tools, Springer,.
Object Management Group. OMG UML 1.3, June 1999. OMG doc ad/99-06-08.
Mohan C 1999.:Tutorial: State of the Art in Workflow Management System Research and Products”, ACM
SIGMOD International Conference on Management of Data, Montreal, Canada, June
Marshak, R.T 1994.: “Falling in Love with Distinctions”, In “New Tools for New Times: The Workflow
Paradigm”, Future Strategies Inc.,
251