Software Architect

Understand the impact of change

Book: 97 Things Every Software Architect Should Know
Publisher: O’Reilly Media
Author: Richard Monson-Haefel
97 Things Every Software Architect Should Know – 67/97

'Coz sharing is caring

A good architect reduces complexity to a minimum and can design a solution whose abstractions provide solid foundations to build upon, but are pragmatic enough to weather change.

The great architect understands the impact of change – not just in isolated software modules, but also between people and between systems.

Change can manifest in a variety of forms:

  • Functional requirements change
  • Scalability needs evolve
  • System interfaces are modified
  • People in the team come and go
  • and the list goes on…

The breadth and complexity of change in a software project is impossible to fathom up-front, and it’s a fruitless task trying to accommodate every potential bump before it happens. But the architect can play a crucial role in determining whether the bumps in the road make or break a project.

The architect’s role is not necessarily to manage change, but rather to ensure change is manageable.

Take, for example, a highly distributed solution that spans many applications and relies on a variety of middleware to glue the pieces together. A change in a business process can cause havoc if the set of dependencies are not correctly tracked or accurately represented in some visual model. The impact downstream is particularly significant if the change affects the data model, breaks existing interfaces, and the existing long-running, stateful transactions must successfully complete under the old version of the process.

This example may appear extreme, but highly integrated solutions are now mainstream. This is evident in the choice of integration standards, frameworks and patterns available. Understanding the implications of change in these outlying systems is critical in ensuring a sustainable level of support to your customers.

Fortunately, there are many tools and techniques to mitigate the impact of change:

  • Make small, incremental changes
  • Build repeatable test cases – run them often
  • Make building test cases easier
  • Track dependencies
  • Act and react systematically
  • Automate repetitive tasks

The architect must estimate the risk of change on various aspects of the project’s scope, time and budget, and be prepared to spend more time on those areas whose impact would be the greatest as the result of “a bump in the road”. Measuring risk is a useful tool for knowing where your valuable time should be spent.

Reducing complexity is important, but reduced complexity it does not equate to simplicity. The pay-off for understanding the type and impact of change on your solutions is immeasurable in the medium- to long-term.

'Coz sharing is caring

By Swatantra Kumar

Swatantra is an engineering leader with a successful record in building, nurturing, managing, and leading a multi-disciplinary, diverse, and distributed team of engineers and managers developing and delivering solutions. Professionally, he oversees solution design-development-delivery, cloud transition, IT strategies, technical and organizational leadership, TOM, IT governance, digital transformation, Innovation, stakeholder management, management consulting, and technology vision & strategy. When he's not working, he enjoys reading about and working with new technologies, and trying to get his friends to make the move to new web trends. He has written, co-written, and published many articles in international journals, on various domains/topics including Open Source, Networks, Low-Code, Mobile Technologies, and Business Intelligence. He made a proposal for an information management system at the University level during his graduation days.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.