Wilhelm Schafer, Burkhard Peuschel, and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....include Arcadia [8] which uses an imperative notation called appl a [13] based on Ada, hfsp [9] which uses an extension of attribute grammars, and Melmac [3] Slang [1] and Process Weaver [4] which use a form of Petri nets. Important examples of rule based PCEs include Grapple [7] and Merlin [11]. We would like to compare our experience against the following two concerns: How (if at all) have the implementors of PCEs been able to support reengineering of their own code What processes (if any) have been constructed to assist and guide users in their reengineering efforts This comparison ....

Wilhelm Schafer, Burkhard Peuschel, and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....on mechanisms needed to support concurrency control; our support for recovery is clearly not powerful enough for all ETMs. Several researchers are currently investigating recovery for ETMs [27] TML behaves according to a task model, described through some modeling formalism, such as rules [96, 17], Petri nets [8, 43] task graphs [110, 80] or workflow [79] A task model describes the set of tasks and activities allowed for users of the system. TML manages all steps and activities generated as each user request is processed, thus TML contains the semantic information for all tasks. ECC is ....

....manager with multiple, distributed data servers. A more appropriate architecture would have peer to peer communication between multiple transaction managers; we implemented such an architecture using mediators in the Oz process centered environment, as described in Section 3.7. 34 Merlin Merlin [96] is a PCE that coordinates and supports development activities in a software process, according to its underlying process description. To coordinate concurrent accesses to documents, the process transaction model consists of five types of transactions Pess Akt, Pess Af, Opt Akt, Kons, Auto 5 ....

Wilhelm Schafer, Burkhard Peuschel, and Stefan Wolf. A Knowledge-based Software Development Environment Supporting Cooperative Work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....might maintain a to do list of pending tasks. SDEs known for guidance support include ProcessWEAVER [32] and 4 In that respect, the choice of the term enactment is misleading, but since it is so widely used in the process community we will stick to this term throughout the thesis. 6 Merlin [109]. 4. Monitoring This refers to the environment s capability to monitor the progress of the process, and accurately assess the state of the process at any particular point in time (other mechanisms can be used to actually extract the process state) An extension to process monitoring is ....

....[85] Various PCEs have been constructed as research prototypes and non commercial systems, and some have been recently released as commercial products. Examples of relatively well known academic and other research PCEs include Arcadia [57] Common Lisp Framework (CLF) 89] Melmac [24] Merlin [109], Spade [3] and TEMPO [11] Examples of commercial products include ProcessWEAVER [32] HP SynerVision [51] and Lion [73] The state of the art in PCE technology (including all the systems mentioned above) however, has been supporting centralized and homogeneous processes, for moderate sized ....

[Article contains additional citation context not shown here]

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....employed the built in delete operation, but there might not be any analogous trick available in other PCEs to which our approach was applied. Our approach adapts in a straightforward manner to most other PCEs whose process enaction is based primarily on rule chaining or triggers, such as Merlin [28], ALF [23] Adele2 [6] and Oikos [9] We believe none of these systems currently provides an automated process evolution tool concerned with process enforcement, although they may permit changes to the process model with the process state continuing to be employed as is . Darwin provides a ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A Knowledge-based Software Development Environment Supporting Cooperative Work. International Journal on Software Engineering & Knowledge Engineering 2(1):79-106, March, 1992.

....been developed by many researchers as a means of addressing the so called software crisis issues of producing large, complex systems. Many process based environments have been developed by the software process community, based on various process formalisms, including rules (Marvel [12] Merlin [21]) finite state automata (StateMate [10] ASL [13] Petri nets (ProcessWeaver [4] imperative programming languages (APPL A [22] logic programming (Oikos [3] Darwin [17] and attribute grammars (HFSP [16] among others. Each environment, however, has used a somewhat different formalism from ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A Knowledge-based Software Development Environment Supporting Cooperative Work. International Journal on Software Engineering & Knowledge Engineering 2(1):79-106, March, 1992.

.... and user modeling; and (2) mechanisms for enacting the modeled process by the PSEEs process engine, where forms of enactment include process automation (e.g. Marvel [30] consistency (e.g. CLF [46] monitoring (e.g. Provence [34] enforcement (e.g. Darwin [42] and guidance (e.g. Merlin [51]) Thus, the PSEE interoperability problem is to balance autonomy and collaboration among multiple processes, both in the modeling and the enactment phases, as a basis for collaboration among multiple groups. 1 1.1 Requirements and Scope decentralized PSEEs We deliberately use the term ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....be immediately applicable to the CLF process centered environment [11] which supports consistency forward chaining conceptually similar to our own. It should also be easily extended to other environments whose process enaction is based primarily on forward chaining or triggers, including Merlin [27], EPOS [12] ALF [22] and Adele2 [8] As far as we know, none of these systems currently provides an automated process evolution tool. The Darwin 1 backward chaining environment includes a sophisticated mechanism for accepting or rejecting process changes [24] where the process (or law ) itself ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A Knowledge-based Software Development Environment Supporting Cooperative Work. International Journal on Software Engineering & Knowledge Engineering 2(1):79-106, March, 1992.

....which uses an imperative notation called appl a [15] based on Ada, hfsp [10] which uses an extension of attribute grammars, and Melmac [4] slang [1] and Process weaver [5] which use a form of Petri nets. Important examples of rule based PCEs include the Common Lisp Framework [3] and Merlin [13]. We would like to compare our experience against other PCEs considering the following two concerns: How (if at all) have the implementors of PCEs been able to support reengineering of their own code What processes (if any) have been constructed to assist users in their reengineering efforts ....

Wilhelm Schafer, Burkhard Peuschel, and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....distinguished from automation chaining, which can be restricted by no backward, no forward or no chain directives [Barghouti 92a] Synchronization is implicit in data access, since MARVEL 3. 0 enforces serializability among concurrent consistency chains and automation rules [Barghouti 92b] Merlin [Schafer 92] is similar to MARVEL. Backward chaining on logic programming rules establish which process steps are currently valid in the user s current role(s) and then forward chaining on planning system rules guide the user through an automated process sequence. The Common Lisp Framework (CLF) CLF 88] ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A Knowledge-based Software Development Environment Supporting Cooperative Work. International Journal on Software Engineering & Knowledge Engineering 2(1):79-106, March, 1992.

....the action or post condition of a rule fulfills the pre conditions of some rules, which are then fired recursively. Rule based PMLs can be roughly divided into backward chaining oriented such as Darwin [22] forward chaining oriented such as AP5 [8] and those that incorporate both, like Merlin [25]. The rule is the minimal common sub process that might be shared among local processes. When a decentralized rule is fired, either directly by a user or indirectly through automatic enaction (chaining) the following takes place: Pre Summit The collaborating SubEnvs supply data to be bound ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....federation. 3. Decentralized process control and centralized tool execution. Control is distributed among multiple process servers, where the tool execution function is supported by a single component. This model supports separate process engines for each user as in Endeavors [14] or Merlin [61] while sharing special computational or database resources used in tool invocation. One can easily imagine multiple workflows accessing the same tool management resource, particularly if only the tool broker is centralized, directing actual tool invocation to distributed hosts as in WebMake ....

Wilhelm Sch¨afer, Burkhard Peuschel, and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

....composition. Finally, we conclude and add some additional remarks regarding our current efforts. 2 Background In the domain of large scale software development, many new product, process, and decision support models have been proposed [DBe90, EJe91, GP 92, HL88, Kai88, MS90, OB92, RD91, SPW92, WS88] These models are used to facilitate different aspects of software development when employed within support systems we call process centered software development support environments (PSDSEs) These models also facilitate the archiving and reuse of product, process, and decision making ....

W. Schafer, B. Pueschel, and S. Wolf. A Knowledge-based Software Development Environment Supporting Cooperative Work. Intern. J. Soft. Engr. and Know. Engr., 2(1):79--106, 1992.

....Process. Various PCEs have been constructed as research prototypes and non commercial systems, and some have been recently released as commercial products. Examples of relatively well known academic and other research PCEs include Arcadia [26] Common Lisp Framework (CLF) 37] Melmac [14] Merlin [47], Adele [33] and Oikos [1] Examples of commercial products include Process Weaver [10] and HP SynerVision. 1.1 Why Decentralization Large scale product development (be it software, or other engineering) typically requires participation of multiple users, often divided in multiple groups, ....

Wilhelm Schafer, Burkhard Peuschel and Stefan Wolf. A knowledge-based software development environment supporting cooperative work. International Journal on Software Engineering & Knowledge Engineering, 2(1):79--106, March 1992.

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