Presentation is loading. Please wait.

Presentation is loading. Please wait.

John Lanuti IBM Rational IT Specialist

Similar presentations


Presentation on theme: "John Lanuti IBM Rational IT Specialist"— Presentation transcript:

1 John Lanuti IBM Rational IT Specialist
What’s Rational? John Lanuti IBM Rational IT Specialist

2 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 2

3 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 3

4 IBM Rational CLM v4.0.x highlights
2013 2012 2011 Enterprise Deployment Requirements Support server rename for production-to-production Tool for validating mapping files Post rename validation support Support additional non-CLM integrations for server rename New platform support Mac OS X, and Safari for RTC, RQM, RRC*, DNG Chrome and Safari for RTC, RQM, RRC*, DNG Extend CLM: Align DOORS.NG and RSA-DM with CLM Serviceability, Quality, and Performance Improvements Customer awareness and engagement Process improvement to enable continuous delivery Individual product enhancements 21 4 4 4

5 IBM Rational Requirements Composer v4.0.x highlights
2011 2012 2013 New online document structures (Modules) for requirement organization and structure Take requirements offline or exchange them round trip for broader collaboration Improved traceability to show more detail to enable business analysts to better analyze Connect tests and plans to requirements using the new RRC/HPQC Integration Adaptor Connect requirements to models and elements through OSLC to RSA Design Manager Business analysts can compare collections to version of the same collections These are just a few of the enhancements planned for See the details and status of our release plan on jazz.net at https://jazz.net/projects/rational-requirements-composer Modules: Artefacts Structure/Organization: Business analysts will have the ability (in addition to a collection) to place artefacts into organized structures and apply hierarchy and order. This will help in the management process to increase control for requirements by group and give teams’ additional meaning, awareness and understanding. The Design Management project on Jazz.net is an effort to improve collaboration in modeling/design and provide stable, server-side integrations/traceability with other lifecycle artifacts, including requirements. AM integration involves two parts: Implementation of OLSC-AM services in RRC Testing/supporting integration scenarios with RSA Design Manager (with links originating from RRC and visible in RRC) RSA Design Manager initial GA June 2011 can see requirements and create OLSC links to the requirements managed in RRC, but they are visible only from the Design Manager side until RRC becomes a consumer of OLSC-AM and can query the Design Manager repository for link information. RSA Design Manager and Rhapsody Design Manager provide the same jazz repository for collaborative design management. The above explanation references RSA more than Rhapsody, since RSA is more often used in IT, as is = RRC. RRC/HPQC integration: using OSLC principles to make requirements available to testers using HPQC and enabling RM-QM traceability visible in both tools. 22 5 5 5

6 IBM Rational Team Concert v4.0.x highlights
2011 2012 2013 Improved performance and usability - Up to 25% faster plan rendering; And new auto-scrolling support Process sharing and customization - Inherit process across projects and add local project customizations Better support for code reviews – View cumulative file changes in a feature – Change Summary view More flexible dependency build support for z/OS – Control build output names with custom patterns Extended platform support – Mac OS X clients, Visual Studio 2012 IDE, and Chrome browser With Rational LifeCycle Adaptors – Integrate w/ HPQC, Git, Jira, Visual Studio Team System and more! These are just a few of the enhancements planned for See the details and status of our release plan on jazz.net at https://jazz.net/projects/rational-requirements-composer Modules: Artefacts Structure/Organization: Business analysts will have the ability (in addition to a collection) to place artefacts into organized structures and apply hierarchy and order. This will help in the management process to increase control for requirements by group and give teams’ additional meaning, awareness and understanding. The Design Management project on Jazz.net is an effort to improve collaboration in modeling/design and provide stable, server-side integrations/traceability with other lifecycle artifacts, including requirements. AM integration involves two parts: Implementation of OLSC-AM services in RRC Testing/supporting integration scenarios with RSA Design Manager (with links originating from RRC and visible in RRC) RSA Design Manager initial GA June 2011 can see requirements and create OLSC links to the requirements managed in RRC, but they are visible only from the Design Manager side until RRC becomes a consumer of OLSC-AM and can query the Design Manager repository for link information. RSA Design Manager and Rhapsody Design Manager provide the same jazz repository for collaborative design management. The above explanation references RSA more than Rhapsody, since RSA is more often used in IT, as is = RRC. RRC/HPQC integration: using OSLC principles to make requirements available to testers using HPQC and enabling RM-QM traceability visible in both tools. 23 6 6 6

7 IBM Rational Quality Manager v4.0.x highlights
2011 2012 2013 Be more efficient with additional ways to sort, filter, query and edit test artifacts Improved requirement driven testing support with new live views and reconciliation capabilities Process customization and enforcement to meet regulatory requirements Reports on master-child test plans and on custom parameters Ability to integrate your specific test automation tool using the new public adapter SDK These are just a few of the enhancements planned for See the details and status of our release plan on jazz.net at https://jazz.net/projects/rational-requirements-composer Modules: Artefacts Structure/Organization: Business analysts will have the ability (in addition to a collection) to place artefacts into organized structures and apply hierarchy and order. This will help in the management process to increase control for requirements by group and give teams’ additional meaning, awareness and understanding. The Design Management project on Jazz.net is an effort to improve collaboration in modeling/design and provide stable, server-side integrations/traceability with other lifecycle artifacts, including requirements. AM integration involves two parts: Implementation of OLSC-AM services in RRC Testing/supporting integration scenarios with RSA Design Manager (with links originating from RRC and visible in RRC) RSA Design Manager initial GA June 2011 can see requirements and create OLSC links to the requirements managed in RRC, but they are visible only from the Design Manager side until RRC becomes a consumer of OLSC-AM and can query the Design Manager repository for link information. RSA Design Manager and Rhapsody Design Manager provide the same jazz repository for collaborative design management. The above explanation references RSA more than Rhapsody, since RSA is more often used in IT, as is = RRC. RRC/HPQC integration: using OSLC principles to make requirements available to testers using HPQC and enabling RM-QM traceability visible in both tools. 24 7 7 7

8 8 More on collaboration and integration Rational Software Architect with Design Management IBM Collaborative Design Management Features and capabilities Design in context Work seamlessly with analysts, developers, and testers using RRC, RTC, RQM, and DOORS. Make designs first class artifacts in your lifecycle projects. Collaborate Invite users and other experts to collaborate on your designs. Use threaded comments, design mark-up, and automated design reviews. Sketch out ideas before turning them into designs. Traceability and impact analysis Link designs to requirements, test artifacts, work items, and other designs. Visualize relationships within a design and with other lifecycle resources. Know the impact of a design change. Manage change Collaborate with your team on changes to the same designs without conflicts. Features shown in screen shot: Mark-up View designs over the web Right panes: Collaborate with stakeholders with commenting Left panes: Browse design information Customer Quote on using this tool: “The ability to review and comment on models from the Web client encourages feedback from a wide array of stakeholders... leading to faster consensus and improved quality of solution designs.” – Lars Tufvesson, Sellegi Publish design documents Generate customized design documents from a template or create living design documents as part of your project. Designs at your finger tips Quickly search across designs to learn from past projects and find reusable design components. 8 8 8 8

9 IBM Rational Recognized As A Leader in ALM
10/23/12 IBM Rational Recognized As A Leader in ALM The Forrester WaveTM: Application Life-cycle Management Q4 2012* Report Highlights Highest Scores among all vendors for Current Offering & Strategy“ “Not only has IBM continued development of its strong suite of products, but it has also stitched them together in a more coherent way.” [IBM] has also made clearer the use cases it supports ... such as Agile teams and embedded software development" Link to report *Forrester Research Inc, October 23, Forrester Research, The Forrester Wave™ is copyrighted by Forrester Research, Inc. Forrester and Forrester Wave™ are trademarks of Forrester Research, Inc. The Forrester Wave™ is a graphical representation of Forrester's call on a market and is plotted using a detailed spreadsheet with exposed scores, weightings, and comments. Forrester does not endorse any vendor, product, or service depicted in the Forrester Wave. Information is based on best available resources. Opinions reflect judgment at the time and are subject to change. 9

10 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 10

11 The confluence of two streams
DOORS Heritage Requirements engineering Manage requirements in modules Traceability at large scale Compliance & safety-critical In DOORS NG 2012 and RRC 4.0.1 Modules Fine-grain access controls Improved scalability (and much more) DOORS NG builds on the heritage of DOORS over the last two decades: proven approaches to requirements engineering, on safety-critical systems, and for complex products and systems. DOORS NG also builds on 4+ years of development and production experience with Jazz RM (sold as Rational Requirements Composer). When we started DOORS NG we combined our RM development teams to make this confluence real. Jazz RM Heritage Engage your stakeholder community Visual notations for requirements Light-weight RM process 11

12 Evolving multiple RM solutions…
DOORS has been the market leading RM tool for the last decade and has lead many initiatives to progress Requirements Management needs It is IBM’s intention to continue to lead the way with new initiatives for RM and DOORS DOORS 9.x With ~1 million users around the world we now enhance DOORS 9 in parallel to Jazz based solutions We plan releases of DOORS 9 in 2012 and are planning releases for 2013 and beyond DOORS Next generation Addressing the RM needs in more agile SE, and the architecturally challenging RFEs on DOORS We intend DOORS and DOORS Next Generation to interoperate to enable you to choose when to move Rational Requirements Composer Continue to evolve to address the RM needs of IT ALM and Agility at Scale We plan to share a single server and web client technology for RRC and DOORS Next Generation

13 DOORS 9.x releases 2012 2011 2012 2013 2014 2015… 2Q12 DOORS 9.4
2Q12 DOORS 9.4 Beginning to transition integrations from synchronization to linked lifecycle data DOORS & RQM Improved visibility of DOORS attributes Invoke DXL using OSLC Link between DOORS 9, DOORS Next Generation Upgrade RIF to the latest version of ReqIF Data exchange: DOORS 9 and DOORS Next Generation Improved support for your supply chain Security Enhancements Move authentication / authorization to DOORS server Document generation Run user-defined templates without an RPE license Usability Improvements DOORS – HP Quality Center v11 4Q12 DOORS 9.5 DOORS – TFS 2010, DOORS – Rhapsody Design Manager IBM Rational DOORS Kit for ISO & IEC 61508 Supporting the “Tracked Resource Set Protocol”, contributing data tor RELM ReqIF supports DOORS-DOORS better due to more meta data being transferred Support for defined filters and views Support for data locking to ensure no edit conflicts between databases 13 13 13 13

14 1414 IBM Rational DOORS Next Generation DOORS concepts improved and much more…. Improved! NEW! Definition Rich-text documents Diagrams: Process, Use Case Storyboards, UI sketching & flow Project glossaries Templates Management Structure, Attributes/Types Traceability, Filtering, Tags Baselines, Change History Reuse (reqs & types) Reporting Metrics & Doc. NEW! NEW! Visibility Customizable dashboards Analysis views Collections Milestone tracking & status Lifecycle Central requirements, test, & development repository Common administration and role-based user licensing Warehouse reporting NEW! NEW! Collaboration Review & Approval Discussions Notification Planning Integrated planning Effort estimation Task Management

15 Choosing the Right RM solution for your teams Buy DOORS; deploy one or both flavors
DOORS 9 indicators DOORS NG indicators You are part of a development program using existing DOORS infrastructure, which is likely to stay in place as-is for a long time. A single-server solution native to the Jazz Team Server making it easier to deploy a multi-product solution. You need the more mature capabilities of DOORS 9, for example: Electronic signatures Baseline comparisons Round trip data import/export Requirements change management driven by a change management tool Simplest on-ramp from MS Word and Excel Built-in visual notations for collaborating around requirements Built-in capabilities for task management and planning A solution using a commercial off-the shelf (COTS) database You need significant product customizations, integrations, or automation based on DXL A web-based RM solution offering the most up-to-date web UI experience (with optional local rich client and interop with DOORS 9.5) Teams need high rigor and high levels of automation Teams seek lightweight RM … an alternative to DOORS 9 15 15

16 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 16

17 The integration problem
1717 The integration problem Over time, the costs of the current set of integrations goes up, as does the cost of making changes time Point-to-point integrations don’t scale Vendor-specific integrations lock you in Integrations consume more and more of the IT budget: 76% of software project delays are caused by integration activities End-user productivity suffers: Either stuck with the wrong tool, stuck doing manual integration, or both More limited ability to respond to change: Constrained by exhausted IT budget and lower productivity

18 Main characteristics of the ideal integration solution
Heterogeneous Able to integrate tools stemming from a variety of sources (commercial, open source, in-house developed, contractor-provided) Open Built with open standards to avoid vendor lock-in Flexible Able to retain use of existing tools while incrementally adopting new tools

19 The LIA architecture is based on linked lifecycle data principles
ALM Automation Monitoring PLM DevOps Open Services for Lifecycle Collaboration (OSLC) Lifecycle integration inspired by the web OSLC provides interfaces that allow lifecycle tools to link and trace data in a consistent manner

20 Requirements driven testing
Example of how LIA extends Rational CLM to leverage select 3rd-party tools Scott, Deb, Marco – Developers Plan the iteration from requirements Develop & deliver changes Bob – Product Owner Defines & links requirements and defect to influence the development plan Tanuj –Tester Validate requirements Submit defects Test the iteration Plan Requirements Find & Fix Defects Rational Team Concert Rational Requirements Composer HP Quality Center Requirements driven testing The Rational Lifecycle Integration Adapters allow customers to apply the CLM usage model in a heterogeneous environment

21 Introducing the Rational Lifecycle Integration Adapters
Standard Edition Tasktop Edition 21

22 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 22

23 10 Billion 61% 45% Mobile is mandatory devices by 2020
of CIOs put mobile as priority Key Message: Mobile is a top priority of the enterprise and IBM delivers a comprehensive end to end mobile solution for the enterprise Speaking Points: Today we are announcing our intent to acquire Worklight. This very strategic acquisition will allow us to accelerate and extend our capabilities for development, integration and management of rich mobile applications This acquisition adds to the extensive capabilities IBM already has in this space including several new and enhanced offerings that we’ll tak more about later – these include: Rational Collaborative Lifecycle Management: which allows customers to simplify the mobile app development across platforms IBM Endpoint Manager for Mobile Devices: which enables customers to deliver a unified endpoint management solution, with integrated mobile security capabilities Social collaboration software: for mobile access to enterprise social collaboration increased productivity with mobile apps 45%

24 Mobile application development includes more than just creating the source code
Production Troubleshooting Maintenance Release Defect Tracking Stakeholder input User Stories Feature identification Automated Environment Configuration Definitive Software Library Application Install Governance Model Architecture Mgmt UX Prototypes So let’s switch gears and talk a bit about Rational’s strategy in the mobile area. The first thing to realize is that mobile software developing includes more than just creating the source code. Like other kinds of software, there is a a whole lifecycle that surrounds the development and delivery of mobile software. There are some unique aspects to mobile software lifecycle. Shorter iterations of product lifecycles More direct involvements from users, different expectation Fast moving space: Keep up with emerging mobile devices and services Agile/Scrum emerged as preferred methodology Increased emphasis on user experience design More frequent user feedback Rapid prototyping, proof of concepts Dedicated UI design teams, increased collaboration between UX/Dev There is also Increased focus on broader mobile application life-cycle aspects Mobile road-map planning Business case development Platform selection/architecture planning Security essential Mobile-device management (MDM) tie-in System Verification Performance Testing Automated Functional Test Code Compile Debug Build & Package

25 IBM Strategy for Mobile Application Development
Start with a mobile runtime. Add best-of-breed code development tools that support the mobile runtime. Integrate with a development platform that covers the entire application lifecycle. Augment with mobile testing and mobile design capabilities. 25 25

26 IBM Mobile Development Lifecycle Solution V4.0
Enact a collaborative, multi-platform mobile development lifecycle A comprehensive mobile development solution combining: Enterprise-grade, standard-based mobile application platform, supporting native, hybrid and mobile web programming models Best-of-class collaborative mobile application development lifecycle capabilities Distributed team build and test integrations with the IBM Mobile Platform “Mobile device-cloud” service integration for on- device testing Support for Agile methodologies for dealing with fast-paced development for mobile Mobile development best practice Design Mobile Testing App Design and Construction SCM and Mobile Builds IBM Worklight Rational is introducing a mobile-specific offering in 4Q 2012. As mobile usage continues to grow WW, developing for mobile is becoming an increasingly important consideration for customers. We have reached a stage where customers are shifting away from “one-off” projects and looking for a strategic solution. Not only do they need a runtime infrastucture – a mobile platform to deploy and run mobile applications for multiple device ecosystems (e.g. iOS, Android) – they also need a development infrasturcture to support the development and delivery of these mobile applications. IBM Mobile Development Lifecycle Solution (IMDLS) is developed to address both of these challenges at the same time. It integrates two things: (1) an enterprise-grade, standard-based mobile application platform based on IBM Worklight technology, as well as (2) a best-of-class collaborative mobile application development platform based on Rational’s CLM capabilities. Using this solution, customers can reduce the cost and complexity in developing for multiple mobile ecosystems, especially when leveaging the hybrid and mobile web programming models supported by the solution. Advanced IDE for developing and unit testing mobile applications increase developer productivity. Distributed team builds enable continuous integration of mobile application code and enables cross-platform build that can reduce hardware acquisition costs (e.g. building an iOS application remotely from a request from a Windows machine). Test management, test plan optimization and “mobile device-cloud” service integrations improve testing productivy and quality, helping customers deliver “5-star” mobile applications. The solution also offers strong support for Agile methodologies, including Agile planning and work-item/back-log managmeent to help customers deal with the fast-paced, frequent release tempo of mobile application development. IBM Mobile Development Lifecycle Solution is one of the few comprehensive solutions currently in the market for mobile application development. Unlike the alternatives, which require customers to assemble the different parts of their mobile development infrastructure from different vendors or products, IMDLS is well-integrated with tested integrations to save customers the pain of putting together a solution themselves, especially when mobile development is a new challenge to a lot of them. IBM Rational Collaborative Lifecycle Management

27 Mobile application development models
File Name Here.ppt 2727 Mobile application development models Web Mobile Web Hybrid Mobile Native HTML, JavaScript, CSS Accessed from a mobile web browser No device-specific capabilities HTML, JavaScript, CSS Accessed from a mobile web browser; mobile- optimized UI Limited access to lower- level device capabilities HTML, JavaScript, CSS, with optional native code Installed and run like a native mobile app; mobile-optimized UI Access to lower-level device capabilities Native code Access to full set of lower-level device capabilities Mobile Browser Web Code <!DOCTYPE html PUBLIC <html> <! - - created <head><title>XYZ</title> </head> <body> </p> Mobile Browser Web Code <!DOCTYPE html PUBLIC <html> <! - - created <head><title>XYZ</title> </head> <body> </p> Native Shell Web Native Device APIs <!D OCT YPE html PUB LIC crea ted Native Appl. Device APIs There are a number of mobile app development approaches / styles that can be utilized to develop apps. You may find yourself using more than 1 style across your portfolio of internal and external apps. Web – user simply accesses your existing web sites from their mobile browser. UI is not mobile-optimized. Mobile web – apps accessed from a mobile browser (like a regular web app), but UIs have been mobile optimized (probably using a JavaScript framework like Dojo, jQuery Mobile, or Sencha Touch). Typically the URLs for these apps start with “m.” – for example “m.cnn.com”. Hybrid – installed and run like a native app, but the core of the app is written in HTML, JS, and CSS, enabling it to run across all major device platforms. This style supports writing native-specific extensions (in the native language), but if this logic is needed across all supported platforms, it will need to be written in multiple languages. Native– building the rich interfaces to mobile applications – embracing the ecosystems of the native vendors… The choices become daunting to consumers (both in understanding skills, resources required, best practices etc..) Richness of the UI increases as you move towards Native. Portability increases as you move away from Native Maintenance increase as you move towards Native, as you are typically needing to maintain separate code bases, tools, and infrastructures. Capabilities available in the various styles: Web and mobile web - almost all modern smartphone/tablet browsers support Geolocation (so, getting the user's location) and ability to store information needed by the app/site locally (but no access is provided to the phone's file storage area) Hybrid - same capabilities as web/mobile web, plus the following (primarily provided via PhoneGap): Accelerometer (captures device motion) - useful for apps where the way the phone is held/moved is important Camera - take a picture or access photos previously taken with the phone Capture - Provides access to the audio, image, and video capture capabilities of the device. Compass - detects the direction or heading that the device is pointed Contacts - create new contacts and access contacts stored on the phone File access - read/write files on the device storage Media - play and record audio files Network / connection info - provides info about the device's network connectivity (wifi, 3G, etc) Notifications - visual, audible, and tactile device notifications (alerts, sounds, vibrations) Native - everything above, plus access to all APIs and capabilities provided via native SDKs (primarily you'd go with Native if you wanted to use native UI widgets and controls vs. web widgets) Richness of Mobile Presentation / Services Portability (cross-device reuse) Maintenance Cost (TCO)

28 Solve mobile development challenges with IBM Mobile Development Lifecycle Solution V4.0
Developing for multiple mobile platforms Delivering high quality apps that engage users and meet business objectives Cross-platform mobile web and hybrid app development, test, and build Manage plans, tasks, code, builds from a common development workbench Agile planning Linkage and traceability across all phases of development UI sketching and storyboarding Test plan optimization and management and integration with mobile “Device-clouds” Portfolio management Integrating with enterprise systems Meeting accelerated time to market requirements Increased complexity and cost of developing, testing, and deploying mobile applications due to multiple platforms, devices, languages, APIs, and tools 4 major mobile platforms Fragmentation within some platforms complicates development and test and increases odds of bugs being found in the field One development team for each platform Not support every platform can mean not reaching all your users Based on our experience and many interactions with clients, partners, and analysts over the years we have defined 4 major challenge areas for IT shops developing and delivering enterprise mobile apps. (Note: Additional reference that highlights the same top challenge areas: ) 1) Developing for multiple mobile platforms Highly fragmented set of mobile devices, platforms and development models (Web, native, hybrid) Native programming models not portable across devices. Very large number of configurations of devices, platforms, carriers, etc. to test Lack of best practices guidance on how to deliver mobile applications Connecting the enterprise back-end services in a secure and scalable manner 2) Delivering apps that engaged users and meet business objectives Strong demand by Line of Business to extend brand to mobile Customers expect higher quality of user experience with mobile apps More direct involvement from users/stakeholders in design People want to use their personal devices for everything (BYOD) 3) Integrating with enterprise systems Enterprise mobile applications are typically multi-tiered and need to leverage existing enterprise back-end data and service In some cases, existing programs need to be refactored to be consumable from mobile applications Mobile application development lifecycle needs to bridge different teams which work on the front-end or the back-end separately 4) Meeting accelerated time to market requirements Faster time-to-market demands More iterative – frequent releases and updates for apps There are 2 key factors affecting project velocity: Gap 1: amongst Line of Business, Development and Test teams (ALM) Late rework due to misalignment of stakeholders Slow progress due to hand-off errors and delays between team roles Gap 2: between Development/Test and Operations Team (DevOps) Slow cycle/iteration times due to DevOps challenges Integrate Worklight Studio with the Rational IDEs to create a comprehensive IDE for all parts of the app (UI, mid tier, back-end) Extend enterprise assets as mobile-consumable services and connect via Worklight adapters Automate and manage continuous, end-to-end build and deployment process with RTC Deploy to private dev/test app Reduce cycle times by aligning dev and operations teams

29 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 29

30 Smarter products mean that complexity is rising
Product innovation enables companies to: Leapfrog their competition Grow demand Increase revenues Raise profits The next generation of innovative, smarter products requires more: Instrumentation Intelligence Interconnection This leads to increasing complexity In todays engineering environments, organizations are aspiring to innovate, and are building ever more complex products and systems to differentiate themselves. The associated engineering effort is generating more and more data with ever increasing complexity. Trends include: More software and systems-of-systems designs, where a larger portion of the product value/innovation is being delivered in software More design and development artifacts. More product variants More collaboration and co-design between HW and SW engineers More regulations, standards, and other aspects of compliance More participants in the supply chain (including the SW supply chain) More pressure to do more with less … improve quality and productivity More pressure to get to market faster 30 30

31 Productive and creative work Productive and creative work
The need for smarter products means complexity will keep rising The time, cost, and effort needed to manage complexity increases faster than the complexity itself Core Engineering Current Workload (trying to manage complexity) Core Engineering Desired Workload (Successfully managing complexity) % of Engineering Time, Cost, and Effort % of Engineering Time, Cost, and Effort Non-productive work Non-productive work Productive and creative work This need for smarter products means that complexity will continue to rise, and continue to hinder engineer productivity, and restrict innovative capacity And unfortunately, the effort required to manage complexity increases faster than the complexity itself. New levels of collaboration and co-design are required across multiple engineering disciplines and ever growing data sets. Engineers are spending more and more time being non-productive in simply coping with the overhead of complexity and less time being productive in doing what they are good at (and enjoy) What’s really needed is a way to enable engineering teams to focus more on core engineering work and spend less time and effort in dealing with complexity. We need to restore the balance and help engineering teams to work faster with higher quality by improving development processes and asking tools to do more. We need a next generation approach to both processes and the applications that support those processes. Productive and creative work Complexity Complexity Engineers spend more time trying to manage complexity and less time being productive Extra manual steps are needed resulting in increased errors Engineers spend more time being productive Automated steps deliver higher quality work with less errors 31

32 Introducing Rational Engineering Lifecycle Manager Extending the Rational solution for systems and software engineering Uses a Linked Data approach that enables Visibility – across many sources of data Organization – information in context Analysis - answer questions using that contextualized information Allows stakeholders to: manage growing complexity derive knowledge from the available data make timely and correct engineering and business decisions Rational Engineering Lifecycle Manager (RELM) Visualize Analyze Organize Cross domain views and navigation Query, reporting, and impact analysis Product, system and component definition Index of Linked Lifecycle Data RELM is built on top of this Lifecycle Query Engine, and extends the Rational solution for systems and software engineering, making available multi-dimensional views of your engineering data and thereby enabling your multi-disciplinary engineering teams to be more productive and make better decisions. RELM’s key innovation is its use of the Lifecycle Query Engine to index Linked Data from many engineering, which makes it possible to mine it in new ways. The fact that data is federated - rather than synchronized, or stored in the one monolithic database - means that it’s possible to implement this solution in finite time and with finite on-going maintenance effort – which is of course less true of the alternative approaches. RELM 1.0 indexes data from the tools of the Rational solution for SSE plus it has potential to index 3rd party and home-grown repositories, which requires development of lightweight connectors for each repository. RELM includes an application running on the Jazz Team Server, which provides access to this data through your web browser. This gives your team new ways to visualize, analyze and organize your engineering data so that you can get new value from it. Visualization capabilities allow you to set up custom views that are populated with near real-time data to provide new perspectives that help your team make decisions and perform tasks. For example, an automotive safety engineer wants a view of cross lifecycle data in the context of the structure of the ISO26262 standard or an aerospace engineer wants to see cross lifecycle data overlaid on a picture of the aircraft with data shown over the parts of the aircraft it relates to. Team-oriented analysis capabilities across disciplines help teams quickly find relevant information and identify dependencies that they may otherwise have missed which could have downstream impacts. For example, with RELM, searching for all engineering artifacts across multiple repositories containing the phrase ‘fuel pump’ becomes a simple, quick, and error free task. Or, perhaps a supplier can no longer supply a particular electronic component and you need to determine what impact there would be by switching that component for a similar component from another supplier. You need to understand the potential impact on components it interfaces with and software that controls it. This would typically mean asking multiple teams to perform impact analysis in different tools and assembling the data. With RELM you can find the component in your system design and generate an interactive impact analysis view that will show you all of the other systems and software design elements and requirements, tests and work items associated with the component. You can work with the view to filter out any artifacts that are not relevant, and parcel out relevant branches to the relevant engineering disciplines to analyze. RELM also offers potential for better reporting from this wealth of data. Answers to complex engineering questions can be visualized and displayed in the most appropriate way for the task at hand, and documents can be generated containing data from across the lifecycle to support audits, proving compliance, and delivery of specifications that form the basis of contractual agreements across the supply chain. The visualization and analysis capabilities of RELM are made all the more powerful by the ability to organize all of the indexed data to add essential context to it. You can organize all of your engineering artifacts according to the products, systems, subsystems, components and capabilities that you are building, and use this context in your visualization and analysis. For example it becomes easy to find all of the requirements, tests and design artifacts related to the head-up display unit of the Japanese variant of the 2014 model of a vehicle. (Common question will be: But I have a product/system structure already in DOORS/Rhapsody/RTC/etc. so why I would want to reflect it again in RELM? Answer: Each tool has it’s own way of expressing this structure and to take advantage of it you need to know the details of each tool. RELM provides a way for one knowledgeable person to extract it and make it accessible and useful to the whole team.) Open Lifecycle Integration 32 32 32

33 RELM Tightly integrates with Rational systems and software solutions and can be extended to your unique environment Rational Engineering Lifecycle Manager (RELM) Visualize Analyze Organize Cross domain views and navigation Query, reporting, and impact analysis Product, system and component definition Architecture and Design Rational Rhapsody with Design Management Planning, Defect, and Change Management Rational Team Concert Index of Linked Lifecycle Data 3rd-party Tools from other vendors RELM is tightly integrated with the Rational solution for systems and software engineering and allows visualization, analysis and organization across engineering data including: Requirements Management with Rational DOORS Quality Management with Rational Quality Manager Planning, Defect and Change Management with Rational Team Concert Architecture and Design with Rational Rhapsody Design Manager (and additional DM integrated data e.g. Simulink) Furthermore, the platform leverages open standards to enable integration of data from other engineering disciplines, allowing you to extend these capabilities and benefits over other tools in your engineering environments, for example electrical, electronic, mechanical etc.) Requirements Management Rational DOORS Custom Home-grown repositories Open Lifecycle Integration Quality Management Rational Quality Manager

34 Take the next step with RELM Conquer unprecedented complexity by making better use of your engineering data Increase your innovative capacity By making better use of your engineering data Improve efficiency and productivity By managing complexity of data and relationships Increase agility to reduce costs By understanding impact of change across engineering disciplines Enhance collaboration and visibility By understanding interaction and dependencies between development disciplines Leverage your existing tools and infrastructure with A federated, linked-data architecture based on open standards Tight integration with Rational systems and software solutions Extensibility to integrate data from other disciples (e.g. electrical, electronic, mechanical) RELM is the latest addition to the Rational SSE offering the potential to make your teams more productive and effective. What is your next step? … Automate another discipline supported by Rational SSE? … Consider RELM? … Consider adding another discipline at the same time you add RELM? Let your business priorities and potential ROI drive your decision When you are ready to take the next step with RELM … engage IBM and our Business Partners to explore a solution and deployment plan for your teams Consider which engineering data sources your teams can better exploit Could involve Rational tools, home-grown databases, mechanical, electrical 34 34

35 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 35

36 What is driving the need for a change?
Increasing Cost of Quality Increasing Development Complexity Balancing Quality and Speed Heterogeneous Environments Public Cloud Private Cloud Data Warehouse Mainframe Enterprise Service Bus Directory Identity File systems Collaboration Web/ Internet Routing Service Third-party Services Portals Content Providers EJB Shared Services Archives Business Partners Messaging Services Other costs Testing costs Traditional Testing Three primary factors have been developing over the past decade - : (Increasing cost of quality) Organizations have been mostly addressing Quality challenges through labor arbitrage. With the rise in global labor wages, outsourcing and off shoring testing strategies as a way to drive down the cost of software development has reached its practical end of life and is no longer sufficient. Putting it simply, a 13% increase in wages in India this year roughly translated to the same kind of growth in spending for QA for many organizations. (Increasing development complexity) Today’s applications and manufactured products are increasingly complex. They comprise an unprecedented level of connectivity and dependency between systems, processes and infrastructure. Whether deployed in traditional software development or cloud environments, businesses are able to create products, systems and services that are increasingly instrumented, interconnected, and intelligent. While better development tools & middleware is fueling this innovation and growth, it also creates unprecedented challenges to test these composite applications, while keeping pace with development teams, and requires significant costs to stand up test environments: The typical cost for a test lab at a F500 is now typically ranging from $5 to $30M. And not only the cost of test labs has been increasing but their number is also increasing dramatically. In the last 5 years one of large FSS customer saw their number of test labs increase 6 fold. 3. (Balancing quality and speed) Historically, businesses have had to balance their ability to deliver quality against speed/time to market. Over the past several years, software development teams have been finding new and innovative ways to drive down cost while increasing their flexibility and productivity through agile development. Test teams can no longer keep up with development’s increased agility and the velocity at which they deliver working software code to be tested. Traditional testing is showing its limits 13% The forecasted increase in wages for India IT workforce in 2011a $5-30 million The typical investment to build a single test lab for a Fortune 500 company. Most have dozens  b… 30-50% The average amount of time testing teams spend on setting up test environments, instead of testing  c * Source: 36

37 Why consider yet another testing tool?
Most testing software today will help you uncover issues at a surface level … Manual Testing, Functional Testing, Performance Testing – can help identify issues…. However – there’s much more … Think of the current software environment as an iceberg … When everything is working, that’s enough. But what happens when a test fails? How do you know what caused the failure? That’s where Rational Integration Tester adds value. With RIT, you can see what’s happening under the surface and when there’s a problem, you can quickly identify it rather than just throwing it back over the fence with a simple “FAILED” stamp. In reality, the tests that you run are probably touching many other pieces of your environment – other internal apps, perhaps 3rd party applications or environments, a database, and any of those parts will impact the result of your tests…

38 Rational Test Workbench
Rational Integration Tester (Green Hat Tester) is a desktop solution that enables testers/developers to: Capture and model virtual services Test services and applications long before their user interfaces becomes available and do integration testing (SOA, BPM) Rational Functional Tester and Performance Tester are desktop solutions that enable users to create tests without having to know how to write code reuse test scripts to drive testing Can be used in combination with Virtual Services Rational Test Virtualization Server is a server solution that: Provides a central environment to virtualize heterogeneous hardware, software and services to provide 24x7 testing capabilities Reduces infrastructure costs of traditional testing environments Virtual Services can be built from the interface definition of the system for a wide variety of protocols, including HTTP, web services, SOA, JMS, TIBCO, IBM WebSphere MQ, Oracle, etc. Developers Testers Rational Integration Tester Rational Performance Tester App Under Test Rational Test Virtualization Server What is Green Hat? The Green Hat solutions focus on a key problem most organizations face: the time, and resources required to set up and manage test environments. Traditionally, people have been running around installing hardware, setting up application servers, database servers, installing application software, configuring all of that. Not only this is very capital intensive problem, but as environments have become more and more complex, this is also a very error prone process that typically involves a lot of scrap and rework. Green Hat solutions enable organizations to address that problem by Virtualizing complete stacks of software, hardware, and services, enabling developers and testers to stand up test environments in a matter of minutes vs weeks, to do that whenever they want, and in effect, start their testing much earlier than what has been traditionally possible. The net result: Green Hat solutions really can help organizations transform the way they deal with software quality by: 1. better managing their costs: Reduce hardware, software and labor costs associated maintaining complex test environments, 2. improve test cycle time: By reducing wasted time spent waiting on the availability of and setting up test environments), and 3. better manage risk in delivering software: By doing testing earlier, organization can avoid late stage integration issues Databases Mainframe applications Third-party Services Packaged apps, messaging services, etc. Rational Test Virtualization Server 38

39 Incremental Testing As components are built:
This enables us to test downstream dependencies as they are built. Initial Stage: A single component can be tested in the context of an end to end environment, supplied by a set of virtual components. As components are built: The same end to end tests can be run, replacing virtualized components with actual components. When the system is complete: End to end testing can be carried out with fewer surprises and lower risk To illustrate this, we’ll look at how we incrementally test our system, integrating different parts as we go. We will start with the testing of one service – which is the e2e environment (as it is the only element that has been built yet) We have the one service but there is a plan to integrate with other components that are either not built yet or are unavailable to test against. We are able to send messages back and forth to this component with GH Tester, but we need to test against downstream dependencies at this stage, so we virtualize a dependency and validate the responses. In fact we can virtualize as many downstream dependencies as we like. All of this can take place within a continuous integration environment. Actual Component Virtual Component

40 Service virtualization delivers realistic simulated development and test environments to minimize constraints Key Features and Benefits Virtualized services can be used for testing when real services are unavailable Virtual environments can be dynamically provisioned, allowing for high capacity, scalability testing scenarios Reduces infrastructure requirements – virtualized services run in a reduced footprint Allows testing of integration and complex scenarios earlier in the test cycle Drives automation of test cases The IBM Cloud can be leveraged to minimize infrastructure set-up time and provide scalable, on-demand infrastructure Service Virtualization provides business value: Reduces test cycle time (Up to 40%) Reduces defects (Up to 30%) Reduces infrastructure required to enable parallel testing

41 Agenda 1 2 3 4 5 6 7 CLM 4.0.x Highlights DOORS Next Generation
Lifecycle Integration Adapters 4 Mobile Development Lifecycle Solution 5 Real Engineering Lifecycle Manager 6 Rational Test Workbench 7 Dev-Ops - SmartCloud Continuous Delivery 41

42 Organizations have significant delivery challenges
Show them there is clear market opportunity, based on customer deals we have seen, pain points and growth in this space (based on competition, analyst info), etc. In this economic climate, customers care about Hard ROI and tell them that this clearly has ROI. Show them.

43 Addressing delivery challenges
Customers Desire for fast and continuous innovation Line of Business Requirements Dev & Test Teams Code & Tests Operations Team Business Services 1st Gap 2nd Gap Addressed by... Addressed by... Dev Ops Agile Dev

44 Addressing only the first gap
Agile Dev Functional Testing Operator Acceptance Testing Production Setup (weeks) Install Test and Ops teams have increased pressures to keep up with increased loads but continue to use waterfall approaches and traditional tools. CI builds are piling up

45 DevOps is… A set of principles and values that facilitate collaboration across disciplines to… Enable rapid evolution of deployed business services Reduce risk, decrease cost, and improve quality across the portfolio People Process Information

46 DevOps Principles and Values
Develop and test against a production-like system Deploy frequently Continuously validate operational quality characteristics People Process Information

47 Infrastructure Developer Rogue Troubleshooting “Hero”
Automate Everything Infrastructure configuration App Developer Application Install & Config Automation X Ruth does automate Old way: Procure, install in data center, config the software stack, install the application, run manual tests. New way: Pull a Lever What makes this possible? Anything which happens to these artifacts should be automated, such as builds, deployment, and test, including (thanks to cloud) creating and configuring the [virtual] machines. Role-specific user interfaces provide access to these automated tasks as appropriate. This makes sure that everything is repeatable. Functional and System Tests Rogue Troubleshooting “Hero” Tester Manual Changes Repeatability Reliability Consistency 47

48 IBM Strategy - integrating previously siloed tools and processes
Accelerate delivery of code changes via automated, repeatable execution of build processes Automatic deployment of applications, middleware and configurations to environments Continuous Integration C I Continuous Deployment C D IBM DevOps Continuous Delivery with feedback Development Entry Points Operations Entry Points Private & Hybrid Clouds Cloud Enablement Technologies Enables private/hybrid cloud service delivery and management Continuous Monitoring C M Continuous Testing C T Automatically test development changes against production-like environments Continuous understanding off deployed application health against production 48 48 48

49 IBM SmartCloud Continuous Delivery 2.0 – Out-of-the-box
Collaborate Define Execute Report Development and Operations define and share patterns Tasks for end-to-end delivery pipeline to integrate workflow (build, deploy, test) Deploy and test changes automatically on production-like environments in the cloud Instant feedback on code changes, build integration, test case results Continuous Integration Continuous Deployment Continuous Testing Provision infrastructure IBM SmartCloud Provisioning Configure Environment - Chef Solo Notes: The following Specific products and versions are provided out of the box IBM SmartCloud Continuous Delivery Client IBM SmartCloud Continuous Delivery Server RTC 4.0 RAM 7.5.1 SCP 2.1 DB2 Express 9.7 Cucumber and jUnit are shipped with this release to allow customers to get started easily and gain value out of samples that are provided Automated Testing Cucumber jUnit Automated Build Process Jazz Build Engine Deployment Library - Reuse & govern software delivery assets in the pipeline – IBM Rational Asset Manager Jazz Build Engine & Dashboards - IBM Rational Team Concert Workgroup for Developer Starter Pack

50 50


Download ppt "John Lanuti IBM Rational IT Specialist"

Similar presentations


Ads by Google