OSLC Community Update Introduction to PROMCODE 19

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

Agenda & Presenters 1. OSLC Community Update Sean Kennedy IBM http: //manualassembly. net 2. Introduction to PROMCODE Dr. Mikio Aoyama Nanzan University http: //www. nise. org 2 © 2014 OSLC UG for Communications

OSLC MS Affiliated TC Creation Pipeline Prioritization & Preparation with MS members TC Charter Creation & TC Co-submitter Recruiting TC Charter Submission & OASIS Process OASIS Approval & 1 st TC meeting Core TC Done Nov 2013 OSLC CCM TC Done Jan 2014 OSLC Automation TC Done Ø Mar 2014 Done OSLC PROMCODE TC Done Ø Mar 2014 Apr-May 2014 Jun 2014 Ø Dec 2013 – Feb Mar 2014 OSLC RAQ Mgmt TC Jul ‘ 13 Oct ‘ 13 Feb ‘ 14 Jun ‘ 14 Core Change and Configuration Mgmt Automation PROMCODE Requirements, Architecture, and Quality Mgmt 3 © 2014 OSLC UG for Communications

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

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

OSLC Connect @ ALM Forum http: //alm-forum. com Great Presentations Towards a Lean Software Lifecycle - Industry Panel Mik Kersten, Tasktop Wide range of other topics, including: Agile, Dev. Ops, Architecture, Testing, & the Business of Software Better Integration through Open Interfaces Steve Speicher, IBM 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 April 1 -3, 2014 Seattle, WA Integration Principles and Reality Ludmila Ohlsson, Ericsson Overcoming Mobility Challenges Dave Stecher, Point. Source Facilitating Stockdale: Confronting and Overcoming the Brutal Facts of Continuous Improvement Sean Kennedy, IBM 6 Networking too! © 2014 OSLC UG for Communications

Introduction to PROMCODE Dr. Mikio Aoyama Nanzan 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. 7 © 2014 OSLC UG for Communications

OSLC BACKGROUND © 2014 OSLC UG for Communications

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 9 * Commissioned study conducted by Forrester Consulting on behalf of IBM. © 2014 OSLC UG for Communications

OSLC’s Simple Solution Users can work seamlessly across their tools (complex and fragile synchronization schemes not required) Architecture of the Web Standard Interfaces Automation Linked Data “Just Enough” integration 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 10 © 2014 OSLC UG for Communications

The Basics: What is OSLC, and why should I care? OSLC is an open community building practical specifications for integrating software Tool Maker • create software using reusable and open assets that will interoperate with other tools both inside and outside your influence providing time and cost savings Tool Manager • reduce the complexity and risk of increasingly complex software infrastructures, and improve the value of software across a broader set of internal and external stakeholders Tool User • choose the best tools for your job and have them interact seamlessly to achieve traceability and visibility with the rest of your organization Systems Integrator • focus energy and resources on higher-value customizations, deliver more business value to your clients, and increase client satisfaction OSLC is beneficial to many stakeholders Contributing Organizations: http: //oslc. co/organizations 11 © 2014 OSLC UG for Communications

Aspirations for OSLC (From the OSLC Steering Committee) Foundational technology for all integration The household name for integrations Natural choice for standardizing looselycoupled integrations in new domains 12 © 2014 OSLC UG for Communications

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

OSLC HISTORY © 2014 OSLC UG for Communications

OSLC History Lesson (through October 2013) OASIS OSLC Core TC co-founded by Ericsson, fluid Operations, IBM, KTH, Software AG, and Tasktop First OSLC Member Section Election: Boeing joins the Steering Committee ay OSLC Steering Committee votes to pursue OASIS: The plan that will eventually see OSLC specification development happen at OASIS is approved , M 3 01 2 W 3 C Linked Data Platform WG approved: Parts of OSLC Core V 2 spec contributed and used as the seed document; OSLC Core V 3 work started with plans to rebase off of this future W 3 C Standard e n Ju 2, 01 OSLC V 2 specs start finalizing: there a growing number of implementations, many popular ALM tools are made available through adapters using a façade pattern 2 ay , M 12 20 e un J 1, OSLC Architecture matures: OSLC Core WG founded, it will serve as the common basis for the OSLC V 2 specs OSLC Change Mgmt V 1 spec released: impls available from 3 vendors and in open source b e 20 15 e 20 OSLC Governance Matures: More rigorous IP policies introduced and Steering Committee created; members from: Accenture, Creative Intellect, EADS, IBM, Siemens, and Tasktop OSLC WGs start to address new segments: Dev. Ops and Product Lifecycle Management first, Integrated Systems Management follows Eclipse Lyo project created: it is to become the resource for OSLC developers un J 9, 0 un e , F 10 20 , J 08 1 20 OSLC Member Section at OASIS created by 22 co-founders 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 V 1 spec OSLC announced: a revolutionary way to make application integrations simple & effective, building on the experience of the Web and the Jazz Platform © 2014 OSLC UG for Communications

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

Why OSLC and Standardizing at OASIS Matters Software runs the world But it is heterogeneous and disjoint And it needs to be integrated Traditional approaches to software integration require custom software Custom software is expensive to maintain and a limit on future choice Custom integrations drive software TCO higher and limit choice Open standards are key enablers for broad and large-scale integration OSLC standards simplify lifecycle integration leading to cost savings and increased flexibility OSLC is helping the world run more efficiently Standardizing OSLC at OASIS will increase adoption and acceptance of OSLC The world will benefit from standardized integration through OSLC 17 © 2014 OSLC UG for Communications

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, Dev. Ops, ISM, and PLM Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web OSLC Member Section Linked Data Platform Working Group Based on and Shaping the Future of Internet Architecture OSLC: 18 Open and Independent Governance and Leadership The Resource for OSLC Implementers Inspired by the web Proven Free to use and share Open Changing the industry Innovative © 2014 OSLC UG for Communications

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