Governing and Managing Shared Services Across the SOA Lifecycle: SOA Taxonomies Framework for a Business Services Portfolio
Original Publication Date: 2009-Mar-10
Included in the Prior Art Database: 2009-Mar-10
The taxonomy model addresses service classification. Service classification is necessary in order to enable analysis of portfolios without having to review WSDL or any other information that may be available. Service classification metadata labels need to contain several attributes that completely define the service. Such metadata label attributes may be inclusive of ownership, Business Unit (BU) stakeholders, version level, service type, function, access rights, and other attributes. These attributes may be selected via drop-down menus when performing service classification.
Governing and Managing Shared Services Across the SOA Lifecycle : SOA Taxonomies Framework for a Business Services Portfolio
One key aspect of managing and governing shared services in an SOA is to classify and categorize services within the services portfolio in an intuitive fashion so that they can be easily discovered across the enterprise. At the same time, the classification has to be organized in a way that it lends itself to controls and mechanisms for effective governance and management of the services. Some governance aspects may relate to control of consistency and integrity of services, and can be accomplished by organizing services in the appropriate classifications and categorization.
Currently, classification systems for services focus on functional aspects of the service. This is insufficient for properly classifying and managing services. Functional aspects alone does not provide enough information about a service related to governance, ownership, business rules, and other attributes related to the service. These advanced aspects of classification and categorization of services can be accomplished only with the definition and implementation of a robust taxonomy for services, and aligning the organization of the enterprise services portfolio along these lines.
As discussed above, there is a need for a robust and effective method for classifying, categorizing, and managing services across BUs, LOBs and the enterprise. This can be accomplished by a well defined framework, implementation model, and a broadly applicable method to implement taxonomies for a services portfolio.
In essence, a service taxonomy models needs to be based not just on organizational structure silos or functional capabilities, but also on cross-business aspects that span beyond a single business unit or domain. The other key aspects of a services taxonomy model should address classification based on corporate principles, information and business process classification constructs, and service delivery-based classifications.
Current approaches and models to define services taxonomies focus on generic methods for classifying business services domains and do not address the cross-business aspects that SOA services are about. Other taxonomies found in industry models are not customizable with respect to aligning the pre-defined classifications to corporate principles, information classifications and realization classification aspects of SOA services. At best these models categorize services and their parent domains under one or more of the following categories: functional, technology and applications. These models also fail to align the enterprise SOA portfolios around the core aspects of business processes and information which is the key to drive service-orientation.
The taxonomy model addresses service classification. Service cla...