Oslc for owf think tank on open forges


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Oslc for owf think tank on open forges

  1. 1. Steve Speicher, IBM Rational Software Open Services for Lifecycle Collaboration open community. open interfaces. open possibilities OSLC Specifications for Interoperability © 2010 IBM Corporation
  2. 2. Traditional Approaches To Tool Integration Have Fallen Short Limited choice and coverage Single repository Point-to-point integrations - Hard to add existing (legacy) - Limited coverage: there are too tools many tools to cover more than a - Difficult to evolve tools small fraction of possibilities individually - Tight dependencies between - Limited to a single vendor’s tools require lockstep upgrades tools or affiliates - Proprietary APIs create vendor lock-in Universal metadata standard Standard implementations - Too slow to complete to keep pace - Requires “forklift” rip and with the market replace of existing tools - Hostage to vendor in-fighting - Hard to get widespread vendor - Difficult to migrate existing project support data and assets - Insufficiently flexible to address different user approaches Slow to emerge and disruptive to adopt 2 © 2010 IBM Corporation
  3. 3. Data Integration - the old way - “data locked in tools” Traceability links Model concepts Payment Pay Settlement Payment Cash Payment service service service service service service Software & Require- Bus Proc Ent Arch Solution Development Test ments Model Architecture Payment Pay Settlement Payment Cash Payment process process process process process process 3 © 2010 IBM Corporation 3
  4. 4. The Problem Needs A New Approach OSLC is a Breakthrough  Traditional integration architectures are like laying a cable between every pair of phones that want to call each other  Traditional integration relationships are like only allowing customers to call people on the “friends and family” list… except it’s the phone company’s “friends and family”  How can we achieve this much connectivity without this much cost and complexity? We need a new architecture and new relationships “You cannot solve a problem from the same Open Services for Lifecycle Collaboration consciousness that created it. You must learn open community. open interfaces. open possibilities to see the world anew.” (Albert Einstein) 4 © 2010 IBM Corporation 4
  5. 5. OSLC and Open Community Open Services for Lifecycle Collaboration open community. open interfaces. open possibilities Participation not politics  Open participation: Community of individuals interested in improving lifecycle integration – No “purity test” for membership – No membership fees  Transparent process: all discussions take place in the open, all documents are freely accessible – Specifications openly published – No chargeable validation suites  Visit open-services.net to sign up …unlike traditional partner programs that are closed and limited 5 © 2010 IBM Corporation 5
  6. 6. OSLC and Open Community Open Services for Lifecycle Collaboration open community. open interfaces. open possibilities Iterative Specification Authoring  Minimalist/additive approach – Not a “complete” definition for a given area  Scenario driven scope  Co-evolve spec and implementations  Open participation around active core group Iterate on Identify working Scenarios drafts Gain technical Call it a consensus, spec collect non- assert statements 6 © 2010 IBM Corporation 6
  7. 7. OSLC @ open-services.net ● Eleven workgroups operating today ● 338+ registered community members (up from 70 people since June 2009) ● Individuals from 34+ different companies have participated in OSLC workgroups (up Individuals represented from: from 5 companies since June 2009) Accenture Lender Processing Services APG Northrop Grumman Black Duck Oracle Boeing QSM ● 2.0 implementations starting to roll out BSD Group Rally Software Citigroup Ravenflow EADS Shell Emphasys Group Siemens Empulsys Sogeti Ericsson SourceGear/Teamprise Fokus Fraunhofer State Street Galorath Tasktop (Eclipse Mylyn) General Motors Thales Health Care Services Corp Tieto IBM TOPIC Embedded Systems Institut TELECOM UrbanCode Integrate Systems WebLayers 7 © 2010 IBM Corporation 7
  8. 8. OSLC and Open Interfaces Open Services for Lifecycle Collaboration open community. open interfaces. open possibilities An Internet of lifecycle resources If the entire Internet can connect like this,  Inspired by Internet principles, implemented would the same idea work for ALM? with Internet technologies: simple interfaces for exchange of resources  Loosely coupled: everything is a “resource” linked together with URLs  Technology neutral: treats all implementations Global Requirements equally Index  Minimalist: defines no more than necessary for Change exchange of resources Requests  Incremental: deliver value now, add more value Diagrams over time  Openly published standards: free to implement and irrevocable HTTP get/put/post …unlike traditional integrations that are tied to brittle, proprietary desktop and server technologies 8 © 2010 IBM Corporation 8
  9. 9. Data Integration – the new way – “WWW Arch and Linked Data” http://acme.com/paymentProcess http://acme.com/paymentService about about about about HTTP/REST Software & Enterprise Require- Bus Proc Solution Development Test Architecture ments Model Architecture 9 © 2010 IBM Corporation 9
  10. 10. Open Services for Lifecycle Collaboration Putting the approach into practice Step 1: Internet URLs for resources Step 2: Shared resource formats Step 3: Shared resource services 10 © 2010 IBM Corporation10
  11. 11. Jazz: An Architecture for Application Integration based on OSLC  Jazz tools implement OSLC specifications. Rational Jazz Non-Jazz Any Server Server Server  Tools integrate with Jazz using OSLC  Jazz tools integrate with Jazz tools OSLC, Jazz, Product Specific using OSLC  Jazz tools extend OSLC definitions Desktop Web Integrating Search Client Client Tool Apps  More about Jazz and Jazz-based solutions, go to jazz.net 11 © 2010 IBM Corporation
  12. 12. Specification Technical Components Discoverable HTTP Service C.R.U.D. for Definitions Resources Delegated UI HTTP for Create Query with and Select Paging UI Previews Standard Resource for Resource Representations Links 12 © 2010 IBM Corporation
  13. 13. Use Delegated Change Request Picker 13 © 2010 IBM Corporation
  14. 14. Barrier to entry: Low For service provider...  Leverages many existing capabilities of tools  Existing REST/HTTP or WebService based APIs can adopted  Existing Web UI dialogs can easily be incorporate needed changes  Open source libraries exist for OAuth – See http://oauth.net/code/ For consumer.... ● Many already have or choose from a vast array of HTTP clients ● Can leverage many open source toolkits ● More and more samples and articles coming each day 14 © 2010 IBM Corporation
  15. 15. Useful Links  OSLC Home Page –http://open-services.net  Video explaining OSLC – http://www.youtube.com/watch?v=B2vqL8fujgE  Whitepaper: The Business Value of OSLC – http://open-services.net/html/opencollab.pdf 15 © 2010 IBM Corporation
  16. 16. Conclusion  Participation is open. Easy. Get involved. ● Visit http://open-services.net ● Let your scenarios / problems be heard ● Help review specifications ● Contribute technical solutions as specification  Let's get our tools integrated... by exposing our data 16 © 2010 IBM Corporation
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.