Cyber-physical systems in manufacturing combine hardware and software, creating significant complexity that traditional software development models don't always address.
Multiple variation points, such as different hardware suppliers or customer workflows, combine to create an explosion of complexity that can overwhelm a project.
Domain-driven design helps teams focus on the business problem first by creating a domain model, rather than immediately jumping to implementation details and frameworks.
Event storming is a collaborative workshop technique that helps teams map out business processes and identify key events, commands, and aggregates for the domain model.
A real-world domain model for a mask repair machine shows how different bounded contexts like handling and repair use specific language to avoid ambiguity.
Translate the abstract domain model into code using tactical patterns like aggregates, entities, value objects, repositories, and factories to structure the software.
Standard DDD patterns can be extended with concepts specific to a domain, such as actuators, sensors, and state machines for hardware-centric systems.
Placing the domain model at the core of a clean architecture isolates business logic from external dependencies like specific hardware, improving testability and maintainability.
Designing software around a stable domain model, rather than volatile external dependencies, makes the system more resilient to changes in hardware or infrastructure.
43:13Carola Lilienthal
30:29Andreas Kaldun
24:52Hendrik Lösch
42:02Simon Lasselsberger
28:11Simon Lasselsberger
1:51:43Hans-Jürgen Eidler
29:11Eberhard Wolff
1:01:30Henning Schwentner
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
Vesterling Consulting GmbH
Vesterling Consulting GmbH
ZEISS Group
Interroll Holding
Universität Basel