Main Point: We know organizations have a gap between the software delivery capabilities they need to succeed and the ones they have in house currently. Successful organizations know that when they improve their abilities in this area, they increase their success. In fact a recent IBV study where organizations self-reported that... Insights from 435 executives in 58 countries, spanning 18 industries 85% realize and reported it is important to critical Only 25% say they are able to fully leverage software delivery effectively So there is a gap -- but when companies that can close the resulting execution gap stand to benefit. Almost 70 percent of the companies currently leveraging software development for competitive advantage outperform their peers from a profitability standpoint TRANSITION – so there is a huge opportunity for our clients to close that gap…let ’s move to the next slide and talk about how -------------------------------------------------------------------------------------------------- Note: Outperformers were determined by a self-assessment of profitability against peers in the industry, ranging from 1 (Significant underperformers) to 5 (Significant outperformers) Significant outperformers were ranked as a 5, Average performers a 3-4 and Underperformers 1-2 new Rational/WebSphere IBV Study "The Software Edge - How effective software development drives competitive advantage" This study examined the correlation between software delivery competency and industry competitive advantage Insights from 435 executives in 58 countries, spanning 18 industries Roles included executives at director level and above in IT and other software organizations Software delivery refers to all areas of development, operations, and support within IT and other development / engineering organizations “ There was 54% of the companies who said they believe software is critical and 32 percent who called it moderately important – so that’s 86 percent of the respondents say software is either critical or moderately important and that points to the need for better tooling for software development and delivery.” said Randy Newell, director of capabilities marketing for IBM Software Group with a focus on the Rational brand.
From the Agenda: In this “new normal,” the most forward thinking companies will: Establish an enterprise capability for accelerated delivery of software that enables them to seize market opportunities and reduce time to customer feedback, improve governance while balancing quality and cost
Solutions designed only for point-to-point integration No external review or visibility into solution Solutions built to patch immediate need Often integrations were built after the fact with limited product APIs Solution design goals and approach limited No consensus driven approach Integrators limited to a small set of business partners No open process for other interested parties to get involved Limits solution to particular use cases and technologies Restrictive licenses and usage of intellectual property License fees or fear of giving up IP, force alternative solutions
Single repository Hard to add existing tools Difficult to evolve tools individually Limited to a single vendor’s tools or affiliates Point-to-point integrations Limited coverage: there are too many tools to cover more than a small fraction of possibilities Tight dependencies between tools require lockstep upgrades Proprietary APIs create vendor lock-in Universal metadata standard Too slow to complete to keep pace with the market Hostage to vendor in-fighting Difficult to migrate existing project data and assets Standard implementations Requires “forklift” rip and replace of existing tools Hard to get widespread vendor support Insufficiently flexible to address different user approaches
You do this everyday! Web browser example. + single web page, data sourced from many places … ads, videos, pictures, tweets, comments, content, more links Linking to application lifecycle data where it is created , instead of copying and synchronizing between tools, is the key insight of OSLC. Doing so using standard interfaces , on top of a proven architecture , has helped many realize the value of OSLC already. With OSLC , instead of worrying about integrating specific tools, we focus on composing a set of capabilities. Animations (OSLC is …) : Approach to integrations Philosophy of specification development Set of specifications that tell you what and how to integrate various capabilities It is also the open community where all this happens 4. Read This has benefits to professional users (5), business leaders (6) and creators of integrations (7)
When: - use this to create and maintain links between issues found in production and the fixes made in development to address them - use this to understand the status of problems which require development teams to provide fixes Why: - it is very common for coordinated actions to be taken across development and operations. Linking respective work items increases efficiency of all collaborators - linking information can assist with problem analysis and troubleshooting of similar problems found by operations in the future. How: - background processes (tasks) are run which maintain synchronization of information between TSRM and ClearQuest - extensible to allow for an organization's customized fields to also be updated appropriately
Mik: 7 minutes
OSLC streamlines and simplifies the creation and management of software, whether the context be traditional IT, smarter infrastructure and devices, mobile, cloud, ... whatever. OSLC's approach to integration solves a decades old problem so that users can mix and match their tools with confidence. This approach is proven and is now to be standardized with support from across the industry, including vendors, enterprise end users, integrators, and academia.
Steering Committee At launch, the current OSLC Steering Committee will become the OASIS OSLC Member Section Steering Committee. In 2014, ½ the Steering Committee seats will be up for election by, and from amongst, the organizations who are part of the Member Section. (The other half in 2015; i.e. half the seats are up for election each year.) Technical Committees (TC) This is where the specification development and standardization work happens. Each TC must have participation from 3+ organizations. (There may be multiple participants from each organization.) Participation Organizations who found, or later join, the Member Section gain several privileges: Voting in and standing for election in Steering Committee elections. Working in Technical Committees and Subcommittees. Participate in reviews of TC drafts and submissions (for standardization)
Points: At the core is a set of Statements (aka facts), which are typically written down or learned Tell the story as if the present is a tester, they have knowledge of their test cases and of Joe. In the Web 1.0/2.0 way to learn these things is by publishing on a HTML page for a human consumer of it This follows TBL’s 4 rules for linked data First we give these statement URIs so computers can identify them and understand them. Grouping into subject-predicate-object builds the statement Next we can do a HTTP GET to learn more When we learn more, it is in the form of more statements with URIs Those URIs point to more things or relate things back to things we already know (Joe) Jira http://www.atlassian.com/software/jira/overview
Points: At the core is a set of Statements (aka facts), which are typically written down or learned Tell the story as if the present is a tester, they have knowledge of their test cases and of Joe. In the Web 1.0/2.0 way to learn these things is by publishing on a HTML page for a human consumer of it This follows TBL’s 4 rules for linked data First we give these statement URIs so computers can identify them and understand them. Grouping into subject-predicate-object builds the statement Next we can do a HTTP GET to learn more When we learn more, it is in the form of more statements with URIs Those URIs point to more things or relate things back to things we already know (Joe) Jira http://www.atlassian.com/software/jira/overview
I call this the 30,000 feet view and the previous example the 3 inch view. So taking a giant leap back, here’s what you get (in a way) at a global scale.
Highlights the different between Linked Data and how OSLC enhances and builds off it. When we have linked data (liked W3C Linked Data Platform), OSLC provides: Resource types and properties (vocabularies) based on scenarios An easy way to embed a fragment of HTML (link preview) into another application using standard HTTP content negotiation A way to take another web application’s (tool’s) web UI’s creation and selection dialog and embed them into your own