rationalize your software delivery with ibm

Rationalize Your Software Delivery

With IBM

Integrated Change, Build And Deploy Is What Sets Us Apart

We Will Show How IBM Rational Addresses JKE’s Software Delivery Strategies

• Implement ALM with the whole team approach Break Down Barriers with the Jazz Platform, Improved Planning and Collaboration

• Improve requirements management

• Build better designs collaboratively

Define, Manage, and Track your Requirements and Designs

• Create an efficient development environment Integrated Change, Build and Deploy Is What Sets Us Apart

• Instill software quality across the lifecycle Quality Is Not Accidental

• Extend the lifecycle to include operations Bridge the Gap between Development and Operations

• Connect all software delivery capabilities together into an end to end open solution

Big Picture – See the Forest for the Trees

4 - Integrated Change, Build And Deploy

Change And Configuration Definition

“Software change and configuration management

(SCCM — mainframe and distributed) tools

implement a set of disciplines used to stabilize, track

and control the versions and configurations of a set

of software items and also may include development

change management, defect tracking, change

automation, development release management,

integrated test management, integrated build

management and other related processes.”

Gartner IT Glossary http://www.gartner.com/it-glossary/


http://www.gartner.com/it-glossary/



JKE’s Current Support For Change And Configuration

Multi-site, globally distributed

development on different

platforms

Many different CCM

methodologies/tools

Each tool requires unique

integration with other tools

Each tool has own repository

Point-to-point integrations

become unmanageable

Brittle/non-existent linkage to

Requirements and Quality

tools

Teams find it hard to

work together

A variety of standalone tools for Change And Configuration Management

(CCM)

UI

LOGIC

DB

UI

LOGIC

DB

UI

LOGIC

DB

UI

LOGIC

DB

UI

LOGIC

DB

Planning:

MS Project

Build Management:

Ant

Reporting:

Business

Objects

Work Items:

ClearQuest

Software

Configuration

Management:

ClearCase

4 - Integrated Change, Build And Deploy 4

5 5

A Better Change and Configuration Management Solution Is Needed

Such a solution must have these

capabilities:

1. Links with Requirements and

Quality Management ALM domains

2. Work Item Management

3. Software Configuration

Management

4. Project Planning/Management

5. Automated Build Management

Rational Team Concert

was designed to do

this. It allows your team

to collaborate on plans,

tasks, code and builds,

all in one place!


Rational Team Concert Is The Core Product In IBM Rational CLM

Jazz Team Server

RTC RRC RQM

Core OSLC REST Services: Discovery, Query, Storage, Presentation, Data Warehousing,

Administration, Reporting, etc…

RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Work items:

Activity, Task, Defect,

Approvals and

Discussions, Open-

ended

Project Planning and

Management:

Agile planning,

Reporting & Dashboards

Build System:

Automation and

integration with SCM

and work items

traceability, Local and

Server builds

Software Configuration

Management:

Server-based sandbox,

Change sets, Streams,

Components, Snapshots

and Baselines

Rational Requirements

Composer

Collections

Requirements

Storyboards

Use cases

…

Rational Software

Architect Design Manager

Designs

Models

Diagrams

…

RSA DM REST

Services: Design

Management

Rational Quality Manager

Test plans

Test cases

Test scripts

Test executions

…


RTC Clients: Web browser, Eclipse-based,

MS Visual Studio

RTC Work Items Are Used To Track And Coordinate Development Tasks And Workflows

Jazz Team Server

RTC RRC RQM



RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Work items:


Approvals and

Discussions, Open-

ended


Management:

Agile planning,


Build System:

Automation and


and work items


Server builds


Management:




and Baselines


Composer

Collections

Requirements

Storyboards

Use cases

…

Rational Software


Designs

Models

Diagrams

…

RSA DM REST

Services: Design

Management


Test plans

Test cases

Test scripts

Test executions

…



MS Visual Studio

Work Items Are The Fundamental Artifacts In RTC

Plan work item types are used to capture high-level plan

elements

Epic

Story

Execution work item types are used to capture the lower-level

details and the work that should be completed in a single

iteration

Task

Defect

Work items are the basis for linkage between many artifacts

8 8 4 - Integrated Change, Build And Deploy

Work Item Creation Is Easy And Fast

Work items that reflect

repeating tasks in

different iterations

Create by

instantiating a

template for each

iteration

Work item template

wizard

Capture and create

new templates


Work Item templates allow the creation of work items with pre-

populated attributes and links

RTC Allows Users To Collaborate With A Real-Time, In-Context Work Item Comment

10

Shows team members and their online status

Can start chat in

context with work item


What requirements did this iteration address?

Are all the requirements tested? What defects are reported against

which requirements?

What requirements am I implementing?

How can I recreate the last version? What test uncovered this defect? What changes occurred last night?

How can I speed up my builds? Are build times getting longer or

shorter?

What is the quality of the build? What has changed that I need to

test? What defects did the last build

address?

Business Analyst

Developer

Tester

Build Manager

11

Traceability Helps Each Team Member Understand What Is The Status Of Their Work And Relate It To Others’ Work


Plan Item Traceability Improves Quality And Predictability

Everyone's work aligns to

requirements

Team members have transparency

to each others work

As things change, the “new reality”

is always available

Team has insight when all work is

done


Testers define and execute test cases with a clear understanding of requirements

Teams collaborate and clarify the details of requirements

Developers understand the requirements, test results and test criteria

http://pokgsa.ibm.com/home/j/i/jinli/web/public/html/arch_ken.html

Relationship Views Enable Continuous Traceability

Traceability View shows linkage of requirements, test cases, and defects

13 4 - Integrated Change, Build And Deploy

Find and respond to gaps as they surface through out the project

Tracing throughout the project improves regulatory compliance

Defect Collaboration In The Development - Test Cycle Reduces Costs And Improves Quality

Minimal # of clicks

needed to submit a

defect - automatically

linked to impacted

artifacts

Test results recorded

and linked to test cases

and associated

requirements

Test results can link to

software builds

Everyone has visibility to

defects, their impact,

and actions taken to

resolve them

14

Testers execute tests and submit defects found to RTC

Developers can see the exact test failure without having to ask for it.

RTC

RQM


RTC Software Configuration Management Consists Of Source Control, Change Management, And Version Control

Jazz Team Server

RTC RRC RQM



RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Work items:


Approvals and

Discussions, Open-

ended


Management:

Agile planning,


Build System:

Automation and


and work items


Server builds


Management:




and Baselines


Composer

Collections

Requirements

Storyboards

Use cases

…

Rational Software


Designs

Models

Diagrams

…

RSA DM REST

Services: Design

Management


Test plans

Test cases

Test scripts

Test executions

…



MS Visual Studio

JKE Needs Software Configuration Management To Track And Control Changes To Its Software Assets

Software Configuration Management (SCM) provides

processes and methodologies for managing assets that

Are stored in a secure repository

Can be organized into versioned artifacts, components and

subsystems

Can be baselined for milestones in projects, and tracked

Can be worked on by multiple developers at the same time

RTC has its own indigenous source control that is built into

Jazz for better integration

Storage model is based on the

change set - a collection of

changes to one or more

files and folders


Many ALM suites integrate with

3rd party tools like Subversion for

configuration management

Integration between Eclipse and

Subversion relies on specifically-

formatted comment templates.

Integrated Configuration Management Is Critical For Development

RTC offers native source control

allowing better integration

especially when it comes to

linking change sets with work

items

17

JIRA or

TeamForge

or others…

Subversion

Rational Team Concert

Planning, Work items,

SCM, Build, Deployment


RTC Uses A Dual Developer Workspace Design “Sandbox” – Developer work area where code changes made. In RTC:

1. On the developer’s machine (Eclipse workspace shown), plus…

2. Personal repository workspace

on the server

Personal repository

workspace

Backed up with other

server repositories

Preserved in baseline and

snapshots

Searchable and collaborative

Available to other team

members to view and access

Permits personal builds

Test your code against latest team build before delivered to stream

Avoids accidentally breaking team build with your changes


New Repository

Workspace

Local

Workspace

(Eclipse)

Server

Client

Repository

Workspace

Stream

Dual

Server-Side

Repositories

Developer

Private

Sandbox Load Check-in

Deliver Accept

Share Project

New Stream

New Repository

Workspace

Local

Workspace

(Eclipse)

Server

Client

Repository

Workspace

Stream

Dual

Server-Side

Repositories

Developer

Private

Sandbox Load Check-in

Deliver Accept

Share Project

New Stream

RTC Streams Reduce The Chaos That Emerges From Constant Branching And Merging

Subversion uses branches

and merges, not streams

Relies on conventions for

naming and committing

Depends on the underlying file

system

Developers need to understand

that structure

RTC's streams are integrated,

organized and managed

The repository manages

searchable metadata about

streams, components, and how

they're linked

The tool is the "integration agent"

19

Trunk

Task Branch

Task Branch Task Branch

Release Branch

Task Branch

Task Branch

V 1.0

Integration Stream

Feature A Stream

Feature B Stream

John’sRepository Workspace

Mary’sRepository Workspace

Fred’sRepository Workspace

Jill’sRepository Workspace

Team members can share change sets using streams or even in an ad hoc

manner directly from each other’s repository workspaces

Change set: A collection of changes to one or more files and folders

Stream: A single configuration of source code


20

We need the system to be flexible

enough to seamlessly hand off

work between developers

whenever necessary.

Version Control

Development Manager

Rational Team Concert's dual

tier repository architecture

allows developers to easily

pick up another's work in case

someone can't continue on

the project.

IBM


Demo 1: Jazz Source Control And Repository Workspaces

21

MTM

Stream

Eclipse based

IDE

2.

Automatically

checked-into

the repository

workspace

Deb’s

repository

workspace

Marco’s

repository

workspace

1. Deb works

on the files for

the Web UI

Eclipse based

IDE

4. Marco can work

on the files in her

absence

Deb is working on the website user interface for Money that Matters.

What will happen though when she suddenly falls ill?

2. Deb works on the

files for the Web UI

1. Check

out code

to local

workspace

4. Marco is unable to

retrieve the files from

her local workspace

unless he gets her

password and

physical access

RTC

Eclipse IDE Eclipse IDE

SVN

repository

3. When Deb falls ill

unexpectedly her files are still

in her local workspace

because she has not yet

committed the latest changes

Subversion

3. When Deb falls

ill unexpectedly,

her coworker can

pull the work in

progress from her

repository

workspace


RTC Has Control Of SCM Permissions At The File And Folder Level

Deletion and Artifact Level Read Permissions

Provide read permissions at the

versioned artifact granularity in SCM

Permanently delete files (Administrators

only)

More Flexible Workspace and Load

Management

Check-in History to easily revert to any

checked-in version


Atlassian Stash Offers Limited Enterprise Enablement For Git Repositories


RTC offers a complete toolset to create and configure JSC repository workspaces, streams, etc.

• Stash can only create an empty Git repository that then can become a remote repository for an existing Git repository

• Stash repository must be configured by Git tools outside of Stash

RTC clients offer all necessary tools to work with version control

• Stash can only perform branch merging

RTC controls user permissions, repository workspaces, streams, and local folders access rights

• Stash manages permissions only for the repositories created by and accessed through Stash

RTC offers fine-grained access to workspace repositories and local folders and files

• Stash controls who can commit to specific branches in a repository

23

Atlassian ALM Solution Lacks Traceability Because Association Of Atlassian JIRA Issues With Code Versions In Stash Is A Manual And Error Prone Process

RTC offers convenient dialog which allows linking the change set to a corresponding work item

• This is a manual action in Stash that is done by entering a JIRA issue key into the commit message

In RTC, a developer can select an existing work item or create a new one while linking the change set to it

• Only an existing JIRA issue can be linked to the Stash commit

RTC can require developers to link a change set to the work item by enforcing RTC check-in policy

• There is no policy enforcement in Stash


25

We have development on

several platforms. How do

you support development on

various platform? Also, what

would you suggest for

transition of System z

developers who user ISPF?

Platforms Support

Development Manager

Rational Team Concert supports

Intel-based servers with a broad

range of operating systems

including Mac OS X, Power with

AIX and Linux and System z with

zOS and Linux. We also have an

ISPF client for RTC…

IBM


Mainframe Programmers Can Continue To Develop Using Traditional Tools If Desired

ISPF Client For Team Concert

Use RTC from traditional

green-screen interface for

SCM

Use repository

workspaces, change

sets, link to work items,

build requests, etc.

Check out/check in code

to native z/OS file system

Build, promote and deploy on

z/OS (and IBM i)

Dependency-based builds

Enhanced conflict resolution

with Compare/Merge

Sparse loading of large

components on z/OS

ISPF SCM Client


RTC Planning Provides Tools To Assist With Planning And Execution Of Both Agile And Traditional Projects

Jazz Team Server

RTC RRC RQM



RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Work items:


Approvals and

Discussions, Open-

ended


Management:

Agile planning,


Build System:

Automation and


and work items


Server builds


Management:




and Baselines


Composer

Collections

Requirements

Storyboards

Use cases

…

Rational Software


Designs

Models

Diagrams

…

RSA DM REST

Services: Design

Management


Test plans

Test cases

Test scripts

Test executions

…



MS Visual Studio

RTC Planning And Management Is Directly Linked To Execution

Track progress during an iteration

Balance work load of developers

Determine schedule dependencies and

constraints

Make plans accessible to everyone on team

Change plan dynamically over course of project

to reflect team's position and direction

Perform estimation and planning at daily,

iteration, and release level

Make plans and status Web-accessible to

extended stakeholders

Planning across projects

Master Plan tracks cross-cutting tasks

See a schedule roll-up of tasks


Module 2 introduced RTC’s ability to create project plans at the start

of a project. But RTC can also:

Planning Across The Entire Team Includes Requirements And Test Team Roles

Product Backlog

Collection of requirements in RRC

Test Plan in RQM

RTC Release Plan with links to related:


RTC Reports And Dashboards Provide Complete Transparency Of The Project Status To Managers And All Team Members

Reports and dashboards help

manaagers keep tabs on project

health

Prevent unpleasant surprises

Reports and dashboards are

customizable and configurable


RTC ships with a library of 50+

predefined reports

Reports provide both real-time

views and historical trends

Dashboards provide at-a- glance

views on project progress

Variety Of Views Helps Managers Keep Track Of Work Items And Changes

Work Breakdown Structure view has resource bars so that managers can determine who is overloaded. They can then manually level the assignments

Taskboard view is ideal for daily Scrums. At a glance everyone can see who is working on what in the pipeline


Customizable Kanban Taskboard Helps to Optimize The Flow Of Work

Uses a “pull” model

Allow teams to set “work in process” limits and visualize the

flow of work

Where is capacity available? Am I exceeding my desired limits?

Green indicates optimal capacity

4- Integrated Change, Build and Deploy Is What Sets Us Apart 32

Not optimal – Should have two tests underway


Verifing Code Compliance With Software Analyzer

How can we make sure our

code is compliant with our

company's and the industry's

standards?

With Rational's software

analysis capabilities you can

verify your code quality

IBM 4 - Integrated Change, Build And Deploy 33

Development Manager

Demo 2: Rational Software Analyzer

Rational Software Analyzer can be integrated with

Rational's development tools to automate code reviews and

verify compliance with a company's or an industry's

standards

Automatically detect bad designs implemented in code

Support and enforce coding standards and best practices


RTC Build System Provides Means To Retrieve Work From Repository, Make Available To Build Scripts, And Deliver Results

Jazz Team Server

RTC RRC RQM



RRC REST

Services: Rqmts

Management

RTC REST

Services: Change

Management

RQM REST

Services: Quality

Management

RSA DM

Work items:


Approvals and

Discussions, Open-

ended


Management:

Agile planning,


Build System:

Automation and


and work items


Server builds


Management:




and Baselines


Composer

Collections

Requirements

Storyboards

Use cases

…

Rational Software


Designs

Models

Diagrams

…

RSA DM REST

Services: Design

Management


Test plans

Test cases

Test scripts

Test executions

…


RTC Clients: Web browser, Eclipse-based, MS

Visual Studio

Automated Builds Save Time And Effort

RTC Build System automates builds as part of the continuous integration process

Small changes are constantly applied and integrated

In some cases, builds are triggered on every commit

Process of integrating early and often improves quality and reduces rework and cost

The build can be fully automated

Compile the source

Generate documentation or supporting files

Package the binaries

Deploy

Trigger test execution

RTC Build System tracks and monitors status of builds 36

Compile Source Generate

supporting files

Package files

Deploy Trigger

Test

So that developers can focus on writing code


Development Teams Can Schedule And Execute Software Builds Efficiently

Visibility to build engines, queues and schedules

Results of each build displayed on status page Any failures/errors

highlighted

Drill down for each build run: Performance

Work performed

Build results can link to change sets and work items Traceability across the

lifecycle

Build results can deploy to servers for testing or production

Work items, tests and change sets included in the build

Build Status


Personal Builds With RTC

Our builds often fail because a

developer commits a change set

that breaks the build. Then the

entire process is held up while we

wait for him/her to rectify it.

With personal builds you can

test it out first before pushing

it to the entire team.

Build Manager


Demo 3: Personal Builds

39

1. Deb makes her

changes to the code

Build Definition

4. B

uild

pu

lls th

e

co

de

fro

m S

VN

sh

are

d r

ep

osito

ry

3. Build runs on

schedule

Build Status

5. If she makes a

mistake it breaks

the build for

everyone

SVN

repository

2. D

eb c

om

mits

to the b

ranch o

r

tru

nk

Personal

Builds are not

available in

Subversion

Build process with Subversion + 3rd

party build engine

Deb’s personal

repository

workspace

1. Deb analyzes her source

code and checks into her

repository workspace

Build Definition

3. Build pulls

the code

from her

repository

workspace

2. D

eb

re

qu

ests

a

build

Build Status

4. Build is

successful

Stream

5. D

eb

de

live

rs c

od

e to

the

te

am

’s s

tre

am

assu

red

of its in

teg

rity

Running a personal build in RTC


After The Build, Files May Also Need To Be Deployed To Test Or Production Servers

RTC creates the deployment package and deploys it to the target server

Create

Package

Definition

Run a

packaging

build

Create a

deployment

definition

Can be deployed

to Linux, Unix,

IBM i, z/OS

Deploy the

package

Copies the

archive file

to the target

Gathers files into an

archive container


For Organizations That Require Advanced Integration, IBM Offers Build Forge

Can execute centrally-controlled builds in parallel across distributed

systems, speeding up the overall process

Utilizes sophisticated scripting and scheduling of the steps comprising

each build

Minimizes the amount of manual intervention required by a build engineer

Support for a broad spectrum of platforms (including System z),

scripting languages, and source code repositories

For usage as an enterprise standard build infrastructure

Builds source code, but also automatically deploys the underlying

software infrastructure (e.g. WebSphere Application Server, Portal) for

the code to run on

This level of automation completely frees up the build engineer and is not

found in any competing product

Tight integration with Rational Team Concert and Jazz artifacts for end-

to-end traceability


RTC Offers Tight Integration With Rational Build Forge

RTC and Build Forge integration is ideal for customers who require:

Enterprise-wide process automation across multiple platforms

Software assembly for Jazz and traditional environments

Build server load balancing

Deployment process automation support

Stringent compliance mandates for governance and traceability

Even when Build Forge manages and runs your builds, RTC will:

Publish build results

Show links to RTC-managed change sets and work items consumed by

build

Create metrics reporting/health status of Build Forge builds

Start Build Forge jobs from the RTC User Interface


Integrated Hudson/Jenkins Build Support

Directly submit builds through RTC to Hudson and view build health

in RTC

No need to log into Hudson to see the console job output

View Hudson Build Result to assess the builds success or failure

Submit builds to Hudson directly from RTC using its extensible

Build Engine support

Hudson console job output linked to the build result as a log file

43 4- Integrated Change, Build and Deploy Is What Sets Us Apart 4 - Integrated Change, Build And Deploy

Mobile Development

In the future, JK Enterprises would

like to expand out applications into

the mobile world. Does IBM have

similar solutions for mobile

development?

IBM Worklight provides an

open, comprehensive and

advanced mobile application

platform for mobile

development.


Development Manager

RTC And Worklight Studio Integration

Worklight Studio is IBM's Eclipse-based mobile

development platform with strong back-end connectivity

RTC keeps track of changes in a Worklight workspace and

creates change sets automatically

RTC controls distributed builds of mobile applications

Distributed RTC builds on Mac OS X for iOS app versions

Android builds distributed to a remote server with the Android SDK

installed to build for an Android device

Builds can be monitored and build results are available locally

SCM Build

Team Concert Client

Studio

Developer


In RTC You Can Configure And Run A Worklight Distributed Build

Configure Build Engine

Define Build

Results

Build Activities

Build Artifacts for download


Summary

Integrated Planning and Work Items management provides in-context collaborative environment

• Plan is always up to date, developers and other team members track their work with zero overhead

Life cycle traceability of work items

• Coverage of requirements, development, builds and test results

Productive Software Configuration Management

• Integrated Jazz Source Control links code artifacts to work items and then to builds and build results

• Enables developers to effectively work in parallel and to easy track versions of code artifacts for issue resolution

Integrated and extensible Build System that seamlessly links to work items and code version artifacts, easily extends to automated deployment

• Execute tests and automatically create issues linked to code artifacts and work items

• Supports all platforms

• RTC Integrates with Build Forge

• RTC integrates with Worklight for mobile application development lifecycle including management

47

Rational Team Concert provides a complete Change and Configuration Management

solution across teams, tools, projects and platforms


© 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.

www.ibm.com/software/rational


http://www.ibm.com/software/rational

rationalize your software delivery with ibm

Documents