We name these groups accordingly.
Next we use a digital camera to capture the result. We can transfer the use cases
to our model later on. In the model the use case groups become packages. Since we
want to concentrate only on the core functions of the on-board computer for the
time being, we move the contents of the packages, navigation system , phone , and
radio , to the side in the diagram ( Figure 2.37 ).
There is normally other information that belongs to a use case, but for which
there are no meaningful model elements in SysML. This additional information
includes short descriptions, references to external documents, open issues, or
management information like priorities and cost estimates.
We can normally accommodate this information in fi elds available to describe
the use case in the modeling tool or as a comment in the diagram. We can of course
create a description in a text document outside the SysML model as an alternative. If
you opt for this alternative you have to make sure that the data stored separately??”
the model and the document??”are maintained consistently.
Pages:
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181