Books for you

50 ). This fi gure is a static view of Figure 2.49 . The dynamic information
about the fl ows is lost in this representation ( Figure 2.50 ).
FIGURE 2-49
The activity of the system process ??? car usage. ???
?«systemProcess?»
act Car usage
Start car usage
Show car
usage data
End car usage
FIGURE 2-50
The function tree for the system process ??? car usage. ???
bdd [package] Car usage [function tree]
?«systemProcess?»
Car usage
?«activity?»
Start car usage
?«activity?»
Show car usage
data
?«activity?»
End car usage
84 CHAPTER 2 The Pragmatic SYSMOD Approach
2.4.4 Model Use Cases Without Redundancies
Non-redundant modeling of use cases is shown in Table 2.12 .
This step is used to refactor our model [16]. This means that we change the
structures of the model without adding new domain information. The model is
cleaned up, so to speak, to create a better basis for expansion.
As soon as we have fi nished creating essential use case descriptions we have a
possibility to detect redundant fl ows. These are identical fl ows that occur in several
use cases.


Pages:
177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201