Skip to content

Contem­porary software architecture: promoting and managing surprises (part 2)

The first part of our serious looked at practices that can be key to dealing with limited time and budgets in architecture. This part will focus on the second essential element of contem­porary software architecture: surprises. Successful projects count on frequent surprises in the imple­men­tation phase and will repeatedly experience minor failures. Priori­tised architecture requirements, architecture work that is inter­twined with devel­opment and the concept of technical debt are all part of this journey.

by Stefan Toth

Read the article here .

Share this article:

Stay Up-to-Date with the iSAQB® Newsletter!

Scroll To Top