o Value: it is either 24/7 or 12/7. The example in Figure 75
shows a registered night parker.For the sake of clarity, we note for the reader that other attributes can be added
for each VE as well as other Values and MetaData. These highly depend on the
deployment of the PBL facility, which definitely changes e.g., from one city to
another.
Functional view
Technical scenarios
Besides the rather static descriptions provided by the Physical-Entity View, the
IoT Context View, and the business goals (see previous sections), we have
found that the semi-dynamic view of UML use-case diagrams is very helpful in
the identifying salient FCs in the functional decomposition and also the
interactions and interfaces of said FCs. Below we provide use-case diagrams
for all major technical use-case scenarios of the PBL system.
Notice that the system-boundary boxes in the use-case diagrams are not
synonymous to the boundary of the PBL system. Rather, they elude to entities
in the context view (see Figure 73 ). All thick-lined boundary boxes are part of
the PBL system (see Figure 74 ).