Books for you

83 ).
The relationship doesn ??™ t state whether or not the requirement is fully realized
by the design element. This would require that the requirements and the design
models had identical granularities. Apart from the fact that this is not practically
feasible, it would result in an undesired dependency of the requirements on the
design. As a pragmatic approach, I recommend to use a comment to document completeness
of the realization ( Figure 2.83 ). A good alternative would be a suitable
FIGURE 2-82
Structures for ??? customer card. ???
bdd [package] Customer card
[port specifications]
ibd [block] Customer data
s:Coil
c:Chip
i:Current
i:Current
<>
e:Energy
e:Energy
p:FS_Customer-
Card ICustomerCard
flow properties
out dataOut:char[]
in dataIn:char[]
?«flowSpecification?»
FS_CustomerCard
<>
<>
125 2.7 Realizing Use Cases
stereotype with a property that describes the degree of realization, e.g., 60 percent.
Before you start using comments or stereotypes, you should of course think about
whether or not you need this information in the model at all.


Pages:
249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273