Style Guidelines and Best Practices : Activity Chart Conventions : Data Stores

Data Stores

In Rational Statemate data stores do not have any impact on code generation. Therefore they can be used as an additional means of visualization:

Data stores might represent stored information for later use (e.g. characteristic tables/maps) or describe a buffer in the computer memory (e.g. “PROCESS_BUFFER” in the Generic Top-Level Structure for ECUs figure). In these “classical” applications data stores are named with the data they contain. Unlabeled flows to or from a store carry the whole data group of the store. Flows carrying subgroups of the stored data are labeled with the respective subgroup names.
Data stores might also be used to visualize the different of communication characteristics within a system e.g. CAN BUS, J1850,… etc. For details on modeling data bus communication, refer to Modeling Bus Communication.