Glossary · Automation software engineering and architecture
Architecture pattern
Also known as: Architectural pattern, Architectural style
German: Architekturmuster
In software engineering, an architecture pattern is a proven, reusable solution to a recurring problem in the overall structure of a software system, describing its main components, their responsibilities and how they interact. Examples include layered, event-driven, component-based and hexagonal architectures.
- Software engineering
In one sentence
An architecture pattern is a reusable solution for the overall structure of a software system, such as layered or event-driven architecture.
Example
A line controller uses a layered architecture: hardware access at the bottom, equipment modules in the middle and recipe-driven sequences on top.
How it applies
- Engineering: Choosing an architecture pattern early sets the rules for dependencies, communication and deployment. In automation, patterns must also respect real-time behavior, cycle times and the constraints of the controller platform.
- Reviews: Architecture reviews check whether the implementation still follows the chosen pattern. Erosion, such as shortcuts across layers, increases Coupling and makes changes risky.
- Documentation: Name the patterns used in the architecture description and explain why they were chosen. A short rationale helps new developers, auditors and the documentation team understand why the system is structured as it is, and it supports Impact analysis later.
Architecture pattern vs. design pattern
An architecture pattern shapes the whole system or a large subsystem. A Design pattern solves a local problem inside a component, such as creating objects or adapting an interface. A system usually follows one or two architecture patterns and uses many design patterns within them.