Using an analogy, kids that don’t like to share.We’ve all seen these kids (of course we were never these kids nor or own children)These kids are very greedy, they won’t share even if they have plenty of toys.If they see another child with something, they want it…even though they have plentyProbably the biggest problem of all, is that other children don’t want to hang around with kids like this and these kids don’t fit well into various groupsAs these hoarder kids grow up, they lack of sharing impacts other group based activities
Take for example school project, team assignments or even sports teams.Perhaps these kids/people are very skilled at something, though they don’t share the responsibilities across the team. Instead, they have a mentality that if members of the group would just “get out of my way” I can carry the team.
Looking to the character Rod Tidwell from the movie Jerry Maguire which resembles a number of people we’ve dealt with in our lives…The problem with the project or teams success isn’t because of me, it is because of the way I wasn’t being utilized. If they would just “throw me the ball” then things would be better. If they would not throw me the ball over the middle so I wouldn’t get killed by DBs, etc
Let’s take a look at tools to assist the development teams.A common and early approach is say to go with an approach that a single vendor has “got this”.Of course this has many benefits: a single tool for end users to learn, cheaper admin as only 1 tool, easier to do cross discipline queries/reports, 1 vendor neck to choke.By any means necessary…haul and move the data, into a consolidated tool, a silo if you will.How many have a single vendor solution today?Who is workings towards getting there?Though, if you happen to succeed with such a project to consolidate. Congratulations. Though, how long did it last before a new acquisition or partnership? Do you make them throw out their tools and come to you?
Even as we try to consolidate onto a single tool, usually some unnatural acts are made to make this tool do everything we want.Take this Bobcat as an example, it has been outfitted with an extension that will feed logs into the cutter, cut the log and then push it threw a splitter. Cool, possible but how far can this go?
Though, there are needs of quite specialized tools like this hay bailer. The have a single function, the have an input and an output. You can adjust how big the bails are but that is it. Similarly we see a number of these tools without our daily lives, specialized Android or iOS app vulnerability testing, DB access generation code.It is often hard to adapt another tool to do this capability but this capability is quite handy, it would even be more valuable if inputs/outputs and connections to power were done a a way that could easily be leveraged by other tools.
Though this is more of the reality we are faced with every day, many different tools, many different purposes and often no consistent interface.As we’ve talked about, some are self-contained like the combine or bulldozer. Others are smaller general purpose, the potential users are different.The strategy of how you’d solve integrating these, is…Well in all likelihood there isn’t a single strategy, just like move towards a single tool for all you needs. Though there can be a primary strategy, different strategies for different needs, etc
Where do we start, let’s look at a leading strategy around open interfaces
Reference: “Linked Data”, Tim Berners-Lee, 2006-07-27
Points:Same information as the previous slide but just as a direct graphHighlight this is just the way the web worksCan point out that easy to extend to include things like: can learn when dependent software has been fixed, built and where it is available
Points:Reapplying the pattern, how this approach can just stitch in new graphs (or knowledge) fetched via GETs or other sources to pull into a bigger data source to apply cross tool query/analytics/visualizations and so on.Exposing an end point doesn’t mean you have to give away free, open access to your data. It just means
Going beyond query and read only access, the care and feeding of your data (and links)Based on industry proven best practices around REST and Linked Data, even including lessons learned from OSLCTouch on the standardization work going on at W3C
Command and control center is vital for staying current and providing information for making informed decisions.OSLC Tracked Resource Set specification provides for a simple, minimal way to tools to communicate a set of changes to consumers
lets take a high-level look at OSLC and its place in the industryOSLC[click] Leading choice …: both for many of our clients who are choosing to use OSLC to integrate their homegrown tools with OSLC-enabled tools and demanding that vendors provide OSLC-based integrations; but also in public interoperability projects such as CESAR and iFEST in Europe, and PROMIS in Japan. There are over 40 publically available tools that can be integrated using OSLC today.[click] Generally applicable: OSLC ‘s original focus was ALM and the IT industry, but just as domain and industry faces similar integration challenges, a solution based on the principles of OSLC can be applied to all of them (and has already been to many)“Simpler and flexible integrations with OSLC make software more useful and valuable for everyone.”[click] Scenario-driven …: Specifications are written to enable high-priority scenarios, and are not complete until they have been implemented. Think of it as “Agile specification development”.Eclipse Lyo (“Lee-o”)[click] Started in 2011, the Eclipse Lyo project exists to provide an SDK for OSLC developers (NOT an Eclipse plugin)Includes Java and Perl libraries for creating integrations based on OSLC specifications.Net libraries available through the CodePlex project OSLC4NetLibraries (and examples) for consuming OSLC data and for authentication using OAuth are included in the 1.1 (Feb 2013) releaseTest Suites simplify validation of existing OSLC providers, and enable test-driven development for new onesReference Implementations for OSLC specifications are (being made) available through Lyo tooW3C[click] OSLC has always been based on the “architecture of the web” and Linked Data, as described by Tim Berners-Lee[click] In 2012, IBM, DERI, EMC, Oracle, Red Hat, SemanticWeb.com, and Tasktop submitted parts of the OSLC Core specification to W3CThe Linked Data Platform (LDP) Working Group ccurrently has 49 participants (all in good standing) representing 30 organizationsLDP will serve as the basis for future OSLC specificationsA reference implementation of LDP is being developed in Eclipse LyoOASIS migration[click] On February 20, 2013, the OSLC Steering Committee (with members from Accenture, Creative Intellect, EADS, Siemens, Tasktop, and IBM) announced its intention to migrate OSLC specification development to the OASIS standardization track.Targeting submission (and acceptance) at the May 1st OASIS Board meetingOASIS Member Section construct allows the OSLC community to continue working the same way and maintain the relationships between domain specifications and the Core spec, while targeting formal standardization tooThe larger OSLC community continues to center itself at open-services.net; think of OASIS as the subcontractor for specification development and standardization[click]Proven … Open … InnovativeBuilt on proven technology, used in production systemsParticipation and use open to anyone, everywhere (@ OSLC, Lyo, W3C, and OASIS)As you can hear from developers and users, as you can see with LDP, OSLC brings real innovation to a challenging
Adoption rate:Using a standard interfaces allows for cheaper +1 integration, not doubt. As tool suppliers support this model, tool adoption rate within your own ALM chain is greatly reduced. The cost to integrate +1 is limited to 1 side of the connections, skills reused. Due to the flexibility, new/better/specialized tools can be added with minimal impact or effort.Focus:By not having to spend the additional time/effort on integration, savings are focused on “getting the job done”. Perhaps even better, as information is current and new/better tools are deployed.Innovation:Tools providers will no longer have to spend so much effort/energy on integrating, instead they can innovate on what is being exposed via open interfaces
Better integrations through open interfaces
Better Integrations through
Steve Speicher @sspeiche
IBM Rational - OSLC Lead
• IBM STSM, Software Group – Rational
• W3C Linked Data PlatformWG
• Rational’s lead for the OSLC
• Eclipse Lyo committer and project co-lead
Integrate with open protocols instead of unnatural adhesion
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those names.
3. When someone looks up a URI, provide useful
information, using the standards (RDF*, SPARQL)
4. Include links to other URIs. so that they
can discover more things.
Linked Data: Tim Berners-Lee
OSLC’s Big Picture
Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web
LINKED DATA PLATFORM WORKING GROUP
Inspired by the web
Free to use and share
Changing the industry
Tests, Libraries, Samples, Examples,
Generally applicable: specs available for many domains
covering ALM, DevOps, ISM, and PLM
Leading choice for strategic
Technical Committees are Driving Growth of Participation
Member Section Co-Founders
OSLC – Who’s involved?
OSLC – Who’s involved?
General Dynamics C4 Systems
Integrate Systems Engineering
NASA Jet Propulsion Laboratory
TOPIC Embedded Systems
Washington Metropolitan Area