P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proceedings of the 18th International Conference on Software Engineering (ICSE-18), pages 331--341, Berlin, Germany, Mar. 1996. IEEE Computer Society Press.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....artefact production as triggers for workflow enactment and model them within the process. For example, some of them use coloured Petrinets as a basic formalism for process modelling and enactment [BDF96, Aal98] Other approaches model a process as activity nets with expression of the data flow [CDG95, HJK96]. Most of these systems also provides facilities to deal with process deviations at run time. For example, Heimann et al. HJK96] use graph rewriting rules to enact and change the process model at run time. Most of the WfMSs and PSEEs of last decade are clientserver systems, with centralized ....

....as a basic formalism for process modelling and enactment [BDF96, Aal98] Other approaches model a process as activity nets with expression of the data flow [CDG95, HJK96] Most of these systems also provides facilities to deal with process deviations at run time. For example, Heimann et al. [HJK96] use graph rewriting rules to enact and change the process model at run time. Most of the WfMSs and PSEEs of last decade are clientserver systems, with centralized enactment facilities. Also they do not exploit the web as basic infrastructure to eases the accessibility of remote users. Recent ....

Heimann, P., Joeris, G., Krapp, C. A.; Westfechtel, B. "DYNAMITE: Dynamic Task Nets for Software Process Management", Proceedings of the 18th International Conference on Software Engineering, Berlin, Germany, 1996 pp. 331-341.

....and (2) to provide means to refine parts of the model during enactment. PROMENADE chooses the second alternative and defines hierarchies of task refinements (i.e. different ways to realize an activity) This is different from other approaches that consider only one level of activity realization [HJK96]. At enactment time one of those refinements is to be selected (or a new refinement can be created) Sometimes this is called a flexible enactment of a model. 5 Table 1: Some existing SPML approaches regarding expressiveness, standarization, flexibility 3 Static part of a model in PROMENADE The ....

Heimann, P.; Joeris, G.; Krapp, C. A.; Westfechtel, B. DYNAMITE: Dynamic Task Nets for Software Process Management. In Proc. of the . Int. Conf. on Software Engineering. Berlin, Germany, 1996 pp. 331341.

....processes, process model de nitions are the means to de ne reusable process speci c knowledge, since the instance level is highly dynamic and resulting structures cannot be reused in most cases. Within the AHEAD 1 environment dynamic task nets have been developed as a process meta model [4, 5]. The meta model supports the continous structural evolution during process enactment and thus meets the formulated requirements (cf. section 2) Dynamic task nets have been formally speci ed in the Programmed Graph Rewriting System (PROGRES) 13] The question arises how domain speci c schematic ....

.... of dynamic, non anticipated situations in the model, every state transition and every operation is followed by an event (cf. SendAbort statement in Figure 4, part ii) 3 For a detailed description on the use of graph transformations within the formal speci cation of dynamic task nets see [4] We presented the main features of a generic process model. In order to manage a certain process, domain speci c knowledge has to be provided. A domainspeci c process structure introduces new task and parameter types and re nes the generic relationship types. Process behavior has to be de ned in ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proc. ICSE `18, pages 331-341, Berlin, Mar. 1996.

....safety and liveness properties, which exclude only a few bad cases. Several PM environments 3 support the description of global aspects of process models within a construction oriented approach: ALF (MASP) 22] MARVEL (ASL) 17] PEACE [2] Oikos (ESP) 1] Merlin [23] DYNAMITE (Task Nets) [14], SPADE (SLANG) 4] and EPOS (SPELL) 15] use only limited forms of global constraints to specify ordering constraints for software process activities, but are not able to specify more abstract properties. In particular, they do not support logical combinations of abstract liveness and safety ....

P. Heimann, G. Joeris, C. Krapp, B. Westfechtel: "DYNAMITE: Dynamic Task Nets for Software Process Management", Proc. ICSE-18, IEEE Computer Society Press, pp. 331-341, 1996.

....defined earlier by the first author [5] We propose to use the workflow paradigm as a means to support the software process. This is an attractive option because it encourages the use of a general purpose paradigm for what has always been supported by specially developed models and systems [1, 10, 11]. Using the workflow paradigm allows the software process as well as the software systems to be developed to be captured in one and the same paradigm; hence helps to reduce the overall complexity of the development process. The use of the workflow paradigm also brings in additional advantages [8] ....

P. Heimann, G. Joeris, C.A. Krapp, and B. Westfechtel. "DYNAMITE: Dynamic Task Nets for Software Process Management". In Proceedings of the International Conference on Software Engineering, pages 331--341. IEEE Press, 1996.

....[11] Beyond that there are a still growing number of visual languages that rely directly on the graph rewriting paradigm, such as GOOD [13] Also, process modelling systems were described with the help of graph grammars and realized by graph rewriting systems. An example for that is DYNAMITE [6] which implements a dynamic task nets. Other applications of graph grammars and graph rewriting systems can be found in Computer Integrated Manufacturing systems (see [26] In this paper we will focus on PROGRES (PROgramming with Graph REwriting System) 18] It is a visual programming language ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proceedings of the 18th International Conference on Software Engineering, pages 331--341, Los Alamitos (CA), 1996. IEEE Computer Society Press.

....to exception handling and dynamic structural changes. Several approaches exist which address these issues. The proposals made by HOON (Han et al. 1996) ProMInanD (Vogel and Erfle, 1992) ObjectFlow (Hsu and Kleissner, 1996) WIDE (Casati et al. 1997) MOBILE (Heinl et al. 1996) and DYNAMITE (Heimann et al. 1996) are worth mentioning. Han et al. 1996) suggest a Petri net based model (HOON) for adaptive WFs. The basic idea is to use mechanisms for later binding of software components and WF models, which may be dynamically and hierarchically combined at run time. HOON does not support dynamic changes in ....

....well as partially defined process patterns, and they must be completed at run time. The authors do not indicate how users are supported in changing an incomplete model and which operations are available. Correctness issues are also not addressed. A more competitive approach is offered by DYNAMITE (Heimann et al. 1996). DYNAMITE aims at the support of the software development process, which is often highly dynamic and for which the planning and the execution of tasks may overlap. DYNAMITE uses dynamic task nets, which are built and modified incrementally during process execution. Formally, task nets are based ....

Heimann, P., Joeris, G., Krapp, C., and Westfechtel, B. (1996). DYNAMITE: Dynamic Task Nets for Software Process Management. Proc. 18th Int. Conf. Software Engineering (pp. 331-341). Berlin, Germany.

....to handle exceptional events must be explicitly modeled as additional paths in the WF graph. When a user detects an exception, he must abort active tasks and modify the flow structure to transfer the control to the exception handling path. An important contribution is offered by DYNAMITE [Heim96]. It aims at the support of the software development process, which is usually highly dynamic and for which the planning and the execution of tasks may overlap. DYNAMITE uses dynamic task nets which are built and modified incrementally during process execution. Formally, they are based on a graph ....

Heimann, P.; Joeris, G.; Krapp, C.; Westfechtel, B.: DYNAMITE: Dynamic Task Nets for Software Process Management. Proc. 18th Int. Conf. Software Engin., Berlin, 1996, pp. 331-341

....Conversely, analysis works bottom up and aims at providing feedback to the next upper level. The process meta model introduces the language (or meta schema) in terms of which process models may be defined at the next lower level. In AHEAD, the activity meta model is based on dynamic task nets [9]. Tasks are organized hierarchically. Complex tasks are decomposed into nets of subtasks; atomic tasks form the leaves of the hierarchy. Tasks are connected horizontally by control flows, which determine the order of task execution. Feedback flows are oriented oppositely to control flows; they are ....

....still present. The extended definition is transformed into the PROGRES specification, which in turn is compiled into C code. Now the process manager may migrate the task net to the improved definition. V. RELATED WORK Previous papers on the AHEAD system have presented instance level evolution [9], 24] and UML modeling of development processes [26] 14] This paper is based on the Ph.D. thesis of the second author [27] which introduces the wide spectrum approach, round trip process evolution, and toleration of inconsistencies. We have not described these contributions in other ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proceedings of the 18th International Conference on Software Engineering (ICSE-18), pages 331--341, Berlin, Germany, Mar. 1996. IEEE Computer Society Press.

....Section 6 concludes the paper. 2 A Sample Application On top of UPGRADE, we are currently developing AHEAD, an Adaptable and HumanCentered Environment for the MAnagement of Development Processes [14] In particular, AHEAD contains tools for managing activities that are based on dynamic task nets [11, 12]. In this paper, we focus on the project management tool which provides a graphical view on a task net and o ers commands for planning, analyzing, and monitoring the project status. A task describes a unit of work to be done. Tasks are organized hierarchically, i.e. a task may be decomposed into ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proceedings of the 18th International Conference on Software Engineering, pages 331-341, Berlin, Mar. 1996. IEEE Computer Society Press.

....process is being executed: changing requirements, feedback to earlier stages of the software life cycle, moved deadlines, shrinking budget, etc. These changes challenge the capabilities of process centered environ ments [7] For modeling software processes, we have proposed dynamic task nets [9], i.e. hierarchies of tasks that are in addition connected by various kinds of horizontal relationships (control flow, data flow, and feedback) The most essential feature of these task nets is that they continuously evolve during the enactment of a software process. This contrasts sharply to the ....

....modeling in UML. In Section 5, we define the semantics of UML process models by a mapping into a graph rewriting system. Section 6 summarizes the lessons learned. Related work is compared in Section 7. Finally, Section 8 presents a short conclusion. 2 Dynamic Task Nets The D YNA MITE model [9] introduces DYNAMIc Task nets for software process management. A task represents a unit of work that is typically performed by a human developer (with tool support) A task may have input parameters and output parameters, which are the documents the task is working on. A task reads its input ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proc. ICSE '18, pages 331-341, Berlin, Mar. 1996.

....anbietet und sowohl invariante Teile (InterfaceA) als auch variable Komponenten (InterfaceC) enth alt. Mit Hilfe dieser Vergr oberung lassen sich Konfigurationsfamilien darstellen (n aheres dazu in [67, 68] 3. 2 Aktivit atenmodell Das Aktivit atenmodell DYNAMITE (DYNAMIc Task NEts [23, 41]) definiert dynamische Aufgabennetze, die sich durch nahtloses Verschr anken von Planen, Ausf uhren, Analysieren und Uberwachen auszeichnen. Ein Aufgabennetz setzt sich aus Aufgaben zusammen, die durch unterschiedliche Arten von Beziehungen verbunden sind. Kontrollfl usse regeln die Reihenfolge ....

Heimann, P., Joeris, G., Krapp, C.-A., Westfechtel, B.: DYNAMITE: Dynamic Task Nets for Software Process Management. In: Proceedings of the 18th International Conference on Software Engineering, pp. 331-- 341, Berlin, M arz 1996. IEEE Computer Society Press

....In contrast to these, development processes are highly creative and cannot be planned fully in advance. The clear separation between planning (build) and execution (run) of a workflow, as implemented in classical WfMSs, cannot be upheld in this context. Our approach, called dynamic task nets [7], takes this challenge into account and allows for the interleaved planning, execution, analysis and monitoring of a workflow. We will only roughly sketch the functionality of our WfMS in this paper by looking into a process for handling change requests of a software system as presented in Figure ....

Heimann, P., Joeris, G., Krapp, C.-A., and Westfechtel, B.: DYNAMITE: Dynamic Task Nets for Software Process Management in Proceedings 18th Int. Conf. Software Engineering (ICSE 18), pages 331 - 341, Berlin, Germany (1996)

....and output documents of the delegated activities have to be propagated over the network as well. 3 Dynamic Task Nets The concept of process delegation which is presented in this paper was developed for dynamic task nets. Dynamic task nets are a visual language for modeling development processes [9]. The concept is implemented within the PMS AHEAD (Adaptable Human centered Environment for the Administration of Development processes) which uses dynamic task nets as process modeling formalism [12, 11] In AHEAD there are basically two user roles: the process manager who is responsible for ....

Peter Heimann, Gregor Joeris, Carl-Arndt Krapp, and Bernhard Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proceedings of the 18th ICSE, pages 331-341, Berlin, March 1996. IEEE Computer Society Press.

....overlap and pass intermediate results overcoming a black box view of a task in correspondence to the design of a reactive task agent. But, in order to avoid a chaotic process the discussion task must not terminate before the CR creation task. This kind of dependency is denoted as simultaneous [HJKW96]; its definition is given in figure 9. Furthermore, document interchange between both tasks is versioned and hence traceability is ensured. 2. Although the preliminary discussion is often needed, it is not mandatory. Therefore, the discussion in the development meeting only has to wait for the ....

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, 1996; pp. 331-341.

....model for planning, analyzing, and executing evolving development processes using hierarchical task nets. The model allows execution of incomplete process models, modifications on the fly, intertwined planning, modification, and enactment of process descriptions ensuring model consistency. While [11] presented the formal foundation, this paper focuses on describing an adaptable environment that realizes the DYNAMITE model and can handle dynamic situations for developers and managers. The remainder of this paper consists of three parts. First, we describe the advantages of our approach ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic Task Nets for Software Process Management. In Proceedings of the 18 th International Conference on Software Engineering, pages 331--341, Berlin, Germany, 1996. IEEE Computer Society Press.

.... cooperation support on workflow level; the second is supported by on the fly instance changes as well as complex workflow schema evolution policies: Dynamic changes: Based on the object oriented modeling and enacting approach, dynamic changes can be handled as any ordinary state transition (cf. [HJKW96, JoHe98]) Every change primitive is encapsulated by a pre condition which restricts its application, and by raising a corresponding event which is handled by the affected task instances in order to ensure the behavioral consistency of the execution states. Thus, dynamic changes can be supported also in ....

....produce several versions of its output and the consuming tasks may obtain several input versions. To avoid chaotic processes, the termination condition is defined as an end end dependency guaranteeing that all predecessor tasks have finished and consequently no new input versions will occur (cf. [HJKW96]) Support for collaborative workflows: Collaborative workflows are supported in our approach by integrated document management services and flexible dataflows which provide controlled cooperation on the workflow level. We discuss these issues in the next section 3.5 Integrated Document ....

[Article contains additional citation context not shown here]

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, 1996; pp. 331-341.

.... and packaged in an experience base [3] By analyzing historical data concerning feedback, problem spots in the software process may be identified (e.g. feedback with long distances between source and target or a large number of iterated process steps) The DYNAMITE approach (DYNAMI c Task NE ts) [15, 17] meets these requirements. In DYNAMITE, software processes are represented by nets of tasks connected by control flow and data flow relations. Each task has an interface and a realization, the latter of which is either complex or atomic (task hierarchies) Tasks and relations are dynamically ....

....feedback relations. Different propagation patterns (R4) may be encoded by customized graph productions and transactions. Previous papers have introduced our overall approach to managing software processes, focusing on the overall formal foundation in [14] on software engineering applications in [15], and the DYNAMITE environment in [17] In contrast, the current paper specifically focuses on feedback handling and presents novel contributions not published so far, neither in own publications nor by others. In particular, we come up with a list of requirements, discuss the features built into ....

[Article contains additional citation context not shown here]

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic Task Nets for Software Process Management. In Proceedings of the 18th International Conference on Software Engineering, pages 331--341, Berlin, Mar. 1996. IEEE Computer Society Press.

.... (see figure 1 and 3) It is out of the scope of this paper to present details about the workspace capabilities (see [Joe98] Rather, we like to show, how data exchange between simultaneously active instances can be controlled on the workflow level by means of the simultaneous dependency (cf. [HJKW96]) The definition of this dependency is illustrated in figure 3. It relaxes the activation condition so that the dependent task does not have to wait for the termination of the preceding task; a task is enabled when all mandatory inputs are available and the preceding task has been started. The ....

....can be treated like a state transtion, and on the fly changes are supported in the presence of distributed workflow enactment since every task instance object has the knowledge about how to react on a change. The basic idea of this approach has been presented in our previous work DYNAMITE [HJKW96] on software process management, and all details of our approach to managing evolving workflow specifications can be found in [JoHe99b] Whether a change is allowed and how to react on it highly depends on the particular situation and the behavior of the involved tasks. In this paper, we ....

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, 1996; pp. 331-341.

....rules (see [30] for all details) Our enactment model is based on treating tasks as reactive components which encapsulates their internal behavior and interact with related tasks of the task graph by message event passing. This is a natural basis for a distributed enactment of workflows (cf. [18, 22, 53, 54]) which was one of the design goals of our approach (beside of flexibility) Every task type inherits from a predefined statechart which defines the fundamental states and transitions of a task (illustrated in figure 5) A task has several built in operations transitions, which can be categorized ....

....handled by event trigger mechanisms. Furthermore, we allow to redefine the application condition as well as the event handling rules for certain task and process definitions as explained below. The basic idea of this approach has been presented in our previous work on software process management [22]. 14 5.1.1 Change Primitives The following list gives an overview of the basic change primitives with their pre defined enabling condition which is based on the execution state of the instances. Note, that by means of selective propagation those instance can be selected which fulfill the ....

[Article contains additional citation context not shown here]

Heimann P., Joeris G., Krapp C.-A., Westfechtel, B.: DYNAMITE: Dynamic Task Nets for Software Process Management. In Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, pp. 331-341 (1996).

No context found.

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic Task Nets for Software Process Management. In Proceedings of the 18 th International Conference on Software Engineering, 1996.

....errors occur which result in feedback to earlier steps in the lifecycle, requirements change, etc. These changes challenge the capabilities of a process centered software engineering environment: its model of the real world process must be modified on the fly [26] Accordingly, in DYNAMITE [15] software processes are represented by dynamic This work was partially supported by the German Research Council (DFG) It is an extended version of a paper presented at the 18th International Conference on Software Engineering in Berlin, Germany [15] 2 Graph Based Software Process Management ....

.... on the fly [26] Accordingly, in DYNAMITE [15] software processes are represented by dynamic This work was partially supported by the German Research Council (DFG) It is an extended version of a paper presented at the 18th International Conference on Software Engineering in Berlin, Germany [15]. 2 Graph Based Software Process Management task state deadline impl. A ready 97 4 5 test B active 97 3 3 review C waiting 97 5 5 . b) external views a) internal representation task node task relation node task graph : production CreateTaskRelation = graph rewriting system PERT ....

[Article contains additional citation context not shown here]

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proceedings of the 18th International Conference on Software Engineering, pages 331--341, Berlin, Mar. 1996. IEEE Computer Society Press.

....activity is finished or will definitely not be executed. 3) The deadline operator says that an activity A can be started only if activity B has not been started. 4) Simultaneous engineering is another good example which also shows the need for advanced data flow modeling capabilities (cf. [13, 15]) in this case, dependent activities can overlap and an activity may pass intermediate results to subsequent activities. In contrast to these requirements, several process modeling languages are based on Petri Net like or equivalent semantics: an activity is represented as one monolithic block, ....

....Workflow Enactment by Reactive Components This section sketches the basic execution model of our approach which is the basis for the detailed consideration of the definition of the execution behavior of a task in the next section. We follow the idea of treating tasks as reactive components (cf. [13, 5, 27, 26]) instead of interpreting a workflow instance by a (centralized) workflow engine, a workflow is directly enacted by distributed task instance agents which interact by event passing. A task has several built in operations transitions, which can be categorized into state transition operations, ....

[Article contains additional citation context not shown here]

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, 1996; pp. 331-341.

.... a copy of a task definition is created (e.g. as in the petri net based SPADE approach [1] and enriched by execution relevant information (e.g. assignment of start tokens) nor separated representation formalisms for schema and instance level nets are used (e.g. as in EPOS [12] or DYNAMITE [10]) Rather, only the actual task instances with their execution state, their dynamic invocation hierarchy, and their actual dataflow are covered at instance level. Because of our focus on collaborative and human centered workflows, we have integrated workspace management facilities to support ....

....Thus, the applicability of a change operation to a task or workflow definition depends on the execution state of all associated instances and the impact of the operation is handled by event trigger mechanisms. This approach has been proposed in our previous work on software process management ([10]) Example: When a new task dependency is added, a corresponding event dependency added is sent to the relevant task instances which react on this event as defined in their behavior specification. In general, they will reevaluate their activation condition and probably will trigger the enable, ....

[Article contains additional citation context not shown here]

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, 1996; pp. 331-341.

....process instances, and exception handling, cf. 6, 4] 2. Mechanisms to flexibly control the flow and assignment of work : This should include actor driven, document based and process based concepts and in particular mechanisms for handling product changes and feedback s in the process, cf. [15]. 3. Transactional support : In order to co ordinate concurrent execution of both manual and automatic tasks and to support the automation of process steps, relaxed and adaptable transaction protocols have to be provided and integrated with the execution behavior specification, cf. 11] 4. ....

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: DYNAMITE: Dynamic Task Nets for Software Process Management. In Proc. of the 18th Int. Conf. on Software Engineering, IEEE Computer Society Press, 1996, pages 331-341.

....changes to the enactment level are already presented in section 2. These are the instantiation of alternative subnets to follow, feedback during task execution, evolving task nets corresponding to the product structure, etc. A detailed description of anticipated dynamic changes can be found in [16, 17]. The process model presented in section 3 is designed to support these kind of changes. The most difficult kind of change are the unanticipated changes. They affect the specification level of the model. They are difficult to handle since the execution semantics and the structural consistency of ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic Task Nets for Software Process Management. In Proceedings of the 18 th International Conference on Software Engineering, 1996.

....with the help of extension mechanisms offered by UML. By means of these mechanisms (stereotypes and properties) we introduce modeling elements such as tasks, inputs and outputs, data and control flows, etc. The process meta model is based on DYNAMITE, which is an acronym for DYNAMIc Task NEts [6]. In addition, DYNAMITE stands for a process management environment [7] which is used to support the execution of software processes. To this end, process models encoded in UML are transformed into executable process models for the DYNAMITE environment. In this way, process modelers are shielded ....

P. Heimann, G. Joeris, C.-A. Krapp, and B. Westfechtel. DYNAMITE: Dynamic task nets for software process management. In Proc. ICSE `18, pages 331--341, Berlin, Mar. 1996.

....specifies how the task may be accomplished. Thus, the task body corresponds to a workflow in a narrower sense or to the implementation of an atomic step. Of course, both concept are well known from software engineering and are at least an im portant requirement for reuse of process models (cf. [HJKW96, EsDa96]) Nevertheless, they are not satisfied by those process modeling approaches where complex workflows directly contain several subworkflows rather than applied occurrences of independently defined tasks. In order to define the task interface and what a task should perform in particular, the output ....

....we have to relax the start condition so that an activity can start when the needed input data is available. Finally, the termination condition is defined as an end end dependency guaranteeing that all predecessor tasks have finished and consequently no new input versions will occur (cf. [HJKW96]) Beside parallel and conditional branching several advanced branching and synchronization operators are very useful a few of which we listing in the following (cf. JaBu96, ReDa98] 1) Our first example is the SEQ operator which forces a set of activities to execute sequentially, but in any ....

[Article contains additional citation context not shown here]

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, Berlin, Germany, 1996; pp. 331-341.

....C) Integration Aspects of Process Repository Space (1) The process and product structure, i.e. the decomposition of processes products and their (static) dependencies, have great interdependencies. Often, the product structure determines parts of the activities which have to be done (cf. 10] [9]) 2) Reflexivity: Obviously, process specifications are documents. Thus, the representation formalism has to provide reflective features (cf. 6] 3) The formal input output relationship holds between (abstract) process and product specifications and determines which kind of input and output a ....

.... Integration of different work environments needs coordination and cooperation support on process, actor, and data level (see Figure 1) For example, cooperation may be explicitly controlled on process level by propagation of changes, and intermediate results (simultaneous engineering) cf. [9]) may be implicitly controlled on data level by extended transaction protocols (cf. 8] or may be supported by direct interaction between different actors (e.g. video conferencing) Thus we have to consider direct and free interaction between work environments as well as controlled ....

[Article contains additional citation context not shown here]

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, IEEE Computer Society Press, 1996, pp. 331-341.

....and execution behavior do not take versioning into account. Moreover, most often only poor work environment and cooperation support is provided by this approach. Examples of this approach are Petri net based or activity centered process management approaches like Spade [BFGL94] or DYNAMITE [HJKW96]. The latter is particularly designed to cope with the dynamic nature of software processes, and provides some remarkable capabilities to support change processes. It provides specific mechanisms for feedback handling and supports cooperation on process level by passing of intermediate results ....

Heimann, P.; Joeris, G.; Krapp, C.-A.; Westfechtel, B.: "DYNAMITE: Dynamic Task Nets for Software Process Management", in Proc. of the 18 th Int. Conf. on Software Engineering, IEEE Computer Society Press, 1996, pages 331-341.

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