System architecture

Project name

Classification	Select an element
Status	Select an element
Program name
Project number
Project manager	Project manager
Version	0.1
Date	Click here to enter a date
Project sponsor	Project sponsor
Author(s)
Distribution

List of changes

Version	Date	Change	Author
0.1

Table 1:	Change control

Description

The system architecture divides the system into subsystems and their components. It describes the system structure and the interfaces. The system architecture allows for a comprehensive view of the system. Depending on the project outcome and scope, it contains several architecture elements and models, e.g. the business process model, the function model (e.g. with Use Cases/user stories), the data architecture/data model, the security architecture. It also contains the IT documentation or refers to the developer's documentation. The system architecture is based on the specifications of the controlling and compliance bodies.

System structure

Overview of the system

Overview diagrams according to the developer's methods (e.g. UML)

Subsystems and components

Visualization of the system structure according to the developer's methods

Description

Architectures/models

Reference to detailed studies

Depending on the project outcome: e.g. business process model, function model (e.g. with use cases/user stories), data architecture/data model, etc.

Technical architecture of the IT system

Products, versions used

Interfaces and scope

Interfaces with peripheral systems

Diagrams according to the developer's methods and explanations/descriptions

Reference to integration concept

Text

Boundaries

Text, possibly diagram

Feasibility assessment

Feasibility assessment, reference to prototyping documentation

Compliance with specifications

Verification of compliance with the specifications of the operator/provider

Requirement assignment and coverage

Reference to system requirements

ID	Requirement	Assignment to subsystem/component	Evaluation of requirement coverage
nn
nn

Table 2:	List of requirements with assignment and coverage

Abbreviations and glossary

Abbreviation/specialist term	Explanation
HERMES	Methodology for projects and programs HERMES 5 is an eCH standard

Table 3:	Abbreviations and glossary

Contents

List of changes	1

Description	1

1	System structure	2

1.1	Overview of the system	2

1.2	Subsystems and components	2

1.3	Architectures/models	2

2	Interfaces and scope	2

2.1	Interfaces with peripheral systems	2

2.2	Reference to integration concept	2

2.3	Boundaries	2

3	Feasibility assessment	2

4	Compliance with specifications	2

5	Requirement assignment and coverage	3

Abbreviations and glossary	4

Contents	5

Tables	5

Tables

Table 1:	Change control	1

Table 2:	List of requirements with assignment and coverage	3

Table 3:	Abbreviations and glossary	4