Upload
others
View
10
Download
1
Embed Size (px)
Citation preview
DOCUMENTATION OFDECISION-AIDING SOFTWARE:
INFER SYSTEM SPECIFICATIONDECISIONS AND DESIGNS INC.
Dorothy M. AmeyPhillip H. Feuerwerger
Roy M. Gulick
June 1979
V- DL,..-Oq QAM
DEES D ADVSAC D PROJCT AGENC
Office of Naval Research * Engineering Psychology Programs
UUTKJIUTT~A I** 11 28 ISOIApwoovol 1 pu1il
777 P.-.-.-.- -- -
p "
DOCUMENTATION OF DECISION-AIDING SOFTWARE:V INFER SVSTEU SPECIFICATION
by
Dorothy M. Amey, Phillip H. Feuerwerger, and Roy M. Gulick
Sponsored by
Defense Advanced Research Projects AgencyARPA Order 3469
June 1979
i-
Q.1
oeCI:510ns uno oe5imf, inc.Suits 600, 8400 Westpark Drive
P.OBox 907Mc Lean, Virginia 22101 OFTW TART:- A -
4703) 821-2828 u"
.' .
. .1
. .. . . . ......
'
ONCSIFI =o E. 1IS t-. .::
Suite ~ ~Afw 600 840WetPk rv W"
P.O.Boxw~l 907- - -- "
CONTENTS
Page
FIGURES ii
1.0 INTRODUCTION 1
1.1 Purpose of the System Specification 1
1.2 References 1
1.3 Terms 21.3.1 INFER 21.3.2 Terms 2
2.0 DESIGN DETAILS 3
2.1 Background 3
2.2 General Operating Procedures 3
2.3 System Logical Flow 3
2.4 HIPO Documentation 6
F or
Di LtAvail ,
Dist
1
ii1
FIGURES
Figure
2-1 LEGEND OF HIPO SYMBOLS5
2-2 OVERALL DIAGRAM AND VISUAL TABLE
- OF CONTENTS 7
INFER SYSTEM SPECIFICATION
1.0 INTRODUCTION
1:1 Purpose of the System Specification
The INFER System Specification is a technical document
written for software development personnel. Together with
the INFER Functional Description, the System Specification
guides the software development effort by identifying the
functional requirements and by providing structured logic
diagrams that depict the flow, control, and processing of
VW information within the system.
The System Specification is generic documentation
intended to guide and facilitate the preparation of thelanguage-specific and computer hardware-specific program
documentation and coding that are necessary to implement and
operate INFER at an installation.
1.2 References
1.2.1 IBM, HIPO--A Design Aid and Documentation Tech-
nique. Technical Publication GC20-1851-0.
White Plains, New York: IBM, October 1974.
1.2.2 Amey, Dorothy M.; Feuerwerger, Phillip H.;
Gulick, Roy M. Documentation of Decision-Aiding....-:.Software: INFER Functional Description. McLean,
Virginia: Decisions and Designs, Inc., June
1979.
1.2.3 Amey, Dorothy M.; Feuerwerger, Phillip H.;
Gulick, Roy M. Documentation of Decision-Aiding
Software: INFER Users Manual. McLean, Virginia:Decisions and Designs, Inc., June 1979.
1.3 Terms
1.3.1 INFER - The name of the system, INFER, is an
abbreviation for inference, reflecting the logical process
supported by the software.
i,11.3.2 HIPO - The specification uses the standard Hier-
archy plus Input-Process-Output (HIPO) diagramming techniqueto depict the structural design and logical flow of thesystem. A legend explaining the HIPO diagramming symbols isincluded. Reference 1.2.1 provides a complete description
of the HIPO documentation technique.
2
4..
*. . . .
. . . . . . . . . . ..- . .,. .
2.0 DESIGN DETAILS
2.1 Background
" Systems development personnel should refer to the INFER
Functional Description, reference 1.2.2, in conjunction with
the documentation contained in this specification. The
Functional Description details the inference models imple-
mented by INFER and discusses the specific functions that
the software must perform. In addition, systems development
personnel may wish to refer to the INFER User's Manual,
Reference 1.2.3.
- 2.2 General Operating Procedures
INFER is a menu-driven system. That is, the system is
designed to interact with the user by presenting a sequen-
*' tial hierarchy of menus and asking the user to respond by
selecting one option from the current menu. If the user
does not select one of the menu options, the system displays
the previous menu. In this manner, the user moves up and
down the hierarchy, as desired. Whenever data entry is
required as a result of option selection, the system spe-
cifically requests the data and specifies the format.
The system is also designed to be generally forgiving
of procedural errors by the user.
2.3 System Logical Flow
INFER is a hierarchically structured, modular software
system. The system structure and logical flow lends itself
to presentation in the form of HIPO diagrams, which are
contained in this document.
3. -" .3 .!
The main purpose of the HIPO diagrams is to provide, ina pictorial manner, the complete set of modular elementsnecessary to the operation of INFER including all input,
"output, and internal functional processing. This is done by*: displaying input items to the process step which uses them,* defining the process, and showing the resulting output of
the process step.
The HIPO documentation diagrams are designed and drawnin a hierarchical fashion from the main calling routines tothe detail-level operation/calculation routines. Extended
written descriptions are given below a HIPO diagram wheneverit is deemed necessary.
A complete explanation of the symbolic notation used in
the HIPO diagrams appears in reference 1.2.1. An abbre-viated legend for the symbols used in this specification ispresented in Figure 2-1. Note that:
a. External system subroutines are depicted partlyin the Process block and partly out. Internal
subroutines are shown within the Process block.
b. Overview diagrams show general inputs and outputsonly, whereas detail/subroutine-level diagrams
show specific input/output tables and/or displays.
c. Rectangular boxes inside the Input/Output blockareas are generally used to denote single dataitems. Two or more boxes are grouped to show thatseveral data items are input/output.
d. Rectangular boxes inside the Process block indi-cate repetitive subprocesses.
-. 4
. . . .. .- . . .- -.- . -- ., , , - . . ' -- _ ," ,"-,- , ,- ," , o.- --. - o - . , .-. - - '
wI
,'". - c€atrol ee
I I Subroutine
=> Date mvment
Pointer
_> Data reference Jgocal rouping
}.Keyed data arrvso
I I
fumction Identified butgot included in package
II IjOff-page connection arrovs -
Iwo~ General f low of data D teme1111mmong subproceses Any general input
t dt nor output iter*, ..' Subroutine In~vke
(Retturn to smde to calling
routine)
outine receives control Input foutput mdim---In includes drun. disk.
Storage tape diskettes
Routine ezito or return Control
< jj) 1*fointin d~hley by f agnmetic tape impute
em line ndicatere--prpted eutput ndium
-. "by progrm esecution or bykayboard Input, especially CRT
Figure 2-1
LEGEND OF HIPO SYMBOLS
U' "5
7 :-7:
The HIPO diagrams appear in the next section, which
completes the System Specification.
2.4 HIPO Documentation
The HIPO diagram identification numbers and figure
numbers used in this section stand alone; i.e., they start
with 1.0, increase hierarchically, and are independent of
the numbering scheme used to this point in this document.
Figure 2-2 is a system structure chart and represents
the overall program logic flow in a visual table of contents.The Visual Table of Contents diagram shows the hierarchical
structure, the functional description labels, and the diagram
(chart) identifiers of functions of INFER.
IM;6
6I
->
z
wa'
w LII
9cc
7z
* . . C) U
- CI
LU Iio zZ44r
-II _-- CDE'fli a
= UA cl I.,2,4 0 -
ca~~~~. &U. *0- o .1l M 0
LU~~~~. L4 Ic mA z E. L>'TL)c
C2. ~
m 'A
.2 000 0
0 0 0 0. 0 404f
E~ CL
-
01
* *0 :t 0 c~0 -0 CL
c S-- 0 L
ii 1C 0 .-0
0. E 0
zC '* " : : 'to UU f% 0L E iI-S.
E~~~~ 0% .~ Lft0r% 0 ) m
S.2 f I 0V 0 2-
- rx
dS7
is 068 0 -'g 9j CL
ca MA f LC ' c eU Cc
49 -- 16 &U 2
*R u=O E ci cc uO CL
a a 8
. ..... ..'A
rCd.
CD1
a'Lla:
0
Ez
a-c
C I *C
r- E 0
CL
0 CL
'A " . -IE 0
CII~CS. 0 oa- x
wm
- - - - -- ----- -L-' --"--
_.IF€_-, -dI -O
0'
'-U I-E =a
I..-..>
E. CL
49-
Co4-
co=_ w Sr-
0 r IT -
CD - c : V l=- ~~:. -. E, = ' _-
0
V.0
,- -, B.,
mme
C-V=
E 0, '0
ac *s-c *
a -= 8 E
,.. o U
*L E
0 S
Woo
SO ~ O CLEj ~ .-n 0.~~.
0. .- c
cJ
mu 1A'
am c
LC -
@40 10
-7o I=' LI' II10 .!. 0
oc~ I to4
ICS
5 0.5
o~t ,.. ..
4.954 ,. 00
N CN
cc
*c *C
4- CC.EO*. u
ILC l= ac ~C 01
CI0 Ms..ow 0
SUS
~Ig~ iiLu m LU
Si 'M a
c b; c
r 7.
LABELS
EVENT NAMES OUTCOME NAMES for events (-N arrays)
212
N 21 1
K
NODE STRUCTURE TABLE* A•
* J Number of outcomes for node 3NI- Number of associated outcome probabilities
from influencing nodes (number joint probabilities)
The number of influencing nodesspecified (node type)
The node numbers ofdirectly influencing nodes
PROBABILITY TABLES
1 0N Probability arrays
2 CONDITIONED
Conditional probabilities
10____0_____
UNCONDITIONEDa0c
2 -\ Directly assessed value
100
HIPO Figure 2.1INFER MODEL DEFINITION TABLES
12
CONDITIONED PROBABILITIES1 2 910
11
2NODE 1: Terminal Probabilities
N-
INDICATOR TABLES
LABELS STATUS
12 2
22
NindicatingOff
Influenced eventnode number
LIKELIHOODS
1
5 likelihoods withzero-fill values
k
H IPO Figure 2.1
INFER MODEL DEFINITION TABLES (continued)
13
- - -, - -. - .
I-c
l1 .4-1 p
-4
C" 0
V 4 4
0 4D
0 CE N .3E. c
c0 E 0
.00 . .. 00( :Ih E.t
o r- *%
E.
SL mu !6 . :8 V 12
0n rR. - CL
.4E 9I'- S-C = -
Z.z:14 4
wIWEATHER I
-~---- Display 1
WEATHER -1
Display 2
IRAIN IITEMPERATUREI
IRAIN
Display 3
ICLOUDS I 1HUMIDITY'
1w ITEMPERATURE I
f Display 4
HIPO Figure 2. 1.1
EXAMPLE OF NODE STRUCTURE ELICITATION
15I
=DI6 LmE o co
I *=.. 0€.=
. w 14 ji 4 c *:-"-I €_I ,-I.= Se
Uz
CD -------- -
i= - ISi
-E c 0_=
i E' =ui ..- o- i~
c .91-0
E
S
'". ai; 1I3
7E C
ca I M
&. S
8 "I ~ .~
.- E" i
I ii Li9
C 4'.
-t Eo ~g
W6 tt
A LaAm me
I',. .; 0j an j~~~
zc r~l 'IllIM 16
0 40
90= 0Co _ 4
cc
x C-S
4- ->
cm U
S L E 0~og J
W, M, .0
04 E 0 m .2 0 .00 .0 C
0. XV m 0.0 E 3: - .
E~ ~~ E isUS. ~ ~CL a, & E-0 = w
UU~ 4- WC W 0 ~W W0u W '
*~~~~ C. L ~~M2 cv 0S .0 W&
C~~~~ ':L L
-L LE,
o. -TC 0 0"o E CL4 *- g
oU IU z U.o L C
2 i 01 ~ .I
-d"
c *
IUi a,.,CL 17
cc 0 0
OC
-~ *.r
Ecc 0,
C
0C
4 -
A2 0
E-
-C 0 '
CSC
'.1..1
4a a .
aMaCa' C I
* 4.
I p
Au --
, - Ma
0t 0" .- m-€
0 E
0.
4l ..s C
S
z 0 .0 w. j.: Z-L** *.0 u D
-W91
c a C~ 0
70. *. *,E0
Sis C =
-~~u 4 0 ~ ;a
4,7~~4 'A(3 .
fA
lo'. CL
im I9c19
ci OW dc
Ew~ c;a
.0
0 .
I C38
a,. 0 s Z.
.4E COb I~COhci;* -t 00 .2.
.0 -L
0 c0
*0 & .2
-em a, .5C3
2a c. 0
C I! ..
1I 9- 4-
CLL
______________I
(~I .N *
0. 7___ ____ ___L z .20
I U000
~0
CL-
00 000
-. 2
c 0.
oMU.
00
00- 0E
a. 0 0iE C
CL - W.C.C
0*-- S
0 E
C *-
Eu O U
*5121
Owso 1- 4
-1-L
0~0
0 C
Icc
4M,
Q 0U' 0E.00
r4-
4-. 02
0 C
cc 0c
C, CL
0~ c ~0 0
EC 0
z MLU -a. 1.-
t: a saam T .- E
0 LC
ac ri22 '
Fi 5w 1 1C
I-W
C)-
CL
.4- 0 m-(M
00 t C.200'0~ 0'iE m- 00s
C.CC r&C : -0W~t >=
0
6u~ V ta! CL cMI-rn 2W I -1w E.~ WE
4c. LM !J mi ZOOzl CV
23c
-7 -7 I -
no
P
46-c
0 IL a n 4-.
F'U
CD0
.0
00
4- -
E- M
0 0
>. 'U
0 E
0. CLC0 cc o
CD-0
SE E
-L (0 0L 2
-81, 0lIS N,
0.
0 Ccw 6.Uc
ul CL%- E
24~
I i : t-Ni"
*~w Iwl 0
a~ a- ccc
C cl£- . '
CC
0E
C E
4-4.
.L0 0
,. .._- p.
.'. 8 ,, ._'"E " a Z n CO c-2. :
.. ...
40 ."0 0."
, 8o
Cc 2
Z so 0 to
E. .
45 o E
0)~~~ 0). £c I . 9. j 0 W= aN
U
us I- Q. 4 .U. 0. Wng
ac 0) TLvE2
0.0
01
CLC
I; E
Si,
'.,= ~ .C o
-~ .- - ,~-100 * 0 S -
~'5 .iU - 0
X 0cm 4
c CL
0
W6
cc2
£
-l amr
a I I
ae uE an
26
*1*0 ca
0.0
V J
WO 0
.. r
o 0j
0 v-
oi
.... 27
* U*_ _ _ _ _ _.5
E
0 C
~C E0 'a* 0 4
E E 0 (~ 'U h. _L
2 w
E 0m
1 0.E~ SV
266
66
0
law a
0.a
IFS-IE4U
0 . 0 .
LD 'm
c *0
co
0.
o 1
- o
C CE
IDJ
E . 2 a ccI~U
z.: N-
CL0E
II.'U~~~ to1
__ __ _
P___
cc EE
H I')11111 c"
29
$- VA --. -
W6 10 a 1 cc
I-m
~> ZC 0w
o go.4- 0
0~ 0 W
h..~~ ZO- W
-. 030
0. ...0 W 4
.M -0 0 0Lr_ CD~
0I
uj -. 0'cc.=a. .2 .S.CD C4 4'
9 El
w sm
* 0 z4
30.
a" "1 .. 0 'j
!i--
C 0 B
_0. 9 C >
i 0 o m "z E .+
,, 0 a) _%0* 0 S o--:t.= E .w o-
CLM
' 51
gog
AOX
"-"1 , i
UI
-i 'U -SO
- I--i l
my IIso
I WI ~ cm
I-. 02
C; E
S c
4-S E
'UU
C.3
o Co
310 4-1 Ic
32S
~u~ u -.a. a
.
Co_ _ _ _ _
2U
ciS
g ~ E
R .0
C
E C- C SCD4-
U.x71J~~
U.
(3*o- tcc~
------ mi S--
9 ~ ~ u 0 . '-'33
0 4
ccU
Los cc I
00 0 I
cm
0r
.0 .0
> 2-
U, 0 & 0cc4- 0 - ~< C 0. o>.0 0
0 a' Z. 120-
-~~ ~ 008 0 .~1 M-- ( .2 -
UJU
& tn16 ao E4
* 4U2 IN
'a, 4ac
34U
W- Ri i T
C -
Lu cc
> E
L'ULAso S-0 Lai 4
ca . L
E 0..* I>U)~
* C 35