© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 1

Software &EngineeringDevelopmentTechniques

s

Research at Siemens CT SE

Dr. Andreas Ulrich

Siemens AG, CT SE 1

ph.: +49 (89) 636 47018

andreas.ulrich@siemens.com

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 2

Software &EngineeringDevelopmentTechniques

sSiemens: 56,870 R&D Employees Worldwide,

Thereof 25,000 Outside of Germany

CT / E 026 a - 08.01

Bracknell

Johannesburg

LissabonMadrid

Toulouse

Eynsham

Berlin

Brussels

Budapest

Milano

Melbourne

Sydney

Bratislava

Roke Manor

Paris

Helsinki

Zürich

Porto

Solna

Bombay

Istanbul Seoul

Penang Singapur

Taipeh

Tel Aviv

Buenos Aires

Sao PauloCuritiba

Shanghai

Yokohama

Burlington

Boca Raton

Auburn Hills

ArlingtonRaleigh

Mississauga

Paderborn

Dresden ErlangenRegensburg

Salzburg

GrazWien

Karlsruhe

Grenoble

Pittsburgh

Issaquah

Chicago

Bangalore

Santa ClaraBerkeley

SacramentoBeijing

Tokyo

places with CT activities

Orlando

Concord

AustinNewport News

PrincetonPiscataway

Redmond

New Dehli

Norcross

Palo Alto

San Jose

Danvers

Linz

Bristol

MunichChang Chun

XianChengdu Nanjing

Tian JinIchon

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 3

Software &EngineeringDevelopmentTechniques

s

Overview: CT Department “Software & Engineering”

• Department “Software & Engineering” in the Corporate Technology Division (CT SE)

• About 220 employees• Located in Munich and Erlangen• 5 Competence Centers

• Development techniques for SW systems

• SW architectures

• Development processes

• Discrete optimization techniques

• Industrial services and solutions

• CT SE mission• Support of Siemens’ divisions in their R&D activities

Consultancy in projects• Information & Communication, Medical Solutions, Automation & Control,

Transportation Systems, Power Transmission and Distribution, etc.

• Guarantee competitiveness of Siemens in the field of SW development for the future Research

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 4

Software &EngineeringDevelopmentTechniques

s

Overview: CT SE “Development Techniques”

• Groups of CT SE “Dev. Techniques” and their activities• Requirement engineering and formal SW verification• Performance engineering• Testing and quality assurance• New development techniques for smart devices

• Research in the “Testing and Quality Assurance” group• Property validation of distributed and concurrent systems based on

observed communication traces• Non-intrusive trace generation for CORBA, .NET and embedded systems

• Analysis of traces to improve dependability and trustworthiness of systems

• Test architectures for distributed and concurrent systems• Test automation solutions for .NET applications and Web services

• Test automation in the telecommunication domain

• Involvements in Siemens consultancy projects (examples)• I&C: Test automation in system test of GSM Base Stations• Med: Testing strategies for computer tomography devices

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 5

Software &EngineeringDevelopmentTechniques

s

Research Project: Analysis of Comm. Traces

• Partner of the project “Pattern-based analysis of communication traces for distributed systems” (TRACY)

• Prof. Alexandre PetrenkoCentre de Recherche Informatique (CRIM), Montréal, Canada

• Ongoing cooperation since 2000

• Problem description• Given

• An executed trace collected by monitoring a system under test

• A set of properties of interest

• Verify whether the system’s behavior represented by the trace exhibits the given properties (patterns)

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 6

Software &EngineeringDevelopmentTechniques

s

Trace Analysis Approach

• Front-end tool to Telelogic ObjectGEODE

• Model reconstruction in SDL from an observed trace

• Template library of general properties

• Event-based and state-based properties

• Described in GOAL language (similar to SDL)

Monitoring Tool

OG Simulator

GOAL Observer

SystemSpecification

PatternSpecification

UserInterface

Operator

Front-End to OG

Model checking results:1- Pattern present or not2- Scenarios

Trace

SDL Model

distributed system of processes

Event...Event

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 7

Software &EngineeringDevelopmentTechniques

s

Potential Research Topics for DeSIRE (1)

• Improve current testing techniques to support dependability of complex real-time systems

• Special focus on integration testing• Increasing complexity of systems pushes system testing to its limit

• Increasing usage of Components-Off-The-Shelf

• Definition of test stop criteria

• Support of an incremental development and test process• Incremental development is general practice in industries

• Product line development

• New approaches must be able to deal with incomplete and changing requirements, design and test specifications

© Siemens AG, CT SE 1, Dr. A. Ulrich 04/21/23

C O

R P

O R

A T

E

T E

C H

N O

L O

G Y

Research at Siemens CT SE 8

Software &EngineeringDevelopmentTechniques

s

Potential Research Topics for DeSIRE (2)

• Passive testing• Developing tracing technologies to capture the behavior of concurrent

systems• E.g. based on existing protocol analyzers

• Improve facilities to support the description of safety, reliability, security properties for practitioners

• Hiding complex formalisms to the user, e.g. temporal logic

• Active testing• Design of test architectures that scale with the system’s complexity

• Decentralized test execution, synthesis of concurrent test cases, test case selection

• Techniques to replay recorded communication traces for the purpose of regression tests

• Avoid the re-occurrence of detected faults in future versions of the system