enih in a series
on rapid appli-
cations develop-
ment (RAD), a
methodology de-
signed to give
much faster re-
sults than the
traditional life
cycle.

The RAD life
cycle is attrac-
tive because it,
can be used to
develop complex,

high-guality applications within tight
budget and time constraints. The life-cy-
cle process incorporates significant im-
provements in the use of personnel,
(ools, development methodology and
management technigues.

RAD is based on the use of Joint Ap-
plication Design (JAD) workshops, inte-
imated computer-nided software engi-?
neering (-CASE) tools, small teams of
highly trained analysts, a development,
methodology that defines the steps re:
uired to achieve high speed develop-
inent, and management technigues
aimed at cutting through bureaucratic
obstacles. The RAD life cycle integrates
(hese familiar concepts and provides a
proven framework for developing appli-
cations much faster.

As shown in the figure, the RAD life
cyele has four phases: reguirements
planning, user design, construction and
cutover.

Workshops are used in the reguire-
ments-planning and user-design phases
to involve executives and end users in
the specification process. The workshops
provide a highly structured environment,
in which small teams of end users and
analysis work together to define re-
auirements and design the system from
he user's perspective. I-CASE tools are
used to capture and analyze design
specifications for the application.

During the construction phase, a team
of analysts, highly trained in the use of
the CASE tool, develops a prototype of
the application in close communication
with end users. The prototype evolves
into the final production system within
a tightly constrained time frame. Cut:
over of the production system reguires
close interaction between end users and
information-systems (IS) analysts.

Each phase should be approved by
the user execulive who's spending the
money. This is the executive owner, as
shown in the figure. i

'The reguirements-planning phase re-
guires that, high-level or knowledgeable
end users determine the functions of the
system. These planning functions are
performed with the guidance of IS pro-
fessionals. Reguirements planning is usu-
ally best done in a workshop with well-
structured procedures.

Key executives and users are selected

to participate in workshops in which a
reguirements document is created. The
workshop progresses through a planned
set of steps under the guidance of a
skilled Joint Reguirements Planning
ČIRP) leader, who is usually the same
leader who will conduct a follow-on

Complex RAD Cycle Can Be Distilled

JAD session, as described below. '

At the start of the workshop, the us-:
TS are encouraged to do most of the
talking. IS professionals transfer the end
users reguirements to the CASE tool's
repository and attempt to create a prag-
matic representation'of system func-
tions that will make the system as valu-
able as possible. ;

The user-design phase reguires that
end users participate strongly in the
non-technical design of the system under
the guidance of IS professionals. User
design is done in a JAD workshop simi-
lar to the JRP workshop.

JAD is a technigue for harnessing end
users in the reguirements analysis,

ses of
sh e RAD Life Cycle —

bilities:

Executive Ownef Hesponsik
(ive abproval tor plarining j
NU Bedilirements-

|
; Heview plans nee

provel for uset desigti |
funds

li Give ap
s Release

i e
VRE

s givea
v Re!

ijser Desig

ži

SP panji
are created. Parti important in |
the RAD life cycle, the design is created,
in the repository of an I'CASE tool that
coordinates the design. with other infor.
mation in the repository. The resulting ..
design can be used directly in the con:
struction phase. As much as possible,
the IS staff attempts to reuse existing
data and process modules contained in
the repository of the IECASE tool. /

For a smooth transition, some of the
users in the planning workshop should
be involved in the design workshop.

In these first two phases, application
users and user executives should play a
larger role than IS professionals. Plan-
ning and user design should be done, to

ENE!
bhasoh ot Personnel
. pha
eveloprnent Joint
; , Regulremenis
| Planning

z Team

ubini ri
appličato
8 pesigni Team
: sirletion

jjser Review :

Uset rd

V r
cutove!
Tedm

te tale mi

Workshops provide a highliy structured environment in which.

end users and analjysts work together to define reguirements
and design the system Jfrom the user'S perspective. ji

specification and design of systems. It is
a highly successful technigue when used
correctly, resulting in high-guality design
being created rapidly. Key end users are
selected to participate in workshops in |
,which the preliminary design of the sys:
tem is created. The workshops progress
through a planned set of steps, defined
by the methodology. '

As in the JRP workshop, the users are
encouraged to do most of the talking,
'The IS staff in the session translates
what the users want into structured
specifications and design.

Along with the specifications, the rele-
vant data model, screen designs, report.
designs and, possibly, rough prototypes

ši

f
Hi
|
i

; VEL determine if the user understands the (|.
EIN PRE S 2", | operation of the system, refining the |
a large extent, by users, with IS provid-; training materials and help screens, and
ing firm guidance. | 3. 306% 46!' | | conducting further training courses. .
(| The users do not sign off on specifica-. , Next week, I will discuss the key play-
ora Ines ko epi 4 ma dag ers in the RAD life cycle.a k

resented in an "CASE tool, which v i
vl be ke rec no he ote The concepts embodied in RAD are de-
tion phase, The executive owner of the. | seribed in a new volume in the James' —
system releases funds for its construc' / Maria Repori Seriex Kor more lafoti
tion on the basis of a review.of the l:: | mation on this volume, cal |
CASE design. '// zo 44% |, (800) 242.1240. For information on |

In the traditional development life cy-. semšnare, please cončaci (ta tka Unit
cle, detailed design is a separate phase |. ed States and Canada) Technology. |

from programming. First, specifications
are written, then detailed design is done,
then the code is written and, finally, the
code is debugged. REF

The RAD life cycle changes the rela:

to Man

; During the RAD construction phase,"

" ments planning phase and detailed prep-

FEBRUARY 5, 1990

geable Phases
A EN ETE NU

CASE tool, and code is automatically '
generated from it. J

IS professionals perform the detailed de-
sign and automatic code generation of
one transaction after another, using the
I CASE tool set. They may show each ..
transaction, as it is built, to end users
and make adjustments to it. The com- .
puterized coordination of the ICASE

tool set integrates the separate trans-,
actions.

End users are closely involved during
the construction phase. They validate
the sereens and design of each transac-
tion as it is built.

Construction proceeds guickly with
ongoing user involvement to ensure that
the delivered product meets the needs
of the users when it is cut over. There
should be no surprises for the users
when the system is installed, because
they have participated in every step of
its construction. | ie

The I-CASE tool set should generate
the coded database descriptions, as well
as executable program code. It should .
also generate technical documentation,
thus ensuring that the documentation
precisely describes the generated system.
A final stage of the construction
phase may be to perform database opti-
mization and use a code optimizer to en-
hance the run:time performance of the
' code. When this is done, good code gen:
erators give about the same run-time |
performance as skilled programmers. |
3
The Cutover Phase ul:
When the system is cut over, a vari-
ety of actions are needed, including com-
prehensive testing, end-user training, or-
ganizational changes and tandem opera-
tion of the new and old systems until / '
the new one settles in. ;
'. Because the construction phase is rel:
atively rapid, planning and preparation
for cutover must begin early. Prelimi- |
nary planning is done in the reguire- "

aration is begun in the user-designn —
phase. % il nati
Steps to prepare for cutover include

developing the conversion system, per:
forming a guality audit, preparing for fi-
nal testing, building the test libraries, |
Carrying out the final testing, ii
documenting the test results, planning kO
and conducting the training program,
evaluating the success of the training to |

Transfer Institute, 741 10ih St, Santa,
Monica, Culf. 90409 (218) 3918905.
In Europe, contact Savant, 2 New St.
Carnforth, Lancs., LA5 9BX United ,
Kingdom (0524) 734 505. j