Upload
strongback-consulting
View
2.463
Download
0
Embed Size (px)
DESCRIPTION
A scenario demonstrating the usage of Rational Team Concert for System i. This is a tool set for building team collaboration around RPG, COBOL, CL, and DDS assets.
Citation preview
1
Rational Team Concert for i
Demo Scenario
• Kenny Smith
• Principal Consultant
2www.StrongbackConsulting.com
Overview
• This presentation is designed to take you through a demonstration scenario of usage with Rational Team Concert for System i
• For an interactive demo, please refer to the Enterprise Modernization sandbox for i
• You can also try out the software directly from http://Jazz.net
www.StrongbackConsulting.com
A sample lifecycle: How do we collaborate?Sample scenario - Business Executive sends a request to the IT department, which involves a change to a composite application with business Logic change with RPG components and web presentation change with EGL components
RequestEnhancement
Divide work into tasks, schedule the release plan, and
assign to Developers/groups
Business Executive
Dev/Proj Mgr - George
RPG Developer - Joe
EGL Developer - Joe
End User
Design changes
tocomponent
RequestDesign
Approval
Approve Technical
Design
Check Project Status
Throughout the Project lifecycle
Integration Testing
Approvechanges
Approve Upgrade to Production
system
Design changes
tocomponents
RequestDesign
ApprovalDeliver
Code changes
DeliverCode Changes
FunctionalTesting
FunctionalTesting
Create Enhancement
Work Item
Check progresson iteration
plan
Sys Admin/Builder - RobinSchedule
And DeployEnhancementsTo Production
System
System Analyst
Approve Technical
Design
Approve Technical
Design
Promote/BuildTesting Integration
Steam
Create requirements
Approval
Code review/approval
www.StrongbackConsulting.com
Sample Application
1. Web application provides a web interface to view “Customer Information” stored on IBM i.
www.StrongbackConsulting.com
Sample Application (continue)
1. RPG component
2. EGL Component
www.StrongbackConsulting.com
RTCi Web Interface 1. Web Client Log In
2. Web Client Menu provides the following tabs:
ProjectArea, WorkItem, DashBoard, Iteraltion Plan, Source Control, Report
www.StrongbackConsulting.com
Define Requirement
www.StrongbackConsulting.com
Demo Scenario – Executive Submits a New Requirement
1. Business executive submits a Story Work Item about a potential new requirement via RTC web interface – Project Dash Board.
2. Fill in the description of the idea and pick the product group/team that the Work Item is filed against.
3. Select Link tab to attach any files (screen capture, article and etc), also add user names who will be notified about this new requirement Work Item.
4. Assign to the system Analyst.
5. System Analyst is notified by RTC and via Email.
System analyst works with end User and other stake holders.
All stake holders add their comments into this Work Item.
www.StrongbackConsulting.com
Demo Scenario – Executive Approves the New Enhancement
2. Executive approves the new requirement.
3. System Analyst assigns the Work Item to the Development/Project Manager to work on.
An agreement is reached.System Analyst clearly defines the requirements - estimated cost, scope, and impact of existing products.
System Analyst requests the approval from Executive.
www.StrongbackConsulting.com
Plan the Work
www.StrongbackConsulting.com
Demo Scenario – Development/Product Manager Creates an Enhancement
1. Development/Project Manager creates an Enhancement Work Item to implement the newly defined feature.
2. In the Link Tab, add the story Work Item as the parent of this new Work Item.
3. In the Approvals Tab, add executive, end user, system Admin, and etc to the approvers and reviewers list.
The Story develops into a defined Enhancement.
www.StrongbackConsulting.com
Demo Scenario – Development/Product Manager Analyzes the Work
2. Set the Parent Work Item for both new Tasks. This shows the overall hierarchy of these Work Items.
1. Development/Project Manager creates two new tasks. One is against RPG component, the other is against EGL component. Assign each to the appropriate developer and set the release plan.
A defined Enhancement is divided into multiple tasks
www.StrongbackConsulting.com
Demo Scenario – Development/Product Manager Plans the Work
1. Development/Project Manager sets the peer reviewers for the new Tasks
2. Development/Project Manager Plans the release
www.StrongbackConsulting.com
Feature Development
www.StrongbackConsulting.com
Demo Scenario – Developer Joe and Mary Accept the New Assignment
1. Dev Joe and Mary are notified by email and log into RTC project area via RTCi and RDi integrated client.
2. Select MyWork Tab to check his/her new work assignment. 3. Dev Joe accepts all works
newly assigned to him. Then Joe opens the Work Item and set the Work Item status to Start Working
3. Dev Mary accept sall works that newlyassigned to her. Then Mary opens the Work Item and set the Work Item status to Start Working
www.StrongbackConsulting.com
Demo Scenario – Stake Holder Approves the Design DocumentsDev Joe submits a design document for Project Lead, System Analyst, and End User’s approval.
Dev Mary submits a design document and a screen capture of User Interface for Project Lead, System Analyst, and End User’s approval.
Project Lead, System Analyst, and End User approve Joe’s design.
Project Lead, System Analyst, and End User approve Mary’s design.
Dev Joe and Mary start implementation of the Enhancement
www.StrongbackConsulting.com
Basic Software Configuration Management (SCM) Anatomy
Streams are for sharing resources. For example, a Team Development Stream contains all product assets that a team is actively working on.
A repository workspace is your personal space saved in the repository. It is for developer to save intermediate work. It is not visible to other team members until you deliver into stream.
Local workspaces are where you edit resources. Changes flow back and forth.
Repository Workspace
Stream Local Workspace
Your changes
Other’s changes
IBM i PC
www.StrongbackConsulting.com
PCIBM i
Local WorkspaceRepository Workspace
Set up/load Local Workspace & Check-in and Deliver from Local Workspace
StreamComponen
tEclipse Project
Folder
Eclipse Project
File
File
File
File
File
Folder
Eclipse Project
Component
Eclipse Project
Folder
Eclipse Project
File
File
File
File
File
Eclipse Project
Create Repository Work Space
Component
Eclipse Project
Folder
Eclipse Project
File
File
File
File
File
Folder
Eclipse Project
Component
Load into Local Workspace
File
Developer Edit the FileCheck-in the new file to Repository WorkspaceDeliver to the Steam to share with other developers
File
File
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Sets up the Work Environment
1. Dev Joe launches the New Repository Workspace panel by selecting My Repository Workspace right mouse menu.
2. Dev Joe selects the right Stream for the RPG component.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Loads the Project into Local Workspace
1. Dev Joe selects the RPG Component.
2. Dev Joe selects to Find and Load Eclipse Project (RDi Project) into Local Workspace.
This tells RTC to load (copy) RPG project into Joe’s local workspace on his PC.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Works on the RDi Project
1. Visualize the RPG application.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Works on the RDi Project
1. Dev Joe opens iProject perspective
2. iProject
3. RDi Remote System Explorer
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Works on the RDi Project
1. Compile the RPG via RDi RSE interface
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Works on the RDi Project
1. Debug the application
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Checks-in & Delivers the Change
1. Dev Joe opens RTC Work Item (RTC) perspective. Select the Pending Change tab and expand the component tree.
Notice the => icon in the Pending Change tab.
This means new change in your local workspace needs to be checked-in to repository workspace and delivered into the stream.
2. Dev Joe launches Check-in Panel by selecting the right mouse menu.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Works on the RDi Project
1. Process forces “A work Item must be associated with the change set”.
2. Click “Associate Existing work item” to pick a Work Item.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Works on the RDi Project
1. Process forces that the change set must be reviewed before it can be dlivered into the Team Integration Stream.
www.StrongbackConsulting.com
Demo Scenario – Reviewers and Approvers Review the Change
Dev Joe updates the Work Item. Approvers and Reviewers are notified by RTCi and via Email.
1. Project Lead and Other RGP developers review the change.
To see the Change Sets, open the Work Item and select Open the Change Sets in the Links Tab
2. Selects the element/file and Open in Compare Editor to compare the changes made by Joe line by line.
All reviewers approve the change.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Checks-in & Delivers the Change (Continue)
1. Dev Joe selects the Work Item and finishes the Check-in and delivery.
This associates the Work Item with that Change Set
Notice: If there is a conflict – the file Joe is about to deliver has been modified by other developers, RTCi will ask Joe to merge the change.
www.StrongbackConsulting.com
Demo Scenario – Developer Joe Resolves the Work Item
1. Dev Joe is notified that his change is approved.
3. Dev Joe Resolves the Work Item.
2. Dev Joe opens the Work Item by select the Work Item in Work Items Tab
www.StrongbackConsulting.com
Demo Scenario – Developer Mary Works on the EGL Project1. Developer Mary creates the Repository Work Space and loads the project into her Local Work Space.
2. Developer Mary opens EGL perspective and opens EGL project.
5. Developer Mary Checks-in and Delivers the code change.
4. Developer Mary finishes the code change and tests in the Sand Box.
3. Mary is notified that Joe has delivered his RPG component changes. So Mary can test her change.
** Notice: Develop Mary does her work in parallel with Developer Joe. This slide continues from slide 15 – Stake Holder Approves the Design Document.
www.StrongbackConsulting.com
Demo Scenario – Developer Mary Checks-in and Delivers the Change
1. Developer Mary Checks-in and Delivers the change.
2. Developer Mary updates the Work Item.
3. Reviewers and approvers are notified by RTC and via Email.
5. Developer Mary Resolves the Work Item
4. Reviewers and approvers approve Mary’s code change.
www.StrongbackConsulting.com
Testing Integration Stream
Builder Promotes Change from Team Dev Steam to Testing Integration Stream
Team Development Stream Joe’s Local Workspace
Joe’s Change
Mary’s Local Workspace
RPG Component
EGL Component
Robin’s Local Workspace
Joe’s Change
Mary’s Change
Deliver
Accept Changes
RPG Component
Joe’s Change
EGL Component
Joe’s Repository Workspace
RPG Component
Mary’s Repository Workspace
EGL Component
Robin’s Repository Workspace
RPG Component
EGL Component
PCIBM i
EGL Component
RPG Component
EGL Component
RPG Component
Joe’s Change
Mary’s ChangeMary’s ChangeMary’s Change
Mary’s Change Mary’s ChangeMary’s Change
Joe’s Change
Joe’s Change Joe’s ChangeJoe’s Change
Check-in
Load
Deliver
Deliver
Check-in
Build
www.StrongbackConsulting.com
Demo Scenario – Builder Robin Sets up the Work Environment
streams
Team Development Stream
Testing Integration Stream
Repository WorkSpacesBuilder EGL Workspace
Builder RPG Workspace
Builder Robin Accepts Incoming Changes from Team Develop Stream
www.StrongbackConsulting.com
Demo Scenario – Builder Robin Sets up the Build Environment
1. Builder Robin defines a Build Engine.
2. Build Robin starts the Build Engine from IBM i system.
www.StrongbackConsulting.com
Demo Scenario – Builder Robin Launches the Build
2. Builder Robin checks the Build Result. In this case, the integrated build failed.
1. Builder Robin submits the Build Request.
3. Builder Robin finds out that Joe’s change breaks the build by opening the Change Sets link in build log.
www.StrongbackConsulting.com
Demo Scenario – Builder Robin Analyzes the Build Log
Team is notified of integration build failure.
Joe is notified of the newly assigned blocking defect.
3. Builder Robin accepts the Joe’s change. Then launch a new build. The build succeeds.
2. Joe starts working on the blocking defect and fixes the error in his Local Workspace, then checks-in and delivers into the Team Dev Steam.
www.StrongbackConsulting.com
Demo Scenario – Builder Robin Analyzes the Build Log (Continue)
1. The team is notified with the latest build result via RTC and Email.
2. A new release is created for End User to do Integration Testing
www.StrongbackConsulting.com
Demo Scenario – Executive Approves to Deploy to Production
End User is notified that a new release candidate is available for testing.
Product/Development Manager resolves the Enhancement Work Item.
End User tests the release and updates the Work Item with successful testing result.
Executive is notified about the testing result.
Executive approves the deployment to the production.
Release is deployed to the production. Work Item is updated with the final result.
www.StrongbackConsulting.com
Additional Features
www.StrongbackConsulting.com
Executive Checks Work Item Status via Dash Board
Executive checks the progress of this Enhancement anytime during the development process by checking the history of Work Item via Dash Board.
RTCi saves the Recently Viewed record on the server. This helps Executive check only Work Items he/she is interested in.
Personal reports can be created for Executive’s convenience.
Executive can also find other related Work Items via Links Tab.
Personal queries can be created for Executive’s convenience.
www.StrongbackConsulting.com
Executive/Project Manager Checks Project Status via Project Dash Board
New Work Items by Severity
Closed Work Items by Priority
Notice: Project Dash Board is highly configurable for every project.
Blocking Work Items
Open Work Items by Type
www.StrongbackConsulting.com
High Traceability of RTCi
All related Work Items are linked, from Story to Enhancement, from Enhancement to Tasks.
Each Task includes a complete list of Change Sets.
Each Change Set includes the detail information for Auditing and other purposes. The time ,the person makes the change, and what are changes are all recorded.
www.StrongbackConsulting.com
High Traceability of RTCi (Continue)
Work Item includes the complete history of the Task.
For each Change Set, you can open the line by line file comparison.
www.StrongbackConsulting.com
Resources
• Our blog site – search on RTC or System i:– http://blog.strongbackconsulting.com/• Jazz Team site for Rational Team Concert– http://jazz.net/• RTCi hub– http://bit.ly/2lhEGk