Lessons Learned Adapting an Existing Architecture in a Changing Business Landscape

This report briefly describes the order management and routing system of a major Swiss bank, broaches some of the architectural changes that we made, and discusses the valuable lessons we learned as we faced up to a variety of people and technical challenges. Intended to replace an end of life, mainframe-based solution, the system had already been three years in the making when the assigned architect decided to move on, along with the entire user interface team. As a result, the majority of the team was fairly new (including its architect), and team collaboration was a crucial ingredient for a successful endeavor. We had to change the architecture to correct missed or partially implemented quality attribute requirements (e.g., throughput, service times, and availability). At the same time we had to satisfy pressing business demand for new features, which also brought architectural changes in the form of new interfaces.

Lessons Learned Adapting an Existing Architecture in a Changing Business Landscape

PDF [644 KB]

PRESENTATION

Author

Arthur Wright

This presentation is related to the following area(s) of work:

SATURN

Published: June 2010


SEI Blog

Find Us Here

Share This Page

Share on Facebook  Send to your Twitter page  Save to del.ico.us  Save to LinkedIn  Digg this  Stumble this page.  Add to Technorati favorites  Save this page on your Google Home Page 

For more information

Contact Us

info@sei.cmu.edu

412-268-5800