Warum wir Software bauen

Das junge und sich sehr schnell entwickelnde Handwerk der Software Entwicklung ist unsere Leidenschaft. Immer die beste Lösung durch Innovation ist Ihr Mehrwert.

Die Prinzipien der Modularität und das Domain-Driven Design (DDD) bilden die Grundlage unserer erfolgreichen Software Entwicklung.

Das Domänen Model erlaubt uns das zu bauende System genau zu verstehen. Mithilfe der Konzepte und Patterns des DDD entsteht daraus eine modulare Software, die alle Qualitätsansprüchen übertrifft.

Wer hat es erfunden?

Viele erfahrene Software Entwickler nutzen Modularität und Konzepte des DDD intuitiv, jedoch ohne sie so zu benennen. Hier einige Zitate von mehr oder weniger bekannten Verfechter dieser Prinzipien.

«The key to controlling complexity is a good domain model, a model that goes beyond a surface vision of a domain by introducing an underlying structure, which gives the software developers the leverage they need. A good domain model can be incredibly valuable, but it’s not something that’s easy to make.»

Martin Fowler

«To communicate effectively, the code must be based on the same language used to write the requirements — the same language that the developers speak with each other and with domain experts.»

Eric Evans Domain-Driven Design: Tackling Complexity in the Heart of Software

«Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.»

Grady Booch Object-Oriented Analysis and Design with Applications

«Clean code is focused. Each function, each class, each module exposes a single-minded attitude that remains entirely undistracted, and unpolluted, by the surrounding details.»

Robert C. Martin Clean Code: A Handbook of Agile Software Craftsmanship

«We need to focus on modularity to ensure a consistent architecture story is told. It is the glue that binds. It’s the piece that helps bridge low-level class design with higher-level service design.»

Kirk Knoernschild Java Application Architecture: Modularity Patterns with Examples Using OSGi

«When you write a software module, you want to make sure that when changes are requested, those changes can only originate from a single person, or rather, a single tightly coupled group of people representing a single narrowly defined business function.»

Robert C. Martin
An den Anfang scrollen