|
Next ARCAD Breakfast
Seminar
This breakfast
is addressed at those of you who are faced with modernizing
iSeries applications and would like to look further than
just modernizing the interface.
Our approach is to
build on your expertise so that you can make your technical choices
in the best conditions, in order to
:
Obtain
a clear and precise view of the existing application,
Retain the stability of your Information System
despite its major migration,
Retain the homogeneity and productivity of your teams,
Handle any increase in complexity.
During this session we will look at an overview of the subject and
several critical points :
-Your questions : Which new technology? To which goal? For what timeframe?
-The different stages in the modernization process ranging from an audit
of the existing application to the
definition
of a common methodology for development management.
- Demonstrations of the various ARCAD Software suites, with concrete
case studies.
To find out
more about our migration consultancy strategy don't miss our next breakfast
demo to be held in May 2005.
Subscribe to this session by clicking
here:
On-line subscription
|
|
Application modernization is a vast subject. Everyone
knows that the choice
of change strategy taken now will determine the successful operation
if the company's information system for the next decade
at least. To add to the confusion and uncertainty of the period,
there is a plethora of different routes to take. As a starting point,
we will present a panorama of the subject based on
our experience in the field.
A budget issue :
Of course, as always, money is a deciding factor. Somewhere in between
the company that makes do with a few tools offered by IBM and the
company that will entirely redevelop its information system in Java,
there is a barrier called investment capacity. One thing is certain
however, that those who decline to modernize in some way are heading
for trouble.
Modernization of the user interface
:
Many iSeries customers choose to stay within this boundary.
It has one enormous advantage, that of retaining the existing application.
Economical,
it brings immediate results. And the disadvantages? A man-machine interface
that does not really adhere
to the accepted standards for a graphical interface. Most products let
you to compensate for this with add-ons. But then the additional dependency
links between
software components can cause problems -
though in a rigorous organization, they can be overcome. Another drawback
: the
inbuilt
limitations
of existing
applications; a
program
that is
over-complex, difficult to maintain and/or undocumented will stay that
way, and continue to drain resources.
Other modernizations :
Spool file mapping tools play an obvious role in application modernization.
In the same way, for that matter,
as :
-EAI tools that standardize inter-application exchanges,
-Reporting tools that avoid the need to write interminable
report programs,
-Portal tools that homogenize applications and avoid
maintaining menu managers .
Knowledge of the existing
application :
This is really the fundamental issue that every enterprise is confronted
with. Sooner or later new resources will be brought in to work on the
information system. They will all need one basic raw material called
documentation.
Modernization of RPG code :
It is not because we have our eyes on new technology
that we should forget good old RPG that over the years has regularly
rejuvenated itself, until today it has the main characteristics
of a modern
language. And by that we don't just mean more readable code. To have
fully modular code, for example, the
ILE1 variant is
indispensable. In this domain, tools such as RPG
Toolbox from Linoma Software can help achieve a rapid and in-depth
migration.
Java :
To go for Java or not? That's the quasi-existential question asked
by many CTOs. Is IBM not feeding us yet another feature likely to be dropped
in a few years? The answer this time is a resounding no. In the same way
as COBOL or RPG are perennial languages, Java has already taken a massive
share of the computing arena.
Born along with the Internet revolution, its growth will follow along with
the offshoot movement. It is already the default standard
for migration and the open source community.
.Net :
“ If you don't do Java, you'll do
.net ”. This statement may be an implacable simplification (a common fault
in this business), but this doesn't make it any less true.
To start off with new technology, you need to look a long way ahead. That
is why in general the major standards are favored. .Net is of course one
of
these
standards. And to answer the question “.net or
not .net ” you just need to ask yourself : “For or against
Microsoft ? ” .
CASE tools :
CASE tools from the iSeries or PC world are still relevant
in this context of technological change. One single and unique language
for everything,
who hasn't dreamt of that ? The only shadow on the horizon is, we are a
long way from these famous “standards” like Java and .net.
The need to systematically pass new recruits through a training session
is dissuasive.
Java CASE tools are starting to make their presence felt, as could
be expected. The only criticism we could level for now is their relative
lack of maturity.
Modernization of organisations :
How can we modernize applications if we are not immersed in a modern environment
? Over and above the choice of languages and architectures, it is more
a real organizational reform that is needed. And this is where tools
such
as ARCAD-Skipper play a decisive role.
ARCAD-Skipper will federate the various teams working in heterogeneous
technical environments while guaranteeing overall consistency and
integrity.
Conclusion :
IBM has prepared the ground with its “IBM Developer Roadmap” document.
This is a good entry point
for forming an opinion. Beyond that, each enterprise is unique.
The choices will always depend on the context, but the key
is to move forward.
1ILE : Integrated Langage
Environment
|
