Architecting for the Future
Yesterday I stated that good software architecture needs to take into account future changes. This is very difficult to do because it is often impossible to anticipate where strategic changes and organizational shifts will take a product. But when the architecture is sound and flexible it can be done. A very good example is the Web itself: you can still use Lynx to view most web content, and all modern browsers are compatible with the most ancient servers out there. At the same time web technologies, such as AJAX, have progressed sufficiently to enable sites like Google Maps. Another good example is our very own PowerTerm WebConnect, which has grown from a browser based host access product to a total enterprise-wide application access solution supporting over 40 types of target systems, including Windows Terminal Services.