1. © 2013 IBM Corporation IBM Rational Solution for Systems and Software Engineering SSE Integrations

2. © 2013 IBM Corporation Product and System Innovation 2 Introduction  The IBM Rational Solution for Systems and Software Engineering Leverages Jazz and OSLC as an open integration platform to: –Improve collaboration and decision making –Improve quality and customer satisfaction –Simplify the implementation of consistent and appropriate workflow processes –Effectively manage the impact and effort of changing requirements –Facilitate compliance and auditing –Reduce time to market –Reduce development costs  These slides provide a summary of the OSLC based integrations available in the IBM Rational Solution for Systems and Software Engineering  Information and resources for other SSE integrations are also provided

3. © 2013 IBM Corporation Product and System Innovation 3 OSLC and Linked Data  OSLC integrations access tool artifacts by means of linked data  As defined by W3C, linked data follows these guidelines: –Use URIs as names for things –Use HTTP URIs so that people can look up those names –When someone looks up a URI, provide useful information, using the standards (RDF SPARQL) –Include links to other URIs, so that they can discover more things  In contrast to integrations that rely on mapping data types and synchronizing disparate databases, the use of linked data makes it possible to access data directly from another product, enabling meaningful relationships and traceability across data linkages  Many Rational tools are OSLC enabled, so you can readily build your own integrations to Rational tools, using OSLC specifications, which are open, scalable, and extensible. Rational- developed OSLC-based integrations share common interface elements and administrative tasks

4. © 2013 IBM Corporation Product and System Innovation 4 OSLC Service Consumers and Providers  OSLC service providers provide an implementation of OSLC services  A service provider offers consumers information for displaying the link to a resource, and rich previews of the resource  OSLC consumers can retrieve data in the form of resources from tools that are enabled as OSLC providers  Tools can be enabled as OSLC consumers or providers, or both  In OSLC, each artifact in the lifecycle is represented by an HTTP resource that has a URI as its name and can be manipulated with HTTP methods, such as GET, PUT, or POST –Every artifact or resource has an RDF representation that consists of a subject, a predicate, and an object –For example, if you were to link from a requirement to a test case, the RDF representation would have the requirement as its subject, the type of relationship or link type as its predicate and the test case as its object, each identified by a URI

5. © 2013 IBM Corporation Product and System Innovation 5 OSLC Integrations  Integrations built with OSLC rely on the OSLC Core specification and a domain specification. –The core specification describes primary integration techniques, use of HTTP and RDF (Resource Description Framework), and identifies the common features that every OSLC service should support –Domain specifications are tailored to a particular ALM area, such as change management, test management, requirements management, or architecture management. Domain specifications comply with the core specification –For example, the change management specification defines a common set of resources, formats, and RESTful services for use in change management tools (consumers) and use by provider tools –Specifications describe a set of services and formats for interacting with other lifecycle tools and do not attempt to standardize the behavior of a tool or class of tools  Eclipse Lyo is an SDK to help the Eclipse community to adopt OSLC (Open Services for Lifecycle Collaboration) specifications and build OSLC-compliant tools. It includes a software development toolkit focused on Java, a test suite to help ensure your integration is OSLC compliant, a reference application with working samples and a simple server you can use in testing. For more information about Eclipse Lyo, see http://www.eclipse.org/lyohttp://www.eclipse.org/lyo

6. © 2013 IBM Corporation Product and System Innovation 6 Friends  For products on the Jazz platform to interact with each other, each server must have the other servers on its list of friends  The link between two servers is called a friend link. –Friend links between servers indicate that any requests coming from these servers can be trusted –By configuring friend links, the server can communicate with friend servers that support OAuth authentication

7. © 2013 IBM Corporation Product and System Innovation 7 Associations  After you connect two servers by using friend links, you must associate two projects on these servers before you can create resource links between them  Association of project areas enables team members to create links from artifacts, such as test cases, requirements, design resources, and work items, in one project area to artifacts in another project area –When adding associated project areas to the current project, the selected application provides services, such as requirements, change requests, defects, or quality tasks, for the current project –The current project also uses its own services, such as requirements management (when working in an RM project), to support activities in the associated project area –Based on the selected association and artifact container, you will be able to use specific link types when creating links between artifacts in the associated project areas  Some associations are automatically created when multiple applications are on the same Jazz Team Server

8. © 2013 IBM Corporation Product and System Innovation 8 Associations

9. © 2013 IBM Corporation Product and System Innovation 9 Associations and Link Types  Associations are represented as two unidirectional Project Links between the source and the target project area  A link type is the kind of link that exists between two artifacts such as a model element and a requirement  The link type explains the semantics of the relationship and is directional Example RM project association with CM project

10. © 2013 IBM Corporation Product and System Innovation 10 Linking  Uni-Directional Linking –Basic OSLC links are uni-directional links, just like links on the internet –While this is good, it makes it difficult to keep track of changes in address as well as performing functions such as impact analysis  Bi-Directional linking –When an outgoing link is created from a source to a target, a backlink can be created from the target incoming to the source –A better approach is to use link discovery… Based on project associations and link type, an application dynamically queries associated projects to provide a complete set of outgoing and incoming links for an artifact

11. © 2013 IBM Corporation Product and System Innovation 11 OSLC Integration vs. Linking  Linking refers to basic uni-directional linking within and between applications  In contrast, an integration results from automation that creates and manages bi-directional linking across applications when a new (uni-directional) outgoing link is created –Integrations are typically cross-domain, but in some cases also apply within a domain  The following slides include tables that summarize the integrations available with the SSE applications –There are two exceptions where linking (and not integration) is included in the tables Linking from DOORS RM artifacts to DM artifacts – these are one way links from DM to RM Linking from DM artifacts to QM artifacts – these are one way links from DM to QM  Note: most of the OSLC linking resulting from compliance with the OSLC standards is not included here, but is available within the SSE applications and is documented in the OSLC Domain StandardsOSLC Domain Standards –The resources defined within each domain standard specify the artifacts that can be linked –The resource relationship properties defined for each resource specify the link types that are supported

12. © 2013 IBM Corporation Product and System Innovation 12 Rational Team Concert Integrations  Rational Team Concert consumes services that these OSLC domains provide: –Change Management V1, V2 –Quality Management V1, V2 –Requirements Management V1, V2 –Design Management V2 DomainLink relationships in Rational Team ConcertLink relationships in external applications Change Management (CM) CM artifacts can be linked to external CM artifacts using the following link types: Affected by defect Related change request Affected by defect Related change request An external CM artifact can be linked to a CM artifact using the following link type: Affects plan item Affects plan item Quality Management (QM) CM artifacts can be linked to QM artifacts using the following link types: Affects test result Blocks test execution record Related test case Related test execution record Related test script Related test plan Tested by test case Affects test result Blocks test execution record Related test case Related test execution record Related test script Related test plan Tested by test case A QM artifact can be linked to a CM artifact using the following link types: Affected by change request Blocked by change request Related change request Tests change request Affected by change request Blocked by change request Related change request Tests change request Requirements Management (RM) CM artifacts can be linked to RM artifacts using the following link types: Affects requirement Implements requirement Tracks requirement Affects requirement Implements requirement Tracks requirement An RM artifact can be linked to a CM artifact using the following link types: Affected by Implemented by Affected by Implemented by Design Management (DM) CM artifacts can be linked to a DM artifacts using the following link type: Elaborated by Architecture Element Elaborated by Architecture Element A DM artifact can be linked to a CM artifact using the following link type: Elaborates Elaborates  Rational Team Concert provides services that these OSLC domains consume: –Change Management V1, V2

13. © 2013 IBM Corporation Product and System Innovation 13 Rational DOORS Next Generation Integrations  Rational DOORS Next Generation consumes services that these OSLC domains provide: –Change Management V1, V2 –Quality Management V1, V2 –Requirements Management V1, V2 –Design Management V2 DomainLink relationships in Rational DOORS Next Generation Link relationships in external applications Change Management (CM) RM artifacts can be linked to CM artifacts using the following link types: Implemented by Affected by (V2) Tracked by (V2) Implemented by Affected by Tracked by A CM artifact can be linked to an RM artifact using the following link types: Implements Affects (V2) Tracks (V2) Implements Affects Tracks Quality Management (QM) RM artifacts can be linked to QM artifacts using the following link type: Validated by Validated by A QM artifact can be linked to an RM artifact using the following link types: Validates (a requirement) Validates (V2) (a requirement collection) Validates Requirements Management (RM) RM artifacts can be linked to external RM artifacts using the following link types: Elaborated by Specified by (V2) References Elaborated by Specified by References An external RM artifact can be linked to an RM artifact using the following link types: Elaborates Specifies (V2) Referenced by Elaborates Specifies Referenced by Design Management (DM) RM artifacts can be linked to DM artifacts using the following link type: Derives Derives A DM artifact can be linked to an RM artifact using the following link type: Derives from Derives from  Rational DOORS Next Generation provides services that these OSLC domains consume: –Requirements Management V1, V2 –Design Management V2

14. © 2013 IBM Corporation Product and System Innovation 14 Rational DOORS Integrations  Rational DOORS consumes services that these OSLC domains provide: –Change Management V1, V2 –Quality Management V2 –Requirements Management V1, V2 –Design Management V2  Rational DOORS provides services that these OSLC domains consume: –Requirements Management V1, V2 DomainLink relationships in Rational DOORSLink relationships in external applications Change Management (CM) RM artifacts can be linked to CM artifacts using the following link types: Implemented by Affected by (V2) Tracked by (V2) Implemented by Affected by Tracked by A CM artifact can be linked to an RM artifact using the following link types: Implements Affects (V2) Tracks (V2) Implements Affects Tracks Quality Management (QM) RM artifacts can be linked to QM artifacts using the following link type: Validated by Validated by A QM artifact can be linked to an RM artifact using the following link types: Validates (a requirement) Validates (V2) (a module) Validates Requirements Management (RM) RM artifacts can be linked to external RM artifacts using the following link types: Elaborated by Specified by (V2) Elaborated by Specified by An external RM artifact can be linked to a RM artifact using the following link types: Elaborates Specifies (V2) Elaborates Specifies Design Management (DM) None. Rational DOORS RM artifacts do not have outgoing links to DM artifacts. A DM artifact can be linked to an RM artifact using the following link types: Refines (V2) Satisfies (V2) Trace (V2) Refines Satisfies Trace

15. © 2013 IBM Corporation Product and System Innovation 15 Rational Quality Manager Integrations  Rational Quality Manager consumes services that these OSLC domains provide: –Change Management V1, V2 –Requirements Management V1, V2 DomainLink relationships in Rational Quality Manager Link relationships in external applications Change Management (CM) QM artifacts can be linked to CM artifacts using the following link types: Affected by Blocked by Related to Tests Affected by Blocked by Related to Tests A CM artifact can be linked to a QM artifact using the following link types: Affects Blocks Related to (a test case) Related to (a test case execution record) Related to (a test plan) Related to (a test script) Tested by Affects Blocks Related to (a test case) Related to (a test case execution record) Related to (a test plan) Related to (a test script) Tested by Requirements Management (RM) QM artifacts can be linked to external RM artifacts using the following link types: Validates (a requirement) Validates (a requirement collection) Validates (a requirement) Validates (a requirement collection) An RM artifact can be linked to a QM artifact using the following link type: Validated by Validated by Design Management (DM) None. Rational Quality Manager QM artifacts do not have outgoing links to DM artifacts. A DM artifact can be linked to a QM artifact using the following link type: Validated by Validated by  Rational Quality Manager provides services that these OSLC domains consume: –Change Management V1, V2 –Quality Management V1, V2 –Requirements Management V1, V2

16. © 2013 IBM Corporation Product and System Innovation 16 Rational Rhapsody Integrations  Rational Rhapsody consumes services that these OSLC domains provide: –Change Management V1, V2 –Quality Management V1, V2 –Requirements Management V1, V2 –Design Management V2  Rational Rhapsody provides services that these OSLC domains consume: –Change Management V2 –Quality Management V2 –Requirements Management V2 –Design Management V2 DomainLink relationships in Rational RhapsodyLink relationships in external applications Change Management (CM) DM artifacts can be linked to CM artifacts using the following link type: Elaborates Elaborates A CM artifact can be linked to a DM artifact using the following link type: Elaborated by Architecture Element Elaborated by Architecture Element Quality Management (QM) DM artifacts can be linked to QM artifacts using the following link type: Validated by Validated by None. Rational Quality Manager QM artifacts do not have outgoing links to DM artifacts. Requirements Management (RM) DM artifacts can be linked to RM artifacts using the following link types: Refines (V2) DOORS only Satisfies (V2) DOORS only Trace (V2) DOORS onlyRefines Satisfies Trace Derives fromDerives from All except DOORS An RM artifact can be linked to a DM artifact using the following link type: Derives All except DOORSDerives Design Management (DM) DM artifacts can be linked to external DM artifacts using user-defined link types An external DM artifact can be linked to a DM artifact using user-defined link types

17. © 2013 IBM Corporation Product and System Innovation 17 Rational Rhapsody Integrations  Rational Rhapsody Design Manager uses an extensible set of OSLC Link Types to link resources within DM as well as integrate with external applications

18. © 2013 IBM Corporation Product and System Innovation 18 Rational Engineering Lifecycle Manager Integrations  Rational Engineering Lifecycle Manager integrates with other applications using Tracked Resource Sets (TRS) that get published to, and indexed by, the RELM Lifecycle Query Engine (LQE) Index (Lifecycle Query Engine) Lifecycle Tool Architecture Management Lifecycle Tool Tool B

19. © 2013 IBM Corporation Product and System Innovation 19 Rational Engineering Lifecycle Manager Integrations  RELM products can be linked to any artifact within the query index  RELM products can also be linked to any artifact addressable with an HTTP URI, including RELM views

20. © 2013 IBM Corporation Product and System Innovation 20 Additional SSE Integrations  Big Lever GEARS  HP Quality Center  Mathworks Simulink  Mentor Graphics Capital  Mentor Graphics Volcano  Method Park Stages  National Instruments TestStand  PTC Windchill  Pure systems pure::variants  Rational Asset Manager  Rational Build Forge  Rational ClearCase  Rational Focal Point  Rational Insight  Rational System Architect  Spirent iTest  Wind River Test Management This is a partial list of available integrations

21. © 2013 IBM Corporation Product and System Innovation 21 Additional Resources  Overview of CLM Integrations in the Rational Solution for Collaborative Lifecycle Management Information Center Overview of CLM Integrations  Extending Rational DOORS by Using OSLC Services in the Rational DOORS Information Center Extending Rational DOORS by Using OSLC Services  Rhapsody Information Center Rhapsody Information Center  Design Manager Information Center Design Manager Information Center  Jazz.net Design Management pageDesign Management  Rational Engineering Lifecycle Manager Information Center Rational Engineering Lifecycle Manager Information Center  Jazz.net Rational Engineering Lifecycle Manager wikiRational Engineering Lifecycle Manager  Jazz.net Integrations pageIntegrations  OSLC and Linked Data Overview Video OSLC and Linked Data Overview Video  OSLC Domain Standards OSLC Domain Standards  OSLC Vocabulary Index OSLC Vocabulary Index  OSLC list of Applications that Implement OSLC SpecificationsApplications that Implement OSLC Specifications  SSE Information Center SSE Information Center

22. © 2013 IBM Corporation Product and System Innovation 22 © Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.