Internet of Things Architecture

Internet-of-Things Architecture © - 260 -

PBL #

Requirement

Type Description^ Rationale^ View^ Perspective^

Functionality

Group

Functional

Component

4

Qualitative

The system shall be

readily extensible to

encompass off-street

parking

In a future version of the system, off-street

parking might also be offered or the system shall

be able to seamlessly cooperate with third-party

systems for off-street-parking management.

(business principle)

none

spe-

cific

Evolution and

Inter-

operability

none specific none specific

11 Qualitative

The user base for the

system shall not be

limited to resident

parkers and time

parkers in future

versions of the system.

In the future new business models are envisaged

for the resident-parking service. An example is

the inclusion of employees of participating

companies in the resident-parking pool. By so

doing, the customer base for the Control Centre

and thus the total revenue that can be generated

with the Control Centre can be extended. This

will increase the attractiveness of parking

services offered to, e.g., municipalities. (business

principle)

No-ne

spe-

cific

Evolution and

inter-

operability

none specific none specific

13 Qualitative

Existing system

software shall be

reused to a maximum.

Decrease the cost and increase the ROI of the

enhanced Control Centre by maximum reuse of

existing hardware within the system but also

outside (compati-bility with existing parking-

enforcement systems, etc.). (business principle)

No-ne

spe-

cific

Evolution and

Inter-

operability

none specific none specific