1. Rational Team Concert Introduction
Sanjay Chandru
Manager, EM Technology Ecosystem Team

2. Agenda Customer’s Challenges Overview of Jazz, and RTC
RTC for System i and z
Component overview
Source Control
SCM Interoperability
Build
Process
Other Components/Features
Demo
Questions/Feedback

3. Collaboration Challenges with Enterprise teams
Why are some teams not following our agreed upon process?
How can see the status of all of my teams in one place?
How can we verify that all of the components of an enterprise application have been built properly?
How are our fellow teams in other platforms organized? Who is working on what?
Our enterprise development teams working on different platforms are struggling to communicate. How can we collaborate in the context of our work
Why and when was this code change made?
Low Complexity High Complexity
We need to deploy an enterprise application to our System z, System i, and Unix servers. How can we coordinate that deployment?
Distributed software development teams across the hall or spread around the world face similar challenges
The build was broken by another team, how can our team repair w/o waiting

4. Enterprise Pressures and Opportunities Addressing the needs of i and z customers
System i/z organizations need to upgrade their existing lifecycle management solutions
to address regulatory compliance issues, adopt better IT Governance approaches, reduce the costs of maintaining infrastructure
to exploit modernization strategies including new languages, tools, and paradigms
to bridge the process islands across platforms and technologies to effective develop and deploy enterprise applications

5. A sample lifecycle: How do we collaborate?
Request
Enhancement
Approve
UI Design
Test changes
to ensure they
meet the
requirement
Approve
changes
End User
Create Iteration
plan and schedule
to coordinate
delivery
Add Work to iteration Plan and assign to Developers
Approve
Technical
Design
Check progress
on iteration
plan
Approve
Upgrade to
Production
system
Dev Mgr
Design changes to
components
Request
Design
Approval
Deliver
Code changes
Integration
Testing
COBOL/RPG Developer
Design changes to
component
Request
Design
Approval
Deliver
Code Changes
Integration
Testing
Java Developer
Deploy
Build to z or i QA System
Schedule
And Deploy
Enhancements
To Production
System z or i Admin
Deploy
Build to Linux, Unix, Windows
QA System
Schedule
And Deploy
Enhancements
To Production
System
Linux/Unix/Windows Sys Admin

6. What if your tools know…
… about your teams
… about your artifacts
… who is responsible for what
… rules under which circumstances code can be delivered
Code quality, traceability, test runs, intellectual property
… how to bootstrap a project
… how to help new team members get started
… your favorite work item types and their state transitions
… when the build runs and what to do if it breaks

7. Innovative Software Engineering
What is Jazz?
Innovation
Rational Products
A major investment by IBM to create a scalable, extensible team collaboration platform for seamlessly integrating tasks across the software lifecycle
A commercial project led by the IBM team that brought you the Eclipse Platform. Rational Team Concert will be the first product built on Jazz and feature tooling the agile practices.
Innovative Software Engineering
Community
Vision
A vision for the value and experience that future Rational products can bring to software and systems delivery teams
Jazz.net – Jazz project venue for open commercial development of Jazz platform and Jazz-based products and an extension of the world wide Eclipse ecosystem

8. The Jazz Platform: An open, extensible architecture Supporting a broad range of desktop clients
Eclipse Clients
Web Clients
MS.net Clients (future)
Rational Desktop Clients
Jazz Client Extensions
Web 2.0
Visual Studio
Rational Software Architect
Eclipse Platform
Rational Systems Developer
Rational Business Developer
Rational Developer for z
Eclipse Platform
Rational Team Concert
Jazz Team Server
Tooling Extensions
Tooling Adapters

9. Jazz as Product Integration Platform
Source Configuration Management
Work Items
Build
Process
Enactment
Security and Access
Project and
Team Structure
Search
Jazz Team Server
Event Notification
Conversation
Storage
Items and relationships
Event history, Item history trends
Jazz Repository
Defects
Requirements
Use-cases, …..
….,Builds
Source code, Test-cases
Test results
Rational ClearCase
Rational ClearQuest
Rational Build Forge

10. An evolution for new and existing customers
The Evolution of the IBM Rational Software Delivery Platform
Existing Offerings
New Offerings
Rational RequisitePro
Rational Team Concert Standard
SCM
Work Items
Build
Reporting
Rational RequisitePro
Future Products
Quality Management
Rational ClearQuest
Rational ClearQuest
Built on the Jazz Technology Platform
Rational Build Forge
Rational Build Forge
Evolution to Jazz Technology Platform
ClearCase
ClearQuest
Build Forge
ClearCase
ClearQuest
Build Forge
Rational Team Concert Enterprise
Rational ClearCase
Rational RequisitePro
Other...
ReqPro Composer
Rational Quality Manager
Rational ClearCase
Other Rational & Non-Rational Offerings
- - -
FUTURE IBM RATIONAL SOFTWARE DELIVERY PLATFORM 10

11. Rational Team Concert for i Capabilities
Build
Local or Remote Build Servers including on IBM i
Native builds of IBM i projects
Work Item and Change Set Traceability
Integration with Build Forge
Team and Private Builds
Ant and Command line builds
SCM
SCM/CRM for IBM i projects (RPG)
Integrated Stream Management
Component Level Baselines
Server-based Sandboxes
Subversion/ClearCase Connectors and coexistence
Work Items
Work item references to host files and host SCM managed artifacts
Defects, Enhancements and Conversations, incl. approvals
Query Editor, Shared Work Item queries
ClearQuest Connector
Jazz Team Server
Single Structure for Project Related Artifacts
In-context Collaboration shows Team Members and Status of their Work
Real-time Project Status Window, Including Customizable Project Dashboard and Real-time Reporting and Queries
World-class Team On-boarding / Offboarding including team membership, sub-teams and project inheritance
Role-based operational control for flexible definition of process and capabilities
Server can be hosted on IBM i using WASi/LWI/DB2i
Process Enactment and Enforcement including sample processes for IBM i development
Team Advisor for defining / refining “rules” and enabling continuous improvement.
Integrated Iteration Planning and Execution
RTCi Client - integrated with RDi client

12. RTCz Client - integrated with RDz client
Rational Team Concert
SCM
SCM/CRM for zOS projects (COBOL, PLI)
Host SCM interoperability
Integrated Stream Management
Component Level Baselines
Server-based Sandboxes
Subversion/Clearcase Connectors and coexistence
Work Items
Work item references to host files and host SCM managed artifacts
Defects, Enhancements and Conversations, incl. approvals
Query Editor, Shared Work Item queries
ClearQuest Connector
Build
Local or Remote Build Servers including on zOS
Native builds of zOS projects
Work Item and Change Set Traceability
Integration with Build Forge
Team and Private Builds
Ant and Command line builds
Jazz Team Server
In-context Collaboration shows Team Members and Status of their Work
Real-time Project Status Window, Including Customizable Project Dashboard and Real-time Reporting and Queries
World-class Team On-boarding / Offboarding including team membership, sub-teams and project inheritance
Role-based operational control for flexible definition of process and capabilities
Server can be hosted on zOS using WASz/DB2z
Team Advisor for defining / refining “rules” and enabling continuous improvement. Including basic advisors for COBOL/PLI artifacts
Process Enactment and Enforcement incl. sample processes for z platform development
Integrated Iteration Planning and Execution
Single Structure for Project Related Artifacts

13. Basic Jazz SCM Anatomy Stream Repository Workspace Local Workspace
Your changes
Other’s changes
Streams are for sharing resources
A repository workspace is your personal space in the repository
Local workspaces are where you edit resources
Changes flow back and forth
Subsequent charts will cover each of these
NOTE: Speak in general terms with regard to change flow when animating this slide. The technical details and discussions of the actions are coming up.
NOTE: We will be mapping the RTC terms to CC terms in the next module if the question comes up on this slide or any of the following slides.
Note that blue is server and green is client
Also note the icons
These conventions will be used throughout the SCM charts
There is a 6 click animation on this slide.
1st – shows the stream object and bullet
2nd – shows the repository workspace object and bullet
A repository workspaces is your personal space on the server but they are searchable by others and others can get changes from them.
3rd – shows the Local workspace object and bullet
Examples of local workspaces include Eclipse workspaces, Visual Studio workspaces and build machine file areas
4th – shows the changes bullet and runs the outgoing changes animation (if you hit page up after it runs and then click again, it will rerun)
5th –runs the incoming changes animation (if you hit page up after it runs and then click again, it will rerun)
6th – shows the final bullet and the icon in the upper right. This icon will be used on other slides to remind us of this relationship.

14. Repository Workspace Repository Workspace Component Local Workspace
Repository Workspaces
Partitioned into components
Jazz understands the structure of your components
Jazz directly supports component based development
Jazz SCM goes beyond most other system’s simple file and folder awareness
Jazz understands more of your components’ structure as we will see next when we look at what a component looks like…

15. Components Repository Workspace Local Workspace Component
Eclipse Project
Folder
File
Local Workspace
Eclipse Project
Folder
File
This example shows Eclipse projects since that is what we will use in the exercises. However, Jazz SCM is not Eclipse project specific. Jazz SCM content can map to other types of local workspaces such as a Visual Studio workspace or a build area on a build machine.
In this example:
There can be any number of components in a repository workspace and any number of Eclipse projects in a component.
Note how an Eclipse project can be contained within a folder structure in a component.
For each component and its Eclipse projects the structure continues as briefly shown here.

16. Components (cont) Local Workspace Change set Change set
Repository Workspace
Local Workspace
Components
Repository Workspace
Change set
Components
Change set
Components Track Changes
Configuration of resources builds from the change set flow
Each change set builds on what came before
Component’s Change History
A time-ordered sequence of change sets
Describes how the component’s content was built from nothing
Note that each user has their own repository workspace(s) and that we are still not sharing these changes with the team yet. That is coming soon when we discuss streams.
There is a four click animation on this slide
1st shows a change set flowing in and the first sub-bullet
2nd shows a change set flowing in and the second sub-bullet
3rd shows a change set flowing in and the second main bullet and its first sub-bullet
4th shows a change set flowing in and the final sub-bullet

17. Streams Local Workspace Repository Workspace Local Workspace
Components
Repository Workspace
Change set
Change set
Change set
Change set
Components
Change set
Change set
Change set
Change set
Stream
Components
Note that streams and repository workspaces are essentially the same except that streams are for sharing and repository workspaces are private
This animation (3 clicks) starts with where we ended on the “Components” chart. The changes have been checked-in to each developer’s repository workspace. Now we will see sharing via a stream.
1st click – delivery
2nd click – accept
3rd click – automatic (if affected component loaded) propagation to local workspace
The following charts will introduce the actions for making this all happen.
Stream
A place to share source with your team
Change set

18. Typical Journey For A Change set
3. Complete (usually combined with deliver)
4. Deliver
Stream
Component
Repository Workspace
Component
2b.Change set
2a. Check-in
A quick animated change flow overview with the screen shots to show the annotations.
Note that Check-in can be made automatic after a save via the preferences.
Local Workspace
1. Change

19. Source Control – Workspaces and Streams
Deliver changes from your Workspace to be integrated with a Stream
Make changes in your own Jazz Workspace, in parallel with other developers
Stream
(not directly editable)
You can accept changes from a Stream or someone else’s Workspace
Workspaces
(loadable and editable)

20. Source Control – RTCi Compare versions of source members
Here is an outstanding change which is about to be delivered from my workspace to the stream. Also, can accept incoming changes or suspend changes.
Explore and drill down
into change-sets
Browse files stored
in the repository

21. Target Interop Scenarios Supported with Rational Team Concert v1.0
Import
Co-exist
Connectors
(Source SCM has master copy)
Integration with the SVN repository with the Collaborative development capabilities of RTC (Workitems, Build)
(Source SCM has master copy)
Provide capability to import from tools into RTC v1.0
(RTC has master copy)
ClearQuest (includes CQ enabled UCM)
Bugzilla
repository
Bi-directional Synchronization
Rational Team Concert v1.0
Rational Team Concert v1.0
Import
One-time import of data with best-effort mapping between models
Connector
Designed for developers who want to use the fully integrated Jazz SCM, but need to connect into a “mother ship” SCM system.
SCM artifacts are replicated/synchronized between the Jazz SCM and the “mother ship” SCM
Useful for pilot projects/staging migration to RTC – not all teams need to move at the same time. Allows teams to begin using RTC in the context of requirement to maintain master source code in a different SCM system.
The team that is using RTC in this scenario is gets the full benefit of the tight Jazz SCM integration.
Coexistence
Designed for developers who can’t or don’t want to switch SCM’s: You continue using your favorite SCM client and server (with all its features and problems)
RTC CDE installs “beside” SCM client
Limited integrations depending on particular SCM client e.g. linking, client-side process integration. Inferior to native Jazz SCM integration due to implementation limitations and the fact that server side is not integrated (example: Subversion and and other SCMs don't support process enactment for SCM operations. If you want that, you have to get your SCM from us)
Jazz SCM can be optionally available to try out for possible upsell (packaging decision)
CVS or SVN repository
Subversion repository
Rational Team Concert v1.0
ClearCase
(Base CC and UCM) 21 21

22. Builds – scheduling or build on demand
You can schedule regular builds and/or request builds on demand.
Define project builds and register build engines to submit the builds requests to.
Check the build history and open the build reports to get build logs, links, listings, etc.
zOS specific build definition property pages

23. Build Reports Team news feeds include Build status
Link to logs (build logs,
Compile listings, etc.
for this build)
List of builds which
have been submitted
for this build definition
Link to the snapshot of the
version which was built
Links to changes and WIs
Integrated for this build
Team news feeds
include Build status

24. Accessing Build Logs
Click the link here to see the contents of the build log (shown below). The log shows that the build created our program successfully, and posted a savefile containing the build to our team’s build website for others to download

25. Process definition
Select a process template or create your own templates.
Processes are highly customizable; create your own roles
and set permissions for those roles, even with sensitivity to
configured development phases. Customize work item
types and state flows, Configure notifications,
approvers, preconditions, and calls to other team tools.
Open, eclipse myway, rup
Define parallel development lines, and releases, iterations or
stages within those development lines. Configure schedules
for iterations and stages.

26. Process Configuration Editor

27. Process - planning Define plans for the stages of development…
…and track the execution of that plan by members of the development team

28. Teams Define your teams, team roles and permissions
The configurable Team Central view allows the whole team to monitor things like team workload, incoming work items, build results, recent team news events, etc.
Start Instant Messaging sessions with other teammates, with linkability to source code, work items, builds, or any other team asset in the repository.
Explore the Team Organization

29. Work Items Team members can carry on discussions about the work item
A Defect work item. You can create your own work item types with their own state flows
Can assign approvers for work items

30. Work Items – Links
Add subscribers to be notified by when this work item changes
Attach files or screenshots to work items
See relationships to other work items, or repository elements
Look at the source changes made for this work item

31. Work Item Queries Run the query and/or save it for future queries
Create your own work item queries with the query editor
Keep your own private queries, or share queries you create with the team
Defined work item queries
Quick Search entry field for work items
Work item query results

32. And there’s a Web UI for universal access! (with security)
Even those not using Eclipse-based clients can interact with the Jazz repository to look at plans and reports, to query and update work items, and drill down into the Source Control system.
This allows non-developer team members (e.g. managers, end users, etc.) to easily collaborate without having to install a rich client.

33. Generate Reports to Monitor Project Health
This is a graphical report showing the trend of open vs. closed work items for our EntryOrder project
Select a type of report to generate, or create and share your own customized reports

34. Customize Dashboards to summarize your project

35. Summary
Jazz is an Open Commercial project for Team Collaboration - join up at
Rational Team Concert will be the first IBM product based on Jazz technology
We are extending RTC to the z platform
With a Team Server that can run on zOS
With extensions to make this useful to COBOL, PLI artifacts on zOS file systems
RTCz will greatly extend Rational’s Application Lifecycle coverage for System z development:
With customizable development processes
With Source Change Management for System z applications
With work items that have rich linkability to other resources in the repository
With Team Build support for System z applications
With customizable reporting and querying to monitor System z project status
With multiple options for notifications to and communications between team members (e.g. , news feeds, IM, subscriptions, etc)
With Web UI for secure universal access

36. DEMO

37. QUESTIONS

39. Jazz Source Control
As you would expect, it manages source code and other digital assets
Maintains previous configurations of source code
Prevents unauthorized access to assets
Alerts users when an asset has changed
In addition
Is aware of the structure of your components
Maintains an integrated history of changes
Helps you handle interruptions and conflicts
Integrates with the rest of Jazz
There is a single click animation that shows “In addition” and its sub-bullets
Emphasize that we will see all of these advantages and more in this presentation

40. Change set Details
Composed from a collection of changes to one or more files and folders
Change set orientation is another example of Jazz understanding your source and its relationships
A change set that affects multiple resources is committed as a single atomic unit
Indicates the reason for the changes
Via a comment, and/or
By referencing the relevant work item
Can be shared with another team member
Via a stream, or
From your repository workspace via a work item
Note that this change set orientation means cross resource dependencies can be managed as a single atomic change set
There is a two click animation on this slide
1st click shows the second primary bullet and its sub-bullets
2nd click shows the third primary bullet and its sub-bullets

41. Change set Delivery is Process Enabled
The deliver operation is process-enabled, allowing the team’s process to check and enforce delivery rules
A failure is shown with a quick fix available.
After fixing, the deliver works. Single click animate here.
During the lab, you will experience this yourself.
There are other rules that can be enforced at delivery and other times. We will not have time to explore all the possibilities but this one is a good example.

42. Delivery Notifications
You will see notifications at the lower right part of your screen and in an event feed.
These incoming change sets will show up in the Pending Changes view.
Click for the animation to show the Pending Changes view.
Note the left pointing arrow decoration and its use in the UI
This is called an incoming change set

43. Getting Teammates’ Delivered Work
An incoming change set is
In the change history of the stream, but
Not in the change history of your repository workspace
Accept adds the change set to your repository workspace’s change history
Stream
Component
Repository Workspace
Component
Accept
After you deliver changes, others will see them as incoming change sets and will want to get them.
Single click animation now the shows the last bullet, the accept call-out and lines and changes the screen shot.
Note that iff you have the Component loaded into your Local Workspace then the change is also propagated to your Local Workspace (the dotted arrow).
Local Workspace

44. A Baseline Is an immutable copy of a component’s configuration
At a particular point in time, and
There can be multiple baselines of a component
Serves as a fixed point of reference
For initializing streams and repository workspaces
For sharing source with people or processes
Can be easily compared
With each other
With the current state of a stream or repository workspace
There is a two click animation on this slide
1st shows the second primary bullet and its sub-bullets
Note that we saw this earlier when we added the Build component to the stream.
2nd shows the third primary bullet and its sub-bullets

45. A Snapshot
Is a collection of one baseline per component in a repository workspace or stream
Captures an important repository workspace configuration for later recreation
There can be multiple snapshots of a repository workspace or stream
Like baselines, snapshots are used for sharing
Create a repository workspace or stream
Update the contents of a repository workspace
Recreate a prior build via a build created snapshot
Note that snapshots are like baselines except that they have a broader scope (a collection of component baselines vs the state of a single component).
There is a single click animation on this slide
Shows the second primary bullet and its sub-bullets