Add a comment


Re: Agility and the essence of software architecture

Nice talk about pragmatic software architecture in general.

What I was missing, though, was a thourough "manifestation" of Agility in the architecture.

Developers experience Aglility as a different process, I´d say. The process focuses on small increments manufactured in short iterations.

Software architecture in this context then should exhibit two properties:
a. make adhering to the process easy
b. mirror the focus of the approach

To me a. means, software structures need to be malleable, fluid, soft, the opposite of monolithic. Because otherwise the frequent "unforseen", "unplanned" changes cannot be accustomed. Microservice and "component thinking" sure help in this regard. But I don´t believe that´s enough.

That´s why I find b. so important. To me it means, increments should be structural elements of software. Increments should be part of the thinking process of the software architect. They should be tangible for the user/customer as well as for the developers.

If increments get dissolved into a mesh of classes/libraries/components/services then the resulting architecture will be hard to understand. Increments should be first class structural elements of software.

This aspect of Agile Architecture I was missing from your presentation.

Re: Agility and the essence of software architecture

HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
E-mail address
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).