There is a large number of patterns that people apply in agile software development projects. These might deal with the process being applied, with software architecture, modeling, building software, testing it, or even with the basics of all software development projects: how do people communicate and collaborate.
Pattern that help you execute projects better and more efficient.
Analysis patterns and design patterns¶
Our catalog of analysis and design patterns is listed here.
Patterns in the software architecture
The patterns listed below are often used in our software architecture, and found their place in our frameworks (ADF):
Patterns that facilitate framework development.
- Layer supertype. Single type that ancestors similar types, such as
- Descriptor. Inheritable enumeration, as used in
- Bridge. Pattern separating implementation of services from its specification.
- Dependency injection. Pattern separating implementation of services from its specification, by defining its configuration.
- Manager. Pattern facilitating services to other framework and application types, such as
User interface patterns
Patterns that allow for the realization of the user interface.
Process layer patterns
Patterns that support the implementation of a use case (or workflow) driven process layer.
- Task. Pattern to implement smart use cases independent of each other.
Domain driven patterns¶
Patterns that support the implementation of a solid domain layer in a domain centric approach.
- Domain object. Layer supertype for all domain objects, such as
- Domain model. Pattern describing model of all domain objects and their associations.
- Value object. Small and simple object, such as
Email that is meaningful to the customer domain, and is used for validation, often as type of properties of
- Smart reference. Domain object to capture all simple references in an application.
- Repository. Pattern that describes classes responsible for fetching existing instances of domain objects.
A collection of patterns to support implementing a back-end agnostic domain layer, by providing state.
- Wrapping or mapping. A collection of patterns to ensure a domain layer independent of underlying technology.
- Domain mapper. Pattern for mapping one type of elements to another, such as for binding and persisting domain objects and user interface panels.
- Internal state. Pattern implementing domain object internal state independent of the underlying technology, without having to perform additional mapping.
- Data transfer object. Transfer mechanism for fetching domain object internal state from underlying services.
Data and service patterns¶
Patterns to provide the domain layer with state, from several back-ends, including databases, middleware, services and legacy systems.
- Data gateway. Pattern that describes interaction between the domain layer and the underlying databases.
- Service gateway. Pattern describing the interaction between the domain layer and the underlying services, middleware and web services.