/'AD-AI82 OIL INTEGRAJE; INF81MAlT mlg4 lON (IUPPOCI UOLurn 5

7 U4CLASSITIED TLAL[HF ET A LI 1O 1~ 10b~q2V F/G 12/5 ML

II

L 36

',,

I

AD-A182 011 m ,L. COPYAFWAL-TR-86-4006Volume VPart 23

INTEGRATED I1FORMATIONSUPPORT SYSTEM (IISS)Volume V - Common Data Model SubsystemPart 23 - ND L Precompiler Build Source Code

Product Specification

General Electric CompanyProduction Resources ConsultingOne River RoadSchenectady, New York 12345

Final Report for Period 22 September 1980 - 31 July 1985

November 1985

Approved for public release; distribution is unlimited.

MATERIALS LABORATORYD T CAIR FORCE WRIGHT AERONAUTICAL LABORATORIES ELECTEAIR FORCE SYSTEMS COMMAND JUL02 tMtWRIGHT-PATTERSON AFB, OH 45433-6533

E

6 30

Unclasified

REPORT DOCUMENTATION PAGE

Unclassifileda SECU~m~v CA.&99#f@C?@.in LWTOSIYW 3 0ISTRPIU71OAVAIa.A11616TV 09 POR?

Approved for publico release;26@ a D~~i.,@~O*e~0S'au. distribution Is unlimitted.

4. VILAPm. III amugmomAtkmZAT1%AILIG .ua kjusBBs s. MukaTOn,.G @AGA&faZA?,Ok AIRPORT NW061111111

AWAL-TR-86-4006 Vol V.* Part 23

6& 00AW1 9 09@AMRh.@ CAGalIZATION IL Office S 'MOO16 g & A Of WONItO~sftORAIZATION4

Geneal Xectrc Co W yAFVAL/NL&TC

ft. A0949811 Wits. Saman ZIP Clk TI D9 et. SawISW~p and s ip Conuo

a River so R~B N 53363Schnectady. NY 12345 AF*034334

s MM of PUow" DosofSDAmm OPPAC IMD016 0 .vanOauAMW gT UMN 6"76qatDNT1014CATON &JUMBIm

Air Force Systems Comad" owr *1ArUY I3658OCa. A@OA8 C v SN,psadw ZIP Cail 10 soumct oDWuw IN OB I I

Wright-Pattraem An. Ohio 45453 1AAAIN900 "a #AD No.

ToIT7500 62 01

(Sea Reverse)11. 094A16 &, UYUSI6

Althoff. J7. L. and Apicella. H. L.

13. ?'Vl Of AIRPORT 13. Ta09 COVISIbo 14. save OF RI" ,..o o.n, 1. eAGI COuaalINal YeebbieaI eRe.rs II Se Pt 1980 - 31 hUI, 04 1 95 les oveamr 40

Is.aw"e "?..vA W 11Tbow @NThe computer software contained berein are theoretical and/or

SCam Peojftt ?wleWIty 020 references that In so way reflect Air Foroe-owned or -developed

11 OGat. COOlS IiS.5uSACI Tanta femba. so Mm VInegmap eWaa abahm"W brfia,

130 mob

)This document Is the product specification establishing the design* implementation of the IISS Configuration Item PREIl which will

recombine the original user Input program along with generatedmodifications Into a single program file.

uwCa~sEi DRU W SAWAS, Wet .C)WcW10 Unclassified

DO FORM 1473. 0 APR 68gO911e Oft I JAN a oOa0161v. unclassifiedgSCuaslY gg.AUIP1GAYIOft Of t~i Mad

Ake___________

I.

11. Title

Integrated Information Support System (IISS)Vol V - Common Data Model SubsystemPart 23 - NDML Precompiler Build Source Code

Product Specification

A S D 86 145717 Jul 1986

Aocession ForNTIS ORA&IDTZC 14BUnannounoed ]Justifloatl-

Distribution/

Availability Codes

Avil and/or

DIst Spca

I.

PS 620141259

1 November 1985

PREFACE

This product specification covers the work performed underAir Force Contract F33615-80-C-5155 (ICAM Project 6201). Thiscontract is sponsored by the Materials Laboratory, Air ForceSystems Command, Wright-Patterson Air Force Base, Ohio. It wasadministered under the technical direction of Mr. Gerald C.Shumaker, ICAM Program Manager, Manufacturing TechnologyDivision, through Project Manager, Mr. David Judson. The PrimeContractor was Production Resources Consulting of the GeneralElectric Company, Schenectady, New York, under the direction ofMr. Alan Rubenstein. The General Electric Project Manager wasMr. Myron Hurlbut of Industrial Automation Systems Department,Albany, New York.

Certain work aimed at improving Test Bed Technology hasbeen performed by other contracts with Project 6201 performingintegrating functions. This work consisted of enhancements toTest Bed software and establishment and operation of Test Bedhardware and communications for developers and other users.Documentation relating to the Test Bed from all of thesecontractors and projects have been integrated under Project 6201for publication and treatment as an integrated set of documents.The particular contributors to each document are noted on theReport Documentation Page (DD1473). A listing and descriptionof the entire project documentation system and how they arerelated is contained in document FTR620100001, Project Overview.

The subcontractors and their contributing activities wereas follows:

TASK 4.2

Subcontractors Role

Boeing Military Aircraft Reviewer.Company (BMAC)

D. Appleton Company Responsible for IDEF support,(DACOM) state-of-the-art literature

search.

General Dynamics/ Responsible for factory viewFt. Worth function and information

models.

iti

Ii

PS 6201412591 November 1985

Subcontractors Role

Illinois Institute of Responsible for factory viewTechnology function research (IITRI)

and Information models ofsmall and sedium-size business.

North American Rockwell Reviewer.

Northrop Corporation Responsible for factory viewfunction and informationmodels.

Pritsker and Associates Responsible for IDEF2 support.

SofTech Responsible for IDEFO support.

TASKS 4.3 - 4.9 (TEST BED)

Subcontractors Role

Boeing Military Aircraft Responsible for consultation onCompany (BMAC) applications of the technology

and on IBM computer technology.

Computer Technology Assisted in the areas ofAssociates (CTA) communications systems, system

design and integrationmethodology, and design of theNetwork Transaction Manager.

Control Data Corporation Responsible for the Common Data(CDC) Model (CDM) implementation and

part of the CDM design (sharedwith DACOM).

D. Appleton Company Responsible for the overall CDM(DACOM) Subsystem design integration

and test plan, as well as partof the design of the CDM(shared with CDC). DACOM alsodeveloped the IntegrationMethodology and did the schemamappings for the ApplicationSubsystems.

iv

PS 6201412591 November 1985

Subcontractors Role

Digital Equipment Consulting and support of theCorporation (DEC) performance testing and on DEC

software and computer systemsoperation.

McDonnell Douglas Responsible for the support andAutomation Company enhancements to the Network(McAuto) Transaction Manager Subsystem

during 1984/1985 period.

On-Line Software Responsible for programming theInternational (OSI) Communications Subsystem on the

IBM and for consulting on theIBM.

Rath and Strong Systems Responsible for assistance inProducts (RSSP) (In 1985 the implementation and use ofbecame McCormack U Dodge) the MRP II package (PIOS) that

they supplied.

SofTech, Inc. Responsible for the design andimplementation of the NetworkTransaction Manager (NTM) in1981/1984 period.

Software Performance Responsible for directing theEngineering (SPE) work on performance evaluation

and analysis.

Structural Dynamics Responsible for the UserResearch Corporation Interface and Virtual Terminal(SDRC) Interface Subsystems.

Other prime contractors under other projects who havecontributed to Test Bed Technology, their contributingactivities and responsible projects are as follows:

Contractors ICAN Project Contributing Activities

Boeing Military 1701, 2201. Enhancements for IBMAircraft Company 2202 node use. Technology(BMAC) Transfer to Integrated

Sheet Metal Center(ISMC).

v

Abe

PS 6201412591 November 1985

Contractors ICAN Project Contributing Activities

Control Data 1502, 1701 IISS enhancements toCorporation (CDC) Common Data ModelProcessor (CDNP).

D. Appleton Company 1502 IISS enhancements to( CON) Integration Methodology.General Electric 1502 Operation of the Test

Bed and communicationsequipment.

Hughes Aircraft 1701 Test Bed enhancements.Company (MAC)

Structural Dynamics 1502, 1701, IISS enhancements toResearch Corporation 1703 User Interface/Virtual(SDRC) Terminal Interface(UI/VTI).

Systran 1502 Test Bed enhancements.

Operation of Test Bed.

vi

PS 6201412591 November 1985

TABLE OF CONTENTS

SECTION 1.0 SCOPE ................................... 1-11.1 Identification ........................ 1-11.2 Functional Summary ................... 1-1

SECTION 2.0 DOCUMENTS ............................... 2-12.1 Reference Documents .................. 2-12.2 Terms and Abbreviations .............. 2-1

SECTION 3.0 REQUIREMENTS ............................ 3-13.1 Structural Description ............... 3-13.2 Functional Flow ...................... 3-13.3 Interfaces ............................ 3-13.3.1 Inputs/Outputs ..................... 3-23.4 Program Interrupts ................... 3-23.5 Timing and Sequencing Description .... 3-23.6 Special Control Features ............. 3-23.7 Storage Allocation ................... 3-23.7.1 Database Definition ................ 3-23.7.1.1 File Description ................. 3-23.7.1.2 Table Description ................ 3-33.7.1.3 Item Description ................. 3-33.8 Object Code Creation ................. 3-33.9 Adaptation Data ...................... 3-33.10 Detail Design Description ............ 3-33.10.1 Main Program List .................. 3-33.10.2 Module List ......................... 3-53.10.3 External Routines List ............. 3-73.10.4 Include File List .................. 3-93.10.5 Where Include File Used List ....... 3-113.10.6 Where External Routine Used List ... 3-133.10.7 Main Program Parts List ............ 3-163.10.8 Module Documentation ............... 3-183.10.9 Include File Description ........... 3-223.10.10 Hierarchy Chart .................... 3-233.11 Program Listings Comments ............ 3-27

SECTION 4.0 QUALITY ASSURANCE PROVISIONS ........... 4-14.1 Introduction and Definitions ......... 4-14.2 Computer Programming and Test

Evaluation ........................... 4-1

vii

PS 6201412591 November 1985

SECTION 1

SCOPE

1.1 Identification

This specification establishes the design of FunctionPREl,YBuild Source Code , one of the major functions of theConfiguration Item9-Precompiler"Pto be built and formallyaccepted by the ICAN Program Office. This CI constitutes one ofthe subsystems of the Common Data Model Processor (CDMP). \

1.2 Functional Summary

': 'The purpose of this Computer Program Configuration Item(CPCI) is to combine previously constructed parcels into amodified application process capable of servicing NDML requests.The following functions will be performed by this CPCI:

1. Write contents of parcel 2 onto the first parcel.

2. Write contents of parcel 3 onto the first parcel.

3. Write contents of parcel 4 onto the first parcel.

4. Delete parcels 1, 2 and 3.

A L

1-I

PS 620141259

1 November 1985

SECTION 2

DOCUMENTS

2.1 Reference Documents

1. ICAM Documentation Standards: IDS15012000A. 28 December1981.

2. D. Appleton Co., CDM Administrators Manual;UM620141000, March 1984.

3. D. Appleton Co., CDMI-IDEF, Model of the Common DataModel; CCS620141000, 15 May 1985.

4. D. Appleton Co., Computer Program DevelopmentSpecification (DS) for ICAM Integrated Support System(IISS) Configuration Item: NDML Precompiler;DS620141200, October 1984.

5. D. Appleton Co., Embedded NDML Programmer's ReferenceManual; PRM620141200, March 1985

6. Softech, Inc., NTM Programmer's Guide; UM620140001,July, 1984.

7. Control Data Corp., Computer Program DevelopmentSpecification (DS) for ICAM Integrated Support System(IISS) Configuration Item: NDDL Command Processor:DS620141100, June 1985.

2.2 Terms and Abbreviations

Attribute Use Class: (AUC)

Conceptual Schema: (CS)

Common Data Model Processor: (CDMP)

Common Data Model: (CDM) Describes common data applicationprocess formats, form definitions, etc, of the IISS and includesconceptual schema, external, internal schems, and schematransformation operators.

Data Field: (DF) An element of data in the externalschema. It is by this name that an NDML programmer references

2-1

PS 6201412591 November 1985

data.

Database Management System: (DBMS)

Distributed Request Supervisor: (DRS) This IISS CDMsubsystem configuration item controls the execution ofdistributed NDML queries and non distributed updates.

Domain: A logical definition of legal attribute classvalues.

Domain Constraint: Predicate that applies to a singledomain.

External Schema: (ES)

Forms: Structured views which may be imposed on windows orother forms. A form is composed of fields where each field is aform, item, or window.

Forms Processor: (FP) A set of callable execution timeroutines available to an application program for formprocessing.

Internal Schema: (IS)

Integrated Information Support System: (IISS) A testcomputing environment used to investigate, demonstrate and testthe concepts of information management and informationintegration in the context of Aerospace Manufacturing. The IISSaddresses the problems of integration of data resident onheterogeneous databases supported by heterogeneous computersinterconnected via a local Area Network.

Mappin: The correspondence of independent objects in twoschemas: ES to CS or CS to IS.

Network Transaction Manager: (NTM) Performs thecoordination, communication and housekeeping functions requiredto integrate the application processes and system servicesresident on the various hosts into a cohesive system.

Neutral Data Manipulation Language: (NDML) A languagedeveloped by the IISS project to provide uniform access tocommon data, regardless of database manager or distributioncriteria. It provides distributed retrieved and single nodeupdates.

2-2

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

PS 6201412591 November 1985

ORACLE: Relational DBMS based on the SQL (Structured QueryLanguage, a product of ORACLE Corp, Menlo Park, CA). The CDM isan ORACLE database.

Parcel: A sequential file containing section source codeof the input application program.

Request Processor: (RP) A COBOL program that will satisfya retrieval or update NDML subtransaction against a particularDatabase Management System.

User Interface: (UI) Controls the user's terminal andinterfaces with the rest of the system.

Virtual Terminal Interface: (VTI) Performs the interfacingbetween different terminals and the UI. This is done bydefining a specific set of terminal features and protocols whichmust be supported by UI software which constitutes the VirtualTerminal Definition. Specific terminals are then mapped againstthe Virtual Terminal software by specific software moduleswritten for each type of real terminal supported.

2-3

Abe

PS 6201412591 November 1985

SECTION 3

REQUIREMENTS

3.1 Structural Description

A graphic portrayal of this CPCI is included in Section3.10. This chart shows the hierarchical relationship of eachmodule making up this CPCI. As can be seen, the lower levelroutines Open, Read and Close the appropriate files. The Deletefile interface is used to remove the parcels that were copiedinto the first parcel.

3.2 Functional Flow

This CPCI implements the logic defined in the DevelopmentSpecification for this CPCI. Details of inputs/outputs andrelationships between modules are to be found in Section 3.10.

This CPCI has been designated to operate in a batch orinteractive mode. It must operate in the system environmentestablished for IISS; that is, use of the Network TransactionManager. It must use the ORACLE Database Management Systeminstalled on a DEC VAX computer.

3.3 Interfaces

The following diagram depicts interface of PREll with otherCPCI's in the system.

----------- +I CDPRE II PS41210 i

I

I PREI !lI I

+-----------

3-1

PS 6201412591 November 1985

3.3.1 Inputs/Ouputs

The following table depicts the inputs and outputs of thisCPCI. A detail description for each item can be found in the DSfor this CPCI.

Function: PREIl

INPUT OUTPUT

Parcel 1 File Name Module StatusParcel 2 File NameParcel 3 File NameParcel 4 File NameSource LanguageCurrent Host

3.4 Program Interrupts

Not applicable to this CPCI.

3.5 Timing and Sequencing Description

This module is called under the control of CDPRE, theprecompiler control module. PREII is called once per successfulprecompilation of a single user module.

3.6 Special Control Features

Not applicable to this CPCI.

3.7 Storage Allocation

3.7.1 Database Definition

The database used by this CPCI is the Common Data Model(CDN) database. This model is defined by the CDKl, the IDEF-lmodel of the CDR. Reference Document Number 3.

3.7.1.1 File Description

No permanent files have been defined for this CPCI. It may

3-2

Aa!

PS 6201412591 November 1985

/

use temporary scratch files for such things as generated programsource code or temporary query results.

3.7.1.2 Table Description

All tables used by this CPCI have been defined by theDevelopment Specification for this CPCI.

ilk 3.8 Object Code Creation

The object code for this CPCI will be created by the systemintegration test team by using defined IISS SoftwareConfiguration Management Procedures. This CPCI will use the "C"language compilers.

3.9 Adaptation Data

This CPCI has been coded using ANSI COBOL, FORTRAN and a"standard" subset of the "C" language. The intent was toprovide a transportable system. Any system environmentsupporting this language, a virtual memory management scheme,the COMM and NTM subsystems of IISS and the ORACLE DatabaseManagement System should be able to support this CPCI. Everypossible attempt has been made to localize and identify anymachine or environment dependent modules through the originaldesign of the IISS and application of Configuration ManagementProcedures.

3.10 Detail Design Description

The following sections have been computer generated forthis CPCI.

3.10.1 Main Program List

The following is a list of all "Main Programs" which

are modules that are not called by any other module beingdocumented here. These modules are either program entry pointsor, if they are hooked into another set of programs viasubroutine calls, they are the points the ekternal programs cancall and therefore enter through. To differentiate between thetwo types of entry points, look at the individual ModuleDocumentation (section 3.10.8) and look at Module Type for eachof the Main Program modules listed. Note whether the routineis a Program, Subroutine, or Function. If it is a Program. itis truly a main program entry point. If not, then it is merelycalled by other programs not being documented here.

3-3

PS 6201412591 November 1985

BUILD SOURCE CODE Main Program List

Module Name Purpose

CDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THEPARCL1

3-4

!I

PS 6201412591 November 1985

3.10.2 Nodule List

The following is a list of all the modules beingdocumented here along with their purpose. Each module has aunique name, no matter what language it was written in.

I

3-5 f

A.

A

PS 6201412591 November 1985

BUILD SOURCE CODE Module List

Module Name Purpose

CDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THEPARCLI

3-6

I\

PS 6201412591 November 1985

3.10.3 External Routines List

The following is a list of all routines or functions notdocumented here that are called by modules that are documentedhere. The first caller, in alphabetical order, is listed aswell. The specification in which any module is documented maybe found in the Module Documentation Index (Document NumberCM 620100001). See section 3.10.6 for a list of the modulesthat call each of these external routines.

3-7

Abe

PS 6201412591 November 1985

BUILD SOURCE CODE External Routines List

Nodule Name First User

CLSFILE CDP12DELFIL CDP12ERRPRO CDP 12FOPEN CDP 12REDLINE CDP 12SPRINTF CDP12STRCPY CDP 12STRNCNP CDP12WRTLINE CDP12

3-8

PS 6201412591 November 1985

3.10.4 Include File List

The following is a list of all include files called inby modules being documented here. Each include file has aunique name regardless of the language being used. The purposeof each include file is listed as well. A more completedescription of each include file is given in section 3.10.9.The purpose listed is the one that is in the source code of theinclude file.

A purpose of "**** PURPOSE NOT FOUND BY STRIPPER "indicates that a purpose statement was not written into theinclude file itself. The most common reason for this is thatthe include file comes from system libraries that were notdeveloped by the project, such as 'C' libraries that areprovided with the 'C' compiler.

See section 3.10.6 for a set of lists which show allthe modules which call in each of these include files.

3 -9

L.?

PS 6201412591 November 1985

BUILD SOURCE CODE Include File List

File Name Purpose

STDIO * PURPOSE NOT FOUND BY STRIPPER ***

3-10

U

PS 6201412591 November 1985

3.10.5 Where Include File Used List

The following lists each include file from 3.10.4 andall the modules documented in this specification which includethem. The purpose of each module is listed as well.

3-1

Akt

PS 620141259

1 November 1985

BUILD SOURCE CODE Where-include-file-used List

Include Module ModuleFile Name Purpose

STDIOCDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCLI

3-12

II

PS 620141259

1 November 1985

3.10.6 Where External Routine Used List

The following lists each external function or routinelisted in 3.10.3 and all the documented modules which call it.The purpose of each module is listed as well.

3-13

PS 6201412591 November 1985

BUILD SOURCE CODE Where-external-routine-used List

System Module ModuleModule Name Purpose

CLSFILECDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL1

DELFILCDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL1

ERRPROCDP12 CDPl2 APPENDS PARCL2. PARCL3,PARCL4 TO THE

PARCLI

FOPENCDP12 CDPl2 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL1

REDLINECDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL1

SPRINTFCDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL1

STRCPYCDP12 CDPI2 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCLI

3-14

IF

PS 6201412591 November 1985

BUILD SOURCE CODE Where-external-routine-used List

System Module ModuleModule Name Purpose

STRNCNPCDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL 1

WRTLINECDP12 CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCL 1

3-15

PS 6201412591 November 1985

3.10.7 Main Program Parts List

The following lists each Main Program listed in 3.10.1and all the modules which are called either by that moduleitself or by any of the documented modules which it calls. Itis possible for a non-main module to be listed more that onceif it is called by multiple modules. The called modules, inthis case known as program parts. are marked as to whetherthey are documented here. If so, the phrase "well-definedmodule" appears by the module name, if not it is an "external"routine". The Purpose of the Main Program module is listedas well.

3-16f

S\

PS 6201412591 November 1985

BUILD SOURCE CODE Main Program Parts List

Main Pgm Module ModuleName Name Type

CDP12 Purpose--,CDP12 APPENDS PARCL2,PARCL3,PARCL4 TO THE PARCLI

CLSFILE External routineDELFIL External routineERRPRO External routineFOPEN External routineREDLINE External routineSPRINTF External routineSTRCPY External routineSTRNCMP External routineVRTLINE External routine

3-17

\4

PS 620141259

1 November 1985

3.10.8 Nodule Documentation

The following documentation describes informationwhich Is specific to each individual module being documentedin this specification as listed in section 3.10.2. Itprovides a compact way of getting information that would beotherwise buried within each module's source code.

The specific items in this module documentation have the

following meanings:

NAME: Name of program Module.

PURPOSE: Purpose of Nodule as detailed in thesource code.

LANGUAGE: Programming language source code iswritten in.The choices are:

VAX-11 FORTRAN

C (I/S-1 Workbench 'C')VAX-11 COBOL

MODULE TYPE: Whether a Program, Subroutine, orFunction.

SOURCE FILE: Name of Source File from file

specification.

SOURCE FILE TYPE: Source File Extension from filespecification.

HOST: Whether this is a host-dependentroutine (VAX or IBM) or blank ifhost-independent.

SUBSYSTEM: IISS sub-system thia file resides in.

SUBDIRECTORY: Sub-directory of that subsystem inwhich this file resides.

DOCUMENTATION GROUP: Name of documentation group of whichthis source file is a member.

DESCRIPTION: A description of the module as otained

3-18

' Ja

PS 6201412591 November 1985

from the source code.

ARGUMENTS: The arguments with which this routineis called if it is a Subroutine or aFunction.

INCLUDE FILES: A list of all the files that areincluded into this module as well astheir purposes.

ROUTINES CALLED: Subroutines or Functions, eitherdocumented or external, called bythis module, if any.

CALLED DIRECTLY BY: The documented routines which callthis module, if any.

USED IN MAIN PROGRAM(S): The documented Main Programs whichcontain this module in their partslist according to the list in section3.10.7.

The Module Documentation is arranged alphabetically accordingto Module Name.

3-19

I

PS 6201412591 November 1985

BUILD SOURCE CODE Module Documentation

NAME: CDP12PURPOSE: CDP12 APPENDS PARCL2, PARCL3, PARCL4 TO

THE PARCLILANGUAGE: CMODULE TYPE: FUNCTIONFUNCTION TYPE: INT ()SOURCE FILE: CDP12SOURCE FILE TYPE: CHOST:SUBSYSTEM: CDMSUBDIRECTORY:DOCUMENTATION GROUP: PS41259

DESCRIPTION:

SYNOPSISC --

CDP12(PARCL1 ,PARCL2,PARCL3,PARCL4,LANGUAGE,FILEHOST,

RET-STATUS)COBOL -- CALL *CDP12" USING

PARCL1,PARCL2,PARCL3.PARCL4,

LANGUAGE,

FILE-HOST,

RET-STATUS.

FORTRAN -- CALLCDP12(PARCLI, PARCL2, PARCL3, PARCL4, LANGUAGE.

FILEHOST ,RET-STATUS)

INPUT:CHAR *PARCLI

3-20

PS 6201412591 November 1985

CHAR *PARCL2 ;CHAR *PARCL3 ;CHAR *PARCL4 ;CHAR *LANGUAGE ;CHAR *FILEHOST

OUTPUT:CHAR *RET-STATUS

DESCRIPTIONCDP12 -- CDP12 APPENDS PARCL2, PARCL3,PARCL4 TO THE

PARCLISO THE PARCLI WILL BE A COMPLETE PROGRAM.

ARGUMENTS:PARCL1 - CHAR *PARCL2 - CHAR *PARCL3 - CHAR *PARCL4 - CHAR *

LANGUAGE - CHAR *FILE HOST - CHAR *

STATUS - CHAR *

INCLUDE FILES:

STDIO - **** PURPOSE NOT FOUND BY STRIPPER *

ROUTINES CALLED:

STRCPYFOPENSPRINTFERRPROREDLIKEWRTLINECLSFILEDELFILSTRNCMP

3-21

|t

PS 6201412591 November 1985

3.10.9 Include File Descriptions

The following list contains a purpose and description ofeach include file listed in 3.10.4 as specified in the sourcecode. The language it is written in is also given.

3-22

PS 6201412591 November 1985

3.10.10 Hierarchy Chart

The following hierarchy charts show the relationshipsbetween all of the modules mentioned in the above documentation.A module may call a subroutine several times within its code,but the call will only be shown once as a single relationship onthis hierarchy chart. All modules shown at the top of the firstpage are considered Main Programs as described in section 3.10.1above.

There is an internal paging scheme as marked by the numbersin the upper right corner of each page. An index after the lastpage of the chart shows where a routine and its calls are firstdefined. If a routine has no page reference, it either makes nocalls or is an external routine. A continuation box on the endof a tree limb shows where that the tree continues on the pagenumbered mentioned. A number in a box with a routine namepoints to the page where the routine is further defined withinthe hierarchy tree. If there is no number in a box, the routineeither makes no calls or is an external routine.

3-23

PS 6201412591 November 1985

- .. . +-

ICDPI21

---- --- +----- --- ---- ------- - -I I I I I I------- + ----- + --------- -------- -------- ------ +ISTRCPYI IFOPENI ISPRINTFI IERRPROI IREDLINEI I(CONT)I

---- + +----+ --- - --- ----- +--- 2+

3-24

A"i

PS 620141259

1 November 1985

2

I CDP121

--------- +----------+-- --- ------ +

I I I I I

+--+-----+ ---- +---- -------- +------- ------- +

I(CONT)I IWRTLINEI ICLSFILEI IDELFILI ISTRNCMPI+----- +--------- +--------- +-------- +---------

3-25

PS 6201412591 November 1985

CDP12 ...... 1CLSFILEDELFILERRPROFOPENREDLINESPRINTFSTRCPYSTRNCMPWRTLINE

14

3-26

I'

PS 6201412591 November 1985

3.11 Program Listings Comments

This information is contained in the Module Descriptions insection 3.10.

3-27

A6-

PS 6201412591 November 1985

SECTION 4

QUALITY ASSURANCE PROVISIONS

4.1 Introduction and Definitions

"Testing" is a systematic process that may be preplannedand explicitly stated. Test techniques and procedures may bedefined in advance, and a sequence of test steps may bespecified. "Debugging" is the process of isolation andcorrection of the cause of an error.

"Antlbugging" is defined as the philosophy of writingprograms in such a way as to make bugs less likely to occur andwhen they do occur, to make them more noticeable to theprogrammer and the user. In other words, as much error checkingas is practical and possible in each routine should beperformed.

4.2 Computer Programming Test and Evaluation

The quality assurance provisions for test consists of thenormal testing techniques that are accomplished during theconstruction process. They consist of design and codewalk-throughs, unit testing, and integration testing. Thesetests are performed by the design team. Structured design,design walk-through and the incorporation of "antibugging"facilitate this testing by exposing and addressing problem areasbefore they become coded "bugs."

4-111111,,v., - t Ile intInql(| I LCt 10A1 /4 R w,1 6bi(,4

DATE

ILMED