Results for area 10.1 Architecure
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.
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.
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
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
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
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)
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
architecture based on political or administrational infrastructure partitioning and its division of responsibilities (rather than functions)
framework that tells designers how elements of hardware and software are to operate in harmony using common protocols and air interface techniques (where applicable)
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
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
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.
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
a definable element of a system, which forms part of a component or system, but does not necessarily have independent operational functionality
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.
a methodology based on decomposition of the Conceptual Architecture into Functional, Control and Information Architectures
scheme for the arrangement or division of objects into groups by functional area
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
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
an identifier for a component of an architecture which indicates the component shall be elaborated in a subsequent architecture
one or more similar or complementary ITS services provided to ITS users
ITS-S application process residing in the ITS-S facilities layer
a specific application area which comprises one or more ITS service groups
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).
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.
entity that is involved in some way with the ITS implementation
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.
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
ITS service which provides directional information to an individual during a trip
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”
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.
entity or organization that controls the collection, holding, processing or use of personal information
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)
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.
minimum component capable of independent functionality
a subsystem of a TICS system, assembly, or other major element of a system which does not have, by itself, independent operational functionality
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).
application that uses ASN.1 encodings for communication (except XER)
application that uses XML encoding
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
is an object-oriented development methodology, which can be applied to the formulation of an architecture
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.
object-oriented modelling language specified in ISO/IEC 19501