WIXLIB

IBM Rational SoftwareRational Team Concertpowered byPhilippe Krief, PhDJazz Jumpstart TeamEclipse Comitterpjkrief@fr.ibm.comSoundAttachedLes Jeudis de l’Objet29 Mai 2008, Nantes 2008 IBM CorporationAgenda Motivation and goals High level architecture Jazz in Action Guiding Principles Jazz Ecosystem Roadmap2From the Eclipse Way to Jazz 2008 IBM Corporation1

IBM Rational SoftwareMotivation and Goals 2008 IBM CorporationWhy are we doing Jazz?The Development Landscape has shifted!LateLate 90’s:90’s: FocusFocus onon PointPoint ToolsToolsWho can build the best Java IDE, the best C IDE, the best Web Tool, WhenWhen wewe builtbuilt Eclipse:Eclipse: FocusFocus onon OneOne DeveloperDeveloperSeamless integration across a set of tools to improve the productivity of one developerToday,Today, wewe mustmust focusfocus onon thethe TeamTeam andand itsits CollaborationCollaboration Geographically Distributed Accelerated Delivery Demands Agility with Predictability Innovation and ctivityofofthetheEntireEntireTeamTeam Increased Need for Transparency4From the Eclipse Way to Jazz 2008 IBM Corporation2

Jazz: Forces in eb“Web2.0”2.0”AgileAgilePracticesPractices5 2008 IBM CorporationThe demand for Application Lifecycle Management (ALM) Traceability of relationships between artifacts“Managing dependencies between high-priority change requests and ongoing applicationdevelopment efforts “sometimes seems like it isn’t humanly possible.” (US healthcarecompany) Automation of high level processes“We had a consulting company define a methodology for us. We still have it on a shelfsomewhere. A process needs to live in the tools we use if it's ever going to befollowed.” (Transportation company)“Automating our build-deploy-test processes would probably save each of our developersabout an hour a day.” (Financial services firm) Reporting provides visibility“We do progress reporting the same way we've been doing it for 40 years. It's all manual:weekly status meetings, progress reports, demonstrations. We’d love to get testresults from nightly builds posted somewhere instead of having to run people down toask them whether things are working yet.” (Bank)A Forrester Research report, “The Changing Face of Application Life-cycle Management”66From the Eclipse Way to Jazz 2008 IBM Corporation3

Social Networking – Power of communities Wikipedia on Web 2.0:– a perceived second generation of web-based communities and hosted services that facilitate collaboration and sharing between usersIn the opening talk of the first Web 2.0 conference, Tim O'Reillyand John Battelle summarized what they saw as key principlesof Web 2.0:–the web as a platform–data as the driving force–network effects created by an architecture of participation–innovation in assembly of systems and sites composed bypulling together features from distributed, independent developers(a kind of "open source" development)–lightweight business models enabled by content and service syndication–the end of the software adoption cycle ("the perpetual beta")–software above the level of a single device, leveraging the power of The Long Tail.–ease of picking-up by early adopters7 2008 IBM CorporationFrom Eclipse to Jazz Eclipse Phenomena––––2.5 millions downloads (Eclipse 3.3)6 years shipping on timeMore than 20 projects delivered on top of Eclipse17 millions LOC Why?–––Extensible PlatformBased on Open StandardsEclipse Community How? Describing the process the Eclipse Way: Tooling the process8From the Eclipse Way to Jazz 2008 IBM Corporation4

Our Eclipse Way blesignofflivebetasalways havea clientenableshow cdrive withopen eyesreduce stressendgameconsume yourown outputvalidatelearnadaptiveplanningattractto latestnew ¬eworthyretrospectivesexploredynamicteamscommon Agile practicescommon Open Source practicesvalidatescaling-up practices9 2008 IBM CorporationBut there are Pain Points on Team Awareness–––––––joining a teamget my environment configured to be productivewhat is happening in my teamcollecting progress statusfollowing the team’s processstarting an ad hoc teamad hoc collaboration/sharing of changesBoring and painful Time thieves10From the Eclipse Way to Jazz 2008 IBM Corporation5

But there are Pain Points on (cont.) Build awareness––––––is the fix in the build?what will be in the next build?tracking a broken buildAvoid breaking a build/personal buildwhy is this change in the build?reconstructing a context for a bug/build failureBoring and painful Time thieves11 2008 IBM CorporationBut there are Pain Points on (cont.) Project Awareness–––––––creating, tracking iteration plansinterrupting development due to a high priority bug fixworking on multiple releases concurrentlytracking the code review of a fixreferencing team artifacts in discussionshow healthy is a component?collecting project data/metrics?Boring and painful Time thieves12From the Eclipse Way to Jazz 2008 IBM Corporation6

What if your tools know about your teamsabout your artifactswho is responsible for whatrules under which circumstances code can be delivered how to bootstrap a projecthow to help new team members get startedyour favorite work item types and their state transitionswhen the build runs and what to do if it breaks– Code quality, traceability, test runs, intellectual property13 2008 IBM CorporationThe Jazz projectPeople working together to deliver great softwareJazz is a project and platform for transforming how people worktogether to deliver greater value and performance from theirsoftware investments. A major investment by IBM to create ascalable, extensible team collaborationplatform. IBM’s vision for the future of softwaredelivery -- supporting a workforce that isincreasingly organizationally and globallydistributed, fluid and dynamic. An evolution of the Rational portfolio,which will evolve to support the Jazztechnology platform over time. A community at Jazz.net – the onlinevenue for open commercialdevelopment of select Jazz-basedproducts.14From the Eclipse Way to Jazz 2008 IBM Corporation7

IBM Rational SoftwareHigh Level Architecture 2008 IBM CorporationTools Collaboration generally means exponential complexity!Until now, building an integrated platformrequired a cross tools understanding:Each integrated tool had to knowabout each other tool.ToolTool A’ATool ETool FTool BTool CTool D16From the Eclipse Way to Jazz 2008 IBM Corporation8

Tools Collaboration based on Middleware Services With the Jazz platform, the tools communicate only with the platform: By listening to normalized/standardized events from the platform By sending normalized/standardized events to the platformToolTool A’ATool BTool CTool DTool ETool FEvents &ServicesAdaptiveProcess Enactment& Continuous AnalysisArtifactrelationshipsTeam Collaboration Services17 2008 IBM CorporationRational Team ConcertWork Items Bug tracking Task tracking Planning ApprovalsSource Control Change Sets Streams BaselinesBuild System Coverage Static analysisAdaptiveProcess Enactment& Continuous AnalysisArtifactrelationshipsFoundation: Project Areas, Teams, Users, Process,Chat, Presence, Events, Alerts, Dashboard, Reports, Search Team Concert provides an integrated Collaborative development environment Using a single repository Integrated Version Control, Work Item and a Build System18From the Eclipse Way to Jazz18 2008 IBM Corporation9

An evolution for new and existing customersThe Evolution of the IBM Rational Software Delivery PlatformNew OfferingsExisting OfferingsRationalBuild ForgeRationalClearCaseEvolution to Jazz Technology PlatformRationalClearQuestWork ProRationalTeam oductsRational QualityManagerBuilt on the Jazz Technology PlatformRationalBuild ForgeClearQuestClearCaseBuild ForgeRationalRequisiteProRationalClearCaseRational TeamConcert yManager---Other Rational& Non-RationalOfferingsFUTURE IBM RATIONAL SOFTWAREDELIVERY PLATFORM1919 2008 IBM CorporationPlaying with OthersBridgeImportOne way datamigrationConnectorsSVN Bridge links work itemswith change sets.Mylin repository connector(incubator)Two way zRepositoryJazzRepositoryCVS or SVNrepository20From the Eclipse Way to JazzSubversionrepositoryJazz Repository 2008 IBM CorporationClearCase(Base and UCM)2010

Jazz Platform ArchitectureJazzWebClientJazz Eclipse ClientOther ClientsJazz Client ExtensionsEclipse PlatformHTTP, Web Services, RSS, JRS (RestFull)Jazz Team ServerJazz Server ExtensionsWeb UIRepositoryJazz KernelCollaborationEclipse Equinox (OSGi)Application Server21 2008 IBM CorporationJazz Platform Architecture -Open Source middlewareJazzWebClientJazz Eclipse ClientOther ClientsJazz Client ExtensionsEclipse PlatformHTTP, Web Services, RSS, JRS (RestFull)Jazz Team ServerWeb UIJabberJazz Server ExtensionsJazz KernelApacheDerbyEclipse EquinoxApache Tomcat22From the Eclipse Way to Jazz 2008 IBM Corporation11

Jazz Platform Architecture -Enterprise middlewareJazzWebClientJazz Eclipse ClientOther ClientsJazz Client ExtensionsEclipse PlatformHTTP, Web Services, RSS, JRS (RestFull)Jazz Team ServerJazz Server ExtensionsWeb UILotusSametimeDB2/OracleJazz KernelEclipse EquinoxWebsphere23 2008 IBM CorporationExtend team collaboration to a broader range of users,from business to software professionalEclipse ClientsWeb ClientsMS.net Clients (future)IBM Desktop ClientsJazz Client ExtensionsWeb 2.0Visual Studio (Future)Rational Software ArchitectEclipse PlatformRational Systems DeveloperLotus MashupRational Application DeveloperEclipse PlatformRational Team ConcertBusiness PartnerClientsJazz Team ServerEclipse PlatformVisual Studio (Future)Lotus QuickR (Future)Tooling ExtensionsTooling ConnectorsMicrosoft Sharepoint (Future)24From the Eclipse Way to Jazz 2008 IBM Corporation12

IBM Rational SoftwareJazz in ActionUse Case: Broken Build 2008 IBM CorporationBroken Build rtReportProblem Report TriageProblem Report TriageCheck Problem ReportCheck Problem ReportFix BugFix dCheckCheckBuildBuildResultsResultsMark PR as ResolvedMark PR as Resolved26From the Eclipse Way to Jazz 2008 IBM Corporation13

IBM Rational SoftwareGuiding Principles 2008 IBM CorporationCollaboration - Team First Explicit team structure and roles– Contributor can belong to more than one team Team awareness––––event feeds per teampresence indicationworkloadchat in context Team autonomy––––28From the Eclipse Way to Jazzteam owns its processteam owns componentsteam has its plansteam has its build 2008 IBM Corporation14

Process Awareness Jazz is Process neutral–Support many different practices and processes Tool understands how a team works.Process is Specific – to the project– to the team– to the current milestone phase– to the assigned roles Process controls how the tools behave29 2008 IBM CorporationProcess Awareness (Cont) Process must be highly tweakable to be tolerable–––Reactive, not controllingNon-intrusive: only when requiredHelpful: self-explaining, quick fixes Reduce team member mistakes Free the team members minds30From the Eclipse Way to Jazz 2008 IBM Corporation15

Traceability over Work Items Automatic linking .31 2008 IBM CorporationTraceability Builds A Build is a first-class object Build engine is “pluggable”:– Associated build results, tests– Full navigability to all artifacts contributingto a build, directly or indirectly– Jazz Build Engine,– CruiseControl,– BuildForge,– Maven (incubator) 32From the Eclipse Way to Jazz 2008 IBM Corporation16

Transparency in PlanningKnowing what is going on without having to ask! Integrates planning with execution Easily see what needs to be done, what is being worked Real-time window on project tdevelopmentwork.work.Alwaysaccurate.Always accurate. 2008 IBM CorporationNo extra effort required to gather dataNo extra effort required to gather dataTransparency in Planning (Cont.) Providing visibility into the progress of development efforts outside of the team34From the Eclipse Way to Jazz 2008 IBM Corporation17