Information Technology Reference
In-Depth Information
Table 7.
(
continued
)
Concern Name:
Transaction Management
Requirements:
•
data and file
transmission
from background system to OBU via different
media: GSM CSD, GPRS, SMS
•
…include data overhead for
restart a transmission
…
•
… no
retransmission
…
Rationale:
•
In the documents there are references to
re-transmitting data
, which needs
some sort of transaction management while transmitting data in order to
detect errors and take proper action accordingly. Besides, the transaction
management could be customised in aspects to be applied to the
transmissions from ETBO only, from all ETBO and OBU transmissions,
or to transmissions from a subset of OBU. Moreover, if there are more
than one ETBO, the data synchronisation between these shall be
transactional.
Concern Name:
Communication Trigger
Requirements:
•
…the
trigger
method shall be configurable…
•
…at least the following
trigger
method should be implemented:
o
… at one or more defined time…
o
... at defined day of the week…
o
... after defined period of time, e.g., 5 hours…
o
… after journey…
o
… when a defined geoobject is detected…
o
… when available memory is used up to 70%...
Rationale:
•
This concern is likely to be implemented as an aspect since it implies a
wide set of possible options (candidates for advice) and their possible
combinations which could be customised for each system instance.
The
highlighted
concerns in Table 6 represent concerns that were missed by
Siemens' developers but they recognized them as highly relevant as, from their
perspective, these concerns might have an important impact on the architecture and
also might be implemented as aspects.
Table 7 shows details about the highlighted concerns such as excerpts of the source
requirements identified by the tool (we cannot show the complete requirements for
Search WWH ::
Custom Search