SOA, OTD, and Web 2.0 = Collaboration
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


SOA, OTD, and Web 2.0 = Collaboration



Presented at Strategic Research Institute's 8th Annual Defense & Aerospace Investor & Corporate Development Conference

Presented at Strategic Research Institute's 8th Annual Defense & Aerospace Investor & Corporate Development Conference



Total Views
Views on SlideShare
Embed Views



3 Embeds 3

http://localhost 1 1 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

SOA, OTD, and Web 2.0 = Collaboration Presentation Transcript

  • 1. SOA, Web 2.0, and Open Technology Technology will Change some Key Competencies of the Defense Integrator Jim Stogdill CTO, ANSS Mission Services Accenture
  • 2. As we go from...
  • 3. This:
  • 5. Or This:
  • 6. Q: What will a company that is well positioned to compete in an era of networked systems look like?
  • 7. Discontinuity • Ubiquitous networks, SOA, Web 2.0, and Open Technology are weaving platforms together into ecosystems of capability. • It’s no longer enough to just know what your program is doing. It has to connect.
  • 8. Thesis: In the Shift from Systems to Ecosystems Companies that Collaborate will do better
  • 9. Or, to put it another way... Wang PC Closed Architecture Open Architecture
  • 10. Pain! From USAF Acquisition:
  • 11. Did that sound like a happy customer?
  • 12. This presentation is supposed to be about SOA Web 2.0 Open Technology...
  • 13. Service Oriented Architecture (SOA): Is an architectural approach in which systems expose capability via well defined service interfaces (often as Web Services) whose goals are cross platform / cross language interoperability and loose coupling between participating systems.
  • 14. Huh?
  • 15. The Overly Simple System Integration View
  • 16. The Overly Simple Data Integration View
  • 17. You might be thinking... “Really Can’t Say that Helped Much”
  • 18. A back of the envelope (literally) commercial SOA example
  • 19. The Pre-SOA Air Operations Center
  • 20. Using SOA to integrate Line of Business Applications
  • 21. Composite Applications and Workflows Note: these connections span programs
  • 22. The SOA-Connected Enterprise
  • 23. Web 2.0 (or just “the web”) is the business revolution in the computer industry caused by the move to the Internet as platform, and an attempt to understand the rules for success on that new platform. Chief among those rules is this: Build applications that harness network effects to get better the more people use them.”
  • 24. Web 2.0 Patterns • Harness collective intelligence: architecture of participation • Data as platform • Rich user experience • Software not tied to a single device • Perpetual beta • Leverage the long tail
  • 25. What it might look like
  • 26. Open Technology Development combines advances in the following areas: 1. Open Standards and Interfaces 2. Open Source Software and Designs 3. Collaborative / Distributive culture and online tools 4. Technological Agility
  • 27. When? Welcome to Project Documentation Source SOSCOE is the glue that holds FCS together... Wiki Distributed Get Started! Peer to Peer Get SOSCOE Open Join Buy a Tee shirt! ... and is an open source project funded by the U.S. Army to develop a next generation real time distributed platform. You are free to use, modify, and distribute SOSCOE. Don’t worry, we aren’t sharing the super secret squirrel stuff.
  • 28. If you are Proprietary standing Lock In here... ... go ahead and push!
  • 29. Bringing it back...
  • 30. New competencies, signals... • They don’t hesitate to use standard SOA interfaces on their projects despite anti-lock-in impact. • They regularly use open source in projects for their customers. • They already have programmers that contribute regularly to open source projects • They use collaborative tools within the enterprise and external to it: Wikis, shared code repositories, chat and irc, mailing lists,... • They are comfortable with agile methods. • They recognize the value of data • They add well understood web-oriented public API’s to their projects.
  • 31. Thanks!