© 2014 IBM Corporation

2434A, Improving Your Time to Value with Rational System z Development SolutionsScott Pecnik, PacGenesis

Please noteIBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

3

Essential Ingredients

The right tools

Goals and planning

Expert training

Specialists

Image courtesy of adamr / FreeDigitalPhotos.net

Image courtesy of stockimages / FreeDigitalPhotos.net

Image courtesy of sheelamohan / FreeDigitalPhotos.net

4

• Clear goals and planning- Transforming development at a large financial institution, Scott Pecnik, PacGenesis

• Expert Guidance- High quality C/C++ applications at a mainframe shop, Kenny Smith, Strongback

• Artisanal finishing– Extending RDz for use with Panvalet, Ravikanth Chavali and

Anand Vijay, Royal Cyber– Meeting compliance requirements for vendor code with RDz and

Endevor, Paul Pilotto, ASIST

Agenda

Clear Goals and PlanningScott Pecnik, PacGenesis

5

6

WhyFrom... To...

Limited transparency into resource usage, quality and project delivery

Improved management, visibility, and quality assurance of projects and teams (including offshore resources), with better estimating, tracking, and reporting

Non-integrated development toolset, requiring developers to jump between tools

Integrated toolset through single window interface across functional areas (build, test, defect management)

Relatively rigid waterfall approach to developing software

Support for Agile and hybrid SDLC methodologies in addition to traditional approaches

Limited adoption of modern development practices, such as Continuous Integration

Deployment of continuous integration capabilities

7

How

Change

People

Pro

cess

Technology

8

What

Manual Integration via Custom RTC Extension

Automated Integration (REXX and CMAN XML APIs)

What’s Next?

From RTC to Existing Build and Deploy System

9

What

Manual Integration via Custom RTC ExtensionDeveloper Manually Stages into CMAN

10

What

Automated Integration (REXX and CMAN XML APIs) No Developer Impact

11

What

What’s Next?Native RTC Build/Compile