When a business manager invests in new or modified software, he or she expects business results from that investment. Sadly, more often than not, they don't get that. They may get a technically brilliant system, but if that system's architecture isn't based on the architecture of the business, or on business goals and strategy – then it's still a failure. In this mini-course you'll learn how to establish a software architecture that is closely aligned to the business and to business goals. Software that can be adapted to future changes in business strategy, business goals, and business processes. Software that can be deployed on-premises, on Azure, or as a hybrid with parts on-premises and parts in the cloud. Here's a list of a few of the things you'll learn in this course: how to enhance requirements, making them laser sharp and business-drivenhow to use an agile approach for turning requirements into a business-driven, service-oriented architecturehow to isolate service consumers from each other, so that no consumer can be adversely affected by changes made for another consumerhow to use high-level architectural patterns, built on top of an infrastructure of sharable informationhow to use the Microsoft Service Bus to get advantage of the best of two worldshow to choose between REST and RPC, HTTP and SOAP, WCF and Web APIBy the way, this mini-course is developed by Sten and Per Sundblad at Sundblad & Sundblad in Uppsala, Sweden. The views and ideas presented in it are not necessarily the views and ideas of Microsoft. They are the views of the Sundblad & Sundblad Organization. For more information, or to contact Sten or Per, visit http://www.certifiedsoftwarearchitect.com/channel9