EMA z
pa a a.
teči r

NA, a kani

mih ME. MRI
nape jem k — le

formation reguired for complete CASE
development, such as that:stored in the
CASE Encyclopedia of Texas Instru-
ments' Information Engineering Facility
or KnowledgeWare:s Information Engi:
neering Workbench. IBM is working in-
tensively to expand its current Reposi:
tory design so that it will eventually
provide all the facilities reguired by
powertful, high-end CASE tools.
One of the more pivotal consider-
ations is compatibility with the ESF.
Currently, CSP/AD runs as a develop-
ment, tool only on S/370 mainframes.
However, it. generates code that can be
executed on AS/400 midrange machines
and PCs. IBM has announced that

Second of a
series of articles
on the IBM Re-
pository, a sig:
nificani compo-
nent of IBM s
applicatons-de-
velopment strat-

egy for the

19905.

The IBM Re-
pository, an:
nounced last
month, establish-
es a common
standard for de-

siju speci(ications generated by comput:

er aided software engineering (CASE)
products and olher development tools.
As deseribed in last week's article, the
Repository represents a critical compo-
nent of AD/Cycle, which provides a
standard development environment
within IBM s Systems Application Archi-
aeetare (SAA).

- Users demand an open software-devel-

opiment environment in which tools.

from many vendors can be used inter-
a chanjeably, sharing, specifications from
a cammon repository of design informa-.

jan. lu defining a repository standard,
Jim is SSAA a NAjOD sei Dano PARTI

z majiki
461 da ; peY— skri iz
ka W 4 h m- jasi tret.

s ka poi ee |

|. SAA
|/ Cormon

User

v an Opem.so!
ir) ki meni h moiiš izniči, Prix ;
Many venidors of software- devElEe
ment tools claim compliance with IBM s
Ap lication-development standards; still,
is important to determine the level of
commitment that the vendor intends to
make to the standard.

As (he figure shows, there are al least
four levels of compatibility with the
AD/Cvele standard for an applications
development environment standard:

" Compliance with CUA. Entails sup:

Le ah A. oni, x;
ge snu givi cos o vu Mi k

| port for a common user interlace for all
applications, using the Conimon User
k —.— Kecess services specified by SAA.

Pe " Compliance with AD/Cyele. Entails

| — use ola conunon standard for design
specificalions, as defined by (he
AD/Oyele Repository.

"" Compliance with External Source

— Format (ESF). ESF is an IBM specifica-
odlen D alEnaje used to import/export. de-
— sij specifications from front-end CASE
nodi go s to Cross System Product/Applica-
Z ima Development (OSP/AD), the desig

nicat on in- ine v K m 3 wil be JADE on
rovid- — he Tat. workstation in June 1990 as an.

Ono System Product kila; enables
— third. m y y vendor tools Ja. gonveci min

A a Ja ore
pala NE ae a. odi
k vi reče, ae JE

tm

aa a AA TT:

Pojma f

— eralor, it will be Poš Sa .- ne

die bid

cations-development tools and applica-

tion models. ESF can be used within an
integrated project-support environment
to import/export design specifications to
a variety of library and configuration-
management, tools.

To date, several vendors of applica-
tions-development, tools have announced
ESF support, including Index Technolo-
sy Corp., KnowledgeWare Ine., Mel)on:
nell Douglas Corp., Nastec Corp., S jage
Software Inc. and Texas Instruments
ne. These vendors are committed to
producing an ESF tag language to inter-
face with CSP/AD.

When CSP/AD version 3 is avajlable
on the PS/2 as an SAA Mihi gen-

Four Ways To Comply with Ab/cyele

Softivare Developinent Tools May Be
Conipritible ovit OHe vi: More Eleiments

l

L

IBM's Repository will make it possible to use CASE tools
from different CASE vendors, all of which interact
with a common knowledge base of design information.

- cutable code for all SAA iji: ronn a,
o in iroi Tole Une, GA NI
sion la mecha-
nism of ESFE. 2:
A vendor might decide not to use |
— OSP/AD as the code generator becnuse
z there are notne spoljcakorenakiina -

ri
ia LI 1 a "4 ui ri ri ui
a h :y a do SE
k it č kesi| IA
me JE Bb h — Ja i
J um A i B g P
a, č m s da
Y | nei k a arij
4 nt, z -
F ! - u "ii
ze z" A a a
oa seči zi! nI j
- ; i i
— due k ki Kaki j
mad ir nila, - Mae
nuj ka 4 a, ba
z 4
a a DA il
1. š s č - ; -
š z jo k zili odet ma)
— J zrači šu
aj si ji - - zi
ja ž k NA a
ne la
4 .- smem a P mamiš m
ba; ; ne
L 1 m
| sk ič h
K čji —— | A PA J a a
: Re pa zaje ze
č 1E [a Baja Mi uta
fine ; ote k z
l gi 5 ei j
Š i KL -
di f sz x
a i pg
kse i
"gi

| koe -4

processiny, associated with objects in the

ČTIN ne
all of the objecis (hat are specified by a |
CASE tool —entities, relationships, data | K
models, process models, normal ized da-

fined in the form of a normalized rela-
tional database.

h applications Building a comp

development environment. š

| for CASE based. on oa nosi peri -

IM kd k

ository Opens Door to Standard Design

Repository standard, obey SAA stan:

dards and create code thats portable

within SAA environments.

Many users view the introduction of

the IBM Repository and the AD/Cyele
applications-development environment |
as the first steps toward the develop:
ment of a software-backplane capability.
The objective of a software backplane IS
one of enabling users to select a variety
of compatible front-end analysis and de-
sign tools, code generators, project-man-
agement facilities and other support
tools that share design information (rom
a common Repository.

A hardware backplane is based on the
concept of plugging standardized hard
ware modules into a common backplane
structure. Similarly, a software
backplane uses the concept of plugging
standardized software modules into a
common design database. However, the
database needs to store more than just

design information; it needs to be a
knowledge base containing all the rule

a

a
Pn
— —

database. The design repository. shock
be an object-oriented database that.

Size m

h k Pa

Pa pa LE NOE kri
mi Ma

 stores both data ; and rules. 1 If Call JE vet nd dors

dr ni,

AI A a
o a 0
aa ?

pie hm: a Tem č dafiini! j Roš agrarnih Maia šča leusiji zi eš ulite
NOS fUaY čontains delDUUOUŠ O

abase sehemes, procedural code. The
attributes of these objects are then de-

Next, the rules that must be obeyed

by all of the objects and attr ibutes are
defined. 'Fhe database provides the

structure of a software backplane. In
this way, it will be possible to use CASE
tools from different CASE vendors, all
of which interact with a common
knowledge base of design information.
There will be a diversity of ideas [rom
different vendors and a wide range of
views on what constitutes the most
powerful tools; however, the tools must
be portable, they must, interconnect, and
they must have integration down the
value train across the corporation. One - (|
application in the value train might be: čiji —
built with one tool; a different applica- |
tion might be built. with another tool. —
[lowever, the tools must ako across

pa

oration reguir

i dd i mm ia k kai m
sh xi
masi nč; nu see DNEH žag jeič
x po sa H i -
well a ful T ke
S, as as D 1d beč

B 4E3 —. z vo ) zb al]
Pali nj io ek ae a A,

teči LIN EI] VE NE aa Taj a kečki (

- 4 FE M niki rala 7 Paka
s H kaj! A gala k . k. )
x dd BE, s, 1

4 x
y si; psi
s sata m

d.o a Zlže ORLE, A
če s Dasi
j zni
š e 1
ja Mei ii AS Re PR me
. nea ui ji Meka 3 ibiskai čet na
» - "a. E po ali hi. ,
1 ".i
moi JI —..

RIŠE
pe
st
nl
ga
či tie
r Uši Ja
zi pa
Tm
z 1
ai
d Ri
m"
JE.
eo
TE
m o SAL pa
de ite
ii bolnik teli
ui? ih JA
i Mi: kej si s
: a z.
ž sa rea ad
kačji je a 17% Na
pe kkz-e pra ger ate
V z?jin, zi Izi
— sist
a E-. j a
puša
h dua
č pe