RTCp enables collaborative application development on System i. Combine multiple version control systems into one wether it be RPG, COBOL, Java, .NET, or C++. Execute build and promotion from a centralized interface, move to iterative development planning,and keep track of tasks and defects with work item tracking. View the whole project scope from a central dashboard.
Unraveling Multimodality with Large Language Models.pdf
Rational Team Concertfor Power Customer Presentation02 09 10
1. Rational Team Concert for Power Systems Software V2.0 Collaborative Application Lifecycle Management for IBM Power Systems
2. Power = i + p Power Systems family System i family (AS/400, iSeries) System p family (pSeries) Unified Hardware & Virtualization Technologies
3. Rational’s Value for Power Systems Extend the software stack with Power Tools Common developer desktop across operating systems and languages Compilers Exploit the hardware with compilers, especially in multi-core & parallel environments Common development infrastructure for Power and the world around Power
4.
5.
6.
7. Easily extend and automate short iteration cycles to meet hot business needs Top down and the low level views linking configuration, bug and cost tracking Project status and cost analysis anytime for all business sponsors Easy triggers to catch licensing issues early Onboard team members across the world across projects in a day not months Seamless access to highest risks and security vulnerabilities Agile work flows automating and smoothing execution Empower team members to collaborate using up to date information “in context” of the work they are doing Automated synchronization of project artifacts Customer Speak : What they would like to see possible CIO Project Manager Developer Legal Counsel Compliance Officer QA Manager
8.
9.
10.
11. Query Storage Collaboration Discovery Administration: Users, projects, process JAZZ SERVICES Business Partner Extensions Your Extensions Rational Developer for z Rational Software Architect Rational Systems Developer Rational Business Developer Rational Developer for Power Eclipse Clients Web Clients Visual Studio Microsoft .NET Clients Rational Desktop Clients Rational Team Concert Web 2.0 Jazz Client Extensions Eclipse Platform IBM Rational Extensions Best Practices Presentation: Mashups Rational Team Concert: An open, extensible architecture Supporting a broad range of desktop clients, IDE’s and languages
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22. To learn more visit: ibm.com/software/rational/announce/modernization
23.
24.
Notes de l'éditeur
What’s New:
What’s New: IBM plans to add C/C++ and COBOL development tools for AIX to the Ra- Rational Developer for Power family in the future, extending the benefits of having an integrated Eclipse development environment to teams devel- oping C/C++ and COBOL applications for AIX. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. The information in this statement is intended to outline our gen- 1 eral product direction and it should not be relied on in making a pur- 1 chasing decision. 1 The information in this statement is for informational purposes only and may not be incorporated into any contract. The information in this statement is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and tim- ing of any features or functionality described for our products remains at our sole discretion.
Here we see the open nature of Rational Team Concert, we provide a broad range of desktop clients that can all talk to the same Rational Team Concert server providing an unprecedented level of breadth and support for software delivery teams. We also provide extensions to increase the scope of Rational Team Concert services and adapters to enable your organization to connect and leverage existing investments such as ClearCase, ClearQuest, or even Open Source Subversion. Moreover, with the open standard called Open Collaboration Lifecycle other vendors can build complementary solutions or their own standalone solution.
Jazz is… A scalable, extensible team collaboration platform A community at Jazz.net where you can see Jazz-based products being built Our vision of the future of systems and software delivery, supporting globally distributed teams An integration architecture enabling mashups and non-jazz based products to participate An evolution of our portfolio which will evolve to leverage Jazz technology over time
What is different about Collaborative ALM solution with RTC and Jazz? You can think about the key differentiator of RTC and Jazz using this analogy: RTC and Jazz are affecting the application development/lifecycle management process similar to what SOA, ESB and Process Servers did for the enterprise application integration and the business process management. Think of point-to-point enterprise applications integration vs. ESB-based integration. RTC and Jazz in addition to providing core ALM functions (boxes in the upper side of the diagram) and common services (listed on the bottom) deliver open and extensible integration platform for the ALM process including integration of the tools and enhanced collaboration of the team members using the tools. The diagrams on this slide are logical, not physical. An example of ALM Solution before RTC and Jazz is based on integration of “point products”, often from different vendors: Complex: To collaborate “Tool A” must know about “Tool B” and vise versa; the users must know multiple tools Integrate a new tool means understanding “Tool A” & “Tool B” and updating A and B to understand “Tool C”… It gets more complex with each tool added to the solution Rigid and brittle Each tool has its own repository, Each tool has its own proprietary API that can change with the next version, so the integrations can easily break If there are many vendors supplying ALM components, who is responsible for the overall solution? Unproductive: The users have to use many tools and different UIs in order to accomplish their tasks The RTC/Jazz diagram is logical. Physically, each RTC function listed on the diagram has server and client components. RTC server contains Jazz Team Server. Jazz Team Server (JTS) implements Jazz Foundation Services (JFS) that realize common services such as discovery, query, admin, storage, etc. – the services that are used by RTC and other Jazz-based products. All services have REST APIs (URL-addressable, over HTTP, using XML payloads). Open Services for Lifecycle Collaboration is an open standard specification and its implementation as part of Jazz Team Server. Another commonly used term is Jazz Integration Architecture (JIA): REST web services for the JFS (for the client-server communication and integration of products built on top of JTS) + REST OSLC domain-specific services (e.g., services to integrate requirements and design artifacts). RTC for Power v2.0 brings RTC capabilities on IBM i and AIX to functional parity with the RTC v2.0 delivered for other platforms. Key features of RTC Seamless collaboration for the ALM tools and for the team(s) Common centralized repository for all artifacts, high information fidelity (data and metadata) passed between core ALM functions due to use of the same data and XML schema for describing all ALM artifacts REST APIs for common Jazz Foundation Services REST APIs for OSLC – for integrating with other ALM tools Single collaborative development infrastructure across all Power operating systems that: Fosters team collaboration by integrating collaboration functions in each role UI and by incorporating best practices process guidance Integrates release planning, reporting, work items (tasks, requirements, issue, etc.), source code management, builds, Common repository for all application development artifacts delivers complete information fidelity (data and metadata) between core ALM functions and ALM phases due to use of the same data and XML schema for describing all ALM artifacts and their associations. For example, it is easy to associate new code submitted to the code repository with the work item (e.g., issue). It is also easy to require such association by using Team Advisor (which is part of the automated governance feature – next) Automates governance Process control and guidance Project status through metrics and reporting Improves auditability for development process via tracking all development artifacts, their associations and events (e.g., builds) in common repositories Agile planning tools with easy estimation, project status tracking with reporting, customizable queries and dashboards Improves developer productivity by adding in-context collaboration with the team in the IDE My tasks, dashboards, instant messaging with advanced, real-time notifications from the build system, etc. Unifies heterogeneous teams working in a broad range of programming languages and platforms Supports Java, IBM i, AIX, .NET, PHP, EGL, HATS, and System z developer coexistence Is ideally suited for geographically distributed development teams because it utilizes REST APIs for communication between the developer IDE and Web browser clients and the server Takes advantage of enterprise level scalability, performance and reliability of the Power platform Can provide a consolidated enterprise ALM for many development teams across all enterprise platforms and geographic locations
To learn more visit the new launch page to learn more about the new offerings, collateral, case studies, demos, papers and download trials. Visit: ibm.com/software/rational/announce/modernization
Small Icon in bottom right is a link to the Rational Cafés landing page