39
WRDC-TR-90-8007 Volume III Part 16 AD-A250 120 INTEGRATED INFORMATION SUPPORT SYSTEM (IISS) Volume III - Configuration Management A Part 16 - Software Availability Bulletin M. Apicella, C. Hedge Control Data Corporation Integration Technology Services O TIC 2970 Presidential Drive " IEC r Fairborn, OH 45324-6209 September 1990 Final Report for Period 1 April 1987 - 31 December 1990 Approved for Public Release; Distribution is Unlimited MANUFACTURING TECHNOLOGY DIRECTORATE WRIGHT RESEARCH AND DEVELOPMENT CENTER AIR FORCE SYSTEMS COMMAND WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-6533 92-12417 92 5 08 008

AD-A250 120

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: AD-A250 120

WRDC-TR-90-8007Volume IIIPart 16

AD-A250 120

INTEGRATED INFORMATION SUPPORT SYSTEM (IISS)Volume III - Configuration Management

A Part 16 - Software Availability Bulletin

M. Apicella, C. Hedge

Control Data CorporationIntegration Technology Services O TIC2970 Presidential Drive " IEC rFairborn, OH 45324-6209

September 1990

Final Report for Period 1 April 1987 - 31 December 1990

Approved for Public Release; Distribution is Unlimited

MANUFACTURING TECHNOLOGY DIRECTORATEWRIGHT RESEARCH AND DEVELOPMENT CENTERAIR FORCE SYSTEMS COMMANDWRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-6533

92-12417

92 5 08 008

Page 2: AD-A250 120

NOTICE

When Government drawings, specifications, or other data are used for any purpose otherthan in connection with a definitely related Government procurement operation, the UnitedStates Government thereby incurs no responsibility nor any obligation whatsoever, regardlesswhether or not the government may have formulated, furnished, or in any way supplied thesaid drawings, specifications, or other data. It should not, therefore, be construed or impliedby any person, persons, or organization that the Government is licensing or conveying anyrights or permission to manufacture, use, or market any patented invention that may in any waybe related thereto.

This technical report has been reviewed and is approved for publication.This report is releasable to the National TechnicalInformation service (NTIS). At NTIS, it gill be

available to the general public, including foreign nations

4_ IDA L. R ect Manager DATE

Wrik -Pa t rs AFB, OH 45433-6533

FOR THE COMMANDER:

SRUCE A. RASMUSEN, Chief DATEWRDC/IlWright-Patterson AFB, OH 45433-6533

If your address has changed, if you wish to be removed form our mailing list, or if theaddressee is no longer employed by your organization please notify WRDC/MTI, Wright-Patterson Air Force Base, OH 45433-6533 to help us maintain a current mailing list.

Copies of this report should not be returned unless return is required by securityconsiderations, contractual obligations, or notice on a specific document.

Page 3: AD-A250 120

REPORT DOCUMENTATION PAGEIa. REPORT SECURITY CLASSIFICATION 1b. RESTRICTIVE MARKINGS

UnclassifiedI

2a. SECURITY CLASSIFICATION AUTHORITY 3. DISTRIBUTION/AVAILABILITY OF REPORT

_________________________________ Approved for Public Release;

2b. DECLASSIFICATION/DOWNGRADING SCHEDULE Distribuion Is Unlimited.

4. PERFORMING ORGANIZATION REPORT NUMBER(S) 5. MONITORING ORGANIZATION REPORT NUMBER(S)SAB620326000 WRDC-TR- 9048007 Vol. 111, Part 16

6a. NAME OF PERFORMING ORGANIZATION .OFFICE SYMBOL 7a. NAME OF MONITORING ORGANIZATIONControl Data Corporation; (d01*ale) WRDC/MTIIntegration Technology Services6c. ADDRESS (C*tyState, and ZIP Coda) 7b. ADDRESS (City State, and ZIP Code)

2970 Presidential DriveFairborn, OH 45324-620 WPAFB, OH 45433-6533

8a. AMEOF UNDIG/SON NG b. OFFICE SYMBOL 9. PROCUREMENT INSTRUMENT IDENTIFICATION NUM.ORGANIZATION (ff applcabie) F30-7C0

Wrhight Research and Development Center, F30-7C06Air Force Systems Command, USAF WRDC/MTI

_______________________10. SOURCE OF FUNDING NOS.8c. ADDRESS (C* State, and ZIP Code)

Wright-Patterson AFB, Ofio 45433-6533 PRGA PROJECT TASK I WORK UNIT11 TTE Wld Scriy ~ssflaio)EL ENT NO. NO. NO. NO.

See TILE Ick 1e~9y lsiiain 78011 F 595600 F95600 20950607

12. PERSONAL AUTHOR(S)Control Data Corporation: Apicella, M., Hedge, C.

13a. TYPE OF REPORT I3b. TIME COVERED 1o 4. DATE OF REPORT (Vr.,Mo.,Day) 15. PAGE COUNTFinal Report 4/l/87-12/31/9 1990OSeptember 30 39

16. SUPPLEMENTARY NOTATION

WRDC/MTI Project Priority 6203

17. COSATI CODES 18. SUBJECT TERMS (C&Oxm7L on reverse It necessary and idenity block no.)

FIELD GROUP SUB GR.

19. ABSTRACT (Continue on reverse if necessary and identify block number)

This bulletin reports the new features and enhancements to IISS and lists all IISS publications.

Block 11 -INTEGRATED INFORMATION SUPPORT SYSTEM (IISS)Vol III -Configuration ManagementPart 16 -Software Availability Bulletin

20. DISTRIBUTION/AVAILABILITY OF ABSTRACT 1. ABSTRACT SECURITY CLASSIFICATION

UNCLASSIFIED/UNLIMITED x SAME AS RPT. DTIC USERS Unclassified

22a. NAME OF RESPONSIBLE INDIVIDUAL k~.TELEPHONE NO. ~ 2c. OFFICE SYMBOLI(Indude Area Code)

David L Judison (513) 255-7371 WRDC/MTI

EDITION OF 1 JAN 73 IS OBSOLETEDD FORM 1473,83 APR Unclassified

SECURITY CLASSIFICATION OF THIS PAGE

Page 4: AD-A250 120

SAB62032600030 September 1990

FOREWORD

This technical report covers work performed under Air ForceContract F33600-87-C-0464, DAPro Project. This contract issponsored by the Manufacturing Technology Directorate, Air ForceSystems Command, Wright-Patterson Air Force Base, Ohio. It wasadministered under the technical direction of Mr. Bruce A.Rasmussen, Branch Chief, Integration Technology Division, throughMr. David L. Judson, Project Manager. The Prime Contractor wasIntegration Technology Services, Software Programs Division,of the Control Data Corporation, Dayton, Ohio, under thedirection of Mr. W. A. Osborne. The DAPro Project Manager forControl Data Corporation was Mr. J. P. Maxwell.

The DAPro project was created to continue the development, test,and demonstration of the Integrated Information Support. System(IISS). The IISS technology work comprises enhancements to IISSsoftware and the establishment and operation of IISS test bedhardware and communications for developers and users.

The following list names the Control Data Corporation

subcontractors and their contributing activities:

SUBCONTRACTOR ROLE

Control Data Corporation Responsible for the overallCommon Data Model designdevelopment and implementation,IISS integration and test, andtechnology transfer of IISS.

D. Appleton Company Responsible for providingsoftware information services forthe Common Data Model and IDEFlXintegration methodology.

ONTEK Responsible for defining andtesting a representativeintegrated system base. inArtificial Intellig ncetechniques to estal~i~hitnessfor use.

Simpact Corporation Responsible for Communicatio-development. .

Structural Dynamics Responsible for User Interfaces,Research Corporation Virtual Terminal Interface, an~

Network Transaction Managerdesign, development.,implementation, and support.

Arizona State University Responsible for test bedoperations and support.

iii

Page 5: AD-A250 120

SAB62032600030 September 1990

Table of Contents

Page

SECTION 1. INTEGRATED INFORMATION SUPPORTSYSTEM RELEASE 3.0 ................. 1-1

1.1 An IISS Overview . 1-11.2 New Features and Enhancements'...... 1-11.3 Important Release Information ...... 1-21.4 Product Delivery Media ............... 1-2

SECTION 2. DESCRIPTION OF RELEASE UPDATES ....... 2-12.1 Common Data Model .................. 2-12.2 User Interface ..................... 2-22.3 Network Transaction Manager ........ 2-72.4 Communications ..................... 2-7

SECTION 3. PUBLICATIONS ......................... 3-13.1 IISS Release 3.0 Publications ....... 3-13.2 Special Purpose Release

Publications ..................... 3-13.3 User Release Publications ............ 3-13.4 IISS Release 3.0 Project

Publications ....................... 3-3

SECTION 4. CONFIGURATION MANAGEMENT ............... 4-1

SECTION 5. SUPPORT INFORMATION .................... 5-1

APPENDIX A. PUBLICATION DESCRIPTIONS ............. A-1

4->

.

iv

Page 6: AD-A250 120

SAB62032600030 September 1990

SECTION 1

INTEGRATED INFORMATION SUPPORT SYSTEM

RELEASE 3.0

The Integrated Information Support System (IISS) has beenupdated to Release 3.0. This IISS release supports the VAXusing VMS and an IBM using MVS. It has been testedwith ORACLE and VAX-Il.

This bulletin reports on what new features and enhancementshave been added and are available, and lists and describes allof the available IISS publications.

1.1 An IISS Overview

IISS provides a single data base, single terminal, singlecomputer view of the corporate data resource. In achieving thisfunction, IISS has been developed as four subsystems havingthese basic responsibilities: common data modeling andprocessing, user interface, network transaction management, andcommunication. It is the role of the first subsystem, calledthe Common Data Model, or CDM, to provide the single data baseview. The User Interface, or UI, allows the applicationdevelopment environment to be managed with a consistent set oftools which provide an easy and controlled access to systems,give rapid assistance to the adding of new applications, andpresent meaningful output.

The UI also includes a virtual terminal interface whichprovides a neutral view of interactive devices.

The Network Transaction Manager, or NTM, provides processmessage management and connectionless communications for IISS ina distributed network operating environment.

The Communication subsystem, or COMM, is designed toprovide reliable point to point data communication betweencomputers. Together, the NTM and COMM subsystems provide for asingle, logical computer view.

This unifying concept of an organization's corporate dataresource, or enterprise, allows related or varied portions to begathered from its multiple - and possibly dissimilar - computersand databases and delivered as one report to the inquiringsource (i.e., application program or terminal operator) using asingle request and without awareness of the data location.

1.2 New Features and Enhancements

The following list presents the IISS products containingnew and enhanced features for this release.

1-1

Page 7: AD-A250 120

Common Data Model (CDM)

CDMRNDDL ProcessorNDML PrecompilerQuery Process GeneratorDistributed Request ProcessorCS/ES TransformerCDM Maintenance Utilities

User Interface (UI)

Rapid Application GeneratorText EditorReport WriterForm Definition Language CompilerForms Driven Form Editor-User Interface Services (UIS)Forms ProcessorVirtual Terminal InterfaceApplication Interface

Network Transaction Manager (NTM)

MonitorMessage Processing UnitNTM ServicesFile I/O Primitives

1.3 Important Release Information

Each of these additions and enhancements have been tested,and of the problems that were detected not all, unfortunately,have been corrected prior to the issuance of this release.These remaining problems are stated and explained in theSoftware Release Bulletin, Publication No. SRB620326000. If theavailability of a new feature or enhancement is delayed becauseof one or more of these problems, you are informed here in thisdocument as well as in the Software Release Bulletin. Problemsassociated with but not affecting the availability of a featureare announced only in the Software Release Bulletin.

1.4 Product Delivery Media

The IISS Release 3.0 software is available in both objectand source code and delivered on magnetic tape media. The tapesare 2400' reels and the IISS release code is inscribed at 1600bpi. Instructions for installing IISS from magnetic tape ontoeither a VAX VMS or IBM MVS system is contained in the VAX orIBM Installation Guides. Please refer to Publications, Section3, for the installation guide publication numbers.

1-2

Page 8: AD-A250 120

SAB62032600030 September 1990

SECTION 2

DESCRIPTION OF RELEASE UPDATES

These descriptions are of all new additions andenhancements to the IISS product for this release. Thedescriptions are brief and in the form of what functions theyadd or enhance; for a complete description of theseimprovements, please refer to the appropriate manual or guidelisted under Publications, 3.3. These descriptions, for yourconvenience, are preceded by a list by subsystem of the new orenhanced features.

2.1 Common Data Model

o CDM Runtime (CDMR) Architectureo NDDL Processoro NDML Precompilero Query Process Generatoro Distributed Request Processoro Aggregatoro CS/ES Transformero CDM Maintenance Utilities

CDM REPORTS

Eight reports have been developed to report the contents ofthe CDM.

IMPACT ANALYSIS

o Complete support for IDEF1Xo Problem corrections

NDDL PROCESSOR

The following enhancements have been added to the NeutralData Definition Language (NDDL) processor feature:

o Complete support for IDEF1Xo DROP LOGICAL UNIT OF WORK (LUW) commando Problem corrections

NDML

The following new items or enhancements have been added tothe Neutral Data Manipulation Language (NDML):

o Complete support for IDEFIXo NDML embedded in C programso Request Processor programs in C and Fortranc Embedded SQL in Cobol, C, and Fortran programs

2-1

Page 9: AD-A250 120

30 Sep0 mer 1990

o Generated Domain Verification logic moved in lineinstead of seperate module

o Enhanced referential integrity error reportingo Problem corrections

2.2 User Interface

The following new items or enhancements have been added tothe User Interface (UI) subsystem:

o Rapid Application Generator and Report Writer- Empty Condition- Multiple ON conditions- Boolean logic conditions- Report Writer conditions- Parameter forms- Program calls

o Form Definition Language Compilero Forms Driven Form Editoro User Interface Serviceso Forms Processoro Virtual Terminal Interfaceo Application Interfaceo Layout Optimization Systemo Electronic Documentation Systemo Reverse VTI for IMS/DCo DB2 Interfaceo System Generation

RAPID APPLICATION GENERATOR

EMPTY Select Condition

An "empty" condition now occurs whenever a database selectaction did not return any rows. If a database select resultedin no data being retrieved, the application now can take aresponsive action. This enhancement also informs theapplication what integrity test failed, as well.

Multiple ON Conditions

Multiple ON conditions are allowed to execute whenever anassociated user-function key is activated. In effect, if aparent condition is true and any of its offspring, or nested,conditions are true, they are executed. Nested conditions areexecuted in the order listed in the source file. Top levelconditions continue to have one condition executed with eachuser-function key activation.

An additional Multiple ON conditions enhancement allows thenext or following action to be executed after its precedingaction is interrupted by a condition, such as, data reads

2-2

Page 10: AD-A250 120

SAB62032600030 September 1990

overflowing a form. The semantics of the use of the universalquantifications subscript (star) was extended to cover nestedconditions.

Boolean Expressions

Boolean logical expressions are allowed in an ON condition,as well as arithmetic and string operators and parentheticallogic. Also, special functions such as application startup andcursor position sensing were added.

Report Writer Conditions

Rapid Application Generator conditions have beenincorporated into the Report Writer. The applicationsprogrammer now has a degree of flow control based upon userinput on report parameter forms.

Parameterization of Reports

The Report Writer now prompts the application programmerfor parameter field entries at startup of the Report program.This allows information, such as Select criterion, to bedefinable at runtime. After the parameter form is presented andthe programmer enters the fields on the parameter form, theparameters are made available to the Report program for use asSelect criterion, etc. This enhancement voids the need to writea different program for each Select criterion.

Program Calls

The Rapid Application Generator now supports program callsto the NTM. This enhancement allows calls to the NTM to beembedded in generated applications which will provide theseprograms the ability to start up other application programs andcommunicate with them.

The program call action also allows routines written in anytraditional language to be executed within the ApplicationDefinition Language (ADL). This makes it possible to pullspecial routines, such as algorithms, etc., into the ADL.

Miscellaneous Rapid Application Generator Enhancements and Adds

Display, Redisplay, and "Noselect" options have been addedto the Present action. The Present action is used to displayand begin reading data from Select options. The Display optionallows forms stacking in a window. The Redisplay option is usedto replace stacked forms in a window. The "Nodisplay" option isused to suppress the reading of data from Select actions.

Embedded C code has been added as an action. Now C codecan be used as an action of a condition and also can be includedas global program definitions.

2-3

Page 11: AD-A250 120

~' SAB62032600030 September 1990

Global keypad definitions now are allowed. This newfeature can be used to define function keys such that they canbe used during an entire application's run. Previously,function keys were defined on forms only and were active onlywhile that form was displayed.

The Signal action now is enabled to use Boolean flags.This enhancement allows for the coordination of severalindependent events, such as, a multi-column report with severalSelects; in effect, its service is similar to that of a macrofacility.

Open-ended and fixed-size arrays now can be usedinterchangeably. Previously, open-ended arrays could be usedwith the Select action only; now, any action or condition canreference open-ended arrays.

Select statements now can be used to referencemulti-dimensional arrays as well as single-dimensional arrays.Select statements also may be nested to any depth rather thanjust a level of ten, and any action, including other Selects,may be nested under a Select statement. Also, multiple Selectsmay target the same item on a form; this allows forms to beraised by Selects which differ only in their Where clauses.

Expressions also can be included within the Set action.The Set action which is used to assign a value to an item hasbeen revised to include on its right-hand side an expression aswell as an integer or string constant.

Syntax error reports now include an error's line number,the token causing the error, and tokens that were expected to bescanned by the parser at the point of the error.

BUSINESS GRAPHICS

The UIS now has the capability to display graphics data in2-dimensional format as x-y plots, bar charts, or pie charts.The UIS uses the graphics field which contains a single graph ofpredefined type and structure; however, the associated graphicspicture is dynamic. In the case of x-y plots and bar charts,more than one dataset may be plotted in a single graphic toyield multiple curves or bars. An x-y plot or bar chart maycontain both additive and absolute dependent datasets for anygiven dependent dataset. Additive datasets are associated withthe specified dependent dataset whenever absolute and dependentdata are present.

Graphics picture size and location values are stated interms of the default terminal character sizes and positions.Scaling is not done automatically; the Business Graphics usermust ensure that graphic information is of the size proper tofit in the available space. Those parts of a picture that donot fit within the displayed space are clipped, not wrapped."he UIS will attempt to adjust pictures appropriately based onthe aspect ratio of the displaying terminal.

2-4

Page 12: AD-A250 120

SAB62032600030 September 1990

Optional graphics attributes have default values set toallow a graph to be included within a display with minimaleffort at time of specification. Attributes not supported by aterminal type, for example, color on a monochrome monitor, willdefault to appropriate values.

Line styles (solid, dashed, dotted, dashed-dotted) and linewidth (varying thicknesses) are now available ongraphics-supporting terminals. Line styles and thickness, aswell as choice of background colors, color for the cure and thearea under the curve are new capabilities available ongraphics-supporting, color terminals. Additional choicesavailable are text size and font styles in axis labels, tickmark labels, legend entries, lower and upper limits of an axis,the linear and logarithmic scales of each axis, grid or no grid,axis locations and lengths, shading patterns below a curve, andsymbols to appear at data points. Another option is availablefor graphs having multiple curves, the choice of displayingdependent data as measured on the axis as additive or absolute.

Graphs are output display only, but data points can bepicked. The picture then can be altered to retain only thepicked area.

Data defined as an input field can be altered so that therelated graph will reflect the new value when it is redisplayed.In moving toward an object-oriented technology, a data source,because of its being separate from the graphics displaymechanism, can have its data displayed as a tabular form, or aline graph, or bar chart, or pie chart without changing theapplication program. Only the form definitions need to bechanged.

LAYOUT OPTIMIZATION SYSTEM

The Layout Optimization System is a new support tool forthe application programmer to use during the modeling stage ofapplication development: it is a tool for creating diagrams. Itis an application callable system that uses features of the UISto enable a developer to quickly define, create and cwtainhardcopy output of various types of diagrams, such as IDEF,network, and hierarchy diagrams.

ELECTRONIC DOCUMENTATION SYSTEM

The Electronic Documentation System (EDS) is a new supporttool that enables the application developer to quickly createdocumentation for each application program under development.It is a document authoring system based on the descriptivemarkup approach which uses the Standard Generalized MarkupLanguage (SGML). SGML is the international standard specifiedby the CALS initiative to be used as the method for textdelivery. The use of EDS increases the productivity ofdevelopers because they no longer have to be concerned with

2-5

Page 13: AD-A250 120

SAB62032600030 September 1990

document formatting issues, but can concentrate on documentcontent. In effect, documentation standards of any type can bepreset without a developer's involvement. Another major featureof EDS is that graphics, tables, and figures can be mergedwithin the text without manually cutting and pasting.

The types of graphics EDS currently supports are UserInterface Screen Dumps, MacPaint files, SDRC I-DEAS picturefiles, and any file that is Postscript EPSF (encapsulatedpostscript files) format.

REVERSE VTI for IMS/DC

Note: The Reverse VTI will not be available for this release.

The Reverse Virtual Terminal Interface, or Reverse VTI,will be added to support the integration into IISS ofIMS/DC-based applications. The Reverse VTI captures the 3270terminal commands from IMS/DC and translates them into VirtualTerminal Commands. It then translates the terminal user'sresponses from Virtual Terminal Commands into 3270 terminalcommands. This allows IMS/DC-based applications to be accessedfrom any IISS terminal.

DB2 INTERFACE

The DB2 Interface has been added to provide access betweenIISS CDM Request Processor routines and the IBM DB2 product.Its essential responsiblity is to establish the initialconnection between the IISS runtime environment and the DB2 DataManagement System. Once the connection is made, the DB2Interface monitors the status of the DB2 connection andmaintains MVS operator communication. The DB2 Interface alsoprovides the internal IISS facilities to open the database,issue SQL calls, and then close the database upon request from aCMD Request Processor or other DB2 applications.

FILE I/O PRIMITIVES

The File I/O Primitives (FIOP) were added to allow theCommon Data Model Runtime (CDMR) and other IISS programs ageneric transportable interface to access system specific files.Facilities are provided by the FIOP for Temporary File Name,Open files, Read records, Write records, Seek one record forwardor backward, Close file and Sort/Merge files. These functionsare available for sequential files of fixed-length records. TheFIOP has been designed for use within the IBM and DEC operatingenvironments and can be called by any IISS service needing toaccess user or system files and requiring portability betweenthe two operating environments.

2-6

Page 14: AD-A250 120

SAB62032600030 September 1990

DYNAMIC FIELDS

The Dynamic Fields capability has been added to allowchanging attributes of fields within forms and replacing formswith windows at runtime. Previously, this activity had to bedefined prior to runtime using the Forms Definition Language(FDL) and then the Forms Language Compiler for compiling thechange definitions. In effect, everything that could be doneusing the FDL now can be done at runtime using Dynamic Fields.Another benefit is the ability to add the "appears if" clause tothe FDL. This means that application programmers can definefields on forms that will appear under certain conditions onlyand detected at runtime; for example, a programmer could definea "total" field to appear only when the sum of a column offigures is greater than zero.

SYSTEM GENERATION

The System Generation service has been added to providefour applications: SYSGEN, allows creation and modification ofthe UI Database; UDBEXP, allows dumping and moving the UIDatabase from system to system within an ordinary sequentialfile; UDBIMP, recreates the UI Database from a dump file; andUDBCNV, which dumps an old-style, Oracle UI Database.

2.3 Network Transaction Manager

Grandchild Support

A new NTM service was added to allow it the capability totrack grandchild processes, that is, to have the last programinitiated within a chain of programs point to the chain'soriginating program. The UIS has been modified to use this newNTM service. The UIS now has the ability to start, for example,the Menu program which in turn starts an application program,and then have the application program, able now to identify theoriginating process, send its user screens directly to the UIS.

2.4 Communications

The Communications (COMM) subsystem did not requireupdating for this release.

2-7

Page 15: AD-A250 120

SAB620326000. 30 September 1990

SECTION 3

PUBLICATIONS

3.1 IISS Release 3.0 Publications

The publications listed in this section contain the latestuser information available at this release. Subsection 3.1lists the special release publications that describe the releasepackage and special release comments and instructions.Subsection 3.2 lists the end-user publications: operatormanuals, programmer reference manuals, user guides, etc. Pleaserefer to subsection 3.3 for a complete list of all IISS projectdocumentation. Each subsection also indicates all new documentsand documents that were rewritten or substantially updated forthis release.

Requests for these publications can be made to the U. S.Air Force, Materials Laboratory, Air Force Wright AeronauticalLaboratories, Air Force Systems Command, Wright-Patterson AirForce Base, Ohio 45433-6533. Please refer to Volume, PartNumber, and title when ordering.

3.2 Special Purpose Release Publications

Two new publications that have a special purpose for boththe IISS installer and its end-user have been added: theSoftware Availability Bulletin, or SAB, and the Software ReleaseBulletin, or SRB. The information contained in these documentsare specific to the current release. The SAB is used toannounce and describe new additions and enhancements, softwareand documentation availability and ordering information. TheSRB is used to announce late-breaking release information andprovide special installation requirements and instructions notcovered in the new release publications, and list significantproblems, notes and cautions.

Volume Part Publication No. Title

III 15 SRB620326000 Software Release BulletinIII 16 SAB620326000 Software Availability Bulletin

3.3 User Release Publications

The publications listed here are end-user documents. Thesetype documents provide guidance, operational, and referentialinformation for the system installer and manager, the systemoperator, and the application programmer.

3-1

Page 16: AD-A250 120

SAB62032600030 September 1990

Volume III IISS Configuration Management

Part Publication No. Title

1 QAP620320000 Quality Assurance Plan2 SUM620320000 System Administrator's Guide5 SUM620323000 System User Manual6 CMU620324000 System Configuration

Management User's Manual7 CMA620324000 System Configuration

Management Administrator'sManual

11 OM 620324001 VAX Installation Guide forExecutable Code

12 OM 620324002 IBM Installation Guide13 UM 620325000 DM User's Manual14 SUM620325000 FAD Administrator's Manual15 SRB620326000 Software Release Bulletin16 SAB620326000 Software Availability

Bulletin17 OM 620324003 VAX Installation Guide for

Source Code

Volume V Common Data Model Subsystem

Part Publication No. Title

1 UM 620341001 CDM Administrator's Manual4 UM 620341002 Information Modeling Manual -

IDEFIX7 UM 620341100 NDDL User's Guide8 PRM620341200 NDML Programmer's Reference

Manual32 UM 620341400 CDM Subsystem Database Build

Instructions User Manual33 UM 620341401 Define/Construct the NDDL

Definition for the CDMSubsystem User Manual

34 UM 620341403 CDM Reports and ApplicationUser's Guide

37 UM 620341410 DDL to NDDL Translator UserManual

38 UM 620341411 DDL to NDDL Translator BuildInstructions User Manual

41 UM 620341420 CDM Impact AnalysisUser Manual

42 UM 620341421 Impact Analysis BuildInstructions User Manual

45 UM 620341430 CDM Compare Utility User'sManual

46 UM 620341431 CDM Compare Utility BuildInstructions User's Manual

47 UM 620341440 SQL User's Manual48 PRM620341440 SQL Reference Manual

3-2

Page 17: AD-A250 120

SAB62032600030 September 1990

Volume VI Network Transaction Manager Subsystem

Part Publication No. Title

2 PRM620342000 NTM Programmer's Guide3 OM 620342000 NTM Operator's Manual4 SUM620342000 NTM System Programmer's

Manual

Volume VIII User Interface Subsystem

Part Publication No. Title

1 OM 620344000 Terminal Operator's Guide6 UM 620344200 Form Processor User's Manual13 UM 620344300 Virtual Terminal User'sManual15 UM 620344400 Forms Editor User Manual25 UM 620344501 Application Generator

User Manual31 UM 620344600 Text Editor User Manual39 UM 620344900 Electronic Documentation

System User Manual

3.4 IISS Release 3.0 Project Publications

These publications represent the entire development and all

release phases of ISS.

Volume I

Part Publication No. Title

1 FTR620300001 Project Overview: ExecutiveSummary

2 FTR620300002 Project Overview: TechnicalSummary

Volume III IISS Configuration Management

Part Publication No. Title

1 QAP620320000 Quality Assurance Plan2 SUM620320000 System Administrator's Guide3 TCD620321000 Technical Control Document4 SCD620322000 Schedule Control Document5 SUM620323000 System User Manual6 CMU620324000 SCM User's Manual7 CMA620324000 SCM Administrator's Manual8 DS 620324000 SCM Development Specification9 UM 620324000 Software Development

Guidelines

3-3

Page 18: AD-A250 120

SAB62032600030 September 1990

10 SUM620324000 System Software Document11 OM 620324001 VAX Installation Guide for

Executable Code12 OM 620324002 IBM Installation Guide13 UM 620325000 DM User's Manual14 SUM620325000 FAD Administrator's Manual15 SRB620326000 Software Release Bulletin16 SAB620326000 Software Availability

Bulletin17 OM 620324003 VAX Installation Guide for

Source Code

Volume IV IISS System

Part Publication No. Title

1 SRD620340000 System Requirements Document2 SDS620340000 System Design Specification3 STP620340000 System Test Plan4 STP620340001 System Integration Test5 STR620340000 System Test Report6 EIF620350001 EIF Technical Report7 EIF620350001 EIF Technical Report

Volume V Common Data Model Subsystem

Part Publication No. Title

1 UM 620341001 CDM Administrator's Manual2 UTP620341000 CDMP Test Case Report3 TBM620341000 CDMP: IDEFI Model of the CDM-

CDM Design Specification4 UM 620341002 Information Modeling Manual-

IDEFIX5 DS 620341100 NDDL Processor Development

Specification6 PS 620341100 NDDL Processor Product

Specification7 UM 620341100 NDDL User's Guide8 PRM620341200 NDML Programmer's Reference

Manual9 DS 620341200 NDML Precompiler Development

Specification-CDMP DesignSpecification

10 PS 620341200 NDML Precompiler Control ModuleProduct Specification

11 PS 620341211 NDML Precompiler ParseApplication Program

12 PS 620341212 NDML Precompiler Parse ProcessDivision ProductSpecification

13 PS 620341213 NDML Precompiler Parse NDMLProduct Specifications

14 PS 620341231 NDML Precompiler Transform NDML

3-4

Page 19: AD-A250 120

SAB62032600030 September 1990

15 PS 620341232 NDML Precompiler DecompositionConcept

16 PS 620341251 NDML Precompiler SelectInternal Schema

17 PS 620341252 NDML Precompiler TransformInternal Schema

18 PS 620341253 NDML Precompiler GenerateConceptual Schema

19 PS 620341254 NDML Precompiler GenerateOracle Request

20 PS 620341255 NDML Precompiler GenerateCODASYL

21 PS 620341256 NDML Precompiler GenerateTotal Request

22 PS 620341258 NDML Precompiler Build Calls/Messages

23 PS 620341259 NDML Precompiler Build SourceCode

24 PS 620341260 NDML Precompiler GenerateSupport

25 PS 620341261 NDML Precompiler GenerateRequest

26 DS 620341310 Distributed RequestSupervisor DevelopmentSpecification

27 PS 620341310 Distributed Request SupervisorProduct Specification

28 DS 620341320 Data Aggregators DevelopmentSpecification

29 PS 620341320 Data Aggregators ProductSpecification

30 DS 620341330 File Utilities DevelopmentSpecification

31 PS 620341330 File Utilities ProductSpecification

32 UM 620341400 CDM Subsystem Database BuildInstructions User Manual

33 UM 620341401 Define/Construct the NeutralData Definition for theCommon Data Model (CDM)Subsystem User Manual

34 UM 620341403 CDM Reports and ApplicationUser's Guide

35 DS 620341410 DDL to NDDL TranslatorDevelopment Specification

36 UTP620341410 DDL to NDDL Translator UnitTest Plan

37 UM 620341410 DDL to NDDL Translator UserManual

38 UM 620341411 DDL to NDDL Translator BuildInstructions User Manual

39 DS 620341420 CDM Impact AnalysisDevelopment Specification

40 UTP620341420 CDM Impact Analysis Unit TestPlan

3-5

Page 20: AD-A250 120

SAB62032600030 September 1990

41 UM 620341420 CDM Impact Analysis UserManual

42 UM 620341421 Impact Analysis BuildInstructions User Manual

43 DS 620341430 CDM Compare Utility DevelpmentSpecification

44 UTP620341430 CDM Compare Utility Unit TestPlan

45 UM 620341430 CDM Compare UtilityUser's Manual

46 UM 620341431 CDM Compare Utility BuildInstructions User's Manual

47 UM 620341440 SQL User's Manual48 PRM620341440 SQL Reference Manual49 IRD620341500 CDM IRDS Feature Evaluation

Report

Volume VI Network Transaction Manager Subsystem

Part Publication No. Title

1 DS 620342000 Network Transaction ManagerDevelopment Specification

2 PRM620342000 NTM Programmer's Guide3 OM 620342000 NTM Operator's Manual4 SUM620342000 NTM System Programmer's

Manual5 PS 620342100 NTM Monitor Product

Specification6 PS 620342200 NTM MPU Product Specification7 PS 620342300 NTM Services Product

Specification

Volume VII Communications Subsystem

Part Publication No. Title

1 DS 620343000 COMM DevelopmentSpecification

2 PS 620343100 Generic Comm Protocol ProductSpecification

3 PS 620343200 VAX IPC Product Specification4 DS 620343300 IBM IHC and IPC Development

Specification5 PS 620343400 File I/O Primitives Product

Specification6 UTP620343400 File I/O Primitives Unit Test

Plan

3-6

Page 21: AD-A250 120

SAB62032600030 September 1990

Volume VIII User Interface Subsystem

Part Publication No. Title

1 OM 620344000 Terminal Operator's Guide2 DS 620344100 User Interface Services

Development Specification-User Interface ManagementSystem DevelopmentSpecification

3 PS 620344100 User 'Interface ServicesProduct Specification

4 UTP620344100 User Interface Services UnitTest Plan

5 DS 620344200 Form Processor DevelopmentSpecification

6 UM 620344200 Form Processor User's Manual7 UTP620344200 Form Processor Unit Test

Plan8 PS 620344200 Form Processor Product

Specification9 UTP620344403 Graph Definition Language10 UTP620344220 Graph Support System11 DS 620344300 Virtual Terminal

Development Specification12 PS 620344300 Virtual Terminal Product

Specification13 UM 620344300 Virtual Terminal User's Manual14 UTP620344300 Virtual Terminal Unit Test

Plan15 UM 620344400 Forms Editor User's Manual16 DS 620344401 Forms Language Compiler

Development Specification17 PS 620344401 Forms Language Compiler

Product Specification18 UTP620344401 Forms Language Compiler Unit

Test Plan19 DS 620344402 Forms Driven Editor

Development Specification20 PS 620344402 Forms Driven Editor Product

Specification21 UTP620344402 Forms Driven Forms Editor Unit

Test Plan22 DS 620344403 Graph Language Development

Specification23 DS 620344501 Rapid Application Generator

and Report WriterDevelopment Specification

24 PS 620344501 Report Writer ProductSpecification

25 UM 620344501 Application Generator UserManual

26 UTP620344501 Report Writer Unit Test Plan27 PS 620344502 Rapid Application Generator

Product Specification

3-7

Page 22: AD-A250 120

SAB62032600030 September 1990

28 UTP620344502 Rapid Application GeneratorUnit Test Plan

29 DS 620344600 Text Editor DevelopmentSpecification

30 PS 620344600 Text Editor ProductSpecification31 UM 620344600 Text Editor User Manual32 UTP620344600 Text Editor Unit Test Plan33 DS 620344700 Application Interface

Development Specification34 PS 620344700 Application Interface Product

Specification35 UTP620344700 Application Interface Unit

Test Plan36 UTP620344800 Layout Optimization System

Unit Test Plan37 DS 620344800 Layout Optimization System

Design Specification38 DS 620344900 Electronic Documentation

Development Specification39 UM 620344900 Electronic Documentation

System User Manual40 UTP620344901 SGML Tagger Unit Test Plan41 UTP620344902 EDS Parser Unit Test Plan42 UTP620344903 EDS Document Type Definition

Unit Test Plan43 UTP620344904 EDS Layout Editor Unit Test

Plan44 UTP620344905 EDS Document Formatter Unit

Test Plan45 UTP620344906 EDS MacPaint to Postscript

Unit Test Plan

3-8

Page 23: AD-A250 120

F1. --7 I

sAm6zO32-0000'~4 ,.'~ -30 September 1990.

SECTION 4

CONFIGURATION MANAGEMENT

The computer systems listed in this section wereused to install and evaluate the IISS Release 3.0 softwaresystem.

Mainframe operatingSystem System

VAX 8600 VMS

4-1

Page 24: AD-A250 120

SAB62032600030 September 1990

SECTION 5

SUPPORT INFORMATION

All IISS Release 3.0 support information is availablethrough the Manufacturing Technology Directorate, Air ForceWright Research and Development Center, Air Force SystemsCommand, Wright-Patterson Air Force Base, Ohio 45433-6533.

5-

5-1

Page 25: AD-A250 120

. 4 --: -. 4,

SAB62032600030 September 1990

APPENDIX A

PUBLICATION DESCRIPTIONS

Volume I, Project Overview

Part 1, Executive SummaryThis document is a general summary of IISS and the Release 3.0enhancements. It is an easy-to-read guide intended for thereader whose organization is not familiar with IISS but has aninterest in integrating their information environment.

Part 2, Technical SummaryThis document is an in-depth summary of IISS and the Release 3.0enhancements. It is intended for the reader whose organizationis familiar with IISS and requires a detailed report of itscurrent status.

Volume III, IISS Configuration Management

Part 1, Quality Assurance PlanThis document discusses the major areas of quality assuranceplanning and provides guidelines for developing, testing andreleasing IISS.

Part 2, System Administrator's GuideThis guide explains the System Administrator's responsibilitiesfor maintaining IISS on the Test Bed. These responsibilitiesinclude adding new users, assigning privileges and quotas, andbackup procedures.

Part 3, Technical Control Docu.nentThis document contains descriptions of features, functions, andtasks involved in the development of the IISS Project. In somecases the features and functions specified relate torequirements or functionality of given subsystems andenhancements to the IISS; in other cases, the specific tasksneeded to carry out implementation are specified. This documenthas not been included in this release.

Part 4, Schedule Control DocumentThis document, is a working document that was developed early inthe IISS project to schedule the first enhancements to the IISSsystem. It also presents the final status of the first IISSrelease. This document has not been included in this release.

Part 5, System User ManualThis document lists the hardware which comprises the Test Bedcomputer system. This document has been deleted from thisrelease and its content function incorporated in theinstallation guides.

A-1

Page 26: AD-A250 120

SAB62032600030 September 1990

Part 6, System Configuration Management User ManualThis manual describes the Software Configuration Management(SCM) functions that are used by all developers of the IISS testbed software. The SCM functions control the maintenance storageof source code.

Part 7, System Configuration Management Administrator's ManualThis manual gives explicit instructions for creating VAX and IBMreleases. General information for administering SoftwareConfiguration Management also is provided.

Part 8, System Configuration Management DevelopmentSecificationThis document establishes the functional requirements of theIISS Software Configuration Management system which controls thestoring and changing of IISS source code and software releases.

Part 9, Software Development GuidelinesThis document identifies and explains guidelines and conventionsto be followed throughout the various phases of IISS Softwaredevelopment.

Part 10, System Software DocumentThis document lists the software maintained and used on the IISSTest Bed during the development, compilation, and testing ofthe IISS Release 3.0. This document has been deleted from thisrelease and its function has been incorporated in theinstallation guides.

Part 11, VAX Installation Guide for Executable CodeThis installation guide provides step-by-step instructions forinstalling IISS Release 3.0 object code onto any VAX computercontaining the prerequisite system hardware and software.

Part 12, IBM Installation GuideTh]is installation guide provides step-by-step instructions forinstalling IISS Release 3.0 object or source code from therelease tape onto any IBM computer containing the prerequisitesystem hardware and software.

Part 13, Document Management User's ManualThis manual describes the Document Management (DM) functionsthat control changes made to IISS documentation. The IISSdocuments are stored in a protected environment controlled bythe DM.

Part 14, FAD Administrator's ManualThis manual gives specific instructions for the use of the FullyAutomated Documentation (FAD) tool which is used in the creationof product specifications for program subsets of the IISSsubsystems.

A-2

Page 27: AD-A250 120

SAB62032600030 September 1990

Part 15, Software Release BulletinThis document provides information specific to the currentrelease. It is information that was not available at the timethe user manuals and installation guides were prepared forrelease. It reports significant problems and provides notes andcautions regarding the installation process and each productfeature as well as updates or changes to the user manuals andinstallation guides.

Part 16, Software Availability BulletinThis document provides a general description of the currentrelease, lists and describes the new features available, listsand describes the available IISS release publications, and liststhe computer systems used to install and evaluate the IISSRelease 3.0 software system. Its intended audience is thereader whose organization is considering integrating theirinformation environment.

Part 17, VAX Installation Guide for Source CodeThis installation guide provides step-by-step instructions forinstalling IISS Release 3.0 source code onto any VAx computercontaining the prerequisite system hardware and software.

Volume IV, IISS System

Part 1, Systems Requirements DocumentThis document presents the IISS philosophy and the software andhardware requirements necessary to develop IISS.

Part 2, System Design SpecificationTh-is technical report discusses the system design and functionalspecifications for IISS. It defines and allocates the IISSfunctionality to its four subsystems: the Network TransactionManager, Common Data Model, User Interface/Virtual TerminalInterface, and Communication.

Part 3, System Test PlanThis plan describes the quality assurance standards and criteriathat the software must meet for system integration and testing.It also presents the system testing methodology to be used, thecriteria for test completion and release, and provides theintegration, testing, and documentation starting and endingschedules.

Part 4, IISS System Integration TestThis document defines and provides the procedure used to testand demonstrate the IISS functionality. All subsystems areexercised and tested by this procedure.

Part 5, System Test ReportThe IISS Release 3.0 test results are summarized and reported inthis document.

A-3

Page 28: AD-A250 120

SAB62032600030 September 1990

Part 6, EIF Technical ReportThis document contains the final report from NorthropCorporation Aircraft Division of an enterprise integrationpreliminary strawman framework.

Part 7, EIF Technical ReportThis document contains the final report from IBM Corporation ofan enterprise integration preliminary strawman framework.

Volume V, Common Data Model Subsystem

Part 1, Common Data Model Administrator's ManualThis document discusses the Common Data Model (CDM) subsystemand the philosophy and practical objectives of the CDMAdministrator, including its design and its role in the IISSenvironment. This document also describes the steps necessaryfor entering and maintaining data in the CDM .

Part 2, Common Data Model Processor Test Case ReportThis document sunmarizes the results from the set of test casesused to test the Common Data Model subsystem.

Part 3, CDMP: IDEFI Model of the CDM - CDM Design SpecificationThis publication describes the Common Data Model Processor, amechanism by which application programs can retrieve and updatedata without knowing where or how the data are stored.

Part 4, Information Modeling Manual - IDEF1XThis document is a modeling guide and reference manual for anextended version of the ICAM definition language for informationmodeling, referred to as IDEFlX. It also describes the IDEFIXsyntax, procedure, and documentation requirements for developinga logical model of the semantic characteristics of data.

Part 5. NDDL Processor Development SpecificationThis document describes functional requirements of the IISSNeutral Data Definition Language which is the primary tool usedfor maintaining the Common Data Model.

Part 6, NDDL Processor Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe "Neutral Data Definition Language Processor" (NDDLProcessor).

Part 7, NDDL User's GuideThT document is a guide for using the Neutral Data DefinitionLanguage (NDDL). This manual also explains the syntax andsemantics of each NDDL command.

A-4

Page 29: AD-A250 120

SAB62032600030 September 1990

Part 8, NDML Programmer's Reference ManualThis document is an applications programmer reference to usingthe Neutral Data Manipulation Language (NDML). This manual alsoexplains the syntax and semantics of all required commands.

Part 9, NDML Precompiler Development SpecificationThis document describes the functions, performance, environment,interfaces, and design requirements of the NDML Precompiler.

Part 10, NDML Precompiler Control Module Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe NDML Precompiler.

Part 11, NDML Precompiler Parse Application Program ProductSpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Parse Application Program.

Part 12, NDML Precompiler Parse Process Division ProductSpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Parse Process Division.

Part 13, NDML Precompiler Parse NDML Product SpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Parse NDML.

Part 14, NDML Precompiler Transform NDML Product SpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Transform NDML.

Part 15, NDML Precompiler Decomposition Concept ProductSpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Decomposition Concept.

Part 16, NDML Precompiler Select Internal Schema ProductSpecificationTh i specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Select Internal Schema.

Part 17, NDML Precompiler Transform Internal Schema ProductSecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Transform Internal Schema.

A-5

Page 30: AD-A250 120

SAB62032600030 September 1990

Part 18, NDML Precompiler Generate Conceptual Schema ProductWei ficationThis specification establishes the development, test, andqualification requirements of the computer program identifiedas the NDML Precompiler Generate Conceputal Schema.

Part 19, NDML Precompiler Generate Oracle Request ProductSpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Generate Oracle Request.

Part 20, NDML Precompiler Generate CODASYL Product SpecificationTh-s specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Generate CODASYL.

Part 21, NDML Precompiler Generate Total Request ProductShecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Generate Total Request.

Part 22, NDML Precompiler Build Calls/ Messages ProductSpecifi cationThIs specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Build Calls/Messages.

Part 23, NDML Precompiler Build Source Code ProductSpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Build Source Code.

Part 24, NDML Precompiler Generate Support Product SpecificationThis specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Generate Support.

Part 25, NDML Precompiler Generate Request Product SpecificationThs specification establishes the development, test, andqualification requirements of the computer program identified asthe NDML Precompiler Generate Request.

Part 26, Distributed Request Supervisor DevelopmentSpecificationThis specification describes the performance, development, test,and qualification requirements of a collection of computerprograms that represent the distributed request supervisor.

Part 27, Distributed Request Supervisor Product SpecificationThis specification describes the development, test, andqualification requirements of a computer program identified asthe Distributed Request Supervisor.

A-6

Page 31: AD-A250 120

SAB62032600030 September 1990

Part 28, Data Aggregators Development SpecificationThis document describes the design implementation of the IISSdata aggregators which combine the various subresults ofdistributed data requests using the relation operators JOIN,UNION and DIFFERENCE.

Part 29, Data A~greqators Product SpecificationThis specification describes the development, test, andqualification requirements of a computer program identified asData Aggregators.

Part 30, File Utilities Development SpecificationThis document describes the design implementation of the IISSfile Utilities which provide file transfer, file delete, andunique file naming services to other IISS components.

Part 31, File Utilities Product SpecificationThis specification describes the development, test, andidalifcation requirements of a collection of computer programsdentified as File Ultilities.

Part 32, CDM Subsystem Database Build Instructions User ManualThis document describes the procedures to use to construct theCDM subsystem database.

Part 33, Define/Construct the Neutral Data Definition for theCommon Data Model (CDM) Subsystem User ManualThfis document describes the requirements for the construction ofthe NDDL. Also presented are lists of 25 groups and the NDMLroutine contained in each group with an example of how a groupis precompiled. Another example explores qenerating, compilingand insertion of a group into the object library of the NDDLRequest Processor main program.

Part 34, CDM Reports and Application User's GuideThe CDM Reports and Applications are utilities that are usefultowards examining the contents of the CDM. The utilities andthe NDDL "copy" commands provide a comprehensive picture of theCDM contents to the Common Data Model Administrator and to NDDLusers. This document is a guide for CDM Administrators andthose who are responsible for maintaining the CDM.

Part 35, DDL to NDDL Translator Development SpecificationThis specification establishes the performance, development,test and qualification requirements of the DDL to NDDLTranslator program.

Part 36, DDL to NDDL Translator Unit Test PlanThis plan establishes the methodology and procedures used toadequately test the capabilities of the DDL to NDDL Translator.

Part_37, DDL to NDDL Translator User ManualThus document is to be used by CDM Administrators who areresponsible for making changes to the CDM and ensuring that itremains in a consistently reliable state.

A-7

Page 32: AD-A250 120

SAB62032600030 September 1990

Part 38, DDL to NDDL Translator Build Instruction User's ManualThis document describes how to construct the DDL to NDDLTranslators. Also, listed are prerequisites of the DDL to NDDLTranslators. Also included are step-by-step instructions forbuilding the DB2 and Total Translators.

Part 39, CDM Impact Analysis Development SpecificationThis document establishes the performance, development, test,and qualification requirements of the CDM Impact Analysisprogram.

Part 40, CDM Impact Analysis Unit Test PlanThis plan establishes the methodology and procedures used toadequately test the capabilities of the CDM Impact Analysisprogram.

Part 41, CDM Impact Analysis User ManualThis document is to be used by CDM Administrators for makingchanges to the CDM and ensuring that it remains in aconsistently functional state. The CDM Impact Analysis Utilityidentifies and reports which software modules and externalschemas are affected by a change to the CDM.

Part 42, Impact Analysis Build Instruction User's ManualThis document describes the construction of the CDM Impact Toolwhich requires precompiling routines to find and report CDMimpacts. Also described are the prerequisite of the impactenvironment, lists of the groups to be precompiled, andstep-by-step instructions on building the CDM impact analysis.

Part 43, CDM Compare Utility Design SpecificationThis document describes the requirements for the performance,design, test, and qualification of the CDM Compare Utility.

Part 44, CDM Compare Utility Unit Test PlanThis document describes the methodology and procedure used totest the functionality of the CDM Compare Utility.

Part 45, CDM Compare User's ManualTHis document is used by CDM administrators for making changesto the CDM and insuring it remains in a consistently functionalstate.

Part 46, CDM Compare Utility Build Instructions User'sManualThis manual discusses the Utility Build prerequisite for the CDMcompare utility environment as well as providing step-by-stepinstructions for building the CDM compare utility executables.

Part 47, SQL User's ManualThis document is designed to help the application programmerwrite embedded SQL statements in host languages to access theheterogeneous distributed databases supported within the CommonData Model operating environment.

A-8

Page 33: AD-A250 120

0'. SAB62032600030 September 1990

Part 48, SQL Reference ManualThis document is an application programmer's reference guide forusinq SQL. This manual explains the syntax and semantics of allrequired commands.

Part 49, CDM IRDS Feature Evaluation ReportThis document provides a comparison between the Common DataModel (CDM) subsystem and the IRDS Standard, an ANSI and FIPSinformation resource standard.

Volume VI, Network Transaction Manager Subsystem

Part 1, Network Transaction Manager Development SpecificationThis document discusses philosophy, structure, and function ofthe Network Transaction Manager (NTM) subsystem. It alsoexplains the data structures associated with the major NTMcomponents along with a discussion of the NTM internal tablesand those aspects of the NTM code that are host systemdependent.

Part 2, NTM Programmer's GuideThis document describes services provided to IISS programmers bythe Network Transaction Manager (NTM). These services are usedby IISS application programs to send messages to and receivemessages from other programs in the IISS.

Part 3, NTM Operator's ManualThis technical manual provides detailed instructions foroperating and maintaining IISS. This includes instruction forbringing up and shutting down the NTM, a description of NTMerror codes, and instructions for maintaining NTM tables.

Part 4, NTM System Programmer's ManualTEis dcument provides an understanding of the internalstructure of the Network Transaction Manager (NTM). It alsoprovides an overview of the NTM architecture and the majorcomponents within that architecture along with a discussion ofthe NTM internal tables. Details of the modules within each ofthe major components and those aspects of the NTM code that arehost system dependent also are provided.

Part 5; NTM Monitor Product SpecificationTis--specification establishes the development, test, andqualification requirements of a computer program identified asthe NTM Monitor.

Part 6, NTM NPU Product SeecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe NTM MPU.

Part 7, NTM Services Product SpecificationThis specification establishes the development, test, andqualification requirements of a collection of computer programsidentified as NTM Services.

A-9

Page 34: AD-A250 120

SAB62032600030 September 1990

Volume VII, Communication Subsystem

Part 1, COMM Development SpecificationThis specification establishes the performance, development,test, and qualification requirements of the CommunicationsSubsystem (COMM).

Part 2, 93eneric COMM Protocol Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe Generic COMM Protocol.

Part 3,- VAX IPC Product SpecificationThis spc2ification establishes the development, test, andqualificatiQn requirements of a computer program identified asthe VAX TPC.

Part 4, IBM IHC and IPC Development SpecificationThis document explains the basic architecture, modules linked toCOMM, NTH, and APS, Inter-Process Primitives, Process ControlPrimitives, PRC Support Routines, Environment Control Modules,Inter-Host Primitives, Interface to CICS Application, and CICSInterface Primitives.

Part 5, File I/O Primitives Product SpecificationThis spec ification establishes the development, test, andqualification requirements of a computer program identified asFile I/C Primitives.

Part 6, File I/O Primitives Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the File I/OPrimitives (FIOPs) within the Communications subsystem.

Volume 'LII, User Interface Subsystem

Part 1, Terminal Operator's GuideThis guide describes how to operate a terminal during an IISSapplication session. This manual also describes the IISS enduser environment and those selective and predefined functionswhich comprise the User Interface Services (UIS).

Part 2, User Interface Services Development SpecificationThis spEcification provides the design of the form-basedapplications that represent the User Interface Services (UIS).The UIS is a collection of applications that use the FormProcessor.

Part 3, User Interface Services Product SpecificationThis specification establishes the development, test, and9ualification requirements of a collection of computer programsidentified as the User Interface Services.

A-10

Page 35: AD-A250 120

SAB62032600030 September 1990

Part 4, User Interface Services Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the User InterfaceServices (UIS).

Part 5, Form Processor Development SpecificationThis spec.1fication describes the development, test andqualification requirements of the Form Processor (FP). The FPis used to permit an application to send/receive data on theformatted screen without having the application program know allthe characteristics of the particular terminal being used. Itis used in conjunction with the Virtual Terminal.

Part 6, Form Processor User's ManualThis manual describes the set of callable execution timeroutines available to an application program for formprocessing. It is intended for application programmers usingthe IISS. Also discussed in this manual are the concepts ofdisplay list, windows, and qualified names which must beunderstood in order to use the Form Processor routines.

Part 7, Forms Processor Unit Test PlanThis specification describes the design of the Form Processor(FP). The FP is a set of callable execution routines availableto an application program for manipulating and displayingelectronic: forms. The FP routines allow programs and theirusers to communicate through predefined forms displayed on aterminal screen.

Part 8. Form Processor Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe Form Processor.

Part 9, Graph Definition Language Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the Graph DefinitionLanguage program.

Part 10_ Graph Support System Unit Test PlanThis unit test plan establishes the methodology and proceduresused to acdequately test the capabilities of the Graph SupportSystem.

Part 11, Virtual Terminal Development SpecificationThis specification describes the performance, development, testand qualification requirements of the Virtual Terminal (VT).rhe VT translates between VT commands and commands forother terminal types. Part of the VT handles sending andreceiving messages across the NTM. Another part interfaces withthe terminal specific device driver.

A-i1

Page 36: AD-A250 120

SAB62032600030 September 1990

Part 12, Virtual Terminal Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe Virtual Terminal.

Part 13, Virtual Terminal User's ManualThis manual describes the program callable interface to the IISSVirtual Terminal, the Virtual Terminal commands, and providesterminal implementation information for programmers who wish toadd new terminal types to the system.

Part 14, Virtual Terminal Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the Virtual Terminal(VT). This document includes tests for the VT callable routinesand the monitor which is the main controller of the VT.

Part 15, Forms Editor User's ManualThis manual explains how to define and maintain electronic formsusing the Form Definition Language and the Forms Driven FormEditor. General electronic form characteristics also aredescribed.

Part 16 Forms Language Compiler Development SpecificationThis documient describes the requirements for the compiler (FLAN)that tranxlates Form Definition Language source files intobinary form definition file format.

Part 17, Forms Language Compiler Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe Forms Language Compiler.

Part 184 forms Language Compiler Unit Test PlanThis unit test plan establishes the methodology and procedures.used to adequately test the capabilities of the Forms DefinitionLanguage Compiler (FLAN) and the Make Includes (MAKINC).

Part 19, Forms Driven Editor Development SpecificationThis specification establishes the design, development, test andqualification requirements of the Forms Driven Form Editor(FDFE). The FDFE is a software tool for creating andinitializing form definitions.

Part 20, Forms Driven Editor Product SpecificationThis specification establishes the developmet, test, andqualification requirements of a computer program identified asthe Forms Driven Forms Editor.

A-12

Page 37: AD-A250 120

SAB62032600030 September 1990

Part 21, Forms Driver Forms Editor Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the Forms DrivenForm Editor.

Part 22, Graph Definition Language Development SpecificationThis specification establishes the design, development, test,qualification, and performance requirements of the GraphDefinition Language (GDL) program, an extension of the FormDefinition Language (FDL) program.

Part 23, Rapid Application Generator and Report WriterDevelopment SpecificationThis document describes the design and development requirementsof the Report Writer program which translates report definitionsinto programs that access databases via the CDM.

Part 24, Report Writer Product SpecificationThis spec-fication establishes the development, test, andqualification reuquirements of a computer program identified asthe Report Writer.

Part 25, Application Generator User ManualThis manual explains the Application Generator and ReportDefinition Language programs and provides the process ofcreating a hard copy report of selected database informationresident in the Common Data Model. This information isaccessible through the IISS Neutral Data Manipulation Language.This manual also describes the Hierarchical Report Writer whichfunctions as a post processor to the initial report writer.

Part 26( Report Writer Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the Report Writerprogram.

Part 27, Rapid Application Generator Product SpecificationThis spec fication establishes the development, test, andqualificaLion requirements of a computer program identified asthe Rapid-Applicaction Generator.Part 28 Rapid Application Generator Unit Test Plan

ThTisuit-test plan establishes the methodology and proceduresused to adequately test the capabilities of the RapidApplication Generator program.

Part 29, Text Editor Development SpecificationThis specification establishes the performance, development,test and qualification requirements of the Text Editor (TE)program. The TE provides IISS users with file editingcapabilities and, in conjunction with the UI Form Processor,provides the ability to edit items displayed on a form.

A-13

Page 38: AD-A250 120

SAB62032600030 September 1990

Part 30, Text Editor Product SpecificationThis spe.ification establishes the development, test, andqualification requirements of the a computer program identifiedas the Text Editor.

Part 31, Text Editor User ManualThis document provides instructions in how to use the TextEditor's file editing capabilities. Editing functions includeinserting, deleting, moving, and replacing text.

Part 32, Text Editor Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the Form ProcessorText Editor (TE) program.

Part 33, Application Interface Development SpecificationThis specification establishes the design, development, test,and qualification requirements of the Application Interface (AI)program. The AI is used by application programs to create themessages which correspond to FP calls and are sent to the UserInterface Monitor (UIM) of the Form processor by way of theNetwork Transaction Manager.

Part 34, Application Interface Product SpecificationThis specification establishes the development, test, andqualification requirements of a computer program identified asthe Application Interface.

Part 35, Application Interface Unit Test PlanThis specification establishes the development, test andqualification requirements of the Application Interface (AI)program.

Part 36, Layout Optimization System Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the LayoutOptimization System program.

Part 37, Layout Optimization System Design SpecificationThis document describes the requirements for the performance,design, test, and qualification of the Layout OptimizationSystem.

Part 38, Electronic Documentation System DevelopmentSpecificationThis specification establishes the development, test, andperformance requirements of an integrated set of computerprograms collectively known as the Electronic DocumentationSystem (EDS). The EDS is intended to support the movement of adocument through the document life cycle.

A-14

Page 39: AD-A250 120

i / i ~~.. . . .. ...... . . . . . . . . . . . . . . . . . . .: ! i! • .

77FIRI - r 77-7." 7 -. 7"

SAB62032600030 September 1990

Part 39, Electronic Documentation System User ManualThe Electronic Documentation System User Manual discusses andexplains how to apply an integrated set of tools that enablesthe user to create, edit, revise, and generate documents with awell-defined logical structure and a well-defined layoutstructure.

Part 40, SGML Tagger Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the SGML Taggerprogram.

Part 41, EDS Parser Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the EDS SGML Taggerprogram.

Part 42c EDS Document Type Definition Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the EDS DocumentType Definition program.

Part 434 EDS Layout Editor Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the EDS Layout Editor program.

Part 44( EDS Document Formatter Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the DocumentFormatter program.

Part 45, EDS MacPaint to Postscript Unit Test PlanThis unit test plan establishes the methodology and proceduresused to adequately test the capabilities of the EDS MacPaint toPostscript program.

A-15 * U.S. GOVERWENT PRINTI1G OFFIC': 1992 - 648-127/62288