●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●

Von der Nutzungsanforderung
zur formalen Softwa...
itemis
Florian Geyer
Planung und Durchführung von UsabilityMaßnahmen im Softwareentwicklungsprozess

●
●
●
●
●
●
●
●
●
●
●...
Von der Nutzungsanforderung zur formalen
Softwarespezifikation
Modellierung mit dem Werkzeug
YAKINDU Requirements



Bede...
Bedeutung klarer Anforderungen für den Projekterfolg

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
Bedeutung klarer Anforderungen für den Projekterfolg

Benötigte
Funktionalität

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
Bedeutung klarer Anforderungen für den Projekterfolg

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
Nutzungsanforderungen und Systemanforderungen
Übersicht
abstrakt

Ziele

Geschäftsziele und Marktanforderungen
Gesetzliche...
Nutzungsanforderungen und Systemanforderungen
Ausgangspunkt – Kontextszenarien
Paul (48) ist ein Mitarbeiter der itemis AG...
Nutzungsanforderungen und Systemanforderungen
Anforderungen dokumentieren – Erfordernisse

Erfordernisse: Notwendige Vorau...
Nutzungsanforderungen und Systemanforderungen
Anforderungen dokumentieren – Nutzungsanforderungen

Nutzungsanforderungen: ...
Nutzungsanforderungen und Systemanforderungen
Anforderungen dokumentieren – Systemanforderungen

Systemanforderungen: Bedi...
Anforderungsspezifikation und -management
Anforderungen dokumentieren – Modelle, Spezifikationen

User Interface
(Mockup, ...
Anforderungsspezifikation und -management
Spezifikationsdokumente


Dokumentation der Anforderungen in einem
Spezifikatio...
Anforderungsspezifikation und -management
Anforderungen verwalten – Herausforderungen

Unterschiedliche Stakeholder
(Busin...
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●

YAKINDU R...
YAKINDU Requirements
Requirements
Navigator
Requirements
Use Cases
Entities

Texteditor

Lifecycles

Spezifikation
mittels...
YAKINDU Requirements

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
YAKINDU Requirements

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
YAKINDU Requirements

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
YAKINDU Requirements

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
YAKINDU Requirements
Dokumente generieren

PDF
HTML
MS Word
Requirements
Use Cases
Entities
Lifecycles
Actors
User Interfa...
YAKINDU Requirements

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
YAKINDU Requirements
Durch Standards offen für Erweiterungen
Eclipse Modeling
Framework ist die Brücke
zu anderen Standard...
YAKINDU Requirements

●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
...
Kontakt:
Florian Geyer, florian.geyer@itemis.de
Michael Jendryschik, michael.jendryschik@itemis.de

●
●
●
●
●
●
●
●
●
●
●
...
Nächste SlideShare
Wird geladen in …5
×

Von der Nutzungsanforderung bis zur formalen Softwarespezifikation – Modellieren mit dem Werkzeug YAKINDU Requirements

1.144 Aufrufe

Veröffentlicht am

Die Analyse und Spezifikation von Software-Anforderungen ist eine komplexe Aufgabe, die als Grundlage jedes Softwareentwicklungsprojekts für den späteren Erfolg oder Misserfolg maßgeblich ist. Oft bleiben jedoch Nutzungsanforderungen auf dem Weg zur Implementierung aufgrund einer mangelnden Integration in formale technische Spezifikationen auf der Strecke. Dieser Vortrag stellt einen werkzeugbasierten Ansatz zur Spezifikation komplexer interaktiver Systeme mit Hilfe des Werkzeugs YAKINDU Requirements vor.

Veröffentlicht in: Technologie
0 Kommentare
1 Gefällt mir
Statistik
Notizen
  • Als Erste(r) kommentieren

Keine Downloads
Aufrufe
Aufrufe insgesamt
1.144
Auf SlideShare
0
Aus Einbettungen
0
Anzahl an Einbettungen
9
Aktionen
Geteilt
0
Downloads
10
Kommentare
0
Gefällt mir
1
Einbettungen 0
Keine Einbettungen

Keine Notizen für die Folie

Von der Nutzungsanforderung bis zur formalen Softwarespezifikation – Modellieren mit dem Werkzeug YAKINDU Requirements

  1. 1. ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Von der Nutzungsanforderung zur formalen Softwarespezifikation Florian Geyer und Michael Jendryschik – itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● © itemis AG
  2. 2. itemis Florian Geyer Planung und Durchführung von UsabilityMaßnahmen im Softwareentwicklungsprozess ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Michael Jendryschik Anwender von YAKINDU Requirements, Schnittstelle zwischen Produktentwicklung und Produktmarketing © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 2
  3. 3. Von der Nutzungsanforderung zur formalen Softwarespezifikation Modellierung mit dem Werkzeug YAKINDU Requirements  Bedeutung klarer Anforderungen für den Projekterfolg  Nutzungsanforderungen und Systemanforderungen  Anforderungsspezifikation und -management  YAKINDU Requirements  Ansatz und Methodik  Demonstration am Beispiel Ausblick und Diskussion ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●  © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 3
  4. 4. Bedeutung klarer Anforderungen für den Projekterfolg ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● © itemis AG Quelle: Projektmanagement Studie 2008 (GPM, PA Consulting Group) 4
  5. 5. Bedeutung klarer Anforderungen für den Projekterfolg Benötigte Funktionalität ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Implementierte Funktionalität © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 5
  6. 6. Bedeutung klarer Anforderungen für den Projekterfolg ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Usability-Engineering-Prozess nach DIN EN ISO 9241-210 © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 6
  7. 7. Nutzungsanforderungen und Systemanforderungen Übersicht abstrakt Ziele Geschäftsziele und Marktanforderungen Gesetzliche Anforderungen Organisatorische Anforderungen StakeholderAnforderungen Erfordernisse Nutzungsanforderungen Aufgaben und Bedürfnisse der Nutzer Umstände des Nutzungskontexts Eingabe und Ausgabe am System Systemanforderungen Funktionale Anforderungen Qualitätsanforderungen Randbedingungen Systemspezifikation User Interface, Prototypen Schnittstellen, Architektur Use Cases Pflichtenheft ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● detailliert © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 7
  8. 8. Nutzungsanforderungen und Systemanforderungen Ausgangspunkt – Kontextszenarien Paul (48) ist ein Mitarbeiter der itemis AG. Er möchte sich zwei Wochen Urlaub nehmen und erstellt daher einen Urlaubsantrag. Er sendet ihn an Harald, den Personalverantwortlichen bei itemis. Harald prüft den Antrag auf Konflikte mit vorhandenen Terminen und verfügbaren Urlaubstagen. Dafür muss er noch einmal Rücksprache mit Teamleiter Joachim halten und notiert sich daher den Antrag für später. Joachim sieht keine Konflikte und daher genehmigt Harald den Antrag von Paul schließlich. Harald benachrichtigt Paul über die Genehmigung seines Antrags. Paul bemerkt später, dass er einen Tag zu viel Urlaub genommen hat und möchte den Antrag ändern. Dafür schickt er einen erneuten Antrag an Harald, der die Änderung akzeptiert und Paul benachrichtigt.  Personen (und Systeme): Mitarbeiter, Personalverantwortlicher, Teamleiter  Benutzerziele und Absichten: Urlaub nehmen, Antrag prüfen  Abläufe oder Workflows: 1. erstellen, 2. senden, 3. rücksprechen, 4. genehmigen...  Objekte und Artefakte: Antrag, Urlaubstage, Termine, Genehmigung  Regelsituationen und Ausnahmesituationen: kein Urlaub, Terminkonflikt, etc. ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●  Informationen über den Arbeitskontext: Mitarbeiterrollen, Unterbrechungen © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 8
  9. 9. Nutzungsanforderungen und Systemanforderungen Anforderungen dokumentieren – Erfordernisse Erfordernisse: Notwendige Voraussetzungen zur Erfüllung eines Zwecks ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● »Der Personalverantwortliche muss die verfügbaren Urlaubstage der Mitarbeiter verfügbar haben um die Urlaubsgenehmigung sicherstellen zu können.« © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 9
  10. 10. Nutzungsanforderungen und Systemanforderungen Anforderungen dokumentieren – Nutzungsanforderungen Nutzungsanforderungen: Erforderliche Benutzeraktionen an einem interaktiven System »Der Nutzer muss am System ausstehende Urlaubsanträge erkennen können.« »Der Nutzer muss am System verfügbare Urlaubstage der Mitarbeiter erkennen können.« ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● »Der Nutzer muss am System eine Urlaubsgenehmigung mit Kommentar eingeben können.« © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 10
  11. 11. Nutzungsanforderungen und Systemanforderungen Anforderungen dokumentieren – Systemanforderungen Systemanforderungen: Bedingungen, die ein System oder eine Systemkomponente erfüllen muss »Vor Verwendung des Systems muss das System dem Nutzer die Möglichkeit bieten, eine sichere Anmeldung über LDAP durchzuführen.« »Nach Eingang eines Urlaubsantrags muss das System dem Nutzer die Möglichkeit bieten, das Urlaubsantragsformular zu öffnen.« ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● »Beim Bearbeiten eines Urlaubsantrags soll das System dem Nutzer ein Textfeld anbieten, um einen Kommentar einzugeben.« © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 11
  12. 12. Anforderungsspezifikation und -management Anforderungen dokumentieren – Modelle, Spezifikationen User Interface (Mockup, Prototyp) Use Case Ablaufdiagramm ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Datenmodelle, Entities © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 12
  13. 13. Anforderungsspezifikation und -management Spezifikationsdokumente  Dokumentation der Anforderungen in einem Spezifikationsdokument (z.B. Pflichtenheft)  Einheitliche Struktur (z.B. Volere)   Eindeutige Identifikatoren  Verweise auf Materialien und Modelle  Prioritäten und Konflikte  Quelle und Abnahmekriterien ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●  Status und Versionen © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 13
  14. 14. Anforderungsspezifikation und -management Anforderungen verwalten – Herausforderungen Unterschiedliche Stakeholder (Business, IT, Usability etc.)  Verschiedene Sprachen und Perspektiven  Änderungen und Auswirkungen von Änderungen  Querbezüge und Nachverfolgbarkeit bei großen Projekten  Konsistenz bei dokumentenbasiertem Vorgehen  Interdisziplinäre Zusammenarbeit und Versionierung ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●  © itemis AG Quelle: Fotolia ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 14
  15. 15. ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● YAKINDU Requirements ist eine Software für das Anforderungsmanagement © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 15
  16. 16. YAKINDU Requirements Requirements Navigator Requirements Use Cases Entities Texteditor Lifecycles Spezifikation mittels einer DSL UI Pages Textbausteine UI Flows Templates Referenzierung Textvervollständigung Refactoring Visualisierung Prüfung und Validierung Übersicht Grafische Ansicht Automatisch generierte Diagramme ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Navigation © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 16
  17. 17. YAKINDU Requirements ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Anforderungen spezifizieren © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 17
  18. 18. YAKINDU Requirements ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Use Cases spezifizieren © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 18
  19. 19. YAKINDU Requirements ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Interfaces spezifizieren – Pages © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 19
  20. 20. YAKINDU Requirements ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Interfaces spezifizieren – Interaktionsdesign © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 20
  21. 21. YAKINDU Requirements Dokumente generieren PDF HTML MS Word Requirements Use Cases Entities Lifecycles Actors User Interface ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● User Interface Flow WBS MS Excel © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 21
  22. 22. YAKINDU Requirements ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Live-Demo © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 22
  23. 23. YAKINDU Requirements Durch Standards offen für Erweiterungen Eclipse Modeling Framework ist die Brücke zu anderen Standards  Austausch mit anderen Werkzeugen durch das Requirements Interchange Format.  Flexible, dynamische Definition des Requirements Schemas  Textuelle Modellierung erlaubt einfache Spracherweiterungen ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●  © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 23
  24. 24. YAKINDU Requirements ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Diskussion und Ausblick © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● 24
  25. 25. Kontakt: Florian Geyer, florian.geyer@itemis.de Michael Jendryschik, michael.jendryschik@itemis.de ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● itemis AG | Am Brambusch 15-24 | D-44536 Lünen | www.itemis.de © itemis AG ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●

×