Results for area 2.4 Processes, phenomena and events
integration of each physical object necessary to implement one or more ITS applications
NOTE 1 to entry An ITS application typically requires multiple components (e.g. an ITS-S acting as a user and another ITS-S acting as a provider). An ITS implementation includes a sample of each component necessary for the service but often does not represent a complete deployment.
NOTE 2 to entry An ITS implementation is typically used for a laboratory or other experimental environment prior to a full-scale deployment.
structured proposal for business improvement that functions as a decision package for decision-makers The business case should explain why a project is required for the business and what the product or service is going to be. It should include an outline of the “Return on Investment” (ROI), or a cost/benefit analysis for the project, the project's product and performance characteristics, major project risks and the opportunities.
The business case addresses, at a high level, the business needs that the project seeks to meet. It includes the reasons for the project, the expected business benefits, the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a GAP analysis and the expected risks.
limits to the collection of personal data
process by which data is formally described and provided to an approved location in the Data Registry
NOTE This process is effected under the control of the ITS/TICS data registrar, in accordance with the requirements of ISO 14817.
a methodology based on decomposition of the Conceptual Architecture into Functional, Control and Information Architectures
sequence of processes that wait in the background for an event, with some of these processes triggering a separate event that can start other processes in turn
transfer of PI from the controller to a processor in the context of a commissioned work
transfer of personal information to recipients other than the data subject, the controller or a processor, in particular publishing of data as well as the use of data for another application purpose of the controller
description of the behavioural requirements of a system and its interaction with a user
[SOURCE: ISO/IEC/IEEE 26515:2018, 3.15, modified — Note 1 to entry removed.]
process by which data is formally described and provided to an approved location in the data concept registry
NOTE 1 to entry This process is effected under the control of the “ITS Registrar”, in accordance with the
requirements of ISO 14817-2.
is an object-oriented development methodology, which can be applied to the formulation of an architecture
action that circumvents all kinds of operations with the set of PI or certain elements of it meaning both processing of PI and transmission of PI to a third party