Improve your SOA project planning
English original
content:
Motivation and problem governance model: The correct form of the SOA project will put the governance model to use Tips and Skills Conclusion Reference Information About the author to the evaluation of this article
related information:
Business Process Rengineering and Beyond
Ensure the success of the project with sound governance principles
Level: Intermediate
Yvonne Balzer
(Yvonne.balzer@de.ibm.com) Advanced IT Management Consultant, IBM Global Services ITMC 2004 August
Service-Oriented Architecture, SOA has significantly improved IT efficiency potential. But to implement it in the organization, just understanding that technology is not enough, it must also be sure to manage. In this article, Yvonne Balzer will describe the principles that can help you successfully implement any SOA project.
Today, the business and IT value chains begin to be integrated in the industry. We now call the company architecture and the service-oriented architecture (SOA) are independent of IT implementation. Therefore, we also need to establish horizontal links between business and IT, define and develop architectures such as SOA, and run a client project specifically for enterprises. For these reasons, the role governing in today's IT industry is more important than before. In this article, I will introduce the best practical governance methods for the IBM IT Management Consulting (ITMC) development group, which have been developed and implemented in several client items. We will start the governance model to meet the needs of SOA from the IT governance structure and practice that has been tested. Motivations and problems Due to the problems and challenges in the industry, IT has undergone fundamental changes in the role of modern organizations. Now, IT must react with a very fast response and flexibly enable business. IT must be designed and managed some highly integrated complex enterprise architecture, and the boundaries between business and IT components are getting more blurred. This article will introduce key governance functions that can help you meet these goals and successfully implement the SOA project. Governance provides an arched structure that supports users' business objectives from strategic, functional, and operative hierarchies. It defines rules, processes, metrics, and organizational structures for effective planning, decision making, manipulation, and SOA project control to achieve user business needs and goals. Finally, the governance model defines the following:
What do I have to do. How to do it. Who should be made. How to make metrics. This model also defines rules, processes, metrics, and organizational structures for effective planning, decision making, manipulation, and SOA project control to achieve user business needs and challenge goals. The following is some of the key issues involved in the SOA project to define the appropriate governance structure:
What benefits can clients get from this project? What is the goal and expectation of the client? While IT planning, manipulation, and decision development, what roles, responsibilities, structures, and processes are existing in the client site? How to improve skills and leadership? What principles are needed and guidelines to optimize the relationship between business and IT? In order to interact with companies and IT to sustain consistency and maintain sufficient flexibility to quickly adapt to new changes, what kind of constructors are suitable? What kind of service specifications, service definitions, and description are suitable? How to control and metrically and service providers? Who will monitor, define and authorize the modifications of the existing service? How to determine the original strategy of the service? What problems exist? How does the project support the client to solve these problems? Based on our experience, we believe that the formal governance model is the key to successful business goals. Therefore, we recommend establishing governance functions in the SOA project. The governance model should also handle the basic needs of progressive transformation, that is, the contents of the content you have learned in each step are set to define and execute the next step. Creating a governance program for SOA transformation and implementation is the core needs of the governance model. To complete this work quickly and reliable, we advocate the use of client existing structures and work together to transform the structure and adapt to the SOA project. Governance Model: The correct form of IT governance of the SOA project has some different definitions. IT Governance Institute (see Resources to get related link) gives a better general overview of IT governance: IT governance is the responsibility of the guidance department and the actuator. It is the main component of corporate governance, consisting of leadership and organizational structure, which ensures that organization's IT can maintain and expand the organization of IT strategies and objectives.
The purpose of IT governance is to guide IT to ensure that its performance can meet business destination, so:
* IT and companies' federations make expected interests into reality.
* IT makes the opportunity to develop and maximize the interests of the company.
* IT resources can be reliable.
* IT related risk is reasonably controlled.
The governance model of Figure 1 is a combination of organizational structure, connection procedures, and related links. It is based on the basic principles of the strategic direction and the recognized principles known as governance principles. In a large number of complex projects, this method has been continuously improved through our experience. As a result, we realize that these elements are the foundation of any type of project. Figure 1. Core Governance Elements Strategic Direction and Guiding Principles The definition of client strategic direction is the key to successfully developing suitable SOA and continuous focus on business needs. Universal understanding of business strategies and objectives is the basis of business units and IT. The principles and guidelines for governance are the foundation of any decision. These principles and guidelines will specify the scope of the solution and define the way of collaboration. Therefore, the implementation department should understand very well. One of the main guidelines is the way of governance. The difference between the two main methods is:
Central Governance: This is the best way for companies. The Governance Commission has a representation from each serving domain (more introductions will be more introduced in the future), which can be dialogue with people who implement the key technical components of the solution. The Central Governance Committee will review any addition, deletion, and existing services to the service before the authorization of the implementation of the revision. Distributed Governance: This is the best way for distributed teams. Each business unit can control how to provide services within its own organization. This requires a functional service domain method. The Central Committee can provide guidelines and specifications for different teams. Each principle should be defined in accordance with basic theory, which is used to explain the purpose and meaning of the principles. The guiding principle defines some basic rules for development, maintenance, and use of SOA. Specific principles are used in architectural design or service definitions, that is, these guiding principles focus on specific topics. These principles have the following features, they can provide inherent features for design patterns, and should include the following aspects:
Guiding Principles:
Reuse, granularity, metosability, compositeentization, and standardization, and standardization, Pass, monitor, and track specific architectural principles: Package business logic and basic technology Separation single implementation and component enterprise view (Enterprise-view) opportunities use the effective use of existing asset lifecycle management system resources to maturity and Performance By understanding the principles of the SOA style of architecture and design, as well as these principles, you can determine the applicability of SOA when designing solutions for business and IT. These principles drive service design with clear basic characteristics. You can give each feature to one or more SOA principles that provide to principles and features with integrity. Governance process governance processes are strategic IT planning and manipulation, such as:
Development of Strategy Development IT Planning Traffic Management Resources Innovation Management Architecture Management. In the SOA project, you need to establish an architecture management process (AMP) at the beginning of the project. The main goal of AMP is to ensure the consistency, effectively development and persistence of the defined SOA. Based on our experience in many projects, we have developed a standard amp, you can quickly and easily use it in the client project. This process consists of four sub-flows, as shown in Figure 2, these subflows use IBM LOVEM representation, definition is perfect and available. (LOVEM is Line of Visibility Engineering Methodology, see Resources for more information). Figure 2. The architecture management process is described in more detail in more detail: some elements in the figure:
The review and approval process of the architecture:
Define a well-constructed approach to review and approve the changes in existing SOA, making decisions consistent with SOA routes. The formal assessment of design and service is a key control point. Exceptions of architecture and progressive development processes:
Provide a method of requesting a system structure decision. Allow an exception to the SOA architecture to meet unique business needs. Architecture maintenance process:
When a new service is added to the architecture, make sure the SOA has been maintained and modified has been conveyed to the risk bearer. The variation of the architecture has a document description and is conveyed. Architecture communication process:
Make sure that SOA is available to people who need access to each. Deepen the understanding of the importance of SOA, to provide architectural governance, some structures must be established within the organization, define all the needs of roles and responsibilities, and the organizational structure that defines appropriate development decisions. Experience shows that establishing an architecture office is useful, especially in complex and huge projects. The duties of the architecture are to maintain SOA in strategic, tactical, and operational levels in line with business needs. The office should include an authority of the architecture design, he is the owner of the architecture management process. In addition, each level defines roles and responsibilities. Based on our work in the client, there are two effective ways to build and run such an architecture office:
If the client organization already has a system with a similar system, you should combine this existing organizational structure. It should be ensured that all functions and responsibilities can be clearly used to develop architecture decisions. For SOA projects, these functions and responsibilities should involve SOA decisions and keep contact at any time. If the client site does not have a governance committee, we recommend that you build an architecture office in the context of the SOA project and make critical delivery items through it. The client and project personnel in the SOA project temporarily act as a staff member of the architecture office. These people should be decision makers and should include CIO. At the end of the project, the architecture office can be integrated into the client organization. Figure 3 illustrates the role and responsibilities of the architecture office and each level. There is an architecture department in the strategic layer, which is a decision-making department, responsible for submission of standards and principles and prioritizing the service through business and IT strategies. In the tactical layer, the architecture group operates as an architecture design authority, responsible for defining architectural management processes, as well as decision guidelines for determining, deleting, or adding services and management domains. Develop and implement services at the operating layer, project group. Figure 3. Architecture Office Each project group requires role description to define its tasks and responsibilities and mode of operation. SOA governance introduces the concept of domain ownership, domain management a range of reusable services for sharing common cogeneration services. In many cases, these are the subsets of business services, such as user information, case information, business competition statistics, etc., as well as competition reference, such as commercial risk level, product analysis and planning services. Each domain is responsible for maintaining its own business object, and is also responsible for publishing a service interface for other domain. The domain provides service search service retrieval and maintenance, packaging business logic, positioning, and format associated with objects and services. When a person in a product or product area wants to obtain a service from the domain, they generate a request and two groups identify each other, create a service level agreement. These linkages and agreements are also between domains. Depending on the concept of domain ownership, some new roles and responsibilities should be provided to the development life cycle in the SOA project, as described below 1 below. Table 1. Role and responsibilities in the SOA project Describe the direction of the domain owner management domain, the domain contains a gathering of one or more services, and also includes service contacts to help owners in multiple business units understand business perspective. The owners of the data and processes use business analysts to clarify business objectives and needs. Track the use of ROI calculation services. Object-oriented business analyst developers in the domain use not to assume the service functional case of the user interface. Make sure that the fully extracted specified business services are identified and specified. Strong and flexible service definitions must be adhered to the development of the surveillance cycle. The business representative is domain identifying and analyzing business services. Domain developers and maintenance people are consistent with service-oriented development life cycle. Create and implement services that meet the development rules (for example, service design considerations or web implementation guides), SOA, and reference architecture. Service testers ensure a strict test to get the right business value. Create test cases for functional interfaces and its independent implementation. The person working in a given service domain is responsible for developing business and technology integration to provide business services that can be shared across business lines to benefit members and areas. When they convert the functions developed into the application into the function developed in the service domain, they will change the development of the application in the organization structure (role and responsibilities). The process of putting a governance model using the development governance model is based on a method with three steps. This method is based on time-constrained client projects. The key to success is the establishment of governance functions.
Step 1: Implement
Set the core governance function in the appropriate location and support the client service operation. Side, you can successfully succeed. Experienced professionals act as high-level management roles. Step 2: Specialization
Establish the necessary structure, process, methods and tools. Absorbed the experience in step 1. Use experienced architects and professionals. Step 3: Stability
Teaching and train client staff running. Change the operating mode into a guidance mode. Advisers and experts with guidance experience. Figure 4 is a more detailed description of these steps. Figure 4. Inputing the management mode is prompted and tips below the implementation of some practical experience from the actual project: there is a regular notice to each need to visit (through the project newsletter, Or maybe it is a meeting). SOA created organizational culture and changed technology, which may cause communication barriers, so communication is very important. Each decision, constraint, and envisage into documentation to ensure the persuasion and transparency of decision making. Define critical delivery and required tools and templates. Practice tools for the management and program of the survival cycle. Define decisions and documentation and communicate and communicate these decisions with basic principles. The strong support and decision makers must maintain all risk bearers. Ending the paper illustrates why governance is important and what it needs in the SOA project. And some key elements of our SOA governance model have been summarized. Starting from the principle of SOA, the architecture management process is described as a critical process to ensure compatibility and consistency for the service architecture. It also describes how to establish an organizational structure for suitable decision making and development to provide the role and responsibilities required. Finally, this article also describes how to put the governance model and provide you with tips and techniques we have obtained in this area. Reference
For more information from the article "Service-Oriented Architecture: Implementation Challenge," E. G. Nadhan (MSDN, April 2004), this article discusses two governance methods. Finding methods available for process design, definition, visualization, and documentation - IBM LoveM, or Line of visibility Engineering Methodology. To get more information, please consult the IBM Red Book "Business Process Rengineering and Beyond". Read "Ten Emerging Best Practices for Building Soas," Jason Bloomberg (SearchWebServices, Feb 2003). Learn more about IT Governance Institute.
About the author Yvonne Balzer acquires a Bachelor degree in Computer Sciences of Business Administration in Manheim, Germany. She is an IBM Global Services's advanced IT management consultant, and she provides ideological guidance for the architecture management and the service-oriented IT governance and IT strategy. Yvonne has experienced experience in IT architects several years and provides financial, utilities and automotive references for domestic and international customers. She leads the market planning in Europe, the Middle East and Asia. Yvonne is a member of the IBM Technical Expert Committee and writes IBM Women in Technology. You can contact her with Yvonne.balzer@de.ibm.com.
