ZapThink

5 IT-Supertrends bis 2020

Jason Bloomberg — Thu, 02 Sep 2010 12:33:55 +0000

Für ZapThink, Marktforscher im Bereich Enterprise Architecture, bietet der Stand(ard) der Dinge nun Anlass, sich verstärkt mit der Zukunft der IT zu beschäftigen. “ZapThink 2020″ ist der Titel eines umfangreichen Frameworks, das die Analysten von ZapThink in den kommenden Monaten auf den Markt bringen werden. Es enthält eine detaillierte Übersicht über die Themen, die IT-Verantwortliche in den kommenden zehn Jahren beschäftigen werden.

Read the entire article at: http://www.cio.de/karriere/2243418/index.html

ZapThink 2020’s Crisis Point: “Collapse of enterprise IT.” Is this our future?

Jason Bloomberg — Mon, 30 Aug 2010 11:34:58 +0000

Comparing IT with office furniture is awful and adequately to only those who sit on their heads. This is why I have doubts in the serious tone of ZapThink.

Read the entire post at:
http://www.ebizq.net/blogs/service_oriented/2010/08/zapthink_2020s_crisis_point_collapse_of_enterprise_it_is_this_our_future.php.

The Impact of a Googless JavaOne

Jason Bloomberg — Mon, 30 Aug 2010 11:18:49 +0000

For example, IBM reduced its level of participation in JavaOne 2003 significantly from previous years. In fact, the referenced article’s Jason Bloomberg quote on IBM’s relationship to Sun and Java could almost be applied to what many of us hope happens today with Oracle, Google, and Java: “I wouldn’t say that by any means they’re [IBM] distancing themselves from Java, but I would say they’re distancing themselves from Sun. . . . ”

Read the entire article at http://www.javaworld.com/community/?q=node/4999

The Crisis Points of the ZapThink 2020 Vision

Jason Bloomberg — Tue, 24 Aug 2010 19:21:26 +0000

ZapThink is announcing a new poster opportunity! ZapThink 2020: The Vision of the Future of Enterprise IT will be one of our biggest poster distributions, sure to be a hit on cubicle walls and desks of the most important IT movers-and-shakers.

Click here for more info on poster sponsorship and gaining access to tens of thousands of high-quality leads!

In our last ZapFlash, The Five Supertrends of Enterprise IT, ZapThink announced our new ZapThink 2020 conceptual framework that helps organizations understand the complex interrelationships among the various forces of change impacting IT shops over the next ten years, and how to leverage those forces of change to achieve the broader goals of the organization. In many ways, however, ZapThink 2020 is as much about risk mitigation as it is about strategic benefit. Every element of ZapThink 2020 is a problem as well as an opportunity. Nowhere is this focus on risk mitigation greater than with ZapThink 2020’s six Crisis Points.

Defining a Crisis Point

Of course, life in general as well as business in particular are both filled with risks, and a large part of any executive’s job description is dealing with everyday crises. A Crisis Point, however, goes beyond everyday, garden variety fire fighting. To be a Crisis Point, the underlying issue must both be potentially game-changing as well as largely unexpected. The element of surprise is what makes each Crisis Point especially dangerous – not that the crisis itself is necessarily a surprise, but rather, just how transformative the event promises to be.

Here then are ZapThink 2020’s seven Crisis Points, why they’re surprising, and why they’re game-changing. Over the next several months we’ll dive deeper into each one, but for now, here’s a high-level overview.

Collapse of enterprise IT – Enterprises who aren’t in the IT business stop doing their own IT, and furthermore, move their outsourced IT off-premise. Why is it that so many enterprises today handle their own IT, and in particular, write their own software? They use office furniture, but nobody would think of manufacturing their own, except of course if you’re in the office furniture manufacturing business. The game-changing nature of this Crisis Point is obvious, but what’s surprising will be just how fast enterprises rush to offload their entire IT organizations, once it becomes clear that the first to do so have achieved substantial benefits from this move.

IPv4 exhaustion – Every techie knows that we’re running out of IP addresses, because the IPv4 address space only provides for about 4.3 billion IP addresses, and they’ve almost all been assigned. IPv6 is around the corner, but very little of our Internet infrastructure supports IPv6 at this time. The surprise here is what will happen when we run out of addresses: the secondary market for IP addresses will explode. As it turns out, a long time ago IANA assigned most IP addresses to a select group of Class A holders, who each got a block of about 16.8 million addresses. Companies like Ford, Eli Lilly, and Halliburton all ended up with one of these blocks. How much money do you think they can make selling them once the unassigned ones are all gone?

Fall of frameworks – Is your chief Enterprise Architect your CEO’s most trusted, important advisor? No? Well, why not? After all, EA is all about organizing the business to achieve its strategic goals in the best way we know how, and the EA is supposed to know how. The problem is, most EAs are bogged down in the details, spending time with various frameworks and other artifacts, to the point where the value they provide to their organizations is unclear. In large part the frameworks are to blame – Zachman Framework, TOGAF, DoDAF, to name a few. For many organizations, these frameworks are little more than pointless exercises in organizing terminology that leads to checklist architectures. At this Crisis Point executives get fed up, scrap their current EA efforts, and bring in an entirely new way of thinking about Enterprise Architecture. Does ZapThink have ideas about this new approach EA? You bet we do. Stay tuned – or better yet, sign up for our newly revised Licensed ZapThink Architect SOA & Cloud Architecture Boot Camp.

Cyberwar – Yes, most risks facing IT shops today are security related. Not a day goes by without another virus or Windows vulnerability coming to light. But what happens when there is a concerted, professional, widespread, expert attack on some key part of our global IT infrastructure? It’s not a matter of if, it’s a matter of when. The surprise here will be just how effective such an attack can be, and perhaps how poor the response is, depending on who the target is. Will terrorists take down the Internet? Maybe just the DNS infrastructure? Or will this battle be between corporations? Regardless, the world post-Cyberwar will never be the same.

Arrival of Generation Y – These are the kids who are currently in college, more or less. Not only is this generation the “post-email” generation, they have grown up with social media. When they hit the workforce they will hardly tolerate the archaic approach to IT we have today. Sure, some will change to fit the current system, but enterprises who capitalize on this generation’s new perspective on IT will obtain a strategic advantage. We saw this generational effect when Generation X hit the workforce around the turn of the century – a cadre of young adults who weren’t familiar with a world without the Web. That generation was instrumental in shifting the Web from a fad into an integral part of how we do business today. Expect the same from Generation Y and social media.

Data explosion – As the quantity and complexity of available information exceeds our ability to deal with such information, we’ll need to take a new approach to governance. ZapThink discussed this Crisis Point in our ZapFlash The Christmas Day Bomber, Moore’s Law, and Enterprise IT. But while an essential part of dealing with the Data Explosion crisis point is a move to governance-driven Complex Systems, we place this Crisis Point in the Democratization of Technology Supertrend. The shift in thinking will be away from the more-is-better, store-and-analyze school of data management to a much greater focus on filtering and curating information. We’ll place increasingly greater emphasis on small quantities of information, by ensuring that information is optimally valuable.

Enterprise application crash – The days of “Big ERP” are numbered – as well as those of “Big CRM” and “Big SCM” and…well, all the big enterprise apps. These lumbering monstrosities are cumbersome, expensive, inflexible, and filled at their core with ancient spaghetti code. There’s got to be a better way to run an enterprise. Fortunately, there is. And once enterprises figure this out, one or more of the big enterprise app vendors will be caught by surprise and go out of business. Will it be your vendor?

The ZapThink Take

We can’t tell you specifically when each of these Crisis Points will come to pass, or precisely how they will manifest. What we can say with a good amount of certainty, however, is that you should be prepared for them. If one or another proves to be less problematic or urgent than feared, then we can all breathe a sigh of relief. But should one come to pass as feared, then the organizations who have suitably prepared for it will not only be able to survive, but will be able to take advantage of the fact that their competition was not so well equipped.

The real challenge with preparing for such Crisis Points is in understanding their context. None of them happens in isolation; rather, they are all interrelated with other issues and the broader Supertrends that they are a part of. That’s where ZapThink comes in. We are currently putting together a poster that will help people at a variety of organizations understand the context for change in their IT shops over the next ten years, and how they will impact business. We’re currently looking for sponsors. Drop us a line if you’d like more information.

Identifying SOA’s ROI Still a Challenge

Jason Bloomberg — Thu, 12 Aug 2010 11:36:50 +0000

It’s 2010; SOA seems to be fairly well established, so much so that the SOA consultant firm ZapThink says it needs to expand its mission. And yet a third of companies still can’t figure out how to show an ROI for SOA.

Read the entire article at http://www.itbusinessedge.com/cm/blogs/lawson/identifying-soas-roi-still-a-challenge/?cs=42729.

The Five Supertrends of Enterprise IT

Jason Bloomberg — Mon, 09 Aug 2010 11:42:44 +0000

Now that SOA has become an established architectural style in enterprises around the globe, it’s time for ZapThink to expand our horizons to the broader set of challenges facing enterprise IT. Fortunately, there’s plenty of work for us to do, as we are entering a dramatic period of change that promises turmoil for the remainder of this decade. Getting our arms around such turmoil, however, is a daunting task, because there are so many threads to the story: Cloud Computing, mobile technologies, advancements in Enterprise Architecture, even the exhaustion of IPv4 as available IP addresses run out in the next year or two. ZapThink is working to help executives, architects, and everyone who counts on IT for a paycheck to navigate these turbulent waters over the next decade.

Announcing ZapThink 2020

Over the next few months, ZapThink will be rolling out a conceptual framework we call ZapThink 2020, which organizes the important trends that are facing enterprise IT today and over the next several years. The point to this exercise is to work through the interrelationships among the various threads, so that no one concept receives more than its fair share of attention. For example, the buzzword du jour is Cloud, but Cloud is a mix of different capabilities that are mostly old wine in new bottles. How will these different capabilities interrelate with everything else going on in the enterprise IT shop, as all the other stories play out and Cloud loses its luster?

In order to organize all the various stories, capabilities, and trends that play a part in the ZapThink 2020 vision, we’ll begin with five broad organizing principles we’d like to call Supertrends. Over time, we’ll fill in much of the missing detail in these Supertrends, but for now, we have a wide brush to paint the big picture. Here then are the five Supertrends of the ZapThink 2020 vision for Enterprise IT:

Location Independence

Narrowly speaking, location independence is a SOA principle, where the underlying physical implementation of a Service is abstracted from the Service itself. This abstraction is also fundamental to the virtualization inherent in Clouds, whether they be public, private, or hybrid. But there’s more to this story than virtualization; mobile presence is also a critical aspect of location independence. Think global buddy list, tied together with your mobile device, your instant messaging, and other indicators of your personal availability. If you can tell people you’re available no matter where you are, that’s part of the location independence Supertrend as well.

Global Cubicle

The Internet gave us the Global Village. Take that idea to its logical extreme and you have the Global Cubicle. Any two people anywhere in the world can work together, communicate, and socialize as though they were in the same room, or even the same cubicle. This Supertrend is over one hundred years old, as the telephone itself gave us our first glimpse of this capability. But now add the location independence from the previous Supertrend, along with ubiquitous computing (where every device is on the Internet, wired or not), combined with the power of social media to bring people together in new ways. Outsourcing and its natural successor, insourcing, become “any-sourcing” as organizations can now find expertise anywhere. And remember, as Generation Y (today’s college kids, more or less) hits the workforce, they will expect and demand a work environment aligned with the Global Cubicle.

Democratization of Technology

How do you buy IT in your organization today? Big vendors, big RFPs, big purchases, high-risk deployments, right? Well, look closer. Is anybody in your organization buying IT via a mobile app store? Or how about provisioning an ad hoc Cloud instance using a personal credit card? Or maybe downloading a free piece of software? This bottom-up acquisition of IT is fast becoming the norm as the subscription-based pricing of SaaS meets open source meets the app store model. Who’ll be left out in the cold? The traditional enterprise app vendors.

Deep Interoperability

Yes, this should work with that. That’s why we have open standards, after all. If everybody supports Web Services or REST or what have you, then we should have product-to-product interoperability. Unfortunately, today’s reality falls far short of the promise of open standards.

But even so, we want more, much more. Remember how modems used to negotiate back in the day? One modem would call another and tell it how fast it could go. The receiving modem would respond with the fastest it could communicate. The two modems would negotiate, gradually proposing slower speeds until they could establish a solid connection.

Take the one-dimensional idea from the modem world of the 1980s and apply it to the multidimensional world of enterprise IT, where any two pieces of software automatically negotiate with each other to establish seamless interoperability. We have the technology now to achieve this goal, but the only way vendors will put in the effort to make deep interoperability a reality is if we stop buying software that doesn’t offer this capability.

Complex Systems Engineering

ZapThink has covered the importance of complex systems theory in the context of SOA in many ZapFlashes, but the story goes well beyond SOA. To achieve true agility, organizations must rethink integration entirely. Governance now becomes the new mantra instead of integration. Chief Information Officers become Chief Governance Officers. Static Enterprise Architecture frameworks give way to continuous business transformation best practices. Business Process Management finally leaves the realm of the integration vendors (who never got it right anyway), as organizations begin truly managing their business processes in order to achieve their goals in the context of an ever-changing business environment.

The ZapThink Take

ZapThink 2020 is a multidimensional vision for change, and the five Supertrends are but one dimension. We’ll also be discussing crisis points that promise sudden, transformative change. Also note that SOA and Cloud are not Supertrends in and of themselves, but they weave their way across the five we’re discussing here. And perhaps most importantly, the business of IT is a critical part of the ZapThink 2020 story, as how organizations spend money on IT will continue to undergo radical change over the next ten years.

ZapThink 2020 also heralds an important transition for ZapThink, as we move to our fourth focus area over the history of our company. We’re still the SOA guys, not to worry, and our LZA SOA course will continue as long as there’s a demand for it. But just as we moved from XML to Web Services to SOA, we’re now moving to the broad-based, continuous business transformation that enterprise IT must enable over the next ten years. Stay tuned, it’s going to be a bumpy ride, but ZapThink will continue to help you navigate the rapids.

LZA SOA Training & Certification: DC – Oct. 5-8, 2010

admin — Sat, 07 Aug 2010 18:45:00 +0000

LZA SOA Training & Certification: DC – Oct. 5-8, 2010
Tuesday October 5, 2010 – Friday October 8, 2010
University of Virginia, Northern Virginia Center
7054 Haycock Road
Falls Church, VA 22043
USA
Price:

Price: $1,995.00 (including $500 early discount) [converted to 1995.00 USD]

Early registration expires: Sep 05, 2010

Map and Directions

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

ZapThink’s Licensed ZapThink Architect (LZA) SOA Training & Certification Boot Camp is recognized around the world as the best single Service-Oriented Architecture training course available anywhere.

The LZA SOA Boot Camp is an intensive, four day “fire hose” of information that prepares you to succeed with your SOA efforts, whether you’re just beginning them or are well down the road with SOA. ZapThink’s LZA SOA Training is the only public course that ZapThink offers, reflecting the best thinking and research that ZapThink produces.

ZapThink’s LZA SOA training & certification has no prerequisites, and is designed for architects, but appropriate for people with different roles and levels of expertise. This course is valuable for anyone who wants in-depth knowledge about how to succeed with SOA.

What makes the LZA SOA Boot Camp so special?

Vendor independent – We discuss vendors in context, both good and bad. You get a balanced perspective on each vendor we discuss.
Architect focused – The course concentrates on what architects have to do to be successful with SOA in their own organizations. We balance technology details with organizational approaches. If you’re not an architect you’ll learn how to think like one in this class!
Practical – we connect theory to practice with what really works in organizations like yours.
Current – we refresh the course on a regular basis to reflect the latest SOA best practices, as well as how SOA relates to other architectural challenges in the enterprise.
Enterprise context – SOA is an approach to organizing enterprise IT resources to meet changing business needs. We place SOA into the context of large organizations, with complex, heterogeneous IT environments and all the politics and bureaucracy that every large organization faces.
Globally recognized certification – Everybody who completes the LZA SOA Boot Camp obtains a certificate representing their LZA credential, giving you the right to call yourself a Licensed ZapThink Architect with all the privileges that come along with this exclusive credential.
Led by globally recognized SOA thought leader – All ZapThink’s courses are developed and led by Jason Bloomberg, ZapThink Managing Partner. Jason has been an analyst with ZapThink since 2001 and is the co-author of Service Orient or Be Doomed!
Not too technical, not too high-level – Unlike courses offered by SOASchool, CBDI, Web Age, SOA Institute, SOA Certified Professional (SOACP), Architecting the Enterprise (AtE), IBM, Oracle, Software AG, and others, we cover the technology without getting lost in the details. We discuss the big picture but connect it to the day-to-day reality of the IT shop.
Available around the world – See the event schedule on this page for all the locations we’re offering the LZA SOA Boot Camp!

Event Agenda

LZA SOA Boot Camp Version 8.0
Day 1
Registration: 8:00 to 8:30 AM
LZA Introduction
Module 1: The Enterprise Context for SOA
Business Constant: Change The Voice of Doom? Business Agility Defining SOA Why SOA? Business Drivers for SOA When Not to Apply SOA The Distributed Computing Pendulum SOA: Paradigm Shift? So, How to Implement SOA? Is SOA New? One Difference is Web Services Confusing SOA & Web Services How to Get a SOA If not Web Services, Then What? What is Architecture?		Architecting SOA: Beyond Use Cases SOA Implementation as Complex System Examples of Complex Systems The Focus of CSE CSE: Overall Coherence SOA as Enterprise Architecture The Zachman Framework Pros & Cons of Zachman Services Thinking Why is SOA Difficult? Case Studies: Mini-Studies on SOA Use Shared Services: US PTO Reducing Integration Costs: Aeroplan Compliance & Volume: .Wells Fargo Bank Meeting Client Needs: MITRE
Module 2: SOA Design Principles
Design Principle #1: Abstraction What’s a Service? Levels of Service Abstraction Service as Interface & Implementation Interoperability vs. Portability Service Interfaces Aren’t Good Enough! Abstractions: Simple on the Outside Abstraction = Working Illusion Building a Working Illusion The Fundamental Technical Challenge of SOA Multiple Interfaces per Implementation Multiple Implementations per Interface Multiple Interfaces per Business Service Actualizing the Business Service Abstraction SOA Design Principle #2: Standardized Service Contract What’s a Service Contract? Consumers & Providers WSDL: Service Contract Starting Point WSDL Basics Contract Metadata Beyond WSDL What’s Missing from WSDL? Sample Service Contract Template Design Principle #3: Encapsulation What’s NOT in the Contract Physical Service Architecture Design Principle #4: Discoverability What are Metadata? Metadata for SOA SOA Registry as Discovery Agency Location Independence Design Principle #5: Reusability Reusability vs. Usability Achieving Reusability: Service Agnosticism		Designing for Reuse:Agnostic Context Reuse over Time Design Principle #6: Granularity Key Service Abstraction Enabler: Proper Granularity Granularity Example Achieving Proper Granularity Example: Too Fine Grained vs.Too Coarse Grained Service Refactoring Refactoring Scenario After Refactoring Design Principle #7: Autonomy Autonomy Issue: Overlapping Functional Control Autonomy Issue: Concurrency Autonomy Issue: Scalability Autonomy Issue: Dependency Composition Autonomy: Problem Composition Autonomy: Solution Design Principle #8: Loose Coupling What about Coupling? Full Decoupling? Loose Coupling: Separation of Concerns Levels of Coupling RPC vs. Document Style Loose Coupling and Context Design Principle #9: Statelessness Maintaining Process Instance State Three Approaches to State Stateful Services Design Principle #10: Composability Metadata-Driven Applications Programmatic vs. Declarative Challenges with Declarative Approach Introducing “SOBA”
Exercise: Service Contract
Module 3: The SOA Reference Architecture
What is a Reference Architecture? Recommended SOA Reference Architecture Structure What’s Different about a SOA Reference Architecture? End-to-End Architecture: The SOA Metamodel SOA Foundation: Model-Driven Architecture SOA Foundation: The 4+1 View Model The 4+1 View Model & .The SOA Metamodel The Agility Model Service Architecture Building the Service Model Introducing “ZapElectric”		ZapElectric Service Model Entity Services Task Services Utility (IS) Services Service Relationships Example Process Isomorphism Service Layers ZapElectric Service Layer Model Component & Implementation Models ZapElectric Logical Architecture Model
Homework: Service Model
Class Ends at 5:00 PM
Day Two
Class Begins at 8:30 AM
Module 4: Intermediaries & Integration
SOA Infrastructure Starting Point: The Intermediary Some Intermediary Roles Intermediaries and Service Facades Intermediaries & Messaging Buying an Intermediary? Don’t we just mean an Enterprise Service Bus? The Great ESB/SOA Middleware Boondoggle Buy More Middleware for SOA? ESB Federation? Compounding the Problem: No Clear ESB Definition The ESB Pattern Do You need an ESB for Service Mediation? Intermediary-Based Service Abstraction Building Intermediary-Based SOA Infrastructure SOA Message Exchange Patterns SOA Tenet: Asynchrony Messages vs. Events Business Driver: Visibility Visibility & Heterogeneity SOA, Integration & Legacy Exposing Existing Capabilities The Continued Value of Legacy Legacy Migration Legacy Enablement		Legacy Rejuvenation Migration vs. Rejuvenation Business Driver: Cost Savings Reducing Integration Cost SOA & Data Data: Foundation for SOA The Data Services Layer Application Services vs. .Data Services Application Services abstract application APIs Application-centric .transactionality Data Services abstract data queries Designing Data Services Performance vs. Flexibility Supporting Data Services with Data Integration Leveraging Data Services Layer Semantic Level Understanding Role of Application Semantics Sample Semantic Model Semantics: The Greatest Integration Challenge of SOA Still a Manual Process Resolving Semantic Issues Industry-Specific Semantic Standards Case Study: SOA at The Hartford
Module 5: Service Composition, Business Process, & SOBAs
What is a Business Process? The Automation Paradox Problems with Traditional BPM Tooling Business Process the Enterprise Application Way Business Process the Service-Oriented Way Service-Oriented Process Process Definitions Example: Orchestration vs. Choreography Web Services Orchestration Standard BPEL Example Limitations of BPEL BPMN to the Rescue? BPMN Example Limitations of BPMN How SOA Fills the Gap What is the Sweet Spot for SOBAs? SOBA Example		Enterprise Applications and Process Example: SAP NetWeaver Transactions and SOA Transactions the .Loosely-Coupled Way Compensating Transactions What about Workflow? Workflow & SOA Ad Hoc Processes Mashups: Situational Apps for SOA Data Mashup Example Process Mashup in Action Process vs. Data? The Long Tail: Applications The Enterprise 2.0 Long Tail Without Governance, Mashups are Dangerous Without SOA, .Mashups are Toys Case Study: SOA Journey at BP
Exercise: Service-Oriented Business Processes
Module 6: XML Infrastructure & Security
Challenges at the Content Level Is XML Required for SOA? What about REST? XML: Foundation for Web Services The XML Processing Problem The XML Performance Crisis Solution: XML Appliances XML Firewall Intermediary Processing Challenges Performance analysis: where is the bottleneck? Critical XML Processing Challenge: Security The Context of IT Security The Open Systems Security Challenge XML Threat Prevention Mitigating XML Threats WSDL protection		XML Firewalls XML Encryption Encryption provides confidentiality XML Digital Signature Message-Level Security: Is SSL Sufficient? Core Requirements for Securing Services Web Services Security WS-Security Tokens Security Assertion Markup Language (SAML) SAML Assertions Federated Security Federated Security Illustration The Security Context Challenge Solving the Security Context Challenge: Single Sign-On The Role of Entitlement Management Case Study: SOA Security in the Real World — BP
Module 7: SOA Governance, Quality & Management (Part 1)
The GQM Loop Corporate Governance Governance & Regulatory Compliance The Business Motivation for Governance How to Tackle Governance? Governance Relationships The Cornerstone of IT Governance is Architecture Elements of IT Governance Strategy What is SOA Governance?		SOA Governance “in the Narrow” SOA Governance Activities Tiers of SOA Governance Enterprise/Strategic IT Governance SOA Operating Model .Governance Enterprise/Strategic IT Governance SOA Operating Model Governance Services Governance
Homework: Business Case
Class Ends at 5:00 PM
Day Three
Class Begins at 8:30 AM
Module 7: SOA Governance, Quality & Management (Part 2)
What is a Policy? Policy “Math” Computing Effective Policy WS-Policy Example S-PolicyAttachment Policy Attachment to WSDL 1.1 Policy: Business vs. .Technical Examples Design Time Policy Examples Run Time Policy Examples Change Time Policy Examples The Challenge of Policy Automation Steps for Automating Policies Some Policy Standards WS-SecurityPolicy Example Supporting Policy Changes The Policy Lifecycle Policy Lifecycle: Architect Policy Lifecycle: Administrator Policy Lifecycle: PEP Policy Lifecycle: Operations Policy Management & Enforcement Creating the Governance Framework SOA Asset Management Consumer Management Design Time Governance Publishing & Discovery Governance Sample Publishing/Discovery Governance Processes Governance Challenge: Reuse = Sharing Is Reuse a Real SOA Benefit? Run Time Governance SOA Monitoring & Management Checkpoints Analysis Checkpoint Design Checkpoint Implementation Checkpoint Operational Readiness Checkpoint		Governance Pitfall: Versioning Handling Service Versioning Versioning Concepts Versioning Strategies Strict Versioning Flexible Versioning Loose Versioning Versioning Policy Issues Governance Pitfall: Interoperability Web Services Interoperability Organization (WS-I) Tool Interoperability: Governance Interoperability Framework (GIF) GIF Capabilities Tool Interoperability: CentraSite Community CentraSite Community Members (Partial list) SOA Quality Quality & Complex Systems Policy Enforcement: Quality Continuous Quality Activities SOA Quality Organization Example The Long-Term Challenge of SOA Testing Testing in Production? The SOA Quality Star Best Effort SOA SOA Governance Infrastructure Complexities of SOA Governance Marketplace What is a Registry? What’s the Deal with UDDI? What is a Repository? The Registry/Repository Management & Loose Coupling SOA Management: .Many Facets The Problem with SOA Management The SOA Management Conundrum The First Rule of SOA Management ZapElectric Physical Architecture Model Case Study: SOA Project Management & Governance – T-Mobile
Exercise: Governance Framework
Module 8: Planning & Running the SOA Initiative
How Do You Eat an Elephant? Iterative: More than Step-by-Step Iterate your Architecture? Project Management for a SOA Project Defining SOA Roadmap Initial Assessments Building Support for SOA Building the SOA Business Case Milestone / KPI Plan The SOA Roadmap The ZapThink SOA Roadmap ZapElectric SOA Roadmap SOA Maturity Models Analogous to CMMI SOA Maturity Model Pointers Using a SOA Maturity Model SOA Maturity Model: HP SOA Maturity Model: Wipro Open Group Service Integration Maturity Model (OSIMM), .from IBM “SOA” Maturity Model – Sonic/Systinet SOA Maturity Model: Oracle SOA Maturity Model: Software AG Define Initial Iteration		SOA Pilots Implementation Planning Bottom Up/Top Down Service Identification: Top Down vs. Bottom Up Defining Services Approach Implementing Services: Methodologies for change The Dual Lifecycle The Service Lifecycle Advanced Vision for Application Assembly Where’s the code? The Agile SOA Lifecycle Top-Down: Analyze Processes Process Analysis Process Optimization Discovering Existing Processes Service Identification: Process Decomposition Implementing Services Defining New SOBAs Technology Selection ZapElectric Component Model Purchasing SOA Technology Technology Selection: Choices
Exercise: SOA Roadmap
Homework: SOA Component Model
Class Ends at 5:00 PM
Day Four
Class Begins at 8:30 AM
Module 9: Addressing SOA Organizational Challenges
Organizational Issues Common SOA Pitfalls SOA Growing Pains The Wrong Question! Challenges in Calculating ROI Achieving Business Agility The Problems with “VDA” Challenge: The Right Amount of Governance Avoid Policy Bloat SOA by Any Name SOA = Best Practices Thinking Outside the SOA Box Dealing with SOA Hype and Anti-Hype Is there an Architect in the House? Hiring Architects EA Challenges: The Role of the EA Enterprise Architecture Challenges Questions to Ask Your EA Good Money after Bad The SOA Consultant Conundrum The SOA School Bus Are “SOA” Consultants Qualified? IT Governance Feedback Loop Interaction Challenges The Ivory Tower Problem The Power of the SOA Center of Excellence Convincing Technical Specialists Working with IT Middle Management Enabling Service Domains		Service Domain Roles SOA Funding Models Traditional IT Funding: Project Based Initial SOA Funding Funding Cross-Departmental SOA Initiatives CapEx vs. OpEx Budget Workarounds Case Study: ABN Amro Staffing Building the right SOA team Core SOA Governance Team Architecture Board SOA Steering Committee SOA Architecture Team Business Process Team Infrastructure/Operations Team Data Services Team SOA Project Staffing Project Leader Data Specialists Security Specialists Legacy Systems Specialists Service Development Specialists BPM/Composition Specialists Governance Tooling Specialists Testing & Deployment Specialists Project Archivists/Cybrarians External Services Specialists Case Study: SOA Organizational Change & Funding @ Novartis
Exercise: ROI of SOA
Module 10: Architecting with the Cloud
Cloud Computing: Old Wine in New Bottles Formal Definition of Cloud Computing Essential Cloud Characteristics Cloud Service Models Cloud Deployment Models Vendor Spin Oracle’s Shopping List IBM’s Shopping List Cutting Through the Hype Cloud Computing Roadmap EA Cloud Strategy Cloud Service Lifecycle Capabilities Design Pattern Relationship between Cloud & SOA Cloud Deployment Choices Services as a Service		Managed Hosting vs. Cloud Computing Some Cloud Realities Cloud Governance SOA Governance & Cloud Synergies Cloud: Raising the Governance Bar Governance-Related Cloud Issues Cloud Governance Challenges Extending SOA Governance to the Cloud Cloud Governance Pitfalls Dealing with Cloud Reliability Example: Amazon EC2 Cloud Governance as VM Governance Rogue Clouds Cloud Governance: Run Time Considerations Cloud Availability & Failover Cloud Governance Technology Cloud Governance Checklist
Final Exam: SOA Jeopardy!
Class Ends at 3:00 PM

Venue:

University of Virginia, Northern Virginia Center
7054 Haycock Road
Falls Church, VA 22043
USA Washington, DC Map and Directions

Nearby Hotels:

Click here for nearby hotels

LZA SOA Training & Certification: Chicago – Nov. 15-18, 2010

admin — Sat, 07 Aug 2010 18:44:27 +0000

LZA SOA Training & Certification: Chicago – Nov. 15-18, 2010
Monday November 15, 2010 – Thursday November 18, 2010
DePaul University, O’Hare Campus
8770 W. Bryn Mawr
Chicago, IL 60631
Price:

Price: $1,995.00 (including $500 early discount) [converted to 1995.00 USD]

Early registration expires: Oct 15, 2010

Map and Directions

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Vendor independent – We discuss vendors in context, both good and bad. You get a balanced perspective on each vendor we discuss.
Architect focused – The course concentrates on what architects have to do to be successful with SOA in their own organizations. We balance technology details with organizational approaches. If you’re not an architect you’ll learn how to think like one in this class!
Practical – we connect theory to practice with what really works in organizations like yours.
Current – we refresh the course on a regular basis to reflect the latest SOA best practices, as well as how SOA relates to other architectural challenges in the enterprise.
Enterprise context – SOA is an approach to organizing enterprise IT resources to meet changing business needs. We place SOA into the context of large organizations, with complex, heterogeneous IT environments and all the politics and bureaucracy that every large organization faces.
Globally recognized certification – Everybody who completes the LZA SOA Boot Camp obtains a certificate representing their LZA credential, giving you the right to call yourself a Licensed ZapThink Architect with all the privileges that come along with this exclusive credential.
Led by globally recognized SOA thought leader – All ZapThink’s courses are developed and led by Jason Bloomberg, ZapThink Managing Partner. Jason has been an analyst with ZapThink since 2001 and is the co-author of Service Orient or Be Doomed!
Not too technical, not too high-level – Unlike courses offered by SOASchool, CBDI, Web Age, SOA Institute, SOA Certified Professional (SOACP), Architecting the Enterprise (AtE), IBM, Oracle, Software AG, and others, we cover the technology without getting lost in the details. We discuss the big picture but connect it to the day-to-day reality of the IT shop.
Available around the world – See the event schedule on this page for all the locations we’re offering the LZA SOA Boot Camp!

Event Agenda

LZA SOA Boot Camp Version 8.0
Day 1
Registration: 8:00 to 8:30 AM
LZA Introduction
Module 1: The Enterprise Context for SOA
Business Constant: Change The Voice of Doom? Business Agility Defining SOA Why SOA? Business Drivers for SOA When Not to Apply SOA The Distributed Computing Pendulum SOA: Paradigm Shift? So, How to Implement SOA? Is SOA New? One Difference is Web Services Confusing SOA & Web Services How to Get a SOA If not Web Services, Then What? What is Architecture?		Architecting SOA: Beyond Use Cases SOA Implementation as Complex System Examples of Complex Systems The Focus of CSE CSE: Overall Coherence SOA as Enterprise Architecture The Zachman Framework Pros & Cons of Zachman Services Thinking Why is SOA Difficult? Case Studies: Mini-Studies on SOA Use Shared Services: US PTO Reducing Integration Costs: Aeroplan Compliance & Volume: .Wells Fargo Bank Meeting Client Needs: MITRE
Module 2: SOA Design Principles
Design Principle #1: Abstraction What’s a Service? Levels of Service Abstraction Service as Interface & Implementation Interoperability vs. Portability Service Interfaces Aren’t Good Enough! Abstractions: Simple on the Outside Abstraction = Working Illusion Building a Working Illusion The Fundamental Technical Challenge of SOA Multiple Interfaces per Implementation Multiple Implementations per Interface Multiple Interfaces per Business Service Actualizing the Business Service Abstraction SOA Design Principle #2: Standardized Service Contract What’s a Service Contract? Consumers & Providers WSDL: Service Contract Starting Point WSDL Basics Contract Metadata Beyond WSDL What’s Missing from WSDL? Sample Service Contract Template Design Principle #3: Encapsulation What’s NOT in the Contract Physical Service Architecture Design Principle #4: Discoverability What are Metadata? Metadata for SOA SOA Registry as Discovery Agency Location Independence Design Principle #5: Reusability Reusability vs. Usability Achieving Reusability: Service Agnosticism		Designing for Reuse:Agnostic Context Reuse over Time Design Principle #6: Granularity Key Service Abstraction Enabler: Proper Granularity Granularity Example Achieving Proper Granularity Example: Too Fine Grained vs.Too Coarse Grained Service Refactoring Refactoring Scenario After Refactoring Design Principle #7: Autonomy Autonomy Issue: Overlapping Functional Control Autonomy Issue: Concurrency Autonomy Issue: Scalability Autonomy Issue: Dependency Composition Autonomy: Problem Composition Autonomy: Solution Design Principle #8: Loose Coupling What about Coupling? Full Decoupling? Loose Coupling: Separation of Concerns Levels of Coupling RPC vs. Document Style Loose Coupling and Context Design Principle #9: Statelessness Maintaining Process Instance State Three Approaches to State Stateful Services Design Principle #10: Composability Metadata-Driven Applications Programmatic vs. Declarative Challenges with Declarative Approach Introducing “SOBA”
Exercise: Service Contract
Module 3: The SOA Reference Architecture
What is a Reference Architecture? Recommended SOA Reference Architecture Structure What’s Different about a SOA Reference Architecture? End-to-End Architecture: The SOA Metamodel SOA Foundation: Model-Driven Architecture SOA Foundation: The 4+1 View Model The 4+1 View Model & .The SOA Metamodel The Agility Model Service Architecture Building the Service Model Introducing “ZapElectric”		ZapElectric Service Model Entity Services Task Services Utility (IS) Services Service Relationships Example Process Isomorphism Service Layers ZapElectric Service Layer Model Component & Implementation Models ZapElectric Logical Architecture Model
Homework: Service Model
Class Ends at 5:00 PM
Day Two
Class Begins at 8:30 AM
Module 4: Intermediaries & Integration
SOA Infrastructure Starting Point: The Intermediary Some Intermediary Roles Intermediaries and Service Facades Intermediaries & Messaging Buying an Intermediary? Don’t we just mean an Enterprise Service Bus? The Great ESB/SOA Middleware Boondoggle Buy More Middleware for SOA? ESB Federation? Compounding the Problem: No Clear ESB Definition The ESB Pattern Do You need an ESB for Service Mediation? Intermediary-Based Service Abstraction Building Intermediary-Based SOA Infrastructure SOA Message Exchange Patterns SOA Tenet: Asynchrony Messages vs. Events Business Driver: Visibility Visibility & Heterogeneity SOA, Integration & Legacy Exposing Existing Capabilities The Continued Value of Legacy Legacy Migration Legacy Enablement		Legacy Rejuvenation Migration vs. Rejuvenation Business Driver: Cost Savings Reducing Integration Cost SOA & Data Data: Foundation for SOA The Data Services Layer Application Services vs. .Data Services Application Services abstract application APIs Application-centric .transactionality Data Services abstract data queries Designing Data Services Performance vs. Flexibility Supporting Data Services with Data Integration Leveraging Data Services Layer Semantic Level Understanding Role of Application Semantics Sample Semantic Model Semantics: The Greatest Integration Challenge of SOA Still a Manual Process Resolving Semantic Issues Industry-Specific Semantic Standards Case Study: SOA at The Hartford
Module 5: Service Composition, Business Process, & SOBAs
What is a Business Process? The Automation Paradox Problems with Traditional BPM Tooling Business Process the Enterprise Application Way Business Process the Service-Oriented Way Service-Oriented Process Process Definitions Example: Orchestration vs. Choreography Web Services Orchestration Standard BPEL Example Limitations of BPEL BPMN to the Rescue? BPMN Example Limitations of BPMN How SOA Fills the Gap What is the Sweet Spot for SOBAs? SOBA Example		Enterprise Applications and Process Example: SAP NetWeaver Transactions and SOA Transactions the .Loosely-Coupled Way Compensating Transactions What about Workflow? Workflow & SOA Ad Hoc Processes Mashups: Situational Apps for SOA Data Mashup Example Process Mashup in Action Process vs. Data? The Long Tail: Applications The Enterprise 2.0 Long Tail Without Governance, Mashups are Dangerous Without SOA, .Mashups are Toys Case Study: SOA Journey at BP
Exercise: Service-Oriented Business Processes
Module 6: XML Infrastructure & Security
Challenges at the Content Level Is XML Required for SOA? What about REST? XML: Foundation for Web Services The XML Processing Problem The XML Performance Crisis Solution: XML Appliances XML Firewall Intermediary Processing Challenges Performance analysis: where is the bottleneck? Critical XML Processing Challenge: Security The Context of IT Security The Open Systems Security Challenge XML Threat Prevention Mitigating XML Threats WSDL protection		XML Firewalls XML Encryption Encryption provides confidentiality XML Digital Signature Message-Level Security: Is SSL Sufficient? Core Requirements for Securing Services Web Services Security WS-Security Tokens Security Assertion Markup Language (SAML) SAML Assertions Federated Security Federated Security Illustration The Security Context Challenge Solving the Security Context Challenge: Single Sign-On The Role of Entitlement Management Case Study: SOA Security in the Real World — BP
Module 7: SOA Governance, Quality & Management (Part 1)
The GQM Loop Corporate Governance Governance & Regulatory Compliance The Business Motivation for Governance How to Tackle Governance? Governance Relationships The Cornerstone of IT Governance is Architecture Elements of IT Governance Strategy What is SOA Governance?		SOA Governance “in the Narrow” SOA Governance Activities Tiers of SOA Governance Enterprise/Strategic IT Governance SOA Operating Model .Governance Enterprise/Strategic IT Governance SOA Operating Model Governance Services Governance
Homework: Business Case
Class Ends at 5:00 PM
Day Three
Class Begins at 8:30 AM
Module 7: SOA Governance, Quality & Management (Part 2)
What is a Policy? Policy “Math” Computing Effective Policy WS-Policy Example S-PolicyAttachment Policy Attachment to WSDL 1.1 Policy: Business vs. .Technical Examples Design Time Policy Examples Run Time Policy Examples Change Time Policy Examples The Challenge of Policy Automation Steps for Automating Policies Some Policy Standards WS-SecurityPolicy Example Supporting Policy Changes The Policy Lifecycle Policy Lifecycle: Architect Policy Lifecycle: Administrator Policy Lifecycle: PEP Policy Lifecycle: Operations Policy Management & Enforcement Creating the Governance Framework SOA Asset Management Consumer Management Design Time Governance Publishing & Discovery Governance Sample Publishing/Discovery Governance Processes Governance Challenge: Reuse = Sharing Is Reuse a Real SOA Benefit? Run Time Governance SOA Monitoring & Management Checkpoints Analysis Checkpoint Design Checkpoint Implementation Checkpoint Operational Readiness Checkpoint		Governance Pitfall: Versioning Handling Service Versioning Versioning Concepts Versioning Strategies Strict Versioning Flexible Versioning Loose Versioning Versioning Policy Issues Governance Pitfall: Interoperability Web Services Interoperability Organization (WS-I) Tool Interoperability: Governance Interoperability Framework (GIF) GIF Capabilities Tool Interoperability: CentraSite Community CentraSite Community Members (Partial list) SOA Quality Quality & Complex Systems Policy Enforcement: Quality Continuous Quality Activities SOA Quality Organization Example The Long-Term Challenge of SOA Testing Testing in Production? The SOA Quality Star Best Effort SOA SOA Governance Infrastructure Complexities of SOA Governance Marketplace What is a Registry? What’s the Deal with UDDI? What is a Repository? The Registry/Repository Management & Loose Coupling SOA Management: .Many Facets The Problem with SOA Management The SOA Management Conundrum The First Rule of SOA Management ZapElectric Physical Architecture Model Case Study: SOA Project Management & Governance – T-Mobile
Exercise: Governance Framework
Module 8: Planning & Running the SOA Initiative
How Do You Eat an Elephant? Iterative: More than Step-by-Step Iterate your Architecture? Project Management for a SOA Project Defining SOA Roadmap Initial Assessments Building Support for SOA Building the SOA Business Case Milestone / KPI Plan The SOA Roadmap The ZapThink SOA Roadmap ZapElectric SOA Roadmap SOA Maturity Models Analogous to CMMI SOA Maturity Model Pointers Using a SOA Maturity Model SOA Maturity Model: HP SOA Maturity Model: Wipro Open Group Service Integration Maturity Model (OSIMM), .from IBM “SOA” Maturity Model – Sonic/Systinet SOA Maturity Model: Oracle SOA Maturity Model: Software AG Define Initial Iteration		SOA Pilots Implementation Planning Bottom Up/Top Down Service Identification: Top Down vs. Bottom Up Defining Services Approach Implementing Services: Methodologies for change The Dual Lifecycle The Service Lifecycle Advanced Vision for Application Assembly Where’s the code? The Agile SOA Lifecycle Top-Down: Analyze Processes Process Analysis Process Optimization Discovering Existing Processes Service Identification: Process Decomposition Implementing Services Defining New SOBAs Technology Selection ZapElectric Component Model Purchasing SOA Technology Technology Selection: Choices
Exercise: SOA Roadmap
Homework: SOA Component Model
Class Ends at 5:00 PM
Day Four
Class Begins at 8:30 AM
Module 9: Addressing SOA Organizational Challenges
Organizational Issues Common SOA Pitfalls SOA Growing Pains The Wrong Question! Challenges in Calculating ROI Achieving Business Agility The Problems with “VDA” Challenge: The Right Amount of Governance Avoid Policy Bloat SOA by Any Name SOA = Best Practices Thinking Outside the SOA Box Dealing with SOA Hype and Anti-Hype Is there an Architect in the House? Hiring Architects EA Challenges: The Role of the EA Enterprise Architecture Challenges Questions to Ask Your EA Good Money after Bad The SOA Consultant Conundrum The SOA School Bus Are “SOA” Consultants Qualified? IT Governance Feedback Loop Interaction Challenges The Ivory Tower Problem The Power of the SOA Center of Excellence Convincing Technical Specialists Working with IT Middle Management Enabling Service Domains		Service Domain Roles SOA Funding Models Traditional IT Funding: Project Based Initial SOA Funding Funding Cross-Departmental SOA Initiatives CapEx vs. OpEx Budget Workarounds Case Study: ABN Amro Staffing Building the right SOA team Core SOA Governance Team Architecture Board SOA Steering Committee SOA Architecture Team Business Process Team Infrastructure/Operations Team Data Services Team SOA Project Staffing Project Leader Data Specialists Security Specialists Legacy Systems Specialists Service Development Specialists BPM/Composition Specialists Governance Tooling Specialists Testing & Deployment Specialists Project Archivists/Cybrarians External Services Specialists Case Study: SOA Organizational Change & Funding @ Novartis
Exercise: ROI of SOA
Module 10: Architecting with the Cloud
Cloud Computing: Old Wine in New Bottles Formal Definition of Cloud Computing Essential Cloud Characteristics Cloud Service Models Cloud Deployment Models Vendor Spin Oracle’s Shopping List IBM’s Shopping List Cutting Through the Hype Cloud Computing Roadmap EA Cloud Strategy Cloud Service Lifecycle Capabilities Design Pattern Relationship between Cloud & SOA Cloud Deployment Choices Services as a Service		Managed Hosting vs. Cloud Computing Some Cloud Realities Cloud Governance SOA Governance & Cloud Synergies Cloud: Raising the Governance Bar Governance-Related Cloud Issues Cloud Governance Challenges Extending SOA Governance to the Cloud Cloud Governance Pitfalls Dealing with Cloud Reliability Example: Amazon EC2 Cloud Governance as VM Governance Rogue Clouds Cloud Governance: Run Time Considerations Cloud Availability & Failover Cloud Governance Technology Cloud Governance Checklist
Final Exam: SOA Jeopardy!
Class Ends at 3:00 PM

Venue:

DePaul University, O’Hare Campus
8770 W. Bryn Mawr
Chicago, IL 60631 Chicago, IL 60631 Map and Directions

Nearby Hotels:

Click here for nearby hotels

LZA SOA Training & Certification: San Jose, CA May 2-5, 2011

admin — Fri, 06 Aug 2010 13:47:30 +0000

LZA SOA Training & Certification: San Jose, CA May 2-5, 2011
Monday May 2, 2011 – Thursday May 5, 2011
San Jose, CA
Price:

Price: $1,995.00 (including $500 early discount) [converted to 1995.00 USD]

Early registration expires: Apr 02, 2011

Map and Directions

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Vendor independent – We discuss vendors in context, both good and bad. You get a balanced perspective on each vendor we discuss.
Architect focused – The course concentrates on what architects have to do to be successful with SOA in their own organizations. We balance technology details with organizational approaches. If you’re not an architect you’ll learn how to think like one in this class!
Practical – we connect theory to practice with what really works in organizations like yours.
Current – we refresh the course on a regular basis to reflect the latest SOA best practices, as well as how SOA relates to other architectural challenges in the enterprise.
Enterprise context – SOA is an approach to organizing enterprise IT resources to meet changing business needs. We place SOA into the context of large organizations, with complex, heterogeneous IT environments and all the politics and bureaucracy that every large organization faces.
Globally recognized certification – Everybody who completes the LZA SOA Boot Camp obtains a certificate representing their LZA credential, giving you the right to call yourself a Licensed ZapThink Architect with all the privileges that come along with this exclusive credential.
Led by globally recognized SOA thought leader – All ZapThink’s courses are developed and led by Jason Bloomberg, ZapThink Managing Partner. Jason has been an analyst with ZapThink since 2001 and is the co-author of Service Orient or Be Doomed!
Not too technical, not too high-level – Unlike courses offered by SOASchool, CBDI, Web Age, SOA Institute, SOA Certified Professional (SOACP), Architecting the Enterprise (AtE), IBM, Oracle, Software AG, and others, we cover the technology without getting lost in the details. We discuss the big picture but connect it to the day-to-day reality of the IT shop.
Available around the world – See the event schedule on this page for all the locations we’re offering the LZA SOA Boot Camp!

Event Agenda

LZA SOA Boot Camp Version 8.0
Day 1
Registration: 8:00 to 8:30 AM
LZA Introduction
Module 1: The Enterprise Context for SOA
Business Constant: Change The Voice of Doom? Business Agility Defining SOA Why SOA? Business Drivers for SOA When Not to Apply SOA The Distributed Computing Pendulum SOA: Paradigm Shift? So, How to Implement SOA? Is SOA New? One Difference is Web Services Confusing SOA & Web Services How to Get a SOA If not Web Services, Then What? What is Architecture?		Architecting SOA: Beyond Use Cases SOA Implementation as Complex System Examples of Complex Systems The Focus of CSE CSE: Overall Coherence SOA as Enterprise Architecture The Zachman Framework Pros & Cons of Zachman Services Thinking Why is SOA Difficult? Case Studies: Mini-Studies on SOA Use Shared Services: US PTO Reducing Integration Costs: Aeroplan Compliance & Volume: .Wells Fargo Bank Meeting Client Needs: MITRE
Module 2: SOA Design Principles
Design Principle #1: Abstraction What’s a Service? Levels of Service Abstraction Service as Interface & Implementation Interoperability vs. Portability Service Interfaces Aren’t Good Enough! Abstractions: Simple on the Outside Abstraction = Working Illusion Building a Working Illusion The Fundamental Technical Challenge of SOA Multiple Interfaces per Implementation Multiple Implementations per Interface Multiple Interfaces per Business Service Actualizing the Business Service Abstraction SOA Design Principle #2: Standardized Service Contract What’s a Service Contract? Consumers & Providers WSDL: Service Contract Starting Point WSDL Basics Contract Metadata Beyond WSDL What’s Missing from WSDL? Sample Service Contract Template Design Principle #3: Encapsulation What’s NOT in the Contract Physical Service Architecture Design Principle #4: Discoverability What are Metadata? Metadata for SOA SOA Registry as Discovery Agency Location Independence Design Principle #5: Reusability Reusability vs. Usability Achieving Reusability: Service Agnosticism		Designing for Reuse:Agnostic Context Reuse over Time Design Principle #6: Granularity Key Service Abstraction Enabler: Proper Granularity Granularity Example Achieving Proper Granularity Example: Too Fine Grained vs.Too Coarse Grained Service Refactoring Refactoring Scenario After Refactoring Design Principle #7: Autonomy Autonomy Issue: Overlapping Functional Control Autonomy Issue: Concurrency Autonomy Issue: Scalability Autonomy Issue: Dependency Composition Autonomy: Problem Composition Autonomy: Solution Design Principle #8: Loose Coupling What about Coupling? Full Decoupling? Loose Coupling: Separation of Concerns Levels of Coupling RPC vs. Document Style Loose Coupling and Context Design Principle #9: Statelessness Maintaining Process Instance State Three Approaches to State Stateful Services Design Principle #10: Composability Metadata-Driven Applications Programmatic vs. Declarative Challenges with Declarative Approach Introducing “SOBA”
Exercise: Service Contract
Module 3: The SOA Reference Architecture
What is a Reference Architecture? Recommended SOA Reference Architecture Structure What’s Different about a SOA Reference Architecture? End-to-End Architecture: The SOA Metamodel SOA Foundation: Model-Driven Architecture SOA Foundation: The 4+1 View Model The 4+1 View Model & .The SOA Metamodel The Agility Model Service Architecture Building the Service Model Introducing “ZapElectric”		ZapElectric Service Model Entity Services Task Services Utility (IS) Services Service Relationships Example Process Isomorphism Service Layers ZapElectric Service Layer Model Component & Implementation Models ZapElectric Logical Architecture Model
Homework: Service Model
Class Ends at 5:00 PM
Day Two
Class Begins at 8:30 AM
Module 4: Intermediaries & Integration
SOA Infrastructure Starting Point: The Intermediary Some Intermediary Roles Intermediaries and Service Facades Intermediaries & Messaging Buying an Intermediary? Don’t we just mean an Enterprise Service Bus? The Great ESB/SOA Middleware Boondoggle Buy More Middleware for SOA? ESB Federation? Compounding the Problem: No Clear ESB Definition The ESB Pattern Do You need an ESB for Service Mediation? Intermediary-Based Service Abstraction Building Intermediary-Based SOA Infrastructure SOA Message Exchange Patterns SOA Tenet: Asynchrony Messages vs. Events Business Driver: Visibility Visibility & Heterogeneity SOA, Integration & Legacy Exposing Existing Capabilities The Continued Value of Legacy Legacy Migration Legacy Enablement		Legacy Rejuvenation Migration vs. Rejuvenation Business Driver: Cost Savings Reducing Integration Cost SOA & Data Data: Foundation for SOA The Data Services Layer Application Services vs. .Data Services Application Services abstract application APIs Application-centric .transactionality Data Services abstract data queries Designing Data Services Performance vs. Flexibility Supporting Data Services with Data Integration Leveraging Data Services Layer Semantic Level Understanding Role of Application Semantics Sample Semantic Model Semantics: The Greatest Integration Challenge of SOA Still a Manual Process Resolving Semantic Issues Industry-Specific Semantic Standards Case Study: SOA at The Hartford
Module 5: Service Composition, Business Process, & SOBAs
What is a Business Process? The Automation Paradox Problems with Traditional BPM Tooling Business Process the Enterprise Application Way Business Process the Service-Oriented Way Service-Oriented Process Process Definitions Example: Orchestration vs. Choreography Web Services Orchestration Standard BPEL Example Limitations of BPEL BPMN to the Rescue? BPMN Example Limitations of BPMN How SOA Fills the Gap What is the Sweet Spot for SOBAs? SOBA Example		Enterprise Applications and Process Example: SAP NetWeaver Transactions and SOA Transactions the .Loosely-Coupled Way Compensating Transactions What about Workflow? Workflow & SOA Ad Hoc Processes Mashups: Situational Apps for SOA Data Mashup Example Process Mashup in Action Process vs. Data? The Long Tail: Applications The Enterprise 2.0 Long Tail Without Governance, Mashups are Dangerous Without SOA, .Mashups are Toys Case Study: SOA Journey at BP
Exercise: Service-Oriented Business Processes
Module 6: XML Infrastructure & Security
Challenges at the Content Level Is XML Required for SOA? What about REST? XML: Foundation for Web Services The XML Processing Problem The XML Performance Crisis Solution: XML Appliances XML Firewall Intermediary Processing Challenges Performance analysis: where is the bottleneck? Critical XML Processing Challenge: Security The Context of IT Security The Open Systems Security Challenge XML Threat Prevention Mitigating XML Threats WSDL protection		XML Firewalls XML Encryption Encryption provides confidentiality XML Digital Signature Message-Level Security: Is SSL Sufficient? Core Requirements for Securing Services Web Services Security WS-Security Tokens Security Assertion Markup Language (SAML) SAML Assertions Federated Security Federated Security Illustration The Security Context Challenge Solving the Security Context Challenge: Single Sign-On The Role of Entitlement Management Case Study: SOA Security in the Real World — BP
Module 7: SOA Governance, Quality & Management (Part 1)
The GQM Loop Corporate Governance Governance & Regulatory Compliance The Business Motivation for Governance How to Tackle Governance? Governance Relationships The Cornerstone of IT Governance is Architecture Elements of IT Governance Strategy What is SOA Governance?		SOA Governance “in the Narrow” SOA Governance Activities Tiers of SOA Governance Enterprise/Strategic IT Governance SOA Operating Model .Governance Enterprise/Strategic IT Governance SOA Operating Model Governance Services Governance
Homework: Business Case
Class Ends at 5:00 PM
Day Three
Class Begins at 8:30 AM
Module 7: SOA Governance, Quality & Management (Part 2)
What is a Policy? Policy “Math” Computing Effective Policy WS-Policy Example S-PolicyAttachment Policy Attachment to WSDL 1.1 Policy: Business vs. .Technical Examples Design Time Policy Examples Run Time Policy Examples Change Time Policy Examples The Challenge of Policy Automation Steps for Automating Policies Some Policy Standards WS-SecurityPolicy Example Supporting Policy Changes The Policy Lifecycle Policy Lifecycle: Architect Policy Lifecycle: Administrator Policy Lifecycle: PEP Policy Lifecycle: Operations Policy Management & Enforcement Creating the Governance Framework SOA Asset Management Consumer Management Design Time Governance Publishing & Discovery Governance Sample Publishing/Discovery Governance Processes Governance Challenge: Reuse = Sharing Is Reuse a Real SOA Benefit? Run Time Governance SOA Monitoring & Management Checkpoints Analysis Checkpoint Design Checkpoint Implementation Checkpoint Operational Readiness Checkpoint		Governance Pitfall: Versioning Handling Service Versioning Versioning Concepts Versioning Strategies Strict Versioning Flexible Versioning Loose Versioning Versioning Policy Issues Governance Pitfall: Interoperability Web Services Interoperability Organization (WS-I) Tool Interoperability: Governance Interoperability Framework (GIF) GIF Capabilities Tool Interoperability: CentraSite Community CentraSite Community Members (Partial list) SOA Quality Quality & Complex Systems Policy Enforcement: Quality Continuous Quality Activities SOA Quality Organization Example The Long-Term Challenge of SOA Testing Testing in Production? The SOA Quality Star Best Effort SOA SOA Governance Infrastructure Complexities of SOA Governance Marketplace What is a Registry? What’s the Deal with UDDI? What is a Repository? The Registry/Repository Management & Loose Coupling SOA Management: .Many Facets The Problem with SOA Management The SOA Management Conundrum The First Rule of SOA Management ZapElectric Physical Architecture Model Case Study: SOA Project Management & Governance – T-Mobile
Exercise: Governance Framework
Module 8: Planning & Running the SOA Initiative
How Do You Eat an Elephant? Iterative: More than Step-by-Step Iterate your Architecture? Project Management for a SOA Project Defining SOA Roadmap Initial Assessments Building Support for SOA Building the SOA Business Case Milestone / KPI Plan The SOA Roadmap The ZapThink SOA Roadmap ZapElectric SOA Roadmap SOA Maturity Models Analogous to CMMI SOA Maturity Model Pointers Using a SOA Maturity Model SOA Maturity Model: HP SOA Maturity Model: Wipro Open Group Service Integration Maturity Model (OSIMM), .from IBM “SOA” Maturity Model – Sonic/Systinet SOA Maturity Model: Oracle SOA Maturity Model: Software AG Define Initial Iteration		SOA Pilots Implementation Planning Bottom Up/Top Down Service Identification: Top Down vs. Bottom Up Defining Services Approach Implementing Services: Methodologies for change The Dual Lifecycle The Service Lifecycle Advanced Vision for Application Assembly Where’s the code? The Agile SOA Lifecycle Top-Down: Analyze Processes Process Analysis Process Optimization Discovering Existing Processes Service Identification: Process Decomposition Implementing Services Defining New SOBAs Technology Selection ZapElectric Component Model Purchasing SOA Technology Technology Selection: Choices
Exercise: SOA Roadmap
Homework: SOA Component Model
Class Ends at 5:00 PM
Day Four
Class Begins at 8:30 AM
Module 9: Addressing SOA Organizational Challenges
Organizational Issues Common SOA Pitfalls SOA Growing Pains The Wrong Question! Challenges in Calculating ROI Achieving Business Agility The Problems with “VDA” Challenge: The Right Amount of Governance Avoid Policy Bloat SOA by Any Name SOA = Best Practices Thinking Outside the SOA Box Dealing with SOA Hype and Anti-Hype Is there an Architect in the House? Hiring Architects EA Challenges: The Role of the EA Enterprise Architecture Challenges Questions to Ask Your EA Good Money after Bad The SOA Consultant Conundrum The SOA School Bus Are “SOA” Consultants Qualified? IT Governance Feedback Loop Interaction Challenges The Ivory Tower Problem The Power of the SOA Center of Excellence Convincing Technical Specialists Working with IT Middle Management Enabling Service Domains		Service Domain Roles SOA Funding Models Traditional IT Funding: Project Based Initial SOA Funding Funding Cross-Departmental SOA Initiatives CapEx vs. OpEx Budget Workarounds Case Study: ABN Amro Staffing Building the right SOA team Core SOA Governance Team Architecture Board SOA Steering Committee SOA Architecture Team Business Process Team Infrastructure/Operations Team Data Services Team SOA Project Staffing Project Leader Data Specialists Security Specialists Legacy Systems Specialists Service Development Specialists BPM/Composition Specialists Governance Tooling Specialists Testing & Deployment Specialists Project Archivists/Cybrarians External Services Specialists Case Study: SOA Organizational Change & Funding @ Novartis
Exercise: ROI of SOA
Module 10: Architecting with the Cloud
Cloud Computing: Old Wine in New Bottles Formal Definition of Cloud Computing Essential Cloud Characteristics Cloud Service Models Cloud Deployment Models Vendor Spin Oracle’s Shopping List IBM’s Shopping List Cutting Through the Hype Cloud Computing Roadmap EA Cloud Strategy Cloud Service Lifecycle Capabilities Design Pattern Relationship between Cloud & SOA Cloud Deployment Choices Services as a Service		Managed Hosting vs. Cloud Computing Some Cloud Realities Cloud Governance SOA Governance & Cloud Synergies Cloud: Raising the Governance Bar Governance-Related Cloud Issues Cloud Governance Challenges Extending SOA Governance to the Cloud Cloud Governance Pitfalls Dealing with Cloud Reliability Example: Amazon EC2 Cloud Governance as VM Governance Rogue Clouds Cloud Governance: Run Time Considerations Cloud Availability & Failover Cloud Governance Technology Cloud Governance Checklist
Final Exam: SOA Jeopardy!
Class Ends at 3:00 PM

Venue:

San Jose, CA San Jose, CA Map and Directions

Nearby Hotels:

Click here for nearby hotels

LZA SOA Training & Certification: Seattle May 2-5, 2011

admin — Fri, 06 Aug 2010 13:47:30 +0000

LZA SOA Training & Certification: Seattle May 2-5, 2011
Monday May 2, 2011 – Thursday May 5, 2011
Seattle Central Community College
Room #4134 (4th Fl, Main Bldg)
1701 Broadway
Seattle, WA 98122
USA
Price:

Price: $1,995.00 (including $500 early discount) [converted to 1995.00 USD]

Early registration expires: Apr 02, 2011

Map and Directions

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Vendor independent – We discuss vendors in context, both good and bad. You get a balanced perspective on each vendor we discuss.
Architect focused – The course concentrates on what architects have to do to be successful with SOA in their own organizations. We balance technology details with organizational approaches. If you’re not an architect you’ll learn how to think like one in this class!
Practical – we connect theory to practice with what really works in organizations like yours.
Current – we refresh the course on a regular basis to reflect the latest SOA best practices, as well as how SOA relates to other architectural challenges in the enterprise.
Enterprise context – SOA is an approach to organizing enterprise IT resources to meet changing business needs. We place SOA into the context of large organizations, with complex, heterogeneous IT environments and all the politics and bureaucracy that every large organization faces.
Globally recognized certification – Everybody who completes the LZA SOA Boot Camp obtains a certificate representing their LZA credential, giving you the right to call yourself a Licensed ZapThink Architect with all the privileges that come along with this exclusive credential.
Led by globally recognized SOA thought leader – All ZapThink’s courses are developed and led by Jason Bloomberg, ZapThink Managing Partner. Jason has been an analyst with ZapThink since 2001 and is the co-author of Service Orient or Be Doomed!
Not too technical, not too high-level – Unlike courses offered by SOASchool, CBDI, Web Age, SOA Institute, SOA Certified Professional (SOACP), Architecting the Enterprise (AtE), IBM, Oracle, Software AG, and others, we cover the technology without getting lost in the details. We discuss the big picture but connect it to the day-to-day reality of the IT shop.
Available around the world – See the event schedule on this page for all the locations we’re offering the LZA SOA Boot Camp!

Event Agenda

LZA SOA Boot Camp Version 8.0
Day 1
Registration: 8:00 to 8:30 AM
LZA Introduction
Module 1: The Enterprise Context for SOA
Business Constant: Change The Voice of Doom? Business Agility Defining SOA Why SOA? Business Drivers for SOA When Not to Apply SOA The Distributed Computing Pendulum SOA: Paradigm Shift? So, How to Implement SOA? Is SOA New? One Difference is Web Services Confusing SOA & Web Services How to Get a SOA If not Web Services, Then What? What is Architecture?		Architecting SOA: Beyond Use Cases SOA Implementation as Complex System Examples of Complex Systems The Focus of CSE CSE: Overall Coherence SOA as Enterprise Architecture The Zachman Framework Pros & Cons of Zachman Services Thinking Why is SOA Difficult? Case Studies: Mini-Studies on SOA Use Shared Services: US PTO Reducing Integration Costs: Aeroplan Compliance & Volume: .Wells Fargo Bank Meeting Client Needs: MITRE
Module 2: SOA Design Principles
Design Principle #1: Abstraction What’s a Service? Levels of Service Abstraction Service as Interface & Implementation Interoperability vs. Portability Service Interfaces Aren’t Good Enough! Abstractions: Simple on the Outside Abstraction = Working Illusion Building a Working Illusion The Fundamental Technical Challenge of SOA Multiple Interfaces per Implementation Multiple Implementations per Interface Multiple Interfaces per Business Service Actualizing the Business Service Abstraction SOA Design Principle #2: Standardized Service Contract What’s a Service Contract? Consumers & Providers WSDL: Service Contract Starting Point WSDL Basics Contract Metadata Beyond WSDL What’s Missing from WSDL? Sample Service Contract Template Design Principle #3: Encapsulation What’s NOT in the Contract Physical Service Architecture Design Principle #4: Discoverability What are Metadata? Metadata for SOA SOA Registry as Discovery Agency Location Independence Design Principle #5: Reusability Reusability vs. Usability Achieving Reusability: Service Agnosticism		Designing for Reuse:Agnostic Context Reuse over Time Design Principle #6: Granularity Key Service Abstraction Enabler: Proper Granularity Granularity Example Achieving Proper Granularity Example: Too Fine Grained vs.Too Coarse Grained Service Refactoring Refactoring Scenario After Refactoring Design Principle #7: Autonomy Autonomy Issue: Overlapping Functional Control Autonomy Issue: Concurrency Autonomy Issue: Scalability Autonomy Issue: Dependency Composition Autonomy: Problem Composition Autonomy: Solution Design Principle #8: Loose Coupling What about Coupling? Full Decoupling? Loose Coupling: Separation of Concerns Levels of Coupling RPC vs. Document Style Loose Coupling and Context Design Principle #9: Statelessness Maintaining Process Instance State Three Approaches to State Stateful Services Design Principle #10: Composability Metadata-Driven Applications Programmatic vs. Declarative Challenges with Declarative Approach Introducing “SOBA”
Exercise: Service Contract
Module 3: The SOA Reference Architecture
What is a Reference Architecture? Recommended SOA Reference Architecture Structure What’s Different about a SOA Reference Architecture? End-to-End Architecture: The SOA Metamodel SOA Foundation: Model-Driven Architecture SOA Foundation: The 4+1 View Model The 4+1 View Model & .The SOA Metamodel The Agility Model Service Architecture Building the Service Model Introducing “ZapElectric”		ZapElectric Service Model Entity Services Task Services Utility (IS) Services Service Relationships Example Process Isomorphism Service Layers ZapElectric Service Layer Model Component & Implementation Models ZapElectric Logical Architecture Model
Homework: Service Model
Class Ends at 5:00 PM
Day Two
Class Begins at 8:30 AM
Module 4: Intermediaries & Integration
SOA Infrastructure Starting Point: The Intermediary Some Intermediary Roles Intermediaries and Service Facades Intermediaries & Messaging Buying an Intermediary? Don’t we just mean an Enterprise Service Bus? The Great ESB/SOA Middleware Boondoggle Buy More Middleware for SOA? ESB Federation? Compounding the Problem: No Clear ESB Definition The ESB Pattern Do You need an ESB for Service Mediation? Intermediary-Based Service Abstraction Building Intermediary-Based SOA Infrastructure SOA Message Exchange Patterns SOA Tenet: Asynchrony Messages vs. Events Business Driver: Visibility Visibility & Heterogeneity SOA, Integration & Legacy Exposing Existing Capabilities The Continued Value of Legacy Legacy Migration Legacy Enablement		Legacy Rejuvenation Migration vs. Rejuvenation Business Driver: Cost Savings Reducing Integration Cost SOA & Data Data: Foundation for SOA The Data Services Layer Application Services vs. .Data Services Application Services abstract application APIs Application-centric .transactionality Data Services abstract data queries Designing Data Services Performance vs. Flexibility Supporting Data Services with Data Integration Leveraging Data Services Layer Semantic Level Understanding Role of Application Semantics Sample Semantic Model Semantics: The Greatest Integration Challenge of SOA Still a Manual Process Resolving Semantic Issues Industry-Specific Semantic Standards Case Study: SOA at The Hartford
Module 5: Service Composition, Business Process, & SOBAs
What is a Business Process? The Automation Paradox Problems with Traditional BPM Tooling Business Process the Enterprise Application Way Business Process the Service-Oriented Way Service-Oriented Process Process Definitions Example: Orchestration vs. Choreography Web Services Orchestration Standard BPEL Example Limitations of BPEL BPMN to the Rescue? BPMN Example Limitations of BPMN How SOA Fills the Gap What is the Sweet Spot for SOBAs? SOBA Example		Enterprise Applications and Process Example: SAP NetWeaver Transactions and SOA Transactions the .Loosely-Coupled Way Compensating Transactions What about Workflow? Workflow & SOA Ad Hoc Processes Mashups: Situational Apps for SOA Data Mashup Example Process Mashup in Action Process vs. Data? The Long Tail: Applications The Enterprise 2.0 Long Tail Without Governance, Mashups are Dangerous Without SOA, .Mashups are Toys Case Study: SOA Journey at BP
Exercise: Service-Oriented Business Processes
Module 6: XML Infrastructure & Security
Challenges at the Content Level Is XML Required for SOA? What about REST? XML: Foundation for Web Services The XML Processing Problem The XML Performance Crisis Solution: XML Appliances XML Firewall Intermediary Processing Challenges Performance analysis: where is the bottleneck? Critical XML Processing Challenge: Security The Context of IT Security The Open Systems Security Challenge XML Threat Prevention Mitigating XML Threats WSDL protection		XML Firewalls XML Encryption Encryption provides confidentiality XML Digital Signature Message-Level Security: Is SSL Sufficient? Core Requirements for Securing Services Web Services Security WS-Security Tokens Security Assertion Markup Language (SAML) SAML Assertions Federated Security Federated Security Illustration The Security Context Challenge Solving the Security Context Challenge: Single Sign-On The Role of Entitlement Management Case Study: SOA Security in the Real World — BP
Module 7: SOA Governance, Quality & Management (Part 1)
The GQM Loop Corporate Governance Governance & Regulatory Compliance The Business Motivation for Governance How to Tackle Governance? Governance Relationships The Cornerstone of IT Governance is Architecture Elements of IT Governance Strategy What is SOA Governance?		SOA Governance “in the Narrow” SOA Governance Activities Tiers of SOA Governance Enterprise/Strategic IT Governance SOA Operating Model .Governance Enterprise/Strategic IT Governance SOA Operating Model Governance Services Governance
Homework: Business Case
Class Ends at 5:00 PM
Day Three
Class Begins at 8:30 AM
Module 7: SOA Governance, Quality & Management (Part 2)
What is a Policy? Policy “Math” Computing Effective Policy WS-Policy Example S-PolicyAttachment Policy Attachment to WSDL 1.1 Policy: Business vs. .Technical Examples Design Time Policy Examples Run Time Policy Examples Change Time Policy Examples The Challenge of Policy Automation Steps for Automating Policies Some Policy Standards WS-SecurityPolicy Example Supporting Policy Changes The Policy Lifecycle Policy Lifecycle: Architect Policy Lifecycle: Administrator Policy Lifecycle: PEP Policy Lifecycle: Operations Policy Management & Enforcement Creating the Governance Framework SOA Asset Management Consumer Management Design Time Governance Publishing & Discovery Governance Sample Publishing/Discovery Governance Processes Governance Challenge: Reuse = Sharing Is Reuse a Real SOA Benefit? Run Time Governance SOA Monitoring & Management Checkpoints Analysis Checkpoint Design Checkpoint Implementation Checkpoint Operational Readiness Checkpoint		Governance Pitfall: Versioning Handling Service Versioning Versioning Concepts Versioning Strategies Strict Versioning Flexible Versioning Loose Versioning Versioning Policy Issues Governance Pitfall: Interoperability Web Services Interoperability Organization (WS-I) Tool Interoperability: Governance Interoperability Framework (GIF) GIF Capabilities Tool Interoperability: CentraSite Community CentraSite Community Members (Partial list) SOA Quality Quality & Complex Systems Policy Enforcement: Quality Continuous Quality Activities SOA Quality Organization Example The Long-Term Challenge of SOA Testing Testing in Production? The SOA Quality Star Best Effort SOA SOA Governance Infrastructure Complexities of SOA Governance Marketplace What is a Registry? What’s the Deal with UDDI? What is a Repository? The Registry/Repository Management & Loose Coupling SOA Management: .Many Facets The Problem with SOA Management The SOA Management Conundrum The First Rule of SOA Management ZapElectric Physical Architecture Model Case Study: SOA Project Management & Governance – T-Mobile
Exercise: Governance Framework
Module 8: Planning & Running the SOA Initiative
How Do You Eat an Elephant? Iterative: More than Step-by-Step Iterate your Architecture? Project Management for a SOA Project Defining SOA Roadmap Initial Assessments Building Support for SOA Building the SOA Business Case Milestone / KPI Plan The SOA Roadmap The ZapThink SOA Roadmap ZapElectric SOA Roadmap SOA Maturity Models Analogous to CMMI SOA Maturity Model Pointers Using a SOA Maturity Model SOA Maturity Model: HP SOA Maturity Model: Wipro Open Group Service Integration Maturity Model (OSIMM), .from IBM “SOA” Maturity Model – Sonic/Systinet SOA Maturity Model: Oracle SOA Maturity Model: Software AG Define Initial Iteration		SOA Pilots Implementation Planning Bottom Up/Top Down Service Identification: Top Down vs. Bottom Up Defining Services Approach Implementing Services: Methodologies for change The Dual Lifecycle The Service Lifecycle Advanced Vision for Application Assembly Where’s the code? The Agile SOA Lifecycle Top-Down: Analyze Processes Process Analysis Process Optimization Discovering Existing Processes Service Identification: Process Decomposition Implementing Services Defining New SOBAs Technology Selection ZapElectric Component Model Purchasing SOA Technology Technology Selection: Choices
Exercise: SOA Roadmap
Homework: SOA Component Model
Class Ends at 5:00 PM
Day Four
Class Begins at 8:30 AM
Module 9: Addressing SOA Organizational Challenges
Organizational Issues Common SOA Pitfalls SOA Growing Pains The Wrong Question! Challenges in Calculating ROI Achieving Business Agility The Problems with “VDA” Challenge: The Right Amount of Governance Avoid Policy Bloat SOA by Any Name SOA = Best Practices Thinking Outside the SOA Box Dealing with SOA Hype and Anti-Hype Is there an Architect in the House? Hiring Architects EA Challenges: The Role of the EA Enterprise Architecture Challenges Questions to Ask Your EA Good Money after Bad The SOA Consultant Conundrum The SOA School Bus Are “SOA” Consultants Qualified? IT Governance Feedback Loop Interaction Challenges The Ivory Tower Problem The Power of the SOA Center of Excellence Convincing Technical Specialists Working with IT Middle Management Enabling Service Domains		Service Domain Roles SOA Funding Models Traditional IT Funding: Project Based Initial SOA Funding Funding Cross-Departmental SOA Initiatives CapEx vs. OpEx Budget Workarounds Case Study: ABN Amro Staffing Building the right SOA team Core SOA Governance Team Architecture Board SOA Steering Committee SOA Architecture Team Business Process Team Infrastructure/Operations Team Data Services Team SOA Project Staffing Project Leader Data Specialists Security Specialists Legacy Systems Specialists Service Development Specialists BPM/Composition Specialists Governance Tooling Specialists Testing & Deployment Specialists Project Archivists/Cybrarians External Services Specialists Case Study: SOA Organizational Change & Funding @ Novartis
Exercise: ROI of SOA
Module 10: Architecting with the Cloud
Cloud Computing: Old Wine in New Bottles Formal Definition of Cloud Computing Essential Cloud Characteristics Cloud Service Models Cloud Deployment Models Vendor Spin Oracle’s Shopping List IBM’s Shopping List Cutting Through the Hype Cloud Computing Roadmap EA Cloud Strategy Cloud Service Lifecycle Capabilities Design Pattern Relationship between Cloud & SOA Cloud Deployment Choices Services as a Service		Managed Hosting vs. Cloud Computing Some Cloud Realities Cloud Governance SOA Governance & Cloud Synergies Cloud: Raising the Governance Bar Governance-Related Cloud Issues Cloud Governance Challenges Extending SOA Governance to the Cloud Cloud Governance Pitfalls Dealing with Cloud Reliability Example: Amazon EC2 Cloud Governance as VM Governance Rogue Clouds Cloud Governance: Run Time Considerations Cloud Availability & Failover Cloud Governance Technology Cloud Governance Checklist
Final Exam: SOA Jeopardy!
Class Ends at 3:00 PM

Venue:

Seattle Central Community College
Room #4134 (4th Fl, Main Bldg)
1701 Broadway
Seattle, WA 98122
USA Seattle, WA 98122 Map and Directions

Nearby Hotels:

Click here for nearby hotels

ZapThink

5 IT-Supertrends bis 2020

ZapThink 2020’s Crisis Point: “Collapse of enterprise IT.” Is this our future?

The Impact of a Googless JavaOne

The Crisis Points of the ZapThink 2020 Vision

Identifying SOA’s ROI Still a Challenge

The Five Supertrends of Enterprise IT

LZA SOA Training & Certification: DC – Oct. 5-8, 2010

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Event Agenda

LZA SOA Boot Camp Version 8.0

Day 1

Module 1: The Enterprise Context for SOA

Module 2: SOA Design Principles

Module 3: The SOA Reference Architecture

Day Two

Module 4: Intermediaries & Integration

Module 5: Service Composition, Business Process, & SOBAs

Module 6: XML Infrastructure & Security

Module 7: SOA Governance, Quality & Management (Part 1)

Day Three

Module 7: SOA Governance, Quality & Management (Part 2)

Module 8: Planning & Running the SOA Initiative

Day Four

Module 9: Addressing SOA Organizational Challenges

Module 10: Architecting with the Cloud

LZA SOA Training & Certification: Chicago – Nov. 15-18, 2010

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Event Agenda

LZA SOA Boot Camp Version 8.0

Day 1

Module 1: The Enterprise Context for SOA

Module 2: SOA Design Principles

Module 3: The SOA Reference Architecture

Day Two

Module 4: Intermediaries & Integration

Module 5: Service Composition, Business Process, & SOBAs

Module 6: XML Infrastructure & Security

Module 7: SOA Governance, Quality & Management (Part 1)

Day Three

Module 7: SOA Governance, Quality & Management (Part 2)

Module 8: Planning & Running the SOA Initiative

Day Four

Module 9: Addressing SOA Organizational Challenges

Module 10: Architecting with the Cloud

LZA SOA Training & Certification: San Jose, CA May 2-5, 2011

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Event Agenda

LZA SOA Boot Camp Version 8.0

Day 1

Module 1: The Enterprise Context for SOA

Module 2: SOA Design Principles

Module 3: The SOA Reference Architecture

Day Two

Module 4: Intermediaries & Integration

Module 5: Service Composition, Business Process, & SOBAs

Module 6: XML Infrastructure & Security

Module 7: SOA Governance, Quality & Management (Part 1)

Day Three

Module 7: SOA Governance, Quality & Management (Part 2)

Module 8: Planning & Running the SOA Initiative

Day Four

Module 9: Addressing SOA Organizational Challenges

Module 10: Architecting with the Cloud

LZA SOA Training & Certification: Seattle May 2-5, 2011

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

What makes the LZA SOA Boot Camp so special?

Event Agenda

LZA SOA Boot Camp Version 8.0

Day 1

Module 1: The Enterprise Context for SOA

Module 2: SOA Design Principles

Module 3: The SOA Reference Architecture

Day Two

Module 4: Intermediaries & Integration

Module 5: Service Composition, Business Process, & SOBAs

Module 6: XML Infrastructure & Security