MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
Software Development Lifecycle
52
The software development lifecycle is highly involved and has many variables. Accordingly,
only the steps in the software development lifecycle applicable to problems encountered in
multi-platform development and deployment are discussed herein. The software
development lifecycle is described in more detail in “Managing the Physical Movement of
Objects” on page 54.
Many multi-platform development models are possible. Some examples of the types of
development and deployment are as follows:
development object (such as static Web content (HTML, GIF)) is deployed using the
iSeries as the target Web server
development object is one-to-one with the release object, such as for server Java
development
client Java development, for example, Implementer Capability Wizard
client Visual Basic development (an application, such as MKS Integrity, accesses an
OS/400 database)
client C/C ++ development
any application using a SETUP.EXE executable
a proprietary development and deployment model (for example, PeopleSoft World)
Another way to look at the various development environments is to look at several of the
metrics that apply to all development types. Each environment has varying degrees of
change being made during development through to the final object being placed in
production. The metrics to consider are as follows:
Degree of Transformation
Between Development and
Production
Same (HTML, OCL)
One to one (RPG, Java)
One to many (C, dll, JAR
(Java Archive), *SRVPGM
One to many several times
(SETUP.EXE)
The development process can involve many users and many roles. The major roles of interest
in multi-platform development and deployment are:
developer
builder (the buildmaster) of the release object
Deployment Environments Execution Locations
Native RPG
Java programs
Application server
Web server
Visual Basic applications
Open environment (servlets)
Proprietary environments
Server
Client
Client (served from server)