D-i4i 999 THE APPLICATI ON OF A GENERAL PURPOSE DATA BASE 1/2MANAGEMENT SYSTEM TO DESIGN AUTOMATION(U) NAVALPOSTGRADUATE SCHOOL MONTEREY CR H J WALDEN DEC 83

UNCLASSIFIED F/G 9/2 NL

'EEEEEohEoEEEmhhEEEEohEEEEEEhEEEEEEEEEEEEmomEEEmEEEEEEEE//l/lEEEl/EEEIIEEIIIEEEEI

0,- ..

J1.

11111.2

NAINL-RA O TNAO 1963 A

NAVAL POSTGRADUATE SCHOOL 7Monterey, California

DTIC& ELECTE.JUN 1 11984j

THESISTHE APPLICAT:-ON OF A GENERAL PURPOSE1

DATA BASE MA, NAGEMENT SYSTEMTO DESIGN AUTOMA.TITON

by.

Heather J. Walden

LL.5 December 1983S

T- 'hesi*s Advisor: A. A. Rcss

Approved for, pub'Li*c release, distributiLor unlimi-'ted

84 06 I 9

0S .96T'Vt

-.. .. ... .- - -*.. 7 -77 7,0-

SCCUSTV CLAMPICAT11011 OF THIS PAGE (When Do&a Enteredl)______________

REPOT DCUMNTATON AGEREAD DNSTRUCTIONS_____ REIM______________________PAGE__ BEFORECOMPLETINGFORM

1. WIPONT NUM11111 L ;VT ACCCSSION; NO . RECIPIENT'S CATALOG NUM1SERf

4. TITLZ (OE WMD S. TYPE OF REPORT & PERIOD COVERED

The Application of a General Purpoe MsrsThisData Base Management System to Design December 1983Automation 6. PERFORMING ORG. REPORT NUMBER

7. AUTHOWS) 6. CONTRACiT OR GRANT NUMSER()

Heather J. Walden

9.r ON191000MIMG ORGANIZATION NAME Awe ALORSS 0.PROGRAM ELEMENT PROJECT, TASKAREA & WORK UNIT NUMUERS

Naval Postgraduate SchoolMonterey, California 93943

ICONTROLLING OFFICE MNM AND ACORESS 12. REPORT DATE

Naval Postgraduate SchoolDembr18413. NUMIUER OF PAGES

Monterey, California 9394315

14. MO1KNITORING AGENCY NAME A AOORSS(II diftew., &Ma CMO1ireld Office) 1S. SECURITY CLASS. (of this report)

UNCLASSIFIED

S.. DECLASSIFICATION/ DOWNGRADINGSCHEDULE

16. DISTPHOUTION STATEMENT (ofdu no""h)et

Approved for public release, distribution unlimited

17. D6ST1111UTION STATEMENT (of a.e abse~ ends in Aleaok O.It different from Report)

1S. SUPPLEMENTARY1 NOTES

19. KEY 00404 (Cetahw en fewse aide it noseacap and Idmntify by' bock nuother)

Computer-Aided Design, Oracle, General Purpose RelationalDBMS, Relational Model for a CAD System, Computer SystemDesign Environment (CSDE)

2L. AISTRACT (Costhwe en revese adds If nesooamy end identUify a, Week amober)

This thesis describes the analysis of the Computer SystemsDesign Environment data base requirements, the design of arelational model to fulfill those requirements and theimplementation of that model on a general purpose data basemanagement system. -

CC I A 71 7 COITION OF I NOV 66 I OSSOLETE1___________________S/N 0102- I.P. 014- 6601 SECURITY CLASSIFICATION Of THIS PAGE (When Owe fteer".

* ~ 7 -J - - J6 %Wp.' 477*4'-jy-*.T- . ~P* p7 J.

Approved for public release, distribution unlimited

The Application of a General PurposeData Base Management System

to Design Automation

by

Heather J. WaldenLieutenant, United States Navy

B.S., Penn State University, 1977

Submitted in partial fulfillment of therequirements for the degree of p

.|

MASTER OF SCIENCE IN COMPUTER SCIENCE

from the

NAVAL POSTGRADUATE SCHOOLDecember 1983

Author: )

Approved by:Thesis Advisor

L -/2> /. .. Second Reader

Chairman, Department of Computer Science

Dean of In o licy Sciences

2

* C .*. -. * . . .:-' * *

---- ,-.,,"--.-._---.--.-.-.'-, . . .. .'I

ABSTRACT

This thesis describes the analysis of the Computer

Systems Design Environment data base requirements, the

design of a relational model to fulfill those requirements

and the implementation of that model on a general purpose

data base management system.

~Acce -,ton For

INTI5 r) .r

IDTI t I T. 'Unr- - Sn

,- .I *" I/i,,_' A:, q ..

Dist ! "-"

.El!

- }'L3

TABLE OF CONTENTS

I. INTRODUCTION ------------------------------------- 5

II. PROBLEM DEFINITION ------------------------------- 8

III. DESIGN ------------------------------------------- 18

IV. IMPLEMENTATION----------------------------------- 50

V. CONCLUDING REMARKS ------------------------------- 61

APPENDIX A - CREATEDB UFI TABLES ----------------------- 65

APPENDIX B - INTERACTIVE APPLICATION GENERATORLISTING ----------------------------------- 69

LIST OF REFERENCES -------------------------------------- 148

BIBLIOGRAPHY -------------------------------------------- 149

INITIAL DISTRIBUTION LIST ------------------------------ 150

4 .

"6

- S.- .S T

,I_.

I. INTRODUCTION

The goal of this research was to determine the validity

of the hypothesis that a general purpose relational data

base management tool could be used to implement a computer

aided design (CAD) system, and, if found valid, to provide

the design of such a data base.

Computers have been used to aid in the design of a

great number of things, the most widely recognized being VLSI

chips. The design of VLSI chips is related to the purpose

of the work supported here. Its purpose is to incorporate

some previously defined function into VLSI technology. This

system, the Computer System Design Environment (CSDE),

instead of defining a new chip uses existing microprocessor

technology to devise a specific controller for a given

design problem. For instance, suppose one needs a microwave

oven controller. Given the performance parameters, this

system can design the software, hardware and interconnecticns

of a microprocessor system to perform this control. In

other words, this computer-aided design system is used to

map a functional specification to a microprocessor and its

associated software and peripherals. O

This thesis work is an extension of the work done by q

Alan Ross in his Ph.D. dissertation, "Computer Aided Design

a-I

S-.'

'a 'a - ' a .O

* . . . ..; F. 7 7 6 . 7 P... .. . .

of Microprocessor-Based Controlers', His dissertation

describes the demonstration of the feasability of automati-

cally designing microprocessor-based real-time systems.

-Briefly, his method was to: 1) create a problem statement

(functional specification), 2) translate it into an inter-

-.. mediate format, 3) select a microprocessor realization from

a library of realizations, 4) generate the software and the

hardware to implement the function on the chosen micropro-

'. cessor, 5) check the timing constraints and develop a

'.'- monitor and 6) output the design description. [Ref. 1)

One of the shortcomings of his work is an overly complex

-V implementation because he did not use an adequate data base

tool to support the library of microprocessor realizations.

His system maintained a 'data base' on formatted, IBM

punched cards. That method of storage is highly inflexible

and resistant to change. It was at best a bulky, awkward

way of storing and carrying around information. Times have

changed and with the aid of currently available data base

S management tools, new implementations can be considered.

One such new tool is Oracle: a general relational data

"- base management system. It is available on the Vax 11/780

.- ' under the VMS operating system and its command language is

SQL (pronounced sequel). A specific goal of this thesis was

. to identify Oraclets usefulness in designing a relational

-. model of the data base requirements of the CSDE,

6

r - I~r

-". ' X~ ",'N....... .*-*W -. I . , .. .

II. PROBLEM DEFINITION

In designing a data base for any system one must make a

careful and dedicated analysis of the system's requirements,

its overall function and its design features, Secondarily,

it is also necessary to discern the system's limitations

with respect to the availability of technological, funding

and manpower resources at the time of conception. It is

also a good idea to study the systemts goals for the future

and plan for extensibility. By doing this, one discovers

the data that is necessary for each function and the rele-

tionships the data have for each other. With this informa-

tion a data base schema can be drawn up that maximizes the

system's capabilities and performance. The system under

scrutiny here is a computer-aided design (CAD) system.

In general, a CAD system is required to automate a

certain function, whether it be the design and manufacture

of microprocessor ships or something totally unrelated to

the computer industry. One instance of a CAD system is the

Structured Computer Aided Logic Design (SCALD) system,

developed out of Lawrence Livermore Laboratories. It

operates by mapping the designer's. input text and graphics-

based instructions to a technology specific wire-wrap list

for processor board construction, In performing this

8

e% %1 %

% , "- a a ". )'"'"." " .-* •'. .- . .2 ,. . . . . . .<"- " • .--

mapping, the SCALD system frees the designer from mechanical,

repetitive tasks that are tedious and error prone for human

beings. It allows the designer to spend his/her time

creatively rather than robotically. [Ref. 2]

The function and operation of the CSDE is very similar

to the SCALD system. A design problem is entered into the

CSDE in the form of a high level language called the Computer

System Design Language (CSDL). The CSDE then attempts to map

the design criteria outlined in the CSDL to a specific

microprocessor system.

For the target system of this research, the Computer

System Design Environment (CSDE), the communication lines

between the data base and the rest of the CSDE system are

related in Figure 1. The user has access to the data base

for three operations: 1) to input a problem statement, 2) to

input microprocessor realizations and 3) to manipulate design

configurations.,-AU

For problem statement input, the user/designer interface

is based on a syntax directed editor (SDE) [Ref. 3].

The problem statement which is produced by the SDE includes

the following sections:

(1) identification section - contains user identification

and documents the problem for record keeping purposes.

(2) environment section - defines the interface between the

controller and the process to be controlled; lists the

external and internal variables which are defined for

the controller.9

Z""

4...' . . . .... . . . . . . . . . . . . . . . . .. . . .

USER

DATA BASE

PROBLEMSTATEMENT

INPUT

MICROPROCESSORREALIZATIONLIBRARY

FINALDESIGN

CONFIGURATION

TRANS LATED ITABLES -FORMATTER

ENVIRONMENT FUNCTIONALDESIGN CRIT. MAPPERID OPTIIZERPRMTIV LST tTIMING REALIZATION

TIMING

TABLEG MONITOR

Figure 1 Original CSDE Layout

FL

(3) contingency list - list of the contingencies (stimuli

the controller must respond to) and tasks (controller

responses) and their time constraints.

(4) procedures section - details the routines which define

the contingency/task pairs,

An example of a problem statement input for a fuel

injection controller is shown in Figure 2 [Ref. 4].

In the design of the current system as shown in Figure 1,

a Translator uses the information in the format above to

create a primitive list and a symbol table which are used by

the Functional Mapper. The Translator is not yet designed

but is an ongoing development in the CSDE project. The

primitive list is developed from the contingency list and

procedures section of the problem input statement. The

symbol table contains the attributes for the variables in the

environment table. The Functional Mapper tries to find the

software and hardware macros listed in the primitive list by

searching a microprocessor realization selected from the

data base library. If there is a functional match, the

Functional Mapper uses the symbol table to match the

attibutes of the primitive's variables to the attributes

of the arguments in the realization.

During this process, the Functional Mapper produces a

realization timing table which contains the accumulated time

durations of the enlisted macros. The Timing Analyzer then

I

.. .. .. .. .. ... . . .. ,,- . .. . . . .-.. .-),, .'4. '.t '-. ' - .,.,. . .- ''.-v' . . .. --.

. IDENTIFICATION:

Designer: Pollock/LoomisDate: 23-Jun-82Project: 280Z Fuel Injection Controller

ENVIRONMENT:

Input: IF,8,RESTRAN THR,I,TTL THF,ITTL;AT3,8,TEMP;ATR,1,TTL;WTR,1,TTL;WT3,8,TEMP;S,1,SWITCH;STSW, 1 ,TTL;

Output: W,8,TTL;Arithmetic: KA,24:REAL; Kl,24:REAL; ALT,24:REAL; WT,24:REAL;

AT,24 :REAL TH,24 :REAL; OLDS,I:BINARY;

CONTINGENCY LIST:

SECTION: INITIAL;"Initialization Contingency"when START:I00MS do SETUPI

end "INITIAL" ;

SECTION: RUN;

"Control Fuel pulse width contingency"when CW:35MS do TW;

"Altitude, Water Temp and Air temp factors contingency"when CKA:100MS do TKA,

"Throttle sensing contingency'.

when CTH:200MS do TTH;

* "Air temp factor contingency"

"AT=(l+(20-T)/400)"when CATMP:240 do TATMP;

"Water temp factor contingency""WT=WTl+(70-T)**2/lE4"1when CWTMP:240 do TWTMP;

"Altitude correction factor contingency""If p<26 inHg then ALT::l else ALT:=.94"when CALT:240 do TALT;

.7 end "RUN";

Figure 2 CSDL Description of Fuel Injection Controller

12

I-".', .' ' ' " " " , ' 1 ' " ', ' ' , f - -. ' ',' ,:.,. " 'L '' .. '- -'."'," t . '"

PROCEDURES;

function START;binary START, 1;sense STSW;

V. if STSW:l then START:=1 else START::0;exit START;

function CW;binary CW,l;CW: =;

exit CW;

Function CALT;binary CALT, 1;sense S;if S/=OLDS then CALT:=l else CALT:=O;

exit CALT;

task SETUP;kl:10.5;do TTH;do TATMP;do TWTMP;do TALT;do TKA;switch section to RUN;

exit SETUP;

task TW;-. " *sense (IF); "resistive transducer for air flow"

W:IF*KA*Kl;issue W;

exit TW;

task TKA;KA: :ALT*WT*AT*TH ;

exit TKA;

task TALT;sense (S) "altitude switch"OLDS:=S;if S=Ithen ALT:=.9g4else ALT:=.

fi;.- exit TALT;

Figure 2 continued

13

" 5 *-'. -............................................................ **.

5757. ~ ~ ~ . :-. - . . . . .V W7' "o * .. - . - - .'...'-.' •

S[ compares the realization timing table to the application

timing table to ensure that user specified timing con-

straints have been met. The Timing Analyzer also adds to

*. the set of software and hardware macros in order to implement

a monitor scheme for the application.

Finally, results are ready for output by the process

Formatter. If the user has specified that another realiza-

.-2 tion in the library be tested for feasibility, the Func-

tional Mapper is again accessed and the process is repeated.

The Optimizer can then select, again based on user

specification, the optimal solution and have it formatted for

output or display.

The above is an overview of the data flow as it existed

prior to this research effort. Modifications have -been made

in this process to incorporate Oracle and to enhance its

efficiency. These and other details are addressed in the

design and implementation chapters.

The second required operation, the entering of

microprocessor realizations, is done through the Application

Design Interface (ADI) developed as a part of this thesis

effort with the use of Oraclets Application Interface

Facility (AIF). The AIF is helpful because it permits the

screen interface designer to set up strong data typing to

help enforce correct data entry, After the designer has

created the data base tables and types, the ADI (a screen

oriented, user-friendly system) prompts the user for

.... ,14

-12 °

V

microprocessor(s), the ADI allows the designer to instan-

tiate an Oracle version of it by entering data through a CRT

terminal interface. In this way, microprocessor realizations

are stored in the data base for later use by the CAD system.

(Ref. 5]

The third area of user interaction involves the Final

Design Configuration (FDC). Once the design of a particular

controller is final, a designer may wish to look at certain

statistics concerning its makeup. Statistics are generated

according to specifications in the Design Criteria Tableestablished by the designer upon problem statement input.

These statistics are automatically stored in the data base

after each successful run of the CAD system. The statistics

include chip count, power requirement, monitor scheme,

storage, time, macro index and chip list.

For the design of a microprocessor-based controller,

the CAD system must use the data base to map the problem

statement to a set of software and hardware macros and to

display the solution to the designer. Returning to Figure 1,

the areas of the existing program that interfact directly

with the data base will have to be rewritten to incorporate

the use of a relational data base management tool.

The CSDE system is also not fully developed or

designed. It is limited to the generation of real-time

controllers and develops non-preemptive scheduling schemes.

Although its basic function has been proven feasible,

15

m [ " - , "p .'- " . W " 4 " 4 ' ' ' .'J . '" . . . 4 .' '°- . ' '' ." "

" '

expanded capabilities for improved design flexibility, such

as graphics display, have not been created. All of these

undeveloped and undesigned CAD features impact the design of

A a data base that should be easily extendable to support

them.

*: Although efforts are underway to develop the Z80 and

8086 specifications, currently, the 8080 microprocessor is

the only realization ready for implementation into the data

base. Other microprocessors will be added to the library as

they become available. Therefore, the data base must pro-

vide a representation that is general and readily extensible.

It must also provide a means to contain all the idiosyncracies

of an individual microprocessor without impacting other parts

of the system.

There is currently only one monitor scheme implemented.

This is another factor whose attributes must be examined in

designing the data base, but this fact must not change the

--.- data base representation just to suit its needs specifically.

In reviewing the above analysis of the CSDE, 3 basic

guidelines concerning any remodeling of the current data

base design can be detected. First of all, the design

should enhance the designerts ability to do his/her job.

The three user --. ices - problem design, microprocessor

volume design an,,- ontroller design - should all be

" easy to understand, _rple to use and increase the

designer's potential performance. Second, the redesign of

16

- .".,5 . . . . .. . .

,A -. ,,.,. . . . . . . . . . . . .. .-

the data base should not complicate the interworkings of the

'' CSDE. If possible the redesign should help streamline the

operation of the CSDE and unravel any 'clever' programming

schemes that were built in out of necessity due to working

with the Fortran/IBM punched card format. And third, the

data base design should be flexible enough to incorporate

future changes readily. The design should apply the well-

known software engineering principles of modularity, infor-

mation hiding and regularity. The system should be designed

so that the information is easily and logically encapsulated

within the framework of the data base, but yet its implemen-

tation should be invisible to the user. The use of all

three principles enhances changeability and, as already

presented, this CAD system is and will be in a state of

change.

The next chapter describes a new design for the CSDE

using a relational data base management system, It

") addresses the organization of data within the data base and

- possible implementation schemas for use by the CSDE

subroutines.

17

III. DESIGN

The last two chapters explained the requirements andrationale of the CSDE. The purpose of this chapter is to

describe the design of a data base for the CSDE that ful-

fills those requirements. This design chapter is primarily

- concerned with the arrangement of the CSDE's necelsary data

into logical entities that can be manipulated by a rela-

tional DBMS, specifically Oracle. This specific design is

* not directly transferable to another type of DBMS. However,

an effort has been made to encapsulate the important1-

operations and ideas so that the resulting design can easily

be modified or rehosted on a different DBMS.As noted in Chapter II, there are three main conceptual

-" areas which must be served by the data base for the CSDE.

These can be classified as: 1) problem statement input,

2) microprocessor realization library and 3) the final

design configuration for a given controller. The data

base has been organized around these three data entities.

Figure 3 illustrates the relationships that the major

subroutines of the CSDE have with these three areas of

functionality.

The user enters the problem statement via the syntax

directed editor (SDE). The information required by the

Functional Mapper (the primitive list and the symbol table)

18

A--

E 7t _7

ObO N 0

,a.-I r- 4J,

4r4 o a, .

(d rd 1)(0-H4-

_4_' 4-J o 0 (

a) 0

m O OH

0-0 t

:':':':I 5

4.f 4J H id ~a a,0) 0 F4 J .

0

9 V0 °0

(a 0 4)U P

E-4 ~HU 0~

'c-I

4)~U 9zU) Y

F 44 4

4 4

19

£L

is then extracted by the Translator and is stored in what is

termed a relational data base type 1 (RDBTI). The remaining

information from the problem statemen: input - the problem

statement identification, the design criteria and the

environmental criteria (in the form of the application timing

table) - are stored in the final design configuration or

RDBT3. RDBT3 is meant to be both a working environment and

a historical repository for the designer. It therefore con-

trains all the necessary facts to extract useful design

abstractions such as chip count and power supply requirements

and to reconstruct the design effort. The RDBT3 will also

contain the set of information comprising the current

*[ realization timing table and a list of the contingencies and

tasks of the design problem with an index to their specifically

required software and hardware macros.

As can be seen by Figure 3, the data base must also hold

microprocessor realizations - the primitive implementations

which are used to construct the designs. These are contained

in RDBT2s and are entered through an Application Design

Interface created using Oracle's Application Interface

Facility. The relational model must therefore also support

the volume designert s effort and supply the fields necessary

to adequately describe a microproc-essor. The following pages

describe in detail the relational models for each data base

type.

20

.- .. . .; - -' " " ' ' "'. . . _ . .' _ ' " ,, ,, . ,, ,.. .' . . ... .'_ _.. .. '-.-

"-. The first relational data base type - RDBT1 - is created

from information extracted from the initial CSDL problem

statement input by the translator, This information is in

the form of a primitive list and a symbol table. The

primitive list is generated from the contingency list and

procedures sections and the symbol table is derived from the

environment section of the problem input. The primitive

list contains the titles of each function required by the

given problem, the primitives (or software macros) that

I produce each function and the arguments or parameter vari-

ables necessary for each primitive. The symbol table

contains the set of actual parameters used in the given

problem statement with their attributes and precisions.

The RDBTI is created by a module - CREATEDB1 - that is

invoked by the Translator module. If it is decided to

change the data base management system, the CREATEDB1 module

will be the only section to require major modification to

incorporate the change. The RDBT1 will also be accessed by

the Functional Mapper to create a mapping of RDBTI to an

RDBT2 contained in the realization library. The resulting

mapping will be stored in an RDBT3 as aprt of the final

design configuration.

The relational model is simple and mirrors and contents

of the primitive list and symbol table in a modified

relational form. The model is shown in Figure 4.

..

21

<<<,

PRIMITIVELIST

field TITLE MACRONAME POINTERX

type CHAR CHAR NUMBER

SYMBOLTABLE

field POINTER X ARGUMENT MINIMUM MAXIMUM

type NUMBER CHAR NUMBER NUMBER

-. '

Figure 4 Translator Output

..

22

%°o

LVI ~ -. - ,I I. -. r... . . .

4.

Title is a primary key to the first table in this section

of the data base. Title is the name of a contingency or task

defined in the original CSDL input by the designer. Macroname

is a software macro which is also selected as a part of a

contingency or task in CSDL input. Pointerx/Argument make

up the key for the second table. Pointer-x is used as a

tpointert from the table Symbol Table(s) to the Primitive

List or in other words, Pointer x is the relation that binds

the two tables together. Pointer x is a unique number

generated for each Title/Macroname relation supplied by the

Translator.

The second table is used to hold the actual parameters

and their precision requirements as defined in the CSDL

description of a problem. These are represented in the

second table by the fields Argument, Minimum and Maximum.

In data base terminology, the relationship between Table 2

and Table 1 is many to one. In this way, the relational

model avoids repetition of the contents of the symbol table

and provides a data base that is easy to comprehend and

logically oriented. Figure 5 shows the recommended

arrangement of data fields for 2 simple tasks.

The second functional area of the CSDE which the data

base supports is the microprocessor realization library.

Each microprocessor realization in the library is

represented as a volume. Each volume is further subdivided

into two more sections; hardware and software. It is from

23

'4

PRIMITIVELIST

TITLE MACRONAME POINTERX

TASK1 S.SENSECOND 1

TASK1 S.ADD 2

TASK2 S.MULT 3

SYMBOL TABLE

POINTERX ARGUMENT MINIMUM MAXIMUM

POINTER X ARGUMENT MINIMUM MAXIMUM

1 SIGNAM 0 8

2 ARGI 0 8

2 ARG2 0 8

2 RSLT 0 83 PARAMI 0 8

3 PARAM2 0 8

3 ANSWER 0 8

Figure 5 Relational Model for a Simple Contingency/Task Function

24

4-. I "7 - 0 --

. . .- -

these volumes of hardware and software components that the

CSDE attempts to build a microprocessor controller complete

with monitor for a given problem specification.

"* Each hardware and software primitive in a volume has

specific characteristics that must be identified by the

volume designer. These characteristics fall into three

general categories that easily lend themselves to a

relational model. The categories are functional specifications,

control lines and text blocks.

Since the hardware and software primitive have different

characteristics, two different type of tables have been

devised. The two table types are also differentiated into

blocks that represent one of three relational categories.

These three categories are the functional specification,

the control lines and the text code. These categories are

.. further defined in the following pages.

In any relational model, a separate block or table is

needed to define multiple instances of a field. In other

words, a particular block can have no two fields the same.

For instance, a hardware primitive may have more than 1

input parameter, so a separate block is necessary to input

parameters. Several of the input parameters in this block

will be incorporated into the design of each hardware

primitive. The tables, blccks, fields and field types are

displayed in Figure 6 and 7 for the hardware and software

macros, respectively.

025

. . ......... .

BLOCK 1 - IDENTITY-BLOCK

-. field MICROPROC HW MACRO MILLIWATTS CHIPCOUNT LATENCY

. . type CHAR CHAR NUMBER NUMBER NUMBER

field POINTER

type NUBMER

BLOCK 2 - PARAMETER BLOCK

" field POINTER PARAMETER MIN MAX

type NUMBER CHAR NUMBER NUMBER

BLOCK 3 - COMMENTBLOCK

field POINTER COMMENT COM ID

type NUMBER CHAR NUMBER

BLOCK 4 - INCLUDEBLOCK

field POINTER INCLUDE INC ID TIMES

type NUMBER CHAR NUMBER NUMBER

BLOCK 5 - CALL BLOCK

field POINTER CALL CALL ID TIMES

type NUMBER CHAR NUMBER NUMBER

BLOCK 6 - CALCBLOCK

_0. field POINTER GLOBVAR OP VAR RSLT CALC ID

type NUMBER CHAR CHAR CHAR CHAR NUMBER

S. Figure 6 Hardware Macro Table

".*

BLOCK 7 -ATTRIBUTE BLOCK

field POINTER LOCALVAR OP VAR RSLT ATTRID

type NUMBER CHAR CHAR CHAR CHAR NUMBER

BLOCK 8 - IFBLOCK

field POINTER VARIABLI OP VARIABLE2

type NUMBER CHAR CHAR CHAR

field IFMP IF_HWMAC IFREQ IF_ID

type CHAR CHAR CHAR NUMBER

BLOCK 9 - TEXT BLOCK

field POINTER TEST TEXT ID

type NUMBER CHAR NUMBER

Figure 6 Continued

27

BLOCK 1 - IDENTITY BLOCK

field MICROPROC S/W MACOR STORAGE TIME EXT REF

type CHAR CHAR NUMBER NUMBER NUMBER

field POINTER

type NUMBER

BLOCK 2 - ARGUMENTBLOCK

field POINTER ARGUMENT MINIMUM MAXIMUM

type NUMBER CHAR NUMBER NUMBER

BLOCK 3 - COMMENTBLOCK

field POINTER COMMENT ID

type NUMBER CHAR NUMBER

BLOCK 4 - INCLUDE BLOCK

field POINTER INCLUDE ID TIMES

type NUMBER CHAR NUMBER NUMBER

BLOCK 5 - CALLBLOCK

field POINTER CALL ID TIMES

type NUMBER CHAR NUMBER NUMBER

Figure 7 Software Macro Table

28

..

BLOCK 6 - CALC BLOCK

field POINTER GLOBVAR OP VAR RESLT ID

type NUMBER CHAR CHAR CHAR CHAR NUMBER

BLOCK 7 - ATTRIBUTE BLOCK

field POINTER LOCALVAR OP VAR RESLT ID

type NUMBER CHAR CHAR CHAR CHAR NUMBER

BLOCK 8 - IFBLOCK

field POINTER VARIABLE1 OP VARIABLE2

type NUMBER CHAR CHAR CHAR

field IFMP IFMACRO IFREQ IF_ID ID

type CHAR CHAR CHAR NUMBER NUMBER

BLOCK 9 - TEXT BLOCK

field POINTER TEST ID

type NUMBER CHAR NUMBER

Figure 7 Continued

29

. .. .., ..... .. . .. . ..-. .. . .... . .. . .. .. .---

. . . ' .

In the HARDWAREMACRO table there are 9 block types.

The first two blocks represent the functional specification

of the hardware primitive. The information in the first

block is required for every hardware primitive. It has two

J,. identifying keys: 1) the microprocessor and 2) the name of

the hardware primitive. A unique number is then generated

when the volume is designed, to as as a pointer to identify

any of the remaining block types associated with the parti-

cular primitive. The other fields in the first block

contain information required by the CSDE to compile power,

*timing and chip count requirements for the controller.

The next block is used to hold the hardware primitive's

parameters or arguments. A hardware primitive may have 0, 1

or as many parameters as it requires. Each argument must

also be identified by its minimum and maximum precision.

For instance, in the example used in reference the

hardware primitive H.SENSECOND for the 8080 requires an

argument called SIGNAM whose minimum precision is 0 bits and

whose maximum precision is 8 bits. The Functional Mapper

will use the information in this second block to try and

match each primitive from the problem statement input with

a realization from the volume.

The next 7 blocks in the HARDWAREMACRO table represent

the control information needed to design a primitive. The

first control type is the COMMENTBLOCK, The COMMENT BLOCK

is included in the realization volume as an aid to the

30

, -. , , - * , . . . ... .* . **.. . • . ..... .. ..,-..12 .: . . ,,K..., ,, ,x,.-Q.,,.....,, .> . . .~. ~.*.,..,

volume writer in keeping track of the purpose for and

operation of the realization primitive. Comments can be 80

alphanumeric characters long in keeping with the general

width of a page. The zero, one, infinity rule applies to

the number of COMMENT-BLOCKs permitted as well as to the

rest of the control line blocks. Each comment line is given

an identification number generated by the DBMS. This is to

keep things organized for output of a realization volume.

Comments are not acknowledged by the Formatter and are,

* therefore, not output in the Final Design Configuration (FDC).

There are two different types of outputs which must be

generated from each realization volume. The first output is

simply a designer tool; a user manual or guide reflecting

the hardware and software primitives of a particular

microprocessor volume. The second output is the FDC of a

microprocessor controller for a specific design problem.

The next two blocks represent similar control functions.

Sometimes it is necessary for a primitive to use another

primitive within its scope. When an INCLUDEBLOCK is

included in a primitive's format the Formatter will

include the primitive in the FDC but list it separately,

after all the initially indexed primitives have been output.

The CALLBLOCK tells the Formatter to include a primitive in

the listing at the point where it was called. Each of these

blocks are identified by a system generated identification

number. These identification numbers not only help to

31

1 d fW . _1. W. . . . . . . .Y". 7.. .7 - N 7 9 0 T 1 C I .

organize the realization volume output but become essential

when implementing conditional (IF) control lines that incor-

porate CALL and INCLUDE functions. The last field, labeled

TIMES, is unique to these two control blocks and can be used

by the volume writer to implement a controlled loop structure

similar to the case type structure implemented in

reference . Its use is explained later in the section

describing the IFBLOCK.

The CALCBLOCK and the ATTRIBUTEBLOCK also have similar

form and function. Both are used to assign values to system

variables. The CALCBLOCK is included in the design

primitive to allow the manipulation of design system global

variables. During system generation, values are assigned to

the global variables by subroutines called by the Formatter.

An example of this in the 8080 microprocessor realization

library is the Portpt global, which stores the number of I/O

ports required for a design, so the system can assign a

specific address to each I/O port. The expression which

calculates the global variable is represented as four fields

in the relational model; one field to represent the actual

global used, one field for the arithmetic operator (, **,

-, ), one field for the value applied against the

operator toward the global and one field to hold the result.

Complicated expressions that would normally involve

parentheses will have to be simplified and distributed over

32

-',

more than one CALCBLOCK. The ID field provides a mechanism

for ordering the expressions.

An example strategy, using the relational model in the

design of a microprocessor primitive is given in Figure 8.

The expression Total = )Global.add + Const) * Globalmult is

divided up into two expressions. The result of the first

expression, SUM, is used to provide a common link between

the expressions. The ATTRIBUTEBLOCK contains the same

field types as the CALC BLOCK. It is used to assign values

to local variables within the primitive in the same manner

in which the CALCBLOCK operates.

The IF BLOCK is a feature which allows the volume

designer some additional flexibility. The IF BLOCK

represents a cross between a case statement and a DO FOR I

1 to X loop. The IF BLOCK originally had the following

syntax:

IF <math-exp> , <rel-op> . <math-exp> SKIP <lines>

The SKIP <lines> clause was employed as a method to include

or not to include lines of the primitive. For example, upon

system generation the global variable representing the total

amount of additional RAM required by a functional specifica-

tion might equal 1792. In this case, 7 additiona 256 byte

RAM primitives are needed to fulfill the functional specifi-

cation. Instead of calling the H.RAM256 macro 7 times, an

if statement had been incorporated into the H.RAM256

33

POINTER GLOBVAR OP VAR RESLT CALCID

1GLOBALADD SU OTA 2U

Figure 8 Example Microprocessor Primitive Design

<34

-_ --. . *. * * . . . . . . . . .. . . . ... , - o - - -o

%'o

,. 7.

hardware primitive allowing for the inclusion of additional

RAM up to the maximum allowed by the 8080 hardware set.

The IFBLOCK of the relational model allows for the

same type of primitive implementation technique. The syntax

of the IF statement has been changed to the following:

IF <var> . <rel-op> . <var> THEN <call or include>

The call or include statement will then contain the number

of times the primitive is to be called or included according

to the relationship identified between teh variables in the

IF statement. A possible implementation of the previous

example would be:

IF <memrept> .GT. <1791> THEN call (8080.H.RAM256.7)

As in a case statement each possible value for <memrept> can

be represented in the primitive. 8080 corresponds to the

IFMP field, HRAM256 corresponds to the IFMACRO field and 7

corresponds to the IF REQ field. During a CSDE system run,

the IFREQ field requirement will be identified and this

number can then be placed in the TIMES field of the

appropriate CALLBLOCK or ATTRIBUTEBLOCK. During system

generation, the Formatter will know haw many times to

include a particular primitive by the quantity held in this

field. An IF ID field is then generated by the system to

keep the IF statements in order for the final outout

listing. The IF BLOCK offers the volume designer flexibility

35

........................

and an avenue for creativity without complicating the design

of the relational representation too much.

The final functional category in the microprocessor

volume design is the TEXTBLOCK. The TEXTBLOCK contains

assembly level code for the microprocessor. Each line of the

code is identified by the ID field to keep the code in order.

Without using some type of incremental function in an extra

field on which the DBMS can sort there would be no way of

identifying which line came first in the coding specification.

Everything contained in the TEXT BLOCKS will be output

in the final design as is expect for two types of text. The

,? first type is a variable enclosed in pound signs (#). Thesed.

will be interpreted as calls to a system procedure of func-

tion, and the corresponding procedure or function will be

implemented to generate character strings for the final

design listing. The two system functions which are

currently implemented are: 1) 'idsec' which prints the next

line of the ID table and 2) tstatus(n)' which returns status

information on the storage attributes. The second exception

is the handling of dummy arguments. Within the text lines,

each dummy argument is enclosed in brackets (t<' and t>t)

and are replaced by the actual arguments wherever the <

and r>1 are encountered.

The SOFTWAREMACRO table has the same three functional

categories represented by its relational model. The only

difference is in the first block containing the primitive 's

36

functional specifications. Whereas the Hardware primitive

required fields to allocate latency, timing and power

requirements the software primitive requires fields for

!storage, timing and external memory references. Theses i4m

fields will be used by the CSDE to calculate total storage

and time requirements for the microprocessor system and to

develop a monitor.

These first two data base types - the Relational Data

Base Type 1 (RDBTI) containing the primitive list and the

symbol table and teh Relational Data Base Type 2 (RDBT2)

containing the realization volume design - will be used by

the Functional Mapper to build a major portion of the final

design configuration (RDBT3). The current CSDE accomplishes

the mapping in two separate operations. First, the index

of the chosen realization volume is checked for a match to

a given design primitive. If a match is found, the

selection criteria in the design primitive are compared

to selection criteria in the realization volume primitive.

By using a relational model, this process can be shortened

into one operation. The SQL language will allow a SELECT

operation on the data base to retrieve a match to any and

all parameters requested. So in a programming procedure a

controlled loop can be created whereby design primitives

with their arguments and precision requirements are fed into

dummy parameters of a SQL select statement. This select

statement will then be the means by which the RDBT2 is

searched for a match.

37

Figure 9 shows a demonstration of this idea. The pro-

cedure, FUNMAP, is called from the Optimizer which sends as

input variables the MACRONAME - name of the design primitive

to be matched to the macro in the realization library -

ARGUMENT - one of the design primitives I/0 parameters - and

MIN, MAX - the precision requirements of the ARGUMENT sent.

As is evident, in this scheme the Funmap procedure is

invoked to test each argument against a possible match in

the realization libaray. The Funmap procedure then sets a

boolean variable - FOUND - equal to tru or false depending

of whether a match was found or not. Other schemes could be

drawn up placing more responsibility on the Funmap design.

For instance, it could be argued that it is the responsibility

of the Funmap to place the found primitive in the PRIMARY_

INDEX in the Final Design Configuration. The purpose of this

figurative Funmap was not to dictate its future but to show

how the SELECT statement streamlines the mapping process.

The third and final functional area of the CSDE require-

ing data base support is the Final Design Configuration

(FDC). As noted previously the RDC is to be used as a work-

ing environment and as a historical notebook for the

designer. It should provide enough information about the

4 microprocessor design to discern useful patterns and

abstractions about the design and to be able to recreate the

designer's original goals in using the CSDE.

38

- *J *

Procedure Funmap (NACRONAME, ARGUMENT, MIN, MAX, FOUND);

SELECT from IDENTITY BLOCK

where (MICROPROC.SW MACRO MACRONAMEand MICROPROCSW MACRO.ARGUMENT = ARGUMENTand MICROPROCSW-MACR.ARGUMENTMINIMUM z MINand MICROPROC.SW-MACRO.ARGUMENT.MAXIMUM z MAX)

or (MICROPROC.HW MACRO = MACRONAMEand MICROPROCHW-MACRO.ARGUMENT = ARGUMENTand MICROPROC.fW-MACRO.ARGUMENT.MINIMUM = MINand MICROPROC.HW--MACRO.ARGUMENT.MAXIMUM z MAX) ;

If SELECT thenFOUND = TRUEElseFOUND = FALSE;

end Funmap;

Figure 9 Functional Mapper Demonstration

39

There are four primary functional areas in the FDC.

They are the:

(1) Identification Section

(2) Design Criteria Section

(3) Timing Tables

(4) An index of the hardware and software primitives

used in the design.

The first area is an identifying key to the FDC. The

information in the ID section is input by the designer with

the Syntax Directed Editor (SDE) at the beginning of the

design process. The data required by the relation includes:

1) the designer t s name, 2) the date, 3) the name of the

design project and 4) version number. Each identification

table will also contain an extra field to be used as a

pointer to which the other three functional areas of the FDC

can point to. The ID Section is also used by the Formatter

upon design configuration output as an identity header. The

relational model for the Identification Section is depicted

in Figure 10.

The next area of concern is the Design Criteria Section.

The design criteria are also input by the designer at the

initial session with the SDE. The designer responds to

prompts regarding CSDE run parameters and FDC output

metrices. All of the possible design criteria have not yet

been developed and as the CSDE matures additional design

40

..6

....-.................... . .

IDENTIFICATION TABLE

field NAME DATE PROJECT IDPTR VERSION_NO

------------------------------------------------------------

- ."type CHAR DATE CHAR NUMBER NUMBER

Figure 10 Identification Section Model

,41

information may be required. With this in mind, the

relational model has been designed for extensibility and

flexibility.

The Design Criteria Section covers 2 general areas:

1) CSDE operating instructions and 2) FDC listing criteria.

The design criteria for the CSDE operating instructions are

very limited at this point and only allow the designer to

specify the order in which library volumes and monitor

strategies are tested. FDC listing parameters are similarly

limited in the present CSDE but as more is studied and known

about designer needs, additional information can be gathered

from the CSDE process and organized for output, As the.. !

system runs now only 2 statistics can be extracted to compare

microprocessor feasibility: power consumption and chip

count (an approximate cost function). Storage and time

comparisons can easily be added to this list. The informa-

tion is already present in the data base. Additional

designer queries will have to added to the frontend and the

responsibility of outputting the information will lie with

the Formatter. The relational model for the Design Criteria

section is shown in Figure 11.

The relational model can be used as follows: 1) the

designer specifies the microprocessor and monitor he/she

wants to use for each run by placing the order number in the

CSDE RUN field and the respective microprocessor and monitor

schemes to be attempted in their respective fields and then

42

L~,2

field IDPTR CSDERUN MP MONITOR

type NUMBER NUMBER CHAR CHAR

field STORAGE TIME POWER CHIP

type NUMBER NUMBER NUMBER NUMBER

Figure 11 Design Criteria Table

443

2) the designer specifies which design abstractions he/she

is interested in for output by responding to SDE system

prompts in the corresponding manner. There is no limit to

the number of fields in a relational table so as the CSDE

grows, numerous designer queries can be placed in the Design

Criteria table.

Another important set of information derived from the

problem statement input used in the FDC concerns what the

present system calls the Application Timing Table (ATT).

The ATT information is extracted from the problem statement

in CSDL format by the Translator. This information is the

set of timing constraints for an application given by the

designer. A second set of related information is contained

in the current Realization Timing Table (RTT). This infor-

mation is extracted by the Functional Mapper from the

microprocessor realization selected from the library as the

mapping takes place. In other words, the RTT contains the

possible timing parameters that the microprocessor in

question can supply to meet the designer ts needs. This

information is used by the Timing Analyzer subroutine to

compare the timing parameters in each table to test a

particular microprocessor for feasibility. If the micro-

processor proves feasible, a monitor scheme is then developed

by the MONITOR subroutine according to the timing

specifications in the RTT.

44

".

The original contrants imposed by Matelan and also

used by Ross have been changed for this design study. This

study is testing the concept that the only timing parameter

needed for feasibility testing is the frequency of a con-

tingency. This is represented as rho in the references, If

this concept is proven out in the future, the design and

implementation will have been greatly simplified. The two

tables have also been logically organized into one rela-

tional table. This is so that all the timing related issues

are modularized into one section. A designer will know

*where to go to find the answer to any question related to

timing. The translator will still have to enter the

application's timing constraints into the data base and the

Functional Mapper will still have to compute the micropro-

cessor s ability to perform the required operation with

respect to time, but the orientation of the data has been

structured into one logical entity, Figure 12 depicts the

data base structure for the Timing Table entity.

The fourth functional entity in the FDC is the index to

the software and hardware macros needed for each contingency

and task in the design statement. Since each contingency or

task will require more than one primitive to realize its

function, 2 tables are necessary. The first table, as

depicted in Figure 13, consists of the title of the

contingency or task, a primitive and a pointer field. The

pointer field is again used to relate the tables in a many

""45

. r .4. .

field CONTINGENCY TASK ATTRHO TRRRHO

a ,. ,

type CHAR CHAR NUMBER NUMBER

Figure 12 Timing Table

-- I

I

46

LOA~

V.

%.-j,,. % ..- % --. % ', % - .. % %,% " . % .. ... ". .. .S . .t -P .2 . - .*C -. .. . . . . . . - .

PRIMARYIDEX

field TITLE PRIMITIVE POINTER

type CHAR CHAR NUMBER

SECONDARY INDEX

field POINTER PRIMITIVE

type NUMBER CHAR

Figure 13 Index Tables

476I

Ht

: ,. -. . . _ , . . .. ... .. , . . . . . . . .. . -.

to one fashion. The second table is defined by a like

pointer field and a field for another primitive of the

contingency or task being defined.

The Functional Mapper will retrieve a title line from

the RDBT1 (which contains the primitive list and symbol

table from the design problem) and place it in the data

base. Next, it will search in RDBT2 for matches to each of

the primitives in RDBT1 and as these matches are found place

them in the FDC. A quick check through the index each time

a mapping is found can indicate whether or not a primitive

has already been used. This is an important test. For

instance, it is not necessary to have redundant hardware or

software necessary to implement multiple divide functions.

Once all design primitives have been mapped into a

particular design volume the Timing Analyzer will add to the

list of primitives any of which are deemed necessary to

fulfill the timing requirements. These can all be placed in

the FDC under a special title. Upon completion of the

microprocessor controller creation, the Formatter will then

use the index to indicate which primitives from the

microprocessor volume in RDBT2 are to be placed in the

final formal output,-V

The final deisgn configuration is accessed and used by

every major subroutine of the CSDE. Care will have to be

taken in the implementation of the CSDE application not to

overwrite and/or eradicate information. It is recommended

48I

that during the reprogramming of the CSDE to incorporate the

relational data base model, each subroutine be written and

tested separately to ensure that the right information is

going into the right location.

This design presentation has illustrated a conceptual

representation of the data base requirements of the CSDE

through a relational model. The three major aspects of the

CSDE have been incorporated into a logical, cohesive blue-

* * print. The next chapter illustrates the implementation

methodology using Oracle on the VAX 11/780 with the VMS

operating system as the DBMS.

.*

411

49

I-'1- " ..... ~ * * * * , ,. - . . ...- .. -- . . . . .

IV. IMPLEMENTATION

This chapter describes the effort necessary to implement

the conceptual design of the CSDE's data base requirements

defined in the previous chapter. In addition to the data

base implementation, this text also describes the creation

of the Application Design Interface (ADI). With this

information, the reader will be able to find and use the

data base tables, to understand some of the restrictions

placed on the implementation by the Oracle DBMS and to have

the background necessary to modify the system should it be

required by future enhancements.

To implement a data base model, one must first describe

that model in terms of the DBMts Data Definition Language

(DDL). In this case, the DBMS is Oracle and it uses the

standard DDL developed by the designers of system R. [Ref. 6]

The format for defining the tables is as follows:

create table <tablename> (<filename><fieldtype>(<field length>));

The DDL format for describing the table in Figure 6 on

page 26is depicted in Figure 14.

Using this example as a reference, specific designX.,

features can be pointed out in relationship to Oracle's data

types. Three data types were used; CHAR, NUMBER, and DATE.

so4 50

6"< ~ ',." ' .4 < .": .: - .- -" " . .• . •" , - - . -. .. . -

.-.. %I

create table identification block (niame char(25),

the-date date,

project char(25),

version-no number(6),

* id_ptr number(6));

Figure 14I DDL Format Example

r-v

51

CHAR allows all characters to be used in the field;

upper/lower case and all special characters. This flexibil-

ity is required by the need to use mathematical symbols in

conjunction with text. Oracle allows CHAP data lengths from

1 to 240. To provide some regularity in the design, CHAR

lengths were limited to 80, 25 and 3. In the tables for the

data base, 80 and 25 was used for text strings and 3 was

used to express mathematical operators. NUMBER is an

integer data type and again, to introduce regularity all

fields of data type NUMBER were limited to a length of 6; 6

being the maximum length required by any one field. The

third and final data type, DATE, is unique in that Oracle

prespecifies the length as 7 so it therefore is left blank.

The tables were placed in a file called CREATEDB.UFI

under the CSDE subdirectory [.HEATHER] on the VAX 11/780

using the EDT editor, available under the VMS operating

system. The listing for the file is available in Appendix A.

After the tables were defined in the DDL and put on file,

Oracle's User Friendly Interface (UFI) was used to make-."

instantiations of the tables in the DBMS. This is done by:

(1) logging on to Oracle as a CSDE user ty typing Oracle

once in VMS.

* (2) typing UFI.

(3) answering the screen prompts for user name and password.

(4) typing @CREATEDB.UF.

52

'-'-.. .. . . . . . . . ...... . . .D 4 - "'-.. .. . . . . . . .

i! arunthe tables are

After asuccessful table buildruteabsae

available through Oracle for data input, The tables remain

as defined and do not have to be recreated unless there is a

.data base design modification.

Data will be input to the tables in three ways:

1) problem statement input via the SDE, 2) creation of the

Final Design Configuration by the CSDE's Functional Mapper

and 3) creation of the realization libraries through

interaction with the ADI. The implementation of the first

two categories is beyond the scope of this research. The

third category, the creation of a realization library, has

been initiated by this thesis effort. An ADI was developed

for use by volume designers according to the specifications

given in the design chapter. The following is a description

of the development of the ADI.

The ADI was developed using Oracle's Application Inter-

face Facility (AIF). The ADI was divided into two parts for

reasons of ease of development and ease of use. There is

one file that can be used to generate specifications for the

hardware primitives and another file to create the software

primitives.

To create an ADI one must first invoke Oracle's P

Interactive Application Generator (IAG). The lAG is a menu

driven interpreter that translates the screen designer's

input into a CRT screen display for easy volume design

9 input. Each response given by the screen designer to the

53

IAG's prompts for typing parameters generates a unique

sequence of code. In other words, the prompts are not

predetermined but vary according to user response. This can

be a problem when trying to correct or modify a given screen

but a careful study of the Oracle documentation and experi-

mentation do make it possible. To invoke the IAG, one

simply logs on to Oracle and then types IAG <filename>. In

this case, the filename for hardware is HDESIGN.INP and

SDESIGN.INP for software. The TAG will then intiate a

series of answer dependent prompts that will define various

aspects of the screen interface.

For both the hradware and software screen interfaces, 7

blocks were designed. Each block is represented by a

screen. The screens were divided into logically ordered and

related entities that also provided a coherent, easy to use

presentation. The relational model represented on each

screen and the number of times the model is repeated on a

single screen is outlined in the following:

(1) IDENTITY BLOCK (1)

(2) PARAMETER BLOCK (3)

(3) COMMENT BLOCK (6)

(4) CALL BLOCK and INCLUDE BLOCK (2 ea.)

(5) ATTRIBUTE BLOCK and CALC BLOCK (2 ea.)

(6) IF BLOCK (1)

(7) TEXT BLOCK (2)

5L

.S.

Each field depicted on the screen is directly related

to a field identified in the data base design. The only

difference between the name of the field on the screen and

in the tables is that the screen name may be slightly more

user friendly than the shortened name used in the data base

design. For instance, MICROPROC in the table IDENTITYBLOCK,

becomes MICROPROCESSOR on the screen.

In addition to the criteria identified in the data base

tables in Appendix A (data type and length), Oracle's lAG

permits further parameterization of each field represented

in the screen interface. The following is the list of

* - prompts the IAG uses to qualify various characteristics

about field representation and usage with a short explanation

of each prompt.

(1) Field name: The name given to a field in the data base

design i.e. MICROPROC.

(2) Length of field/Display length. The length of the

field identified in the data base design and the length

of the field to be represented on the screen. In this

implementation these characteristics were always the

same.

(3) Is this field in the base table Y/N: A 'Y' or YES

answer means that the field being described corresponds

to a column of the table being processed by this block.

All fields have a YES answer for this question as there

is a 1:1 correspondence between the tables and the

55

If~i!! .. . . . . .

screen blocks. Exception: The times field in the CALL

and Include Blocks is not depicted on the screen. This

field is input by the CSDE.

(4) Is this field part of the primary key: The fields that

make up the primary key are ide'tified in the tables of

Appendix A by the words 'NOT NULL' next to their data

length parameter. Usually the key is made up of the

pointer and another field within the block that make

the key unique. For example, in the second block,

PARAMETERBLOCK, the key is made up of the fields

labeled POINTER and PARAMETER.

(5) Field to copy primary key from: Unrelated to this

design, therefore left black by hitting the return key.

(6) Default value: None of the fields have one in this ADI,

therefore left black by hitting the return key.

(7) Page: Identifies which screen page/block the table

is a part of. In this screen design, the hardware

and software files are each made up of 7 pages.

(8) Line: Identifies the line number of a page on which

the field prompt is placed. An effort was made to

place similar or identical fields on the same lines

on the different pages.

(9) Column: Identifies the column number from 1-80 on

which the data will be entered. The prompt will appear

beside the column number identified.

56

• -.. .. , -. , ., . -...-.... '. .--. . . .. , -. . . .. . . .

(10) Prompt: Identifies the prompt that appears on the

screen, i.e. MICROPROCESSOR.

(11) Display prompt above field Y/N: The answer is NO

throughout the screen interface design. A NO answer

displays the prompt beside the data entry field

display.

- (12) Allow field to be entered: All fields are designer

enterable except the ID# fields. These fields are

generated by a sequel statement embedded in the screen

interface design.

(13) Allow fields to be updated: if the answer to the above

question was no this prompt does not appear. It also

does not appear for fields labeled as a part of the

key. Otherwise, all other fields are updateable.

(14) SQL> This is a prompt for a sequel statement related

to the field being entered. In this screen design, the

SQL statements were used to automatically generate

unique ID numbers to be used as part of that tables

key. The generic SQL statement is as follows: SELECT

" MAX (<fieldname + 1>) INTO <fieldname> FROM

<tablename>;. The fieldname is the same for both sets

of brackets and the tablename is the table in which the

fieldname resides. Oracle requires that a dummy record

be used to start the process of automatic number

generation. An INSERT statement was used to set up a

fake record with zeros in all the number data typed

K57

I .S * . -. * . -

fields and 'DUMMY RECORD' in all the character string

fields for each of the tables that used a SQL

statement of this kind. This fact will most likely

have to be considered in the design of the Functional

Mapper. SQL statements can be used for additional

checks for data entry clarification. As more is

known about the requirements of the volume design

effort the SQL statements may become an avenue for

additional data typing or input.

4 ~ (15) Message if value not found: This and the next prompt

are only generated if a SQL statement has been used.

The message usually generated in this instance relates

that the ID# was not generated. There is no reason to

this author's knowledge why the numbers would not be

generated.

(16) Must value exist. The answer is YES.

(17) Is field fixed length: None of the fields are fixed

length. Fixed length refers to the number of charac-

ters or numbers that must be entered and does not refer

to the maximum length definition.

(18) Auto jump to next field: If any of the fields were

fixed length this could be used. As it is now, the

designer must his <return> to move the cursor to the

beginning of the next field.

58

-_. . ' - - . - .. - -- .- . . . ..,

(19) Convert field to upper case: This is not necessary in.%

this application.

(20) Help message: This IAG prompt gives the screen inter-

face designer a chance to help the volume designer by

clarifying what goes into the field. The current help

messages will probably be modified as more is known

about the volume design effort.

(21) Lowest Value: None of the fields in this application

needed to use this concept.

(22) Highest value: None of the fields in this application

needed to use this concept.

Once all the screen criteria have been entered the

interface designer must then retype IAG filename for a

compile to take place. Appendix 2 is a listing of the IAG

compiled code. It is easy to discern from the listing all

specific screen design decisions concerning each block and

their corresponding fields. Further enlightenment regarding

2- .the TAG prompts can be found in the Oracle Manual in the TAF

Application Design Reference section.

One Oracle idiosyncracy that should be pointed out to

future generations of Oracle users involves the modification

process. it is easier to erase an entire field and reanswer

0, the prompt- regarding its screen activation than to try to

change the individual rcsponses. This is because, as noted

before, the 7rompts are answer dependent.

59

:- " " " . . -. . .- , .. . . . .. .. . .- .

In general, an effort was mtade to make the screen

interface easy to read, easy to use and regular. This will

-S.. hopefully make it easy for the volume designer to do his/her

-$ job and for future changes to be applied against the screen

interface.

1 10

a-.'

7 60

.°Z W

V. CONCLUDING REMARKS

"? The previous pages describe the operations of the CSDE;

the responsibilities of the major subroutines, the data flow

characteristics and the data base requirements. Following

these descriptions, a relational data model is defined and

its implementation on the Oracle DBMS is outlined.

* Chapter I was dedicated to introducing the problem.

- This was done by describing an analogy to a current techno-

logy and its relationship to the work this thesis effort

supports. Chapter I also laid the foundation for the ensuing

chapters, discribing what was to be discussed in each of them.

Chapter II analyzed and defined the problem; what were the

data base requirements of the CSDE and how did they need to

be supported. Chapter III described in detail the rela-

tional model that can support those requirements. Following

this, Chapter IV described the step by step procedures

-. needed to implement the relational model on a general

purpose DBMS - Oracle.

Throughout this thesis effort an attempt was made to

recommend possible uses of the data base by the CSDE

subroutines. The final incorporation of the relational

model into the CSDE's subroutines will depend on individual

expertise and experience. However, there are many thingsi."

- 61

- " -. - " . . '.

; ."

to be considered in this future implementation and in the

following paragraphs I will briefly highlight some of

these.

The next obvious step is to use the relational model in

the CSDEts subroutines and make use of the Oracle DBMS. The

first part of this step would be to design and implement.4

a Translator based on the relational model. As was previ-

ously noted, the purpose of the Translator subroutine is to

make the SDE input information available to the CREATEDB1

module, which then places the data in the Primitive List and

Symbol Table tables. In parallel to the performance of this

task, a microprocessor design volume will also have to be

placed in the data base tables. This can be done using the

Application Design Interface (ADI) for those designs

currently being developed or through an interface translator

for those preexisting microprocessor designs, where it would

be too cumbersome to reenter the data by hand. Onec these

entities are in place, the Functional Mapper can be designed.

Relational DBMSts are a relatively new technology.

Their use in CAD systems is even more recent. Hence, the

amount of applicable literature is limited. However, one

thing the literature does reflect is the fact that

relational data bases are generally slow, [Ref. 7]

In light of this fact, the designer of any one of the

subroutines using the relational model will have to determine

query algorithms that optimize Oracle's efficiency and

62

. .. :. . . . ,-. .. .. -,-% i . . .' ,. - .. ; .. .- . ., . - A .. . -- = S.':+ ! , .:

effectiveness. There are characteristics of the CSDEts use

of the data base that will weight the construction of such

algorithms a certain way. For instance, when CREATEDBI

enters data into the Primitive List and Symbol Table it will

do so sequentially. There is no random generation of primi-

tives and their arguments. A Title group is defined with

the macros that will perform the given function and placed

in the Primitive List. The arguments for each macro are

then supplied with their corresponding precision parameters

sequentially.

Therefore, there will be no need for the Oracle system

to insert records between existing records. All records

will be added to the end of the last record in the table.

The algorithm should be designed to take advantage of this

fact if at all possible.

The query algorithms for the Timing Analyzer and the

Formatter will be variations on this select, compare and

insert theme. This variation will enable the programmer to

design, test and conduct performance evaluation on the

various related algorithms using the Oracle DBMS.

If during the creation of the query algorithms it

becomes necessary to modify the data base in order to

optimize Oracle's effectiveness, this can be easily done.

This is one of the benefits of a relational data base model.

The fact that the functional capabilities are incorporated in

a single module make it an easy base to transform.

6 3

-. . + . .- . . . i -

This is in effect the major contribution of this

research. Through this effort the CSDErs data requirements

were thoroughly analyzed and the information was encapsu-

lated into localized entities which form the basic buidling

blocks of the 3 major complex data structures: 1) problem

statement input, 2) microprocessor volume library 2) micro-

processor volume library and 3) the final design configura-

tion. These three structures, because of their final

relational form, can be easily modified. However, the

identification and cataloguing of their purpose and function

will probably not change drastically. The changes that will

come will probably be additions to the data base as new

requirements become apparent and necessary.

From here then, the next step is to verify that this

plan can be used effectively by the Oracle DBMS. If it is

discovered that Oracle can not meet the requirements of the

CSDE project, this thesis has provided a sound analysis of

the data base requirements, defined in Chapter II and

realized into relational form in Chapter III, for implementation

on any future system.

A User's Guide for the ADI is on file with the CSDE

project.

6%%

64

. 4 ,•.*...* . . . . -. - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --- .

APPENDIX A

CREATEDB UFI TABLES

CREATE TA3LE PRIMITIVELIST (TITLE CHAR(29) NI~T NluLL,'MACRONAmE CHAQ(25) 'JOT f;ULL,POINTERX tMUJVEQ (6))

SNOT NJLL INDICATES FIELD IS A PA'RT OF THE KEY

CRETE ABE S~'OLTAPLE (POINTERX NIJMREP(b) NOT LL

APGJMENT CHA9(25) NOT 'NULL ,

P-4 IN.M;Jk NflMPARb 6

SNEXT 9 BLOCK~S MAK(E UP THE HAQP>#AREf4AC'( TAB~LEFOR THE REALIZATION VOLUME D)ESIGN,

CREATE TABLE IDENTITYBLOCK C MICROPROC CHAR(25) NOT NOiILL,HtjmACPO CH.AR(25) NOT NULL,MILLTAATTS NUMfER(6),

CHTPCOUNT NUMRERb),LATENCY NUMRER(6),POINTER .JE())

CREATE TABLE PARAAETERBLOCK (POI.\iTFR NAJUMHE(t) NOT N1lILL,PARAMETER CHAR(25) NOT NULL,

'4 XI 'A U " NUMBERPb)

CREATE TABLE CO"NIENTFILOCKC POINTER NUJMRER(b) NJOT NULL,COAMENT CHAR(RO),MO,110 NUM9EP(b) NG T NLL);

CREATE TABLE INCLtdDE9Lr)CKC POINTER NIJMPEP(6) NOT NULL,INCLUDE CHAR(25) ,I".CID JIJ"9EPI b) NTNULL,T I AES3 NUMB E (b

CREATE TABLE CALL3LOCK onINITE: N.JUREP(b) NOT NUILL,CaLL CI-1P(25),CALLI) rjIIMBER( 6 ) "JOT NULL,TIMES NUmt-EPb))

S...65

CREATE TA6LE CALCRLOCK POINTER NIJMBER(h) NOT NUJLL,GLORVAP CHAR(25),OP CHAPC3),

RSLT CHAPC?5)oCALCIr) NUMRER(6) NOT 'iJLL);

CREATE TABLE ATTRIBIJTEBLOCK CPOINTER NUMBEPC6) 'JOT NULL,LOCALVAR CHAP(2;),OJP CH.AR(3),VAR~ CHAP(?5),RSLT CHAR(25),ATTPIO NUMHER(b) NO(T -"JJLL);

CREATE TABLE IF9LOCK (POINTER NIJMP;ERC6) 1NOT NULL,VARIA.9LEI CHAR(29),OP CHAP(3),VARIU3LE2 CHARC25),IF'4P CH-AR(25),IFMAACRO CH-AP(25),IFREO CAA(25),ID 'UMERE(6),IFID) 'IJABER(6) N*OT NULL);

CREATE TABLE TEXT9LOCK (POINTER AiJM',BEP(6) NOT Nt1JLL,

TEXT ID iJjNEkP (b) NOT NULLL);

STHE NEXT 9 9LOCKS CONTAIN THE TARLES NECESSARY FOR THEK: ~ SOFTvARE PRIMITIVES FOR THE REALIZATION VOLUME

CREATE TARLE SIDE'4TTTYRLflCK C41CPOPPCC CHAR(25) NOT NULL,Sp~mACPr) CHAR(?9) NOT NHILL,STORAGE NhJ-9ER(b),

TIvE NIfJMPFQ(61,EXTPEF Nl)~MEP(b)pPOINTER NUmPR~b));

CREATE TAHLE SPPAMETER9LOCK C0IF NUVPEP(b) '\IOT NjULL,PARAmETER CHAP(25) NOT

NULL,Kt, I % I 'M I-' 'ltlltREIP("4A xT '-I. 'lJA NUM3EP 6~

66

ACREATE TABLE SCOMMENT BLOCK P OINTER J') AER(6) NOT 'lULL,COMMENT CHAP(8O),rOkMID NUMF3ER(6) NiOT NULL)

CREATE TABLE SINCLUDFf3LOC< POINTER NIJM0BER(b) NOT NULL,INCL'ODE CHAP(?5),INCID NUP43ER(b) 'JOT NULL,TIIAES NU'ApRF-b));

CREATE TABLE SCALLRLOCK CPOPITER NU~m9ER(6) NOT NULL,

CALL CHAP(?5),CALLTD NU'ABEP(6) NOT NULL,T IMESF N U M E R~b

CREATE TABLE SCALC9LOC' POINTEP URRb NOT NULL,

GL093VAP CHA4(25),OP CHAR(3),VAR CHAfR(25),RSLT CH4P(?5),CaLCID NUMSEP(b) 'JOT NIULL);

CREATE TABLE SATTIBUTEBLOCK C OINTEP WNU-9ER(6) NOr NULL,LOCALV4R CHAR(25),OP CHAP(3),

RSLT CH-AR(25),?ATTRIfl NUMA3EQ(b) NOT NIULL);

CREATE TABLE SIFBLOCK fPOINTER Nl.JkMFEP(6) NOT NJLL,VAPIABLE I CHAR(25),OP CHAR(3),VAR149LE2 CHAR(25),IF'JP CHAR(25),TFtMACpn CHAP(25),IFPEr) CwAR(25),

PRO I D 'J'J1ABE (b)6I1) NJJMPP (b) NOT N1tLL)

CREATE TABLE STEXT9LOCw CPOINTER NtJmPr:?(~,) qOT TILL,

TEXT CHAP( 3)),

TEXT TO MU~M9EQ (b) N\OT NUILL)

67

e-r

! THE NEXT TA9LE REPRESEN"TS THE RELATIO14AL MODE-L FO'q TmE

! IDENTIFICATION TA3LE

CREATE TAHLE IDENTTFICATION (NAME CHAR(?5) NOT NULL,THEDATE DATE NOT NULL,PROlJECT C-4ARC25) NOI NIULL,

VERSIONNO1 f\IJlAAQEP(6) NOT NULL,IDPTR NUMq3EP(b,) lNOjT NULL);

LINI THE NEXT TA13LE REPRESENTS THE DESIGN CRITERIA TA9LE

CREATE TABLE DESIGNCRITERIA (IDPTP NIJMB EP(6) NOT NULL,CSOERU~l NUMPER(3) NOUT N~ULL,MsP CH4AR(25),MONITOR CHAR(25),

STORAGE 'l-mBeFR Cb),TI A E N ? l , ,-P oy EF R 4 I'A RE Pb),

CHIP AUM3EP(6));

ITHE FOLLOhING TABLE REPRESENTS THE TIMIN1"G TABLE

CREATE TABLE TT',1',IG CONTINGENCY CHAR(25) NOT NULL,TASK CHAR(?5) N~OT NUILL,ATTRHO NU'4eEPL~,),

RTTHO NljlIER(6));

ITHE NEXT TM2J TARLES PEPPESENIT THE PELATIONAL M~ODEL FOR THEHARDImARE AND SOFTtjARE PRINAITI-4E INDFX

CREATE TA9LE DRImARYINDEX (TITLE CHAP(?5) NOT NUJLL,PRI'AITIVE CHAR(?5) 'JOT NULL,PRI'VPTR '4IJPEP(b));

CREATE TABLE SEC01,rnARYINOEX CPRImPTR NL09E(,) 'JOT NJULL,P91MITIVE CHAR(25) NOT NuLL);

68

APPE[DIX. B

INTERACTIVE APPLICATION GENERATOR LISTING

;Database :CREATEn6. UF 1;ORACLE worksoace size / Context areas

;3lock name / rescrintion :SOFTIDENTITY/SOFT1 dE PEFnOQANCF SPECS;Table name :SIDENTTTY9LOCK;Check for uniaueness before insertinr -/N :N

;Disolav/duffer how Tany records

;Field naeM4ICROPROC;Tyoe of field:CHAR;Lenoth of field / Disolay lenqth :25/25;Is this field in the base tatle Y/1I,Y;Is this field oart of the orijary key Y/'JV;Field to coov orimarv key from

;Default value

;Paae :

;Line :2;Column :Ib

;promot1ICPPOCESSOR;Oisolav oromot ahove field Y/'4

;Allow fiel to be enterel I V/NV;SOL>

;Isd ie fixed lenrit YI'iN

;Auto jumo to next fiel I Y/N :

;Convert fiell to uooer cise Y/N ?N

;Helo TessaniENTER 'AICoPP3CES3,n9 TYPP i.e. VMO;Lowest value

69

. - I.

;Hiqhest value I;Field name :St4ACRO

;Tvoe of field :

CHAR

;Length of field / OisOl3v lenath

25/25

;Is this field in the base taole Y/h :

y;Is this field nart of the orimarv k.v Y/ :

Y

;Field to cooy oimary key from

;Default value

;Paqe :1

;Line :

;Column :

20

;Drotot :SOFT4A.E PRIMITIVE

;Disolay oromot ahova field Y/N :

I allow field to ne e ntere Y/NIy1;SQL>

;Is fielII fixel lenorh t, 0) :N

;Auto jurno tn newt fiel11 Y/J

;Convert field to uoner case Y/N

N;4elo message :

ENTER SOFTAARE 0oI0'TIVF rj F. r _scPrF0

;Lowest vale :

;Hiqhest value

; ield name

STORAGE

;Tyoe of fiel i

.Len lth o + fiel / Oisonl v leaot'

5/6

70

r7

.........................................

;Is this fielf in the hase table Y/liY;Is this field oart of the orimary kev Y/.I :N;Default value:

;Paqe :1

;Line :b

;ColuTn :9;Promot :

STORAGE

;DiSDlav oromot above field Y/14

;Allow fieli to be entered Y/P

;Allow field to he u'jatel Y/I

;SQL>

;Is field mndat orv Y/NN

;Is field fixel leno th Y/1N

;Auto jumo to next fieldI Y/'4N;Convert fiel d to uooer case Y/N'iN

;Helo messae :HOW MANY qYTES IS THE rTMTIVE CSE

;Lowest value

;Hiahest value

;Field name

TIME;Tyoe of fiel- :

'11 J e E R;Lenath of fiele I Disol v le not I

b/6UIs this fielI in the h11 t ole Y/l!Y

;Is this fiel ! o rt of the oriP3ry key Y/19NJ

;0efault value

;Pao-p :

<"71

to, .................................%. .*. --....

;Line

;COIu,~n :b;P romot :TIME;Di sol ay oromzot arnovap tiel' -IY/M

;Allow fieli to be enterej Y/',!y;Allow f iel-i to -e uodate, Y/*IySOL>

;Is field manlatory Y/S :N;Is field fixed leni-th Y/11N;Auto jumo to n'ext fieldI Y/P1

;Con~vert fieldl to uorner case Y/N

flielo messaoe :HON~ mA~NY CLOCK (CT) STATES DOES T,415 0,1'4rVF qFQsIf.RE?;Lowest value :

;Hiqhest value

;Field n~ameEXTREFTyoe of field

1NJM 13E 9;Lenclth of fielm / isolav ler-coth:

b/b;Is this fiel-I in~ the hase t-iole Y/"!

-;Is t-)is fiel-I oart of tlie orim'ar- iev Y/'l

; De fau I valIue

0 ;Lin~e:

;ColIU-nn

;P-omotEXTERAL QEPE; PjCEiS

72

;)isolav ornmot anove field Y/N •

N

;Allow fiel. to be entered Y/IA "

;Allow field to be uodatel Y/'

y;SQL>

I s field mandlatory Y/N

;Is fielJ fixee lenat n Y/> :

;Auto jumn to next field f/'J

N;Convert field to uorer case Y/q :

;Held messaqe :

NUm8EP OF MEMORY STATES;Lowest value •

;Highest value :

;Field name "

POINTEP

;Tyoe of fieldNJ46ER

;Lenqth of fielJ / Disola' lenth

b/b;Is this field in the base taole y/rM

Y

;Is this field cirt of the orimarv key Y/NN

;Default value :99

;Paoe :

;Line :12;Colunn :

;PromotPOINTER

;Disolay oromot above field Y~/N

N

;Allow field to b entered Y/'N;SOL>

SELECT mAX(Pq[NTER + 1)

INJTO POINTER

73

FROM SIDENTITY9LOCK

;Wessaoe if value not found :POINTER VALUE NOT GENEFRATED Ry ?JMS;Must value exist Y/ :

;Field name ;

;Block name / Descriotion :PARAMETERS/PRI'AITIVE'S I/) VARIA9LES;Table nameSPARAMETERBLOCK

;Check for unioqueness before insertino YIN

;Disolay/Ruffer how many records

;Base crt line ?3;How many physical lines oer recnrd ?

;Field name :POINTER;Tyoe of fiell :NUm8ER;Lenth of field / DiSola'y lenoth6/6;Is this fielj in the bage raole Y/N-Jy;Is thiis fieli oart of the orimary key Y/N1y;Field to CODY orimary key from

;Default value :

;O age :

;Lint :

;Column :9;PromotPOINTER

;Disolay oromot anove fie:|l Y/N

S;Of solay cromot once fir ' lock YIN

;Allow fieli to be enterel Y/'4 :

S.., ; SOL >

74-

*2*

;Is field fixed lenm th Y/'4

;Auto jumo to newt field Y/N "

;Convert fieli to uooer case Y/14N;HeliD vessa:)eENTER POINTER VALUE GFIEPARTEI) I LAST 8LOCK

;Lowest value :

;Highest value :

;Field name :PARAMETER;Tyoe of field

~CHAR

;Lenoth of fieli / niso lay lenqth :

25/25;Is this field in the base table Y/N :

y;Is this field oart of the ori-nary key

;Field to coov orimarv wev from

- .. ;Default value

;Page :

2;Line :I;Column :4.0;Promot :PARAMETER;Disolay oromot inove field Y/N

N;Disolay oromot once for block Y/1.

.N;Allow field1 to be entered Y/J

% '' ;Is field fixed lenrjth Y/' "

;Auto iumo to next field Y/14

V. ;Convert fieli to uoner cise Y/\N

75

*44 4 *. .-,. .. . . .. . ..

°-aAe . ? S. t L - '

q. . .. ... .. . . . ..... . , .. . . . . . .. ,

.lelo messaieENTER INPUT OR OUJTOtT PARA-1ETEPS FOP PPIAI[TTVE

;Lowest value

;Hiahest value

F iel1 - name

'4INIMUM;Tyne of field :

NiMBER;Lenqth of field / Dishlay lenoth

b/6;Is this field in t he baqp tale -/'Y;IS this field cart of the ofimarv key Y/*' :N

;Default value

;Paqe :

2;Line :2

;Column :9;P;romot4 IN IMU N'

;OisoIav oromot above field Y/'J

DisolaV oromot once for .)ock Yll'i

N

;Allow field to be entered Y/'qY

;Allow fiel.1 to he uodate! Y/' 1Y

;SQL>

;Is field man Iadat rry Y/N

N Is f ielId f ix ed ILanithn YI /N'

;Auto ju-o to nex t fiel14 Y/',[N

;Convert fiell to uoner c.se 1/"

N

;Helo messae :

ENTER MINITMJM P ECISIL)N F DJ: T i.e. A hits

;Lowest value

;Hinhest value :

76

1° - .. *.

". . " " . - -. . -. -.-. - . .-.. -'. . .. . . . , . . . . . . .....

m T .I F•

N. ;Field na1e :

.AXIMUM;Tyoe of field :NUMBER

;Lenoth of field / Disnlay lenothb/b;Is this field in tle base taole / :

;Is this field oart of the orim~r'y key Y/N

;Default value

;Paae :

2;Line :2;Column :

;Promot :MAXIMUM;Display oromot aove field Y/;,JN;Disolay oromot once for t]lock Y/I-NJ;Allow field to be entered Y/'i :Y;Allow fiel.i to be undateli Y/N :Y;SOL>

;Is field man-latory YIN

;Is field fixe1l len)th Y/'i:

;Auto jumo to next fiel'l Y/N :" N

;Convert fie1A to uooer case Y/N

;Helo message :

E'ITER M1A X Im IM PRF CIS'Fr1E A PmvE r j.e. P tOi'S-'"-'" ;Lowest valu-

. .... ;Highest value

S;Field nae :

;9locK ar / Doscriotion "C3MNMENT/CO0',E\jT5 FIQ PPTIAtTIVE

•7 7

" ° . - .o . v - . , • . *

p.-.7

;Table name* SCO'AMENTBLOCK

;Check for ujninueness before insertino Y/N'

;Disolav/Buffer how many recnri-s:5;3ase crt line ?

4'-.. 4

;How many ohvsical lines ner record ?(4;Field name:POINTER;Tvoe of field :.4j M 6 E;Lenath of field / £Disclay lenothb/b;Is thiis f iel-I in t'e base tahle Y/PIY;Is this, field Dart of the orjmary &rey W/JY;Field to cony Drimary key from

;Default value

;Paae :3;Line :

;ColIumn

;Promot :P3 0I N T E R;3isolav nromnr acove fieldI Y/N

;Disolay oromot once *or niock Y/',

;Allow, fiel to te enterei Y/':

*.;s f i pId f' i d In:: th Y/i

;Auto jumo ro next fi ell f/NJ"I

;Convert I iel-i rn uoner case Y/\

ENTER POTINTEP VaL iF GEtjEATEr- 1\1 rPPST -ILOCI;Lowest valja :

78

V_ ,, .. . . . . o- . - - . .

;Hiqhest value

;Field n~ame:COmmENT;Tyoe of field

L.-.CHA P en t;Length of field / Disolav iength

8O/8O;Is this field in the base ta.le y/N :Y

Is this field oart of the orimrv key i/N

N

;Default value :

;Paae3;Line :2;Colu'nn :9

;Promot :

COMMENT

;Disolav oromot atove field Y/N :N

;Disolay oromot once for bloci Y/,IN

;Allow fiel-l to be entered Y/"]

;Allow field to be uodated Y/'I

;SOL>

;Is fiel1 man-lator Y /N :N

;Is H ie fiwed I n 4th YN

;Auto jumo to newt field y/N,

;Convert field to uooer case'4;Helo messai :

COMMENTS ; ILL 6E IN THE ODEi cF Ir',pur

;Lowest value :

;Highest value :

COmID

79

*. " . .. . "S.- * " .4.- "- " - ",*"- +- " . "- " + + - • . % - - " ' +,% % - % " " - "-% "- - " - ", " - '

;Tyoe of fieli1JUMBEP;Lenath of fielo / Disnliy lenoth6/6

* ;Ts thiis fiellI in the base table YIM

*;Is this field oart of the oimaryv key YINj

;Field to cocy orin'arv key from

;Default value

3

;Line :

;Column :

;Promot :ID;DisDlaV 'ororn above fiela Y/NN;)iso~lay oromot once for block Y/,11N;Al low fieldl to be enterel Y/N1N

SELECT VIAX( C')mID + 1)

FROMl SCOMVIE'JT LOCK

; 04essacqe if valup not found1ID NOT GENEPATE) P1 ,',' ,'A;Miust value exist Y/NJY;Field name:

;Block name / escriotionI'4CLUr)F/ INCLJDE DESCRIPrnNiS;Table nameIN~JCLII 0E BLO0CK';Check for iniiueness -efor- insertini Y/'!

;Disolay/3uffe-r h-ow many reCorls2;5ase crt line?

;Hsow many ohvsicil lines ner r-sird ?

80

°''

;Field namePOINTER;Tvoe of field

• NUMBEcz

;Lenroth of field / DisolaY lenith :6/6

;Is this fiel in t he base taole Y/J,;Is this field oart of the orimary key Y/NY;Field to Coov orimary key from "

;Default value

;Paqe :'4;Line :

;Colu~n :-a 9

;promotPOI NTER;Disolay opomot above fie-l, Yi •N

;Display oromot once for t-loc Y/'4

;Allow field to be enterel Y';"Y;SOL>

Ls field fix-d lenrth Y/"I:

;Auto jumo to next fip)- ('j

;Convert fiel.i to uooer c3 Se Y/'J

;lelo message "E4TEP POTNTEP VALJF GEi!EATFDr f I r -:, I r;Lowest value

;Hiahest value:

;FielI nameINCLUDE

e :Tyne nf fieldC.4tAR

* Lencith o f #i e I / >so Ia' v I itb* l125/25

S',I t his f i I- in r) 'Ias e, t a 0 1 'e

81

-, .. - - - * . .

;Is this fieldj oart of the crj'n'aiy key, YI

;Default value

P~age:£4

-4' ;Li ne :

;Colu-rn :40

I NCLUJDE;Disolay oromot anove! field Y/- :N;Disolay ororrot once for olock YIN4

;Allow. fielj to be enterel1 Y/'1

;Allow field to be uodatg .I YIN,Y;SOL>

;Is field mandatory YININUS f ielId f ix e i Ile nh Y /N

;Auto ,u'rC to nprt fieli yINj

;Con~vert fi allI to uooer case Y/\J

*;-ieln mes a :E'JTEP NAV97 JF HI'.: OP S/.,4 PP PAIT TVE TO F r'ICLU~r;Lowest value

;-liahest valuje

IA I"JCID;TvYoe o f f i II

Lenoth of f iell Disc))lv lc-notll

;Is this f iel-j in tna tbase al (/

;Is this field oart of the orirnarv kev Y'l

;Fielj to c-)oy orimairy K-v from-

;Default value99;Paae :

;Line:

;Column :12;Promot :INCLUDE ID;Disolav oromot above field1 Y/,,JN;Di sol ay oronot on~ce for o cl Y1/i1N;Allow fielij to be entered Y1,1

SELECT mAX (INJCID + 1)INTO INCIDFROM INCL'JDEBLnCK

;Messaae if valup no found:I D NjOTr ENERATED RY 06*V'3;%lust value exist Y/N:

* ;Block nam~e / rescrict ionCALL 8LOCh</ maCFRO TO qE j5E-) cy ri!PYW'-1T c;j1jITIVE

SCALL9LOCK;Check for uni-iueness hefore inser-timi Y1/'IN;Disnlay/iluffer how -many r-ecoris2;Base crt linea

'How mnyr~ ohvsical lines rer rerd ?

P 9 I1 NT EP

;rvoe of fjel1i

*L Le n at 1 o f f i I n / tioa ln

;Is t "i S f i lI i n h~ ase mie l e Y

*;s i 'S fj i r-a rt ri t 1) ~r iT,-3rv y 0

83

;Fieldl to cooy ori'vrarv '(,0 fr~m

.4 ;Default value

Line:

;Colurnn:9;Promot:POINTER;Disoiay somorot above field Y"~

;Disrolay nromot once for olockc Y1/,

;Allow field ro be entere-1 Y'I

; SOL>

;I ieI l f i Xerl ler,3t h y /'

;Auto jumo to next fiell Y/',

;Convert fieldI to ijooer caseY1N;Helo messae3eENTER VALIJE GE7NEfATFD 0.J FIPST DaGE;Lowest valie

;Hiqhest value

;Field nameCALL;Tvofb of field1CHAR

Lernath of field /Disclay lengith:

;Is rblis fldin the r-ase taole '/*j

;Is thiq fie)i:'" of t1)0 ori'ra?, key Y/"

;Default 4alue

;Pal

;Limp

814

| 40;PromotCALL

;Disnlay oromot aoove field Y/NN;Disolay oromot once for 6lock Y/NJN

;Allow field to be entered YIN :Y;Allow field to be undate. Y/N :Y; SOL>

;Is field mandatory Y IN

;Is field fixed lenath Y1/ "N;Auto jumo to next field Y/N :N;Convert field to uDDer case f/'1N;Helo messa4e :ETER H/4 OR S/'., PRI VITIVE TO FE CALLED FPf)'Y' CI)PENiT , ACRr);Lowest value

;Higqhest value :

;Field name :CALLI);Tvoe of fieli :NUMBER;Lengt h of field / Oisplay lenots pb/6;Is this fiel in t me base taole Y/Y

;Is t is field Dart of the orimary <ey Y /,IY;Field to cooy orimary key from

;Default value

; Paae :

;Line :2;Column :t0;Promot .1CALL TIO

-. , . ......- ...... . .........-.-. , ..

;Disolav oromot irnove field Y/NN;Display nromot once for olock Y/NI

N;Allow fiels to be entered YIN

; SQL>SELECT 'AAX ( CALLID + I )

INTO CALLIDFROM SCALLBLOCK

;4essaae if va lue not found

ID NOT GENEPATED!';Must value exist Y/NY;Field name

;Tlock name / DescriotionCALC/ CALCULATION OF GLOBAL VtRjA9LES

;Table nameCALCBLOCK;Check for uniaueness befire insertina Y/lJ

N- ;Disolay/iuffer how many records :

-. 2

;Base crt line ?2;How many ohysical lines ner racord ?

o5

;Field namePOINTER;Tyoe of fiel]NUMBER;Lenoth of field / Disolay lenato)b/b

;Is this fiel- in t~'e base taole 1/N

YUs t',is field oart of t he orimary key Y /NY

;Field to coov opimary key from

;Default value

;Paqe :5;Line :

;Column8

86

.................................................~ -

~;Prormot :

POINTEP

;Disnlay oromot above field Y/'J

*. {);Disolay oromot Once for olock Y/N'J

N;Allow fiel. to t-e entered YIN

Y;SOL>

;Is field fixed len~th YP1

;Auto jumo to next fielrd YI'

N;Convert fiell to uooer case Y/1

N;Helo messa:oe:ENTER POTNTEP VALJE GENETED 0A FTRST PAGE

;Lowest value

;Hiqhest value

;Field na1eGLOBVAR.Tyoe of fieldCHAR;Lenqth of fiell I Oisclav lenith

,::..25/25

;Is this fieldI in the base taole Yl/"j

y;Is this field nart of the orimary key Y/N

N

;Default value :

;Paqe :5;Line :

;Colu-n :

;PromotGLOBAL vA4TARL;Di solay oro-ot &.ova field Y /N

;Disolay orn-or once for b!Ock Y/"J

;Allow fiel- to he enterej Y/'I

y;Allo,, fielj to he uo-jate'i Y' P4

87

*::: 8 7** .-. ***- *...*.*.

:: .:

Y

[-,OL >

l,','-;SQL>

;Is field manlatory Y/N :

N;Is field fixed len-ith Y/1:

N;Auto jumv to next field Y/ J :N;Convert fiell to uoner case Y/'J

N;Helo messaleENTER GLO6AL vAPI.9LE TO 6E CNLC'ILATED

;Lowest value

;Hiqhest value

;Field name

OP* -. ;Type of fieldJ

CHAR;Lenqth of field / risolav lenath3/3;Is this field in the base taole Y/N

Y

;Is this fiel- oart of the orimn3ry Iey Yt"

N

;Default value "

;Paqe :5;Line :2;Column :

10;Promot :OPERATOR;Displav oromot above field Y/'l :NDiso)lay oromo'" once 4 or' h-loek y/I. :

N I

;Allow fiel-l to be enteredi Y/',:YI

;Allow fiel to be uoratel Y 'JIY

;SQL>

;Is field minjatory Y/NN

88

% .,'r" " ',:-3 '_ ~~~~~. . .. . . . . . . . . . . ."- k . . . . . * . •-.. .-

. . .... . :, .. - . . . ..

TIs f ielId f ired Ilen-ih Y/IN;Auto jumo to next f isl-l Y/%N;Con~vert fiel-d to uoer case YINN;Helo messaieENTER OPFRAroR **,,,

;Lowest val-je:

;Highest value

Field name:VAR;Tyoe of field:CHAR;Lernath of field / Pisoliv lenath25/29;Is this field in the b3se t-30le Y/"I

y* ~;Is ttis fieldj rart of tlip orimary key /v

;Default value:

* ;Page:5;Line:2;Column

;Promot:VARI AFLE

D~ ;i s oI av Dorom ot ato v e f ielId Y NN;Disolay oromor once for block Y/',N;Allow fiell to be entered Y'VY;Allow fiel:1 to be uodated f/NY;SOL>

fI field r m inja t o r YY / N

;s f i 0ld' f ix ed I --n -t I Y/'I :

;Auto jumo to next field YIN

;Convert fiel-i to uoner caise f

*1' 89

- " " -". ", . .. .. - . .. . . . ' .' ,' '., " ' -- ,. . *.. . . . . '., .

4"77

N;Helo messaoeGLOBAL VAFIABLE (OPFRATOR) VAPIALE RESULT;Lowest value :

;Hiahest value

;Field name :RSLI;Tyne of fiellCHAR;Lenqth of field / Disolv lenith :25/25;Is this field in the base taolo y/YlY;Is this field oart of the orimary key Y/" :N;Default value

;Page :5;Line :3;Column :40

;Promot :RESULT;Disolav oromot a~,ove field Y/ N :N

;Disolay oromot once for nlock Y/I:N;Allow fiel to be enter'e Y/' :Y;Allow fiel- to he uodatel Y/1 :

Y;SQL>

;Is field man atory Y/I:N;Is field fixed lenith Y/" :N

A uto jLJmo tO nLeIt fiellt Y/1%

;Convert fiell to uorer case YIN :

Nc. ;Helo fessa-lo-

GLOBAL VA I49LF ()PEPATnP) VarIAQLE RESULT;Lowest value I

90 :4g

" 1I

;Hjcqhest value

;F'iecid rne

41 CALC TI

;Tycoe of fiel 'NUMBEQ

;LevnOth Off ie ) / ~~S 0 a, 1v n '

1s t hi S fi in t , bas 35 e e/~

;Is this f jell -1 art o h rmr e I

;Fiel-I to cony P rira rY ~e' v +O

;Default value9q

;Paqe:

.7. ;Line:

10;Prom~otCALC In

;Diso1ay cromnt once for kilock Y/"I

SQL>SELECT vA (CALCVr) +

INTO CALCIDFROM CALCbL'">

I D % 0 T ;E E C.T P, ;4 Y T~ j4 Y'i T

;Fiel-I nr,.!e :

;3locic n-~e )q'oi

AT T RINUTF;Table naffe

'Ye ATTPI- IITE L UCK;Check for uniaups i -4nS i ns~prt i r)'

Di so ay/- iuf r hav -. irv r'pco)rd1s

91

;Base crt lin~e ?.4t.4

* . ;How many onysical lin~es oer reccnrd

;Field n~ame:* . POINTER

;Tyve of fiell

Lenoth of field /Dis~lay lervathb/b;IS this fieli. in~ thp raS t~l a /Y;Is this fieli -j--rt of th)e orim-iry key Y/\jY;Field1 to coov nrivry kcy from

;Default value

;Paae:

;Line:1;Column~ :

;,Promot !PO N T F;Disolav coromot aho.,e field Y/"IN;Disol ay oror,'ot on~ce for t-l ock Y

;AlloM field to be entetel /I

* s f ie l i 4 x ed I en --i r Y/'

;Auto jurno to n~ext fiel'i Y/'A

;Convprt fiell to unoer case /'

;Hplo Messa'1eENTER VALjF G:;NEQ TFP im FI r T G;Lowest v.31up

;H0oes vlup-

;Field name

Li CALv'AR;Tyop of fiel-i

i. " ,.. .. . . . . . " . . . . . . . * • . ~ J .

CHAR;Length of field / Oisclay lenoth

25/25;Is this field in the h3se taols Y',r4J

;Is this fielI oart of the orim3rv k~v Y/'

;Default value

;Paae :5

rS. ;Line :

*;Column :40

;Promot :

LOCAL VARIA9LE*Disolav cromnt above field finN;Disolay oromnt once for 013Ck Y/l'N

;AII o, field to be entAr eJ Y/AJY

;Allow field to ne uodate! Y/'JY

i ; S(QL>

;Is field mandatory Y/N

;Is field fixed l 'rnqth Y'/'

;Auto jumo to next field Y'/N

N;Convert field t uooer case Y/'N;Helo messaie :

ENTER LOCAL V RIA.LE ,.CI JALU " TS T') 'IE C ILC!'LarE ,

;Lowest valie

;Hiqhest value

;Field na'ne

;Tvoe of field

CHAR;Lenglth of field / )isol length

IS this fiel d in t r - as 0 t-le Y/'J

93

,~ ,:.." 2 **K *.*.* 3 . . . .§ ..-- '-~

;Is this field nart of the orim.ry key I/ •

;Default valueli" ; Paqe :

;Line:2;Column10

;PromntOPEPA T OR

D .' I~so I a y o r on o abo v +iei i Y /NJ

;Disolay oromct once for omock Yl''N

;Allow fiell to be nrtorel 1'

;Allow field to be uodated Y/'ly'.ZI / ;S 0 L >

I s field 3n-Iatorv Y/,',j

;Is field fixed lent (/' t

;Auto ju"'o to next fiel-i Yl',

;Convert field to uoner case Y/N!

;Helo messae :ENTER **,OR,-, O /;Lowest value :

* VAR;Tyoe of fieli-CHAR

L e ;Lenith off iel / I )so1 y e,, t15/25;IS tnis fiel - in t e h,;e " Y/'I

y; s this fie) d ,v rt of r e :ri'nry k9. Yl'

NJ

;Lefault value

;Paae :

94-

, " " . % - . . . , • . .. . - . .

* - ;Lin~e2;Column~

;PromotVAR149LE;Disolay Dromot above field YINN;Disoiay oromot once for block Y/ -N

* ;Allow fiell to be entere 4 Y/'i)

Al low f ield to he undateli Y/4

;SOL>

;Is field mvaniitory Y/Nj

;s f ieId( f ir le n 0th Y/'

;Auto jumo to next f ielId- Y/PI

'Convert field to uooer cise Yl'j

* ;Helo messaie:

LOCAL VARIA63LE (OPFPATrjP) V4QAc LF PES'JLT

* -;Lowest V81lWe

* ;Hiahesr value

RSL I;Tyop of fjal-JCHAR;*Lenqth of field / rs 5 l~ iv1pn-lt k25/25;s 1,h is f iel I 1 i n t s ba s rl o /AY

;Is this fiell oart of t~~e ori 1"3rv K~ey Y*/11

F*Default value

;Paqe5;Li ne

'Coluinra 0

,.....~~ ~ . . ... .. . .. ... . .7 71 .. . .. .. . .Z7.

;PromotRESULT

N;Oisolav oromot once for Yloc1 %/N:

N

;Allow fiel to be enterp-I Y/',

Y;Allow fie],' to he uDiate:j Y/"4

y;SOL>

;Is fi eld maatorv YINN

;IS fielI- fIxel lenIt, h /' P

;Auto jumo to next field Y/':N

;Convert fieldI to ucoer c q-e Y/','

;Helo messa:ie :LOCAL VaRIaBLE (OPEARTOk) VP~I4ALE = ES:LT

;Looest value :

;H~iahest value

;F ieI i -aATTPTD;Tvoe of fieldNUMBER

;Lenath of fieli / )isrI3v leno'th :* t/b

;IS thi S fieI in te base t a le :y;Is this fielI c art of the o imar v key fIY

;Fiell to cooy o-imary ;e-y fromr

;Default valueqc)

;Pane5

;Li ne

;Co I u"nt5

;PromotATTRI9-ITF I];D isol1 -4v rr n ar v e fi 1-1 /'1

36G

Ab-R14i 999 TH4E APPLICATION OF A GENERAL PURPOSE DATA BASE 212MANAGEMENT SYSTEM TO DESIGN flUTOMATION(U) NAVALPOSTGRADUATE SCHOOL MONTEREY CA H J WALDEN DEC 83

UNCL755FIEDG 9/2 N

15mEE EEh 0

It,* *'

'4W

C2.2

I P R "LU

* '., II 1- Il.--- 122

~~NATIONAL UR AU 0 . TAAS - 63t- A

%i

"..2

'C ,

--C.

QN

;Disola3y oromot once for block Y/N

;Allow fieldl to he entereri f/Nl

- NSL>"" SELECT mAX (ArTPIO + 1)

" I4TO ATTRlD

=€" FROM SAT TIRI UTEBJLOC K

-.'J ;Dessaqe i f value not founri

.,-, ID NOT GENERATED RY SYSTEv

. , ;Must value evist YIN :

Y

;Field nae t

"-" ;Bl1ock name /Descrintion

%-:IF/SOFTAARE MACRO IF ST41TEvENTS

, ;Table namBe

' SIFBLOCK! ;Check fop uniouen,ss tefore insertino Y/11

N

% . ;Disolay/Buffr how many records

'-. ;Field naee

POINTER

;Tyoe of fie1.i

NUMBER'i ;Lenqth of field / Qisv~lav l=.noth

;Is this fieldJ in the base taole Y/11l

;Is this fiel j oart of the oriary k(ey YIN;

Y;Field to coov or'imarv key fro-

NO4 ;Default value t

;'4ust vau: xs /

Vid ;Line:

t.ec %am /Iecfr o

,%, ; C o l u m n :

KN 9

;Pomot :' POINTER.-4 ;Disolay oom t above fiel YN :

.4 ie;Allow field to h- ente ey YI' :

"" 9 7

,

h';: ":",75 ;"De""" ault 'i value' :""' ,I ; ;" "".. "" :''";::'"" "'::"""':> .. ...::'":"" """" :"

Y;SOL>

;Is field fixed lenath Y/' :N;Auto jumo to next field YIN "N;Convert field to uooer case Y/N :N;Helo message :ENTER VALUE GENERATED) ON FIRST PAG;E

-;Lowest value

;Hiqhest value :

;Field name :VARIABLE1;Type of fiel :CHAR-Lenqth of field / Disoliy lenqtth :25/25;Is this field in the base table Y/,I :Y;Is this field oart o f the Drimarv key Y/N :

;Oefault value :

;"age :

'- 6;Line :

;Column :40;Promot :VARIABLE I;Display oromot above field Y/N :

;Allow field to he entereJ Y/ :Y;Allow fiel3 to be undated Y/"J :Y;SQL>

;Is field mandatory Y/N :

;Is field fixed lenctn Y/N

. ~;Auto jumo to next fiel Y/N%N

98

:.-..

.. ... -. .A. ,, ... . . . . . . . . . .

;Convert field to uooer case Y/J :N;Help messane :VARIABLE I (OP) VARIABLE 2 = QESULT;Lowest value :

;Highest value :

;Field nanne•OP;Tyoe of fieldCHAR;Lenoth of field / Disolay lenath :

;Is this field in the hse table Y/* :

;Is this field cart of the orimay key Y/:N;Default value •

;Page :

;Line :2;Column :10;Promot :OPERATOR;Disolay oromot atlove field Y/N :

;Allow field to be entered Y/N :Y;Allow field to be uolated Y/NY;SQL>

;Is field mandatorv Y/NN

". .:-;Is field fixed length Y/N :

;Auto jumo to next field YI' :a. N

.Z. ;Convert field to uooer case (/I

;Help message :

;Lowest value :

;Highest value :

99

;Field name:VARIABLE2

9 ;Type of fiellCHAR;Length of field / Display leng~th25125;Is this field in the base ta31e Y/NJ

;Is this fiell oart of th orimary key f/':

;Default value:

;Page :

;Line :k 2

;Column :40;Promot:VARIABLE 2;Display oromot above field Y/N:~1;Al low fiell to be entered Y/NJ

.4 Y;Allow field to be UoD1atel Y/4Y;SQL>

;Is field maniatory Y/N:

;Is field fixed lenot', Y/NN;Auto jumo to next fieli- Y/14:N4;Convert fieli to uooer case i'/j

;Help messacie:VARIAB3LE 1 (OP) VAPIARLE 2 RESULT

;Lowest value:

Highest value:

Field name:IFMP;Type of field:r CHAR;Length of fieldi / isolay lenath

100

%F ---

;IS this field in t~e base tatle Y/1 :

y

;Is this field oar't of the orimarv key / :

N;Default value "

;Paoe :

6

;Line :

;Coluumn :

17;Promor :MICROPROCESSOR;Disolav oromot aoove field Y/N' :N

;Allow field to be entered y/l :

y, ;Allow field to be uodateJ Y/I

;SQL>

;Is field mandatory YINN

;Is field fixed lenith Y/'4

;Auto jumo to next field YI,1N;Convert field to uooer case Y/\14;Helo messaieENTER MICPOPR9CESSOR TYPE i.e. QO5O

;Lowest value

;Hiqhest value

;Fiell nameIFMACRO;Tyoe of fiel :CHAR

p. ;Lenath of field / Disolay lenctn

25/25;IS this field in the oase tanle YltY;Is this field oart of the orimafy key Y/' :

N;Zefault value :

Page0

101

.J . 7

Line :6

;Column :27

;Promot :S/ OR HI/ PQTITIVE NAMA;Display oomot above field Y/N :N;Allow field to te enterel 1/, :Y;Allow field to he uodatei Y/, :

-. 4 Y

;SQL>

;Is field maniatory YIN :

;Is field fixed lenqth YI:N :

;Auto jumo to next fiela VIN :

;Convert fiell to uooer case Y/'J :a-.. N

;Helo message :NAME OF MACRO IF STATEMIENT APOLIES TO;Lowest value :

;Highest value

;Field naie :IFREQ;Type of field :NUMBER;Lenqth of field I Disolav lenith :6/6;Is this fiel-I in the base ta3,le Y/N :Y;Is this fielI nart of thp ori"rv key I'. :N;Default value :

;Paoe :6;Line :

;Column :lb

;Promot :TIMES REQUTqED

102

4' : " '% 4 . ' " "- "' " . . . .. ",,-,. -. v.,-,..---. -. -4 2.--, -. .~ .~ .

;Display oromot above field Y/N :

N;Allow field to be entered Y/N :Y;Allow fiell to be uolated Y/ :Y;SQL>

;Is field mandatory YIN

;Is field fixed lenvh YIN :

;Auto jumo to next field Y/N :

;Convert field to uooer case Y/':N;Help message :

NUMBER OF TIMES PRI'IT[VE 'dILL " E USE)

;Lowest value :

;Highest value

.1* ;Field name :IFID;Type of field :NUMBER;Lentith of field / Disolay lenoth

6/6;Is this field in the base taole Y/4Y;Is this field part of the orimary Key Y/,' :

;Field to cooy orimary key from

;Default value :

;Page :

;Line :10;Column :30;Prompt :IF ID;Disolay orofot above field Y/N :

N;Allow field to be enter-ed Y/N •

;SOL>

A.,..103

'Oki

%.lip'.' : " %, ' ', % ," .'/,..;.. ." .', '; -' .. '-','..'_",. .'-,. .- ,. ,' .'. '

i ~ i ! - . l " m[ =. , . . . . . . . . . . .

SELECT %1AX ( IFID + 1)

INTO IFI)FROM SIFBLOCK

. ." ;essacae i f valIue not f otn~d

ID NOT GENERATED BY SYSTEM;4ust value exist Y/N :Y;Field name :

;Block name / Descriotion :TEXT/MACPO ASSEMBLY PROGRAM;Table name :STEXTBLOCK;Check for uniqLeness before insertin:i Y/" :N;Disolay/Buffer how many records5;Base crt line ?

;4ow many physical lines per record ?

;Field name !

POINTER;Tyoe of field :NJMRER;Lenoth of field / Disolay lenoth :b/b;Is this field in the base taole YINY;Is this field oart of the orimary key YINY;Field to cOpy orimvry Key frim

;Default value :

;Page :7;Line :!;Column :

;Promot :POINTER;Disolay oromot anove field Y/IN :N;Disolay oromot once for olock Y/NN

;Allow field to he entered Y/IN

104

.

-. . W. WL 4'. 1

Y;SQL>

;Is d ieId fixeJ lenth Y/N :

;Auto jumo to next fiel(I f/'4N;Convert fiel- to uooer case /NN;Help message :ENTER VALUE GENERATEO ON FTRST PAGE;Lowest value :

;Hiqhest value

;Field nar'e::. TEXT

EXT;Type of fieldCHAR;Lenath of field / Disolay leoth -80/80;is this field in the base tanle Y/;rY;Is this field oart of the orimarv cey Y/,"N;Default value :

"" ;Pace :- 7

;Line

;Column :b;Promot :TEXT;Disolav oromot a ove field Y/NN;(isolav oroiot once for clock Yl/, :

;Allow fiell to be entered Y/NY;Allow field to ne Undat~d Y/-1iY;SOL>

;Is field mandatorV YIN :N;Is field *ixed lerQh Y/;i

005

,a. . . . . . . , . . . , . . , . .% .: . : ,. , , , , : -,°. . , .' .. ,'. % - ; . ,, . , ., , , , .

;Auto jumn to next field Y/', :

N;Convert field to uocer case Y/NJN;Helo message :ENTER ASSEM5LY CODE

;Lowest value :

;Hiqhest value

;Field name :TEXTIO;Tyoe of field :NUMBER;Lenoth of field / Disolay lenrith :

b/6;Is this field in the base ta!le Y/h :Y;Is this field part of tie orimary key Y/lY;Field to cooy Primary key from :

;Default value99;Page :7;Line :

d d;Column :10;PromotTEXT Ir);Disolay oromot above field Y/N :N

;Disolay oromot once for olock Y/N

;Allo w fielI to be enterel I'I N;SOL>SELECT MAX (TEXTIn + 1)INTO TEXTIDFRO1 STEXTBLOCK

;Messaae if value not found :

I D NOT GEVE9ATED 9Y SYSTEm';14ust value exist Y/*J :Y;Fiell name :

106

Il'.'@ ~ . .' ' ' ; :_. .,' . .'. . - T " , '_, .,: , ' ; - - ' _ . ,_._._..'., -,'---

;~1ock name / Descri~di'~r~ :

ZEND

S.

S..1S.

S

S.

J

5,.

I

5-

.5

.5

.5

I

I

I

10 .5'

I .

4.* *5*..

;DatatiaseC RE ATED9~. UF I

4 ;ORACLE wor~sDace size /Context areas

;'Alock nam'e / InescriotionIDENTI T'/HA4~Dnj4'E PEPFnOR",iA-CE SPECIF ICAr roS;Table namreIDENT ITYBLOCK;CheCk for uniaueness hefore insertinwI Y/'!

;Disolay/53uffer how many records

;Field na~re:41CROPROC;ryoe of ie~l ICHAR

* ;Length of fiell / isolay leiatIh

;Is th~is field in the oase t~ole Y/%IY

% ; Is th~is fieli oart of toe orimiry key YINjY;Field to c)ovy orimary wey from

;Default value

;Paae :

;Line :

;Column :

;Promot :M ICR OP ROCE SSOR~;Disclay oromot above field V/N4;Allow field to he enterel Y/>iY;SOL>

;Is field fixed le Y' /Nj

;Auto jumo to next fieli YINj

;Convert fiell to unor case YIN

;Helo TessaneENTER vTC~flppCESirJP To RE OFSCE TiFr

108

4 - - -. - - ' -. i - . , . . . .- . , , .- . .

,

;Lowest value :

;Highest value :

;Field namhe :HAIMACRO,'

;Tyoe of fieldCHAR;Lencth of field / Disolay lenath25/25;Is this field in the baqe taole Y/N :

;Is this field cart f the orimary key ,l*,

Y;Field to Cooy orimarv key fr,)m

;Default value :4"

;Page :

;Line :IL

;Colun :20

4" ;Promot :

HARDWARE PRIMITIVE;Oisolay oromot arove fie?'i Y/A :

" N

;Allow field to be entered Y/IN

,;SOL>

;Is field fixed enqth YIN

;Auto jumo to next field yINN

;Convert fiel,1 to uDDer case Y/, :N;Helo messaieE14TER NAME IF HI MACRO TO SE DESCRIE, i.e. H.2AVP5b

;Lowest value

;Highest value :

;Field na~e :-MILLINATTS

;Tyoe of fieli :

109

11

;Lennth of field / Display lenoth :6/b;Is this field in the base taole Y/N

. Y;Is this field part of the orimary key Y/N :" " N

;Default value

;Page :

;Line :6

;Column :

12;Promot :MILLIioATTS

;Disolay oromot above fi-ld YINN;Allow fiell to he entered Y/N :Y;Allow fiell to be uodatel Y/N :Y;SOL>

;Is field -mandatory Y/N :N;Is field fixed Ien th YI'i :N;Auto jumo to next field /- :NConvert field to uooer case Y/%l

;Help message :ENTER POcWER C0NSUMPTTO(m EouUrE1EAjTS FORCR'0;Lowest value

;Highest value

;Field nameCHIPCOUNT;Tyoe of fiellNJMBEP

;Length of fiel / Disolav lernoith6/6;Is this field in the base t-ole YINY;Is this fiel- oart of the orimarv key Y/NN

110I.i

' .- ' '. .- .' .-.... ...- , ..... .- - ..- .- , - ., -, -, -, , . . -,.,- . = .• .- . .. -, . .. ,-.-..-" '.- .- .. , .- . , . - .. . . .. .. .. ' " , ' '";'.'-*' - '", ,- . ; . .. *''.- L, .. " . -"

• .. .'-

;Default value •

* ;Oaqe :

;Line :a;Column :12

'.. ;Promot :CHIP COUNI;Disolay orOmot above field Y/N :

;Allow field to be entered Y/N :Y;A)low field to be uodated YI', :Y; SGL>

;Is field mandatory Y/N ?

;Is field fixed lenith Y/\ :

;Auto jumo to next field Y/N :

;Convert field to uooer case f/'JN;Helo message :EITER NUMBER OF CHIP COmPONETS RECtUIRED 8Y 4ACRO APPP.

COST;Lowest value :

;Highest value :

;Field name :LATENCY;Tyoe of field :'-JMBER;Lenfath of fieli / isolvv' lernoth6/b;Is this fiel1 i , tfe base taole Y'INY

,. ;Is this field oart o0 the orinarv key N N;Default value

;Page :

;Lime*4p

• .. ,.\'V%,% 'V

%" 7

gnato

;COIuTrP :9;Promot :

LATENCY;Display Promot above field Y/N !

N;Allow field to be entered Y/N :Y

;Allow field to be uodated YIN :

y.. ;SOL>

;Is field mandatory Y/N

;Is field fixed length Y/N :

N;Auto jumo to next field Y/N .

;Convert field to uooer case 'N :

N.. ;Helo message :

;Lowest value :

;Hiahest value :

;Field name :POINTER;Tyoe of field :

NUMBER;Lenqth of field / Disolay lenoth

b/6;Is this field in the base table Y/NY

;Is this field cart of the orimary key Y/N :

4;Default value :99

;PageI

;Line :12;Column :

9;Promot :

POINTER;Display oromot above field Y/

06112

qP ~~~~~~~~.......,, ...- ..-. ., . . ...-..... . . . . ..

, '...

N;Allow fiel1 to be entered Y/N

~N" ; SOL

SELECT M6X (P3INTER #l)INTO POTNTERFROM IDENTITYSLOCK

;Messaqe if value not found :POINTER NOT GENERATED 9Y SYSTEm;:!!';Must value ewist Y/N •Y;Field name

~;Block name /Description:

'? PARAM4ETER/CONTAINS mACRO'S ARGU\4ENTS ,vITH PRECISION REQ'TS

V.. ;Table name :PARAMETERBLOCK;Check for uniQueness before insertinq Y/N :Y;Disolay/9uffer how many records :6;Base crt line ?

;How many ohysical lines oer record ?

;Field name :POINTER

;Type of field :NUMBER;LenQth of field / Display lenqth :6/b;Is this field in the base taole Y/N :Y;Is this field part of the orimary key Y/I :

".. Y

;Field to copy primary key from

;Default value :

;Paqe :

;Line :

;Column :94...

;Prompt :V POINTER

%'1

"-'.'.113

;Display oromot above field Y/N :i1;Display oromot once for block Y/N :

- .N

;Allow field to be entered Y/N :Y;SOL>

;Is field fixed length Y/IN :

;Auto jumo to next field Y/N :

;Convert field to UODer case Y/N :N

;Help messane :

ENTER POINTER VALUE GENERATED TN PPEVfl'JUS BLOCK;Lowest value :

;Highest value :

;Field name

PARAMETER;Type of field :CHAR

;Length of field / Disolay lenqth

25/25;Is this field in the base taole Y/N :

5'-% ;Is this field oart of the orimary key Y/I NY;Field to coOy orimary key from

;Default value

;Paqe :- 2

;Line :

-" ;Column :

Promot :PARAMETEP

;Disolay oromot aoove field Y/NN;Dlsolay oromot ohce for block Y'J :

;Allow fiel to he entered Y/N :Y

114''. .

S *. *. ...

..%. .e. .. " "

; SQL>

;Is field fixed lenoth Y/NN;Auto jumo to next field Y/N :

;Convert field to uDDer case Y/NJ :N;Help message :ENTER INPUT OR OUTPUT PAPAmETER FOR PPImITIVE;Lowest value :

;Hiqhest value :

. . ;Field name :•INIMUm;Type of field :NUMBER;Length of field / Display length :b/6;Is this field in the base table Y/ J :Y;Is this field Dart of the orimarv key Y/N :N;Default value :

;Page :

;Line :

;Column :9;Promot :MINIMUM

;Displav oromot above fiell Y/N :

;Disolay oromot once for block Y/N'iN;Allow field to be entered Y/N1Y;Allow fiell to he uodated Y/\JY;SQL>

;Is field mandatory Y/ N

;Is field fixed lenoth Y/N :

q..-4

-- . . .-

f 2" ' "''",% ' ""o" . '"""" ' " ""'*"."', " "'--. , - - -" "" "-"'. ."" """" . ".-.-.-,"- " ' '

JA I> -J I_.. . . . . - -~

;Auto jumo to next field Y/N •N;Convert field to uooer case Y/N :N;Helo message :ENTER MINIMJM PRECTSTnN FOP PARAMFTER i.e. 8 bits;Lowest value :

;Highest value :

;Field name :MAXIMUM;Tyoe of field :NUMBER;Length of field / Disolay lpnoth "

* . bib

;Is this field in the base table Y/N°%'

;Is this field oart of the orimary Key Y/N :

;Default value :

V ;Page :9'4 2

.;Line :2;Column :

;Promot :MAXIMUM;Disolay oromot above field Y/N •

N;Disolay oromot once for lock Y/N :

;Allow fiell to be entered Y/N1 :Y;Allow field to he uodatei Y/1 :Y;SQL>

;Is field mandatory Y/N :N

;Is field fixed lenath YIN :

;Auto jumo to next field Y/NN;Convert fiell to uooer case Y/J :

N.N

116

V.

i;elo messale :ENTER MAXIMJM RIT PQECISION FOR PARAMETER i.e. 1 hits;Lowest value :

;Hiahent value :

;Field name :

;Block name / Oescriotion :COMMENTS/COMmENTS FOR PRImITIVE;Table name :COMMENTBLOCK;Check for uninueness hefore insertini Y/N :N

;Disolay/Buffer how many records :

;Base crt line ?* '4

;How many physical lines oer record ?4

;Field name :POINTER;Tyoe of field :NUMBER;Lenoth of field / Disolav lenqth :

b/b;Is this fiel-1 in the base tacble Y/N :Y

;Is this field oart of the orinarv key Y/N :Y;Field to cooy orimary key from :

;Default value :

;Paqe3;Line :I;Column :

;Promot :

POINTEP "

;Disolay oromot above field Y/N :N

;Disolay oromot once for block (/N :

;Allow field to be entered Y/ ..Y

117.

I.,

4-,4% " '" " *"' . .. '... - 4 .- '.4. - ".-.'- *.-" -'-* , " " , "...-.," -. - - -* -" . . -'- .'. ". ".

; SQL>

;Is field fixed lenth Y/N :

;Auto jumo to next field Y/ N :

4- ;Convert field to uooer case Y/IN :N;Helo message :

ETER POINTER VALUE GENERATED IN FIRST 9LOCK OF PPIMITIVEDESCRIPTION

;Lowest value :

;Highest value

;Field nameCO MME NT;Tyoe of field :

CHAR

;Length of fiel. / Disolay length :~80/80

;Is this field in the base table Y/N :Y

. . ;Is this field oart of the orimarv key Y/NiN;Default value :

;Oage :

;Line :

2;Column :

.1' ;Promot :

COMMENT

;Disolav oromot above field Y/N :-N;Disnlav oromot once for olock l'/N *N;Allow field to he entered Y/N :

;Allow fiel to be uorlated Y/4 :Y

@ S 1S L>

;Is field mandatory YIN :

;Is field fixed Ienqt h Y/'I

L118

.o'*/*, / . a... . . . . .* ~ * **

;Auto jumo to newt field Y/NI :

N;Convert field to unoer case Y/1J :

N";Helo messale :

" COMMENT PRIITTVE FIR FETTE. JNCDERSTANOTNG OF DESIG:j

;Lowest value

;Highest value :

;Field name :

COAID;Tyoe of field :

NUMBER

;Length of field / Oisolav lennth

b/b;Is this field in the base tanle YIN :

Y;Is this field cart of the orim3ry key Y/N :

Y, ;Field to cooy orimrarv kly from "

;Default value :

;Page :3;Line :3;Column :90;Promot :COMMENT TO;Disolay oromot above field Y/N :

;Disolay promot once for block Y/N

;Allow field to be entered Y/'4 :!%'" N

; SOL>SELECT mAX (COMID + 1)INTO COvIDFROM COMmENTBLOC<

;4essaqe if value not found :

COMMENT IO NOT GENEPATED!';

;Must value exist Y/N :

Y

119

k' ,°

4.'

;Field nave :

;Block name / OescriotionINCLUDE/ DESC4IPTIfl\I OF PqJ'ATIVE TO BE T:ICLUCIC 4IrH C'JQP-jTPRIMITIVE;Table na'me

I NCLUrEBLOC '

;Check for unioueness before insertini Y/kIN;Disoiay/t uffer how many records :

;Base crt line ?S2

;How anv ohvsical lines or recowrm ?

43

;Field nave "

'N POINTER;Tyoe of fiell :4UMBER;Lenath of field / Disolay lenatrpb/6;IS this fiell in the hase t.3ole Y/NY;Is this fiell oart of the oriTary key /NJ :

Y;Field to covy Orimary kpy from

;Default value :

;Paqe :LI

;Line :1

;Column :9;Promot :POINTFP;Disolav oromot aoove field Y/I

4. N;Oisolay oromot once for nloc' Y/I :N

;Allow fiell to be entered Y/l'iY;SQL>

;Is field fixed len-ith Y/')

;Auto jumo to next field Y/J :

120

-,4'. .... ,, ,,',,. ,"".'%,, .. . ' .'., . :' .'''''.:... ., . . .".. .'.7 ..

' 44 4.4 ° ° " ",' ' .' ' ' -. . . .4,. . .. , •

"" " " "...'.-

.J7.

;Convert field to uooer case Y/'I :

;Helo message :ENTER POINJTER VALUE GENERArED FROm FIRST :LOCK/PAGE

;Lowest value

;Highest value :

;Field nale :INCLUDE;Tyoe of fieldCHAR;Lenoth of field / Disolav lnQt h :251/2 S

S;Is this field in the base tIa le Y/- :Y

;Is this field nart of the orimary key Y/NJ- N

;Default value

;Paqe :

;Line :

;Colunn :140

;Promot :INCLUDE;Disolay oromot aoove field Y/N

~;Disolay oromot once for olock Y/N

N;Allow field to be enterel Y/4 :

Y

;Allow field to be uolated Y/J :Y

: SGL>

;Ts field man.atory YINN

;Is field fixed lenoth Y/J)N

;Auto jumo to next fielI Y/NN

;Convert field to uooer case Y/N

;Helo messale

kit:

I I 1- i I ~ ~~ ~~~ * i u n- - - -] ' - - , .... ...

/..~~~J .-;4 .-.

ENTER HARDoYARE OR SOFT 'APE PRlITTVE TO RE INCL.JOE);Lowest value :

;Highest value:

;Field name ,INCID;Tyoe of fieldNUIBEP;Lenqth of field / Disolay len thb/b

;Is this fiel1 in the thase tai le Y/IjY

;Is this fieli part of the orimary key Y/'JY;Field to coov orimary key fror :

;Default value :* - 99

;Page :

;Line :2;Colu-nn :12;Promot :INCLUDE ID;Disolay oromot above field Y/N :

;Disolav oromot once for olock Y/N:N;Allow fieli t'o be enteredJ Y/'J:

;SOL>SELECT MAX (TNCIO + 1)INTO INCIDFROM I.NCLUDEBLOCK

;4essaae if value not foundINCLUDE TO NOT GE.JERATEO PY 3YSTE,! ' ';'4ust value exist Y/IY;Field name

;Block name / DescriotionCALL/DESCRIITION OF PPIM'TTIVE TJ 3E CALLED 9YCURRE NTPR l IT IVE;Table name

122

...... :... ... ,... .. .. .. . . ..*.... .. . ..A.

C ALL BL OCX;Check for .nioupness before insertirno Y/N :N;Disolav/Ruffer how many records

;Base crt line ?1

;HIow many physical lines oer record ?

;F'ield name:POINTER;Type of field:NUMBER;Lenqth of field / Display length:6/6

* - ;Is this field in the base taole Y/'1:

;Is this field part of the orimar-v key Y/N:V. Y

;Field to copy primary key fr-om

;Default value

;Paae :

;Line :

;Column:9;Promot:POINTER;D is o Iay o r om ot a be)v e fi elId Y/NJN;Display oro'not once for block V/NN;Allow field to be entered Y/NV;SQL'>

;Is field f ixed lenqth Y/N:N;Auto jump to next field Y/NN;Convert field to uooer case V/N

0 N;Help message:ENTER POINTER VALIUE GENERATED INq FiRsr RLOCK;Lowest value

123

~ **-7

;Highest value

;Field name ?

CALL;Type of field :CHAR;Length of field D Qisplay lenqth :25/25;Is this fiel in the base taole Y/N :Y;Is this field oart of the orimarv key f/N :N;Default value

;Paqe :

;Line :* I

;Column :40

;Promot :CALL;Disolay oromot above fiell Y/N :N; isolay oromot once for olock Y/N :IN;Allow field to be entered Y/1 :Y;Allow fiell to be uodateI Y/4 :Y;SQL>

;Is fieldl mandatory YINN;Is field fixed lenath Y/,4 :

;Auto jumo to next fiel Y/\J :N;Convert field to uooer case Y/'i

;Helo messaoe :

ENTER H/I.v O S/1 PRImITIVE TO 9E CALLED FQOM ClPPENT M-CRU

;Lowest value :

;Highest value

;Field name

.1*

°-S

** . . ...°S -. . 5 5 -- - -.°

.V . .. 7 - w%--. - V. W

CALLID

;Type of fieldNUMBER;Length of field / Disolay lenoth :6b/b

;Is this field in the base ta ,le Y/N :

Y;Is this field oart of the orimary key Y/N :Y;Field to cony orimary key from

;Default value :

99*' ;Page :

;Line :2

+.'"";Column :

;Promot :

CALL ID,. ;Disolay oromot above field Y/N :

NDisplay oromot once for olock Y/N:

;Allow field to be entered YIN :

;SQL>SELECT MAX (CALLIrD + 1)INTO CALLIDFROM CALLSLOCK

;Messaae if value not found :

CALL ID NOT GENERATED BY SYSTEM!!!

;4ust value exist Y/N :Y

;Field name :

;Block name / DescriotionCALC/CALCULATION OF GLOBAL V4PIABLES

;Table name :CALCBLOCK;Check for uniaueness before insertini Y/N :N

;Disolay/Buffer how many records :2;Base crt line ?

2

125

*

;How many ohysical lines oer record ?5

;Field name :POINTER

;Type of field :NUMBER

* * Z: ;Lenath of field / Disolav lenath :

6/6;Is this field in the base table YIN :Y;Is this field part of the orimary key Y/NY;Field to cOoy orimary key from

;Default value :

;Page5

;Line :1

;Column :

- . ;Promot :POINTER

;Display oromot above field Y/N

N;Disolay oromot once for block YIN :

NV ;Allow field to be entered Y/N :

Y; SL>

;Is field fixed lenoth (/N :

1

;Auto jumo to next field YIN :

,.4, ;Convert field to udder case Y/I, :

N;Held messape :

" ENTER POINTEP VALJE GENERATErD IN FIRST B3LOCK

;Lowest value :

;-4iqhest value :

;Field name :

GLOBVAR

;Tyoe of field :CHAR

126'I

. . -.

.4*;--~ * %

;Lenqth of field / O;solav lenith :

25/25;Is this field in the base taole /I :

4 Y

;Is this field cart of the orimary key Y/N :

N;Default value :

;Paae :5;Line :

I;Column :40

;Promot :GLOBAL VARIAILE

;Disolay oromot above field Y/N :

N

;Disolav oromot once for block Y/N :N4;Allow field to be entered YI/ :

y;Allow field to be uodatel Y/J :

Y

;SOL>

;Is field mandatorv Y/J :N

;Is field fixed len~th YIN :

N

"-" ;Auto jumo to next field Y/N :

N;Convert field to uooer case f/% :A;Helo message

ENTER GLOBAL VARIABLE TO tE CALCULATEr)

;Lowest value :

;Liqhest value :

;Field name :OP

;Type of field :

CHAR;Lenoth of field / Disolay le, oth

3/3;Is this field in the base taole Y/J :

;o." -,

A

127

"' 4 4i" . . - * . -, . . " - . : - - ' '. -"* -. . . . - . -." -. . 4 . - " .'. . . . . .*-" " - . . .*.w ;; , ,. ........ ......"."' ". .".". ." ".".' ".".' "." ". ." ". ."" ' " ' ' ' " --" " " " "

;Is this field oart nf the orimary kev Y/i

;Default value :

;Paqe :

;Line :2;Column :10

.4 ;Promot :

OPERATOR

;Display oromot above field Y/N

;Display promot once for block Y/',i :

;Allow field to be entered Y/N :

Y

;Allow field to be uodated Y/JY

;SQL>

;Is field mandatory Y/N

;Is field fixed lenath Y/ :N

;Auto jumo to next field Y/N :N

;Convert field to uooer case Y/4 :

N;Helo message :ENTER OPERATOR **,*,+,-,/

;Lowest value :

;Highest value :

;Field name :

VAR;Tyoe of field :CHAR;Lenqth of field / Disolay lenath

25/25;Is this field in the base ta, le Y/N :

;Is this field part of the orimary key /N :"

;Default value

LLk

I|I:

:12

4,4 ..4 .-4'.':---'-"/ .?".-'-:.;.- . .- '.- -,. -,"-"- .-.- .--.."'.,''.'.v -5,,.% -).-. .,

* ;Page :

;Line :2;Column :40;Prompt :VARIABLE;Display oromot above field Y/N :N;Display oromot once for block Y/N :

;Allow field to be entered Y/N :Y;Allow field to be uodated YIN :Y;SQL>

;Is field mandatory Y/N :

;Is field fixed length Y/Nly;Auto jumo to next field Y/N :

;Convert field to uooer case Y/J :

;Helo message :GLOBAL VARIABLE (OPEPATOR) VARIARLE =SLT;Lowest value :

* ;Highest value :

;Field name :RSLT;Tyoe of field :

CHAR;Lenqth of field / Disolav lenth :25/25;Is this field in the base teole Y/IJNY;Is this field oirt of the orim ry Kpv f/'1 N;Default value :

;Paqe :

5;Line :

• s.

129,'t,

. * 2*'29 - .,

.'-". . .. .. ..- . .- . . . , .° '

I:.:" .%

;Colunn :40;Promot :RESULT

;Display oromot above field Y/N .N1 ;Disolay oromot once for block Y/'j :N;Allow field to be entered Y/N :Y;Allow field to be undated Y/N :Y;SQL>

.. ;Is field mandatory Y/N :

;Is field fixed length Y/N :

;Auto jumo to next field Y/N :N

.*.-" ;Convert field to ucoer case Y/N :*~N

;Helo messaqe :GLOBAL VAPIABLE (rJPEPATOR) VARI-RLE PESULT

*;Lowest value

;Highest value :

;Field nane :CALCID;Tyoe of field :NUMBER;Lenath of field / Disolay lenth .6/6;Is this field in the hase table Y/N

;Is this field oart of the orimarn y key Y/11V

, ;Field to cocy orimarv key from

;Default value:

;Paae :

;Line :"5* '4

;Column :

103

'.Z.- 130 **

. . . --

'/'"',;:.,' .",";',':,':":: ,';. .:.':>. -;.• . .-.-:' > .:-.:-.:'. .- -i.;--.-:--.. .- , ...-.-. . .*. .- -.--.. -..

;Promot ?

CALC ID;Display oromot above field Y/N

. . N

;Display oromot once for block YIN •

;Allow field to he entered Y/N :Y;SQL>

*:: SELECT mAX (CALCID + 1)INTO CALCIDFROM CALCBLOCK

; 4essaqe if value not foundeCALC ID NOT GENERATED BY SYSTE'A!U!!;Must value exist Y/N :Y

;Is field fixed length yINN;Auto jumo to next fiell Y/%

;Convert field to uooer case Y/49. N

;Helo messae :VALUE SHOULD BE GENERATED BY SYSTEM AT COYMIT TI E;Lowest value :

;Highest value :

;Field name :

;Block name / Descriotion :ATTRISUTE/ CALCULATION OF GLn9AL VARIAbLES

;Table name :ATTRIBUTERLOCK

;Check for uniaueness before insertinq Y/N :N;Display/Buffer how many records2

;Base crt line ?

;How many physical lines per record ?5

;Fiell name :POINTER;Type of field :NUMBER;Lenath of field / Disolqy lenato :

131

;Is this fielI in the base table y/rj :

Y;Is this fiel- oart of the orirarv Key Y/NY;Field to COoy orimary key from :

;Default value :

;Page :

;Line :

;Col unn :9;Promot :

*POINTER;Disolav promot aoove fieli Y/N :

N;Disolay promot once for vlock Y/N :

;Allow field to he entereJ Y/'4V;SOL>

mN

-';Auto jum to next fiel Y/,N

" . ;Convert field to uooer case Y/'J :N;Help messaoe :

* ENTER POINTER VALJE GENEPATEn FROMl FIRST 3L9CK/P~rE;Lowest value :

;Hiqhest value

;Field name :LOCALVAR;Tyoe of fiellCHAR

;Lenqth of fijll / !iS)j lay lenqth25/25;Is this fiell in the base taole Y/IY

;Is this fieldl oart of the orimarv Kev Y/N

;Default value:

132

i:: ; ,; ::-: - ,- • " , , - - -. ,-1. - -a ****~ .*,..' -, *. . ,,- -. ,-. .. .

;Page :

;Line :

;Column40;Promot :LOCAL VARIABLE;Disolay oromot above field Y/N :

;Disolay oromDt once for block Y/Nj

;Allow field to be entered YIN :

".- ;Allow field to he un,lated Y/ :Y

-" ;SOL>

;Is field mandatorv Y/NIN;Is field fixed ler th Y/MN;Auto jumo to next field Y/NN;Convert fielI to unoer case Y/N :N;Helo message :ENTER LOCAL VARIABLE VALUE TO BE CALCULATED;Lowest value :

;Hiqhest value :

;Field name :OP;Tyoe of fiell :CHAR;Length of field / Oisolay lenath3/3;Is this *iell in the base taole Y/NY;Is this field Dart of the crinarv key Y/i :

;Default value :

;Page :

. ;Line

133

......................... ......... .. ...

;Columin :to;Promot :OPERATOR;Disolay oroniot ah'ove field Y/NN;Disolay oromot once for olock Y/'J:N;Allow field to he entered Y/'N :y

'4;Allow fiell to be undated Y/NJy; SQL)

;Is field mandatory Y/NN;Is field fixed len!3th Y/11

Auto jumo to next field Y/N

Convert field to uooer case ,/N

;Helo messai. :LOCAL VARIA3LE (*,,,,)VARTALF P ES'JLT;Lowest value :

;Highest value :

;Field name:VAR;Tyoe of field :CHiAR;Lenth of field o fisolav lenot/ :25/25;Is this field in the ase tanle YINy;Is this field oart of the oriary key YN

;Default value:

;Paqe :5;Line :2;Column :

;Promot :

VA3

;TieoJf elpC-A;L n t f fi l 4s l:v l~ t

25/2

;Is thi . iel.. . . . . . . . . . . . . Y '

Y4 . . - . -;Is this. .. . .. .. . .. . .. .. . .. . .. .. . .. . .. ../- 4

5'.17741.

VARIABLE;Display oromot above field Y/NN

;Display oromot on'ce for blocic y/rj

;Allow fiell to be en~tered Y/NY;Allow field to be uodated Y/NY

K-;SOL>

;Is field maniatory Y/N

;Is field fixed lencth YIN.1;Auto jump to n~ext field Y/N:

5' ;Convert field to uoper case Y/NI

;Help messaqe:'5' LOCAL VARIABLE (fPERATOP) VAPTA3LE R E~tJLT* . ;Lowest value:

* ;Highest value

;Field niamieRSLT;Type of fieldCHAR

55~5;Length of field /Disolay lenat~ :?5125;Is this field ir' t'ie base ti~Ole Y/NY;Is this field oart of the orimrary Icey Y/1J :

* *Default value

;Page:5

-'55 ;Line :3;Column

;Promot :RESULT;Display oromnt above field Y/1,

;Disp'lay oromot on~ce for block 'f/N

135

;Allow fieli to be entered Y/N :Y;Allow fiel' to he uodated Y/N

Y;SQL>

;Is field mandatory Y/N

NNV;Is field fixed lenqth Y/N

;Auto jumo to next field Y/\j

;Convert field to u~oer case Y/:

;Help message :RESULT CAN CONTAII INTERMEDIATE OR FINAJL RESULTS OF VARCALC.;Lowest value

;Highest value :

;Field name

ATTRI r);Type of fiel :'NJMBER

;Length of field / Disolay lenat :6/6

;Is thiis fiel in the bise tan le Y/ :Y;Is this fiell part of the orirary key Y/N :

Y;Field to copy primary key from

;Default valueQ9;Page :

;Line :

;Column :is

;Promot :ATTRIBUTE IO;Display oromot above field Y/N

N;Display oromot once for block Y/N

4 136

• ,.

. . . ... _ -. , . ,. -_ _,, ,-

;Allow field to be Pntere Y/\J :Y

;SOL>SELECT MAX (ATTRID + 1)INTO ATTRIDFROM ATTPIBJTERLOCK

04essape if value not foundSYSTEM DID NOT GEIERATE ATTRI3UTE ID;4ust value exist YINY

;Is field fixed length Y/IN;Auto jumo to next field Y/N :N

;Convert field to uocer C3se Y/1)

N

;Helo messa~e :

ATTRIBUTE ID IS SYSTEm GE iRATED jNir IS A KFY FIELD

;Lowest value :

;Hiqhest value

;Field name :

;Block name / nescriotionTF/DESCRIBES PRIMTIVE IF STATE'APITS

;Table name :

IF9LOCK

;Check for unicueness before insertini Y/NNJ

;Disolay/8uffer how many recordsI

;Field name :

POINTER

;Tvoe of fiell :

'JUMPER;Lenqth of fiel / isnlav I'E,3t h6/6

;Is this field in he basP t : le Y/NY

;Is this fielI oart of the ori'-ary key Y/ l :Y

;Field to cooy orimarv Key from

;Default value

;Paqe :

137

4.'

%-

b4

;Line :I;Column :

;Promot :POINTER ,

;Disolay oromot above field Y/N :

N;Allow field to be entered V/N :

:: Y: ;SOL>

;Is field fixed lenith Y/N

r, N

;Auto jumo to nex t field YIN :

;Convert field to uooer cise YIN1,, N

;Helo messaI PS" ENTER POINTER VALUJE GENERATED IN FIRST 9LrCK/PAGE

;Lowest value

;Hiqhest value

;Field na-e :VARIABLE1;Tyoe of fielJI :CHAR;Lenath of field I Disolav lenath :

i ?5125

;Is this field in the base taole Y/NY;Is this field oart of the orimary key Y/NN

;Default value

;Page :b

;Line :1

;Column :40;Promor :VARIABLEI;Disolay oromot above field YIN

;Allow fiell to he entered Y/"j

138

Y;Allow field to be uodatel Y/'4Y;SQL>

;Is field mandatory Y/N •

N;Is field fixed length V/!J :N;Auto jumo to next field Y/N :-N

.. ;Convert field to uooer case Y/% :N;Helo messaie :VARIABLE1 (OP) VARIALE2 qsRESULT;Lowest value :

;Highest value

;Field name :OP;Tyoe of fiel :CHAR;Lenoth of field / isllar lenoth :3/3;Is this field in the base taole Y/ :Y;Is this field oart of the orimary key Y/NN

;Default value :

;Pacqe:b;Line :2

;Column :

to;Promot :OPERATOR

,.K ;Disolay oromot aoove field V/N •

;Allow field to be entered Y/"I

Y;Allow field to be uodated Y/N :

;SOL>

;is field mandatory Y/N

139

*1=°..%

N;Is field fixed length Y/N N;Auto ju1o to next field Y/N

N;Convert fielI to uooe P case YIN :N

;Hein mvessaae:RELATIONAL OPERATOR (=,,>,<:,>)

;Lowest value :

;Hiqhest value :

;Field name :VARIABLE2;Tyoe of field :CHAR;Lenoth of field / Oisolav lenoth :

25/25;Is this field in the base taole Y/N :Y;Is this fieli oart of the orimary key Y/.

N;Default value

;Page :b

;Line :2;Column :

;Promot :

VARIABLE2;Disolay oromot above field Y/N :

;Allow field to be entered Y/N

Y;Allow field to be uodatel Y/j :

V:.-.--: ; S QL'•

;Is field manlatory Y/N :

;Is field fixed lenoth Y'1 :

-V N;Auto jumo to next field Y/N :

N- " ;Convert fiell to uover case Y/N

3140Q

... . . . . . . . ..

,.... _ .. ... ....... ,1................ - , -, , ",.. ,.. .. C , ... .

N;Heln messaqe :VARIABLEI (REL OP) VARIABLE2 RESULT

;Lowest value :

;Hiahest value :

;Field name :

IFMP;Tyoe of field :

CHAR

;Lenqth of field / Disol y lenoth :25/25;Is this field in the base table Y/N :Y

;Is this field oart of the orimary key Y/N :N;Default value :

;Page :

6

;Line :4

;Column :

16;Promot :4ICROPPOCESSOR

;Disolay oromot above field Y/I N

N

;Allow field to be entered Y/NY;Allow field to be uodated Y/N

Y

;SQL>

;Is field mandatory Y/.N

;Is field fixed lenoth Y/N :N;Auto jumo to next field Y/N :N

;Convert field to unoer case Y/'j :N

;Helo messaieENTER mlCROPP)CESSOR TYPE i.e. 08O

;Lowest value :

;Highest value :

,"--

Ar.4 Id

W'I

.6°

. ;Field amhe I

IF A c O

,. ;Tye of field

CHAR;Lenqth of field / Disolay lenath :

25/25;Is this field in the base table Y/N :

Y;Is this field Dart of the orimary key YIN :N

;Default value :

;Page :

6;Line :6;Column :27;Promot :

S/W OR H/A PRIMITIVE NAME

;Display oromot above field YIN :

N;Allow field to be entered Y'1/i :

Y;Allow fiell to be uodatel Y/N :y

;SQL>

;Is field mandatorv Y/N :

N;Is field fixed lenqth ylr,j :N

;Auto jumo to next field YIN :N

;Convert field to uooer case f/I :

N;Helo messaqe :

ENTER mACRO TO 4F CALLED OR T'JCLiJUED

;Lowest value :

;Highest value :

;Field name :IFREG;Tyoe of field :

NUMBER;Lenqth of field / Disolay !ennth :

V

142

6 4

6 Ii2 *

do- F W I~F "F -.

,,*

6/6;Is this field in ttie base taole Y/N :Y;Is this field oart of the orimary key yI :N;Default value :

;Page :6;Line :8

;Column :16;Promot :

N,. TIMES PEQUIRED;Dislay oromot above field Y/NJ :N;Allow fiell to he entere1 Y/' :Y;Allow field to be uodatmd Y/N :y

"" ;SQL

-. :Is field mandjtory Y/N :

;Is field fixed lenoth Y/% :N;Auto jumo to next field Y/j :N;Convert field to uooer case YIN :4;Helo messa e :E4NTER NUM7HE4 IF TfvES P'v TJVE ,ILL BE USFD;Lowest value :

;Hiqhest value :

;Field name :iFID;Tvoe of field :NUMBER;Length of field / Disolay lenoth :

6/6;Is this field in the base tatle Y/N :Y;Is this field oart of the orimary Key /N YY;Field to coov orimary key from

*°

. ***d*. *""- •--'-"€ " " "•o••. . . .. , .-" " -" """ " " " " -.','AI'.'_ _' .- ",. .-,"., ," *' , . *..- . " .. ",- -,- .. ,. .. . . " .j

. .. . - - - - -.-. . .- . . . ..- ° ,-.

"v"'.o. . o

;Default value :99;Page :

• 6

* ;Line:to;Column :30;Promot :IF ID;Display oromo" above field YIN :

N;Allow fiell to be entered YIN

Y

N;SGL>SELECT MAX (IrD * 1)INTO IFIDFROM IFBLOCK

;4essage if value not found :ID NOT GENERATED;Must value exist Y/N :

;Field name :

. ~ ;Block name / Descriotion :TEXT/ MACRO ASSEMBLY PROGPAM1

;Table name :TEXTBLOCK

;Check for uniaueness before insertina V/N :

N;Disolay/Suffer how many records :

. ;Base crt line ?3;How Many physiCal lines oer record ?

;Field name :POINTER;Type of fiel :NUMBER

;Lenqth of field / Qisolay lencth :

b/b;Is this field in the base table YIN :

Y1s this fieli oart of the orimarv keyv Y/N

•• .. • ,o° ° -.. . % .. % .. . .. . .. . . . . . . . .

*_ -, ,* . *. * *. .,,..., . ... . .. ,,, . . . ...... ,,.., ,. ,..** - '. .- .. .....'.. .'.- .. • -. Lv3-.. • .' .'2' '," -...:. * -.~ .- , -~..§-

I e 1 .114 4I i i l I , id ' I " . - . ; , . . _% . " ,. ,- . ._,W. , . .

.. .

;Field to copy orimary key from :

;Default value :

;Page :7;Line :I;Column :9;Promot :POINTER;Disolay oromot above field YIN :

N-:w ;oisolav orOmot once for block YIN :

4-. N

;Allow fiel1l to be entered Y/A :

V Y-.

- ; SOL>

;Is field fixed lenath Y/IN :

N;Auto jumo to next field Y/'

;Convert field to ucoer case Y/N :

N;Helo messaae :

. ENTER POINTER VALUE GENEQATEI) TN THE FIRST PLOCK

;Lowest value :

*-" ;Hiqhest value :

;Field name :TEXT;Tyoe of field :CHAR;Lenqth of field / Disolay lennth

80/80;Is this field in the bose taole Y'l :

Y;Is this field oart of the oriT rv key Y/ :

N;Default value :

;age :7

;Line :2

'145

.p.e

* ;Column :6;Prompt :TEXT;Display oromot above field Y/J :N;Display oromot once for block Y'/N :N;Allow field to be entereo Y/N :Y;Allow fieli to be updated Y/N :Y;SQL>

;Is field manlatory Y/N :N;Is field fixed lenith Y/' JN;Auto jumo to next field Y/NN;Convert field to uooer case Y/N :N;Help messaie :ENTER ASSEM9LY CODE LINE;Lowest value :

;Highest value :

;Field name :TEXTID;Tyoe of field :NUMBER;Lenqth of field / Oisolay lenoth :6/6;Is this field in the base taole Y/I :Y;Is this field part of the orimary key Y/NY;Field to coov orimary key from

.

;Default valueq9

; Page :7;Line :3;Column :

10

-.. ' . " ." .° 4 .." °" =- . . . . . . . ." ' e=.'".. w', q" " '.=" " """ ' wW ,r ". *, " ". "" , .' .. • '..- '. '- '-,, .".''*,,,....- ,'-.' ,'_',_.'..% =. ,%' '.,, .' .- .'-.-.,.' = ." •"-" • .. ,-.

;Promot :

TEXT ID;Displav oromot above field Y/N :

N;Disolay oromot once for block Y/N :N

.-.. ;Allow field to be entered Y/N :

N;SQL>SELECT 4AX (TEXTID + 1)INTO TEXTIDFROM TEXTBLOCK

;4essaae if value not found :

ID NOT GENERATED 6Y SYSTEM;Must value exist Y/N :Y;Field name

;Block name / OescriptiOn :

%END

,

IT.-6A

%

LIST OF REFERENCES

1. Ross, A.A., Comuter Aided Design of Microprocessor-basedControllers, PhD. Dissertation, University of California,Davis, June 1978, pp. 10-15.

2. McWilliams, Thomas, "SCALD: Structured Computer AidedLogic Design", 15th Design Automation ConferenceProceedings, 1978, Las Vegas, Nevada.

3. Sherlock, Barbara J., User-Friendly, Syntax Directed Inputto a Computer Aided Design System, Master's Thesis,Naval Postgraduate School, Monterey, California, June1983, pp. 22-32.

4. Ross, A.A. and Loomis, H.H. Jr., "Computer Aided Design ofMicroprocessor Based Systems", 15th Design AutomationConference Proceedings, pp. 227-230, IEEE.

5. Oracle Users Manual, Rlational Systems Incorporated,March 1983.

6. Date, C.J., An Introduction to Database Systems,Addison-Wesley Publishing Company, pp. 382-384, 1977.

7. Katz, Randy H., "David: Design Aids for VLSI UsingIntegrated Databases", IEEE TC Database EngineeringBulletin, Vol. 5, No. 2, June 1982, pp. 29-32.

1u8

"%

.

'v -. ,7 .. ;-5. -,,-'.- ..' -'<,;..,-? .' .v --' .. '... ..- - . . . • - ..-... -. - . .8, .. ..L . .,I, . _ , . . .., , -_ . ' , . .. . . - ,. . ,- : , . _ - , . .

BIBLIOGRAPHY

Matelan, M.N., "Automating the Design of Dedicated Real Time

* Control Systems", Preprint UCRL-78651, Lawrence Livermore* Lab, 21 August 1976.

149

L - 7

7 - 7 - ..

INITIAL DISTRIBUTION LIST

No. Copies

1. Defense Technical Information Center 2Cameron StationAlexandria, Virginia 22314

2. Library, Code 0142 2Naval Postgraduate SchoolMonterey, California 93943

3. Chairman, Code 52 2Department of Computer ScienceNaval Postgraduate SchoolMonterey, California 93943

4. LTCOL Alan A. Ross. Code 52Rs 4Department of Computer ScienceNaval Postgraduate SchoolMonterey, California 93943

5. LT Heather J. Walden, USN 1304 Mansion DriveAlexandria, Virginia 22302

.15

• .

• "< 1 5 0

.p.

-n - - . . .

* :- *~ 4 j~ ~t ~ ,..7.~Nb - sk

9

t

I I

*~r'

4-. -t /~ 4~j~t1

.,~ ~r-~ .

<A ~ "A'.' - ~ iV* ~

>2 , LVI'

-. *. ,.4.

, *..

A

<4* 10?

U

I i '4*' CC--

r-' .t I X '1r"4 *1.~*

\I~'"~ A~

-

N.. .

* 4~44.f~ 4 4 9 - ~2.. 2*t '19-N--- - -

* 7*

U'* 'it

At ~' -..- -4---.

V

-I.~)* 4 . ~'

S

*,e~.

ILi.

"I . Aft 1 ,r . .. :.t.. N

.