Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Key concepts and themes
- What is SOA?
- Choosing the appropriate architectural style
- The "pipe and filter" style
- Data type constraints
- The development lifecycle
- Achieving the right level of abstraction
- Core themes in RUP for SOA
Service identification and specification
- Constructing a service model
- WSDL-defined services
- Developing service specifications
- Defining service providers
- Determining service granularity
- Behavioral specification
- Policy specification
- Identifying candidate services
- Refactoring services
Managing a service portfolio
- Applications as dynamic entities
- Portfolio of available capabilities
- Process time-binding
- Run-time binding
- WSDL, XSD, and WS-Policy
- The service portfolio management process
- Configuring an SLA for a web service
Partitioning service-oriented solutions
- Managing models
- Categorizing elements
- Model review by different stakeholders
- Using packages
- Representing views of the model
- Composite structure from UML 2.0
- Utilizing "parts" and "connectors"
- Partitioning managed services
New and updated guidelines
- Managing message attachments
- Designing messages
- Ensuring consistency of message schema
- Service data encapsulation
- Relationship data schema and service boundaries
- Service mediation
- State management
- Evaluating the merits of stateful and stateless services
- Managing resource state
- Transitioning from services to service components
- The traditional design/implementation model
Message-centric design
- Focus on the service domain
- Domain engineering
- Applying object-oriented analysis and design
- Producing highly reusable models
- The traditional business-to-business arena
- EDI standardization
- Hybrid message and service-centric approach
- Use case analysis
- Documenting requirements
- Utilizing business process models
- Non-functional requirements
- The requirements database
Service-centric design
- Exposing expected business functions
- Exposing service provider operations
- Creating intuitive service interfaces
- Service-centric modeling
- Use-case driven approach
- Understanding actor needs
- Project goals from a business perspective
- Involvement of the software architect
- Policy information required by service consumers
- The role of the business executive
- Interaction with back-end systems
- Connecting services to the implementation model
- Refining the service model
- Addressing performance concerns
Collaboration-centric design
- Collaborating services
- Process view of services
- Traditional business modeling
- Fulfilling roles in collaboration
- Partner Interchange processes (PIPs)
- OAGIS standards
- Process-centric mindset
- The "business vs. IT gap"
- "Black box" activities
- Defining key performance indicators (KPIs)
- Versioning and publishing a model
- Producing metrics for monitoring
- Choreography language
- Business process execution language (BPEL)
- Monitoring services
What is SOA Governance?
- Compliance with standards or laws
- Change management
- Ensuring service quality
- Managing the service portfolio
- Managing the service lifecycle
- Using policies to restrict behavior
- Monitoring service performance
The SOA Governance issue
- Governance appearing as SOA initiatives
- A dynamic environment for service interaction
- Encouraging service reuse
- Controlling service interactions
SOA Governance Stages
- First: Recognizing the need for governance
- Second: Governance improving business execution
- Third: Combining technology and behavioral changes
- Fourth: Technology selection and implementation
Service Management
- Design-time perspective
- Run-time perspective
- Repository of services for reuse
- Services on heterogeneous platforms
- Service virtualization for run-time management
Critical governance components
- Service registry and asset repository
- Creating a "SOA Centre of Excellence"
- Establishing SOA organizational guidelines
- Organizational maturity
- Agreed governance policies
SOA Governance tools
- Real-time event monitoring
- Failures in a BSM framework
- Service-level instrumentation
- Integration with operational management systems
- Virtualization as an enabler for separating governance/service logic
- Operational staff managing service virtualization
Developing core SOA governance
- Reasons for the growing complexity of the SOA technology stack
- Mixing COTS and in-house solutions
- Justifying the use of external consultants
- Identifying the core business
Roles and responsibilities involved in SOA Governance
- Establishing a SOA Centre of Excellence
- Enterprise-wide planning and execution support
- Roles of the SOA/governance architect
- Resolving conflicting interests
- Ensuring adherence to governance guidelines
Barriers to SOA governance
- Failing to realize the need for governance
- Lack of governance technologies
- Lack of service virtualization
State of good governance
- Interaction with external parties
- Managing business rules and BRE management
- Regulations for effective governance
- The agreements repository
- Proactively embedding governance in business processes
- Governance through action rather than statement
- SLA monitoring for premium pricing
Critical success factors
- Start thinking about governance early
- View governance as a moving target
- Manage policies as entities with their own lifecycles
- Choose a technology platform
- The platform should address immediate governance needs
- Ensure future support as SOA infrastructure scales
- Enforce service level agreements
Requirements
Experience in software design
21 Hours
Testimonials (2)
The exercise and the trainer is very helpful in the coding.
Paul Andrew - IT
Course - REST API - a pattern of exchange of information between sites
Drawing on a whiteboard in real time as he explained, top experience. He knew to explain every topic.
