P. Heimann, C.-A. Krapp, and B. Westfechtel. An environment for managing software development processes. In Proceedings of the 8th Conference on Software Engineering Environments, pages 101-109, Cottbus, Germany, Apr. 1997.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....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 ....

P. Heimann, C.-A. Krapp, and B. Westfechtel. An environment for managing software development processes. In Proc. 8th Conf. on Software Engineering Environments, pages 101-109, Cottbus, Germany, Apr. 1997.

....resources, and products at an informal level. Section 3 presents cutouts of the corresponding PROGRES specifications. Section 4 discusses related work. Section 5 concludes the paper. 2 Management Models 2. 1 Process Model Our process management model is based on DYNAMIC Task nets (DYNAMITE [11]) which support dynamic development processes through evolving task nets. Editing, analysis, and execution of task nets may be interleaved seamlessly. A task is an entity which describes work to be done. The interface of a task specifies what to do (in terms of inputs, outputs, pre and ....

P. Heimann, C.-A. Krapp, and B. Westfechtel. An environment for managing software development processes. In Proceedings of the 8th Conference on Software Engineering Environments, pages 101-109, Cottbus, Germany, Apr. 1997.

.... 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 ....

....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 DYNAMITE in order to meet these ....

[Article contains additional citation context not shown here]

P. Heimann, C.-A. Krapp, and B. Westfechtel. An Environment for Managing Software Development Processes. In Proceedings of the 8th Conference on Software Engineering Environments, Cottbus, Germany, Apr. 1997. IEEE Computer Society Press. To appear.

....and Gregor Joeris 3 can be described by graph rewrite rules in a uniform formal framework. Since the specification is operational, executable code may be generated from the specification. In this way, a rapid prototype of a process centered software engineering environment may be constructed [16], avoiding manual coding in a conventional programming language. For this purpose, we are using the PROGRES development environment [35] The users of the DYNAMITE environment are shielded from the internal data structures and the underlying graph rewriting system (Fig. 1b) DYNAMITE offers ....

.... view of a task net resembling a PERT chart, and the tasks to be performed by a developer are displayed in a tabular agenda as in [1, 31] In previous papers, we have introduced DYNAMITE in an informal way [15] and have described the process support tools provided by the DYNAMITE environment [16]. In contrast, this paper mainly focuses on the underlying formal specification. In fact, DYNAMITE is a sophisticated practical application of graph rewriting. Thus, we describe our specification approach in some detail and discuss its advantages and shortcomings. In Sec. 2, we introduce dynamic ....

[Article contains additional citation context not shown here]

P. Heimann, C.-A. Krapp, and B. Westfechtel. An environment for managing software development processes. In Proceedings of the 8th Conference on Software Engineering Environments, pages 101--109, Cottbus, Germany, Apr. 1997. IEEE Computer Society Press.

....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 from the formalism for defining executable process models (the ....

....especially when use cases are defined redundantly. 5 ENVIRONMENT GENERATION The UML itself is not executable, i.e. process models described in UML can neither be simulated nor enacted. However, they can be transformed into an executable form as follows. We employ the DYNAMITE environment [7] to support process enactment. DYNAMITE has in turn been constructed with the help of PROGRES [20] an environment for executable programmed graph rewriting systems. To this end, we have specified the process meta model for dynamic task nets as a programmed graph rewriting system [8, 12] Node ....

P. Heimann, C.-A. Krapp, and B. Westfechtel. An environment for managing software development processes. In Proc. 8th Conf. on Software Engineering Environments, pages 101--109, Cottbus, Germany, Apr. 1997.

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