An Architectural Framework for Non Functional Requirements in Enterprise SOA Adoption

Summary form only given. Service oriented architecture (SAO) is latest trend in trying to bridge the gap between business strategists and IT architects. Architecting services from an enterprise perspective does not just involve identifying and fitting pieces together, but managing and addressing cross cutting concerns or non functional requirements (NFRs). With most of the discussion on SOA being around abstracting the business functions as reuse-able services, IT architects have to additionally worry about the existing system qualities. So, a flat view over services has to be complimented with an approach of looking into these additional obligations, which adds a new dimension of complexity during the adoption of SOA. This tutorial is intended to provide our insights into managing this complexity throughout the different phases of SOA adoption, by minimizing the risk through calculated assumptions. We will initially set the context of the different phases of service adoption. We will then present an approach for managing the complexities of NFRs through earlier defined adoption phases. We will conclude with a discussion of the essential artifacts and tools for guiding service design.