Home
News
Services
Training
Products
Partners
Contact Us
myAPG
Public training calendar


Partner and ISV
Partner
Partner
Influencing Member
Architecture Forum Member

|
|
Model Driven Service-Oriented Architecture
|
Objectives |
|
Discuss SOA background / benefits |
|
Discuss SOA development method integrated with Unified Process |
|
UML 2.0 modeling |
|
Apply Model Driven Architecture® (MDA®) |
|
Review UML-based business modeling
|
|
Discuss service identification activities from existing assets and business models |
|
Discuss business goals and associated services |
|
Understand how to model services in UML |
|
Identify service partitions and gateways |
|
Model service specifications, service contracts, security patterns with UML |
|
Discuss message design considerations |
|
Discuss service orchestration and choreography |
|
Introduce SOA-related standards |
|
Description |
|
Model Driven Service-Oriented Architecture teaches the experienced software
architect how to represent the architecture and design of a software application
that uses web services. Beginning with a discussion of the business benefits
and technical background of service-oriented architecture (SOA), the course
continues with a review of typical business modeling activities. Then the course
describes several techniques for identifying candidate services including domain
decomposition, business model analysis, goal-service modeling, and asset
analysis. Once a candidate portfolio of services is identified, the course
discusses how to partition services, capture non-functional requirements and
service polices, and service repositories. Topics of message design and
security policies and requirements are discussed. The course finishes with
describing how to design services, specify their internal components, and
service orchestration and choreography. Students use the UML Profile for
Software Services to describe SOA using composite structures, collaborations,
components, and interfaces.
|
|
Audience |
|
Enterprise architect |
|
Business architect |
|
Software architect |
|
Software designer |
|
Senior developer |
|
System engineer |
|
|
|
Classroom requirements |
|
No computers required |
|
|
|
|
|