Abstract 1994) so less successful cases are a large part of the Traditional notations of processes are oftenbased on not a-tions that are formalized with different types of automata and a suitable domain specific (graphical) notation. These notations allow elaborate analysis of the processes such as proving equivalence between processes. They are also effi-cient in capturing exact behavior, but are sometimes e- rgarded as difficult to use by users less familiar with formal notations and do not always promote easy reuse and step-wise refinement. A notation for processes using transition rules and catego-rization of formulae in transition rules is exemplified and proposed for applications domains such as business proc-esses, system development processes etc. Transition rules enable users to successively refine the processes and also enable similarity measurements and reuse in a Case-Based Reasoning approach. Transition rules in the proposal handle also time, important for some features. Using formalized transition rules also gives access to logical based tools (veri-fication, simulations).
[1]
Ivica Crnkovic,et al.
Case-Based Reasoning for Reuse and Validation of System Development Processes
,
1999,
ICCBR Workshops.
[2]
Peter Funk.
CABS : a case-based and graphical requirements capture, formalisation and verification system
,
1999
.
[3]
Alexandre Hanft,et al.
Cases with a Life-Cycle
,
1999,
ICCBR Workshops.
[4]
David Stuart Robertson,et al.
Formal Support for an Informal Business Modelling Method
,
2000,
Int. J. Softw. Eng. Knowl. Eng..
[5]
Ian D. Watson,et al.
Applying case-based reasoning - techniques for the enterprise systems
,
1997
.
[6]
Carsten Tautz,et al.
CBR for Experimental Software Engineering
,
1998,
Case-Based Reasoning Technology.