Partners: NXP, TomTom, Logica, TNO, GreenCat, TU/e, Universiteit Twente, et al.
Presentation: click here to view the slideshow of SPITS architecture objectives and architecture.
Objectives
The objectives for this work package are the definition and verification of the SPITSPlatform overall architecture. The SPITSPlatform will enable SPITS compatible applications to run during and after the SPITS project is executed. The SPITSPlatform provides open interfaces to support third party application development. The SPITS platform will be scalable and extendable.
These objectives are carried out in support of the other SPITS WPs that deliver the SPITS platform, SPITS applications and demos.
Key challenges include:
- Flexible platform architecture enabled to integrate diversity of down loadable services and user interaction
- Cost effective modular platform architecture supporting both mainstream and high-end vehicle market segments
- HW and SW upgradeability
- Security mechanisms against tampering and unauthorised use and safeguarding SPITS integrity. Security supports paid services and is compliant to privacy requirements
- Influence of safety requirements on SPITS
- Integration of existing technologies from different partners into a single architecture
- To create a network architecture supporting SPITS based on draft and worldwide variety of standards
- Standard documentation, but benefit from standard supplier development processes and quality
Validation and Implementation: WP01 will monitor the validation and implementation of the architecture as performed by the other work packages, to ensure that the implementation is compliant with the architecture. The system validation will be performed by WP07, while the validation of the subsystems will a responsibility of the respective WP's. The Architecture enables the validation and certification of applications and platform implementations also after SPITS project closure.
The engineering management and integration of all OBUs, RSUs, BOs, and application activities in the other work packages is monitored through the installation of an SPITSCCB (Change Control Board). Product quality assurance and the essential development process harmonization is addressed.
The architecture developed in this project is open. Hence, managed interface control is addressed. Instantiation of the open architecture only occurs upon implementation in a specific product line for the different OBUs, RSUs, BOs and applications.
Objectives of the Architectural deliverables
- SPITSPlatform specifications should enables ITS and Infotainment application designers to create applications and services.
- An ITS or Infotainment software designer must be able to develop an SPITS compliant application or service based on the information in these specifications. The specifications defines functions which can be used by applications.
- The SPITSSub System specifications enables SPITSSub System and SPITS Component suppliers to create related parts of the SPITSPlatform.
- A SPITS supplier must be able to develop and build compliant SPITS subsystem or SPITSComponent based on the information in these specifications.
SPITS Platform and Architecture
Intro
The complete SPITS system consists of a SPITS platform and applications. The use cases specified by WP1 describe examples of how users can use the total SPITS system. The functionality will be divided between applications and the SPITS platform, based on the reusability or other considerations. The architecture developed by WP1, describes only the platform, where the applications will be actors on the platform.
The SPITS architecture describes "the fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution". This description consists of a set of consistent views. A view is a model of (a part) of a system. Examples of views are: context view, infrastructure view, process view, requirements view, etc.
The purpose of our architecture is to define a common ground for all the participating members such that everybody has the same view on the development of the SPITS system.
The SPITS system will be decomposed in several subsystems and each subsystem will be further decomposed in smaller subsystems. Each of these decompositions is described by the workpackage developing that subsystem (see Governance section below). The decomposition should describe the complete SPITS system but describe the subsystem system in more detail. Each decomposition of the system consists of a set of views of that composition these views describe that decomposition in a consistent manner.
