System and Service Architecture

Project Name

System and Service Architecture

Approval

Title
Issue Number / Revision Number
Author / Date
Approved By / Date of Approval

Change Log

Reason for change / Issue Nr. / Revision Number / Date

Change Record

Issue Number / Revision Number0
Reason for change / Date / Pages / Paragraph(s)

Distribution

Name/Organisational Unit

Table of contents:

1Introduction

2Overall System Architecture

3Design and Development Plan

4Design Justification File

Design Justification Form #1 - Item or area concerned

Design Justification Form #2 - Item or area concerned

Page 1/6

1Introduction

The System and Service Architecture (SSA) is dedicated to defining and specifying the

overall pilot system starting from the high level architecture down to its building blocks.

The SSA shall describe types of applications, targeted user groups, extent of development

and/or integration of hardware, software and content elements and choice of the most

appropriate system to be used in the project.

1.1Reference Documents

Ref. / Document ID. / Title / Rev.

1.2Acronyms

Tag / Description
SSA / System and Service Architecture

2Overall System Architecture

This section shall include a presentation of the overall system architecture, broken down into its key subsystems (typically one or more diagrams), with associated description of these subsystems, their roles, data/information flow among them, main interfaces (internal and external) and protocols, as relevant.

A specific emphasis should be given to the elements which will be developed, customised, integrated in the framework of the project

This section shall also clearly point out the strategic role of the satellite component/s in the proposed system compared to potential alternatives.

The SSA shall provide a provisional list of the sites (or areas, if related to mobile units) where the system will be installed for the pilot utilisation.

Within the SSA, the Contractor shall clearly indicate the source of procurement for the differentelements (e.g. purchase of commercial products (COTS), loan from partners or sponsors, developments performed within the contract) and the associated economic value, and whether they are long lead items.

3Design and Development Plan

Projects addressing development of hardware and/orsoftware shall include a design and development plan to illustratein a concise and conceptual manner the logical execution of the proposeddevelopment activities.

It shall define and include decision points upon which thecourse of the development will depend, together with the relevant quality standardand procedures, where applicable.

4Design Justification File

The SSA shall include the Design Justification File (DJF)documenting and detailing the trade-off processes performed to justify the designchoices, and the associated design documents. This will apply to either elements to bedeveloped or elements that need to be selected from already available solutions.

The following template provides the explanation of the different line items (which are generic to allow these forms to be used in different hardware and software areas):

Item/Area: Item or area

Date:Self explanatory

Design Choice: Statement of the issue that leads to design choices

Solution:Proposed decision i.e. proposed best solution to the design decision

Alternatives: Alternative solutions considered and reasons for non-selection (these should be supported by analyses in the appendix)

Impact:Impact on other parts of the development

Comment: Other relevant information

Analyses:In appendix.

Note: the above line items should be modified to reflect the needs of your project, company procedures, etc.

Examples of the Justification Forms are given below.

Design Justification Form #1 - Item or area concerned

Item/Area
Date
Design Choice
Solution
Alternatives
Impact
Comment
Analyses

Design Justification Form #2 - Item or area concerned

Etc.

Page 1/6