Ebook Models and tools for managing development processes: Part 2
➤ Gửi thông báo lỗi ⚠️ Báo cáo tài liệu vi phạmNội dung chi tiết: Ebook Models and tools for managing development processes: Part 2
Ebook Models and tools for managing development processes: Part 2
9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 RES [Schiirr 1989; Schiirr 1990; Schiirr 1994; Schiirr et al. 1995; Schiirr et al. 1999]. rhe PROGRES specification of the management model serves in turn as a starting point for the implementation of the management system to be described in the next chapter.Note that the specification concerns the Ebook Models and tools for managing development processes: Part 2 internal representation used by management tools, hl contrast, in the previous chapter many figures showed external representations of graphs visibleEbook Models and tools for managing development processes: Part 2
at the user interface. These levels have to be separated clearly. Internal representations include all details which have to be taken care of by sophi9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 lows: Firstly, we give a brief introduction to PROGRES and motivate its application to the management of development processes (Section 9.1). The subsequent sections are devoted to the specification of the submodels for product, activity, and resource management (Sections 9.2 9.4. respectively). In Ebook Models and tools for managing development processes: Part 2 Section 9.5. we explain how general base models can be adapted to a specific application domain. Afterwards, we discuss our experiences gathered in usEbook Models and tools for managing development processes: Part 2
ing the PROGRES language (Section 9.6). Section 9.7 compares related work, and Section 9.8 gives a short summary.9.1 PROGRES at a First GlanceBuilding9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 signs, manufacturing plans. SA diagrams, software architectures, or programs. In order to realize commands to be executed on such documents, sophisticated operations on the corresponding internal data structures have to be performed. Before implementing these operations in a programming language suc Ebook Models and tools for managing development processes: Part 2 h as c, Ada, or Modula-2, a high-level specification is required from which the implementation may be derived.To satisfy this need, the specificationEbook Models and tools for managing development processes: Part 2
language PROGRES [Schiirr and Zirndorf 1996] has been developed within our group, rhe PROGRES language integrates concepts from various disciplines (d9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 ns of logic calculus the discussion of1949. Management Model: Formal Specificationwhich goes beyond the scope of this book (see [Schiirr 1991; Schiirr 1996]). Let us briefly summarize the most important language features:PROGRES is based on attributed graphs as the underlying data model. Nodes, whic Ebook Models and tools for managing development processes: Part 2 h may carry attributes, are connected by binary, directed relationships (edges), which may not carry attributes.A graph schema defines types of nodes,Ebook Models and tools for managing development processes: Part 2
edges, and attributes, thereby serving as a database schema. Node types are organized into a multiple inheritance hierarchy. All graph operations hav9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 lationships), rest lift ions (unary relationships. i.e., conditions on nodes), and constraints.Graph transformations are described declarative!}' by means of graph rewrite rules (rule-based programming style). A graph rewrite rule essentially consists of a left-hand side the graph pattern to be matc Ebook Models and tools for managing development processes: Part 2 hed and a right-hand side the replacing subgraph. “Declarative” means that the user of PROGRES is not concerned with the algorit Inns for pattern matcEbook Models and tools for managing development processes: Part 2
hing and replacement. In particular, the left-hand sides can be very general graph patterns containing paths, restrictions, optional nodes, set nodes,9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 ements (i.c.l a graph test searches for a pattern and leaves the host graph unaffected).In case the rule-based programming style does not suffice, PROGRES provides control structures for calling graph rewrite rules and graph tests (sequence, branch, various forms of loops, etc. [Zirndorf and Schiirr Ebook Models and tools for managing development processes: Part 2 199l;Schiirr 1997]). These control structures take non-determinism into account which is inherent Io graph rewrite rules because there are often diffEbook Models and tools for managing development processes: Part 2
erent pattern matches among which one can be selected for replacement, hl particular, if the appli cation of a rule fails, backtracking is triggered s9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 et al. 1999] offers tightly integrated, syntax-aided tools for const met ing specifications. The PROGRES language is hybrid in that it contains both textual and graphical parts. The editor guarantees correctness with respect to the context-free syntax and checks the rules of the context-sensitive s Ebook Models and tools for managing development processes: Part 2 yntax incrementally. The browser supports navigation along both context-free and context-sensitive relationships (in the underlying syntax tree and alEbook Models and tools for managing development processes: Part 2
ong bindings of identifiers to their declarations, respectively). The interpreter executes an intermediate graph code which is incrementally generated9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 e specification can be edited during interpret.at ion).In this chapter, we use PROGR ES to specify the structure of the management database and the operations performed on it. Attributed graphs are well suited9.2 Product Management Model 195to represent, version histories, configurations, task nets, Ebook Models and tools for managing development processes: Part 2 etc. in a natural way.The overall product management graph is a quite sophisticated graph structure which has to fulfill many consistency constraintsEbook Models and tools for managing development processes: Part 2
. Operations on the product management graph perform complicated changes which can be specified with the help of graph rewrite rules such that these c9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 project. The specification fragments to be presented were created with the help of the PROGRES environment, which also provides a tool for transforming the specification into a text-processing format. In our presentation, we do not assume that the reader is familiar with the PBO-GRES language. Bathe Ebook Models and tools for managing development processes: Part 2 r, the language constructs are explained as required. For further information on PROGRES, the reader is referred to [Schiirr 1996; Schiirr 1998],9.2 PEbook Models and tools for managing development processes: Part 2
roduct Management ModelAfter having introduced the product management model in an informal way in Section 8.1, we now turn to its formal specification9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 cy-preserving operations.9.2.1 Graph SchemaNode classes, edge types, and attributes PROGRES is based on attributed graphs. An attributed graph consists of nodes decorated with attributes and edges which do not carry attributes. An edge represents a binary, directed relationship. When a node is delet Ebook Models and tools for managing development processes: Part 2 ed, all adjacent edges are deleted as well (referential integrity). Furthermore, an edge may be traversed in both directions (from source to target, aEbook Models and tools for managing development processes: Part 2
nd vice versa).As in database management systems, the elements of graphs of a certain classe.g., product management, graphs to be discussed below are 9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 ts instances will carry. An edge type defines the classes of source and target nodes and the cardinality of its instances.Node classes are organized into a multiple inheritance hierarchy. A subclass inherits from its superclasses all attributes and adjacent edge types. Inheritance on edge types is n Ebook Models and tools for managing development processes: Part 2 ot supported.A graph schema may be represented both textually and graphically. Figure 9.1 displays a graphical schema diagram for product management gEbook Models and tools for managing development processes: Part 2
raphs; later on, we will also use the textual notation as required. In the diagram, each node class is represented by a box which contains the name of9. Management Model: Formal SpecificationTo formalize the management model introduced in the previous chapter, we use the specification language PROGR Ebook Models and tools for managing development processes: Part 2 duct management•o3-ựi~~~3" oGọi ngay
Chat zalo
Facebook