1 / 19

OSLC Community Update & Introduction to PROMCODE 19 February 2014

OSLC Community Update & Introduction to PROMCODE 19 February 2014. Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web. Agenda & Presenters. OSLC Community Update Sean Kennedy IBM Introduction to PROMCODE Dr. Mikio Aoyama Nanzan University.

naomi
Télécharger la présentation

OSLC Community Update & Introduction to PROMCODE 19 February 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSLC Community Update & Introduction to PROMCODE 19 February 2014 Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web

  2. Agenda & Presenters • OSLC Community Update Sean KennedyIBM • Introduction to PROMCODEDr. Mikio AoyamaNanzan University http://manualassembly.net http://www.nise.org

  3. Jul ‘13 Oct ‘13 Feb ‘14 Jun ‘14 Core Change and Configuration Mgmt Automation PROMCODE Requirements, Architecture, and Quality Mgmt OSLC MS Affiliated TC Creation Pipeline

  4. Integrating and extending ALM, PLM and beyond OSLC is being standardized at OASIS Member Section Co-Founders Technical Committees are Driving Growth of Participation IBM Confidential - NDA

  5. OSLC: Collaborating across the industry Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web .NET too: http://oslc4net.codeplex.com/ OSLC Member Section http://oasis-oslc.org Linked Data Platform Working Group http://LinkedDataPlatform.org European Safety-Critical Interoperability Specification http://www.crystal-artemis.eu/ The Resource for OSLC Implementers http://eclipse.org/lyo Systems Engineering DSIG: OSLC4MBSE Working Group http://bit.ly/OMG-OSLC4MBSE Tool Integration and Interoperability Working Group http://bit.ly/INCOSE-TIIWG

  6. OSLC Connect @ ALM Forum http://alm-forum.com Great Presentations Wide range of other topics, including: Agile, DevOps, Architecture, Testing, & the Business of Software Towards a Lean Software Lifecycle - Industry Panel Mik Kersten, Tasktop Better Integration through Open Interfaces Steve Speicher, IBM April 1-3, 2014 Seattle, WA Link, not Synch! Arthur Ryman, IBM PROMCODE: An Open Platform for Large-Scale Contracted Software Delivery in Software Supply Chains Dr. Mikio Aoyama, Nanzan University Integration Principles and Reality Ludmila Ohlsson, Ericsson Overcoming Mobility Challenges Dave Stecher, PointSource Networking too! Facilitating Stockdale: Confronting and Overcoming the Brutal Facts of Continuous Improvement Sean Kennedy, IBM

  7. Introduction to PROMCODE Dr. Mikio AoyamaNanzan University http://www.nise.org Dr. Mikio Aoyama is a professor at the department of software engineering, Nanzan University, Japan. Before he joined the university, he has 15 years of experiences in the industry including managing large-scale software development. Currently, he is a chair of PROMCODE consortium, a joint research consortium with IBM, Fujitsu, NEC, NTT DATA, Hitachi and Nomura Research Institute founded on May 21, 2012. His research interest include software architecture, including cloud computing, SOA and automotive software, and requirements engineering. He published many books and more than 100 refereed papers. He has been serving many international conferences, including ICSE, IEEE Cloud, IEEE RE, and APSEC.

  8. OSLC Background

  9. The Integration Problem Point-to-point Integrations don’t scale Monocultures lock you in Maintenance, management, and change costs go up over time Ongoing and unexpected costs drain resources End-user productivity suffers: Either stuck with the wrong tool, stuck doing manual integration; often stuck doing both Creating new integrations is unpredictable Past choices restrict present action and future vision Integrations consume more of the IT budget: integration failures are the top 2 causes of software project delays* More limited ability to respond to change Constrained by exhausted IT budget and lower productivity * Commissioned study conducted by Forrester Consulting on behalf of IBM.

  10. OSLC’s Simple Solution Users can work seamlessly across their tools (complex and fragile synchronization schemes not required) Architecture of the Web Standard Interfaces Linked Data “Just Enough” integration Automation Increased reuse Increased traceability Monitoring Decreased maintenance costs Better visibility OSLC is an open and scalable approach to lifecycle integration. It simplifies key integration scenarios across heterogeneous tools

  11. The Basics: What is OSLC, and why should I care? OSLC is an open community building practical specifications for integrating software OSLC is beneficial to many stakeholders Contributing Organizations: http://oslc.co/organizations

  12. Aspirations for OSLC (From the OSLC Steering Committee)

  13. The Organizational Vision for OSLC OSLC Member Section at OASIS open-services.net News Steering Committee Subcommittees Implementer’s Expo User Groups Technical Committees Resources and Tutorials Forums ~~~ ~~..~~ Approved Standard W3C LDP WG Approved Standard Use what you need, share what you can. Approved Standard Approved Standard Eclipse Lyo Samples and Examples Libraries Test Suites OSLC4Net Reference Implementations

  14. OSLC HISTORY

  15. OSLC History Lesson (through October 2013) OASIS OSLC Core TC co-founded by Ericsson, fluid Operations, IBM, KTH, Software AG, and Tasktop OSLC Steering Committee votes to pursue OASIS: The plan that will eventually see OSLC specification development happen at OASIS is approved First OSLC Member Section Election: Boeing joins the Steering Committee 2013, May W3C Linked Data Platform WG approved: Parts of OSLC Core V2 spec contributed and used as the seed document; OSLC Core V3 work started with plans to rebase off of this future W3C Standard OSLC Member Section at OASIS created by 22 co-founders 2012, June OSLC V2 specs start finalizing: there are a growing number of implementations, many popular ALM tools are made available through adapters using a façade pattern OSLC Governance Matures: More rigorous IP policies introduced and Steering Committee created; members from: Accenture, Creative Intellect, EADS, IBM, Siemens, and Tasktop 2012, May 2011, June OSLC Architecture matures: OSLC Core WG founded, it will serve as the common basis for the OSLC V2 specs OSLC WGs start to address new segments: DevOps and Product Lifecycle Management first, Integrated Systems Management follows OSLC Change Mgmt V1 spec released: impls available from 3 vendors and in open source Eclipse Lyo project created: it is to become the resource for OSLC developers 2010, Feb 2009, June Many new WGs get started, including: Quality Mgmt, Requirements Mgmt, and Architecture Mgmt OSLC Change Mgmt is the first WG: scenario discussions will lead to a draft, implementations, and the V1 spec 2008, June OSLC announced: a revolutionary way to make application integrations simple & effective, building on the experience of the Web and the Jazz Platform

  16. OSLC Governance History • OASIS • Internationally recognized independent SDO • Formal support from 22 organizations (at launch) • Participation governed by established OASIS model Steering committee • Multi-organization steering committee established • New governance model introduced Community governance of OSLC IBM de facto governance (with community support) June 2012 May 2013

  17. Why OSLC and Standardizing at OASIS Matters

  18. OSLC: Standardizing the sharing of lifecycle data Scenario-driven & Solution-oriented Leading choice for strategic integration technology Generally applicable: specs available for many domains covering ALM, DevOps, ISM, and PLM Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web Based on and Shaping the Future of Internet Architecture Open and Independent Governance and Leadership OSLC Member Section Linked Data Platform Working Group The Resource for OSLC Implementers OSLC: Inspired by the web Proven Free to use and share Open Changing the industry Innovative

  19. Member Interest Member Interest OSLC UG Member Interest External Initiative OSLC UG External Initiative OSLC UG External Initiative Timing and Mission of OSLC Domain TCs, TBD Current spec progress? Final Scope Draft Converge Core 3.0 Change Management 3.0 1 Asset Management 3.0 OSLC Member Section Configuration Management 2 Core TC Quality Management 3.0 A Unordered Change and Configuration Management TC Requirements Management 3.0 Architecture Management 3.0 B Requirements, Architecture, and Quality Management TC C Automation TC Automation 3.0 D Integrated Service Management TC Performance Monitoring 3.0 Resource Reconciliation 3.0 E Other TCs based on other OSLC WGs, OSLC UGs, existing external initiatives, Member interest, or a combination of. PLM/ALM Estimation and Measurement Active specification work continues at open-services.net until those specs are contributed to an affiliated TC at OASIS

More Related