Suitable software architecture for high quality

An architecture only helps if it is also known to the developers. This is why the architecture needs to be documented appropriately. In the simplest case, documentation in smaller agile projects can be done on a whiteboard. For larger and more complex systems, we also have extensions for modeling tools that are matched precisely to our method and which provide appropriate modeling support.

With a suitable architecture, unnecessary and expensive wrong developments can be avoided. To prevent these in the first place, we at Fraunhofer IESE always define the central drivers of an architecture first. These may include quality requirements such as the wish to be able to derive different products from one central architecture. In addition, we offer support through documentation guidelines and templates. In this context, architecture decisions and their systematic elaboration and documentation play a role, as do suitable architecture views that summarize, package, and present information for certain stakeholder roles. For embedded systems, views that comply with the SPES-XT meta-model are also used, whereas the views of ACES-ADF are used for information systems. Nevertheless, architecture definition and documentation must never become an end in itself. They must serve to facilitate further development, be intertwined with such development, and ultimately also be reflected directly in the source code.

What We Offer:


  • Fraunhofer ACES offers a method for the definition and documentation of architecture.
  • With the help of scalable models, even large and complex systems can be mastered.
  • In order to validate the design early on, we integrate simulations and/or rely on prototypes to test concepts, if necessary.

Customer Statement


“The collaboration with Fraunhofer IESE turned out to be a very good decision at all times. The analysis of our current system, the development of a future-oriented software architecture, the making of sustainable design decisions, the execution of prototypes, and the introduction of a modern holistic development methodology were always accompanied by a large degree of professional competence, flexibility, and extraordinary commitment. We are grateful for the open, pleasant, and very trustful collaboration and want to continue it jointly and successfully.”

Holger Eser, KSB Aktiengesellschaft

Software Architecture in practice


Continuing Education

Software Architecture Seminar

You want to use the appropriate software architecture in your daily work? We train you in the typical activities of an architect.

In addition to the acquisition of methodological knowledge, the emphasis is on the practical application of what you have learned. Many exercises and exchanges with experts consolidate the acquired knowledge. Benefit from our expertise!


Success Story

Caruso: A Digital Ecosystem

Caruso GmbH has developed its open and neutral data and service marketplace for the Automotive Aftermarket with the support of Fraunhofer IESE.

As a neutral and strategic technology partner, we were instrumental in helping build up the ecosystem by assisting with the systematic structuring and step-by-step development of the platform as the core of digital ecosystems.


Fraunhofer IESE-Blog

Blockchain: Yes or No?

Many companies are currently wondering whether it might be reasonable and promising for them to develop applications based on Blockchain technology, or to at least experiment with that. But how to get started?

We at Fraunhofer IESE offer methodological support for approaching this topic in a structured manner.