Prev | Current Page 177 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"


Write down the standard fl ow of a use case freely out of your gut feeling. For
example, this could look like in Figure 2.43 for our use case start car usage .
The pragmatic use case description corresponds to the explanations we
obtained from the domain experts. The essential description we are looking for
has a higher degree of abstraction. We want to detach from the technical realization
and limit ourselves to the domain core??”the essence.
As an example let ??™ s look at the fi rst step of our pragmatic description. We discover
a technical detail: the customer card. Inserting and reading the customer
card are not the domain intention. These two steps are not the goal of the on-board
computer. From the domain perspective what these two steps do is they identify
a customer. We could easily think of a different technical implementation.
We similarly proceed step by step in the use case and distill the essence out of
it. Since the description is more abstract it won ??™ t come as a surprise that it is much
shorter than the pragmatic description.


Pages:
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189
rozrywka i hobby noclegi zakopane Bukmacher pinacle Spa w Ciechocinku bramy