System Architect

Creation of architectural concepts for a (new) functional description. The documentation takes place on a Confluence page. Starting with a draft/brainstorming, there is constant development until a concrete functional architecture has been developed. The implementation of this functional architecture is not part of the specifications

Creation of architecture documentation using the tools set for the specific Software Program. These tools may include standard SW such as Enterprise Architect. The documentation must include the following information which will then be aggregated into an Architecture Definition Document (ADD):

* High Level Architecture Diagram

* Use Cases Diagram

* Component Diagram

* Interface Diagram

* Sequence Diagram

* Technology Architecture

Carrying out various architectural coordination with functional partners (internal and external) and system suppliers:

* Architecture handover to the function owner for further processing

* Planning, preparation and implementation of architectural workshops/appointments with other architects, for architectural reviews and know-how transfer

* Regular coordination with E2E architects

All architectures must be created taking into account the following criteria:

Use of existing technical conditions such as supplier systems or technical resources.

Consideration of the current state of technology: The ability to innovate is essential for existing functional architectures in order to keep up with changing times. The challenge is to combine old, historically grown systems with new technologies, such as the vehicle architecture requires.