N. S. Barghouti, Supporting cooperation in the marvel process-centered sde, in: H. Weber (Ed.), Fifth ACM SIGSOFT Symposium on Software Development Environments, Vol. 17 of Special issue of Software Engineering Notes, Tyson's Corner VA, 1992, pp. 21--31. 34  Home/Search   Document Not in Database   Summary   Related Articles   Check

....tools and user roles. Di#erent styles of specification result from focus on one of these aspects, that is taken to be central. A few interesting specification style alternatives are explored in PCSDEs: Rule based specifications are employed by the majority of the analyzed PCSDE (e.g. MARVEL[14], OIKOS[15] EPOS[16] Merlin[17] to mention a few) Rules usually specify an event causing their activation, a guarding condition and an action to be taken in case the condition is true. Another popular rule format surrounds an action with pre and post conditions. Rules permit a proscriptive ....

....constraints are respected. This kind of support is usually associated with systems that employ an artifact based style of interaction (Section 6.1) e.g. Merlin [17] PROSYT [32] Shamus [21] A goal based strategy a#ords users additional flexibility and support. In systems such as MARVEL[14], EPOS[16] Grapple [33] and ALF [34] users are free to choose any possible action supported by the system, independently of pre conditions being enabled. These systems use inferencing to dynamically build plans that cause the pre condition of an action to be satisfied so that it can be ....

[Article contains additional citation context not shown here]

N. S. Barghouti, Supporting cooperation in the marvel process-centered sde, in: H. Weber (Ed.), Fifth ACM SIGSOFT Symposium on Software Development Environments, Vol. 17 of Special issue of Software Engineering Notes, Tyson's Corner VA, 1992, pp. 21--31. 34

....to the actual process performance and enabling branches, backtracks, and loops in process model enactment. Research in the PCE area has concentrated on the modeling and enactment domains [5] It has resulted in a set of mature process modeling languages and enactment mechanisms, e.g. 6] 7] [8], 9] 10] 11] 12] 13] 5] 14] Excellent overviews on the research in the PCE area and comparisons of different approaches can be found in, e.g. 15] 16] 17] 18] 19] 4] Unfortunately, the consequences for the interactive tools of the environment have been studied much less. ....

N. Barghouti, Supporting Cooperation in the MARVEL Process-Centered Sojtware Development Environment, In: Proc. of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, New York, New York, USA, 1992, pp. 21-31.

....levels of granularity, to provide the appropriate level of guidance for different developers [16] Process integration [27] however, which in our setting means the integration of multiple process models to produce an overall, coherent development process, remains a problematic research area. in [2], one technique for such integration is proposed, based on a concurrency control mechanism developed for a co operative software development environment. 3 Finally, ViewPoint development process models may be partly described by precise inconsistency handling rules, that specify how to act in ....

N. Barghouti, "Supporting Cooperation in the MARVEL Process-Centered Environment", ACM Software Engineering Notes, 17(5), December 1992, 21-31.

....development process. The transactional approach is based on advanced transaction models that allow more concurrency between activities [7] The transactional point of view considers each person s activity as a transaction that has to be completed to reach the sub goal. The process point of view [14, 2, 1] considers each person s activity as a task which has to be completed in a predefined order and with some specific conditions. Most of the time, approaches that cover these two points of view are biased towards one of them. However, these two points of view are essential in cooperative ....

N. Barghouti. Supporting Cooperation in the MARVEL Process-Centered SDE. Proceedings of the Fifth ACM SIGSOFT Symposium on Software 24 Development Environments, 17(5):21--31, December 1992.

....development process. The transactional approach is based on advanced transaction models that allow more concurrency between activities[1] The transactional point of view considers each person s activity as a transaction that has to be completed to reach the sub goal. The process point of view [2, 3, 4] considers each person s activity as a task which has to be completed in a predefined order and with some specific conditions. Most of the time, approaches that cover these two points of view are biased towards one of them. However, these two points of view are essential in cooperative ....

N. Barghouti. Supporting Cooperation in the MARVEL Process-Centered SDE. Proceedings of the Fifth ACM SIGSOFT Symposium on Software Development Environments, 17(5):21--31, December 1992.

....in the tool declaration. If so, multiple instances of the same task or several entirely different tasks can be submitted to the same persistent tool execution. Formal parameters and locking information are also listed (locks and transaction management are outside the scope of this paper, see [6, 2]) The envelope specified by the task handles the passing of arguments back and forth to from the environment as well as the details of interaction with a tool that is already running. We made no changes at all to Oz s task definition syntax [11] and our approach is intended to be orthogonal to ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 21--31, Tyson's Corner VA, December

....message numbered 1. The Bank CP is launched by the user [1] and starts executing [2 8] at which point it is in states f Doing t, Doing dg. The two sub procedures, Transfer and Deposit, are launched at [6 7] The Transfer CP is the first one instantiated [9 10] and it starts executing. Between [11] and [12] the Transfer CP begins a transaction. Proceeding on to [13 14] we see that the Transfer CP has acquired the necessary locks and a new working context, 00001001, is created and sent to the user s agenda [15 16, 18 20] The Transfer CP then moves into state P0 [17] The Deposit CP is ....

....transaction suspended; when resumed, the entire chain would attempt to execute atomically. Since atomic rule chains had this ability to be arbitrarily undone and restarted, they could only be composed of special rules without any external activity (i.e. inference rules, described in [11]) 3. The Crl language was designed for the Marvel RBDE, and had grammatical constructs that directly accessed specific semantic information from Marvel. 4. The Marvel system originally restricted each user to execute only a single activity at a time. In this situation, it made sense to abort ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 21--31, Tyson's Corner VA, December 1992.

....repository, called the objectbase [38] The PSL at Columbia University has been working on PCEs for several years and Oz is its most recent effort. The system benefits of course from our previous experience, most specifically the one gained in developing and testing the Marvel 3. x PCE [5] [1], to which Oz is intended to be the successor. While Oz inherited from Marvel most of its main features, some crucial enhancements have been planned and implemented. One of the most important is the modification of its client server architecture from a single server to a multi server structure, ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 21--31, Tyson's Corner VA, December 1992. Special issue of Software Engineering Notes, 17(5), December 1992.

....listed in the tool declaration. If so, multiple instances of the same activity or several entirely different activities can be submitted to the same persistent tool execution. Formal parameters and locking information are also listed (transaction management is outside the scope of this paper, see [4], 33] The envelope specified by the associated task handles the passing of arguments back and forth to from the environment s repository as well as the details of interaction with a tool that is already running. These declarations appear in identical form in SEL specifications, but in that ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 21--31, Tyson's Corner VA, December 1992. Special issue of Software Engineering Notes, 17(5), December 1992.

....a conventional database system) it would be declared as MULTI NO QUEUE; then, USER2 s request is handled by the normal multi tasking nature of TOOL1 and USER1 and USER2 work in isolation. Marvel s default concurrency control policy handles lock conflicts on data provided by the process server [1]. If TOOL1 enables collaborative work, we again use the MULTI NO QUEUE attribute, but assume that most of the multi user machinery is offered by the tool itself. Concurrency control on data provided by the process server must be relaxed to allow for the desired data sharing, e.g. two users ....

Barghouti, N.S.: Supporting cooperation in the marvel process-centered SDE. 5th ACM SIGSOFT Symposium on Software Development Environments (December 1992) 21--31.

....would be listed in the tool declaration. If so, multiple instances of the same task or several entirely different tasks can be submitted to the same persistent tool execution. Formal parameters and locking information are also listed (transaction management is outside the scope of this paper, see [2, 12]) The envelope specified by the task handles the passing of arguments back and forth to from IEEE Seventh International Workshop on Computer Aided Software Engineering, July 1995, pp. 40 48. 43 the environment as well as the details of interaction with a tool that is already running. We made no ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 21--31, Tyson's Corner VA, December 1992. Special issue of Software Engineering Notes, 17(5), December 1992.

....coordination. The latter is concerned with coordinating concurrent activities that might violate the consistency of the project database, assuming that all participants use the same process, the same schema, and most importantly, share the same centralized, project database (see, for example, [4]) In contrast, we focus in this paper on collaboration between users or teams with different processes, different schemas, and different project databases. PSEE Autonomy Each local SubEnv should have complete control over its process, tools and data, while allowing access by remote SubEnvs ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 48 21--31, Tyson's Corner VA, December 1992. Special issue of Software Engineering Notes, 17(5), December 1992.

....to potentially be blocked if their required resources are not available. Concurrency is not explicitly dealt with yet. Locking is done in active databases, but this may be inappropriate for software engineering purposes. A more cooperative model may be needed such as the one found in Marvel [1]. However, as stated earlier, the proposed execution model does not currently deal with concurrency issues. The event rule model is flexible. This flexibility means that things such as the automatic collection of metrics can be triggered by events without having to call the collection routines ....

Barghouti, S. Supporting Cooperation in the Marvel Process-Centered SDE. in Proc. of the 5th ACM SIGSOFT Symposium on Software Development Environments, Dec. 1992, pp. 21-31.

....the global coordination structure and possibly even allowing on line reconfiguration of the coordination structure. Rather, single tools react to incoming messages which have to be issued ad hoc by the users. Software Development Environments Software Development Environments (SDEs) like Marvel [3], Oz [32] or SPADE [2] coordinate compilers, linkers or debuggers as external tools. In these environments, tool coordination focuses on the software development process and the tools come from that application area only. Wrapping is used to connect the tools to the SDE, but the connection ....

Naser S. Barghouti: "Supporting cooperation in the Marvel process-centered SDE ", Proceedings of the Fifth ACM SIGSOFT/SIGPLAN Symposium on Software Development Environments, ACM SIGSOFT Software Engineering Notes, 17(5), pp. 21-- 31, 1992.

....a particular object and another rule in a concurrent chain attempts to obtain a conflicting lock on the same object. The middle layer resolves such conflicts through a semantics based protocol that understands the distinction between consistency and automation chains indicated by the process model [6]. Consistency is all or nothing: if a consistency chain cannot be completed due to a lock conflict when a rule attempts to access an object, the entire chain should be aborted (rolled back) In contrast, rule chains purely for automation can be terminated after the previous rule when there is a ....

Naser S. Barghouti. Supporting Cooperation in the MARVEL Process-Centered SDE. In Fifth ACM SIGSOFT Symposium on Software Development Environments. Washington DC, December, 1992. In press.

....modify his own private copy. In conflict situations, NSE doesn t abort, but supports merging of the proposed private version with the public one, and provides assistance to eliminate the conflict. PSEE systems generally uses the underlying database to detect conflicts. A representative is Marvel [B 92] allowing exchange of uncommitted data between cooperative transactions given that certain consistency criteria are not violated. Conflict are resolved by giving priorities to transactions to prevent lost work. There are no communication protocols. 4 The SCOOP cooperative transaction model. ....

....Engine. Defining the PML (at least functionally) as a super set of the underlying DDL DML allow effective DB PM integration, without binding us unduly to the actual (OO)DBMS. Such a DB PM architecture have been demonstrated by e.g. Adele Tempo, EPOS [CLH94] SPADE, Merlin [FKB 94] Marvel [B 92] and other PM systems, all running on top of a DBMS. It may be a mapping problem that the lower levels of the process model becomes represented as DBMS encoded communication or access protocols, while the upper levels dealing with consistency maintenance, global workflow and work ....

N.S. Barghouti, Supporting Cooperation in the MARVEL Process-Centered SDE. 5th ACM SIGSOFT SDE, December 1992.

.... and Perspectives As justified before, we believe that a concurrency control approach better fits indirect cooperation correctness than a concurrent engineering one (in opposition to, as example [2] In this context, our approach to support cooperation is quite original: when most models [16, 1, 22] found correctness on classical serializability and uses some knowledge on the process to relax serializability (figure 2, b) we found correctness on a new criterion which defines a large sphere of security and we use knowledge to restrict this sphere of security (figure 2, a) The ....

Barghouti, N. Supporting Cooperation in the MARVEL Process-Centered SDE. Proceedings of the Fifth ACM SIGSOFT Symposium on Software Development Environments 17, 5 (December 1992), 21--31. 12

....is a tool for collaborative software development described in (Kaplan et al. 1992) Based on ConversationBuilder (Gintell et al. 1993) propose a collaborative inspection and review system for software engineering products. The system is tailorable to different development process models. (Barghouti 1992) describes the cooperation facilities of MARVEL which is a rule based software engineering environment. Rules are used to describe the development process model and to control the execution of the development tools. Pulli and Heikkinen 1993) propose concepts for concurrent engineering for ....

Barghouti, N.S. 1992. "Supporting cooperation in the MARVEL process-centered SDE." In: Proc. of the Fifth ACM SIGSOFT Symposium on Software Development Environments, H.

....would be listed in the tool declaration. If so, multiple instances of the same task or several entirely different tasks can be submitted to the same persistent tool execution. Formal parameters and locking information are also listed (transaction management is outside the scope of this paper, see [3], 17] The envelope specified by the task handles the passing of arguments back and forth to from the environment as well as the details of interaction with a tool that is already running. 9 These declarations appear in identical form in SEL specifications, but in that case each envelope ....

Naser S. Barghouti. Supporting cooperation in the marvel process-centered SDE. In Herbert Weber, editor, 5th ACM SIGSOFT Symposium on Software Development Environments, pages 21--31, Tyson's Corner VA, December 1992. Special issue of Software Engineering Notes, 17(5), December 1992.

....among information systems, without loosing the model generality. Such a model enables research in this area to be more focused on issues that are common to all the above mentioned systems, such as alternative paths of operations in case of network failures and the application of meta data. MARVEL [2] is a process centered environment that supports teams of users working on medium to large scale projects. An instantiated environment is created by an administrator who provides the data schema, process model, tool envelopes (which are equivalent to components) and coordination model for a ....

N. S. Barghouti. Supporting cooperation in the Marvel process-centered SDE. In Proceedings of the Fifth ACM SIGSOFT Symposium on Software Development Environments, pages 21--30, Tyson's Corner, Virginia, Dec. 1992.

.... [14,16,18] exploit in order to boost the creation of domain focused and location transparent environments [4,19] LAN based Intranets and even isolated workstations offer a great potential in terms of process centered environments: the cooperation and coordination aspects become crucial [1,2,3]. While in the past PCEs supported the work of big groups of people with a wide variety of competencies, the personal productivity tools now available allow small groups (even a single person) to develop substantial parts of a project if adequately supported. The split of the work tends to be ....

....Fig.5: Deployment of federation infrastructures Information Distribution min max max 13 Considering the problem of where to deploy the various components of the federation infrastructure, focusing on information and process management components, we noticed (Fig. 5) that there is a tendency [2,3,5] to associate information with process logic. Alternative approaches have been investigated [8] but we decided that, given the dynamic characteristics of a federation context, the ability of our infrastructure to adapt to different situations without being re engineered was a major goal. The main ....

N.S. Barghouti. Supporting cooperation in the Marvel process-centered SDE. In Fifth ACM SIGSOFT Symposium on Software Development Environments. Herbert Weber (ed.), 1992.

....is not suitable for the kinds of long, nested transactions which are found in an SEE. It may be the case that environment frameworks which support process transactions across subsets do not need many of the services described here. This topic is very much a research issue. 4.6. 8 Examples Marvel [7], CAIS A, and PCTE [35] provide data transactions, as do many modern data management systems. 4.7 Concurrency Service This service provides capabilities which ensure reliable concurrent access (by users or processes) to the object management system. 4.7.1 Conceptual The Concurrency service ....

....Development, and the other categories of Process Management services might be regarded as extensions of the Process Development service. Draft November 24, 1993 Edition 57 5.1. 8 Examples IPSE2.5 s PML [79] Arcadia [52] EAST [9] ESF [74] EFA [47] Enterprise II [60] COHESION [14] Marvel [7], and SLCSE [80] all provide some process development services. 5.2 Process Enactment Service A process definition may be enacted by process agents that may be humans (project user roles or individuals) or machines. 3 An SEE may support either or both methods of process enactment (humans or ....

Barghouti N. S. Supporting Cooperation in the Marvel Process-Centered SDE. Proc. of the ACM SIGSOFT Fifth Symposium on Software Development Environments, McLean VA, ACM SIGSoft Software Engineering Notes 17(5):21-31, December 1992.

....two authors have separately developed and implemented two architectures for custombased interoperation of specific PSSs. The first was a heterogeneous process engine built on top of Process Weaver (PW) 18] and Adele [15] The second was the Provence environment [5] which integrated Marvel [4] and the Unix working environment to provide an open process monitoring environment [6] The objective in both cases was to build an abstract process engine out of the two PSSs, without changing either of them, making them interoperate in a peer to peer fashion that enables them to ....

....active) is automatically generated. The automatic generation, based on a set of conventions, hides a major part of the interoperation from the process modeler. 6.2 Provence The Provence architecture[5] also fits the state based approach. Provence aimed at interoperating a rule based PSS, Marvel[4], with a file based one, the Unix working environment (file system, tools and events) for the purpose of monitoring development activities and automating some of them. A common meta model defined concepts like object, attribute, event and process state, and bindings were then provided from this ....

N.S. Barghouti. Supporting Cooperation in the MARVEL Process-Centered SDE. In Proc. SIGSOFT'92, 5th ACM SIGSOFT Symposium on Software Development Environments. H. Weber, editor. Tyson's Corner, VA, USA, Dec. 1992. Published as special issue of SEN, 17(5), ACM Press.

....It may be argued that it is unrealistic, or even undesirable, to create a solid boundary between the IM and the PS, especially with regard to transaction management for interteam coordination and intrateam cooperation during process execution. Indeed the architectures of some PSEEs, such as Marvel [12] and Merlin [50] do not clearly separate the functions of the IM from those 5 6 1995 17:53 PAGE PROOFS for John Wiley Sons Ltd paper 4 BARGHOUTI, EMMERICH, SCH AFER, SKARRA of the PS. The reason for this, however, is that at the time when these PSEEs were built, the available database ....

....that such a policy is usually hardwired in the database system. This limits the application system to a policy that might not be appropriate for all situations. Instead, Marvel provides a default serializability based policy, but also a language called CRL to modify the concurrency control policy [12, 11]. A CRL specification consists of a set of control rules, each of which describes a class of interference situations, with varying degrees of specificity, and prescribes actions for resolving such situations. Each control rule defines a selection criterion, some variables that are bound to either ....

Naser S. Barghouti. Supporting Cooperation in the Marvel Process-Centered SDE. In Proc. of ACM SIGSOFT '92: Fifth Symposium on Software Development Environments, pages 21--31, Tyson's Corner, VA, December 1992.

No context found.

Barghouti, N.S. 1992. "Supporting cooperation in the MARVEL process-centered SDE." In: Proc. of the Fifth ACM SIGSOFT Symposium on Software Development Environments, H. Weber, ed. Software Engineering Notes, Vol. 17, No. 5, 2131.

First 50 documents

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