What will a company that is
well positioned to compete
in an era of networked
systems look like?
• 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.
In the Shift from Systems to
Collaborate will do better
Or, to put it another
Closed Architecture Open Architecture
This presentation is
supposed to be about
Service Oriented Architecture (SOA):
Is an architectural approach in which
systems expose capability via well
deﬁned service interfaces (often as Web
Services) whose goals are cross
platform / cross language
interoperability and loose coupling
between participating systems.
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.”
Web 2.0 Patterns
• Harness collective intelligence: architecture
• Data as platform
• Rich user experience
• Software not tied to a single device
• Perpetual beta
• Leverage the long tail
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
4. Technological Agility
Welcome to www.SOSCOE.org
Source SOSCOE is the glue that holds FCS together...
Get Started! Peer to Peer
Get SOSCOE Open
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.
If you are Proprietary
standing Lock In
... go ahead
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
• 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.