Kaiser, G.E. & Ben-Shaul, I.Z. 1993. Process Evolution in the Marvel Environment. In: Procs. of 8th Int. Software Process Workshop, IEEE Computer Society Press, 104-106.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....a PML for environments. Defining a PML for humans to be interpreted (process ontology) is almost ignored in current PCSE environments (Marttiin, 1997) Approaches for customising a PML to be enacted by tools and interpreted by process engines include the metalinguistic approach in Amber (Kaiser et al. 1993) and language extension mechanism by (Balzer and Narayanaswamy, 1993) Customisation of concept structures behind PMLs (process ontologies) can be defined in MetaEdit (Koskinen and Marttiin, 1997) and OVAL (Malone et al. 1995) Some concept adaptation can also be achieved through specialising ....

....can support it. A key problem of process evolution is how to make changes to an enacting model while making the current process state consistent with the new process model. This problem is addressed by process reflection in EPOS and SPADE, and by using a process evolution algorithm in Marvel (Kaiser and Ben Shaul, 1993). Another issue is how to change the way how process models are interpreted by a process engine without changing the process models themselves, e.g. for different levels of process support. This is addressed by metalinguistic extensibility in Amber (Kaiser et al. 1996) 2.4. PE process A ....

Kaiser, G.E. & Ben-Shaul, I.Z. 1993. Process Evolution in the Marvel Environment. In: Procs. of 8th Int. Software Process Workshop, IEEE Computer Society Press, 104-106.

....the form of event condition action (ECA) rules and then roll back semantics for constraint management enforcement. While some researchers have used ECA rules to implement consistency management capabilities, the semantics of consistency management are fairly di erent from reactive control [SHO95, KBS, BK92] Veri cation as Consistency Management Technique. However, while this roll back based support for consistency management might be adequate for some types of application programs, it is a very expensive management strategy for schema evolution programs. Consider a large schema evolution ....

....rules that are a mechanism for detecting the occurrence of some event and responding to it by some action. While some researchers have used ECA rules to implement consistency management capabilities, the semantics 13 of consistency management are fairly di erent from reactive control [SHO95, KBS, BK92] Consistency management activities are a required part of any computation in which constraints are enforced and failure to satisfy the constraints may invalidate the activity. The failure to complete the activity associated with an ECA rule, however, may not necessarily invalidate the ....

G.E. Kaiser and I.Z. Ben-Shaul. Process Evolution in the MARVEL Environment. In Schafer

.... [9, 21] Example research prototypes focusing on process evolution are SPADE [3] Process Modeling Modeling PMod PMAn PM Runtime Support P AMan PExec PEvol PInst PMon PSE Functions and Artifacts Figure 1: A Functional View on a PSE OM Organizational Modeling OMod CMan EPOS [25] Marvel [28]. 5] provide a conceptual framework for process evolution in PSEs. Configuration Management (CMan) Configuration management CMan provides functionality to manage the products of processes, e.g. versions, releases. Configuration management is agreed to be an important part of a SEE. 12, 15] ....

Kaiser, G. E., Ben-Shaul, I. Z., "Process Evolution in the Marvel Environment", Proceedings 8th Intl. Software Process Workshop (ISPW-8), Wadern, Germany, March 1993, IEEE CS Press, pp. 104-106.

....is based on the notion of process consistency, and on ways to identify inconsistencies that might be introduced as a result of changes that were made to the process model. We summarize here our general approach and solution to this problem. A detailed discussion of this topic can be found in [58, 68]. 2.2.5.1 Process Consistency and Enforcement Process consistency refers to constraints that are defined in the process (either implicitly or explicitly) and are assumed to always hold for any relevant process state in any instantiation of the process. The process state is deemed consistent if ....

Gail E. Kaiser, Israel Z. Ben-Shaul, George T. Heineman, and Wilfredo Marrero. Process evolution for the marvel environment. Technical Report CUCS-047-92, Columbia University Department of Computer Science, April 1993.

....illustrated in Figure 2. Additional details about multi user issues, primarily concurrency control policies specified by the process engineer in the coordination model, are given in [2, 1] Marvel s support for schema and process evolution while a long term project is in progress is described in [14]. We completed Marvel 3.0, the first multi user version, in Fall 1991. 3.0.1 was developed using the C Marvel environment instance of the Marvel 3.0 kernel, and released in Spring 1992. The final Marvel 3.1 was released in March 1993, and consists of about client client client Process Data ....

Gail E. Kaiser, Israel Z. Ben-Shaul, George T. Heineman, and Wilfredo Marrero. Process evolution for the marvel environment. Technical Report CUCS-04792, Columbia University Department of Computer Science, April 1993.

....facility assumes a shared network file system. The external view is illustrated in Figure 2. Additional details about multi user issues, primarily concurrency control, are given in [2, 1, 9] Marvel s support for schema and process evolution while a long term project is in progress is described in [12]. We completed Marvel 3.0, the first multi user version, in Fall 1991. 3.0.1 was developed using the C Marvel environment on top of Marvel 3.0, and released in Spring 1992. The final Marvel 3.1 was released in March 1993, and consists of about 154,000 lines of C, yacc and lex code. 3.1 supports ....

Gail E. Kaiser, Israel Z. Ben-Shaul, George T. Heineman, and Wilfredo Marrero. Process evolution for the marvel environment. Technical Report CUCS-047-92, Columbia University Department of Computer Science, April 1993.

....changes to detect possible inconsistencies in a single process is sufficient for retaining the consistency of the entire environment, because imported (and shared) rules are the only means for processes to interact with each other. Initial work on process evolution in PCEs has been done in Marvel [27], and an Evolver tool was developed that is able to detect and update an objectbase to correspond to the newly defined process consistency. It is intended to be extended in the thesis for use by the import procedure. 3.2.3 Decentralized Process Enaction Per SubEnv, Oz assumes a four level ....

Gail E. Kaiser, Israel Z. Ben-Shaul, George T. Heineman, and Wilfredo Marrero. Process evolution for the marvel environment. Technical Report CUCS-047-92, Columbia University Department of Computer Science, April 1993. Submitted for publication.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC