@Entenwilli @01Parzival10 I discussed this again with Nicolas because I thought that our ideas from the last meeting missed one important part: The individual flow graphs are, in fact, not individual, but parts of a complete flow graph, that holds more information than just a list of subgraphs. To be mathematically precise: Each graph is an induced subgraph G[x], induced by the sink x. Although they are not connected, they still belong to the same DAG. So here is the updated proposal:

Let's define FlowGraph, PartialFlowGraph, and Vertex.

Flow graphs hold a list of partial graphs and also provide methods for, e.g., extracting the graph from DFDs or PCM (can be using something like an ActionSequenceFinder internally), or for lookup of vertices that represent the same model elements (PCM elements or DFD nodes).

Each partial flow graph represents the induced subgraph of one sink. Thus, it should contain methods for the propagation, for the lookup of elements that meet a constraint, and for getting the sink (and in the case of PCM even getting the source, because partial flow graphs are always a sequence in PCM).

A vertex represents one DFD node or one relevant PCM element, holds node and data characteristics, and knows about its preceding vertices. The vertex knows how to get node characteristics (could, again, be using a calculator) and how to process ingoing data characteristics (i.e., the node's behavior). However, only the partial flow graph knows how to propagate, so the partial flow assigns data characteristics to vertices.

Of course, this also means we have abstract flow graphs, partial flow graphs and vertices, and also specific implementations for DFD and PCM. This not only enhances the capabilities of the analysis (e.g., joined flows) but makes the analysis also way easier to understand and unifies a lot of concepts. Furthermore, we would also not break the object-oriented paradigm that often :)

From action sequences to DAGs #100

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions