comprehensive, condensed, multi-view, and consensual basis for quality-assured
requirements engineering as a basis for all subsequent tasks, from data modeling to
the development of DT-based software functions.
Step 1: Identification of Stakeholders and Use Cases
Based on a general understanding of the use cases, company internal stakeholders
as well as external stakeholders of the ecosystem are identified. They contribute to the methods described in the steps 2–9.
Methods: Virtual or face-2-face interviews, surveys, workshops with design
thinking, and creativity sessions
Results: Stakeholder table and use case characterization (short description)
Step 2: Definition of Strategic Business Impact for Use Cases
The current and future business impact for the identified use cases is analyzed.
Methods: Qualitative description and quantitative evaluation of strategic business
impact is analyzed within interviews and workshops. Hereby standardized
strategic issues (e.g. goals, benefits, and SWOT) and measurable criteria for
strategic ratings are used.
Results: Strategic use case business charter
Step 3: Prioritization and Selection of Focus Use Cases
The use case candidates from step 1 and 2 are prioritized based on the evaluation
results from step 2. Most attractive use cases are selected as focus use cases by
all stakeholders.
Methods: Prioritization and selection methods, e.g. scoring methods, AHP (analytic hierarchy process)
Results: Portfolio matrix and prioritized use cases
Step 4: Definition of Status Quo (As-Is) Use Cases – Static view of IT assets
Definition of a static IT network diagram of As-Is focus use cases showing all
relevant IT components (e.g., hardware, software), roles, actors, and their datainput/output relations.
Methods: Design of a static use case entity-relationship-diagram
Results: Static IT network diagram: As-Is Use Case Representation
Step 5: Definition of Status Quo (As-Is) Use Cases – Dynamic view of IT assets
Development of a workflow diagram of As-Is focus use cases showing logical
sequence of activities of roles or actors, and their data input/output relations
Methods: Design of a use case specific workflow
Results: Dynamic IT workflow diagram: As-Is use case description
Step 6: Definition of Status Quo (As-Is) Use Cases – Data exchange view
Specification of data (e.g., data types, data attributes) exchanged by relevant
actors.
Methods: Interviews and workshops on further data concretization
The Challenge of Implementing Digital Twins in Operating Value Chains
135
requirements engineering as a basis for all subsequent tasks, from data modeling to
the development of DT-based software functions.
Step 1: Identification of Stakeholders and Use Cases
Based on a general understanding of the use cases, company internal stakeholders
as well as external stakeholders of the ecosystem are identified. They contribute to the methods described in the steps 2–9.
Methods: Virtual or face-2-face interviews, surveys, workshops with design
thinking, and creativity sessions
Results: Stakeholder table and use case characterization (short description)
Step 2: Definition of Strategic Business Impact for Use Cases
The current and future business impact for the identified use cases is analyzed.
Methods: Qualitative description and quantitative evaluation of strategic business
impact is analyzed within interviews and workshops. Hereby standardized
strategic issues (e.g. goals, benefits, and SWOT) and measurable criteria for
strategic ratings are used.
Results: Strategic use case business charter
Step 3: Prioritization and Selection of Focus Use Cases
The use case candidates from step 1 and 2 are prioritized based on the evaluation
results from step 2. Most attractive use cases are selected as focus use cases by
all stakeholders.
Methods: Prioritization and selection methods, e.g. scoring methods, AHP (analytic hierarchy process)
Results: Portfolio matrix and prioritized use cases
Step 4: Definition of Status Quo (As-Is) Use Cases – Static view of IT assets
Definition of a static IT network diagram of As-Is focus use cases showing all
relevant IT components (e.g., hardware, software), roles, actors, and their datainput/output relations.
Methods: Design of a static use case entity-relationship-diagram
Results: Static IT network diagram: As-Is Use Case Representation
Step 5: Definition of Status Quo (As-Is) Use Cases – Dynamic view of IT assets
Development of a workflow diagram of As-Is focus use cases showing logical
sequence of activities of roles or actors, and their data input/output relations
Methods: Design of a use case specific workflow
Results: Dynamic IT workflow diagram: As-Is use case description
Step 6: Definition of Status Quo (As-Is) Use Cases – Data exchange view
Specification of data (e.g., data types, data attributes) exchanged by relevant
actors.
Methods: Interviews and workshops on further data concretization
The Challenge of Implementing Digital Twins in Operating Value Chains
135