Results for area 10 Architecture and Terminology
association where the target class is an aggregate; therefore the source class is a part
NOTE 1 to entry This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “aggregate”
characteristic of information, which prevents the possibility to determine directly or indirectly the identity of the data subject
process by which personal information (PI) is irreversibly altered in such a way that an Individual or a legal entity can no longer be identified directly or indirectly either by the controller alone or in collaboration with any other party
personal information that has been subject to a process of anonymisation and that by any means can no longer be used to identify an Individual or legal entity
application that uses ASN.1 encodings for communication (except XER)
ITS-S application process residing in the ITS-S facilities layer
application that uses XML encoding
ITS set of concepts and rules for an intelligent transport system describing the inter-relationship between entities in the entire system, independent of the hardware and software environment
NOTE Architecture is described through a series of viewpoints that may be at varying levels of generality/specificity, abstraction/concretion, totality/component and so on. See also communications architecture, logical architecture, organizational architecture, physical architecture, reference architecture and system architecture definitions below.
specific form of a system architecture for use as a tool in the initial stages of an ITS implementation; non specified system design for a family of functionally different ITS systems, interconnected to operate in consort; it is the non specified system design for a family of functionally different systems, interconnected to operate in harmony. An ITS architecture can be described from different viewpoints, and from multiple viewpoints by conceptual, logical and / or physical representations.
NOTE An ITS Architecture is not specific to any single location. Additional terms may be explicitly referenced in individual standards or references to the source definition explicitly provided.
a TICS Architecture can be described by conceptual, logical and/or physical representations; (see also Conceptual Architecture, Functional Architecture, Logical Architecture, Deployment Design); a TICS Architecture is not specific to any single location
one or more instances of the use of the ASN.1 notation for type, value, value set, information object class, information object, and information object set (as well as the parameterized variant of those), encapsulated using the ASN.1 module notation [ISO/IEC 8824)
semantic relationship between classes
method of writing specifications and developing applications, based on a platform-independent model (PIM)
NOTE: A complete MDA specification consists of a definitive platform-independent base UML model, plus one or more platform-specific models (PSM) and interface definition sets, each describing how the base model is implemented on a different middleware platform.
NOTE 1 to entry: It is additional information about a piece of data (element). Often attributes are used to pass information about the element and hence can be said to provide metadata for the element. An attribute is a value indicator (=) and the attribute value is specified within the tag (i.e. <H3 align=”centre”>). Attribute in XML is a name=”value” pair that can be placed in the start tag of an element. For XML, all values have to be quoted with single or double quotes.
association that connects exactly two classes
any personal information related to a natural person revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, health data or sex life; its processing is prohibited except for closing circumstances
data type whose range is a list of predefined values, called enumeration literals
any of a group of data structures (i.e. object class, property, value domain, data elements, message, interface dialogue, association) referring to abstractions or things in the natural world that can be identified with explicit boundaries and meaning and whose properties and behaviour all follow the same rules
description of the organization of data in a manner that reflects an information structure
NOTE See also information model.
organized and constructed (electronic data base) compilation of descriptions of data concepts that provides a consistent means for documenting, storing and retrieving the syntactical form (i.e. representational form) and the meaning and connotation of each data concept
<XML> enable elements and attributes with specific names and types (both simple and complex) to appear in document instances
data concept; grouping of data elements primarily for the purpose of referring to the group with a single name, and thereby efficiently reusing groups of data elements that commonly appear together (e.g. ASN.1 SEQUENCE, SEQUENCE OF, SET, SET OF or CHOICE) in a message specification
NOTE This data concept type may be used to specify groups of data elements for other purposes as well.
registration process to store data definitions, characterized in a consistent manner, as determined according to the provisions of ISO 14817, used for a specific purpose (in this case ITS/TICS)
NOTE The data registration process provides a determination of the ITS Data Dictionary items accepted into the ITS/TICS Data Registry. The Data Registry contains not only data about data concepts in terms of their names and representational forms but also substantial data about the semantics or meaning associated with the data concepts. A Data Registry may contain data that assists information interchange and reuse, both from the perspective of human users and for machine-interpretation of data concepts. The Data Registry is comprised of items only from ITS/TICS Data Dictionaries, showing their source; however, not all ITS/TICS Data Dictionary items shall necessarily be submitted for inclusion, or accepted, into the Data Registry.
<XML> create new types (both simple and complex)
<UML> diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships
data concept; collection of all the temporal sequences of messages, including variants such as multiple responses, that are used to accomplish the services that the interface dialogue provides
privacy stakeholder that processes PI on behalf of and in accordance with the instructions of a PI processor
a specific application area which comprises one or more ITS service groups
formal set of production rules that comprise a grammar defining language, such as XML
one of several architectural viewpoints of the system of interest, showing the functionality that will be needed to fulfil the requirements expressed in the user needs, this functionality being shown as a series of functions and data stores plus the data flows between them and the data flows between the functions and the terminators
one of several architectural viewpoints of the system of interest, showing how the functionality from the functional viewpoint can be allocated to different physical locations and combined into different building blocks
a subset of a physical architecture which mainly considers the realization of providing one or more service(s)
globally unique identifier that is unique in space and time, i.e. no other object will ever have the same identifier at any other place and at any time
a description or definition of a design in terms of its processes and data flows; it does not include hardware or physical items; a functional Architecture is an aspect of a "Logical", "Process Oriented" decomposition of an overall TICS Architecture (see Process Oriented Logical Architecture); a functional Architecture is not specific to any location; a description of the system in terms of functions and information flows between the functions
with respect to a Process Oriented Logical Architecture, the Physical Architecture is the allocation of the functions and data flows of the logical architecture to physical entities (but not relate to the deployment of equipment) (see Process Oriented and Logical Architecture); a Physical Architecture, whilst describing physical configurations in system terms, is not specific to any particular location
taxonomic relationship between a more general element and a more specific element
NOTE 1 The more specific element is fully consistent with the more general element (it has all of its properties, members, and relationships) and may contain additional information.
NOTE 2 In the metamodel, a Generalization is a directed inheritance relationship, uniting a GeneralizableElement with a more general GeneralizableElement in a hierarchy. Generalization is a subtyping relationship; that is, an Instance of the more general GeneralizableElement may be substituted by an Instance of the more specific GeneralizableElement.
instance of an object identifier type which relates to an associated module
NOTE In ISO/IEC 8824 a module identifier is defined as: ModuleIdentifier::= modulereference DefinitiveIdentifier If the "DefinitiveIdentifier" is not empty, the denoted object identifier value unambiguously and uniquely identifies the module being defined. No defined value may be used in defining the object identifier value.
reference identifiers which relate to prescribed Sub Modules determined in subordinate Standards
establishes the link between a data subject and its PI or a set of PI
conditions which result in a data subject being identified, directly or indirectly, on the basis of a given set of PI
rights of an invididual to have access to personal data held about the individual and ability to challenge and correct such data
with respect to process oriented decomposition, the Information Architecture defines the entities and the relationships of information (Data model) and the principal data constructs (see Process Oriented and Logical Architecture)
NOTE The Information Architecture is not specific to any location
system of facilities, equipment and ITS services that is needed for the operation of an organization
NOTE 1 to entry: Specifically in the case of C-ITS the most stationary part of C-ITS incorporating sensors, actuators, static ITS Station(s).
instance of some information object class, being composed of a set of fields which conform to field specification of the class; graphical representation that logically organizes various data concepts by depicting key relationships among the data concepts
EXAMPLE An information model might specify that a Vehicle may be described by a variety of properties, such as: Make, Model, Year, and Vehicle Identification Number. Likewise a Collision might be described by properties such as Time of Occurrence, Severity, and Number of Vehicles Involved. Finally, the model might depict that a Collision has a many-to-many relationship to a Vehicle.
NOTE Information models can be depicted using UML Class Diagrams.
architecture based on political or administrational infrastructure partitioning and its division of responsibilities (rather than functions)
language for defining interfaces to CORBA objects which is independent of platform, operating system and programming language
minimum component capable of independent functionality
IRI compact string of characters for identifying an abstract or physical resource
<XML> set of unique identifiers
NOTE 1 to entry: Namespace is a mechanism to resolve naming conflicts between elements in an XML document when each comes from a different vocabulary. It allows the commingling of like tag names from different namespaces. A namespace identifies an XML vocabulary defined within a URN. An attribute on an element, attribute, or entity reference associates a short name with the URN that defines the namespace; that short name is then used as a prefix to the element, attribute, or entity reference name to uniquely identify the namespace.
Namespace references have scope. All child nodes beneath the node that specifies the namespace inherit that namespace. This allows nonqualified names to use the default namespace.
scheme for the arrangement or division of objects into groups by functional area
a subsystem of a TICS system, assembly, or other major element of a system which does not have, by itself, independent operational functionality
framework that tells designers how elements of hardware and software are to operate in harmony using common protocols and air interface techniques (where applicable)
one of several architectural viewpoints of the system of interest, showing the links between the building blocks in the physical viewpoint that will enable them to communicate with each other, and including details of expected data throughputs and any other constraints that will affect the eventual choices of communications hardware and software
data concept; an expression of the inherent concept embodied in a data element without regard to the value domain(s) by which it can be physically represented.
NOTE A data element concept is represented by an object class and a property of that object class.
association where the target class is a composite; therefore the source class is a part that is strongly owned by the composite and may not be part of any other composite
NOTE This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “composite”.
<UML> endpoint of an association, which connects the association to a classifier
<UML> endpoint of an association, which connects the association to a classifier
a statement summarising the overall concept and goals that the standard seeks to achieve
individual occurrence of a data concept
cooperative systems subset of overall ITS that communicates and shares information between ITS stations to give advice or facilitate actions with the objective of improving safety, sustainability, efficiency and comfort beyond the scope of stand-alone systems
NOTE 1 to entry: As an alternative to a “subset”, cooperative-ITS could be viewed as a “paradigm” in overall ITS.
acceptable standard of accuracy of personal data
<XML> set of valid literals for a data type
definition of the processes (the activities and functions) that are required to provide the required 'User Services'; describes how the system behaves, including what it does with the inputs that it receives and how it produces the outputs
NOTE It may be described either from an object oriented, or process oriented, perspective and describes the system according to its behaviour (and may also be called the "Functional Architecture" or"Functional Viewpoint" ). In an object oriented perspective a logical architecture elaborates the conceptual behaviour and in so doing defines some detail of the objects. In a process oriented perspective, the logical (or functional) architecture determines the nature of the system (in terms of functions and data stores), and describes its conceptual behaviour and the detail of what must be done to the inputs to produce the outputs. The logical architecture is independent of any hardware or software approach.
word denoting a description that is one level of abstraction above the concept being described
any documenting characteristic of a data concept
representation of an entity from which the important elements have been abstracted by removing unimportant detail while at the same time retaining the interrelationship between the key elements of the whole
NOTE A model may be made more or less abstract by the successive suppression of detail such that the concepts and relationships come into enhanced focus and become more readily understood. However the process can be taken too far when the simplification has exceeded the threshold where a necessary understanding may be achieved. Thus the process of modelling is one of going only far enough to achieve the optimum understanding and insight — and no further.
NOTE A model is a way of representing something, other than in its natural state.
data concept; structural relationship
ITS service which provides directional information to an individual during a trip
indexical term used by humans as a means of identifying data elements and other data concepts
a design in generic terms based on a requirement rather than an exact identification of equipment specification or manufacturers identification
inter ORB protocol that defines the message formats between ORBs in a distributed environment
rigorous statement of policy, sometimes expressed in the format IF…THEN…ELSE…, that must be followed when the stated conditions are satisfied
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.
it represents a particular instance of a class; it has identity and attribute values; the same notation also represents a role within a collaboration because roles have instance like characteristics object modelling technique is an object-oriented development methodology, which can be applied to the formulation of an architecture
data concept; expression of a specific and explicit representation of some information about something of interest within the ITS/TICS domain
expression of what a stakeholder wants the ITS implementation to provide, usually written in the language of the stakeholder and thus possibly having little or no formal structure
NOTE There could be many aspirations for each ITS implementation, depending on its scope and the number of stakeholders that are involved.
prevention of misuse of computer data: legal safeguards to prevent misuse of information stored on computers, particularly information about individual people
<UML> semantic condition or restriction
NOTE 1 to entry: Certain constraints are predefined in the UML, others may be user defined. Constraints are one of three extensibility mechanisms in UML.
limits to the purposes which personal data can be used
limits to the collection of personal data
framework into which business processes are deployed and ensures that the organization's core qualities are realized across the business processes deployed within the organization
NOTE In this way organizations aim to consistently realize their core qualities across the services they offer to their clients
viewpoint showing how the "building blocks" from the physical viewpoint (or the functional viewpoint) can be allocated to the different types of organisation (or organisations themselves if known) that will be involved with the ITS implementation
data about a living individual, identified or identifiable, as determined by the privacy laws and conventions of a political jurisdiction
any data or information related to an individual or legal entity or an association of person or individuals by which the individual or legal entity or association of persons could be identified
NOTE 1 to entry: The EU-Dir 95/48/EC names in its Art 2 lit. (a) the personal information as “personal data” and defines it as: “any information relating to an identified or identifiable natural person (‘data subject’); an identifiable person is one who can be identified, directly or indirectly, in particular by reference to an identification number or to one or more factors specific to his physical, physiological, mental, economic, cultural or social identity”.
policy of openness about developments, practices and policies with respect to personal data
<XML> identification of element types and structure within a document
NOTE 1 to entry: The mark-up is not actually part of the content, but identifies the components and their roles.
element of the run-time extension of an Enumeration data type
NOTE It has no relevant substructure, that is, it is atomic. The enumeration literals of a particular Enumeration data type are ordered.
formal expression, using “shall” language, to define what the stakeholders expect the ITS implementation to provide, and from which the functional viewpoint is created, also known as “user need”
statement of user need, typically expressed in a single-sentence form to assist with later verification of compliance
<XML> processor that reads an XML document and determines the structure and properties of the data
Note 1 to entry: If the parser goes beyond the XML rules for conformance and validates the document against an XML schema, the parser is said to be a “validating” parser. A generalized XML parser reads XML files and generates a hierarchically structured tree, then hands off data to viewers and other applications for processing.
A validating XML parser also checks the XML syntax and reports errors.
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.
process based on data element transformation
a methodology based on decomposition of the Conceptual Architecture into Functional, Control and Information Architectures
types defined by directly specifying the set of its values
inter ORB protocol that allows ORBs to use the Internet as a communications bus by mapping inter ORB messages onto TCP/IP
NOTE This is an implementation of GIOP.
a statement of what objective results are to be provided by the standard and how it is intended to achieve the vision
atomic constituent of the UML model logical data structure within an XML document, a piece of data within a file [XML]
NOTE An XML element consists of a start tag, and end tag, and the information between the tags, which is often referred to as the contents. Start tags and end tags show the beginning and end of an element. A schema that can provide a description of the structure of the data describes elements used in an XML file.
a definable element of a system, which forms part of a component or system, but does not necessarily have independent operational functionality
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
representation of a series of interactions between an outside entity and the system, which ends by providing business value
NOTE A use case is a sequence of actions that an actor (usually a person, but perhaps an external entity, such as another system) performs within a system to achieve a particular goal.
<XML> short name to uniquely identify the namespace profile
<UML> stereotyped package that contains model elements, which have been customized for a specific domain or purpose using extension mechanisms, such as stereotypes, tagged definitions and constraints
Note 1 to entry: A profile may also specify model libraries on which it depends and the metamodel subset that it extends.
type which is used only for defining the value and subtype notation for a type
NOTE Associated types are defined when it is necessary to make it clear that there may be a significant difference between how the type is defined in ASN.1 and how it is encoded. Associated types do not appear in user specifications.
<UML> explicit definition of a property as a name-value pair
NOTE 1 to entry: Certain tags are predefined in the UML; others MAY be user defined. Tagged values are one of three extensibility mechanisms in UML.
NOTE 2 to entry: In a tagged value, the name is referred as the tag.
list of functions and some indication of their interfaces (or APIs) and interactions with each other and with functions located outside of the scope of the reference architecture
an identifier for a component of an architecture which indicates the component shall be elaborated in a subsequent architecture
organizational element or an individual appointed by ISO/TC 204 to undertake the day-to-day management of the Data Registry process
standards (or specifications) proposed by software vendors group or the standards proposed by multiple open standards bodies in the same functional stack
NOTE i.e. web services specification other than SOAP, WSDL, and UDDI.
set of rules for encoding electronic documents define by the World Wide Web Consortium W3C
NOTE Although developed for documents, it is today widely used for data exchange in general, usually in conjunction with an XML Schema Definition
really simple syndication comprises a Web feed format used to publish frequently updated sources of information
meaning, including concept(s), associated with a given data concept
<XML, UML> system of representing an information model that defines the data’s elements and attributes
definition of the content and structure of data using an ASN.1 type definition
facility enabling web services to add new features incrementally
one or more similar or complementary ITS services provided to ITS users
ITS service actively requesting the data that is required for the service operation
ITS service operating on data delivered without request by an actor or its system
individual's or legal entity's (data subject) explicitly or implicitly freely given agreement to the processing of its PI in the course of which the data subject has been in advance completely informed about the purpose, the legal basis and the third parties, receiving data subject’s PI, and all these in a comprehensible form
non-scheduled, non-fixed route public transport services for customers requiring special assistance and access to specific destinations at a user-requested time (e.g., disabled or elderly persons)
purposes for which personal data are collected
the exact equipment specification or manufacturers identification as installed in a deployment
ability of a device to perform its intended function under given conditions of use for a specified period of time (or number of cycles)
any natural or legal person, public authority, agency or any other body which alone or jointly with others collect and/or process and determine the purposes and means of the processing of PI, independently whether or not a person uses the PI by themselves or assigns the tasks to a processor; where the purposes and means of processing are determined by national or Community laws or regulations, the controller or the specific criteria for his nomination may be designated by national or Community law
entity or organization that controls the collection, holding, processing or use of personal information
state of an entity or a set of state variables; also the qualification of a contract or agreement
structure of expressions in a language and the rules governing the structure of a language
a set of inter-related components which interact with one another in an organised fashion to provide independent operational functionality
NOTE This is the IEEE Definition qualified with the “Independent operational functionality” phase).
framework that may be used repeatedly to meet requirements that are similar to some extent
tModel of UDDI describes a "technical model" representing a reusable concept, such as a Web service type, a protocol used by web services, or a category system
<UML> new type of modelling element that extends the semantics of the metamodel
NOTE 1 to entry: Stereotypes have to be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user defined. Stereotypes are one of three extensibility mechanisms in UML.
NOTE 2 to entry: The stereotype may specify additional constraints and tag definitions that apply to model elements. In addition, a stereotype may be used to indicate a difference in meaning or usage between two model elements with identical structure.
system architecture is a framework for ITS deployments; it is a single, high-level description of the major elements or objects and the interconnections among them
NOTE System architecture provides the framework around which the interfaces, specifications and detailed system designs can be defined. An architecture is not a product design, nor a detailed specification for physical deployment.
is an object-oriented development methodology, which can be applied to the formulation of an architecture
entity that is external to the system but with which the system communicates either to obtain inputs or to which it can send outputs
NOTE 1 Terminators may be split up into actors if necessary.
NOTE 2 In most ITS architectures, the terminators may be the same in both the functional and the physical viewpoints.
NOTE 3 In the US National ITS Architecture, a terminator defines the boundary of the system of interest. Each terminator may represent the people, systems and general environment that interface to ITS. The interfaces between terminators and the sub-systems and processes within the National ITS Architecture are defined, but no functional requirements are allocated to terminators. The logical and physical architecture views of the National ITS Architecture both have exactly the same set of terminators.
set of attributes which makes it possible to identify, contact or locate the data subject
any person or legal entity receiving PI of a data subject other than the data subject itself or the controller or the processor
<UML> description of a set of objects that share the same attributes, operations, methods, relationships, and semantics
set of fields, forming a template for the definition of a potentially unbounded collection of information objects, the instances of the class
data type (or type for short) that represents in a formalised way a class of information (for example, numerical, textual, still image or video information); the representation is conformant to definitions given in ISO/IEC 8824-1
simple type whose values are the set of all object identifiers allocated in accordance with the rules of the ISO/IEC 9834 series
type definition that does not conform to ISO/IEC 8824
individual or organisation having a right, share, claim or interest in a system or in its possession of characteristics that meet their needs and expectations
NOTE: Their involvement can be through use, manufacture of products, provision of Services, or regulation.
object-oriented modelling language specified in ISO/IEC 19501
one who directly receives and can act on ITS data or control products; an ITS user is one who receives, directly or indirectly, or provides to, the transaction of an ITS service; these users of ITS services must be human, external systems, or another source of data, e.g. detection equipment
named value denoting a characteristic of an element; a property has semantic impact
NOTE Certain properties are predefined in the UML; others MAY be user defined. See: tagged value.
protocol for transmitting private information via the Internet by using public and private keys to encrypt data
XML based specification for the interoperable exchange of metadata
NOTE It is today most commonly used to exchange UML models between UML tools. XMI is specified in ISO/IEC 19503:2005.
occurrence of a message containing the actual values for the data elements and, in some cases, data about the message
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
relationship nature of how two entities affect each other including dependencies
web services that are designed to specifically support ITS services via the internet
a formal description of the allowed content of an XML document that claims compliance to the schema; XML Schema Definitions allow for formal validation of syntactical compliance of instance documents
entity that is involved in some way with the ITS implementation
data element that cannot be further subdivided meaningfully within the context of ASN.1
basic standards are defined as those prepared by an open standards body, and are the only standards for functional stacks
dependency states that the implementation or functioning of one or more elements requires the presence of one or more other elements
specialization/generalization relationship in which an object class of a specialized element (child) is substituted for a generalized element (parent)
any operation or set of operations which is performed upon personal data, whether or not by automatic means, such as collection, recording, organization, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, blocking, erasure or destruction
natural person or legal entity or organization that processes personal information (PI) on behalf of and in accordance with the instructions of a PI controller and if it use PI only for the commissioned work
set of data grouped together for transmission