DEVELOPMENT OF INTEGRATED PROGRAMS

FOR A_ROSPACE-VEHIC!_.E n_._]_N (IPAD)

IPAD Reqt_i_ements

D6-IPAD-70040-D

December-19, 197,7

/,

/ 1/_/" < Jr .... ,_ #

(Reference: Statement of Work 8.3)

i

I

)

Prepared under Contract No. NAS1-14700 by

Boeing Commercial Airplane Company

P.O. Box 3707

Seattle, Washington 98124

for

Langley Research Center

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION

REV. B

https://ntrs.nasa.gov/search.jsp?R=19870018866 2019-01-16T09:30:48+00:00Z
IPAD REQUIREMENTS

D6-IPAD-70040-D

December 19, 1977

(Reference: Statement of Work 8.3}

Prepared under Contract No. NAS_-_4700 by

Boeing Commerical Airplane Company

P.O. Boa 3707

Seattle, Washington 9812_

£or

Langley Research Center

NATIONAL AERONAUTICS AND SPACE ADMINISTRATION

ZPAD Project Manager

IPAD Project Office (IP0)

NASA Langley Research Center

DATE JZ// ?/!7

-i-
AUTHORS

 derson

A. L._

DATE _-/_ - 77

DATE & -I 0-77

- D.A. Davis _ __

L. Dickmann __ _2__

E. N _/Jochem

. M. K_to

G. yon Limbach

RESPONSIBLE MANAGER:

6-/o-77

DA= &-/,0-7 7

DA= <_- lOq7

H. Blair Burner

DATEI//9/77

CONCURRENCE:

S. O. W_hlstrom

IPAD Engineering Development Manager

D. E. Taylorf_-/ ....

IPAD Program_pport Manager

DATE

R. E/Miller, _r. /_

IPA_ Program ManageW

BOEING COMMERCIAL AIRPLANE

DATE I/-/_-?7__

COMPANY

-ii-
NASA Concurrence:

'_.-"__.>-Jv_-.r", o=_='_/,_/_7

Document Revlewer, IPAD _reject Office

NASA LANGLEY RESEARCH CE_ER

-iii-
ABSTRACT

The IPAD Requirements Document, is the product of the

Requirements Analysis Task, WBS I .6.2 and contains the IPAD System

Design Requirements. It is based on the IPAD User Requirements

Document (D6-IPAD-70013-D) and the Integrated Information

Processing Requirements Document {D6-IPAD-70012-D). This document

contains general information about IPAD and a list of the system

design requirements that are to be satisfied by the IPAD system.

The system design requirements definition contained in this

document is to De cc_,sidered as a baseline definition of the IPAD

system design requirements.

-iv-
E

O

oo

r.

r.

oo

I I

D

n

z tv

i

ii

iii

iv

v B

vi

vii

viii

ix

x I

xi 1

xii

xiii 1

xiv

xvi xv i

xvii I

xviii

xix

J

xx

xxi

xxii

xxiii ,

xxiv B

1

2

3

4

5

6

7

8

9 B

i0

ii

12

13

14

15 B

16 t

17 t

18

19 r

20

21

22

23 [

24 B

REV SY_

LIST

II

ADDED PAGES II

z _ z Iv z tv

OF

!

L

,,,.=,

a.

z

ACTIVE PAGES

I I

I ADDED PAGES

Z Iv Z no -r in,

B

x_i..,I

xxv11 B

B

25 B

26

27

28

29

30

31

32

33

34

35 )

36 !

37

38

39

40

41 }

43 _

45 _

46 _

47 _

48 _

i51 ,

i52 i

53 _

54 _'

56 _

_59 !

i60

161 I

_62 l

163 {

164

65 i

66

!67 !

69

70

71 !

172 I

73

-V-
0o

o

o

II Q- '

z

74

75

76

77

78

79

8O

81

82

ia3

84

85

86

87

88

_89

90

91

92

93

94

95

96

97

98

99

ilO0

lOl

102

103

104

105

106

107

108

109

ii0

lll

112

113

114

115

116

:117

ii18

119

120

121

LIST OF

IJ i,

ADDED PAGES II

:3E

o. o.

n,.z n,.z n,.

ACTIVE PAGES J i

j ADDED PAGES

n,'Z n,' iv

122I

123

'124

125

126

127

128

129

130

131

132

I

133 134 _I

135

I

136I

137i

138

139

_140

141

142

143

144

145

146I

147I

148!

149

is0i

151 -.'

152I 153

154I

1551

156

157

158

159

160

161!I

162

163}

164i

165t

166 i

167

168

169

170B

REV SYM

B

-vi-
[ LIST OF ACTIVE PAGES

ADDED PAGES ADDED PAGES

171 ]_ A.7 B

172 I 227 }I B. I B

B.2 17 3 1 228 I

174 ! 229 I_ B .3 I

17s I 230 B., !

176 I 231 i B.5 i

I '

17 7 232 i B., 6 _i

178 234 I B. 7 i

179 [ 235 B. 8 1

180 236 B. 9 i

181 ! 237 _ B. I0 !

182 _ 238 i B. 11

183 ! i 239 B. 12 _i

184 i 240 1 B. 13 ;

18 5

i 241 1 '_

186 • ! 242 I C. 1 :

187 _ 243 I C •2 i

18 8 244 C. 3 '

189 245 i C. ;4

190 i 246 D C. 5 i

i

191 _ C.6

192 C.7 !

193 i C.8

19 4 ! C •9=

195 _ C.I0 !

196 : C.11 '

197 ; C.12 i

198 i C.13

199 i C. I;4

C.15 ;

200 i 212 B C.16 _

201 i 213 C.17

202 i 21/4 C.18 1

203 I 215 C.19 _

204 i 216 C.20 :

205 ' 217 C.21

206 218 I C.22

207 219 I

208 220 ,i

209 221 I

210 222

i

! 2214 t

A.I 225

A.2 226 IB

A.3

A.4

A.5

A.6

)

IB

-viiREV SYM B
U

Q

REVISIONS

SYM REVI

A

DESCRIPTION

Add four new requirements:

i) 43.1 User Absence and Substitution

2) 57.1 Computer Program Certification and

Version Control

3) 57.2 Checklist

4) 87.1 Data Set Modification Log

Change requirements:

2-135, 5-329, 10-55, 16-221, 21-80, 46-337,

52-113, 60-262, 80-33, 81-340, 71-13 and 128-287

Delete requirement:

49-359

Note: All approved changes are denoted by the

revision symbol.

B Revise section 2.0 by:

I) Retitling 82 req. to clarify meaning

2) Adding a diagram to each third-level numbered

paragraph (approx. 19) to serve as an index

to the requirements therein

3) Add Appendix B, a short description of

requirements

4) Add Appendix C, a keyword list

5) Delete the hyphenated part of each requirement

number

-viiiI ATE I APPROVAL

2-6-79 Per CCR

#37

11-6-19 per CCR

#50

REV SYM n
TABLE OF CONTENTS

S_Y • o • o • • O • _ • • • o, • • as • o • o, • • o • • o

1.0 INTRODUCTION .....................

1. I IPAD OBJECTIVES .................

I. I. 1 Purpose .................

1.1.2 Scope of IPAD ...............

1.2 BACKGROUND INFORMATION .............

2.0

I. 2. I Problem Description ...........

1.2.2 Ewents Leading to the Requirements ....

_PAD REQUIREMENTS ..................

2. I USeR INTERFACE ............... . .

2. I. 1 User Language ..............

2. I. 2 User Tools ................

. I. 3 User Access ...............

2.2 DESIGN SUPPORT AND CONTROLS ...........

2.2.1 Design Process Support ..........

2.2.2 Computer Aided Design Project

Management ................

1

6

?

7

7

8

B

12

15

15

15

36

58

84

84

9"/

2.3 INFORMATION MANAGEMENT ............. 116

i. 3. I Data Management ............. 116

2.3.2 Infozmation Management Tools ....... 170

2.3.3 Computer Program Library ......... 178

2.4 AUXIT.LIARY/AXTERNAL SYSTEMS INTP_F_J_ES ..... 186

2.4.1 Host/Remote System Inter£aces ...... 186

2._.2 Software Interfaces ........... 191

2.5 GENERAL SYSTEM CAPABILITIES ........... 195

-ixREV. B
2.5.1 Performance ............... 195

2.5.2 Security ................. 206

2.5.3 Reliability ................ 211

2.5.4 Flexibility ............... 215

2.6 GRAPHICS ................. ._ . . 219

2.6.1 Graphics Standard ............ 219

2.6.2 Device Interface ............. 224

2.7 GRAPHICS RELATED TOdLS ............. 227

2.7. I _rap_ics Related Programming Tools .... 227

2.7.2 Geometry ................. 233

BIBLIOGRAPHY ...................... . . 246

APPENDIX A---CROSS REFERENCE ................ A. I

APPENDIX B--BRIEF DESCRIPTIONS .............. B. 1

APPENDIX C--KEYW_tD LIST ................. C. 1

REV. B

-x-
I_ST OF TABLES

Table Page

2.3.1.1.3-I Data Storage Estimate--IPAD Project I

SuDsonic Transport ............... 140

2.3. I. 1.3-2 Data Storage Estimate--Large Aerospace Company

IPAD DistriDuted Environment .......... 141

REV. B

-xi-
LIST OF FIGURES

Fi qume

2.0-1

2.1.1 -1

2.1.2-1

2.1.3-1

2.2.1 -1

2.2.2-1

2.2.2.2-1

2.2.2.2-2

2.3.1-1

2.3.1-2

2.3.2-1

2.3.3-1

2.4.1-1

2.4.2-1

2.5.1-1

2..5.2-1

2.5.3-1

2.5.4-1

2.6.1-1

2.6.2-1

2.7.1-1

2.7.2-1

IPAD Requirements , . .............. 16

Oser Language Requirements .......... 17

User Tool Requlremants ............ . 37

User Access RequireMents ........... 59

Design Process Support Requirements ..... 85

Computer-Aided Design Project Management . , . 98

Current SessLon Resource Report ........ 105

Summation Resources Report .......... 106

Data Management Requirements ......... _18

Data Management Requirements (Co_tSd} ..... 119

In¢ormation Management Tools Requirements , , . 171

Computer Program Library Requirements ..... 179

Host/Remote System Interface Requirements , , , 187

Software Interfaces Requirements ....... 192

Performance Requirements ........... 196

Security Re qulrements ............. 207

Reliability Requirements ........... 212

Flexibility Requirements ........... 216

Graphics Standard Requirements ........ 220

Device Interface Requirements ......... 225

Graphics Related Programming Tools

Requir_aerts ................ 228

Geometry Requ/r ements ............. 234

REV. B

-xii-
ACRONYMSAND ABBREVIATIONS

ACT

AED

ANSI

APT

ART

BCD

BCS

BPI

CAD

CAM

CDC

CDR

CG

CL

CLFILE

CLP

COBOL

CDLIST

CPI

CPU

_T

_%DA

DEC

DaMS

Accept_ce _iteria for Testing

ALGOL Extended for Design

American National Standards Xnstitute

Automatically Programmed Tools

Average Response Time

Binary Coded Decimal

Boeing Computer Services

Bits per inch

Computer Aided Design

C_puter Aided ManufacturiDg

Control Data Corporation

Critical De _gn _ iew

Center of Gravity

1. Command Language

2. Center Line

Center Line File

Cummand Language Processor

Common Business Oriented Language

Corporate Like Organizational Lists

Charactezs per

Central Processing Unit

Cathode-ray tube

Data Area Data Administration

Digital Equipment Corporation

Data Base Management System

REV. 8

-xiii-
EIA

FDP

FEDD

FORTRAN

GNAME

IBM

XDMS

IDR

INAME

XNTOL/OUTTOL

_PAD

IPEX

IPIP

IPO

ITAB

K/B

ERDNOS

LCGT

LRC

MIT

NASA

NOS

N/C

CM

Electronic Institute of America

FORTRAN Drawing Package

Far Early Domestic Dissemintation

Formula Translator

Group Name

International Business Machines Corporation

Integrated Data Management System {Cullinane Corp.)

Intermediate Design Review

Individual _ame

Inner Tolelance/O_ter Tolerance

Input/Output

Integrated Programs for Aerospace-Vehicle Design

IPAD Executive

XPAD Information Processor

IPAD Pro3ect Office (NASA Langley Research Center}

Industry Ted_nical Advisory Board (IPAD)

Job Execution Queue

Kel Board

A CDC Operating System

Low Cost Graphics Terminal

Langley Research Center _ASA)

Massachusetts Institute of Technology

National Aeronautics and Space Administration

Network Operating System (CDC)

Numerical Control

Operational Module

REV. B

-x.iv-
OS

PDR

RFP

RJE

RTAC

SAMM

SD

SGHS

SGS

SIGGRAPH

SLRT

SM

SOW

VM/CMS

WBS

2-D

3-D

Operating System

Preliminary Design Review

Request for Proposal

Remote Job Entry

Research and Technology Advisory Committee {NASA}

Systematic Activity Modeling Method (BCS)

Short Duratio_

Specialized Graphics Hardware Systems

Standard Graphics Softwa_

Special Interest Group--Graphics

Standard Li_ting Response Time

Source Module

Statement o£ Work

Virtual Machine/Conversatlonal Monitor System (IBM}

Work Breakd_ Structure

Two-Dimensiuna 1

Three -Dimensional

REV. B

--XV--
DEF IN_T IONS

ACCESS CODE

A code which will authorize an IPAD user to read or modify a

specific data set.

ACCEPTANCE CRITERIA

The rules, or standards that will be used during acceptance

testing to determine if a requirement has been satisfied.

ACCOUNTING P_OGRAM

A program which maintains statistics on computer resource

utilization.

AERGKLAST_C CXCLE

Consists of iterative processes which start with a stress

analysis based on rigid structure loads and ends with a

compatible solution between applied loads, structural sizing

for strength and fatigue and mass and stiffness to meet

_tatic and dynamic criteria. Implied in the solution is a

structure closely appxoximating minimum weight and cost.

ANSI STANDARD

A standard formulated _d controlled by the American National

Standards Institute (ANSI).

_E_ECARD

A card designed to ho_ microfilm image film.

APPLICATION P_GRAMS

Computer programs developed for the purpose of solving a

particular problem.

ARCHIVAL STORAGE

A repository for the storage of less frequently used data.

AVERAGE RESPONSE TIME

A measure of the actual response time experienced by a user.

This is usually estimated by observing many transactions and

is highly dependent on machine loading.

REV. B
BATCH CONTROL CARDS

Cards that contain commands directing the operation of

computer programs in the batch processing mode.

BATCH PROCESSING

A mode of computer processing in which computer programs are

executed with no interactio_ with the user during processing.

BATCH SUBMITTAL

Submitting computer program_) to a computer for batch

processing.

BINARY CODED DECIMAL (BCD)

A numeric code for representing each character of an

alphabet.

BENCHMARK

A point o_ reference f_om which measurements can be made to

evaluate the performance o_ computers or computer programs

relative to each other.

CARPET PLOT

This plot is generatea by intersecting a function of two

variables by two families of planes and plotting the

intersection curves.

CLASSIFICATION CODE

Used to identify items classified within a Uniform

Classification and Coding System. The system is based on

organizing data in a u_nsistent and disciplined manner. Each

code is meaningful and discrete, and is a universal index for

all information bearing the same code. It is useful as a

tool for storing, retrieving, sorting, analyzing, collating,

and identifying data. These codes may be used as sorting

criteria for the data stored in the information bank.

COMMAND LAN_AGE

A language for directing a computer in which each command

corresponds to a function to be performed.

COMMAND MODE

A mode in which the 1B_D System is awaiting a command from

the user.

-xviiREV. B
COMMUNICATION RATES

A unit of sig haling

unit of time.

•peed ° The number of signal events per

COMPUTE_ AIDED DESIGN {CAD|

The application of com_uters to assist in conducting

activities needed to get design ideas and concepts defined,

refined, and documented ready to transmit to manufacturing.

Included are not only conception and definition of vehicles,

systems, and hardware, but their evaluation through analysis.

COMPUTER AIDED DRAFTING

The adaptation of the computer for automated drafting. It

provides a man-machine dialogue allc_ing construction and

display of geometric _tities using a graphics device.

COMPUTER AIDED MANUF_CTURZN_ (CAM)

The application of computers to assist in performing

£unctions from the receipt of product definition to the

completion o£ an acceptable hardware item, system, or

vehicle.

COMPUTER PROGRAM

A series of instructions or statements, in a form acceptable

to a computer, prepared in order to achieve a certain result.

COMPUTER PROGRAM CERTIFICATION

The process of confirming that a computer program has been

validated.

COMPUTER PROGRAM VALIIIKTZON

The test and evaluation of a cunputer program to ensure that

all requirements have been satisfied and that the program is

corre ct.

O0N P_GUBAT ZON CONTRDL

A procedure fur controlled development and maintenance o£ a

document, program, or other entity to ensure its integrity by

carefully controlling all changes.

CONED UR PLOT

The plot of contour lines, usually generated by intersecting

a surface with parallel planes.

-xviiiREV. B
CONTROL CARDS

Cards that contain control data for directing the operation

of a computer or computer program.

CRITICAL DESI_ REVIEW (CDI_

A major review of the products of an IPAD Program Task

required to obtain approval to proceed to subsequent tasks.

CRITICAL PAtH

The longest time path of sequenced events and activities that

has the least positive slack. Slack is defined as the

difference between the latest allowable start time and the

expected start time of an activity. If the latest allowable

start time is greater than the expected start time, slack is

positive.

DATA AREA

An arbitrary collectiun of the data sets which are gro_ged

together for purposes of control, management, ease of use,

etc.

DATA BASE

A collecti_ of interrelated data with as little redundancy

as possible to serve one or more applications in an optimal

tashion.

DATA BASE MANAGEMENT

The _unction performed by a data base management system.

DATA BASE MANAGEMENT SYSTEM _BM_

A generalized tool for managing data bases. It makes data

interrogation, maintenance, and analysis of data available to

users.

DATA DEFINITION

The means by which data is described through its physical and

logical characteristics.

DATA DICTIONARY

A directory c_taining data element name, descriptions,

security controls, physical location, etc.

REV. B

-x.ix-
DATA ELEMENT

A named unit of data Which is not defined in terms of any

other named units of data.

DATA FORMAT

Defines the informatiun bank access method used to store and

retrieve a data set oc_urence.

DATA INTEGRITY

Ensuring that the data base is protected at all times against

invalid alteration or destruction.

DATA OCCURR_CE

Actual value(s) of data corresponding to a particular data

re fat ionship.

DATA PRIMITIVES

The basic indivisible building blocks for data in' the

information bank.

DATA RECORD

An ordered set of data elements.

DATA RELATIONSHIP

A data relationship is a logical grouping of one or more data

record s.

DATA SET

A specific occurrence of data corresponding to a given data

format.

DATA SET HEADER

Data contained in a data set header is used to identify the

owner and source of tb8 data set and to control access to the

values contained in the data set ° Headers for may contain

additional information such as element type, coordinate

system, etc°

DATA SET QUALIFIER

A version number or alphanumeric appendage to a generic name

to make a unique name for a data set.

REV. B

-xx-
I_TA SURVE _CE

Monitoring of data prouessing activities for the purpose af

reconstructing data which has been destroyed or modified, and

in/orming the affected users.

DEFAULT

A system assigned value or result which will be in force

unless intentionally overridden by the user.

DICTIONARY

Dictionaries contain definitions of data elements, data

relationships, data _crmats, coding modules, operational

modules, and jobs.

DZGITI ZERS

A device which assigns digital numbers to analog

measurements.

DISPLAY FORMAT

A special class of data formats that is used for displaying

data sets.

DISPLAY LAN_JAG E

The language interface between the user and a graphics

device.

DISTRIBUTED COMP _TING

Computing performed within a network of distributed computing

facilities. _he processors for this type of system usually

function with control distributed in time and space

throughout the network. Associated with the distributed

computing may be distributed storage facilities.

EXPLICIT INPUT/OUTPUT

Input/output action to or from a data set _hich is under the

control of a user program.

FLATBED PLOTTER

This name is used to describe those plotting devices which

draw on a horizontal flat surface, such as the Orthomat,

Gerber, etc.

REV. B
GEOMETRIC DESCRIPTION

The mathematical model describing a geometric entity.

HIGHER LEVEL LANGUAGE

A computer programming language in which the instructions or

commands may each result in many machine language

instructions.

HOST COMPUTER

The interacti_ computer complex for which the IPAD System

will be developed.

IMPLICIT INPUT/OUTPUT

Input/output action to and from a data set under the direct

control of IPAD.

INFORMATION BANK

The collection of all data areas defined to IPAD.

INTERACTIVE GRAPHICS

A graphics capability which allows the user to communicate

with the computer.

INTERACTIVE PROCESSING

Execution of a computer program which communicates directly

with the user, in the sense that it displays information in

response to new inputs and supports intense dialogue.

INTERACTIVE TERMINAL

A cummunicatiun device which provides a hardware interface

between the user and a computer for interactive processing.

INTERFACE ROUTINES

Software routines which interface hardware or software.

I-O LIST

A last Of variables representing data which are to be read or

written.

REV. B

-xxli-
IPAD CO_UNXCATION NETMDRK

All hardware and software furnished and maintained by the

IPAD contractor ur by independent vendors which is used to

provide communications between the IPAD host computers and

any IPAD satellite cou_uter. This shall include any

translators required to reformat data or computer programs

for transmission betwem_ computers.

IPAD COMPUTER PROGRAM LIBRARY

The collection of all user supplied computer programs

installed into IPAD.

/3_AD SYSTEM

An interactive computing system being developed to support

the aerospace vehicle design process.

IPAD SYSTEM ADMINISTRATOR

A person who has authority to administer the IPAD system.

His responsibilities are to maintain the IPAD system

(hardware and softwar_ once it is installed; to assure

system performance, integrity and security; and to interface

with t_e IPAD user commanity which he serves.

JOB

A sequence of executable operational modules.

JOB EXECUTION QUEUE

A queu e containing jobs submitted by IPAD users.

JOB NETWORK

A set of log_cally connected jobs in the IPAD system whose

execution order is dependent upon user supplied parameters or

calculated results.

KEY WORD LIST

Part of each dictionary which allows users to search and find

existing dictionary entries to fulfill their needs. This

capability will help to limit the number of redundant entries

in the dictionary which contain the same information or have

the same mathematical definition.

REV. B

-xx iii-
LANGUAGESYNTAX

The structure of a language. The objects in a language and

the relationships between those objects.

LINKED PROGRAMS

Separately assembled EEogram segments which are combined

together through a linkage processor to allow them to operate

as a single program unit.

LOGICAL STRUCTURE

MENU

The structure of data as it ks referred to by an application

computer program or a user.

A list of available choices displayed to a user at an

interactive terminal.

MESSAGE FILE

A file of messages for users created by the system or other

IPAD users.

MICROFII_ PLOTTER

A plotting device capable of producing microfilm output.

NARRATIVE TUEORIAL S

_ducational material displayed at a terminal which instructs

the user in the use ol the system capabilities.

OBJECT MODULE

A module of a computer program expressed in the language of a

computer.

OPERATIONAL MODULE

An executable collect_ of ob_ct modules which contribute

to one or more jobs.

OPERATING SYSTEM

The control program f_ the host computer or satellite

computer under w_ich IPAD or a subset of IPAD executes.

REV. B

-xx.i.v-
PASS XVE COMMAND

Such commands cause the IPAD system to inform the user of the

functions which are a_ailable to pursue a particular task.

PERMISSION CODE

Constraints on the use of the ZPAD command language.

PRC_'ZE_S

A series of continuous actions that are defined and planned

within a hierarchical system of levels divided into

activities that are accomplished by executing one or more

jobs. Each level has forward and feedback data flow paths

defined within activities and between related activities.

Data transfer between levels may be forward or feedback.

PROGRAM ITEM NUMBER (PIN}

A number which relates an item of work to the work breakdown

structure. It is used as a primary index to work items and

for cost collection.

PROJECT

The sequence cf tasks and subtasks to be performed during an

associated design and/or analysis effort.

PROJECT PLAN

The definition of all project tasks, subtasks, expected

results, and the associated oontrol in terms of schedule

dependencies.

QUERY LANGUAGE

A language designed specifically for formulating data base

retrieval requests.

It_4OTE JOB ENTRY

Entry into the host computer of a job from a remote input

device.

REMOTE SITE

Any computer processing system which is remote from and

connected to the host computing system.

REV. B

-xxw-
RESPONSE TIME

The time interval, between the operator typing the character

signifying the end of the input and the terminal typing the

first letter of the reply.

REQUIRemENTS TREE

A hierarchical structure for the IPAD requirements. The

outline of the body of the IPAD requirements document.

SATELLITE COMPUTER

Any cumputer remote from and in communication with an IPAD

host computer.

SECURITY CODES

Coded conventions established to meet company or governmental

rules pertaining to controlling access to data. These are a

key subset of the total set of access codes.

SOURCE MODULE

A specific collection of symbolic code that contributes to

the delinition of one or more operational modules. Source

modules are the smallest division of user source code that

can be defined.

SUB_SK

A sequence of jobs which represents a step in a project.

SU_TASK DATA AREA

A data area that is associated with a user during the

execution of one subtask. Each subtask will have an

associated subtask data area. The subtask data area is a

private user working data area and all data is generated in a

subtask data area.

TASK

A sequence of subtasks accomplished by a group which

represent a milestone in the projeot plan.

USER IDENTXFICATION

A unique identifier associated with each user of IPAD. It is

mandatory that this ID be associated with a person and not an

activity or an organxzation.

REV. B
UTILITY SOFTWARE

Programs which aid systems operations. They usua]ly perform

services freauently needed by users.

VFPSIOM NUMBEP

A special identification used to denote a specific version of

a data set or a pro aram.

X-Y PLOTS

A two-dimensional p]ot of one variable against another.

-xxvJ i-
SUMMARY

The principal objective of IPAD is to provide a computer

software system which will aid the U.S. Aerospace Industry in the

design of future vehicles. It will be an engineering information

processing system £or aerospace vehicle design to be installed

the computer complexes of major U.S. Aerospace companies. It

shall serve as the Key con_aunication and calculation integrator

for a large number of designers conducting a broad range of design

tasks over significant periods o_ time and on a wide variety o_

aerospace vehicles. IPAD will increase the effectiveness of the

individual designer by accelerating the computational and data

m_u_agement tasks of the design process. The system must respond

to company needs from conceptual t_rough detailed design and

provide interfaces to computer-aided design and computer-aided

manufacturing. IPAD im_st be _eadily modifiable and will change as

tt,e user Is needs change.

Requirements for a user interface to IPAD cover t/%e areas of

language, tools, and access. User friendly languages will be

provided for interface with the IPAD system. An assortment of

user tools will be available. A variety of modes of access and

dlfferent priorities of access are provided for the user's

convenience. For the protection o_ the user and the system, user

identification and classification are required.

A co_nand language will provide access to IPAD system

capabilities. The command language will allow a user, unfamiliar

with the language, to get assistance on IPAD use. A query

ianguage will be provided to enable a user to access information

in the IPAD data base. T_e IPAD languages will be constructed to

accomodate users with different levels of IPAD expertise; e.g.,

expert, intermediate or novice.

An assortment of user tools will be available to all IPAD

usersumanagers, enganeers and supporting staff. The tools will

De ava/lable interactively and in batch mode. The number and

types of tools made available will change as the needs of t_e IPAD

user evolve.

IPAD will provide tools to enable the user to:

edit and update stored data, computer programs and text

documents ;

generate reports using information from the IPAD

In£ormation Bank;

£acilitate communication between IPAD users by providing

utilities to build in£ormation menus, organization lists

-l-
and mailing lists and enabling a user to transmit

messages to other IPAD users;

maintain and query references to IPAD documents and

procedure s;

o evaluate computing system performance ;

o _elp the user when he requests assistance;

• debug computer programs; and

• construct command sequences.

IPAD will provide a _ariety of modes to the user for

interfacing with the IPAD system. He may interface via an

interactive terminal, batc31 control cards or by initiating user

programs that issue cunnands or calls for IPAD capabilities.

Interactive work may De done either by textual or graphical

terminals. Batch jobs may be submitted remotely via a satellite

computer or from an interactive terminal.

Four different categories of user priority will be

recognized: standard, appoin_aent, short duration, and emergency.

The standard user's access time and turnaround time is dependent

upon system load. The purpose of the appointment category is to

give a user an opportunity, through the use of appointments, to

run in _ semiprivileged state. An appointn_nt user has fast

access to t/%e system and cannot be put in a wait queue when the

system gets overloaded. Snort duration users are privileged in

access and response time but limited in hook-up duration and

restricted in activities. An emergency user has to 9 priority over

all other categories of users.

IPAD will provide processing security for individual users.

Thls protection will be provided by employing user passwords.

These pdsswords must provide unique identification, must be

protected from discovery and must be easy to use and modify.

IPAD will support engineering an_ management in planning,

deflnlng, modifying, controllilg and integratir_ engineering

teci_ical processes. Support provided includes the building and

saving of 3oh sequences, the execution and monitoring of jobs,

process reporting and data release control to inform users of data

status. _iformation to be s_ared Dy ,_re than one organization

shall be under release control.

IPAD will support managers in planning, monitoring and

reporting Design Projects. Management computer programs will be

made available for analyzing tectnlical and management information.

An individual IPAD usez will be able to assess the status of his

own sumtasK, data, task or the overall project status. In

-2-
response to IPAD monitoring and reporting, controls may be exerted

to limit, terminate or suspend activities.

In/ormation management within IPAD is broken down into three

categories: data management, information management tools and

computer program library. Data management is concerned with the

organization, manipulation, control, integrity, security and

ach_tnistration ot IPAD data. Information management tools are

provided to maintain data, to perform data transformations, to

c_upare data and to perform arithmetic and logical operations on

data. Tl,e computer program library contains computer programs in

source and executable forms. The programs may be supplied by the

user or generated by so£tware processes (e.g., compilation).

Co,_uter programs may be structured into jobs and executed.

The handling o_ data within IPAD will have many facits

including organization, m_nipulation, control, integrity, security

and administration. Data organization at the elementary level

will consist of elements, formats and data relationships which

will be grouped into _ata sets. Data sets are organized into data

areas. Data manipulation includes capabilities to query, to copy

dat= and programs and to access and retrieve arc.hived data. Data

control governs data access, data changes, purging and data

r_tention. Backup and recovery procedures are provided to guard

the integrity oz all data in the IPAD data base. Proper security

clearance will be required to access some data sets within IPAD.

Security control of read/write access will be provided. Data

administration responsibility is to be assigned to a designated

person or organization who will De responsible for exercising

control over the entire IPAD inzormation bank.

IPAD capabilities shall De provided to enable the user to

m_intain data in tale IPAD infor,m_tion bank and to perform data

transformations. Maintenance features include data updating, data

restructuring and data reformatting. Fale maintenance

capabilities will be also provided. Files may be created from

data in the IPAD intormatm0n bank or data _rom files may be

inserted into the IPAD data base. Command sequences for creating

or decomposing files may be saved for subsequent execution.

The computer program library shall consist of programs in

source or executaEle forms. The programs may be supplied by the

user or generated Dy sottware processes (e.g., compilation}.

Insertion and deletion of programs shall be straightforward and

,l_cnine independent so that a company may insert its own programs.

IPAD user aids will be nade available to facilitate the

interZacing or existlng aerospace computer programs with each

o_/1 er.

IPAD must be adaptable to difterent hardware implementation

and computing facilities. IPAD must De able to share data with

non-IPAD systems and to safeguard and control non-IPAD data while

-3-
in the custody of IPAD. Existing telecommunication standards will

De used to facilitate cc_u_nication between computing systems.

Support software and user aids will be provided to facilitate

transfer of programs, data base, etc.

IPAD must be able to interface with the host system and with

remote systei_s. IPAD snail permit access to and recei_ data from

non-IPAD systems using existing standards whenever possible.

IPAD shall be able to communicate with existing software

systems external to IPAD and facilitate transfer of program

,_dules, data bases, etc., between IPAD installations. Support

software and user aids shall _e provided for such purposes.

The IPAD systeal sh_ll provide fail-safe security to prevent

the disclosure oZ information which may be detrimental to National

Security or the proprietary interests of the user company. System

iailure must not result in the degradation of IPAD security

controls. The reliability and availability of the IPAD system

_,ould not De li,_iting factors in the system's usefulness. IPAD

sr_ll be designed to De flexible when adapting and interfacing

with individu_l installations.

Mesponse tlme must De adequate. System capacity should be

i_,dware configuration limited rather than software limited.

Tools £or performance monitoring will be provided for the Syst_n

A_tinistr_tor. Varlous accounting programs will be provided for

project management, reporting and statistics.

_raphics standards for communicating between devices will be

established. Graphic equipment interface software will be

provided w_thin IPAD to accommodate a prescribed assortment of

graphical equlpment.

A standard graphics software package (CORE) will De provided

consisting of lower level primitive routines which will minimize

mac1_ine dependence and will be capable o£ supporting a wide range

of graphics devices. These basic functions will all_ development

of _ophisticated graphics related applications.

IPAD shall provide techniques for converting data from the

IPAD standard for_ts to the format required by dumb and

intelligent type terminals. Cumpression and explosion techniques

shall reduce the amount of data sent over communication lines.

IPAD shall prowide a variety of _unctions to support CAD, NC

and related analyses. Tools shall be provided to construct and

display engineering deslgns and data plots. Standard and extended

geometry formats shall be supported. Conversion utilities shall

be provlded to convert geQmetry formats to a standard format for

commun_cat ion purposes.

-4-
Graphics related programming tools shall be provided to allow

the development of sophisticated graphics capabilities from the

standard graphics software primitives. An animation package shall

be provided to display dynamic phenomena.

IPAD shall provide a wide variety of CAD/CAM geometric

entities for the construction and display of engineering designs.

A standard geometry format for comn_nications sh_ll be provided.

IPAD shall provide tools to detine cutter paths utilizing CAD

engineering desi_ geometries and shall also provide a utility to

convert the same geometry to APT geometry source format.

-5-
1.0 IN_)DUCTION

The IPAD Requirements Document defines the requirements that

are to be satisfied by the IPAD System. After approval, this

document will be placed under configuration control. The

requirements definition contained in this document is to be

considered as a baseline definition of the IPAD requirements. All

changes or additions to the requirements definition must be made

to these documents.

The IPAD Requirements Document was produced by the

Requirements Analysis Task. The sources of information are the

Integration and Information Processing Requirements and the IPAD

User Requirements.

The two documents were assigned to personnel on the

requirements analysis team. Each person composed a list of

recognized requirements from an assigned document or sections of a

document. Each item in the list was composed of a requirements

number, a reference to the source of the requirement (document,

section, page), and a statement of the requirement. The

requirements in these lists were studied by the team and divided

into two groups: firm requirements and questionable requirements.

These questionable requirements were presented with questions to

the IPAD Program Engineering Group and to a representative of the

NASA IPAD Project Office. _he firm requirements were analyzed by

the requirements analysis team. These questionable requirements

were also analyzed when they became firm requirements.

During analysis, each requirement was evaluated against nine

criteria. _%ese criteria are: complete; correct; precise;

unambiguous ; clear ; consis tent; re levent; testable ; traceable;

free of design detail; and manageable.

If a requirement did not satisfy all nine criteria, it was

returned to the originator for resolution. The requirements that

satisfied the criteria were placed _nto the appropriate section of

the IPAD Requirements Document. As the problems were resolved

with the requirements presented to their originator for

resolution, those requirements were re-analyzed and eventually

placed in the document.

Acceptance test criteria were written for each requirement.

These will become part of the TpAD Acceptance Test Plan. An

abstract of the acceptance test criteria for each requirement is

included with each requirement in this document.

The format adopted for documenting each requirement is as

follows. Each requirement will start a new page and will begin

with a sequence number and a title. _he sequence number will have

the form n-r, where n is a running sequence number 1,2,3,...,etc.,
and r is the requirement number. Next will come the requirement

source references delimited by con_Qas. ExEept for Boeing and NASA

requirements rework team source reference, each source reference

will have the form: doc/sec, where doc is the document source, and

sec is the section withln the document. Possible document sources

(doc) are:

1.3 for document Db-IPAD-70012-D;

1.4 for document D6-1PAD-700 13-D ;

SOW for Statement of Work;

F3 for IPAD FeasiDility Study, Volume III;

SCAC--_qA for Boeing/NASA requirements rework team.

Next comes the requirement description followed by the

acceptaulce criteria aDstract.

1 .1 IPAD OBJECTIVES

1.1.1 Purpose

Within the concept of a design data management system, IPAD

is intended to satisfy three primary objectives:

1. improved productivity;

2. fewer manufacturing changes ; and

3. lower tectulical risks.

1.1.2 Scope of IPAD

IPAD is software to computerize, insofar as possible,

company-wide design-information processing. Its intended scope is

such that it will simultaneously support design activities of a

typical cumpany mix o£ multiple development projects. It will

serve management and very large engineering staffs at all levels

oz design (conceptual, preliminary, and final) and will aid in the

assembly and organization of design data for support of

manuf acturlng processes.

IPAD software will function on "third generation" computer

complexes typical of those in use today Dy large aerospace

corpordtions and will augment, rather than replace, existing

"sy_-tem software." it is currently visualized as composed of (I)

executive software that will control user_lirected processes

through "interactive- interfaces with a large number of terminals

in simultaneous use by engineering and management personnel; (2) a

large n_r of utility software packages for routine information

manipulation and display function; and (3) data manaqement

software to provide a comprehensive, versatile capability for

efficiently storing, tracking, protecting, and retrieving

-7-
exceptionally large quantities of data maintained on multiple

storage devices.

Note that the data base includes the technical analysis and

design computer programs utilized by various disciplinary

specialists. Such programs are not regarded as part ot IPAD, but

,mast be provided by the user to form t_e complete design-software

system; they can include existing and future company-proprietary

programs, as well as those in the public domain. The data base

will dlso include all o_£icial project information defining the

characteristics oZ current baseline and alternative designs and

thelr perforlm_nce, as well as archival "handbook" information

formir_ the tectu%ology base for company designs. Simultaneous

access to the same baselin_ design information by all disciplinary

groups will thus be possible. Temporary libraries, for design

in£orm_tlon Deing actively utilized by individuals or tea,ms, will

also De provided.

It should be emphasized that IPAD is not "automated design"

software _,d will not constrain company design methods. The

c_aracteristics and quality of aerospace designs in the future, as

now, will depend on such elements as the creativity of designers,

the quality o£ technical stafis and their analysis tools and

design data, and the coordination of design and manufacturing

technologies. IPAD is a tool to improve the efficiency and

ezZectiveness of the use of these elements.

IPAD processing requirements shall be developed to

incorporate the requaxements for military and commercial aircraft

and aerospace vehicles.

1.2 BACKG_O UND INFORMATION

I. Z. I Problem Description

The Evolution ot Comput_g in the Design Process

Large design problems require a division of tasks.

Indlvidual designers are assigned a part of a task under the

_irection of a task leader. The designer performs his subtask by

dividing it into several manageable jobs. Tasks are organized and

reported by the task leader as part o_ a project group responsible

for the design of a product.

_e result of the design process is a single product entity

_l which all components must function harmoniously. Hence,

extenslve data con_nun_cation, evdluation, and iteration are

required to optimize the design. Orderly methods for introducing

changes _n the design are necessary to ensure convergence. These

methods establish a data (inZoz_Ik%tion) _andling environment.

-8-
This environment characteristically:

Requires extensive record keeping for data and

configuration management;

Requires accurate and timely production and

communication of data;

• Has complex informal and formal communication paths;

Is continuous with respect to time, activities and

people.

These information functional characteristics remain unchanged even

though the methods and computerized tools used may change

significantly.

Prior to the use of computers, all calculations were

perZonned by hand or Dy using slide rules and other mechnical

aids. This process required the designer to record a set of

values, input these values into a mechanical device, record

results and generally manage each detail of tale computation by

_and. The slze and complexity of the calculations were limited by

the manual abilities of t_e designer.

When computers were first introduced, they were used to

relieve the manual constraint on calculations. Typically, the

computer was programmed to perform the arithmetic, record

intermediate values, and generally manage the computation process;

hence, effectively automating the routine manual activities in

performing calculations.

The computer was so effective that the designer was able to

extend his cOmputational ability by many orders of magnitude,

often utilizing theories and methods previously unavailable

Decause of their extensive arithmetic. Improvements in computing

hardware, operatM, g system software, and programming languages

resulted an further extensions of this computation capability.

The continued automation of calculations, produced new

constraants. While individual designers _re able to produce

thousands and even millions ot numerical results in very short

periods of time, the volume of data to be handled by people became

the constraining factor. People began to be faced with

unmandgeaDle data volumes associated with data preparation,

evaluation of output _nd _nmunlcation oZ results. Computing

h_rdware and software were oriented to batch processing at the

physical site of the computer and gave no support to the

transmission o_ data between individuals or between coding modules

to be executed together as one job. Hence, while large volumes of

calculations could no_ be performed, information handling was

still a manual process.

-9-

REV. B
Early automation of calculations on simple tasks soon gave

r_se to other problems that were part ot the task but manual in

nature. The general question of problem solving efficiency began

to emerge. Instead of seeking efficiency improvements on one

isolated task element such as calculations, all task elements come

into question. Studies examined t_is broader eZficiency question

ol how to lower task total cost by considering both the human

aspects and the computer aspects of a task. In summary, the

significant findings were:

The computing cost is approximately one-tenth of the

total cost ;

The time people spend on the task is the most important

cost element;

A proper selection of computing devices and services can

reduce task total cost by 25_ through reducing time

people spend waiting for computations.

The early successes with calculation automation on simple tasks

naturally led to putting more complex tasks on t_e computer.

These more complex tasks inevitably resulted in data handling

problems, especially at technical module interfaces.

Integrated systems were developed to relieve the constraint

oZ communicating large volumes of data across program interfaces.

These systei_s typlcally included several modules, each identified

with a set of calculations. Data was transferred across module

interfaces Dy developing compatible data formats and passing the

data through the computer system directly. As a result, modules

were able to conumn_icate technical data reliably, precisely and

rapidly.

Executive control systems were developed giving the user

control of the operation or the integrated system with language

syntax t_iliar to him. Data management systems were also

developed for automatic retrieval and storage of data by co_uand

ot tae individual program.

Computing hardware and software were developed to support a

direct real-time interface between the user and the computer.

This interface, combined with executive and data management

_ottware, gave t_e user control o£ the computer with respect to

h_s own prooessing, it allowed the user, within limits, to make

real-t_ae adjustments to data and execution sequences and to

Interrogate output through direct access to large capacity data

stordge devices.

T_is environment introduced several advantages. Integrated

systems were effectively configured to include several related

dlsciplines, thus providing a medium for exchange of data and a

-10-
common reZerence system for problem solution and theory

develo_,ent. In parallel, later generation computing systems

provided arithmetic and data transfer rates sufficient to support

the data _lumes to analyze total aircraft responses such as the

aeroelastic cycle, the total /light control system, or the engine

to airframe interface.

By coupling integrated systems with interactive graphics

devxces, computer-aide_ drafting systems were developed. These

systems h_ been interiaced with numerical control software, thus

providing a direct tie between product design and manufacturing.

The Next Steps That Need to be Taken _n the Development of

Computers to Support the Design Process

Early in the IPAD study, the problem solving environment

typified by integrated systems was re-examined. This examination

identifed some very diz£erent characteristics associated with the

design process whlch had not been identified. These

c_dracteristics evolve frc_ the long duration of problem solving

which is characteristic of all but the simplest work and is

particularly present _n product design processes which span months

and even years. It was found that design is a hierarchy of

processes; individuals _nd their subtasks, tasks composed of many

su_tasks, and product studies composed ot many tasks.

In examining the details of this process with respect to time

uuration, it was observed t_at:

DiZferent subtas_s or different sequences are utilized

as the study progresses and as new insight is gained

into technology trades;

Most su_tasks are not completed in one work period;

therefore, t/%e designer must re-orient himself, the data

and the subtask in order to continue at his next work

period.

Large design problems are divided into management, technical,

and support tasks. These tasks are further subdivided into

manageable work packages. During _ performance of these work

packages there ks a need for communication between the groups

involved. To support t_is c0mn_nication, a computing system

st_uld be available with the following key features:

Re

IS readily accessiDle by personnel in engineering,

manuZacturing, manag_nent, and support functions;

2. Is easy to use without the need for long training periods;

o

Provides timely responses that encourage a continuous thought

process for a large number of users;

-11-
•

5_

e

•

8.

Can be installed in various con_puting environments without

extensive modification to itself and little or no

modification to the _ost computing environment;

Provides secure, private, and reliable storage for programs

_nd data ;

Provides for the interrogation of storage and the sharing of

information among _eople, among programs, and among people

and programs;

Provides for the incorporation of existing programs;

Provides for the dynamic specification and control of

sequences in which programs are to be executed.

Is extendable in scope to cope with new methods of solving

existing proDlems;

10. Allows a computing task to be suspended and resumed at a

later time;

11. Keeps a record oZ users, activities, data storage accesses,

data transZers, data creations, etc.

12. Provides for information continuity over long periods of

time;

13. Provides tot information continuity over many different task

sequences.

The Problem Definition

There are no universally available computing systems that

satisfy all oZ the needs of a computing system to support the

engineering process as described. IPAD development must consider

the existing computing environments and the computing environments

expected in the future. The difference between these computing

environments and the computing system needed to support the design

process is the problem that is to be solved. That problem

de_Inition must De measured against the time and resources that

are available to determine what part can be solved by specified

dates. IPAD development must proceed in such a way that the

evolving system keeps pace with tae changlng needs of potential

users and t/ue changing state-•Z-the-art of computing systems.

1.2.2 Events Leaainq to the Requirements

IPAD has evolved over the past ten years beginning with

discussions at Boeing in 1967 and continuing with a study and

critique process that _as included extensive aerospace industry

Jxxvolvement. Two in-depth studies of the feasibility and possible

-12-
forms of an IPAD system were carried out by The Boeing Company and

General Dynamics/Convair° _he total cost of these studies over a

17-month period was $611,000. Each study contractor undertook a

careZul dissection of the vehicle design process to delineate

those iunctions and tasks that can be beneficially supported by

conjurer hardware and software and then defined the format and

elements of a software system that could substantially improve the

design process. They assessed the impact of t_is £PAD system on

company c_nputer hardware requirements and on the performance of

co,_any starts aria evaluated its cost and benefit potential°

One company examined these questions An the context of design

of %_,ree kinds o_ ve/licles - a large subs_lic transport, a

supersonic tr_u, sport, and a hydro£oil - and developed a

c_nprehensive, detailed picture of the design process as a

muitilayered network oZ functions. The other examined intensively

the tasks and interfaces of individual designers and groups and

analyzed careaully t_e _n£ormation flow in design. They used a

combination ol bottom-up counting ot the effects of the

constituent parts of the design process and extrapolation of

ex_rience with existing _mall software systems to arrive at

computer requirements, costs, and benefits of IPAD software. Both

concluded IPAD is feasible and will fit on existing computers.

They arrived at so/tware systems that differed in detail, Dut

exhiblted the same ge,_ral characteristics and order-of-magnitude

costs. Projected benefits included 25-90 percent time and 20-60

percent cost savings in design, better management visibility, and

reduced product risk and cost resulting Zrom greater depth in

early tr_de-offs, on-tinge designs, and fewer design changes during

production.

Results of these studies were aired in tour oral reports that

were heavily attended Dy representatives o_ industry; for example,

83 industry representatives attended the Zinal oral presentations.

Following completion of the studies, the results were critiqued by

teams from McDonnell Aircraft Co. ; Lockheed-Georgia Co.; Grumman

Aerospace Corp.; _ockwell International Corp., Los Angeles,

Aircraft Div. ; Control Data Corp. ; IBM Corp. ; and Sperry Univac.

These firms examined such questions as completeness of the

studles, crediDility of the proposed systems and projected

development parameters, user acceptance, and government and

industry roles. '1_ey expended significant effort over four

months, employing 31 team members and about 100 part-time

consultants. The critique reports reveal a wide spectrum of

views, but stong consensus t_at IPAD development should proceed,

should not include disciplinary module development which should

remain largely the prerogative of industry, and should provide

early delivery o£ software and user involvement. Because of the

inevitaDle budget limitations, it was recommended that NASA limit

its speciZic objective to production of a truncated, but

'_or_ing," system.

-13-
Other evaluations of IPAD include an Army-funded study by

McDonnell Douglas Astronautics Co. of its benefit potential for

missile design and a small NASA-funded study by Battelle Columbus

LaDordtories o£ its potential for non-aerospace application. In

addztion, the NASA Mesearch and Technology Advisory Committee

(RTAC) on Materials and Structures sponsored a colloquium of highlevel aerospace managers at MIT on January 30-31, 1974, at which

IPAD was examined and dlscussed. As a result, the NASA RTAC on

Material_ and Structures recommended pursuit of the IPAD

development by NASA.

In FeDruary t_rough April, 1975, an IPAD Prospectus, prepared

by NASA, was reviewed a,_ commented by aerospace executives whose

zirms were anticipated to be interested in membership an the IPAD

advisory board, evaluation of 1PAD software, and involvement in

IPAD support and maintenance in the future.

An RFP for IPAD developxaent was released in May, 1975.

Proposals were received from the Boeing Commercial Airplane

Company, McDonnell-Douglas, and a Computer Science CorporationGrumman team. In December, 1975, the Boeing commercial Airplane

Compal,y _as selected as the IPAD System developer. The

develo_nent contract covers a five-year period involving

approximately 100 man _ears of development effort.

Oontractor work on IPAD development Degan in April 1976.
2.0 IPAD REQUIREMENTS

The principal ob_cti%_ of IPAD is %0 provide a computer

software system which will aid the U.S. Aerospace Industry in the

design of future vehicles. IPADms ccr_uter based capability will

substantially reduce design time and costs and will afford

improved vehicle performance.

IPAD is an engineering information processing system fur

aerospace vehicle design and is to be installed on the computer

complexes of major U.S. AexDspace companies. It shall ser%_ as

the key commum_cation and calculation integrator for a large

numr_r of designers conducting a broad range of design tasks over

significant periods of time and on a wide variety of aerospace

vehicles. IPRD will increase the e_fectiveness of the individual

designer by accelerating the computational and data management

tasks _ the design process. The system must respond to company

needs from conceptual through detailed design and provide

interfaces to computer-aided design and computer-aided

manufacturing. IPAD must be readily modifiable and will change as

the user's needs change. _ee figure 2.0-I.}

2.1 USER INTERFACE

Requirements concerning the user interface cover the areas of

user language, user tools, and user access. User friendly

languages will be provided for interface with the IPAD system. An

assortment of user tools will be available. A variety of modes of

access and diZferent priorities at access are provided for the

user's convenaence. For the protection of the user and the

system, user identification and classification are required.

2. I. 1 User Language

User friendly languages will be provided fur interface with

the IPAD system. A command language will provide access to IPAD

system capabilities. The oommand language will allow a user,

unfamiliar with the language, to get assistance on how to use

IPAD. A query language will be provided to enable a user to

access information in the IPAD data base. _he IPAD languages will

be constructed to accomodate users with different levels of IPAD

expertise; i.e., expext, intermediate or novice. (See figure

2.1.1 -1 .)

REV. B

-15-
...,J

REV. B
I,-'- Z0

..--!

...I iI i

,_C oO I (.D ._I la..l

U-I I

,_I ,-I ,-'I i

REV.B

-17-

qb_

(.-

I=:

S,-

re"

(-.

.-J L

::)!

,J

oJ

'-,I

-r-
REQUIEEMENT I USER LANGUAGE

SOURCE 1 .q,/2.1.1

_S_I_ION

The IPAD user languages (e.g., cummmld, query, edit, etc.)

are user oriented and consistent in vocabulary, and syntax.

Defaults are employed when practical and are directed towards the

experienced user.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A user opinion survey will be used to evaluate the IPAD user

languages for all modes of operation during acceptance testing.

The evaluation criteria wiil include: consistency in vocabulary,

syntax and £ormat, ease of changing from one user language to

another, and ease of use. These criteria will first be evaluated

during the user language design phase and subsequently tested

concurrently with most of t_e other requirements, with each user

completing a check list for each mode of the user language that is

tested.

In addition, tests must be conducted to verify that the

defaults in the user language are operational, and that they are

directed to the experienced user.

REV. B

-18-
R_UIILE_VIENT _ USER SKILL LEVELS

SOURCE SOW/5.2.2, 1.4/2. I. I

DESCRIPTION

IPAD shall address the problem of variation in expertise in

tIAe use of computers and IPAD itself.

The system shall direct by virtue of the user inputs, the

level of response required and make dynamic ad_stments based on

the detected skill ot the user. It is intended that IPAD minimize

frustrations at all user skill levels by optimizing guidance in

the use oZ IPAD conm_nds ana supplying explanations of

diagnostics, prompts, defaults as indicated by the user input.

ABSTRACT OF THE ACCEPTANCE CRITERIA

'_he system capability to detect the skill level of users and

_e appropriate responses will be checked for all user functions.

A user opinion survey will be used to evaluate the "help"

pruvide_ _or all uses oz IPAD. The criteria considered will be

utility, clarity, ease of use, adequacy, and appropriateness for

s_ill level.

REV. B

-19-
REQUIREMENT 3 E PAYOR DIAGNOSTICS

SOURCE SOW/5.2.2, 1.4/3.3.1, I._/2.4.3

DESCRIPTION

All user input to IPAD or its utilities (excluding user

supplied utilities and application programs) shall be checked for

errors. IPAD error diagnostics shall

a. Be complete, clear, concise, courteous, and spelled

correctly.

b. Explain the error and how to rectify the problem.

c. Be specifically identified as to source.

d. Be Zully explained in both the user's manual and through

HELP mode.

e. Include warnings for semantically suspicious commands.

Z. Include a brie_ mode which at the user's option will

eliminate all put the most essential portions of

diagnostic messages.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A user opinion survey will be used to evaluate all IPAD error

diagnostics based upon t/%e user's ability to quickly correct

errors through the use of the diagnostics. _le diagnostics will

be evaluated for completeness, clarity, courtesy, adequacy of

explanation, and ease of error detection.

The user option to request "brie£" diagnostics will be

checked. The ability to return to the detailed error diagnostics

should also be tested.

This requirement will be tested concurrently with other

requirements throughout acceptance testing.

REV. B

-2 O-
2. I - 1. I IPAD Command Language

The IPAD command language is composed of active and passive

command types. Active commands enable the IPAD user to initiate

IPAD system capabilities. Passive commands help the user to

understand IPAD and how to use the active commands.

T_e command language is to be user friendly; that is,

abbreviated commands will De accepted, detault parameters will be

provided w_ere needed and useful error and warning diagnostics

will be returned whenewer necessary. Host operating system

capabilities will be accessible from IPAD but the corresponding

cc_um_nd language will be independent of the host computer.

Managers or persons in authority will be able to restrict the

set of coum_nds available to each individual user. Status,

resource and message re_orting will be available upon request.

Active conumand functions may be part of subordinate user

languages but will be accessible t_rough the IPAD command

language.

REV. B

-21-
R_QUIR2_IENT _ COMMAND LANGUAGE FUNCI'IONS

SOURCE 1.4/2.5.2.1, I._/2.5.2. _

DESCR IPT ION

IPAD ira/st provide a user command language to perform certain

Zunctions, examples of which are given below. These functions

include two types: those that are part of the executive level of

the £PAD co_aand language and those that are incorporated in

suuordinate user languages.

_xecutive-level IPAD command language functions shall include

the following capabilities:

• lnitiate execution of a job.

• Request loading of SMs/OMs/jobs previously saved by the

user.

• Initiate saving of SMs/OMs/jobs for subsequent usage.

• Interrupt execution of a job wit_ or without automatic

data saving.

• Restart an interrupted job.

• Initiate printing of data or programs.

. Submit a batch joD Zor execution.

• Query the status of a job.

• Send a message to other IPAD users.

• _equest aelp.

• aequest display of information on use o£ IPAD (overview,

Key word, prou_dures, menus, command structure, etc.).

• Access IPAD utilities.

• Access host operating system capabilities.

• Exit IPAD.

REV. B

-22-
Command functions that may be part of subordinate user

langudges, but which must be accessible through the IPAD command

language include :

° Display an explanation o_ the current operation that the

user is performing.

• Find desired _n/ormation (data, programs, data

definitions, etc.)

• Generate printed reports.

• Compare two data sets or programs.

• Display graphical information.

• Define new data elements/formats/relationships

- Purge entries from a data base.

• Review/update data or data element dictionaries.

• Review/update infori_tion about tasks, sub-tasks, or

jobs.

• Review/Update sc_edule/budget/owrall information about

a project.

• Enter new data or programs.

• Edit contents o Z a data base.

• Transfer data, _Ms/GMs from one area to another.

• Link OMs together for execution.

In addition to the command functions described in this

requirement, IPAD shall provide a set of '_rompting" displays that

are callable from the IPAD command language. (See requirement 5.)

ABSTRAL_f OF THE ACCEPTANCE CRITERIA

_hese commands will be tested with the passive commands

(requirement 5} in conjunction with other tests. A test procedure

will be developed to assure that all commands (executive level and

subordinate language) are tested.

ODnsiderations for testing include:

-23-

REV. B
a)

b)

c)

d)

e)

Commands function properly.

Mnemonics are suitable.

AbDreviations are suitable.

Language is consistent.

Defaults are most commonly used cases.

Parameters are easy to use & remember.

Language usage is consistent with documentation.

REV. B

-24-
RE QUIR_MENT 5 USER AIDS

SOHRCE I ._/2.4 .I .I

DESCRIPTION

1PAD will provide a number of aids ro assist the user in the

use of IPAD to accomplish hls product design task. The user shall

De able to request help to receive an overview of the capabilities

available to him in the IPAD system. At any time, the user shall

be =ble to request an overview of the IPAD commands currently

available. The overviews will include a textual description of

the capabilities of each command and a menu of choices to permit

the user to request additional information. The user shall also

be able to request an explanation of any command currently

avdilaDle to him to receive a textual description of the function

of t_e command and an explanation of the syntax of that command.

The user will also be prompted by IPAD in the entry of his

requests.

The engineering user shall be able to use these user aids to

be guided to the correct procedure, data, and programs which he

needs to perform the design function.

When a command is changed, deleted, or added, notification

will De sent to the syste1_s administrator if the required

accompanying explanation _s not been updated.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The user aids will be tested throughout the testing period in

conjunction with other requirement testing. All user aid

capabilities will be tested.

The considerations that will be tested are:

a) User acceptability

b) C_mQand explanations and overviews can be created by the

system administrator and can beacessed by all IPAD

users

c) Co,maand explanations or overviews for a user program can

be created and requested by users of that task

-25-

REV. B
d} Command explanations and overviews function correctly.

REV. B

-26-
_QUIRE_NT 6 COb_D LANGUAGE

SOURCE SOW/5 .Z .2

DESCRIPTION

The com_nd language shall be easy for the engineering user

to understand and use. The commands shall appear to the user to

be independent of the hOSt computer, except in those cases where

it may be necessary or desiraDle to allow an IPAD user to have

direct access to host commands.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A user opinion survey will be used to evaluate all active and

passive con_aands considering usefulness, clarity, ease of use and

adequacy. Test parameters will include a variety of user skill

levels and batch and interactive modes on mDre than one host

computer to verizy host independence.

REV. B

-27-
REQUIREMENT 7 AL_ESS TO HOST O/S FUNCTIONS

SOURCE SOW/5.2.2, 1.4/3.5.2, 1.4/3.3.1

DESCRIPTION

The host operating system capabilities shall be accessible

irom IPAD.

ABSTRACT OF THE A%_EPTANCE CRITERIA

A subset of functions of the host operating system will be

selected and used from within IPAD. It will be established that

the f_ictions are available and operate correctly and that they

can be intermixed with the IPAD functions. Furt/lermore, a

subje_cive user opinion will be established as to the ease of use

or _ost operating system features.

-28-

REV. B
REQGI REMENT 8 COMMAND PROMPTS

SOUkCE SOW/5.2.2, I. _/3.3. I

DESCRIPTION

IPAD shall interpret or translate commands into appropriate

operating system _unctions, possibly initiating or/let IPAD

sor tware.

IPAD shall provide co_nd decoding, provide error

diagnostacs for syntactically ill-formed conumands, provide warning

messages rot semantically suspicious commands, accept abbreviated

co_mnands, supply default parameters, and provide lists of

alternate parameters and their descriptions on request from the

user.

ABSTRACT OF THE ACCEPTANCE CRITERIA

T_e IPAD command language decoding and display capability

will De tested in conjunction with other acceptance te_cs and

should verify that:

a) IPAD commands function correctly;

b) Abbreviated commands are accepted;

c) Warning messages are appropriate;

d) IPAD will provide lists of alternate para_neters and

their descriptions upon request;

e) Default parameters are provided for each command.

User acceptunce and operational correctness will be the

princi_l evaluation criteria.

REV. B

-29-
REQUIREMENT 9 USER ACCESS CONTROL

SOUkCL I .4/2 .8 .2

DESCRIPTION

IPAD shall provide a manager or person in authority the

ability to restrict the set of commands available to an individual

user. The default s_all De that all commands except those

reserved for the system administrator are permitted.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The capability to restrict a set of commands available to an

individual user will De tested wit/l the £ollowing procedure:

a) T_le set of commands to be restricted will be tested both

as restricted and unrestricted.

b) The default will be tested to verify t/tat all commands

are available to t_e individual except those reserved

for the system administrator.

c) Verlfy that the syst_a administxator can access reserved

system commands but t_at the unprivileged user cannot

access these commands.

A user opinion survey will evaluate this capability based

upon user acceptance and operational correctness.

REV. B

-30-
REQUIREMENT 10 EXIT _E PORTS

SOURCE 1 .4/2 .6

DESCRIPTION

The co_and "EXIT" will cause the user to log-off the system

preceded oy a resources report on the current session. Two

reports are available:

EXIT alone will invoke a summary report on the resources used

during the current session and will consist of total resouces

used (CU's and dollars}, total Dudgeted to the user and total

remaining.

EXIT, R will invoke a more detalled resources summary as

described in Requirement 52, type 1.

ABSTRACT OF THE ACL_PTAI_CE CRITERIA

During the execution o_ other acceptance tests users will use

EXIT and EXIT, R. The appropriate resource reports will be

checked for accuracy, completeness and acceptability to the users.

REV. B

-31-
i. I. I .2 Query Language (s)

A special query language shall be provided for accessing

inZor,_ation in the IPAD _ata bases. Queries may be initiated by

engineers, managers or supportlng sta£_.

REV. B

-32-
I%EQU_NT ] I QUERY LANG_GE

SOURC_ SOW/5 .2. I .3, 1.3/4.5.1

DESCRIPTION

Access to data element values shall be through an interactive

query language. The query language shall support logical requests

wz_ch include arithmetic operations and refer to any data element.

The result of a query may be a single value or a list of values o_

one or more elements. Results of one query may be referenced in

another query. Queries may De restricted to user designated data

areas on data sets. The query language shall also be usable trom

wlr_hin an operational module running either in batch or

interactive mode.

ABSTRAL_ OF THE AC_EP_NCE CRITERIA

A user opinion survey will evaluate the interactive query

l_nguage based upon user acceptability and operational

correctness. Users will request data elements, both directly and

in batch or interactive user programs.

_3%e tests should include arithmetic operations on data

_l_aents _nd queries which result in s_ngle values or lists of

values. There s_ould De a test in which the results of one query

are referenced in another query. It should also be verified that

queries can be restricted to a specific data set or a specific

d_ta area.

REVo B

-33-
REQUIRIMENT 12 HEADER DATA QUERY

SOURCE I. 3/3.2.2.1, I. 4/2.5.2

DESCRIPTION

IPAD shall provide the capability to query data set header on

any information contained in t/,e data set header. (See

requirements 60.)

ABSTRACT OF THE ACCEPTANCE CRITERIA

Users will test the capability to query header da£a by

requesting status in±ormation about data sets and by requesting

l_sts of data sets based upon different elements of the header

information such as owner, data set, type, location, etc.

Mequests should include queries on user supplied header

_lIor_tion. Evaluation will be based upon user acceptance and

operational correctness.

REV. B

-34-
R_.QUIRI:MENT 13 MANAGEMENT QUERY LANGUI_E

SOUI<CE BCAC-NASA

DESCRIPT ION

A management query language, which may be part of the IPAD

query language, shall permit interrogation of official project

data.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A stdndard project will be deiined. Each of • testors will

develop individual questions and actions to do and then use the

query language to carry out these on their own version of the

project aata. Three out of four of the persons who conduct the

test must classify hot/% the language capabilities and ease of use

as acceptable.

REV. B

-35-
2. I .2 User Tools

An assortment ot user tools will be available to all IPAD

users--managers, engineers and supporting staff. The tools will

De available interactively and in batch mode. The number and

types of tools made availaDle will change as the needs of the IPAD

user evolves. (See figure 2.1.2-I.)

IPAD will provide tools to enable the user to:

• edit and update stored data, computer programs and text

documents ;

• generate reports using information from the IPAD

Information BanX ;

• _acilitate communication between IPAD users by providing

utilities to build iD_formation menus, organization lists

and mailing lists and enabling a user to transmit

messages to other IPAD users;

• maintain _nd query references to IPAD documents and

procedures ;

• evaluate computing system pertormance;

• help the user waen he requests assistance;

• debug computer programs ; and

• construct commdnd sequences

REV. B

-3b-
I--

Z

re'-

ILl

.-m,

0

n

.--.11

...I

ILL

i

I--

I---

--.J Z

,'--, 0

I--- ,--,

I-- z I---

,.--, 0 _

,--., >,- I-- ,---, r',

I--- I'-- _ .._.1

.-J _ I._ I---

Z _--_ t__ _D Z

0 I-- O0 _-_

_ _ I.I-I _ Z

---I r_ Z C-) (--_ LLJ

I-- (/) I--- l.J- _ C_

Z _ r_ I-_ LI-I

eE

0

v

I--

I1/

!

_d

*rREV.B

-37-
_QUI_ENT 14 UTILITY PROGRAMS

SOURCE I. _/3.3, SOW/5.2.3

DESCRIPTION

Utilities must provide a machine independent interface and

sh_ll be dccessible from both interactive and batch mode_ of

operation. The set of IPAD utility functions must be open ended.

ABSTRACT OF THE _CCEPTANCE CRITERIA

Utillties will be use_ in both batch and interactive modes to

check thelr availdbility. The user will provide a new utility to

check the open ended requirement. Both oZ these features will be

checked wit_ tae s_se utility.

REV. B

-38-
REQUIREMENT 15 EDIT UTILITY

SOURCE SOW/5.2.3, I. 4/3.3. q, SOW/5. I. 8

DESCRIPTION

_eneral text editing and update capabilities shall be

provided to perform t_e following functions:

a) The editor shall permit on-line development of programs

or data Dy entering alphanumeric text from the

intera_cive console.

b} The editor shall pennit changes to source modules (SM)

or data by adding, altering or deleting statements. A

chronological record of changes shall be kept

automatlcally at tae user's option.

c_ The edltor should allow the user to selectively display

part or all of the cnlrrent data set as well as data

identified Dy the editor in respu_se to the current

command.

ABSTRACT OF THE ACCEPTANC[.: CRITERIA

The text editor will be checked by several users of the

various s_ill levels. This can De accomplished in conjunction

wlt_l ot_er tests.

The capability will De checked by:

a) _ntering alphanumeric text at the terminal ;

b) Revision of the text (change, add, delete) at the

terminal ;

c) Display the current data or other data in t_e data set

at the user's option; and

d) Maintain a chronological record of the changes made to

the data (this option will he selected).

REV. B

-39-
These will be tested Zor accuracy, responsiveness and ease of

operation.

REV. B

-_0-
REQUIREMENT 1 6 DOCUMENTATION UTILITY

SOURCE I ._/2.5. _, I. _/2.7.4

DESCRIPTION

1PAD shall provide a complete capability to enter, maintain

and print documents. The following featuzes are minimum

requirem, ents -o

1. Source data entry online at terminal.

o Data available immediately azter input for review and

update (addition_, deletions, revisions).

. Support of rough drafts and finished documents with page

headings, formatting, footnotes, page numbering and

right-margin control.

Automatic table of contents preparation through use of

section and paragraph headings.

. Provision to cmeate a document in subsections and

comDine the subsections to create the tor_l document.

. Search for portion(s) o£ a document based on a search

argument.

D Provlsion for operator developed dictionary to be used

for automatlc spelling checK.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The document preparation and update capability will be tested

Dy having expert operators develop, update and manipulate

documents and by _aving novice operators use the on-line learning

capability. The _ull range of facilities will be tested for

correctness, and ease ot use.

REVo B
RLQUIREMENT 97 REPORTING UTILITY

SOURCE SOW/5.2.3, SOW/5.1.4, 1.4/3.3.8, 1.4/2.5.4

DKSCRIPTION

A report generation capability shall be provided for use in

user requestea, and automatic reporting. This s_all include an

Knglish-liKe display language processor to be used by nonprogrammers to format visudl displays, identify, save, and

retrieve a standard report format both for on-line and batch use.

The report generation capability shall interface with the

IPAD data retrieval capability and with utilities such as the

_ithmetic/logical operation utility (see requirement 95), unit

transformation (see requirement 93), and other applicable

utilities.

ABSTRACT OF THE ACCEPTANC£ CRITERIA

The Report Generation Utility will be testedby several users

Dy creating a report and having it printed both on-line and batch.

During testing, other utilities will De interfaced including data

retrieval, arithmetic/logical operations and unit transformation.

Testing will De for ease of operation and accuracy.

REV. B

-42-
REQUIREMENT 18 MENU BUILDING UTILITY

SOURCE SOW/5.2.3, 1. q/3.3.5

DESCR IPTION

IPAD shall provide aids for building l_nus. Menus are

established during the planning and preparation phases and provide

llats of IPAD commands, computer programs, execution sequences,

data sets, etc. from which t_e user may select.

ABSTRAC_I OF THE ACCEPTANCE CRITERIA

The capability to allow users to build menus will be checked

Dy building menus that will be used for other aspects of the

acceptance tests. _lese menus must be easy to build and function

correctly in the other acceptance tests.

REV. B

-4 3-
R_QUIREMENT 19 ORGANIZATION LEST UTILITY

SOURCE 1. _/3.3 • 18

DLSCRIPTION

IPAD shall provide the means to produce Corporate Like

Organizational Lists (COLIST). These lists shall consist of Group

Names (GNAME), dependent group names (down to any level) and

te_ainating with Individual Named (INAME) members of a group.

Each individual member may have descriptors assigned such as,

Supervisor, Social Security No., Security Classification, Mail

Ztop, Phone No., etc.

In addition to using COLIST Zor organizational display, it

may also be used function_lly. It s_all be possible to use COLIST

as a means o£ indicating the receivers oz messages or creating a

,_iling list.

The use of _y group name when using COLIST functionally

implies that all the i_,dividuals in all the suDordinate groups are

included. At least tl_ following list of Zunctions shall apply to

COLIST.

_iven a GNAME or an It_ME and a DESCRIPTOR NAME, IPAD shall

De able to:

a) Display the INAME and the assigned DESCRIPTOR value or

list the INAMES (Defined by GNAME) and their assigned

descriptor values, e.g., If DESCRIPTOR(S) = MAIL STOP

ORGANIZATION NO., a mailing list will be produced for

everyone _n group GNAME.

b) Compar_ the DESChIPT_R value (s) assigned to INAMES with

a list or s_mllar descriptors assigned to data to

establish a key-locK relationship.

This can De used Zor access permission to classified data

when GNAME(s) and/ or INAME(s) are assigned to data to denote

access authorization.

c) Search and display the INAME(s) within the GNAME (s)

w_ich nave any of the descriptor names assigned.

REVo B
ABSTRACT OF TBE ACCEPTANCE CRITERIA

The organization list capability will be tested by producing

the Corporate Like Organizational Lists (CULISTS). The procedure

wlll follow the description of this requirement and will test the

security access relationship. Messages will be sent to insure

proper functioning (see requirement 20}. _he test will be for

ease ot operation and accuracy.

REVo B

-u,5-
R_2UIREM_NT 20 MAILING LIST UTILITM

SOURCE ]._/2.?

DESCRIPTION

IPAD shall provide the means to construct mailing lists.

Such lists c_l be input d_rectly by a user or constructed by IPAD

from recorded data such as those who have accessed a given data

set, own overdue data, used a specified IPAD utility belonging to

a given organization, etc.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The capability to _llow the user to construct mailing lists

Dy direct input, system construction using recorded data and in

conjunction with the orga,lization lists will be tested. Several

sources for mailing lists will be accessed, such as users of data

sets on record, owners of overdue data, etc. The tests will be

£oz ease of operation and accuracy.

REV. B

-4b-
REQUIKEMENT 21 MESSAGE UTILITY

SOURCE 1._/2.7.2, 1._/3.3.9, SOW/5.1.6

DESC_ IPTI(AN

There are two basic i_ssage types within IPAD.

I. System to User messages

2. User to User messages.

1.0 System to User Messages

There are two categories of system messages:

Messages which originate with the operator or System

Admini strat or

Messages which are sent aut_aatically and are triggered

Dy certain user activity.

1.1 System Administrator Messages

These messages are assigned the following display priorities:

"Authorized User" priority messages. This priority is

available to r/ae System Administrators and operators and

any user who is authorized. These messages will be

automatically dasplayed during the time IPAD is awaiting

input from t/%e recipient in CLP mode.

"System Administrator/Operator- priority messages.

These messages are automatically displayed during the

time IPAD is awaiting input from the recipient in any

user function or the CLP mode.

• System Administrator/Operator emergency messages. These

messages display immediately, interrupting the

recipient.

1.2 Messages Transmitted automatically

These messages are triggered by special user activity which

Jupacts other users and informs them of a change in status. These

messages are stored in the recipienc's message file in the same

manne* _ as user to user x_essages described in Section 2.0.

2.0 User to User Messages

REV. B

-_'/-
2.1 Message Storage

Messages sent from one user to another are stored in the

recipient's message file. T_ere are no limitations on the size of

this fil_.

2._ "Messages Waiting TM Noti£ication

_,en a message is stored but not yet displayed, a prompt (or

indicator) will display that messages are waiting. The prompt

will become increasingly annoying as the number of waiting

messages increases but not to the level that it will disrupt the

t_ntinuit_ of work if the user elects to view his messages later.

2.3 Message Display and Save

When = user elects to display his messages he may save any or

all of the displayed messages. Messages not saved are deleted at

the tez_ntination ot that session.

2.4 Message Read Conii_m_tion

The "sending" user will be able to request automatic

conZlrmation t/%at his message has been displayed. An automatic

conZirmation message will be sent to him when r/_e recipient has

displayed the message.

2.5 Message Accumulation Control

The automatic printing and mailing o_ users messages after a

speci£1c time interval (installation parameter) will be the means

ot controlling the accumulation of unread user messages. After

uxmead user messages have been printed a certain number of times

(installation parameter) they will be deleted. IPAD will not

archive user messages.

2.b Message Priorities

IPAO will provide a user message priority scheme. IPAD will

provide d _ixed number of message priority categories and a using

installation will De able to select its priority message

categories as an _nstallation parameter.

The message priority levels wlLich IPAD will recognize

include:

_tandard User Messages: as described in Section 2.2 with

the constraint that the mmessages waiting" prompt occurs

only when the recipient is in t_e CLP mode.

Priority User Messages: as described in Section 2.2 but

the ,'messages waiting" prompt will be different from the

-48-

REV. B
Standard User message prompt but occurs only when the

recipient is in the CLP mode.

_nergency User Messages: as described in Section 2.2 but

the "messages waiting" prompt will be different from the

Standard and Priority prQmpts and will be displayed _hen

t/le recipient is in any user Zunction.

ABSTRACT UF ACCEPTANCE CRITERIA

The message processing capability shall be checked by

in_uttlng the following message types to a specific user.

• zrom another user with varying message priorities

from the system administrator with varying message

priorities

Zrola the automatic system message capability resulting

from user activity triggered messages.

REV. B

-4,9-
R___UIREMENT 22 DOCL_4ENTREFERENCEUTILITY

SO_CE 1.4/2.4.4

DE SCR IP TI ON

IPAD shall provide the capability to create, update and query

(by keyword) references to documents on standard design and

processing procedures. These references must be identified and

accessible by revision date.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The capability for the user to create, revise and access

li_ts of references to documents on standard design and processing

procedures will De tested. The procedure will be to create and

revise such lists and then access them by keywords and by revision

d_te. Ease of operation and accuracy will De tested.

REV. B

-50-
REQUIREMENT 23 PROGRAM PERFORMANCE MONITORING UTILITY

SOURCE 1.4/3.3.17

DES CR IPT ION

For any IPAD application program, a Zacility shall be

available w_ich can be used to evaluate the program performance.

Thls facility will ,_nitor the execution of such a program and

identity computer resources that are used in selected subsets of

the pzogr am.

ABSTRACT OF THE ACCEPTANCE CRITERIA

T_e application program performance facility will be tested

on at least two application programs with known program

performance. The results of the IPAD monitor will De compared

with the known results.

REV. B

-51 -
REQUIREMENT 2_ LEARNING UTILITY

SOURCE 1 ._/3 .3.16

DESCR IPTION

IPAD shall support a computer based learning utility.

utility shall comprise the following:

This

a) A language whic_z permits an autt_r to prepare, maintain

and improve courseware ;

b) A means for the student to progress tarough the course

materlal at a self controlled pace by means of branching

and immediate error feedback;

c) A means for a teacher to maintain appropriate

surveillance of the community of users of a given

course. The capability to control the use of this

utility shall De provided. The mistakes which the

learner makes while working the sample probl_ns created

to teach IPAD will De recorded. The content and format

of the record will be installation selectable and will

probably contain items such as : course, student,

organization, date, question, and incorrect response.

Tl_ format o£ this record shall be compatible with the

IPAD query Zacllity.

ABSTRACT OF THE AL_EPTANCE CRITERIA

Computer based learning and monitoring of learning activities

will _e tested by developing and using a complete course package.

The author will test the ability to enter material and make

changes to it. Users of various levels of expertise will act as

students to check the tutorial features o1 the utility. Finally a

teacher o£ t_e course wlll check the capability to maintain

survelllance over t_e students to analyze their progress. During

the test, the provision to control access to the utility will be

checked. The capabilities will be tested for correct functioning,

completeness and ease of use.

REV. B

-52-
REQUIREMENT 25 ON-LINE INSTRUCTION UTILITY

SOURCE 1.4/2.2.2, 1.4/2.2.3, 1.4/2.2.1

DESCRIPTION

When t_ user is in the learning mode, he shall have a choice

of available options open to him. The user shall be able to

select from short texts, programmed learning and example problems

available on-line in IPAD.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The tutorial aids will be tested by several users of various

skill levels at the terminal. The options of short texts

{describing IPAD features), program/ued learning and example

problems will De utilized durlng the tests. A user opinion survey

will De conducted to insure the aids are responsive to the users

satisfaction and successfully teach IPAD.

REV. B

-53-
kEQUIREMENT 26 USER ASSISTANCE UTILITY

SOURCE I .4/2 .3 •3

DESCRIPTION

For the novice user the IPAD System shall present a message

at log-on asking if direction is needed. An a_firmative response

should result in the activation of user aids to provide an

overview of IPAD capabilities.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A user designated as "NOVICE" will log-on to IPAD and reply

that direction is required. The user aids will De evaluated for

provlding the user with e_fective instructions for using IPAD.

REV. B

-54-
REQUIHEMENT 27 USER INTERFACE DESCRIPTION UTILITY

SOURCE BCAC-NASA

i%ESCR IPTION

A utility will be provided for creating and interrogating

data sets of text that describe the user oummand interface to IPAD

and to selected user supplied modules and data.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The utility to create and interrogate user commands data sets

will be tested by seve£al users by creating the text for some of

the commands during the acceptance testing and by interrogating

those and existing data sets. The user commands will include IPAD

and s_ne user supplied modules. Testing will be for ease of

operation, responsiveness and accuracy.

R£V. B

-55-
REQUIREMENT 28 PROGRAM DEBUGGING UTILITY

SOURCE 1.4/2.5.2, 1._/3.3.17

DESCRIPTION

IPAD _hall provide on-line debugging aids such as:

• The ability to stop t_e action and then proceed;

• T_e ability to execute stepwise;

• The aDility to determine or change the value of any

program variaDle in any subroutine while the action is

stopped ;

• Tf_ aDility to query and update the information bank

(e.g., values oi elements) while the action is stopped.

ABSq2RAC_D OF THE ACCEPTANCE CRITERIA

The debugging aids will be tested by several users in

conjunction with ot_er acceptance tests while running programs online. The procedure will Zollow the steps outlined:

a)

b)

c)

d)

e)

Stop the action;

Execute the program stepwise;

Determine tf_ value of any program variable;

Dpdate values of elements;

Proceed with tne program.

REV. B

-56-
I'_U IREMENT 29 COMEgdqD S_QUENCE INTERPRETATION UTILITY

SOURCE 3OW/5.2.2, 1.4/2.4.1.2

DESCRIPTION

IPAD shall provide means for automatic interpretation of

sequences of operations to be performed using IPAD. The user

shall have the aDility to construct command sequence files either

through the normal text editing features oZ the system or by

requesting IPAD to save a sequence of commands from a work

sessiun. The command sequences shall be "macro-like" in the

user "s aDility to allow _or operand substitution by run time

parameters. IPAD s_all have the capability to interrupt a

sequence to alert the user to unexpected conditions, e.g., input

_ile not available, abnormal termination of a program, etc. IPAD

shall have the c_paDility to supply automatically the default

intermediate requests to LPIP for retrieving or saving files to

pezmit continuity of a user defined coa_nand sequence.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Command sequences will be created, e_cuted and the results

checked according to t_e following procedure.

a) Create and execute cosunand sequence data by saving user

commands °

D) Modify and execute conunand sequence data created in a).

c) Create and execute coaunand sequence data identical to a)

by use of the text editor.

d) Modify and execute command sequence data created in c)

to make it identical to b).

Both parametric and non-parametric commands will be tested

and must work correctly.

REV. B

-5"/-
2.1.3 User Access

This section presents the requirements that concern the user

access in the areas of _de of access, priority of access, and

user security and identification.

Speci£ied under mode of access are the type of access of

_,teractive (interactive batch, etc), the type of terminals, job

interrupt, checkpoint/restart, and real time message capabilities.

Four different capabilities o2 user priority are recognized.

The purpose of t_e different categories is to keep an adequate

_ccess and response time zor the majority of the users.

Security is provided for the individual user by the use of

password identification and user classification. (See figure

2.1.3-1.)

2.1.3.1 Mode

There are a variety o£ modes availaDle to the IPAD user for

interfacing with the IPAD system. He may interZace via an

interactive terminal, batch control cards or by initiating user

pzogr_s that issue commands or calls for IPAD capabilities.

Interactive work may be done eltner by textual or graphical

terminals. Batch jobs _y be submitted remotely via a satellite

computer.

Batch or interactive jobs may be interrupted to review

intermediate results or oDtain help. Execution may then be

resumed or aborted. Batch jobs may be submitted from interactive

ter_d nal s.

A checkpoint/restart capability may be applied to any job

running under IPAD. Parameters, tot controlling when checkpoints

_re taken, will be controlled by the user.

_e user may elect to _have real time messages sent to all

i_teractive terminals or to have data yield by multiple terminals

simultaneously.

REV. B

-58-
m

!

¢I)

I--

Z

-=-s

0

LzJ

Or=

.-I

._J

I.L

Q

GO

Z

Zo

i,i (__

L_

Z 0

C'J _" L._ W W

L_

*rm..

t.)

(.)

!

t_

*m.m.

L_.

REV. B

-59-
REQUIREMENT 30 INTERACTIVE, BATCH, AND PROGRAM COM_4ANDS

SOURCE SOW/5 .2 .2

DESCRIPTION

The user shall have r/le ability to communicate with IPAD

through interactive termlnal commands, batch control cards, or

co,_ands or calls from user programs in execution under IPAD

control. The format of the commands shall be compatible in these

three ImDdes wherever possible.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A set of three tests will be used to evaluate the three modes

ot IPAD communication for all IPAD commands. The commands must De

availdDle and operational in all three modes of communication, and

will be evaluated for format compatibility between the three

mode s :

a) All IPAD commands will be tested using an interactive

terminal;

b) All IPAD commands will be tested using batch control

cards (submitted over the counter and RJE) ;

c) All IPAD commands will be tested using calls in programs

executing under IPAD control.

REV. B

-60-
PJ_QU IREMENT 31 INT_tACTI VE TERMINALS

SUGRCE SOW/5.1.1, 1.3/3.3.6, 1._/3.5.3

DESCRIPTI ON

IPAD shall accommodate interactive terminals as primary user

Interface. Communicatic_ rates shall De limited only by hardware

factors unless stated as a part of the system design. The design

shall not preclude advances in terminal technology.

ABSTRACT OF THE ACCEPTANCE CRITERIA

T_e ability of t/le IPAD system to facilitate textual and

graphic (storage and rezreshed) interactive terminals as the

primary user interface will De tested _or ease of use by systems

programmers while building software interfaces for the devices

lasted in requir_uent 122.

Communication rates on these devices will also be tested to

ensure that the only limitatiQns are due to hardware. If

limitations are discovered, the system design must so state.

REV. B

-(ol-
R_QDIREMKNT 32 SATELLITE COMPUTEE SUPPORT

SODRCE I .3/3 .3.2

DESC_ IPTI ON

IPAD jobs may De executed in whole or in part on a satellite

cos_uter (a remote system). These jobs must be recognized and

supported by the IPAD System.

ABSTRACT OF THE ACC_:PTANCK CRITERIA

Test _he capdbility of IPAD to support a distributed

computzng network in the _ollowing tests:

Run jobs on the IP_D host which are executed in part on a

satellite computer ;

Kun 3obs on a satellite computer IPAD which are executed in

part on the IPAD _ost.

REV. B

-62-
_EQUIREMEN T 33 INTERRUPT AND RESUME CAPABILITY

SOURCE SOW/5.1.11, SOW/5.3.1, 1._/2.1.3, 1._/2._.2

D_SCR IPTXON

T_,e user must have the capability to interrupt his

interactive terminal session at any point for the following

reasons:

4)

b)

c)

d)

Quit and cancel results of current session;

Interrupt and resume at a later time;

Interrupt execution and review results to that time;

Interrupt execution and obtain _LP.

_BSTRAC_ OF THE ACCEPTANCE CRITERIA

The interrupt, termination, and restart capabilities of IPAD

will De tested 1/1 an interactive terminal session. A special

s_mple of input data will be specified. Tests should include :

I. Quit and cancel results of current session.

a) The user will interrupt and purge all data sets

generated in the current work session.

b) The user will interrupt and purge at least one data set

generated in the current work session.

2. Interrupt and resume at a later time.

3. Interrupt execution and review results to that point.

W. /nterrupt execution and request HELP then restart execution.

REV. B

-63-
Bd/QUIREFIENT 34 BILTCH JOB PROCF_SING

SOUkCE SOW/5.1.12, SOW/5.3.1, 1._12.4.3, 1._/2.5.3, 1.413.5.3,

1._/3.3.6, 1.3/3.3.6

DESCRIPT I ON

IP_ s_ll permit su_ttal o_ a comput_%g job for batch

processing from an interactive teminal, or through nozlnal batch

suDmit_l. It shall be possible to moni_r progress and to

interrupt a Datch exec_ti_ for the follow_g reasons:

d) Review inter_diate results, and

b) Abort the 3oD.

When _n _teractive job is switched to batch processing, the

system will suspend the jc_ when it is coa_plete or when user input

is required. The user wlll be able to restart the job at the

_x)int of suspension.

The _er shall also nave the capability to tr_u_sfer a batch

]oh to interactiwe processing.

_BST_uiCT OF THE ACCEPTAS_E CRIT_IA

Tests of Datch subnlittal in IPA/) will _ c_ducted to verify

the following :

- A batch job my _ submitted from an interactive

terminal;

• A batch j_ may _ submitted using "over the counter" or

RJE procedures;

• A batch joo in execution _y De traulsferred to

interactive processing ;

• A batch job in execution _y be J_%terz_/pted;

• A suspended batc/l job may be restarted at the poiJ%t of

suspension.

REV. B
The tests will include a mix o_ batch jobs, requiring data

from various sources as de/ined in t_e sample test input data.

REV. B

-65-
R_QUIRg/_ENT 35 CHECq<POINT AND RESTART CAPABILITY

SUURCE BCAC-NASA

DESCR IFr I ON

A checKpoint/restart capability shall be available for jobs

running under IPAD control. Checkpoints shall be user selectable

in terms oi elapsed time, resources consumed or events.

AB-_RACT OF THE ACCEPTANCE CRITERIA

Test the checkpoint/restart capability for operational

correctness in both batc/l and interactive modes. A special sample

oZ test input data will De supplied. The capability to establish

a checkpoint and to restart a job successfully from the specified

checkpoint will be tested under each o£ _ following conditions:

I. a user established checkpoint based on elapsed time;

. A user established checkpoint based on computer

resources consumed, including memory, number of data

accesses, etc. for each resource parameter whic_ may be

controlled Dy users ;

. A user estaDlasned checkpoint based on a specific

"event", £or example, completion of a sequence of

operatlons, or excessive use of a resource.

REV. B

-66-
kEQHIREMENT 36 CONFERENCE VIEWING OF DATA

SOURCE I ._/2 . 7 .3

DESCRIPTION

IPAD shall provide the means for multiple or conference

viewing ot data. T_is requires concurrent display of data at more

than one terminal. In addition, IPAD shall provide the means to

send real time messages a,_ to edit the data being viewed by all

the members of the conference.

ABS_ACT OF THE ACCEPTANCE CRITERIA

The following tb_ree "conference mode u capabilities of IPAD

will be tested using two, five, and ten terminals:

The tests should verlfy that both alphanumeric and graphical

data will display concurrently on all terminals in conference

mode.

There will be a test to ensure that users at any terminal in

conference mode are able to edit data. It must be verified that

no two terminal users can simultaneously edit the data being

vlewe_.

A test will verity that a message input from any terminal is

displdyed correctly on all terminals in conference mode.

REV. B

-67-
2.1.3 ._ Priority

Four different categories of user priority will be

recognlzed: standard, appointment, short duration, and emergency.

The standard user's access time and turnaround time is dependent

upon system load. The purpose of t_e appointment category is to

gave a user an opportunity, through the use ot appointments, to

run in a semiprivileged state. An appointment user has fast

access to the system and cannot be put in a wait queue when the

system gets overloaded. Short duration users are privileged in

access and response time but limited in hook-up duration and

restricted in actlvities. An emergency user has to 9 priority over

all ot/,er categories of users.

A quantity called t_e Standard Limiting Response Time (SLMT)

will De used to insure that system response time for all users

including rd%e emergency, snort duration and appointment use is

always within the prescriDed limits.

REV. B

-68-
REqUIrEMENT 37 USER PRIORITIES

SOURC _: 1 .q/2.3.1

DESCR IPTI ON

•he IPAD Zystem shall recognize the following categories of

user:

• Emergency

• Short Duration

• Appointment

• Ztandazd

The Emergency User shall be recognized by the IPAD System to

have the following capabilities:

a) He will _ave i/mnediate access to the system.

D) T_e control procedures for obtaining an emergency

priority will be left to the IPAD system administrator.

c) He will have top priority over all other categories of

user during job execution.

d) He Will be penalized with a premium charge.

The Snort Duration (SD} user will be recognized by the system

to _ave the following capabilities and restrictions:

a) He shall be able to access the computer with a minimum

frustration from communication overload. The following

criteria shall apply: 95_ of the SD users' attempts to

establish a communication link with IPAD shall be

successful within 10 seconds ot completing the mechanics

of establishing c_muunication, i.e., finish dialing.

The system design should consider the following

possibilities :

(I) Some nardwired terminals with direct communication

to IPAD; these terminals would be dedicated SD user

terminals; or

REV. B

-bg-
(2) If normal telephone lines are used some kind of

_lold device which will accept user calls and process

them in the order received, but with sufficient lines to

meet the 95_-10 seconds criteria specified above.

The SD user s_all be restricted to a fixed hook up

duration. This duration shall be adjustable to suit

individual company needs. The range should address 0-30

minutes if system design requires the range to be set.

The SD user shall be restrlcted in activity so that he

,nay not perzorm functions which would affect the

integrity of information in the information bank in the

event that the time limit was reached before the user

had completed has task (e.g., any kind of editing task).

c) The system admi_Listrator shall be able to establish the

functions available to an SD user. For example:

(I) Determine the status of things:

System load (holding queue status)

Chec_ on 3oh status or resources

_eview and query data in information Dank

(2) Make, cnange or cancel an appointment

(31 Receive and send messages

(_} Abort a batch job

d) In the event t_at the SD user reaches his time limit he

shall be unconditionally logged off.

T_e Appointment user shall be recognized by the IPAD System

to nave t/le following capabilities and restrictions.

a) The Appointl_nt user is defined as a user who has

requested and been granted, by the IPAD System, a

speclf_ed work period or periods in IPAD for a defined

date.

b) The IPAD System shall me designed to recognize a daily

cycle o£ appolntments. The cycle shall oonsist of an

app01ntment starting time (S) and a given number of

appointment periods (N) each having a duration time of T

ndnutes, where S, N and T may be selected by the company

using the system and should have the following range ot

values, 0 _< S _< 1_0 minutes, 3 __ N _< 288, and 5 _< T

minutes _< 480 (where T is in increments of 5 minutes).

The condition that T%N >_ (14_0-S) must also be satisfied.

REV. B

-70-
c) The system shall be designed so that a company can

remove t/le appointment capability if it so desires.

d) The IP_D System shall be designed to limit the number of

users who can make appointments in an appointment

period.

e) A user may make appointments for himself or others from

the COMMAND mode. _hen making or changing an

appointment the user may enter the date for which he

requires the appointment and the system will display to

him the appointment periods (in hours and minutes) still

available to ilim. He then selects an appointment

period.

Each IPAD user (as deZined Dy the permission codes)

shall be limited in the number of appointment periods he

may use in any £our week period. The number of

appointment p_riods and the specific four week cycle

dates are flexible and may be selected to suit

individual company requirements.

g) user can request an appointment up to D days ahead ot

tae appointment date and may change or cancel that

appointment up to H burs ahead of the appointment time

without forZelt of his allotted appointment periods.

Where 0 <_ D <_ 28 and 0 _< H _< 48 may De selected by the

using company.

h)

±)

An appointment user must use _is appointment during the

time the appointment period is in force or his

appointment will be dropped _rom the system and he will

forfeit his allotted appointment period.

An appointment user is not restricted in the manner in

whlch he elects to make his allotted appointment

periods. He ,my make them singly or any number in

series up to the maximum allowed. He must designate the

numDer of periods he requires when he makes his

appointment.

J) The appointment user shall De able to access the

computer suDject to the tollowing criteria.

95_ of t_e attempts to communicate with IPAD by an

appoln_nent user shall be successful within 10 seconds

of dialing. The system design should consider the

following pos sibilities :

(I) Some hardwired terminals with direct communication

to IPAD. These terminals would be dedicated

(appointment user terminals).

REV. B

-71-
{2) If normal telephone lines are used the system shall

be designed to reserve sufficient lines during each

appointment period to accommodate the number of

appointment reservations.

K) If the appointment user has not completed his task by

the end of t_e requested appointment period (s) the

system will take the following steps.

(1) The system will enforce a normal INTERRUPT.

(2) The system will check and list the appointment

periods available for the rest of that day and inform

the user. The user may then elect to:

• Ta_e a new appointment, and if it runs concurrently,

continue with his work.

• IS ne has a joD in execution he may transfer to a

batch job.

• Request standard user category if resources are

availaDie.

• Log-off the system.

The Standard user shall be recognized by the IPAD System to

_ve the zollowing capabilities and restrictions.

d) The Standard user has no special privileges. If all the

communication lines are occupied he has no recourse but

to keep dialing. He can check on the system load

through SD capability and decide on his next course of

action.

b) In t_e event of system overload he will be unable to

co1_ence his task even though Be is able to communicate

with the system. He will be held in a waiting queue

until t_e system response level permits him to use the

sys tern.

c} During the period in which a Standard user is held in

the waitixg queue he will be informed on a regular basis

of his position in t_ queue and will be able to make an

appointment or log-oft.

ABSTRACT OF THE ACCEPTANCE CRITERIA

REV. B

-72-
The IPAD user categories-- access considerations will be

tested with the procedures summarized below:

General

A user in each or the four categories will attempt to access

IPAD. The results and the IPAD responses will be compared to

verity _at IPAD recognizes the four categories of user. A user

opinion survey will evaluate IPAD access Zor each category.

Emergency Users

T_e emergency user's access to IPAD smDuld be tested and

evaludted:

Verity that the emergency user has "immediate" access to

the system.

Check the accounting for the session to demonstrate that

the emergency user pays a premium charge.

Test that the system administrator can assign emergency

status.

Compare a mix of jobs from different user categories to

verity that the emergency job has priority.

Short Duration

The Short Duration user's access to IPAD should be tested and

evaluated :

1,000 attempts to access £PAD as a short duration user

should be made. At least 950 attempts must be

successful withln 10 seconds after completing the

mechanlcs of establishing conuuunlcation.

An SD user should exceed his duration to verify that he

will be unconditionally logged oft.

Check that the short duration parameter maybe varied by

company installation. Test several different values,

including the range boundaries of 0. and 30. Also, test

inwaliu val_es.

An SD user shoul_ attempt to edit and update datasets,

to execute a 3oh, and to perform other functions which

might aif ect the information baud. These operations

should not De allowed.

Verify that the SD user is able to perform the functions

specified for him in this requirement.

-73-

REV. B
• Test that the system administrator is able to establish

or restrict the functions available to the SD user.

Appointment Jsers

The appointment user's access to IPAD should be tested and

eva luated :

• Several appointments should be made for defined dates.

It should be verified that this user is able to access

IPAD during these appointments, and that other users are

not aDle to use these appointments.

. Check that all appointment parameters specified in this

requirement may be set or modified by each company.

Verify that these parameters must satisfy conditions in

the requirements.

. Test the IPAD access scheme without the optional

appointment capability.

• Specify a limit of 5 users for each appointment period,

and verify that the sixth user will be unsuccessful in

making an appointment.

• Users should test the following:

a) Change t_e time and/or date of an appointment.

b) Cancel an appointment.

c) Make appointments for other users.

d) Change/ca,_el appointments Zor other users.

e} Specify date and select appointments from

displayed choices.

• Specify a "company w. limit oZ 20 appointments per user

for a four week peraod, and verify that a user cannot

exceed this number.

• Veri£y that a user can cancel or change an appointment

if the numDer oZ hours notice limitation is met.

• Verify that a user forfeits his appointment if he

attempts to c_ange or cancel it after the nil" limit is

passed.

• Check that the user cannot make an appointment

insufficiently far in advance.

REV. B

-7_-
A user should make an appointment and fail to keep it

without cancelling. The appointment should be dropped

from t_e system.

500 attempts s_ould be made to access IPAD with au,

appointment. Of these, at least _75 attempts should be

successful to meet the 95_ requirement.

Continue to use IPAD beyond the allocated appointment

time to evaluate the options under IPAD. Test the

followlng :

a. Wit_ a light appointment load, verify that the user

may make an immediate appointment and continue his work.

D. With a incapacity- appointment load, the user's

attempt to make an immediate appointment should fail.

c. Make an appointment for later in the day.

d. When a user's job is executing at the time his

appointment runs out, transfer the job to a batch job.

e. When suft_cient resources are available to permit

standard users, verify that the user can continue as a

"standard" user.

f. When suZficient resources are not available to

permit standard users, veri_y that the user cannot

continue as a standard user. Check that the user can

log off.

Standard Users

The standard user's access to IPAD shall be tested and

evaluated:

Verify that the standard user has no special privileges

and that in a competition for resources, other users

_ave priority over the standard user.

In a test to si,mulate system overload, verify that the

standard user can cQmnunicate with IPAD as he is held in

a wa_t queue. Verify that the user is informed of queue

position and that he can make an appointment or log off.

Veri_y that the standard user can use IPAD once the

system load is reduced.

REV. B

-75-
_EQUIREMENT 38 STANDARD LIMITING RESPONSE TIME

SOURCE 1.4/2.3.1, 1.3/3.3.5.3

DESCRIPTION

The system shall recognize a quantity called STANDARD

LIMITING RESPONSE TIME (S_RT}. The value and means for computing

the value of SLRT shall be variable and controlled by each

individual company using the system.

The system s_all cQmpute the actual response time (ART) based

on installation par_ueters and take the following action:

a) If ART > S_RT the system will block Standard users from

pezforIRing their task in IPAD and place them in a

waiting queue.

b) If ART < SL_ the system will not block Standard users

from performing their tasks in IPAD and will process

users _n order from the waiting queue. If the queue is

vacant, Standard users may De processed directly.

Privileged users (_mergency, Short Duration and Appointment)

are not affected by SLRT and will be permitted to access the

system without constraint.

The SIA_ shall apply to only the interactive user and shall

have no effect on IPAD jobs that are submitted for batch

processing.

ABSTRACT OF THE ACCEPTANC_ _ITERIA

The Standard Limiting Response Time (SLRT) will be tested by

detlning parameters for measuring response time and loading the

system so that ART > SLRT. A check will De made that standard

users are blocked from performing their task and are placed in a

wait queue. There will De users of the other category to insure

they are not affected by ART and SLRT.

REV. B

-76-
2.1.3.3 User Security and Identification

IPAD must provide security for individual users. This

protection will he provided by employing user passwords. These

passwords must provide unique identification, must be protected

_rom discovery and must be easy to use and modify.

Access to IPAD dat& will De controlled by user

classlfica%ion. Data manipulation will likewise be controlled.

User classifications will be available upun request.

REV. B

-"/7-
REQUIREMENT 39 USER IDENTIFICATION

SOURCE I .4/2 .3.2

DESCi%IPTION

The IPAD system shall determine the authority of a user to

access IPAD through t_e use of an identification sequence which

shall include user identification, password, security

classification, an_ project i_entification.

Identification in r/%is context establishes user personal

identification and the discipline or group to which the user is

assigned. A password or other means of verification is required

to protect the person being identified from impers_ation.

ABSTRACT OF THE ACCEPTANCE CRITERIA

User access to IPAD will be tested to identify satisfactory

operation for both interactive and batch modes. Tests will

include both valid and invalid user identification. User access

to IPAD wall be tested for user acceptance. Users with various

levels of computing skills will access the IPAD system and remote

IPAD system and will input unique ID and applicable user ID

verification. A user survey will be conducted for ease of use and

adequ a_.

REV. B

-78-
_QUIREMENT 40 UNACCEPTABLE USER IDENTIFICATION

SOURCE 1-_/2.3.2

DESCR IPTION

The system shall recognize unacceptable identification and

indicate to the user the source of the inaccuracy and subsequently

permit hl_ to re-enter t_e identification data. After x such

attempts (where x is an installation parameter} without successful

accepEance of the identification data, the user will be terminated

from IPAD after D_ing Zorewarned prior to the last attempt. Any

termination immediately following an unsuccessful access attempt

shall be recorded and made available to the system administrator.

ABSTMACT OF THE ACCEPTANCE CRITERIA

Users will attempt to log on with improper user IDs and

p_sswords. A check will De made that users are allowed 3

attempts; that users are forewarned after two attempts and that

records of unsuccessful access attempts are only available to the

system administrator.

REV. B

-79-
P_EQUIB_24ENT _ I PASSWORD PROTECTION

SOURCE 1 .4/2 •3.2

DESC_ IPTI ON

The password shall De protected from discovery as a result of

its normal use.

ABSTRACT OF THE ACCEPTANCE CRITERIA

ChecKs will be made to insure the password will not be

disclosed through its normal use. These will include a check to

make sure the password is not displayed on the terminal or on

batc_ printout. A check will also be made to insure that a nonauthorized user cannot access any records of user passwords.

REV. B

-80-
KEQUIKEMENT 42 PASSW0_D CONTROL

SOpkCE I. _/2.3.2

DKSCRIPTION

The establishment and subsequent changes to the password

shall be acoomplisned with a minimum o_ user inconvenience.

_ges may be accomplished by the user.

ABS_CT OF THE ACCEPTANCE CRITERIA

Chec_ the IPAD capability to assign and change user

passwords. A password will be defined for a set of typical users.

Each o£ these users will change their assigned password a minimum

of 5 times while testing ot21er features o± IPAD. Attempts will be

made to illegally access password data.

REV. B

-81-
REQUIREMENT 43 USER CLASSIFICATION DISPLAY

SOURCE I .4/2.5._, I. _/Z. 5.2

DESCRIPTION

The IPAD System shall provide the user on request with a

display of his classifications for accessing and manipulating

data °

ABSTR_C_f OF THE ACCEPTANCE CRITERIA

For various users with a distribution of authorized functions

and data access classifications, a check will be made to insure

correct reporting of these classifications. A check will also be

_de to insure t_at users may use authorized functions and data

accesses while they are prevented from unauthorized activity.

Tests will be for correctness and useability.

REV. B

-82-
P_EQUIKEMEN T W3. I USER ABSENCE AND REASSIGNMENT CONTROL

SOURCE 6.3.8

DESCRIPT ION

It shall be possible to convey to IPAD that a user will be

absent from active participation on the system as follows:

a) User initiated--between defined dates (vacation, trips)

b) Management initiated--after a specified date, for an

indefinite period, for any reason (transfer,

termination, etc.). The manager who will reallocate the

wor_ shall be identified.

Notification of absence a) above, shall result in protection

of the user's working area including automatic deletion

capaDllitites such as deletion ot messages not read within an

allowed time. Messages will De accepted during this period and

sending users will be notified of the intended recipient "s

absence.

The time period allowed between the starting and finishing

date Zor category a) is a system parameter.

Notification of absence b) to the system results in offline

w_rning messages being sent to the manager responsible for the

absent user's work. The message will remind the manager of the

user's termination date and will list the tasMs, subtasks,

suspended joos, data sets and programs for which the terminating

user is responsiDle in order that the manager may reassign them.

The messages will be sent periodically until everything has been

reassigned.

Users who have accessed data or programs owned by the

replaced user will receive automatic messages informing them of

the change in data ownership.

ABSTRACT OF THE ACCEPTANCE CRITERIA

T_e capability of IPAD to track t_e aDsence of users and make

appropriate notification of the absence will be tested by

simulating a series of absences.

REV. B

-83-
2.2 DESIGN SUPPORT AND CONTROLS

A design process is a complex network of engineering,

computational and management activities. LPAD will support the

planning, defining, modifying and reporting ot the design process.

M_u%agement monitoring o£ projects will also be supported.

2. i. I Design Process Support

1PAD will support engineering and management in planning,

detlning, modifying, controlling and integrating engineering

technical processes. Support provided includes the building and

saving of job sequences, the execution and monitoring of jobs,

process reporting and data release control to inform users of data

status. Inlormation to be snared by more than one organization

s_ll be under release control. (See figure 2.2. I-1.)

2.2.1.1 Definition

The ability to plan, define and modiZy an integrated

e_igineering technical process snail be supported by IPAD. The

deslgn process shall serve as the Oasis for data identification,

control of information flow, etc. The processes in turn will be

dssoclated with a speclfic design project.

The building block of a process shall be a job. A job will

involve user input data, execution of user computer programs or

IPAD utilities and a choice of outputs. A job may be processed in

batch, interactive or mlxed mode. Data flow occurs between and

within jobs.

Jobs may be grouped into nierarchial levels. The highest

grouping is defined as a process. The number and designation of

t_ese levels is defined Dy the user. IPAD shall De able to

recognize an unlimited number of processes.

REV. B

-8_-
I-- ZW

:EZ W

C_

Q-

--I

¢:)Q

z0Z

LL.

ILl ZZZZ

Z0

Z0 _---

h- .:_ Z0 0

_- h--

UJ

Z0 UJ

LLJ

GO

Z Ill

_-- ,,l 0

h- ILl LLJ0

_ LL] _.__

0_ _Z_Z0 i,

C_:00 =>- C_:Z

o4

4_

(])

O"

(1)

O_

4o

£. 0

O.

0..

Q.) U0

t-'-

f-_I

£.

::3

.I,-

LL.

REV.B

-85-
REQUIREMENT _ PROCESSES PLANNIN_ AND DEFINITION

SOURC£ 1.3/3.3.1, 1.3/3.3.b, 1.3/3.3.2, 1.3/3.3

DESCR IPTION

The capability to plan, define and modify an integrated

englneering technical process such as the reference design process

described in Db-IPAD-70010-D and its associated data interfaces as

described by the data flow model in section 2.0 of D6-IPAD-70012-D

shall De supported by IPAD. The information contained in such a

process definition shall be used by IPAD £or data identification,

control oZ information £1ow and activities, etc., when such a

process has been made part ot a specific design project.

_,e building Dlock of a process shall be a job. A ,job may

•nvolve user input oZ data, execution ot one or more computer

programs as well as executlon of one or more IPAD utilities or

system functions. A 3oh may De processed in a batch, interactive

or mixed mode. Data £1ow occurs between and within jobs.

Jobs may be grouped and such groups of jobs grouped further

in an _ierarchical fashion to any level. The highest group is

dezined as the process. The number of levels in this hierarchy

and the designation of these levels shall be definable by the

user.

IPAD s_all be aDle to recognize an unlimited number of

processes.

ABSTRAL_ OF THE ACCEPTANCE CRITERIA

The process planning and definition capabilities of IPAD will

De tested Zor adequacy and ease of use by defining to IPAD a

subset of one or more levels of the reference design process

including the data flow. A test should verify that the data flow

model shall result in an accurate data transfer between two jobs

or between a joD and the information Dank.

be capability to identity changes to the process and data

flow de_inlti0ns will be tested to verify t_at IPAD will

_Istinguish between each process or data flow version.

REV. B

-86-
An arbitrary number of processes and data flows will be

defined u,ltil hardware capacity is reached and then tested in a

simulated production environment. Accuracy must not be affected

Dy the quantity oi= defined processes.

REV. B

-87-
2.2.1.2 Preparation of Jobs

IPAD will support rne building and saving of job sequences.

In co,mection with job sequences, IPAD wall provide the means for

collecting data, preparing and verifying input, and setting up and

checking data fluw between programs.

REV. B

-8 8-
REQUI_NT 4 5 JOBS PREPARATION

SOURCE SOW/5.1.9, 1.4/2.5.2, 1.3/5.1.3

DESCRIPTION

IPAD shall provide means for preparing for a job or a group

ot jobs:

This involves :

a) Collecting computer prograuns;

b) Assembling programs into a job sequence;

c) Settin 9 up and checking consistent and compatible data

flow among t_e programs in the job sequence;

d} Collecting data;

e) Preparing and verifying input;

f) Storing job sequence for future use.

These sequences may be deflned in terms of previously defined

sequence s.

ABZTRACT OF THE AL'CEPTANCE CRITERIA

All the IPAD system aids described in this requirement for

preparing 3obs or groups of jobs will be tested by several users

to _etermane if they are operationally correct. The tests will

include defining job sequences in terms ot previously defined job

sequences. A user survey will evaluate these aids for ease of

operation, accuracy, and e/ficiency.

REV. B

-89-
2.2.1.3 Execution and Monitoring of Jobs

The system shall provide t/le means to assist a user in

running a job or sequenoe of jobs within IPAD. Computer program

relerence to data sets, input and output, is controlled by the

user and may be specified by the user on a computer program at

execution time. Information to identify these data sets may be

supplled by the user or by a computer program.

REV. B

-90-
D

_6 JOB EXECUTION AND MONITORING

SOURCE I . _/2 .5.3

DESCRIPTION

The system shall provide t_e means to assist a user in

running a job. In this context, a job may involve more than one

computer program linked in sequence. The following activities are

ex_*_les of activities which shall be available while running a

job:

- Reviewing selected intermediate results

• Reviewing selected final results

ABSTRACT OF THE ACCEPTANCE CRITERIA

Several users will test the IPAD system capabilities to

assist a user in running a job, including:

a) Reviewing selected intermediate results;

b} Reviewing selected final results;

A user survey will evaluate these capabilities based on

operational correctness and ease of use.

REV. B

-91-
REQUIREMENT _7 DYNAMIC REFERENCE TO DATA

SOURCE I .3/4.5.2

DESCRIPTION

IPAD shall permit computer programs to reference data sets in

speciZic aata areas with the user identifying the input and output

d_ta sets to the job or group of jobs at execution time. These

data sets may be identiZied by information supplied either by the

user or the program.

ABSTRACr OF THE AOCEPTANCE CRITERIA

The capability to dynamically reZerex_e input and output data

sets at execution time will be tested by several users

concurrently. The tests will include data set identification

supplied by both the user and user progran_. The capability will

be evaluated zor ease of use and accuracy.

REV. B

-92-
2.2. I °_ Reporting

Design process reports shall be available either through

routine reporting or upon specific request° These reports may

relate information about the design process model, data flow or

technical status of data.

REV. B

-93-
RE_UIREMEN T _8 PROCESS REPORTS

SOURCE BCAC-NASA

DESCRIPT ION

IPAD shall provide for design process reports. These reports

include a display of the design process model or parts thereof

including data flow as well as tecnnical status of the data. It

shall be possible to define these reports as part of the process

itself but they shall also be available to the user at his

specific request.

ABSTRACT OF THE ACCEPTANCE CRITERIA

_lis test will be in two parts. First the ability of IPAD to

d_splay in graphical form the design process definitions will De

tested by defining a multi-level Zairly complex design process and

displaying all and selected parts of the model.

Secondly, a test will be made ot IPAD's ability to report in

graphical or textual torm on status oZ data when the process ha8

been made part of a project. Two aesign processes will be defined

and made part of a project. Simulated progress will be created.

Automatic, user requested, problem, and tecnnical status report_

will be evaluated for correctness.

REV. B

-94-
2.2.1.5 Control of Information

Information to be shared by more t/zan one job or by more than

one organization s_all be under release control. Jobs may use

nun-released data for generating preliminary results, but

resultant data based on non-released information shall be nonreleasable unless the data is approved by the system

administrator.

REV. B

-95-
REQUIREMENT _9 INFORMATION RELEASE

The intent oz r31is requirement is covered by the revised

requirement 8].

REV. B

-96-
2.2.2 Computer Aided Design Project Management

IPAD will support managers in planning, monitoring and

reporting Design Projects. Management computer programs will be

made available for analyzing technical ana management information.

_n indivldual _PAD user will be able to assess the status of his

own su_casK, data, tas_ or the overall project status. In

response to IPAD monitoriilg and reporting, c_trols may be exerted

to limit, terminate or suspend activities. (See figure 2.2.2-I.)

2.2.2.1 Planning

IPAD will support management planning of design project by

assisting a manager in identifying tasks and subtasks, in

scheduling manpower and resource assignment and in relating the

dependency between tasks. IPAD shall support management computer

programs and in the retrieval and display of project technical and

management informdt ion.

REV. B

-97-
I--- ZWW

O-

.-J

.-J

--s

I.L

Z0

0 ._j

LI.I

REV.B

-98-

-I-} U

.r-j, 0

e-

• rU_

a_

r_

IE0!

C_J

_J

_r_

°r--

L_-
REQUIREMENT 50 PROJECT PLANN ING

SOURCE 1._/2.5.1, 1.4/2.5._, 1.3/3.3.3

DESCRIPTION

IPAD shall provide the means whereby managers can plan a

design pro3ect using one or more design processes.

"Plan" in t_is sense includes grouping ot jobs or groups of

lobs into subtasks and su_tas_s into tasks as well as scheduling,

manpower and computer resources assignment to these tasks and

subtas_s. The technical dependency of tasks to each other is

indicated in the design process. To this end the following

requirements apply:

The planner shall be able to define tasks and subtasks

from the selected process (es)

The planner s_ll be able to schedule, by project, tasks

and subtasks and assign names and commit schedule dates

to them.

The system will provide the means to name subtasks and

tasks Dy project to address various levels of planning

and enaDle the planner to assign task and subtask

dependency.

The means to dssign manpower and computer resource

constraints to named tasks and subtasks shall be

availaDle.

aeview of information on scheduling, manpower and

computer resources s_all be available at the terminal or

off-line by display or hardcopy. The input shall

consist of project task or subtask name and a selection

of any combination of schedule, manpower, computer

resources and dependency. The means to select bar chart

or taDular display of infor,mation shall be available.

Bar chart display will have available a standard set of

symbols to denote Key activities. The set of symbols

shall be open ended and will have the purpose of

denoting such activities as:

Start/Complete Project

-99-

REV. B
Complete Key Tasks

Decision Milestone

Begln Milestone

End Milestone

ABSTRACT OF THE ACCEPTANCE CRITERIA

The project planning capability of the IPAD system will be

tested by developing a aesign project with all the attributes

cited in this requirement. The procedure will basically follow

these steps:

a) Dezine tasks and subtasks ;

D)

c)

Schedule the tasks and subtas_s;

Assign manpower and computer resources to tasks and

suDtasks ;

d) Display scheduling, manpower and computer resources at

the terminal or off-line selecting bar chart or tabular

displays ;

e) Use a sta,_ard set of symDols for bar chart display.

REV. B

-100-
kEQUIREMENT 5 1 MANAGEMENT SUPPORT

SOURCE 1.3/3.3.4, 1.3/3.3.5, 1.4/3.3.6, SC_/5.1.14

DESCRIPTION

IPAD shall support management in storage and utilization of

management computer programs such as critical path determination

or cumulative cost distribution, and IPAD shall facilitate

retriewal and display o_ project technlcal and management

information _or reviews of task assignments, work progress,

schedules, au_d resources expended and available.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The ability of the IPAD System to store and utilize

m_agement computer programs will be tested by running a computer

program such as critical path determination or cumulative cost

d_str_ution. The IPAD System must facilitate the execution of

the program and the retrieval and display o_ management

inforn_tion from the program.

REV. B

-101-
2.2.2.2 Monitoring Control and Reporting

Several levels of monitoring and reporting are available

wire,in IPAD. This capability may be used by the IPAD user to

assess the status oZ his own subtasks, to assess the status of

data, tasks or suOtasks within a project or to assess the overall

status of a project. This capability may be used to monitor

resources used versus resources planned or budgeted. In response

to IPAD reporting, controls may be exerted to limit, terminate or

suspend activities. Reports may be generated on a routine basis

or by specific request.

REV. B

-102-
_EQDI_ENT 52 RESOURCEREPORTS

SOURCE 1.4/2.9.4, 1.4/2.5.4, 1.3/3.3.5.2

DESCRIPTION

At anytime in the command mode a user shall be able to

request a report on resources, both computer and manpower by

entering a suitable command such as RESOURCES, p. In addition,

when a user requests EXIT an automatic short report of total CU's

for session will De generated prior to log-off. (See requirement

10.) EXIT, R will present report type 1 described below.

There are two types oZ reports required:

Type 1 Computing resources used during the current session

and the budget/used/remaining for each _btask

worked on.

Type 2 Cumulative s_m_ation of bot/l computing resources

and manpower (extracted from the payroll accounting

system). Reporting basis shall include :

a. Organization

b. Program Item Number

c. Per son

d- Project

Reporting period shall include:

a. Latest Week

b. Latest Month

c. Year to Date

d. Project Start to Date

e. Any arbitrary period based on specified start

and ending dates

T_,e two types of reports are discussed in more detail in the

following sections.

REV. B

-103-
Report Type I, Work done during current session:

User in session report consists of a work item oriented

report relative to the work done during the current session at the

terminal. Only computer resources are required.

Figure 2.2.2.2-I gives an example of the type I automatic

report on resources used following the "EXIT, R # or "RESOURCES"

co_nd.

Report Type 2, S_m_ation Base d Reports:

Summation based reports consist of both manpower and computer

resources relative to individuals and groups of individuals

defined by a project manpower oganization. Figure 2.2.2.2-2 gives

an example of the type 2 automatic report following the

"RESOURCES, S" command. The following describes source of data

i or t_ reporting basis.

Tin manpower organization will be defined to IPAD through the

"COLIST" capability (see requirement 19).

The work item organization will De defined to IPAD through a

WB_ (Work Breakdown Structure} which may be done using

"COLIST- and will also be used to de_ine the type of report

needed.

Work Item based reports consist of resources, both manpower

and computer resources, relative to tasks and subtasks within

a given pro 3ect.

Work item based on an individual's name for a specific

dssigmnent or total assigrunents.

REV. B

-10_-
EXAMPLE OF REPORT TYPE 1

Input

Command=Resources or Exit, R

Output

Work Done by:

CURRENT SESSION RESOURCES REPORT

Time Date

WORK DONE

PROJECT SUB JOB STATUS

TASK

PR I IN -WORK

ST 11 IN-WORK

J111 IN-WORK

Jl12 INTER.

IN-WORK

ST21 COMP.

J21 1 COMP.

PR2

COMPUTER

II

RESOURCES

USED THIS

SESSION

CU 'S

$

TOTAL COMPUTER RESOURCES

i

USED TO BUDGETED REMAINING

DATE

CU'S CU'S CU'S

$ $ $

III I

TOTAL

Figure 2.2.2.2-I, Current Session Resources Report

REV. B

-105-
Example of Report Type 2

Input

Command - Resources PI' P2' P3' P4' P5

Output

P1 " S (Summary Report)

P2 = Reporting Basis

I - Organization (Colist No.)

2 - Program Item Number

P3 = Level of Detail

I

2

3

4

P4 : Reporting Period

3 - Person

4 - Project

Resources Reporting Basis

Time Period to

Request by.

1 - Latest Week

2 - Latest Month

3 - Year to Date

4 - Project Start to Date

5 - Arbitrary Period

Start Date

End Date

Level

of

Detail

AAAA

(Level 4

Subtotal )

AAAB

(Level 4

Subtotal)

AAA

(Level 3

Subtotal)

AAB

(Level 3

Subtotal )

AA

(Level 2

Subtotal)

A

(Level 1

Total)

Item

Manpower

Computing

Total

Manpower

Computing

Total

Manpower

Computing

Total

Manpower

Computing

Total

Manpower

Computing

Total

Manpower

Computing

Total

Units

M/Hrs

$

CU's

$

$

M/Hrs

$

CU's

$

$

M/Hrs

$

CU' s

$

$

M/Hrs

$

CU' s

$

$

M/Hrs

S

CU's

$

$

M/Hrs

$

CU' s

$

$

Used

Figure 2.2.2.2-2

RESOURCES

Budgetted Remaining

Summation Resources Report

REV. B - 106-
ABS_%AL_ OF THE ACCEPTANCE CRITERIA

During IPAD system testing, reports will be requested on

individual computer resources account for current status during

terminal sessions. T_ese will include all the overall accounting

level reports dezined in the requlrement. In addition periodic

reports will be requested and compared to the individual reports.

The status of accounts will be checked independently of terminal

sessions.

REV. B

-107-
RE_U IREMENT 53 SUBTASK M_NITORING

SOURCE 1 .3/3 .3 .6

DESCRIFEION

IPAD shall provide the capability to monitor subtask status

or suDtasKs which hdve been suspended. Status needs include

schedule, number and status of suspended and active jobs, and

resource in£ormation.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The subtask monitoring capability will be tested

conjunction with Req. 55 "Budget Status" and Req. 5_ nRevised Task

Status". Several suDtasKs in various stages o_ activity will be

suspended and reports requested. IPAD should accurately supply

the following:

a) Job Status

• Jobs completed prior to suspension and resources

used for each batch step.

• Jobs in progress at the time of suspension,

resources _or job steps completed.

• Cause or source o_ suspension.

D) SuDtask resource reporting

• Schedule constrains

• Data Sets Created

• Budget/Actual/Remaining

REV. B

-108-
REQUIREMENT 54 SUBTASK MODIFICATIONS

SOURCE 1.3/3.3.5.2, 1.4/2.9.1.1, 1.4/3.3.7

D_ _ IPT ION

IPAD shall provide _acilities to perform the following

_u_ct ion s:

a) Input current status of tasks in progress;

D) Add, delete or alter tasks and subtasks at any time

during working phases o_ the task;

c) Stop a task in progress to be resumed at some time in

the future without loss of work continuity. THis may be

acco,_lished Dy closing off resources for the task and

issuing a message.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The project reporting capability for task and subtask status

wlll be tested in conjunction with requir_nent 55 "Budget Status

Report" and requireme_,t 53 "Subtask Monitoring". A project with a

series of suDtasKs will be set up and run. The ability to input

current status of tasks, add, delete or alter tasks or subtasks

during working phases of the task will be tested and checked by

requesting reports. A task will De stopped by closing off

resources. An appropriate n_ssage should be issued. At a later

date the task will be restarted.

REV. B

-109-
_UIP_ENT 55 P_OJECT RESOURCE MONITORING

SOURCE 1.3/3.3.5.2, 1.3/3.3.5.1

DEZCRIPTION

IPAD must produce a report that compares project resources

used to those budgeted. The report will identify subtasks and

collect accounting in£o_ation for each specified category, such

ds program item number (PIN), which relates to Work Breakdown%

Structure (WBS). IPAD will monitor resources and report all uses

o£ unplanned resources. _esources constuned by each job will be

the responsibility of the user, who will also establish the

appropriate time and resource limits. When the limits are

exceedeQ, any currently running 3obs will be completed and the

system will suspend t/le su_tasK, which will be held for review by

the user. At the appropriate manager's discretion, the subtask

will _e able to restart from the point of suspension.

ABS_CT OF THE ACCEPTANCE CRITERIA

A WBS structure with associated PINs will be created.

Several subtasks will be created and run to various stages of

completlon. Accounting inZormation reports will be requested by

subtask, PIN and job. A subtask will use unplanned resources to

check IPAD's ability to report this use. Low resource lin%its will

be set on a job to check suDtask suspension. (See reql/irement

107-Subtask Monitoring.) SuDtask restart will be attempted with

auld without the appropriate manager, permission. IP_29 nnlst

perZorm correctly throughout these tests,auld the reports will be

checked for ease of use as well.

REV. B

-110-
REQUI.REMKNT 56 PROJECT SCHEDULE MONITORING AND CONTROL

SuURC E 1.3/3.5.4.2, 1.LI,/2.9.1.11, 1.3/3.3.3.3

DESCRIPTION

Projects may be placed under optional schedule control. IPAD

would 1_nitor project planning data and provide reports of status

and impending problems. For example, IPAD would provide the

capability to limit job execution when a job is part of a subtask

riot yet scheduled or or one that has already been completed. IPAD

could also monitor proDect data set occurrences to determine if a

project milestone has been met. When a milestone is missed, IPAD

will report the exception to e_ch affected organization.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Schedule monitoring and the ability of the system to control

schedules will be tested in conjunction with the sample project

plan developed for requirement 50, ACT I. Using the optional

schedule control, IPAD wlll:

a) Report status and impending problems;

b) When a milestone is missed, analyze impact and print

report, which is to be dlstributed to each affected

orga ni za tion;

c) Stop 3ob execution if subtask has not been scheduled or

_as been completed.

REV. B

-111-
REQUIREMENT 57 OPTIONAL AUTOMATIC REPORTING

SOURCE 1.3/3.3.7._, 1.4/2.5._, 1.4/2.1.4

DESCR IPTION

IPAD shall provide the capability for optional automatic

reporting such as automatic reporting of data which is due in the

data base to meet a schedule date, all data which is overdue in

the data base, and notification of a data set change to all users

who had accessed t_e data set.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The following automatic reports will be generated and checked

Zor accuracy and reliability.

a) A report to list data which is due in the data base to

meet a schedule date.

b) A report to list data wh_c_ is overdue in the data base.

c) Revise a data set and initiate the notification of the

revision to all users who have accessed the data set.

REV. B

-112-
D

REQUIREMENT 57.1 APPLICATION PROGRAM CERTIFICATION

SOURCE 1.3/5.2.2, 1.3/5.2.3

DESCRIPTION

In order to document the integrity of a given job execution,

Its co,_onent operational modules must s_n_how be certified.

Certi£ication implies that a _dgment has been made about the

trustworthiness o1 the computer code to perform its intended

ZunctiQn. As an example, an operational module may ha%_ one of

the following certifications:

a) In checkout

b) Research use only

c) StafZ use

d) Airplane progranVmodel use

e} FAA certificatiQn use (legally certified)

The certification of a job is the same as the "lo_st"

certification operational module contained in the job.

Since many c_anges maybe made to a computer program, a

mechanism is needed to automatically record program versions.

This applies to coding modules, operational modules and jobs.

certification data must accompany the program module in the

progr_a library.

The

ABSTRACT OFT HE ACCEPTANCE CRITERIA

The capability of IPAD to correctly assign version numbers

and identify certification of programs in the program library will

De tested.

REV. B

-113-
_E_UIREMENT 57.2 USER ACTIVITY CHECKLIST

SOURCL 1._/2.6

D£SCRIPTI ON

Uccasionally during his work session (at anytime in the

CCMMAND MODE) a user needs the capability to request a summary of

his activities in order to confirm that he has in fact done what

he intende_ to do up to t_at point. Two types of report are

needed, one to check specific items and one to check all user

activities.

The entities needing verification during the user's current

work session are: data names, coding module names, operating

module names, suDtasK names, job names and their respective

headers, where appropriate.

The user also must verify the activities which he has

performed (or which nave been performed by a job) on these

entlties. These activities are: accessed; copied and given a new

n_ne; created; modified and given a new version name; deleted;

interrupted (in the case oZ a job) and suspended; in-work, and

completed (in the case ot a subtask).

Ix, the case of headers the item(s) in the header that are

aifected should De identitied with appropriate comments such as

"L_TA SET XYZ, READ PERMISSION GRANTED TO JOHN BROWN AND ALL

MEMBERS ASSIGNED TO THE. AERODYNAMICS DATA AREA."

The report should include the date and time when the activity

was completed and be broken down by Subtask.

The user must be able to enable or disable this checklist

capability using a command.

Report Format Examples

Session Date: 5/10/77 User I/D:

Subtask XXX Completed at 10:45 a.m.

Data Set XYZ (Data Area=Stress) accessed at 10:15 a.m.

Data Set ABC (Data Area=Wing Pro3ect) copied at 10:20 a.m.

to Data Area=Stress a,_ renamed CBA

Job Joe (Data Area=Stress) Run commenced at 10:30 a.m. ;

completed at I0:_5 a.m. with normal exit

Data Sets Accessed:

I. XYZ (Data Area=Stress}

2. CBA (Data Area=Stress)

-114-

REV° B
Data Sets Produced:

I. PQR (Data Area=Stress)

3ubtask YYY suspended at I0:52 a.m.

Operating module EFG version changed at I0:_7 a.m. Execute

permission granted to John Brown anQ all members assigned to

the Aerodynamics Data Area.

_BSTR_CT OF THE aCCEPTANCE CRITERIA

Typical work session scenarios will be performed and the

checklist reports displayed and checked for accuracy and

completion.

REV. B

-115-
2 .3 INFORMATION MANAGEMENT

Information manngement is Droken down into three categories -

c_td management, infonuation management tools and computer program

liDrary. Data management is concerned with the organization,

m_nipulation, control, antegrlty, security and administration of

IPAD data. Information management tools are provided to maintain

data, to perforul data transformations, to compare data and to

perform arithmetic _nd logical operations on data. The computer

program library contains computer programs in source and

executable forms. The programs may be supplied by the user or

generated by software processes (e.g., compilation). Oomputer

p_ograms may be structured into jobs and executed. Information

amout programs is availdDle to the user.

2.3. I Data Management

The handling o_ data within IPAD has many facets including

organization, manipulation, control, integrity, security and

administration. Data organization at the elementary level

consists ot elements, formats and data relationships which will be

groupe_ into data sets. Data sets are organized into data areas.

Data manipulation includes capabilities to query, to copy data and

programs and to access and retrieve archlved data. Data control

governs data access, ddta changes, purging and data retention.

BacKup and recovery procedures are provided to guard the integrity

or all data in the IPAD data base, Proper security clearance is

required to access some data sets wathin IPAD. Security control

oZ read/write access is availaDle. Data administration

responsibility is assigned to a designated person or organization

who will De responslDle Zor exercising control over the entire

IPAD information bank. (See Zigure 2.3.1-1 and 2.3.1-2.)

;_.3.1.1 Data Organization

_t the elementary level IPAD data will consist of data

eleme,_ts, data formats and data relationships. These elementary

irons may be grouped and organized into data sets which may be

logically related to other data sets. Data sets will be logically

organized iJlto data areas. A data set may belong to more than one

data area. Header data will be associated with each data set to

enable the user to query a,K1 retrleve data.

Eac_ data area will contain a dictionary or index that lists

the data sets within each area and also describes the contents of

eaca data set. Each IPAD user will have his own private working

d_td space.

Ddta areas m_y be combined into a single data area. Data

dlctio1_ries _or the data areas will also De combined. Data

-116-

REV. B
definition ambiguities and redundancies wall be reported to the

LLse_.

REV. B

-117-
LL.

CD

l'm

Z

_ES

&.m.m

0

hl

,,-,,.,.

,t

•--m.m

d6_

_ °<_ooo _

0

Figure 2.3.1-1

Data Management Requiremen

-118-

REV. B
C'q

U_

0

C_4

REV. B

Z Z

Z Z I'-- Lm.l _'

I--- i.1_ Z (:_ _ 0

o M M

M M M

-119-

Figure 2.3.1-2

Data Management Requirements

(Cont'd)
REQUIREMENT 58 INFORMATION BANK STRUCTURE

SOURCE 1.3/3.1.3.1, 1.3/3.1.3.2

DESCR IPTION

The capability must be provided _or groups of IPAD data sets

to be logically organized into data areas for convenience of

nandlang, reporting requirements, program input/output, frequency

oZ access, etc. There should be no restriction on the number of

data areas that a given data set may belong to. Separate user

action shall be required to make a data set or data area a member

oz anot/%er date area.

A _ata area imay be contained in part or all within another

data area. The totality of all data areas (sets) constitutes the

information bank which is a single source non redundant

computerized data resource of a c_pany.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A number of data sets will be created, as will a number of

data areas. The ability to make a data area, in whole or in part,

a member of another area will be tested. One data set will be

H_de a member of all data areas. Queries and data accesses will

De made to determine correct assignment oZ data areas and data

sets.

In addition the capaDility of IPAD to control and manage data

as a company resource will be evaluated. An information bank

equivalent to figure 3.1.3.2-I through 3.1.3.2-6 of D6-IPAD-70012-

D will be defined. The data model constructed _or requirement 44,

ACT 2, will be interfaced to the information banK. Several

related projects will be defined and executed.

REV. B

-120-
P_EQUIREMENT 59 DATA S_T ASSOCIATION

SOURCE 1.3/3.2.1

DESCRIPTION

IPAD shall provide the capability to logically associate data

sets with a given data set. If a data set is accessed for the

purpose o£ reading, its associates (and associates of these to

whatever depth defined) are also accessed.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A chain of logically associated data sets will be created.

The first will be accessed and queries performed to insure the

rest of the chain is also accessed. Chains of length 2 and length

10 will _e used.

REV. B

-121-
REQUIREMENT 60 DATA SET HEADERS

SOURCE 1.3/3.1._.3, 1.3/3.2.2, 1.3/3.3.7.1, 1.3/3.1.1

DESCRIPTION

IPAD shall provide t_e capability to logically associate

header data wit_ each data set. Header data may be classified

Lnto three categories:

. IPAD System Data - This data is required by IPAD to maintain

data set integrity :

o

o

a)

b)

c)

d)

e)

£)

Unique Data Set Name

Creation Date

Creation Time

Storage Relationship

Storage Format

Otter

Installation Control Data - This data is used by an

installation to control data access and retention.

a) Security - National, Company, Project and/or User

Security Information.

Owner I.D. - Creator of data set.

c) Retention Classification - How long should data set be

retained (see requirement 79).

d) Version I.D. - The information is used if multiple

versions of a data set are stored {see requirement 77).

Project/User Controlled Data - This data is used to determine

how the data is to be applied.

a} Oser Qualifier - For Example: Airplane Model, Case No.,

etc.

REV. B

-122-
b)

c)

d)

e)

f)

g)

Approval Category - Prepared, Checked or Approved (see

requirement 8 1) .

Quality Categories - Preliminary or Final

Classification Code.

Project I.D.

Process I.D.

Other (such as date due).

ABSTRACT OF THE ACCEPTANCE CRITERIA

The IPAD capability to store, retrieve, and modify header

data _ssociated with data sets will be tested. Data definitions

will me entered specifying the installation control header data,

including planned date and last possible date. Several data sets

will then be created, and the capability of IPAD to successfully

retrieve the header informati_1 for these data sets will be

tested, as well as the user's capability to modify the header

1_,f or mation.

In _n additional test, a data set will be created under IPAD,

archived, and later retrieved. The header information will be

checked for accuracy.

REV. B

-123-
REQUIREMENT bl DATA AREA CONTENTS

SOURCE I .3/3 . I .2

D_SCRIPTION

A data area s_all consist of two general items: a dictionary

or index or equivalent concept describing what the area contains,

_nd the data sets, data definitions, etc., that it actually

contains.

ABSTRACT OF THE ACCEPTANCE C_ITERIA

A data area will be created which contains a variety of data

sets and data definitions. Queries will De made to determine the

correctness or the dictionary/index and to access the data sets,

etc., to insure that the contents of the data area is correct.

REV. B

-12_-
REQU_NT 62 PRIVATE DATA SPACE

SOURCE 1.3/3.1.2, 1. _/2.5.5

DESCRIPTION

Each active subtask in IPAD shall have a special subtask data

area which will _unction as its private working data space. All

data generated by t_e subtask is automatically placed in the

subtask area. Data contained in subtask area is unxeleased data.

(See requirement 81 .)

ABSTRACT OF THE ACCEPTANCE C_ITERIA

Three separate su_tas_s will Be defined and will generate

data sets to insure the existence of the private working data

area. A check will be made to insure these areas are private and

cannot be accessed from another subtask.

REVo B

-125-
2.3. I. 1. I Data Definition Contents

IPAD will support an expandable list of data element types.

An orderly growth of data set definitions and occurrences of data

corresponOing to the definition will also be supported.

Capabilities for a company to insert into the information bank,

for query, definitions, and sets of vdlues for engineering

standards will be provided. A user program will be allowed to

access data sets or data elements within any number of specified

data areas.

Data areas may be combined into a slngle data area. Data

d_ctionaries for the data areas will also be combined. Data

definition ambiguities and redundancies will be reported to the

user.

REV. B

-126-
R_QUIREMENT 63 DATA ELEMENT TYPES

SOURCe: I .3/4 .2 .4

DESCRIPTION

IPAD shall support an expandable list of data element types

suc/1 as text, scalars, vectors, matrices, tables, and lists. Data

elements may De populated with characters, integers, real,

complex, or multiple precision values.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Data formats will De defined using all the mentioned data

element types with integers, reals, complex and multiple precision

values. Data will be loaded and used to test accuracy. New data

types will De defined and used. A user opinion survey will be

made to check useability of element type definition.

REV. B

-127-
REQUIREMENT 64 DATA GROW_

SOURCE I .3/4 .0

DESCRIPTION

IPAD shall support an orderly growth of data set (elements,

relationship formats) definitions within an IPAD information bank

without impacting the availability of the existing information.

In addition, IPAD shall support an orderly growth of occurrences

oZ data corresponding to r/le definitions.

ABSTR/HJf OF THE ACCEPTANCE CRITERIA

A set oZ definitions of elements, relationships and formats

will be used to simulate data definition growth to system storage

capacity in several simulated system loadings. There shall be no

evidence of software limitations on the number of data definitions

supported by IPAD.

REV. B

-128-
H_QUTREMENT 65 ENGINEERING STANDARDS

SOURCE SOW/5.1.2, I. 4/2.4.5

DESCRIPTION

The IPAD System must provide the capability for a using

company to insert into the information bank, definitions and sets

oZ values for engineering standards. IPAD will provide a default

s_t ot engineering standards, tO include material property lists,

universal constants, etc. These engineering standards shall be

available for query.

ABSTRACT OF THE ACCEPTANCE CRITERIA

DeZinitions and sets of walues will be entered into the

informtion bank for engineering standards. Query will be done

against that information to guarantee its accuracy. In addition a

complete query and print out of the default information will be

performed to check its accuracy.

REV. B

-129-
REQUIkEMENT 6b REORGANIZING DATA AREAS

SOURCE BCAC-NASA

DESCRIPTION

The capability shall be provided to organize the information

bank Dy combining individual data areas into one composite data

area or moving one nested data area into another data area thus

creatlng a new combination, the data dictionaries for the

individua± areas shall also be comDined and the user will be

notified of any ambiguities and/or redundancies resulting from

duplicate data definitions. The result of this operation shall be

a reorganized inIormation Dank with correct data dictionaries for

the restructured areas.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The capability to confine individual data areas into one data

area will be tested. Several users will test this requirement by

combining data areas that have been used in other tests. There

will be ambiguities and redundancies and the user must be notified

oz these and provided an easy means of resolving them. After

successfullyl combining data areas, only one data area and data

dictionary must exist. Ease of use is the prime consideration of

this test.

REV. B

-130-
2.3. I. I. 2 Data Structure

Data structures used by a company shall be provided and

supported by IPAD. Logical structure independent o£ physical

structure will be provided so that an alteration to the physical

structure will not affect the user or his program. A capability

for defining data relationships will be provided to the user. The

format in which the data is to be presented to the user may also

be specified. Logical relationships of data elements may be

established, recorded, viewed, located, and modified. Data

element names are to be unique within a data area. There may be

d_ta areas in which data element definitions are not allowed.

REV. B

-131-
_LEQU I_ENT 67 DA_A STRUCTURF_

SOURCE SOW/5.2.1.1, SOW/5.2.1.2, 1.3/4._, 1.3/4.3.4

DESCRIPTI ON

IPAD shall provide and support those data structures used by

Engineering. The capability to have logical structure independent

oI physical structure s_all be provided. In t_is case, alteration

to the physical structure must not affect the user or his

programs.

ABS_3_A_f OF THE ACCEPTANCE CRITERIA

A set of structures will De developed which test the full

spectrum of IPAD logical structures. To test independence of

p_ysical _nd logical structures, r/%e physical structure will be

modifaed several times and query's run to insure no user impact.

The user (engineering) acceptance of the logical structures will

be evaluated Dy means of a user survey.

REV. B

-132-
_MEQU_NT 68 DATA ELEMENTS AND RELATIONSHIPS

SOURCE SOW/5.2.1.1, 1.3/_.1.2, 1.3/4.3.2

DESCRIPTION

IPAD shall provide the user with the capability to define

data elements and to introduce relationships between them.

Data element definitions shall include such attributes as

name, type (integer, real, c_aracter, vector, matrix, tensor,

etc.) , synonyms, textual definition, engineering use description,

unit (s) , default value,external representation format, etc.

A data relationship is a logical grouping of data elements,

possibly expressed in tera%s of other relationships. The user

shall have rA_e capability of expressing relationships for the

purpose of storing and retrieving data. Relationships will in

general be expressed at the tlme of use, rout it shall be possible

£or t/%e user to define and store relationships for future usage.

Accompanying the data relationship shall De the ability for a

user or a user's program to specify the format in which the data

is to be delivered from IPAD or presented to IPAD. A format shall

define such things as: di_lay format (e.g., FORTRAN format

capabllity), external media type, and external units (which ir

different from units defined with an element will cause unit

conversion). Forn_t_ may be expressed at time of usage and may

also be stored for future use. One format may be used in

conjunction with several relationships.

A_STRACT OF THE ACCEPTANCE CRITERIA

Users will define data elements and data relationships both

at _e time of usage and to be stored for later use. All

attributes for data element definition described in the

requirement will be tested.

Another test should verify that the relationships and data

element definitions can be used to store aud access data

successfully.

REV. B

-133-
The capability to define the I/O format for data will be

tested both from within a user program and as a direct user

request. Specific items defined wall include those identified in

the requirement.

A user opinion survey will evaluate these capabilities based

upon correctness and user _cceptability.

REV. B

-13_-
I_.,QUXRI_ENT 69 OPERATIONS ON DATA RELATIONSHIPS

SOURCE SOW/5.1.18, 1.3/4.3, 1.4/2.5.2

DESCR IPTI ON

IPAD shall provid_ means for establishing, recording,

viewing, locating, and modifying the logical relationships of data

elements stored _l a data area.

ABSTRAt_ OF THE ACCEPTANCE CRITERIA

User will deZine to IPAD sample logical relationships of data

ele_nts stored in a data area. Users other t_an those who

originally defined the logical relationships will then attempt to

locate and view these logical relationships. Several

_K_ifications should then be ,_de and the resulting logical

relationships viewed to verify that the modifications were

correctly performed.

REV. B

-135-
_E_UIREMENT 70 DATA EleMENT NAMES

SUURCE 1.3/_.2.1, 1.3/q._.1.1, 1.3/4.2..2

DESCRIPTION

Data element names shall be unique within the data area in

whica the el_nents are defined and in any of its dependent data

areas. It shall be possible to designate data areas for which

data element definitions are not allowed.

ABSTRA%_f OF THE AOCEPTANCE CRITERIA

A sample oZ data element names will be defined for a specific

data area. It should be verified that these data element names

are available to the data area and any of its dependent data

areas. Attempts should be made to define duplicate data element

names for this data area and these attempts should be

unsuccessful.

A data area should De designated for which data element

de£initions are not allowed. It should then be verified that data

element names cannot be defined for this data area.

REV. B

-136-
2.3.1.1.3 Quantifiers

The data volumes and data processing activities that IPAD

must support vary from company to company. Bounds on volumes of

storing and retrieving activities are estimated from the Data Flow

MDdel in document D6-1PAD-70012-D.

REV. B

-137-
REQUIREMENT 71 DATA QUAN'EFI CATI ON

SOURCE SOW/5.2.1, 1.3/2.2, 1.3/2.3

DE_CR IPTION

The data volumes and data processing activities that IPAD

must support vary from company to company. The following

guidelznes establish the upper bound of data volumes.

Two product development processes through detail design are

in progress at any given time. The data storage required is:

Immediate access - 150 billion bits

Archive (10 ,rain. access) - 190 billion bits

Archive (2_ hr. access) - 360 billion bits

Ten products are undergoing sustaining design. For this

activity, it is _ssumed that 20_ of the total sustaining design

data is required for current work and requires immediate access;

40% consists 0£ archived drawings w_ic_ must be available within

10 mlnutes; _nd the remainlng 40_ is also archived and must be

availaDle within 24 hours. The data storage required is:

Immediate access - 470 Dillion bits

Archive (10 rain. access} - 9_0 billion bits

Archive (24 hr. access) - 940 billion bits

PrelL_inary deslgz,, of exploratory nature of 10 products per

year. Data storage required:

Immediate access - 100 billion bits

Archive (24 _r. access) - 620 billion bits

For archival purposes, it is assumed that there is a

continued il,crease of data volume that corresponds to one product

ae_cription (detailed design) every two years and 10_ of the

information developed during exploratory preliminary design. The

annual increase in data storage is:

Archive (24 hr. access) - 310 billion bits

The bounds of data storage required are as follows (the lower

bound is assumed to De approximately 10_ of the upper bound):

REV. B

-138-
Lower Upper

Bound Bound

Immediate access (billion bits) 70 720

Annual Growth

Azc_ive - I0 min. access

{billion bits) 110 1130

Archive - 24 hr. access

(billion bits) 190 1920 3 10

The above volumes were estimated from the data flow model in

document D6-1PAD-70012-D. Table 2.3.1.1.3-I contains a summary of

the output data ££om each design level. A factor was used to

account for iterations estimated for each level and the

distribution of on-line data and archival data. This data

sto_age, representing the development of one aerospace vehicle,

was further factored to represent the total engineering data

storage required for one large aerospace company and is shown in

table 2.3.1.1.3-2.

REV. B

-139-
Table 2.3.1.1.3-1 Data Storage Estimate - IPAD Project I

Subsonic Transport (Ref, D6-1PAD-7OOIO-D)

(Data Expressed as Millions of 60 Bit Words)

Data

Data Output by Output

Design Level

(ReF: D6-1PAD-70012-D) Single Pass

Data Through

Data Model Output Levels

ABA .35

Subtotal Level II

ABB .12

ABBA .Of

ABBB .32

Subtotal Level Ill

ABC ,61

ABCA 5,22

ABCB 1,02

ABCC 11.52

ABCD 13,01

ABCF 6.68

Subtotal Level IV

Total Levels II-IV

Exploratory

Preliminary Design

ABDA

ABDB

ABDC

Subtotal Level V

Total Levels II-V

Preliminary Design

618

248

437

ACAA

ACAB

ACAC

ACAD

648

593

2649

7

Total Level VI

Detail Design

Storage Factor Based D A T A S T 0 R A G E

on Estimated Iterations Archival

of Levels Archival On-Llne ,

On-Line 10-min 24-hour lO-min 24-hour

Access Access Access Access

,35 10 -- 20 3,5

38.1

|

1304

897

.45 10 -- 90 4.5

4 -- 26 152 -- 991

160 -- 1038

2 1.2 4.8 2608 1565 6260

7.0

40

2768 1565 7298

,2 ,4 ,4 779 . 1559 1559

REV. B

-140-
Table 2.3.1.1.3-2 Data Storage Estimate

Large Aerospace Company

IPAD Distributed Environment

(Data Storage Expressed as Bllllons of Bits)

Activities Assumed

for Data Volume

Estimate of an

Aerospace Company

2 Product Development

Processes in Progress

at Any Given Time

•Prellmlnary Design

•Detail Design

Sub-Total

10 Products in

Sustaining Design

Sub-Total

Preliminary Design of

Exploratory Nature (EPD)

IO Products per Year

Sub-Total

Total Data Storage

Archival Growth

•One Product per Year

•10% Exploratory

Preliminary Design

Total Archival Growth

Storage Factor

Based on Table

2.3.1.1.3-I

(Converted to

Billion Bits)

.5(Lev. II-V)

1.5 (Lev. Vl)

10 (Lev. Vl)

I0 (Lev. II-IV)

DATA STORAGE

On-Line

8O

70

150 190

470

Archival

100

1.0 (Lev. VI )

.1 (EPD)

720

Q_

10-mln 24-hour

Access Access

50 220

140 140

360

940 940

-- 620

1130 1920

230

-- 70

310

REV. B

-lq. 1-
ABSTRACT OF THE ACCEPTANCE CRITERIA

In order to test the data volumes and data processing

activities that can be supported by IPAD, a computer simulation

model will be developed based on the Data Flow Model in document

Db-IPAD-70012-D. IPAD _/st function correctly and within response

constraints at both the upper and lower bounds given.

REV. B

-142-
2.3. I. 2 Data Max_ipulation

IPAD data manipulation capabilities include the ability to

query specific data areas, to copy data and programs from other

data area into a user's own data area, to access and retrieve data

from arc_,ive files.

REV,, B

-143-
REQUIREMENT 72 DATA SET £DPYING

SOURCE 1.4/2.5.2

D_SCRIPTION

The system shall provide the user with a means to copy data

and programs into his own subtas_ or data area Hrom other data

areas.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The software to copy data and programs into a user data area

will be tested. The accuracy of before and after images will be

verified.

REVo B

-_W4-
_EQU IREME NT 73 ARCHIVAL DATA

SOURCE SOW/5.1.22, 1.3/3.1.3.2

DESCRIPTION

IPAD shall provide appropriate aids for access to engineering

project data after it has been archived. These aids include, for

example, an interactive query of data area catalogs to determine

the existence of data sets that have been archived. Users shall

not be aware of arc_,ival storage media. Queries of archived data

sets shall cause the archived data sets to be returned to online

status for i_ued_ate access. Data sets containing geometry of

parts shall be available online within 10 minutes from any

terminal in an IPAD installation having terminals distributed

across both global and local networks. All other archived data

sets shall be available wlthin 2_ hours. (See requirement 71 for

the quantities of archived data expected in an IPAD installation.)

ABSTRACT uF THE ACCEPTANCE CRITERIA

The existence of software to retrieve archived data to online storage will be verified. The efficiency and accuracy of the

software to identify and move data to on-line storage will be

tested.

REV. B

-145-
F_.QUIREMENT 74 PROGRAM DA_% ACCESS

SOURCE SOW/5.2 •1.1, 1.3/4.4.2

DESCRIPTION

IPAD shall provide the ability for user programs to work

within a subset of a data area or with data from more than one

datd area.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Multiple data areas will be created. User programs Will be

written which will utilize data from a subset of a specified data

area and from several specified data areas.

REV. B

-146-
REQUIREMENT 75 USER DATA ACCESS

SOURCE 1.3/3.2.2.1, 1.3/4.5.1

DESCRIPTION

The user shall be able to limit a query to a specific data

area or to any subset of the information bank identified in a

previous query.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Queries will be made to check that they may be limited to a

selected data area or areas. The carry over from previous queries

feature will also be tested. The tests will be _or accuracy and

responsiveness.

REV. B

-1_7-
2.3. I. 3 Data Control

Data control is instigated to insure the validity and

accuracy of IPAD. All accesses to IPAD data sets are recorded and

are available for examination. Any change to a data set must be

accompanied by a corresponding change in the data set name. A

data set that has other data sets dependent upon it can only be

purged with special peri_ission. Data set retention

classiZicatlons establish how long a data set will be retained and

whether the data set is to be archived or not. IPAD data can be

qualified as for information only, preliminary or final. IPAD

users using unreleased data will be notified when released data

becomes available. Data sets may be shared or private. IPAD will

per:Idt automatic and m_,ual distribution o_ data and programs

t_roughout the IPAD computer r_twork.

REV. B

-1_8-
REQUIREMENT 76 DATA SET ACCESS RECORDS

SOURCE SOW/5.1.15, SOW/5.2.1.6, 1.3/3.3.7.4, F3/3.1,

1.3/3.3.7-2, 1.4/2.1.4

DESCRIPTION

IPAD shall keep a record of all accesses to a data set. The

information kept in this record shall be open ended and may

include user identification, date, time, _b, and type of access.

Tt_ record is for the purpose of notification and will be

maintained tot the life of the data set or until it is no longer

useful (program parameter}.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A set of data to be kept for each access will be defined

includlng user id, date, time, job, and type of access. A random

mix of users will access data sets by user query, system data

manipulation utilities under user control, and user jobs. A

planned set of activities will guide these tests and will be used

to establish operational correctness. Exact agreement between the

user mix and the records kept by the system is required.

REV. B

-149-
REQUIKEMENT 77 DATA SET IDENTIFI_TION CONTROL

SOURCE 1.3/3.1.4-2

DESCRIPTION

The system must guarantee that data set content changes cause

a change in data set identification. This will be accomplished by

the user inserting a new name, or a system supplied version

identirication to the existing name by a version number, (default

procedure ) .

ABStrACT OF THE ACCEPTANCE CRITERIA

C_eck that the access of data sets in write mode causes the

IPAD system to either

a) request the user to specify a new name for the data set

or

b) assign a version number to the old name by default of

a).

REV. B

-150-
REQUIREMENT 78 D_TA PURGE PERMISSION

SOURCE 1 .3/3 .3.7 .5

D_:SCR IPT ION

Special permission s_all be required to purge any data set

wD_ich has a dependent data set while these data sets are under

project control.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The data set purge permission requirement will be tested by

dttempting to purge data sets which have dependent data sets both

with permission and without permission.

REV. B

-151-
REQUIREMENT 79 DATA RETENTION CLASSIFICATION

SOURCE I .3/3.3.7.5

DESCRIPTION

IPAD shall provide for data set retention classifications

such as permanent, program life, project life, number of years,

etc. Project life should be the archival default rating and the

system shall have provisions to selectively purge or archive data

set occurrences which are determined by retention classification

to be no longer required.

ABSTRACT OF THE AC_PTANCE CRITERIA

The retention classification of data sets to control

archiving and purging will be tested. The procedure will be as

zollows:

a. Several data sets will be classified for retention in the

various categories cited in this requirement.

b. Establish artificial tlmes for project life, etc.

c. Check that retention classiZications have been correctly

labelled for eacn data set.

d. Test automatic purges and archivals.

e. Test defaults.

REV. B

-152-
_REQUIREMENT 80 DATA VERSTION NOTIFICATION

SOUkCE 1.3/3.1.4, 1.4/2.9.2, 1.4/2.5.5

DESCR IPTI ON

A procedure is required to notify users when they access data

t_at a later version of the data is availaDle (see requiement 81).

ABSTRACT OF THE ACCEPTANCE CRITERIA

The approved data identification will be tested by several

users each or whom accesses preliminary information for which

released information is available. The notification must be

issued.

REV. B

-153-
REQUIREMENT 81 DATA RELEASE MECHANISM

SOURCE 1.3/3.1. _, 1._/2.5.5

DESCRIPTION

IPAD shall provide a data release mechanism equivalent to

signing a drawing. Approval categories such as the following

shall be possible:

CO DE LAB EL DE FIN IT ION

R1 Prepared Creator is satisfied

with data

R2 Checker is satisfied

with data

R3 Responsible manager is

satisfied with data

Checked

Approved

_w T_e release mechanism saall also make provisions to identify

the quality of the data and permit release of intermediate

i_tormation. _uality categories such as the following shall

be possiDle for all released data.

CODE LAB EL DEFINITI ON

Q1 Preliminary

Q2 Final

Data likely to change

Data unlikely to change

o

_o

Released data is subject to version control and qualification

in accordance with Requirement 77-32.

Subsequent release of new versions of previously released

data shall result in the following:

Notify those users t/uat have accessed the previous

version that a new version exists. (See requirement

57.)

New use o_ the data shall always be the latest version

(unless user specifies a particular version).

REV. B

-15_-
o

D

Continued use o2 previous versions shall be possible but

an automatic warning or message is required. (See

requirement 80. )

The appropriate release and quality labels shall be shown on

each page of data printed or displayed.

The user should De able to request a list of release and

quality labels on the input which was used to produce the

current output.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A basic set of data approval and quality categories will De

de£ined to IPAD. Data release will be simulated and will include

optional aDbreviations. A check will be made to insure that only

authorized people may assign data release and quality categories

to data.

REV. B

-155-
REQUIREME_N_TT 82 SHARED AND PRIVATE DATA SETS

SOURC£ SOW/5 .2 .1 .1

DESCRIPTION

IPAD s_all acc_s_date both shared and private data sets.

Users with a need to read a private data set shall be given "read

only" permission Dy the owner/creator of the private data. There

shall be no restriction on the number of users who may be

permitted to read a shared data set concurrently.

ABb_fRACT OF THE ACCEPTANCE CRITERIA

The ability to use either private or shared data sets will be

tested by several users. The procedure will include:

a. Use a private data set and prove that other users cannot

access it;

D. Snare a data set by several users simultaneously (read only).

REV. B

-156-
REQUIREMENT 83 DATA DISTRIBUTION CONTROL

SOURCE BCAC-NASA

DESCRIPTION

IPAD shall permit both automatic (IPAD initiated and

controlled) and manual {TPAD user initiated and controlled)

distribution of data _nd programs throughout the IPAD computer

complex. IPAD shall retain knowledge of the location of and

access control to all dat_ and programs within the IPAD system.

ABb_fRACT OF THE ACCEPTANCE CRTTERIA

T_e data distribution control feature of IPAD will be tested

Zor bot_ automatic (system initiated) and manual (user initiated)

modes. The procedure will include the following steps.

a) Several users at various locations will create data sets

and/or programs and check that the system automatically

distributes them to the correct source.

b) Several users will create data sets and/or programs and

tell the system where to distribute them and then check

that they are distributed properly.

c) Check the accuracy of the syste,_ records of location of

data and programs by query.

REV. B

-157-
2.3. I. _ Data Integrity

IPAD must guard t_e integrity of all data in the IPAD data

Dase. This requires that proper backup and recovery procedures be

provided. These procedures shall be sufficient to guard against

system failure, or accidental or intentional destruction of the

IPAD data base.

Loss or modification of IPAD data other than through normal

use shall De identified and reported to the owner(s) of the data.

Further unauthorized use of the data shall be blocked by IPAD.

As part ot system backup and recovery, a history of

trar_actions and data will be maintained to permit the recreation

o_ required data. History transactions may be arcD_ived if the

required data is archived.

Provisions will De available within IPAD to validate user

data. Validation will be performed on values when entered or on

selected contents of a data set at the user's request. The set of

validation available tr_n IPAD will be extendable and user

derinabl e.

REV. B

-158-
REQUIREMENT 8_ RECOVERY AND BACKUP

SOUR__CE SOW/5.1.24, ,_W/5.2.1.6, 1.3/3.5, 1.tt/2.8.2

DESCRIPTION

Recovery and backup procedures shall be provided to ensure

data integrity in case of syste_n failure or accidental or

intentional destruction oZ the data bases.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The backup and recovery capabilities will be evaluated. A

planned set of failures will be simulated. These simulations

shall include all known types of system iailures and accidental or

intentional destruction of the information bank. The backup and

recovery capabilities will be judged on adequacy, computing

resources required, time required to reco%_r and user involvement

required.

REV. B

-159-
REQUIREMENT 05 MODIFICATION OR LOSS OF DATA

SOURCE 1._/2.8.2, SOW/5.2.1.6

DESCRIPTION

In the event that the IPAD system, or any agent other than

the user in the normal course of using the system, causes loss or

modification of data an the IPAD information bank, the system

shall be designed to identify the affected data.

The system will immediately report the identity of the

affected data and the ndture of the proDlexn to the owners of the

data, and shall bloc_ furt/%er use of that data.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A simulation of both lost and modified data will be made.

This data will be both programs and data in several different data

areas. Correct identification and reporting of the lost or

damaged data will be checked for accuracy and timeliness.

Attempts to use damaged data will be made to insure IPAD correctly

blocks that use.

REVo B

-160-
REQUIREMENT _6 DATA TRANSACTION HISTORY

_gURCE SOW/5.1.15, $UW/5.2.1.4, 1.3/3.1.4.2, 1.3/3.1.4.3,

1.3/3.3.7 1._/3.3.11, I._/2.8.2

DESCRIPTI ON

The system shall record a history of transactions and data

needed to recreate data w_ich has Deen willfully or inadvertently

destroyed or modified. This includes date, creator (owner),

creating job, and input sets to creating job, etc. There shall be

a mec_nism to make it cgtional for specified data sets.

This history must be maintained as long as the data is

maintained. It may be archived if the data is archived.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Data sets will be created to check that the history

information exists as long as the data set exists, the data sets

will be transferred to ren_te IPAD and back, to archival and back

and between data areas. T_e data will be destroyed and the

ability o_ IPAD to recreate it will be checked. A deliberate

attempt to delete history informatlon while it exists will be made

in addition to checking that authorized purging of the data set

causes deletion of the history data.

REV. B

-161-
REQU IRhMENT 87 DATA VALIDATION

SOURCE 1.3/3._, 1.3/3.3.6.2

DESCRI PT I ON

IPAD shall provide for validation of user data including a

r_ige of values check. The set of validation operations will be

extendable and user definable. Validation will be performed on

values when entered and on selected contents of a data set at user

request.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A data definition will be created wit_ several user defined

vaiidation checks. Both good and bad data will be entered to

insure IPAD accepts good data and rejects bad data. After some

data n=s been entered a new validation check will be defined which

rejects some of the previously entered data. The user will

request this check _e run against a subset of the already entered

data to insure IPAD detects the Dad data. The tests will be for

ease of use and accuracy.

REV. B

-162-
_QUIRF_ENT 87. I DATA SET MODLFICATION LOG

SOURCE 1.3/3.3.7.3

DESCRIPTI ON

The following information shall be available in a data set

modification log to clarify t_e history ot data set versions: (see

requirement 77} :

1. Reason for change

2. Description of change

Note: This information is in addition to the data set

headers (see requirement 60).

ABST_ OF THE ACCEPTANCE CRITERIA

The capability for IPAD tO maintain a data set modification

log will be tested. Users notified of ddta set changes (see

requien_nt 80) will access the data set modifiction log to

determine the general nature of the change. This test will be

cox_ucted in conjunction with ACT 80-33/I.

REV. B

-163-
2.3.1.5 Data Security

Read access to classified and proprietary data including

headers shall require proper security clearance. Read access to

other data may require need-to-know security clearance but access

to the corresponding headers is unrestricted. Only the data

owner (s) ,m_y nave write access to data.

User access to specific data sets may be controlled by a

aeslgnated authority. Under this control, a user must establish

"need to Know" rlg_ts before access is permitted.

Computer programs are subject to the same access restrictions

as _,dividuals (noted above). The security classification of the

person executing the programs is used to establis_ computer

progr_a accessibility.

IPAD shall have the ability to report unauthorized attempts

to access IPAD data. The reports will be submitted to the system

administrator for iurt3,er action.

REV. B

-10_-
REQUI/hS_ENT 88 USER READ AND WRITE SECURITY

SOURCE S0W/5.1.21, SOW/5.2.1.6, 1.3/3.2.1, 1._/2.8.2,

1.3/3.2.3. I

DESCRIPTION

Read (query) access to classilied and proprietary data

(xncluding headers) shall require proper clearance and be subject

to "need to know.- Read access to all other data shall be subject

to "need to know," except that headers oZ such data shall not be

subject to any read (query} control.

The IPAD system must provide a mean_ to enable a designated

authority to establish a user,s "need to know" rights relative to

s_ec_fic sets oi data.

Write access to all data shall be possible by the owner (s)

only.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Access to data by users ot_er than the owner will be tested

by having users try to access data labelled classified and

proprietary for reading. Only those with proper clearance and a

need to know should be able to access this data (even the header

information is protected}. For other data, users must have a need

to know, but the headers are accessible. The means of determining

the need to _utow authority and controlling user clearance will be

tested as well as the data protection. The owner of the data must

have access to write for updating, etc. This aspect will also be

checked.

REV. B

-165-
R_QUIRKMENT 89 PROGRAM READ AND WRITE SECURITY

SOURCE 1.3/3.2.3.2, 1.3/3.2.2.2

DESCRIPTION

Computer program access to a data set, including header,

shall be subject to the same control as a user access based on the

access restrictions oI the person executing the computer program.

ABSTRA_f OF THE ACCEPTANCE CRITERIA

The access of data by a computer program will be tested

similarly to or in conjunction with the test of requirement 88

"READ AND WRITE ACCESS". The user of the computer program and the

user's classification (authority to access data) have the same

restrictions as a user directly accessing the data and the

protectzon of the data will be tested by having both authorized

and unauthorlzed users run the programs that will request the

data. The owner will also access the data through a computer

program to read and write in the data set.

REV. B

-166-
REQUIREMENT 90 CLASSIFIED DATA ACCESS

SOURCE 1 . 4/2 . 8.2

DESCRIPTION

Access to classizied and proprietary data shall require

stringent user identiZication.

Any unauthorized attempts to access this data shall be

reported to t_e system administrator by the IPAD system.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The unauthorized access security feature of IPAD will be

tested by attempting to access classified and proprietary data

wlthout authorization. Check that the system reports these

attempts to the system administrator.

REV. B

-167-
2.3.1.b System Administration

The s_stem administrato_ is a designated person or

organization recognizable by IPAD who is responsible for

exercising control over the IPAD information bank. The system

admanistrator will have special privileges. He will be permitted

quick and easy access to the IPAD system and be capable of

performing tasks available to no other users. Written IPAD

procedures will Zully descriDe the functions and authority of the

system admu_nistrator.

The system administrator may delegate control of selected

£unctions to other persons or organizations. These delegated

persons may likewise delegate protions of their control to other

persons or organizations.

REV. B

-168-
REQU IREME_NT 91 SYSTEM ADMINISTRATION

SOURCE 1.4/2.7.1, 1.3/3.1._.1, SOW/5.2.1.2

D_SCR IPTION

The IPAD system Imast accommodate the special requirements of

system administration. The IPAD System Administrator is a person

or organization responsible tot exercising control over the IPAD

system and information Dank. This control includes system

parameters, distribution of functions, data structures, and

security. The system must recognize the authority of the IPAD

System Administrator (s) as he accesses the system and allow him to

perform his functions.

It sI_all be possible for the IPAD System Administrator to

delegate control of selected £unctions to persons or organizations

designated by him. Such delegated control shall permit the

further delegation of control.

The IPAD System Administrator (s) must be able to access the

IPAD system quickly and easily--more so than the normal user. The

system must recognize his authority and allow _ to perform tasks

that other users cannot. Written procedures must fully describe

t_e functions and authority of the IPAD System Administrator (s).

ABSTRACT OF THE ACCEPTANCE CRITERIA

In two parallel tests, the System Administrator and a regular

user should each access IPAD and attempt to perform the system

administration commands. The System Administrator should obtain

access to the system more quickly and should be able to perform

all commands. T_e otter user will De tested to ensure that he is

r_ricted from the use of System Administrator commands. The

test should verify that the System Administrator is able to

authorize t_e use of selected system administration commands for

another user who can successfully use these commands. This user

should then authorize the use of a subset of these commands to

still another user or organization.

Note: Commands tested will include assignment of permission and

access codes and assignlnent of data set approval status.

REV. B

-169-
2.3.2 Information Management Tools

IPAD capabilities shall be provided to enable the user to

maintain data in the IPAD information bank and to perform data

transformations. Maintenance features include data updating, data

restructuring and data reformatting. File maintenance

capabilities are also provided. Files may be created from data in

the IPAD information bank or data from files may De inserted into

the IPAD data base. Command sequences for creating or decomposing

files may be saved for subsequent execution.

A capability will De provided to enable a user to compare two

data sets, to find out the difference between them and to get

n_aningful diagnostics in return.

Utility programs s_all De provided to perform arithmetic and

logical operations on selected data. Functions available shall

include conversions of data, scaling, summing, Boolean operations,

linear algebra, numerical differentiation and integration of data.

IPAD will provide for mapping IPAD element names to variable names

used in user programs. (See figure 2.3.2-I.)

REV. B

-170-
I'-'-

:=) 0

I.U

O..

-J

_J

UC_

t

REV.B

Z

z C)

(_ C,O

I--- czC

C) CZ)

LI_ (.-3Z

Z I-- Z _

Z

LLJ

i,i Z

I--- Z

Z_

MMM

-171-

L

=300

l--

_JE

GJ

c.- 0E0

4-

e-!

,4

_J

Qri,
REQUIREMENT 92 DATA UPDATE AND TRANSPORMATION

SOURCE SOW/5.2-I._

DESCRIPTION

T_ following update and transformation capabilities shall be

provided :

a) Altering existing values and data structures, adding new

data structures and values, and deleting old values and

data structures.

b) Restructuring existing data by means of special

commands, wltnout loss ot existing content.

c) Creating a file from information in the data base with

data format specification by the user extending to the

bit lewel.

d) Decomposing a file and inserting information into the

data Dase with data format extending to t/%e bit level.

e) Saving command sequences used to create or decompose

files for subsequent execution.

_) Creating files for transfer to an external medium in any

national standard, e.g., binary, BCD.

ABSTkACT OF THE ACCEPTANCE CRITERIA

The data update and transformation capabilities will be

tested by the following procedure:

a) A data set wall De constructed containing data

structures and data values. The appropriate utility

will be exercised to add, delete and modify existing

data values and structures. The data will be displayed

for purposes of verification.

b) The IPAD special commands for restructuring existing

data will be applied to the data set in a to restructure

it. Again, data will be displayed for verification.

REV. B

-172-
c)

d)

e}

f)

Define a file to the bit level and create it from the

data set in a) using the appropriate IpAD utility.

Reverse the process in c) to create another data set.

Save the command sequence from c) and use it to create

another Zile. Compare for verification.

Create a file in eac_ National Standard supported by

IPAD using techniques of c) Successfully transfer the

file to an external medium.

REV. B

-173-
REQUIREMENT 93 DATA TRANSFORMATION

SOURCE I. 3/4. _. 3, I. 3/_. _. 2

DESCRIPTION

IPAD shall provide the means to automatically present data in

the correct Zorm expected by the calling program or user. Some

examples are: unit conversions, coordinate transformations and

user supplied transformations.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The following will be checked to test the transformation

capabili ties:

a) IPAD's ability to perform unit transformations.

b) The ability to perform coordinate transformations

between rectangular or oblique cartesian, polar and

cylindrical coordinates.

c) The ability to perform transformations on I, 2 or 3

order tensors.

d) The ability to perform transformations according to a

user specified formula.

(e) The ability to perform transformations defined by user

supplied code (analogous to a Fortran function or

subroutine) .

REV. B

-17_-
REQU IR/KMENT 94 PROGRAMS AND DATA SET COMPARISON

SOURCE F3/3.1, SOW/5.2.3, SOW/5.1.13, 1.4/2.5.3

DES_IPTION

IPAD will compare two or more programs or data sets for

physical differences and infozm the user of differences with

meaningful diagnostic messages. T_e comparison shall cover:

a) Data that was inserted (or deleted) in one data set or

program al_ not in the other

b) Taking a) into account, the remaining data items taken

in sequence are checked for those items that are

dif£erent.

c) Verification that two data sets are identical. When two

items differ, it shall be ascertained whether or not

they are real numbers (in single or multiple precision.)

If they can be interpreted as real numbers, they shall

be considered identical if the absolute values of Doth

n_L_ers are less than a user specified value or if the

relative difference of the two numbers is less than a

second user supplied value.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The compare utility will be subject to the following tests:

a) Compare two known identical programs using the compare

utility.

b) After changing part of one of the programs used in a),

test the ability of the compare utility to recognize and

report the changes accurately.

c) Check t_at t_e user interface to the compare utility is

acceptable by means of a user survey.

d) Compare two sequential binary tiles of mixed data (real

numbers, integers, text, packed integers), in which all

information except the real numbers is identical in the

-175-

REVo B
e)

two files but the real numbers differ to varying degrees

in value.

Same as d)except for two BCD files.

REV. B

-176-
REQUIREMENT 95 MATHEMATICAL OPERATIONS

SOURCE SOW/5.2.3, 1.t_/3.3.15, 1.3/4.5.1

DESCRIPTION

A set of utility programs shall be provided to perform

arithmetic and logical operations on selected data. Functions such

as unit conversions of data, scaling, summing, Boolean operations,

and linear algebra operations shall be included. Other functions

such as numerical differentiation and integration of data arranged

in tabular form are frequently performed by engineers. In

general, these operations can be descriDed as arithmetic

operations on columns of a table.The set of operations shall be

open ended.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The system data manipulation capabilities ; unit conversion,

scaling, summing, sorting, boolean operations, linear algebra,

n_nerical differentiation and integration and table or array

operations will De tested for accuracy and user acceptance. This

will De doi_ by building a set of test data and problems and

having a range of users use them to evaluate the data manipulation

capabili ties.

-177-

REV. B
2.3.3 Computer Progra,u Library

The computer program library shall consist of programs in

source or executable forms. The programs may be supplied by the

u_er or generated by software processes (e.g., compilation).

Program inputs and outputs may be IPAD controlled, i.e., I/O

content below data set level is controllea by the user program.

Insertion and deletion of programs shall be straightforward

and ,machine independent so that a company may insert its own

programs. IPAD user aids will be made available to facilitate the

interfacing ot existing aerospace computer programs with each

other.

Program descriptions and keyword lists may be entered and

n_de available for subsequent query. (See figure 2.3.3-I.)

REV. B

-178-
I--- Z

ILl

C_

UJ

..Jo

REV,,B

l'--

t.O Z

,,:Z:

o

I--

,,.,,.. O

U-ZM

Z0

I--

CL

GO

L_0

0Z

I--0 _:_

I_-__0

n.,," I_ _' U_I U_I

I_ _" ILl I--- O0

<:_ I_ZZ

I=--4_ I_

•:_ t_> .:_ .:C .:_ 0 ID_ 0 0 0

0_ I.I_l r_ r_

Z

z_

Z0_0

Z_00

cq cq cq

-179-

u'l

C::

"m

m,,-

r.,

,.--I E

S.- 0

SO,.

S,.

O_

.._E0

(..)I

0'3

r,- i r-
REQUIREMENT 96 PROGRAM LIBRARY

SOURCE 1.3/5. I, SOW/5.2.1. I

DhSCRIPTION

IPAD shall provide for a single application program library

whxcn shall consist of programs in either source or executable

_o_n and which have oeen directly supplied by the user or

generated Dy software processes.

Standards for program integration, data handling, and program

catalog procedures shall De developed. The IPAD system shall

check programs for con/ormity to these standards and shall not

allow _nsertion of programs which do not meet these standards.

The IPAD computer program library shall be subject to the

same requirements for security, integrity, version control, and

access control as generally applied to the IPAD information bank.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The IPAD program library will be utilized and tested

tr,roughout t_e test period. A procedure to test the library will

_nclude lo_ding and accessing programs by t_e user and by the

system. T_e security and integrity requirements and access

control wall be tested in conjunction with those general

requirements for the IPAD information ban_. The test procedure

will include accessing programs from libraries other than IPAD.

REV. B

-180-
REQUIIt_MENT 97 EXPLICIT AND IMPLICIT I/O

SOURCE 1.3/5.3, SOW/5.2.1, SOW/5.2.1.5

DESCRIPTION

It is required that IPAD support several modes of program

interfaces with the informatiun bank. The primary purpose is to

make provisions which allow s_nple installation of existing

application programs into IPAD.

IPAD must provide for installation of the following types of

application computer program:

Programs for which the contents o_ all input and output

data sets are defined to IPAD and for which all data

management is "implicit" (IPAD controlled).

Programs for which t/le contents of some input and output

data sets are defined to IPAD, and for which IPAD I/O is

both "implicit" {IPAD controlled) and ,'explicit" (user

program controlled). If data reformatting is needed for

"explicit n I/O, IPAD shall support preparation of a data

translation program.

Progral-q for which the contents of input and output data

sets are undefined to IPAD, and for which all data

management is "explicit t (user program controlled).

The use of the terms implicit and explicit I/O should be

interpreted as follows:

L_LICIT input/output action to and from a data set is

totally under the direct control of IPAD. Note, query

is possible at the level of data elements.

EXPLICIT input/output action to and from a data set is

under control o£ the user program. IPAD is responsible

only for the data set as a unit. Query is possible at

the level o£ data set and in general, IPAD is not

capable of interpreting the content of any data set

handled in this way.

REV. B

-18 1-
_STRACT OF THE A%_EPTANCE CRITERIA

The ability of IPAD to support the various modes of program

input and output will be tested in conjunction with other tests

and with standalone tests as required.

The procedure will include the installation of application

programs with implicit I/O, explicit I/O and a combination of

implicit and explicit I/O. For implicit data, queries will be

made at the element level. Tests will be for user acceptance and

correct operation.

REV. B

-182-
REQUIPd'_4ENT 98 PROGRAM IDENTIFICATION AND DESCRIPTION

_OURCE F3/2.2, SOW/5.2.1.1

DESCRIPTION

IPAD shall provide t_e means for users to enter keywords and

standardized descriptions of their programs. These descriptions

shall be available Zor subsequent query.

ABSTKACT OF THE ACCEPTANCE CRITERIA

Users will test the capability to enter keywords and

descriptions oi their programs in both batch and interactive

modes. Users other than those who input the information will then

query the information by entering the keywords. The feature must

operate correctly and it most be responsive to the users'

satisZaction in interactive mode.

REV. B

-183-
REQUIREMENT 99 PROGRAM INTERFACE

SOURCE SOW/5.1.27, 1._/3.3.19

DESCRIPTION

IPAD software shall include features and user aids to

facilitate interfacing existing computer programs with each other.

Such Zeatures shall make use of IPAD data transformation

facilities (requirement 93). IPAD shall also supply user aids to

facilitate integration of existing programs into IPAD. Such aids

1_y include automatic identification of I_D stat_ents in source

progr_us and assistance in converting them to an IPAD compatable

zorm.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Existing Boeing and ITAB member companies' design programs

will be used to test the features and user aids for facilitating

the interfacing of existing programs with each other and

integrating r/%em into IPAD. The functional capabilities such as

detection of I/O statements of these user aids will be verified

and user evaluation ot these features for ease o_ operation and

adequacy of support will be established.

REV° B

-184-
REQUIP_MENT 100 PROGRAM INSERTION AND DELETION

SOURCE SOW/5.2. I, SOW/5.1.23, I °4/2.1.5

DESCRIPTION

insertion and deletion of programs in the program library

shall be straightforward and essentially machine independent so

that a company may insert its own proprietary programs.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A group of ITAB users wall insert and delete programs from

their companies in the IPAD program library. User opinion will

evaluate this capability for ease of use, operational correctness,

and machine independence.

REV. B

-185-
2.4 AUXILIARY/EXTERNAL SYSTEM INTERFACES

IPAD must be flexible in regard to hardware implementation

and computing facility. IPAD must be able to share data with nonIPAD systems and to safeguard and control non-IPAD data while in

the custody of IPAD. Existing telecommunication standards will be

used to facilitate communication between computing systems.

Support software and user aids will be provided to facilitate

transfer of programs, data base, etc.

2.4.1 Bost/kemote System Interfaces

The requirements regarding IPAD's interface with the host

system and IPAD,s interface with remote systems are specified in

thls section. IPAD is to be flexible in regard to hardware

imple,_entation and computing facility. IPAD shall permit access

to and receive data Zr_a non-IPAD systems using exasting standards

whenever possible. (See figure 2.4.1-I. )

REV. B

-186-
I

i=-

,:,,,,

linE

,.J

C_

REV.B

GO GO

I:_ =E

ILl

Z >--.

,=_ C,O

GO r._ v Z

ILl0 I--"

I--" ,---,0

Z GO

GO

I-=- _" ILl

_o4_ 0 0

0

<_m_mm

- 187-

°r'-

m,-

r,j

m=

4-L

e=EOE

w_0

-r-!

%..

or== IJ=
REQUIPJ/_ENT 10 1 HOST COMPUTER (S)

SOURCE SOW/5.3, SOW/5.3.2, 1.4/3.5.2, 1.3/3.4.2

DESCR IPTION

IPAD must be able to operate on either a single computer or

on a distriDuted computer complex. The computing facility may be

dedicated solely to IPAD use or IPAD may execute as part of a job

mix. A computer complex may consist of CPU's with shared data

storage units processing under single or multiple control and may

include remotely connected computer Zacilities. The user

interface to IPAD must be independent of the computing complex

configuration alrnougn it may be restricted at some parts of the

complex.

ABSTRACT OF THE AL_EPTANCE CRITERIA

A user opinion sur_ey of the ITAB members will be used to

evaluate the design of IPAD with respect to the ability of IPAD to

operate on a single computer or to be distributed on a computer

c onlpl ex.

The Independence of IPAD with respect to job mix or dedicated

facility will be tested by randomly selecting three functional

tests for requirements to be rerun in a different environment.

(I£ they were run on a dedicated IPAD facility, they will be run

as part oz a job mix and vice versa). The results will be

compared with the original tests.

The user interface will be tested on all available _ardware,

including remote access, evaluated on the basis of invariance over

hardware. All deviatlons will be noted and the IPAD engineering

team will decide which are acceptable.

REV. B

-188-
REQUIREMENT 10 2 COMMUNICATION STA_ARDS

SOURCE 1 .3/3 . %.3 .1

DESCR IPT ION

Communications standards should be selected to facilitate

IPAD's communication between computing systems and between

aerospace companies. Existing standards should be used whenever

possible.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A user opinion survey will be conducted for the ITAB members

to evaluate the IPAD communications standards. The standards must

be judged acceptable by a majority of ITAB members.

REV. B

-189-
REQUIREM. ENT 103 ACCESS BY OTHER SYSTEMS

SOURCE I. 3/3. @. I, _. 3/3. _. 3

DE SCR I PTI ON

IPAD shall permlt access to all uesign data under IPAD

control from non-lP_D systems. Data produced on non-IPAD systems

shall be received into any IPAD system. Such data shall have

appropriate safeguards and controls while in the custody of IPAD.

Conuaunications wit_ non-IPAD slstems will be through standard

formats and subject to IPAD security control.

ABSTRAL_f OF THE ACCEPTANCE CRITERIA

A special sample oI test input data will be entered at a

remote site. The data will have security provisions. Legitimate

attempts to access this data will be made to ensure that IPAD

permits data access from a remote site. Attempts must also be

z_de to illegally access and change t_is data to test IPAD's

capability to sazeguard ddta in its custody.

REV. B

-190-
2.4.2 Software Interfaces

IPAD shall be able to conm_nicate with existing software

systems external to IPAD and facilitate transfer of program

modules, data Dases, etc., between IPAD installations. Support

software and user aids _lall be provided for such purposes. (See

_ igure 2.4.2-I.)

REV. B

-191-
.=p

i,i

Q

REVoB

,-_- (...}

i,iI,t

.=._

,=_ f.z'}

cz)

c/)

>-.

Cz)

c:_ i,t

L_ LL_ •-1- C/) 0

I--- 0

,-.--I ,---I

,--4

-192-

u")

c-E

G.}

OfJ

(-..

I- 0!

If-.

I.i_
F_QUIP_MENT 10_ CLI_IUNICATION WITH OTHER SYSTEMS

SOURCE 1 ._/_ ._ .3

DESCR IPTION

IPAD must nave the ability to communicate with existing

software systems external to IPAD in data forms sufficiently

accurate to preserve the useability and accuracy requirement

speci£ied in requirement 110.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Data generated on an external system will be extracted and

inserted into the IPAD inZormation bank. This data will then be

extracted from IPAD and returned to the external system and

compared with the original data. The original accuracy must be

preser_d. In addition, the communication must De direct and noncumbersome in the opinion o£ the testers.

REVo B

-193-
REQUIREMENT 105 PROGRAM AND DATA TRANSFER

SOURCE SOW/5.1.26, I .4/3.3.10

DESCRIPTION

IPAD shall facilitate transfer of program modules, data,

etc., between IPAD installations. Support software and user aids

shall be provided to perform such data transfers and to account

for ditzerences in computer word sizes.

ABSTRACT OF THE AL_EPTANCE CRI_RIA

To test this capability the following procedure will be

followed :

a) Progralns will be transferred from one installation to

another, then back to the first, and verified to be

identical using the IPAD compare utility.

_) When the programs are transfered to the second

installation, test data (defined data sets) will also be

transfered and the programs executed and checked to

verify t/%at execution was performed correctly.

REV° B

-194-
2.5 GENERAL SYSTEM CAPABILITIES

The general system capabilities in the area of performance,

security, reliability and flexibility are discussed in this

section. Regarding performance, response time must be adequate,

system capabilities are only limited by the hardware configuration

and adequate accuracy in storing and manipulating numeric data

must be provided. Performance monitoring tools are provided to

aid the system administrator.

The IPAD system shall provide fail-safe security to prevent

the disclosure oZ anformation which may be detrimental to National

Securlty or the propraetary interests o_ the user company. The

r_lia_ility and availability of the IPAD system are important

considerations but should not be limiting factors in the system's

use£ulness. IPAD shall be designed to De flexible when adapting

and interfacing with indivldual installations.

2.5.1 Performance

The performance capabilities of the IPAD system a_e given in

this sectlon. System capacity is to be hardware configuration

limited rather than software limited. Very large capacities are

envisioned. Tools for performance monitoring are to be provided

Zor the System Administrator. T_e ability to store numerical data

w_th at least ten significant digits will be provided. Various

accounting progr_,ns wall be provided for project management,

reporting and statistics. (See figure 2.5.1-I.)

REV. B

-195-
I--"

Z

W

__1

_J

I--

-_1

Z

0

I,_

Z

Z

(.I) I_I_I

(_0 _- ,_ _ Z

Z I-- _ _

_ _ U-- U

I-- 0 1_- _ _ 0

ILl (,--) I_- (-.)

Z _ _- _"

0 I-- U_I W _ i,l

t_ I-- I-- I_LJ

0 0 0 0 _

I--

I._'_£/')_ I.L _ _ X

-.J LIJ

-196-

REV. B

_=,

S,.

U

E

L

n

m

_J

L
REQUI_ENT 106 RESPONSE TIME

SOURCE I. 4/3. I. 2, SOW/5. I. I

DLSCRIPTION

IPAD shall provide fur adequate respunse time. Guidelines

£or desirable response times wTLich should be sought are as

tollows.

Response time is defined as the time elapsed between the last

input by the user and the first character displayed by the

computer.

The response times given are tt_se for which the user will be

comZortable and continue to utilize the terminal for his purposes.

(15 to 60 seconds)

Some log-on/log-off functions where the user is familiar

with the delay.

Single enquiries where the user is familiar with the

delay, preferably cued by a messaged from the computer

within two seconds acknowledging the command.

System failures and recoveries, preferably cued, where

possible, by a ,message from the computer within two

seconds warning of the delay.

Loading of programs and data Zor execution and

prooessing, preferably cued by a message within two

seconds acknowledging the command.

Restart from a prior session.

(4 to 15 seconds)

Low key enquiry dialogue possible but awkward.

Intense creative dialogue not possible.

(2 to 4 seconds)

REV. B

-197-
Complex enquiries where continuity of thought is

necessary.

Initial acknowledgment by the system that it is

"listening."

Error messages.

(Less than 2 seconds)

Intense creative dialog.

AcKnowledgment Dy the system t_at a command has been

received.

Response to a paging request through a keyboard.

(Less than I second)

Response to a paging request using a light pen.

Development oZ geometric entities.

(Less than 0.1 seconds}

Brightening of characters from a light pen selection.

Appearance of a line when using the light pen as a

drawing stylus.

Appearance of a character on a CRT keyboard.

The critical threshold for effective creative dialogue is two

seconds. Beyond two seconds mental efficiency degrades rapidly.

Delays beyond fifteen seconds should De structured to relieve the

user of both mental and physical captivity. Experienced users

will prefer faster response times.

Deviations - permissible deviations in response times depend

upon the activity. Response times less than two seconds should

not vary by more than I00_.

ABSTRACT OF THE ACCEPTANCE CRITERIA

REV. B

-I 98-
be response times in the interactive l_de will be monitored

and recorded by activity throughout the test period. Acceptance

will De based on user satisfaction and t_e response times that are

recoraed. User opinion will be solicitea.

REV. B

-199-
REQUIREMENT 107 "SYSTEM WORKING" SIGNAL

SOURCE 1.4/4.1, SOW/5. I. 1

DESCRIPTION

If an IPAD command, or application program execution requires

more than x seconds of time, the system shall display a signal

every x seconds (flashing) to indicate tot he user that the

computer is working. The user may speciZy x but the default value

shall be 5 seconds.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The "system working" signal will be tested in con_inction

with other tests both for user specified ("X") seconds response

and the default (5 seco,_s).

REV. B

-200-
REQUIREMENT 108 SYSTEM CAPACITY

SOURCJ=; SOW/5.1.1, 1.4/4.6.1, 1.4/2.1.2

DESCRIPTION

The IPAD System capacity shall De considered to be "hardware

configuration limited" with no actual restriction placed on the

IPAD System.

Capacity here reZers to computer memory capacity, size of

information banK, the number of interactive terminals

simultaneously in use, etc.

Explanatzon: The capacities envisioned are very large. For

example, t_e number of interactive terminals simultaneously in use

is expected to be very much greater than 100, likely to exceed

400, and may grow to several thousand.

ABSTRACT OF THE ACCEPTANCE CRITERIA

T_e capacity oi t_e IPAD system must be proven to be limited

only by hardware configu/ation. In addition to saturating the

acceptance test hardware configuration, slmulation techniques will

be used to test this aspect of the system. Procedures for

developing the simulation models must be prepared and approved for

each aspect of system loading prior to te_cing this requirement.

REV. B

-201-
REQUI_NT 109 SYSTEM PERFORMANCE MONITORING UTILITY

SOURCE SUW/5.2.1.7, I._/_.3.1, 1.4/2.9.2, 1.4/4.3.2,

I .3/3.3.5.3

DESCRIPTION

A complete set of software tools shall be provided for

perzormance monitoring by the System Administrator. The tools

shall include a software probe capable of gathering a complete set

uz performance parameters over the entire spectrum of IPAD

activities so that fundamental software and hardware activities

(aata transfers, d_sc accesses, etc.) can be related to user level

actions (e.g., speciflc commands and operands). The probe shall:

a) Be operational in a production environment and shall not

seriously perturb system resource utilization by more

than 5 _.

b) Be capable of producing statistical summaries as well as

a complete c_ronological trace of all or any part of the

measured IPAD performance parameters.

c) Have a '_ode;" e.g., inactive, summary, or complete

trace, that is dynamically selectable by the System

Admini str ator.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The System Administrator shall demonstrate the software tools

for system performance monltoring throughout the acceptance

testing, it must be shown that the features described in this

requirement are available and t_at the software probe fulfills the

monitoring functions described. The testing procedures must be

developed for the monitor_/ig aspects once they have been defined.

Several hardware and software conditions will be simulated to test

as broad a spectrum of the IPAD system operation as practical.

REV. B

-202-
RKQUIP_MENT 110 NUMERIC ACCURACY

SOURCE I . 4/4 . 4 . I

DkSCRIPTION

The system shall nave the ability to store numerical data

with at least 10 significant digits and to perform arithmetic

operations wit/% no additional loss of accuracy other than that

i_q_)sed Dy purely mathematical considerations.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The s_nificant digit accuracy (at least 10 significant

dlgits) will be tested Dy several users by comparing computational

results wlth _own accurate results (Zrom other computer programs

outside of IPAD or calculator computations).

REV. B

-203-
RLQUIREMENT 1 11 USAGE ACCOUNTING

S_JRCE 1.4/3.31.14, 1.4/3.3.11, 1.3/3.31.7, SOW/5.1.15,

SOW/5.2.1.6

DESCR IPT I ON

IPAD shall provide t_e capability of determining how data and

system resources are used. This shall be in the form of a data

base audit facility add a system resource accounting facility.

The Zollow_ng capabilities shall be included in the data base

audit Za cility:

• Determine t_e origin of data: Originator I.D., date of

creation, trace of antecedents Zor data sets.

- Most r_cent date of reference to data.

• I.D. of _ii recent users Within installation specified

time.

• Count o_ the number of accesses to data.

• Count of unauthorized attempts to access data.

T_e system resource accounting facility shall include:

• Processor time Zor all jobs.

• Memory utilization _Qr program memory and secondary

storage (disks, tapes, etc. )

• Permanent file utilization.

These facilities will be used in support of utilities such as

pro3ect m_nagement aids, usage statistics reports and report

generator s.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The data base audit facility will be tested by requesting

reports on data set accesses to include:

-204-

REV. B
a) Origin of data (originator I.D., etc.)

Most recent date of access

c) _°D. of most recent user

d) Count of number of accesses to data

e) Count of number of unauthQrized attempts to access data.

In addition the system resource accounting facility will be

tested by requesting reports to include:

a) Processor times for jobs.

b) Utilization o_ program memory and secondary storage.

c) Permanent file utilization.

The reports will be generated in conjunction with other

acceptance tests and co,,pared to known information where possible.

Reports must De accurate to within ÷_5% when compared to known

operation.

REV. B

-20 5-
2.5.2 Security

The IPAD system is to be fail-safe in security. Means will

be provided to prevent the disclosure o£ information which would

be detrimental to National Security or the proprietary interests

of the user company. System failure must not result in the

degradation ot IPAD security controls. (See figure 2.5.2-I.)

REV. B

-206-
i

I--- z

iii

5-

ill

lira

n_ n

--JI

--J

Ii0 !

REV.B

ZO

I---

l.IJ

I'-- O

l::}.. ZO

I--- 0

U__

Z_ 1=_

I.LI (.-)

>..- O0 I._

ILl

I_ I.L..--..I

O0Z

n.-" I 0

Q_ .__1 0 ,'_ I_

_:_ ,_:

L.I_Z

(_0 P--, i _

,,!. ,:,fi, i i i i,,,i

-207-

4-}

e-E

G,I L

,,ft.. LU

G)I

.r..

Jlm,
REQUIR2/W.ENT 112 PROPRIETARY INFORMATION PROTECTION

SOURCE 1._/2,8.2

DESCRIPTION

IPAD shall provide t,_e means to prevent the disclosure of

information which would be detrimental to the proprietary

interests of the company.

This may be dchieved through security codes assigned to

individual users. These codes will address the various levels of

sensitivity o_ protection required of different information. The

number and character of the protection levels may be optional to

satisfy individual company requirements.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Test the IPAD system provisions to prevent disclosure of

proprietary information, A group of users for a typical company

will be identified having the following types of data access

control: I) Jnclassizied data only; 2) Company limited data; S)

Company proprietary data; _) 3oint venture proprietary data; and

5) third party proprietary data. Both valid and invalid attempts

to access data sets with corresponding security will be made to

test the proprietary inzormation security of IPAD.

REV. B

-208-
_EQUIP_MENT 1 13 FAIL-SAFE SECURITY

SOURCE I .4/2 . 8 .2

DESCRIPTI ON

Failure of the IPAD System shall not result in a degradation

of the security controls provided by the system. The system will

be fail-safe from t_e security viewpoint.

ABSTRACT OF THE ACCEPTANCE CRITERIA

A n_r (determined in testing) of deliberate failures will

De effected without warning when data sets or data areas

designated as "classi£ied m are in the IPAD system. Separate tests

of failures involving the IPAD system, the host operating system,

and the hardWare co,_onenns will be conducted. The security

controls rot classlfied and unclassified data will be checked by

both authorized and unauthorized users immediately after failure,

and again, after normal operation is restored. The security

controls must De maintained during and after system failure.

REV. B

-209-
R_QUIREMENT 114 NATIONAL SECURITY

SOURCE 1.4/2.8.2

D_SCRIPTION

IPAD shall not preclude operating in accordance with the

current Industry Security Manual For Safeguarding Classified

Information (DOD5220.22-M).

ABSTRACT OF THE ACCEPTANCE CRITERIA

The IPAD system must be checked to verify that it can operate

in accordance with the current DOD security manual for industry.

The host operating system and the IPAD system (including the

distributed processing area) will De secured in order to enter and

process data sets and data areas classified by national security

regulations as confidential, secret, and top secret. Authorized

and unauthorized users will then attempt to access the data.

REV. B

-210-
2.5.3 Reliability

The reliability and availability of the IPAD system are

important considerations. They should not be limiting factors in

the system's useZulness. (See _igure 2.5.3-I.}

REV. B

-211-
F--

z

O

W

._J

i

REV. B

I--- F-,-

L.J

c::: >"

L.U

I--- F-.-

oO cz')

(i) (/)

u5

,,,

l.j_if-z) _ _ ._I

"-" X

• I._ i_.-

M M M M

-212-

u'1

r--

E

L

tw...

r-,,.,

,.r--

!

OJ

S,-

or-.

I,
REQUIREMENT 115 SYSTEM RELIABILITY

SOURCE 1 .4/3 • 1 .3

DESCRIPTION

The reliability of the IPAD System, hardware, and operating

system will be such t_at system reliability need not be a specific

planning consideration for IPAD users or the system administrator.

ABSTRACE OF THE ACCEPTANCE CRITERIA

The reliability of the IPAD system, hardware and Operating

system shall be monitored for a _ week period aligned with the

test o_ requirem_,t 116--IPAD System Availability. The system

shall Zunction properly. Any error detected in calculations, data

management or any function of the IPAD system, hardware or

operating system shall be considered a £ailure to meet the

rellability requirement.

REV. B

-213-
REQUIREMENT 116 SYSTEM AVAILABILITY

SOURCE I .4/4 .2.2

DESCRIPTION

During any consecutive four week period, the minimum average

user availability for the IPAD system shall be 97.5_ of the total

dvailaDle host computing time allocated to IPAD. The IPAD system

is considered available when a user is able to productively

pertozm his desired objectives.

ABSTRACT OF THE _CCEPTANC£ CRITERI_

The IPAD System scheduled availability will be monitored for

a 4 week period. This test will De conducted concurrently with

all acceptance testing. The system availability shall not be less

tf_n 97.5_ of the scheduled availability. During this test, the

sclleduled availability will ,lot be less than 8 hours per day.

REV. B

-2 14-
2.5.4 Flexibility

IPAD is designed to De flexible in adapting to and

interfacing with individual installation. Modular functional

capabilities, specialized interfacing capabilities, and variable

parameters are provided to aid flexibility. {See figure 2.5.4-1.)

REV. B

-2 15-
F--

:,..-

n.,-

.._I

LL.

C/)

C_C

I,I

Z i--

___ W

i,l t-_

_ I---

_,,_ "_ _ - ,.'5,

i.._ c,-I *

I

-216-

u")

e-.

.E

m,-

*r--

*r'-

x

!

_J

f,,-

*r

i,

REV. B
R UIRm N'r 117 MODULAk DESXGN

SOURCE I._/3.5._, 1._/2.1.5

DESCRIPTION

IPAD shall be designed so that t_e ft=Ictional capabilities

are modular, allowing a company to gradually adopt IPAD to their

z_eeds. Specialized interfacing facilities shall be provided by

IPAD to aid users in designing interfaces to systems outside IPAD.

ABS'I_AL_f OF THE ACCEPTANCE CRITERIA

An initial version of IPAD will be brought up, including only

the minimum IPAD functions and data set management. A test must

show that this software c0nfigu_ation is operational.

Additional _unctional capabilities will De added one at a

time, with complete system testing after each addition. Functions

added and tested will include process definition, data element

management, project definition, and sc/%edule control.

The IPAD facilities to aid design of interfaces to systems

outside of IPAD will be tested for two external systems: I) IPAD

geometry data sets to be interfaced to a remote release system and

2) IPAD cost data interfaced to an external management system.

The facilities to support interface design will be evaluated for

ease of use and adequacy.

REV. B

-217-
REQUIREMENT 118 SYSTEM PARAMETERS

SOURCE 1.4/2.1.6, 1.3/3.3.5.3

DESCRIPTION

Parameters aze directly or indirectly associated with many

requirements. Such parameters would include the period of time

for messages to be auto_tically erased, the arrangement for user

appointments, etc. Values for these parameters shall be easily

set by an individual znst_llation.

ABSTRJ_CT OF THE ACCEPTANCE CRITERIA

Tests shall be made to ensure that an individual installation

has the ability to specify all variable IPAD system parameters and

veri£y that these parameters operate correctly. Tests shall also

De made to determine that the installation is able to easily

change these parameters. Where a parameter is limited to a range

of values, it must De verified that an invalid value may not be

speci£ied, but that t_e upper and lower bounds to the range are

acceptable.

All _rdxiaDle IPAD system paran_eters are tested and

_nitialized to valid default values if unspecified by the

znstallation, and that the parameters so set are tested to ensure

that they operate correctly.

REV. B

-218-
2 .b GRAPI:_ CS

Gra_ics standards rot communicating between devices will be

establ_sbed. Graphic equipment interface so£tware will be

provided wlthin IPAD to accommodate a prescribed assortment of

graphical equipment.

Z.6. I Graphics Standard

A standard graphics software package will be provided

consisting of lower level primitive routines which will minimize

machlne dependence and will be capable of supporting a wide range

oZ graphics devices. These basic functions will allow development

o£ sophisticated graphics related applications.

IPAD shall provide both data explosion and data compression

techniques for converting data fr_a the IPAD standard formats to

the £ormat required by dumb and intelligent type terminals,

respectively. Compression techniques shall also reduce the amount

of data sent over communication lines. (See figure 2.6.1-I.}

REV. B

-2 19-
Z

Id.l

I,.LJ O

l.l.J

,.:C

.,_I

...I

l.L.

REV.B

_M

-220-

U5

c"

s::

_J

S,-

t_

C}"

(U

m,.'

e-U

,,i.-.

I,..

CDI

C_

S,-

.m.-

l.L.
REQUIREMENT 119 GRAPHICS PRIMITIVES

SOURCE BCAC-NASA

DESC_ IPTION

A stanaard graphics software package consisting of primitives

which embody the concept of device independence will be provided

in IPAD (si1_ilar to subroutine package being defined by SIGGRAPH).

Examples of functions to be provided include:

I. Line drawing

2. Text drawing

3. Segments

4. View transformation

5. Attributes

6. Control

7. Input

ABSTRACT UF THE ACCEPTANCE CRITERIA

An application program which uses the graphics software

pr_aitives will be written and tested using a variety of devices

to veriZy that the grapILlcs software package functions correctly.

A user opinion survey will be used to determine if the

systems design meets the organizational specifications of the

requirement. The efficiency of the graphics primitives will also

be evaluated by the users.

REV. B

-229-
_EQUIREMENT 120 COMMUNICATION STANDARD WITH

NON-INTELLIGENT TERMINALS

SOURCE BCAC-NASA

DESC_IPT ION

IPAD shall establish standards for communication with dumb

graphics terminals, which recognize coordinate data only, and

provide for conversion of geometry data stored in IPAD's standard

geometry format prior to transmitting them to such terminals.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The IPAD standards for communication with dumb graphics

terminals will be evaluated during system design by a group of

users.

In testing, a data set containing geometric data in the IPAD

standard geometry format will be created. This data will then be

converted to the standard conununication interface format and then

transmitted to each type ot dumD graphics terminal supported by

IPAD to test the functionality and ef£iciency of the TPAD

conversion and transmission software.

REV. B

-222-
121 COMMUNICATION STANDARD WITH

INTELLIGENT GRAPHICS TERMINALS

S OUMC E BCAC-NASA

DESCRIPTION

IPAD shall establish standards for _unication with

intelligent grapb_ics terminals. Such standards shall be intended

to improwe response time. If required, IPAD shall provide for

conversion or geometry data stored in IPAD's standard geometry

format prior to tra,Lsmitting them to such terminals.

ABSTRACT 0_" THE ACCEPTANCE CRITERIA

During systems design, users will evaluate the IPAD standards

Ior c_muunication with intelligent graphics terminals,

particularly in respect to the goal of reducing response time.

In testing, the data set containing geometry data which was

czeated ior requirement 120, ACT I will be converted to the

standard communications interface format zor intelligent graphics

ter,_inals. This data wlll then be transmitted to each type of

Intelligent graphics termlnal supported by IPAD to test t_e

_unctionality and eZficie_cy of the IPAD conversion and

transi[_ssion software.

REV. B

-223-
2.6.2 Device Interface

IPAD shall provide i_erface software for a prescribed

assortment of graphical equipment. (See figure 2. b. 2- I.)

REV. B

-224-
l--- Z

LIJ

IJJ

0..

--I

..J

i,

Q

¢%1

LJ.J

C_

p--

LL0

OO

I,I

¢_)

LL

C_

LJ.J

p-. Z

I-..-i

(,,9

(._)

i---i

-Ic_

(..9

C,4

W

_M

4J

e- ULCUI

REV.B

-225-
}tE_UIKEMENT 122 GRAPHICS INTERFACE SOFTWARE

SOURCE I ._/3 . 1 . 1

DESCRIPTION

IPAD shall provide interface software for the following

grapaics devices :

Tektronics

VG3300

SC 4020

IBM 2250

763 Calcump

Flatbed plotter

Scanning units

Digitizer

Micro_ ilm plotter

Pro j ection devices

This interface software shall provide the transformations and

other capabil_ties requlred to ma_e the graphics software

independent of the graphics devices.

ABSTRACT OF THE ACCEPTANCE CRITERIA

Interface software for all devices listed below will be

tested either on-line or off-line as appropriate. Specific models

must be specified for those devices listed as general types.

TeKtronics

VG 3300

SC _020

IBM 2250

763 Calc0mp

FlatDed Plotter

Scanning Units

Digitizer

Microtilm Plotter

Projection devices

REV. B

-226-
2.7 GRAPHICS RELATED TOOLS

IPAD shall provide a variety of Zunctions to support CAD, NC

_nd related analyses. Tools shall be provided to construct and

display engineering designs and data plots. Animation techniques

shall be provided fur display of dynamic phenomena. Standard and

extended geometry formats shall De supported. Conversion

utllitles shall be provided to convert geometry formats to a

standard format for communication purposes.

2.7.1 Graphics Related Programming Tools

Graphics related programming tools shall be provided to allow

the development or sophisticated graphics capabilities from the

standard graphics software primitives. An animation package shall

be provided to display dynamic phenomena. (See figure 2.7.1-I.)

REV. B

-227-
I--- W

C_

_..I

..-I

UC2

I

C_4

REV.B

.=.J

f,...)

c:_ -..J

LzJ C)

_--0

I----

Z

LL.

CZ) IJ-I •--r- ,_ -T- l B

"-ri

_ C4

o

-228-

(I) L0

S. 0

04-)

E

rJ0

•r..L

_" °m-.

rd O" !

SU-
REQUIkEMENT 123 G_APHIC DISPI_Y O F NUMERICAL DATA

SOURCE 1.4/2.5._, SOW/5.1.4

DESCRIPTION

IPAD s_all include comprehensive capability fur conversion of

numerical data into graphical format such as: multiple x-y plots,

Par charts, contour plots and carpet plots.

ABS_ACT QF THE ACCEPTANCE CkITERIA

The IPAD capability to convert numerical data into graphical

zorI_t will be tested in conjuz,ction with other graphics

requirements as well as by a seperate operation. The primary

cansiderations are the user's ease of conversion and the accuracy

of the conversion. All graphic Zormats available in TPAD will be

tested.

REV. B

-229-
R_QUIREMENT 124 ANIMATION PACKAGE

SOURCE 1.4/3.4.3, SOW/5.2.4.2

DESCRIPTION

IPAD shall provide an animation package to help display

dynamic phenomena flicker free. The result will be either viewed

directly on a scope, ar generated on a movie film for later

display.

ASSTRACT OF THE ACCEPTANCE CRITERIA

_he animation package will be tested by developing an

animated sequence and viewing it on a scope and then generating it

on a movie film to De viewed off-line. Accuracy and quality oZ

the animation both on scope and on film will be the acceptance

criteria.

REV. B

-230-
_EQUI}%_MENT 125 GKAPHIC PROGRAMMING TOOLS

SOURCE I. 4/3. _. 2, SOW/5.2.4.1

DESCRIPTION

Graphic progranTning tools shall be provided through support

routines. These routines will allow development of a

sophisticated graphics capability from simplified building blocks.

The following functions shall be provided:

Superposition of text _orizontally, vertically, or at an

angle.

• Menu and message display.

Decoding of integer and floating point variables for

graphic textual display.

• Numerical data display with editing capability.

Change o£ drawing scale, two- and three-dimensional

windowing and clipping.

• Shading, hidden surface and line removal.

• Dynamic write protection for any part of the screen.

Ability to obtain hardcopy of screen contents (e.g., on

plotter or hardcopy unit attached to graphical display

device) .

• Grid and graph generation, including labels and titles.

Graphic INPUT (e.g., keyDoard, lightpen, function

button, digitlzer)

• Variety of dashes for Vector plotting.

• Variable plot intensity, including blinking.

REV. B

-23 I-
ABSTRACT OF THE ACCEPTANCE CRITERIA

•he graphic programming tools listed in this requirement will

be called from a selected pre-existing graphics program which uses

these options extensively. The results of running the program

using IPAD should agree with the results under non-IPAD usage.

The ease oi conversion will also be a test criteria. Program

efflciency in the IPAD enviro,_nent should at least equal its nonIPAD eZf iciency.

-232-

REV. B
2.7.2 Geometry

IPAD shall provide a wide variety of CAD/CAM geometric

entities for the construction and display of engineering designs.

A standard geometry format for communications shall be provided.

IPAD shall provide tools to define cutter paths utilization

CaD engineering design geometries and s_all also provide a utility

to convert the same geometry to APT geometry source format. (See

_igure 2.7.2-1.)

REV. B

-233-
l--

ILl

ILl

I.I-I

Q-

.J

-.JI

C/)

.-J 00

I--"

ILl

F--

,--5U

-234-

E

,L

O"0I

LL

REV.B
REQUIREMENT 126 DESIGN DRA2TING CAPABI/_TXES

SOURCE 1 .4/3 .

DESCRIPTION

IPAD s_all provide the following CAD entities :

PLAN FORMS IN ANY PLANE OF SPACE

• Polnt

• Line

• Circle or circular arc

• Fillet

• Ellipse

• HyperDola

• Parabola

• General conic

• Cubic spline

• Rectangle

• Triangle

• Hexagon

- E_t ity stri_

NON-PLANAR FORMS

• Cubic spline

• Surface of revolut£on

• Ruled surface

• Developed surZace (flat pattern}

-235-

REV. B
• Curve mesh surface

• Fillet suxf ace

• Surface intersection curve

• Draft curve

• Surface edge curve

IPAD shall further provide the following CAD functions:

FUNCTIONS SUPPORTING GRAPHIC DEVELOPMENT

• Break away IID_S

• Generate array oI entities

• Entity group

• Pattern of entities

• General notes

• Labels

• True position symOols

• Dimensioning (manual and automatic}

• Balloon labels

• 2D section properties

• 3D analysis

• Mirror entities

• Variable line fonts

• English/metric conversion

• Blan_/unblank

• Delete

• Detail magnification

• z c lipping/peeling

o View/dept_ modification

-236-

REV. B
Variable vlew point location (orthographic, auxiliary)

Automatic scaling

Plotter output

Composite surfaces with the option for surface blending.

Cross-sectioning island techniques.

Interactive hidden line removal or truncation for

"cleaned up m views.

Display and allow modification of the definition

(canonical) torm of all entities.

Entity selection for all functions by cursor position,

sequence nun_er, pointer or "all within diagonal

points."

Provide macro capabilit_ for capturing and naming a

sequence of construction operations allowing that

sequence to De invoked by name.

Provide capabillty where any solid can be sliced by any

plane or surface. The resultant cross-section can be

used for the following functions: dimensions, analysis,

cross-hatching, and further construction.

Both 2D and 3D non-montonic splines.

Data plot system including generation, naming, filing

and recall ot graphs and histograms.

Provide capability to construct normal areas with trim

options.

Chamfer line with trim options.

Auto c_amfer/fillet capability for open and closed

figures.

Translate, rotate, duplicate with following facilities:

I) "Repeat" n times, 2) Include scaling, 3) Tool

paths are included, _) Depth is added to translation.

Provide the means to define and display up to 32

simultaneous view areas controlled by user with auto

rescale.

Provide for "remembering- entities selected for a series

of operations without forcing a reselection.

-237-

REV. B
User defined symbol or character set.

Provide capability to go directly to point, line or arc

from anywhere using K/B conunands.

Allow user to c_ange display tolerance (for curves) to

speed display generation.

Lockout rejectea entity until another entity has been

selected.

Provide FOR ERAN COMMON to expand with added system

capaDilitles without oDsoleting old drawings.

Provide extended spline analysis via line printer or CRT

output (e.g., slope at each point).

Proviae calculator li_e capabilities including the use

ot named variables, evaluating expressions and functions

to be input wf_re numeric input only is now permitted.

Provide extended analytic function including: CG, AREA,

CURVE I_NGTH, distanoe between entities, etc.

Provide loft conic.

Allow a BASIC DIMENSION or REFERENCE BLOCK to be placed

around any draZting LABEL or DIMENSION.

Provide automatic text arrow control for linear

dimension Dased on origin selection.

Treat a set of contlguous curves as a single curve for

purposes of surface definition, machining applications

and construction.

Associative graphics geometry data base which include

the £ollowin_ relationships: inclusion, causality, and

connectivity.

Chazacter recognltion to input system commands with

"teach m moae.

Provide £or data unit having the attribute which when

c_anged causes the change to be reflected throughout the

data Dase for all instances where it is used.

Within a macro, provide FORTRAN capabilities such as

GOT0, IF, and statement labelling.

Provide Datcn mode capability.

REV. B

-238-
D

Provide capability for working in different coordinate

sys terns, e.g., wing to body.

Find slope and curvature of any curve at a specified

point.

For any 3D curve, given 2 coordinates, find the 3rd

coordinate nearest _ cursor position.

Provide chord-height-tolerance point matrix for any

curve.

Allow _,,y curve to be generated from coefficient inputs.

Provide annullment of curves, surfaces, and volumes

(resultant curves must be continuous) e.g., a window

"subtracted _ from a surface.

Define a 3D curve as 2 2D curves in difZerent views.

Provide tSe capability to label entities as they are

created, e.g., P35 = X Y Z.

Provide both function button and mnemonic input modes.

D

ABSTRACT OF THE ACCEPTANCE CRITERIA

The computer aided design (CAD) entities and functions listed

in this requirement will De tested in con]unction with requirement

125, ACT I. The procedure will include the development of

geometric packages that will incorporate all of the entity

features and can be operated on to use all of the listed

£unctions. The entities and functions can be tested in any

combination and sequence as determined by the users; each entity

and function will be tested by several users and in several

contexts. The criteria for this test will be accuracy, efficiency

and ease of operation.

REVo B

-239-
REQUIREMENT 127 GEOMTRY CONVERSION TO APT FORMAT

SOURCE BCAC-NASA

DESCRIPTI ON

IPAD shall provide a utility to convert geometry data from

the IPAD co1_munication format to APT geometry source format. For

this purpose a specific APT format shall be selected.

ABSTRACT OF THE ACCEPTANCE CRITERIA

The specific APT format to be used for testing will be

selected with the assistance of STAB members. The utility to

convert geometry data to the APT geometry source format will be

tested with a geometry package already developed and used in an

APT program. The CL data will be developed for a zero diameter

cutter and plotted full size on mylar off-line on a flat bed

plotter. The plot will be compared to results achieved outside of

IPAD. Plots developed with APT geometry must agree with

previously developed geometry within .001". Efficiency to be

specified.

REV. B

-2_0-
D

_EQU IRm_ENT 128 STANDARD GEOMETRY FORMAT

SOURCE 1 .3/3 . _. 3 .2

DESCRIPTION

IPAD shall provide a standard geometry format. The entities

supported by IPAD will include those recommended by ANSI Y1_.26.1.

I_AD shall include ways to generate elements and shall allow a

nonassociative coezficient format. The IPAD standard format

should adhere to the _ollowing:

a) Be restricted to bounded geometry in parametric form;

b) Accommodate new element types and geometry techniques as

they are developed;

c) Operate in multiple dimensions _.g., 2D or 3D)

according to the needs of the user ;

d) Include a D_ierarc_ical structure for relating data.

IPAD shall include the aDility to transform between its

stu_dard geometry format and the Y14.26.1 standard for

ccn_nlcation. IPAD will allow the representation of entities in

nonparametric form but will not support transformation between

parametric and nonparametric representations.

ABSTRACf OF THE ACCEPTANCE CRITERIA

The IPAD standard geometry format will be evaluated as

z ollows:

Geometry data types shall De as follows: engineering

drawings, idealization of major aircraft components for analysis

and aircraft structure in sufficient detail for detail design and

manufacture by a subcontractor.

Data in the coefficient _ormat will be transmitted to the

IPAD standard format and back to the coefficient format.

Data in the IPAD standard format will be transmitted to the

ANSI YI_.26.1 communications standard and back.

-24 1-

REV. B
The acceptance criteria is that IPAD allow the above function

to be performed with ,_ change in the accuracy of the geometric

data.

REV. B

-2_ 2-
REQUIREMENT 119 NL_4ERICAL CONTROL CAPABILITIES

DES CR IPT I0N

•l_%e system shall provide the following NC capabilities.

Constrain CL output to the configuration supplied by the

MULTAX APT statement in support of _ and 5-axes

machining.

Allow any postprocessor command to be inserted, for

inclusion in the CLFILE, after each complete tool path.

Display approximate machining time on demand for every

complete tool par/%, or all tool paths generated.

• Provide CLFILE editor.

Provide circular interpolation, if applicable, for any

Pocket/Profile or /Lathe finish paths in which lines and

arcs are the only entity types.

Provide separate path generation with optional separate

tool _or 3-axis and 5-axis contouring to allow fewer

paths and larger tolerance.

Buffer Pocket/Profile/Lathe datd so that the number of

approx_/uating segments is limited only by disk size.

Allow user to enter a secondary feedrate statement when

cornering. (This will override any automatic system

generated feed rate).

Provide for machining around bosses while in the lace

mode oZ 3-axis and 5-axls end cutting.

Allow a rough distance to be kept while in the 3-axis or

5-axis end cutting modes.

Allow macD_ining the resultant of any curve projected to

any surface in either the 3-axis or 5-axis end cutting

modes.

REV. B

-2_3-
Provide continuous check of cutter interZerring with

walls w_Lile machining a region bounded by surfaces in

the 5-axis end cutting mode.

Provide graphic lathes module with the following major

functions : TURN, FACE, BORE, CONTOUR, GROOVE, TAPER,

THREAD, TOOL.

Provide dynamic tool display and positioning for cut

vector insertion/modification or LATHE check surface

creation.

Place d_rection arrowhead on tool path display.

Allow accessing individual cut vectors in order to

modify, delete, or insert cut vectors.

Provide a c_olce of tangent, secant, or chordal

approximation for all curves used in pocket, profile, or

lathe path generation.

Provide INTOL and/or OUTTOL approximation for all

surface used in 3-axis and 5-axis contouring:

Incorporate t_e APT MACRO capaDility.

Surface display control including number of paths,

f_neness and direction of path.

Provide 10 standard APT vector definitions and display

same with an arrowhead indicating direction.

Provide the 7 standard APT plane definitions, planes are

displayed as infinite entities.

Provide standard APT definitions for surface and solids

including: sphere, cylinder, core, torus, nexahedron,

spheroid, ellipsoid, circular rod and toroid.

The means to define the Intersection of a curve and a

surface (point x,y,z} also the direction cosines of the

normal at that point.

Provides deep hole chip removal sequence ; user defined

drill cycle; piercing operation; GS0 drill cycle output;

3,4, 5 axis point-to-point operations.

Provides user choice of simple or complex analysis ;

handles pockets of any depth and any planar bottom;

provides cornering feedrate control.

REV. B

-24_-
D Provide option to specify number of paths for display,

allow for a pause to insert tool path motion, continue

or quit and save.

ABSTRACT OF TBE ACCEPTANCE CRITERIA

Utilize APT numerical control programmers of various skill

levels to test the NC capabilities listed in this requirement.

The capabilities are not sequential in nature. Each NC programmer

can select those capabilities to be tested but several should test

each capability zor final evaluation. The parameters to be

checked include ease of command, response time accuracy and

usability of CL output. A test part (or parts} should be machined

for a complete evaluation. The geometry t_at is used for the C%M

functmons should be generated using CAD functions (requirement

126).

REV. B

-245-
B I BI_O_I-IY

o

_e

o

4a,

5.

Feasibility Study of an Integrated Program for Aerospace

Vehicle Design (IPAD), Voluune 3, T_e Boeing Company, Contract

NAS1-11441, 1973. NASA CR 132390-97.

IPAD Doc_nent - D6-IPAD-70012-D, "Integrated Information

Processing Requirements," The Boeing Company, Contract NAS1--

14700.

IPAD Document - D6-IPAD-70013-D, "User Requirements," The

Boeing Company, Contract NAS 1-14 700.

Y_ller, R. E., "AFIPS, Vol. 33, Part I, 1968.

State,sent ot Work, ,,Development of Integrated Programs for

Aerospace Vehicle Design (IPAD} ,u 1-15-4934A, April 15, 1976.

REV. B

-24b-
APPENDIX A

Cross reZerence listing o_ requirements

by number then by title.

REV. B

-A.1-
IPAD REQUIREMENTS

I

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

i0

21

22

23

24

25

26

27

28

29

3O

31

32

33

34

35

36

37

38

39

40

41

42

43

43.1

44

45

46

PAGE

18

19

20

22

25

27

28

29

3O

31

33

34

35

38

39

41

42

43

44

4O

47

50

51

52

53

54

55

5b

57

60

61

62

63

64

66

b7

69

76

78

79

8O

81

82

83

86

89

91

REQUIREMENT TITLE

USER LANGUAGE

USER SKILL LEVELS

ERROR DIAGNOSTICS

COMMAND LANGUAGE FUNCTIONS

USER AIDS

COMM_ND LANGUAGE

ACCESS TO HOST O/S FUNCTIONS

COMMAND PROMPTS

USeR ACCESS CONTROL

EXIT REPORTS

QUERY LANGUAGE

HEADER DATA QUERY

MANAGEMENT QUERY LANGUAGE

UTILITY PROGRAMS

EDIT UTILI_f

DOCUMENTATION UTILITY

REPORTING UTI LITY

MENU BUILDING UTILITY

ORGANIZATION LIST UTILITY

MAILING LIST UTILITY

MESSAGE UTILITY

DOCUMENT REFERENCE UTILITY

PRO_ PERFORMANCE MONITORING UTILITY

LEARNING UTIL ITY

ONLINE INSTRUCTION UTILITY

USER ASSI_EANCE UTILITY

USER INTERFACE DESCRIPTION UTILITY

PROGRAM DEBUGGING UTILITY

COMMAND SEQUENCE INTERPRETATION UTILITY

INTEFJ_CTIVE, BATCH, AND PROGRAM COMMANDS

INTERACTIVE TERMINALS

SATELLITE COMPUTER SUPPORT

INTERRUPT AND RESUME CAPABILITY

BATCH JOB PROCESSING

CHECKPOINT AND RESTART CAPABILITY

CONFERENCE VIEWING OF DATA

USER PRIORITIES

STANDARD LIMITING P_ESPONSE TIME

DSER IDENTIFICATION

UNACCEPTABLE USER IDENTIFICATION

PASSWORD PROTECTION

PASSWORD CONTROL

USER CLASSIFICATION DISPLAY

USER ABSENCE AND REASSIGNMENT CONTROL

PROCESS PLANNING AND DEFINITION

JOB PREPARATION

JOB EXECUTION AND MONITORING

REV. B

-A.2-
IPAD REQU I RF/V_ENTS

NEW m

47

48

49

5O

51

52

53

54

55

56

57

57. I

57.2

58

59

60

61

b2

b3

b4

65

6b

b7

68

b9

7O

71

72

7_

74

75

76

77

78

79

_0

81

82

83

84

85

86

87

87.1

88

90

PAG.___EE

92

94

96

99

101

103

108

109

110

111

112

113

114

120

121

122

124

12-5

127

128

129

130

132.

133

135

136

138

144

145

146

147

149

150

151

152

15..%

154

156

157

159

16 0

161

102

163

165

166

167

REQUIREMENT TITLE

DYNAMIC REFERENCE TO DATA

PROCESS REPORTS

INFORMATION RELEASE

PROJECT PLANNING

MANAGEMENT SUPPORT

RESOURCE REPORTS

S UBTASK MONITORING

SUBTASK MODIFICATION

PROJECT RESOURCE MONITORING

PI_OJECT SCHEDULE MONITORING AND CONTROL

OPTIONAL AUTOMATIC REPORTING

APPLICATION PROGRAM CERTIFICATION

USER ACTIVITY CHECKLIST

INFORMATION BANK STRUCI_JRE

DATA SET ASSOCIATION

DATA SET HEADERS

DATA AREA CONTENTS

PRIVATE DATA SPACE

DATA ELEMENT TYPES

DATA G_OWTH

ENGINEERING STANDARDS

REORGANIZING DATA AREAS

DATA STRUCI_J RES

DATA ELEMENTS AND RELATIONSHIPS

OPERATIONS ON DATA RELATIONSHIPS

DATA ELEMENT NAMES

DATA QUANTIFI CATI ON

DATA SET COPYING

ARCHIVAL DATA

PROGRAM DATA ACCESS

USER DATA ACCESS

DATA SET ACCESS RECORDS

DAT_ SET IDENTIFICATION CONTROL

DATA P_&E PERMISSION

DATA RETENTION CLASSIFICATION

DATA VERSION NOTIFICATION

DATA RELEASE MECHANISM

SHARED AND PRIVATE DATA SETS

DATA DISTRIBUTION CONTROL

RECOVERY AND BACKUP

MODIFICATION OR LOSS OF DATA

DATA TKANSACTION HISTORY

DATA VALIDATION

DATA SET MODIFICATION LOG

USER READ AND WRITE S_CURITM

PROGRA_ READ AND WRITE SECURITY

ClaSSIFIED DATA ACCESS

REV. B'

-A. 3-
IPAD REQUIREMENTS

N _Mw

91

92

93

94

95

96

97

98

99

100

101

102

103

104

I05

106

I07

108

I09

110

111

112

113

114

115

11_

117

118

119

I_0

121

122

123

12LI

125

lZ6

127

128

129

PAGE

169

172

174

175

177

180

181

183

184

185

188

189

190

193

194

197

200

201

202

203

20_

208

209

210

213

214

217

218

221

222

223

226

229

230

231

235

2LI0

2_1

243

REQUIREMENT TITLE

SYSTEM ADMINI STRATION

DATA UPDATE AND TRANSFORMATION

DATA TRANSFORMATION

PROGRAM AND DATA SET COMPARISON

MATHEMATICAL OPERATIONS

PROGRAM LIBRARY

EXPLICITY AND IMPLICIT I/O

PROGRAM IDENTIFICATION AND DESCRIPTION

PROGRAM INTERFACE

PROGRAM INSERTION AND DELETION

HOST COMPUTER (S)

COMMUNICATION STANDARDS

ACCESS BY OTHER SYSTEMS

COM_MUNICATION WITH OTHER SYSTEMS

PROGRAM AND DATA TRANSFER

/_ESPONSE TIME

"SYSTEM WORKING" SIGNAL

SYSTEM CAPACITY

SYS_F-M PERFORMANCE MONITORING UTILITY

NL_ERIC ACCURACY

USAGE ACCOUNTING

PROPRIETARY INFORMATION PROTECTION

FAlL-SAFE SECURITY

NATIONAL SECURITY

SYSTEM RELIABILITY

SYSTEM AVAILABILITY

MODULAR DESIGN

SYSTEM PARAMETERS

GRAPHICS PRIMITIVES

COMMUNICATION STANDARD FOR NON-INTELLIGENT GRAPHICS

TERMINALS

CGMMUNICATION STANDA_R_ F(3R INTELLIGENT GRAPHICS

TERMINALS

GRAPHICS INTERFACE SOFI'WARE

GRAPHIC DISPLAY OF NUMERIC DATA

ANIMATION PACKAGE

GRAPHIC PROGRAMMING TOOLS

DESIGN DRAFTING CAPABILITIES

G_0METRY CONVERSION TO APT FORMAT

STANDARD GEOMETRY FORMAT

NUMERICAL CONTROL CAPABILITIES

REVo B

-A.4-
IPAD P_QUIREMENTS

.k_QUI_NT TITLE

ACCESS BY OTHER SYST_

AC_CESS TO HOST O/S FUNCTIONS

ANIMATION PACKAGE

APPLIC7%TION PROGRAM CERTIFICATION

ARCHIVAL DATA

BATCH JOB PROCESSING

CHECKPOINT AND RESTART CAPABILITY

CLASSIFIED DATA ACCESS

COMMAND LANGUAGE

COM/_AND LANGUAGE FUNCTIONS

COMMAND PROMPTS

COMMAND SEQUENCE INTERPBETATION UTILITY

COMMUNICATION STANDARD FOR NON-INTELLIGENT

GRAPHICS TERMINALS

Ctlw_4UNICATION STANDARD FOR INTELLIGENT

GRAPHICS TERMINALS

COMMUNICATION STANDARDS

COMMUNICATION WITh OTHE_ SYSTEMS

CONFERENCE VIEWING OF DATA

DATA AREA CONTENTS

DATA DISTRIBUTION C_9NTROL

DATA ELEMENT NAMES

DATA ELEMENT TYPES

DATA _LEMENTS AND RELATIONSHIPS

DATA GROWTH

iak_% PURGE PERMISSION

DATA _0ANTIFICAT lON

DATA R_TENTION CLASSIFICATION

DATA RELEASE MECHANISM

DATA SET ACCESS RECORDS

DATA SET ASSOCIATION

DATA SET COPYING

DATA _T HEADERS

DATA SET IDENTIFICATION

DATA SET MODIFICATION LOG

DATA STRUCTURES

DATA TRANSFORMAT ION

DATA TRANSACTION HISTQRY

DATA DPDATE AND TRANSFORMATION

DA_A VALIDATION

DATA VERSION NOTIFICATION

D_.SIGN DRAFTING CAPABILITIES

DOCUMENT REFERENCE UTILITY

DOCUMENTATION UTILITY

DYNAMIC REFERENCE TO DATA

EDIT OTILITY

ENGINEERING STAN DABDS

REV. B

-"A. 5-

103

7

124

57.1

73

34

35

90

6

4

8

29

120

121

102

104

36

61

83

70

63

68

64

78

71

79

81

76

59

72

60

77

87.1

67

93

86

92

87

80

126

22

16

47

15

65

190

28

230

113

145

64

66

167

27

22

29

57

222

223

189

193

67

124

157

136

127

133

128

151

138

152

15Lt

149

121

144

122

150

163

132

174

161

172

162

153

235

50

41

92

39

129
IPAD REQUIREMENTS

REQUIREMENT TITLE

ERROR DIAGNOSTICS

EXIT REPORTS

EXPLICITY AND IMPLICIT I/0

FAIL-SAFE SECURITY

t4]_OME_I<Y CXgNVERSION TO APT FORMAT

GRAPHIC DISPLAY OF NUMERIC DATA

GIIAPHICS INTERFACE SOFTWA_

GRAPHIC PhOGltA/V_MING TOOLS

_PHICS PRIMITIVES

H£_DER DATA QUERY

IIOST COMPUTER (S)

INFORMATION RELEASE

INFORMATION BANK STRUCTURE

INTERACTIVE, BATCH, AND PR/gGRAM CC_NDS

INTER_/.'TI VE TERMINALS

INTERRUPT AND RESUME CAPABILITY

JOB EXECUTION AND MONITORING

JOB PREPARATION

LEARNING UTILITY

MAILING LIST UTILITY

MANAGEMENT QUERY LANGUAGE

MANAGEMENT SUPPORT

MATHEMATICAL OPERATIONS

MENU BUILDING UTILITY

MESSAGE UTILITY

MODIFICATION OR LOSS _ DAT3%

MODULAR DESIGN

NATIONAL SECURITY

NUMERIC ACCURACY

NL_4ERICAL CONTROL CAPABILITIES

ONLINE INSTRUCTION UTILITY

OPERATIONS ON DATA BLELATIONSHI2S

OPTIONAL AUTOMATIC P,EPOKTING

ORGANIZATION LIST UTILITY

PASSWORD CONTROL

PASSWORD PROTECTION

PRIVATE DATA SPACE

P_OCESS PLANNING AND DEFINITION

PROC_ SS REPORTS

PROGRAM AND DATA SET COMPARISON

PROGRAM AND DATA TRANSFER

PI(OGPJ_M DATA ACCESS

PROGRAM DEBUGGING UTILITY

PROGRAM IDENTIFICATION AND DESCRIPTION

PROGRAM INSERTION AND DELETION

PROGRAM INTERFACE

PI_OC4<AM LIBRARY

REV. B

-A.6-

3

10

97

113

127

123

122

125

119

12

101

49

58

30

31

33

46

45

24

2O

13

51

95

18

21

85

117

114

110

129

25

69

57

19

42

41

62

44

48

94

105

74

28

98

100

99

96

PAGE

20

31

181

209

240

229

226

231

221

34

188

96

120

60

61

63

91

89

52

46

35

101

177

43

47

160

217

210

203

243

53

135

112

44

81

80

125

86

94

175

194

146

56

183

185

184

180
IPAD REQUIREMENTS

REQUIREMENT TITLE

PROGRAM PERFORMANCE MONITORING UTILITY

PROGRAM READ AND WRITE SECURITY

PROJECT PLANNING

PROJECT RESOURCE MONITOItlNG

PROJECT SCHEDULE MONITORING AND CONTROL

PROPRIETARY INFOP_IATI£1_ PROTECTION

QUERY LANGUAGE

RECOVERY AND BACKUP

*(EORGANIZING DATA AREAS

REPORTING UTILITY

RLS OURC_ REPORTS

RESPONSE TIME

SATELLITE COMPUTER SUPPORT

SHA_ED AND PRIVATE DA_ SETS

STANDARD GEOMETRY FORMAT

b?ANDARD LIMITING RESPONSE TIME

SUBTA_K MODIFICATION

SUBTASK MONITORING

SY STEM ADMINI STRATI ON

SYSTEM AVAILABILITY

&_Y_I_EM CAPACITY

SMSTEM PARAMETERS

SYSTEM PERFORMANCE MONITOItlNG UTILITY

SYSTEM RELIABILITY

SYSTEM WORKING" SIGNAL

UNACCEPTABLE USER IDENTIFICATION

USAGE ACCOUNTING

USEh ABSENCE AND BY-J&SSIGNMENT CONTk<)L

USER ACCESS CONTROL

USER ACTIVITY CHECKLIST

USER AIDS

USER ASSISTANCE UTILITY

USER CLASSIFICATION DISPLAY

USER [_TA ACCESS

USER IDENTIFICATION

U_EA INTERFACE DESCRIPTION UTILITY

USER LANGUAGE

USER PRIORITIES

USER READ AND WRITE SECURITY

USER SKILL LEVELS

UTILITY PROGRAMS

23

89

50

55

56

112

11

8_

66

17

52

106

32

82

128

38

54

53

91

116

108

118

109

115

107

40

111

43.1

9

57.2

5

26

43

75

39

27

1

37

88

2

14

PAG____EE

51

166

99

110

111

208

33

159

130

42

103

197

62

156

241

76

109

108

169

214

201

218

202

213

2O0

79

204

83

30

114

25

54

82

147

78

55

18

69

165

19

38

REV. B

-A.7-
APPENDIX B

BRIEF REQUIR_4ENT DESCRIPTION

REV° B

-B. 1-
REQM'T TITLE DESCRIPTION OF REQUIREMENT

2. I USER INTERFACE

2.1.1 USER LANGUAGE

. User Language IPAD user languages shall be useroriented, cQnsistent in vocabulary

and syntax.

1 User S_lll Levels IPAD shall address the problem of

variation in expertise.

o Error Diagnostics IPAD s_all provide flexible error

diagnostic capabilities which are

helpful, complete, user-friendly, etc.

_s Command Language

Funct ions

IPAD shall provide a user command

language comprised of IPAD executive

level commands and commands in subordinate user languages.

5. User Aides IPAD shall assist the user in accomplishing his design task by providing a

description and overview of capabilities

available in the IPAD system.

b_ Command Language IPAD command language shall be engineering-user oriented.

8 Access to Host O/S

Functions

IPAD shall allc_ access to the host

operating system capabilities.

Command Prompts IPAD shall interpret commands into

appropriate operating system functions

supplying defaults, accepting abbreviated commands, etc.

_o User Access Control IPAD shall provide the capability for a

manager to control the set of commands

available to an individual IPAD user.

10. Exit Reports IPAD shall provide reports of the status

of data sets affected by the current

TPAD wor_ session, resources used,

messages on file, etc.

11. Query Language IPAD snall provide an interactive query

language supporting logical requests

which may include arithmetic operations

and refer to any data element.

REV. B

-B. 2-
12. Header Data Query

13. Management Query

IPAD shall provide the capability to query

header data.

IPAD shall provide the capability to

interrogate the official project data.

1 _. Utility Programs

15. Edit Utility

16. Document Utility

17. Reporting Utility

18. Menu Building Utility

19.

20.

2..1.2

21.

22.

:'3.

2_.

Organization Lists

Utility

Mail List Utility

Message Utllity

Document Re£erence

Uti 1 Ity

Program Performance

Monitoring Uti l_ty

Learning Utility

REV. B

USER TOOLS

IPAD shall provide an open-ended set of

machine-independent interface utilities.

IPAD shall prowide a general text-editing

and update capability permitting on-line

development of programs, changes to source

modules, and selective display of the

current data set and data in response to

the current command.

IPAD shall provide a compete capability

to enter, maintain, and print documents.

IPAD shall provide means for user-requested

and automatic reporting.

IPAD shall provide aids for planning-andpreparation phase usage in establishing

individual user ccmmk_nd menus.

IPAD shall provide the means to produce

corporate-like organizational lists down

to individual named members and associated

descriptors.

IPAD shall provide a flexible means of

constructing/accessing data for mailing

lists.

IPAD shall provide a means for one user

to send a message (either displayed

interactively or hard copied in batch) to

designated users.

IPAD stall provide the capability to create,

update, and query references to documents on

standard design and processing procedures.

IPAD shall provide a facility to monitor

execution oZ a program and provide

computer resource indicators.

IPAD shall support a computer-based learning

-B. 3-
25.

26.

27.

2B.

29.

30.

31e

32.

33.

3_.

35.

36.

tool allowing an instructor-student relationship, including munitoring of progress

On-Line Ins truction

Utility

IPAD shall support on-line instruction with

selection from short lists, programmed

learning, and example problems.

User Assistance

Utility

IPAD shall provide conditional activation

of enhanced user-aids for giving novice

users a better view of IPAD capabilities.

User Interface

Description Utility

IPAD shall provide a utility for creating

and interogating data sets of text describing the IPAD user-command interface.

Progr am Debugging

Utility

IPAD shall pruvide advanced un-line

debugging aids for observing and controlling executive programs.

Command Sequence

Interpretation Utility

IPAD shall provide means for interpretation

of macro-like command sequence files.

2.1.3 U_R ACCESS

//Iteractive, Batch,

and Program Commands

IPAD shall addressible thru interactive

terminal commands, batch control cards,

or calls from user programs running under

IPAD control.

Interactive Terminals IPAD shall use textual and graphical

interactive terminals _oth storage and

refreshed) as the primary user interface.

Satellite Computer

Suppor t

IPAD shall be able to run jobs, in whole

or in part, on a remote computer system.

Interrupt and Resume

Capability

IPAD shall allow the user to interupt

his interactive terminal session at any

point.

Batch Job Processing IPAD shall pemit submittal of batch

processing jobs from interactive

terminals or through normal batch

submittal.

Checkpoint and Restart

Capability

. IPAD shall allow a checkpoint/restart

capability for jobs running under the

control of IPAD.

Conference Viewing o_

Data

IPAD shall provide the means for multiple

and conference viewing of IPAD data and

generated displays.

-B._-

REV. B
37. User Priorities IPAD shall recognize the emergency,

short-duration, appointment, and

standard user categories for priority

control °

38. Standard Limiting

Response Time

IPAD shall provide user response by

using the concept of standard limiting

response tame (SLRT} .

39. User Identlfication IPAD shall determine the authority of a

potential user to access the IPAD system

by checking passwords, user ID, etc°

40. Unacceptable User _D IPAD shall provide diagnostic aids to

unacceptable identification which allow

for the re-entering of ID data°

41. Password Protection IPAD shall protect the user password

from discovery thru normal usage.

42. Password Control _PAD shall permit the user to easily

change his own password.

43. User Classificati_

Display

IPAD shall allow the user to request

a display of the classifications

assigned to the user for accessing

and manipulating data.

43.1 User Absence and

Reassignment Control

IPAD shall protect an absent users wQrking area and warn the user's manager

of messages, tasks, subtasks involved.

2.2 DESIGN sUPpORT AND CONTROLS

2.2.1 DESIGN PROCESS SUPPORT

44.

45.

46.

Process Plamning and

Definition

Job Preparation

Job Execution and

Monitoring

IPAD shall be able to support an unlimited number of design-team processes.

IPAD shall provide the means for job

preparation including collecting programs

and data, assembling into job sequence, etc.

XPAD shall provide mechanisms for monitoring and providing executive authority

over running jobs.

REV. B

-B .5-
_7. Dynamic Reference

To Data

IPAD shall permit programs to reference

data sets in specific data areas with

the user identifying the input/output

data sets to the job or group of jobs

at execution time.

48. Process Reporting IPAD shall provide for design process

reports which may include both graphical

and textual data.

49. Information Release This requirement now covered by zeqmt 81

50.

2.2.2 COMPUTER AIDED DESIGN PROJECT _%NAGEMENT

Project Planning IPAD shall provide the means whereby

managers can plan a design project using

one or more design processes.

51. Hanag ement Support IPAD shall support design management

by storage and utilization of maragement tools such as critical path, work

progress, etc.

52. Resource Reports XPAD shall provide individual reports

on the status of computer resouro8

and manpower accounts.

53. Subtask Mumit uring IPAD shall provide the means to

subtask status or subtasks which have

been suspended.

5_. SubtaskModification IPAD shall allow _or input of task

status, add/delete/alter tasks and

subtasks, or suspend a task in progress.

55. Project ResOurce

Monitoring

IPAD shall prepare a report comparing

the computer resources budgeted versus

actual usage.

56. Pro_ct Schedule

Monitoring and

C_trol

IPAD shall permit projects to be driven

by schedule c_trol.

57. Optional Automatic

Reporting

IPAD shall permit optional automatic

reporting of such iems as schedule

deliquencies, r_tice of data changes

to users having accessed particular

data sets, etc.

57.1 Application Program

Certification

IPAD shall document the integrity of

a given job execution by certifying

the component operational modules.

-B.6-

REV. B
57.2 User Activity

Checklist

IPAD shall provide the capability for

the user to request a summary of his

activities °

2.3 INPGRMATIDN MANAGEMENT

2.3. I DATA MAN_ENT

58. Information Bank

Structure

IPAD shall permit groups of IPAD data

sets to be logically grouped into data

areas for user convenience.

59. Data Set Association IPAD shall provide the capability to

logically associate data sets with a

given data set.

60. Data Set Headers IPAD shall permit the logical association of header data with each data set.

61. Data Area Contents IPAD shall provide data areas consisting

of both a data dictionary and the actual

data sets.

Private Data Space IPAD shall provide a special subtask

area as the private data area for each

subtask.

63. Data Element Types IPAD shall support an expandable list of

data element types such as text, scalars,

vect_s, matrices, tables, lists, etc.

6#. Data Growth IPAD shall support an orderly growth of

data set definitions within an IPAD information bank without inpacting information

avai lability.

65. Engineering Standards IPAD shall provide means for the installing definitions, sets of values for

engineering standards, etc. in the information bank.

66. Reorganizing Data

Areas

IPAD shall provide the capability of

combining individual data areas into one

resulting data area.

67. Data Structures IPAD shall provide and support those data

structures commonly used by engineering

disciplines.

68° Data Elements and

Relation ships

XPAD shall provide the user with a

capability to define data elements and

to introduce relationships between them.

-B°7-

REV. B
69.

70.

71.

72.

73.

74.

Operations on Data

Relatiunships

Data Element Names

Data Quantification

Data Set Copying

Arc hived Data

Program Data Access

75. User Data Access

?6. Data Set Ac_ss

Records

77. Data Set

Identi_ i cation

78.

79.

80.

Data Purge Permission

Data Retention

Classification

Data Version

Notification

81. Data Rel ease

Mechanism

REV. B

IPAD shall allow establishing, recording,

viewing, locating, and modifying the

logical relationships of data elements.

IPAD shall expect unique element names

within the data areas in which the

elements are defined.

IPAD shall support extensive data

volumes witA upper and lower data

volumes defined to support at least

ten IPAD-design products.

IPAD shall pr_ide the means to the

user for copying data and programs

into subtask or private data areas

from other data areas.

IPAD shall provide for access to

archived project data.

IPAO shall allow user programs to

_rk within a subset of a data area or

with data from multiple data areas.

IPAD shall allow the user to limit a

query to a specific data area or to a

subset of the information data bank.

IPAD shall keep a record of all accesses

to a data set.

IP_D shall guarantee that data set

content changes cause changes in

data set identification.

IPAD shall require special permission

to purge any data set which has a

dependent data set while these data

sets are under project control.

IPAD shall provide for data set retention

classifications to include permanent,

program life, project life, etc.

IPAD shall notify users accessing

preliminary data that a later version

o_ the data is available.

IPAD shall provide for the creator or

modifier of data to release it and qualify

the data set for the benefit of other users

-B.8-
82.

83.

Shared and Private

Data Sets

Data Distribution

Control

84. Reco_ry and Backup

85. Modilication or Loss

of Data

86. Data Transaction

History

87. Data Validation

87.1 Data S_t Modification

Log

88. User Read and Write

Security

89. Program Read and

Write Security

90. ClassiZied Data

Access

91. System Administration

92.

2.3.2

Data Update _and

Transformation

93. Data trans f urination

IPAD shall accomodate both shared and

private data sets.

I_AD shall permit both automatic

and manual distribution of data and

programs throughout the TpAD Computer

Complex.

IPRD shall provide for recovery and

backup in case of system failure or

descruction of data bases.

IPAD shall automatically identify any

data areas affected by losses or

modifications to the data base.

IPAD shall record a transaction history

with data needed to recreate data

destroyed or modified.

IPAD shall pr_ide for validation of

user data including a range of values

check.

IPAD shall log data set modification

history for each version.

IPAD shall control the users ability

to read and write data as per the needto-know and other security consideration.

IPAD shall control computer program

access to data in a similar manner

to the interactive user query.

IPAD shall require stringent user

identification to access classified

and/or proprietary data.

IPAD shall accomodate the special

managerial requirements of the data

administrator.

INFORMATION MANAGEMENT TOLLS

IPAD shall provide update and

transformation capabilities for a wide

range of requirements.

1PAD shall provide automated means for

unit conversions, data transformations.

REV. B

-B.9-
94. Program and Data

Set Comparison

IPAD shall compare two or more data sets

or programs for physical differences and

report those differences.

95. Mathmatical Operations IPAD shall provide utilities for perfozming arithmetic and logical operations

on selected data.

2.3.3 C0_UTER PROGRAM LIBRARY

96. Program Library IPAD shall support a program library

consisting of programs in either source

or executable form for use in the design

process.

97. Explicit and Implicit IPAD shall support several modes of

program interfaces with the information

data bank.

98. Program Identification

and Description

IPAD shall allow users to enter keywords

and standard descriptions of their programs

99. Program Interfaces IPAD shall include tools for interfacing

existing design computer programs with

each other.

100. Program Insertion and

Deletion

IPAD shall prcwide for the easy insertion of programs from the library.

2 ._ JAUXILIARY/EXTERNAL SYSTEM INTerFACES

2.4.1 HOST/REMOTE SYSTEM INTERFACES

10 1. HOSt Computers IPAD shall be capable of operating on

either a single computer or on a distributed computer complex.

10 2. CQm_unication

Standa _d s

IPAD shall utilize co_nications

standards between computing systems and

aerospace companies.

103. Access By 0tber

Systems

IPAD shall permit access to all design

data u_der IPAD control obtained from

non-IPAD systems.

2 . _ .2 SOFTW&RE INTERFACES

I0_. Communication With

Other Systems

XPAD shall have the ability to communicate with existing software systems

external to IPAD.

REV. B

-B. 10-
105. Program and Data

Transfer

IPAD shall facilitate transfer of

program modules, data bases, etc. between installations, accounting for

differences in co_uter word sizes.

2.5 GENERAL S¥ST_ CAPABILITIES

2.5.1 PERFORMANCE

106. Response Time _PAD shall provide for adequate response time for varying functions.

107. nSystem Working"

Signal

II_ shall display a signal to the

user to indicate the system is working

(used if response time is long} .

108. System Capacity IPAD shall have no restrictions imposed

other than the physical limitations of

the hardware configuration used to

support ZPADo

109. System Performance

Monitoring Utility

IPAD shall provide a complete set of

tools for the system administrator to

monitor system performance.

110. Numeric Accuracy IPAD shall be able to store numerical

data with at least 10 significant digits.

11 1. Usage Accounting IPAD shall be able to determine how data

and system resources are used.

2.5.2 ,._EC-'UR.1TY

112. Proprietary Information

Protection

ZPAD shall prevent the disclosure of

information to proprietary interests of

the user-company.

113. Fail-Safe Security ZPAD shall not compromise security

considerations even in the event of a

system failure.

11_. _ational Security ZPAD shall not preclude the operation in

accordance with standards for the safeguarding of classified information.

REV. B

-B.1 1 -
2.5.3 R_.,ZKB 1"n'PI_Z

115. System Reliability IPAD shall be reliable to the point that

system reliability need not be a planning

consideration for IPAD users.

11b. System Availability IPAD shall be available more than 97.5S

of the available time allocated to IPRD

use on the host computer.

2.5.,

117. Modular Design IPAD shall be designed for modular £unctional capabilities, allowing a gradual

adoptation of IPAD within a company.

118. System Parameters XP_D shall have installation parameters

available for tuning the IPAD system to

the needs and capabilities of the installat_ion.

2.6 GRAPHICS

2 . 6 . 1 GRAPHICS STANDARDS

119. Graphics Primitives IPAD shall utilize a standard graphics

software package consisting of defined,

standard graphics primitives.

120. CQmmunication Standard

for Non-lntelligent

Graphics Terminals

IRKD shall establish standards for communication with non-intelligent graphics

terminals.

121. Communication Standard

f or Intelligent

Graphics Terminals

XPAD shall establish standards for communication with intelligent graphics

terminals.

2.6 • 2 DEVICE INTERFACE

122. Graphics Interface

Software

XPAD shall provide interface software for

most common graphics devices.

2.7 GRAPHICS RELATED TOOLS

2.7.1 GRAPHIC S .R_LATED pRO_NG TOOLS

123. Graphic Display of

Numerical Data

IPAD shall include comprehensive capabilities for conversion of nnmerical data

into graphical format.

REV. B
12q,. Animation Package

125. Graphic Programming

Tools

126. Design Drafting

Cap abili ties

127. Geometry Conversion

To APT Format

128. Standard Geometry

Format

129. Numerical Control

Capabilities

LPAD shall provide an animation package

to help display dynamic phenomena in a

flicker-f ree form.

IPAD shall provide comprehensive graphic

programming tools allowing development from

simplified building blocks o

2./.2 GE QMETRY

IPAD shall provide CAD entities such as

point, line, circle, fillet, ellipse,

rectangle, ruled surface, curve mesh

surf ace, etc.

IPAD shall provide a utility to convert

from geometry data in the IPAD communication format into a form suitable for

APT usage.

IPAD shall be capable of allowing a geometry format _hich is an extension of the

ANSI Y 1_ ° 26 proposed standards.

IPAD shall provide a wide range of N.C.

capabilities.

REVo B

-13.13-
REV.

B

-C. 1-
KEYWORD LIST

KEYWORD

b,O

2,0

3_*,0

111,0

7.0

43,0.

I03,0

9,0

60 ,3

95,0

74 .0

4,0

4,0

76.0

7k.3

76.0

57.2

7.0

95,0

96.0

96.0

ll .O

gl,O

55,0

111,0

II0.0

46.0

57.2

57.2_

38._

66.0

56.0

5.0

_.0

92.0

54.0

126,0

12'_,0

128,0

57.1

37.0

37.0

37.0

37.0

37.0

127,0

73.0

71 .0

ABBREVIATED C3MM ANDS

A B BRE V I AT IF1'4

ABORT

ACCESSES

ACCESSIBLE HOST OPERATING

ACCESSING DATA

ACCESS BY []THFR SYSTFMS

ACCESS CONTROL

_CCESS CONTROL

ACCESS CONTROL

ACCESS DATA AREA SUBSET

ACCESS HF]ST OPERATING SYSTEM

ACCESS IPAD UTILITYS

ACCESS LOG

ACCESS MULTIPLE DATA AREAS

ACCESS RECORDS

ACCFSS SUMMARY

ACCESS TO _OST _/S FUNCTIONS

ACCESS T3 J3BS

ACCESS TO PROGRAMS

ACCESS TO SDURCF MODULES

ACCESS

ACr'ESS

ACCOUNTING INFORMATION

ACCOUNTING

ACCURACY

ACTIVITIES

ACTIVITY DATE

ACTIVITY SUMMARY

ACTUAL _FSPONSE TIME

A00 DATA

ADD

AIDS

ALTERNATE PARAMETERS

ALTER VALUES

ALTE_

ANIMATION

ANIMATION PACKAGE

ANSI Y1_,26

APPLICATION

A P PZI NT MENT

APPOINTMENT PERIOD

APPOINTMENT RESFRVAT IONS

APPOINTMENT USER

APPOINTMENT USER TERMI'_ALS

APT FrlRMAT

ARCHIVAL DATA

ARCHIVE DATA

SYST EM

C AP AB IL I TI ES

PROGRAM CERTIFICATION

C.2

REV. B
KEYWORD LIST

RFO

_mm

7g.O

g5.3

30.0

51 .0

b0.0

59.0

IIO,0

g3,3

I16.0

84.0

50.0

30.0

34.0

4,0

4_, 0

34,0

38.0

II,0

34.0

30.0

50.0

IC2,0

c_5.0

3,0

52,0

55,_

52.0

55.0

I_,0

126.0

122.0

33.0

129.0

108.0

57.1

57 .I

42, 0

2_,3

87. i

87.I

2e,O

87,1

35.0

35.0

35.0

90, 0

90,0

19,0

KFYWORD

ARCHIVE DATA

ARITHMETIC OP_-'RA TID'_ S

ART

ASSIGNMENTS

ASSIGN NAMES

ASSr)ClATIVE DATA RELATIONSHIP

ATTRI BUTE S

AJIOMATI: UNIT CDNVERSIDXl

AVAILABILITY

BACKUP

BAR CHART

BATCH COMMANDS

BATCH JOB PROCESSING

BATCH JgB

BATCH MDDF

BATCH PROCESSING

BATCH PROCESSING

BATCH OUFRY LANGUAGE

BATCH SUBMITTAL

BATCH

BEGIN MILESTONE

BETWEEN AEROSPACE COMPANIES

BOOLEAN DP FRATI[INS

BRIEF ERROR DIAGNOSTIC

BUDGETED RESOURCE REPORT

BJDGET STATJS REP]RT

BUDGET

BUDGET

BJ ILD MENU

CAD

CALCOMP 763

CANCEL RESULTS

CAPABILITIES

CAPACITY OF IPAD

CERTIFICATION

CERTIFIED OPERATIONAL MODULES

CHANGES TO PASSWORD

CqANGE DATA

CHANGE DESCRIPTION

CHANGE HISTORY

CHANGE PROGRAM

CHANGE REASON

CHECKP]INT

CHECKPO INT RESTART

C;4ECKPOINT AND RESTART CAPLABILITY

CLASSIFIED DATA

CLASSIFIED DATA ACCFSS

C3LIST

C.3

REV. B
K_YWORD LIST

P_O KFYWqRO

_.0

27.0

30.0

5.0

9.3

5.0

27.0

8.0

8.0

4.0

b.O

29.0

1.0

4.0

6.0

37.0

5.0

8.0

9.0

29.0

2q. 0

50.0

102 .O

102.0

103.0

104.0

121 .0

4.3

lq.O

19,0

lq.3

4.0

lq.O

4.0

50.0

50.0

46.0

9q.O

50.0

52.3

52.0

55.0

24 .0

24.0

120.0

36.0

50.0

20.0

COMBINE DATA AREAS

C OMMA NDS

COMM ANDS

COMMANDS

COMMAND AVAILABILITY

COMMAND CATEGORIES

COMMAND DESCRIPTION

C CMMAND DECODIN3

COM_IANO DECODING AND DISPLAY

COMMAND FUNCTIONS

COMMAND FUNCTI F3NS

COMMAND INT__ RPPETATIDN

CmMMAND LANGUAGE

CPMMAND LANGUAGE FUNCTIONS

COMMAND LANGUAGE

COMMAND MODE

COMMAND OVERVIEW

COMMAND PI_OMPT S

COMMAND RESTRICTION

COMMAND SFOJENCES

COMMAND SEQUENCE I'_TERPRETATION

COMMIT SCHEDULE DATES

COMMUNICATION

COMMUNICATION STANDARDS

COMMUNICATION WITM

COMMUNICATION WITH

COMMUNICATION WITH INTELLIGENT

COMPARE DATA

COMPARE DESCRIPTOR

COMPARE DESCRIPTOR TO INANE

COMPARE INAME T3 DESCRIPTOR

COMPARE PROSRAMS

COMPAR_

COMPARE

CqMPLETE KEY TASKS

COMPLETE PROJECT

COMPUTER PROGRAM

COMPUTER PROGRAM

COMPUTER RESOURCES

COMPUTER RESOURCE REPORT

COMPUTER RESOURCES

COM_UTE R PESOURC ES

COMPJTOR C_URSES

C [!MPUTOR LEARNING

COMUNICATION WITH NON-INTELLIGFNT

CONFERENCE VEIWING

CONSTRAINTS

CONSTRUCT

C.4

UTILITY

TERMINALS

TERMINALS

REV. B
KEYWDPD LIST

REQ

ZO.O

91 .0

60.3

119.0

12g. O

123.0

127.3

93.0

72.0

72.0

57._

1g,0

19.0

28.0

19.0

i_.0

19.0

57.2

111.0

51.0

51.0

52.0

52.3

125.0

60.0

75.0

91.0

_I .0

47.0

74.0

5_.0

70.0

63.0

94.0

61.0

83.0

93,0

44,0

61.0

64.0

65 .0

63.9

58.0

70.0

44.0

45.0

4_.0

71.0

KEYWORD

CONSTRUCT MAIL LIST

CT)NTENT

CONTROLLED DATA

CgNTROL

CONTROL

CONVERSION TO

CONVERT

cOn RDINATE TRANSFORMATION

CgPY DATA

COPY PROGRAMS

CgPY SUMMARY

CORPORAT_ LIKE LIST

CORPORATE LIKE ORGANIZATIONAL

C RRRE CTI ON

CREATE MAILING LIST

CRFATE MENU

CR_ATF ORGANIZATION LIST

CRFATIgN SUMM_RY

CRE ATION

CRITICAL mATH

CUMJLATIVE COST DISTRIBUTION

CUMULATIVE RESOURCE REPORTS

CURRENT STATUS

CURVPS

DATA ACCESS

DATA ACCESS

DATA ADMINISTRAllgN

DATA APOROVAL CATEGORIES

DATA AREAS

DATA AREAS

DATA ARC

D AT A AR EA

DATA CHARACTERISTISS

OATA CCMPARISON

DATA CONTENT

DATA CONTROL

DATA CONVERSION

DATA DEFINITION

DATA DEFINITION

DATA DEEINITTDN

DATA DEFINITIgN

DATA ELPMENT TYPE

DATA ELEMENT TYPE

DATA _LEMENT NAME

DATA EL OW

DATA FLOW

DATA FLOW

DATA FLOW

C.5

REV. B

LIST
KEYWgRDLIST

REO

mQn

68.0

64.3

96.0

86.0

44 .3

67.0

60.0

_ .3

44.0

92.0

93.0

9_.9

64.0

02.0

43.1

63.0

7_o0

81 .0

71.0

68.0

69.0

81.0

58.0

60.0

79.0

47.0

5_.0

59.0

76.0

57.0

72.0

94.0

12.3

60. O

77.0

87.1

77.0

77.0

57.3

75. 0

62.0

71.0

67.0

68.0

91.3

76.0

85.9

92.3

KEYWORD

DATA F{]RM AT

DATA GROWTH

DATA HANDLING

DATA HISIDRY

DATA IDFNTI FICATIDN

DATA INDEPENDENCE

DATA INSTALLATION C[_NTROL

DATA INTEGRITY

DATA INTEPFACES

DATA MAMIPULATION

DATA MANIPULATION

DATA MANIPULATICNS

DATA OCCUREICE

DATA OPFRATIONS

OATA OWNERSHIP CHANGE

DATA PRI'_ ITIVES

DATA PUARGE

DATA QUALIFICATION

DATA QUANTIFICAT ION

DATA RE LAT I']NSHI P

DATA PFLATIONSHIP 3PERATIONS

DATA RELEASE MECHANISM

DATA R ESF]UR C _

DATA RETFNTION

DATA RETENTION

DATA SETS

DATA SFTS

DATA SET ASSgCIATI']'_

DATA SET ACCESS

DATA SET CHA'_GE

DATA SET COPYING

DATA SET COMPARISON

DATA SFT _E_DER

DATA SET HEADER

DATA SET IDENTIFICATIF_N CONTROL

DATA SET MODIFICATION LOG

DATA SET QUALIFICATION

DATA SET V_RSION

DATA S ET

DATA SET

DATA SPACE

DATA STORAGE

DATA STRUCTURE

DATA STRUCTURF

DATA STRUCTJRE

DATA SUBSET

DATA TRANSACTION HISTCRY

DATA TRAN SF ORMAT I Or,!

REV. B.

C.6
KEYWORD LIST

RF_I

93,0

I05,9

92,0

87,0

80,.9

81,0

7L,O

45,0

IIl, O

2_,0

50,9

a,O

E,O

%,0

4,0

4,0

4,0

4,0

4,0

4,0

44.3

91,0

54.3

iOO.O

57.2

50.0

19,0

78,0

59.3

27.0

27.0

]9,0

19, 0

126,0

44,0

48,3

4£. 0

50.0

50.0

117.0

bl,O

64 ,0

55.0

68.0

122.0

4.0

15.3

4.0

KEYWORD

DATA TRANSFORMATION

DATA TRANSFER

DATA UPDATE

DATA VALIDATIPN

[ATA VERSION

DATA VERSION

DATA VOLUME

DATA

DATA

DE BUGG IMG

DECISION MILESTONE

DECODING

DEFAULT PARAMFTERS

DEFINE DATA

DEFINE DATA ELEMENTS

DEFINE DATA FCPMATS

DEFINE DATA PELATIONSHIPS

DEFINE FORMATS

DEFINE RELATIONSHIPS

DE FI NE

DEFINITION OF PR,_CESSES

DEFINITION

DELFTE

DELE TF

DFLETION SUMMARY

DEPENDANCY ]F TASKS

DEPENDANT GROUP NAME

DEPENDENT DATA SET

DEPENDENT DATA SETS

DESCRIBE COMMAND

DESCRIPTIONS DF THE USER INTERFACE

DESCRIPTOR

DESCRIPTOR NAME

DESIGN DRAFTING

DESIGN PROJECT

DESIGN PROCESS

D_SIGN PRgCES_ _EPO_TS

DFSIGN PR']CESSE S

DFSIGN PPnJFCT

DF SIGN

DICTIONAR Y

DICT ION ARY

DIrTIONARY

DICTIONARY

DIGITIZER

DISPLAY CURRENT O=ERATICN

DISPLAY DATA

DISPLAY GRAPHICS

C.7

REV. B
KEYWORD LIST

RFO

21.0

_,.0

43.0

48.0

50.0

83.0

16.0

16.0

16.0

2?.0

22.0

22.3

22.0

16. 0

16.0

22 ._

22.0

22.0

16.0

125. 0

120.0

124.0

47.0

12(,. 0

6.0

15.0

4.0

36 .O

4.0

4.0

15.0

35.0

37._)

37.0

bO.O

6.3

4.0

4.0

28.0

28.0

28.0

3.3

8.0

3.0

28.0

3.0

KEYWORD

DISPLAY MESSAGE

DISPLAY

DISPLAY

DISPLAY

DISPLAY

DISTRIBUTED COMPUTING

DOCMENT _4AI'_TENANCE

D_CUMENTATION UTILITY

DOCUMENTATION

DOCUMENT

DgCUMENT

DOCUMENT

DOCUMENT

O _CU ME NT

DOCUMENT

DOCU MFNT

DOCUMENT

DOCUMENT

DOCJ MENT

DRAWING SCALE

DUMB

DYNAMIC GRAPHICS

DYNAMIC REFERENCE

DY NA MI C

Cr]NTE NTS

INFORMATION

INFORMATION RETRIEVAL

INFORMATION STORAGE

P RE P ARAT IO_

PREPARATION AND MAINTENANCE

REFFRENCES

REFERENCE UTILITY

SUB JESTS

TO DATA

EASY CQMMAN) LANGUAGE

EDIT/UPDATE LANGUAGE

EDIT DATA BASE

EDIT DATA

EDIT DICTIONARIES

EDIT MANAGEMENT INFORMATION

EDIT JTILITY

EDIT

EDIT

ELAPSED TIME

EMERGENCY

EMERGENCY USER

END M ILL STrlIE

ENSINEERING LANGUASE

ENTER DATA

ENTER DATA BASE

ERROR CORRECTION

ERROR DIAGNOSIS

ERROR DIAGNOSIS AND

ERROR DIAGNOSTIC

ERROR DIAGNOSTICS

ERPOR SOURCE

E_,OP

RROR

C ERR E CTION

C.8

REVo B
KEYW]RD LIST

RF_

42.0

23.0

3b.0

25.0

96,Z)

4.0

23.0

33. 0

97.0

4.0

i0.0

4.0

i0.0

10. 0

52.0

63.0

2.0

2.0

97.0

12_.0

113.0

113.0

113.0

46.0

4.0

4.0

122.0

i17.0

126.0

65.0

5.0

17.0

4.0

4.0

127.0

127.0

125.0

126.0

19.0

31.0

119.0

119.0

120.0

12 I. 0

122.0

123.0

124.0

125.0

KFYWORD

--m

ESTABLISHME'_T OF PASSWf]RD

EVALUATE PERFORMANCE

EVENTS

EXAMPLE PROBLEMS

EXFCUTABLE

EX EC UTE

EXEtUTION MDqITDRING

EXECUTION

EXISTING PROGRAMS

FXIT IPAD

FXIT REPORTS

EXIT

EXIT

EXTT,R

EXIT, R

EXPANDABLE LIST

EXPERTI SE

EXPF RT

EXPLICIT Ii2

EXTEND

FAILURE

FAIL-SAFF

FAIL-SAFE SECURITY

FINAL RESULTS

FIND INFORMATION

FIND

FLATBED PLOTTER

FJNCTIONAL CAPABILITIES

FUNCTIONS

GATHER INFORMATION

GENERAL PASSISVE C3MMANDS

GENERATE REPORT

GENERATE QEPORTS

GENERATE

GEOMETRY CONVERSION

GEOMETRY DAIA

GFOMETRY FORMAT DEFINITION

GEOMETRY

GNAME

GRAPH

GRAPH

GRAPH

ICAL

ICS

ICS

SRAPHICS

GRAPHICS

GRAPHICS

GRAPHICS

G RAPH IC S

GRAPHICS

TERMINALS

PRIMATIVES

C.9

REV. B
KEYW]RD LIST

RFQ

lq.O

45.0

47 .0

50.0

106.0

i01. O

37 .3

50.0

12.0

12.0

3.0

4.0

5.3

37.0

6.0

I01.0

7.0

7.0

122.0

Bg. 0

39.0

77.0

37.0

56.0

97. O

19.0

6.0

lOl .0

61.0

b_,.O

65.0

68.0

IQ.O

9.0

37.0

44.D

44.0

51 .0

51.0

58.0

5_.0

66.0

_'I.O

91.0

97.0

112.O

47.0

L,5.0

KFYWORD

GROUP NAME

GROJ_ FIF JOP, S

GRnUP OF JOBS

GROUP OF JOBS

GUIDE LINES

HARDWARE CONFIGURATION

-_ARDW IRE] TERMINALS

HARD COPY

HEADER DATA QUERY

HEADER DATA

HELP

F4ELP

HELP

H('LD SEPVIC_

HOST COMMAND LANGUASE

HOST COMPUTER

HOST OPFRATING SYSTEM

HOST O/S

IBM 22 50

IDENTIFICATION

IDFNTIFICATION SEOUENCE

IDENT IF ICATI gN

IMMEDIATE ACCESS

I_PENDING PROBLEM REPCRTS

IMPLICIT I/F]

INAME

INDEPENDANT OF HOST COMPUTER

INDEPENDENT

INDEX

INDEX

INDEX

INDEX

INDIVIDUAL NAME

INDIVIDUAL USER COMMANDS

INFORMATION BANK

INFORMATION C]NTR3L

INFORMATION FLOW

I'_FORMAT ION DISPLAY

INFORMATION RETRIEVAL

INFORMATION BANK STRUCTURE

INFORMATION BANK

INFORMATION BANK

INFORMATION RELEASE

INFORMATION BANK CD'4TROL

INFORMATION BANK

INFORMAT ION

INPUT DATA SETS

I NOUT

C.10

REV. B
KEYW]RDLIST

REQ

54.0

llc).O

lO0.O

97.0

I16.0

23.0

60,,0

01.0

90.0

121.0

121.0

I?i.0

3G.O

30.0

3t.O

33.9

34.0

11.0

15.0

38.0

44.0

97.0

99.0

27.0

99.0

i0 3.0

122.0

34.0

46.0

2_9.0

79.0

_.0

8.0

57.2

33.0

33,0

33.0

33.0

34.0

4.0

4.0

37.0

57.2

5.3

3_.0

37.0

43.0

I03.0

KEYWORD

INPUT

INPUT

INSERT

INSTALLATION

I NSTALLATION

INSTRUCTION

INTEGRITY

INTEGRITY

INTEGRITY

IN[ELLIGENT TERMINALS

INTELLIGENT GRAPHICS TERMINALS

I_TELLIG_NT

INTERAC TIVE

INTERACTIVE COMMANDS

I_TE RACTIVE TERMINALS

INTERACTIVE TERMINAL SESSION

INTERACTIVE JOB

INTERACTIVE QUERY LANGUAGE

INTERACTIVE PROGRAM DEVELOPMENT

INTERACTIVE USFR

INTERACTIVE MODE

11 TE RF AC E S

INTERFACES

INTE RFACE

INT F RF AC E

INTERFACE WIT_

INTE PF ACE

INTEQMEgIAT{ RESULTS

INIERMEDIATE RESULTS

INTERPRETATION

INTERPRETATION OF C_MMAND SEQUENCES

INTERPRET

INTERPRET COMMAND

INTERRUPTION SUMMARY

INTERRUPT

INTERRUPT AID RESUME

INTEPRUPT A_D RESUME CAPABILITY

INTERRUPT EXCUTION

I_TE RPUPT

INTERRUPT

INTFRRUPT JOB

INTERRUPT

IN-WORK SUMMARY

IPAD COMMANDS

IPAD CONTROL

IPAD SYSTEM ADMINISTRATOR

IPAD SYSTEM

IPAD SYSTEM

C.11

REV. B
KFYWOPD LIST

REO

lO3.O

104. 0

104 .0

I13.0

I15.0

116.0

44.0

127.0

34.0

4.0

4 6.0

46.0

5('.0

b7.1

4.0

46.0

45.9

4.0

45,0

4.0

I0. 0

34 .0

44.0

45.0

47.0

50.0

c_8.3

50.0

24.0

24.0

24.3

25.0

24.D

73. 0

55.0

4.0

9.0

QS.0

126.0

125.0

119.0

46.0

4.0

19.0

4.0

4.0

5.0

5B.O

KFYWORD

IPAD SYSTEMS

IPAD SYSTEM

IPAD _YSI EMS

IPAD SYSTEM

IPAD SYSTEM

IPAD SYSTEM

IPAD UTILITIES

I PAD

J']_ CONTROL

JOB EXECUTION

JOG EXECUTION

JOB EXECUTION

JR_, EXEC UTI'DN

JOB INTEGRITY

JOB LOADING

dO_ MONITORING

JOB PREPARATION

JOB SAVING

JOB SEOUENC _

JOP, STATUS

JOB STATUS

JOB SUBMITTAL

JOB

JOB

JOB

JO£

KEY,/ORDS

KEY ACTIVITIES

LEARNING COMPUTEP

LEARNING UTILITY

L EARNINC_

LEARNING

L_ARN

LIBRARY CATALOG

LIMITS

LIMIT ACCESS

LIMIT COMMANDS

LINEAR ALGEBRA

LINES

LINF DENSITY

LINE DRAWING

LINKED PROGRAMS

LINK PROGRAMS

LIST

LOAD MODUL_S

LOAD

LOCAL COMMANDS

LOGICAL DATA _ODEL

AND MONITORING

C.12

REV. B
KEYWDRDLIST

REO

_mw

66.0

g5.0

67.0

37.0

85.0

Ig.O

20.0

20.0

20.0

69.3

13.0

13.0

51 .0

51.0

50.0

43.0

50.0

52.0

52.0

95.0

IS.O

IE_.O

18.0

21.0

43.1

21.0

21.0

Ic_.O

2] .0

21.3

21.0

21.0

4.0

54.0

122.0

44.0

44.0

$7oi

_7 .i

92.0

54.0

i17.0

117.0

53.0

109.0

23.0

34.0

5b.0

KEYWORD

LqGICAL DATA MODEL

LOGICAL OPERATIONS

LO_ICAL STRUCTURE

LOG OFF

LOSS OF DATA

MAILING LIST

MAILING LIST

MAILING LIST UTILITY

MAIL LIST

MAINTAIN DATA RELATIONSHIPS

_ANAGEMENT ]ATA

MANAGEMENT QUERY LANGUAGE

MANASEMFNT

MANAGEMENT SUPPORT

MANAGER

MANIPULATING DATA

MANPOWE R RESOURCES

MANPOWER RESDU,_CE REPORTS

MA _,iPOWE R RESOURCES

MATHMATI CAL OPE RATIONS

MENU BUILDING

MENU BUILDING UTILITY

MENU

ME,SAGES Tf] OTHER USERS

MESSAGES

MESSAGE DISPLAY

_ESSAGE FILE

MESSAGE RECEIVER

_ESSAGE RECEIVER

MESSAGE TO DESIGNATED USER

MFSSAGE UTILITY

ME SS AGE

MESSAGE

MESSAGE

MICROFILM PLOTTER

MIXED MOO E

MODIFICATION OF PROCESSES

MODI FICATIDN LOG

MODIFICATION HIST]RY

MODIFY DATA STRUCTURE

MODIFY SUBTASK STATUS

MODULAR DESIGN

MODULAR

MONI TDRING

MONI TORING

MONITOR PROGRAM

MONITOR PROGRESS

MONITOR RESOURCES

C.13

REV. B
KEYWORD LIST

REO

e_m

23.0

6_.0

36.0

]Q.O

114.0

114.0

88.3

g g.0

6b.O

120,3

I03.0

104.0

104.0

5E_.O

43.1

80. 0

26.0

2.0

53.3

53.0

q5.0

110.0

ii0.0

123.0

129.0

129.0

123.0

120.0

33,0

13.0

50.0

15.0

25.0

25.0

15.0

73.0

29.0

69.0

57.0

19.0

lq.O

ig.o

lq.O

47.0

5.0

i18.0

42.0

42.0

KEYWCRD

MONITOR

MOV= DATA AREAS

MULTIPLE VIEWING

NAME

NATIONAL SECURITY

NATIONAL

NEED TO KNOW

NEED TO KNOW

NESTED DATA AREA

NON-INTELLIGENT GRAPHICS TERMINALS

NON- IRAD SYSTEM

NON-IRAD SYSTEM

NON- IPAD SYSTEMS

NCN REDUNDANT

NOTIFICATION IF USER'S ABSENCE

NOTIFICATION

NOVICE

_,OVICE

NUMBER OF ACTIVE JOBS

NUMBER IF SUSPENDED J_BS

NUMERISAL DI FFER='_TI AT ICN

NUMFRI CAL

NUMERICAL ACCURACY

NU_'ERICAL DATA

NUMERICAL C]NTRO L

NJME RICAL

NUMERIC TO GRAPHICS

N.C. CAPA_ILITES

OBTAIN HELP

OFFICIAL PROJECT DATA

OFFLINE

ON-LINE DATA DEVELOPMENT

DN-L INE INSTRUCII']N

ON-LINE INSTRUCTION UTILITY

ON-LINE PROGRAM DEVELOPMENT

ON-LINE STORAGE

OPERATING SEQUENCE

OPERATIONS DN DATA RELATIONSHIPS

OPTIONAL AUTOMATIC REPORTING

DRGANI ZATION

CIRGAN IZ ATION DISPLAY

ORGANIZATION LIST DISPLAY

ORGANI ZATIO_ LIST

OUTPUT DATA S_TS

OVERVIEW

PARAMETERS

PASSWORDS

PASSWORD CONTROL

C.14

REV. B
KEYWORDLIST

|

R=Q

i I I

41.0

39.0

41.0

23.0

23.0

i09.0

lOq. O

52 .J

37.0

21 .0

67.0

50.0

123.0

126,0

55.0

eO.O

81.0

37.0

119.0

4.0

8?.0

62,0

44,0

44 ,O

44. 0

48.9

44 .0

?5.0

125.0

89.0

57.1

30.0

74.0

28.0

9_.0

tO0 ._

23. 0

98.0

96._3

99.0

I00.0

b5,0

96.0

I00.0

23.0

105.0

KFYWORD

PASSWORD PROTECTION

PASSW F_RD

PASSWORD

PERFORMANCE

PERFORMANCE MONITORING

PFRFgRMANCE

Pr RFORMANCr MONITDRINC

PEPIODIC RE_3_T

PEQMISSION CODES

PERSONAL MESSAGES

PHYSICAL STRUCTURE

PLANNING PROCESSES

PLANNING

PLOTS

PL OTTER

P_INT OF SUSPENSION

PRELIMINARY DATA

PRELIMINARY DAT

PREMIUM CHARGE

PRIMARY USER INTERFACE

PRIMATIVES

PRINT

PRIVATE DATA SFTS

PR I VA TE

PROCESS DFF INITION

P_OCESS PLANNI NS

P_OCESS PLANNING A_D

PROCESS _EPORTS

PROCESS

DEFINITION

PROGRAMMED LEARNING

PROGRAMMING

PROGRAM ACCESS

PROGRAM CERTIFICATION

PROGRAM COMMANDS

PROGRAM DATA ACCESS

PROGRAM DEBUGGING UTILITY

PROGRAM DESCRIPTION

PROGRAM DELETI]N

PRCGRAM EXECUTIO'q MO_IITORING

PPOGRAM IDENTIFICATION

PROGRAM INTEGRATION

PROGRAM INTERFACE

PROGRAM INSERTION

PROGRAM ITEM _!UMBER

PROGRAM LIBRARY

PR _qGRAM LIBRARY

PROGRAM MONITORING

R_FIGRAM MODULES

C.15

REV. B
KEYWORDLIST

REQ

_wn

23.0

23.0

23.0

89.0

i05.0

57.1

8(_,3

23.0

30.0

47.0

q7.0

I00,0

122.0

56,0

7_ .0

13.0

39.3

56.0

50.0

56,0

55.0

56,0

56.0

50.0

e.O

gO, 0

112,0

112,0

112,0

78.0

8_.,J

12,0

12,0

75.0

6.0

Ii,0

28,0

75,0

ii .0

12,0

13.0

65.0

33 ._

33.0

_7,3

36,J

R4,0

3,0

KEYWORD

PROGRAM PERFORMANCE MONITORING

PROGRAM PERFORMANCE M_ITORING

PROGRAM RESOURCES MONITORING

PROGRAM READ SECURITY

PRqGRAM TRANSF-R

pRFIGRAM VERSIONS

PROGRAM WRITE SECURITY

ION DEVICES

S

C ONTROL

DicTA

IDENTIFICATION

MILE STONE

PLANNING

PLANNINC

RESOURCE MONITORING

SCHEDULF MONITORING

SCNEDULE CCNTROL

PPOSRAM

PROGRAM

PROGRAM

PR OGRA M

PROGRAM

PROJ FCT

PROJECT

PRnJECT

PROJECT

PROJECT

PROJECT

PROJECT

PP OJ E CT

PPO, JECT

PROJECT

PROJECT

PROJECT

PROMPTS

PROPRIETARY

PROPRIETOPY

PROPR IF TFIRY

pRrlTECTI3N

PURGE PERMISSION

QJERY ACCESS

QUERY DATA

_UERY HEADER DATA

QJERY INFORMATI CN

QUERY JOB STATUS

QUERY lANGUAGE

QUERY PROGRAM

OUERY SPECIFIED

QUERY

QUERY

QUERY

OUERY

QUIT

OUIT

RANGE CHECK

REAL TIME MESSAGES

RECOVERY

RECTIFY ERROR

AND CANCEL

DATA

INFORMATIO_

BANK

r)ATA

RESULTS

UTILITY

PROTECTION

SUBSET

AREA

C.16

REV: B
D

D

REQ

Qm_

123. 0

2Z.O

47.3

31.0

8C.0

el.O

115.0

52 .0

32.0

32.0

66.0

17,0

4_.9

111.0

17.0

17.0

b2.0

55.0

4.0

i0.0

I0.0

4.0

35.0

10,0

i0.0

I0.0

51.0

51.0

57.0

52.3

III.0

52.0

53.9

23.0

52.0

23.0

3_.3

106.0

106.0

28. 0

4.0

28.0

34.0

4.0

55.0

9.0

66.0

54.3

KEYWDRD LIST

KEYWORD

REDUCE

REFERENCES

REFERENCE TO DATA

REFRESNED GRAPqICS TERMINALS

RELEASED DATA

_ELE_SED DATA

RE LIABILITY

REMAINING RES3URCE REPORT

REMOTE COMPUTER

RE MOTE

REORGANIZE DATA AREAS

REPORTING UTILITY

REPO:_TS

REPORTS

R_PJRT GEN_PATICN UTILITY

REPORT

R E PORT

REPORT

PEOUEST HEL_

REOUF ST RESOURCES

R=QU_ST STAT_S

REOUEST TUTORIALS

RES OURC_S CONSUMED

RESOURCES USED

RESOURCES REMAINING

R ESO URCE S

RESOURCES AVAILABLE

RESOURCES EXPENDED

RESOURCES USED

RESOURCES REMAINING

RESOURCES

RESOURCE CRNTROL

RESOURCE INF3QMATID_

RESOURCE MONITFJR ING

RESOURCE REPORTS

RESOURCE

RESPONCE TIME

RESPONCE TIME

RESPONCE

RESTART EXECUTI3N

RESTART JOB

RESTART

RESTART

R_START

RESTART

RFSTRICT COMMANDS

RE STRUCTURE DATA ARE AS

RESUME A TASK

C.17

REV. B
KEYW3RD LIST

REO

33.0

7G.3

73.0

45.3

46.0

51.0

34.0

33.0

24.0

25.0

32.0

32.0

32,D

4.0

9_.0

122.0

51.0

56.0

57.3

56.0

53.0

56.0

50.0

122.0

37. O

16.0

39.3

88.0

89.0

91.0

96. 0

I13.0

114.0

119.0

15.0

70,3

24.0

24 .0

4.0

29. 0

29.0

29.0

5?.0

50.0

126.0

_2.0

37.0

37. 0

KFYWORD

RESUME

RETEK'TIDN CLASSIFISATION

RETRIEVE A_CHIVED DATA

REVIEWING FINAL RESULTS

REVI_WIMG INTERMEDIATF RESULTS

REVIEWS

REVIEW INTERMEDIATE RESULTS

REVIEW RESULTS

SAMPLE PROBLE MS

SAWPLE PROBLEMS

SATELLITE

SAT=LLITE C3MP UTER

SATELLITE C3M_UTER SUPPORT

SAVE

SCALING

SCANNING UNITS

SCHEDULES

SCHEDULE C_NTRUL

SCHEDJLE DAT_

SCHEDULE MONI TDRI'_G

SCHEDULg

SCHEDULE

S:HEDULING

SC_020

SD JSER

SE ARCH

SECJRITY CLASSIFICAT IDN

SECURITY CONTROL

SECURITY CONTROL

SECdRITY CDNT_3L

SgCJRITY C{]N TPD L

SECURITY

_FCURITY

SEGMENTS

SELECTIVE DATA DISPLAY

SELECTIVE PURGE

SELF-TEACH

SELF-TEACH COMPJTER

SEND MESSAGE

SEQUENCE C3'_TINUITY

SEOJENCE I'4TERPR FTAT I [_N

SEQJENCF

SESSION RES3U_CE RFPDPT

SET _F SYMBOLS

SH APE S

SHARED DATA SETS

SHORT OURATIDN

SHORT DURATION USER

C.18

REVo B
KEYWORD LIST

RE_

110.3

108.0

2.0

2.0

38.3

]22.0

60.0

15.0

06.0

37.0

16.0

65.0

96.0

128.0

38.0

3P._

37. 0

65.0

37.0

i 28.0

43.1

4.0

50.0

4.0

111.0

53 .D

53.0

56.9

i0.0

48.0

53.0

54 .0

_5.0

91.0

2_.3

54.0

28.0

9].0

4.0

55.0

72.0

53._)

50.0

_3.0

54.0

56.0

54 .0

KEYWOR9

SIGNIFICANT DIGIT

SIZE DF IPAD

SKILL LEVFL

SKILL

SLRT

SOFTWARE

SOURCE AND OUALITY

SOLJRCE MODULE CHANGES

SOURCE

SPECIFIED W3R< PERIOD

SPELLING CHECK

STANDARDS

STANDARDS

STANDARD GEOM?-TRY

STANDARD LIMITING

STANDARD R E SP'INCE

STANDARD USER

STANDARD VALUE

STANDARD

S TA_IDARD

START-FINISH PERIOD

START JOB

START PROJECT

START

STATISTICS

STATUS OF ACTIVF JOBS

STATUS OF SUSPENDED JOBS

STATUS R EPO_TS

STATUS

STATUS

STATUS

STATUS

STATUS

STATUS

STEP-BY-STEP ; XECUTION

STr_P A TASK

STOP EXECUTION

S TOP

STORAGE

SUP MIT BATCH JDB

SUBTASKS

SUBTASK DATA AREA

SU_TASK MONIT]RING

SUBTASK

SU BT ASK

SJBTASK

SUBTASK

SUB TASK MODIFICATION

ES PONCE TIME

C.19

REV. B
KEYWDRD LIST

REO

_oo

KFYWORD

57.2

9b.O

125.3

51,0

55,0

l.O

i03,0

40,0

Ol.O

i0_, 0

i16,0

i0_ .0

ql,O

60.0

60.0

37 ,O

21.D

37.0

ile,O

115.0

107.0

16.0

50.0

50.0

54.0

2,.0

24.0

2_.0

44 ,0

122.0

31.0

120.0

121,0

33.0

50.0

40.0

43.1

31.0

B] .0

15,0

llg. O

I0_.0

125,0

37.0

R6,0

4.0

34.0

I05,0

SUMMARY

SUMMINS

SUPFR POSITION

SU PPOR T

SUSPEND

S Y NT AX

SYSTEM ACCESS

SYSTEM ADM I'_I STRATOR

SYSTEM ADMINISTRATION

SYSTEM ADMINISTRATOR

SYSTEM AVAILABILITY

SYSTEM CAPACITY

SYSTEM CONTROL

SYSTFM DATA

SYSTEM DATA IDENTIFICATION

SYSTEM [had

SYSTEM MESSA_FS

SYSTFM OVERLOAD

SYSTEM P ARA_ETERS

SYSTEM RFLIABILITY

SYSTEM WORKING SIGNAL

TAP LE OF CONTENTS

TABJLAR DISPLAY

TASK

TASK

TEACHING COMPUTER

TEACHING SURVEILLANCE

TEACH

TECHNICAL PROCESS

TEKTRONI CS

TERMINALS

TERMINALS

TERMI NALS

TERMINAL SESSION

TEQMINAL

TERMINATED

TERMINAT:D USER'S TASK

TEXTUAL/GRAPHICAL lq TERACTIVE

TEXTUAL T E_'MI NALS

TEXT EDIT

TEXT

TIM E

TOOLS

TOP PRIORITY

TRACE OF ANTECEDENTS

TRANSFER DATA

T_ANSFER

TRANSFER

C.20

TERMINALS

REV. B
KEY_DRD LIST

REQ

mtm

K_YWORD

R.O

9.0

21 .J

25.0

5.0

40.J

40.0

40.0

90.0

III.0

70.0

70. 0

43.0

45.0

85.0

40.0

iii .0

II].0

_3.1

_3.1

g.O

8_.0

57.2

26.0

b.O

P6.0

26.0

46.0

37.0

43.0

43.3

27.0

75.0

39.3

?6.0

27.0

27 .D

I01.0

1.0

21.0

37.0

6_.9

43.1

2.0

43.1

88.0

47.0

48.0

TRANSLATE

TRANSLATE COMMAND

TRANSMIT MESSAGE

TUTORIALS

TUTORIAL AIDS

UNACCEPTABLE IDENTIFICATI DN

UNACCEPTABLE USER ID

UNACCEPTABLE USER IOENTIFICATION

UN AUTHORIZFD ACCESS

UNAU THOR I ZED

UNIQUE NAME

UNI OUR

UNIT CqNVERSIRN

JNIT CONVERSION

UNPLANNED DATA MODIFICATION

UN. UCCESSFUL Accrss ATTEMPT

USAGE ACCOUNTING

US AGE

USER ABSENCE AND REASSIGNMENT CONTROL

USFR ABSENCE CONTROL

US;R ACCESS CONTROL

USER ACCESS

USER ACTIVITY CH_CK LIST

USE R A IDS

US ER AIDS

USPR ASSISTANCE

USeR ASSISTA_ICE UTILITY

USER ASSIST

USER CATEGORIES

USER CLASSIFICATION DISPLAY

USER CLASSIFICATION

USFR COMMANDS

USeR DATA ASSESS

JSER IDENTIFICATIg_

USER INSTRUCTION

USER INTERFACE DESCRIPTION UTILITY

USER INTERFACE

USeR INTERFACF

USFR LANGUAGES

USER MESSAGES

USER PRIORITIES

USER READ SECURITY

USER REASSIGNMENT

USER SKILL LEVEL

USER TERMINATI3N

USER WRITE SECURITY

USER

USER

REV. B

C.21
KFYW]RDLIST

RFO

_mo

14,0

14,D

87,0

118.0

g4 ,0

122,0

llg,O

1,0

37,0

3,0

8,0

43,1

55.0

54.0

62.0

5b ,0

51 .0

57.2

KEYWDRD

UTILITY FUNSTIONS

UTILITY PROSRAMS

VALI PAT ION

VARIABLE PARAMFT_RS

VE R IF ICAT ION

VG33,30

VIFW TRANSFORMATION

VOCAf_UL ARY

WAITING

WARNINGS

WARN ING

WARNING

WBS

WQPK I

WOPK

W']RK

WOrK

NG PHASES

NG

_RFAKD_WN

PRDGRESS

SUMM _ Y

OF TA SK

STRUCTURE

REV. B

C.22