This chapter provides a roadmap, walking through each phase (inception, elaboration,

construction, and transition) of a typical System z development project.

This chapter provides the process essentials: A brief definition of each project phase

(inception, elaboration, construction, and transition) in terms of the main goals, activities, and

milestones. For each activity, the chapter lists the corresponding key roles, tasks, output work

products, and available examples from the Catalog Manager case study. The corresponding

section of the RUP for System z Web site provides advanced System z practitioners with all

the links necessary to perform specific activities or tasks.

This chapter describes the RUP for System z process from an end-to-end lifecycle

perspective. The end-to-end lifecycle can be used as a template for planning and running a

project. It provides a complete model with predefined phases, iterations, activities, and tasks.

The RUP for System z includes a large number of content elements (roles, tasks, and

artifacts). Most of these elements come from the Rational Unified Process (RUP) and its

Service-Oriented Architecture (SOA) extension. However, some content elements have been

added to the RUP for System z because they are specific to the System z environment. This

chapter presents these new content elements.

It is common knowledge that the use of a new technology is best shown by real working

examples. In this chapter, you will find a real-life case study as an example of how we put

RUP for System z into practice. The case study walks you through our development of a

COBOL CICS application, showing you actual work products and deliverables at various

levels of incremental progress and achievement, as derived during the different phases and

iterations of the method. Reading this chapter will allow you to visualize how RUP for System

z can be put into practice during application development projects in your own organization.

This chapter introduces the Enterprise Generation Language (EGL) and the value that this

programming language can bring to you and your organization. EGL is a high-level

procedural language that developers unfamiliar to Java™ can use to quickly develop Web,

TUI, and batch applications with data-driven business logic. EGL can also be used to

generate COBOL for your System z. EGL was designed for developers who need to focus on

the business logic of an application rather than the technology or platform on which the

application needs to run. The result is higher productivity. We used EGL in this IBM

Redbooks publication project to develop a Web client application that consumes COBOL

CICS Web Services.

The RUP for System z includes a Work Breakdown Structure that covers the whole

development lifecycle from beginning to end. This Work Breakdown Structure can be used as

a template for planning and running a project. This chapter presents the Work Breakdown

Structure for each project phase (inception, elaboration, construction, and transition).

Download : www.redbooks.ibm.com/redbooks/pdfs/sg247362.pdf