这个广告的场景是两个女同学在草地上坐着看书，一个手里拿着康师傅铁观音茶，另一个拿着“OSCILLATIONS IN NONLINEAR SYSTEMS”（非线性系统中振荡）。 当时看到这本《OSCILLATIONS IN NONLINEAR SYSTEMS》时，当时就震惊了。这姑娘是学数学还是学物理的，这也不像理科女啊！
The governance team needs to analyze all processes affected by SOA
Identify the decision points, then associate decision points with rights, policies for making the decisions, and supporting measures
Discover decision points, where controls are needed, around:
Artifacts: SOA related specifications, release orders, change requests, and so on.
Events: Project milestones, iteration completions, and phase transitions
Create process control mechanisms that are either:
Prescriptive (规定的): For highly routine activities, provides a specific step-by-step process – for highly routine activities
Adaptive (自适应的): For creative tasks, such as software development, assign resources and set activities dynamically at defined events, in a goal-driven manner. – for creative activities.
Develop process measures to:
Determine if the process is meeting business needs
Provide feedback for evolving the process
Drive the desired behavior in the organization
*The Rational Unified Process for SOA Governance
The Rational Unified Process has the SOA Governance plug-in that describes:
Roles
Tasks (grouped by governance lifecycle phase)
Work products (grouped by domain)
Guidance
Concepts
Guidelines
Templates and examples
It helps identify appropriate best practices, merged with your existing IT processes, to provide proper governance of the capabilities introduced with SOA
A service registry securely registers services and relevant information.
A service registry enables SOA lifecycle management and SOA governance by:
Publishing service endpoint capabilities
Managing service metadata
Finding and subscribing to the services
Enforcing Service Level Agreements and policies
Registries allow a company to effectively manage the metadata of its services to ensure that service consumers and providers have a common understanding of the service. The governance issues addressed by the service registry include how:
Service-related information is stored, managed, maintained, and accessed
Service Requesters determine which Services to use
Service Requesters locate Service endpoints
Requesters are notified of changes
The governance responsibilities of the service registry include:
Manage service-related information (interface, service location, additional information such as specification, and so on) in a centralized manner
Provide categorization and versioning capabilities to leverage service-related information
Provide service requesters with extensive discovery and notification capabilities
Securely register business services for finding, publishing and notifying changes to SOA infrastructure components. House the metadata about business services in managing the lifecycle of a service in SOA.
Part of any governance solution is meeting the organization’s compliance requirements. Compliance is documenting and proving that governance is in place and is being executed: the decisions are documented and the decision policies are followed. The compliance specifics depends on clients’ needs. In the US, they are likely to include Sarbanes-Oxley （萨班斯·奥克斯利法案）, but may also include domain-specific standards such as CFR-11 for the pharmaceutical industry, or Basel II for banking. The compliance requirements should be determined in the plan phase, and addressed throughout the lifecycle.
Governance is the foundation for all phases within the IBM SOA Lifecycle (as the graph above)
SOA governance assigns formal decision rights, policies, and measures to address such concerns as:
Service registration
Service versioning
Service ownership
Service discovery and access
Deployment of services and composite applications
Security for services
Benefits of SOA Governance
Realize the business benefits of SOA
Business process flexibility and improved time to market
Mitigate business risk and regain control
Quality of service, consistency of service
Improve team effectiveness
The right things measured
Clear communication between business and IT
There are three main points to the Governance model:
Financial transparency covers issues around funding:
Business and IT alignment deals more with service identification and service portfolio management.
Process control is what many companies immediately focus on.
财务透明 + 业务和IT的一致 + 流程控制
SOA Governance Lifecycle
计划 + 定义 + 使能 + 测量
插播：计划 + 组织 + 领导 + 控制 （管理过程）
Plan phase: The organization assesses what the immediate goals are for the SOA initiative, the goals for governance, organizational cultural factors, existing organizational and governance models, and company priorities in the short and long terms. (Model)
Define phase: The organization defines the integration standards, creates or modifies the organizational structure, plans for change management, creates policies for funding and service identification, and decides how important metrics will be monitored so the model can be improved. (Assemble)
Enable phase: The organization puts the governance model into practice. (Deploy)
Measure phase: As in the Manage phase in the SOA lifecycle, the organization prepares for the next iteration and a new Plan stage, using the monitoring inputs from the measure stage as the basis for the next iteration of the governance plan. (Manage)
14 Critical Processes
Service Planning: involves decomposing business processes and identifying service interfaces.
Service Ownership and Funding: Establishing funding, project plans and resources.
Service Modeling: Focuses on processes for creating and enforcing enterprise service standards.
Service Implementation: requires that processes support the development and testing of services.
Service Management: requires that the governance process provide support to monitor composite application performance. This allows for the proper tuning and debugging of composite applications.
An abstract view of SOA depicts it as a partially layered architecture of composite services that align with business processes.
Business process flows can be supported by a choreography of these exposed services into composite applications. An integration architecture supports the routing, mediation, and translation of these services, components, and flows using an Enterprise Service Bus (ESB). The deployed services must be monitored and managed for quality of service and adherence to non-functional requirements.
SOI integrates applications using service interactions that support interoperability, flexibility, and reuse.
Three Integration approaches:
P2P (brittle): Custom Point-to-Point Integration is expensive to maintain and very costly to adapt to new business requirements. Any change to either endpoint or to the internal components (OS, IP address, hostname) will break it.
EAI (less brittle): (Enterprise Application Intergration) Changes to endpoints may require some adjustments, but these changes do not ripple through the entire infrastructure like P2P. Changes to internal components may force changes to other components, since internal broker components are typically tightly coupled. Initial costs are higher than P2P, but maintenance is much lower.
SOI (the least brittle): SOI, if implemented using Web services, has standard interfaces and is less expensive for new business requirements. As long as the exposed interface (WSDL/SOAP) does not change, the endpoint can be completely swapped with no integration impact. Changes to internal components should not impact any other part of the ESB since even the internal components are loosely coupled.
Service Oriented Architecture (SOA) SOA is an architectural style and a design principle for application development and integration. Shifts focus to the assembly of applications from services, and away from implementation details.
最近评论