CashFlow, A Visualization Framework for 3D Flow - Studierstube ...

Software Design3.5. General CashFlow UML Diagram3.5 General CashFlow UML DiagramFigure 3.9: Simplified CashFlow UML diagram showing data access. All nodes accessing data are derivedfrom Data Consumer. A DataConsumer uses a virtual array provided by the DataAccess node to access theactual data inside the MultiData node. Topology and connectivity information is offered by the Grid node.The Loader inserts data from files into the MultiData node (write access). The Mapper nodes create newdata by processing existing data (read/write access). Render nodes read data only and create images.Complete CashFlow UML diagram in figure 4.5 page 71.When looking at the CashFlow framework using a top–down approach all nodescan be separated in Data nodes and Data Consumer nodes. These nodes are sketchedin an UML diagram in figure 3.9.• Data nodesare used to store and access data.– MultiData nodes are used to store any type of data.– DataAccess nodes define the virtual array and provide virtual array iterators.These nodes always link to a MultiData node the virtual array isdefined on.– Grid nodes specify the type of grid the data is defined on. Grid nodes alsoprovide grid iterators used for accessing several different grids using oneinterface. A Grid node always links to a DataAccess node.The DataConsumer nodes can either handle grids or access data without referringto a grid structure. If grids are processed a reference to a grid node and areference to a DataAccess node is required. The DataAccess node itself links toa MultiData node. On the other hand if only data is manipulated one referenceto a DataAccess node is sufficient. As already mentioned the DataAccess node49