How Architecture Contributes to Quality at Speed

QE Unit
8 min readApr 14, 2022
Photo by Laurent Vénérosy https://unsplash.com/photos/af7UAJzQJgY

Software is a must-have.

The competition pressures the actors to reinvent themselves continuously. It’s not enough to be good at one point in time; successful actors must be able to adapt constantly in an evolving ecosystem with low predictability.

Organizations require both economies of scale and economies of speed to survive in our context. Software has become the only way to iterate and scale fast enough business processes, from customer experience to internal operations.

Such interdependency on software implies that business speed and adaptation capabilities now depend on the level of software mastery of organizations. It is not possible anymore to consider software as a nice-to-have priority.

Quality Engineering constrains the software lifecycle to Quality at Speed with the five domains of MAMOS: Methods, Architecture, Management, Organization, Skills. Find the full content in the ebook On Defining Quality Engineering: Thrive your business with Quality at Speed software.

This article shares how Architecture-including software-contributes to Quality and Speed.

Follow the QE Unit for more exclusive Quality Engineering from the community.

How Architecture contributes to Quality

Digital businesses require translating business ideas into concrete products that can fulfill the evolving needs of its users. One main challenge is to answer the multiple requirements and combine technologies to create valuable software components.

Architecture contributes to Quality by enabling this translation with urbanization, allowing separation of concerns, composition, and interoperability. The proper identification of business modules supports the elasticity afterward.

Separation of concerns

We can be anything, but not everything. Too many things concentrated in a single place lead to too much complexity we cannot handle. The same problem happens with software requiring to separate the concerns of different layers.

The principle of separation of concerns isolates specific complexity in abstraction layers. This division maximizes the fit to…

--

--

QE Unit

The Quality Engineering Unit is a community dedicated to improving our software quality practices through transversality — for more https://qeunit.com/follow