Ebook Models and tools for managing development processes: Part 2

Ebook Models and tools for managing development processes: Part 2 include of the following content: Chapter 9: management model: formal speci cation; chapter 10: management system; chapter 11: applications, experiences, and evaluation; chapter 12: overview; chapter 13: dynamic task nets; chapter 14: unified multi-project resource management; chapter 15: object-oriented process modeling; chapter 16: current status and future work.

To formalize the management mo del intro duced in the previous chapter, we

use the sp eci cation language PROGRES [Sch urr 1989; Sch urr 1990; Sch urr

1994;Sch urretal.1995;Sch urretal.1999].ThePROGRESsp eci cationofthe

managementmo delserves inturnasastartingp ointfortheimplementationof

themanagementsystemtob edescrib ed inthenextchapter

Notethatthesp eci cationconcernstheinternalrepresentationusedb

man-agementto ols.Incontrast,inthepreviouschaptermany guresshowedexternal

representations of graphs visible at theuser interface These levels have to b e

separated clearly Internal representations include all details which have to b e

takencare of b sophisticatedmanagementto ols.On theotherhand,asimple

andreadablerepresentation isrequiredattheuser interface

This chapter is structured as follows: Firstly, we give a brief intro duction

to PROGRESand motivateitsapplicationto themanagementofdevelopment

pro cesses(Section9.1).Thesubsequentsectionsaredevotedtothesp eci cation

ofthesubmo delsforpro duct,activity,andresourcemanagement(Sections9.2{

9.4, resp ectively) In Section 9.5, we explain how general base mo dels can b e

adaptedtoasp eci capplicationdomain.Afterwards,wediscussourexp eriences

gathered inusing thePROGRES language(Section 9.6).Section 9.7compares

relatedwork,andSection9.8gives ashortsummary

9.1 PROGRES at a First Glance

Building to ols for engineering design applications is a challenging task Such

to olsop erateoncomplicatedinternaldatastructures representinge.g.CAD

de-signs, manufacturingplans, SA diagrams,software architectures, or programs

Inorderto realize commandsto b eexecuted onsuch do cuments,sophisticated

op erationsonthecorresp ondinginternaldatastructures haveto b ep erformed

Before implementingthese op erations in a programminglanguage such as C,

Ada, or Mo dula-2, ahigh-levelsp eci cation is required fromwhich the

imple-mentationmayb e derived

To satisfy this need, the sp eci cation language PROGRES [Sch urr and

Z undorf1996]hasb een develop ed withinourgroup.ThePROGRES language

integratesconceptsfromvariousdisciplines(databasesystems,knowledge-based

systems, graph rewriting systems, programming languages) into one coherent

languagewhosesemanticsisde nedb meansoflogiccalculus thediscussionof

B Westfechtel: Managing Development Processes, LNCS 1646, pp 193–242, 1999.

c

Springer-Verlag Berlin Heidelberg 1999

which go esb eyondthescop eof thisb o ok(see [Sch urr1991;Sch urr1996]).Let

us summarizethemostimp ortantlanguagefeatures:

{ PROGRESisbasedonattributedgraphsastheunderlyingdatamo del.No des,

which maycarry attributes, are connected b binary, directed relationships

(edges),whichmaynotcarry attributes

{ Agraphschema de ... othcases,comp onentsforNCprogramswereomittedfrom

thegure.Attheb ottom,(cut-outsof)versiongraphsforthedo cumentsDesign,

RawDesign, and Plan are given (see Figure 8 .2 on page 1 72 for the external... des andadjacent edges(e.g.,asuccessor

rela-tionshipismo deledas aHISTORYno de andPredecessor/Successoredges)

This solution allowsfor attaching attributes to relationships, and for. .. ematched|andaright-handside

|thereplacingsubgraph.\Declarative"meansthattheuserofPROGRESis

notconcernedwith thealgorithmsforpatternmatchingandreplacement.In

particular,theleft-handsides