2005-01-14T12:33:52+01:00
2005-01-14T12:33:52+01:00
iText1.1 by lowagie.com (based on itext-paulo-142)
engines={image=false textcolor=true vector=false text=true} tetml={filename={D:\drim\repository\projects\drim_124_0\metadata\8\0\804a3be86862b9892e45512da8254e56\804a3be86862b9892e45512da8254e56.para.xml} elements={annotations=false bookmarks=false destinations=false fields=false javascripts=false} }
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
1140
1
1
4
0
Connecticut
C
o
n
n
e
c
t
i
c
u
t
Avenue,
A
v
e
n
u
e
,
N.
N
.
W.,
W
.
,
Suite
S
u
i
t
e
1020
1
0
2
0
Washington,
W
a
s
h
i
n
g
t
o
n
,
D.C.
D
.
C
.
20036
2
0
0
3
6
SOFTWARE
S
O
F
T
W
A
R
E
CONSIDERATIONS
C
O
N
S
I
D
E
R
A
T
I
O
N
S
IN
I
N
AIRBORNE
A
I
R
B
O
R
N
E
SYSTEMS
S
Y
S
T
E
M
S
AND
A
N
D
EQUIPMENT
E
Q
U
I
P
M
E
N
T
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
Copyright
C
o
p
y
r
i
g
h
t
©
©
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
1992
1
9
9
2
RTCA/DO-178B
R
T
C
A
/
D
O
-
1
7
8
B
Prepared
P
r
e
p
a
r
e
d
by:
b
y
:
December
D
e
c
e
m
b
e
r
1,
1
,
1992
1
9
9
2
RTCA
R
T
C
A
SC-
S
C
-
167
1
6
7
/
/
EUROCAE
E
U
R
O
C
A
E
WG-
W
G
-
12
1
2
Uncontrolled
U
n
c
o
n
t
r
o
l
l
e
d
copy
c
o
p
y
when
w
h
e
n
printed
p
r
i
n
t
e
d
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Copies
C
o
p
i
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
may
m
a
y
be
b
e
obtained
o
b
t
a
i
n
e
d
from
f
r
o
m
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
1140
1
1
4
0
Connecticut
C
o
n
n
e
c
t
i
c
u
t
Avenue,
A
v
e
n
u
e
,
Northwest,
N
o
r
t
h
w
e
s
t
,
Suite
S
u
i
t
e
1020
1
0
2
0
Washington,
W
a
s
h
i
n
g
t
o
n
,
D.
D
.
C.
C
.
20036-4001
2
0
0
3
6
-
4
0
0
1
U.S.A.
U
.
S
.
A
.
Telephone:
T
e
l
e
p
h
o
n
e
:
202-833-9339
2
0
2
-
8
3
3
-
9
3
3
9
Facsimile:
F
a
c
s
i
m
i
l
e
:
202-833-9434
2
0
2
-
8
3
3
-
9
4
3
4
Please
P
l
e
a
s
e
contact
c
o
n
t
a
c
t
RTCA
R
T
C
A
for
f
o
r
price
p
r
i
c
e
and
a
n
d
ordering
o
r
d
e
r
i
n
g
information.
i
n
f
o
r
m
a
t
i
o
n
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
FOREWORD
F
O
R
E
W
O
R
D
This
T
h
i
s
document
d
o
c
u
m
e
n
t
was
w
a
s
prepared
p
r
e
p
a
r
e
d
by
b
y
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
167
1
6
7
of
o
f
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
It
I
t
was
w
a
s
approved
a
p
p
r
o
v
e
d
by
b
y
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
on
o
n
December
D
e
c
e
m
b
e
r
1,
1
,
1992.
1
9
9
2
.
RTCA
R
T
C
A
is
i
s
an
a
n
association
a
s
s
o
c
i
a
t
i
o
n
of
o
f
aeronautical
a
e
r
o
n
a
u
t
i
c
a
l
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
of
o
f
the
t
h
e
United
U
n
i
t
e
d
States
S
t
a
t
e
s
of
o
f
America
A
m
e
r
i
c
a
from
f
r
o
m
both
b
o
t
h
government
g
o
v
e
r
n
m
e
n
t
and
a
n
d
industry.
i
n
d
u
s
t
r
y
.
Dedicated
D
e
d
i
c
a
t
e
d
to
t
o
the
t
h
e
advancement
a
d
v
a
n
c
e
m
e
n
t
of
o
f
aeronautics,
a
e
r
o
n
a
u
t
i
c
s
,
RTCA
R
T
C
A
seeks
s
e
e
k
s
sound
s
o
u
n
d
technical
t
e
c
h
n
i
c
a
l
solutions
s
o
l
u
t
i
o
n
s
to
t
o
problems
p
r
o
b
l
e
m
s
involving
i
n
v
o
l
v
i
n
g
the
t
h
e
application
a
p
p
l
i
c
a
t
i
o
n
of
o
f
electronics
e
l
e
c
t
r
o
n
i
c
s
and
a
n
d
telecommunications
t
e
l
e
c
o
m
m
u
n
i
c
a
t
i
o
n
s
to
t
o
aeronautical
a
e
r
o
n
a
u
t
i
c
a
l
operations.
o
p
e
r
a
t
i
o
n
s
.
Its
I
t
s
objective
o
b
j
e
c
t
i
v
e
is
i
s
the
t
h
e
resolution
r
e
s
o
l
u
t
i
o
n
of
o
f
such
s
u
c
h
problems
p
r
o
b
l
e
m
s
by
b
y
mutual
m
u
t
u
a
l
agreement
a
g
r
e
e
m
e
n
t
of
o
f
its
i
t
s
member
m
e
m
b
e
r
and
a
n
d
participating
p
a
r
t
i
c
i
p
a
t
i
n
g
organizations.
o
r
g
a
n
i
z
a
t
i
o
n
s
.
The
T
h
e
findings
f
i
n
d
i
n
g
s
of
o
f
RTCA
R
T
C
A
are
a
r
e
in
i
n
the
t
h
e
nature
n
a
t
u
r
e
of
o
f
recommendations
r
e
c
o
m
m
e
n
d
a
t
i
o
n
s
to
t
o
all
a
l
l
organizatio
o
r
g
a
n
i
z
a
t
i
o
ns
n
s
concerned.
c
o
n
c
e
r
n
e
d
.
As
A
s
RTCA
R
T
C
A
is
i
s
not
n
o
t
an
a
n
official
o
f
f
i
c
i
a
l
agency
a
g
e
n
c
y
of
o
f
the
t
h
e
United
U
n
i
t
e
d
States
S
t
a
t
e
s
Government,
G
o
v
e
r
n
m
e
n
t
,
its
i
t
s
recommendations
r
e
c
o
m
m
e
n
d
a
t
i
o
n
s
may
m
a
y
not
n
o
t
be
b
e
regarded
r
e
g
a
r
d
e
d
as
a
s
statements
s
t
a
t
e
m
e
n
t
s
of
o
f
official
o
f
f
i
c
i
a
l
government
g
o
v
e
r
n
m
e
n
t
policy
p
o
l
i
c
y
unless
u
n
l
e
s
s
so
s
o
enunciated
e
n
u
n
c
i
a
t
e
d
by
b
y
the
t
h
e
federal
f
e
d
e
r
a
l
government
g
o
v
e
r
n
m
e
n
t
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
or
o
r
agency
a
g
e
n
c
y
having
h
a
v
i
n
g
statutory
s
t
a
t
u
t
o
r
y
jurisdiction
j
u
r
i
s
d
i
c
t
i
o
n
over
o
v
e
r
any
a
n
y
matters
m
a
t
t
e
r
s
to
t
o
which
w
h
i
c
h
the
t
h
e
recommendations
r
e
c
o
m
m
e
n
d
a
t
i
o
n
s
relate.
r
e
l
a
t
e
.
The
T
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
these
t
h
e
s
e
guidelines
g
u
i
d
e
l
i
n
e
s
was
w
a
s
jointly
j
o
i
n
t
l
y
accomplished
a
c
c
o
m
p
l
i
s
h
e
d
by
b
y
RTCA
R
T
C
A
SC-167
S
C
-
1
6
7
and
a
n
d
the
t
h
e
European
E
u
r
o
p
e
a
n
Organisation
O
r
g
a
n
i
s
a
t
i
o
n
for
f
o
r
Civil
C
i
v
i
l
Aviation
A
v
i
a
t
i
o
n
Equipment
E
q
u
i
p
m
e
n
t
(EUROCAE)
(
E
U
R
O
C
A
E
)
WG-12
W
G
-
1
2
through
t
h
r
o
u
g
h
a
a
consensus
c
o
n
s
e
n
s
u
s
process.
p
r
o
c
e
s
s
.
i
i
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Consensus
C
o
n
s
e
n
s
u
s
n.
n
.
Collective
C
o
l
l
e
c
t
i
v
e
opinion
o
p
i
n
i
o
n
or
o
r
concord;
c
o
n
c
o
r
d
;
general
g
e
n
e
r
a
l
agreement
a
g
r
e
e
m
e
n
t
or
o
r
accord.
a
c
c
o
r
d
.
[Latin,
[
L
a
t
i
n
,
from
f
r
o
m
consentire,
c
o
n
s
e
n
t
i
r
e
,
to
t
o
agree]
a
g
r
e
e
]
ii
i
i
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
TABLE
T
A
B
L
E
OF
O
F
CONTENTS
C
O
N
T
E
N
T
S
Page
P
a
g
e
-
INTRODUCTION............................................................................................................................................1
I
N
T
R
O
D
U
C
T
I
O
N
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
Purpose.................................................................................................................................................1
P
u
r
p
o
s
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
Scope.....................................................................................................................................................1
S
c
o
p
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
Relationship
R
e
l
a
t
i
o
n
s
h
i
p
to
t
o
Other
O
t
h
e
r
Documents
D
o
c
u
m
e
n
t
s
....................................................................................................1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
How
H
o
w
to
t
o
Use
U
s
e
This
T
h
i
s
Document..............................................................................................................1
D
o
c
u
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
Document
D
o
c
u
m
e
n
t
Overview...........................................................................................................................3
O
v
e
r
v
i
e
w
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
2.0
2
.
0
SYSTEM
S
Y
S
T
E
M
ASPECTS
A
S
P
E
C
T
S
RELATING
R
E
L
A
T
I
N
G
TO
T
O
SOFTWARE
S
O
F
T
W
A
R
E
DEVELOPMENT...............................................5
D
E
V
E
L
O
P
M
E
N
T
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
2.1
2
.
1
Information
I
n
f
o
r
m
a
t
i
o
n
Flow
F
l
o
w
Between
B
e
t
w
e
e
n
System
S
y
s
t
e
m
and
a
n
d
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Processes
P
r
o
c
e
s
s
e
s
..................................5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
2.1.1
2
.
1
.
1
Information
I
n
f
o
r
m
a
t
i
o
n
Flow
F
l
o
w
from
f
r
o
m
System
S
y
s
t
e
m
Processes
P
r
o
c
e
s
s
e
s
to
t
o
Software
S
o
f
t
w
a
r
e
Processes..........................6
P
r
o
c
e
s
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
2.1.2
2
.
1
.
2
Information
I
n
f
o
r
m
a
t
i
o
n
Flow
F
l
o
w
from
f
r
o
m
Software
S
o
f
t
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
to
t
o
System
S
y
s
t
e
m
Processes..........................6
P
r
o
c
e
s
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
2.2
2
.
2
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
and
a
n
d
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
............................................................................................6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
2.2.1
2
.
2
.
1
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
Categorization.................................................................................7
C
a
t
e
g
o
r
i
z
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
2.2.2
2
.
2
.
2
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Definitions...........................................................................................7
D
e
f
i
n
i
t
i
o
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
2.2.3
2
.
2
.
3
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Determination......................................................................................8
D
e
t
e
r
m
i
n
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
2.3
2
.
3
System
S
y
s
t
e
m
Architectural
A
r
c
h
i
t
e
c
t
u
r
a
l
Considerations..............................................................................................8
C
o
n
s
i
d
e
r
a
t
i
o
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
2.3.1
2
.
3
.
1
Partitioning.......................................................................................................................9
P
a
r
t
i
t
i
o
n
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2.3.2
2
.
3
.
2
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
........................................................................9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2.3.3
2
.
3
.
3
Safety
S
a
f
e
t
y
Monitoring...........................................................................................................9
M
o
n
i
t
o
r
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2.4
2
.
4
System
S
y
s
t
e
m
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
User-Modifiable
U
s
e
r
-
M
o
d
i
f
i
a
b
l
e
Software,
S
o
f
t
w
a
r
e
,
Option-
O
p
t
i
o
n
-
Selectable
S
e
l
e
c
t
a
b
l
e
Software
S
o
f
t
w
a
r
e
and
a
n
d
Commercial
C
o
m
m
e
r
c
i
a
l
Off-The-
O
f
f
-
T
h
e
-
Shelf
S
h
e
l
f
Software
S
o
f
t
w
a
r
e
....................................................................................10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
2.5
2
.
5
System
S
y
s
t
e
m
Design
D
e
s
i
g
n
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
Field-Loadable
F
i
e
l
d
-
L
o
a
d
a
b
l
e
Software
S
o
f
t
w
a
r
e
...................................................10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
2.6
2
.
6
System
S
y
s
t
e
m
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
Software
S
o
f
t
w
a
r
e
Verification.............................................11
V
e
r
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
2.7
2
.
7
Software
S
o
f
t
w
a
r
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
System
S
y
s
t
e
m
Verification
V
e
r
i
f
i
c
a
t
i
o
n
........................................................................11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
3.0
3
.
0
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE..........................................................................................................................13
C
Y
C
L
E
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
3
3.1
3
.
1
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Processes
P
r
o
c
e
s
s
e
s
.......................................................................................................13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
3
3.2
3
.
2
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Definition
D
e
f
i
n
i
t
i
o
n
......................................................................................................13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
3
3.3
3
.
3
Transition
T
r
a
n
s
i
t
i
o
n
Criteria
C
r
i
t
e
r
i
a
Between
B
e
t
w
e
e
n
Processes..........................................................................................14
P
r
o
c
e
s
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
4
4.0
4
.
0
SOFTWARE
S
O
F
T
W
A
R
E
PLANNING
P
L
A
N
N
I
N
G
PROCESS
P
R
O
C
E
S
S
.......................................................................................................15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
5
4.1
4
.
1
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process
P
r
o
c
e
s
s
Objectives..........................................................................................15
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
5
4.2
4
.
2
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process
P
r
o
c
e
s
s
Activities............................................................................................15
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
5
4.3
4
.
3
Software
S
o
f
t
w
a
r
e
Plans...................................................................................................................................16
P
l
a
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
6
4.4
4
.
4
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Planning
P
l
a
n
n
i
n
g
................................................................................16
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
6
4.4.1
4
.
4
.
1
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Environment
E
n
v
i
r
o
n
m
e
n
t
........................................................................17
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
7
4.4.2
4
.
4
.
2
Language
L
a
n
g
u
a
g
e
and
a
n
d
Compiler
C
o
m
p
i
l
e
r
Consideration.....................................................................17
C
o
n
s
i
d
e
r
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
7
4.4.3
4
.
4
.
3
Software
S
o
f
t
w
a
r
e
Test
T
e
s
t
Environment.........................................................................................18
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
8
iii
i
i
i
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
4.5
4
.
5
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Standards..................................................................................................18
S
t
a
n
d
a
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
8
4.6
4
.
6
Review
R
e
v
i
e
w
and
a
n
d
Assurance
A
s
s
u
r
a
n
c
e
of
o
f
the
t
h
e
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process.........................................................18
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
8
Page
P
a
g
e
5.0
5
.
0
SOFTWARE
S
O
F
T
W
A
R
E
DEVELOPMENT
D
E
V
E
L
O
P
M
E
N
T
PROCESSES
P
R
O
C
E
S
S
E
S
.......................................................................................19
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
5.1
5
.
1
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Process.....................................................................................................19
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
5.1.1
5
.
1
.
1
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Process
P
r
o
c
e
s
s
Objectives.............................................................19
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
5.1.2
5
.
1
.
2
Software
S
o
f
t
w
a
r
e
Require
R
e
q
u
i
r
e
ments
m
e
n
t
s
Process
P
r
o
c
e
s
s
Activities...............................................................19
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
5.2
5
.
2
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process.................................................................................................................20
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
0
5.2.1
5
.
2
.
1
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
.........................................................................20
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
0
5.2.2
5
.
2
.
2
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process
P
r
o
c
e
s
s
Activities...........................................................................20
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
0
5.2.3
5
.
2
.
3
Designing
D
e
s
i
g
n
i
n
g
for
f
o
r
User-Modifiable
U
s
e
r
-
M
o
d
i
f
i
a
b
l
e
Software
S
o
f
t
w
a
r
e
.................................................................21
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
1
5.3
5
.
3
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process.................................................................................................................21
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
1
5.3.1
5
.
3
.
1
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process
P
r
o
c
e
s
s
Objectives.........................................................................21
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
1
5.3.2
5
.
3
.
2
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
..........................................................................22
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
5.4
5
.
4
Integration
I
n
t
e
g
r
a
t
i
o
n
Process...........................................................................................................................22
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
5.4.1
5
.
4
.
1
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
...................................................................................22
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
5.4.2
5
.
4
.
2
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
.....................................................................................22
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
5.4.3
5
.
4
.
3
Integration
I
n
t
e
g
r
a
t
i
o
n
Considerations..........................................................................................23
C
o
n
s
i
d
e
r
a
t
i
o
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
3
5.5
5
.
5
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
........................................................................................................................................23
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
3
6.0
6
.
0
SOFTWARE
S
O
F
T
W
A
R
E
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
PROCESS...............................................................................................25
P
R
O
C
E
S
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
5
6.1
6
.
1
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
....................................................................................25
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
5
6.2
6
.
2
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Process
P
r
o
c
e
s
s
Activities......................................................................................26
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
6
6.3
6
.
3
Software
S
o
f
t
w
a
r
e
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
....................................................................................................26
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
6
6.3.1
6
.
3
.
1
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
High-Level
H
i
g
h
-
L
e
v
e
l
Requirements.......................................27
R
e
q
u
i
r
e
m
e
n
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
7
6.3.2
6
.
3
.
2
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Low-Level
L
o
w
-
L
e
v
e
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
.......................................27
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
7
6.3.3
6
.
3
.
3
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Software
S
o
f
t
w
a
r
e
Architecture..............................................28
A
r
c
h
i
t
e
c
t
u
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
8
6.3.4
6
.
3
.
4
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Source
S
o
u
r
c
e
Code..............................................................28
C
o
d
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
8
6.3.5
6
.
3
.
5
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Outputs
O
u
t
p
u
t
s
of
o
f
the
t
h
e
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
........................29
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
9
6.3.6
6
.
3
.
6
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Test
T
e
s
t
Cases,
C
a
s
e
s
,
Procedures
P
r
o
c
e
d
u
r
e
s
and
a
n
d
Results......................29
R
e
s
u
l
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
9
6.4
6
.
4
Software
S
o
f
t
w
a
r
e
Testing
T
e
s
t
i
n
g
Process................................................................................................................29
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
9
6.4.1
6
.
4
.
1
Test
T
e
s
t
Environment..........................................................................................................30
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
0
6.4.2
6
.
4
.
2
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Test
T
e
s
t
Case
C
a
s
e
Selection
S
e
l
e
c
t
i
o
n
................................................................30
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
0
6.4.2.1
6
.
4
.
2
.
1
Normal
N
o
r
m
a
l
Range
R
a
n
g
e
Test
T
e
s
t
Cases
C
a
s
e
s
.....................................................................31
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
1
6.4.2.2
6
.
4
.
2
.
2
Robustness
R
o
b
u
s
t
n
e
s
s
Test
T
e
s
t
Cases...........................................................................31
C
a
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
1
6.4.3
6
.
4
.
3
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Testing
T
e
s
t
i
n
g
Methods.....................................................................31
M
e
t
h
o
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
1
6.4.4
6
.
4
.
4
Test
T
e
s
t
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
...............................................................................................33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
6.4.4.1
6
.
4
.
4
.
1
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Test
T
e
s
t
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
...................................33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
6.4.4.2
6
.
4
.
4
.
2
Structural
S
t
r
u
c
t
u
r
a
l
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
...............................................................33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
6.4.4.3
6
.
4
.
4
.
3
Structural
S
t
r
u
c
t
u
r
a
l
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
Resolution...........................................33
R
e
s
o
l
u
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
iv
i
v
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Page
P
a
g
e
7.0
7
.
0
SOFTWARE
S
O
F
T
W
A
R
E
CONFIGURATION
C
O
N
F
I
G
U
R
A
T
I
O
N
MANAGEMENT
M
A
N
A
G
E
M
E
N
T
PROCESS………………………………...35
P
R
O
C
E
S
S
…
…
…
…
…
…
…
…
…
…
…
…
.
.
.
3
5
7.1
7
.
1
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
........................................................35
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
7.2
7
.
2
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
..........................................................35
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
7.2.1
7
.
2
.
1
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Identification........................................................................................35
I
d
e
n
t
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
7.2.2
7
.
2
.
2
Baselines
B
a
s
e
l
i
n
e
s
and
a
n
d
Traceability...........................................................................................36
T
r
a
c
e
a
b
i
l
i
t
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
6
7.2.3
7
.
2
.
3
Problem
P
r
o
b
l
e
m
Reporting,
R
e
p
o
r
t
i
n
g
,
Tracking
T
r
a
c
k
i
n
g
and
a
n
d
Corrective
C
o
r
r
e
c
t
i
v
e
Action.............................................36
A
c
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
6
7.2.4
7
.
2
.
4
Change
C
h
a
n
g
e
Control
C
o
n
t
r
o
l
.............................................................................................................37
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
7
7.2.5
7
.
2
.
5
Change
C
h
a
n
g
e
Review.............................................................................................................37
R
e
v
i
e
w
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
7
7.2.6
7
.
2
.
6
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Status
S
t
a
t
u
s
Accounting...............................................................................37
A
c
c
o
u
n
t
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
7
7.2.7
7
.
2
.
7
Archive,
A
r
c
h
i
v
e
,
Retrieval
R
e
t
r
i
e
v
a
l
and
a
n
d
Release..................................................................................38
R
e
l
e
a
s
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
8
7.2.8
7
.
2
.
8
Software
S
o
f
t
w
a
r
e
Load
L
o
a
d
Control.................................................................................................38
C
o
n
t
r
o
l
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
8
7.2.9
7
.
2
.
9
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Control...............................................................39
C
o
n
t
r
o
l
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
9
7.3
7
.
3
Data
D
a
t
a
Control
C
o
n
t
r
o
l
Categories
C
a
t
e
g
o
r
i
e
s
..................................................................................................................39
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
9
8.0
8
.
0
SOFTWARE
S
O
F
T
W
A
R
E
QUALITY
Q
U
A
L
I
T
Y
ASSURANCE
A
S
S
U
R
A
N
C
E
PROCESS...................................................
P
R
O
C
E
S
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
41
4
1
8.1
8
.
1
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Process
P
r
o
c
e
s
s
Objectives.........................................................................41
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
1
8.2
8
.
2
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
..........................................................................41
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
1
8.3
8
.
3
Software
S
o
f
t
w
a
r
e
Conformity
C
o
n
f
o
r
m
i
t
y
Review.........................................................................................................42
R
e
v
i
e
w
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
2
9.0
9
.
0
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
LIAISON
L
I
A
I
S
O
N
PROCESS...................................................................................................43
P
R
O
C
E
S
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
3
9.1
9
.
1
Means
M
e
a
n
s
of
o
f
Compliance
C
o
m
p
l
i
a
n
c
e
and
a
n
d
Planning..............................................................................................43
P
l
a
n
n
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
3
9.2
9
.
2
Compliance
C
o
m
p
l
i
a
n
c
e
Substantiation..............................................................................................................43
S
u
b
s
t
a
n
t
i
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
3
9.3
9
.
3
Minimum
M
i
n
i
m
u
m
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Data
D
a
t
a
That
T
h
a
t
Is
I
s
Submitted
S
u
b
m
i
t
t
e
d
to
t
o
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Authority..............43
A
u
t
h
o
r
i
t
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
3
9.4
9
.
4
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Data
D
a
t
a
Related
R
e
l
a
t
e
d
to
t
o
Type
T
y
p
e
Design.....................................................................44
D
e
s
i
g
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
4
10.0
1
0
.
0
OVERVIEW
O
V
E
R
V
I
E
W
OF
O
F
AIRCRAFT
A
I
R
C
R
A
F
T
AND
A
N
D
ENGINE
E
N
G
I
N
E
CERT
C
E
R
T
IFICATION
I
F
I
C
A
T
I
O
N
.......................................................45
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
5
10.1
1
0
.
1
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Basis
B
a
s
i
s
............................................................................................................................45
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
5
10.2
1
0
.
2
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification..................................................................................................45
C
e
r
t
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
5
10.3
1
0
.
3
Compliance
C
o
m
p
l
i
a
n
c
e
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
.............................................................................................................45
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
5
11.0
1
1
.
0
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE
C
Y
C
L
E
DATA
D
A
T
A
............................................................................................................47
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
7
11.1
1
1
.
1
Plan
P
l
a
n
for
f
o
r
Soft
S
o
f
t
ware
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification...................................................................................48
C
e
r
t
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
8
11.2
1
1
.
2
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan............................................................................................................48
P
l
a
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
8
11.3
1
1
.
3
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
..............................................................................................................49
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
9
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan
P
l
a
n
..................................................................................50
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
0
-
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Plan...................................................................................................51
P
l
a
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1
-
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards.................................................................................................51
S
t
a
n
d
a
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1
-
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards.............................................................................................................51
S
t
a
n
d
a
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1
-
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
................................................................................................................52
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
2
-
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data
D
a
t
a
..........................................................................................................52
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
2
-
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
...........................................................................................................................52
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
2
-
Source
S
o
u
r
c
e
Code.......................................................................................................................................53
C
o
d
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
3
v
v
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Page
P
a
g
e
-
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
..................................................................................................................53
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
3
-
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Cases
C
a
s
e
s
and
a
n
d
Procedures...............................................................................53
P
r
o
c
e
d
u
r
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
3
-
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results.........................................................................................................53
R
e
s
u
l
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
3
-
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index............................................................53
I
n
d
e
x
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
3
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index........................................................................................................54
I
n
d
e
x
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
4
-
Problem
P
r
o
b
l
e
m
Reports................................................................................................................................54
R
e
p
o
r
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
4
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Records............................................................................55
R
e
c
o
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
5
-
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Records............................................................................................55
R
e
c
o
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
5
11.20
1
1
.
2
0
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
............................................................................................55
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
5
12.0
1
2
.
0
ADDITIONAL
A
D
D
I
T
I
O
N
A
L
CONSIDERATIONS
C
O
N
S
I
D
E
R
A
T
I
O
N
S
........................................................................................................57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
7
12.1
1
2
.
1
Use
U
s
e
of
o
f
Previously
P
r
e
v
i
o
u
s
l
y
Developed
D
e
v
e
l
o
p
e
d
Software
S
o
f
t
w
a
r
e
........................................................................................57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
7
12.1.1
1
2
.
1
.
1
Modifications
M
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
Previously
P
r
e
v
i
o
u
s
l
y
Developed
D
e
v
e
l
o
p
e
d
Software
S
o
f
t
w
a
r
e
..................................................57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
7
12.1.2
1
2
.
1
.
2
Change
C
h
a
n
g
e
of
o
f
Aircraft
A
i
r
c
r
a
f
t
Installation...................................................................................57
I
n
s
t
a
l
l
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
7
12.1.3
1
2
.
1
.
3
Change
C
h
a
n
g
e
of
o
f
Application
A
p
p
l
i
c
a
t
i
o
n
or
o
r
Development
D
e
v
e
l
o
p
m
e
n
t
Environment...........................................57
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
7
12.1.4
1
2
.
1
.
4
Upgrading
U
p
g
r
a
d
i
n
g
A
A
Development
D
e
v
e
l
o
p
m
e
n
t
Baseline
B
a
s
e
l
i
n
e
.........................................................................58
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
8
12.1.5
1
2
.
1
.
5
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
...........................................59
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
9
12.1.6
1
2
.
1
.
6
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Considerations............................................................59
C
o
n
s
i
d
e
r
a
t
i
o
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
9
12.2
1
2
.
2
Tool
T
o
o
l
Qualification.............................................................................................................................59
Q
u
a
l
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
9
12.2.1
1
2
.
2
.
1
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Criteria
C
r
i
t
e
r
i
a
fo
f
o
r
r
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Tools
T
o
o
l
s
.......................................60
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
0
12.2.2
1
2
.
2
.
2
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Criteria
C
r
i
t
e
r
i
a
fo
f
o
r
r
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Tools
T
o
o
l
s
..........................................61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
1
12.2.3
1
2
.
2
.
3
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Data
D
a
t
a
...............................................................................................61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
1
12.2.3.1
1
2
.
2
.
3
.
1
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan..........................................................................61
P
l
a
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
1
12.2.3.2
1
2
.
2
.
3
.
2
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
...........................................................61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
1
12.2.4
1
2
.
2
.
4
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Agreement
A
g
r
e
e
m
e
n
t
...................................................................................62
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
2
12.3
1
2
.
3
Alternative
A
l
t
e
r
n
a
t
i
v
e
Methods.........................................................................................................................62
M
e
t
h
o
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
2
12.3.1
1
2
.
3
.
1
Formal
F
o
r
m
a
l
Methods............................................................................................................62
M
e
t
h
o
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
2
12.3.2
1
2
.
3
.
2
Exhaustive
E
x
h
a
u
s
t
i
v
e
Input
I
n
p
u
t
Testing.............................................................................................63
T
e
s
t
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
3
12.3.3
1
2
.
3
.
3
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
Multiple
M
u
l
t
i
p
l
e
-Version
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
.............63
.
.
.
.
.
.
.
.
.
.
.
.
.
6
3
12.3.3.1
1
2
.
3
.
3
.
1
Independence
I
n
d
e
p
e
n
d
e
n
c
e
of
o
f
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
.................64
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
4
12.3.3.2
1
2
.
3
.
3
.
2
Multiple
M
u
l
t
i
p
l
e
Processor-Related
P
r
o
c
e
s
s
o
r
-
R
e
l
a
t
e
d
Verification
V
e
r
i
f
i
c
a
t
i
o
n
............................................64
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
4
12.3.3.3
1
2
.
3
.
3
.
3
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Source
S
o
u
r
c
e
Code
C
o
d
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
......................................65
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
12.3.3.4
1
2
.
3
.
3
.
4
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
for
f
o
r
Multiple
M
u
l
t
i
p
l
e
-Version
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
...................................................................................................65
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
12.3.3.5
1
2
.
3
.
3
.
5
Multiple
M
u
l
t
i
p
l
e
Simulators
S
i
m
u
l
a
t
o
r
s
and
a
n
d
Verification..................................................65
V
e
r
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
12.3.4
1
2
.
3
.
4
Software
S
o
f
t
w
a
r
e
Reliability
R
e
l
i
a
b
i
l
i
t
y
Models
M
o
d
e
l
s
.......................................................................................65
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
12.3.5
1
2
.
3
.
5
Product
P
r
o
d
u
c
t
Service
S
e
r
v
i
c
e
History...............................................................................................65
H
i
s
t
o
r
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
ANNEX
A
N
N
E
X
A
A
PROCESS
P
R
O
C
E
S
S
OBJECTIVES
O
B
J
E
C
T
I
V
E
S
AND
A
N
D
OUTPUTS
O
U
T
P
U
T
S
BY
B
Y
SOFTWARE
S
O
F
T
W
A
R
E
LEVEL..............................................67
L
E
V
E
L
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
7
ANNEX
A
N
N
E
X
B
B
ACRONYMS
A
C
R
O
N
Y
M
S
AND
A
N
D
GLOSSARY
G
L
O
S
S
A
R
Y
OF
O
F
TERMS........................................................................................79
T
E
R
M
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
9
Acronyms
A
c
r
o
n
y
m
s
.........................................................................................................................................................79
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
9
vi
v
i
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Glossary............................................................................................................................................................80
G
l
o
s
s
a
r
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
0
APPENDIX
A
P
P
E
N
D
I
X
A
A
BACKGROUND
B
A
C
K
G
R
O
U
N
D
OF
O
F
DOCUMENT
D
O
C
U
M
E
N
T
DO-178............................................................A-1
D
O
-
1
7
8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
A
-
1
-
Prior
P
r
i
o
r
Document
D
o
c
u
m
e
n
t
Version
V
e
r
s
i
o
n
History
H
i
s
t
o
r
y
2.0
2
.
0
RTCA
R
T
C
A
/
/
EUROCAE
E
U
R
O
C
A
E
Committee
C
o
m
m
i
t
t
e
e
Activities
A
c
t
i
v
i
t
i
e
s
in
i
n
the
t
h
e
Production
P
r
o
d
u
c
t
i
o
n
of
o
f
This
T
h
i
s
Document
D
o
c
u
m
e
n
t
3.0
3
.
0
Summary
S
u
m
m
a
r
y
Of
O
f
Differences
D
i
f
f
e
r
e
n
c
e
s
between
b
e
t
w
e
e
n
DO-178B
D
O
-
1
7
8
B
and
a
n
d
DO-178A
D
O
-
1
7
8
A
APPENDIX
A
P
P
E
N
D
I
X
B
B
COMMITTEE
C
O
M
M
I
T
T
E
E
MEMBERSHIP
M
E
M
B
E
R
S
H
I
P
................................................................................................................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
B-1
B
-
1
APPENDIX
A
P
P
E
N
D
I
X
C
C
INDEX
I
N
D
E
X
OF
O
F
TERMS....................................................................................................................................
T
E
R
M
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
C-1
C
-
1
APPENDIX
A
P
P
E
N
D
I
X
D
D
IMPROVEMENT
I
M
P
R
O
V
E
M
E
N
T
SUGGESTION
S
U
G
G
E
S
T
I
O
N
FORM
F
O
R
M
.............................................................................................D-1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
D
-
1
Page
P
a
g
e
LIST
L
I
S
T
OF
O
F
FIGURES
F
I
G
U
R
E
S
AND
A
N
D
TABLES
T
A
B
L
E
S
FIGURES
F
I
G
U
R
E
S
FIGURE
F
I
G
U
R
E
1-1
1
-
1
DOCUMENT
D
O
C
U
M
E
N
T
OVERVIEW
O
V
E
R
V
I
E
W
...................................................................................................................................3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
FIGURE
F
I
G
U
R
E
2-1
2
-
1
SYSTEM
S
Y
S
T
E
M
SAFETY-RELATED
S
A
F
E
T
Y
-
R
E
L
A
T
E
D
INFORMATION
I
N
F
O
R
M
A
T
I
O
N
FLOW
F
L
O
W
BETWEENSYSTEM
B
E
T
W
E
E
N
S
Y
S
T
E
M
AND
A
N
D
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE
C
Y
C
L
E
PROCESSES....................................................................................................................................5
P
R
O
C
E
S
S
E
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
FIGURE
F
I
G
U
R
E
3-1
3
-
1
EXAMPLE
E
X
A
M
P
L
E
OF
O
F
A
A
SOFTWARE
S
O
F
T
W
A
R
E
PROJECTUSING
P
R
O
J
E
C
T
U
S
I
N
G
FOUR
F
O
U
R
DIFFERENT
D
I
F
F
E
R
E
N
T
DEVELOPMENT
D
E
V
E
L
O
P
M
E
N
T
SEQUENCES
S
E
Q
U
E
N
C
E
S
..........................................................................................................................................................14
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
4
FIGURE
F
I
G
U
R
E
6-1
6
-
1
SOFTWARE
S
O
F
T
W
A
R
E
TESTING
T
E
S
T
I
N
G
PROCESS
P
R
O
C
E
S
S
...................................................................................................................30
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
0
TABLES
T
A
B
L
E
S
TABLE
T
A
B
L
E
7-1
7
-
1
SCM
S
C
M
PROCESS
P
R
O
C
E
S
S
OBJECTIVES
O
B
J
E
C
T
I
V
E
S
ASSOCIATED
A
S
S
O
C
I
A
T
E
D
WITH
W
I
T
H
CC1
C
C
1
AND
A
N
D
CC2
C
C
2
DATA
D
A
T
A
........................................39
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
9
TABLE
T
A
B
L
E
A-1
A
-
1
SOFTWARE
S
O
F
T
W
A
R
E
PLANNING
P
L
A
N
N
I
N
G
PROCESS
P
R
O
C
E
S
S
................................................................................................................68
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
8
TABLE
T
A
B
L
E
A-2
A
-
2
SOFTWARE
S
O
F
T
W
A
R
E
DEVELOPMENT
D
E
V
E
L
O
P
M
E
N
T
PROCESSES.................................................................................................69
P
R
O
C
E
S
S
E
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
9
TABLE
T
A
B
L
E
A-3
A
-
3
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
OF
O
F
OUTPUTS
O
U
T
P
U
T
S
OF
O
F
SOFTWARE
S
O
F
T
W
A
R
E
REQUIREMENTS
R
E
Q
U
I
R
E
M
E
N
T
S
PROCESS
P
R
O
C
E
S
S
.................................70
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
0
TABLE
T
A
B
L
E
A-4
A
-
4
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
OF
O
F
OUTPUTS
O
U
T
P
U
T
S
OF
O
F
SOFTWARE
S
O
F
T
W
A
R
E
DESIGN
D
E
S
I
G
N
PROCESS
P
R
O
C
E
S
S
...................................................71
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
1
TABLE
T
A
B
L
E
A-5
A
-
5
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
OF
O
F
OUTPUTS
O
U
T
P
U
T
S
OF
O
F
SOFTWARE
S
O
F
T
W
A
R
E
CODING
C
O
D
I
N
G
&
&
INTEGRATION
I
N
T
E
G
R
A
T
I
O
N
PROCESSES
P
R
O
C
E
S
S
E
S
....................................................................................................................................................72
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
2
TABLE
T
A
B
L
E
A-6
A
-
6
TESTING
T
E
S
T
I
N
G
OF
O
F
OUTPUTS
O
U
T
P
U
T
S
OF
O
F
INTEGRATION
I
N
T
E
G
R
A
T
I
O
N
PROCESS
P
R
O
C
E
S
S
...........................................................................73
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
3
TABLE
T
A
B
L
E
A-7
A
-
7
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
OF
O
F
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
PROCESS
P
R
O
C
E
S
S
RESULTS
R
E
S
U
L
T
S
.....................................................................74
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
4
TABLE
T
A
B
L
E
A-8
A
-
8
SOFTWARE
S
O
F
T
W
A
R
E
CONFIGURATION
C
O
N
F
I
G
U
R
A
T
I
O
N
MANAGEMENT
M
A
N
A
G
E
M
E
N
T
PROCESS
P
R
O
C
E
S
S
.................................................................75
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
5
TABLE
T
A
B
L
E
A-9
A
-
9
SOFTWARE
S
O
F
T
W
A
R
E
QUALITY
Q
U
A
L
I
T
Y
ASSURANCE
A
S
S
U
R
A
N
C
E
PROCESS
P
R
O
C
E
S
S
.......................................................................................76
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
6
TABLE
T
A
B
L
E
A-10
A
-
1
0
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
LIAISON
L
I
A
I
S
O
N
PROCESS.........................................................................................................77
P
R
O
C
E
S
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
7
vii
v
i
i
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
1
1
1
1
INTRODUCTION
I
N
T
R
O
D
U
C
T
I
O
N
The
T
h
e
rapid
r
a
p
i
d
increase
i
n
c
r
e
a
s
e
in
i
n
the
t
h
e
use
u
s
e
of
o
f
software
s
o
f
t
w
a
r
e
in
i
n
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
used
u
s
e
d
on
o
n
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
engines
e
n
g
i
n
e
s
in
i
n
the
t
h
e
early
e
a
r
l
y
1980s
1
9
8
0
s
resulted
r
e
s
u
l
t
e
d
in
i
n
a
a
need
n
e
e
d
for
f
o
r
industry-accepted
i
n
d
u
s
t
r
y
-
a
c
c
e
p
t
e
d
guidance
g
u
i
d
a
n
c
e
for
f
o
r
satisfying
s
a
t
i
s
f
y
i
n
g
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
DO-178,
D
O
-
1
7
8
,
"Software
"
S
o
f
t
w
a
r
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
Airborne
A
i
r
b
o
r
n
e
Systems
S
y
s
t
e
m
s
and
a
n
d
Equipment
E
q
u
i
p
m
e
n
t
Cert
C
e
r
t
ification,"
i
f
i
c
a
t
i
o
n
,
"
was
w
a
s
written
w
r
i
t
t
e
n
to
t
o
satisfy
s
a
t
i
s
f
y
this
t
h
i
s
need.
n
e
e
d
.
This
T
h
i
s
document,
d
o
c
u
m
e
n
t
,
now
n
o
w
revised
r
e
v
i
s
e
d
in
i
n
the
t
h
e
light
l
i
g
h
t
of
o
f
experience,
e
x
p
e
r
i
e
n
c
e
,
provides
p
r
o
v
i
d
e
s
the
t
h
e
aviation
a
v
i
a
t
i
o
n
community
c
o
m
m
u
n
i
t
y
with
w
i
t
h
guidance
g
u
i
d
a
n
c
e
for
f
o
r
determining,
d
e
t
e
r
m
i
n
i
n
g
,
in
i
n
a
a
consistent
c
o
n
s
i
s
t
e
n
t
manner
m
a
n
n
e
r
and
a
n
d
with
w
i
t
h
an
a
n
acceptable
a
c
c
e
p
t
a
b
l
e
level
l
e
v
e
l
of
o
f
confidence,
c
o
n
f
i
d
e
n
c
e
,
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
comply
c
o
m
p
l
y
with
w
i
t
h
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
As
A
s
software
s
o
f
t
w
a
r
e
use
u
s
e
increases,
i
n
c
r
e
a
s
e
s
,
technology
t
e
c
h
n
o
l
o
g
y
evolves
e
v
o
l
v
e
s
and
a
n
d
experience
e
x
p
e
r
i
e
n
c
e
is
i
s
gained
g
a
i
n
e
d
in
i
n
the
t
h
e
application
a
p
p
l
i
c
a
t
i
o
n
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
this
t
h
i
s
document
d
o
c
u
m
e
n
t
will
w
i
l
l
be
b
e
reviewed
r
e
v
i
e
w
e
d
and
a
n
d
revised.
r
e
v
i
s
e
d
.
Appendix
A
p
p
e
n
d
i
x
A
A
contains
c
o
n
t
a
i
n
s
a
a
history
h
i
s
t
o
r
y
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
Purpose
P
u
r
p
o
s
e
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
is
i
s
to
t
o
provide
p
r
o
v
i
d
e
guidelines
g
u
i
d
e
l
i
n
e
s
for
f
o
r
the
t
h
e
production
p
r
o
d
u
c
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
for
f
o
r
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
that
t
h
a
t
performs
p
e
r
f
o
r
m
s
its
i
t
s
intended
i
n
t
e
n
d
e
d
function
f
u
n
c
t
i
o
n
with
w
i
t
h
a
a
level
l
e
v
e
l
of
o
f
confidence
c
o
n
f
i
d
e
n
c
e
in
i
n
safety
s
a
f
e
t
y
that
t
h
a
t
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
These
T
h
e
s
e
guidelines
g
u
i
d
e
l
i
n
e
s
are
a
r
e
in
i
n
the
t
h
e
form
f
o
r
m
of:
o
f
:
-
Objectives
O
b
j
e
c
t
i
v
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
-
Descriptions
D
e
s
c
r
i
p
t
i
o
n
s
of
o
f
activities
a
c
t
i
v
i
t
i
e
s
and
a
n
d
design
d
e
s
i
g
n
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
achieving
a
c
h
i
e
v
i
n
g
those
t
h
o
s
e
objectives
o
b
j
e
c
t
i
v
e
s
-
Descriptions
D
e
s
c
r
i
p
t
i
o
n
s
of
o
f
the
t
h
e
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
indicate
i
n
d
i
c
a
t
e
that
t
h
a
t
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
have
h
a
v
e
been
b
e
e
n
satisfied.
s
a
t
i
s
f
i
e
d
.
-
Scope
S
c
o
p
e
This
T
h
i
s
document
d
o
c
u
m
e
n
t
discusses
d
i
s
c
u
s
s
e
s
those
t
h
o
s
e
aspects
a
s
p
e
c
t
s
of
o
f
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
that
t
h
a
t
pertain
p
e
r
t
a
i
n
to
t
o
the
t
h
e
production
p
r
o
d
u
c
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
for
f
o
r
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
used
u
s
e
d
on
o
n
aircraft
a
i
r
c
r
a
f
t
or
o
r
engines.
e
n
g
i
n
e
s
.
In
I
n
discussing
d
i
s
c
u
s
s
i
n
g
those
t
h
o
s
e
aspects,
a
s
p
e
c
t
s
,
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
and
a
n
d
its
i
t
s
relationship
r
e
l
a
t
i
o
n
s
h
i
p
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
is
i
s
described
d
e
s
c
r
i
b
e
d
to
t
o
aid
a
i
d
in
i
n
the
t
h
e
understanding
u
n
d
e
r
s
t
a
n
d
i
n
g
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
A
A
complete
c
o
m
p
l
e
t
e
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
and
a
n
d
validation
v
a
l
i
d
a
t
i
o
n
processes,
p
r
o
c
e
s
s
e
s
,
or
o
r
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
engine
e
n
g
i
n
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
not
n
o
t
intended.
i
n
t
e
n
d
e
d
.
Since
S
i
n
c
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
issues
i
s
s
u
e
s
are
a
r
e
discussed
d
i
s
c
u
s
s
e
d
only
o
n
l
y
in
i
n
relation
r
e
l
a
t
i
o
n
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle,
c
y
c
l
e
,
the
t
h
e
operational
o
p
e
r
a
t
i
o
n
a
l
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
resulting
r
e
s
u
l
t
i
n
g
software
s
o
f
t
w
a
r
e
are
a
r
e
not
n
o
t
discussed.
d
i
s
c
u
s
s
e
d
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
aspects
a
s
p
e
c
t
s
of
o
f
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
data
d
a
t
a
are
a
r
e
beyond
b
e
y
o
n
d
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
This
T
h
i
s
document
d
o
c
u
m
e
n
t
does
d
o
e
s
not
n
o
t
provide
p
r
o
v
i
d
e
guidelines
g
u
i
d
e
l
i
n
e
s
concerning
c
o
n
c
e
r
n
i
n
g
the
t
h
e
structure
s
t
r
u
c
t
u
r
e
of
o
f
the
t
h
e
applicant’s
a
p
p
l
i
c
a
n
t
’
s
organization,
o
r
g
a
n
i
z
a
t
i
o
n
,
the
t
h
e
relationships
r
e
l
a
t
i
o
n
s
h
i
p
s
between
b
e
t
w
e
e
n
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
and
a
n
d
its
i
t
s
suppliers,
s
u
p
p
l
i
e
r
s
,
or
o
r
how
h
o
w
the
t
h
e
responsibilities
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
are
a
r
e
divided.
d
i
v
i
d
e
d
.
Personnel
P
e
r
s
o
n
n
e
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
criteria
c
r
i
t
e
r
i
a
are
a
r
e
also
a
l
s
o
beyond
b
e
y
o
n
d
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
Relationship
R
e
l
a
t
i
o
n
s
h
i
p
to
t
o
Other
O
t
h
e
r
Documents
D
o
c
u
m
e
n
t
s
In
I
n
addition
a
d
d
i
t
i
o
n
to
t
o
the
t
h
e
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
various
v
a
r
i
o
u
s
national
n
a
t
i
o
n
a
l
and
a
n
d
international
i
n
t
e
r
n
a
t
i
o
n
a
l
standards
s
t
a
n
d
a
r
d
s
for
f
o
r
software
s
o
f
t
w
a
r
e
are
a
r
e
available.
a
v
a
i
l
a
b
l
e
.
In
I
n
some
s
o
m
e
communities,
c
o
m
m
u
n
i
t
i
e
s
,
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
these
t
h
e
s
e
standards
s
t
a
n
d
a
r
d
s
may
m
a
y
be
b
e
required.
r
e
q
u
i
r
e
d
.
However,
H
o
w
e
v
e
r
,
it
i
t
is
i
s
outside
o
u
t
s
i
d
e
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
invoke
i
n
v
o
k
e
specific
s
p
e
c
i
f
i
c
national
n
a
t
i
o
n
a
l
or
o
r
international
i
n
t
e
r
n
a
t
i
o
n
a
l
standards,
s
t
a
n
d
a
r
d
s
,
or
o
r
to
t
o
propose
p
r
o
p
o
s
e
a
a
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
these
t
h
e
s
e
standards
s
t
a
n
d
a
r
d
s
might
m
i
g
h
t
be
b
e
used
u
s
e
d
as
a
s
an
a
n
alternative
a
l
t
e
r
n
a
t
i
v
e
or
o
r
supplement
s
u
p
p
l
e
m
e
n
t
to
t
o
this
t
h
i
s
document
d
o
c
u
m
e
n
t
Where
W
h
e
r
e
this
t
h
i
s
document
d
o
c
u
m
e
n
t
uses
u
s
e
s
the
t
h
e
term
t
e
r
m
"standards,"
"
s
t
a
n
d
a
r
d
s
,
"
it
i
t
should
s
h
o
u
l
d
be
b
e
interpreted
i
n
t
e
r
p
r
e
t
e
d
to
t
o
mean
m
e
a
n
the
t
h
e
use
u
s
e
of
o
f
project
p
r
o
j
e
c
t
specific
s
p
e
c
i
f
i
c
standards
s
t
a
n
d
a
r
d
s
as
a
s
applied
a
p
p
l
i
e
d
by
b
y
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system,
s
y
s
t
e
m
,
airborne
a
i
r
b
o
r
n
e
equipment,
e
q
u
i
p
m
e
n
t
,
engine,
e
n
g
i
n
e
,
or
o
r
aircraft
a
i
r
c
r
a
f
t
manufacturer.
m
a
n
u
f
a
c
t
u
r
e
r
.
Such
S
u
c
h
standards
s
t
a
n
d
a
r
d
s
may
m
a
y
be
b
e
derived
d
e
r
i
v
e
d
from
f
r
o
m
general
g
e
n
e
r
a
l
standards
s
t
a
n
d
a
r
d
s
produced
p
r
o
d
u
c
e
d
or
o
r
adopted
a
d
o
p
t
e
d
by
b
y
the
t
h
e
manufacturer
m
a
n
u
f
a
c
t
u
r
e
r
for
f
o
r
its
i
t
s
activities.
a
c
t
i
v
i
t
i
e
s
.
-
How
H
o
w
to
t
o
Use
U
s
e
This
T
h
i
s
Document
D
o
c
u
m
e
n
t
These
T
h
e
s
e
points
p
o
i
n
t
s
need
n
e
e
d
to
t
o
be
b
e
noted
n
o
t
e
d
when
w
h
e
n
using
u
s
i
n
g
this
t
h
i
s
document:
d
o
c
u
m
e
n
t
:
-
Explanatory
E
x
p
l
a
n
a
t
o
r
y
text
t
e
x
t
is
i
s
included
i
n
c
l
u
d
e
d
to
t
o
aid
a
i
d
the
t
h
e
reader
r
e
a
d
e
r
in
i
n
understanding
u
n
d
e
r
s
t
a
n
d
i
n
g
the
t
h
e
topic
t
o
p
i
c
under
u
n
d
e
r
discussion.
d
i
s
c
u
s
s
i
o
n
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
section
s
e
c
t
i
o
n
2
2
provides
p
r
o
v
i
d
e
s
information
i
n
f
o
r
m
a
t
i
o
n
necessary
n
e
c
e
s
s
a
r
y
to
t
o
understand
u
n
d
e
r
s
t
a
n
d
the
t
h
e
interaction
i
n
t
e
r
a
c
t
i
o
n
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
2
2
between
b
e
t
w
e
e
n
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
Similarly,
S
i
m
i
l
a
r
l
y
,
section
s
e
c
t
i
o
n
3
3
is
i
s
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
and
a
n
d
section
s
e
c
t
i
o
n
10
1
0
is
i
s
an
a
n
overview
o
v
e
r
v
i
e
w
of
o
f
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
engine
e
n
g
i
n
e
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
-
This
T
h
i
s
document
d
o
c
u
m
e
n
t
is
i
s
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
used
u
s
e
d
by
b
y
the
t
h
e
international
i
n
t
e
r
n
a
t
i
o
n
a
l
aviation
a
v
i
a
t
i
o
n
community.
c
o
m
m
u
n
i
t
y
.
To
T
o
aid
a
i
d
such
s
u
c
h
use,
u
s
e
,
references
r
e
f
e
r
e
n
c
e
s
to
t
o
specific
s
p
e
c
i
f
i
c
national
n
a
t
i
o
n
a
l
regulations
r
e
g
u
l
a
t
i
o
n
s
and
a
n
d
procedures
p
r
o
c
e
d
u
r
e
s
are
a
r
e
minimized.
m
i
n
i
m
i
z
e
d
.
Instead,
I
n
s
t
e
a
d
,
generic
g
e
n
e
r
i
c
terms
t
e
r
m
s
are
a
r
e
used.
u
s
e
d
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
term
t
e
r
m
"certification
"
c
e
r
t
i
f
i
c
a
t
i
o
n
authority"
a
u
t
h
o
r
i
t
y
"
is
i
s
used
u
s
e
d
to
t
o
mean
m
e
a
n
the
t
h
e
organization
o
r
g
a
n
i
z
a
t
i
o
n
or
o
r
person
p
e
r
s
o
n
granting
g
r
a
n
t
i
n
g
approval
a
p
p
r
o
v
a
l
on
o
n
behalf
b
e
h
a
l
f
of
o
f
the
t
h
e
country
c
o
u
n
t
r
y
responsible
r
e
s
p
o
n
s
i
b
l
e
for
f
o
r
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine
e
n
g
i
n
e
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
Where
W
h
e
r
e
a
a
second
s
e
c
o
n
d
country
c
o
u
n
t
r
y
or
o
r
a
a
group
g
r
o
u
p
of
o
f
countries
c
o
u
n
t
r
i
e
s
validates
v
a
l
i
d
a
t
e
s
or
o
r
participates
p
a
r
t
i
c
i
p
a
t
e
s
in
i
n
this
t
h
i
s
certification,
c
e
r
t
i
f
i
c
a
t
i
o
n
,
this
t
h
i
s
document
d
o
c
u
m
e
n
t
may
m
a
y
be
b
e
used
u
s
e
d
with
w
i
t
h
due
d
u
e
recognition
r
e
c
o
g
n
i
t
i
o
n
given
g
i
v
e
n
to
t
o
bilateral
b
i
l
a
t
e
r
a
l
agreements
a
g
r
e
e
m
e
n
t
s
or
o
r
memoranda
m
e
m
o
r
a
n
d
a
of
o
f
understanding
u
n
d
e
r
s
t
a
n
d
i
n
g
between
b
e
t
w
e
e
n
the
t
h
e
countries
c
o
u
n
t
r
i
e
s
involved.
i
n
v
o
l
v
e
d
.
-
This
T
h
i
s
document
d
o
c
u
m
e
n
t
recognizes
r
e
c
o
g
n
i
z
e
s
that
t
h
a
t
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
herein
h
e
r
e
i
n
are
a
r
e
not
n
o
t
mandated
m
a
n
d
a
t
e
d
by
b
y
law,
l
a
w
,
but
b
u
t
represent
r
e
p
r
e
s
e
n
t
a
a
consensus
c
o
n
s
e
n
s
u
s
of
o
f
the
t
h
e
aviation
a
v
i
a
t
i
o
n
community.
c
o
m
m
u
n
i
t
y
.
It
I
t
also
a
l
s
o
recognizes
r
e
c
o
g
n
i
z
e
s
that
t
h
a
t
alternative
a
l
t
e
r
n
a
t
i
v
e
methods
m
e
t
h
o
d
s
to
t
o
the
t
h
e
methods
m
e
t
h
o
d
s
described
d
e
s
c
r
i
b
e
d
herein
h
e
r
e
i
n
may
m
a
y
be
b
e
available
a
v
a
i
l
a
b
l
e
to
t
o
the
t
h
e
applicant.
a
p
p
l
i
c
a
n
t
.
For
F
o
r
these
t
h
e
s
e
reasons,
r
e
a
s
o
n
s
,
the
t
h
e
use
u
s
e
of
o
f
words
w
o
r
d
s
such
s
u
c
h
as
a
s
"shall"
"
s
h
a
l
l
"
and
a
n
d
"must"
"
m
u
s
t
"
is
i
s
avoided.
a
v
o
i
d
e
d
.
-
This
T
h
i
s
document
d
o
c
u
m
e
n
t
states
s
t
a
t
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
levels,
l
e
v
e
l
s
,
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
2.2.2.
2
.
2
.
2
.
Annex
A
n
n
e
x
A
A
specifies
s
p
e
c
i
f
i
e
s
the
t
h
e
variation
v
a
r
i
a
t
i
o
n
in
i
n
these
t
h
e
s
e
objectives
o
b
j
e
c
t
i
v
e
s
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
If
I
f
an
a
n
applicant
a
p
p
l
i
c
a
n
t
adopts
a
d
o
p
t
s
this
t
h
i
s
document
d
o
c
u
m
e
n
t
for
f
o
r
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
purposes,
p
u
r
p
o
s
e
s
,
it
i
t
may
m
a
y
be
b
e
used
u
s
e
d
as
a
s
a
a
set
s
e
t
of
o
f
guidelines
g
u
i
d
e
l
i
n
e
s
to
t
o
achieve
a
c
h
i
e
v
e
these
t
h
e
s
e
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
Section
S
e
c
t
i
o
n
11
1
1
contains
c
o
n
t
a
i
n
s
the
t
h
e
data
d
a
t
a
generally
g
e
n
e
r
a
l
l
y
produced
p
r
o
d
u
c
e
d
to
t
o
aid
a
i
d
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
The
T
h
e
names
n
a
m
e
s
of
o
f
the
t
h
e
data
d
a
t
a
are
a
r
e
denoted
d
e
n
o
t
e
d
in
i
n
the
t
h
e
text
t
e
x
t
by
b
y
capitalization
c
a
p
i
t
a
l
i
z
a
t
i
o
n
of
o
f
the
t
h
e
first
f
i
r
s
t
letter
l
e
t
t
e
r
of
o
f
each
e
a
c
h
word
w
o
r
d
in
i
n
the
t
h
e
name.
n
a
m
e
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
Source
S
o
u
r
c
e
Code
C
o
d
e
-
Section
S
e
c
t
i
o
n
12
1
2
discusses
d
i
s
c
u
s
s
e
s
additional
a
d
d
i
t
i
o
n
a
l
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
including
i
n
c
l
u
d
i
n
g
guidance
g
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
for
f
o
r
tool
t
o
o
l
qualification,
q
u
a
l
i
f
i
c
a
t
i
o
n
,
and
a
n
d
for
f
o
r
the
t
h
e
use
u
s
e
of
o
f
alternative
a
l
t
e
r
n
a
t
i
v
e
methods
m
e
t
h
o
d
s
to
t
o
those
t
h
o
s
e
described
d
e
s
c
r
i
b
e
d
in
i
n
sections
s
e
c
t
i
o
n
s
2
2
through
t
h
r
o
u
g
h
11.
1
1
.
Section
S
e
c
t
i
o
n
12
1
2
may
m
a
y
not
n
o
t
apply
a
p
p
l
y
to
t
o
every
e
v
e
r
y
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
-
The
T
h
e
tables
t
a
b
l
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
variation
v
a
r
i
a
t
i
o
n
and
a
n
d
the
t
h
e
glossary
g
l
o
s
s
a
r
y
are
a
r
e
contained
c
o
n
t
a
i
n
e
d
in
i
n
Annexes,
A
n
n
e
x
e
s
,
and
a
n
d
are
a
r
e
normative,
n
o
r
m
a
t
i
v
e
,
parts
p
a
r
t
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Other
O
t
h
e
r
material
m
a
t
e
r
i
a
l
is
i
s
contained
c
o
n
t
a
i
n
e
d
in
i
n
Appendices,
A
p
p
e
n
d
i
c
e
s
,
and
a
n
d
are
a
r
e
informative
i
n
f
o
r
m
a
t
i
v
e
parts
p
a
r
t
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
In
I
n
cases
c
a
s
e
s
where
w
h
e
r
e
examples
e
x
a
m
p
l
e
s
are
a
r
e
used
u
s
e
d
to
t
o
indicate
i
n
d
i
c
a
t
e
how
h
o
w
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
might
m
i
g
h
t
be
b
e
applied,
a
p
p
l
i
e
d
,
either
e
i
t
h
e
r
graphically
g
r
a
p
h
i
c
a
l
l
y
or
o
r
through
t
h
r
o
u
g
h
narrative,
n
a
r
r
a
t
i
v
e
,
the
t
h
e
examples
e
x
a
m
p
l
e
s
are
a
r
e
not
n
o
t
to
t
o
be
b
e
interpreted
i
n
t
e
r
p
r
e
t
e
d
as
a
s
the
t
h
e
preferred
p
r
e
f
e
r
r
e
d
method.
m
e
t
h
o
d
.
-
A
A
list
l
i
s
t
of
o
f
items
i
t
e
m
s
does
d
o
e
s
not
n
o
t
imply
i
m
p
l
y
the
t
h
e
list
l
i
s
t
is
i
s
all-inclusive.
a
l
l
-
i
n
c
l
u
s
i
v
e
.
-
Notes
N
o
t
e
s
are
a
r
e
used
u
s
e
d
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
provide
p
r
o
v
i
d
e
explanatory
e
x
p
l
a
n
a
t
o
r
y
material,
m
a
t
e
r
i
a
l
,
emphasize
e
m
p
h
a
s
i
z
e
a
a
point,
p
o
i
n
t
,
or
o
r
draw
d
r
a
w
attention
a
t
t
e
n
t
i
o
n
to
t
o
related
r
e
l
a
t
e
d
items
i
t
e
m
s
which
w
h
i
c
h
are
a
r
e
not
n
o
t
entirely
e
n
t
i
r
e
l
y
within
w
i
t
h
i
n
context.
c
o
n
t
e
x
t
.
Notes
N
o
t
e
s
do
d
o
not
n
o
t
contain
c
o
n
t
a
i
n
guidance.
g
u
i
d
a
n
c
e
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
3
3
-
Document
D
o
c
u
m
e
n
t
Overview
O
v
e
r
v
i
e
w
Figure
F
i
g
u
r
e
1-1
1
-
1
is
i
s
a
a
pictorial
p
i
c
t
o
r
i
a
l
overview
o
v
e
r
v
i
e
w
of
o
f
this
t
h
i
s
document’s
d
o
c
u
m
e
n
t
’
s
sections
s
e
c
t
i
o
n
s
and
a
n
d
their
t
h
e
i
r
relationship
r
e
l
a
t
i
o
n
s
h
i
p
to
t
o
each
e
a
c
h
other.
o
t
h
e
r
.
FIGURE
F
I
G
U
R
E
1-1
1
-
1
DOCUMENT
D
O
C
U
M
E
N
T
OVERVIEW
O
V
E
R
V
I
E
W
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
2
2
SYSTEM
S
Y
S
T
E
M
ASPECTS
A
S
P
E
C
T
S
RELATING
R
E
L
A
T
I
N
G
TO
T
O
SOFTWARE
S
O
F
T
W
A
R
E
DEVELOPMENT
D
E
V
E
L
O
P
M
E
N
T
5
5
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
those
t
h
o
s
e
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
necessary
n
e
c
e
s
s
a
r
y
to
t
o
understand
u
n
d
e
r
s
t
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
Discussed
D
i
s
c
u
s
s
e
d
are:
a
r
e
:
-
Exchange
E
x
c
h
a
n
g
e
of
o
f
data
d
a
t
a
between
b
e
t
w
e
e
n
the
t
h
e
system
s
y
s
t
e
m
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.1).
2
.
1
)
.
-
Categorization
C
a
t
e
g
o
r
i
z
a
t
i
o
n
of
o
f
failure
f
a
i
l
u
r
e
conditions,
c
o
n
d
i
t
i
o
n
s
,
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
levels,
l
e
v
e
l
s
,
and
a
n
d
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
determination
d
e
t
e
r
m
i
n
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.2).
2
.
2
)
.
-
System
S
y
s
t
e
m
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.3).
2
.
3
)
.
-
System
S
y
s
t
e
m
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
option-selectable
o
p
t
i
o
n
-
s
e
l
e
c
t
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
and
a
n
d
commercial
c
o
m
m
e
r
c
i
a
l
off-
o
f
f
-
the-shelf
t
h
e
-
s
h
e
l
f
software
s
o
f
t
w
a
r
e
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.4).
2
.
4
)
.
-
System
S
y
s
t
e
m
design
d
e
s
i
g
n
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
field-loadable
f
i
e
l
d
-
l
o
a
d
a
b
l
e
software
s
o
f
t
w
a
r
e
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.5).
2
.
5
)
.
-
System
S
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.6).
2
.
6
)
.
-
Software
S
o
f
t
w
a
r
e
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
system
s
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.7).
2
.
7
)
.
2.1
2
.
1
Information
I
n
f
o
r
m
a
t
i
o
n
Flow
F
l
o
w
Between
B
e
t
w
e
e
n
System
S
y
s
t
e
m
and
a
n
d
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Processes
P
r
o
c
e
s
s
e
s
Figure
F
i
g
u
r
e
2-1
2
-
1
is
i
s
an
a
n
overview
o
v
e
r
v
i
e
w
of
o
f
the
t
h
e
safety
s
a
f
e
t
y
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
information
i
n
f
o
r
m
a
t
i
o
n
flow
f
l
o
w
between
b
e
t
w
e
e
n
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
Due
D
u
e
to
t
o
interdependence
i
n
t
e
r
d
e
p
e
n
d
e
n
c
e
of
o
f
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
and
a
n
d
the
t
h
e
system
s
y
s
t
e
m
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
flow
f
l
o
w
of
o
f
information
i
n
f
o
r
m
a
t
i
o
n
described
d
e
s
c
r
i
b
e
d
in
i
n
these
t
h
e
s
e
sections
s
e
c
t
i
o
n
s
is
i
s
iterative.
i
t
e
r
a
t
i
v
e
.
FIGURE
F
I
G
U
R
E
2-1
2
-
1
SYSTEM
S
Y
S
T
E
M
SAFETY-RELATED
S
A
F
E
T
Y
-
R
E
L
A
T
E
D
INFORMATION
I
N
F
O
R
M
A
T
I
O
N
FLOW
F
L
O
W
BETWEEN
B
E
T
W
E
E
N
SYSTEM
S
Y
S
T
E
M
AND
A
N
D
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE
C
Y
C
L
E
PROCESSES
P
R
O
C
E
S
S
E
S
Note:
N
o
t
e
:
At
A
t
the
t
h
e
time
t
i
m
e
of
o
f
publication
p
u
b
l
i
c
a
t
i
o
n
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
guidelines
g
u
i
d
e
l
i
n
e
s
for
f
o
r
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
were
w
e
r
e
under
u
n
d
e
r
development
d
e
v
e
l
o
p
m
e
n
t
by
b
y
an
a
n
international
i
n
t
e
r
n
a
t
i
o
n
a
l
committee.
c
o
m
m
i
t
t
e
e
.
While
W
h
i
l
e
every
e
v
e
r
y
attempt
a
t
t
e
m
p
t
was
w
a
s
made
m
a
d
e
to
t
o
keep
k
e
e
p
the
t
h
e
inter-process
i
n
t
e
r
-
p
r
o
c
e
s
s
information
i
n
f
o
r
m
a
t
i
o
n
flows
f
l
o
w
s
and
a
n
d
definitions
d
e
f
i
n
i
t
i
o
n
s
compatible,
c
o
m
p
a
t
i
b
l
e
,
some
s
o
m
e
differences
d
i
f
f
e
r
e
n
c
e
s
may
m
a
y
exist
e
x
i
s
t
between
b
e
t
w
e
e
n
the
t
h
e
final
f
i
n
a
l
published
p
u
b
l
i
s
h
e
d
documents.
d
o
c
u
m
e
n
t
s
.
Any
A
n
y
differences
d
i
f
f
e
r
e
n
c
e
s
will
w
i
l
l
be
b
e
reconciled
r
e
c
o
n
c
i
l
e
d
in
i
n
future
f
u
t
u
r
e
revisions
r
e
v
i
s
i
o
n
s
of
o
f
the
t
h
e
documents.
d
o
c
u
m
e
n
t
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
6
6
2.1.1
2
.
1
.
1
Information
I
n
f
o
r
m
a
t
i
o
n
Flow
F
l
o
w
from
f
r
o
m
System
S
y
s
t
e
m
Processes
P
r
o
c
e
s
s
e
s
to
t
o
Software
S
o
f
t
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
The
T
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
determines
d
e
t
e
r
m
i
n
e
s
and
a
n
d
categorizes
c
a
t
e
g
o
r
i
z
e
s
the
t
h
e
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
of
o
f
the
t
h
e
system.
s
y
s
t
e
m
.
Within
W
i
t
h
i
n
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
an
a
n
analysis
a
n
a
l
y
s
i
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
design
d
e
s
i
g
n
defines
d
e
f
i
n
e
s
safety
s
a
f
e
t
y
related
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
specify
s
p
e
c
i
f
y
the
t
h
e
desired
d
e
s
i
r
e
d
immunity
i
m
m
u
n
i
t
y
from,
f
r
o
m
,
and
a
n
d
system
s
y
s
t
e
m
responses
r
e
s
p
o
n
s
e
s
to,
t
o
,
these
t
h
e
s
e
failure
f
a
i
l
u
r
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
These
T
h
e
s
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
defined
d
e
f
i
n
e
d
for
f
o
r
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software
s
o
f
t
w
a
r
e
to
t
o
preclude
p
r
e
c
l
u
d
e
or
o
r
limit
l
i
m
i
t
the
t
h
e
effects
e
f
f
e
c
t
s
of
o
f
faults,
f
a
u
l
t
s
,
and
a
n
d
may
m
a
y
provide
p
r
o
v
i
d
e
fault
f
a
u
l
t
detection
d
e
t
e
c
t
i
o
n
and
a
n
d
fault
f
a
u
l
t
tolerance.
t
o
l
e
r
a
n
c
e
.
As
A
s
decisions
d
e
c
i
s
i
o
n
s
are
a
r
e
being
b
e
i
n
g
made
m
a
d
e
during
d
u
r
i
n
g
the
t
h
e
hardware
h
a
r
d
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
and
a
n
d
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes,
p
r
o
c
e
s
s
e
s
,
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
analyzes
a
n
a
l
y
z
e
s
the
t
h
e
resulting
r
e
s
u
l
t
i
n
g
system
s
y
s
t
e
m
design
d
e
s
i
g
n
to
t
o
verify
v
e
r
i
f
y
that
t
h
a
t
it
i
t
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
a
a
part
p
a
r
t
of
o
f
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
which
w
h
i
c
h
are
a
r
e
inputs
i
n
p
u
t
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
To
T
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
properly
p
r
o
p
e
r
l
y
implemented
i
m
p
l
e
m
e
n
t
e
d
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle,
c
y
c
l
e
,
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
typically
t
y
p
i
c
a
l
l
y
include
i
n
c
l
u
d
e
or
o
r
reference:
r
e
f
e
r
e
n
c
e
:
-
The
T
h
e
system
s
y
s
t
e
m
description
d
e
s
c
r
i
p
t
i
o
n
and
a
n
d
hardware
h
a
r
d
w
a
r
e
definition.
d
e
f
i
n
i
t
i
o
n
.
-
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
including
i
n
c
l
u
d
i
n
g
applicable
a
p
p
l
i
c
a
b
l
e
Federal
F
e
d
e
r
a
l
Aviation
A
v
i
a
t
i
o
n
Regulations
R
e
g
u
l
a
t
i
o
n
s
(FAR
(
F
A
R
-
-
United
U
n
i
t
e
d
States),
S
t
a
t
e
s
)
,
Joint
J
o
i
n
t
Aviation
A
v
i
a
t
i
o
n
Regulations
R
e
g
u
l
a
t
i
o
n
s
(JAR
(
J
A
R
-
-
Europe),
E
u
r
o
p
e
)
,
Advisory
A
d
v
i
s
o
r
y
Circulars
C
i
r
c
u
l
a
r
s
(United
(
U
n
i
t
e
d
States),
S
t
a
t
e
s
)
,
etc.
e
t
c
.
-
System
S
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software,
s
o
f
t
w
a
r
e
,
including
i
n
c
l
u
d
i
n
g
functional
f
u
n
c
t
i
o
n
a
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
performance
p
e
r
f
o
r
m
a
n
c
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Software
S
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
and
a
n
d
data
d
a
t
a
substantiating
s
u
b
s
t
a
n
t
i
a
t
i
n
g
their
t
h
e
i
r
determination,
d
e
t
e
r
m
i
n
a
t
i
o
n
,
failure
f
a
i
l
u
r
e
conditions,
c
o
n
d
i
t
i
o
n
s
,
their
t
h
e
i
r
categories,
c
a
t
e
g
o
r
i
e
s
,
and
a
n
d
related
r
e
l
a
t
e
d
functions
f
u
n
c
t
i
o
n
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software.
s
o
f
t
w
a
r
e
.
-
Safety
S
a
f
e
t
y
strategies
s
t
r
a
t
e
g
i
e
s
and
a
n
d
design
d
e
s
i
g
n
constraints,
c
o
n
s
t
r
a
i
n
t
s
,
including
i
n
c
l
u
d
i
n
g
design
d
e
s
i
g
n
methods,
m
e
t
h
o
d
s
,
such
s
u
c
h
as,
a
s
,
partitioning,
p
a
r
t
i
t
i
o
n
i
n
g
,
dissimilarity,
d
i
s
s
i
m
i
l
a
r
i
t
y
,
redundancy
r
e
d
u
n
d
a
n
c
y
or
o
r
safety
s
a
f
e
t
y
monitoring.
m
o
n
i
t
o
r
i
n
g
.
-
If
I
f
the
t
h
e
system
s
y
s
t
e
m
is
i
s
a
a
component
c
o
m
p
o
n
e
n
t
of
o
f
another
a
n
o
t
h
e
r
system,
s
y
s
t
e
m
,
the
t
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
for
f
o
r
that
t
h
a
t
system.
s
y
s
t
e
m
.
System
S
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
may
m
a
y
specify
s
p
e
c
i
f
y
requirements
r
e
q
u
i
r
e
m
e
n
t
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
to
t
o
aid
a
i
d
system
s
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
activities.
a
c
t
i
v
i
t
i
e
s
.
2.1.2
2
.
1
.
2
Information
I
n
f
o
r
m
a
t
i
o
n
Flow
F
l
o
w
from
f
r
o
m
Software
S
o
f
t
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
to
t
o
System
S
y
s
t
e
m
Processes
P
r
o
c
e
s
s
e
s
The
T
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
determines
d
e
t
e
r
m
i
n
e
s
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
and
a
n
d
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
on
o
n
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
using
u
s
i
n
g
information
i
n
f
o
r
m
a
t
i
o
n
provided
p
r
o
v
i
d
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
This
T
h
i
s
information
i
n
f
o
r
m
a
t
i
o
n
includes
i
n
c
l
u
d
e
s
fault
f
a
u
l
t
containment
c
o
n
t
a
i
n
m
e
n
t
boundaries,
b
o
u
n
d
a
r
i
e
s
,
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
and
a
n
d
error
e
r
r
o
r
sources
s
o
u
r
c
e
s
that
t
h
a
t
may
m
a
y
have
h
a
v
e
been
b
e
e
n
detected
d
e
t
e
c
t
e
d
or
o
r
eliminated
e
l
i
m
i
n
a
t
e
d
through
t
h
r
o
u
g
h
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
or
o
r
by
b
y
the
t
h
e
use
u
s
e
of
o
f
tools
t
o
o
l
s
or
o
r
by
b
y
other
o
t
h
e
r
methods
m
e
t
h
o
d
s
used
u
s
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process.
p
r
o
c
e
s
s
.
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
data
d
a
t
a
is
i
s
important
i
m
p
o
r
t
a
n
t
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
Modifications
M
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
may
m
a
y
affect
a
f
f
e
c
t
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
and,
a
n
d
,
therefore,
t
h
e
r
e
f
o
r
e
,
need
n
e
e
d
to
t
o
be
b
e
identified
i
d
e
n
t
i
f
i
e
d
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
for
f
o
r
evaluation.
e
v
a
l
u
a
t
i
o
n
.
2.2
2
.
2
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
and
a
n
d
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Guidance
G
u
i
d
a
n
c
e
follows
f
o
l
l
o
w
s
concerning
c
o
n
c
e
r
n
i
n
g
system
s
y
s
t
e
m
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
categories,
c
a
t
e
g
o
r
i
e
s
,
the
t
h
e
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
levels,
l
e
v
e
l
s
,
the
t
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
and
a
n
d
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
categories,
c
a
t
e
g
o
r
i
e
s
,
and
a
n
d
how
h
o
w
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
determined.
d
e
t
e
r
m
i
n
e
d
.
The
T
h
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
of
o
f
a
a
system
s
y
s
t
e
m
is
i
s
establis
e
s
t
a
b
l
i
s
hed
h
e
d
by
b
y
determining
d
e
t
e
r
m
i
n
i
n
g
the
t
h
e
severity
s
e
v
e
r
i
t
y
of
o
f
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
on
o
n
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
its
i
t
s
occupants.
o
c
c
u
p
a
n
t
s
.
An
A
n
error
e
r
r
o
r
in
i
n
software
s
o
f
t
w
a
r
e
may
m
a
y
cause
c
a
u
s
e
a
a
fault
f
a
u
l
t
that
t
h
a
t
contributes
c
o
n
t
r
i
b
u
t
e
s
to
t
o
a
a
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
Thus,
T
h
u
s
,
the
t
h
e
level
l
e
v
e
l
of
o
f
software
s
o
f
t
w
a
r
e
integrity
i
n
t
e
g
r
i
t
y
necessary
n
e
c
e
s
s
a
r
y
for
f
o
r
safe
s
a
f
e
operation
o
p
e
r
a
t
i
o
n
is
i
s
related
r
e
l
a
t
e
d
to
t
o
the
t
h
e
system
s
y
s
t
e
m
failure
f
a
i
l
u
r
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
7
7
2.2.1
2
.
2
.
1
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
Categorization
C
a
t
e
g
o
r
i
z
a
t
i
o
n
For
F
o
r
a
a
complete
c
o
m
p
l
e
t
e
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
categories,
c
a
t
e
g
o
r
i
e
s
,
refer
r
e
f
e
r
to
t
o
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
regulations
r
e
g
u
l
a
t
i
o
n
s
and
a
n
d
guidance
g
u
i
d
a
n
c
e
material,
m
a
t
e
r
i
a
l
,
Federal
F
e
d
e
r
a
l
Aviation
A
v
i
a
t
i
o
n
Administration
A
d
m
i
n
i
s
t
r
a
t
i
o
n
AC
A
C
25-1309-1A
2
5
-
1
3
0
9
-
1
A
and/or
a
n
d
/
o
r
the
t
h
e
Joint
J
o
i
n
t
Aviation
A
v
i
a
t
i
o
n
Authorities
A
u
t
h
o
r
i
t
i
e
s
AMJ
A
M
J
25-
2
5
-
1309,
1
3
0
9
,
as
a
s
amended.
a
m
e
n
d
e
d
.
The
T
h
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
categories
c
a
t
e
g
o
r
i
e
s
listed
l
i
s
t
e
d
are
a
r
e
derived
d
e
r
i
v
e
d
from
f
r
o
m
this
t
h
i
s
guidance
g
u
i
d
a
n
c
e
material
m
a
t
e
r
i
a
l
and
a
n
d
are
a
r
e
included
i
n
c
l
u
d
e
d
to
t
o
assist
a
s
s
i
s
t
in
i
n
the
t
h
e
use
u
s
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
The
T
h
e
categories
c
a
t
e
g
o
r
i
e
s
are:
a
r
e
:
-
Catastrophic:
C
a
t
a
s
t
r
o
p
h
i
c
:
Failure
F
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
which
w
h
i
c
h
would
w
o
u
l
d
prevent
p
r
e
v
e
n
t
continued
c
o
n
t
i
n
u
e
d
safe
s
a
f
e
flight
f
l
i
g
h
t
and
a
n
d
landing.
l
a
n
d
i
n
g
.
-
Hazardous/Severe-Major:
H
a
z
a
r
d
o
u
s
/
S
e
v
e
r
e
-
M
a
j
o
r
:
Failure
F
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
which
w
h
i
c
h
would
w
o
u
l
d
reduce
r
e
d
u
c
e
the
t
h
e
capability
c
a
p
a
b
i
l
i
t
y
of
o
f
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
the
t
h
e
ability
a
b
i
l
i
t
y
of
o
f
the
t
h
e
crew
c
r
e
w
to
t
o
cope
c
o
p
e
with
w
i
t
h
adverse
a
d
v
e
r
s
e
operating
o
p
e
r
a
t
i
n
g
conditions
c
o
n
d
i
t
i
o
n
s
to
t
o
the
t
h
e
extent
e
x
t
e
n
t
that
t
h
a
t
there
t
h
e
r
e
would
w
o
u
l
d
be:
b
e
:
-
a
a
large
l
a
r
g
e
reduction
r
e
d
u
c
t
i
o
n
in
i
n
safety
s
a
f
e
t
y
margins
m
a
r
g
i
n
s
or
o
r
functional
f
u
n
c
t
i
o
n
a
l
capabilities,
c
a
p
a
b
i
l
i
t
i
e
s
,
-
physical
p
h
y
s
i
c
a
l
distress
d
i
s
t
r
e
s
s
or
o
r
higher
h
i
g
h
e
r
workload
w
o
r
k
l
o
a
d
such
s
u
c
h
that
t
h
a
t
the
t
h
e
flight
f
l
i
g
h
t
crew
c
r
e
w
could
c
o
u
l
d
not
n
o
t
be
b
e
relied
r
e
l
i
e
d
on
o
n
to
t
o
perform
p
e
r
f
o
r
m
their
t
h
e
i
r
tasks
t
a
s
k
s
accurately
a
c
c
u
r
a
t
e
l
y
or
o
r
completely,
c
o
m
p
l
e
t
e
l
y
,
or
o
r
-
adverse
a
d
v
e
r
s
e
effects
e
f
f
e
c
t
s
on
o
n
occupants
o
c
c
u
p
a
n
t
s
including
i
n
c
l
u
d
i
n
g
serious
s
e
r
i
o
u
s
or
o
r
potentially
p
o
t
e
n
t
i
a
l
l
y
fatal
f
a
t
a
l
injuries
i
n
j
u
r
i
e
s
to
t
o
a
a
small
s
m
a
l
l
number
n
u
m
b
e
r
of
o
f
those
t
h
o
s
e
occupants.
o
c
c
u
p
a
n
t
s
.
-
Major:
M
a
j
o
r
:
Failure
F
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
which
w
h
i
c
h
would
w
o
u
l
d
reduce
r
e
d
u
c
e
the
t
h
e
capability
c
a
p
a
b
i
l
i
t
y
of
o
f
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
the
t
h
e
ability
a
b
i
l
i
t
y
of
o
f
the
t
h
e
crew
c
r
e
w
to
t
o
cope
c
o
p
e
with
w
i
t
h
adverse
a
d
v
e
r
s
e
operating
o
p
e
r
a
t
i
n
g
conditions
c
o
n
d
i
t
i
o
n
s
to
t
o
the
t
h
e
extent
e
x
t
e
n
t
that
t
h
a
t
there
t
h
e
r
e
would
w
o
u
l
d
be,
b
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
a
a
significant
s
i
g
n
i
f
i
c
a
n
t
reduction
r
e
d
u
c
t
i
o
n
in
i
n
safety
s
a
f
e
t
y
margins
m
a
r
g
i
n
s
or
o
r
functional
f
u
n
c
t
i
o
n
a
l
capabilities,
c
a
p
a
b
i
l
i
t
i
e
s
,
a
a
significant
s
i
g
n
i
f
i
c
a
n
t
increase
i
n
c
r
e
a
s
e
in
i
n
crew
c
r
e
w
workload
w
o
r
k
l
o
a
d
or
o
r
in
i
n
conditions
c
o
n
d
i
t
i
o
n
s
impairing
i
m
p
a
i
r
i
n
g
crew
c
r
e
w
efficiency,
e
f
f
i
c
i
e
n
c
y
,
or
o
r
discomfort
d
i
s
c
o
m
f
o
r
t
to
t
o
occupants,
o
c
c
u
p
a
n
t
s
,
possibly
p
o
s
s
i
b
l
y
including
i
n
c
l
u
d
i
n
g
injuries.
i
n
j
u
r
i
e
s
.
-
Minor:
M
i
n
o
r
:
Failure
F
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
which
w
h
i
c
h
would
w
o
u
l
d
not
n
o
t
significantly
s
i
g
n
i
f
i
c
a
n
t
l
y
reduce
r
e
d
u
c
e
aircraft
a
i
r
c
r
a
f
t
safety,
s
a
f
e
t
y
,
and
a
n
d
which
w
h
i
c
h
would
w
o
u
l
d
involve
i
n
v
o
l
v
e
crew
c
r
e
w
actions
a
c
t
i
o
n
s
that
t
h
a
t
are
a
r
e
well
w
e
l
l
within
w
i
t
h
i
n
their
t
h
e
i
r
capabilities.
c
a
p
a
b
i
l
i
t
i
e
s
.
Minor
M
i
n
o
r
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
may
m
a
y
include,
i
n
c
l
u
d
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
a
a
slight
s
l
i
g
h
t
reduction
r
e
d
u
c
t
i
o
n
in
i
n
safety
s
a
f
e
t
y
margins
m
a
r
g
i
n
s
or
o
r
functional
f
u
n
c
t
i
o
n
a
l
capabilities,
c
a
p
a
b
i
l
i
t
i
e
s
,
a
a
slight
s
l
i
g
h
t
increase
i
n
c
r
e
a
s
e
in
i
n
crew
c
r
e
w
workload,
w
o
r
k
l
o
a
d
,
such
s
u
c
h
as,
a
s
,
routine
r
o
u
t
i
n
e
flight
f
l
i
g
h
t
plan
p
l
a
n
changes,
c
h
a
n
g
e
s
,
or
o
r
some
s
o
m
e
inconvenience
i
n
c
o
n
v
e
n
i
e
n
c
e
to
t
o
occupants.
o
c
c
u
p
a
n
t
s
.
-
No
N
o
Effect:
E
f
f
e
c
t
:
Failure
F
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
which
w
h
i
c
h
do
d
o
not
n
o
t
affect
a
f
f
e
c
t
the
t
h
e
operational
o
p
e
r
a
t
i
o
n
a
l
capability
c
a
p
a
b
i
l
i
t
y
of
o
f
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
increase
i
n
c
r
e
a
s
e
crew
c
r
e
w
workload.
w
o
r
k
l
o
a
d
.
2.2.2
2
.
2
.
2
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Definitions
D
e
f
i
n
i
t
i
o
n
s
Software
S
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
based
b
a
s
e
d
upon
u
p
o
n
the
t
h
e
contribution
c
o
n
t
r
i
b
u
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
to
t
o
potential
p
o
t
e
n
t
i
a
l
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
as
a
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
implies
i
m
p
l
i
e
s
that
t
h
a
t
the
t
h
e
level
l
e
v
e
l
of
o
f
effort
e
f
f
o
r
t
required
r
e
q
u
i
r
e
d
to
t
o
show
s
h
o
w
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
requirements
r
e
q
u
i
r
e
m
e
n
t
s
varies
v
a
r
i
e
s
with
w
i
t
h
the
t
h
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category.
c
a
t
e
g
o
r
y
.
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
definitions
d
e
f
i
n
i
t
i
o
n
s
are:
a
r
e
:
-
Level
L
e
v
e
l
A:
A
:
Software
S
o
f
t
w
a
r
e
whose
w
h
o
s
e
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
as
a
s
shown
s
h
o
w
n
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
would
w
o
u
l
d
cause
c
a
u
s
e
or
o
r
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
a
a
failure
f
a
i
l
u
r
e
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
resulting
r
e
s
u
l
t
i
n
g
in
i
n
a
a
catastrophic
c
a
t
a
s
t
r
o
p
h
i
c
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
for
f
o
r
the
t
h
e
aircraft.
a
i
r
c
r
a
f
t
.
-
Level
L
e
v
e
l
B:
B
:
Software
S
o
f
t
w
a
r
e
whose
w
h
o
s
e
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
as
a
s
shown
s
h
o
w
n
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
would
w
o
u
l
d
cause
c
a
u
s
e
or
o
r
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
a
a
failure
f
a
i
l
u
r
e
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
resulting
r
e
s
u
l
t
i
n
g
in
i
n
a
a
hazardous/severe-major
h
a
z
a
r
d
o
u
s
/
s
e
v
e
r
e
-
m
a
j
o
r
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
for
f
o
r
the
t
h
e
aircraft.
a
i
r
c
r
a
f
t
.
-
Level
L
e
v
e
l
C:
C
:
Software
S
o
f
t
w
a
r
e
whose
w
h
o
s
e
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
as
a
s
shown
s
h
o
w
n
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
would
w
o
u
l
d
cause
c
a
u
s
e
or
o
r
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
a
a
failure
f
a
i
l
u
r
e
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
resulting
r
e
s
u
l
t
i
n
g
in
i
n
a
a
major
m
a
j
o
r
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
for
f
o
r
the
t
h
e
aircraft.
a
i
r
c
r
a
f
t
.
-
Level
L
e
v
e
l
D:
D
:
Software
S
o
f
t
w
a
r
e
whose
w
h
o
s
e
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
as
a
s
shown
s
h
o
w
n
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
would
w
o
u
l
d
cause
c
a
u
s
e
or
o
r
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
a
a
failure
f
a
i
l
u
r
e
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
resulting
r
e
s
u
l
t
i
n
g
in
i
n
a
a
minor
m
i
n
o
r
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
for
f
o
r
the
t
h
e
aircraft.
a
i
r
c
r
a
f
t
.
-
Level
L
e
v
e
l
E:
E
:
Software
S
o
f
t
w
a
r
e
whose
w
h
o
s
e
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
as
a
s
shown
s
h
o
w
n
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
would
w
o
u
l
d
cause
c
a
u
s
e
or
o
r
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
a
a
failure
f
a
i
l
u
r
e
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
with
w
i
t
h
no
n
o
effect
e
f
f
e
c
t
on
o
n
aircraft
a
i
r
c
r
a
f
t
operational
o
p
e
r
a
t
i
o
n
a
l
capability
c
a
p
a
b
i
l
i
t
y
or
o
r
pilot
p
i
l
o
t
workload.
w
o
r
k
l
o
a
d
.
Once
O
n
c
e
software
s
o
f
t
w
a
r
e
has
h
a
s
been
b
e
e
n
confirmed
c
o
n
f
i
r
m
e
d
as
a
s
level
l
e
v
e
l
E
E
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority,
a
u
t
h
o
r
i
t
y
,
no
n
o
further
f
u
r
t
h
e
r
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
apply.
a
p
p
l
y
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
8
8
2.2.3
2
.
2
.
3
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
Initially,
I
n
i
t
i
a
l
l
y
,
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
determines
d
e
t
e
r
m
i
n
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
appropriate
a
p
p
r
o
p
r
i
a
t
e
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
of
o
f
a
a
particular
p
a
r
t
i
c
u
l
a
r
system
s
y
s
t
e
m
without
w
i
t
h
o
u
t
regard
r
e
g
a
r
d
to
t
o
system
s
y
s
t
e
m
design.
d
e
s
i
g
n
.
The
T
h
e
impact
i
m
p
a
c
t
of
o
f
failure,
f
a
i
l
u
r
e
,
both
b
o
t
h
loss
l
o
s
s
of
o
f
function
f
u
n
c
t
i
o
n
and
a
n
d
malfunction,
m
a
l
f
u
n
c
t
i
o
n
,
is
i
s
addressed
a
d
d
r
e
s
s
e
d
when
w
h
e
n
making
m
a
k
i
n
g
this
t
h
i
s
determination.
d
e
t
e
r
m
i
n
a
t
i
o
n
.
Note:
N
o
t
e
:
(1)
(
1
)
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
may
m
a
y
want
w
a
n
t
to
t
o
consider
c
o
n
s
i
d
e
r
planned
p
l
a
n
n
e
d
functionality
f
u
n
c
t
i
o
n
a
l
i
t
y
to
t
o
be
b
e
added
a
d
d
e
d
during
d
u
r
i
n
g
future
f
u
t
u
r
e
developments,
d
e
v
e
l
o
p
m
e
n
t
s
,
as
a
s
well
w
e
l
l
as
a
s
potential
p
o
t
e
n
t
i
a
l
changes
c
h
a
n
g
e
s
in
i
n
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
that
t
h
a
t
may
m
a
y
result
r
e
s
u
l
t
in
i
n
a
a
more
m
o
r
e
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
and
a
n
d
higher
h
i
g
h
e
r
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
It
I
t
may
m
a
y
be
b
e
desirable
d
e
s
i
r
a
b
l
e
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
software
s
o
f
t
w
a
r
e
to
t
o
a
a
level
l
e
v
e
l
higher
h
i
g
h
e
r
than
t
h
a
n
that
t
h
a
t
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
of
o
f
the
t
h
e
original
o
r
i
g
i
n
a
l
application,
a
p
p
l
i
c
a
t
i
o
n
,
since
s
i
n
c
e
later
l
a
t
e
r
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
for
f
o
r
substantiating
s
u
b
s
t
a
n
t
i
a
t
i
n
g
a
a
higher
h
i
g
h
e
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
application
a
p
p
l
i
c
a
t
i
o
n
may
m
a
y
be
b
e
difficult.
d
i
f
f
i
c
u
l
t
.
(2)
(
2
)
For
F
o
r
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
mandated
m
a
n
d
a
t
e
d
by
b
y
operating
o
p
e
r
a
t
i
n
g
regulations,
r
e
g
u
l
a
t
i
o
n
s
,
but
b
u
t
which
w
h
i
c
h
do
d
o
not
n
o
t
affect
a
f
f
e
c
t
the
t
h
e
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
of
o
f
the
t
h
e
aircraft,
a
i
r
c
r
a
f
t
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
an
a
n
accident
a
c
c
i
d
e
n
t
flight
f
l
i
g
h
t
data
d
a
t
a
recorder,
r
e
c
o
r
d
e
r
,
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
needs
n
e
e
d
s
to
t
o
be
b
e
commensurate
c
o
m
m
e
n
s
u
r
a
t
e
with
w
i
t
h
the
t
h
e
intended
i
n
t
e
n
d
e
d
function.
f
u
n
c
t
i
o
n
.
In
I
n
some
s
o
m
e
cases,
c
a
s
e
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
may
m
a
y
be
b
e
specified
s
p
e
c
i
f
i
e
d
in
i
n
equipment
e
q
u
i
p
m
e
n
t
minimum
m
i
n
i
m
u
m
performance
p
e
r
f
o
r
m
a
n
c
e
standards.
s
t
a
n
d
a
r
d
s
.
If
I
f
the
t
h
e
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
a
a
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
contributes
c
o
n
t
r
i
b
u
t
e
s
to
t
o
more
m
o
r
e
than
t
h
a
n
one
o
n
e
failure
f
a
i
l
u
r
e
condition,
c
o
n
d
i
t
i
o
n
,
then
t
h
e
n
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
of
o
f
that
t
h
a
t
component
c
o
m
p
o
n
e
n
t
determines
d
e
t
e
r
m
i
n
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
that
t
h
a
t
software
s
o
f
t
w
a
r
e
component.
c
o
m
p
o
n
e
n
t
.
There
T
h
e
r
e
are
a
r
e
various
v
a
r
i
o
u
s
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
strategies,
s
t
r
a
t
e
g
i
e
s
,
such
s
u
c
h
as
a
s
those
t
h
o
s
e
described
d
e
s
c
r
i
b
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
2.3,
2
.
3
,
which
w
h
i
c
h
during
d
u
r
i
n
g
the
t
h
e
evolution
e
v
o
l
u
t
i
o
n
of
o
f
the
t
h
e
system
s
y
s
t
e
m
design,
d
e
s
i
g
n
,
may
m
a
y
result
r
e
s
u
l
t
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
being
b
e
i
n
g
revised.
r
e
v
i
s
e
d
.
A
A
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
may
m
a
y
be
b
e
allocated
a
l
l
o
c
a
t
e
d
to
t
o
one
o
n
e
or
o
r
more
m
o
r
e
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
components.
c
o
m
p
o
n
e
n
t
s
.
A
A
parallel
p
a
r
a
l
l
e
l
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
is
i
s
one
o
n
e
in
i
n
which
w
h
i
c
h
a
a
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
is
i
s
implemented
i
m
p
l
e
m
e
n
t
e
d
with
w
i
t
h
multiple
m
u
l
t
i
p
l
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
such
s
u
c
h
that
t
h
a
t
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
more
m
o
r
e
than
t
h
a
n
one
o
n
e
component
c
o
m
p
o
n
e
n
t
is
i
s
required
r
e
q
u
i
r
e
d
to
t
o
produce
p
r
o
d
u
c
e
the
t
h
e
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
For
F
o
r
a
a
parallel
p
a
r
a
l
l
e
l
implementation,
i
m
p
l
e
m
e
n
t
a
t
i
o
n
,
at
a
t
least
l
e
a
s
t
one
o
n
e
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
will
w
i
l
l
have
h
a
v
e
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
for
f
o
r
that
t
h
a
t
system
s
y
s
t
e
m
function.
f
u
n
c
t
i
o
n
.
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
the
t
h
e
other
o
t
h
e
r
components
c
o
m
p
o
n
e
n
t
s
are
a
r
e
determined
d
e
t
e
r
m
i
n
e
d
using
u
s
i
n
g
the
t
h
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
loss
l
o
s
s
of
o
f
that
t
h
a
t
function.
f
u
n
c
t
i
o
n
.
Examples
E
x
a
m
p
l
e
s
of
o
f
such
s
u
c
h
implementations
i
m
p
l
e
m
e
n
t
a
t
i
o
n
s
are
a
r
e
described
d
e
s
c
r
i
b
e
d
in
i
n
paragraphs
p
a
r
a
g
r
a
p
h
s
2.3.2,
2
.
3
.
2
,
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software,
S
o
f
t
w
a
r
e
,
and
a
n
d
2.3.3,
2
.
3
.
3
,
Safety
S
a
f
e
t
y
Monitoring.
M
o
n
i
t
o
r
i
n
g
.
A
A
serial
s
e
r
i
a
l
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
is
i
s
one
o
n
e
in
i
n
which
w
h
i
c
h
multiple
m
u
l
t
i
p
l
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
are
a
r
e
used
u
s
e
d
for
f
o
r
a
a
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
such
s
u
c
h
that
t
h
a
t
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
any
a
n
y
of
o
f
the
t
h
e
components
c
o
m
p
o
n
e
n
t
s
could
c
o
u
l
d
produce
p
r
o
d
u
c
e
the
t
h
e
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
In
I
n
this
t
h
i
s
implementation,
i
m
p
l
e
m
e
n
t
a
t
i
o
n
,
the
t
h
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
will
w
i
l
l
have
h
a
v
e
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
of
o
f
the
t
h
e
system
s
y
s
t
e
m
function.
f
u
n
c
t
i
o
n
.
Development
D
e
v
e
l
o
p
m
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
to
t
o
a
a
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
does
d
o
e
s
not
n
o
t
imply
i
m
p
l
y
the
t
h
e
assignment
a
s
s
i
g
n
m
e
n
t
of
o
f
a
a
failure
f
a
i
l
u
r
e
rate
r
a
t
e
for
f
o
r
that
t
h
a
t
software.
s
o
f
t
w
a
r
e
.
Thus,
T
h
u
s
,
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
or
o
r
software
s
o
f
t
w
a
r
e
reliability
r
e
l
i
a
b
i
l
i
t
y
rates
r
a
t
e
s
based
b
a
s
e
d
on
o
n
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
cannot
c
a
n
n
o
t
be
b
e
used
u
s
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
as
a
s
can
c
a
n
hardware
h
a
r
d
w
a
r
e
failure
f
a
i
l
u
r
e
rates.
r
a
t
e
s
.
Strategies
S
t
r
a
t
e
g
i
e
s
which
w
h
i
c
h
depart
d
e
p
a
r
t
from
f
r
o
m
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
paragraph
p
a
r
a
g
r
a
p
h
(2.2.3)
(
2
.
2
.
3
)
need
n
e
e
d
to
t
o
be
b
e
justified
j
u
s
t
i
f
i
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
2.3
2
.
3
System
S
y
s
t
e
m
Architectural
A
r
c
h
i
t
e
c
t
u
r
a
l
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
If
I
f
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
determines
d
e
t
e
r
m
i
n
e
s
that
t
h
a
t
the
t
h
e
system
s
y
s
t
e
m
architecture
a
r
c
h
i
t
e
c
t
u
r
e
precludes
p
r
e
c
l
u
d
e
s
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
from
f
r
o
m
contributing
c
o
n
t
r
i
b
u
t
i
n
g
to
t
o
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
of
o
f
a
a
system,
s
y
s
t
e
m
,
then
t
h
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
category
c
a
t
e
g
o
r
y
of
o
f
the
t
h
e
remaining
r
e
m
a
i
n
i
n
g
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
to
t
o
which
w
h
i
c
h
the
t
h
e
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
can
c
a
n
contribute.
c
o
n
t
r
i
b
u
t
e
.
The
T
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
considers
c
o
n
s
i
d
e
r
s
the
t
h
e
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
design
d
e
s
i
g
n
decisions
d
e
c
i
s
i
o
n
s
to
t
o
determine
d
e
t
e
r
m
i
n
e
whether
w
h
e
t
h
e
r
they
t
h
e
y
affect
a
f
f
e
c
t
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
or
o
r
software
s
o
f
t
w
a
r
e
functionality.
f
u
n
c
t
i
o
n
a
l
i
t
y
.
Guidance
G
u
i
d
a
n
c
e
is
i
s
provided
p
r
o
v
i
d
e
d
on
o
n
several
s
e
v
e
r
a
l
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
strategies
s
t
r
a
t
e
g
i
e
s
that
t
h
a
t
may
m
a
y
limit
l
i
m
i
t
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
errors,
e
r
r
o
r
s
,
or
o
r
detect
d
e
t
e
c
t
errors
e
r
r
o
r
s
and
a
n
d
provide
p
r
o
v
i
d
e
acceptable
a
c
c
e
p
t
a
b
l
e
system
s
y
s
t
e
m
responses
r
e
s
p
o
n
s
e
s
to
t
o
contain
c
o
n
t
a
i
n
the
t
h
e
errors.
e
r
r
o
r
s
.
These
T
h
e
s
e
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
techniques
t
e
c
h
n
i
q
u
e
s
are
a
r
e
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
interpreted
i
n
t
e
r
p
r
e
t
e
d
as
a
s
the
t
h
e
preferred
p
r
e
f
e
r
r
e
d
or
o
r
required
r
e
q
u
i
r
e
d
solutions.
s
o
l
u
t
i
o
n
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
9
9
2.3.1
2
.
3
.
1
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
is
i
s
a
a
technique
t
e
c
h
n
i
q
u
e
for
f
o
r
providing
p
r
o
v
i
d
i
n
g
isolation
i
s
o
l
a
t
i
o
n
between
b
e
t
w
e
e
n
functionally
f
u
n
c
t
i
o
n
a
l
l
y
independent
i
n
d
e
p
e
n
d
e
n
t
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
to
t
o
contain
c
o
n
t
a
i
n
and/or
a
n
d
/
o
r
isolate
i
s
o
l
a
t
e
faults
f
a
u
l
t
s
and
a
n
d
potentially
p
o
t
e
n
t
i
a
l
l
y
reduce
r
e
d
u
c
e
the
t
h
e
effort
e
f
f
o
r
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
If
I
f
protection
p
r
o
t
e
c
t
i
o
n
by
b
y
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
is
i
s
provided,
p
r
o
v
i
d
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
each
e
a
c
h
partitioned
p
a
r
t
i
t
i
o
n
e
d
component
c
o
m
p
o
n
e
n
t
may
m
a
y
be
b
e
determined
d
e
t
e
r
m
i
n
e
d
using
u
s
i
n
g
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
that
t
h
a
t
component.
c
o
m
p
o
n
e
n
t
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
includes:
i
n
c
l
u
d
e
s
:
-
These
T
h
e
s
e
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
should
s
h
o
u
l
d
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
when
w
h
e
n
designing
d
e
s
i
g
n
i
n
g
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
protection
p
r
o
t
e
c
t
i
o
n
to
t
o
determine
d
e
t
e
r
m
i
n
e
their
t
h
e
i
r
potential
p
o
t
e
n
t
i
a
l
for
f
o
r
violating
v
i
o
l
a
t
i
n
g
that
t
h
a
t
protection:
p
r
o
t
e
c
t
i
o
n
:
-
Hardware
H
a
r
d
w
a
r
e
resources:
r
e
s
o
u
r
c
e
s
:
processors,
p
r
o
c
e
s
s
o
r
s
,
memory
m
e
m
o
r
y
devices,
d
e
v
i
c
e
s
,
I/O
I
/
O
devices,
d
e
v
i
c
e
s
,
interrupts,
i
n
t
e
r
r
u
p
t
s
,
and
a
n
d
timers.
t
i
m
e
r
s
.
-
Control
C
o
n
t
r
o
l
coupling:
c
o
u
p
l
i
n
g
:
vulnerability
v
u
l
n
e
r
a
b
i
l
i
t
y
to
t
o
external
e
x
t
e
r
n
a
l
access.
a
c
c
e
s
s
.
-
Data
D
a
t
a
coupling:
c
o
u
p
l
i
n
g
:
shared
s
h
a
r
e
d
or
o
r
overlaying
o
v
e
r
l
a
y
i
n
g
data,
d
a
t
a
,
including
i
n
c
l
u
d
i
n
g
stacks
s
t
a
c
k
s
and
a
n
d
processor
p
r
o
c
e
s
s
o
r
registers.
r
e
g
i
s
t
e
r
s
.
-
Failure
F
a
i
l
u
r
e
modes
m
o
d
e
s
of
o
f
hardware
h
a
r
d
w
a
r
e
devices
d
e
v
i
c
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
protection
p
r
o
t
e
c
t
i
o
n
mechanisms.
m
e
c
h
a
n
i
s
m
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
should
s
h
o
u
l
d
address
a
d
d
r
e
s
s
the
t
h
e
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
design
d
e
s
i
g
n
considerations,
c
o
n
s
i
d
e
r
a
t
i
o
n
s
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
extent
e
x
t
e
n
t
and
a
n
d
scope
s
c
o
p
e
of
o
f
interactions
i
n
t
e
r
a
c
t
i
o
n
s
permitted
p
e
r
m
i
t
t
e
d
between
b
e
t
w
e
e
n
the
t
h
e
partitioned
p
a
r
t
i
t
i
o
n
e
d
components,
c
o
m
p
o
n
e
n
t
s
,
and
a
n
d
whether
w
h
e
t
h
e
r
the
t
h
e
protection
p
r
o
t
e
c
t
i
o
n
is
i
s
implemented
i
m
p
l
e
m
e
n
t
e
d
by
b
y
hardware
h
a
r
d
w
a
r
e
or
o
r
by
b
y
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software.
s
o
f
t
w
a
r
e
.
-
If
I
f
the
t
h
e
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
protection
p
r
o
t
e
c
t
i
o
n
involves
i
n
v
o
l
v
e
s
software,
s
o
f
t
w
a
r
e
,
then
t
h
e
n
that
t
h
a
t
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
be
b
e
assigned
a
s
s
i
g
n
e
d
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
corresponding
c
o
r
r
e
s
p
o
n
d
i
n
g
to
t
o
the
t
h
e
highest
h
i
g
h
e
s
t
level
l
e
v
e
l
of
o
f
the
t
h
e
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
components.
c
o
m
p
o
n
e
n
t
s
.
2.3.2
2
.
3
.
2
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
2.3.3
2
.
3
.
3
Safety
S
a
f
e
t
y
Monitoring
M
o
n
i
t
o
r
i
n
g
Multiple
M
u
l
t
i
p
l
e
-version
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
is
i
s
a
a
system
s
y
s
t
e
m
design
d
e
s
i
g
n
technique
t
e
c
h
n
i
q
u
e
that
t
h
a
t
involves
i
n
v
o
l
v
e
s
producing
p
r
o
d
u
c
i
n
g
two
t
w
o
or
o
r
more
m
o
r
e
components
c
o
m
p
o
n
e
n
t
s
of
o
f
software
s
o
f
t
w
a
r
e
that
t
h
a
t
provide
p
r
o
v
i
d
e
the
t
h
e
same
s
a
m
e
function
f
u
n
c
t
i
o
n
in
i
n
a
a
way
w
a
y
that
t
h
a
t
may
m
a
y
avoid
a
v
o
i
d
some
s
o
m
e
sources
s
o
u
r
c
e
s
of
o
f
common
c
o
m
m
o
n
errors
e
r
r
o
r
s
between
b
e
t
w
e
e
n
the
t
h
e
components.
c
o
m
p
o
n
e
n
t
s
.
Multiple
M
u
l
t
i
p
l
e
-version
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
is
i
s
also
a
l
s
o
referred
r
e
f
e
r
r
e
d
to
t
o
as
a
s
multi-version
m
u
l
t
i
-
v
e
r
s
i
o
n
software,
s
o
f
t
w
a
r
e
,
dissimilar
d
i
s
s
i
m
i
l
a
r
software,
s
o
f
t
w
a
r
e
,
N-version
N
-
v
e
r
s
i
o
n
programming,
p
r
o
g
r
a
m
m
i
n
g
,
or
o
r
software
s
o
f
t
w
a
r
e
diversity.
d
i
v
e
r
s
i
t
y
.
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
completed
c
o
m
p
l
e
t
e
d
or
o
r
activated
a
c
t
i
v
a
t
e
d
before
b
e
f
o
r
e
dissimilarity
d
i
s
s
i
m
i
l
a
r
i
t
y
is
i
s
introduced
i
n
t
r
o
d
u
c
e
d
into
i
n
t
o
a
a
development,
d
e
v
e
l
o
p
m
e
n
t
,
remain
r
e
m
a
i
n
potential
p
o
t
e
n
t
i
a
l
error
e
r
r
o
r
sources.
s
o
u
r
c
e
s
.
System
S
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
specify
s
p
e
c
i
f
y
a
a
hardware
h
a
r
d
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
which
w
h
i
c
h
provides
p
r
o
v
i
d
e
s
for
f
o
r
the
t
h
e
execution
e
x
e
c
u
t
i
o
n
of
o
f
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software.
s
o
f
t
w
a
r
e
.
The
T
h
e
degree
d
e
g
r
e
e
of
o
f
dissimilarity
d
i
s
s
i
m
i
l
a
r
i
t
y
and
a
n
d
hence
h
e
n
c
e
the
t
h
e
degree
d
e
g
r
e
e
of
o
f
protection
p
r
o
t
e
c
t
i
o
n
is
i
s
not
n
o
t
usually
u
s
u
a
l
l
y
measurable.
m
e
a
s
u
r
a
b
l
e
.
Probability
P
r
o
b
a
b
i
l
i
t
y
of
o
f
loss
l
o
s
s
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
will
w
i
l
l
increase
i
n
c
r
e
a
s
e
to
t
o
the
t
h
e
extent
e
x
t
e
n
t
that
t
h
a
t
the
t
h
e
safety
s
a
f
e
t
y
monitoring
m
o
n
i
t
o
r
i
n
g
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
versions
v
e
r
s
i
o
n
s
detects
d
e
t
e
c
t
s
actual
a
c
t
u
a
l
errors
e
r
r
o
r
s
or
o
r
experiences
e
x
p
e
r
i
e
n
c
e
s
transients
t
r
a
n
s
i
e
n
t
s
that
t
h
a
t
exceed
e
x
c
e
e
d
comparator
c
o
m
p
a
r
a
t
o
r
threshold
t
h
r
e
s
h
o
l
d
limits.
l
i
m
i
t
s
.
Dissimilar
D
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
versions
v
e
r
s
i
o
n
s
are
a
r
e
usually
u
s
u
a
l
l
y
used,
u
s
e
d
,
therefore,
t
h
e
r
e
f
o
r
e
,
as
a
s
a
a
means
m
e
a
n
s
of
o
f
providing
p
r
o
v
i
d
i
n
g
additional
a
d
d
i
t
i
o
n
a
l
protection
p
r
o
t
e
c
t
i
o
n
after
a
f
t
e
r
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
level,
l
e
v
e
l
,
as
a
s
described
d
e
s
c
r
i
b
e
d
in
i
n
section
s
e
c
t
i
o
n
6,
6
,
have
h
a
v
e
been
b
e
e
n
satisfied.
s
a
t
i
s
f
i
e
d
.
Dissimilar
D
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
methods
m
e
t
h
o
d
s
may
m
a
y
be
b
e
reduced
r
e
d
u
c
e
d
from
f
r
o
m
those
t
h
o
s
e
used
u
s
e
d
to
t
o
verify
v
e
r
i
f
y
single
s
i
n
g
l
e
version
v
e
r
s
i
o
n
software
s
o
f
t
w
a
r
e
if
i
f
it
i
t
can
c
a
n
be
b
e
shown
s
h
o
w
n
that
t
h
a
t
the
t
h
e
resulting
r
e
s
u
l
t
i
n
g
potential
p
o
t
e
n
t
i
a
l
loss
l
o
s
s
of
o
f
system
s
y
s
t
e
m
function
f
u
n
c
t
i
o
n
is
i
s
acceptable
a
c
c
e
p
t
a
b
l
e
as
a
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
is
i
s
discussed
d
i
s
c
u
s
s
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
12.3.3.
1
2
.
3
.
3
.
Safety
S
a
f
e
t
y
monitoring
m
o
n
i
t
o
r
i
n
g
is
i
s
a
a
means
m
e
a
n
s
of
o
f
protecting
p
r
o
t
e
c
t
i
n
g
against
a
g
a
i
n
s
t
specific
s
p
e
c
i
f
i
c
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
by
b
y
directly
d
i
r
e
c
t
l
y
monitoring
m
o
n
i
t
o
r
i
n
g
a
a
function
f
u
n
c
t
i
o
n
for
f
o
r
failures
f
a
i
l
u
r
e
s
which
w
h
i
c
h
would
w
o
u
l
d
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
the
t
h
e
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
Monitoring
M
o
n
i
t
o
r
i
n
g
functions
f
u
n
c
t
i
o
n
s
may
m
a
y
be
b
e
implemented
i
m
p
l
e
m
e
n
t
e
d
in
i
n
hardware,
h
a
r
d
w
a
r
e
,
software,
s
o
f
t
w
a
r
e
,
or
o
r
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software.
s
o
f
t
w
a
r
e
.
Through
T
h
r
o
u
g
h
the
t
h
e
use
u
s
e
of
o
f
monitoring
m
o
n
i
t
o
r
i
n
g
techniques,
t
e
c
h
n
i
q
u
e
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
of
o
f
the
t
h
e
monitored
m
o
n
i
t
o
r
e
d
function
f
u
n
c
t
i
o
n
may
m
a
y
be
b
e
reduced
r
e
d
u
c
e
d
to
t
o
the
t
h
e
level
l
e
v
e
l
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
loss
l
o
s
s
of
o
f
its
i
t
s
related
r
e
l
a
t
e
d
system
s
y
s
t
e
m
function.
f
u
n
c
t
i
o
n
.
To
T
o
allow
a
l
l
o
w
this
t
h
i
s
level
l
e
v
e
l
reduction,
r
e
d
u
c
t
i
o
n
,
there
t
h
e
r
e
are
a
r
e
three
t
h
r
e
e
important
i
m
p
o
r
t
a
n
t
attributes
a
t
t
r
i
b
u
t
e
s
of
o
f
the
t
h
e
monitor
m
o
n
i
t
o
r
that
t
h
a
t
should
s
h
o
u
l
d
be
b
e
determined:
d
e
t
e
r
m
i
n
e
d
:
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
10
1
0
-
Software
S
o
f
t
w
a
r
e
level:
l
e
v
e
l
:
Safety
S
a
f
e
t
y
monitoring
m
o
n
i
t
o
r
i
n
g
software
s
o
f
t
w
a
r
e
is
i
s
assigned
a
s
s
i
g
n
e
d
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category
c
a
t
e
g
o
r
y
for
f
o
r
the
t
h
e
monitored
m
o
n
i
t
o
r
e
d
function.
f
u
n
c
t
i
o
n
.
-
System
S
y
s
t
e
m
fault
f
a
u
l
t
coverage:
c
o
v
e
r
a
g
e
:
Assessment
A
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
system
s
y
s
t
e
m
fault
f
a
u
l
t
coverage
c
o
v
e
r
a
g
e
of
o
f
a
a
monitor
m
o
n
i
t
o
r
ensures
e
n
s
u
r
e
s
that
t
h
a
t
the
t
h
e
monitor's
m
o
n
i
t
o
r
'
s
design
d
e
s
i
g
n
and
a
n
d
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
are
a
r
e
such
s
u
c
h
that
t
h
a
t
the
t
h
e
faults
f
a
u
l
t
s
which
w
h
i
c
h
it
i
t
is
i
s
intended
i
n
t
e
n
d
e
d
to
t
o
detect
d
e
t
e
c
t
will
w
i
l
l
be
b
e
detected
d
e
t
e
c
t
e
d
under
u
n
d
e
r
all
a
l
l
necessary
n
e
c
e
s
s
a
r
y
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Independence
I
n
d
e
p
e
n
d
e
n
c
e
of
o
f
Function
F
u
n
c
t
i
o
n
and
a
n
d
Monitor:
M
o
n
i
t
o
r
:
The
T
h
e
monitor
m
o
n
i
t
o
r
and
a
n
d
protective
p
r
o
t
e
c
t
i
v
e
mechanism
m
e
c
h
a
n
i
s
m
are
a
r
e
not
n
o
t
rendered
r
e
n
d
e
r
e
d
inoperative
i
n
o
p
e
r
a
t
i
v
e
by
b
y
the
t
h
e
same
s
a
m
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
that
t
h
a
t
causes
c
a
u
s
e
s
the
t
h
e
hazard.
h
a
z
a
r
d
.
2.4
2
.
4
System
S
y
s
t
e
m
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
User-Modifiable
U
s
e
r
-
M
o
d
i
f
i
a
b
l
e
Software,
S
o
f
t
w
a
r
e
,
Option-Selectable
O
p
t
i
o
n
-
S
e
l
e
c
t
a
b
l
e
Software
S
o
f
t
w
a
r
e
and
a
n
d
Commercial
C
o
m
m
e
r
c
i
a
l
Off-The-Shelf
O
f
f
-
T
h
e
-
S
h
e
l
f
Software
S
o
f
t
w
a
r
e
The
T
h
e
potential
p
o
t
e
n
t
i
a
l
effects
e
f
f
e
c
t
s
of
o
f
user
u
s
e
r
modification
m
o
d
i
f
i
c
a
t
i
o
n
are
a
r
e
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
and
a
n
d
used
u
s
e
d
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
then,
t
h
e
n
,
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
Designing
D
e
s
i
g
n
i
n
g
for
f
o
r
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
is
i
s
discussed
d
i
s
c
u
s
s
e
d
further
f
u
r
t
h
e
r
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
5.2.3.
5
.
2
.
3
.
A
A
change
c
h
a
n
g
e
that
t
h
a
t
affects
a
f
f
e
c
t
s
the
t
h
e
non-modifiable
n
o
n
-
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
its
i
t
s
protection,
p
r
o
t
e
c
t
i
o
n
,
or
o
r
the
t
h
e
modifiable
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
boundaries
b
o
u
n
d
a
r
i
e
s
is
i
s
a
a
software
s
o
f
t
w
a
r
e
modification
m
o
d
i
f
i
c
a
t
i
o
n
and
a
n
d
discussed
d
i
s
c
u
s
s
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
12.1.1.
1
2
.
1
.
1
.
For
F
o
r
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
a
a
modifiable
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
is
i
s
that
t
h
a
t
part
p
a
r
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
changed
c
h
a
n
g
e
d
by
b
y
the
t
h
e
user,
u
s
e
r
,
and
a
n
d
a
a
non-modifiable
n
o
n
-
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
is
i
s
that
t
h
a
t
which
w
h
i
c
h
is
i
s
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
changed
c
h
a
n
g
e
d
by
b
y
the
t
h
e
user.
u
s
e
r
.
Some
S
o
m
e
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
may
m
a
y
include
i
n
c
l
u
d
e
optional
o
p
t
i
o
n
a
l
functions
f
u
n
c
t
i
o
n
s
which
w
h
i
c
h
may
m
a
y
be
b
e
selected
s
e
l
e
c
t
e
d
by
b
y
software
s
o
f
t
w
a
r
e
programmed
p
r
o
g
r
a
m
m
e
d
options
o
p
t
i
o
n
s
rather
r
a
t
h
e
r
than
t
h
a
n
by
b
y
hardware
h
a
r
d
w
a
r
e
connector
c
o
n
n
e
c
t
o
r
pins.
p
i
n
s
.
The
T
h
e
option-selectable
o
p
t
i
o
n
-
s
e
l
e
c
t
a
b
l
e
software
s
o
f
t
w
a
r
e
functions
f
u
n
c
t
i
o
n
s
are
a
r
e
used
u
s
e
d
to
t
o
select
s
e
l
e
c
t
a
a
particular
p
a
r
t
i
c
u
l
a
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
within
w
i
t
h
i
n
the
t
h
e
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
See
S
e
e
paragraph
p
a
r
a
g
r
a
p
h
5.4.3
5
.
4
.
3
for
f
o
r
guidelines
g
u
i
d
e
l
i
n
e
s
on
o
n
deactivated
d
e
a
c
t
i
v
a
t
e
d
code.
c
o
d
e
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
system
s
y
s
t
e
m
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
option-selectable
o
p
t
i
o
n
-
s
e
l
e
c
t
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
and
a
n
d
commercial
c
o
m
m
e
r
c
i
a
l
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
software
s
o
f
t
w
a
r
e
includes:
i
n
c
l
u
d
e
s
:
-
User-modifiable
U
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
:
:
Users
U
s
e
r
s
may
m
a
y
modify
m
o
d
i
f
y
software
s
o
f
t
w
a
r
e
within
w
i
t
h
i
n
the
t
h
e
modification
m
o
d
i
f
i
c
a
t
i
o
n
constraints
c
o
n
s
t
r
a
i
n
t
s
without
w
i
t
h
o
u
t
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
review,
r
e
v
i
e
w
,
if
i
f
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
provide
p
r
o
v
i
d
e
for
f
o
r
user
u
s
e
r
modification.
m
o
d
i
f
i
c
a
t
i
o
n
.
-
The
T
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
specify
s
p
e
c
i
f
y
the
t
h
e
mechanisms
m
e
c
h
a
n
i
s
m
s
which
w
h
i
c
h
prevent
p
r
e
v
e
n
t
the
t
h
e
user
u
s
e
r
modification
m
o
d
i
f
i
c
a
t
i
o
n
from
f
r
o
m
affecting
a
f
f
e
c
t
i
n
g
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
whether
w
h
e
t
h
e
r
or
o
r
not
n
o
t
they
t
h
e
y
are
a
r
e
correctly
c
o
r
r
e
c
t
l
y
implemented.
i
m
p
l
e
m
e
n
t
e
d
.
The
T
h
e
software
s
o
f
t
w
a
r
e
which
w
h
i
c
h
provides
p
r
o
v
i
d
e
s
the
t
h
e
protection
p
r
o
t
e
c
t
i
o
n
for
f
o
r
user
u
s
e
r
modification
m
o
d
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
at
a
t
the
t
h
e
same
s
a
m
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
as
a
s
the
t
h
e
function
f
u
n
c
t
i
o
n
it
i
t
is
i
s
protecting
p
r
o
t
e
c
t
i
n
g
from
f
r
o
m
errors
e
r
r
o
r
s
in
i
n
the
t
h
e
modifiable
m
o
d
i
f
i
a
b
l
e
component.
c
o
m
p
o
n
e
n
t
.
-
If
I
f
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
do
d
o
not
n
o
t
include
i
n
c
l
u
d
e
provision
p
r
o
v
i
s
i
o
n
for
f
o
r
user
u
s
e
r
modification,
m
o
d
i
f
i
c
a
t
i
o
n
,
the
t
h
e
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
not
n
o
t
be
b
e
modified
m
o
d
i
f
i
e
d
by
b
y
the
t
h
e
user
u
s
e
r
unless
u
n
l
e
s
s
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
this
t
h
i
s
document
d
o
c
u
m
e
n
t
is
i
s
demonstrated
d
e
m
o
n
s
t
r
a
t
e
d
for
f
o
r
the
t
h
e
modification.
m
o
d
i
f
i
c
a
t
i
o
n
.
-
At
A
t
the
t
h
e
time
t
i
m
e
of
o
f
the
t
h
e
user
u
s
e
r
modification,
m
o
d
i
f
i
c
a
t
i
o
n
,
the
t
h
e
user
u
s
e
r
should
s
h
o
u
l
d
take
t
a
k
e
responsibility
r
e
s
p
o
n
s
i
b
i
l
i
t
y
for
f
o
r
all
a
l
l
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management,
m
a
n
a
g
e
m
e
n
t
,
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance,
a
s
s
u
r
a
n
c
e
,
and
a
n
d
software
s
o
f
t
w
a
r
e
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
-
Option-selectable
O
p
t
i
o
n
-
s
e
l
e
c
t
a
b
l
e
software:
s
o
f
t
w
a
r
e
:
When
W
h
e
n
software
s
o
f
t
w
a
r
e
programmed
p
r
o
g
r
a
m
m
e
d
options
o
p
t
i
o
n
s
are
a
r
e
included,
i
n
c
l
u
d
e
d
,
means
m
e
a
n
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
inadvertent
i
n
a
d
v
e
r
t
e
n
t
selections
s
e
l
e
c
t
i
o
n
s
involving
i
n
v
o
l
v
i
n
g
non-approved
n
o
n
-
a
p
p
r
o
v
e
d
configurations
c
o
n
f
i
g
u
r
a
t
i
o
n
s
for
f
o
r
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
within
w
i
t
h
i
n
the
t
h
e
installation
i
n
s
t
a
l
l
a
t
i
o
n
environment
e
n
v
i
r
o
n
m
e
n
t
cannot
c
a
n
n
o
t
be
b
e
made.
m
a
d
e
.
-
Commercial
C
o
m
m
e
r
c
i
a
l
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
software:
s
o
f
t
w
a
r
e
:
COTS
C
O
T
S
software
s
o
f
t
w
a
r
e
included
i
n
c
l
u
d
e
d
in
i
n
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
or
o
r
equipment
e
q
u
i
p
m
e
n
t
should
s
h
o
u
l
d
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
If
I
f
deficiencies
d
e
f
i
c
i
e
n
c
i
e
s
exist
e
x
i
s
t
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
of
o
f
COTS
C
O
T
S
software,
s
o
f
t
w
a
r
e
,
the
t
h
e
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
augmented
a
u
g
m
e
n
t
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
The
T
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
in
i
n
paragraphs
p
a
r
a
g
r
a
p
h
s
12.14,
1
2
.
1
4
,
Upgrading
U
p
g
r
a
d
i
n
g
A
A
Development
D
e
v
e
l
o
p
m
e
n
t
Baseline,
B
a
s
e
l
i
n
e
,
and
a
n
d
12.3.5,
1
2
.
3
.
5
,
Product
P
r
o
d
u
c
t
Service
S
e
r
v
i
c
e
History,
H
i
s
t
o
r
y
,
may
m
a
y
be
b
e
relevant
r
e
l
e
v
a
n
t
in
i
n
this
t
h
i
s
instance.
i
n
s
t
a
n
c
e
.
2.5
2
.
5
System
S
y
s
t
e
m
Design
D
e
s
i
g
n
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
Field-Loadable
F
i
e
l
d
-
L
o
a
d
a
b
l
e
Software
S
o
f
t
w
a
r
e
Field-loadable
F
i
e
l
d
-
l
o
a
d
a
b
l
e
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
refers
r
e
f
e
r
s
to
t
o
software
s
o
f
t
w
a
r
e
or
o
r
data
d
a
t
a
tables
t
a
b
l
e
s
that
t
h
a
t
can
c
a
n
be
b
e
loaded
l
o
a
d
e
d
without
w
i
t
h
o
u
t
removing
r
e
m
o
v
i
n
g
the
t
h
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
from
f
r
o
m
its
i
t
s
installation.
i
n
s
t
a
l
l
a
t
i
o
n
.
The
T
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
associated
a
s
s
o
c
i
a
t
e
d
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
11
1
1
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
data
d
a
t
a
loading
l
o
a
d
i
n
g
function
f
u
n
c
t
i
o
n
are
a
r
e
part
p
a
r
t
of
o
f
the
t
h
e
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
If
I
f
the
t
h
e
inadvertent
i
n
a
d
v
e
r
t
e
n
t
enabling
e
n
a
b
l
i
n
g
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
data
d
a
t
a
loading
l
o
a
d
i
n
g
function
f
u
n
c
t
i
o
n
could
c
o
u
l
d
induce
i
n
d
u
c
e
a
a
system
s
y
s
t
e
m
failure
f
a
i
l
u
r
e
condition,
c
o
n
d
i
t
i
o
n
,
a
a
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirement
r
e
q
u
i
r
e
m
e
n
t
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
data
d
a
t
a
loading
l
o
a
d
i
n
g
function
f
u
n
c
t
i
o
n
is
i
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
System
S
y
s
t
e
m
safety
s
a
f
e
t
y
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
relating
r
e
l
a
t
i
n
g
to
t
o
field-loadable
f
i
e
l
d
-
l
o
a
d
a
b
l
e
software
s
o
f
t
w
a
r
e
include:
i
n
c
l
u
d
e
:
-
Detection
D
e
t
e
c
t
i
o
n
of
o
f
corrupted
c
o
r
r
u
p
t
e
d
or
o
r
partially
p
a
r
t
i
a
l
l
y
loaded
l
o
a
d
e
d
software.
s
o
f
t
w
a
r
e
.
-
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
of
o
f
the
t
h
e
effects
e
f
f
e
c
t
s
of
o
f
loading
l
o
a
d
i
n
g
the
t
h
e
inappropriate
i
n
a
p
p
r
o
p
r
i
a
t
e
software.
s
o
f
t
w
a
r
e
.
-
Hardware/software
H
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
compatibility.
c
o
m
p
a
t
i
b
i
l
i
t
y
.
-
Software/software
S
o
f
t
w
a
r
e
/
s
o
f
t
w
a
r
e
compatibility.
c
o
m
p
a
t
i
b
i
l
i
t
y
.
-
Aircraft/software
A
i
r
c
r
a
f
t
/
s
o
f
t
w
a
r
e
compatibility.
c
o
m
p
a
t
i
b
i
l
i
t
y
.
-
Inadvertent
I
n
a
d
v
e
r
t
e
n
t
enabling
e
n
a
b
l
i
n
g
of
o
f
the
t
h
e
field
f
i
e
l
d
loading
l
o
a
d
i
n
g
function.
f
u
n
c
t
i
o
n
.
-
Loss
L
o
s
s
or
o
r
corruption
c
o
r
r
u
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
display.
d
i
s
p
l
a
y
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
field-loadable
f
i
e
l
d
-
l
o
a
d
a
b
l
e
software
s
o
f
t
w
a
r
e
includes:
i
n
c
l
u
d
e
s
:
-
Unless
U
n
l
e
s
s
otherwise
o
t
h
e
r
w
i
s
e
justified
j
u
s
t
i
f
i
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
the
t
h
e
detection
d
e
t
e
c
t
i
o
n
mechanism
m
e
c
h
a
n
i
s
m
for
f
o
r
partial
p
a
r
t
i
a
l
or
o
r
corrupted
c
o
r
r
u
p
t
e
d
software
s
o
f
t
w
a
r
e
loads
l
o
a
d
s
should
s
h
o
u
l
d
be
b
e
assigned
a
s
s
i
g
n
e
d
the
t
h
e
same
s
a
m
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
or
o
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
as
a
s
the
t
h
e
most
m
o
s
t
severe
s
e
v
e
r
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
or
o
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
function
f
u
n
c
t
i
o
n
that
t
h
a
t
uses
u
s
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
load.
l
o
a
d
.
-
If
I
f
a
a
system
s
y
s
t
e
m
has
h
a
s
a
a
default
d
e
f
a
u
l
t
mode
m
o
d
e
when
w
h
e
n
inappropriate
i
n
a
p
p
r
o
p
r
i
a
t
e
software
s
o
f
t
w
a
r
e
or
o
r
data
d
a
t
a
is
i
s
loaded,
l
o
a
d
e
d
,
then
t
h
e
n
each
e
a
c
h
partitioned
p
a
r
t
i
t
i
o
n
e
d
component
c
o
m
p
o
n
e
n
t
of
o
f
the
t
h
e
system
s
y
s
t
e
m
should
s
h
o
u
l
d
have
h
a
v
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
specified
s
p
e
c
i
f
i
e
d
for
f
o
r
operation
o
p
e
r
a
t
i
o
n
in
i
n
this
t
h
i
s
mode
m
o
d
e
which
w
h
i
c
h
address
a
d
d
r
e
s
s
the
t
h
e
potential
p
o
t
e
n
t
i
a
l
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
loading
l
o
a
d
i
n
g
function,
f
u
n
c
t
i
o
n
,
including
i
n
c
l
u
d
i
n
g
support
s
u
p
p
o
r
t
systems
s
y
s
t
e
m
s
and
a
n
d
procedures,
p
r
o
c
e
d
u
r
e
s
,
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
a
a
means
m
e
a
n
s
to
t
o
detect
d
e
t
e
c
t
incorrect
i
n
c
o
r
r
e
c
t
software
s
o
f
t
w
a
r
e
and/or
a
n
d
/
o
r
hardware
h
a
r
d
w
a
r
e
and/or
a
n
d
/
o
r
aircraft
a
i
r
c
r
a
f
t
combinations
c
o
m
b
i
n
a
t
i
o
n
s
and
a
n
d
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
protection
p
r
o
t
e
c
t
i
o
n
appropriate
a
p
p
r
o
p
r
i
a
t
e
to
t
o
the
t
h
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
of
o
f
the
t
h
e
function.
f
u
n
c
t
i
o
n
.
-
If
I
f
software
s
o
f
t
w
a
r
e
is
i
s
part
p
a
r
t
of
o
f
an
a
n
airborne
a
i
r
b
o
r
n
e
display
d
i
s
p
l
a
y
mechanism
m
e
c
h
a
n
i
s
m
that
t
h
a
t
is
i
s
the
t
h
e
means
m
e
a
n
s
for
f
o
r
ensuring
e
n
s
u
r
i
n
g
that
t
h
a
t
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
conforms
c
o
n
f
o
r
m
s
to
t
o
a
a
certified
c
e
r
t
i
f
i
e
d
configuration,
c
o
n
f
i
g
u
r
a
t
i
o
n
,
then
t
h
e
n
that
t
h
a
t
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
either
e
i
t
h
e
r
be
b
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
the
t
h
e
highest
h
i
g
h
e
s
t
level
l
e
v
e
l
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
to
t
o
be
b
e
loaded,
l
o
a
d
e
d
,
or
o
r
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
justify
j
u
s
t
i
f
y
the
t
h
e
integrity
i
n
t
e
g
r
i
t
y
of
o
f
an
a
n
end-to-end
e
n
d
-
t
o
-
e
n
d
check
c
h
e
c
k
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification.
i
d
e
n
t
i
f
i
c
a
t
i
o
n
.
2.6
2
.
6
System
S
y
s
t
e
m
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
The
T
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
from
f
r
o
m
the
t
h
e
system
s
y
s
t
e
m
operational
o
p
e
r
a
t
i
o
n
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
result
r
e
s
u
l
t
from
f
r
o
m
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
include:
i
n
c
l
u
d
e
:
-
The
T
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
for
f
o
r
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
establish
e
s
t
a
b
l
i
s
h
two
t
w
o
characteristics
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
of
o
f
the
t
h
e
software:
s
o
f
t
w
a
r
e
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
performs
p
e
r
f
o
r
m
s
specified
s
p
e
c
i
f
i
e
d
functions
f
u
n
c
t
i
o
n
s
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
does
d
o
e
s
not
n
o
t
exhibit
e
x
h
i
b
i
t
specific
s
p
e
c
i
f
i
c
anomalous
a
n
o
m
a
l
o
u
s
behavior(s)
b
e
h
a
v
i
o
r
(
s
)
as
a
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
Additional
A
d
d
i
t
i
o
n
a
l
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
generated
g
e
n
e
r
a
t
e
d
to
t
o
eliminate
e
l
i
m
i
n
a
t
e
the
t
h
e
anomalous
a
n
o
m
a
l
o
u
s
behavior.
b
e
h
a
v
i
o
r
.
-
These
T
h
e
s
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
then
t
h
e
n
be
b
e
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
are
a
r
e
verified
v
e
r
i
f
i
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
2.7
2
.
7
Software
S
o
f
t
w
a
r
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
System
S
y
s
t
e
m
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
system
s
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
is
i
s
beyond
b
e
y
o
n
d
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
However,
H
o
w
e
v
e
r
,
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
aid
a
i
d
and
a
n
d
interact
i
n
t
e
r
a
c
t
with
w
i
t
h
the
t
h
e
system
s
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
Software
S
o
f
t
w
a
r
e
design
d
e
s
i
g
n
details
d
e
t
a
i
l
s
that
t
h
a
t
relate
r
e
l
a
t
e
to
t
o
the
t
h
e
system
s
y
s
t
e
m
functionality
f
u
n
c
t
i
o
n
a
l
i
t
y
need
n
e
e
d
to
t
o
be
b
e
made
m
a
d
e
available
a
v
a
i
l
a
b
l
e
to
t
o
aid
a
i
d
system
s
y
s
t
e
m
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
System
S
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
may
m
a
y
provide
p
r
o
v
i
d
e
significant
s
i
g
n
i
f
i
c
a
n
t
coverage
c
o
v
e
r
a
g
e
of
o
f
code
c
o
d
e
structure.
s
t
r
u
c
t
u
r
e
.
Coverage
C
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
of
o
f
system
s
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
tests
t
e
s
t
s
may
m
a
y
be
b
e
used
u
s
e
d
to
t
o
achieve
a
c
h
i
e
v
e
the
t
h
e
coverage
c
o
v
e
r
a
g
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
various
v
a
r
i
o
u
s
test
t
e
s
t
activities
a
c
t
i
v
i
t
i
e
s
described
d
e
s
c
r
i
b
e
d
under
u
n
d
e
r
software
s
o
f
t
w
a
r
e
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
3
3
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYLCE
C
Y
L
C
E
13
1
3
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
definition,
d
e
f
i
n
i
t
i
o
n
,
and
a
n
d
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
The
T
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
do
d
o
not
n
o
t
prescribe
p
r
e
s
c
r
i
b
e
a
a
preferred
p
r
e
f
e
r
r
e
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycles
c
y
c
l
e
s
and
a
n
d
interactions
i
n
t
e
r
a
c
t
i
o
n
s
between
b
e
t
w
e
e
n
them.
t
h
e
m
.
The
T
h
e
separation
s
e
p
a
r
a
t
i
o
n
of
o
f
the
t
h
e
processes
p
r
o
c
e
s
s
e
s
is
i
s
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
imply
i
m
p
l
y
a
a
structure
s
t
r
u
c
t
u
r
e
for
f
o
r
the
t
h
e
organization
o
r
g
a
n
i
z
a
t
i
o
n
(s)
(
s
)
that
t
h
a
t
perform
p
e
r
f
o
r
m
them,
t
h
e
m
,
For
F
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
(s)
(
s
)
is
i
s
constructed
c
o
n
s
t
r
u
c
t
e
d
that
t
h
a
t
includes
i
n
c
l
u
d
e
s
these
t
h
e
s
e
processes.
p
r
o
c
e
s
s
e
s
.
3.1
3
.
1
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Processes
P
r
o
c
e
s
s
e
s
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
are:
a
r
e
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
that
t
h
a
t
defines
d
e
f
i
n
e
s
and
a
n
d
coordinates
c
o
o
r
d
i
n
a
t
e
s
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
a
a
project.
p
r
o
j
e
c
t
.
Section
S
e
c
t
i
o
n
4
4
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
that
t
h
a
t
produce
p
r
o
d
u
c
e
the
t
h
e
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
These
T
h
e
s
e
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process,
p
r
o
c
e
s
s
,
and
a
n
d
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
Section
S
e
c
t
i
o
n
5
5
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
-
The
T
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
that
t
h
a
t
ensure
e
n
s
u
r
e
the
t
h
e
correctness,
c
o
r
r
e
c
t
n
e
s
s
,
control,
c
o
n
t
r
o
l
,
and
a
n
d
confidence
c
o
n
f
i
d
e
n
c
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
their
t
h
e
i
r
outputs.
o
u
t
p
u
t
s
.
The
T
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process,
p
r
o
c
e
s
s
,
and
a
n
d
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process.
p
r
o
c
e
s
s
.
It
I
t
is
i
s
important
i
m
p
o
r
t
a
n
t
to
t
o
understand
u
n
d
e
r
s
t
a
n
d
that
t
h
a
t
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
performed
p
e
r
f
o
r
m
e
d
concurrently
c
o
n
c
u
r
r
e
n
t
l
y
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
Sections
S
e
c
t
i
o
n
s
6
6
through
t
h
r
o
u
g
h
9
9
describe
d
e
s
c
r
i
b
e
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes.
p
r
o
c
e
s
s
e
s
.
3.2
3
.
2
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Definition
D
e
f
i
n
i
t
i
o
n
A
A
project
p
r
o
j
e
c
t
defines
d
e
f
i
n
e
s
one
o
n
e
or
o
r
more
m
o
r
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
(s)
(
s
)
by
b
y
choosing
c
h
o
o
s
i
n
g
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
for
f
o
r
each
e
a
c
h
process,
p
r
o
c
e
s
s
,
specifying
s
p
e
c
i
f
y
i
n
g
a
a
sequence
s
e
q
u
e
n
c
e
for
f
o
r
the
t
h
e
activities,
a
c
t
i
v
i
t
i
e
s
,
and
a
n
d
assigning
a
s
s
i
g
n
i
n
g
responsibilities
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
for
f
o
r
the
t
h
e
activities.
a
c
t
i
v
i
t
i
e
s
.
For
F
o
r
a
a
specific
s
p
e
c
i
f
i
c
project,
p
r
o
j
e
c
t
,
the
t
h
e
sequencing
s
e
q
u
e
n
c
i
n
g
of
o
f
these
t
h
e
s
e
processes
p
r
o
c
e
s
s
e
s
is
i
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
attributes
a
t
t
r
i
b
u
t
e
s
of
o
f
the
t
h
e
project,
p
r
o
j
e
c
t
,
such
s
u
c
h
as
a
s
system
s
y
s
t
e
m
functionality
f
u
n
c
t
i
o
n
a
l
i
t
y
and
a
n
d
complexity,
c
o
m
p
l
e
x
i
t
y
,
software
s
o
f
t
w
a
r
e
size
s
i
z
e
and
a
n
d
complexity,
c
o
m
p
l
e
x
i
t
y
,
requirements
r
e
q
u
i
r
e
m
e
n
t
s
stability,
s
t
a
b
i
l
i
t
y
,
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
results,
r
e
s
u
l
t
s
,
development
d
e
v
e
l
o
p
m
e
n
t
strategies
s
t
r
a
t
e
g
i
e
s
and
a
n
d
hardware
h
a
r
d
w
a
r
e
availability.
a
v
a
i
l
a
b
i
l
i
t
y
.
The
T
h
e
usual
u
s
u
a
l
sequence
s
e
q
u
e
n
c
e
through
t
h
r
o
u
g
h
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
is
i
s
require
r
e
q
u
i
r
e
ments,
m
e
n
t
s
,
design,
d
e
s
i
g
n
,
coding
c
o
d
i
n
g
and
a
n
d
integration.
i
n
t
e
g
r
a
t
i
o
n
.
Figure
F
i
g
u
r
e
3-1
3
-
1
illustrates
i
l
l
u
s
t
r
a
t
e
s
the
t
h
e
sequence
s
e
q
u
e
n
c
e
of
o
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
several
s
e
v
e
r
a
l
components
c
o
m
p
o
n
e
n
t
s
of
o
f
a
a
single
s
i
n
g
l
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
with
w
i
t
h
different
d
i
f
f
e
r
e
n
t
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycles.
c
y
c
l
e
s
.
Component
C
o
m
p
o
n
e
n
t
W
W
implements
i
m
p
l
e
m
e
n
t
s
a
a
set
s
e
t
of
o
f
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
by
b
y
developing
d
e
v
e
l
o
p
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
using
u
s
i
n
g
those
t
h
o
s
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
define
d
e
f
i
n
e
a
a
software
s
o
f
t
w
a
r
e
design,
d
e
s
i
g
n
,
implementing
i
m
p
l
e
m
e
n
t
i
n
g
that
t
h
a
t
design
d
e
s
i
g
n
into
i
n
t
o
source
s
o
u
r
c
e
code,
c
o
d
e
,
and
a
n
d
then
t
h
e
n
integrating
i
n
t
e
g
r
a
t
i
n
g
the
t
h
e
component
c
o
m
p
o
n
e
n
t
into
i
n
t
o
the
t
h
e
hardware.
h
a
r
d
w
a
r
e
.
Component
C
o
m
p
o
n
e
n
t
X
X
illustrates
i
l
l
u
s
t
r
a
t
e
s
the
t
h
e
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
used
u
s
e
d
in
i
n
a
a
certified
c
e
r
t
i
f
i
e
d
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine.
e
n
g
i
n
e
.
Component
C
o
m
p
o
n
e
n
t
Y
Y
illustrates
i
l
l
u
s
t
r
a
t
e
s
the
t
h
e
use
u
s
e
of
o
f
a
a
simple,
s
i
m
p
l
e
,
partitioned
p
a
r
t
i
t
i
o
n
e
d
function
f
u
n
c
t
i
o
n
that
t
h
a
t
can
c
a
n
be
b
e
coded
c
o
d
e
d
directly
d
i
r
e
c
t
l
y
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Component
C
o
m
p
o
n
e
n
t
Z
Z
illustrates
i
l
l
u
s
t
r
a
t
e
s
the
t
h
e
use
u
s
e
of
o
f
a
a
prototyping
p
r
o
t
o
t
y
p
i
n
g
strategy.
s
t
r
a
t
e
g
y
.
Usually,
U
s
u
a
l
l
y
,
the
t
h
e
goals
g
o
a
l
s
of
o
f
prototyping
p
r
o
t
o
t
y
p
i
n
g
are
a
r
e
to
t
o
better
b
e
t
t
e
r
understand
u
n
d
e
r
s
t
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
to
t
o
mitigate
m
i
t
i
g
a
t
e
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
technical
t
e
c
h
n
i
c
a
l
risks.
r
i
s
k
s
.
The
T
h
e
initial
i
n
i
t
i
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
used
u
s
e
d
as
a
s
the
t
h
e
basis
b
a
s
i
s
to
t
o
implement
i
m
p
l
e
m
e
n
t
a
a
prototype.
p
r
o
t
o
t
y
p
e
.
This
T
h
i
s
prototype
p
r
o
t
o
t
y
p
e
is
i
s
evaluated
e
v
a
l
u
a
t
e
d
in
i
n
an
a
n
environment
e
n
v
i
r
o
n
m
e
n
t
representative
r
e
p
r
e
s
e
n
t
a
t
i
v
e
of
o
f
the
t
h
e
intended
i
n
t
e
n
d
e
d
use
u
s
e
of
o
f
the
t
h
e
system
s
y
s
t
e
m
under
u
n
d
e
r
development.
d
e
v
e
l
o
p
m
e
n
t
.
Results
R
e
s
u
l
t
s
of
o
f
the
t
h
e
evaluation
e
v
a
l
u
a
t
i
o
n
are
a
r
e
used
u
s
e
d
to
t
o
refine
r
e
f
i
n
e
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
processes
p
r
o
c
e
s
s
e
s
of
o
f
a
a
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
may
m
a
y
be
b
e
iterative,
i
t
e
r
a
t
i
v
e
,
that
t
h
a
t
is,
i
s
,
entered
e
n
t
e
r
e
d
and
a
n
d
re-entered.
r
e
-
e
n
t
e
r
e
d
.
The
T
h
e
timing
t
i
m
i
n
g
and
a
n
d
degree
d
e
g
r
e
e
of
o
f
iteration
i
t
e
r
a
t
i
o
n
varies
v
a
r
i
e
s
due
d
u
e
to
t
o
the
t
h
e
incremental
i
n
c
r
e
m
e
n
t
a
l
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
system
s
y
s
t
e
m
functions,
f
u
n
c
t
i
o
n
s
,
complexity,
c
o
m
p
l
e
x
i
t
y
,
requirements
r
e
q
u
i
r
e
m
e
n
t
s
development,
d
e
v
e
l
o
p
m
e
n
t
,
hardware
h
a
r
d
w
a
r
e
availability,
a
v
a
i
l
a
b
i
l
i
t
y
,
feedback
f
e
e
d
b
a
c
k
to
t
o
previous
p
r
e
v
i
o
u
s
processes,
p
r
o
c
e
s
s
e
s
,
and
a
n
d
other
o
t
h
e
r
attributes
a
t
t
r
i
b
u
t
e
s
of
o
f
the
t
h
e
project.
p
r
o
j
e
c
t
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
14
1
4
The
T
h
e
various
v
a
r
i
o
u
s
parts
p
a
r
t
s
of
o
f
the
t
h
e
s
s
elected
e
l
e
c
t
e
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
are
a
r
e
tied
t
i
e
d
together
t
o
g
e
t
h
e
r
with
w
i
t
h
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
incremental
i
n
c
r
e
m
e
n
t
a
l
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
and
a
n
d
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
FIGURE
F
I
G
U
R
E
3-1
3
-
1
EXAMPLE
E
X
A
M
P
L
E
OF
O
F
A
A
SOFTWARE
S
O
F
T
W
A
R
E
PROJECT
P
R
O
J
E
C
T
USING
U
S
I
N
G
FOUR
F
O
U
R
DIFFERENT
D
I
F
F
E
R
E
N
T
DEVELOPMENT
D
E
V
E
L
O
P
M
E
N
T
SEQUENCES
S
E
Q
U
E
N
C
E
S
3.3
3
.
3
Transition
T
r
a
n
s
i
t
i
o
n
Criteria
C
r
i
t
e
r
i
a
Between
B
e
t
w
e
e
n
Processes
P
r
o
c
e
s
s
e
s
Transition
T
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
are
a
r
e
used
u
s
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
whether
w
h
e
t
h
e
r
a
a
process
p
r
o
c
e
s
s
may
m
a
y
be
b
e
entered
e
n
t
e
r
e
d
or
o
r
re-entered.
r
e
-
e
n
t
e
r
e
d
.
Each
E
a
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
performs
p
e
r
f
o
r
m
s
activities
a
c
t
i
v
i
t
i
e
s
on
o
n
inputs
i
n
p
u
t
s
to
t
o
produce
p
r
o
d
u
c
e
outputs.
o
u
t
p
u
t
s
.
A
A
process
p
r
o
c
e
s
s
may
m
a
y
produce
p
r
o
d
u
c
e
feedback
f
e
e
d
b
a
c
k
to
t
o
other
o
t
h
e
r
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
receive
r
e
c
e
i
v
e
feedback
f
e
e
d
b
a
c
k
from
f
r
o
m
others.
o
t
h
e
r
s
.
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
feedback
f
e
e
d
b
a
c
k
includes
i
n
c
l
u
d
e
s
how
h
o
w
information
i
n
f
o
r
m
a
t
i
o
n
is
i
s
recognized,
r
e
c
o
g
n
i
z
e
d
,
controlled
c
o
n
t
r
o
l
l
e
d
and
a
n
d
resolved
r
e
s
o
l
v
e
d
by
b
y
the
t
h
e
receiving
r
e
c
e
i
v
i
n
g
process.
p
r
o
c
e
s
s
.
An
A
n
example
e
x
a
m
p
l
e
of
o
f
a
a
feedback
f
e
e
d
b
a
c
k
definition
d
e
f
i
n
i
t
i
o
n
is
i
s
problem
p
r
o
b
l
e
m
reporting.
r
e
p
o
r
t
i
n
g
.
The
T
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
will
w
i
l
l
depend
d
e
p
e
n
d
on
o
n
the
t
h
e
planned
p
l
a
n
n
e
d
sequence
s
e
q
u
e
n
c
e
of
o
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes,
p
r
o
c
e
s
s
e
s
,
and
a
n
d
may
m
a
y
be
b
e
affected
a
f
f
e
c
t
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
Examples
E
x
a
m
p
l
e
s
of
o
f
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
which
w
h
i
c
h
may
m
a
y
be
b
e
chosen
c
h
o
s
e
n
are:
a
r
e
:
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
reviews
r
e
v
i
e
w
s
have
h
a
v
e
been
b
e
e
n
performed;
p
e
r
f
o
r
m
e
d
;
the
t
h
e
input
i
n
p
u
t
is
i
s
an
a
n
identified
i
d
e
n
t
i
f
i
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item;
i
t
e
m
;
and
a
n
d
a
a
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analysis
a
n
a
l
y
s
i
s
has
h
a
s
been
b
e
e
n
completed
c
o
m
p
l
e
t
e
d
for
f
o
r
the
t
h
e
input.
i
n
p
u
t
.
Every
E
v
e
r
y
input
i
n
p
u
t
to
t
o
a
a
process
p
r
o
c
e
s
s
need
n
e
e
d
not
n
o
t
be
b
e
complete
c
o
m
p
l
e
t
e
before
b
e
f
o
r
e
that
t
h
a
t
process
p
r
o
c
e
s
s
can
c
a
n
be
b
e
initiated,
i
n
i
t
i
a
t
e
d
,
if
i
f
the
t
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
the
t
h
e
process
p
r
o
c
e
s
s
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
If
I
f
a
a
process
p
r
o
c
e
s
s
acts
a
c
t
s
on
o
n
partial
p
a
r
t
i
a
l
inputs,
i
n
p
u
t
s
,
subsequent
s
u
b
s
e
q
u
e
n
t
inputs
i
n
p
u
t
s
to
t
o
the
t
h
e
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
examined
e
x
a
m
i
n
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
that
t
h
a
t
the
t
h
e
previous
p
r
e
v
i
o
u
s
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
still
s
t
i
l
l
valid.
v
a
l
i
d
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
15
1
5
4
4
SOFTWARE
S
O
F
T
W
A
R
E
PLANNING
P
L
A
N
N
I
N
G
PROCESS
P
R
O
C
E
S
S
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
This
T
h
i
s
process
p
r
o
c
e
s
s
produces
p
r
o
d
u
c
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards
s
t
a
n
d
a
r
d
s
that
t
h
a
t
direct
d
i
r
e
c
t
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes.
p
r
o
c
e
s
s
e
s
.
Table
T
a
b
l
e
A-1
A
-
1
of
o
f
Annex
A
n
n
e
x
A
A
is
i
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
4.1
4
.
1
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
means
m
e
a
n
s
of
o
f
producing
p
r
o
d
u
c
i
n
g
software
s
o
f
t
w
a
r
e
which
w
h
i
c
h
will
w
i
l
l
satisfy
s
a
t
i
s
f
y
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
provide
p
r
o
v
i
d
e
the
t
h
e
level
l
e
v
e
l
of
o
f
confidence
c
o
n
f
i
d
e
n
c
e
which
w
h
i
c
h
is
i
s
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
are:
a
r
e
:
-
The
T
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
that
t
h
a
t
will
w
i
l
l
address
a
d
d
r
e
s
s
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
are
a
r
e
defined
d
e
f
i
n
e
d
(subsection
(
s
u
b
s
e
c
t
i
o
n
4.2).
4
.
2
)
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle(s),
c
y
c
l
e
(
s
)
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
inter-relationships
i
n
t
e
r
-
r
e
l
a
t
i
o
n
s
h
i
p
s
between
b
e
t
w
e
e
n
the
t
h
e
processes,
p
r
o
c
e
s
s
e
s
,
their
t
h
e
i
r
sequencing,
s
e
q
u
e
n
c
i
n
g
,
feedback
f
e
e
d
b
a
c
k
mechanisms,
m
e
c
h
a
n
i
s
m
s
,
and
a
n
d
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
are
a
r
e
determined
d
e
t
e
r
m
i
n
e
d
(section
(
s
e
c
t
i
o
n
3).
3
)
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment,
e
n
v
i
r
o
n
m
e
n
t
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
methods
m
e
t
h
o
d
s
and
a
n
d
tools
t
o
o
l
s
to
t
o
be
b
e
used
u
s
e
d
for
f
o
r
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
each
e
a
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
have
h
a
v
e
been
b
e
e
n
selected
s
e
l
e
c
t
e
d
(subsection
(
s
u
b
s
e
c
t
i
o
n
4.4).
4
.
4
)
.
-
Additional
A
d
d
i
t
i
o
n
a
l
considerations,
c
o
n
s
i
d
e
r
a
t
i
o
n
s
,
such
s
u
c
h
as
a
s
those
t
h
o
s
e
discussed
d
i
s
c
u
s
s
e
d
in
i
n
section
s
e
c
t
i
o
n
12,
1
2
,
have
h
a
v
e
been
b
e
e
n
addressed,
a
d
d
r
e
s
s
e
d
,
if
i
f
necessary.
n
e
c
e
s
s
a
r
y
.
-
Software
S
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
to
t
o
be
b
e
produced
p
r
o
d
u
c
e
d
are
a
r
e
defined
d
e
f
i
n
e
d
(subsection
(
s
u
b
s
e
c
t
i
o
n
4.5).
4
.
5
)
.
-
Software
S
o
f
t
w
a
r
e
plans
p
l
a
n
s
that
t
h
a
t
comply
c
o
m
p
l
y
with
w
i
t
h
subsection
s
u
b
s
e
c
t
i
o
n
4.3
4
.
3
and
a
n
d
section
s
e
c
t
i
o
n
11
1
1
have
h
a
v
e
been
b
e
e
n
produced.
p
r
o
d
u
c
e
d
.
-
Development
D
e
v
e
l
o
p
m
e
n
t
and
a
n
d
revision
r
e
v
i
s
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
are
a
r
e
coordinated
c
o
o
r
d
i
n
a
t
e
d
(subsection
(
s
u
b
s
e
c
t
i
o
n
4.3).
4
.
3
)
.
4.2
4
.
2
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
Effective
E
f
f
e
c
t
i
v
e
planning
p
l
a
n
n
i
n
g
is
i
s
a
a
determining
d
e
t
e
r
m
i
n
i
n
g
factor
f
a
c
t
o
r
in
i
n
producing
p
r
o
d
u
c
i
n
g
software
s
o
f
t
w
a
r
e
that
t
h
a
t
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
at
a
t
a
a
point
p
o
i
n
t
in
i
n
time
t
i
m
e
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
that
t
h
a
t
provides
p
r
o
v
i
d
e
s
timely
t
i
m
e
l
y
direction
d
i
r
e
c
t
i
o
n
to
t
o
the
t
h
e
personnel
p
e
r
s
o
n
n
e
l
performing
p
e
r
f
o
r
m
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes.
p
r
o
c
e
s
s
e
s
.
See
S
e
e
also
a
l
s
o
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
subsection
s
u
b
s
e
c
t
i
o
n
9.
9
.
I.
I
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
to
t
o
be
b
e
used
u
s
e
d
for
f
o
r
the
t
h
e
project
p
r
o
j
e
c
t
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
or
o
r
selected.
s
e
l
e
c
t
e
d
.
-
Methods
M
e
t
h
o
d
s
and
a
n
d
tools
t
o
o
l
s
should
s
h
o
u
l
d
be
b
e
chosen
c
h
o
s
e
n
that
t
h
a
t
provide
p
r
o
v
i
d
e
error
e
r
r
o
r
prevention
p
r
e
v
e
n
t
i
o
n
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
coordination
c
o
o
r
d
i
n
a
t
i
o
n
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
to
t
o
provide
p
r
o
v
i
d
e
consistency
c
o
n
s
i
s
t
e
n
c
y
among
a
m
o
n
g
strategies
s
t
r
a
t
e
g
i
e
s
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
a
a
means
m
e
a
n
s
to
t
o
revise
r
e
v
i
s
e
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
as
a
s
a
a
project
p
r
o
j
e
c
t
progresses.
p
r
o
g
r
e
s
s
e
s
.
-
When
W
h
e
n
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
is
i
s
used
u
s
e
d
in
i
n
a
a
system,
s
y
s
t
e
m
,
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
choose
c
h
o
o
s
e
the
t
h
e
methods
m
e
t
h
o
d
s
and
a
n
d
tools
t
o
o
l
s
to
t
o
achieve
a
c
h
i
e
v
e
the
t
h
e
error
e
r
r
o
r
avoidance
a
v
o
i
d
a
n
c
e
or
o
r
detection
d
e
t
e
c
t
i
o
n
necessary
n
e
c
e
s
s
a
r
y
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
For
F
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
to
t
o
be
b
e
complete,
c
o
m
p
l
e
t
e
,
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
be
b
e
under
u
n
d
e
r
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
and
a
n
d
reviews
r
e
v
i
e
w
s
of
o
f
them
t
h
e
m
completed
c
o
m
p
l
e
t
e
d
(subsection
(
s
u
b
s
e
c
t
i
o
n
4.6).
4
.
6
)
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
16
1
6
4.3
4
.
3
Software
S
o
f
t
w
a
r
e
Plans
P
l
a
n
s
-
If
I
f
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
is
i
s
planned
p
l
a
n
n
e
d
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.4),
2
.
4
)
,
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
describe
d
e
s
c
r
i
b
e
how
h
o
w
the
t
h
e
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
(selected
(
s
e
l
e
c
t
e
d
options,
o
p
t
i
o
n
s
,
flight
f
l
i
g
h
t
test)
t
e
s
t
)
will
w
i
l
l
be
b
e
defined,
d
e
f
i
n
e
d
,
verified
v
e
r
i
f
i
e
d
and
a
n
d
handled
h
a
n
d
l
e
d
to
t
o
achieve
a
c
h
i
e
v
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
If
I
f
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
code
c
o
d
e
is
i
s
planned,
p
l
a
n
n
e
d
,
the
t
h
e
process,
p
r
o
c
e
s
s
,
tools,
t
o
o
l
s
,
environment,
e
n
v
i
r
o
n
m
e
n
t
,
and
a
n
d
data
d
a
t
a
items
i
t
e
m
s
substantiating
s
u
b
s
t
a
n
t
i
a
t
i
n
g
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
paragraph
p
a
r
a
g
r
a
p
h
5.2.3
5
.
2
.
3
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards.
s
t
a
n
d
a
r
d
s
.
Other
O
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
may
m
a
y
begin
b
e
g
i
n
before
b
e
f
o
r
e
completion
c
o
m
p
l
e
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
if
i
f
the
t
h
e
plans
p
l
a
n
s
and
a
n
d
procedures
p
r
o
c
e
d
u
r
e
s
for
f
o
r
the
t
h
e
specific
s
p
e
c
i
f
i
c
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
are
a
r
e
available.
a
v
a
i
l
a
b
l
e
.
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
means
m
e
a
n
s
of
o
f
satisfying
s
a
t
i
s
f
y
i
n
g
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
They
T
h
e
y
specify
s
p
e
c
i
f
y
the
t
h
e
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
that
t
h
a
t
will
w
i
l
l
perform
p
e
r
f
o
r
m
those
t
h
o
s
e
activities.
a
c
t
i
v
i
t
i
e
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
are:
a
r
e
:
-
The
T
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
1
1
1.
1
.
1)
1
)
serves
s
e
r
v
e
s
as
a
s
the
t
h
e
primary
p
r
i
m
a
r
y
means
m
e
a
n
s
for
f
o
r
communicating
c
o
m
m
u
n
i
c
a
t
i
n
g
the
t
h
e
proposed
p
r
o
p
o
s
e
d
development
d
e
v
e
l
o
p
m
e
n
t
methods
m
e
t
h
o
d
s
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
for
f
o
r
agreement,
a
g
r
e
e
m
e
n
t
,
and
a
n
d
defines
d
e
f
i
n
e
s
the
t
h
e
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
The
T
h
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.2)
1
1
.
2
)
defines
d
e
f
i
n
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
(s)
(
s
)
and
a
n
d
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
The
T
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.3)
1
1
.
3
)
defines
d
e
f
i
n
e
s
the
t
h
e
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
will
w
i
l
l
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
The
T
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.4)
1
1
.
4
)
defines
d
e
f
i
n
e
s
the
t
h
e
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
will
w
i
l
l
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
The
T
h
e
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.5)
1
1
.
5
)
defines
d
e
f
i
n
e
s
the
t
h
e
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
will
w
i
l
l
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
should
s
h
o
u
l
d
comply
c
o
m
p
l
y
with
w
i
t
h
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
should
s
h
o
u
l
d
define
d
e
f
i
n
e
the
t
h
e
criteria
c
r
i
t
e
r
i
a
for
f
o
r
transition
t
r
a
n
s
i
t
i
o
n
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
by
b
y
specifying:
s
p
e
c
i
f
y
i
n
g
:
-
The
T
h
e
inputs
i
n
p
u
t
s
to
t
o
the
t
h
e
process,
p
r
o
c
e
s
s
,
including
i
n
c
l
u
d
i
n
g
feedback
f
e
e
d
b
a
c
k
from
f
r
o
m
other
o
t
h
e
r
processes.
p
r
o
c
e
s
s
e
s
.
-
Any
A
n
y
integral
i
n
t
e
g
r
a
l
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
that
t
h
a
t
may
m
a
y
be
b
e
required
r
e
q
u
i
r
e
d
to
t
o
act
a
c
t
on
o
n
these
t
h
e
s
e
inputs.
i
n
p
u
t
s
.
-
Availability
A
v
a
i
l
a
b
i
l
i
t
y
of
o
f
tools,
t
o
o
l
s
,
methods,
m
e
t
h
o
d
s
,
plans
p
l
a
n
s
and
a
n
d
procedures.
p
r
o
c
e
d
u
r
e
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
should
s
h
o
u
l
d
state
s
t
a
t
e
the
t
h
e
procedures
p
r
o
c
e
d
u
r
e
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
implement
i
m
p
l
e
m
e
n
t
software
s
o
f
t
w
a
r
e
changes
c
h
a
n
g
e
s
prior
p
r
i
o
r
to
t
o
use
u
s
e
on
o
n
a
a
certified
c
e
r
t
i
f
i
e
d
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine.
e
n
g
i
n
e
.
Such
S
u
c
h
changes
c
h
a
n
g
e
s
may
m
a
y
be
b
e
as
a
s
a
a
result
r
e
s
u
l
t
of
o
f
feedback
f
e
e
d
b
a
c
k
from
f
r
o
m
other
o
t
h
e
r
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
may
m
a
y
cause
c
a
u
s
e
a
a
change
c
h
a
n
g
e
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
4.4
4
.
4
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
cycle
c
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Planning
P
l
a
n
n
i
n
g
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
the
t
h
e
planning
p
l
a
n
n
i
n
g
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
methods,
m
e
t
h
o
d
s
,
tools,
t
o
o
l
s
,
procedures,
p
r
o
c
e
d
u
r
e
s
,
programming
p
r
o
g
r
a
m
m
i
n
g
languages
l
a
n
g
u
a
g
e
s
and
a
n
d
hardware
h
a
r
d
w
a
r
e
that
t
h
a
t
will
w
i
l
l
be
b
e
used
u
s
e
d
to
t
o
develop,
d
e
v
e
l
o
p
,
verify,
v
e
r
i
f
y
,
control
c
o
n
t
r
o
l
and
a
n
d
produce
p
r
o
d
u
c
e
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
(section
(
s
e
c
t
i
o
n
11)
1
1
)
and
a
n
d
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
Examples
E
x
a
m
p
l
e
s
of
o
f
how
h
o
w
the
t
h
e
software
s
o
f
t
w
a
r
e
environment
e
n
v
i
r
o
n
m
e
n
t
chosen
c
h
o
s
e
n
can
c
a
n
have
h
a
v
e
a
a
beneficial
b
e
n
e
f
i
c
i
a
l
effect
e
f
f
e
c
t
on
o
n
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
include
i
n
c
l
u
d
e
enforcing
e
n
f
o
r
c
i
n
g
standards,
s
t
a
n
d
a
r
d
s
,
detecting
d
e
t
e
c
t
i
n
g
errors,
e
r
r
o
r
s
,
and
a
n
d
implementing
i
m
p
l
e
m
e
n
t
i
n
g
error
e
r
r
o
r
prevention
p
r
e
v
e
n
t
i
o
n
and
a
n
d
fault
f
a
u
l
t
tolerance
t
o
l
e
r
a
n
c
e
methods.
m
e
t
h
o
d
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
is
i
s
a
a
potential
p
o
t
e
n
t
i
a
l
error
e
r
r
o
r
source
s
o
u
r
c
e
that
t
h
a
t
can
c
a
n
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
failure
f
a
i
l
u
r
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
Composition
C
o
m
p
o
s
i
t
i
o
n
of
o
f
this
t
h
i
s
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
may
m
a
y
be
b
e
influenced
i
n
f
l
u
e
n
c
e
d
by
b
y
the
t
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
use
u
s
e
of
o
f
dissimilar,
d
i
s
s
i
m
i
l
a
r
,
redundant
r
e
d
u
n
d
a
n
t
components.
c
o
m
p
o
n
e
n
t
s
.
The
T
h
e
goal
g
o
a
l
of
o
f
error
e
r
r
o
r
prevention
p
r
e
v
e
n
t
i
o
n
methods
m
e
t
h
o
d
s
is
i
s
to
t
o
avoid
a
v
o
i
d
errors
e
r
r
o
r
s
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
that
t
h
a
t
might
m
i
g
h
t
contribute
c
o
n
t
r
i
b
u
t
e
to
t
o
a
a
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
The
T
h
e
basic
b
a
s
i
c
principle
p
r
i
n
c
i
p
l
e
is
i
s
to
t
o
choose
c
h
o
o
s
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
design
d
e
s
i
g
n
methods,
m
e
t
h
o
d
s
,
tools,
t
o
o
l
s
,
and
a
n
d
programming
p
r
o
g
r
a
m
m
i
n
g
languages
l
a
n
g
u
a
g
e
s
that
t
h
a
t
limit
l
i
m
i
t
the
t
h
e
opportunity
o
p
p
o
r
t
u
n
i
t
y
for
f
o
r
introducing
i
n
t
r
o
d
u
c
i
n
g
errors,
e
r
r
o
r
s
,
and
a
n
d
verification
v
e
r
i
f
i
c
a
t
i
o
n
methods
m
e
t
h
o
d
s
that
t
h
a
t
ensure
e
n
s
u
r
e
that
t
h
a
t
errors
e
r
r
o
r
s
introduced
i
n
t
r
o
d
u
c
e
d
are
a
r
e
detected.
d
e
t
e
c
t
e
d
.
The
T
h
e
goal
g
o
a
l
of
o
f
fault
f
a
u
l
t
tolerance
t
o
l
e
r
a
n
c
e
methods
m
e
t
h
o
d
s
is
i
s
to
t
o
include
i
n
c
l
u
d
e
safety
s
a
f
e
t
y
features
f
e
a
t
u
r
e
s
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
or
o
r
Source
S
o
u
r
c
e
Code
C
o
d
e
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
will
w
i
l
l
respond
r
e
s
p
o
n
d
correctly
c
o
r
r
e
c
t
l
y
to
t
o
input
i
n
p
u
t
data
d
a
t
a
errors
e
r
r
o
r
s
and
a
n
d
prevent
p
r
e
v
e
n
t
output
o
u
t
p
u
t
and
a
n
d
control
c
o
n
t
r
o
l
errors.
e
r
r
o
r
s
.
The
T
h
e
need
n
e
e
d
for
f
o
r
error
e
r
r
o
r
prevention
p
r
e
v
e
n
t
i
o
n
or
o
r
fault
f
a
u
l
t
tolerance
t
o
l
e
r
a
n
c
e
methods
m
e
t
h
o
d
s
is
i
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
17
1
7
The
T
h
e
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
presented
p
r
e
s
e
n
t
e
d
above
a
b
o
v
e
may
m
a
y
affect:
a
f
f
e
c
t
:
-
The
T
h
e
methods
m
e
t
h
o
d
s
and
a
n
d
notations
n
o
t
a
t
i
o
n
s
used
u
s
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
and
a
n
d
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process.
p
r
o
c
e
s
s
.
-
The
T
h
e
programming
p
r
o
g
r
a
m
m
i
n
g
language(s)
l
a
n
g
u
a
g
e
(
s
)
and
a
n
d
methods
m
e
t
h
o
d
s
used
u
s
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process.
p
r
o
c
e
s
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
tools.
t
o
o
l
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
and
a
n
d
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
tools.
t
o
o
l
s
.
-
The
T
h
e
need
n
e
e
d
for
f
o
r
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
12.2).
1
2
.
2
)
.
4.4.1
4
.
4
.
1
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Environment
E
n
v
i
r
o
n
m
e
n
t
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
is
i
s
a
a
significant
s
i
g
n
i
f
i
c
a
n
t
factor
f
a
c
t
o
r
in
i
n
the
t
h
e
production
p
r
o
d
u
c
t
i
o
n
of
o
f
high
h
i
g
h
quality
q
u
a
l
i
t
y
software.
s
o
f
t
w
a
r
e
.
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
can
c
a
n
also
a
l
s
o
adversely
a
d
v
e
r
s
e
l
y
affect
a
f
f
e
c
t
the
t
h
e
production
p
r
o
d
u
c
t
i
o
n
of
o
f
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
in
i
n
several
s
e
v
e
r
a
l
ways.
w
a
y
s
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
a
a
compiler
c
o
m
p
i
l
e
r
could
c
o
u
l
d
introduce
i
n
t
r
o
d
u
c
e
errors
e
r
r
o
r
s
by
b
y
producing
p
r
o
d
u
c
i
n
g
a
a
corrupted
c
o
r
r
u
p
t
e
d
output
o
u
t
p
u
t
or
o
r
a
a
linker
l
i
n
k
e
r
could
c
o
u
l
d
fail
f
a
i
l
to
t
o
reveal
r
e
v
e
a
l
a
a
memory
m
e
m
o
r
y
allocation
a
l
l
o
c
a
t
i
o
n
error
e
r
r
o
r
that
t
h
a
t
is
i
s
present.
p
r
e
s
e
n
t
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
selection
s
e
l
e
c
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
methods
m
e
t
h
o
d
s
and
a
n
d
tools
t
o
o
l
s
includes:
i
n
c
l
u
d
e
s
:
-
During
D
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
proces
p
r
o
c
e
s
s,
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
should
s
h
o
u
l
d
be
b
e
chosen
c
h
o
s
e
n
to
t
o
minimize
m
i
n
i
m
i
z
e
its
i
t
s
potential
p
o
t
e
n
t
i
a
l
risk
r
i
s
k
to
t
o
the
t
h
e
final
f
i
n
a
l
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
-
The
T
h
e
use
u
s
e
of
o
f
qualified
q
u
a
l
i
f
i
e
d
tools
t
o
o
l
s
or
o
r
combinations
c
o
m
b
i
n
a
t
i
o
n
s
of
o
f
tools
t
o
o
l
s
and
a
n
d
parts
p
a
r
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
should
s
h
o
u
l
d
be
b
e
chosen
c
h
o
s
e
n
to
t
o
achieve
a
c
h
i
e
v
e
the
t
h
e
necessary
n
e
c
e
s
s
a
r
y
level
l
e
v
e
l
of
o
f
confidence
c
o
n
f
i
d
e
n
c
e
that
t
h
a
t
an
a
n
error
e
r
r
o
r
introduced
i
n
t
r
o
d
u
c
e
d
by
b
y
one
o
n
e
part
p
a
r
t
would
w
o
u
l
d
be
b
e
detected
d
e
t
e
c
t
e
d
by
b
y
another.
a
n
o
t
h
e
r
.
An
A
n
acceptable
a
c
c
e
p
t
a
b
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
is
i
s
produced
p
r
o
d
u
c
e
d
when
w
h
e
n
both
b
o
t
h
parts
p
a
r
t
s
are
a
r
e
consistently
c
o
n
s
i
s
t
e
n
t
l
y
used
u
s
e
d
together.
t
o
g
e
t
h
e
r
.
-
Software
S
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
or
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards,
s
t
a
n
d
a
r
d
s
,
which
w
h
i
c
h
include
i
n
c
l
u
d
e
consideration
c
o
n
s
i
d
e
r
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
level,
l
e
v
e
l
,
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
to
t
o
minimize
m
i
n
i
m
i
z
e
potential
p
o
t
e
n
t
i
a
l
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment-related
e
n
v
i
r
o
n
m
e
n
t
-
r
e
l
a
t
e
d
errors.
e
r
r
o
r
s
.
-
If
I
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
is
i
s
sought
s
o
u
g
h
t
for
f
o
r
use
u
s
e
of
o
f
the
t
h
e
tools
t
o
o
l
s
in
i
n
combination,
c
o
m
b
i
n
a
t
i
o
n
,
the
t
h
e
sequence
s
e
q
u
e
n
c
e
of
o
f
operation
o
p
e
r
a
t
i
o
n
of
o
f
the
t
h
e
tools
t
o
o
l
s
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
plan.
p
l
a
n
.
-
If
I
f
optional
o
p
t
i
o
n
a
l
features
f
e
a
t
u
r
e
s
of
o
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
are
a
r
e
chosen
c
h
o
s
e
n
for
f
o
r
use
u
s
e
in
i
n
a
a
project,
p
r
o
j
e
c
t
,
the
t
h
e
effects
e
f
f
e
c
t
s
of
o
f
the
t
h
e
options
o
p
t
i
o
n
s
should
s
h
o
u
l
d
be
b
e
examined
e
x
a
m
i
n
e
d
and
a
n
d
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
plan.
p
l
a
n
.
Note:
N
o
t
e
:
This
T
h
i
s
is
i
s
especially
e
s
p
e
c
i
a
l
l
y
important
i
m
p
o
r
t
a
n
t
where
w
h
e
r
e
the
t
h
e
tool
t
o
o
l
directly
d
i
r
e
c
t
l
y
generates
g
e
n
e
r
a
t
e
s
part
p
a
r
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
In
I
n
this
t
h
i
s
context,
c
o
n
t
e
x
t
,
compilers
c
o
m
p
i
l
e
r
s
are
a
r
e
probably
p
r
o
b
a
b
l
y
the
t
h
e
most
m
o
s
t
important
i
m
p
o
r
t
a
n
t
tools
t
o
o
l
s
to
t
o
consider.
c
o
n
s
i
d
e
r
.
4.4.2
4
.
4
.
2
Language
L
a
n
g
u
a
g
e
and
a
n
d
Compiler
C
o
m
p
i
l
e
r
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
Upon
U
p
o
n
successful
s
u
c
c
e
s
s
f
u
l
completion
c
o
m
p
l
e
t
i
o
n
of
o
f
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
the
t
h
e
compiler
c
o
m
p
i
l
e
r
is
i
s
considered
c
o
n
s
i
d
e
r
e
d
acceptable
a
c
c
e
p
t
a
b
l
e
for
f
o
r
that
t
h
a
t
product.
p
r
o
d
u
c
t
.
For
F
o
r
this
t
h
i
s
to
t
o
be
b
e
valid,
v
a
l
i
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
need
n
e
e
d
to
t
o
consider
c
o
n
s
i
d
e
r
particular
p
a
r
t
i
c
u
l
a
r
features
f
e
a
t
u
r
e
s
of
o
f
the
t
h
e
programming
p
r
o
g
r
a
m
m
i
n
g
language
l
a
n
g
u
a
g
e
and
a
n
d
compiler.
c
o
m
p
i
l
e
r
.
The
T
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
considers
c
o
n
s
i
d
e
r
s
these
t
h
e
s
e
features
f
e
a
t
u
r
e
s
when
w
h
e
n
choosing
c
h
o
o
s
i
n
g
a
a
programming
p
r
o
g
r
a
m
m
i
n
g
language
l
a
n
g
u
a
g
e
and
a
n
d
planning
p
l
a
n
n
i
n
g
for
f
o
r
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Some
S
o
m
e
compilers
c
o
m
p
i
l
e
r
s
have
h
a
v
e
features
f
e
a
t
u
r
e
s
intended
i
n
t
e
n
d
e
d
to
t
o
optimize
o
p
t
i
m
i
z
e
performance
p
e
r
f
o
r
m
a
n
c
e
of
o
f
the
t
h
e
object
o
b
j
e
c
t
code.
c
o
d
e
.
If
I
f
the
t
h
e
test
t
e
s
t
cases
c
a
s
e
s
give
g
i
v
e
coverage
c
o
v
e
r
a
g
e
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
level,
l
e
v
e
l
,
the
t
h
e
correctness
c
o
r
r
e
c
t
n
e
s
s
of
o
f
the
t
h
e
optimization
o
p
t
i
m
i
z
a
t
i
o
n
need
n
e
e
d
not
n
o
t
be
b
e
verified.
v
e
r
i
f
i
e
d
.
Otherwise,
O
t
h
e
r
w
i
s
e
,
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
these
t
h
e
s
e
features
f
e
a
t
u
r
e
s
on
o
n
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
be
b
e
determined
d
e
t
e
r
m
i
n
e
d
following
f
o
l
l
o
w
i
n
g
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
subparagraph
s
u
b
p
a
r
a
g
r
a
p
h
6.4.4.2.
6
.
4
.
4
.
2
.
-
To
T
o
implement
i
m
p
l
e
m
e
n
t
certain
c
e
r
t
a
i
n
features,
f
e
a
t
u
r
e
s
,
compilers
c
o
m
p
i
l
e
r
s
for
f
o
r
some
s
o
m
e
languages
l
a
n
g
u
a
g
e
s
may
m
a
y
produce
p
r
o
d
u
c
e
object
o
b
j
e
c
t
code
c
o
d
e
that
t
h
a
t
is
i
s
not
n
o
t
directly
d
i
r
e
c
t
l
y
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
source
s
o
u
r
c
e
code,
c
o
d
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
initialization,
i
n
i
t
i
a
l
i
z
a
t
i
o
n
,
built
b
u
i
l
t
-in
-
i
n
error
e
r
r
o
r
detection
d
e
t
e
c
t
i
o
n
or
o
r
exception
e
x
c
e
p
t
i
o
n
handling
h
a
n
d
l
i
n
g
(subparagraph
(
s
u
b
p
a
r
a
g
r
a
p
h
6.4.4.2,
6
.
4
.
4
.
2
,
item
i
t
e
m
b).
b
)
.
The
T
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
18
1
8
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
a
a
means
m
e
a
n
s
to
t
o
detect
d
e
t
e
c
t
this
t
h
i
s
object
o
b
j
e
c
t
code
c
o
d
e
and
a
n
d
to
t
o
ensure
e
n
s
u
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
coverage
c
o
v
e
r
a
g
e
and
a
n
d
define
d
e
f
i
n
e
the
t
h
e
means
m
e
a
n
s
in
i
n
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
plan.
p
l
a
n
.
-
If
I
f
a
a
new
n
e
w
compiler,
c
o
m
p
i
l
e
r
,
linkage
l
i
n
k
a
g
e
editor
e
d
i
t
o
r
or
o
r
loader
l
o
a
d
e
r
version
v
e
r
s
i
o
n
is
i
s
introduced,
i
n
t
r
o
d
u
c
e
d
,
or
o
r
compiler
c
o
m
p
i
l
e
r
options
o
p
t
i
o
n
s
are
a
r
e
changed
c
h
a
n
g
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle,
c
y
c
l
e
,
previous
p
r
e
v
i
o
u
s
tests
t
e
s
t
s
and
a
n
d
coverage
c
o
v
e
r
a
g
e
analyses
a
n
a
l
y
s
e
s
may
m
a
y
no
n
o
longer
l
o
n
g
e
r
be
b
e
valid.
v
a
l
i
d
.
The
T
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
planning
p
l
a
n
n
i
n
g
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
a
a
means
m
e
a
n
s
of
o
f
re
r
e
-verification
-
v
e
r
i
f
i
c
a
t
i
o
n
which
w
h
i
c
h
is
i
s
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
section
s
e
c
t
i
o
n
6
6
and
a
n
d
paragraph
p
a
r
a
g
r
a
p
h
12.1.3.
1
2
.
1
.
3
.
4.4.3
4
.
4
.
3
Software
S
o
f
t
w
a
r
e
Test
T
e
s
t
Environment
E
n
v
i
r
o
n
m
e
n
t
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
software
s
o
f
t
w
a
r
e
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
planning
p
l
a
n
n
i
n
g
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
methods,
m
e
t
h
o
d
s
,
tools,
t
o
o
l
s
,
procedures
p
r
o
c
e
d
u
r
e
s
and
a
n
d
hardware
h
a
r
d
w
a
r
e
that
t
h
a
t
will
w
i
l
l
be
b
e
used
u
s
e
d
to
t
o
test
t
e
s
t
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
Testing
T
e
s
t
i
n
g
may
m
a
y
be
b
e
performed
p
e
r
f
o
r
m
e
d
using
u
s
i
n
g
the
t
h
e
target
t
a
r
g
e
t
computer,
c
o
m
p
u
t
e
r
,
a
a
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
emulator
e
m
u
l
a
t
o
r
or
o
r
a
a
host
h
o
s
t
computer
c
o
m
p
u
t
e
r
simulator.
s
i
m
u
l
a
t
o
r
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
emulator
e
m
u
l
a
t
o
r
or
o
r
simulator
s
i
m
u
l
a
t
o
r
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
qualified
q
u
a
l
i
f
i
e
d
as
a
s
described
d
e
s
c
r
i
b
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
12.2.
1
2
.
2
.
-
The
T
h
e
differences
d
i
f
f
e
r
e
n
c
e
s
between
b
e
t
w
e
e
n
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
and
a
n
d
the
t
h
e
emulator
e
m
u
l
a
t
o
r
or
o
r
simulator,
s
i
m
u
l
a
t
o
r
,
and
a
n
d
the
t
h
e
effects
e
f
f
e
c
t
s
of
o
f
these
t
h
e
s
e
differences
d
i
f
f
e
r
e
n
c
e
s
on
o
n
the
t
h
e
ability
a
b
i
l
i
t
y
to
t
o
detect
d
e
t
e
c
t
errors
e
r
r
o
r
s
and
a
n
d
verify
v
e
r
i
f
y
functionality,
f
u
n
c
t
i
o
n
a
l
i
t
y
,
should
s
h
o
u
l
d
be
b
e
considered.
c
o
n
s
i
d
e
r
e
d
.
Detection
D
e
t
e
c
t
i
o
n
of
o
f
those
t
h
o
s
e
errors
e
r
r
o
r
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
by
b
y
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
and
a
n
d
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan.
P
l
a
n
.
4.5
4
.
5
Software
S
o
f
t
w
a
r
e
Test
T
e
s
t
Environment
E
n
v
i
r
o
n
m
e
n
t
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
rules
r
u
l
e
s
and
a
n
d
constraints
c
o
n
s
t
r
a
i
n
t
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
include
i
n
c
l
u
d
e
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards,
S
t
a
n
d
a
r
d
s
,
the
t
h
e
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards.
S
t
a
n
d
a
r
d
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
uses
u
s
e
s
these
t
h
e
s
e
standards
s
t
a
n
d
a
r
d
s
as
a
s
a
a
basis
b
a
s
i
s
for
f
o
r
evaluating
e
v
a
l
u
a
t
i
n
g
the
t
h
e
compliance
c
o
m
p
l
i
a
n
c
e
of
o
f
actual
a
c
t
u
a
l
outputs
o
u
t
p
u
t
s
of
o
f
a
a
process
p
r
o
c
e
s
s
with
w
i
t
h
intended
i
n
t
e
n
d
e
d
outputs.
o
u
t
p
u
t
s
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
comply
c
o
m
p
l
y
with
w
i
t
h
section
s
e
c
t
i
o
n
11.
1
1
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
enable
e
n
a
b
l
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
of
o
f
a
a
given
g
i
v
e
n
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
or
o
r
related
r
e
l
a
t
e
d
set
s
e
t
of
o
f
products
p
r
o
d
u
c
t
s
to
t
o
be
b
e
uniformly
u
n
i
f
o
r
m
l
y
designed
d
e
s
i
g
n
e
d
and
a
n
d
implemented.
i
m
p
l
e
m
e
n
t
e
d
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
disallow
d
i
s
a
l
l
o
w
the
t
h
e
use
u
s
e
of
o
f
constructs
c
o
n
s
t
r
u
c
t
s
or
o
r
methods
m
e
t
h
o
d
s
that
t
h
a
t
produce
p
r
o
d
u
c
e
outputs
o
u
t
p
u
t
s
that
t
h
a
t
cannot
c
a
n
n
o
t
be
b
e
verified
v
e
r
i
f
i
e
d
or
o
r
that
t
h
a
t
are
a
r
e
not
n
o
t
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Note:
N
o
t
e
:
In
I
n
developing
d
e
v
e
l
o
p
i
n
g
standards,
s
t
a
n
d
a
r
d
s
,
consideration
c
o
n
s
i
d
e
r
a
t
i
o
n
can
c
a
n
be
b
e
given
g
i
v
e
n
to
t
o
previous
p
r
e
v
i
o
u
s
experience.
e
x
p
e
r
i
e
n
c
e
.
Constraints
C
o
n
s
t
r
a
i
n
t
s
and
a
n
d
rules
r
u
l
e
s
on
o
n
development,
d
e
v
e
l
o
p
m
e
n
t
,
design,
d
e
s
i
g
n
,
and
a
n
d
coding
c
o
d
i
n
g
methods
m
e
t
h
o
d
s
can
c
a
n
be
b
e
included
i
n
c
l
u
d
e
d
to
t
o
control
c
o
n
t
r
o
l
complexity.
c
o
m
p
l
e
x
i
t
y
.
Defensive
D
e
f
e
n
s
i
v
e
programming
p
r
o
g
r
a
m
m
i
n
g
practices
p
r
a
c
t
i
c
e
s
may
m
a
y
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
to
t
o
improve
i
m
p
r
o
v
e
robustness.
r
o
b
u
s
t
n
e
s
s
.
4.6
4
.
6
Review
R
e
v
i
e
w
and
a
n
d
Assurance
A
s
s
u
r
a
n
c
e
of
o
f
the
t
h
e
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process
P
r
o
c
e
s
s
Reviews
R
e
v
i
e
w
s
and
a
n
d
assurance
a
s
s
u
r
a
n
c
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
are
a
r
e
conducted
c
o
n
d
u
c
t
e
d
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
and
a
n
d
means
m
e
a
n
s
are
a
r
e
provided
p
r
o
v
i
d
e
d
to
t
o
execute
e
x
e
c
u
t
e
them.
t
h
e
m
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
chosen
c
h
o
s
e
n
methods
m
e
t
h
o
d
s
will
w
i
l
l
enable
e
n
a
b
l
e
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
can
c
a
n
be
b
e
applied
a
p
p
l
i
e
d
consistently.
c
o
n
s
i
s
t
e
n
t
l
y
.
-
Each
E
a
c
h
process
p
r
o
c
e
s
s
produces
p
r
o
d
u
c
e
s
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
its
i
t
s
outputs
o
u
t
p
u
t
s
can
c
a
n
be
b
e
traced
t
r
a
c
e
d
to
t
o
their
t
h
e
i
r
activity
a
c
t
i
v
i
t
y
and
a
n
d
inputs,
i
n
p
u
t
s
,
showing
s
h
o
w
i
n
g
the
t
h
e
degree
d
e
g
r
e
e
of
o
f
independence
i
n
d
e
p
e
n
d
e
n
c
e
of
o
f
the
t
h
e
activity,
a
c
t
i
v
i
t
y
,
the
t
h
e
environment,
e
n
v
i
r
o
n
m
e
n
t
,
and
a
n
d
the
t
h
e
methods
m
e
t
h
o
d
s
to
t
o
be
b
e
used.
u
s
e
d
.
-
The
T
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
are
a
r
e
consistent
c
o
n
s
i
s
t
e
n
t
and
a
n
d
comply
c
o
m
p
l
y
with
w
i
t
h
section
s
e
c
t
i
o
n
11.
1
1
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
19
1
9
5
5
SOFTWARE
S
O
F
T
W
A
R
E
DEVELOPMENT
D
E
V
E
L
O
P
M
E
N
T
PROCESS
P
R
O
C
E
S
S
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
applied
a
p
p
l
i
e
d
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
(section
(
s
e
c
t
i
o
n
4)
4
)
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.2).
1
1
.
2
)
.
Table
T
a
b
l
e
A-2
A
-
2
of
o
f
Annex
A
n
n
e
x
A
A
is
i
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
are:
a
r
e
:
-
Software
S
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process.
p
r
o
c
e
s
s
.
-
Software
S
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process.
p
r
o
c
e
s
s
.
-
Software
S
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process.
p
r
o
c
e
s
s
.
-
Integration
I
n
t
e
g
r
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
Software
S
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
produce
p
r
o
d
u
c
e
one
o
n
e
or
o
r
more
m
o
r
e
levels
l
e
v
e
l
s
of
o
f
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
produced
p
r
o
d
u
c
e
d
directly
d
i
r
e
c
t
l
y
through
t
h
r
o
u
g
h
analysis
a
n
a
l
y
s
i
s
of
o
f
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
system
s
y
s
t
e
m
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
Usually,
U
s
u
a
l
l
y
,
these
t
h
e
s
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
further
f
u
r
t
h
e
r
developed
d
e
v
e
l
o
p
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
thus
t
h
u
s
producing
p
r
o
d
u
c
i
n
g
one
o
n
e
or
o
r
more
m
o
r
e
successive,
s
u
c
c
e
s
s
i
v
e
,
lower
l
o
w
e
r
levels
l
e
v
e
l
s
of
o
f
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
However,
H
o
w
e
v
e
r
,
if
i
f
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
generated
g
e
n
e
r
a
t
e
d
directly
d
i
r
e
c
t
l
y
from
f
r
o
m
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
then
t
h
e
n
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
also
a
l
s
o
considered
c
o
n
s
i
d
e
r
e
d
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
and
a
n
d
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
for
f
o
r
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
also
a
l
s
o
apply.
a
p
p
l
y
.
The
T
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
a
a
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
involves
i
n
v
o
l
v
e
s
decisions
d
e
c
i
s
i
o
n
s
made
m
a
d
e
about
a
b
o
u
t
the
t
h
e
structure
s
t
r
u
c
t
u
r
e
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
During
D
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
is
i
s
defined
d
e
f
i
n
e
d
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
developed.
d
e
v
e
l
o
p
e
d
.
Low-level
L
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
from
f
r
o
m
which
w
h
i
c
h
Source
S
o
u
r
c
e
Code
C
o
d
e
can
c
a
n
be
b
e
directly
d
i
r
e
c
t
l
y
implemented
i
m
p
l
e
m
e
n
t
e
d
without
w
i
t
h
o
u
t
further
f
u
r
t
h
e
r
information.
i
n
f
o
r
m
a
t
i
o
n
.
Each
E
a
c
h
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
process
p
r
o
c
e
s
s
may
m
a
y
produce
p
r
o
d
u
c
e
derived
d
e
r
i
v
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Derived
D
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
are
a
r
e
not
n
o
t
directly
d
i
r
e
c
t
l
y
traceable
t
r
a
c
e
a
b
l
e
to
t
o
higher
h
i
g
h
e
r
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
An
A
n
example
e
x
a
m
p
l
e
of
o
f
such
s
u
c
h
a
a
derived
d
e
r
i
v
e
d
require
r
e
q
u
i
r
e
ment
m
e
n
t
is
i
s
the
t
h
e
need
n
e
e
d
for
f
o
r
interrupt
i
n
t
e
r
r
u
p
t
handling
h
a
n
d
l
i
n
g
software
s
o
f
t
w
a
r
e
to
t
o
be
b
e
developed
d
e
v
e
l
o
p
e
d
for
f
o
r
the
t
h
e
chosen
c
h
o
s
e
n
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
may
m
a
y
include
i
n
c
l
u
d
e
derived
d
e
r
i
v
e
d
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
may
m
a
y
include
i
n
c
l
u
d
e
derived
d
e
r
i
v
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
effects
e
f
f
e
c
t
s
of
o
f
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
on
o
n
safety
s
a
f
e
t
y
related
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
5.1
5
.
1
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Process
P
r
o
c
e
s
s
The
T
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
uses
u
s
e
s
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
These
T
h
e
s
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
include
i
n
c
l
u
d
e
functional,
f
u
n
c
t
i
o
n
a
l
,
performance,
p
e
r
f
o
r
m
a
n
c
e
,
interface
i
n
t
e
r
f
a
c
e
and
a
n
d
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
5.1.1
5
.
1
.
1
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
are:
a
r
e
:
-
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
developed.
d
e
v
e
l
o
p
e
d
.
-
Derived
D
e
r
i
v
e
d
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
indicated
i
n
d
i
c
a
t
e
d
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
5.1.2
5
.
1
.
2
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
Inputs
I
n
p
u
t
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
include
i
n
c
l
u
d
e
the
t
h
e
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
the
t
h
e
hardware
h
a
r
d
w
a
r
e
interface
i
n
t
e
r
f
a
c
e
and
a
n
d
system
s
y
s
t
e
m
architecture
a
r
c
h
i
t
e
c
t
u
r
e
(if
(
i
f
not
n
o
t
included
i
n
c
l
u
d
e
d
in
i
n
the
t
h
e
requirements)
r
e
q
u
i
r
e
m
e
n
t
s
)
from
f
r
o
m
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
process,
p
r
o
c
e
s
s
,
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
When
W
h
e
n
the
t
h
e
planned
p
l
a
n
n
e
d
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
have
h
a
v
e
been
b
e
e
n
satisfied,
s
a
t
i
s
f
i
e
d
,
these
t
h
e
s
e
inputs
i
n
p
u
t
s
are
a
r
e
used
u
s
e
d
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
primary
p
r
i
m
a
r
y
output
o
u
t
p
u
t
of
o
f
this
t
h
i
s
process
p
r
o
c
e
s
s
is
i
s
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data
D
a
t
a
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.9).
1
1
.
9
)
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
20
2
0
The
T
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
is
i
s
complete
c
o
m
p
l
e
t
e
when
w
h
e
n
its
i
t
s
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
it
i
t
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
system
s
y
s
t
e
m
functional
f
u
n
c
t
i
o
n
a
l
and
a
n
d
interface
i
n
t
e
r
f
a
c
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
are
a
r
e
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
be
b
e
analyze
a
n
a
l
y
z
e
for
f
o
r
ambiguities,
a
m
b
i
g
u
i
t
i
e
s
,
inconsistencies
i
n
c
o
n
s
i
s
t
e
n
c
i
e
s
and
a
n
d
undefined
u
n
d
e
f
i
n
e
d
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Inputs
I
n
p
u
t
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
detected
d
e
t
e
c
t
e
d
as
a
s
inadequate
i
n
a
d
e
q
u
a
t
e
or
o
r
incorrect
i
n
c
o
r
r
e
c
t
should
s
h
o
u
l
d
be
b
e
reported
r
e
p
o
r
t
e
d
as
a
s
feedback
f
e
e
d
b
a
c
k
to
t
o
the
t
h
e
input
i
n
p
u
t
source
s
o
u
r
c
e
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
clarification
c
l
a
r
i
f
i
c
a
t
i
o
n
or
o
r
correction.
c
o
r
r
e
c
t
i
o
n
.
-
Each
E
a
c
h
system
s
y
s
t
e
m
requirement
r
e
q
u
i
r
e
m
e
n
t
that
t
h
a
t
is
i
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
address
a
d
d
r
e
s
s
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
to
t
o
preclude
p
r
e
c
l
u
d
e
system
s
y
s
t
e
m
hazards
h
a
z
a
r
d
s
should
s
h
o
u
l
d
be
b
e
defined.
d
e
f
i
n
e
d
.
-
The
T
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
conform
c
o
n
f
o
r
m
to
t
o
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards,
S
t
a
n
d
a
r
d
s
,
and
a
n
d
be
b
e
verifiable
v
e
r
i
f
i
a
b
l
e
and
a
n
d
consistent.
c
o
n
s
i
s
t
e
n
t
.
-
The
T
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
stated
s
t
a
t
e
d
in
i
n
quantitative
q
u
a
n
t
i
t
a
t
i
v
e
terms
t
e
r
m
s
with
w
i
t
h
tolerances
t
o
l
e
r
a
n
c
e
s
where
w
h
e
r
e
applicable.
a
p
p
l
i
c
a
b
l
e
.
-
The
T
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
not
n
o
t
describe
d
e
s
c
r
i
b
e
design
d
e
s
i
g
n
or
o
r
verification
v
e
r
i
f
i
c
a
t
i
o
n
detail
d
e
t
a
i
l
except
e
x
c
e
p
t
for
f
o
r
specified
s
p
e
c
i
f
i
e
d
and
a
n
d
justified
j
u
s
t
i
f
i
e
d
design
d
e
s
i
g
n
constraints.
c
o
n
s
t
r
a
i
n
t
s
.
-
Each
E
a
c
h
system
s
y
s
t
e
m
requirement
r
e
q
u
i
r
e
m
e
n
t
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
be
b
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
one
o
n
e
or
o
r
more
m
o
r
e
software
s
o
f
t
w
a
r
e
high-
h
i
g
h
-
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Each
E
a
c
h
high-level
h
i
g
h
-
l
e
v
e
l
requirement
r
e
q
u
i
r
e
m
e
n
t
should
s
h
o
u
l
d
be
b
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
one
o
n
e
or
o
r
more
m
o
r
e
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
except
e
x
c
e
p
t
for
f
o
r
derived
d
e
r
i
v
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Derived
D
e
r
i
v
e
d
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
5.2
5
.
2
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process
P
r
o
c
e
s
s
The
T
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
refined
r
e
f
i
n
e
d
through
t
h
r
o
u
g
h
one
o
n
e
or
o
r
more
m
o
r
e
iterations
i
t
e
r
a
t
i
o
n
s
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
can
c
a
n
be
b
e
used
u
s
e
d
to
t
o
implement
i
m
p
l
e
m
e
n
t
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
5.2.1
5
.
2
.
1
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
are:
a
r
e
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
from
f
r
o
m
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Derived
D
e
r
i
v
e
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
5.2.2
5
.
2
.
2
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
The
T
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
inputs
i
n
p
u
t
s
are
a
r
e
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data,
D
a
t
a
,
the
t
h
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards.
S
t
a
n
d
a
r
d
s
.
When
W
h
e
n
the
t
h
e
planned
p
l
a
n
n
e
d
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
have
h
a
v
e
been
b
e
e
n
satisfied,
s
a
t
i
s
f
i
e
d
,
the
t
h
e
high-
h
i
g
h
-
level
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
used
u
s
e
d
in
i
n
the
t
h
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
to
t
o
develop
d
e
v
e
l
o
p
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
This
T
h
i
s
may
m
a
y
involve
i
n
v
o
l
v
e
one
o
n
e
or
o
r
more
m
o
r
e
lower
l
o
w
e
r
levels
l
e
v
e
l
s
of
o
f
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
primary
p
r
i
m
a
r
y
output
o
u
t
p
u
t
of
o
f
the
t
h
e
process
p
r
o
c
e
s
s
is
i
s
the
t
h
e
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
I
I
1.
1
.
10)
1
0
)
which
w
h
i
c
h
includes
i
n
c
l
u
d
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
is
i
s
complete
c
o
m
p
l
e
t
e
when
w
h
e
n
its
i
t
s
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
it
i
t
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
includes:
i
n
c
l
u
d
e
s
:
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
21
2
1
-
Low-level
L
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
developed
d
e
v
e
l
o
p
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
conform
c
o
n
f
o
r
m
to
t
o
the
t
h
e
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
and
a
n
d
be
b
e
traceable,
t
r
a
c
e
a
b
l
e
,
verifiable
v
e
r
i
f
i
a
b
l
e
and
a
n
d
consistent
c
o
n
s
i
s
t
e
n
t
-
Derived
D
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
and
a
n
d
analyzed
a
n
a
l
y
z
e
d
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
higher
h
i
g
h
e
r
level
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
not
n
o
t
compromised.
c
o
m
p
r
o
m
i
s
e
d
.
-
Software
S
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
could
c
o
u
l
d
introduce
i
n
t
r
o
d
u
c
e
possible
p
o
s
s
i
b
l
e
modes
m
o
d
e
s
of
o
f
failure
f
a
i
l
u
r
e
into
i
n
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
or,
o
r
,
conversely,
c
o
n
v
e
r
s
e
l
y
,
preclude
p
r
e
c
l
u
d
e
others.
o
t
h
e
r
s
.
The
T
h
e
use
u
s
e
of
o
f
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
or
o
r
other
o
t
h
e
r
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
means
m
e
a
n
s
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
may
m
a
y
alter
a
l
t
e
r
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
assignment
a
s
s
i
g
n
m
e
n
t
for
f
o
r
some
s
o
m
e
components
c
o
m
p
o
n
e
n
t
s
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
In
I
n
such
s
u
c
h
cases,
c
a
s
e
s
,
additional
a
d
d
i
t
i
o
n
a
l
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
as
a
s
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
-
Control
C
o
n
t
r
o
l
flow
f
l
o
w
and
a
n
d
data
d
a
t
a
flow
f
l
o
w
should
s
h
o
u
l
d
be
b
e
monitored
m
o
n
i
t
o
r
e
d
when
w
h
e
n
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
dictate,
d
i
c
t
a
t
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
watchdog
w
a
t
c
h
d
o
g
timers,
t
i
m
e
r
s
,
reasonableness-checks
r
e
a
s
o
n
a
b
l
e
n
e
s
s
-
c
h
e
c
k
s
and
a
n
d
cross-channel
c
r
o
s
s
-
c
h
a
n
n
e
l
comparisons.
c
o
m
p
a
r
i
s
o
n
s
.
-
Responses
R
e
s
p
o
n
s
e
s
to
t
o
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
should
s
h
o
u
l
d
be
b
e
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Inadequate
I
n
a
d
e
q
u
a
t
e
or
o
r
incorrect
i
n
c
o
r
r
e
c
t
inputs
i
n
p
u
t
s
detected
d
e
t
e
c
t
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
either
e
i
t
h
e
r
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process,
p
r
o
c
e
s
s
,
or
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
as
a
s
feedback
f
e
e
d
b
a
c
k
for
f
o
r
clarification
c
l
a
r
i
f
i
c
a
t
i
o
n
or
o
r
correction.
c
o
r
r
e
c
t
i
o
n
.
Note:
N
o
t
e
:
The
T
h
e
current
c
u
r
r
e
n
t
state
s
t
a
t
e
of
o
f
software
s
o
f
t
w
a
r
e
engineering
e
n
g
i
n
e
e
r
i
n
g
does
d
o
e
s
not
n
o
t
permit
p
e
r
m
i
t
a
a
quantitative
q
u
a
n
t
i
t
a
t
i
v
e
correlation
c
o
r
r
e
l
a
t
i
o
n
between
b
e
t
w
e
e
n
complexity
c
o
m
p
l
e
x
i
t
y
and
a
n
d
the
t
h
e
attainment
a
t
t
a
i
n
m
e
n
t
of
o
f
safety
s
a
f
e
t
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
While
W
h
i
l
e
no
n
o
objective
o
b
j
e
c
t
i
v
e
guidelines
g
u
i
d
e
l
i
n
e
s
can
c
a
n
be
b
e
provided,
p
r
o
v
i
d
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
avoid
a
v
o
i
d
introducing
i
n
t
r
o
d
u
c
i
n
g
complexity
c
o
m
p
l
e
x
i
t
y
because
b
e
c
a
u
s
e
as
a
s
the
t
h
e
complexity
c
o
m
p
l
e
x
i
t
y
of
o
f
software
s
o
f
t
w
a
r
e
increases,
i
n
c
r
e
a
s
e
s
,
it
i
t
becomes
b
e
c
o
m
e
s
re
r
e
difficult
d
i
f
f
i
c
u
l
t
to
t
o
verify
v
e
r
i
f
y
the
t
h
e
design
d
e
s
i
g
n
and
a
n
d
to
t
o
show
s
h
o
w
that
t
h
a
t
the
t
h
e
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
5.2.3
5
.
2
.
3
Designing
D
e
s
i
g
n
i
n
g
for
f
o
r
User-Modifiable
U
s
e
r
-
M
o
d
i
f
i
a
b
l
e
Software
S
o
f
t
w
a
r
e
Guidance
G
u
i
d
a
n
c
e
follows
f
o
l
l
o
w
s
concerning
c
o
n
c
e
r
n
i
n
g
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
designed
d
e
s
i
g
n
e
d
to
t
o
be
b
e
modifiable
m
o
d
i
f
i
a
b
l
e
by
b
y
its
i
t
s
users.
u
s
e
r
s
.
A
A
modifiable
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
is
i
s
that
t
h
a
t
part
p
a
r
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
changed
c
h
a
n
g
e
d
by
b
y
the
t
h
e
user
u
s
e
r
and
a
n
d
a
a
non-
n
o
n
-
modifiable
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
is
i
s
that
t
h
a
t
which
w
h
i
c
h
is
i
s
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
changed
c
h
a
n
g
e
d
by
b
y
the
t
h
e
user.
u
s
e
r
.
User-modifiable
U
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
may
m
a
y
vary
v
a
r
y
in
i
n
complexity.
c
o
m
p
l
e
x
i
t
y
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
a
a
single
s
i
n
g
l
e
memory
m
e
m
o
r
y
bit
b
i
t
used
u
s
e
d
to
t
o
select
s
e
l
e
c
t
one
o
n
e
of
o
f
two
t
w
o
equipment
e
q
u
i
p
m
e
n
t
options,
o
p
t
i
o
n
s
,
a
a
table
t
a
b
l
e
of
o
f
messages,
m
e
s
s
a
g
e
s
,
or
o
r
a
a
memory
m
e
m
o
r
y
area
a
r
e
a
that
t
h
a
t
can
c
a
n
be
b
e
programmed,
p
r
o
g
r
a
m
m
e
d
,
compiled,
c
o
m
p
i
l
e
d
,
and
a
n
d
linked
l
i
n
k
e
d
for
f
o
r
aircraft
a
i
r
c
r
a
f
t
maintenance
m
a
i
n
t
e
n
a
n
c
e
functions.
f
u
n
c
t
i
o
n
s
.
Software
S
o
f
t
w
a
r
e
of
o
f
any
a
n
y
level
l
e
v
e
l
can
c
a
n
include
i
n
c
l
u
d
e
a
a
modifiable
m
o
d
i
f
i
a
b
l
e
component.
c
o
m
p
o
n
e
n
t
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
designing
d
e
s
i
g
n
i
n
g
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
non-modifiable
n
o
n
-
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
should
s
h
o
u
l
d
be
b
e
protected
p
r
o
t
e
c
t
e
d
from
f
r
o
m
the
t
h
e
modifiable
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
to
t
o
prevent
p
r
e
v
e
n
t
interference
i
n
t
e
r
f
e
r
e
n
c
e
in
i
n
the
t
h
e
safe
s
a
f
e
operation
o
p
e
r
a
t
i
o
n
of
o
f
the
t
h
e
non-modifiable
n
o
n
-
m
o
d
i
f
i
a
b
l
e
component.
c
o
m
p
o
n
e
n
t
.
This
T
h
i
s
protection
p
r
o
t
e
c
t
i
o
n
can
c
a
n
be
b
e
enforced
e
n
f
o
r
c
e
d
by
b
y
hardware,
h
a
r
d
w
a
r
e
,
by
b
y
software,
s
o
f
t
w
a
r
e
,
by
b
y
the
t
h
e
tools
t
o
o
l
s
used
u
s
e
d
to
t
o
make
m
a
k
e
the
t
h
e
change,
c
h
a
n
g
e
,
or
o
r
by
b
y
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
the
t
h
e
three.
t
h
r
e
e
.
-
The
T
h
e
applicant-provided
a
p
p
l
i
c
a
n
t
-
p
r
o
v
i
d
e
d
means
m
e
a
n
s
should
s
h
o
u
l
d
be
b
e
shown
s
h
o
w
n
to
t
o
be
b
e
the
t
h
e
only
o
n
l
y
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
the
t
h
e
modifiable
m
o
d
i
f
i
a
b
l
e
component
c
o
m
p
o
n
e
n
t
can
c
a
n
be
b
e
changed.
c
h
a
n
g
e
d
.
5.3
5
.
3
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process
P
r
o
c
e
s
s
In
I
n
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process,
p
r
o
c
e
s
s
,
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
implemented
i
m
p
l
e
m
e
n
t
e
d
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
5.3.1
5
.
3
.
1
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
is:
i
s
:
-
Source
S
o
u
r
c
e
code
c
o
d
e
is
i
s
developed
d
e
v
e
l
o
p
e
d
that
t
h
a
t
is
i
s
traceable,
t
r
a
c
e
a
b
l
e
,
verifiable,
v
e
r
i
f
i
a
b
l
e
,
consistent,
c
o
n
s
i
s
t
e
n
t
,
and
a
n
d
correctly
c
o
r
r
e
c
t
l
y
implements
i
m
p
l
e
m
e
n
t
s
low-
l
o
w
-
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
22
2
2
5.3.2
5
.
3
.
2
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
The
T
h
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
inputs
i
n
p
u
t
s
are
a
r
e
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards.
S
t
a
n
d
a
r
d
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
may
m
a
y
be
b
e
entered
e
n
t
e
r
e
d
or
o
r
re-entered
r
e
-
e
n
t
e
r
e
d
when
w
h
e
n
the
t
h
e
planned
p
l
a
n
n
e
d
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
The
T
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
produced
p
r
o
d
u
c
e
d
by
b
y
this
t
h
i
s
process
p
r
o
c
e
s
s
based
b
a
s
e
d
upon
u
p
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
primary
p
r
i
m
a
r
y
results
r
e
s
u
l
t
s
of
o
f
this
t
h
i
s
process
p
r
o
c
e
s
s
are
a
r
e
Source
S
o
u
r
c
e
Code
C
o
d
e
(subsection
(
s
u
b
s
e
c
t
i
o
n
1
1
1.
1
.
I
I
1)
1
)
and
a
n
d
object
o
b
j
e
c
t
code.
c
o
d
e
.
The
T
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
is
i
s
complete
c
o
m
p
l
e
t
e
when
w
h
e
n
its
i
t
s
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
it
i
t
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
should
s
h
o
u
l
d
implement
i
m
p
l
e
m
e
n
t
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
conform
c
o
n
f
o
r
m
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
The
T
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
should
s
h
o
u
l
d
conform
c
o
n
f
o
r
m
to
t
o
the
t
h
e
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards.
S
t
a
n
d
a
r
d
s
.
-
The
T
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
should
s
h
o
u
l
d
be
b
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
Design
D
e
s
i
g
n
Description.
D
e
s
c
r
i
p
t
i
o
n
.
-
Inadequate
I
n
a
d
e
q
u
a
t
e
or
o
r
incorrect
i
n
c
o
r
r
e
c
t
inputs
i
n
p
u
t
s
detected
d
e
t
e
c
t
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process,
p
r
o
c
e
s
s
,
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
or
o
r
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
as
a
s
feedback
f
e
e
d
b
a
c
k
for
f
o
r
clarification
c
l
a
r
i
f
i
c
a
t
i
o
n
or
o
r
correction.
c
o
r
r
e
c
t
i
o
n
.
5.4
5
.
4
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
The
T
h
e
target
t
a
r
g
e
t
computer,
c
o
m
p
u
t
e
r
,
and
a
n
d
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
and
a
n
d
object
o
b
j
e
c
t
code
c
o
d
e
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
are
a
r
e
used
u
s
e
d
with
w
i
t
h
the
t
h
e
linking
l
i
n
k
i
n
g
and
a
n
d
loading
l
o
a
d
i
n
g
data
d
a
t
a
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.16)
1
1
.
1
6
)
in
i
n
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
integrated
i
n
t
e
g
r
a
t
e
d
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
5.4.1
5
.
4
.
1
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
is:
i
s
:
-
The
T
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
is
i
s
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
e
target
t
a
r
g
e
t
hardware
h
a
r
d
w
a
r
e
for
f
o
r
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration.
i
n
t
e
g
r
a
t
i
o
n
.
5.4.2
5
.
4
.
2
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
The
T
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
consists
c
o
n
s
i
s
t
s
of
o
f
software
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
and
a
n
d
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration.
i
n
t
e
g
r
a
t
i
o
n
.
The
T
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
may
m
a
y
be
b
e
entered
e
n
t
e
r
e
d
or
o
r
re-entered
r
e
-
e
n
t
e
r
e
d
when
w
h
e
n
the
t
h
e
planned
p
l
a
n
n
e
d
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
have
h
a
v
e
been
b
e
e
n
satisfied.
s
a
t
i
s
f
i
e
d
.
The
T
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
inputs
i
n
p
u
t
s
are
a
r
e
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
and
a
n
d
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
and
a
n
d
object
o
b
j
e
c
t
code
c
o
d
e
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process.
p
r
o
c
e
s
s
.
The
T
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
are
a
r
e
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code,
C
o
d
e
,
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
11.12,
1
1
.
1
2
,
and
a
n
d
the
t
h
e
linking
l
i
n
k
i
n
g
and
a
n
d
loading
l
o
a
d
i
n
g
data.
d
a
t
a
.
The
T
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
complete
c
o
m
p
l
e
t
e
when
w
h
e
n
its
i
t
s
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
it
i
t
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
should
s
h
o
u
l
d
be
b
e
generated
g
e
n
e
r
a
t
e
d
from
f
r
o
m
the
t
h
e
Source
S
o
u
r
c
e
and
a
n
d
linking
l
i
n
k
i
n
g
and
a
n
d
loading
l
o
a
d
i
n
g
data.
d
a
t
a
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
be
b
e
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
for
f
o
r
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration.
i
n
t
e
g
r
a
t
i
o
n
.
-
Inadequate
I
n
a
d
e
q
u
a
t
e
or
o
r
incorrect
i
n
c
o
r
r
e
c
t
inputs
i
n
p
u
t
s
detected
d
e
t
e
c
t
e
d
during
d
u
r
i
n
g
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
or
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
as
a
s
feedback
f
e
e
d
b
a
c
k
for
f
o
r
clarification
c
l
a
r
i
f
i
c
a
t
i
o
n
or
o
r
correction.
c
o
r
r
e
c
t
i
o
n
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
23
2
3
5.4.3
5
.
4
.
3
Integration
I
n
t
e
g
r
a
t
i
o
n
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
5.5
5
.
5
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
The
T
h
e
following
f
o
l
l
o
w
i
n
g
are
a
r
e
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
and
a
n
d
software
s
o
f
t
w
a
r
e
patches.
p
a
t
c
h
e
s
.
An
A
n
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
may
m
a
y
be
b
e
designed
d
e
s
i
g
n
e
d
to
t
o
include
i
n
c
l
u
d
e
several
s
e
v
e
r
a
l
configurations,
c
o
n
f
i
g
u
r
a
t
i
o
n
s
,
not
n
o
t
all
a
l
l
of
o
f
which
w
h
i
c
h
are
a
r
e
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
used
u
s
e
d
in
i
n
every
e
v
e
r
y
application.
a
p
p
l
i
c
a
t
i
o
n
.
This
T
h
i
s
can
c
a
n
lead
l
e
a
d
to
t
o
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
that
t
h
a
t
cannot
c
a
n
n
o
t
be
b
e
executed
e
x
e
c
u
t
e
d
or
o
r
data
d
a
t
a
that
t
h
a
t
is
i
s
not
n
o
t
used.
u
s
e
d
.
This
T
h
i
s
differs
d
i
f
f
e
r
s
from
f
r
o
m
dead
d
e
a
d
code
c
o
d
e
which
w
h
i
c
h
is
i
s
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
glossary
g
l
o
s
s
a
r
y
and
a
n
d
discussed
d
i
s
c
u
s
s
e
d
in
i
n
subparagraph
s
u
b
p
a
r
a
g
r
a
p
h
6.4.4.3.
6
.
4
.
4
.
3
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
and
a
n
d
patches
p
a
t
c
h
e
s
includes:
i
n
c
l
u
d
e
s
:
-
Evidence
E
v
i
d
e
n
c
e
should
s
h
o
u
l
d
be
b
e
available
a
v
a
i
l
a
b
l
e
that
t
h
a
t
the
t
h
e
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
is
i
s
disabled
d
i
s
a
b
l
e
d
for
f
o
r
the
t
h
e
environments
e
n
v
i
r
o
n
m
e
n
t
s
where
w
h
e
r
e
its
i
t
s
use
u
s
e
is
i
s
not
n
o
t
intended.
i
n
t
e
n
d
e
d
.
Unintended
U
n
i
n
t
e
n
d
e
d
activation
a
c
t
i
v
a
t
i
o
n
of
o
f
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
due
d
u
e
to
t
o
abnormal
a
b
n
o
r
m
a
l
system
s
y
s
t
e
m
conditions
c
o
n
d
i
t
i
o
n
s
is
i
s
the
t
h
e
same
s
a
m
e
as
a
s
unintended
u
n
i
n
t
e
n
d
e
d
activation
a
c
t
i
v
a
t
i
o
n
of
o
f
activated
a
c
t
i
v
a
t
e
d
code.
c
o
d
e
.
-
The
T
h
e
methods
m
e
t
h
o
d
s
for
f
o
r
handling
h
a
n
d
l
i
n
g
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
should
s
h
o
u
l
d
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
-
Patches
P
a
t
c
h
e
s
should
s
h
o
u
l
d
not
n
o
t
be
b
e
used
u
s
e
d
in
i
n
software
s
o
f
t
w
a
r
e
submitted
s
u
b
m
i
t
t
e
d
for
f
o
r
use
u
s
e
in
i
n
a
a
certified
c
e
r
t
i
f
i
e
d
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine
e
n
g
i
n
e
to
t
o
implement
i
m
p
l
e
m
e
n
t
changes
c
h
a
n
g
e
s
in
i
n
requirements
r
e
q
u
i
r
e
m
e
n
t
s
or
o
r
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
or
o
r
changes
c
h
a
n
g
e
s
found
f
o
u
n
d
necessary
n
e
c
e
s
s
a
r
y
as
a
s
a
a
result
r
e
s
u
l
t
of
o
f
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
Patches
P
a
t
c
h
e
s
may
m
a
y
be
b
e
used
u
s
e
d
on
o
n
a
a
limited,
l
i
m
i
t
e
d
,
case-by-case
c
a
s
e
-
b
y
-
c
a
s
e
basis,
b
a
s
i
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
to
t
o
resolve
r
e
s
o
l
v
e
known
k
n
o
w
n
deficiencies
d
e
f
i
c
i
e
n
c
i
e
s
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment.
e
n
v
i
r
o
n
m
e
n
t
.
such
s
u
c
h
as
a
s
a
a
known
k
n
o
w
n
compiler
c
o
m
p
i
l
e
r
problem.
p
r
o
b
l
e
m
.
-
When
W
h
e
n
a
a
patch
p
a
t
c
h
is
i
s
used,
u
s
e
d
,
these
t
h
e
s
e
should
s
h
o
u
l
d
be
b
e
available:
a
v
a
i
l
a
b
l
e
:
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
guidance
g
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Confirmation
C
o
n
f
i
r
m
a
t
i
o
n
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process
p
r
o
c
e
s
s
can
c
a
n
effectively
e
f
f
e
c
t
i
v
e
l
y
track
t
r
a
c
k
the
t
h
e
patch.
p
a
t
c
h
.
-
Regression
R
e
g
r
e
s
s
i
o
n
analysis
a
n
a
l
y
s
i
s
to
t
o
provide
p
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
the
t
h
e
patch
p
a
t
c
h
satisfies
s
a
t
i
s
f
i
e
s
all
a
l
l
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
developed
d
e
v
e
l
o
p
e
d
by
b
y
normal
n
o
r
m
a
l
methods.
m
e
t
h
o
d
s
.
-
Justification
J
u
s
t
i
f
i
c
a
t
i
o
n
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
for
f
o
r
the
t
h
e
use
u
s
e
of
o
f
a
a
patch.
p
a
t
c
h
.
-
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
enable
e
n
a
b
l
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
complete
c
o
m
p
l
e
t
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
give
g
i
v
e
visibility
v
i
s
i
b
i
l
i
t
y
to
t
o
the
t
h
e
derived
d
e
r
i
v
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
give
g
i
v
e
visibility
v
i
s
i
b
i
l
i
t
y
to
t
o
the
t
h
e
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
design
d
e
s
i
g
n
decisions
d
e
c
i
s
i
o
n
s
made
m
a
d
e
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
and
a
n
d
allow
a
l
l
o
w
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
complete
c
o
m
p
l
e
t
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
Source
S
o
u
r
c
e
Code
C
o
d
e
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
to
t
o
enable
e
n
a
b
l
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
absence
a
b
s
e
n
c
e
of
o
f
undocumented
u
n
d
o
c
u
m
e
n
t
e
d
Source
S
o
u
r
c
e
Code
C
o
d
e
and
a
n
d
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
complete
c
o
m
p
l
e
t
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
25
2
5
6.0
6
.
0
SOFTWARE
S
O
F
T
W
A
R
E
VERIFICATION
V
E
R
I
F
I
C
A
T
I
O
N
PROCESS
P
R
O
C
E
S
S
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
Verification
V
e
r
i
f
i
c
a
t
i
o
n
is
i
s
a
a
technical
t
e
c
h
n
i
c
a
l
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
results
r
e
s
u
l
t
s
of
o
f
both
b
o
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
applied
a
p
p
l
i
e
d
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
(section
(
s
e
c
t
i
o
n
4)
4
)
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.3).
1
1
.
3
)
.
Verification
V
e
r
i
f
i
c
a
t
i
o
n
is
i
s
not
n
o
t
simply
s
i
m
p
l
y
testing.
t
e
s
t
i
n
g
.
Testing,
T
e
s
t
i
n
g
,
in
i
n
general,
g
e
n
e
r
a
l
,
cannot
c
a
n
n
o
t
show
s
h
o
w
the
t
h
e
absence
a
b
s
e
n
c
e
of
o
f
errors.
e
r
r
o
r
s
.
As
A
s
a
a
result,
r
e
s
u
l
t
,
the
t
h
e
following
f
o
l
l
o
w
i
n
g
subsections
s
u
b
s
e
c
t
i
o
n
s
use
u
s
e
the
t
h
e
term
t
e
r
m
"verify"
"
v
e
r
i
f
y
"
instead
i
n
s
t
e
a
d
of
o
f
"test"
"
t
e
s
t
"
when
w
h
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
being
b
e
i
n
g
discussed
d
i
s
c
u
s
s
e
d
are
a
r
e
typically
t
y
p
i
c
a
l
l
y
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
reviews,
r
e
v
i
e
w
s
,
analyses
a
n
a
l
y
s
e
s
and
a
n
d
test.
t
e
s
t
.
Tables
T
a
b
l
e
s
A-3
A
-
3
through
t
h
r
o
u
g
h
A-7
A
-
7
of
o
f
Annex
A
n
n
e
x
A
A
contain
c
o
n
t
a
i
n
a
a
summary
s
u
m
m
a
r
y
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process,
p
r
o
c
e
s
s
,
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
Note:
N
o
t
e
:
For
F
o
r
lower
l
o
w
e
r
software
s
o
f
t
w
a
r
e
levels,
l
e
v
e
l
s
,
less
l
e
s
s
emphasis
e
m
p
h
a
s
i
s
is
i
s
on:
o
n
:
-
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
Degree
D
e
g
r
e
e
of
o
f
test
t
e
s
t
coverage.
c
o
v
e
r
a
g
e
.
-
Control
C
o
n
t
r
o
l
of
o
f
verification
v
e
r
i
f
i
c
a
t
i
o
n
procedures.
p
r
o
c
e
d
u
r
e
s
.
-
Independence
I
n
d
e
p
e
n
d
e
n
c
e
of
o
f
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
-
Overlapping
O
v
e
r
l
a
p
p
i
n
g
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities,
a
c
t
i
v
i
t
i
e
s
,
that
t
h
a
t
is,
i
s
,
multiple
m
u
l
t
i
p
l
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
activities,
a
c
t
i
v
i
t
i
e
s
,
each
e
a
c
h
of
o
f
which
w
h
i
c
h
may
m
a
y
be
b
e
capable
c
a
p
a
b
l
e
of
o
f
detecting
d
e
t
e
c
t
i
n
g
the
t
h
e
same
s
a
m
e
class
c
l
a
s
s
of
o
f
error.
e
r
r
o
r
.
-
Robustness
R
o
b
u
s
t
n
e
s
s
testing.
t
e
s
t
i
n
g
.
-
Verification
V
e
r
i
f
i
c
a
t
i
o
n
activities
a
c
t
i
v
i
t
i
e
s
with
w
i
t
h
an
a
n
indirect
i
n
d
i
r
e
c
t
effect
e
f
f
e
c
t
on
o
n
error
e
r
r
o
r
prevention
p
r
e
v
e
n
t
i
o
n
or
o
r
detection,
d
e
t
e
c
t
i
o
n
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
conformance
c
o
n
f
o
r
m
a
n
c
e
to
t
o
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards.
s
t
a
n
d
a
r
d
s
.
6.1
6
.
1
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
to
t
o
detect
d
e
t
e
c
t
and
a
n
d
report
r
e
p
o
r
t
errors
e
r
r
o
r
s
that
t
h
a
t
may
m
a
y
have
h
a
v
e
been
b
e
e
n
introduced
i
n
t
r
o
d
u
c
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
Removal
R
e
m
o
v
a
l
of
o
f
the
t
h
e
errors
e
r
r
o
r
s
is
i
s
an
a
n
activity
a
c
t
i
v
i
t
y
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
The
T
h
e
general
g
e
n
e
r
a
l
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
are
a
r
e
to
t
o
verify
v
e
r
i
f
y
that:
t
h
a
t
:
-
The
T
h
e
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
have
h
a
v
e
been
b
e
e
n
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
satisfy
s
a
t
i
s
f
y
those
t
h
o
s
e
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
The
T
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
have
h
a
v
e
been
b
e
e
n
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
satisfy
s
a
t
i
s
f
y
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
If
I
f
one
o
n
e
or
o
r
more
m
o
r
e
levels
l
e
v
e
l
s
of
o
f
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
between
b
e
t
w
e
e
n
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
the
t
h
e
successive
s
u
c
c
e
s
s
i
v
e
levels
l
e
v
e
l
s
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
such
s
u
c
h
that
t
h
a
t
each
e
a
c
h
successively
s
u
c
c
e
s
s
i
v
e
l
y
lower
l
o
w
e
r
level
l
e
v
e
l
satisfies
s
a
t
i
s
f
i
e
s
its
i
t
s
higher
h
i
g
h
e
r
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
If
I
f
code
c
o
d
e
is
i
s
generated
g
e
n
e
r
a
t
e
d
directly
d
i
r
e
c
t
l
y
from
f
r
o
m
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
this
t
h
i
s
objective
o
b
j
e
c
t
i
v
e
does
d
o
e
s
not
n
o
t
apply.
a
p
p
l
y
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
have
h
a
v
e
been
b
e
e
n
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
Source
S
o
u
r
c
e
Code
C
o
d
e
that
t
h
a
t
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
The
T
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
The
T
h
e
means
m
e
a
n
s
used
u
s
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
these
t
h
e
s
e
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
technically
t
e
c
h
n
i
c
a
l
l
y
correct
c
o
r
r
e
c
t
and
a
n
d
complete
c
o
m
p
l
e
t
e
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
26
2
6
6.2
6
.
2
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
Software
S
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
satisfied
s
a
t
i
s
f
i
e
d
through
t
h
r
o
u
g
h
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
reviews,
r
e
v
i
e
w
s
,
analyses,
a
n
a
l
y
s
e
s
,
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
test
t
e
s
t
cases
c
a
s
e
s
and
a
n
d
procedures,
p
r
o
c
e
d
u
r
e
s
,
and
a
n
d
the
t
h
e
subsequent
s
u
b
s
e
q
u
e
n
t
execution
e
x
e
c
u
t
i
o
n
of
o
f
those
t
h
o
s
e
test
t
e
s
t
procedures.
p
r
o
c
e
d
u
r
e
s
.
Reviews
R
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
provide
p
r
o
v
i
d
e
an
a
n
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
accuracy,
a
c
c
u
r
a
c
y
,
completeness,
c
o
m
p
l
e
t
e
n
e
s
s
,
and
a
n
d
verifiability
v
e
r
i
f
i
a
b
i
l
i
t
y
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
and
a
n
d
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
The
T
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
test
t
e
s
t
cases
c
a
s
e
s
may
m
a
y
provide
p
r
o
v
i
d
e
further
f
u
r
t
h
e
r
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
internal
i
n
t
e
r
n
a
l
consistency
c
o
n
s
i
s
t
e
n
c
y
and
a
n
d
completeness
c
o
m
p
l
e
t
e
n
e
s
s
of
o
f
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
execution
e
x
e
c
u
t
i
o
n
of
o
f
the
t
h
e
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
provides
p
r
o
v
i
d
e
s
a
a
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
inputs
i
n
p
u
t
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
include
i
n
c
l
u
d
e
the
t
h
e
system
s
y
s
t
e
m
require
r
e
q
u
i
r
e
ments,
m
e
n
t
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
traceability
t
r
a
c
e
a
b
i
l
i
t
y
data,
d
a
t
a
,
Source
S
o
u
r
c
e
Code,
C
o
d
e
,
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code,
C
o
d
e
,
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan.
P
l
a
n
.
The
T
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
are
a
r
e
recorded
r
e
c
o
r
d
e
d
in
i
n
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Cases
C
a
s
e
s
and
a
n
d
Procedures
P
r
o
c
e
d
u
r
e
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.13)
1
1
.
1
3
)
and
a
n
d
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results
R
e
s
u
l
t
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.14).
1
1
.
1
4
)
.
The
T
h
e
need
n
e
e
d
for
f
o
r
the
t
h
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
be
b
e
verifiable
v
e
r
i
f
i
a
b
l
e
once
o
n
c
e
they
t
h
e
y
have
h
a
v
e
been
b
e
e
n
implemented
i
m
p
l
e
m
e
n
t
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
may
m
a
y
itself
i
t
s
e
l
f
impose
i
m
p
o
s
e
additional
a
d
d
i
t
i
o
n
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
or
o
r
constraints
c
o
n
s
t
r
a
i
n
t
s
on
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
The
T
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
provides
p
r
o
v
i
d
e
s
traceability
t
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
those
t
h
o
s
e
software
s
o
f
t
w
a
r
e
requirements:
r
e
q
u
i
r
e
m
e
n
t
s
:
-
The
T
h
e
traceability
t
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
test
t
e
s
t
cases
c
a
s
e
s
is
i
s
accomplished
a
c
c
o
m
p
l
i
s
h
e
d
by
b
y
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
analysis.
a
n
a
l
y
s
i
s
.
-
The
T
h
e
traceability
t
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
the
t
h
e
code
c
o
d
e
structure
s
t
r
u
c
t
u
r
e
and
a
n
d
the
t
h
e
test
t
e
s
t
cases
c
a
s
e
s
is
i
s
accomplished
a
c
c
o
m
p
l
i
s
h
e
d
by
b
y
the
t
h
e
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis.
a
n
a
l
y
s
i
s
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
activities
a
c
t
i
v
i
t
i
e
s
includes:
i
n
c
l
u
d
e
s
:
-
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
traceability
t
r
a
c
e
a
b
i
l
i
t
y
to
t
o
those
t
h
o
s
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
verified.
v
e
r
i
f
i
e
d
.
-
The
T
h
e
results
r
e
s
u
l
t
s
of
o
f
the
t
h
e
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analyses
a
n
a
l
y
s
e
s
and
a
n
d
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
and
a
n
d
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analyses
a
n
a
l
y
s
e
s
should
s
h
o
u
l
d
show
s
h
o
w
that
t
h
a
t
each
e
a
c
h
software
s
o
f
t
w
a
r
e
requirement
r
e
q
u
i
r
e
m
e
n
t
is
i
s
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
code
c
o
d
e
that
t
h
a
t
implements
i
m
p
l
e
m
e
n
t
s
it
i
t
and
a
n
d
to
t
o
the
t
h
e
review,
r
e
v
i
e
w
,
analysis,
a
n
a
l
y
s
i
s
,
or
o
r
test
t
e
s
t
case
c
a
s
e
that
t
h
a
t
verifies
v
e
r
i
f
i
e
s
it.
i
t
.
-
If
I
f
the
t
h
e
code
c
o
d
e
tested
t
e
s
t
e
d
is
i
s
not
n
o
t
identical
i
d
e
n
t
i
c
a
l
to
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software,
s
o
f
t
w
a
r
e
,
those
t
h
o
s
e
differences
d
i
f
f
e
r
e
n
c
e
s
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
and
a
n
d
justified.
j
u
s
t
i
f
i
e
d
.
-
When
W
h
e
n
it
i
t
is
i
s
not
n
o
t
possible
p
o
s
s
i
b
l
e
to
t
o
verify
v
e
r
i
f
y
specific
s
p
e
c
i
f
i
c
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
by
b
y
exercising
e
x
e
r
c
i
s
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
in
i
n
a
a
realistic
r
e
a
l
i
s
t
i
c
test
t
e
s
t
environment,
e
n
v
i
r
o
n
m
e
n
t
,
other
o
t
h
e
r
means
m
e
a
n
s
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
and
a
n
d
their
t
h
e
i
r
justification
j
u
s
t
i
f
i
c
a
t
i
o
n
for
f
o
r
satisfying
s
a
t
i
s
f
y
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
or
o
r
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results.
R
e
s
u
l
t
s
.
-
Deficiencies
D
e
f
i
c
i
e
n
c
i
e
s
and
a
n
d
errors
e
r
r
o
r
s
discovered
d
i
s
c
o
v
e
r
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
reported
r
e
p
o
r
t
e
d
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
clarification
c
l
a
r
i
f
i
c
a
t
i
o
n
and
a
n
d
correction.
c
o
r
r
e
c
t
i
o
n
.
6.3
6
.
3
Software
S
o
f
t
w
a
r
e
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
Reviews
R
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
are
a
r
e
applied
a
p
p
l
i
e
d
to
t
o
the
t
h
e
results
r
e
s
u
l
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
One
O
n
e
distinction
d
i
s
t
i
n
c
t
i
o
n
between
b
e
t
w
e
e
n
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
is
i
s
that
t
h
a
t
analyses
a
n
a
l
y
s
e
s
provide
p
r
o
v
i
d
e
repeatable
r
e
p
e
a
t
a
b
l
e
evidence
e
v
i
d
e
n
c
e
of
o
f
correctness
c
o
r
r
e
c
t
n
e
s
s
and
a
n
d
reviews
r
e
v
i
e
w
s
provide
p
r
o
v
i
d
e
a
a
qualitative
q
u
a
l
i
t
a
t
i
v
e
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
correctness.
c
o
r
r
e
c
t
n
e
s
s
.
A
A
review
r
e
v
i
e
w
may
m
a
y
consist
c
o
n
s
i
s
t
of
o
f
an
a
n
inspection
i
n
s
p
e
c
t
i
o
n
of
o
f
an
a
n
output
o
u
t
p
u
t
of
o
f
a
a
process
p
r
o
c
e
s
s
guided
g
u
i
d
e
d
by
b
y
a
a
checklist
c
h
e
c
k
l
i
s
t
or
o
r
similar
s
i
m
i
l
a
r
aid.
a
i
d
.
An
A
n
analysis
a
n
a
l
y
s
i
s
may
m
a
y
examine
e
x
a
m
i
n
e
in
i
n
detail
d
e
t
a
i
l
the
t
h
e
functionality,
f
u
n
c
t
i
o
n
a
l
i
t
y
,
performance,
p
e
r
f
o
r
m
a
n
c
e
,
traceability
t
r
a
c
e
a
b
i
l
i
t
y
and
a
n
d
safety
s
a
f
e
t
y
implications
i
m
p
l
i
c
a
t
i
o
n
s
of
o
f
a
a
software
s
o
f
t
w
a
r
e
component,
c
o
m
p
o
n
e
n
t
,
and
a
n
d
its
i
t
s
relationship
r
e
l
a
t
i
o
n
s
h
i
p
to
t
o
other
o
t
h
e
r
components
c
o
m
p
o
n
e
n
t
s
within
w
i
t
h
i
n
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
6.3.1
6
.
3
.
1
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
High-Level
H
i
g
h
-
L
e
v
e
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
these
t
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
is
i
s
to
t
o
detect
d
e
t
e
c
t
and
a
n
d
report
r
e
p
o
r
t
requirements
r
e
q
u
i
r
e
m
e
n
t
s
errors
e
r
r
o
r
s
that
t
h
a
t
may
m
a
y
have
h
a
v
e
been
b
e
e
n
introduced
i
n
t
r
o
d
u
c
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process.
p
r
o
c
e
s
s
.
These
T
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
confirm
c
o
n
f
i
r
m
that
t
h
a
t
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
satisfy
s
a
t
i
s
f
y
these
t
h
e
s
e
objectives:
o
b
j
e
c
t
i
v
e
s
:
-
Compliance
C
o
m
p
l
i
a
n
c
e
with
w
i
t
h
system
s
y
s
t
e
m
requirements:
r
e
q
u
i
r
e
m
e
n
t
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
system
s
y
s
t
e
m
functions
f
u
n
c
t
i
o
n
s
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
are
a
r
e
defined,
d
e
f
i
n
e
d
,
that
t
h
a
t
the
t
h
e
functional,
f
u
n
c
t
i
o
n
a
l
,
performance,
p
e
r
f
o
r
m
a
n
c
e
,
and
a
n
d
safety-
s
a
f
e
t
y
-
related
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
are
a
r
e
satisfied
s
a
t
i
s
f
i
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
that
t
h
a
t
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
reason
r
e
a
s
o
n
for
f
o
r
their
t
h
e
i
r
existence
e
x
i
s
t
e
n
c
e
are
a
r
e
correctly
c
o
r
r
e
c
t
l
y
defined.
d
e
f
i
n
e
d
.
-
Accuracy
A
c
c
u
r
a
c
y
and
a
n
d
consistency:
c
o
n
s
i
s
t
e
n
c
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
each
e
a
c
h
high-level
h
i
g
h
-
l
e
v
e
l
requirement
r
e
q
u
i
r
e
m
e
n
t
is
i
s
accurate,
a
c
c
u
r
a
t
e
,
unambiguous
u
n
a
m
b
i
g
u
o
u
s
and
a
n
d
sufficiently
s
u
f
f
i
c
i
e
n
t
l
y
detailed
d
e
t
a
i
l
e
d
and
a
n
d
that
t
h
a
t
the
t
h
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
do
d
o
not
n
o
t
conflict
c
o
n
f
l
i
c
t
with
w
i
t
h
each
e
a
c
h
other.
o
t
h
e
r
.
-
Compatibility
C
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
the
t
h
e
target
t
a
r
g
e
t
computer:
c
o
m
p
u
t
e
r
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
no
n
o
conflicts
c
o
n
f
l
i
c
t
s
exist
e
x
i
s
t
between
b
e
t
w
e
e
n
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
features
f
e
a
t
u
r
e
s
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer,
c
o
m
p
u
t
e
r
,
especially,
e
s
p
e
c
i
a
l
l
y
,
system
s
y
s
t
e
m
response
r
e
s
p
o
n
s
e
times
t
i
m
e
s
and
a
n
d
input/output
i
n
p
u
t
/
o
u
t
p
u
t
hardware.
h
a
r
d
w
a
r
e
.
-
Verifiability:
V
e
r
i
f
i
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
each
e
a
c
h
high-level
h
i
g
h
-
l
e
v
e
l
requirement
r
e
q
u
i
r
e
m
e
n
t
can
c
a
n
be
b
e
verified.
v
e
r
i
f
i
e
d
.
-
Conformance
C
o
n
f
o
r
m
a
n
c
e
to
t
o
standards:
s
t
a
n
d
a
r
d
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
were
w
e
r
e
followed
f
o
l
l
o
w
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
and
a
n
d
that
t
h
a
t
deviations
d
e
v
i
a
t
i
o
n
s
from
f
r
o
m
the
t
h
e
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
justified.
j
u
s
t
i
f
i
e
d
.
-
Traceability:
T
r
a
c
e
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
functional,
f
u
n
c
t
i
o
n
a
l
,
performance,
p
e
r
f
o
r
m
a
n
c
e
,
and
a
n
d
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
that
t
h
a
t
are
a
r
e
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
were
w
e
r
e
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Algorithm
A
l
g
o
r
i
t
h
m
aspects
a
s
p
e
c
t
s
:
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
the
t
h
e
accuracy
a
c
c
u
r
a
c
y
and
a
n
d
behavior
b
e
h
a
v
i
o
r
of
o
f
the
t
h
e
proposed
p
r
o
p
o
s
e
d
algorithms,
a
l
g
o
r
i
t
h
m
s
,
especially
e
s
p
e
c
i
a
l
l
y
in
i
n
the
t
h
e
area
a
r
e
a
of
o
f
discontinuities.
d
i
s
c
o
n
t
i
n
u
i
t
i
e
s
.
6.3.2
6
.
3
.
2
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Low-Level
L
o
w
-
L
e
v
e
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
these
t
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
is
i
s
to
t
o
detect
d
e
t
e
c
t
and
a
n
d
report
r
e
p
o
r
t
requirements
r
e
q
u
i
r
e
m
e
n
t
s
errors
e
r
r
o
r
s
that
t
h
a
t
may
m
a
y
have
h
a
v
e
been
b
e
e
n
introduced
i
n
t
r
o
d
u
c
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process.
p
r
o
c
e
s
s
.
These
T
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
confirm
c
o
n
f
i
r
m
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
satisfy
s
a
t
i
s
f
y
these
t
h
e
s
e
objectives:
o
b
j
e
c
t
i
v
e
s
:
-
Compliance
C
o
m
p
l
i
a
n
c
e
with
w
i
t
h
high-level
h
i
g
h
-
l
e
v
e
l
requirements:
r
e
q
u
i
r
e
m
e
n
t
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
low-
l
o
w
-
level
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
that
t
h
a
t
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
design
d
e
s
i
g
n
basis
b
a
s
i
s
for
f
o
r
their
t
h
e
i
r
existence
e
x
i
s
t
e
n
c
e
are
a
r
e
correctly
c
o
r
r
e
c
t
l
y
defined.
d
e
f
i
n
e
d
.
-
Accuracy
A
c
c
u
r
a
c
y
and
a
n
d
consistency:
c
o
n
s
i
s
t
e
n
c
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
each
e
a
c
h
low-level
l
o
w
-
l
e
v
e
l
requirement
r
e
q
u
i
r
e
m
e
n
t
is
i
s
accurate
a
c
c
u
r
a
t
e
and
a
n
d
unambiguous
u
n
a
m
b
i
g
u
o
u
s
and
a
n
d
that
t
h
a
t
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
do
d
o
not
n
o
t
conflict
c
o
n
f
l
i
c
t
with
w
i
t
h
each
e
a
c
h
other.
o
t
h
e
r
.
-
Compatibility
C
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
the
t
h
e
target
t
a
r
g
e
t
computer:
c
o
m
p
u
t
e
r
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
no
n
o
conflicts
c
o
n
f
l
i
c
t
s
exist
e
x
i
s
t
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
features
f
e
a
t
u
r
e
s
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer,
c
o
m
p
u
t
e
r
,
especially,
e
s
p
e
c
i
a
l
l
y
,
the
t
h
e
use
u
s
e
of
o
f
resources
r
e
s
o
u
r
c
e
s
(such
(
s
u
c
h
as
a
s
bus
b
u
s
loading),
l
o
a
d
i
n
g
)
,
system
s
y
s
t
e
m
response
r
e
s
p
o
n
s
e
times,
t
i
m
e
s
,
and
a
n
d
input/output
i
n
p
u
t
/
o
u
t
p
u
t
hardware.
h
a
r
d
w
a
r
e
.
-
Verifiability:
V
e
r
i
f
i
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
each
e
a
c
h
low-level
l
o
w
-
l
e
v
e
l
requirement
r
e
q
u
i
r
e
m
e
n
t
can
c
a
n
be
b
e
verified.
v
e
r
i
f
i
e
d
.
-
Conformance
C
o
n
f
o
r
m
a
n
c
e
to
t
o
standards:
s
t
a
n
d
a
r
d
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
were
w
e
r
e
followed
f
o
l
l
o
w
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
and
a
n
d
that
t
h
a
t
deviations
d
e
v
i
a
t
i
o
n
s
from
f
r
o
m
the
t
h
e
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
justified.
j
u
s
t
i
f
i
e
d
.
-
Traceability:
T
r
a
c
e
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
were
w
e
r
e
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Algorithm
A
l
g
o
r
i
t
h
m
aspects
a
s
p
e
c
t
s
:
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
the
t
h
e
accuracy
a
c
c
u
r
a
c
y
and
a
n
d
behavior
b
e
h
a
v
i
o
r
of
o
f
the
t
h
e
proposed
p
r
o
p
o
s
e
d
algorithms,
a
l
g
o
r
i
t
h
m
s
,
especially
e
s
p
e
c
i
a
l
l
y
in
i
n
the
t
h
e
area
a
r
e
a
of
o
f
discontinuities.
d
i
s
c
o
n
t
i
n
u
i
t
i
e
s
.
27
2
7
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
28
2
8
6.3.3
6
.
3
.
3
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Software
S
o
f
t
w
a
r
e
Architecture
A
r
c
h
i
t
e
c
t
u
r
e
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
these
t
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
is
i
s
to
t
o
detect
d
e
t
e
c
t
and
a
n
d
report
r
e
p
o
r
t
errors
e
r
r
o
r
s
that
t
h
a
t
may
m
a
y
have
h
a
v
e
been
b
e
e
n
introduced
i
n
t
r
o
d
u
c
e
d
during
d
u
r
i
n
g
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
These
T
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
confirm
c
o
n
f
i
r
m
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
satisfies
s
a
t
i
s
f
i
e
s
these
t
h
e
s
e
objectives:
o
b
j
e
c
t
i
v
e
s
:
-
Compatibility
C
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements:
r
e
q
u
i
r
e
m
e
n
t
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
does
d
o
e
s
not
n
o
t
conflict
c
o
n
f
l
i
c
t
with
w
i
t
h
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
especially
e
s
p
e
c
i
a
l
l
y
functions
f
u
n
c
t
i
o
n
s
that
t
h
a
t
ensure
e
n
s
u
r
e
system
s
y
s
t
e
m
integrity,
i
n
t
e
g
r
i
t
y
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
schemes.
s
c
h
e
m
e
s
.
-
Consistency:
C
o
n
s
i
s
t
e
n
c
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
a
a
correct
c
o
r
r
e
c
t
relationship
r
e
l
a
t
i
o
n
s
h
i
p
exists
e
x
i
s
t
s
between
b
e
t
w
e
e
n
the
t
h
e
components
c
o
m
p
o
n
e
n
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
This
T
h
i
s
relationship
r
e
l
a
t
i
o
n
s
h
i
p
exists
e
x
i
s
t
s
via
v
i
a
data
d
a
t
a
flow
f
l
o
w
and
a
n
d
control
c
o
n
t
r
o
l
flow.
f
l
o
w
.
-
Compatibility
C
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
the
t
h
e
target
t
a
r
g
e
t
computer:
c
o
m
p
u
t
e
r
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
no
n
o
conflicts
c
o
n
f
l
i
c
t
s
exist,
e
x
i
s
t
,
especially
e
s
p
e
c
i
a
l
l
y
initialization,
i
n
i
t
i
a
l
i
z
a
t
i
o
n
,
asynchronous
a
s
y
n
c
h
r
o
n
o
u
s
operation,
o
p
e
r
a
t
i
o
n
,
synchronization
s
y
n
c
h
r
o
n
i
z
a
t
i
o
n
and
a
n
d
interrupts,
i
n
t
e
r
r
u
p
t
s
,
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
the
t
h
e
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
features
f
e
a
t
u
r
e
s
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
-
Verifiability:
V
e
r
i
f
i
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
can
c
a
n
be
b
e
verified,
v
e
r
i
f
i
e
d
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
there
t
h
e
r
e
are
a
r
e
no
n
o
unbounded
u
n
b
o
u
n
d
e
d
recursive
r
e
c
u
r
s
i
v
e
algorithms.
a
l
g
o
r
i
t
h
m
s
.
-
Conformance
C
o
n
f
o
r
m
a
n
c
e
to
t
o
standards:
s
t
a
n
d
a
r
d
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
were
w
e
r
e
followed
f
o
l
l
o
w
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
and
a
n
d
that
t
h
a
t
deviations
d
e
v
i
a
t
i
o
n
s
to
t
o
the
t
h
e
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
justified,
j
u
s
t
i
f
i
e
d
,
especially
e
s
p
e
c
i
a
l
l
y
complexity
c
o
m
p
l
e
x
i
t
y
restrictions
r
e
s
t
r
i
c
t
i
o
n
s
and
a
n
d
design
d
e
s
i
g
n
constructs
c
o
n
s
t
r
u
c
t
s
that
t
h
a
t
would
w
o
u
l
d
not
n
o
t
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
integrity:
i
n
t
e
g
r
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
breaches
b
r
e
a
c
h
e
s
are
a
r
e
prevented
p
r
e
v
e
n
t
e
d
or
o
r
isolated.
i
s
o
l
a
t
e
d
.
6.3.4
6
.
3
.
4
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
detect
d
e
t
e
c
t
and
a
n
d
report
r
e
p
o
r
t
errors
e
r
r
o
r
s
that
t
h
a
t
may
m
a
y
have
h
a
v
e
been
b
e
e
n
introduced
i
n
t
r
o
d
u
c
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process.
p
r
o
c
e
s
s
.
These
T
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
confirm
c
o
n
f
i
r
m
that
t
h
a
t
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
are
a
r
e
accurate,
a
c
c
u
r
a
t
e
,
complete
c
o
m
p
l
e
t
e
and
a
n
d
can
c
a
n
be
b
e
verified.
v
e
r
i
f
i
e
d
.
Primary
P
r
i
m
a
r
y
concerns
c
o
n
c
e
r
n
s
include
i
n
c
l
u
d
e
correctness
c
o
r
r
e
c
t
n
e
s
s
of
o
f
the
t
h
e
code
c
o
d
e
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
and
a
n
d
conformance
c
o
n
f
o
r
m
a
n
c
e
to
t
o
the
t
h
e
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards.
S
t
a
n
d
a
r
d
s
.
These
T
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
are
a
r
e
usually
u
s
u
a
l
l
y
confined
c
o
n
f
i
n
e
d
to
t
o
the
t
h
e
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
The
T
h
e
topics
t
o
p
i
c
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Compliance
C
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements:
r
e
q
u
i
r
e
m
e
n
t
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
accurate
a
c
c
u
r
a
t
e
and
a
n
d
complete
c
o
m
p
l
e
t
e
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
low-level
l
o
w
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
that
t
h
a
t
no
n
o
Source
S
o
u
r
c
e
Code
C
o
d
e
implements
i
m
p
l
e
m
e
n
t
s
an
a
n
undocumented
u
n
d
o
c
u
m
e
n
t
e
d
function.
f
u
n
c
t
i
o
n
.
-
Compliance
C
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture:
a
r
c
h
i
t
e
c
t
u
r
e
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
matches
m
a
t
c
h
e
s
the
t
h
e
data
d
a
t
a
flow
f
l
o
w
and
a
n
d
control
c
o
n
t
r
o
l
flow
f
l
o
w
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
Verifiability:
V
e
r
i
f
i
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
does
d
o
e
s
not
n
o
t
contain
c
o
n
t
a
i
n
statements
s
t
a
t
e
m
e
n
t
s
and
a
n
d
structures
s
t
r
u
c
t
u
r
e
s
that
t
h
a
t
cannot
c
a
n
n
o
t
be
b
e
verified
v
e
r
i
f
i
e
d
and
a
n
d
that
t
h
a
t
the
t
h
e
code
c
o
d
e
does
d
o
e
s
not
n
o
t
have
h
a
v
e
to
t
o
be
b
e
altered
a
l
t
e
r
e
d
to
t
o
test
t
e
s
t
it.
i
t
.
-
Conformance
C
o
n
f
o
r
m
a
n
c
e
to
t
o
standards:
s
t
a
n
d
a
r
d
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
were
w
e
r
e
followed
f
o
l
l
o
w
e
d
during
d
u
r
i
n
g
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
code,
c
o
d
e
,
especially
e
s
p
e
c
i
a
l
l
y
complexity
c
o
m
p
l
e
x
i
t
y
restrictions
r
e
s
t
r
i
c
t
i
o
n
s
and
a
n
d
code
c
o
d
e
constraints
c
o
n
s
t
r
a
i
n
t
s
that
t
h
a
t
would
w
o
u
l
d
be
b
e
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
Complexity
C
o
m
p
l
e
x
i
t
y
includes
i
n
c
l
u
d
e
s
the
t
h
e
degree
d
e
g
r
e
e
of
o
f
coupling
c
o
u
p
l
i
n
g
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
components,
c
o
m
p
o
n
e
n
t
s
,
the
t
h
e
nesting
n
e
s
t
i
n
g
levels
l
e
v
e
l
s
for
f
o
r
control
c
o
n
t
r
o
l
structures,
s
t
r
u
c
t
u
r
e
s
,
and
a
n
d
the
t
h
e
complexity
c
o
m
p
l
e
x
i
t
y
of
o
f
logical
l
o
g
i
c
a
l
or
o
r
numeric
n
u
m
e
r
i
c
expressions.
e
x
p
r
e
s
s
i
o
n
s
.
This
T
h
i
s
analysis
a
n
a
l
y
s
i
s
also
a
l
s
o
ensures
e
n
s
u
r
e
s
that
t
h
a
t
deviations
d
e
v
i
a
t
i
o
n
s
to
t
o
the
t
h
e
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
justified.
j
u
s
t
i
f
i
e
d
.
-
Traceability:
T
r
a
c
e
a
b
i
l
i
t
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
were
w
e
r
e
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
-
Accuracy
A
c
c
u
r
a
c
y
and
a
n
d
consistency:
c
o
n
s
i
s
t
e
n
c
y
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
correctness
c
o
r
r
e
c
t
n
e
s
s
and
a
n
d
consistency
c
o
n
s
i
s
t
e
n
c
y
of
o
f
the
t
h
e
Source
S
o
u
r
c
e
Code,
C
o
d
e
,
including
i
n
c
l
u
d
i
n
g
stack
s
t
a
c
k
usage,
u
s
a
g
e
,
fixed
f
i
x
e
d
point
p
o
i
n
t
arithmetic
a
r
i
t
h
m
e
t
i
c
overflow
o
v
e
r
f
l
o
w
and
a
n
d
resolution,
r
e
s
o
l
u
t
i
o
n
,
resource
r
e
s
o
u
r
c
e
contention,
c
o
n
t
e
n
t
i
o
n
,
worst-case
w
o
r
s
t
-
c
a
s
e
execution
e
x
e
c
u
t
i
o
n
timing,
t
i
m
i
n
g
,
exception
e
x
c
e
p
t
i
o
n
handling,
h
a
n
d
l
i
n
g
,
use
u
s
e
of
o
f
uninitialized
u
n
i
n
i
t
i
a
l
i
z
e
d
variables
v
a
r
i
a
b
l
e
s
or
o
r
constants,
c
o
n
s
t
a
n
t
s
,
unused
u
n
u
s
e
d
variables
v
a
r
i
a
b
l
e
s
or
o
r
constants,
c
o
n
s
t
a
n
t
s
,
and
a
n
d
data
d
a
t
a
corruption
c
o
r
r
u
p
t
i
o
n
due
d
u
e
to
t
o
task
t
a
s
k
or
o
r
interrupt
i
n
t
e
r
r
u
p
t
conflicts.
c
o
n
f
l
i
c
t
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
6.3.5
6
.
3
.
5
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Outputs
O
u
t
p
u
t
s
of
o
f
the
t
h
e
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
results
r
e
s
u
l
t
s
of
o
f
the
t
h
e
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
are
a
r
e
complete
c
o
m
p
l
e
t
e
and
a
n
d
correct.
c
o
r
r
e
c
t
.
This
T
h
i
s
could
c
o
u
l
d
be
b
e
performed
p
e
r
f
o
r
m
e
d
by
b
y
a
a
detailed
d
e
t
a
i
l
e
d
examination
e
x
a
m
i
n
a
t
i
o
n
of
o
f
the
t
h
e
linking
l
i
n
k
i
n
g
and
a
n
d
loading
l
o
a
d
i
n
g
data
d
a
t
a
and
a
n
d
memory
m
e
m
o
r
y
map.
m
a
p
.
The
T
h
e
topics
t
o
p
i
c
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Incorrect
I
n
c
o
r
r
e
c
t
hardware
h
a
r
d
w
a
r
e
addresses.
a
d
d
r
e
s
s
e
s
.
-
Memory
M
e
m
o
r
y
overlaps.
o
v
e
r
l
a
p
s
.
-
Missing
M
i
s
s
i
n
g
software
s
o
f
t
w
a
r
e
components.
c
o
m
p
o
n
e
n
t
s
.
6.3.6
6
.
3
.
6
Reviews
R
e
v
i
e
w
s
and
a
n
d
Analyses
A
n
a
l
y
s
e
s
of
o
f
the
t
h
e
Test
T
e
s
t
Cases,
C
a
s
e
s
,
Procedures
P
r
o
c
e
d
u
r
e
s
and
a
n
d
Results
R
e
s
u
l
t
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
these
t
h
e
s
e
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
testing
t
e
s
t
i
n
g
of
o
f
the
t
h
e
code
c
o
d
e
was
w
a
s
developed
d
e
v
e
l
o
p
e
d
and
a
n
d
performed
p
e
r
f
o
r
m
e
d
accurately
a
c
c
u
r
a
t
e
l
y
and
a
n
d
completely.
c
o
m
p
l
e
t
e
l
y
.
The
T
h
e
topics
t
o
p
i
c
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Test
T
e
s
t
cases
c
a
s
e
s
:
:
The
T
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
test
t
e
s
t
cases
c
a
s
e
s
is
i
s
presented
p
r
e
s
e
n
t
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
6.4.4.
6
.
4
.
4
.
-
Test
T
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
:
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
verify
v
e
r
i
f
y
that
t
h
a
t
the
t
h
e
test
t
e
s
t
cases
c
a
s
e
s
were
w
e
r
e
accurately
a
c
c
u
r
a
t
e
l
y
developed
d
e
v
e
l
o
p
e
d
into
i
n
t
o
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
and
a
n
d
expected
e
x
p
e
c
t
e
d
results.
r
e
s
u
l
t
s
.
-
Test
T
e
s
t
results:
r
e
s
u
l
t
s
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
test
t
e
s
t
results
r
e
s
u
l
t
s
are
a
r
e
correct
c
o
r
r
e
c
t
and
a
n
d
that
t
h
a
t
discrepancies
d
i
s
c
r
e
p
a
n
c
i
e
s
between
b
e
t
w
e
e
n
actual
a
c
t
u
a
l
and
a
n
d
expected
e
x
p
e
c
t
e
d
results
r
e
s
u
l
t
s
are
a
r
e
explained.
e
x
p
l
a
i
n
e
d
.
6.4
6
.
4
Software
S
o
f
t
w
a
r
e
Testing
T
e
s
t
i
n
g
Process
P
r
o
c
e
s
s
Testing
T
e
s
t
i
n
g
of
o
f
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
has
h
a
s
two
t
w
o
complementary
c
o
m
p
l
e
m
e
n
t
a
r
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
One
O
n
e
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
satisfies
s
a
t
i
s
f
i
e
s
its
i
t
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
second
s
e
c
o
n
d
objective
o
b
j
e
c
t
i
v
e
is
i
s
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
with
w
i
t
h
a
a
high
h
i
g
h
degree
d
e
g
r
e
e
of
o
f
confidence
c
o
n
f
i
d
e
n
c
e
that
t
h
a
t
errors
e
r
r
o
r
s
which
w
h
i
c
h
could
c
o
u
l
d
lead
l
e
a
d
to
t
o
unacceptable
u
n
a
c
c
e
p
t
a
b
l
e
failure
f
a
i
l
u
r
e
conditions,
c
o
n
d
i
t
i
o
n
s
,
as
a
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
have
h
a
v
e
been
b
e
e
n
removed.
r
e
m
o
v
e
d
.
Figure
F
i
g
u
r
e
6-1
6
-
1
is
i
s
a
a
diagram
d
i
a
g
r
a
m
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
testing
t
e
s
t
i
n
g
process.
p
r
o
c
e
s
s
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
three
t
h
r
e
e
types
t
y
p
e
s
of
o
f
testing
t
e
s
t
i
n
g
in
i
n
the
t
h
e
figure
f
i
g
u
r
e
are:
a
r
e
:
-
Hardware/software
H
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing:
t
e
s
t
i
n
g
:
To
T
o
verify
v
e
r
i
f
y
correct
c
o
r
r
e
c
t
operation
o
p
e
r
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
in
i
n
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
Software
S
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing:
t
e
s
t
i
n
g
:
To
T
o
verify
v
e
r
i
f
y
the
t
h
e
interrelationships
i
n
t
e
r
r
e
l
a
t
i
o
n
s
h
i
p
s
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
components
c
o
m
p
o
n
e
n
t
s
and
a
n
d
to
t
o
verify
v
e
r
i
f
y
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
within
w
i
t
h
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
Low-level
L
o
w
-
l
e
v
e
l
testing:
t
e
s
t
i
n
g
:
To
T
o
verify
v
e
r
i
f
y
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Note:
N
o
t
e
:
If
I
f
a
a
test
t
e
s
t
case
c
a
s
e
and
a
n
d
its
i
t
s
corresponding
c
o
r
r
e
s
p
o
n
d
i
n
g
test
t
e
s
t
procedure
p
r
o
c
e
d
u
r
e
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
and
a
n
d
executed
e
x
e
c
u
t
e
d
for
f
o
r
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing
t
e
s
t
i
n
g
or
o
r
software
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing
t
e
s
t
i
n
g
and
a
n
d
satisfy
s
a
t
i
s
f
y
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
and
a
n
d
structural
s
t
r
u
c
t
u
r
a
l
coverage,
c
o
v
e
r
a
g
e
,
it
i
t
is
i
s
not
n
o
t
necessary
n
e
c
e
s
s
a
r
y
to
t
o
duplicate
d
u
p
l
i
c
a
t
e
the
t
h
e
test
t
e
s
t
for
f
o
r
low-level
l
o
w
-
l
e
v
e
l
testing.
t
e
s
t
i
n
g
.
Substituting
S
u
b
s
t
i
t
u
t
i
n
g
nominally
n
o
m
i
n
a
l
l
y
equivalent
e
q
u
i
v
a
l
e
n
t
low-level
l
o
w
-
l
e
v
e
l
tests
t
e
s
t
s
for
f
o
r
high-level
h
i
g
h
-
l
e
v
e
l
tests
t
e
s
t
s
may
m
a
y
be
b
e
less
l
e
s
s
effective
e
f
f
e
c
t
i
v
e
due
d
u
e
to
t
o
the
t
h
e
reduced
r
e
d
u
c
e
d
amount
a
m
o
u
n
t
of
o
f
overall
o
v
e
r
a
l
l
functionality
f
u
n
c
t
i
o
n
a
l
i
t
y
tested.
t
e
s
t
e
d
.
To
T
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
testing
t
e
s
t
i
n
g
objectives:
o
b
j
e
c
t
i
v
e
s
:
-
Test
T
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
based
b
a
s
e
d
primarily
p
r
i
m
a
r
i
l
y
on
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Test
T
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
verify
v
e
r
i
f
y
correct
c
o
r
r
e
c
t
functionality
f
u
n
c
t
i
o
n
a
l
i
t
y
and
a
n
d
to
t
o
establish
e
s
t
a
b
l
i
s
h
conditions
c
o
n
d
i
t
i
o
n
s
that
t
h
a
t
reveal
r
e
v
e
a
l
potential
p
o
t
e
n
t
i
a
l
errors.
e
r
r
o
r
s
.
-
Software
S
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
determine
d
e
t
e
r
m
i
n
e
what
w
h
a
t
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
were
w
e
r
e
not
n
o
t
tested.
t
e
s
t
e
d
.
-
Structural
S
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
determine
d
e
t
e
r
m
i
n
e
what
w
h
a
t
software
s
o
f
t
w
a
r
e
structures
s
t
r
u
c
t
u
r
e
s
were
w
e
r
e
not
n
o
t
exerc
e
x
e
r
c
ised.
i
s
e
d
.
29
2
9
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
30
3
0
6.4.1
6
.
4
.
1
Test
T
e
s
t
Environment
E
n
v
i
r
o
n
m
e
n
t
FIGURE
F
I
G
U
R
E
6-1
6
-
1
SOFTWARE
S
O
F
T
W
A
R
E
TESTING
T
E
S
T
I
N
G
PROCESS
P
R
O
C
E
S
S
More
M
o
r
e
than
t
h
a
n
one
o
n
e
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
may
m
a
y
be
b
e
needed
n
e
e
d
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
testing.
t
e
s
t
i
n
g
.
An
A
n
excellent
e
x
c
e
l
l
e
n
t
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
includes
i
n
c
l
u
d
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
and
a
n
d
tested
t
e
s
t
e
d
in
i
n
a
a
high
h
i
g
h
fidelity
f
i
d
e
l
i
t
y
simulation
s
i
m
u
l
a
t
i
o
n
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment.
e
n
v
i
r
o
n
m
e
n
t
.
Note:
N
o
t
e
:
In
I
n
many
m
a
n
y
cases,
c
a
s
e
s
,
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
and
a
n
d
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
necessary
n
e
c
e
s
s
a
r
y
can
c
a
n
be
b
e
achieved
a
c
h
i
e
v
e
d
only
o
n
l
y
with
w
i
t
h
more
m
o
r
e
precise
p
r
e
c
i
s
e
control
c
o
n
t
r
o
l
and
a
n
d
monitoring
m
o
n
i
t
o
r
i
n
g
of
o
f
the
t
h
e
test
t
e
s
t
inputs
i
n
p
u
t
s
and
a
n
d
code
c
o
d
e
execution
e
x
e
c
u
t
i
o
n
than
t
h
a
n
generally
g
e
n
e
r
a
l
l
y
possible
p
o
s
s
i
b
l
e
in
i
n
a
a
fully
f
u
l
l
y
integrated
i
n
t
e
g
r
a
t
e
d
environment.
e
n
v
i
r
o
n
m
e
n
t
.
Such
S
u
c
h
testing
t
e
s
t
i
n
g
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
on
o
n
a
a
small
s
m
a
l
l
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
that
t
h
a
t
is
i
s
functionally
f
u
n
c
t
i
o
n
a
l
l
y
isolated
i
s
o
l
a
t
e
d
from
f
r
o
m
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
components.
c
o
m
p
o
n
e
n
t
s
.
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
may
m
a
y
be
b
e
given
g
i
v
e
n
for
f
o
r
testing
t
e
s
t
i
n
g
done
d
o
n
e
using
u
s
i
n
g
a
a
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
emulator
e
m
u
l
a
t
o
r
or
o
r
a
a
host
h
o
s
t
computer
c
o
m
p
u
t
e
r
simulator.
s
i
m
u
l
a
t
o
r
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
includes:
i
n
c
l
u
d
e
s
:
-
Selected
S
e
l
e
c
t
e
d
tests
t
e
s
t
s
should
s
h
o
u
l
d
be
b
e
performed
p
e
r
f
o
r
m
e
d
in
i
n
the
t
h
e
integrated
i
n
t
e
g
r
a
t
e
d
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment,
e
n
v
i
r
o
n
m
e
n
t
,
since
s
i
n
c
e
some
s
o
m
e
errors
e
r
r
o
r
s
are
a
r
e
only
o
n
l
y
detected
d
e
t
e
c
t
e
d
in
i
n
this
t
h
i
s
environment.
e
n
v
i
r
o
n
m
e
n
t
.
6.4.2
6
.
4
.
2
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Test
T
e
s
t
Case
C
a
s
e
Selection
S
e
l
e
c
t
i
o
n
Requirements-based
R
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
testing
t
e
s
t
i
n
g
is
i
s
emphasized
e
m
p
h
a
s
i
z
e
d
because
b
e
c
a
u
s
e
this
t
h
i
s
strategy
s
t
r
a
t
e
g
y
has
h
a
s
been
b
e
e
n
found
f
o
u
n
d
to
t
o
be
b
e
the
t
h
e
most
m
o
s
t
effective
e
f
f
e
c
t
i
v
e
at
a
t
revealing
r
e
v
e
a
l
i
n
g
errors.
e
r
r
o
r
s
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
case
c
a
s
e
selection
s
e
l
e
c
t
i
o
n
includes:
i
n
c
l
u
d
e
s
:
-
To
T
o
implement
i
m
p
l
e
m
e
n
t
the
t
h
e
software
s
o
f
t
w
a
r
e
testing
t
e
s
t
i
n
g
objectives,
o
b
j
e
c
t
i
v
e
s
,
two
t
w
o
categories
c
a
t
e
g
o
r
i
e
s
of
o
f
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
included:
i
n
c
l
u
d
e
d
:
normal
n
o
r
m
a
l
range
r
a
n
g
e
test
t
e
s
t
cases
c
a
s
e
s
and
a
n
d
robustness
r
o
b
u
s
t
n
e
s
s
(abnormal
(
a
b
n
o
r
m
a
l
range)
r
a
n
g
e
)
test
t
e
s
t
cases.
c
a
s
e
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
31
3
1
-
The
T
h
e
specific
s
p
e
c
i
f
i
c
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
error
e
r
r
o
r
sources
s
o
u
r
c
e
s
inherent
i
n
h
e
r
e
n
t
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
6.4.2.1
6
.
4
.
2
.
1
Normal
N
o
r
m
a
l
Range
R
a
n
g
e
Test
T
e
s
t
Cases
C
a
s
e
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
normal
n
o
r
m
a
l
range
r
a
n
g
e
test
t
e
s
t
cases
c
a
s
e
s
is
i
s
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
the
t
h
e
ability
a
b
i
l
i
t
y
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
to
t
o
respond
r
e
s
p
o
n
d
to
t
o
normal
n
o
r
m
a
l
inputs
i
n
p
u
t
s
and
a
n
d
conditions.
c
o
n
d
i
t
i
o
n
s
.
Normal
N
o
r
m
a
l
range
r
a
n
g
e
test
t
e
s
t
cases
c
a
s
e
s
include:
i
n
c
l
u
d
e
:
-
Real
R
e
a
l
and
a
n
d
integer
i
n
t
e
g
e
r
input
i
n
p
u
t
variables
v
a
r
i
a
b
l
e
s
should
s
h
o
u
l
d
be
b
e
exercised
e
x
e
r
c
i
s
e
d
using
u
s
i
n
g
valid
v
a
l
i
d
equivalence
e
q
u
i
v
a
l
e
n
c
e
classes
c
l
a
s
s
e
s
and
a
n
d
boundary
b
o
u
n
d
a
r
y
values.
v
a
l
u
e
s
.
-
For
F
o
r
time-related
t
i
m
e
-
r
e
l
a
t
e
d
functions,
f
u
n
c
t
i
o
n
s
,
such
s
u
c
h
as
a
s
filters,
f
i
l
t
e
r
s
,
integrators
i
n
t
e
g
r
a
t
o
r
s
and
a
n
d
delays,
d
e
l
a
y
s
,
multiple
m
u
l
t
i
p
l
e
iterations
i
t
e
r
a
t
i
o
n
s
of
o
f
the
t
h
e
code
c
o
d
e
should
s
h
o
u
l
d
be
b
e
performed
p
e
r
f
o
r
m
e
d
to
t
o
check
c
h
e
c
k
the
t
h
e
characteristics
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
of
o
f
the
t
h
e
function
f
u
n
c
t
i
o
n
in
i
n
context.
c
o
n
t
e
x
t
.
-
For
F
o
r
state
s
t
a
t
e
transitions,
t
r
a
n
s
i
t
i
o
n
s
,
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
exercise
e
x
e
r
c
i
s
e
the
t
h
e
transitions
t
r
a
n
s
i
t
i
o
n
s
possible
p
o
s
s
i
b
l
e
during
d
u
r
i
n
g
normal
n
o
r
m
a
l
operation.
o
p
e
r
a
t
i
o
n
.
-
For
F
o
r
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
expressed
e
x
p
r
e
s
s
e
d
by
b
y
logic
l
o
g
i
c
equations,
e
q
u
a
t
i
o
n
s
,
the
t
h
e
normal
n
o
r
m
a
l
range
r
a
n
g
e
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
verify
v
e
r
i
f
y
the
t
h
e
variable
v
a
r
i
a
b
l
e
usage
u
s
a
g
e
and
a
n
d
the
t
h
e
Boolean
B
o
o
l
e
a
n
operators.
o
p
e
r
a
t
o
r
s
.
Note:
N
o
t
e
:
One
O
n
e
method
m
e
t
h
o
d
is
i
s
to
t
o
test
t
e
s
t
all
a
l
l
combinations
c
o
m
b
i
n
a
t
i
o
n
s
of
o
f
the
t
h
e
variables.
v
a
r
i
a
b
l
e
s
.
For
F
o
r
complex
c
o
m
p
l
e
x
expressions,
e
x
p
r
e
s
s
i
o
n
s
,
this
t
h
i
s
method
m
e
t
h
o
d
is
i
s
impractical
i
m
p
r
a
c
t
i
c
a
l
due
d
u
e
to
t
o
the
t
h
e
large
l
a
r
g
e
number
n
u
m
b
e
r
of
o
f
test
t
e
s
t
cases
c
a
s
e
s
required.
r
e
q
u
i
r
e
d
.
A
A
different
d
i
f
f
e
r
e
n
t
strategy
s
t
r
a
t
e
g
y
that
t
h
a
t
ensures
e
n
s
u
r
e
s
the
t
h
e
required
r
e
q
u
i
r
e
d
coverage
c
o
v
e
r
a
g
e
could
c
o
u
l
d
be
b
e
developed.
d
e
v
e
l
o
p
e
d
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
for
f
o
r
Level
L
e
v
e
l
A,
A
,
the
t
h
e
Boolean
B
o
o
l
e
a
n
operators
o
p
e
r
a
t
o
r
s
could
c
o
u
l
d
be
b
e
verified
v
e
r
i
f
i
e
d
by
b
y
analysis
a
n
a
l
y
s
i
s
or
o
r
review,
r
e
v
i
e
w
,
and
a
n
d
to
t
o
complement
c
o
m
p
l
e
m
e
n
t
this
t
h
i
s
activity,
a
c
t
i
v
i
t
y
,
test
t
e
s
t
cases
c
a
s
e
s
could
c
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
to
t
o
provide
p
r
o
v
i
d
e
modified
m
o
d
i
f
i
e
d
condition/decision
c
o
n
d
i
t
i
o
n
/
d
e
c
i
s
i
o
n
coverage.
c
o
v
e
r
a
g
e
.
6.4.2.2
6
.
4
.
2
.
2
Robustness
R
o
b
u
s
t
n
e
s
s
Test
T
e
s
t
Cases
C
a
s
e
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
robustness
r
o
b
u
s
t
n
e
s
s
test
t
e
s
t
cases
c
a
s
e
s
is
i
s
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
the
t
h
e
ability
a
b
i
l
i
t
y
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
to
t
o
respond
r
e
s
p
o
n
d
to
t
o
abnormal
a
b
n
o
r
m
a
l
inputs
i
n
p
u
t
s
and
a
n
d
conditions.
c
o
n
d
i
t
i
o
n
s
.
Robustness
R
o
b
u
s
t
n
e
s
s
test
t
e
s
t
cases
c
a
s
e
s
include:
i
n
c
l
u
d
e
:
-
Real
R
e
a
l
and
a
n
d
integer
i
n
t
e
g
e
r
variables
v
a
r
i
a
b
l
e
s
should
s
h
o
u
l
d
be
b
e
exercised
e
x
e
r
c
i
s
e
d
using
u
s
i
n
g
equivalence
e
q
u
i
v
a
l
e
n
c
e
class
c
l
a
s
s
selection
s
e
l
e
c
t
i
o
n
of
o
f
invalid
i
n
v
a
l
i
d
values.
v
a
l
u
e
s
.
-
System
S
y
s
t
e
m
initialization
i
n
i
t
i
a
l
i
z
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
exercised
e
x
e
r
c
i
s
e
d
during
d
u
r
i
n
g
abnormal
a
b
n
o
r
m
a
l
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
The
T
h
e
possible
p
o
s
s
i
b
l
e
failure
f
a
i
l
u
r
e
modes
m
o
d
e
s
of
o
f
the
t
h
e
incoming
i
n
c
o
m
i
n
g
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
determined,
d
e
t
e
r
m
i
n
e
d
,
especially
e
s
p
e
c
i
a
l
l
y
complex,
c
o
m
p
l
e
x
,
digital
d
i
g
i
t
a
l
data
d
a
t
a
strings
s
t
r
i
n
g
s
from
f
r
o
m
an
a
n
external
e
x
t
e
r
n
a
l
system.
s
y
s
t
e
m
.
-
For
F
o
r
loops
l
o
o
p
s
where
w
h
e
r
e
the
t
h
e
loop
l
o
o
p
count
c
o
u
n
t
is
i
s
a
a
computed
c
o
m
p
u
t
e
d
value,
v
a
l
u
e
,
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
attempt
a
t
t
e
m
p
t
to
t
o
compute
c
o
m
p
u
t
e
out-of-range
o
u
t
-
o
f
-
r
a
n
g
e
loop
l
o
o
p
count
c
o
u
n
t
values,
v
a
l
u
e
s
,
and
a
n
d
thus
t
h
u
s
demonstrate
d
e
m
o
n
s
t
r
a
t
e
the
t
h
e
robustness
r
o
b
u
s
t
n
e
s
s
of
o
f
the
t
h
e
loop-related
l
o
o
p
-
r
e
l
a
t
e
d
code.
c
o
d
e
.
e
e
.
.
A
A
check
c
h
e
c
k
should
s
h
o
u
l
d
be
b
e
made
m
a
d
e
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
protection
p
r
o
t
e
c
t
i
o
n
mechanisms
m
e
c
h
a
n
i
s
m
s
for
f
o
r
exceeded
e
x
c
e
e
d
e
d
frame
f
r
a
m
e
times
t
i
m
e
s
respond
r
e
s
p
o
n
d
correctly.
c
o
r
r
e
c
t
l
y
.
-
For
F
o
r
time-related
t
i
m
e
-
r
e
l
a
t
e
d
functions,
f
u
n
c
t
i
o
n
s
,
such
s
u
c
h
as
a
s
filters,
f
i
l
t
e
r
s
,
integrators
i
n
t
e
g
r
a
t
o
r
s
and
a
n
d
delays,
d
e
l
a
y
s
,
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
for
f
o
r
arithmetic
a
r
i
t
h
m
e
t
i
c
overflow
o
v
e
r
f
l
o
w
protection
p
r
o
t
e
c
t
i
o
n
mechanisms.
m
e
c
h
a
n
i
s
m
s
.
-
For
F
o
r
state
s
t
a
t
e
transitions,
t
r
a
n
s
i
t
i
o
n
s
,
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
provoke
p
r
o
v
o
k
e
transitions
t
r
a
n
s
i
t
i
o
n
s
that
t
h
a
t
are
a
r
e
not
n
o
t
allowed
a
l
l
o
w
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.4.3
6
.
4
.
3
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Testing
T
e
s
t
i
n
g
Methods
M
e
t
h
o
d
s
Requirements-based
R
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
testing
t
e
s
t
i
n
g
methods
m
e
t
h
o
d
s
consist
c
o
n
s
i
s
t
of
o
f
methods
m
e
t
h
o
d
s
for
f
o
r
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing,
t
e
s
t
i
n
g
,
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
software
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing,
t
e
s
t
i
n
g
,
and
a
n
d
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
low-level
l
o
w
-
l
e
v
e
l
testing.
t
e
s
t
i
n
g
.
With
W
i
t
h
the
t
h
e
exception
e
x
c
e
p
t
i
o
n
of
o
f
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing,
t
e
s
t
i
n
g
,
these
t
h
e
s
e
methods
m
e
t
h
o
d
s
do
d
o
not
n
o
t
prescribe
p
r
e
s
c
r
i
b
e
a
a
specific
s
p
e
c
i
f
i
c
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
or
o
r
strategy.
s
t
r
a
t
e
g
y
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Hardware/Software
H
a
r
d
w
a
r
e
/
S
o
f
t
w
a
r
e
Integration
I
n
t
e
g
r
a
t
i
o
n
Testing:
T
e
s
t
i
n
g
:
This
T
h
i
s
testing
t
e
s
t
i
n
g
method
m
e
t
h
o
d
should
s
h
o
u
l
d
concentrate
c
o
n
c
e
n
t
r
a
t
e
on
o
n
error
e
r
r
o
r
sources
s
o
u
r
c
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
operating
o
p
e
r
a
t
i
n
g
within
w
i
t
h
i
n
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment,
e
n
v
i
r
o
n
m
e
n
t
,
and
a
n
d
on
o
n
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
functionality.
f
u
n
c
t
i
o
n
a
l
i
t
y
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing
t
e
s
t
i
n
g
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
in
i
n
the
t
h
e
target
t
a
r
g
e
t
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
32
3
2
computer
c
o
m
p
u
t
e
r
will
w
i
l
l
satisfy
s
a
t
i
s
f
y
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Typical
T
y
p
i
c
a
l
errors
e
r
r
o
r
s
revealed
r
e
v
e
a
l
e
d
by
b
y
this
t
h
i
s
testing
t
e
s
t
i
n
g
method
m
e
t
h
o
d
include:
i
n
c
l
u
d
e
:
-
Incorrect
I
n
c
o
r
r
e
c
t
interrupt
i
n
t
e
r
r
u
p
t
handling.
h
a
n
d
l
i
n
g
.
-
Failure
F
a
i
l
u
r
e
to
t
o
satisfy
s
a
t
i
s
f
y
execution
e
x
e
c
u
t
i
o
n
time
t
i
m
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Incorrect
I
n
c
o
r
r
e
c
t
software
s
o
f
t
w
a
r
e
response
r
e
s
p
o
n
s
e
to
t
o
hardware
h
a
r
d
w
a
r
e
transients
t
r
a
n
s
i
e
n
t
s
or
o
r
hardware
h
a
r
d
w
a
r
e
failures,
f
a
i
l
u
r
e
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
start-up
s
t
a
r
t
-
u
p
sequencing,
s
e
q
u
e
n
c
i
n
g
,
transient
t
r
a
n
s
i
e
n
t
input
i
n
p
u
t
loads
l
o
a
d
s
and
a
n
d
input
i
n
p
u
t
power
p
o
w
e
r
transients.
t
r
a
n
s
i
e
n
t
s
.
-
Data
D
a
t
a
bus
b
u
s
and
a
n
d
other
o
t
h
e
r
resource
r
e
s
o
u
r
c
e
contention
c
o
n
t
e
n
t
i
o
n
problems,
p
r
o
b
l
e
m
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
memory
m
e
m
o
r
y
mapping.
m
a
p
p
i
n
g
.
-
Inability
I
n
a
b
i
l
i
t
y
of
o
f
built-in
b
u
i
l
t
-
i
n
test
t
e
s
t
to
t
o
detect
d
e
t
e
c
t
failures.
f
a
i
l
u
r
e
s
.
-
Errors
E
r
r
o
r
s
in
i
n
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
interfaces.
i
n
t
e
r
f
a
c
e
s
.
-
Incorrect
I
n
c
o
r
r
e
c
t
behavior
b
e
h
a
v
i
o
r
of
o
f
feedback
f
e
e
d
b
a
c
k
loops.
l
o
o
p
s
.
-
Incorrect
I
n
c
o
r
r
e
c
t
control
c
o
n
t
r
o
l
of
o
f
memory
m
e
m
o
r
y
management
m
a
n
a
g
e
m
e
n
t
hardware
h
a
r
d
w
a
r
e
or
o
r
other
o
t
h
e
r
hardware
h
a
r
d
w
a
r
e
devices
d
e
v
i
c
e
s
under
u
n
d
e
r
software
s
o
f
t
w
a
r
e
control.
c
o
n
t
r
o
l
.
-
Stack
S
t
a
c
k
overflow.
o
v
e
r
f
l
o
w
.
-
Incorrect
I
n
c
o
r
r
e
c
t
operation
o
p
e
r
a
t
i
o
n
of
o
f
mechanism(s)
m
e
c
h
a
n
i
s
m
(
s
)
used
u
s
e
d
to
t
o
confirm
c
o
n
f
i
r
m
the
t
h
e
correctness
c
o
r
r
e
c
t
n
e
s
s
and
a
n
d
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
of
o
f
field-loadable
f
i
e
l
d
-
l
o
a
d
a
b
l
e
software.
s
o
f
t
w
a
r
e
.
-
Violations
V
i
o
l
a
t
i
o
n
s
of
o
f
software
s
o
f
t
w
a
r
e
partitioning.
p
a
r
t
i
t
i
o
n
i
n
g
.
-
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Software
S
o
f
t
w
a
r
e
Integration
I
n
t
e
g
r
a
t
i
o
n
Testing:
T
e
s
t
i
n
g
:
This
T
h
i
s
testing
t
e
s
t
i
n
g
method
m
e
t
h
o
d
should
s
h
o
u
l
d
concentrate
c
o
n
c
e
n
t
r
a
t
e
on
o
n
the
t
h
e
inter-relationships
i
n
t
e
r
-
r
e
l
a
t
i
o
n
s
h
i
p
s
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
on
o
n
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
software
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing
t
e
s
t
i
n
g
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
interact
i
n
t
e
r
a
c
t
correctly
c
o
r
r
e
c
t
l
y
with
w
i
t
h
each
e
a
c
h
other
o
t
h
e
r
and
a
n
d
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
This
T
h
i
s
method
m
e
t
h
o
d
may
m
a
y
be
b
e
performed
p
e
r
f
o
r
m
e
d
by
b
y
expanding
e
x
p
a
n
d
i
n
g
the
t
h
e
scope
s
c
o
p
e
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
through
t
h
r
o
u
g
h
successive
s
u
c
c
e
s
s
i
v
e
integration
i
n
t
e
g
r
a
t
i
o
n
of
o
f
code
c
o
d
e
components
c
o
m
p
o
n
e
n
t
s
with
w
i
t
h
a
a
corresponding
c
o
r
r
e
s
p
o
n
d
i
n
g
expansion
e
x
p
a
n
s
i
o
n
of
o
f
the
t
h
e
scope
s
c
o
p
e
of
o
f
the
t
h
e
test
t
e
s
t
cases.
c
a
s
e
s
.
Typical
T
y
p
i
c
a
l
errors
e
r
r
o
r
s
revealed
r
e
v
e
a
l
e
d
by
b
y
this
t
h
i
s
testing
t
e
s
t
i
n
g
method
m
e
t
h
o
d
include:
i
n
c
l
u
d
e
:
-
Incorrect
I
n
c
o
r
r
e
c
t
initialization
i
n
i
t
i
a
l
i
z
a
t
i
o
n
of
o
f
variables
v
a
r
i
a
b
l
e
s
and
a
n
d
constants.
c
o
n
s
t
a
n
t
s
.
-
Parameter
P
a
r
a
m
e
t
e
r
passing
p
a
s
s
i
n
g
errors.
e
r
r
o
r
s
.
-
Data
D
a
t
a
corruption,
c
o
r
r
u
p
t
i
o
n
,
especially
e
s
p
e
c
i
a
l
l
y
global
g
l
o
b
a
l
data.
d
a
t
a
.
-
Inadequate
I
n
a
d
e
q
u
a
t
e
end-to-end
e
n
d
-
t
o
-
e
n
d
numerical
n
u
m
e
r
i
c
a
l
resolution.
r
e
s
o
l
u
t
i
o
n
.
-
Incorrect
I
n
c
o
r
r
e
c
t
sequencing
s
e
q
u
e
n
c
i
n
g
of
o
f
events
e
v
e
n
t
s
and
a
n
d
operations.
o
p
e
r
a
t
i
o
n
s
.
-
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Low-Level
L
o
w
-
L
e
v
e
l
Testing:
T
e
s
t
i
n
g
:
This
T
h
i
s
testing
t
e
s
t
i
n
g
method
m
e
t
h
o
d
should
s
h
o
u
l
d
concentrate
c
o
n
c
e
n
t
r
a
t
e
on
o
n
demonstrating
d
e
m
o
n
s
t
r
a
t
i
n
g
that
t
h
a
t
each
e
a
c
h
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
its
i
t
s
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
low-level
l
o
w
-
l
e
v
e
l
testing
t
e
s
t
i
n
g
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
satisfy
s
a
t
i
s
f
y
their
t
h
e
i
r
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Typical
T
y
p
i
c
a
l
errors
e
r
r
o
r
s
revealed
r
e
v
e
a
l
e
d
by
b
y
this
t
h
i
s
testing
t
e
s
t
i
n
g
method
m
e
t
h
o
d
include:
i
n
c
l
u
d
e
:
-
Failure
F
a
i
l
u
r
e
of
o
f
an
a
n
algorithm
a
l
g
o
r
i
t
h
m
to
t
o
satisfy
s
a
t
i
s
f
y
a
a
software
s
o
f
t
w
a
r
e
requirement.
r
e
q
u
i
r
e
m
e
n
t
.
-
Incorrect
I
n
c
o
r
r
e
c
t
loop
l
o
o
p
operations
o
p
e
r
a
t
i
o
n
s
-
Incorrect
I
n
c
o
r
r
e
c
t
logic
l
o
g
i
c
decisions.
d
e
c
i
s
i
o
n
s
.
-
Failure
F
a
i
l
u
r
e
to
t
o
process
p
r
o
c
e
s
s
correctly
c
o
r
r
e
c
t
l
y
legitimate
l
e
g
i
t
i
m
a
t
e
combinations
c
o
m
b
i
n
a
t
i
o
n
s
of
o
f
input
i
n
p
u
t
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Incorrect
I
n
c
o
r
r
e
c
t
responses
r
e
s
p
o
n
s
e
s
to
t
o
missing
m
i
s
s
i
n
g
or
o
r
corrupted
c
o
r
r
u
p
t
e
d
input
i
n
p
u
t
data.
d
a
t
a
.
-
Incorrect
I
n
c
o
r
r
e
c
t
handling
h
a
n
d
l
i
n
g
of
o
f
exceptions,
e
x
c
e
p
t
i
o
n
s
,
such
s
u
c
h
as
a
s
arithmetic
a
r
i
t
h
m
e
t
i
c
faults
f
a
u
l
t
s
or
o
r
violations
v
i
o
l
a
t
i
o
n
s
of
o
f
array
a
r
r
a
y
limits.
l
i
m
i
t
s
.
-
Incorrect
I
n
c
o
r
r
e
c
t
computation
c
o
m
p
u
t
a
t
i
o
n
sequence.
s
e
q
u
e
n
c
e
.
-
Inadequate
I
n
a
d
e
q
u
a
t
e
algorithm
a
l
g
o
r
i
t
h
m
precision,
p
r
e
c
i
s
i
o
n
,
accuracy
a
c
c
u
r
a
c
y
or
o
r
performance.
p
e
r
f
o
r
m
a
n
c
e
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
33
3
3
6.4.4
6
.
4
.
4
Test
T
e
s
t
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
is
i
s
a
a
two
t
w
o
step
s
t
e
p
process,
p
r
o
c
e
s
s
,
involving
i
n
v
o
l
v
i
n
g
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
and
a
n
d
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis.
a
n
a
l
y
s
i
s
.
The
T
h
e
first
f
i
r
s
t
step
s
t
e
p
analyzes
a
n
a
l
y
z
e
s
the
t
h
e
test
t
e
s
t
cases
c
a
s
e
s
in
i
n
relation
r
e
l
a
t
i
o
n
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
confirm
c
o
n
f
i
r
m
that
t
h
a
t
the
t
h
e
selected
s
e
l
e
c
t
e
d
test
t
e
s
t
cases
c
a
s
e
s
satisfy
s
a
t
i
s
f
y
the
t
h
e
specified
s
p
e
c
i
f
i
e
d
criteria.
c
r
i
t
e
r
i
a
.
The
T
h
e
second
s
e
c
o
n
d
step
s
t
e
p
confirms
c
o
n
f
i
r
m
s
that
t
h
a
t
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
exercised
e
x
e
r
c
i
s
e
d
the
t
h
e
code
c
o
d
e
structure.
s
t
r
u
c
t
u
r
e
.
Structural
S
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
may
m
a
y
not
n
o
t
satisfy
s
a
t
i
s
f
y
the
t
h
e
specified
s
p
e
c
i
f
i
e
d
criteria.
c
r
i
t
e
r
i
a
.
Additional
A
d
d
i
t
i
o
n
a
l
guidelines
g
u
i
d
e
l
i
n
e
s
are
a
r
e
provided
p
r
o
v
i
d
e
d
for
f
o
r
resolution
r
e
s
o
l
u
t
i
o
n
of
o
f
such
s
u
c
h
situations
s
i
t
u
a
t
i
o
n
s
as
a
s
dead
d
e
a
d
code
c
o
d
e
(subparagraph
(
s
u
b
p
a
r
a
g
r
a
p
h
6.4.4.3).
6
.
4
.
4
.
3
)
.
6.4.4.1
6
.
4
.
4
.
1
Requirements-Based
R
e
q
u
i
r
e
m
e
n
t
s
-
B
a
s
e
d
Test
T
e
s
t
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
this
t
h
i
s
analysis
a
n
a
l
y
s
i
s
is
i
s
to
t
o
determine
d
e
t
e
r
m
i
n
e
how
h
o
w
well
w
e
l
l
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
testing
t
e
s
t
i
n
g
verified
v
e
r
i
f
i
e
d
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
This
T
h
i
s
analysis
a
n
a
l
y
s
i
s
may
m
a
y
reveal
r
e
v
e
a
l
the
t
h
e
need
n
e
e
d
for
f
o
r
additional
a
d
d
i
t
i
o
n
a
l
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
cases.
c
a
s
e
s
.
The
T
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
show
s
h
o
w
that:
t
h
a
t
:
-
Test
T
e
s
t
cases
c
a
s
e
s
exist
e
x
i
s
t
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
requirement.
r
e
q
u
i
r
e
m
e
n
t
.
-
Test
T
e
s
t
cases
c
a
s
e
s
satisfy
s
a
t
i
s
f
y
the
t
h
e
criteria
c
r
i
t
e
r
i
a
of
o
f
normal
n
o
r
m
a
l
and
a
n
d
robustness
r
o
b
u
s
t
n
e
s
s
testing
t
e
s
t
i
n
g
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
6.4.2.
6
.
4
.
2
.
6.4.4.2
6
.
4
.
4
.
2
Structural
S
t
r
u
c
t
u
r
a
l
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
this
t
h
i
s
analysis
a
n
a
l
y
s
i
s
is
i
s
to
t
o
determine
d
e
t
e
r
m
i
n
e
which
w
h
i
c
h
code
c
o
d
e
structure
s
t
r
u
c
t
u
r
e
was
w
a
s
not
n
o
t
exercised
e
x
e
r
c
i
s
e
d
by
b
y
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
procedures.
p
r
o
c
e
d
u
r
e
s
.
The
T
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
cases
c
a
s
e
s
may
m
a
y
not
n
o
t
have
h
a
v
e
completely
c
o
m
p
l
e
t
e
l
y
exercised
e
x
e
r
c
i
s
e
d
the
t
h
e
code
c
o
d
e
structure,
s
t
r
u
c
t
u
r
e
,
so
s
o
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
is
i
s
performed
p
e
r
f
o
r
m
e
d
and
a
n
d
additional
a
d
d
i
t
i
o
n
a
l
verification
v
e
r
i
f
i
c
a
t
i
o
n
produced
p
r
o
d
u
c
e
d
to
t
o
provide
p
r
o
v
i
d
e
structural
s
t
r
u
c
t
u
r
a
l
coverage.
c
o
v
e
r
a
g
e
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
confirm
c
o
n
f
i
r
m
the
t
h
e
degree
d
e
g
r
e
e
of
o
f
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
-
The
T
h
e
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
may
m
a
y
be
b
e
performed
p
e
r
f
o
r
m
e
d
on
o
n
the
t
h
e
Source
S
o
u
r
c
e
Code,
C
o
d
e
,
unless
u
n
l
e
s
s
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
A
A
and
a
n
d
the
t
h
e
compiler
c
o
m
p
i
l
e
r
generates
g
e
n
e
r
a
t
e
s
object
o
b
j
e
c
t
code
c
o
d
e
that
t
h
a
t
is
i
s
not
n
o
t
directly
d
i
r
e
c
t
l
y
traceable
t
r
a
c
e
a
b
l
e
to
t
o
Source
S
o
u
r
c
e
Code
C
o
d
e
statements.
s
t
a
t
e
m
e
n
t
s
.
Then,
T
h
e
n
,
additional
a
d
d
i
t
i
o
n
a
l
verification
v
e
r
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
performed
p
e
r
f
o
r
m
e
d
on
o
n
the
t
h
e
object
o
b
j
e
c
t
code
c
o
d
e
to
t
o
establish
e
s
t
a
b
l
i
s
h
the
t
h
e
correctness
c
o
r
r
e
c
t
n
e
s
s
of
o
f
such
s
u
c
h
generated
g
e
n
e
r
a
t
e
d
code
c
o
d
e
sequences.
s
e
q
u
e
n
c
e
s
.
A
A
compiler-generated
c
o
m
p
i
l
e
r
-
g
e
n
e
r
a
t
e
d
array-bound
a
r
r
a
y
-
b
o
u
n
d
check
c
h
e
c
k
in
i
n
the
t
h
e
object
o
b
j
e
c
t
code
c
o
d
e
is
i
s
an
a
n
example
e
x
a
m
p
l
e
of
o
f
object
o
b
j
e
c
t
code
c
o
d
e
that
t
h
a
t
is
i
s
not
n
o
t
directly
d
i
r
e
c
t
l
y
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
-
The
T
h
e
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
confirm
c
o
n
f
i
r
m
the
t
h
e
data
d
a
t
a
coupling
c
o
u
p
l
i
n
g
and
a
n
d
control
c
o
n
t
r
o
l
coupling
c
o
u
p
l
i
n
g
between
b
e
t
w
e
e
n
the
t
h
e
code
c
o
d
e
components.
c
o
m
p
o
n
e
n
t
s
.
6.4.4.3
6
.
4
.
4
.
3
Structural
S
t
r
u
c
t
u
r
a
l
Coverage
C
o
v
e
r
a
g
e
Analysis
A
n
a
l
y
s
i
s
Resolution
R
e
s
o
l
u
t
i
o
n
Structural
S
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
may
m
a
y
reveal
r
e
v
e
a
l
code
c
o
d
e
structure
s
t
r
u
c
t
u
r
e
that
t
h
a
t
was
w
a
s
not
n
o
t
exercised
e
x
e
r
c
i
s
e
d
during
d
u
r
i
n
g
testing.
t
e
s
t
i
n
g
.
Resolution
R
e
s
o
l
u
t
i
o
n
would
w
o
u
l
d
require
r
e
q
u
i
r
e
additional
a
d
d
i
t
i
o
n
a
l
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity.
a
c
t
i
v
i
t
y
.
This
T
h
i
s
unexecuted
u
n
e
x
e
c
u
t
e
d
code
c
o
d
e
structure
s
t
r
u
c
t
u
r
e
may
m
a
y
be
b
e
the
t
h
e
result
r
e
s
u
l
t
of:
o
f
:
-
Shortcomings
S
h
o
r
t
c
o
m
i
n
g
s
in
i
n
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
cases
c
a
s
e
s
or
o
r
procedures
p
r
o
c
e
d
u
r
e
s
:
:
The
T
h
e
test
t
e
s
t
cases
c
a
s
e
s
should
s
h
o
u
l
d
be
b
e
supplemented
s
u
p
p
l
e
m
e
n
t
e
d
or
o
r
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
changed
c
h
a
n
g
e
d
to
t
o
provide
p
r
o
v
i
d
e
the
t
h
e
missing
m
i
s
s
i
n
g
coverage.
c
o
v
e
r
a
g
e
.
The
T
h
e
method(s)
m
e
t
h
o
d
(
s
)
used
u
s
e
d
to
t
o
perform
p
e
r
f
o
r
m
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
reviewed.
r
e
v
i
e
w
e
d
.
-
Inadequacies
I
n
a
d
e
q
u
a
c
i
e
s
in
i
n
software
s
o
f
t
w
a
r
e
requirements:
r
e
q
u
i
r
e
m
e
n
t
s
:
The
T
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
modified
m
o
d
i
f
i
e
d
and
a
n
d
additional
a
d
d
i
t
i
o
n
a
l
test
t
e
s
t
cases
c
a
s
e
s
developed
d
e
v
e
l
o
p
e
d
and
a
n
d
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
executed.
e
x
e
c
u
t
e
d
.
-
Dead
D
e
a
d
code:
c
o
d
e
:
The
T
h
e
code
c
o
d
e
should
s
h
o
u
l
d
be
b
e
removed
r
e
m
o
v
e
d
and
a
n
d
an
a
n
analysis
a
n
a
l
y
s
i
s
performed
p
e
r
f
o
r
m
e
d
to
t
o
assess
a
s
s
e
s
s
the
t
h
e
effect
e
f
f
e
c
t
and
a
n
d
the
t
h
e
need
n
e
e
d
for
f
o
r
reverification.
r
e
v
e
r
i
f
i
c
a
t
i
o
n
.
-
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code:
c
o
d
e
:
For
F
o
r
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
which
w
h
i
c
h
is
i
s
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
executed
e
x
e
c
u
t
e
d
in
i
n
any
a
n
y
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
used
u
s
e
d
within
w
i
t
h
i
n
an
a
n
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine,
e
n
g
i
n
e
,
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
analysis
a
n
a
l
y
s
i
s
and
a
n
d
testing
t
e
s
t
i
n
g
should
s
h
o
u
l
d
show
s
h
o
w
that
t
h
a
t
the
t
h
e
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
such
s
u
c
h
code
c
o
d
e
could
c
o
u
l
d
be
b
e
inadvertently
i
n
a
d
v
e
r
t
e
n
t
l
y
executed
e
x
e
c
u
t
e
d
are
a
r
e
prevented,
p
r
e
v
e
n
t
e
d
,
isolated,
i
s
o
l
a
t
e
d
,
or
o
r
eliminated.
e
l
i
m
i
n
a
t
e
d
.
For
F
o
r
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
which
w
h
i
c
h
is
i
s
only
o
n
l
y
executed
e
x
e
c
u
t
e
d
in
i
n
certain
c
e
r
t
a
i
n
configurations
c
o
n
f
i
g
u
r
a
t
i
o
n
s
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment,
e
n
v
i
r
o
n
m
e
n
t
,
the
t
h
e
operational
o
p
e
r
a
t
i
o
n
a
l
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
needed
n
e
e
d
e
d
for
f
o
r
normal
n
o
r
m
a
l
execution
e
x
e
c
u
t
i
o
n
of
o
f
this
t
h
i
s
code
c
o
d
e
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
and
a
n
d
additional
a
d
d
i
t
i
o
n
a
l
test
t
e
s
t
cases
c
a
s
e
s
and
a
n
d
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
developed
d
e
v
e
l
o
p
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
required
r
e
q
u
i
r
e
d
coverage
c
o
v
e
r
a
g
e
objectives.
o
b
j
e
c
t
i
v
e
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
7.0
7
.
0
SOFTWARE
S
O
F
T
W
A
R
E
CONFIGURATION
C
O
N
F
I
G
U
R
A
T
I
O
N
MANAGEMENT
M
A
N
A
G
E
M
E
N
T
PROCESS
P
R
O
C
E
S
S
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
(SCM
(
S
C
M
process.
p
r
o
c
e
s
s
.
The
T
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
is
i
s
applied
a
p
p
l
i
e
d
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
(section
(
s
e
c
t
i
o
n
4)
4
)
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.4).
1
1
.
4
)
.
Outputs
O
u
t
p
u
t
s
of
o
f
the
t
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
are
a
r
e
recorded
r
e
c
o
r
d
e
d
in
i
n
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Records
R
e
c
o
r
d
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.18)
1
1
.
1
8
)
or
o
r
in
i
n
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
Table
T
a
b
l
e
A-8
A
-
8
of
o
f
Annex
A
n
n
e
x
A
A
is
i
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
SCM
S
C
M
process.
p
r
o
c
e
s
s
.
7.1
7
.
1
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
SCM
S
C
M
process,
p
r
o
c
e
s
s
,
working
w
o
r
k
i
n
g
in
i
n
cooperation
c
o
o
p
e
r
a
t
i
o
n
with
w
i
t
h
the
t
h
e
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
assists
a
s
s
i
s
t
s
in
i
n
satisfying
s
a
t
i
s
f
y
i
n
g
general
g
e
n
e
r
a
l
objectives
o
b
j
e
c
t
i
v
e
s
to:
t
o
:
-
Provide
P
r
o
v
i
d
e
a
a
defined
d
e
f
i
n
e
d
and
a
n
d
controlled
c
o
n
t
r
o
l
l
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
-
Provide
P
r
o
v
i
d
e
the
t
h
e
ability
a
b
i
l
i
t
y
to
t
o
consistently
c
o
n
s
i
s
t
e
n
t
l
y
replicate
r
e
p
l
i
c
a
t
e
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
for
f
o
r
software
s
o
f
t
w
a
r
e
manufacture
m
a
n
u
f
a
c
t
u
r
e
or
o
r
to
t
o
regenerate
r
e
g
e
n
e
r
a
t
e
it
i
t
in
i
n
case
c
a
s
e
of
o
f
a
a
need
n
e
e
d
for
f
o
r
investigation
i
n
v
e
s
t
i
g
a
t
i
o
n
or
o
r
modification.
m
o
d
i
f
i
c
a
t
i
o
n
.
-
Provide
P
r
o
v
i
d
e
control
c
o
n
t
r
o
l
of
o
f
process
p
r
o
c
e
s
s
inputs
i
n
p
u
t
s
and
a
n
d
outputs
o
u
t
p
u
t
s
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
that
t
h
a
t
ensures
e
n
s
u
r
e
s
consistency
c
o
n
s
i
s
t
e
n
c
y
and
a
n
d
repeatability
r
e
p
e
a
t
a
b
i
l
i
t
y
of
o
f
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
-
Provide
P
r
o
v
i
d
e
a
a
known
k
n
o
w
n
point
p
o
i
n
t
for
f
o
r
review,
r
e
v
i
e
w
,
assessing
a
s
s
e
s
s
i
n
g
status,
s
t
a
t
u
s
,
and
a
n
d
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
by
b
y
control
c
o
n
t
r
o
l
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
and
a
n
d
the
t
h
e
establishment
e
s
t
a
b
l
i
s
h
m
e
n
t
of
o
f
baselines.
b
a
s
e
l
i
n
e
s
.
-
Provide
P
r
o
v
i
d
e
controls
c
o
n
t
r
o
l
s
that
t
h
a
t
ensure
e
n
s
u
r
e
problems
p
r
o
b
l
e
m
s
receive
r
e
c
e
i
v
e
attention
a
t
t
e
n
t
i
o
n
and
a
n
d
changes
c
h
a
n
g
e
s
are
a
r
e
recorded,
r
e
c
o
r
d
e
d
,
approved,
a
p
p
r
o
v
e
d
,
and
a
n
d
implemented.
i
m
p
l
e
m
e
n
t
e
d
.
-
Provide
P
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
e
of
o
f
approval
a
p
p
r
o
v
a
l
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
by
b
y
control
c
o
n
t
r
o
l
of
o
f
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
-
Aid
A
i
d
the
t
h
e
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Ensure
E
n
s
u
r
e
that
t
h
a
t
secure
s
e
c
u
r
e
physical
p
h
y
s
i
c
a
l
archiving,
a
r
c
h
i
v
i
n
g
,
recovery
r
e
c
o
v
e
r
y
and
a
n
d
control
c
o
n
t
r
o
l
are
a
r
e
maintained
m
a
i
n
t
a
i
n
e
d
for
f
o
r
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items.
i
t
e
m
s
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
SCM
S
C
M
are
a
r
e
independent
i
n
d
e
p
e
n
d
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
However,
H
o
w
e
v
e
r
,
two
t
w
o
categories
c
a
t
e
g
o
r
i
e
s
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
may
m
a
y
exist
e
x
i
s
t
based
b
a
s
e
d
on
o
n
the
t
h
e
SCM
S
C
M
controls
c
o
n
t
r
o
l
s
applied
a
p
p
l
i
e
d
to
t
o
the
t
h
e
data
d
a
t
a
(subsection
(
s
u
b
s
e
c
t
i
o
n
7.3).
7
.
3
)
.
7.2
7
.
2
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
The
T
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
includes
i
n
c
l
u
d
e
s
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
change
c
h
a
n
g
e
control,
c
o
n
t
r
o
l
,
baseline
b
a
s
e
l
i
n
e
establishment,
e
s
t
a
b
l
i
s
h
m
e
n
t
,
and
a
n
d
archiving
a
r
c
h
i
v
i
n
g
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
related
r
e
l
a
t
e
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
The
T
h
e
following
f
o
l
l
o
w
i
n
g
guidelines
g
u
i
d
e
l
i
n
e
s
define
d
e
f
i
n
e
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
each
e
a
c
h
SCM
S
C
M
process
p
r
o
c
e
s
s
activity.
a
c
t
i
v
i
t
y
.
The
T
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
does
d
o
e
s
not
n
o
t
stop
s
t
o
p
when
w
h
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
is
i
s
accepted
a
c
c
e
p
t
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority,
a
u
t
h
o
r
i
t
y
,
but
b
u
t
continues
c
o
n
t
i
n
u
e
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
service
s
e
r
v
i
c
e
life
l
i
f
e
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
7.2.1
7
.
2
.
1
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Identification
I
d
e
n
t
i
f
i
c
a
t
i
o
n
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
label
l
a
b
e
l
unambiguously
u
n
a
m
b
i
g
u
o
u
s
l
y
each
e
a
c
h
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
(and
(
a
n
d
its
i
t
s
successive
s
u
c
c
e
s
s
i
v
e
versions)
v
e
r
s
i
o
n
s
)
so
s
o
that
t
h
a
t
a
a
basis
b
a
s
i
s
is
i
s
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
the
t
h
e
control
c
o
n
t
r
o
l
and
a
n
d
reference
r
e
f
e
r
e
n
c
e
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items.
i
t
e
m
s
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
each
e
a
c
h
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item,
i
t
e
m
,
for
f
o
r
each
e
a
c
h
separately
s
e
p
a
r
a
t
e
l
y
controlled
c
o
n
t
r
o
l
l
e
d
component
c
o
m
p
o
n
e
n
t
of
o
f
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item,
i
t
e
m
,
and
a
n
d
for
f
o
r
combinations
c
o
m
b
i
n
a
t
i
o
n
s
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
that
t
h
a
t
comprise
c
o
m
p
r
i
s
e
a
a
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
should
s
h
o
u
l
d
be
b
e
configuration-identified
c
o
n
f
i
g
u
r
a
t
i
o
n
-
i
d
e
n
t
i
f
i
e
d
prior
p
r
i
o
r
to
t
o
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
and
a
n
d
traceability
t
r
a
c
e
a
b
i
l
i
t
y
data
d
a
t
a
recording.
r
e
c
o
r
d
i
n
g
.
35
3
5
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
36
3
6
-
A
A
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
should
s
h
o
u
l
d
be
b
e
configuration-identified
c
o
n
f
i
g
u
r
a
t
i
o
n
-
i
d
e
n
t
i
f
i
e
d
before
b
e
f
o
r
e
that
t
h
a
t
item
i
t
e
m
is
i
s
used
u
s
e
d
by
b
y
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
referenced
r
e
f
e
r
e
n
c
e
d
by
b
y
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data,
d
a
t
a
,
or
o
r
used
u
s
e
d
for
f
o
r
software
s
o
f
t
w
a
r
e
manufacture
m
a
n
u
f
a
c
t
u
r
e
or
o
r
software
s
o
f
t
w
a
r
e
loading.
l
o
a
d
i
n
g
.
-
If
I
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
cannot
c
a
n
n
o
t
be
b
e
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
physical
p
h
y
s
i
c
a
l
examination
e
x
a
m
i
n
a
t
i
o
n
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
part
p
a
r
t
number
n
u
m
b
e
r
plate
p
l
a
t
e
examination),
e
x
a
m
i
n
a
t
i
o
n
)
,
then
t
h
e
n
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
should
s
h
o
u
l
d
contain
c
o
n
t
a
i
n
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
which
w
h
i
c
h
can
c
a
n
be
b
e
accessed
a
c
c
e
s
s
e
d
by
b
y
other
o
t
h
e
r
parts
p
a
r
t
s
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
This
T
h
i
s
may
m
a
y
be
b
e
applicable
a
p
p
l
i
c
a
b
l
e
for
f
o
r
field
f
i
e
l
d
-loadable
-
l
o
a
d
a
b
l
e
software
s
o
f
t
w
a
r
e
(subsection
(
s
u
b
s
e
c
t
i
o
n
2.5).
2
.
5
)
.
7.2.2
7
.
2
.
2
Baselines
B
a
s
e
l
i
n
e
s
and
a
n
d
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
baseline
b
a
s
e
l
i
n
e
establishment
e
s
t
a
b
l
i
s
h
m
e
n
t
is
i
s
to
t
o
define
d
e
f
i
n
e
a
a
basis
b
a
s
i
s
for
f
o
r
further
f
u
r
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
and
a
n
d
allow
a
l
l
o
w
reference
r
e
f
e
r
e
n
c
e
to.
t
o
.
control
c
o
n
t
r
o
l
of,
o
f
,
and
a
n
d
traceability
t
r
a
c
e
a
b
i
l
i
t
y
between
b
e
t
w
e
e
n
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items.
i
t
e
m
s
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Baselines
B
a
s
e
l
i
n
e
s
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
used
u
s
e
d
for
f
o
r
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit.
c
r
e
d
i
t
.
(Intermediate
(
I
n
t
e
r
m
e
d
i
a
t
e
baselines
b
a
s
e
l
i
n
e
s
may
m
a
y
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
to
t
o
aid
a
i
d
in
i
n
controlling
c
o
n
t
r
o
l
l
i
n
g
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities.)
a
c
t
i
v
i
t
i
e
s
.
)
-
A
A
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
baseline
b
a
s
e
l
i
n
e
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
and
a
n
d
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(subsection
(
s
u
b
s
e
c
t
i
o
n
II.
I
I
.
16).
1
6
)
.
Note:
N
o
t
e
:
User-modifiable
U
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
is
i
s
not
n
o
t
included
i
n
c
l
u
d
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
baseline,
b
a
s
e
l
i
n
e
,
except
e
x
c
e
p
t
for
f
o
r
its
i
t
s
associated
a
s
s
o
c
i
a
t
e
d
protection
p
r
o
t
e
c
t
i
o
n
and
a
n
d
boundary
b
o
u
n
d
a
r
y
components.
c
o
m
p
o
n
e
n
t
s
.
Therefore,
T
h
e
r
e
f
o
r
e
,
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
may
m
a
y
be
b
e
made
m
a
d
e
to
t
o
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
without
w
i
t
h
o
u
t
affecting
a
f
f
e
c
t
i
n
g
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
baseline.
b
a
s
e
l
i
n
e
.
-
Baselines
B
a
s
e
l
i
n
e
s
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
in
i
n
controlled
c
o
n
t
r
o
l
l
e
d
software
s
o
f
t
w
a
r
e
libraries
l
i
b
r
a
r
i
e
s
(physical,
(
p
h
y
s
i
c
a
l
,
electronic,
e
l
e
c
t
r
o
n
i
c
,
or
o
r
other)
o
t
h
e
r
)
to
t
o
ensure
e
n
s
u
r
e
their
t
h
e
i
r
integrity.
i
n
t
e
g
r
i
t
y
.
Once
O
n
c
e
a
a
baseline
b
a
s
e
l
i
n
e
is
i
s
established,
e
s
t
a
b
l
i
s
h
e
d
,
it
i
t
should
s
h
o
u
l
d
be
b
e
protected
p
r
o
t
e
c
t
e
d
from
f
r
o
m
change.
c
h
a
n
g
e
.
-
Change
C
h
a
n
g
e
control
c
o
n
t
r
o
l
activities
a
c
t
i
v
i
t
i
e
s
should
s
h
o
u
l
d
be
b
e
followed
f
o
l
l
o
w
e
d
to
t
o
develop
d
e
v
e
l
o
p
a
a
derivative
d
e
r
i
v
a
t
i
v
e
baseline
b
a
s
e
l
i
n
e
from
f
r
o
m
an
a
n
established
e
s
t
a
b
l
i
s
h
e
d
baseline.
b
a
s
e
l
i
n
e
.
-
A
A
baseline
b
a
s
e
l
i
n
e
should
s
h
o
u
l
d
be
b
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
baseline
b
a
s
e
l
i
n
e
from
f
r
o
m
which
w
h
i
c
h
it
i
t
was
w
a
s
derived,
d
e
r
i
v
e
d
,
if
i
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
is
i
s
sought
s
o
u
g
h
t
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
or
o
r
data
d
a
t
a
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
baseline.
b
a
s
e
l
i
n
e
.
-
A
A
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
should
s
h
o
u
l
d
be
b
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
from
f
r
o
m
which
w
h
i
c
h
it
i
t
was
w
a
s
derived,
d
e
r
i
v
e
d
,
if
i
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
is
i
s
sought
s
o
u
g
h
t
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
or
o
r
data
d
a
t
a
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item.
i
t
e
m
.
-
A
A
baseline
b
a
s
e
l
i
n
e
or
o
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
should
s
h
o
u
l
d
be
b
e
traceable
t
r
a
c
e
a
b
l
e
either
e
i
t
h
e
r
to
t
o
the
t
h
e
output
o
u
t
p
u
t
it
i
t
identifies
i
d
e
n
t
i
f
i
e
s
or
o
r
to
t
o
the
t
h
e
process
p
r
o
c
e
s
s
with
w
i
t
h
which
w
h
i
c
h
it
i
t
is
i
s
associated.
a
s
s
o
c
i
a
t
e
d
.
7.2.3
7
.
2
.
3
Problem
P
r
o
b
l
e
m
Reporting,
R
e
p
o
r
t
i
n
g
,
Tracking
T
r
a
c
k
i
n
g
and
a
n
d
Corrective
C
o
r
r
e
c
t
i
v
e
Action
A
c
t
i
o
n
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
problem
p
r
o
b
l
e
m
reporting,
r
e
p
o
r
t
i
n
g
,
tracking
t
r
a
c
k
i
n
g
and
a
n
d
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
is
i
s
to
t
o
record
r
e
c
o
r
d
process
p
r
o
c
e
s
s
non-
n
o
n
-
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards,
s
t
a
n
d
a
r
d
s
,
to
t
o
record
r
e
c
o
r
d
deficiencies
d
e
f
i
c
i
e
n
c
i
e
s
of
o
f
outputs
o
u
t
p
u
t
s
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
to
t
o
record
r
e
c
o
r
d
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
software
s
o
f
t
w
a
r
e
products,
p
r
o
d
u
c
t
s
,
and
a
n
d
to
t
o
ensure
e
n
s
u
r
e
resolution
r
e
s
o
l
u
t
i
o
n
of
o
f
these
t
h
e
s
e
problems.
p
r
o
b
l
e
m
s
.
Note:
N
o
t
e
:
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
and
a
n
d
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
problems
p
r
o
b
l
e
m
s
may
m
a
y
be
b
e
recorded
r
e
c
o
r
d
e
d
in
i
n
separate
s
e
p
a
r
a
t
e
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
systems.
s
y
s
t
e
m
s
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
A
A
problem
p
r
o
b
l
e
m
report
r
e
p
o
r
t
should
s
h
o
u
l
d
be
b
e
prepared
p
r
e
p
a
r
e
d
that
t
h
a
t
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
process
p
r
o
c
e
s
s
non-compliance
n
o
n
-
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
plans,
p
l
a
n
s
,
output
o
u
t
p
u
t
deficiency,
d
e
f
i
c
i
e
n
c
y
,
or
o
r
software
s
o
f
t
w
a
r
e
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
and
a
n
d
the
t
h
e
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
taken,
t
a
k
e
n
,
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
11.17.
1
1
.
1
7
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
7.2.4
7
.
2
.
4
Change
C
h
a
n
g
e
Control
C
o
n
t
r
o
l
7.2.5
7
.
2
.
5
Change
C
h
a
n
g
e
Review
R
e
v
i
e
w
37
3
7
-
Problem
P
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
for
f
o
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
affected
a
f
f
e
c
t
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item(s)
i
t
e
m
(
s
)
or
o
r
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
affected
a
f
f
e
c
t
e
d
process
p
r
o
c
e
s
s
activities,
a
c
t
i
v
i
t
i
e
s
,
status
s
t
a
t
u
s
reporting
r
e
p
o
r
t
i
n
g
of
o
f
problem
p
r
o
b
l
e
m
reports,
r
e
p
o
r
t
s
,
and
a
n
d
approval
a
p
p
r
o
v
a
l
and
a
n
d
closure
c
l
o
s
u
r
e
of
o
f
problem
p
r
o
b
l
e
m
reports.
r
e
p
o
r
t
s
.
-
Problem
P
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
that
t
h
a
t
require
r
e
q
u
i
r
e
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
or
o
r
outputs
o
u
t
p
u
t
s
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
should
s
h
o
u
l
d
invoke
i
n
v
o
k
e
the
t
h
e
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activity.
a
c
t
i
v
i
t
y
.
Note:
N
o
t
e
:
The
T
h
e
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
and
a
n
d
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
related.
r
e
l
a
t
e
d
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
provide
p
r
o
v
i
d
e
for
f
o
r
recording,
r
e
c
o
r
d
i
n
g
,
evaluation,
e
v
a
l
u
a
t
i
o
n
,
resolution
r
e
s
o
l
u
t
i
o
n
and
a
n
d
approval
a
p
p
r
o
v
a
l
of
o
f
changes
c
h
a
n
g
e
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Change
C
h
a
n
g
e
control
c
o
n
t
r
o
l
should
s
h
o
u
l
d
preserve
p
r
e
s
e
r
v
e
the
t
h
e
integrity
i
n
t
e
g
r
i
t
y
of
o
f
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
and
a
n
d
baselines
b
a
s
e
l
i
n
e
s
by
b
y
providing
p
r
o
v
i
d
i
n
g
protection
p
r
o
t
e
c
t
i
o
n
against
a
g
a
i
n
s
t
their
t
h
e
i
r
change.
c
h
a
n
g
e
.
-
Change
C
h
a
n
g
e
control
c
o
n
t
r
o
l
should
s
h
o
u
l
d
ensure
e
n
s
u
r
e
that
t
h
a
t
any
a
n
y
change
c
h
a
n
g
e
to
t
o
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
requires
r
e
q
u
i
r
e
s
a
a
change
c
h
a
n
g
e
to
t
o
its
i
t
s
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification.
i
d
e
n
t
i
f
i
c
a
t
i
o
n
.
-
Changes
C
h
a
n
g
e
s
to
t
o
baselines
b
a
s
e
l
i
n
e
s
and
a
n
d
to
t
o
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
under
u
n
d
e
r
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
should
s
h
o
u
l
d
be
b
e
recorded,
r
e
c
o
r
d
e
d
,
approved,
a
p
p
r
o
v
e
d
,
and
a
n
d
tracked.
t
r
a
c
k
e
d
.
Problem
P
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
is
i
s
related
r
e
l
a
t
e
d
to
t
o
change
c
h
a
n
g
e
control,
c
o
n
t
r
o
l
,
since
s
i
n
c
e
resolution
r
e
s
o
l
u
t
i
o
n
of
o
f
a
a
reported
r
e
p
o
r
t
e
d
problem
p
r
o
b
l
e
m
may
m
a
y
result
r
e
s
u
l
t
in
i
n
changes
c
h
a
n
g
e
s
to
t
o
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
or
o
r
baselines.
b
a
s
e
l
i
n
e
s
.
Note:
N
o
t
e
:
It
I
t
is
i
s
generally
g
e
n
e
r
a
l
l
y
recognized
r
e
c
o
g
n
i
z
e
d
that
t
h
a
t
early
e
a
r
l
y
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
assists
a
s
s
i
s
t
s
the
t
h
e
control
c
o
n
t
r
o
l
and
a
n
d
management
m
a
n
a
g
e
m
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
-
Software
S
o
f
t
w
a
r
e
changes
c
h
a
n
g
e
s
should
s
h
o
u
l
d
be
b
e
traced
t
r
a
c
e
d
to
t
o
their
t
h
e
i
r
origin
o
r
i
g
i
n
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
repeated
r
e
p
e
a
t
e
d
from
f
r
o
m
the
t
h
e
point
p
o
i
n
t
at
a
t
which
w
h
i
c
h
the
t
h
e
change
c
h
a
n
g
e
affects
a
f
f
e
c
t
s
their
t
h
e
i
r
outputs.
o
u
t
p
u
t
s
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
an
a
n
error
e
r
r
o
r
discovered
d
i
s
c
o
v
e
r
e
d
at
a
t
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration,
i
n
t
e
g
r
a
t
i
o
n
,
that
t
h
a
t
is
i
s
shown
s
h
o
w
n
to
t
o
result
r
e
s
u
l
t
from
f
r
o
m
an
a
n
incorrect
i
n
c
o
r
r
e
c
t
design,
d
e
s
i
g
n
,
should
s
h
o
u
l
d
result
r
e
s
u
l
t
in
i
n
design
d
e
s
i
g
n
correction,
c
o
r
r
e
c
t
i
o
n
,
code
c
o
d
e
correction
c
o
r
r
e
c
t
i
o
n
and
a
n
d
repetition
r
e
p
e
t
i
t
i
o
n
of
o
f
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
integral
i
n
t
e
g
r
a
l
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
-
Throughout
T
h
r
o
u
g
h
o
u
t
the
t
h
e
change
c
h
a
n
g
e
activity,
a
c
t
i
v
i
t
y
,
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
affected
a
f
f
e
c
t
e
d
by
b
y
the
t
h
e
change
c
h
a
n
g
e
should
s
h
o
u
l
d
be
b
e
updated
u
p
d
a
t
e
d
and
a
n
d
records
r
e
c
o
r
d
s
should
s
h
o
u
l
d
be
b
e
maintained
m
a
i
n
t
a
i
n
e
d
for
f
o
r
the
t
h
e
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activity.
a
c
t
i
v
i
t
y
.
The
T
h
e
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activity
a
c
t
i
v
i
t
y
is
i
s
aided
a
i
d
e
d
by
b
y
the
t
h
e
change
c
h
a
n
g
e
review
r
e
v
i
e
w
activity.
a
c
t
i
v
i
t
y
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
change
c
h
a
n
g
e
review
r
e
v
i
e
w
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
ensure
e
n
s
u
r
e
problems
p
r
o
b
l
e
m
s
and
a
n
d
changes
c
h
a
n
g
e
s
are
a
r
e
assessed,
a
s
s
e
s
s
e
d
,
approved
a
p
p
r
o
v
e
d
or
o
r
disapproved,
d
i
s
a
p
p
r
o
v
e
d
,
approved
a
p
p
r
o
v
e
d
changes
c
h
a
n
g
e
s
are
a
r
e
implemented,
i
m
p
l
e
m
e
n
t
e
d
,
and
a
n
d
feedback
f
e
e
d
b
a
c
k
is
i
s
provided
p
r
o
v
i
d
e
d
to
t
o
affected
a
f
f
e
c
t
e
d
processes
p
r
o
c
e
s
s
e
s
through
t
h
r
o
u
g
h
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
and
a
n
d
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
methods
m
e
t
h
o
d
s
defined
d
e
f
i
n
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
The
T
h
e
change
c
h
a
n
g
e
review
r
e
v
i
e
w
activity
a
c
t
i
v
i
t
y
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Confirmation
C
o
n
f
i
r
m
a
t
i
o
n
that
t
h
a
t
affected
a
f
f
e
c
t
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
are
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identified.
i
d
e
n
t
i
f
i
e
d
.
-
Assessment
A
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
impact
i
m
p
a
c
t
on
o
n
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
with
w
i
t
h
feedback
f
e
e
d
b
a
c
k
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
-
Assessment
A
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
problem
p
r
o
b
l
e
m
or
o
r
change,
c
h
a
n
g
e
,
with
w
i
t
h
decis
d
e
c
i
s
ions
i
o
n
s
for
f
o
r
action
a
c
t
i
o
n
to
t
o
be
b
e
taken.
t
a
k
e
n
.
-
Feedback
F
e
e
d
b
a
c
k
of
o
f
problem
p
r
o
b
l
e
m
report
r
e
p
o
r
t
or
o
r
change
c
h
a
n
g
e
impact
i
m
p
a
c
t
and
a
n
d
decisions
d
e
c
i
s
i
o
n
s
to
t
o
affected
a
f
f
e
c
t
e
d
processes.
p
r
o
c
e
s
s
e
s
.
7.2.6
7
.
2
.
6
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Status
S
t
a
t
u
s
Accounting
A
c
c
o
u
n
t
i
n
g
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
status
s
t
a
t
u
s
accounting
a
c
c
o
u
n
t
i
n
g
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
provide
p
r
o
v
i
d
e
data
d
a
t
a
for
f
o
r
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
baselines,
b
a
s
e
l
i
n
e
s
,
problem
p
r
o
b
l
e
m
reports,
r
e
p
o
r
t
s
,
and
a
n
d
change
c
h
a
n
g
e
control.
c
o
n
t
r
o
l
.
The
T
h
e
status
s
t
a
t
u
s
accounting
a
c
c
o
u
n
t
i
n
g
activity
a
c
t
i
v
i
t
y
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Reporting
R
e
p
o
r
t
i
n
g
on
o
n
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
baseline
b
a
s
e
l
i
n
e
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
problem
p
r
o
b
l
e
m
report
r
e
p
o
r
t
status,
s
t
a
t
u
s
,
change
c
h
a
n
g
e
history,
h
i
s
t
o
r
y
,
and
a
n
d
release
r
e
l
e
a
s
e
status.
s
t
a
t
u
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
38
3
8
-
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
the
t
h
e
data
d
a
t
a
to
t
o
be
b
e
maintained
m
a
i
n
t
a
i
n
e
d
and
a
n
d
the
t
h
e
means
m
e
a
n
s
of
o
f
recording
r
e
c
o
r
d
i
n
g
and
a
n
d
reporting
r
e
p
o
r
t
i
n
g
status
s
t
a
t
u
s
of
o
f
this
t
h
i
s
data.
d
a
t
a
.
7.2.7
7
.
2
.
7
Archive,
A
r
c
h
i
v
e
,
Retrieval
R
e
t
r
i
e
v
a
l
and
a
n
d
Release
R
e
l
e
a
s
e
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
archive
a
r
c
h
i
v
e
and
a
n
d
retrieval
r
e
t
r
i
e
v
a
l
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
can
c
a
n
be
b
e
retrieved
r
e
t
r
i
e
v
e
d
in
i
n
case
c
a
s
e
of
o
f
a
a
need
n
e
e
d
to
t
o
duplicate,
d
u
p
l
i
c
a
t
e
,
regenerate,
r
e
g
e
n
e
r
a
t
e
,
retest
r
e
t
e
s
t
or
o
r
modify
m
o
d
i
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
release
r
e
l
e
a
s
e
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
only
o
n
l
y
authorized
a
u
t
h
o
r
i
z
e
d
software
s
o
f
t
w
a
r
e
is
i
s
used,
u
s
e
d
,
especially
e
s
p
e
c
i
a
l
l
y
for
f
o
r
software
s
o
f
t
w
a
r
e
manufacturing,
m
a
n
u
f
a
c
t
u
r
i
n
g
,
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
being
b
e
i
n
g
archived
a
r
c
h
i
v
e
d
and
a
n
d
retrievable.
r
e
t
r
i
e
v
a
b
l
e
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
should
s
h
o
u
l
d
be
b
e
retrievable
r
e
t
r
i
e
v
a
b
l
e
from
f
r
o
m
the
t
h
e
approved
a
p
p
r
o
v
e
d
source
s
o
u
r
c
e
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
developing
d
e
v
e
l
o
p
i
n
g
organization
o
r
g
a
n
i
z
a
t
i
o
n
or
o
r
company).
c
o
m
p
a
n
y
)
.
-
Procedures
P
r
o
c
e
d
u
r
e
s
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
to
t
o
ensure
e
n
s
u
r
e
the
t
h
e
integrity
i
n
t
e
g
r
i
t
y
of
o
f
the
t
h
e
stored
s
t
o
r
e
d
data
d
a
t
a
(regardless
(
r
e
g
a
r
d
l
e
s
s
of
o
f
medium
m
e
d
i
u
m
of
o
f
storage)
s
t
o
r
a
g
e
)
by:
b
y
:
-
Ensuring
E
n
s
u
r
i
n
g
that
t
h
a
t
no
n
o
unauthorized
u
n
a
u
t
h
o
r
i
z
e
d
changes
c
h
a
n
g
e
s
can
c
a
n
be
b
e
made.
m
a
d
e
.
-
Selecting
S
e
l
e
c
t
i
n
g
storage
s
t
o
r
a
g
e
media
m
e
d
i
a
that
t
h
a
t
minimize
m
i
n
i
m
i
z
e
regeneration
r
e
g
e
n
e
r
a
t
i
o
n
errors
e
r
r
o
r
s
or
o
r
deterioration.
d
e
t
e
r
i
o
r
a
t
i
o
n
.
-
Exercising
E
x
e
r
c
i
s
i
n
g
and/or
a
n
d
/
o
r
refreshing
r
e
f
r
e
s
h
i
n
g
archived
a
r
c
h
i
v
e
d
data
d
a
t
a
at
a
t
a
a
frequency
f
r
e
q
u
e
n
c
y
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
the
t
h
e
storage
s
t
o
r
a
g
e
life
l
i
f
e
of
o
f
the
t
h
e
medium.
m
e
d
i
u
m
.
-
Storing
S
t
o
r
i
n
g
duplicate
d
u
p
l
i
c
a
t
e
copies
c
o
p
i
e
s
in
i
n
physically
p
h
y
s
i
c
a
l
l
y
separate
s
e
p
a
r
a
t
e
archives
a
r
c
h
i
v
e
s
that
t
h
a
t
minimize
m
i
n
i
m
i
z
e
the
t
h
e
risk
r
i
s
k
of
o
f
loss
l
o
s
s
in
i
n
the
t
h
e
event
e
v
e
n
t
of
o
f
a
a
disaster.
d
i
s
a
s
t
e
r
.
-
The
T
h
e
duplication
d
u
p
l
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
verified
v
e
r
i
f
i
e
d
to
t
o
produce
p
r
o
d
u
c
e
accurate
a
c
c
u
r
a
t
e
copies,
c
o
p
i
e
s
,
and
a
n
d
procedures
p
r
o
c
e
d
u
r
e
s
should
s
h
o
u
l
d
exist
e
x
i
s
t
that
t
h
a
t
ensure
e
n
s
u
r
e
error-free
e
r
r
o
r
-
f
r
e
e
copying
c
o
p
y
i
n
g
of
o
f
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
should
s
h
o
u
l
d
be
b
e
identified
i
d
e
n
t
i
f
i
e
d
and
a
n
d
released
r
e
l
e
a
s
e
d
prior
p
r
i
o
r
to
t
o
use
u
s
e
for
f
o
r
software
s
o
f
t
w
a
r
e
manufacture
m
a
n
u
f
a
c
t
u
r
e
and
a
n
d
the
t
h
e
authority
a
u
t
h
o
r
i
t
y
for
f
o
r
their
t
h
e
i
r
release
r
e
l
e
a
s
e
should
s
h
o
u
l
d
be
b
e
established.
e
s
t
a
b
l
i
s
h
e
d
.
As
A
s
a
a
minimum,
m
i
n
i
m
u
m
,
the
t
h
e
components
c
o
m
p
o
n
e
n
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
(which
(
w
h
i
c
h
includes
i
n
c
l
u
d
e
s
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
and
a
n
d
may
m
a
y
also
a
l
s
o
include
i
n
c
l
u
d
e
associated
a
s
s
o
c
i
a
t
e
d
media
m
e
d
i
a
for
f
o
r
software
s
o
f
t
w
a
r
e
loading)
l
o
a
d
i
n
g
)
should
s
h
o
u
l
d
be
b
e
released.
r
e
l
e
a
s
e
d
.
Note:
N
o
t
e
:
Release
R
e
l
e
a
s
e
is
i
s
generally
g
e
n
e
r
a
l
l
y
also
a
l
s
o
required
r
e
q
u
i
r
e
d
for
f
o
r
the
t
h
e
data
d
a
t
a
that
t
h
a
t
defines
d
e
f
i
n
e
s
the
t
h
e
approved
a
p
p
r
o
v
e
d
software
s
o
f
t
w
a
r
e
for
f
o
r
loading
l
o
a
d
i
n
g
into
i
n
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
that
t
h
a
t
data
d
a
t
a
is
i
s
outside
o
u
t
s
i
d
e
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
but
b
u
t
may
m
a
y
include
i
n
c
l
u
d
e
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index.
I
n
d
e
x
.
-
Data
D
a
t
a
retention
r
e
t
e
n
t
i
o
n
procedures
p
r
o
c
e
d
u
r
e
s
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
enable
e
n
a
b
l
e
software
s
o
f
t
w
a
r
e
modifications.
m
o
d
i
f
i
c
a
t
i
o
n
s
.
7.2.8
7
.
2
.
8
Software
S
o
f
t
w
a
r
e
Load
L
o
a
d
Control
C
o
n
t
r
o
l
Note:
N
o
t
e
:
Additional
A
d
d
i
t
i
o
n
a
l
data
d
a
t
a
retention
r
e
t
e
n
t
i
o
n
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
may
m
a
y
include
i
n
c
l
u
d
e
items
i
t
e
m
s
such
s
u
c
h
as
a
s
business
b
u
s
i
n
e
s
s
needs
n
e
e
d
s
and
a
n
d
future
f
u
t
u
r
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
reviews,
r
e
v
i
e
w
s
,
which
w
h
i
c
h
are
a
r
e
outside
o
u
t
s
i
d
e
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
activity
a
c
t
i
v
i
t
y
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
is
i
s
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
with
w
i
t
h
appropriate
a
p
p
r
o
p
r
i
a
t
e
safeguards.
s
a
f
e
g
u
a
r
d
s
.
Software
S
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
refers
r
e
f
e
r
s
to
t
o
the
t
h
e
process
p
r
o
c
e
s
s
by
b
y
which
w
h
i
c
h
programmed
p
r
o
g
r
a
m
m
e
d
instructions
i
n
s
t
r
u
c
t
i
o
n
s
and
a
n
d
data
d
a
t
a
are
a
r
e
transferred
t
r
a
n
s
f
e
r
r
e
d
from
f
r
o
m
a
a
master
m
a
s
t
e
r
memory
m
e
m
o
r
y
device
d
e
v
i
c
e
into
i
n
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
methods
m
e
t
h
o
d
s
may
m
a
y
include
i
n
c
l
u
d
e
(subject
(
s
u
b
j
e
c
t
to
t
o
approval
a
p
p
r
o
v
a
l
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority)
a
u
t
h
o
r
i
t
y
)
the
t
h
e
installation
i
n
s
t
a
l
l
a
t
i
o
n
of
o
f
factory
f
a
c
t
o
r
y
per-programmed
p
e
r
-
p
r
o
g
r
a
m
m
e
d
memory
m
e
m
o
r
y
devices
d
e
v
i
c
e
s
or
o
r
in
i
n
situ
s
i
t
u
re-programming
r
e
-
p
r
o
g
r
a
m
m
i
n
g
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
using
u
s
i
n
g
a
a
field
f
i
e
l
d
loading
l
o
a
d
i
n
g
device.
d
e
v
i
c
e
.
Whichever
W
h
i
c
h
e
v
e
r
method
m
e
t
h
o
d
is
i
s
used,
u
s
e
d
,
software
s
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Procedures
P
r
o
c
e
d
u
r
e
s
for
f
o
r
part
p
a
r
t
numbering
n
u
m
b
e
r
i
n
g
and
a
n
d
media
m
e
d
i
a
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
that
t
h
a
t
identify
i
d
e
n
t
i
f
y
software
s
o
f
t
w
a
r
e
configurations
c
o
n
f
i
g
u
r
a
t
i
o
n
s
that
t
h
a
t
are
a
r
e
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
approved
a
p
p
r
o
v
e
d
for
f
o
r
loading
l
o
a
d
i
n
g
into
i
n
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
-
Whether
W
h
e
t
h
e
r
the
t
h
e
software
s
o
f
t
w
a
r
e
is
i
s
delivered
d
e
l
i
v
e
r
e
d
as
a
s
an
a
n
end
e
n
d
item
i
t
e
m
or
o
r
is
i
s
delivered
d
e
l
i
v
e
r
e
d
installed
i
n
s
t
a
l
l
e
d
in
i
n
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment,
e
q
u
i
p
m
e
n
t
,
records
r
e
c
o
r
d
s
should
s
h
o
u
l
d
be
b
e
kept
k
e
p
t
that
t
h
a
t
confirm
c
o
n
f
i
r
m
software
s
o
f
t
w
a
r
e
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
hardware.
h
a
r
d
w
a
r
e
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Note:
N
o
t
e
:
Additional
A
d
d
i
t
i
o
n
a
l
guidance
g
u
i
d
a
n
c
e
on
o
n
software
s
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
is
i
s
provided
p
r
o
v
i
d
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
2.5.
2
.
5
.
7.2.9
7
.
2
.
9
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Control
C
o
n
t
r
o
l
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
software
s
o
f
t
w
a
r
e
fife
f
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
control
c
o
n
t
r
o
l
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
tools
t
o
o
l
s
used
u
s
e
d
to
t
o
produce
p
r
o
d
u
c
e
the
t
h
e
software
s
o
f
t
w
a
r
e
are
a
r
e
identified,
i
d
e
n
t
i
f
i
e
d
,
controlled,
c
o
n
t
r
o
l
l
e
d
,
and
a
n
d
retrievable.
r
e
t
r
i
e
v
a
b
l
e
.
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
tools
t
o
o
l
s
are
a
r
e
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
and
a
n
d
identified
i
d
e
n
t
i
f
i
e
d
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.15).
1
1
.
1
5
)
.
Guidance
G
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
(or
(
o
r
equivalent)
e
q
u
i
v
a
l
e
n
t
)
of
o
f
the
t
h
e
tools
t
o
o
l
s
used
u
s
e
d
to
t
o
develop,
d
e
v
e
l
o
p
,
control,
c
o
n
t
r
o
l
,
build,
b
u
i
l
d
,
verify,
v
e
r
i
f
y
,
and
a
n
d
load
l
o
a
d
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
-
The
T
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
for
f
o
r
controlling
c
o
n
t
r
o
l
l
i
n
g
qualified
q
u
a
l
i
f
i
e
d
tools,
t
o
o
l
s
,
should
s
h
o
u
l
d
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
I
I
or
o
r
2
2
data
d
a
t
a
(subsection
(
s
u
b
s
e
c
t
i
o
n
7.3),
7
.
3
)
,
as
a
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
12.2.3,
1
2
.
2
.
3
,
item
i
t
e
m
b.
b
.
-
Unless
U
n
l
e
s
s
7.2.9
7
.
2
.
9
item
i
t
e
m
b
b
applies,
a
p
p
l
i
e
s
,
the
t
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
for
f
o
r
controlling
c
o
n
t
r
o
l
l
i
n
g
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
(or
(
o
r
equivalent)
e
q
u
i
v
a
l
e
n
t
)
of
o
f
tools
t
o
o
l
s
used
u
s
e
d
to
t
o
build
b
u
i
l
d
and
a
n
d
load
l
o
a
d
the
t
h
e
software
s
o
f
t
w
a
r
e
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
compilers,
c
o
m
p
i
l
e
r
s
,
assemblers,
a
s
s
e
m
b
l
e
r
s
,
linkage
l
i
n
k
a
g
e
editors)
e
d
i
t
o
r
s
)
should
s
h
o
u
l
d
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
data,
d
a
t
a
,
as
a
s
a
a
minimum.
m
i
n
i
m
u
m
.
7.3
7
.
3
Data
D
a
t
a
Control
C
o
n
t
r
o
l
Categories
C
a
t
e
g
o
r
i
e
s
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
can
c
a
n
be
b
e
assigned
a
s
s
i
g
n
e
d
to
t
o
one
o
n
e
of
o
f
two
t
w
o
categories:
c
a
t
e
g
o
r
i
e
s
:
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
1
1
(CC1)
(
C
C
1
)
and
a
n
d
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
(CC2).
(
C
C
2
)
.
These
T
h
e
s
e
categories
c
a
t
e
g
o
r
i
e
s
are
a
r
e
related
r
e
l
a
t
e
d
to
t
o
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
controls
c
o
n
t
r
o
l
s
placed
p
l
a
c
e
d
on
o
n
the
t
h
e
data.
d
a
t
a
.
Table
T
a
b
l
e
7-1
7
-
1
defines
d
e
f
i
n
e
s
the
t
h
e
set
s
e
t
of
o
f
SCM
S
C
M
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
each
e
a
c
h
control
c
o
n
t
r
o
l
category,
c
a
t
e
g
o
r
y
,
where
w
h
e
r
e
·
·
indicates
i
n
d
i
c
a
t
e
s
that
t
h
a
t
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
apply
a
p
p
l
y
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
of
o
f
that
t
h
a
t
category.
c
a
t
e
g
o
r
y
.
The
T
h
e
tables
t
a
b
l
e
s
of
o
f
Annex
A
n
n
e
x
A
A
specify
s
p
e
c
i
f
y
the
t
h
e
control
c
o
n
t
r
o
l
category
c
a
t
e
g
o
r
y
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
item,
i
t
e
m
,
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
data
d
a
t
a
control
c
o
n
t
r
o
l
categories
c
a
t
e
g
o
r
i
e
s
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
categorized
c
a
t
e
g
o
r
i
z
e
d
as
a
s
CC
C
C
should
s
h
o
u
l
d
be
b
e
applied
a
p
p
l
i
e
d
according
a
c
c
o
r
d
i
n
g
to
t
o
Table
T
a
b
l
e
7-
7
-
1
1
.
.
-
The
T
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
categorized
c
a
t
e
g
o
r
i
z
e
d
as
a
s
C
C
should
s
h
o
u
l
d
be
b
e
applied
a
p
p
l
i
e
d
according
a
c
c
o
r
d
i
n
g
to
t
o
Table
T
a
b
l
e
7-1
7
-
1
as
a
s
a
a
minimum.
m
i
n
i
m
u
m
.
39
3
9
TABLE
T
A
B
L
E
7
7
-1
-
1
SCM
S
C
M
PROCESS
P
R
O
C
E
S
S
OBJECTIVES
O
B
J
E
C
T
I
V
E
S
ASSOCIATED
A
S
S
O
C
I
A
T
E
D
WITH
W
I
T
H
CC1
C
C
1
and
a
n
d
CC2
C
C
2
DATA
D
A
T
A
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
8.0
8
.
0
SOFTWARE
S
O
F
T
W
A
R
E
QUALITY
Q
U
A
L
I
T
Y
ASSURANCE
A
S
S
U
R
A
N
C
E
PROCESS
P
R
O
C
E
S
S
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
(SQA)
(
S
Q
A
)
process.
p
r
o
c
e
s
s
.
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
is
i
s
applied
a
p
p
l
i
e
d
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
(section
(
s
e
c
t
i
o
n
4)
4
)
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Plan
P
l
a
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.5).
1
1
.
5
)
.
Outputs
O
u
t
p
u
t
s
of
o
f
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
recorded
r
e
c
o
r
d
e
d
in
i
n
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Records
R
e
c
o
r
d
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.19)
1
1
.
1
9
)
or
o
r
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
assesses
a
s
s
e
s
s
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
their
t
h
e
i
r
outputs
o
u
t
p
u
t
s
to
t
o
obtain
o
b
t
a
i
n
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
satisfied,
s
a
t
i
s
f
i
e
d
,
that
t
h
a
t
deficiencies
d
e
f
i
c
i
e
n
c
i
e
s
are
a
r
e
detected,
d
e
t
e
c
t
e
d
,
evaluated,
e
v
a
l
u
a
t
e
d
,
tracked
t
r
a
c
k
e
d
and
a
n
d
resolved,
r
e
s
o
l
v
e
d
,
and
a
n
d
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
conform
c
o
n
f
o
r
m
to
t
o
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
8.1
8
.
1
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Process
P
r
o
c
e
s
s
Objectives
O
b
j
e
c
t
i
v
e
s
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
provide
p
r
o
v
i
d
e
confidence
c
o
n
f
i
d
e
n
c
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
produce
p
r
o
d
u
c
e
software
s
o
f
t
w
a
r
e
that
t
h
a
t
conforms
c
o
n
f
o
r
m
s
to
t
o
its
i
t
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
by
b
y
assuring
a
s
s
u
r
i
n
g
that
t
h
a
t
these
t
h
e
s
e
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
performed
p
e
r
f
o
r
m
e
d
in
i
n
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
approved
a
p
p
r
o
v
e
d
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards.
s
t
a
n
d
a
r
d
s
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
are
a
r
e
to
t
o
obtain
o
b
t
a
i
n
assurance
a
s
s
u
r
a
n
c
e
that:
t
h
a
t
:
-
Software
S
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
comply
c
o
m
p
l
y
with
w
i
t
h
approved
a
p
p
r
o
v
e
d
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards.
s
t
a
n
d
a
r
d
s
.
-
The
T
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
A
A
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
is
i
s
conducted.
c
o
n
d
u
c
t
e
d
.
The
T
h
e
applicability
a
p
p
l
i
c
a
b
i
l
i
t
y
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
by
b
y
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
Table
T
a
b
l
e
A-9
A
-
9
of
o
f
Annex
A
n
n
e
x
A.
A
.
8.2
8
.
2
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
e
s
To
T
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
objectives:
o
b
j
e
c
t
i
v
e
s
:
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
take
t
a
k
e
an
a
n
active
a
c
t
i
v
e
role
r
o
l
e
in
i
n
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
and
a
n
d
have
h
a
v
e
those
t
h
o
s
e
performing
p
e
r
f
o
r
m
i
n
g
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
enabled
e
n
a
b
l
e
d
with
w
i
t
h
the
t
h
e
authority,
a
u
t
h
o
r
i
t
y
,
responsibility
r
e
s
p
o
n
s
i
b
i
l
i
t
y
and
a
n
d
independence
i
n
d
e
p
e
n
d
e
n
c
e
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
and
a
n
d
reviewed
r
e
v
i
e
w
e
d
for
f
o
r
consistency.
c
o
n
s
i
s
t
e
n
c
y
.
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
approved
a
p
p
r
o
v
e
d
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards.
s
t
a
n
d
a
r
d
s
.
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
audits
a
u
d
i
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
to
t
o
obtain
o
b
t
a
i
n
assurance
a
s
s
u
r
a
n
c
e
that:
t
h
a
t
:
-
Software
S
o
f
t
w
a
r
e
plans
p
l
a
n
s
are
a
r
e
available
a
v
a
i
l
a
b
l
e
as
a
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
4.2.
4
.
2
.
-
Deviations
D
e
v
i
a
t
i
o
n
s
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
detected,
d
e
t
e
c
t
e
d
,
recorded,
r
e
c
o
r
d
e
d
,
evaluated,
e
v
a
l
u
a
t
e
d
,
tracked
t
r
a
c
k
e
d
and
a
n
d
resolved.
r
e
s
o
l
v
e
d
.
Note:
N
o
t
e
:
It
I
t
is
i
s
generally
g
e
n
e
r
a
l
l
y
accepted
a
c
c
e
p
t
e
d
that
t
h
a
t
early
e
a
r
l
y
detection
d
e
t
e
c
t
i
o
n
of
o
f
process
p
r
o
c
e
s
s
deviations
d
e
v
i
a
t
i
o
n
s
assists
a
s
s
i
s
t
s
efficient
e
f
f
i
c
i
e
n
t
achievement
a
c
h
i
e
v
e
m
e
n
t
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
Approved
A
p
p
r
o
v
e
d
deviations
d
e
v
i
a
t
i
o
n
s
are
a
r
e
recorded.
r
e
c
o
r
d
e
d
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
has
h
a
s
been
b
e
e
n
provided
p
r
o
v
i
d
e
d
as
a
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
-
The
T
h
e
problem
p
r
o
b
l
e
m
reporting,
r
e
p
o
r
t
i
n
g
,
tracking
t
r
a
c
k
i
n
g
and
a
n
d
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
process
p
r
o
c
e
s
s
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan.
P
l
a
n
.
-
Inputs
I
n
p
u
t
s
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
by
b
y
the
t
h
e
on-going
o
n
-
g
o
i
n
g
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
have
h
a
v
e
been
b
e
e
n
addressed.
a
d
d
r
e
s
s
e
d
.
41
4
1
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
42
4
2
Note:
N
o
t
e
:
Monitoring
M
o
n
i
t
o
r
i
n
g
of
o
f
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
may
m
a
y
be
b
e
performed
p
e
r
f
o
r
m
e
d
to
t
o
provide
p
r
o
v
i
d
e
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
under
u
n
d
e
r
control.
c
o
n
t
r
o
l
.
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
the
t
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
have
h
a
v
e
been
b
e
e
n
satisfied
s
a
t
i
s
f
i
e
d
in
i
n
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
approved
a
p
p
r
o
v
e
d
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
is
i
s
controlled
c
o
n
t
r
o
l
l
e
d
in
i
n
accordance
a
c
c
o
r
d
a
n
c
e
with
w
i
t
h
the
t
h
e
control
c
o
n
t
r
o
l
categories
c
a
t
e
g
o
r
i
e
s
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
7.3
7
.
3
and
a
n
d
the
t
h
e
tables
t
a
b
l
e
s
of
o
f
Annex
A
n
n
e
x
A.
A
.
-
Prior
P
r
i
o
r
to
t
o
the
t
h
e
delivery
d
e
l
i
v
e
r
y
of
o
f
software
s
o
f
t
w
a
r
e
products
p
r
o
d
u
c
t
s
submitted
s
u
b
m
i
t
t
e
d
as
a
s
part
p
a
r
t
of
o
f
a
a
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
application,
a
p
p
l
i
c
a
t
i
o
n
,
a
a
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
should
s
h
o
u
l
d
be
b
e
conducted.
c
o
n
d
u
c
t
e
d
.
-
The
T
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
produce
p
r
o
d
u
c
e
records
r
e
c
o
r
d
s
of
o
f
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.19),
1
1
.
1
9
)
,
including
i
n
c
l
u
d
i
n
g
audit
a
u
d
i
t
results
r
e
s
u
l
t
s
and
a
n
d
evidence
e
v
i
d
e
n
c
e
of
o
f
completion
c
o
m
p
l
e
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
submitted
s
u
b
m
i
t
t
e
d
as
a
s
part
p
a
r
t
of
o
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
application.
a
p
p
l
i
c
a
t
i
o
n
.
8.3
8
.
3
Software
S
o
f
t
w
a
r
e
Conformity
C
o
n
f
o
r
m
i
t
y
Review
R
e
v
i
e
w
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
is
i
s
to
t
o
obtain
o
b
t
a
i
n
assurances,
a
s
s
u
r
a
n
c
e
s
,
for
f
o
r
a
a
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
submitted
s
u
b
m
i
t
t
e
d
as
a
s
part
p
a
r
t
of
o
f
a
a
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
application,
a
p
p
l
i
c
a
t
i
o
n
,
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
complete,
c
o
m
p
l
e
t
e
,
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
is
i
s
complete,
c
o
m
p
l
e
t
e
,
and
a
n
d
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
is
i
s
controlled
c
o
n
t
r
o
l
l
e
d
and
a
n
d
can
c
a
n
be
b
e
regenerated.
r
e
g
e
n
e
r
a
t
e
d
.
This
T
h
i
s
review
r
e
v
i
e
w
should
s
h
o
u
l
d
determine
d
e
t
e
r
m
i
n
e
that:
t
h
a
t
:
-
Planned
P
l
a
n
n
e
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
for
f
o
r
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit,
c
r
e
d
i
t
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
generation
g
e
n
e
r
a
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data,
d
a
t
a
,
have
h
a
v
e
been
b
e
e
n
completed
c
o
m
p
l
e
t
e
d
and
a
n
d
records
r
e
c
o
r
d
s
of
o
f
their
t
h
e
i
r
completion
c
o
m
p
l
e
t
i
o
n
are
a
r
e
retained.
r
e
t
a
i
n
e
d
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
developed
d
e
v
e
l
o
p
e
d
from
f
r
o
m
specific
s
p
e
c
i
f
i
c
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
or
o
r
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
those
t
h
o
s
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards,
s
t
a
n
d
a
r
d
s
,
and
a
n
d
is
i
s
controlled
c
o
n
t
r
o
l
l
e
d
in
i
n
accordance
a
c
c
o
r
d
a
n
c
e
with
w
i
t
h
the
t
h
e
SCM
S
C
M
Plan.
P
l
a
n
.
-
Problem
P
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
SCM
S
C
M
Plan,
P
l
a
n
,
have
h
a
v
e
been
b
e
e
n
evaluated
e
v
a
l
u
a
t
e
d
and
a
n
d
have
h
a
v
e
their
t
h
e
i
r
status
s
t
a
t
u
s
recorded.
r
e
c
o
r
d
e
d
.
-
Software
S
o
f
t
w
a
r
e
requirement
r
e
q
u
i
r
e
m
e
n
t
deviations
d
e
v
i
a
t
i
o
n
s
are
a
r
e
recorded
r
e
c
o
r
d
e
d
and
a
n
d
approved.
a
p
p
r
o
v
e
d
.
-
The
T
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
can
c
a
n
be
b
e
regenerated
r
e
g
e
n
e
r
a
t
e
d
from
f
r
o
m
the
t
h
e
archived
a
r
c
h
i
v
e
d
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
g
g
The
T
h
e
approved
a
p
p
r
o
v
e
d
software
s
o
f
t
w
a
r
e
can
c
a
n
be
b
e
loaded
l
o
a
d
e
d
successfully
s
u
c
c
e
s
s
f
u
l
l
y
through
t
h
r
o
u
g
h
the
t
h
e
use
u
s
e
of
o
f
released
r
e
l
e
a
s
e
d
instructions.
i
n
s
t
r
u
c
t
i
o
n
s
.
-
Problem
P
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
deferred
d
e
f
e
r
r
e
d
from
f
r
o
m
a
a
previous
p
r
e
v
i
o
u
s
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
are
a
r
e
re-evaluated
r
e
-
e
v
a
l
u
a
t
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
their
t
h
e
i
r
status.
s
t
a
t
u
s
.
-
If
I
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
is
i
s
sought
s
o
u
g
h
t
for
f
o
r
the
t
h
e
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
the
t
h
e
current
c
u
r
r
e
n
t
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
baseline
b
a
s
e
l
i
n
e
is
i
s
traceable
t
r
a
c
e
a
b
l
e
to
t
o
the
t
h
e
previous
p
r
e
v
i
o
u
s
baseline
b
a
s
e
l
i
n
e
and
a
n
d
the
t
h
e
approved
a
p
p
r
o
v
e
d
changes
c
h
a
n
g
e
s
to
t
o
that
t
h
a
t
baseline.
b
a
s
e
l
i
n
e
.
Note:
N
o
t
e
:
For
F
o
r
post-certification
p
o
s
t
-
c
e
r
t
i
f
i
c
a
t
i
o
n
software
s
o
f
t
w
a
r
e
modifications,
m
o
d
i
f
i
c
a
t
i
o
n
s
,
a
a
subset
s
u
b
s
e
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
activities,
a
c
t
i
v
i
t
i
e
s
,
as
a
s
justified
j
u
s
t
i
f
i
e
d
by
b
y
the
t
h
e
significance
s
i
g
n
i
f
i
c
a
n
c
e
of
o
f
the
t
h
e
change,
c
h
a
n
g
e
,
may
m
a
y
be
b
e
performed.
p
e
r
f
o
r
m
e
d
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
43
4
3
9.0
9
.
0
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
LIAISON
L
I
A
I
S
O
N
PROCESS
P
R
O
C
E
S
S
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process
p
r
o
c
e
s
s
is
i
s
to
t
o
establish
e
s
t
a
b
l
i
s
h
communication
c
o
m
m
u
n
i
c
a
t
i
o
n
and
a
n
d
understanding
u
n
d
e
r
s
t
a
n
d
i
n
g
between
b
e
t
w
e
e
n
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
and
a
n
d
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
to
t
o
assis
a
s
s
i
s
t
t
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process
p
r
o
c
e
s
s
is
i
s
applied
a
p
p
l
i
e
d
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
(section
(
s
e
c
t
i
o
n
4)
4
)
and
a
n
d
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.1).
1
1
.
1
)
.
Table
T
a
b
l
e
A-10
A
-
1
0
of
o
f
Annex
A
n
n
e
x
A
A
is
i
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
this
t
h
i
s
process.
p
r
o
c
e
s
s
.
9.1
9
.
1
Means
M
e
a
n
s
of
o
f
Compliance
C
o
m
p
l
i
a
n
c
e
and
a
n
d
Planning
P
l
a
n
n
i
n
g
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
proposes
p
r
o
p
o
s
e
s
a
a
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
that
t
h
a
t
defines
d
e
f
i
n
e
s
how
h
o
w
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
will
w
i
l
l
satisfy
s
a
t
i
s
f
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis.
b
a
s
i
s
.
The
T
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.1)
1
1
.
1
)
defines
d
e
f
i
n
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
within
w
i
t
h
i
n
the
t
h
e
context
c
o
n
t
e
x
t
of
o
f
the
t
h
e
proposed
p
r
o
p
o
s
e
d
means
m
e
a
n
s
of
o
f
compliance.
c
o
m
p
l
i
a
n
c
e
.
This
T
h
i
s
plan
p
l
a
n
also
a
l
s
o
states
s
t
a
t
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
as
a
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should:
s
h
o
u
l
d
:
-
Submit
S
u
b
m
i
t
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
and
a
n
d
other
o
t
h
e
r
requested
r
e
q
u
e
s
t
e
d
data
d
a
t
a
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
for
f
o
r
review
r
e
v
i
e
w
at
a
t
a
a
point
p
o
i
n
t
in
i
n
time
t
i
m
e
when
w
h
e
n
the
t
h
e
effects
e
f
f
e
c
t
s
of
o
f
changes
c
h
a
n
g
e
s
are
a
r
e
minimal,
m
i
n
i
m
a
l
,
that
t
h
a
t
is,
i
s
,
when
w
h
e
n
they
t
h
e
y
can
c
a
n
be
b
e
managed
m
a
n
a
g
e
d
within
w
i
t
h
i
n
project
p
r
o
j
e
c
t
constraints.
c
o
n
s
t
r
a
i
n
t
s
.
-
Resolve
R
e
s
o
l
v
e
issues
i
s
s
u
e
s
identified
i
d
e
n
t
i
f
i
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
concerning
c
o
n
c
e
r
n
i
n
g
the
t
h
e
planning
p
l
a
n
n
i
n
g
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Obtain
O
b
t
a
i
n
agreement
a
g
r
e
e
m
e
n
t
with
w
i
t
h
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
on
o
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
9.2
9
.
2
Compliance
C
o
m
p
l
i
a
n
c
e
Substantiation
S
u
b
s
t
a
n
t
i
a
t
i
o
n
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
provides
p
r
o
v
i
d
e
s
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
reviews
r
e
v
i
e
w
s
may
m
a
y
take
t
a
k
e
place
p
l
a
c
e
at
a
t
the
t
h
e
applicant’s
a
p
p
l
i
c
a
n
t
’
s
facilities
f
a
c
i
l
i
t
i
e
s
or
o
r
the
t
h
e
applicant’s
a
p
p
l
i
c
a
n
t
’
s
suppliers’
s
u
p
p
l
i
e
r
s
’
facilities.
f
a
c
i
l
i
t
i
e
s
.
This
T
h
i
s
may
m
a
y
involve
i
n
v
o
l
v
e
discussions
d
i
s
c
u
s
s
i
o
n
s
with
w
i
t
h
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
or
o
r
its
i
t
s
suppliers.
s
u
p
p
l
i
e
r
s
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
arranges
a
r
r
a
n
g
e
s
these
t
h
e
s
e
reviews
r
e
v
i
e
w
s
of
o
f
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
makes
m
a
k
e
s
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
available
a
v
a
i
l
a
b
l
e
as
a
s
needed.
n
e
e
d
e
d
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should:
s
h
o
u
l
d
:
-
Resolve
R
e
s
o
l
v
e
issues
i
s
s
u
e
s
raised
r
a
i
s
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
as
a
s
a
a
result
r
e
s
u
l
t
of
o
f
its
i
t
s
reviews.
r
e
v
i
e
w
s
.
-
Submit
S
u
b
m
i
t
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.20)
1
1
.
2
0
)
and
a
n
d
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(subsection
(
s
u
b
s
e
c
t
i
o
n
11.16)
1
1
.
1
6
)
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
-
Submit
S
u
b
m
i
t
or
o
r
make
m
a
k
e
available
a
v
a
i
l
a
b
l
e
other
o
t
h
e
r
data
d
a
t
a
or
o
r
evidence
e
v
i
d
e
n
c
e
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
requested
r
e
q
u
e
s
t
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
9.3
9
.
3
Minimum
M
i
n
i
m
u
m
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Data
D
a
t
a
That
T
h
a
t
Is
I
s
Submitted
S
u
b
m
i
t
t
e
d
to
t
o
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Authority
A
u
t
h
o
r
i
t
y
The
T
h
e
minimum
m
i
n
i
m
u
m
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
that
t
h
a
t
is
i
s
submitted
s
u
b
m
i
t
t
e
d
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
is:
i
s
:
-
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index.
I
n
d
e
x
.
-
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary.
S
u
m
m
a
r
y
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
44
4
4
9.4
9
.
4
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Data
D
a
t
a
Related
R
e
l
a
t
e
d
to
t
o
Type
T
y
p
e
Design
D
e
s
i
g
n
Unless
U
n
l
e
s
s
otherwise
o
t
h
e
r
w
i
s
e
agreed
a
g
r
e
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority,
a
u
t
h
o
r
i
t
y
,
the
t
h
e
regulations
r
e
g
u
l
a
t
i
o
n
s
concerning
c
o
n
c
e
r
n
i
n
g
retrieval
r
e
t
r
i
e
v
a
l
and
a
n
d
approval
a
p
p
r
o
v
a
l
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
related
r
e
l
a
t
e
d
to
t
o
the
t
h
e
type
t
y
p
e
design
d
e
s
i
g
n
applies
a
p
p
l
i
e
s
to:
t
o
:
-
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data.
D
a
t
a
.
-
Design
D
e
s
i
g
n
Description.
D
e
s
c
r
i
p
t
i
o
n
.
-
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
-
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index.
I
n
d
e
x
.
-
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary.
S
u
m
m
a
r
y
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
10.0
1
0
.
0
OVERVIEW
O
V
E
R
V
I
E
W
OF
O
F
AIRCRAFT
A
I
R
C
R
A
F
T
AND
A
N
D
ENGINE
E
N
G
I
N
E
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
This
T
h
i
s
section
s
e
c
t
i
o
n
is
i
s
an
a
n
overview
o
v
e
r
v
i
e
w
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
for
f
o
r
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
engines
e
n
g
i
n
e
s
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment,
e
q
u
i
p
m
e
n
t
,
and
a
n
d
is
i
s
provided
p
r
o
v
i
d
e
d
for
f
o
r
information
i
n
f
o
r
m
a
t
i
o
n
purposes
p
u
r
p
o
s
e
s
only.
o
n
l
y
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
considers
c
o
n
s
i
d
e
r
s
the
t
h
e
software
s
o
f
t
w
a
r
e
as
a
s
part
p
a
r
t
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
installed
i
n
s
t
a
l
l
e
d
on
o
n
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine;
e
n
g
i
n
e
;
that
t
h
a
t
is,
i
s
,
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
does
d
o
e
s
not
n
o
t
approve
a
p
p
r
o
v
e
the
t
h
e
software
s
o
f
t
w
a
r
e
as
a
s
a
a
unique,
u
n
i
q
u
e
,
stand-alone
s
t
a
n
d
-
a
l
o
n
e
product.
p
r
o
d
u
c
t
.
10.1
1
0
.
1
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Basis
B
a
s
i
s
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
establishes
e
s
t
a
b
l
i
s
h
e
s
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
for
f
o
r
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine
e
n
g
i
n
e
in
i
n
consultation
c
o
n
s
u
l
t
a
t
i
o
n
with
w
i
t
h
the
t
h
e
applicant.
a
p
p
l
i
c
a
n
t
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
defines
d
e
f
i
n
e
s
the
t
h
e
particular
p
a
r
t
i
c
u
l
a
r
regulations
r
e
g
u
l
a
t
i
o
n
s
together
t
o
g
e
t
h
e
r
with
w
i
t
h
any
a
n
y
special
s
p
e
c
i
a
l
conditions
c
o
n
d
i
t
i
o
n
s
which
w
h
i
c
h
may
m
a
y
supplement
s
u
p
p
l
e
m
e
n
t
the
t
h
e
published
p
u
b
l
i
s
h
e
d
regulations.
r
e
g
u
l
a
t
i
o
n
s
.
For
F
o
r
modified
m
o
d
i
f
i
e
d
aircraft
a
i
r
c
r
a
f
t
or
o
r
engines,
e
n
g
i
n
e
s
,
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
considers
c
o
n
s
i
d
e
r
s
the
t
h
e
impact
i
m
p
a
c
t
the
t
h
e
modification
m
o
d
i
f
i
c
a
t
i
o
n
has
h
a
s
on
o
n
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
originally
o
r
i
g
i
n
a
l
l
y
established
e
s
t
a
b
l
i
s
h
e
d
for
f
o
r
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine.
e
n
g
i
n
e
.
In
I
n
some
s
o
m
e
cases,
c
a
s
e
s
,
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
for
f
o
r
the
t
h
e
modification
m
o
d
i
f
i
c
a
t
i
o
n
may
m
a
y
not
n
o
t
change
c
h
a
n
g
e
from
f
r
o
m
the
t
h
e
original
o
r
i
g
i
n
a
l
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis;
b
a
s
i
s
;
however,
h
o
w
e
v
e
r
,
the
t
h
e
original
o
r
i
g
i
n
a
l
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
may
m
a
y
not
n
o
t
be
b
e
applicable
a
p
p
l
i
c
a
b
l
e
for
f
o
r
showing
s
h
o
w
i
n
g
that
t
h
a
t
the
t
h
e
modification
m
o
d
i
f
i
c
a
t
i
o
n
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
and
a
n
d
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
changed.
c
h
a
n
g
e
d
.
10.2
1
0
.
2
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
assesses
a
s
s
e
s
s
e
s
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
for
f
o
r
completeness
c
o
m
p
l
e
t
e
n
e
s
s
and
a
n
d
consistency
c
o
n
s
i
s
t
e
n
c
y
with
w
i
t
h
the
t
h
e
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
that
t
h
a
t
was
w
a
s
agreed
a
g
r
e
e
d
upon
u
p
o
n
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis.
b
a
s
i
s
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
satisfies
s
a
t
i
s
f
i
e
s
itself
i
t
s
e
l
f
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
proposed
p
r
o
p
o
s
e
d
by
b
y
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
is
i
s
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
and
a
n
d
other
o
t
h
e
r
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
informs
i
n
f
o
r
m
s
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
of
o
f
issues
i
s
s
u
e
s
with
w
i
t
h
the
t
h
e
proposed
p
r
o
p
o
s
e
d
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
that
t
h
a
t
need
n
e
e
d
to
t
o
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
prior
p
r
i
o
r
to
t
o
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
agreement.
a
g
r
e
e
m
e
n
t
.
10.3
1
0
.
3
Compliance
C
o
m
p
l
i
a
n
c
e
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
Prior
P
r
i
o
r
to
t
o
certification,
c
e
r
t
i
f
i
c
a
t
i
o
n
,
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
determines
d
e
t
e
r
m
i
n
e
s
that
t
h
a
t
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine
e
n
g
i
n
e
(including
(
i
n
c
l
u
d
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
its
i
t
s
systems
s
y
s
t
e
m
s
or
o
r
equipment)
e
q
u
i
p
m
e
n
t
)
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis.
b
a
s
i
s
.
For
F
o
r
the
t
h
e
software,
s
o
f
t
w
a
r
e
,
this
t
h
i
s
is
i
s
accomplished
a
c
c
o
m
p
l
i
s
h
e
d
by
b
y
reviewing
r
e
v
i
e
w
i
n
g
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
and
a
n
d
evidence
e
v
i
d
e
n
c
e
of
o
f
compliance.
c
o
m
p
l
i
a
n
c
e
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
uses
u
s
e
s
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
as
a
s
an
a
n
overview
o
v
e
r
v
i
e
w
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
may
m
a
y
review
r
e
v
i
e
w
at
a
t
its
i
t
s
discretion
d
i
s
c
r
e
t
i
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
their
t
h
e
i
r
outputs
o
u
t
p
u
t
s
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
as
a
s
discussed
d
i
s
c
u
s
s
e
d
in
i
n
subsection
s
u
b
s
e
c
t
i
o
n
9.2.
9
.
2
.
45
4
5
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
IS
I
S
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
11.0
1
1
.
0
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE
C
Y
C
L
E
DATA
D
A
T
A
Data
D
a
t
a
is
i
s
produced
p
r
o
d
u
c
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
to
t
o
plan,
p
l
a
n
,
direct,
d
i
r
e
c
t
,
explain,
e
x
p
l
a
i
n
,
define,
d
e
f
i
n
e
,
record,
r
e
c
o
r
d
,
or
o
r
provide
p
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
e
of
o
f
activities.
a
c
t
i
v
i
t
i
e
s
.
This
T
h
i
s
data
d
a
t
a
enables
e
n
a
b
l
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
certification,
c
e
r
t
i
f
i
c
a
t
i
o
n
,
and
a
n
d
post-certification
p
o
s
t
-
c
e
r
t
i
f
i
c
a
t
i
o
n
modification
m
o
d
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
This
T
h
i
s
section
s
e
c
t
i
o
n
discusses
d
i
s
c
u
s
s
e
s
the
t
h
e
characteristics,
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
,
form,
f
o
r
m
,
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
controls,
c
o
n
t
r
o
l
s
,
and
a
n
d
content
c
o
n
t
e
n
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
The
T
h
e
characteristics
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
are:
a
r
e
:
-
Unambiguous:
U
n
a
m
b
i
g
u
o
u
s
:
Information
I
n
f
o
r
m
a
t
i
o
n
is
i
s
unambiguous
u
n
a
m
b
i
g
u
o
u
s
if
i
f
it
i
t
is
i
s
written
w
r
i
t
t
e
n
in
i
n
terms
t
e
r
m
s
which
w
h
i
c
h
only
o
n
l
y
allow
a
l
l
o
w
a
a
single
s
i
n
g
l
e
interpretation,
i
n
t
e
r
p
r
e
t
a
t
i
o
n
,
aided
a
i
d
e
d
if
i
f
necessary
n
e
c
e
s
s
a
r
y
by
b
y
a
a
definition.
d
e
f
i
n
i
t
i
o
n
.
-
Complete:
C
o
m
p
l
e
t
e
:
Information
I
n
f
o
r
m
a
t
i
o
n
is
i
s
complete
c
o
m
p
l
e
t
e
when
w
h
e
n
it
i
t
includes
i
n
c
l
u
d
e
s
necessary,
n
e
c
e
s
s
a
r
y
,
relevant
r
e
l
e
v
a
n
t
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and/or
a
n
d
/
o
r
descriptive
d
e
s
c
r
i
p
t
i
v
e
material,
m
a
t
e
r
i
a
l
,
responses
r
e
s
p
o
n
s
e
s
are
a
r
e
defined
d
e
f
i
n
e
d
for
f
o
r
the
t
h
e
range
r
a
n
g
e
of
o
f
valid
v
a
l
i
d
input
i
n
p
u
t
data,
d
a
t
a
,
figures
f
i
g
u
r
e
s
used
u
s
e
d
are
a
r
e
labeled,
l
a
b
e
l
e
d
,
and
a
n
d
terms
t
e
r
m
s
and
a
n
d
units
u
n
i
t
s
of
o
f
measure
m
e
a
s
u
r
e
are
a
r
e
defined.
d
e
f
i
n
e
d
.
-
Verifiable:
V
e
r
i
f
i
a
b
l
e
:
Information
I
n
f
o
r
m
a
t
i
o
n
is
i
s
verifiable
v
e
r
i
f
i
a
b
l
e
if
i
f
it
i
t
can
c
a
n
be
b
e
checked
c
h
e
c
k
e
d
for
f
o
r
correctness
c
o
r
r
e
c
t
n
e
s
s
by
b
y
a
a
person
p
e
r
s
o
n
or
o
r
tool.
t
o
o
l
.
-
Consistent:
C
o
n
s
i
s
t
e
n
t
:
Information
I
n
f
o
r
m
a
t
i
o
n
is
i
s
consistent
c
o
n
s
i
s
t
e
n
t
if
i
f
there
t
h
e
r
e
are
a
r
e
no
n
o
conflicts
c
o
n
f
l
i
c
t
s
within
w
i
t
h
i
n
it.
i
t
.
-
Modifiable:
M
o
d
i
f
i
a
b
l
e
:
Information
I
n
f
o
r
m
a
t
i
o
n
is
i
s
modifiable
m
o
d
i
f
i
a
b
l
e
if
i
f
it
i
t
is
i
s
structured
s
t
r
u
c
t
u
r
e
d
and
a
n
d
has
h
a
s
a
a
style
s
t
y
l
e
such
s
u
c
h
that
t
h
a
t
changes
c
h
a
n
g
e
s
can
c
a
n
be
b
e
made
m
a
d
e
completely,
c
o
m
p
l
e
t
e
l
y
,
consis
c
o
n
s
i
s
tently,
t
e
n
t
l
y
,
and
a
n
d
correctly
c
o
r
r
e
c
t
l
y
while
w
h
i
l
e
retaining
r
e
t
a
i
n
i
n
g
the
t
h
e
structure.
s
t
r
u
c
t
u
r
e
.
-
Traceable:
T
r
a
c
e
a
b
l
e
:
Information
I
n
f
o
r
m
a
t
i
o
n
is
i
s
traceable
t
r
a
c
e
a
b
l
e
if
i
f
the
t
h
e
origin
o
r
i
g
i
n
of
o
f
its
i
t
s
components
c
o
m
p
o
n
e
n
t
s
can
c
a
n
be
b
e
determined.
d
e
t
e
r
m
i
n
e
d
.
In
I
n
addition,
a
d
d
i
t
i
o
n
,
this
t
h
i
s
guidance
g
u
i
d
a
n
c
e
applies:
a
p
p
l
i
e
s
:
-
Form:
F
o
r
m
:
The
T
h
e
form
f
o
r
m
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
for
f
o
r
the
t
h
e
efficient
e
f
f
i
c
i
e
n
t
retrieval
r
e
t
r
i
e
v
a
l
and
a
n
d
review
r
e
v
i
e
w
of
o
f
software
s
o
f
t
w
a
r
e
fife
f
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
service
s
e
r
v
i
c
e
life
l
i
f
e
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
The
T
h
e
data
d
a
t
a
and
a
n
d
the
t
h
e
specific
s
p
e
c
i
f
i
c
form
f
o
r
m
of
o
f
the
t
h
e
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
Note:
N
o
t
e
:
(1)
(
1
)
The
T
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
may
m
a
y
take
t
a
k
e
a
a
number
n
u
m
b
e
r
of
o
f
forms.
f
o
r
m
s
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
it
i
t
can
c
a
n
be
b
e
in
i
n
written
w
r
i
t
t
e
n
form,
f
o
r
m
,
as
a
s
computer
c
o
m
p
u
t
e
r
files
f
i
l
e
s
stored
s
t
o
r
e
d
on
o
n
magnetic
m
a
g
n
e
t
i
c
media,
m
e
d
i
a
,
or
o
r
as
a
s
displays
d
i
s
p
l
a
y
s
on
o
n
a
a
remote
r
e
m
o
t
e
terminal.
t
e
r
m
i
n
a
l
.
It
I
t
may
m
a
y
be
b
e
packaged
p
a
c
k
a
g
e
d
as
a
s
individual
i
n
d
i
v
i
d
u
a
l
documents,
d
o
c
u
m
e
n
t
s
,
combined
c
o
m
b
i
n
e
d
into
i
n
t
o
larger
l
a
r
g
e
r
documents,
d
o
c
u
m
e
n
t
s
,
or
o
r
distributed
d
i
s
t
r
i
b
u
t
e
d
across
a
c
r
o
s
s
several
s
e
v
e
r
a
l
documents.
d
o
c
u
m
e
n
t
s
.
(2)
(
2
)
The
T
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
may
m
a
y
be
b
e
required
r
e
q
u
i
r
e
d
as
a
s
separate
s
e
p
a
r
a
t
e
printed
p
r
i
n
t
e
d
documents
d
o
c
u
m
e
n
t
s
by
b
y
some
s
o
m
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authorities.
a
u
t
h
o
r
i
t
i
e
s
.
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
can
c
a
n
be
b
e
placed
p
l
a
c
e
d
in
i
n
one
o
n
e
of
o
f
two
t
w
o
categories
c
a
t
e
g
o
r
i
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
controls
c
o
n
t
r
o
l
s
applied:
a
p
p
l
i
e
d
:
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
1
1
(CC1)
(
C
C
1
)
and
a
n
d
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
(CC2)
(
C
C
2
)
(subsection
(
s
u
b
s
e
c
t
i
o
n
7.3).
7
.
3
)
.
This
T
h
i
s
distinction
d
i
s
t
i
n
c
t
i
o
n
provides
p
r
o
v
i
d
e
s
a
a
means
m
e
a
n
s
to
t
o
manage
m
a
n
a
g
e
development
d
e
v
e
l
o
p
m
e
n
t
costs
c
o
s
t
s
where
w
h
e
r
e
less
l
e
s
s
stringent
s
t
r
i
n
g
e
n
t
controls
c
o
n
t
r
o
l
s
can
c
a
n
be
b
e
applied
a
p
p
l
i
e
d
without
w
i
t
h
o
u
t
a
a
reduction
r
e
d
u
c
t
i
o
n
in
i
n
safety.
s
a
f
e
t
y
.
The
T
h
e
minimum
m
i
n
i
m
u
m
control
c
o
n
t
r
o
l
category
c
a
t
e
g
o
r
y
assigned
a
s
s
i
g
n
e
d
to
t
o
each
e
a
c
h
data
d
a
t
a
item,
i
t
e
m
,
and
a
n
d
its
i
t
s
variation
v
a
r
i
a
t
i
o
n
by
b
y
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
Annex
A
n
n
e
x
A.
A
.
The
T
h
e
following
f
o
l
l
o
w
i
n
g
data
d
a
t
a
descriptions
d
e
s
c
r
i
p
t
i
o
n
s
define
d
e
f
i
n
e
the
t
h
e
data
d
a
t
a
generally
g
e
n
e
r
a
l
l
y
produced
p
r
o
d
u
c
e
d
to
t
o
aid
a
i
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
The
T
h
e
descriptions
d
e
s
c
r
i
p
t
i
o
n
s
are
a
r
e
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
describe
d
e
s
c
r
i
b
e
all
a
l
l
data
d
a
t
a
necessary
n
e
c
e
s
s
a
r
y
to
t
o
develop
d
e
v
e
l
o
p
a
a
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
and
a
n
d
are
a
r
e
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
imply
i
m
p
l
y
a
a
particular
p
a
r
t
i
c
u
l
a
r
data
d
a
t
a
packaging
p
a
c
k
a
g
i
n
g
method
m
e
t
h
o
d
or
o
r
organization
o
r
g
a
n
i
z
a
t
i
o
n
of
o
f
the
t
h
e
data
d
a
t
a
within
w
i
t
h
i
n
a
a
package.
p
a
c
k
a
g
e
.
In
I
n
addition
a
d
d
i
t
i
o
n
to
t
o
the
t
h
e
data
d
a
t
a
defined
d
e
f
i
n
e
d
in
i
n
these
t
h
e
s
e
subsections,
s
u
b
s
e
c
t
i
o
n
s
,
other
o
t
h
e
r
data
d
a
t
a
may
m
a
y
be
b
e
produced
p
r
o
d
u
c
e
d
as
a
s
evidence
e
v
i
d
e
n
c
e
to
t
o
aid
a
i
d
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
-
Control:
C
o
n
t
r
o
l
:
If
I
f
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
used
u
s
e
d
for
f
o
r
this
t
h
i
s
purpose,
p
u
r
p
o
s
e
,
this
t
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
plan
p
l
a
n
which
w
h
i
c
h
defines
d
e
f
i
n
e
s
the
t
h
e
process
p
r
o
c
e
s
s
for
f
o
r
which
w
h
i
c
h
the
t
h
e
data
d
a
t
a
will
w
i
l
l
be
b
e
produced.
p
r
o
d
u
c
e
d
.
While
W
h
i
l
e
the
t
h
e
nature
n
a
t
u
r
e
and
a
n
d
content
c
o
n
t
e
n
t
of
o
f
this
t
h
i
s
data
d
a
t
a
may
m
a
y
vary,
v
a
r
y
,
as
a
s
a
a
minimum,
m
i
n
i
m
u
m
,
CC2
C
C
2
controls
c
o
n
t
r
o
l
s
should
s
h
o
u
l
d
be
b
e
applied.
a
p
p
l
i
e
d
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
memoranda
m
e
m
o
r
a
n
d
a
and
a
n
d
meeting
m
e
e
t
i
n
g
minutes.
m
i
n
u
t
e
s
.
47
4
7
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
48
4
8
-
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
The
T
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
is
i
s
the
t
h
e
primary
p
r
i
m
a
r
y
means
m
e
a
n
s
used
u
s
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
for
f
o
r
determining
d
e
t
e
r
m
i
n
i
n
g
whether
w
h
e
t
h
e
r
an
a
n
applicant
a
p
p
l
i
c
a
n
t
is
i
s
proposing
p
r
o
p
o
s
i
n
g
a
a
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
that
t
h
a
t
is
i
s
commensurate
c
o
m
m
e
n
s
u
r
a
t
e
with
w
i
t
h
the
t
h
e
rigor
r
i
g
o
r
required
r
e
q
u
i
r
e
d
for
f
o
r
the
t
h
e
level
l
e
v
e
l
of
o
f
software
s
o
f
t
w
a
r
e
being
b
e
i
n
g
developed.
d
e
v
e
l
o
p
e
d
.
This
T
h
i
s
plan
p
l
a
n
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
System
S
y
s
t
e
m
overview:
o
v
e
r
v
i
e
w
:
This
T
h
i
s
section
s
e
c
t
i
o
n
provides
p
r
o
v
i
d
e
s
an
a
n
overview
o
v
e
r
v
i
e
w
of
o
f
the
t
h
e
system,
s
y
s
t
e
m
,
including
i
n
c
l
u
d
i
n
g
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
its
i
t
s
functions
f
u
n
c
t
i
o
n
s
and
a
n
d
their
t
h
e
i
r
allocation
a
l
l
o
c
a
t
i
o
n
to
t
o
the
t
h
e
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software,
s
o
f
t
w
a
r
e
,
the
t
h
e
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
processor(s)
p
r
o
c
e
s
s
o
r
(
s
)
used,
u
s
e
d
,
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
interfaces,
i
n
t
e
r
f
a
c
e
s
,
and
a
n
d
safety
s
a
f
e
t
y
features.
f
e
a
t
u
r
e
s
.
-
Software
S
o
f
t
w
a
r
e
overview:
o
v
e
r
v
i
e
w
:
This
T
h
i
s
section
s
e
c
t
i
o
n
briefly
b
r
i
e
f
l
y
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
functions
f
u
n
c
t
i
o
n
s
with
w
i
t
h
emphasis
e
m
p
h
a
s
i
s
on
o
n
the
t
h
e
proposed
p
r
o
p
o
s
e
d
safety
s
a
f
e
t
y
and
a
n
d
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
concepts,
c
o
n
c
e
p
t
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
resource
r
e
s
o
u
r
c
e
sharing,
s
h
a
r
i
n
g
,
redundancy,
r
e
d
u
n
d
a
n
c
y
,
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software,
s
o
f
t
w
a
r
e
,
fault
f
a
u
l
t
tolerance,
t
o
l
e
r
a
n
c
e
,
and
a
n
d
timing
t
i
m
i
n
g
and
a
n
d
scheduling
s
c
h
e
d
u
l
i
n
g
strategies.
s
t
r
a
t
e
g
i
e
s
.
-
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
considerations.
c
o
n
s
i
d
e
r
a
t
i
o
n
s
.
This
T
h
i
s
section
s
e
c
t
i
o
n
provides
p
r
o
v
i
d
e
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis,
b
a
s
i
s
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
means
m
e
a
n
s
of
o
f
compliance,
c
o
m
p
l
i
a
n
c
e
,
as
a
s
relating
r
e
l
a
t
i
n
g
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
This
T
h
i
s
section
s
e
c
t
i
o
n
also
a
l
s
o
states
s
t
a
t
e
s
the
t
h
e
proposed
p
r
o
p
o
s
e
d
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
and
a
n
d
summarizes
s
u
m
m
a
r
i
z
e
s
the
t
h
e
justification
j
u
s
t
i
f
i
c
a
t
i
o
n
provided
p
r
o
v
i
d
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process,
p
r
o
c
e
s
s
,
including
i
n
c
l
u
d
i
n
g
potential
p
o
t
e
n
t
i
a
l
software
s
o
f
t
w
a
r
e
contributions
c
o
n
t
r
i
b
u
t
i
o
n
s
to
t
o
failure
f
a
i
l
u
r
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle:
c
y
c
l
e
:
This
T
h
i
s
section
s
e
c
t
i
o
n
defines
d
e
f
i
n
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
to
t
o
be
b
e
used
u
s
e
d
and
a
n
d
includes
i
n
c
l
u
d
e
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
each
e
a
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
and
a
n
d
its
i
t
s
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
which
w
h
i
c
h
detailed
d
e
t
a
i
l
e
d
information
i
n
f
o
r
m
a
t
i
o
n
is
i
s
defined
d
e
f
i
n
e
d
in
i
n
their
t
h
e
i
r
respective
r
e
s
p
e
c
t
i
v
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
The
T
h
e
summary
s
u
m
m
a
r
y
explains
e
x
p
l
a
i
n
s
how
h
o
w
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
each
e
a
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
will
w
i
l
l
be
b
e
satisfied,
s
a
t
i
s
f
i
e
d
,
and
a
n
d
specifies
s
p
e
c
i
f
i
e
s
the
t
h
e
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
to
t
o
be
b
e
involved,
i
n
v
o
l
v
e
d
,
the
t
h
e
organizational
o
r
g
a
n
i
z
a
t
i
o
n
a
l
responsibilities,
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
,
and
a
n
d
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process
p
r
o
c
e
s
s
responsibilities.
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data:
d
a
t
a
:
This
T
h
i
s
section
s
e
c
t
i
o
n
specifies
s
p
e
c
i
f
i
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
that
t
h
a
t
will
w
i
l
l
be
b
e
produced
p
r
o
d
u
c
e
d
and
a
n
d
controlled
c
o
n
t
r
o
l
l
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
This
T
h
i
s
section
s
e
c
t
i
o
n
also
a
l
s
o
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
of
o
f
the
t
h
e
data
d
a
t
a
to
t
o
each
e
a
c
h
other
o
t
h
e
r
or
o
r
to
t
o
other
o
t
h
e
r
data
d
a
t
a
defining
d
e
f
i
n
i
n
g
the
t
h
e
system,
s
y
s
t
e
m
,
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
to
t
o
be
b
e
submitted
s
u
b
m
i
t
t
e
d
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority,
a
u
t
h
o
r
i
t
y
,
the
t
h
e
form
f
o
r
m
of
o
f
the
t
h
e
data,
d
a
t
a
,
and
a
n
d
the
t
h
e
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
will
w
i
l
l
be
b
e
made
m
a
d
e
available
a
v
a
i
l
a
b
l
e
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
-
Schedule:
S
c
h
e
d
u
l
e
:
This
T
h
i
s
section
s
e
c
t
i
o
n
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
means
m
e
a
n
s
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
will
w
i
l
l
use
u
s
e
to
t
o
provide
p
r
o
v
i
d
e
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
with
w
i
t
h
visibility
v
i
s
i
b
i
l
i
t
y
of
o
f
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
so
s
o
reviews
r
e
v
i
e
w
s
can
c
a
n
be
b
e
planned.
p
l
a
n
n
e
d
.
-
Additional
A
d
d
i
t
i
o
n
a
l
considerations.:
c
o
n
s
i
d
e
r
a
t
i
o
n
s
.
:
This
T
h
i
s
section
s
e
c
t
i
o
n
describes
d
e
s
c
r
i
b
e
s
specific
s
p
e
c
i
f
i
c
features
f
e
a
t
u
r
e
s
that
t
h
a
t
may
m
a
y
affect
a
f
f
e
c
t
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process,
p
r
o
c
e
s
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
alternative
a
l
t
e
r
n
a
t
i
v
e
methods
m
e
t
h
o
d
s
of
o
f
compliance,
c
o
m
p
l
i
a
n
c
e
,
tool
t
o
o
l
qualification,
q
u
a
l
i
f
i
c
a
t
i
o
n
,
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
option-selectable
o
p
t
i
o
n
-
s
e
l
e
c
t
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
COTS
C
O
T
S
software,
s
o
f
t
w
a
r
e
,
field
f
i
e
l
d
-loadable
-
l
o
a
d
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software,
s
o
f
t
w
a
r
e
,
and
a
n
d
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
-
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
The
T
h
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
includes
i
n
c
l
u
d
e
s
the
t
h
e
objectives,
o
b
j
e
c
t
i
v
e
s
,
standards
s
t
a
n
d
a
r
d
s
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle(s)
c
y
c
l
e
(
s
)
to
t
o
be
b
e
used
u
s
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
It
I
t
may
m
a
y
be
b
e
included
i
n
c
l
u
d
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
This
T
h
i
s
plan
p
l
a
n
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Standards:
S
t
a
n
d
a
r
d
s
:
Identification
I
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards,
S
t
a
n
d
a
r
d
s
,
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
and
a
n
d
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
for
f
o
r
the
t
h
e
project.
p
r
o
j
e
c
t
.
Also,
A
l
s
o
,
references
r
e
f
e
r
e
n
c
e
s
to
t
o
the
t
h
e
standards
s
t
a
n
d
a
r
d
s
for
f
o
r
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
including
i
n
c
l
u
d
i
n
g
COTS
C
O
T
S
software,
s
o
f
t
w
a
r
e
,
if
i
f
those
t
h
o
s
e
standards
s
t
a
n
d
a
r
d
s
are
a
r
e
different.
d
i
f
f
e
r
e
n
t
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle:
c
y
c
l
e
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
form
f
o
r
m
the
t
h
e
specific
s
p
e
c
i
f
i
c
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle(s)
c
y
c
l
e
(
s
)
to
t
o
be
b
e
used
u
s
e
d
on
o
n
the
t
h
e
project,
p
r
o
j
e
c
t
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
This
T
h
i
s
description
d
e
s
c
r
i
p
t
i
o
n
is
i
s
distinct
d
i
s
t
i
n
c
t
from
f
r
o
m
the
t
h
e
summary
s
u
m
m
a
r
y
provided
p
r
o
v
i
d
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification,
C
e
r
t
i
f
i
c
a
t
i
o
n
,
in
i
n
that
t
h
a
t
it
i
t
provides
p
r
o
v
i
d
e
s
the
t
h
e
detail
d
e
t
a
i
l
necessary
n
e
c
e
s
s
a
r
y
to
t
o
ensure
e
n
s
u
r
e
proper
p
r
o
p
e
r
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
.
.
-
Software
S
o
f
t
w
a
r
e
evelopment
e
v
e
l
o
p
m
e
n
t
environment:
e
n
v
i
r
o
n
m
e
n
t
:
A
A
statement
s
t
a
t
e
m
e
n
t
of
o
f
the
t
h
e
chosen
c
h
o
s
e
n
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
in
i
n
terms
t
e
r
m
s
of
o
f
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software,
s
o
f
t
w
a
r
e
,
including:
i
n
c
l
u
d
i
n
g
:
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
-
The
T
h
e
chosen
c
h
o
s
e
n
requirements
r
e
q
u
i
r
e
m
e
n
t
s
development
d
e
v
e
l
o
p
m
e
n
t
method(s)
m
e
t
h
o
d
(
s
)
and
a
n
d
tools
t
o
o
l
s
to
t
o
be
b
e
used.
u
s
e
d
.
-
The
T
h
e
chosen
c
h
o
s
e
n
design
d
e
s
i
g
n
method(s)
m
e
t
h
o
d
(
s
)
and
a
n
d
tools
t
o
o
l
s
to
t
o
be
b
e
used.
u
s
e
d
.
-
The
T
h
e
programming
p
r
o
g
r
a
m
m
i
n
g
language(s),
l
a
n
g
u
a
g
e
(
s
)
,
coding
c
o
d
i
n
g
tools,
t
o
o
l
s
,
compilers,
c
o
m
p
i
l
e
r
s
,
linkage
l
i
n
k
a
g
e
editors
e
d
i
t
o
r
s
and
a
n
d
loaders
l
o
a
d
e
r
s
to
t
o
be
b
e
used.
u
s
e
d
.
-
The
T
h
e
hardware
h
a
r
d
w
a
r
e
platforms
p
l
a
t
f
o
r
m
s
for
f
o
r
the
t
h
e
tools
t
o
o
l
s
to
t
o
be
b
e
used.
u
s
e
d
.
The
T
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
is
i
s
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
procedures
p
r
o
c
e
d
u
r
e
s
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives.
o
b
j
e
c
t
i
v
e
s
.
These
T
h
e
s
e
procedures
p
r
o
c
e
d
u
r
e
s
may
m
a
y
vary
v
a
r
y
by
b
y
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
tables
t
a
b
l
e
s
of
o
f
Annex
A
n
n
e
x
A.
A
.
This
T
h
i
s
plan
p
l
a
n
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Organization:
O
r
g
a
n
i
z
a
t
i
o
n
:
Organizational
O
r
g
a
n
i
z
a
t
i
o
n
a
l
responsibilities
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
within
w
i
t
h
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
and
a
n
d
interfaces
i
n
t
e
r
f
a
c
e
s
with
w
i
t
h
the
t
h
e
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
-
Independence:
I
n
d
e
p
e
n
d
e
n
c
e
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
methods
m
e
t
h
o
d
s
for
f
o
r
establishing
e
s
t
a
b
l
i
s
h
i
n
g
verification
v
e
r
i
f
i
c
a
t
i
o
n
independence,
i
n
d
e
p
e
n
d
e
n
c
e
,
when
w
h
e
n
required.
r
e
q
u
i
r
e
d
.
-
Verification
V
e
r
i
f
i
c
a
t
i
o
n
methods:
m
e
t
h
o
d
s
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
methods
m
e
t
h
o
d
s
to
t
o
be
b
e
used
u
s
e
d
for
f
o
r
each
e
a
c
h
activity
a
c
t
i
v
i
t
y
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
-
Review
R
e
v
i
e
w
methods,
m
e
t
h
o
d
s
,
including
i
n
c
l
u
d
i
n
g
checklists
c
h
e
c
k
l
i
s
t
s
or
o
r
other
o
t
h
e
r
aids.
a
i
d
s
.
-
Analysis
A
n
a
l
y
s
i
s
methods,
m
e
t
h
o
d
s
,
including
i
n
c
l
u
d
i
n
g
traceability
t
r
a
c
e
a
b
i
l
i
t
y
and
a
n
d
coverage
c
o
v
e
r
a
g
e
analysis.
a
n
a
l
y
s
i
s
.
-
Testing
T
e
s
t
i
n
g
methods,
m
e
t
h
o
d
s
,
including
i
n
c
l
u
d
i
n
g
guidelines
g
u
i
d
e
l
i
n
e
s
that
t
h
a
t
establish
e
s
t
a
b
l
i
s
h
the
t
h
e
test
t
e
s
t
case
c
a
s
e
selection
s
e
l
e
c
t
i
o
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
to
t
o
be
b
e
used,
u
s
e
d
,
and
a
n
d
the
t
h
e
test
t
e
s
t
data
d
a
t
a
to
t
o
be
b
e
produced.
p
r
o
d
u
c
e
d
.
d
d
Verification
V
e
r
i
f
i
c
a
t
i
o
n
environment:
e
n
v
i
r
o
n
m
e
n
t
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
equipment
e
q
u
i
p
m
e
n
t
for
f
o
r
testing,
t
e
s
t
i
n
g
,
the
t
h
e
testing
t
e
s
t
i
n
g
and
a
n
d
analysis
a
n
a
l
y
s
i
s
tools,
t
o
o
l
s
,
and
a
n
d
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
for
f
o
r
applying
a
p
p
l
y
i
n
g
these
t
h
e
s
e
tools
t
o
o
l
s
and
a
n
d
hardware
h
a
r
d
w
a
r
e
test
t
e
s
t
equipment
e
q
u
i
p
m
e
n
t
(see
(
s
e
e
also
a
l
s
o
paragraph
p
a
r
a
g
r
a
p
h
4.4.3,
4
.
4
.
3
,
item
i
t
e
m
b
b
for
f
o
r
guidance
g
u
i
d
a
n
c
e
on
o
n
indicating
i
n
d
i
c
a
t
i
n
g
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
and
a
n
d
simulator
s
i
m
u
l
a
t
o
r
or
o
r
emulator
e
m
u
l
a
t
o
r
differences).
d
i
f
f
e
r
e
n
c
e
s
)
.
-
Transition
T
r
a
n
s
i
t
i
o
n
criteria:
c
r
i
t
e
r
i
a
:
The
T
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
entering
e
n
t
e
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
defined
d
e
f
i
n
e
d
in
i
n
this
t
h
i
s
plan.
p
l
a
n
.
-
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
considerations:
c
o
n
s
i
d
e
r
a
t
i
o
n
s
:
If
I
f
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
is
i
s
used,
u
s
e
d
,
the
t
h
e
methods
m
e
t
h
o
d
s
used
u
s
e
d
to
t
o
verify
v
e
r
i
f
y
the
t
h
e
integrity
i
n
t
e
g
r
i
t
y
of
o
f
the
t
h
e
partitioning.
p
a
r
t
i
t
i
o
n
i
n
g
.
-
Compiler
C
o
m
p
i
l
e
r
assumptions:
a
s
s
u
m
p
t
i
o
n
s
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
assumptions
a
s
s
u
m
p
t
i
o
n
s
made
m
a
d
e
by
b
y
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
about
a
b
o
u
t
the
t
h
e
correctness
c
o
r
r
e
c
t
n
e
s
s
of
o
f
the
t
h
e
compiler,
c
o
m
p
i
l
e
r
,
linkage
l
i
n
k
a
g
e
editor
e
d
i
t
o
r
or
o
r
loader
l
o
a
d
e
r
(paragraph
(
p
a
r
a
g
r
a
p
h
4.4.2).
4
.
4
.
2
)
.
-
Reverification
R
e
v
e
r
i
f
i
c
a
t
i
o
n
Guidelines:
G
u
i
d
e
l
i
n
e
s
:
For
F
o
r
software
s
o
f
t
w
a
r
e
modification,
m
o
d
i
f
i
c
a
t
i
o
n
,
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
methods
m
e
t
h
o
d
s
for
f
o
r
identifying
i
d
e
n
t
i
f
y
i
n
g
the
t
h
e
affected
a
f
f
e
c
t
e
d
areas
a
r
e
a
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
and
a
n
d
the
t
h
e
changed
c
h
a
n
g
e
d
parts
p
a
r
t
s
of
o
f
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
The
T
h
e
reverification
r
e
v
e
r
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
ensure
e
n
s
u
r
e
that
t
h
a
t
previously
p
r
e
v
i
o
u
s
l
y
reported
r
e
p
o
r
t
e
d
errors
e
r
r
o
r
s
or
o
r
classes
c
l
a
s
s
e
s
of
o
f
errors
e
r
r
o
r
s
have
h
a
v
e
been
b
e
e
n
eliminated.
e
l
i
m
i
n
a
t
e
d
.
-
Previously
P
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software:
s
o
f
t
w
a
r
e
:
For
F
o
r
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
if
i
f
the
t
h
e
initial
i
n
i
t
i
a
l
compliance
c
o
m
p
l
i
a
n
c
e
baseline
b
a
s
e
l
i
n
e
for
f
o
r
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
does
d
o
e
s
not
n
o
t
comply
c
o
m
p
l
y
with
w
i
t
h
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
methods
m
e
t
h
o
d
s
to
t
o
satis
s
a
t
i
s
fy
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
Multiple-version
M
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software:
s
o
f
t
w
a
r
e
:
If
I
f
multiple
m
u
l
t
i
p
l
e
-version
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
is
i
s
used,
u
s
e
d
,
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
(paragraph
(
p
a
r
a
g
r
a
p
h
12.3.3).
1
2
.
3
.
3
)
.
49
4
9
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
50
5
0
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan
P
l
a
n
The
T
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan
P
l
a
n
establishes
e
s
t
a
b
l
i
s
h
e
s
the
t
h
e
methods
m
e
t
h
o
d
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
achieve
a
c
h
i
e
v
e
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
(SCM)
(
S
C
M
)
process
p
r
o
c
e
s
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
This
T
h
i
s
plan
p
l
a
n
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Environment:
E
n
v
i
r
o
n
m
e
n
t
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
SCM
S
C
M
environment
e
n
v
i
r
o
n
m
e
n
t
to
t
o
be
b
e
used,
u
s
e
d
,
including
i
n
c
l
u
d
i
n
g
procedures,
p
r
o
c
e
d
u
r
e
s
,
tools,
t
o
o
l
s
,
methods,
m
e
t
h
o
d
s
,
standards,
s
t
a
n
d
a
r
d
s
,
organizational
o
r
g
a
n
i
z
a
t
i
o
n
a
l
responsibilities,
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
,
and
a
n
d
interfaces.
i
n
t
e
r
f
a
c
e
s
.
-
Activities:
A
c
t
i
v
i
t
i
e
s
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
that
t
h
a
t
will
w
i
l
l
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for:
f
o
r
:
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
identification:
i
d
e
n
t
i
f
i
c
a
t
i
o
n
:
Items
I
t
e
m
s
to
t
o
be
b
e
identified,
i
d
e
n
t
i
f
i
e
d
,
when
w
h
e
n
they
t
h
e
y
will
w
i
l
l
be
b
e
identified,
i
d
e
n
t
i
f
i
e
d
,
the
t
h
e
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
methods
m
e
t
h
o
d
s
for
f
o
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
part
p
a
r
t
numbering),
n
u
m
b
e
r
i
n
g
)
,
and
a
n
d
the
t
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
of
o
f
software
s
o
f
t
w
a
r
e
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
and
a
n
d
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
identification.
i
d
e
n
t
i
f
i
c
a
t
i
o
n
.
-
Baselines
B
a
s
e
l
i
n
e
s
and
a
n
d
traceability:
t
r
a
c
e
a
b
i
l
i
t
y
:
The
T
h
e
means
m
e
a
n
s
of
o
f
establishing
e
s
t
a
b
l
i
s
h
i
n
g
baselines,
b
a
s
e
l
i
n
e
s
,
what
w
h
a
t
baselines
b
a
s
e
l
i
n
e
s
will
w
i
l
l
be
b
e
established,
e
s
t
a
b
l
i
s
h
e
d
,
when
w
h
e
n
these
t
h
e
s
e
baselines
b
a
s
e
l
i
n
e
s
will
w
i
l
l
be
b
e
established,
e
s
t
a
b
l
i
s
h
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
library
l
i
b
r
a
r
y
controls,
c
o
n
t
r
o
l
s
,
and
a
n
d
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
and
a
n
d
baseline
b
a
s
e
l
i
n
e
traceability.
t
r
a
c
e
a
b
i
l
i
t
y
.
-
Problem
P
r
o
b
l
e
m
reporting:
r
e
p
o
r
t
i
n
g
:
The
T
h
e
content
c
o
n
t
e
n
t
and
a
n
d
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
problem
p
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes,
p
r
o
c
e
s
s
e
s
,
when
w
h
e
n
they
t
h
e
y
will
w
i
l
l
be
b
e
written,
w
r
i
t
t
e
n
,
the
t
h
e
method
m
e
t
h
o
d
of
o
f
closing
c
l
o
s
i
n
g
problem
p
r
o
b
l
e
m
reports,
r
e
p
o
r
t
s
,
and
a
n
d
the
t
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
to
t
o
the
t
h
e
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activity.
a
c
t
i
v
i
t
y
.
-
Change
C
h
a
n
g
e
control:
c
o
n
t
r
o
l
:
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
and
a
n
d
baselines
b
a
s
e
l
i
n
e
s
to
t
o
be
b
e
controlled,
c
o
n
t
r
o
l
l
e
d
,
when
w
h
e
n
they
t
h
e
y
will
w
i
l
l
be
b
e
controlled,
c
o
n
t
r
o
l
l
e
d
,
the
t
h
e
problem/change
p
r
o
b
l
e
m
/
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activities
a
c
t
i
v
i
t
i
e
s
that
t
h
a
t
control
c
o
n
t
r
o
l
them,
t
h
e
m
,
pre-
p
r
e
-
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
controls,
c
o
n
t
r
o
l
s
,
post-certification
p
o
s
t
-
c
e
r
t
i
f
i
c
a
t
i
o
n
controls,
c
o
n
t
r
o
l
s
,
and
a
n
d
the
t
h
e
means
m
e
a
n
s
of
o
f
preserving
p
r
e
s
e
r
v
i
n
g
the
t
h
e
integrity
i
n
t
e
g
r
i
t
y
of
o
f
baselines
b
a
s
e
l
i
n
e
s
and
a
n
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items.
i
t
e
m
s
.
-
Change
C
h
a
n
g
e
review:
r
e
v
i
e
w
:
The
T
h
e
method
m
e
t
h
o
d
of
o
f
handling
h
a
n
d
l
i
n
g
feedback
f
e
e
d
b
a
c
k
from
f
r
o
m
and
a
n
d
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes;
p
r
o
c
e
s
s
e
s
;
the
t
h
e
methods
m
e
t
h
o
d
s
of
o
f
assessing
a
s
s
e
s
s
i
n
g
and
a
n
d
prioritizing
p
r
i
o
r
i
t
i
z
i
n
g
problems,
p
r
o
b
l
e
m
s
,
approving
a
p
p
r
o
v
i
n
g
changes,
c
h
a
n
g
e
s
,
and
a
n
d
handling
h
a
n
d
l
i
n
g
their
t
h
e
i
r
resolution
r
e
s
o
l
u
t
i
o
n
or
o
r
change
c
h
a
n
g
e
implementation;
i
m
p
l
e
m
e
n
t
a
t
i
o
n
;
and
a
n
d
the
t
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
of
o
f
these
t
h
e
s
e
methods
m
e
t
h
o
d
s
to
t
o
the
t
h
e
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
and
a
n
d
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
activities.
a
c
t
i
v
i
t
i
e
s
.
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
status
s
t
a
t
u
s
accounting:
a
c
c
o
u
n
t
i
n
g
:
The
T
h
e
data
d
a
t
a
to
t
o
be
b
e
recorded
r
e
c
o
r
d
e
d
to
t
o
enable
e
n
a
b
l
e
reporting
r
e
p
o
r
t
i
n
g
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
status,
s
t
a
t
u
s
,
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
where
w
h
e
r
e
that
t
h
a
t
data
d
a
t
a
will
w
i
l
l
be
b
e
kept,
k
e
p
t
,
how
h
o
w
it
i
t
will
w
i
l
l
be
b
e
retrieved
r
e
t
r
i
e
v
e
d
for
f
o
r
reporting,
r
e
p
o
r
t
i
n
g
,
and
a
n
d
when
w
h
e
n
it
i
t
will
w
i
l
l
be
b
e
available.
a
v
a
i
l
a
b
l
e
.
-
Archive,
A
r
c
h
i
v
e
,
retrieval,
r
e
t
r
i
e
v
a
l
,
and
a
n
d
release:
r
e
l
e
a
s
e
:
The
T
h
e
integrity
i
n
t
e
g
r
i
t
y
controls,
c
o
n
t
r
o
l
s
,
the
t
h
e
release
r
e
l
e
a
s
e
method
m
e
t
h
o
d
and
a
n
d
authority,
a
u
t
h
o
r
i
t
y
,
and
a
n
d
data
d
a
t
a
retention.
r
e
t
e
n
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
load
l
o
a
d
control:
c
o
n
t
r
o
l
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
safeguards
s
a
f
e
g
u
a
r
d
s
and
a
n
d
records.
r
e
c
o
r
d
s
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
controls:
c
o
n
t
r
o
l
s
:
Controls
C
o
n
t
r
o
l
s
for
f
o
r
the
t
h
e
tools
t
o
o
l
s
used
u
s
e
d
to
t
o
develop,
d
e
v
e
l
o
p
,
build,
b
u
i
l
d
,
verify
v
e
r
i
f
y
and
a
n
d
load
l
o
a
d
the
t
h
e
software,
s
o
f
t
w
a
r
e
,
addressing
a
d
d
r
e
s
s
i
n
g
items
i
t
e
m
s
I
I
through
t
h
r
o
u
g
h
7
7
above.
a
b
o
v
e
.
This
T
h
i
s
includes
i
n
c
l
u
d
e
s
control
c
o
n
t
r
o
l
of
o
f
tools
t
o
o
l
s
to
t
o
be
b
e
qualified.
q
u
a
l
i
f
i
e
d
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
controls:
c
o
n
t
r
o
l
s
:
Controls
C
o
n
t
r
o
l
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
I
I
and
a
n
d
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
data.
d
a
t
a
.
-
Transition
T
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
The
T
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
entering
e
n
t
e
r
i
n
g
the
t
h
e
SCM
S
C
M
process.
p
r
o
c
e
s
s
.
-
SCM
S
C
M
data:
d
a
t
a
:
A
A
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
SCM
S
C
M
process,
p
r
o
c
e
s
s
,
including
i
n
c
l
u
d
i
n
g
SCM
S
C
M
Records,
R
e
c
o
r
d
s
,
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index.
I
n
d
e
x
.
-
Supplier
S
u
p
p
l
i
e
r
control:
c
o
n
t
r
o
l
:
The
T
h
e
means
m
e
a
n
s
of
o
f
applying
a
p
p
l
y
i
n
g
SCM
S
C
M
process
p
r
o
c
e
s
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
sub-tier
s
u
b
-
t
i
e
r
suppliers.
s
u
p
p
l
i
e
r
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Plan
P
l
a
n
The
T
h
e
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Plan
P
l
a
n
establishes
e
s
t
a
b
l
i
s
h
e
s
the
t
h
e
methods
m
e
t
h
o
d
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
achieve
a
c
h
i
e
v
e
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
(SQA)
(
S
Q
A
)
process.
p
r
o
c
e
s
s
.
The
T
h
e
SQA
S
Q
A
Plan
P
l
a
n
may
m
a
y
include
i
n
c
l
u
d
e
descriptions
d
e
s
c
r
i
p
t
i
o
n
s
of
o
f
process
p
r
o
c
e
s
s
improvement,
i
m
p
r
o
v
e
m
e
n
t
,
metrics,
m
e
t
r
i
c
s
,
and
a
n
d
progressive
p
r
o
g
r
e
s
s
i
v
e
management
m
a
n
a
g
e
m
e
n
t
methods.
m
e
t
h
o
d
s
.
This
T
h
i
s
plan
p
l
a
n
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Environment:
E
n
v
i
r
o
n
m
e
n
t
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
SQA
S
Q
A
environment,
e
n
v
i
r
o
n
m
e
n
t
,
including
i
n
c
l
u
d
i
n
g
scope,
s
c
o
p
e
,
organizational
o
r
g
a
n
i
z
a
t
i
o
n
a
l
responsibilities
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
and
a
n
d
interfaces,
i
n
t
e
r
f
a
c
e
s
,
standards,
s
t
a
n
d
a
r
d
s
,
procedures,
p
r
o
c
e
d
u
r
e
s
,
tools
t
o
o
l
s
and
a
n
d
methods.
m
e
t
h
o
d
s
.
-
Authority:
A
u
t
h
o
r
i
t
y
:
A
A
statement
s
t
a
t
e
m
e
n
t
of
o
f
the
t
h
e
SQA
S
Q
A
authority,
a
u
t
h
o
r
i
t
y
,
responsibility,
r
e
s
p
o
n
s
i
b
i
l
i
t
y
,
and
a
n
d
independence,
i
n
d
e
p
e
n
d
e
n
c
e
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
approval
a
p
p
r
o
v
a
l
authority
a
u
t
h
o
r
i
t
y
for
f
o
r
software
s
o
f
t
w
a
r
e
products.
p
r
o
d
u
c
t
s
.
-
Activities:
A
c
t
i
v
i
t
i
e
s
:
The
T
h
e
SQA
S
Q
A
activities
a
c
t
i
v
i
t
i
e
s
that
t
h
a
t
are
a
r
e
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
and
a
n
d
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
including:
i
n
c
l
u
d
i
n
g
:
-
SQA
S
Q
A
methods,
m
e
t
h
o
d
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
reviews,
r
e
v
i
e
w
s
,
audits,
a
u
d
i
t
s
,
reporting,
r
e
p
o
r
t
i
n
g
,
inspections,
i
n
s
p
e
c
t
i
o
n
s
,
and
a
n
d
monitoring
m
o
n
i
t
o
r
i
n
g
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
-
Activities
A
c
t
i
v
i
t
i
e
s
related
r
e
l
a
t
e
d
to
t
o
the
t
h
e
problem
p
r
o
b
l
e
m
reporting,
r
e
p
o
r
t
i
n
g
,
tracking
t
r
a
c
k
i
n
g
and
a
n
d
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
system.
s
y
s
t
e
m
.
-
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
activity.
a
c
t
i
v
i
t
y
.
-
Transition
T
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
The
T
h
e
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
entering
e
n
t
e
r
i
n
g
the
t
h
e
SQA
S
Q
A
process.
p
r
o
c
e
s
s
.
-
Timing:
T
i
m
i
n
g
:
The
T
h
e
timing
t
i
m
i
n
g
of
o
f
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
in
i
n
relation
r
e
l
a
t
i
o
n
to
t
o
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
-
SQA
S
Q
A
Records:
R
e
c
o
r
d
s
:
A
A
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
the
t
h
e
records
r
e
c
o
r
d
s
to
t
o
be
b
e
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
SQA
S
Q
A
process.
p
r
o
c
e
s
s
.
-
Supplier
S
u
p
p
l
i
e
r
control:
c
o
n
t
r
o
l
:
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
means
m
e
a
n
s
of
o
f
ensuring
e
n
s
u
r
i
n
g
that
t
h
a
t
sub-tier
s
u
b
-
t
i
e
r
suppliers'
s
u
p
p
l
i
e
r
s
'
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
will
w
i
l
l
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
SQA
S
Q
A
Plan.
P
l
a
n
.
-
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
methods,
m
e
t
h
o
d
s
,
rules
r
u
l
e
s
and
a
n
d
tools
t
o
o
l
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
These
T
h
e
s
e
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
The
T
h
e
methods
m
e
t
h
o
d
s
to
t
o
be
b
e
used
u
s
e
d
for
f
o
r
developing
d
e
v
e
l
o
p
i
n
g
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
such
s
u
c
h
as
a
s
structured
s
t
r
u
c
t
u
r
e
d
methods.
m
e
t
h
o
d
s
.
-
Notations
N
o
t
a
t
i
o
n
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
express
e
x
p
r
e
s
s
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
such
s
u
c
h
as
a
s
data
d
a
t
a
flow
f
l
o
w
diagrams
d
i
a
g
r
a
m
s
and
a
n
d
formal
f
o
r
m
a
l
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
languages.
l
a
n
g
u
a
g
e
s
.
-
Constraints
C
o
n
s
t
r
a
i
n
t
s
on
o
n
the
t
h
e
use
u
s
e
of
o
f
the
t
h
e
requirement
r
e
q
u
i
r
e
m
e
n
t
development
d
e
v
e
l
o
p
m
e
n
t
tools.
t
o
o
l
s
.
-
The
T
h
e
method
m
e
t
h
o
d
to
t
o
be
b
e
used
u
s
e
d
to
t
o
provide
p
r
o
v
i
d
e
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
the
t
h
e
system
s
y
s
t
e
m
process.
p
r
o
c
e
s
s
.
-
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
methods,
m
e
t
h
o
d
s
,
rules
r
u
l
e
s
and
a
n
d
tools
t
o
o
l
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
develop
d
e
v
e
l
o
p
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
These
T
h
e
s
e
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Design
D
e
s
i
g
n
description
d
e
s
c
r
i
p
t
i
o
n
method(s)
m
e
t
h
o
d
(
s
)
to
t
o
be
b
e
used.
u
s
e
d
.
-
Naming
N
a
m
i
n
g
conventions
c
o
n
v
e
n
t
i
o
n
s
to
t
o
be
b
e
used.
u
s
e
d
.
-
Conditions
C
o
n
d
i
t
i
o
n
s
imposed
i
m
p
o
s
e
d
on
o
n
permitted
p
e
r
m
i
t
t
e
d
design
d
e
s
i
g
n
methods,
m
e
t
h
o
d
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
scheduling,
s
c
h
e
d
u
l
i
n
g
,
and
a
n
d
the
t
h
e
use
u
s
e
of
o
f
interrupts
i
n
t
e
r
r
u
p
t
s
and
a
n
d
event-driven
e
v
e
n
t
-
d
r
i
v
e
n
architectures,
a
r
c
h
i
t
e
c
t
u
r
e
s
,
dynamic
d
y
n
a
m
i
c
tasking,
t
a
s
k
i
n
g
,
re-entry,
r
e
-
e
n
t
r
y
,
global
g
l
o
b
a
l
data,
d
a
t
a
,
and
a
n
d
exception
e
x
c
e
p
t
i
o
n
handling,
h
a
n
d
l
i
n
g
,
and
a
n
d
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
their
t
h
e
i
r
use.
u
s
e
.
-
Constraints
C
o
n
s
t
r
a
i
n
t
s
on
o
n
the
t
h
e
use
u
s
e
of
o
f
the
t
h
e
design
d
e
s
i
g
n
tools.
t
o
o
l
s
.
-
Constraints
C
o
n
s
t
r
a
i
n
t
s
on
o
n
design,
d
e
s
i
g
n
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
exclusion
e
x
c
l
u
s
i
o
n
of
o
f
recursion,
r
e
c
u
r
s
i
o
n
,
dynamic
d
y
n
a
m
i
c
objects,
o
b
j
e
c
t
s
,
data
d
a
t
a
aliases,
a
l
i
a
s
e
s
,
and
a
n
d
compacted
c
o
m
p
a
c
t
e
d
expressions.
e
x
p
r
e
s
s
i
o
n
s
.
-
Complexity
C
o
m
p
l
e
x
i
t
y
restrictions,
r
e
s
t
r
i
c
t
i
o
n
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
maximum
m
a
x
i
m
u
m
level
l
e
v
e
l
of
o
f
nested
n
e
s
t
e
d
calls
c
a
l
l
s
or
o
r
conditional
c
o
n
d
i
t
i
o
n
a
l
structures,
s
t
r
u
c
t
u
r
e
s
,
use
u
s
e
of
o
f
unconditional
u
n
c
o
n
d
i
t
i
o
n
a
l
branches,
b
r
a
n
c
h
e
s
,
and
a
n
d
number
n
u
m
b
e
r
of
o
f
entry/exit
e
n
t
r
y
/
e
x
i
t
points
p
o
i
n
t
s
of
o
f
code
c
o
d
e
components.
c
o
m
p
o
n
e
n
t
s
.
51
5
1
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
52
5
2
-
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
the
t
h
e
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
is
i
s
to
t
o
define
d
e
f
i
n
e
the
t
h
e
programming
p
r
o
g
r
a
m
m
i
n
g
languages,
l
a
n
g
u
a
g
e
s
,
methods,
m
e
t
h
o
d
s
,
rules
r
u
l
e
s
and
a
n
d
tools
t
o
o
l
s
to
t
o
be
b
e
used
u
s
e
d
to
t
o
code
c
o
d
e
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
These
T
h
e
s
e
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Programming
P
r
o
g
r
a
m
m
i
n
g
language(s)
l
a
n
g
u
a
g
e
(
s
)
to
t
o
be
b
e
used
u
s
e
d
and/or
a
n
d
/
o
r
defined
d
e
f
i
n
e
d
subset(s).
s
u
b
s
e
t
(
s
)
.
For
F
o
r
a
a
programming
p
r
o
g
r
a
m
m
i
n
g
language,
l
a
n
g
u
a
g
e
,
reference
r
e
f
e
r
e
n
c
e
the
t
h
e
data
d
a
t
a
that
t
h
a
t
unambiguously
u
n
a
m
b
i
g
u
o
u
s
l
y
defines
d
e
f
i
n
e
s
the
t
h
e
syntax,
s
y
n
t
a
x
,
the
t
h
e
control
c
o
n
t
r
o
l
behavior,
b
e
h
a
v
i
o
r
,
the
t
h
e
data
d
a
t
a
behavior
b
e
h
a
v
i
o
r
and
a
n
d
side-effects
s
i
d
e
-
e
f
f
e
c
t
s
of
o
f
the
t
h
e
language.
l
a
n
g
u
a
g
e
.
This
T
h
i
s
may
m
a
y
require
r
e
q
u
i
r
e
limiting
l
i
m
i
t
i
n
g
the
t
h
e
use
u
s
e
of
o
f
some
s
o
m
e
features
f
e
a
t
u
r
e
s
of
o
f
a
a
language.
l
a
n
g
u
a
g
e
.
-
Source
S
o
u
r
c
e
Code
C
o
d
e
presentation
p
r
e
s
e
n
t
a
t
i
o
n
standards,
s
t
a
n
d
a
r
d
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
line
l
i
n
e
length
l
e
n
g
t
h
restriction,
r
e
s
t
r
i
c
t
i
o
n
,
indentation,
i
n
d
e
n
t
a
t
i
o
n
,
and
a
n
d
blank
b
l
a
n
k
line
l
i
n
e
usage
u
s
a
g
e
and
a
n
d
Source
S
o
u
r
c
e
Code
C
o
d
e
documentation
d
o
c
u
m
e
n
t
a
t
i
o
n
standards,
s
t
a
n
d
a
r
d
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
name
n
a
m
e
of
o
f
author,
a
u
t
h
o
r
,
revision
r
e
v
i
s
i
o
n
history,
h
i
s
t
o
r
y
,
inputs
i
n
p
u
t
s
and
a
n
d
outputs,
o
u
t
p
u
t
s
,
and
a
n
d
affected
a
f
f
e
c
t
e
d
global
g
l
o
b
a
l
data.
d
a
t
a
.
-
Naming
N
a
m
i
n
g
conventions
c
o
n
v
e
n
t
i
o
n
s
for
f
o
r
components,
c
o
m
p
o
n
e
n
t
s
,
subprograms,
s
u
b
p
r
o
g
r
a
m
s
,
variables,
v
a
r
i
a
b
l
e
s
,
and
a
n
d
constants.
c
o
n
s
t
a
n
t
s
.
-
Conditions
C
o
n
d
i
t
i
o
n
s
and
a
n
d
constraints
c
o
n
s
t
r
a
i
n
t
s
imposed
i
m
p
o
s
e
d
on
o
n
permitted
p
e
r
m
i
t
t
e
d
coding
c
o
d
i
n
g
conventions,
c
o
n
v
e
n
t
i
o
n
s
,
such
s
u
c
h
as
a
s
the
t
h
e
degree
d
e
g
r
e
e
of
o
f
coupling
c
o
u
p
l
i
n
g
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
and
a
n
d
the
t
h
e
complexity
c
o
m
p
l
e
x
i
t
y
of
o
f
logical
l
o
g
i
c
a
l
or
o
r
numerical
n
u
m
e
r
i
c
a
l
expressions
e
x
p
r
e
s
s
i
o
n
s
and
a
n
d
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
their
t
h
e
i
r
use.
u
s
e
.
-
Constraints
C
o
n
s
t
r
a
i
n
t
s
on
o
n
the
t
h
e
use
u
s
e
of
o
f
the
t
h
e
coding
c
o
d
i
n
g
tools.
t
o
o
l
s
.
-
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data
D
a
t
a
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data
D
a
t
a
is
i
s
a
a
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
including
i
n
c
l
u
d
i
n
g
the
t
h
e
derived
d
e
r
i
v
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
This
T
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Description
D
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
allocation
a
l
l
o
c
a
t
i
o
n
of
o
f
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
software,
s
o
f
t
w
a
r
e
,
with
w
i
t
h
attention
a
t
t
e
n
t
i
o
n
to
t
o
safety
s
a
f
e
t
y
related
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
potential
p
o
t
e
n
t
i
a
l
failure
f
a
i
l
u
r
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Functional
F
u
n
c
t
i
o
n
a
l
and
a
n
d
operational
o
p
e
r
a
t
i
o
n
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
under
u
n
d
e
r
each
e
a
c
h
mode
m
o
d
e
of
o
f
operation.
o
p
e
r
a
t
i
o
n
.
-
Performance
P
e
r
f
o
r
m
a
n
c
e
criteria,
c
r
i
t
e
r
i
a
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
precision
p
r
e
c
i
s
i
o
n
and
a
n
d
accuracy.
a
c
c
u
r
a
c
y
.
-
Timing
T
i
m
i
n
g
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
constraints.
c
o
n
s
t
r
a
i
n
t
s
.
-
Memory
M
e
m
o
r
y
size
s
i
z
e
constraints.
c
o
n
s
t
r
a
i
n
t
s
.
-
Hardware
H
a
r
d
w
a
r
e
and
a
n
d
software
s
o
f
t
w
a
r
e
interfaces,
i
n
t
e
r
f
a
c
e
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
protocols,
p
r
o
t
o
c
o
l
s
,
formats,
f
o
r
m
a
t
s
,
frequency
f
r
e
q
u
e
n
c
y
of
o
f
inputs
i
n
p
u
t
s
and
a
n
d
frequency
f
r
e
q
u
e
n
c
y
of
o
f
outputs.
o
u
t
p
u
t
s
.
-
Failure
F
a
i
l
u
r
e
detection
d
e
t
e
c
t
i
o
n
and
a
n
d
safety
s
a
f
e
t
y
monitoring
m
o
n
i
t
o
r
i
n
g
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software,
s
o
f
t
w
a
r
e
,
how
h
o
w
the
t
h
e
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
interact
i
n
t
e
r
a
c
t
with
w
i
t
h
each
e
a
c
h
other,
o
t
h
e
r
,
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
of
o
f
each
e
a
c
h
partition.
p
a
r
t
i
t
i
o
n
.
-
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
The
T
h
e
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
is
i
s
a
a
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
and
a
n
d
the
t
h
e
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
will
w
i
l
l
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
This
T
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
A
A
detailed
d
e
t
a
i
l
e
d
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
how
h
o
w
the
t
h
e
software
s
o
f
t
w
a
r
e
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
specified
s
p
e
c
i
f
i
e
d
software
s
o
f
t
w
a
r
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
including
i
n
c
l
u
d
i
n
g
algorithms,
a
l
g
o
r
i
t
h
m
s
,
data
d
a
t
a
structures,
s
t
r
u
c
t
u
r
e
s
,
and
a
n
d
how
h
o
w
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
allocated
a
l
l
o
c
a
t
e
d
to
t
o
processors
p
r
o
c
e
s
s
o
r
s
and
a
n
d
tasks.
t
a
s
k
s
.
-
The
T
h
e
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
defining
d
e
f
i
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
structure
s
t
r
u
c
t
u
r
e
to
t
o
implement
i
m
p
l
e
m
e
n
t
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
The
T
h
e
input/output
i
n
p
u
t
/
o
u
t
p
u
t
description,
d
e
s
c
r
i
p
t
i
o
n
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
a
a
data
d
a
t
a
dictionary,
d
i
c
t
i
o
n
a
r
y
,
both
b
o
t
h
internally
i
n
t
e
r
n
a
l
l
y
and
a
n
d
externally
e
x
t
e
r
n
a
l
l
y
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
The
T
h
e
data
d
a
t
a
flow
f
l
o
w
and
a
n
d
control
c
o
n
t
r
o
l
flow
f
l
o
w
of
o
f
the
t
h
e
design.
d
e
s
i
g
n
.
-
Resource
R
e
s
o
u
r
c
e
limitations,
l
i
m
i
t
a
t
i
o
n
s
,
the
t
h
e
strategy
s
t
r
a
t
e
g
y
for
f
o
r
managing
m
a
n
a
g
i
n
g
each
e
a
c
h
resource
r
e
s
o
u
r
c
e
and
a
n
d
its
i
t
s
limitations,
l
i
m
i
t
a
t
i
o
n
s
,
the
t
h
e
margins,
m
a
r
g
i
n
s
,
and
a
n
d
the
t
h
e
method
m
e
t
h
o
d
for
f
o
r
measuring
m
e
a
s
u
r
i
n
g
those
t
h
o
s
e
margins,
m
a
r
g
i
n
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
timing
t
i
m
i
n
g
and
a
n
d
memory.
m
e
m
o
r
y
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
53
5
3
-
Scheduling
S
c
h
e
d
u
l
i
n
g
procedures
p
r
o
c
e
d
u
r
e
s
and
a
n
d
inter-processor/inter-task
i
n
t
e
r
-
p
r
o
c
e
s
s
o
r
/
i
n
t
e
r
-
t
a
s
k
communication
c
o
m
m
u
n
i
c
a
t
i
o
n
mechanisms,
m
e
c
h
a
n
i
s
m
s
,
including
i
n
c
l
u
d
i
n
g
time
t
i
m
e
-rigid
-
r
i
g
i
d
sequencing,
s
e
q
u
e
n
c
i
n
g
,
preemptive
p
r
e
e
m
p
t
i
v
e
scheduling,
s
c
h
e
d
u
l
i
n
g
,
Ada
A
d
a
rendezvous,
r
e
n
d
e
z
v
o
u
s
,
and
a
n
d
interrupts.
i
n
t
e
r
r
u
p
t
s
.
-
Source
S
o
u
r
c
e
Code
C
o
d
e
-
Design
D
e
s
i
g
n
methods
m
e
t
h
o
d
s
and
a
n
d
details
d
e
t
a
i
l
s
for
f
o
r
their
t
h
e
i
r
implementation,
i
m
p
l
e
m
e
n
t
a
t
i
o
n
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
software
s
o
f
t
w
a
r
e
data
d
a
t
a
loading,
l
o
a
d
i
n
g
,
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
or
o
r
multiple
m
u
l
t
i
p
l
e
-version
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software.
s
o
f
t
w
a
r
e
.
-
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
methods
m
e
t
h
o
d
s
and
a
n
d
means
m
e
a
n
s
of
o
f
preventing
p
r
e
v
e
n
t
i
n
g
partition
p
a
r
t
i
t
i
o
n
breaches.
b
r
e
a
c
h
e
s
.
-
Descriptions
D
e
s
c
r
i
p
t
i
o
n
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
components,
c
o
m
p
o
n
e
n
t
s
,
whether
w
h
e
t
h
e
r
they
t
h
e
y
are
a
r
e
new
n
e
w
or
o
r
previously
p
r
e
v
i
o
u
s
l
y
developed,
d
e
v
e
l
o
p
e
d
,
and,
a
n
d
,
if
i
f
previously
p
r
e
v
i
o
u
s
l
y
developed,
d
e
v
e
l
o
p
e
d
,
reference
r
e
f
e
r
e
n
c
e
to
t
o
the
t
h
e
baseline
b
a
s
e
l
i
n
e
from
f
r
o
m
which
w
h
i
c
h
they
t
h
e
y
were
w
e
r
e
taken.
t
a
k
e
n
.
-
Derived
D
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
resulting
r
e
s
u
l
t
i
n
g
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process.
p
r
o
c
e
s
s
.
-
If
I
f
the
t
h
e
system
s
y
s
t
e
m
contains
c
o
n
t
a
i
n
s
deactivated
d
e
a
c
t
i
v
a
t
e
d
code,
c
o
d
e
,
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
means
m
e
a
n
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
code
c
o
d
e
cannot
c
a
n
n
o
t
be
b
e
enabled
e
n
a
b
l
e
d
in
i
n
the
t
h
e
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
-
Rationale
R
a
t
i
o
n
a
l
e
for
f
o
r
those
t
h
o
s
e
design
d
e
s
i
g
n
decisions
d
e
c
i
s
i
o
n
s
that
t
h
a
t
are
a
r
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
This
T
h
i
s
data
d
a
t
a
consists
c
o
n
s
i
s
t
s
of
o
f
code
c
o
d
e
written
w
r
i
t
t
e
n
in
i
n
source
s
o
u
r
c
e
language(s)
l
a
n
g
u
a
g
e
(
s
)
and
a
n
d
the
t
h
e
compiler
c
o
m
p
i
l
e
r
instructions
i
n
s
t
r
u
c
t
i
o
n
s
for
f
o
r
generating
g
e
n
e
r
a
t
i
n
g
the
t
h
e
object
o
b
j
e
c
t
code
c
o
d
e
from
f
r
o
m
the
t
h
e
Source
S
o
u
r
c
e
Code,
C
o
d
e
,
and
a
n
d
linking
l
i
n
k
i
n
g
and
a
n
d
loading
l
o
a
d
i
n
g
data.
d
a
t
a
.
This
T
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
the
t
h
e
software
s
o
f
t
w
a
r
e
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
name
n
a
m
e
and
a
n
d
date
d
a
t
e
of
o
f
revision
r
e
v
i
s
i
o
n
and/or
a
n
d
/
o
r
version,
v
e
r
s
i
o
n
,
as
a
s
applicable.
a
p
p
l
i
c
a
b
l
e
.
-
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
The
T
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
consists
c
o
n
s
i
s
t
s
of
o
f
a
a
form
f
o
r
m
of
o
f
Source
S
o
u
r
c
e
Code
C
o
d
e
that
t
h
a
t
is
i
s
directly
d
i
r
e
c
t
l
y
usable
u
s
a
b
l
e
by
b
y
the
t
h
e
central
c
e
n
t
r
a
l
processing
p
r
o
c
e
s
s
i
n
g
unit
u
n
i
t
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
and
a
n
d
is,
i
s
,
therefore,
t
h
e
r
e
f
o
r
e
,
the
t
h
e
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
e
hardware
h
a
r
d
w
a
r
e
or
o
r
system.
s
y
s
t
e
m
.
-
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Cases
C
a
s
e
s
and
a
n
d
Procedures
P
r
o
c
e
d
u
r
e
s
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Cases
C
a
s
e
s
and
a
n
d
Procedures
P
r
o
c
e
d
u
r
e
s
detail
d
e
t
a
i
l
how
h
o
w
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
implemented.
i
m
p
l
e
m
e
n
t
e
d
.
This
T
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
descriptions
d
e
s
c
r
i
p
t
i
o
n
s
of
o
f
the:
t
h
e
:
-
Review
R
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
procedures:
p
r
o
c
e
d
u
r
e
s
:
Details,
D
e
t
a
i
l
s
,
supplementary
s
u
p
p
l
e
m
e
n
t
a
r
y
to
t
o
the
t
h
e
description
d
e
s
c
r
i
p
t
i
o
n
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan,
P
l
a
n
,
which
w
h
i
c
h
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
scope
s
c
o
p
e
and
a
n
d
depth
d
e
p
t
h
of
o
f
the
t
h
e
review
r
e
v
i
e
w
or
o
r
analysis
a
n
a
l
y
s
i
s
methods
m
e
t
h
o
d
s
to
t
o
be
b
e
used.
u
s
e
d
.
-
Test
T
e
s
t
cases:
c
a
s
e
s
:
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
each
e
a
c
h
test
t
e
s
t
case,
c
a
s
e
,
set
s
e
t
of
o
f
inputs,
i
n
p
u
t
s
,
conditions,
c
o
n
d
i
t
i
o
n
s
,
expected
e
x
p
e
c
t
e
d
results
r
e
s
u
l
t
s
to
t
o
achieve
a
c
h
i
e
v
e
the
t
h
e
required
r
e
q
u
i
r
e
d
coverage
c
o
v
e
r
a
g
e
criteria,
c
r
i
t
e
r
i
a
,
and
a
n
d
the
t
h
e
pass/fail
p
a
s
s
/
f
a
i
l
criteria.
c
r
i
t
e
r
i
a
.
-
Test
T
e
s
t
proceed:
p
r
o
c
e
e
d
:
The
T
h
e
step-by-step
s
t
e
p
-
b
y
-
s
t
e
p
instructions
i
n
s
t
r
u
c
t
i
o
n
s
for
f
o
r
how
h
o
w
each
e
a
c
h
test
t
e
s
t
case
c
a
s
e
is
i
s
to
t
o
be
b
e
set
s
e
t
up
u
p
and
a
n
d
executed,
e
x
e
c
u
t
e
d
,
how
h
o
w
the
t
h
e
test
t
e
s
t
results
r
e
s
u
l
t
s
are
a
r
e
evaluated,
e
v
a
l
u
a
t
e
d
,
and
a
n
d
the
t
h
e
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
to
t
o
be
b
e
used.
u
s
e
d
.
-
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results
R
e
s
u
l
t
s
The
T
h
e
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results
R
e
s
u
l
t
s
are
a
r
e
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities.
a
c
t
i
v
i
t
i
e
s
.
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results
R
e
s
u
l
t
s
should:
s
h
o
u
l
d
:
-
For
F
o
r
each
e
a
c
h
review,
r
e
v
i
e
w
,
analysis
a
n
a
l
y
s
i
s
and
a
n
d
test,
t
e
s
t
,
indicate
i
n
d
i
c
a
t
e
each
e
a
c
h
procedure
p
r
o
c
e
d
u
r
e
that
t
h
a
t
passed
p
a
s
s
e
d
or
o
r
failed
f
a
i
l
e
d
during
d
u
r
i
n
g
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
and
a
n
d
the
t
h
e
final
f
i
n
a
l
pass/fail
p
a
s
s
/
f
a
i
l
results.
r
e
s
u
l
t
s
.
-
Identify
I
d
e
n
t
i
f
y
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
or
o
r
software
s
o
f
t
w
a
r
e
version
v
e
r
s
i
o
n
reviewed,
r
e
v
i
e
w
e
d
,
analyzed
a
n
a
l
y
z
e
d
or
o
r
tested.
t
e
s
t
e
d
.
-
Include
I
n
c
l
u
d
e
the
t
h
e
results
r
e
s
u
l
t
s
of
o
f
tests,
t
e
s
t
s
,
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses,
a
n
a
l
y
s
e
s
,
including
i
n
c
l
u
d
i
n
g
coverage
c
o
v
e
r
a
g
e
analyses
a
n
a
l
y
s
e
s
and
a
n
d
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analyses.
a
n
a
l
y
s
e
s
.
-
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
The
T
h
e
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(SECI)
(
S
E
C
I
)
identifies
i
d
e
n
t
i
f
i
e
s
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment.
e
n
v
i
r
o
n
m
e
n
t
.
This
T
h
i
s
index
i
n
d
e
x
is
i
s
written
w
r
i
t
t
e
n
to
t
o
aid
a
i
d
reproduction
r
e
p
r
o
d
u
c
t
i
o
n
of
o
f
the
t
h
e
hardware
h
a
r
d
w
a
r
e
and
a
n
d
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
54
5
4
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment,
e
n
v
i
r
o
n
m
e
n
t
,
for
f
o
r
software
s
o
f
t
w
a
r
e
regeneration,
r
e
g
e
n
e
r
a
t
i
o
n
,
reverification,
r
e
v
e
r
i
f
i
c
a
t
i
o
n
,
or
o
r
software
s
o
f
t
w
a
r
e
modification,
m
o
d
i
f
i
c
a
t
i
o
n
,
and
a
n
d
should:
s
h
o
u
l
d
:
-
Identify
I
d
e
n
t
i
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
hardware
h
a
r
d
w
a
r
e
and
a
n
d
its
i
t
s
operating
o
p
e
r
a
t
i
n
g
system
s
y
s
t
e
m
software.
s
o
f
t
w
a
r
e
.
-
Identify
I
d
e
n
t
i
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
such
s
u
c
h
as
a
s
compilers,
c
o
m
p
i
l
e
r
s
,
linkage
l
i
n
k
a
g
e
editors
e
d
i
t
o
r
s
and
a
n
d
loaders,
l
o
a
d
e
r
s
,
and
a
n
d
data
d
a
t
a
integrity
i
n
t
e
g
r
i
t
y
tools
t
o
o
l
s
(such
(
s
u
c
h
as
a
s
tools
t
o
o
l
s
that
t
h
a
t
calculate
c
a
l
c
u
l
a
t
e
and
a
n
d
embed
e
m
b
e
d
checksums
c
h
e
c
k
s
u
m
s
or
o
r
cyclical
c
y
c
l
i
c
a
l
redundancy
r
e
d
u
n
d
a
n
c
y
checks).
c
h
e
c
k
s
)
.
-
Identify
I
d
e
n
t
i
f
y
the
t
h
e
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
used
u
s
e
d
to
t
o
verify
v
e
r
i
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools.
t
o
o
l
s
.
-
Identify
I
d
e
n
t
i
f
y
qualified
q
u
a
l
i
f
i
e
d
tools
t
o
o
l
s
and
a
n
d
their
t
h
e
i
r
associated
a
s
s
o
c
i
a
t
e
d
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data.
d
a
t
a
.
Note:
N
o
t
e
:
This
T
h
i
s
data
d
a
t
a
may
m
a
y
be
b
e
included
i
n
c
l
u
d
e
d
in
i
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index.
I
n
d
e
x
.
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
The
T
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(SCI)
(
S
C
I
)
identifies
i
d
e
n
t
i
f
i
e
s
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
Note:
N
o
t
e
:
The
T
h
e
SCI
S
C
I
can
c
a
n
contain
c
o
n
t
a
i
n
one
o
n
e
data
d
a
t
a
item
i
t
e
m
or
o
r
a
a
set
s
e
t
(hierarchy)
(
h
i
e
r
a
r
c
h
y
)
of
o
f
data
d
a
t
a
items.
i
t
e
m
s
.
The
T
h
e
SCI
S
C
I
can
c
a
n
contain
c
o
n
t
a
i
n
the
t
h
e
items
i
t
e
m
s
listed
l
i
s
t
e
d
below
b
e
l
o
w
or
o
r
it
i
t
may
m
a
y
reference
r
e
f
e
r
e
n
c
e
another
a
n
o
t
h
e
r
SCI
S
C
I
or
o
r
other
o
t
h
e
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identified
i
d
e
n
t
i
f
i
e
d
data
d
a
t
a
that
t
h
a
t
specifies
s
p
e
c
i
f
i
e
s
the
t
h
e
individual
i
n
d
i
v
i
d
u
a
l
items
i
t
e
m
s
and
a
n
d
their
t
h
e
i
r
versions.
v
e
r
s
i
o
n
s
.
The
T
h
e
SCI
S
C
I
should
s
h
o
u
l
d
identify:
i
d
e
n
t
i
f
y
:
-
The
T
h
e
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
-
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
-
Each
E
a
c
h
Source
S
o
u
r
c
e
Code
C
o
d
e
component.
c
o
m
p
o
n
e
n
t
.
-
Previously
P
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
if
i
f
used.
u
s
e
d
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
-
Archive
A
r
c
h
i
v
e
and
a
n
d
release
r
e
l
e
a
s
e
media.
m
e
d
i
a
.
-
Instructions
I
n
s
t
r
u
c
t
i
o
n
s
for
f
o
r
building
b
u
i
l
d
i
n
g
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code,
C
o
d
e
,
including,
i
n
c
l
u
d
i
n
g
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
instructions
i
n
s
t
r
u
c
t
i
o
n
s
and
a
n
d
data
d
a
t
a
for
f
o
r
compiling
c
o
m
p
i
l
i
n
g
and
a
n
d
linking;
l
i
n
k
i
n
g
;
and
a
n
d
the
t
h
e
procedures
p
r
o
c
e
d
u
r
e
s
used
u
s
e
d
to
t
o
recover
r
e
c
o
v
e
r
the
t
h
e
software
s
o
f
t
w
a
r
e
for
f
o
r
regeneration,
r
e
g
e
n
e
r
a
t
i
o
n
,
testing
t
e
s
t
i
n
g
or
o
r
modification.
m
o
d
i
f
i
c
a
t
i
o
n
.
-
Reference
R
e
f
e
r
e
n
c
e
to
t
o
the
t
h
e
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(subsection
(
s
u
b
s
e
c
t
i
o
n
II.
I
I
.
15),
1
5
)
,
if
i
f
is
i
s
packaged
p
a
c
k
a
g
e
d
separately.
s
e
p
a
r
a
t
e
l
y
.
-
Data
D
a
t
a
integrity
i
n
t
e
g
r
i
t
y
checks
c
h
e
c
k
s
for
f
o
r
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code,
C
o
d
e
,
if
i
f
used.
u
s
e
d
.
Note:
N
o
t
e
:
The
T
h
e
SCI
S
C
I
may
m
a
y
be
b
e
produced
p
r
o
d
u
c
e
d
for
f
o
r
one
o
n
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
version
v
e
r
s
i
o
n
or
o
r
it
i
t
may
m
a
y
be
b
e
extended
e
x
t
e
n
d
e
d
to
t
o
contain
c
o
n
t
a
i
n
data
d
a
t
a
for
f
o
r
several
s
e
v
e
r
a
l
alternative
a
l
t
e
r
n
a
t
i
v
e
or
o
r
successive
s
u
c
c
e
s
s
i
v
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
versions.
v
e
r
s
i
o
n
s
.
-
Problem
P
r
o
b
l
e
m
Reports
R
e
p
o
r
t
s
Problem
P
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
are
a
r
e
a
a
means
m
e
a
n
s
to
t
o
identify
i
d
e
n
t
i
f
y
and
a
n
d
record
r
e
c
o
r
d
the
t
h
e
resolution
r
e
s
o
l
u
t
i
o
n
to
t
o
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
anomalous
a
n
o
m
a
l
o
u
s
behavior,
b
e
h
a
v
i
o
r
,
process
p
r
o
c
e
s
s
non-compliance
n
o
n
-
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
and
a
n
d
standards,
s
t
a
n
d
a
r
d
s
,
and
a
n
d
deficiencies
d
e
f
i
c
i
e
n
c
i
e
s
in
i
n
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
Problem
P
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Identification
I
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
and/or
a
n
d
/
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
in
i
n
which
w
h
i
c
h
the
t
h
e
problem
p
r
o
b
l
e
m
was
w
a
s
observed.
o
b
s
e
r
v
e
d
.
-
Identification
I
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item(s)
i
t
e
m
(
s
)
to
t
o
be
b
e
modified
m
o
d
i
f
i
e
d
or
o
r
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
process
p
r
o
c
e
s
s
to
t
o
be
b
e
changed.
c
h
a
n
g
e
d
.
-
A
A
problem
p
r
o
b
l
e
m
description
d
e
s
c
r
i
p
t
i
o
n
that
t
h
a
t
enables
e
n
a
b
l
e
s
the
t
h
e
problem
p
r
o
b
l
e
m
to
t
o
be
b
e
understood
u
n
d
e
r
s
t
o
o
d
and
a
n
d
resolved.
r
e
s
o
l
v
e
d
.
d
d
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
taken
t
a
k
e
n
to
t
o
resolve
r
e
s
o
l
v
e
the
t
h
e
reported
r
e
p
o
r
t
e
d
problem.
p
r
o
b
l
e
m
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Records
R
e
c
o
r
d
s
The
T
h
e
results
r
e
s
u
l
t
s
of
o
f
the
t
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
recorded
r
e
c
o
r
d
e
d
in
i
n
SCM
S
C
M
Records.
R
e
c
o
r
d
s
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
lists,
l
i
s
t
s
,
baseline
b
a
s
e
l
i
n
e
or
o
r
software
s
o
f
t
w
a
r
e
library
l
i
b
r
a
r
y
records,
r
e
c
o
r
d
s
,
change
c
h
a
n
g
e
history
h
i
s
t
o
r
y
reports,
r
e
p
o
r
t
s
,
archive
a
r
c
h
i
v
e
records,
r
e
c
o
r
d
s
,
and
a
n
d
release
r
e
l
e
a
s
e
records.
r
e
c
o
r
d
s
.
These
T
h
e
s
e
examples
e
x
a
m
p
l
e
s
do
d
o
not
n
o
t
imply
i
m
p
l
y
records
r
e
c
o
r
d
s
of
o
f
these
t
h
e
s
e
specific
s
p
e
c
i
f
i
c
types
t
y
p
e
s
need
n
e
e
d
to
t
o
be
b
e
produced.
p
r
o
d
u
c
e
d
.
Note:
N
o
t
e
:
Due
D
u
e
to
t
o
the
t
h
e
integral
i
n
t
e
g
r
a
l
nature
n
a
t
u
r
e
of
o
f
the
t
h
e
SCM
S
C
M
process,
p
r
o
c
e
s
s
,
its
i
t
s
outputs
o
u
t
p
u
t
s
will
w
i
l
l
often
o
f
t
e
n
be
b
e
included
i
n
c
l
u
d
e
d
as
a
s
parts
p
a
r
t
s
of
o
f
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
-
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Records
R
e
c
o
r
d
s
The
T
h
e
results
r
e
s
u
l
t
s
of
o
f
the
t
h
e
SQA
S
Q
A
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
recorded
r
e
c
o
r
d
e
d
in
i
n
SQA
S
Q
A
Records.
R
e
c
o
r
d
s
.
These
T
h
e
s
e
may
m
a
y
include
i
n
c
l
u
d
e
SQA
S
Q
A
review
r
e
v
i
e
w
or
o
r
audit
a
u
d
i
t
reports,
r
e
p
o
r
t
s
,
meeting
m
e
e
t
i
n
g
minutes,
m
i
n
u
t
e
s
,
records
r
e
c
o
r
d
s
of
o
f
authorized
a
u
t
h
o
r
i
z
e
d
process
p
r
o
c
e
s
s
deviations,
d
e
v
i
a
t
i
o
n
s
,
or
o
r
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
records.
r
e
c
o
r
d
s
.
11.20
1
1
.
2
0
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
The
T
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
is
i
s
the
t
h
e
primary
p
r
i
m
a
r
y
data
d
a
t
a
item
i
t
e
m
for
f
o
r
showing
s
h
o
w
i
n
g
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
This
T
h
i
s
summary
s
u
m
m
a
r
y
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
System
S
y
s
t
e
m
overview:
o
v
e
r
v
i
e
w
:
This
T
h
i
s
section
s
e
c
t
i
o
n
provides
p
r
o
v
i
d
e
s
an
a
n
overview
o
v
e
r
v
i
e
w
of
o
f
the
t
h
e
system,
s
y
s
t
e
m
,
including
i
n
c
l
u
d
i
n
g
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
its
i
t
s
functions
f
u
n
c
t
i
o
n
s
and
a
n
d
their
t
h
e
i
r
allocation
a
l
l
o
c
a
t
i
o
n
to
t
o
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software,
s
o
f
t
w
a
r
e
,
the
t
h
e
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
the
t
h
e
processor(s)
p
r
o
c
e
s
s
o
r
(
s
)
used,
u
s
e
d
,
the
t
h
e
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
interfaces,
i
n
t
e
r
f
a
c
e
s
,
and
a
n
d
safety
s
a
f
e
t
y
features.
f
e
a
t
u
r
e
s
.
This
T
h
i
s
section
s
e
c
t
i
o
n
also
a
l
s
o
describes
d
e
s
c
r
i
b
e
s
any
a
n
y
differences
d
i
f
f
e
r
e
n
c
e
s
from
f
r
o
m
the
t
h
e
system
s
y
s
t
e
m
overview
o
v
e
r
v
i
e
w
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
overview:
o
v
e
r
v
i
e
w
:
This
T
h
i
s
section
s
e
c
t
i
o
n
briefly
b
r
i
e
f
l
y
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
functions
f
u
n
c
t
i
o
n
s
with
w
i
t
h
emphasis
e
m
p
h
a
s
i
s
on
o
n
the
t
h
e
safety
s
a
f
e
t
y
and
a
n
d
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
concepts
c
o
n
c
e
p
t
s
used,
u
s
e
d
,
and
a
n
d
explains
e
x
p
l
a
i
n
s
differences
d
i
f
f
e
r
e
n
c
e
s
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
overview
o
v
e
r
v
i
e
w
proposed
p
r
o
p
o
s
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
considerations:
c
o
n
s
i
d
e
r
a
t
i
o
n
s
:
This
T
h
i
s
section
s
e
c
t
i
o
n
restates
r
e
s
t
a
t
e
s
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
described
d
e
s
c
r
i
b
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
and
a
n
d
describes
d
e
s
c
r
i
b
e
s
any
a
n
y
differences.
d
i
f
f
e
r
e
n
c
e
s
.
-
Software
S
o
f
t
w
a
r
e
characteristics:
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
:
This
T
h
i
s
section
s
e
c
t
i
o
n
states
s
t
a
t
e
s
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
size,
s
i
z
e
,
timing
t
i
m
i
n
g
and
a
n
d
memory
m
e
m
o
r
y
margins,
m
a
r
g
i
n
s
,
resource
r
e
s
o
u
r
c
e
limitations,
l
i
m
i
t
a
t
i
o
n
s
,
and
a
n
d
the
t
h
e
means
m
e
a
n
s
of
o
f
measuring
m
e
a
s
u
r
i
n
g
each
e
a
c
h
characteristic.
c
h
a
r
a
c
t
e
r
i
s
t
i
c
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
:
:
This
T
h
i
s
section
s
e
c
t
i
o
n
summarizes
s
u
m
m
a
r
i
z
e
s
the
t
h
e
actual
a
c
t
u
a
l
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle(s)
c
y
c
l
e
(
s
)
and
a
n
d
explains
e
x
p
l
a
i
n
s
differences
d
i
f
f
e
r
e
n
c
e
s
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
proposed
p
r
o
p
o
s
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data:
d
a
t
a
:
This
T
h
i
s
section
s
e
c
t
i
o
n
references
r
e
f
e
r
e
n
c
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes.
p
r
o
c
e
s
s
e
s
.
It
I
t
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
of
o
f
the
t
h
e
data
d
a
t
a
to
t
o
each
e
a
c
h
other
o
t
h
e
r
and
a
n
d
to
t
o
other
o
t
h
e
r
data
d
a
t
a
defining
d
e
f
i
n
i
n
g
the
t
h
e
system,
s
y
s
t
e
m
,
and
a
n
d
the
t
h
e
means
m
e
a
n
s
by
b
y
which
w
h
i
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
will
w
i
l
l
be
b
e
made
m
a
d
e
available
a
v
a
i
l
a
b
l
e
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
This
T
h
i
s
section
s
e
c
t
i
o
n
also
a
l
s
o
describes
d
e
s
c
r
i
b
e
s
any
a
n
y
differences
d
i
f
f
e
r
e
n
c
e
s
from
f
r
o
m
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Additional
A
d
d
i
t
i
o
n
a
l
considerations:
c
o
n
s
i
d
e
r
a
t
i
o
n
s
:
This
T
h
i
s
section
s
e
c
t
i
o
n
summarizes
s
u
m
m
a
r
i
z
e
s
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
issues
i
s
s
u
e
s
that
t
h
a
t
may
m
a
y
warrant
w
a
r
r
a
n
t
the
t
h
e
attention
a
t
t
e
n
t
i
o
n
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
and
a
n
d
references
r
e
f
e
r
e
n
c
e
s
data
d
a
t
a
items
i
t
e
m
s
applicable
a
p
p
l
i
c
a
b
l
e
to
t
o
these
t
h
e
s
e
issues,
i
s
s
u
e
s
,
such
s
u
c
h
as
a
s
issue
i
s
s
u
e
papers
p
a
p
e
r
s
or
o
r
special
s
p
e
c
i
a
l
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Software
S
o
f
t
w
a
r
e
identification:
i
d
e
n
t
i
f
i
c
a
t
i
o
n
:
This
T
h
i
s
section
s
e
c
t
i
o
n
identifies
i
d
e
n
t
i
f
i
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
by
b
y
part
p
a
r
t
number
n
u
m
b
e
r
and
a
n
d
version.
v
e
r
s
i
o
n
.
-
Change
C
h
a
n
g
e
history:
h
i
s
t
o
r
y
:
If
I
f
applicable,
a
p
p
l
i
c
a
b
l
e
,
this
t
h
i
s
section
s
e
c
t
i
o
n
includes
i
n
c
l
u
d
e
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
software
s
o
f
t
w
a
r
e
changes
c
h
a
n
g
e
s
with
w
i
t
h
attention
a
t
t
e
n
t
i
o
n
to
t
o
changes
c
h
a
n
g
e
s
made
m
a
d
e
due
d
u
e
to
t
o
failures
f
a
i
l
u
r
e
s
affecting
a
f
f
e
c
t
i
n
g
safety,
s
a
f
e
t
y
,
and
a
n
d
identifies
i
d
e
n
t
i
f
i
e
s
changes
c
h
a
n
g
e
s
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
since
s
i
n
c
e
the
t
h
e
previous
p
r
e
v
i
o
u
s
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
status:
s
t
a
t
u
s
:
This
T
h
i
s
section
s
e
c
t
i
o
n
contains
c
o
n
t
a
i
n
s
a
a
summary
s
u
m
m
a
r
y
of
o
f
problem
p
r
o
b
l
e
m
reports
r
e
p
o
r
t
s
unresolved
u
n
r
e
s
o
l
v
e
d
at
a
t
the
t
h
e
time
t
i
m
e
of
o
f
certification,
c
e
r
t
i
f
i
c
a
t
i
o
n
,
including
i
n
c
l
u
d
i
n
g
a
a
statement
s
t
a
t
e
m
e
n
t
of
o
f
functional
f
u
n
c
t
i
o
n
a
l
limitations.
l
i
m
i
t
a
t
i
o
n
s
.
-
Compliance
C
o
m
p
l
i
a
n
c
e
statement:
s
t
a
t
e
m
e
n
t
:
This
T
h
i
s
section
s
e
c
t
i
o
n
includes
i
n
c
l
u
d
e
s
a
a
statement
s
t
a
t
e
m
e
n
t
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
this
t
h
i
s
document
d
o
c
u
m
e
n
t
and
a
n
d
a
a
summary
s
u
m
m
a
r
y
July
J
u
l
y
2,
2
,
1996
1
9
9
6
of
o
f
the
t
h
e
methods
m
e
t
h
o
d
s
used
u
s
e
d
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
compliant
c
o
m
p
l
i
a
n
t
with
w
i
t
h
criteria
c
r
i
t
e
r
i
a
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
55
5
5
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
56
5
6
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
This
T
h
i
s
section
s
e
c
t
i
o
n
also
a
l
s
o
addresses
a
d
d
r
e
s
s
e
s
additional
a
d
d
i
t
i
o
n
a
l
rulings
r
u
l
i
n
g
s
and
a
n
d
deviations
d
e
v
i
a
t
i
o
n
s
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
plans,
p
l
a
n
s
,
standards
s
t
a
n
d
a
r
d
s
and
a
n
d
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
12.0
1
2
.
0
ADDITIONAL
A
D
D
I
T
I
O
N
A
L
CONSIDERATIONS
C
O
N
S
I
D
E
R
A
T
I
O
N
S
The
T
h
e
previous
p
r
e
v
i
o
u
s
sections
s
e
c
t
i
o
n
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
provide
p
r
o
v
i
d
e
guidance
g
u
i
d
a
n
c
e
for
f
o
r
satisfying
s
a
t
i
s
f
y
i
n
g
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
requirements
r
e
q
u
i
r
e
m
e
n
t
s
in
i
n
which
w
h
i
c
h
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
submits
s
u
b
m
i
t
s
evidence
e
v
i
d
e
n
c
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
This
T
h
i
s
section
s
e
c
t
i
o
n
introduces
i
n
t
r
o
d
u
c
e
s
additional
a
d
d
i
t
i
o
n
a
l
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
concerning
c
o
n
c
e
r
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
in
i
n
relation
r
e
l
a
t
i
o
n
to
t
o
the
t
h
e
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
tools,
t
o
o
l
s
,
and
a
n
d
alternative
a
l
t
e
r
n
a
t
i
v
e
methods
m
e
t
h
o
d
s
for
f
o
r
achieving
a
c
h
i
e
v
i
n
g
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
sections
s
e
c
t
i
o
n
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
12.1
1
2
.
1
Use
U
s
e
of
o
f
Previously
P
r
e
v
i
o
u
s
l
y
Developed
D
e
v
e
l
o
p
e
d
Software
S
o
f
t
w
a
r
e
The
T
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
subsection
s
u
b
s
e
c
t
i
o
n
discuss
d
i
s
c
u
s
s
the
t
h
e
issues
i
s
s
u
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
modifications,
m
o
d
i
f
i
c
a
t
i
o
n
s
,
the
t
h
e
effect
e
f
f
e
c
t
of
o
f
changing
c
h
a
n
g
i
n
g
an
a
n
aircraft
a
i
r
c
r
a
f
t
installation,
i
n
s
t
a
l
l
a
t
i
o
n
,
application
a
p
p
l
i
c
a
t
i
o
n
environment,
e
n
v
i
r
o
n
m
e
n
t
,
or
o
r
development
d
e
v
e
l
o
p
m
e
n
t
environment,
e
n
v
i
r
o
n
m
e
n
t
,
upgrading
u
p
g
r
a
d
i
n
g
a
a
development
d
e
v
e
l
o
p
m
e
n
t
baseline,
b
a
s
e
l
i
n
e
,
and
a
n
d
SCM
S
C
M
and
a
n
d
SQA
S
Q
A
considerations.
c
o
n
s
i
d
e
r
a
t
i
o
n
s
.
The
T
h
e
intention
i
n
t
e
n
t
i
o
n
to
t
o
use
u
s
e
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
is
i
s
stated
s
t
a
t
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
12.1.1
1
2
.
1
.
1
Modifications
M
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
Previously
P
r
e
v
i
o
u
s
l
y
Developed
D
e
v
e
l
o
p
e
d
Software
S
o
f
t
w
a
r
e
This
T
h
i
s
guidance
g
u
i
d
a
n
c
e
discusses
d
i
s
c
u
s
s
e
s
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
where
w
h
e
r
e
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
comply
c
o
m
p
l
y
with
w
i
t
h
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Modification
M
o
d
i
f
i
c
a
t
i
o
n
may
m
a
y
result
r
e
s
u
l
t
from
f
r
o
m
requirement
r
e
q
u
i
r
e
m
e
n
t
changes,
c
h
a
n
g
e
s
,
the
t
h
e
detection
d
e
t
e
c
t
i
o
n
of
o
f
errors,
e
r
r
o
r
s
,
and/or
a
n
d
/
o
r
software
s
o
f
t
w
a
r
e
enhancements.
e
n
h
a
n
c
e
m
e
n
t
s
.
Analysis
A
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
for
f
o
r
proposed
p
r
o
p
o
s
e
d
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
include:
i
n
c
l
u
d
e
:
-
The
T
h
e
revised
r
e
v
i
s
e
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
should
s
h
o
u
l
d
be
b
e
reviewed
r
e
v
i
e
w
e
d
considering
c
o
n
s
i
d
e
r
i
n
g
the
t
h
e
proposed
p
r
o
p
o
s
e
d
modifications.
m
o
d
i
f
i
c
a
t
i
o
n
s
.
-
If
I
f
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
is
i
s
revised,
r
e
v
i
s
e
d
,
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
paragraph
p
a
r
a
g
r
a
p
h
12.1.4
1
2
.
1
.
4
should
s
h
o
u
l
d
be
b
e
considered.
c
o
n
s
i
d
e
r
e
d
.
-
Both
B
o
t
h
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
changes
c
h
a
n
g
e
s
and
a
n
d
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
changes
c
h
a
n
g
e
s
should
s
h
o
u
l
d
be
b
e
analyzed,
a
n
a
l
y
z
e
d
,
including
i
n
c
l
u
d
i
n
g
the
t
h
e
consequences
c
o
n
s
e
q
u
e
n
c
e
s
of
o
f
software
s
o
f
t
w
a
r
e
requirement
r
e
q
u
i
r
e
m
e
n
t
changes
c
h
a
n
g
e
s
upon
u
p
o
n
other
o
t
h
e
r
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
coupling
c
o
u
p
l
i
n
g
between
b
e
t
w
e
e
n
several
s
e
v
e
r
a
l
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
that
t
h
a
t
may
m
a
y
result
r
e
s
u
l
t
in
i
n
reverification
r
e
v
e
r
i
f
i
c
a
t
i
o
n
effort
e
f
f
o
r
t
involving
i
n
v
o
l
v
i
n
g
more
m
o
r
e
than
t
h
a
n
the
t
h
e
modified
m
o
d
i
f
i
e
d
area.
a
r
e
a
.
-
The
T
h
e
area
a
r
e
a
affected
a
f
f
e
c
t
e
d
by
b
y
a
a
change
c
h
a
n
g
e
should
s
h
o
u
l
d
be
b
e
determined.
d
e
t
e
r
m
i
n
e
d
.
This
T
h
i
s
may
m
a
y
be
b
e
done
d
o
n
e
by
b
y
data
d
a
t
a
flow
f
l
o
w
analysis,
a
n
a
l
y
s
i
s
,
control
c
o
n
t
r
o
l
flow
f
l
o
w
analysis,
a
n
a
l
y
s
i
s
,
timing
t
i
m
i
n
g
analysis
a
n
a
l
y
s
i
s
and
a
n
d
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analysis.
a
n
a
l
y
s
i
s
.
-
Areas
A
r
e
a
s
affected
a
f
f
e
c
t
e
d
by
b
y
the
t
h
e
change
c
h
a
n
g
e
should
s
h
o
u
l
d
be
b
e
reverified
r
e
v
e
r
i
f
i
e
d
considering
c
o
n
s
i
d
e
r
i
n
g
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
section
s
e
c
t
i
o
n
6.
6
.
12.1.2
1
2
.
1
.
2
Change
C
h
a
n
g
e
of
o
f
Aircraft
A
i
r
c
r
a
f
t
Installation
I
n
s
t
a
l
l
a
t
i
o
n
Airborne
A
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
or
o
r
equipment
e
q
u
i
p
m
e
n
t
containing
c
o
n
t
a
i
n
i
n
g
software
s
o
f
t
w
a
r
e
which
w
h
i
c
h
has
h
a
s
been
b
e
e
n
previously
p
r
e
v
i
o
u
s
l
y
certified
c
e
r
t
i
f
i
e
d
at
a
t
a
a
certain
c
e
r
t
a
i
n
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
and
a
n
d
under
u
n
d
e
r
a
a
specific
s
p
e
c
i
f
i
c
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
may
m
a
y
be
b
e
used
u
s
e
d
in
i
n
a
a
new
n
e
w
aircraft
a
i
r
c
r
a
f
t
installation.
i
n
s
t
a
l
l
a
t
i
o
n
.
This
T
h
i
s
guidance
g
u
i
d
a
n
c
e
should
s
h
o
u
l
d
be
b
e
used
u
s
e
d
for
f
o
r
new
n
e
w
aircraft
a
i
r
c
r
a
f
t
installations,
i
n
s
t
a
l
l
a
t
i
o
n
s
,
if
i
f
using
u
s
i
n
g
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software:
s
o
f
t
w
a
r
e
:
-
The
T
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
assesses
a
s
s
e
s
s
e
s
the
t
h
e
new
n
e
w
aircraft
a
i
r
c
r
a
f
t
installation
i
n
s
t
a
l
l
a
t
i
o
n
and
a
n
d
determines
d
e
t
e
r
m
i
n
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
and
a
n
d
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis.
b
a
s
i
s
.
No
N
o
additional
a
d
d
i
t
i
o
n
a
l
effort
e
f
f
o
r
t
will
w
i
l
l
be
b
e
required
r
e
q
u
i
r
e
d
if
i
f
these
t
h
e
s
e
are
a
r
e
the
t
h
e
same
s
a
m
e
for
f
o
r
the
t
h
e
new
n
e
w
installation
i
n
s
t
a
l
l
a
t
i
o
n
as
a
s
they
t
h
e
y
were
w
e
r
e
in
i
n
the
t
h
e
previous
p
r
e
v
i
o
u
s
installation.
i
n
s
t
a
l
l
a
t
i
o
n
.
-
If
I
f
functional
f
u
n
c
t
i
o
n
a
l
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
are
a
r
e
required
r
e
q
u
i
r
e
d
for
f
o
r
the
t
h
e
new
n
e
w
installation,
i
n
s
t
a
l
l
a
t
i
o
n
,
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
paragraph
p
a
r
a
g
r
a
p
h
12.1.1,
1
2
.
1
.
1
,
Modifications
M
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
Previously
P
r
e
v
i
o
u
s
l
y
Developed
D
e
v
e
l
o
p
e
d
Software
S
o
f
t
w
a
r
e
,
,
should
s
h
o
u
l
d
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
If
I
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
development
d
e
v
e
l
o
p
m
e
n
t
activity
a
c
t
i
v
i
t
y
did
d
i
d
not
n
o
t
produce
p
r
o
d
u
c
e
outputs
o
u
t
p
u
t
s
required
r
e
q
u
i
r
e
d
to
t
o
substantiate
s
u
b
s
t
a
n
t
i
a
t
e
the
t
h
e
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
new
n
e
w
installation,
i
n
s
t
a
l
l
a
t
i
o
n
,
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
paragraph
p
a
r
a
g
r
a
p
h
12.1.4,
1
2
.
1
.
4
,
Upgrading
U
p
g
r
a
d
i
n
g
a
a
Development
D
e
v
e
l
o
p
m
e
n
t
Baseline,
B
a
s
e
l
i
n
e
,
should
s
h
o
u
l
d
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
12.1.3
1
2
.
1
.
3
Change
C
h
a
n
g
e
of
o
f
Application
A
p
p
l
i
c
a
t
i
o
n
or
o
r
Developme
D
e
v
e
l
o
p
m
e
nt
n
t
Environment
E
n
v
i
r
o
n
m
e
n
t
Use
U
s
e
and
a
n
d
modification
m
o
d
i
f
i
c
a
t
i
o
n
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
may
m
a
y
involve
i
n
v
o
l
v
e
a
a
new
n
e
w
development
d
e
v
e
l
o
p
m
e
n
t
environment,
e
n
v
i
r
o
n
m
e
n
t
,
a
a
new
n
e
w
target
t
a
r
g
e
t
processor
p
r
o
c
e
s
s
o
r
or
o
r
other
o
t
h
e
r
hardware,
h
a
r
d
w
a
r
e
,
or
o
r
integration
i
n
t
e
g
r
a
t
i
o
n
with
w
i
t
h
other
o
t
h
e
r
software
s
o
f
t
w
a
r
e
than
t
h
a
n
that
t
h
a
t
used
u
s
e
d
for
f
o
r
the
t
h
e
original
o
r
i
g
i
n
a
l
application.
a
p
p
l
i
c
a
t
i
o
n
.
57
5
7
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
58
5
8
New
N
e
w
development
d
e
v
e
l
o
p
m
e
n
t
environments
e
n
v
i
r
o
n
m
e
n
t
s
may
m
a
y
increase
i
n
c
r
e
a
s
e
or
o
r
reduce
r
e
d
u
c
e
some
s
o
m
e
activities
a
c
t
i
v
i
t
i
e
s
within
w
i
t
h
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
New
N
e
w
application
a
p
p
l
i
c
a
t
i
o
n
environments
e
n
v
i
r
o
n
m
e
n
t
s
may
m
a
y
require
r
e
q
u
i
r
e
activities
a
c
t
i
v
i
t
i
e
s
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
which
w
h
i
c
h
address
a
d
d
r
e
s
s
modifications.
m
o
d
i
f
i
c
a
t
i
o
n
s
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
change
c
h
a
n
g
e
of
o
f
application
a
p
p
l
i
c
a
t
i
o
n
or
o
r
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
includes:
i
n
c
l
u
d
e
s
:
-
If
I
f
a
a
new
n
e
w
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
uses
u
s
e
s
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
subsection
s
u
b
s
e
c
t
i
o
n
12.2,
1
2
.
2
,
Tool
T
o
o
l
Qualification,
Q
u
a
l
i
f
i
c
a
t
i
o
n
,
may
m
a
y
be
b
e
applicable.
a
p
p
l
i
c
a
b
l
e
.
-
The
T
h
e
rigor
r
i
g
o
r
of
o
f
the
t
h
e
evaluation
e
v
a
l
u
a
t
i
o
n
of
o
f
an
a
n
application
a
p
p
l
i
c
a
t
i
o
n
change
c
h
a
n
g
e
should
s
h
o
u
l
d
consider
c
o
n
s
i
d
e
r
the
t
h
e
complexity
c
o
m
p
l
e
x
i
t
y
and
a
n
d
sophistication
s
o
p
h
i
s
t
i
c
a
t
i
o
n
of
o
f
the
t
h
e
programming
p
r
o
g
r
a
m
m
i
n
g
language.
l
a
n
g
u
a
g
e
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
rigor
r
i
g
o
r
of
o
f
the
t
h
e
evaluation
e
v
a
l
u
a
t
i
o
n
for
f
o
r
Ada
A
d
a
generics
g
e
n
e
r
i
c
s
will
w
i
l
l
be
b
e
greater
g
r
e
a
t
e
r
if
i
f
the
t
h
e
generic
g
e
n
e
r
i
c
parameters
p
a
r
a
m
e
t
e
r
s
are
a
r
e
different
d
i
f
f
e
r
e
n
t
in
i
n
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
For
F
o
r
object
o
b
j
e
c
t
oriented
o
r
i
e
n
t
e
d
languages,
l
a
n
g
u
a
g
e
s
,
the
t
h
e
rigor
r
i
g
o
r
will
w
i
l
l
be
b
e
greater
g
r
e
a
t
e
r
if
i
f
the
t
h
e
objects
o
b
j
e
c
t
s
that
t
h
a
t
are
a
r
e
inherited
i
n
h
e
r
i
t
e
d
are
a
r
e
different
d
i
f
f
e
r
e
n
t
in
i
n
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
If
I
f
a
a
different
d
i
f
f
e
r
e
n
t
compiler
c
o
m
p
i
l
e
r
or
o
r
different
d
i
f
f
e
r
e
n
t
set
s
e
t
of
o
f
compiler
c
o
m
p
i
l
e
r
options
o
p
t
i
o
n
s
are
a
r
e
used,
u
s
e
d
,
resulting
r
e
s
u
l
t
i
n
g
in
i
n
different
d
i
f
f
e
r
e
n
t
object
o
b
j
e
c
t
code,
c
o
d
e
,
the
t
h
e
results
r
e
s
u
l
t
s
from
f
r
o
m
a
a
previous
p
r
e
v
i
o
u
s
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
using
u
s
i
n
g
the
t
h
e
object
o
b
j
e
c
t
code
c
o
d
e
may
m
a
y
not
n
o
t
be
b
e
valid
v
a
l
i
d
and
a
n
d
should
s
h
o
u
l
d
not
n
o
t
be
b
e
used
u
s
e
d
for
f
o
r
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
In
I
n
this
t
h
i
s
case,
c
a
s
e
,
previous
p
r
e
v
i
o
u
s
test
t
e
s
t
results
r
e
s
u
l
t
s
may
m
a
y
no
n
o
longer
l
o
n
g
e
r
be
b
e
valid
v
a
l
i
d
for
f
o
r
the
t
h
e
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
criteria
c
r
i
t
e
r
i
a
of
o
f
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
Similarly,
S
i
m
i
l
a
r
l
y
,
compiler
c
o
m
p
i
l
e
r
assumptions
a
s
s
u
m
p
t
i
o
n
s
about
a
b
o
u
t
optimization
o
p
t
i
m
i
z
a
t
i
o
n
may
m
a
y
not
n
o
t
be
b
e
valid.
v
a
l
i
d
.
-
If
I
f
a
a
different
d
i
f
f
e
r
e
n
t
processor
p
r
o
c
e
s
s
o
r
is
i
s
used
u
s
e
d
then:
t
h
e
n
:
-
The
T
h
e
results
r
e
s
u
l
t
s
from
f
r
o
m
a
a
previous
p
r
e
v
i
o
u
s
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
directed
d
i
r
e
c
t
e
d
at
a
t
the
t
h
e
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
interface
i
n
t
e
r
f
a
c
e
should
s
h
o
u
l
d
not
n
o
t
be
b
e
used
u
s
e
d
for
f
o
r
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
The
T
h
e
previous
p
r
e
v
i
o
u
s
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
tests
t
e
s
t
s
should
s
h
o
u
l
d
be
b
e
executed
e
x
e
c
u
t
e
d
for
f
o
r
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
Reviews
R
e
v
i
e
w
s
of
o
f
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
should
s
h
o
u
l
d
be
b
e
repeated.
r
e
p
e
a
t
e
d
.
-
Additional
A
d
d
i
t
i
o
n
a
l
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
tests
t
e
s
t
s
and
a
n
d
reviews
r
e
v
i
e
w
s
may
m
a
y
be
b
e
necessary.
n
e
c
e
s
s
a
r
y
.
-
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
interfaces
i
n
t
e
r
f
a
c
e
s
should
s
h
o
u
l
d
be
b
e
conducted
c
o
n
d
u
c
t
e
d
where
w
h
e
r
e
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
is
i
s
used
u
s
e
d
with
w
i
t
h
different
d
i
f
f
e
r
e
n
t
interfacing
i
n
t
e
r
f
a
c
i
n
g
software.
s
o
f
t
w
a
r
e
.
12.1.4
1
2
.
1
.
4
Upgrading
U
p
g
r
a
d
i
n
g
A
A
Development
D
e
v
e
l
o
p
m
e
n
t
Baseline
B
a
s
e
l
i
n
e
Guidelines
G
u
i
d
e
l
i
n
e
s
follow
f
o
l
l
o
w
for
f
o
r
software
s
o
f
t
w
a
r
e
whose
w
h
o
s
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
from
f
r
o
m
a
a
previous
p
r
e
v
i
o
u
s
application
a
p
p
l
i
c
a
t
i
o
n
are
a
r
e
determined
d
e
t
e
r
m
i
n
e
d
to
t
o
be
b
e
inadequate
i
n
a
d
e
q
u
a
t
e
or
o
r
do
d
o
not
n
o
t
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
due
d
u
e
to
t
o
the
t
h
e
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
a
a
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
These
T
h
e
s
e
guidelines
g
u
i
d
e
l
i
n
e
s
are
a
r
e
intended
i
n
t
e
n
d
e
d
to
t
o
aid
a
i
d
in
i
n
the
t
h
e
acceptance
a
c
c
e
p
t
a
n
c
e
of:
o
f
:
-
Commercial
C
o
m
m
e
r
c
i
a
l
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
software.
s
o
f
t
w
a
r
e
.
-
Airborne
A
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
other
o
t
h
e
r
guidelines.
g
u
i
d
e
l
i
n
e
s
.
-
Airborne
A
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
developed
d
e
v
e
l
o
p
e
d
prior
p
r
i
o
r
to
t
o
the
t
h
e
existence
e
x
i
s
t
e
n
c
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
Software
S
o
f
t
w
a
r
e
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
to
t
o
this
t
h
i
s
document
d
o
c
u
m
e
n
t
at
a
t
a
a
lower
l
o
w
e
r
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
upgrading
u
p
g
r
a
d
i
n
g
a
a
development
d
e
v
e
l
o
p
m
e
n
t
baseline
b
a
s
e
l
i
n
e
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
should
s
h
o
u
l
d
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
while
w
h
i
l
e
taking
t
a
k
i
n
g
advantage
a
d
v
a
n
t
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
development
d
e
v
e
l
o
p
m
e
n
t
that
t
h
a
t
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
aspects
a
s
p
e
c
t
s
of
o
f
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
based
b
a
s
e
d
on
o
n
the
t
h
e
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
and
a
n
d
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
as
a
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
Comparison
C
o
m
p
a
r
i
s
o
n
to
t
o
failure
f
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
application
a
p
p
l
i
c
a
t
i
o
n
will
w
i
l
l
determine
d
e
t
e
r
m
i
n
e
areas
a
r
e
a
s
which
w
h
i
c
h
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
upgraded.
u
p
g
r
a
d
e
d
.
-
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
from
f
r
o
m
a
a
previous
p
r
e
v
i
o
u
s
development
d
e
v
e
l
o
p
m
e
n
t
should
s
h
o
u
l
d
be
b
e
evaluated
e
v
a
l
u
a
t
e
d
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
are
a
r
e
satisfied
s
a
t
i
s
f
i
e
d
for
f
o
r
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
Reverse
R
e
v
e
r
s
e
engineering
e
n
g
i
n
e
e
r
i
n
g
may
m
a
y
be
b
e
used
u
s
e
d
to
t
o
regenerate
r
e
g
e
n
e
r
a
t
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
that
t
h
a
t
is
i
s
inadequate
i
n
a
d
e
q
u
a
t
e
or
o
r
missing
m
i
s
s
i
n
g
in
i
n
satisfying
s
a
t
i
s
f
y
i
n
g
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
In
I
n
addition
a
d
d
i
t
i
o
n
to
t
o
producing
p
r
o
d
u
c
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
additional
a
d
d
i
t
i
o
n
a
l
activities
a
c
t
i
v
i
t
i
e
s
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives.
o
b
j
e
c
t
i
v
e
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
59
5
9
-
If
I
f
use
u
s
e
of
o
f
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
is
i
s
planned
p
l
a
n
n
e
d
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
in
i
n
upgrading
u
p
g
r
a
d
i
n
g
a
a
development
d
e
v
e
l
o
p
m
e
n
t
baseline,
b
a
s
e
l
i
n
e
,
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
paragraph
p
a
r
a
g
r
a
p
h
12.3.5
1
2
.
3
.
5
should
s
h
o
u
l
d
be
b
e
considered.
c
o
n
s
i
d
e
r
e
d
.
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
specify
s
p
e
c
i
f
y
the
t
h
e
strategy
s
t
r
a
t
e
g
y
for
f
o
r
accomplis
a
c
c
o
m
p
l
i
s
hing
h
i
n
g
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
this
t
h
i
s
document
d
o
c
u
m
e
n
t
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
12.1.5
1
2
.
1
.
5
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
If
I
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
is
i
s
used,
u
s
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process
p
r
o
c
e
s
s
for
f
o
r
the
t
h
e
new
n
e
w
application
a
p
p
l
i
c
a
t
i
o
n
should
s
h
o
u
l
d
include,
i
n
c
l
u
d
e
,
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
section
s
e
c
t
i
o
n
7:
7
:
-
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
of
o
f
the
t
h
e
previous
p
r
e
v
i
o
u
s
application
a
p
p
l
i
c
a
t
i
o
n
to
t
o
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
Change
C
h
a
n
g
e
control
c
o
n
t
r
o
l
that
t
h
a
t
enables
e
n
a
b
l
e
s
problem
p
r
o
b
l
e
m
reporting,
r
e
p
o
r
t
i
n
g
,
problem
p
r
o
b
l
e
m
resolution,
r
e
s
o
l
u
t
i
o
n
,
and
a
n
d
tracking
t
r
a
c
k
i
n
g
of
o
f
changes
c
h
a
n
g
e
s
to
t
o
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
used
u
s
e
d
in
i
n
more
m
o
r
e
than
t
h
a
n
one
o
n
e
application.
a
p
p
l
i
c
a
t
i
o
n
.
12.1.6
1
2
.
1
.
6
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
If
I
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
is
i
s
used,
u
s
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process
p
r
o
c
e
s
s
for
f
o
r
the
t
h
e
new
n
e
w
application
a
p
p
l
i
c
a
t
i
o
n
should
s
h
o
u
l
d
include,
i
n
c
l
u
d
e
,
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
section
s
e
c
t
i
o
n
8:
8
:
-
Assurance
A
s
s
u
r
a
n
c
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
satisfy
s
a
t
i
s
f
y
or
o
r
exceed
e
x
c
e
e
d
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
criteria
c
r
i
t
e
r
i
a
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
the
t
h
e
new
n
e
w
application.
a
p
p
l
i
c
a
t
i
o
n
.
-
Assurance
A
s
s
u
r
a
n
c
e
that
t
h
a
t
changes
c
h
a
n
g
e
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
stated
s
t
a
t
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
plans.
p
l
a
n
s
.
12.2
1
2
.
2
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
of
o
f
a
a
tool
t
o
o
l
is
i
s
needed
n
e
e
d
e
d
when
w
h
e
n
processes
p
r
o
c
e
s
s
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
are
a
r
e
eliminated,
e
l
i
m
i
n
a
t
e
d
,
reduced
r
e
d
u
c
e
d
or
o
r
automated
a
u
t
o
m
a
t
e
d
by
b
y
the
t
h
e
use
u
s
e
of
o
f
a
a
software
s
o
f
t
w
a
r
e
tool
t
o
o
l
without
w
i
t
h
o
u
t
its
i
t
s
output
o
u
t
p
u
t
being
b
e
i
n
g
verified
v
e
r
i
f
i
e
d
as
a
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
section
s
e
c
t
i
o
n
6.
6
.
The
T
h
e
use
u
s
e
of
o
f
software
s
o
f
t
w
a
r
e
tools
t
o
o
l
s
to
t
o
automate
a
u
t
o
m
a
t
e
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
can
c
a
n
help
h
e
l
p
satisfy
s
a
t
i
s
f
y
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
insofar
i
n
s
o
f
a
r
as
a
s
they
t
h
e
y
can
c
a
n
enforce
e
n
f
o
r
c
e
conformance
c
o
n
f
o
r
m
a
n
c
e
with
w
i
t
h
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
and
a
n
d
use
u
s
e
automatic
a
u
t
o
m
a
t
i
c
checks.
c
h
e
c
k
s
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
of
o
f
the
t
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
tool
t
o
o
l
provides
p
r
o
v
i
d
e
s
confidence
c
o
n
f
i
d
e
n
c
e
at
a
t
least
l
e
a
s
t
equivalent
e
q
u
i
v
a
l
e
n
t
to
t
o
that
t
h
a
t
of
o
f
the
t
h
e
process(es)
p
r
o
c
e
s
s
(
e
s
)
eliminated,
e
l
i
m
i
n
a
t
e
d
,
reduced
r
e
d
u
c
e
d
or
o
r
automated.
a
u
t
o
m
a
t
e
d
.
If
I
f
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
of
o
f
tool
t
o
o
l
functions
f
u
n
c
t
i
o
n
s
can
c
a
n
be
b
e
demonstrated,
d
e
m
o
n
s
t
r
a
t
e
d
,
only
o
n
l
y
those
t
h
o
s
e
functions
f
u
n
c
t
i
o
n
s
that
t
h
a
t
are
a
r
e
used
u
s
e
d
to
t
o
eliminate,
e
l
i
m
i
n
a
t
e
,
reduce,
r
e
d
u
c
e
,
or
o
r
automate
a
u
t
o
m
a
t
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities,
a
c
t
i
v
i
t
i
e
s
,
and
a
n
d
whose
w
h
o
s
e
outputs
o
u
t
p
u
t
s
are
a
r
e
not
n
o
t
verified,
v
e
r
i
f
i
e
d
,
need
n
e
e
d
be
b
e
qualified.
q
u
a
l
i
f
i
e
d
.
Only
O
n
l
y
deterministic
d
e
t
e
r
m
i
n
i
s
t
i
c
tools
t
o
o
l
s
may
m
a
y
be
b
e
qualified,
q
u
a
l
i
f
i
e
d
,
that
t
h
a
t
is,
i
s
,
tools
t
o
o
l
s
which
w
h
i
c
h
produce
p
r
o
d
u
c
e
the
t
h
e
same
s
a
m
e
output
o
u
t
p
u
t
for
f
o
r
the
t
h
e
same
s
a
m
e
input
i
n
p
u
t
data
d
a
t
a
when
w
h
e
n
operating
o
p
e
r
a
t
i
n
g
in
i
n
the
t
h
e
same
s
a
m
e
environment.
e
n
v
i
r
o
n
m
e
n
t
.
The
T
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
may
m
a
y
be
b
e
applied
a
p
p
l
i
e
d
either
e
i
t
h
e
r
to
t
o
a
a
single
s
i
n
g
l
e
tool
t
o
o
l
or
o
r
to
t
o
a
a
collection
c
o
l
l
e
c
t
i
o
n
of
o
f
tools.
t
o
o
l
s
.
Software
S
o
f
t
w
a
r
e
tools
t
o
o
l
s
can
c
a
n
be
b
e
classified
c
l
a
s
s
i
f
i
e
d
as
a
s
one
o
n
e
of
o
f
two
t
w
o
types:
t
y
p
e
s
:
-
Software
S
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools:
t
o
o
l
s
:
Tools
T
o
o
l
s
whose
w
h
o
s
e
output
o
u
t
p
u
t
is
i
s
part
p
a
r
t
of
o
f
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
and
a
n
d
thus
t
h
u
s
can
c
a
n
introduce
i
n
t
r
o
d
u
c
e
errors.
e
r
r
o
r
s
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
a
a
tool
t
o
o
l
which
w
h
i
c
h
generates
g
e
n
e
r
a
t
e
s
Source
S
o
u
r
c
e
Code
C
o
d
e
directly
d
i
r
e
c
t
l
y
from
f
r
o
m
low-
l
o
w
-
level
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
would
w
o
u
l
d
have
h
a
v
e
to
t
o
be
b
e
qualified
q
u
a
l
i
f
i
e
d
if
i
f
the
t
h
e
generated
g
e
n
e
r
a
t
e
d
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
not
n
o
t
verified
v
e
r
i
f
i
e
d
as
a
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
section
s
e
c
t
i
o
n
6.
6
.
-
Software
S
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools:
t
o
o
l
s
:
Tools
T
o
o
l
s
that
t
h
a
t
cannot
c
a
n
n
o
t
introduce
i
n
t
r
o
d
u
c
e
errors,
e
r
r
o
r
s
,
but
b
u
t
may
m
a
y
fail
f
a
i
l
to
t
o
detect
d
e
t
e
c
t
them.
t
h
e
m
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
a
a
static
s
t
a
t
i
c
analyzer,
a
n
a
l
y
z
e
r
,
that
t
h
a
t
automates
a
u
t
o
m
a
t
e
s
a
a
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity,
a
c
t
i
v
i
t
y
,
should
s
h
o
u
l
d
be
b
e
qualified
q
u
a
l
i
f
i
e
d
if
i
f
the
t
h
e
function
f
u
n
c
t
i
o
n
that
t
h
a
t
it
i
t
performs
p
e
r
f
o
r
m
s
is
i
s
not
n
o
t
verified
v
e
r
i
f
i
e
d
by
b
y
another
a
n
o
t
h
e
r
activity.
a
c
t
i
v
i
t
y
.
Type
T
y
p
e
checkers,
c
h
e
c
k
e
r
s
,
analysis
a
n
a
l
y
s
i
s
tools
t
o
o
l
s
and
a
n
d
test
t
e
s
t
tools
t
o
o
l
s
are
a
r
e
other
o
t
h
e
r
examples.
e
x
a
m
p
l
e
s
.
Tool
T
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
guidance
g
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
Tools
T
o
o
l
s
should
s
h
o
u
l
d
be
b
e
qualified
q
u
a
l
i
f
i
e
d
according
a
c
c
o
r
d
i
n
g
to
t
o
the
t
h
e
type
t
y
p
e
specified
s
p
e
c
i
f
i
e
d
above.
a
b
o
v
e
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
60
6
0
-
Combined
C
o
m
b
i
n
e
d
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
and
a
n
d
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools
t
o
o
l
s
should
s
h
o
u
l
d
be
b
e
qualified
q
u
a
l
i
f
i
e
d
to
t
o
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
12.2.1,
1
2
.
2
.
1
,
unless
u
n
l
e
s
s
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
between
b
e
t
w
e
e
n
the
t
h
e
two
t
w
o
functions
f
u
n
c
t
i
o
n
s
can
c
a
n
be
b
e
demonstrated.
d
e
m
o
n
s
t
r
a
t
e
d
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process
p
r
o
c
e
s
s
and
a
n
d
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
apply
a
p
p
l
y
to
t
o
software
s
o
f
t
w
a
r
e
tools
t
o
o
l
s
to
t
o
be
b
e
qualified.
q
u
a
l
i
f
i
e
d
.
The
T
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
are
a
r
e
described
d
e
s
c
r
i
b
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
12.2.1,
1
2
.
2
.
1
,
item
i
t
e
m
d.
d
.
A
A
tool
t
o
o
l
may
m
a
y
be
b
e
qualified
q
u
a
l
i
f
i
e
d
only
o
n
l
y
for
f
o
r
use
u
s
e
on
o
n
a
a
specific
s
p
e
c
i
f
i
c
system
s
y
s
t
e
m
where
w
h
e
r
e
the
t
h
e
intention
i
n
t
e
n
t
i
o
n
to
t
o
use
u
s
e
the
t
h
e
tool
t
o
o
l
is
i
s
stated
s
t
a
t
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification.
C
e
r
t
i
f
i
c
a
t
i
o
n
.
Use
U
s
e
of
o
f
the
t
h
e
tool
t
o
o
l
for
f
o
r
other
o
t
h
e
r
systems
s
y
s
t
e
m
s
may
m
a
y
need
n
e
e
d
further
f
u
r
t
h
e
r
qualification.
q
u
a
l
i
f
i
c
a
t
i
o
n
.
12.2.1
1
2
.
2
.
1
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Criteria
C
r
i
t
e
r
i
a
for
f
o
r
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Tools
T
o
o
l
s
The
T
h
e
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
includes:
i
n
c
l
u
d
e
s
:
-
If
I
f
a
a
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tool
t
o
o
l
is
i
s
to
t
o
be
b
e
qualified,
q
u
a
l
i
f
i
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
the
t
h
e
tool.
t
o
o
l
.
should
s
h
o
u
l
d
satisfy
s
a
t
i
s
f
y
the
t
h
e
same
s
a
m
e
objectives
o
b
j
e
c
t
i
v
e
s
as
a
s
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
of
o
f
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
assigned
a
s
s
i
g
n
e
d
to
t
o
the
t
h
e
tool
t
o
o
l
should
s
h
o
u
l
d
be
b
e
the
t
h
e
same
s
a
m
e
as
a
s
that
t
h
a
t
for
f
o
r
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
it
i
t
produces,
p
r
o
d
u
c
e
s
,
unless
u
n
l
e
s
s
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
can
c
a
n
justify
j
u
s
t
i
f
y
a
a
reduction
r
e
d
u
c
t
i
o
n
in
i
n
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
of
o
f
the
t
h
e
tool
t
o
o
l
to
t
o
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
Note:
N
o
t
e
:
A
A
reduction
r
e
d
u
c
t
i
o
n
in
i
n
a
a
tool's
t
o
o
l
'
s
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
can
c
a
n
be
b
e
based
b
a
s
e
d
upon
u
p
o
n
the
t
h
e
significance
s
i
g
n
i
f
i
c
a
n
c
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
to
t
o
be
b
e
eliminated,
e
l
i
m
i
n
a
t
e
d
,
reduced
r
e
d
u
c
e
d
or
o
r
automated,
a
u
t
o
m
a
t
e
d
,
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
the
t
h
e
entire
e
n
t
i
r
e
suite
s
u
i
t
e
of
o
f
verification
v
e
r
i
f
i
c
a
t
i
o
n
activities.
a
c
t
i
v
i
t
i
e
s
.
This
T
h
i
s
significance
s
i
g
n
i
f
i
c
a
n
c
e
is
i
s
a
a
function
f
u
n
c
t
i
o
n
of:
o
f
:
-
The
T
h
e
type
t
y
p
e
of
o
f
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
to
t
o
be
b
e
eliminated,
e
l
i
m
i
n
a
t
e
d
,
reduced
r
e
d
u
c
e
d
or
o
r
automated.
a
u
t
o
m
a
t
e
d
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
a
a
verification
v
e
r
i
f
i
c
a
t
i
o
n
activity
a
c
t
i
v
i
t
y
for
f
o
r
conformance
c
o
n
f
o
r
m
a
n
c
e
of
o
f
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
with
w
i
t
h
software
s
o
f
t
w
a
r
e
indentation
i
n
d
e
n
t
a
t
i
o
n
standards
s
t
a
n
d
a
r
d
s
is
i
s
less
l
e
s
s
significant
s
i
g
n
i
f
i
c
a
n
t
than
t
h
a
n
verification
v
e
r
i
f
i
c
a
t
i
o
n
activity
a
c
t
i
v
i
t
y
for
f
o
r
compliance
c
o
m
p
l
i
a
n
c
e
of
o
f
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
with
w
i
t
h
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
The
T
h
e
likelihood
l
i
k
e
l
i
h
o
o
d
that
t
h
a
t
other
o
t
h
e
r
verification
v
e
r
i
f
i
c
a
t
i
o
n
activities
a
c
t
i
v
i
t
i
e
s
would
w
o
u
l
d
have
h
a
v
e
detected
d
e
t
e
c
t
e
d
the
t
h
e
same
s
a
m
e
error(s).
e
r
r
o
r
(
s
)
.
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
demonstrate
d
e
m
o
n
s
t
r
a
t
e
that
t
h
a
t
the
t
h
e
tool
t
o
o
l
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
its
i
t
s
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
(subparagraph
(
s
u
b
p
a
r
a
g
r
a
p
h
12.2.3.2).
1
2
.
2
.
3
.
2
)
.
This
T
h
i
s
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
may
m
a
y
involve
i
n
v
o
l
v
e
a
a
trial
t
r
i
a
l
period
p
e
r
i
o
d
during
d
u
r
i
n
g
which
w
h
i
c
h
a
a
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
tool
t
o
o
l
output
o
u
t
p
u
t
is
i
s
performed
p
e
r
f
o
r
m
e
d
and
a
n
d
tool-related
t
o
o
l
-
r
e
l
a
t
e
d
problems
p
r
o
b
l
e
m
s
are
a
r
e
analyzed,
a
n
a
l
y
z
e
d
,
recorded
r
e
c
o
r
d
e
d
and
a
n
d
corrected.
c
o
r
r
e
c
t
e
d
.
-
Software
S
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
should
s
h
o
u
l
d
be
b
e
verified
v
e
r
i
f
i
e
d
to
t
o
check
c
h
e
c
k
the
t
h
e
correctness,
c
o
r
r
e
c
t
n
e
s
s
,
consistency,
c
o
n
s
i
s
t
e
n
c
y
,
and
a
n
d
completeness
c
o
m
p
l
e
t
e
n
e
s
s
of
o
f
the
t
h
e
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
to
t
o
verify
v
e
r
i
f
y
the
t
h
e
tool
t
o
o
l
against
a
g
a
i
n
s
t
those
t
h
o
s
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
the
t
h
e
tool's
t
o
o
l
'
s
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
are
a
r
e
different
d
i
f
f
e
r
e
n
t
from
f
r
o
m
those
t
h
o
s
e
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
since
s
i
n
c
e
the
t
h
e
tool's
t
o
o
l
'
s
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
correspond
c
o
r
r
e
s
p
o
n
d
to
t
o
its
i
t
s
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
instead
i
n
s
t
e
a
d
of
o
f
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
may
m
a
y
be
b
e
achieved
a
c
h
i
e
v
e
d
by:
b
y
:
-
Review
R
e
v
i
e
w
of
o
f
the
t
h
e
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
as
a
s
described
d
e
s
c
r
i
b
e
d
in
i
n
paragraph
p
a
r
a
g
r
a
p
h
6.3.1,
6
.
3
.
1
,
items
i
t
e
m
s
a
a
and
a
n
d
b.
b
.
-
Demonstration
D
e
m
o
n
s
t
r
a
t
i
o
n
that
t
h
a
t
the
t
h
e
tool
t
o
o
l
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
its
i
t
s
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
under
u
n
d
e
r
normal
n
o
r
m
a
l
operating
o
p
e
r
a
t
i
n
g
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
Demonstration
D
e
m
o
n
s
t
r
a
t
i
o
n
that
t
h
a
t
the
t
h
e
tool
t
o
o
l
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
its
i
t
s
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
while
w
h
i
l
e
executing
e
x
e
c
u
t
i
n
g
in
i
n
abnormal
a
b
n
o
r
m
a
l
operating
o
p
e
r
a
t
i
n
g
conditions,
c
o
n
d
i
t
i
o
n
s
,
including
i
n
c
l
u
d
i
n
g
external
e
x
t
e
r
n
a
l
disturbances
d
i
s
t
u
r
b
a
n
c
e
s
and
a
n
d
selected
s
e
l
e
c
t
e
d
failures
f
a
i
l
u
r
e
s
applied
a
p
p
l
i
e
d
to
t
o
the
t
h
e
tool
t
o
o
l
and
a
n
d
its
i
t
s
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
Requirements-based
R
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
and
a
n
d
additional
a
d
d
i
t
i
o
n
a
l
tests
t
e
s
t
s
to
t
o
complete
c
o
m
p
l
e
t
e
the
t
h
e
coverage
c
o
v
e
r
a
g
e
of
o
f
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Structural
S
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
appropriate
a
p
p
r
o
p
r
i
a
t
e
for
f
o
r
the
t
h
e
tool's
t
o
o
l
'
s
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
61
6
1
-
Robustness
R
o
b
u
s
t
n
e
s
s
testing
t
e
s
t
i
n
g
for
f
o
r
tools
t
o
o
l
s
with
w
i
t
h
a
a
complex
c
o
m
p
l
e
x
data
d
a
t
a
flow
f
l
o
w
or
o
r
control
c
o
n
t
r
o
l
flow,
f
l
o
w
,
as
a
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
subparagraph
s
u
b
p
a
r
a
g
r
a
p
h
6.4.2.2,
6
.
4
.
2
.
2
,
appropriate
a
p
p
r
o
p
r
i
a
t
e
to
t
o
the
t
h
e
tool's
t
o
o
l
'
s
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
-
Analysis
A
n
a
l
y
s
i
s
of
o
f
potential
p
o
t
e
n
t
i
a
l
errors
e
r
r
o
r
s
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
tool,
t
o
o
l
,
to
t
o
confirm
c
o
n
f
i
r
m
the
t
h
e
validity
v
a
l
i
d
i
t
y
of
o
f
the
t
h
e
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan.
P
l
a
n
.
12.2.2
1
2
.
2
.
2
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Criteria
C
r
i
t
e
r
i
a
for
f
o
r
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Tools
T
o
o
l
s
The
T
h
e
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools
t
o
o
l
s
should
s
h
o
u
l
d
be
b
e
achieved
a
c
h
i
e
v
e
d
by
b
y
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
that
t
h
a
t
the
t
h
e
tool
t
o
o
l
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
its
i
t
s
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
under
u
n
d
e
r
normal
n
o
r
m
a
l
operational
o
p
e
r
a
t
i
o
n
a
l
conditions.
c
o
n
d
i
t
i
o
n
s
.
12.2.3
1
2
.
2
.
3
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Data
D
a
t
a
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data
d
a
t
a
includes:
i
n
c
l
u
d
e
s
:
-
When
W
h
e
n
qualifying
q
u
a
l
i
f
y
i
n
g
a
a
tool,
t
o
o
l
,
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
related
r
e
l
a
t
e
d
airborne
a
i
r
b
o
r
n
e
software
s
o
f
t
w
a
r
e
should
s
h
o
u
l
d
specify
s
p
e
c
i
f
y
the
t
h
e
tool
t
o
o
l
to
t
o
be
b
e
qualified
q
u
a
l
i
f
i
e
d
and
a
n
d
reference
r
e
f
e
r
e
n
c
e
the
t
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data.
d
a
t
a
.
-
The
T
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
controlled
c
o
n
t
r
o
l
l
e
d
as
a
s
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
1
1
(CC1)
(
C
C
1
)
for
f
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
and
a
n
d
CC2
C
C
2
for
f
o
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools.
t
o
o
l
s
.
-
For
F
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
the
t
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
the
t
h
e
data
d
a
t
a
in
i
n
section
s
e
c
t
i
o
n
11
1
1
and
a
n
d
have
h
a
v
e
the
t
h
e
same
s
a
m
e
characteristics
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
and
a
n
d
content
c
o
n
t
e
n
t
as
a
s
data
d
a
t
a
for
f
o
r
airborne
a
i
r
b
o
r
n
e
software,
s
o
f
t
w
a
r
e
,
with
w
i
t
h
these
t
h
e
s
e
considerations:
c
o
n
s
i
d
e
r
a
t
i
o
n
s
:
-
A
A
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
same
s
a
m
e
objectives
o
b
j
e
c
t
i
v
e
s
as
a
s
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
-
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
same
s
a
m
e
objectives
o
b
j
e
c
t
i
v
e
s
as
a
s
the
t
h
e
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data
D
a
t
a
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
-
A
A
Tool
T
o
o
l
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
same
s
a
m
e
objectives
o
b
j
e
c
t
i
v
e
s
as
a
s
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
12.2.3.1
1
2
.
2
.
3
.
1
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
For
F
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
to
t
o
be
b
e
qualified,
q
u
a
l
i
f
i
e
d
,
the
t
h
e
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
describes
d
e
s
c
r
i
b
e
s
the
t
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
This
T
h
i
s
plan
p
l
a
n
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
tool.
t
o
o
l
.
-
Details
D
e
t
a
i
l
s
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
sought,
s
o
u
g
h
t
,
that
t
h
a
t
is,
i
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
to
t
o
be
b
e
eliminated,
e
l
i
m
i
n
a
t
e
d
,
reduced
r
e
d
u
c
e
d
or
o
r
automated.
a
u
t
o
m
a
t
e
d
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
proposed
p
r
o
p
o
s
e
d
for
f
o
r
the
t
h
e
tool.
t
o
o
l
.
-
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
tool's
t
o
o
l
'
s
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
-
The
T
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
activities
a
c
t
i
v
i
t
i
e
s
to
t
o
be
b
e
performed.
p
e
r
f
o
r
m
e
d
.
-
The
T
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data
d
a
t
a
to
t
o
be
b
e
produced.
p
r
o
d
u
c
e
d
.
12.2.3.2
1
2
.
2
.
3
.
2
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
describe
d
e
s
c
r
i
b
e
the
t
h
e
tool's
t
o
o
l
'
s
operational
o
p
e
r
a
t
i
o
n
a
l
functionality.
f
u
n
c
t
i
o
n
a
l
i
t
y
.
This
T
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
tool's
t
o
o
l
'
s
functions
f
u
n
c
t
i
o
n
s
and
a
n
d
technical
t
e
c
h
n
i
c
a
l
features.
f
e
a
t
u
r
e
s
.
For
F
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
it
i
t
includes
i
n
c
l
u
d
e
s
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
performed
p
e
r
f
o
r
m
e
d
by
b
y
the
t
h
e
tool.
t
o
o
l
.
-
User
U
s
e
r
information,
i
n
f
o
r
m
a
t
i
o
n
,
such
s
u
c
h
as
a
s
installation
i
n
s
t
a
l
l
a
t
i
o
n
guides
g
u
i
d
e
s
and
a
n
d
user
u
s
e
r
manuals.
m
a
n
u
a
l
s
.
-
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
tool's
t
o
o
l
'
s
operational
o
p
e
r
a
t
i
o
n
a
l
environment.
e
n
v
i
r
o
n
m
e
n
t
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
62
6
2
-
For
F
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
the
t
h
e
expected
e
x
p
e
c
t
e
d
responses
r
e
s
p
o
n
s
e
s
of
o
f
the
t
h
e
tool
t
o
o
l
under
u
n
d
e
r
abnormal
a
b
n
o
r
m
a
l
operating
o
p
e
r
a
t
i
n
g
conditions.
c
o
n
d
i
t
i
o
n
s
.
12.2.4
1
2
.
2
.
4
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Agreement
A
g
r
e
e
m
e
n
t
The
T
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
gives
g
i
v
e
s
its
i
t
s
agreement
a
g
r
e
e
m
e
n
t
to
t
o
the
t
h
e
use
u
s
e
of
o
f
a
a
tool
t
o
o
l
in
i
n
two
t
w
o
steps:
s
t
e
p
s
:
-
For
F
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
agreement
a
g
r
e
e
m
e
n
t
with
w
i
t
h
the
t
h
e
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan.
P
l
a
n
.
For
F
o
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools,
t
o
o
l
s
,
agreement
a
g
r
e
e
m
e
n
t
with
w
i
t
h
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
-
For
F
o
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
agreement
a
g
r
e
e
m
e
n
t
with
w
i
t
h
the
t
h
e
Tool
T
o
o
l
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary.
S
u
m
m
a
r
y
.
For
F
o
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools,
t
o
o
l
s
,
agreement
a
g
r
e
e
m
e
n
t
with
w
i
t
h
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
of
o
f
the
t
h
e
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
12.3
1
2
.
3
Alternative
A
l
t
e
r
n
a
t
i
v
e
Methods
M
e
t
h
o
d
s
Some
S
o
m
e
methods
m
e
t
h
o
d
s
were
w
e
r
e
not
n
o
t
discussed
d
i
s
c
u
s
s
e
d
in
i
n
the
t
h
e
previous
p
r
e
v
i
o
u
s
sections
s
e
c
t
i
o
n
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
because
b
e
c
a
u
s
e
of
o
f
inadequate
i
n
a
d
e
q
u
a
t
e
maturity
m
a
t
u
r
i
t
y
at
a
t
the
t
h
e
time
t
i
m
e
this
t
h
i
s
document
d
o
c
u
m
e
n
t
was
w
a
s
written
w
r
i
t
t
e
n
or
o
r
limited
l
i
m
i
t
e
d
applicability
a
p
p
l
i
c
a
b
i
l
i
t
y
for
f
o
r
airborne
a
i
r
b
o
r
n
e
software.
s
o
f
t
w
a
r
e
.
It
I
t
is
i
s
not
n
o
t
the
t
h
e
intention
i
n
t
e
n
t
i
o
n
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
restrict
r
e
s
t
r
i
c
t
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
any
a
n
y
current
c
u
r
r
e
n
t
or
o
r
future
f
u
t
u
r
e
methods.
m
e
t
h
o
d
s
.
Any
A
n
y
single
s
i
n
g
l
e
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
discussed
d
i
s
c
u
s
s
e
d
in
i
n
this
t
h
i
s
subsection
s
u
b
s
e
c
t
i
o
n
is
i
s
not
n
o
t
considered
c
o
n
s
i
d
e
r
e
d
an
a
n
alternative
a
l
t
e
r
n
a
t
i
v
e
to
t
o
the
t
h
e
set
s
e
t
of
o
f
methods
m
e
t
h
o
d
s
recommended
r
e
c
o
m
m
e
n
d
e
d
by
b
y
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
but
b
u
t
may
m
a
y
be
b
e
used
u
s
e
d
in
i
n
satisfying
s
a
t
i
s
f
y
i
n
g
one
o
n
e
or
o
r
more
m
o
r
e
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
in
i
n
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Alternative
A
l
t
e
r
n
a
t
i
v
e
methods
m
e
t
h
o
d
s
may
m
a
y
be
b
e
used
u
s
e
d
to
t
o
support
s
u
p
p
o
r
t
one
o
n
e
another.
a
n
o
t
h
e
r
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
may
m
a
y
assist
a
s
s
i
s
t
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
or
o
r
a
a
qualified
q
u
a
l
i
f
i
e
d
tool
t
o
o
l
may
m
a
y
assist
a
s
s
i
s
t
the
t
h
e
use
u
s
e
of
o
f
formal
f
o
r
m
a
l
methods.
m
e
t
h
o
d
s
.
An
A
n
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
cannot
c
a
n
n
o
t
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
in
i
n
isolation
i
s
o
l
a
t
i
o
n
from
f
r
o
m
the
t
h
e
suite
s
u
i
t
e
of
o
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
The
T
h
e
effort
e
f
f
o
r
t
for
f
o
r
obtaining
o
b
t
a
i
n
i
n
g
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
of
o
f
an
a
n
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
is
i
s
dependent
d
e
p
e
n
d
e
n
t
on
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
and
a
n
d
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
on
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
using
u
s
i
n
g
an
a
n
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
includes:
i
n
c
l
u
d
e
s
:
-
An
A
n
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
should
s
h
o
u
l
d
be
b
e
shown
s
h
o
w
n
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
specify
s
p
e
c
i
f
y
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification,
C
e
r
t
i
f
i
c
a
t
i
o
n
,
and
a
n
d
obtain
o
b
t
a
i
n
agreement
a
g
r
e
e
m
e
n
t
from
f
r
o
m
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
for:
f
o
r
:
-
The
T
h
e
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
proposed
p
r
o
p
o
s
e
d
method
m
e
t
h
o
d
on
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
-
The
T
h
e
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
proposed
p
r
o
p
o
s
e
d
method
m
e
t
h
o
d
on
o
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
-
The
T
h
e
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
use
u
s
e
of
o
f
the
t
h
e
alternative
a
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
which
w
h
i
c
h
shows
s
h
o
w
s
that
t
h
a
t
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
-
The
T
h
e
rationale
r
a
t
i
o
n
a
l
e
should
s
h
o
u
l
d
be
b
e
substantiated
s
u
b
s
t
a
n
t
i
a
t
e
d
by
b
y
software
s
o
f
t
w
a
r
e
plans,
p
l
a
n
s
,
processes,
p
r
o
c
e
s
s
e
s
,
expected
e
x
p
e
c
t
e
d
results,
r
e
s
u
l
t
s
,
and
a
n
d
evidence
e
v
i
d
e
n
c
e
of
o
f
the
t
h
e
use
u
s
e
of
o
f
the
t
h
e
method.
m
e
t
h
o
d
.
12.3.1
1
2
.
3
.
1
Formal
F
o
r
m
a
l
Methods
M
e
t
h
o
d
s
Formal
F
o
r
m
a
l
methods
m
e
t
h
o
d
s
involve
i
n
v
o
l
v
e
the
t
h
e
use
u
s
e
of
o
f
formal
f
o
r
m
a
l
logic,
l
o
g
i
c
,
discrete
d
i
s
c
r
e
t
e
mathematics,
m
a
t
h
e
m
a
t
i
c
s
,
and
a
n
d
computer-readable
c
o
m
p
u
t
e
r
-
r
e
a
d
a
b
l
e
languages
l
a
n
g
u
a
g
e
s
to
t
o
improve
i
m
p
r
o
v
e
the
t
h
e
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
and
a
n
d
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
software.
s
o
f
t
w
a
r
e
.
These
T
h
e
s
e
methods
m
e
t
h
o
d
s
could
c
o
u
l
d
produce
p
r
o
d
u
c
e
an
a
n
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
whose
w
h
o
s
e
operational
o
p
e
r
a
t
i
o
n
a
l
behavior
b
e
h
a
v
i
o
r
is
i
s
known
k
n
o
w
n
with
w
i
t
h
confidence
c
o
n
f
i
d
e
n
c
e
to
t
o
be
b
e
within
w
i
t
h
i
n
a
a
defined
d
e
f
i
n
e
d
domain.
d
o
m
a
i
n
.
In
I
n
their
t
h
e
i
r
most
m
o
s
t
thorough
t
h
o
r
o
u
g
h
application,
a
p
p
l
i
c
a
t
i
o
n
,
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
could
c
o
u
l
d
be
b
e
equivalent
e
q
u
i
v
a
l
e
n
t
to
t
o
exhaustive
e
x
h
a
u
s
t
i
v
e
analysis
a
n
a
l
y
s
i
s
of
o
f
a
a
system
s
y
s
t
e
m
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
its
i
t
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Such
S
u
c
h
analysis
a
n
a
l
y
s
i
s
could
c
o
u
l
d
provide:
p
r
o
v
i
d
e
:
-
Evidence
E
v
i
d
e
n
c
e
that
t
h
a
t
the
t
h
e
system
s
y
s
t
e
m
is
i
s
complete
c
o
m
p
l
e
t
e
and
a
n
d
correct
c
o
r
r
e
c
t
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
its
i
t
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
of
o
f
which
w
h
i
c
h
code,
c
o
d
e
,
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
or
o
r
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
satisfy
s
a
t
i
s
f
y
the
t
h
e
next
n
e
x
t
higher
h
i
g
h
e
r
level
l
e
v
e
l
of
o
f
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
The
T
h
e
goal
g
o
a
l
of
o
f
applying
a
p
p
l
y
i
n
g
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
is
i
s
to
t
o
prevent
p
r
e
v
e
n
t
and
a
n
d
eliminate
e
l
i
m
i
n
a
t
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
design
d
e
s
i
g
n
and
a
n
d
code
c
o
d
e
errors
e
r
r
o
r
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
Thus,
T
h
u
s
,
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
are
a
r
e
complementary
c
o
m
p
l
e
m
e
n
t
a
r
y
to
t
o
testing.
t
e
s
t
i
n
g
.
Testing
T
e
s
t
i
n
g
shows
s
h
o
w
s
that
t
h
a
t
functional
f
u
n
c
t
i
o
n
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
satisfied
s
a
t
i
s
f
i
e
d
and
a
n
d
detects
d
e
t
e
c
t
s
errors,
e
r
r
o
r
s
,
and
a
n
d
formal
f
o
r
m
a
l
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
methods
m
e
t
h
o
d
s
could
c
o
u
l
d
be
b
e
used
u
s
e
d
to
t
o
increase
i
n
c
r
e
a
s
e
confidence
c
o
n
f
i
d
e
n
c
e
that
t
h
a
t
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
will
w
i
l
l
not
n
o
t
occur
o
c
c
u
r
(for
(
f
o
r
inputs
i
n
p
u
t
s
that
t
h
a
t
are
a
r
e
out
o
u
t
of
o
f
range)
r
a
n
g
e
)
or
o
r
unlikely
u
n
l
i
k
e
l
y
to
t
o
occur.
o
c
c
u
r
.
Formal
F
o
r
m
a
l
methods
m
e
t
h
o
d
s
may
m
a
y
be
b
e
applied
a
p
p
l
i
e
d
to
t
o
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
with
w
i
t
h
consideration
c
o
n
s
i
d
e
r
a
t
i
o
n
of
o
f
these
t
h
e
s
e
factors:
f
a
c
t
o
r
s
:
-
Levels
L
e
v
e
l
s
of
o
f
the
t
h
e
design
d
e
s
i
g
n
refinement:
r
e
f
i
n
e
m
e
n
t
:
The
T
h
e
use
u
s
e
of
o
f
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
begins
b
e
g
i
n
s
by
b
y
specifying
s
p
e
c
i
f
y
i
n
g
software
s
o
f
t
w
a
r
e
high-
h
i
g
h
-
level
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
in
i
n
a
a
formal
f
o
r
m
a
l
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
language
l
a
n
g
u
a
g
e
and
a
n
d
verifying
v
e
r
i
f
y
i
n
g
by
b
y
formal
f
o
r
m
a
l
proofs
p
r
o
o
f
s
that
t
h
a
t
they
t
h
e
y
satisfy
s
a
t
i
s
f
y
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
especially
e
s
p
e
c
i
a
l
l
y
constraints
c
o
n
s
t
r
a
i
n
t
s
on
o
n
acceptable
a
c
c
e
p
t
a
b
l
e
operation.
o
p
e
r
a
t
i
o
n
.
The
T
h
e
next
n
e
x
t
lower
l
o
w
e
r
level
l
e
v
e
l
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
then
t
h
e
n
shown
s
h
o
w
n
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Performing
P
e
r
f
o
r
m
i
n
g
this
t
h
i
s
process
p
r
o
c
e
s
s
down
d
o
w
n
to
t
o
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
provides
p
r
o
v
i
d
e
s
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
satisfies
s
a
t
i
s
f
i
e
s
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Application
A
p
p
l
i
c
a
t
i
o
n
of
o
f
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
can
c
a
n
start
s
t
a
r
t
and
a
n
d
stop
s
t
o
p
with
w
i
t
h
consecutive
c
o
n
s
e
c
u
t
i
v
e
levels
l
e
v
e
l
s
of
o
f
the
t
h
e
design
d
e
s
i
g
n
refinement,
r
e
f
i
n
e
m
e
n
t
,
providing
p
r
o
v
i
d
i
n
g
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
those
t
h
o
s
e
levels
l
e
v
e
l
s
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
specified
s
p
e
c
i
f
i
e
d
correctly.
c
o
r
r
e
c
t
l
y
.
-
Coverage
C
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
software
s
o
f
t
w
a
r
e
architecture:
a
r
c
h
i
t
e
c
t
u
r
e
:
Formal
F
o
r
m
a
l
methods
m
e
t
h
o
d
s
may
m
a
y
be
b
e
applied
a
p
p
l
i
e
d
to
t
o
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that:
t
h
a
t
:
-
Are
A
r
e
safety-related.
s
a
f
e
t
y
-
r
e
l
a
t
e
d
.
-
Can
C
a
n
be
b
e
defined
d
e
f
i
n
e
d
by
b
y
discrete
d
i
s
c
r
e
t
e
mathematics.
m
a
t
h
e
m
a
t
i
c
s
.
-
Involve
I
n
v
o
l
v
e
complex
c
o
m
p
l
e
x
behavior,
b
e
h
a
v
i
o
r
,
such
s
u
c
h
as
a
s
concurrency,
c
o
n
c
u
r
r
e
n
c
y
,
distributed
d
i
s
t
r
i
b
u
t
e
d
processing,
p
r
o
c
e
s
s
i
n
g
,
redundancy
r
e
d
u
n
d
a
n
c
y
management,
m
a
n
a
g
e
m
e
n
t
,
and
a
n
d
synchronization.
s
y
n
c
h
r
o
n
i
z
a
t
i
o
n
.
These
T
h
e
s
e
criteria
c
r
i
t
e
r
i
a
can
c
a
n
be
b
e
used
u
s
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
set
s
e
t
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
at
a
t
the
t
h
e
level
l
e
v
e
l
of
o
f
the
t
h
e
design
d
e
s
i
g
n
refinement
r
e
f
i
n
e
m
e
n
t
to
t
o
which
w
h
i
c
h
the
t
h
e
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
are
a
r
e
applied.
a
p
p
l
i
e
d
.
-
Degree
D
e
g
r
e
e
of
o
f
rigor:
r
i
g
o
r
:
Formal
F
o
r
m
a
l
methods
m
e
t
h
o
d
s
include
i
n
c
l
u
d
e
these
t
h
e
s
e
increasingly
i
n
c
r
e
a
s
i
n
g
l
y
rigorous
r
i
g
o
r
o
u
s
levels:
l
e
v
e
l
s
:
-
Formal
F
o
r
m
a
l
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
with
w
i
t
h
no
n
o
proofs.
p
r
o
o
f
s
.
-
Formal
F
o
r
m
a
l
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
with
w
i
t
h
manual
m
a
n
u
a
l
proofs.
p
r
o
o
f
s
.
-
Formal
F
o
r
m
a
l
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
with
w
i
t
h
automatically
a
u
t
o
m
a
t
i
c
a
l
l
y
checked
c
h
e
c
k
e
d
or
o
r
generated
g
e
n
e
r
a
t
e
d
proofs.
p
r
o
o
f
s
.
The
T
h
e
use
u
s
e
of
o
f
formal
f
o
r
m
a
l
specifications
s
p
e
c
i
f
i
c
a
t
i
o
n
s
alone
a
l
o
n
e
forces
f
o
r
c
e
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
to
t
o
be
b
e
unambiguous.
u
n
a
m
b
i
g
u
o
u
s
.
Manual
M
a
n
u
a
l
proof
p
r
o
o
f
is
i
s
a
a
well-understood
w
e
l
l
-
u
n
d
e
r
s
t
o
o
d
process
p
r
o
c
e
s
s
that
t
h
a
t
can
c
a
n
be
b
e
used
u
s
e
d
when
w
h
e
n
there
t
h
e
r
e
is
i
s
little
l
i
t
t
l
e
detail.
d
e
t
a
i
l
.
Automatically
A
u
t
o
m
a
t
i
c
a
l
l
y
checked
c
h
e
c
k
e
d
or
o
r
generated
g
e
n
e
r
a
t
e
d
proofs
p
r
o
o
f
s
can
c
a
n
aid
a
i
d
the
t
h
e
human
h
u
m
a
n
proof
p
r
o
o
f
process
p
r
o
c
e
s
s
and
a
n
d
offer
o
f
f
e
r
a
a
higher
h
i
g
h
e
r
degree
d
e
g
r
e
e
of
o
f
dependability,
d
e
p
e
n
d
a
b
i
l
i
t
y
,
especially
e
s
p
e
c
i
a
l
l
y
for
f
o
r
more
m
o
r
e
complicated
c
o
m
p
l
i
c
a
t
e
d
proofs.
p
r
o
o
f
s
.
12.3.2
1
2
.
3
.
2
Exhaustive
E
x
h
a
u
s
t
i
v
e
Input
I
n
p
u
t
Testing
T
e
s
t
i
n
g
There
T
h
e
r
e
are
a
r
e
situations
s
i
t
u
a
t
i
o
n
s
where
w
h
e
r
e
the
t
h
e
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
of
o
f
an
a
n
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
or
o
r
equipment
e
q
u
i
p
m
e
n
t
is
i
s
simple
s
i
m
p
l
e
and
a
n
d
isolated
i
s
o
l
a
t
e
d
such
s
u
c
h
that
t
h
a
t
the
t
h
e
set
s
e
t
of
o
f
inputs
i
n
p
u
t
s
and
a
n
d
outputs
o
u
t
p
u
t
s
can
c
a
n
be
b
e
bounded.
b
o
u
n
d
e
d
.
If
I
f
so,
s
o
,
it
i
t
may
m
a
y
be
b
e
possible
p
o
s
s
i
b
l
e
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
that
t
h
a
t
exhaustive
e
x
h
a
u
s
t
i
v
e
testing
t
e
s
t
i
n
g
of
o
f
this
t
h
i
s
input
i
n
p
u
t
space
s
p
a
c
e
can
c
a
n
be
b
e
substituted
s
u
b
s
t
i
t
u
t
e
d
for
f
o
r
a
a
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity.
a
c
t
i
v
i
t
y
.
For
F
o
r
this
t
h
i
s
alternative
a
l
t
e
r
n
a
t
i
v
e
method,
m
e
t
h
o
d
,
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
include:
i
n
c
l
u
d
e
:
-
A
A
complete
c
o
m
p
l
e
t
e
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
the
t
h
e
set
s
e
t
of
o
f
valid
v
a
l
i
d
inputs
i
n
p
u
t
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
-
An
A
n
analysis
a
n
a
l
y
s
i
s
which
w
h
i
c
h
confirms
c
o
n
f
i
r
m
s
the
t
h
e
isolation
i
s
o
l
a
t
i
o
n
of
o
f
the
t
h
e
inputs
i
n
p
u
t
s
to
t
o
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
-
Rationale
R
a
t
i
o
n
a
l
e
for
f
o
r
the
t
h
e
exhaustive
e
x
h
a
u
s
t
i
v
e
input
i
n
p
u
t
test
t
e
s
t
cases
c
a
s
e
s
and
a
n
d
procedures.
p
r
o
c
e
d
u
r
e
s
.
-
The
T
h
e
test
t
e
s
t
cases,
c
a
s
e
s
,
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
and
a
n
d
test
t
e
s
t
results.
r
e
s
u
l
t
s
.
12.3.3
1
2
.
3
.
3
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Guidelines
G
u
i
d
e
l
i
n
e
s
follow
f
o
l
l
o
w
concerning
c
o
n
c
e
r
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
as
a
s
it
i
t
applies
a
p
p
l
i
e
s
to
t
o
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software.
s
o
f
t
w
a
r
e
.
If
I
f
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
modified
m
o
d
i
f
i
e
d
because
b
e
c
a
u
s
e
of
o
f
the
t
h
e
use
u
s
e
of
o
f
multiple-
m
u
l
t
i
p
l
e
-
version
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software,
s
o
f
t
w
a
r
e
,
evidence
e
v
i
d
e
n
c
e
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
satisfied
s
a
t
i
s
f
i
e
d
and
a
n
d
that
t
h
a
t
equivalent
e
q
u
i
v
a
l
e
n
t
error
e
r
r
o
r
detection
d
e
t
e
c
t
i
o
n
is
i
s
achieved
a
c
h
i
e
v
e
d
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
version.
v
e
r
s
i
o
n
.
63
6
3
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
64
6
4
Multiple,
M
u
l
t
i
p
l
e
,
dissimilar
d
i
s
s
i
m
i
l
a
r
versions
v
e
r
s
i
o
n
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
are
a
r
e
produced
p
r
o
d
u
c
e
d
using
u
s
i
n
g
combinations
c
o
m
b
i
n
a
t
i
o
n
s
of
o
f
these
t
h
e
s
e
techniques:
t
e
c
h
n
i
q
u
e
s
:
-
The
T
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
implemented
i
m
p
l
e
m
e
n
t
e
d
in
i
n
two
t
w
o
or
o
r
more
m
o
r
e
different
d
i
f
f
e
r
e
n
t
programming
p
r
o
g
r
a
m
m
i
n
g
languages.
l
a
n
g
u
a
g
e
s
.
-
The
T
h
e
object
o
b
j
e
c
t
code
c
o
d
e
is
i
s
generated
g
e
n
e
r
a
t
e
d
using
u
s
i
n
g
two
t
w
o
or
o
r
more
m
o
r
e
different
d
i
f
f
e
r
e
n
t
compilers.
c
o
m
p
i
l
e
r
s
.
-
Each
E
a
c
h
software
s
o
f
t
w
a
r
e
version
v
e
r
s
i
o
n
of
o
f
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
executes
e
x
e
c
u
t
e
s
on
o
n
a
a
separate,
s
e
p
a
r
a
t
e
,
dissimilar
d
i
s
s
i
m
i
l
a
r
processor,
p
r
o
c
e
s
s
o
r
,
or
o
r
on
o
n
a
a
single
s
i
n
g
l
e
processor
p
r
o
c
e
s
s
o
r
with
w
i
t
h
the
t
h
e
means
m
e
a
n
s
to
t
o
provide
p
r
o
v
i
d
e
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
versions.
v
e
r
s
i
o
n
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
design,
d
e
s
i
g
n
,
and/or
a
n
d
/
o
r
Source
S
o
u
r
c
e
Code
C
o
d
e
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
by
b
y
two
t
w
o
or
o
r
more
m
o
r
e
development
d
e
v
e
l
o
p
m
e
n
t
teams
t
e
a
m
s
whose
w
h
o
s
e
interactions
i
n
t
e
r
a
c
t
i
o
n
s
are
a
r
e
managed.
m
a
n
a
g
e
d
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
design,
d
e
s
i
g
n
,
and/or
a
n
d
/
o
r
Source
S
o
u
r
c
e
Code
C
o
d
e
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
on
o
n
two
t
w
o
or
o
r
more
m
o
r
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environments,
e
n
v
i
r
o
n
m
e
n
t
s
,
and/or
a
n
d
/
o
r
each
e
a
c
h
version
v
e
r
s
i
o
n
is
i
s
verified
v
e
r
i
f
i
e
d
using
u
s
i
n
g
separate
s
e
p
a
r
a
t
e
test
t
e
s
t
environments.
e
n
v
i
r
o
n
m
e
n
t
s
.
-
The
T
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
is
i
s
linked
l
i
n
k
e
d
and
a
n
d
loaded
l
o
a
d
e
d
using
u
s
i
n
g
two
t
w
o
or
o
r
more
m
o
r
e
different
d
i
f
f
e
r
e
n
t
linkage
l
i
n
k
a
g
e
editors
e
d
i
t
o
r
s
and
a
n
d
two
t
w
o
or
o
r
more
m
o
r
e
different
d
i
f
f
e
r
e
n
t
loaders.
l
o
a
d
e
r
s
.
-
The
T
h
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
design,
d
e
s
i
g
n
,
and/or
a
n
d
/
o
r
Source
S
o
u
r
c
e
Code
C
o
d
e
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
in
i
n
conformance
c
o
n
f
o
r
m
a
n
c
e
with
w
i
t
h
two
t
w
o
or
o
r
more
m
o
r
e
different
d
i
f
f
e
r
e
n
t
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards,
S
t
a
n
d
a
r
d
s
,
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards,
S
t
a
n
d
a
r
d
s
,
and/or
a
n
d
/
o
r
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards,
S
t
a
n
d
a
r
d
s
,
respectively.
r
e
s
p
e
c
t
i
v
e
l
y
.
When
W
h
e
n
multiple
m
u
l
t
i
p
l
e
versions
v
e
r
s
i
o
n
s
of
o
f
software
s
o
f
t
w
a
r
e
are
a
r
e
used,
u
s
e
d
,
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
methods
m
e
t
h
o
d
s
may
m
a
y
be
b
e
modified
m
o
d
i
f
i
e
d
from
f
r
o
m
those
t
h
o
s
e
used
u
s
e
d
to
t
o
verify
v
e
r
i
f
y
single
s
i
n
g
l
e
version
v
e
r
s
i
o
n
software.
s
o
f
t
w
a
r
e
.
They
T
h
e
y
will
w
i
l
l
apply
a
p
p
l
y
to
t
o
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
that
t
h
a
t
are
a
r
e
multi-thread,
m
u
l
t
i
-
t
h
r
e
a
d
,
such
s
u
c
h
as
a
s
separate,
s
e
p
a
r
a
t
e
,
multiple
m
u
l
t
i
p
l
e
development
d
e
v
e
l
o
p
m
e
n
t
teams.
t
e
a
m
s
.
The
T
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
is
i
s
dependent
d
e
p
e
n
d
e
n
t
on
o
n
the
t
h
e
combined
c
o
m
b
i
n
e
d
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software
s
o
f
t
w
a
r
e
architectures
a
r
c
h
i
t
e
c
t
u
r
e
s
since
s
i
n
c
e
this
t
h
i
s
affects
a
f
f
e
c
t
s
the
t
h
e
dissimilarity
d
i
s
s
i
m
i
l
a
r
i
t
y
of
o
f
the
t
h
e
multiple
m
u
l
t
i
p
l
e
software
s
o
f
t
w
a
r
e
versions.
v
e
r
s
i
o
n
s
.
Additional
A
d
d
i
t
i
o
n
a
l
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
to
t
o
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
are:
a
r
e
:
-
To
T
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
that
t
h
a
t
the
t
h
e
inter-version
i
n
t
e
r
-
v
e
r
s
i
o
n
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
satisfied,
s
a
t
i
s
f
i
e
d
,
including
i
n
c
l
u
d
i
n
g
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
during
d
u
r
i
n
g
normal
n
o
r
m
a
l
and
a
n
d
abnormal
a
b
n
o
r
m
a
l
operations
o
p
e
r
a
t
i
o
n
s
and
a
n
d
state
s
t
a
t
e
transitions.
t
r
a
n
s
i
t
i
o
n
s
.
-
To
T
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
that
t
h
a
t
equivalent
e
q
u
i
v
a
l
e
n
t
error
e
r
r
o
r
detection
d
e
t
e
c
t
i
o
n
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
Other
O
t
h
e
r
changes
c
h
a
n
g
e
s
in
i
n
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
may
m
a
y
be
b
e
agreed
a
g
r
e
e
d
with
w
i
t
h
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority,
a
u
t
h
o
r
i
t
y
,
if
i
f
the
t
h
e
changes
c
h
a
n
g
e
s
are
a
r
e
substantiated
s
u
b
s
t
a
n
t
i
a
t
e
d
by
b
y
rationale
r
a
t
i
o
n
a
l
e
that
t
h
a
t
confirms
c
o
n
f
i
r
m
s
equivalent
e
q
u
i
v
a
l
e
n
t
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
coverage.
c
o
v
e
r
a
g
e
.
12.3.3.1
1
2
.
3
.
3
.
1
Independence
I
n
d
e
p
e
n
d
e
n
c
e
of
o
f
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
When
W
h
e
n
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
versions
v
e
r
s
i
o
n
s
are
a
r
e
developed
d
e
v
e
l
o
p
e
d
independently
i
n
d
e
p
e
n
d
e
n
t
l
y
using
u
s
i
n
g
a
a
managed
m
a
n
a
g
e
d
method,
m
e
t
h
o
d
,
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
have
h
a
v
e
the
t
h
e
potential
p
o
t
e
n
t
i
a
l
to
t
o
reveal
r
e
v
e
a
l
certain
c
e
r
t
a
i
n
classes
c
l
a
s
s
e
s
of
o
f
errors
e
r
r
o
r
s
such
s
u
c
h
that
t
h
a
t
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
each
e
a
c
h
software
s
o
f
t
w
a
r
e
version
v
e
r
s
i
o
n
is
i
s
equivalent
e
q
u
i
v
a
l
e
n
t
to
t
o
independent
i
n
d
e
p
e
n
d
e
n
t
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes.
p
r
o
c
e
s
s
e
s
.
To
T
o
realize
r
e
a
l
i
z
e
the
t
h
e
advantage
a
d
v
a
n
t
a
g
e
of
o
f
this
t
h
i
s
potential,
p
o
t
e
n
t
i
a
l
,
guidance
g
u
i
d
a
n
c
e
for
f
o
r
independence
i
n
d
e
p
e
n
d
e
n
c
e
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
demonstrate
d
e
m
o
n
s
t
r
a
t
e
that
t
h
a
t
different
d
i
f
f
e
r
e
n
t
teams
t
e
a
m
s
with
w
i
t
h
limited
l
i
m
i
t
e
d
interaction
i
n
t
e
r
a
c
t
i
o
n
developed
d
e
v
e
l
o
p
e
d
each
e
a
c
h
software
s
o
f
t
w
a
r
e
version's
v
e
r
s
i
o
n
'
s
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
and
a
n
d
Source
S
o
u
r
c
e
Code.
C
o
d
e
.
-
Independent
I
n
d
e
p
e
n
d
e
n
t
test
t
e
s
t
coverage
c
o
v
e
r
a
g
e
analyses
a
n
a
l
y
s
e
s
should
s
h
o
u
l
d
still
s
t
i
l
l
be
b
e
performed
p
e
r
f
o
r
m
e
d
as
a
s
with
w
i
t
h
a
a
single
s
i
n
g
l
e
version.
v
e
r
s
i
o
n
.
12.3.3.2
1
2
.
3
.
3
.
2
Multiple
M
u
l
t
i
p
l
e
Processor-Related
P
r
o
c
e
s
s
o
r
-
R
e
l
a
t
e
d
Verification
V
e
r
i
f
i
c
a
t
i
o
n
When
W
h
e
n
each
e
a
c
h
version
v
e
r
s
i
o
n
of
o
f
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
executes
e
x
e
c
u
t
e
s
on
o
n
a
a
different
d
i
f
f
e
r
e
n
t
type
t
y
p
e
of
o
f
processor,
p
r
o
c
e
s
s
o
r
,
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
some
s
o
m
e
aspects
a
s
p
e
c
t
s
of
o
f
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
of
o
f
the
t
h
e
code
c
o
d
e
with
w
i
t
h
the
t
h
e
processor
p
r
o
c
e
s
s
o
r
(paragraph
(
p
a
r
a
g
r
a
p
h
6.4.3,
6
.
4
.
3
,
item
i
t
e
m
a)
a
)
may
m
a
y
be
b
e
replaced
r
e
p
l
a
c
e
d
by
b
y
verification
v
e
r
i
f
i
c
a
t
i
o
n
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
multiple
m
u
l
t
i
p
l
e
types
t
y
p
e
s
of
o
f
processor
p
r
o
c
e
s
s
o
r
produce
p
r
o
d
u
c
e
the
t
h
e
correct
c
o
r
r
e
c
t
outputs.
o
u
t
p
u
t
s
.
This
T
h
i
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
consists
c
o
n
s
i
s
t
s
of
o
f
integration
i
n
t
e
g
r
a
t
i
o
n
tests
t
e
s
t
s
in
i
n
which
w
h
i
c
h
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
multiple
m
u
l
t
i
p
l
e
versions
v
e
r
s
i
o
n
s
are
a
r
e
cross-
c
r
o
s
s
-
compared
c
o
m
p
a
r
e
d
in
i
n
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
cases.
c
a
s
e
s
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
show
s
h
o
w
that:
t
h
a
t
:
-
Equivalent
E
q
u
i
v
a
l
e
n
t
error
e
r
r
o
r
detection
d
e
t
e
c
t
i
o
n
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
-
Each
E
a
c
h
processor
p
r
o
c
e
s
s
o
r
was
w
a
s
designed
d
e
s
i
g
n
e
d
by
b
y
a
a
different
d
i
f
f
e
r
e
n
t
developer.
d
e
v
e
l
o
p
e
r
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
The
T
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
multiple
m
u
l
t
i
p
l
e
versions
v
e
r
s
i
o
n
s
are
a
r
e
equivalent.
e
q
u
i
v
a
l
e
n
t
.
12.3.3.3
1
2
.
3
.
3
.
3
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Source
S
o
u
r
c
e
Code
C
o
d
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
The
T
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
for
f
o
r
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
(subparagraph
(
s
u
b
p
a
r
a
g
r
a
p
h
6.4.4.2)
6
.
4
.
4
.
2
)
may
m
a
y
be
b
e
modified
m
o
d
i
f
i
e
d
for
f
o
r
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
or
o
r
equipment
e
q
u
i
p
m
e
n
t
using
u
s
i
n
g
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software.
s
o
f
t
w
a
r
e
.
Structural
S
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
may
m
a
y
be
b
e
performed
p
e
r
f
o
r
m
e
d
at
a
t
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
level
l
e
v
e
l
even
e
v
e
n
if
i
f
the
t
h
e
object
o
b
j
e
c
t
code
c
o
d
e
is
i
s
not
n
o
t
directly
d
i
r
e
c
t
l
y
traceable
t
r
a
c
e
a
b
l
e
to
t
o
Source
S
o
u
r
c
e
Code
C
o
d
e
statements
s
t
a
t
e
m
e
n
t
s
provided
p
r
o
v
i
d
e
d
that
t
h
a
t
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
shows
s
h
o
w
s
that:
t
h
a
t
:
-
Each
E
a
c
h
version
v
e
r
s
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
is
i
s
coded
c
o
d
e
d
using
u
s
i
n
g
a
a
different
d
i
f
f
e
r
e
n
t
programming
p
r
o
g
r
a
m
m
i
n
g
language.
l
a
n
g
u
a
g
e
.
-
Each
E
a
c
h
compiler
c
o
m
p
i
l
e
r
used
u
s
e
d
is
i
s
from
f
r
o
m
a
a
different
d
i
f
f
e
r
e
n
t
developer.
d
e
v
e
l
o
p
e
r
.
12.3.3.4
1
2
.
3
.
3
.
4
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
for
f
o
r
Multiple-Version
M
u
l
t
i
p
l
e
-
V
e
r
s
i
o
n
Dissimilar
D
i
s
s
i
m
i
l
a
r
Software
S
o
f
t
w
a
r
e
If
I
f
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
is
i
s
used,
u
s
e
d
,
the
t
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
may
m
a
y
be
b
e
modified,
m
o
d
i
f
i
e
d
,
if
i
f
evidence
e
v
i
d
e
n
c
e
is
i
s
available
a
v
a
i
l
a
b
l
e
that
t
h
a
t
the
t
h
e
multiple
m
u
l
t
i
p
l
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
are
a
r
e
dissimilar.
d
i
s
s
i
m
i
l
a
r
.
This
T
h
i
s
depends
d
e
p
e
n
d
s
on
o
n
the
t
h
e
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
of
o
f
equivalent
e
q
u
i
v
a
l
e
n
t
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
in
i
n
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
multiple
m
u
l
t
i
p
l
e
software
s
o
f
t
w
a
r
e
versions
v
e
r
s
i
o
n
s
using
u
s
i
n
g
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools.
t
o
o
l
s
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
show
s
h
o
w
that:
t
h
a
t
:
-
Each
E
a
c
h
tool
t
o
o
l
was
w
a
s
obtained
o
b
t
a
i
n
e
d
from
f
r
o
m
a
a
different
d
i
f
f
e
r
e
n
t
developer.
d
e
v
e
l
o
p
e
r
.
-
Each
E
a
c
h
tool
t
o
o
l
has
h
a
s
a
a
dissimilar
d
i
s
s
i
m
i
l
a
r
design.
d
e
s
i
g
n
.
12.3.3.5
1
2
.
3
.
3
.
5
Multiple
M
u
l
t
i
p
l
e
Simulators
S
i
m
u
l
a
t
o
r
s
and
a
n
d
Verification
V
e
r
i
f
i
c
a
t
i
o
n
If
I
f
separate,
s
e
p
a
r
a
t
e
,
dissimilar
d
i
s
s
i
m
i
l
a
r
simulators
s
i
m
u
l
a
t
o
r
s
are
a
r
e
used
u
s
e
d
to
t
o
verify
v
e
r
i
f
y
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
versions,
v
e
r
s
i
o
n
s
,
then
t
h
e
n
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
simulators
s
i
m
u
l
a
t
o
r
s
may
m
a
y
be
b
e
modified.
m
o
d
i
f
i
e
d
.
This
T
h
i
s
depends
d
e
p
e
n
d
s
on
o
n
the
t
h
e
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
of
o
f
equivalent
e
q
u
i
v
a
l
e
n
t
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
in
i
n
the
t
h
e
simulation
s
i
m
u
l
a
t
i
o
n
of
o
f
the
t
h
e
multiple
m
u
l
t
i
p
l
e
software
s
o
f
t
w
a
r
e
versions
v
e
r
s
i
o
n
s
using
u
s
i
n
g
multiple
m
u
l
t
i
p
l
e
simulators.
s
i
m
u
l
a
t
o
r
s
.
Unless
U
n
l
e
s
s
it
i
t
can
c
a
n
be
b
e
justified
j
u
s
t
i
f
i
e
d
as
a
s
unnecessary,
u
n
n
e
c
e
s
s
a
r
y
,
for
f
o
r
multiple
m
u
l
t
i
p
l
e
simulators
s
i
m
u
l
a
t
o
r
s
to
t
o
be
b
e
dissimilar,
d
i
s
s
i
m
i
l
a
r
,
evidence
e
v
i
d
e
n
c
e
should
s
h
o
u
l
d
be
b
e
available
a
v
a
i
l
a
b
l
e
that:
t
h
a
t
:
-
Each
E
a
c
h
simulator
s
i
m
u
l
a
t
o
r
was
w
a
s
developed
d
e
v
e
l
o
p
e
d
by
b
y
a
a
different
d
i
f
f
e
r
e
n
t
team.
t
e
a
m
.
-
Each
E
a
c
h
simulator
s
i
m
u
l
a
t
o
r
has
h
a
s
different
d
i
f
f
e
r
e
n
t
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
a
a
different
d
i
f
f
e
r
e
n
t
design
d
e
s
i
g
n
and
a
n
d
a
a
different
d
i
f
f
e
r
e
n
t
programming
p
r
o
g
r
a
m
m
i
n
g
language.
l
a
n
g
u
a
g
e
.
-
Each
E
a
c
h
simulator
s
i
m
u
l
a
t
o
r
executes
e
x
e
c
u
t
e
s
on
o
n
a
a
different
d
i
f
f
e
r
e
n
t
processor.
p
r
o
c
e
s
s
o
r
.
Note:
N
o
t
e
:
When
W
h
e
n
a
a
multiple
m
u
l
t
i
p
l
e
processor
p
r
o
c
e
s
s
o
r
system
s
y
s
t
e
m
using
u
s
i
n
g
multiple,
m
u
l
t
i
p
l
e
,
dissimilar
d
i
s
s
i
m
i
l
a
r
versions
v
e
r
s
i
o
n
s
of
o
f
software
s
o
f
t
w
a
r
e
are
a
r
e
executing
e
x
e
c
u
t
i
n
g
on
o
n
identical
i
d
e
n
t
i
c
a
l
processors,
p
r
o
c
e
s
s
o
r
s
,
it
i
t
may
m
a
y
be
b
e
difficult
d
i
f
f
i
c
u
l
t
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
dissimilarity
d
i
s
s
i
m
i
l
a
r
i
t
y
of
o
f
simulators
s
i
m
u
l
a
t
o
r
s
because
b
e
c
a
u
s
e
of
o
f
the
t
h
e
reliance
r
e
l
i
a
n
c
e
on
o
n
information
i
n
f
o
r
m
a
t
i
o
n
obtained
o
b
t
a
i
n
e
d
from
f
r
o
m
a
a
common
c
o
m
m
o
n
source,
s
o
u
r
c
e
,
the
t
h
e
processor
p
r
o
c
e
s
s
o
r
manufacturer.
m
a
n
u
f
a
c
t
u
r
e
r
.
12.3.4
1
2
.
3
.
4
Software
S
o
f
t
w
a
r
e
Reliability
R
e
l
i
a
b
i
l
i
t
y
Models
M
o
d
e
l
s
During
D
u
r
i
n
g
the
t
h
e
preparation
p
r
e
p
a
r
a
t
i
o
n
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
methods
m
e
t
h
o
d
s
for
f
o
r
estimating
e
s
t
i
m
a
t
i
n
g
the
t
h
e
post-verification
p
o
s
t
-
v
e
r
i
f
i
c
a
t
i
o
n
probabilities
p
r
o
b
a
b
i
l
i
t
i
e
s
of
o
f
software
s
o
f
t
w
a
r
e
errors
e
r
r
o
r
s
were
w
e
r
e
examined.
e
x
a
m
i
n
e
d
.
The
T
h
e
goal
g
o
a
l
was
w
a
s
to
t
o
develop
d
e
v
e
l
o
p
numerical
n
u
m
e
r
i
c
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
for
f
o
r
such
s
u
c
h
probabilities
p
r
o
b
a
b
i
l
i
t
i
e
s
for
f
o
r
software
s
o
f
t
w
a
r
e
in
i
n
computer-based
c
o
m
p
u
t
e
r
-
b
a
s
e
d
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
The
T
h
e
conclusion
c
o
n
c
l
u
s
i
o
n
reached,
r
e
a
c
h
e
d
,
however,
h
o
w
e
v
e
r
,
was
w
a
s
that
t
h
a
t
currently
c
u
r
r
e
n
t
l
y
available
a
v
a
i
l
a
b
l
e
methods
m
e
t
h
o
d
s
do
d
o
not
n
o
t
provide
p
r
o
v
i
d
e
results
r
e
s
u
l
t
s
in
i
n
which
w
h
i
c
h
confidence
c
o
n
f
i
d
e
n
c
e
can
c
a
n
be
b
e
placed
p
l
a
c
e
d
to
t
o
the
t
h
e
level
l
e
v
e
l
required
r
e
q
u
i
r
e
d
for
f
o
r
this
t
h
i
s
purpose.
p
u
r
p
o
s
e
.
Hence,
H
e
n
c
e
,
this
t
h
i
s
document
d
o
c
u
m
e
n
t
does
d
o
e
s
not
n
o
t
provide
p
r
o
v
i
d
e
guidance
g
u
i
d
a
n
c
e
for
f
o
r
software
s
o
f
t
w
a
r
e
error
e
r
r
o
r
rates.
r
a
t
e
s
.
If
I
f
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
proposes
p
r
o
p
o
s
e
s
to
t
o
use
u
s
e
software
s
o
f
t
w
a
r
e
reliability
r
e
l
i
a
b
i
l
i
t
y
models
m
o
d
e
l
s
for
f
o
r
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit,
c
r
e
d
i
t
,
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
the
t
h
e
model
m
o
d
e
l
should
s
h
o
u
l
d
be
b
e
included
i
n
c
l
u
d
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification,
C
e
r
t
i
f
i
c
a
t
i
o
n
,
and
a
n
d
agreed
a
g
r
e
e
d
with
w
i
t
h
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
12.3.5
1
2
.
3
.
5
Product
P
r
o
d
u
c
t
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
If
I
f
equivalent
e
q
u
i
v
a
l
e
n
t
safety
s
a
f
e
t
y
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
can
c
a
n
be
b
e
demonstrated
d
e
m
o
n
s
t
r
a
t
e
d
by
b
y
the
t
h
e
use
u
s
e
of
o
f
the
t
h
e
software's
s
o
f
t
w
a
r
e
'
s
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history,
h
i
s
t
o
r
y
,
some
s
o
m
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
may
m
a
y
be
b
e
granted.
g
r
a
n
t
e
d
.
The
T
h
e
acceptability
a
c
c
e
p
t
a
b
i
l
i
t
y
of
o
f
this
t
h
i
s
method
m
e
t
h
o
d
is
i
s
dependent
d
e
p
e
n
d
e
n
t
on:
o
n
:
65
6
5
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
66
6
6
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
-
Effectiveness
E
f
f
e
c
t
i
v
e
n
e
s
s
of
o
f
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
activity.
a
c
t
i
v
i
t
y
.
-
Stability
S
t
a
b
i
l
i
t
y
and
a
n
d
maturity
m
a
t
u
r
i
t
y
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
-
Relevance
R
e
l
e
v
a
n
c
e
of
o
f
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
Actual
A
c
t
u
a
l
error
e
r
r
o
r
rates
r
a
t
e
s
and
a
n
d
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
-
Impact
I
m
p
a
c
t
of
o
f
modifications.
m
o
d
i
f
i
c
a
t
i
o
n
s
.
Guidance
G
u
i
d
a
n
c
e
for
f
o
r
the
t
h
e
use
u
s
e
of
o
f
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
includes:
i
n
c
l
u
d
e
s
:
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
show
s
h
o
w
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
and
a
n
d
associated
a
s
s
o
c
i
a
t
e
d
evidence
e
v
i
d
e
n
c
e
used
u
s
e
d
to
t
o
comply
c
o
m
p
l
y
with
w
i
t
h
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
have
h
a
v
e
been
b
e
e
n
under
u
n
d
e
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
show
s
h
o
w
that
t
h
a
t
the
t
h
e
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
during
d
u
r
i
n
g
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
provides
p
r
o
v
i
d
e
s
assurance
a
s
s
u
r
a
n
c
e
that
t
h
a
t
representative
r
e
p
r
e
s
e
n
t
a
t
i
v
e
data
d
a
t
a
is
i
s
available
a
v
a
i
l
a
b
l
e
and
a
n
d
that
t
h
a
t
in
i
n
-service
-
s
e
r
v
i
c
e
problems
p
r
o
b
l
e
m
s
were
w
e
r
e
reported
r
e
p
o
r
t
e
d
and
a
n
d
recorded,
r
e
c
o
r
d
e
d
,
and
a
n
d
are
a
r
e
retrievable.
r
e
t
r
i
e
v
a
b
l
e
.
-
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
changes
c
h
a
n
g
e
s
during
d
u
r
i
n
g
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
should
s
h
o
u
l
d
be
b
e
identified
i
d
e
n
t
i
f
i
e
d
and
a
n
d
the
t
h
e
effect
e
f
f
e
c
t
analyzed
a
n
a
l
y
z
e
d
to
t
o
confirm
c
o
n
f
i
r
m
the
t
h
e
stability
s
t
a
b
i
l
i
t
y
and
a
n
d
maturity
m
a
t
u
r
i
t
y
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
Uncontrolled
U
n
c
o
n
t
r
o
l
l
e
d
changes
c
h
a
n
g
e
s
to
t
o
the
t
h
e
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
during
d
u
r
i
n
g
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
may
m
a
y
invalidate
i
n
v
a
l
i
d
a
t
e
the
t
h
e
use
u
s
e
of
o
f
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
-
The
T
h
e
intended
i
n
t
e
n
d
e
d
software
s
o
f
t
w
a
r
e
usage
u
s
a
g
e
should
s
h
o
u
l
d
be
b
e
analyzed
a
n
a
l
y
z
e
d
to
t
o
show
s
h
o
w
the
t
h
e
relevance
r
e
l
e
v
a
n
c
e
of
o
f
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
-
If
I
f
the
t
h
e
operating
o
p
e
r
a
t
i
n
g
environments
e
n
v
i
r
o
n
m
e
n
t
s
of
o
f
the
t
h
e
existing
e
x
i
s
t
i
n
g
and
a
n
d
proposed
p
r
o
p
o
s
e
d
applications
a
p
p
l
i
c
a
t
i
o
n
s
differ,
d
i
f
f
e
r
,
additional
a
d
d
i
t
i
o
n
a
l
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
confirm
c
o
n
f
i
r
m
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives.
o
b
j
e
c
t
i
v
e
s
.
f
f
The
T
h
e
analysis
a
n
a
l
y
s
i
s
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
changes
c
h
a
n
g
e
s
and
a
n
d
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
environment
e
n
v
i
r
o
n
m
e
n
t
may
m
a
y
require
r
e
q
u
i
r
e
the
t
h
e
use
u
s
e
of
o
f
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
design
d
e
s
i
g
n
data
d
a
t
a
to
t
o
confirm
c
o
n
f
i
r
m
the
t
h
e
applicability
a
p
p
l
i
c
a
b
i
l
i
t
y
of
o
f
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
If
I
f
the
t
h
e
software
s
o
f
t
w
a
r
e
is
i
s
a
a
subset
s
u
b
s
e
t
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
that
t
h
a
t
was
w
a
s
active
a
c
t
i
v
e
during
d
u
r
i
n
g
the
t
h
e
service
s
e
r
v
i
c
e
period,
p
e
r
i
o
d
,
then
t
h
e
n
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
confirm
c
o
n
f
i
r
m
the
t
h
e
equivalency
e
q
u
i
v
a
l
e
n
c
y
of
o
f
the
t
h
e
new
n
e
w
environment
e
n
v
i
r
o
n
m
e
n
t
with
w
i
t
h
the
t
h
e
previous
p
r
e
v
i
o
u
s
environment,
e
n
v
i
r
o
n
m
e
n
t
,
and
a
n
d
determine
d
e
t
e
r
m
i
n
e
those
t
h
o
s
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
that
t
h
a
t
were
w
e
r
e
not
n
o
t
executed
e
x
e
c
u
t
e
d
during
d
u
r
i
n
g
normal
n
o
r
m
a
l
operation.
o
p
e
r
a
t
i
o
n
.
Note:
N
o
t
e
:
Additional
A
d
d
i
t
i
o
n
a
l
verification
v
e
r
i
f
i
c
a
t
i
o
n
may
m
a
y
be
b
e
needed
n
e
e
d
e
d
to
t
o
confirm
c
o
n
f
i
r
m
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
those
t
h
o
s
e
components.
c
o
m
p
o
n
e
n
t
s
.
-
The
T
h
e
problem
p
r
o
b
l
e
m
report
r
e
p
o
r
t
history
h
i
s
t
o
r
y
should
s
h
o
u
l
d
be
b
e
analyzed
a
n
a
l
y
z
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
how
h
o
w
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
problems
p
r
o
b
l
e
m
s
occurred
o
c
c
u
r
r
e
d
and
a
n
d
which
w
h
i
c
h
problems
p
r
o
b
l
e
m
s
were
w
e
r
e
corrected.
c
o
r
r
e
c
t
e
d
.
-
Those
T
h
o
s
e
problems
p
r
o
b
l
e
m
s
that
t
h
a
t
are
a
r
e
indicative
i
n
d
i
c
a
t
i
v
e
of
o
f
an
a
n
inadequate
i
n
a
d
e
q
u
a
t
e
process,
p
r
o
c
e
s
s
,
such
s
u
c
h
as
a
s
design
d
e
s
i
g
n
or
o
r
code
c
o
d
e
errors,
e
r
r
o
r
s
,
should
s
h
o
u
l
d
be
b
e
indicated
i
n
d
i
c
a
t
e
d
separately
s
e
p
a
r
a
t
e
l
y
from
f
r
o
m
those
t
h
o
s
e
whose
w
h
o
s
e
cause
c
a
u
s
e
are
a
r
e
outside
o
u
t
s
i
d
e
the
t
h
e
scope
s
c
o
p
e
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
such
s
u
c
h
as
a
s
hardware
h
a
r
d
w
a
r
e
or
o
r
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
errors.
e
r
r
o
r
s
.
-
The
T
h
e
data
d
a
t
a
described
d
e
s
c
r
i
b
e
d
above
a
b
o
v
e
and
a
n
d
these
t
h
e
s
e
items
i
t
e
m
s
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification:
C
e
r
t
i
f
i
c
a
t
i
o
n
:
-
Analysis
A
n
a
l
y
s
i
s
of
o
f
the
t
h
e
relevance
r
e
l
e
v
a
n
c
e
of
o
f
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
Length
L
e
n
g
t
h
of
o
f
service
s
e
r
v
i
c
e
period
p
e
r
i
o
d
and
a
n
d
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
calculating
c
a
l
c
u
l
a
t
i
n
g
the
t
h
e
number
n
u
m
b
e
r
of
o
f
hours
h
o
u
r
s
in
i
n
service,
s
e
r
v
i
c
e
,
including
i
n
c
l
u
d
i
n
g
factors
f
a
c
t
o
r
s
such
s
u
c
h
as
a
s
operational
o
p
e
r
a
t
i
o
n
a
l
modes,
m
o
d
e
s
,
the
t
h
e
number
n
u
m
b
e
r
of
o
f
independently
i
n
d
e
p
e
n
d
e
n
t
l
y
operating
o
p
e
r
a
t
i
n
g
copies
c
o
p
i
e
s
in
i
n
the
t
h
e
installation
i
n
s
t
a
l
l
a
t
i
o
n
and
a
n
d
in
i
n
service,
s
e
r
v
i
c
e
,
and
a
n
d
the
t
h
e
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
"normal
"
n
o
r
m
a
l
operation"
o
p
e
r
a
t
i
o
n
"
and
a
n
d
"normal
"
n
o
r
m
a
l
operation
o
p
e
r
a
t
i
o
n
time."
t
i
m
e
.
"
-
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
what
w
h
a
t
was
w
a
s
counted
c
o
u
n
t
e
d
as
a
s
an
a
n
error
e
r
r
o
r
and
a
n
d
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
that
t
h
a
t
definition.
d
e
f
i
n
i
t
i
o
n
.
-
Proposed
P
r
o
p
o
s
e
d
acceptable
a
c
c
e
p
t
a
b
l
e
error
e
r
r
o
r
rates
r
a
t
e
s
and
a
n
d
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
the
t
h
e
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period
p
e
r
i
o
d
in
i
n
relation
r
e
l
a
t
i
o
n
to
t
o
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
and
a
n
d
proposed
p
r
o
p
o
s
e
d
error
e
r
r
o
r
rates.
r
a
t
e
s
.
-
If
I
f
the
t
h
e
error
e
r
r
o
r
rate
r
a
t
e
is
i
s
greater
g
r
e
a
t
e
r
than
t
h
a
n
that
t
h
a
t
identified
i
d
e
n
t
i
f
i
e
d
in
i
n
the
t
h
e
plan,
p
l
a
n
,
these
t
h
e
s
e
errors
e
r
r
o
r
s
should
s
h
o
u
l
d
be
b
e
analyzed
a
n
a
l
y
z
e
d
and
a
n
d
the
t
h
e
analyses
a
n
a
l
y
s
e
s
reviewed
r
e
v
i
e
w
e
d
with
w
i
t
h
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
67
6
7
ANNEX
A
N
N
E
X
A
A
PROCESS
P
R
O
C
E
S
S
OBJECTIVES
O
B
J
E
C
T
I
V
E
S
AND
A
N
D
OUTPUTS
O
U
T
P
U
T
S
BY
B
Y
SOFTWARE
S
O
F
T
W
A
R
E
LEVEL
L
E
V
E
L
This
T
h
i
s
annex
a
n
n
e
x
provides
p
r
o
v
i
d
e
s
guidelines
g
u
i
d
e
l
i
n
e
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
described
d
e
s
c
r
i
b
e
d
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
These
T
h
e
s
e
tables
t
a
b
l
e
s
reference
r
e
f
e
r
e
n
c
e
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
previously
p
r
e
v
i
o
u
s
l
y
described
d
e
s
c
r
i
b
e
d
in
i
n
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
The
T
h
e
tables
t
a
b
l
e
s
include
i
n
c
l
u
d
e
guidelines
g
u
i
d
e
l
i
n
e
s
for:
f
o
r
:
-
The
T
h
e
process
p
r
o
c
e
s
s
objectives
o
b
j
e
c
t
i
v
e
s
applicable
a
p
p
l
i
c
a
b
l
e
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
For
F
o
r
level
l
e
v
e
l
E
E
software,
s
o
f
t
w
a
r
e
,
see
s
e
e
paragraph
p
a
r
a
g
r
a
p
h
2.2.2.
2
.
2
.
2
.
-
The
T
h
e
independence
i
n
d
e
p
e
n
d
e
n
c
e
by
b
y
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
applicable
a
p
p
l
i
c
a
b
l
e
to
t
o
satisfy
s
a
t
i
s
f
y
that
t
h
a
t
process's
p
r
o
c
e
s
s
'
s
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
The
T
h
e
control
c
o
n
t
r
o
l
category
c
a
t
e
g
o
r
y
by
b
y
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
(subsection
(
s
u
b
s
e
c
t
i
o
n
7.3).
7
.
3
)
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
68
6
8
Table
T
a
b
l
e
A-1
A
-
1
Software
S
o
f
t
w
a
r
e
Planning
P
l
a
n
n
i
n
g
Process
P
r
o
c
e
s
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Table
T
a
b
l
e
A-2
A
-
2
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Processes
P
r
o
c
e
s
s
e
s
69
6
9
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
70
7
0
Table
T
a
b
l
e
A-3
A
-
3
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Outputs
O
u
t
p
u
t
s
of
o
f
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Process
P
r
o
c
e
s
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Table
T
a
b
l
e
A-4
A
-
4
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Outputs
O
u
t
p
u
t
s
of
o
f
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Process
P
r
o
c
e
s
s
71
7
1
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
72
7
2
Table
T
a
b
l
e
A-5
A
-
5
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Outputs
O
u
t
p
u
t
s
of
o
f
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
&
&
Integration
I
n
t
e
g
r
a
t
i
o
n
Processes
P
r
o
c
e
s
s
e
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Table
T
a
b
l
e
A-6
A
-
6
Testing
T
e
s
t
i
n
g
of
o
f
Outputs
O
u
t
p
u
t
s
of
o
f
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
73
7
3
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
74
7
4
Table
T
a
b
l
e
A-7
A
-
7
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Process
P
r
o
c
e
s
s
Results
R
e
s
u
l
t
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
75
7
5
Table
T
a
b
l
e
A-8
A
-
8
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Process
P
r
o
c
e
s
s
Note:
N
o
t
e
:
(1)
(
1
)
Although
A
l
t
h
o
u
g
h
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
section
s
e
c
t
i
o
n
7
7
do
d
o
not
n
o
t
vary
v
a
r
y
with
w
i
t
h
software
s
o
f
t
w
a
r
e
level,
l
e
v
e
l
,
the
t
h
e
control
c
o
n
t
r
o
l
category
c
a
t
e
g
o
r
y
assigned
a
s
s
i
g
n
e
d
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
may
m
a
y
vary.
v
a
r
y
.
(2)
(
2
)
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
section
s
e
c
t
i
o
n
7
7
provide
p
r
o
v
i
d
e
a
a
sufficient
s
u
f
f
i
c
i
e
n
t
integrity
i
n
t
e
g
r
i
t
y
basis
b
a
s
i
s
in
i
n
the
t
h
e
SCM
S
C
M
process
p
r
o
c
e
s
s
activities
a
c
t
i
v
i
t
i
e
s
without
w
i
t
h
o
u
t
the
t
h
e
need
n
e
e
d
for
f
o
r
the
t
h
e
independence
i
n
d
e
p
e
n
d
e
n
c
e
criteria.
c
r
i
t
e
r
i
a
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
76
7
6
Table
T
a
b
l
e
A-9
A
-
9
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Process
P
r
o
c
e
s
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Table
T
a
b
l
e
A-10
A
-
1
0
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Liaison
L
i
a
i
s
o
n
Process
P
r
o
c
e
s
s
77
7
7
Note:
N
o
t
e
:
The
T
h
e
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
and
a
n
d
the
t
h
e
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
are
a
r
e
outputs
o
u
t
p
u
t
s
of
o
f
other
o
t
h
e
r
processes.
p
r
o
c
e
s
s
e
s
.
They
T
h
e
y
are
a
r
e
included
i
n
c
l
u
d
e
d
in
i
n
this
t
h
i
s
table
t
a
b
l
e
to
t
o
show
s
h
o
w
completion
c
o
m
p
l
e
t
i
o
n
of
o
f
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process
p
r
o
c
e
s
s
objectives.
o
b
j
e
c
t
i
v
e
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
ANNEX
A
N
N
E
X
B
B
79
7
9
ACRONYMS
A
C
R
O
N
Y
M
S
AND
A
N
D
GLOSSARY
G
L
O
S
S
A
R
Y
OF
O
F
TERMS
T
E
R
M
S
Acronyms
A
c
r
o
n
y
m
s
AC
A
C
Advisory
A
d
v
i
s
o
r
y
Circular
C
i
r
c
u
l
a
r
AMJ
A
M
J
Advisory
A
d
v
i
s
o
r
y
Material
M
a
t
e
r
i
a
l
-
-
Joint
J
o
i
n
t
CC1
C
C
1
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
I
I
CC2
C
C
2
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
COTS
C
O
T
S
commercial
c
o
m
m
e
r
c
i
a
l
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
EUROCAE
E
U
R
O
C
A
E
European
E
u
r
o
p
e
a
n
Organisation
O
r
g
a
n
i
s
a
t
i
o
n
for
f
o
r
Civil
C
i
v
i
l
Aviation
A
v
i
a
t
i
o
n
Equipment
E
q
u
i
p
m
e
n
t
FAA
F
A
A
Federal
F
e
d
e
r
a
l
Aviation
A
v
i
a
t
i
o
n
Administration
A
d
m
i
n
i
s
t
r
a
t
i
o
n
FAR
F
A
R
Federal
F
e
d
e
r
a
l
Aviation
A
v
i
a
t
i
o
n
Regulation
R
e
g
u
l
a
t
i
o
n
IC
I
C
integrated
i
n
t
e
g
r
a
t
e
d
circuit
c
i
r
c
u
i
t
I/O
I
/
O
input
i
n
p
u
t
and/or
a
n
d
/
o
r
output
o
u
t
p
u
t
JAA
J
A
A
Joint
J
o
i
n
t
Aviation
A
v
i
a
t
i
o
n
Authorities
A
u
t
h
o
r
i
t
i
e
s
JAR
J
A
R
Joint
J
o
i
n
t
Aviation
A
v
i
a
t
i
o
n
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
RTCA
R
T
C
A
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
SCI
S
C
I
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
SCM
S
C
M
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
SECI
S
E
C
I
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
SQA
S
Q
A
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
80
8
0
Glossary
G
l
o
s
s
a
r
y
These
T
h
e
s
e
definitions
d
e
f
i
n
i
t
i
o
n
s
are
a
r
e
provided
p
r
o
v
i
d
e
d
for
f
o
r
the
t
h
e
terms
t
e
r
m
s
which
w
h
i
c
h
are
a
r
e
used
u
s
e
d
in
i
n
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
If
I
f
a
a
term
t
e
r
m
is
i
s
not
n
o
t
defined
d
e
f
i
n
e
d
in
i
n
this
t
h
i
s
annex,
a
n
n
e
x
,
it
i
t
is
i
s
possible
p
o
s
s
i
b
l
e
that
t
h
a
t
it
i
t
is
i
s
defined
d
e
f
i
n
e
d
instead
i
n
s
t
e
a
d
in
i
n
the
t
h
e
body
b
o
d
y
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Refer
R
e
f
e
r
to
t
o
the
t
h
e
American
A
m
e
r
i
c
a
n
Heritage
H
e
r
i
t
a
g
e
Dictionary
D
i
c
t
i
o
n
a
r
y
for
f
o
r
the
t
h
e
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
common
c
o
m
m
o
n
terms.
t
e
r
m
s
.
Algorithm
A
l
g
o
r
i
t
h
m
-
-
A
A
finite
f
i
n
i
t
e
set
s
e
t
of
o
f
well-defined
w
e
l
l
-
d
e
f
i
n
e
d
rules
r
u
l
e
s
that
t
h
a
t
gives
g
i
v
e
s
a
a
sequence
s
e
q
u
e
n
c
e
of
o
f
operations
o
p
e
r
a
t
i
o
n
s
for
f
o
r
performing
p
e
r
f
o
r
m
i
n
g
a
a
specific
s
p
e
c
i
f
i
c
task.
t
a
s
k
.
Anomalous
A
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
-
-
Behavior
B
e
h
a
v
i
o
r
that
t
h
a
t
is
i
s
inconsistent
i
n
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
specified
s
p
e
c
i
f
i
e
d
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Applicant
A
p
p
l
i
c
a
n
t
-
-
A
A
person
p
e
r
s
o
n
or
o
r
organization
o
r
g
a
n
i
z
a
t
i
o
n
seeking
s
e
e
k
i
n
g
approval
a
p
p
r
o
v
a
l
from
f
r
o
m
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority.
a
u
t
h
o
r
i
t
y
.
Approval
A
p
p
r
o
v
a
l
-
-
The
T
h
e
act
a
c
t
or
o
r
instance
i
n
s
t
a
n
c
e
of
o
f
expressing
e
x
p
r
e
s
s
i
n
g
a
a
favorable
f
a
v
o
r
a
b
l
e
opinion
o
p
i
n
i
o
n
or
o
r
giving
g
i
v
i
n
g
formal
f
o
r
m
a
l
or
o
r
official
o
f
f
i
c
i
a
l
sanction.
s
a
n
c
t
i
o
n
.
Assurance
A
s
s
u
r
a
n
c
e
-
-
The
T
h
e
planned
p
l
a
n
n
e
d
and
a
n
d
systematic
s
y
s
t
e
m
a
t
i
c
actions
a
c
t
i
o
n
s
necessary
n
e
c
e
s
s
a
r
y
to
t
o
provide
p
r
o
v
i
d
e
adequate
a
d
e
q
u
a
t
e
confidence
c
o
n
f
i
d
e
n
c
e
and
a
n
d
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
a
a
product
p
r
o
d
u
c
t
or
o
r
process
p
r
o
c
e
s
s
satisfies
s
a
t
i
s
f
i
e
s
given
g
i
v
e
n
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Audit
A
u
d
i
t
-
-
An
A
n
independent
i
n
d
e
p
e
n
d
e
n
t
examination
e
x
a
m
i
n
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
their
t
h
e
i
r
outputs
o
u
t
p
u
t
s
to
t
o
confirm
c
o
n
f
i
r
m
required
r
e
q
u
i
r
e
d
attributes.
a
t
t
r
i
b
u
t
e
s
.
Baseline
B
a
s
e
l
i
n
e
-
-
The
T
h
e
approved,
a
p
p
r
o
v
e
d
,
recorded
r
e
c
o
r
d
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
of
o
f
one
o
n
e
or
o
r
more
m
o
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items,
i
t
e
m
s
,
that
t
h
a
t
thereafter
t
h
e
r
e
a
f
t
e
r
serves
s
e
r
v
e
s
as
a
s
the
t
h
e
basis
b
a
s
i
s
for
f
o
r
further
f
u
r
t
h
e
r
development,
d
e
v
e
l
o
p
m
e
n
t
,
and
a
n
d
that
t
h
a
t
is
i
s
changed
c
h
a
n
g
e
d
only
o
n
l
y
through
t
h
r
o
u
g
h
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
procedures.
p
r
o
c
e
d
u
r
e
s
.
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
-
-
Legal
L
e
g
a
l
recognition
r
e
c
o
g
n
i
t
i
o
n
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
that
t
h
a
t
a
a
product,
p
r
o
d
u
c
t
,
service,
s
e
r
v
i
c
e
,
organization
o
r
g
a
n
i
z
a
t
i
o
n
or
o
r
person
p
e
r
s
o
n
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Such
S
u
c
h
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
comprises
c
o
m
p
r
i
s
e
s
the
t
h
e
activity
a
c
t
i
v
i
t
y
of
o
f
technically
t
e
c
h
n
i
c
a
l
l
y
checking
c
h
e
c
k
i
n
g
the
t
h
e
product,
p
r
o
d
u
c
t
,
service,
s
e
r
v
i
c
e
,
organization
o
r
g
a
n
i
z
a
t
i
o
n
or
o
r
person
p
e
r
s
o
n
and
a
n
d
the
t
h
e
formal
f
o
r
m
a
l
recognition
r
e
c
o
g
n
i
t
i
o
n
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
by
b
y
issue
i
s
s
u
e
of
o
f
a
a
certificate,
c
e
r
t
i
f
i
c
a
t
e
,
license,
l
i
c
e
n
s
e
,
approval
a
p
p
r
o
v
a
l
or
o
r
other
o
t
h
e
r
documents
d
o
c
u
m
e
n
t
s
as
a
s
required
r
e
q
u
i
r
e
d
by
b
y
national
n
a
t
i
o
n
a
l
laws
l
a
w
s
and
a
n
d
procedures.
p
r
o
c
e
d
u
r
e
s
.
In
I
n
particular,
p
a
r
t
i
c
u
l
a
r
,
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
a
a
product
p
r
o
d
u
c
t
involves:
i
n
v
o
l
v
e
s
:
(a)
(
a
)
the
t
h
e
process
p
r
o
c
e
s
s
of
o
f
assessing
a
s
s
e
s
s
i
n
g
the
t
h
e
design
d
e
s
i
g
n
of
o
f
a
a
product
p
r
o
d
u
c
t
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
it
i
t
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
a
a
set
s
e
t
of
o
f
standards
s
t
a
n
d
a
r
d
s
applicable
a
p
p
l
i
c
a
b
l
e
to
t
o
that
t
h
a
t
type
t
y
p
e
of
o
f
product
p
r
o
d
u
c
t
so
s
o
as
a
s
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
an
a
n
acceptable
a
c
c
e
p
t
a
b
l
e
level
l
e
v
e
l
of
o
f
safety;
s
a
f
e
t
y
;
(b)
(
b
)
the
t
h
e
process
p
r
o
c
e
s
s
of
o
f
assessing
a
s
s
e
s
s
i
n
g
an
a
n
individual
i
n
d
i
v
i
d
u
a
l
product
p
r
o
d
u
c
t
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
it
i
t
conforms
c
o
n
f
o
r
m
s
with
w
i
t
h
the
t
h
e
certified
c
e
r
t
i
f
i
e
d
type
t
y
p
e
design;
d
e
s
i
g
n
;
(c)
(
c
)
the
t
h
e
issuance
i
s
s
u
a
n
c
e
of
o
f
a
a
certificate
c
e
r
t
i
f
i
c
a
t
e
required
r
e
q
u
i
r
e
d
by
b
y
national
n
a
t
i
o
n
a
l
laws
l
a
w
s
to
t
o
declare
d
e
c
l
a
r
e
that
t
h
a
t
compliance
c
o
m
p
l
i
a
n
c
e
or
o
r
conformity
c
o
n
f
o
r
m
i
t
y
has
h
a
s
been
b
e
e
n
found
f
o
u
n
d
with
w
i
t
h
standards
s
t
a
n
d
a
r
d
s
in
i
n
accordance
a
c
c
o
r
d
a
n
c
e
with
w
i
t
h
items
i
t
e
m
s
(a)
(
a
)
or
o
r
(b)
(
b
)
above.
a
b
o
v
e
.
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Authority
A
u
t
h
o
r
i
t
y
-
-
The
T
h
e
organization
o
r
g
a
n
i
z
a
t
i
o
n
or
o
r
person
p
e
r
s
o
n
responsible
r
e
s
p
o
n
s
i
b
l
e
within
w
i
t
h
i
n
the
t
h
e
state
s
t
a
t
e
or
o
r
country
c
o
u
n
t
r
y
concerned
c
o
n
c
e
r
n
e
d
with
w
i
t
h
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
the
t
h
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Note:
N
o
t
e
:
A
A
matter
m
a
t
t
e
r
concerned
c
o
n
c
e
r
n
e
d
with
w
i
t
h
aircraft,
a
i
r
c
r
a
f
t
,
engine
e
n
g
i
n
e
or
o
r
propeller
p
r
o
p
e
l
l
e
r
type
t
y
p
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
or
o
r
with
w
i
t
h
equipment
e
q
u
i
p
m
e
n
t
approval
a
p
p
r
o
v
a
l
would
w
o
u
l
d
usually
u
s
u
a
l
l
y
be
b
e
addressed
a
d
d
r
e
s
s
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority;
a
u
t
h
o
r
i
t
y
;
matters
m
a
t
t
e
r
s
concerned
c
o
n
c
e
r
n
e
d
with
w
i
t
h
continuing
c
o
n
t
i
n
u
i
n
g
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
might
m
i
g
h
t
be
b
e
addressed
a
d
d
r
e
s
s
e
d
by
b
y
what
w
h
a
t
would
w
o
u
l
d
be
b
e
referred
r
e
f
e
r
r
e
d
to
t
o
as
a
s
the
t
h
e
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
authority.
a
u
t
h
o
r
i
t
y
.
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
-
-
Acceptance
A
c
c
e
p
t
a
n
c
e
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
that
t
h
a
t
a
a
process,
p
r
o
c
e
s
s
,
product
p
r
o
d
u
c
t
or
o
r
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
satisfies
s
a
t
i
s
f
i
e
s
a
a
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
requirement.
r
e
q
u
i
r
e
m
e
n
t
.
Change
C
h
a
n
g
e
control
c
o
n
t
r
o
l
-
-
(1)
(
1
)
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
recording,
r
e
c
o
r
d
i
n
g
,
evaluating,
e
v
a
l
u
a
t
i
n
g
,
approving
a
p
p
r
o
v
i
n
g
or
o
r
disapproving
d
i
s
a
p
p
r
o
v
i
n
g
and
a
n
d
coordinating
c
o
o
r
d
i
n
a
t
i
n
g
changes
c
h
a
n
g
e
s
to
t
o
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
after
a
f
t
e
r
formal
f
o
r
m
a
l
establishment
e
s
t
a
b
l
i
s
h
m
e
n
t
of
o
f
their
t
h
e
i
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
or
o
r
to
t
o
baselines
b
a
s
e
l
i
n
e
s
after
a
f
t
e
r
their
t
h
e
i
r
establishment.
e
s
t
a
b
l
i
s
h
m
e
n
t
.
(2)
(
2
)
The
T
h
e
systematic
s
y
s
t
e
m
a
t
i
c
evaluation,
e
v
a
l
u
a
t
i
o
n
,
coordination,
c
o
o
r
d
i
n
a
t
i
o
n
,
approval
a
p
p
r
o
v
a
l
or
o
r
disapproval
d
i
s
a
p
p
r
o
v
a
l
and
a
n
d
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
approved
a
p
p
r
o
v
e
d
changes
c
h
a
n
g
e
s
in
i
n
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
of
o
f
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
after
a
f
t
e
r
formal
f
o
r
m
a
l
establishment
e
s
t
a
b
l
i
s
h
m
e
n
t
of
o
f
its
i
t
s
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
or
o
r
to
t
o
baselines
b
a
s
e
l
i
n
e
s
after
a
f
t
e
r
their
t
h
e
i
r
establishment.
e
s
t
a
b
l
i
s
h
m
e
n
t
.
Note:
N
o
t
e
:
This
T
h
i
s
term
t
e
r
m
may
m
a
y
be
b
e
called
c
a
l
l
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
control
c
o
n
t
r
o
l
in
i
n
other
o
t
h
e
r
industry
i
n
d
u
s
t
r
y
standards.
s
t
a
n
d
a
r
d
s
.
Code
C
o
d
e
-
-
The
T
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
particular
p
a
r
t
i
c
u
l
a
r
data
d
a
t
a
or
o
r
a
a
particular
p
a
r
t
i
c
u
l
a
r
computer
c
o
m
p
u
t
e
r
program
p
r
o
g
r
a
m
in
i
n
a
a
symbolic
s
y
m
b
o
l
i
c
form,
f
o
r
m
,
such
s
u
c
h
as
a
s
source
s
o
u
r
c
e
code,
c
o
d
e
,
object
o
b
j
e
c
t
code
c
o
d
e
or
o
r
machine
m
a
c
h
i
n
e
code.
c
o
d
e
.
Commercial
C
o
m
m
e
r
c
i
a
l
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
(COTS)
(
C
O
T
S
)
software
s
o
f
t
w
a
r
e
-
-
Commercially
C
o
m
m
e
r
c
i
a
l
l
y
available
a
v
a
i
l
a
b
l
e
applications
a
p
p
l
i
c
a
t
i
o
n
s
sold
s
o
l
d
by
b
y
vendors
v
e
n
d
o
r
s
through
t
h
r
o
u
g
h
public
p
u
b
l
i
c
catalog
c
a
t
a
l
o
g
listings.
l
i
s
t
i
n
g
s
.
COTS
C
O
T
S
software
s
o
f
t
w
a
r
e
is
i
s
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
customized
c
u
s
t
o
m
i
z
e
d
or
o
r
enhanced.
e
n
h
a
n
c
e
d
.
Contract-negotiated
C
o
n
t
r
a
c
t
-
n
e
g
o
t
i
a
t
e
d
software
s
o
f
t
w
a
r
e
developed
d
e
v
e
l
o
p
e
d
for
f
o
r
a
a
specific
s
p
e
c
i
f
i
c
application
a
p
p
l
i
c
a
t
i
o
n
is
i
s
not
n
o
t
COTS
C
O
T
S
software.
s
o
f
t
w
a
r
e
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
81
8
1
Compiler
C
o
m
p
i
l
e
r
-
-
Program
P
r
o
g
r
a
m
that
t
h
a
t
translates
t
r
a
n
s
l
a
t
e
s
source
s
o
u
r
c
e
code
c
o
d
e
statements
s
t
a
t
e
m
e
n
t
s
of
o
f
a
a
high
h
i
g
h
level
l
e
v
e
l
language,
l
a
n
g
u
a
g
e
,
such
s
u
c
h
as
a
s
FORTRAN
F
O
R
T
R
A
N
or
o
r
Pascal,
P
a
s
c
a
l
,
into
i
n
t
o
object
o
b
j
e
c
t
code.
c
o
d
e
.
Component
C
o
m
p
o
n
e
n
t
-
-
A
A
self-contained
s
e
l
f
-
c
o
n
t
a
i
n
e
d
part,
p
a
r
t
,
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
parts,
p
a
r
t
s
,
subassemblies
s
u
b
a
s
s
e
m
b
l
i
e
s
or
o
r
units,
u
n
i
t
s
,
which
w
h
i
c
h
performs
p
e
r
f
o
r
m
s
a
a
distinct
d
i
s
t
i
n
c
t
function
f
u
n
c
t
i
o
n
of
o
f
a
a
system.
s
y
s
t
e
m
.
Condition
C
o
n
d
i
t
i
o
n
-
-
A
A
Boolean
B
o
o
l
e
a
n
expression
e
x
p
r
e
s
s
i
o
n
containing
c
o
n
t
a
i
n
i
n
g
no
n
o
Boolean
B
o
o
l
e
a
n
operators.
o
p
e
r
a
t
o
r
s
.
Condition/Decision
C
o
n
d
i
t
i
o
n
/
D
e
c
i
s
i
o
n
Coverage
C
o
v
e
r
a
g
e
-
-
Every
E
v
e
r
y
point
p
o
i
n
t
of
o
f
entry
e
n
t
r
y
and
a
n
d
exit
e
x
i
t
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
been
b
e
e
n
invoked
i
n
v
o
k
e
d
at
a
t
least
l
e
a
s
t
once,
o
n
c
e
,
every
e
v
e
r
y
condition
c
o
n
d
i
t
i
o
n
in
i
n
a
a
decision
d
e
c
i
s
i
o
n
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
taken
t
a
k
e
n
on
o
n
all
a
l
l
possible
p
o
s
s
i
b
l
e
outcomes
o
u
t
c
o
m
e
s
at
a
t
least
l
e
a
s
t
once,
o
n
c
e
,
and
a
n
d
every
e
v
e
r
y
decision
d
e
c
i
s
i
o
n
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
taken
t
a
k
e
n
on
o
n
all
a
l
l
possible
p
o
s
s
i
b
l
e
outcomes
o
u
t
c
o
m
e
s
at
a
t
least
l
e
a
s
t
once.
o
n
c
e
.
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
-
-
(1)
(
1
)
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
designating
d
e
s
i
g
n
a
t
i
n
g
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
in
i
n
a
a
system
s
y
s
t
e
m
and
a
n
d
recording
r
e
c
o
r
d
i
n
g
their
t
h
e
i
r
characteristics.
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
.
(2)
(
2
)
The
T
h
e
approved
a
p
p
r
o
v
e
d
documentation
d
o
c
u
m
e
n
t
a
t
i
o
n
that
t
h
a
t
defines
d
e
f
i
n
e
s
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item.
i
t
e
m
.
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
-
-
(1)
(
1
)
One
O
n
e
or
o
r
more
m
o
r
e
hardware
h
a
r
d
w
a
r
e
or
o
r
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
treated
t
r
e
a
t
e
d
as
a
s
a
a
unit
u
n
i
t
for
f
o
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
purposes.
p
u
r
p
o
s
e
s
.
(2)
(
2
)
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
treated
t
r
e
a
t
e
d
as
a
s
a
a
unit
u
n
i
t
for
f
o
r
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
purposes.
p
u
r
p
o
s
e
s
.
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
-
-
(1)
(
1
)
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
identifying
i
d
e
n
t
i
f
y
i
n
g
and
a
n
d
defining
d
e
f
i
n
i
n
g
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
of
o
f
a
a
system,
s
y
s
t
e
m
,
controlling
c
o
n
t
r
o
l
l
i
n
g
the
t
h
e
release
r
e
l
e
a
s
e
and
a
n
d
change
c
h
a
n
g
e
of
o
f
these
t
h
e
s
e
items
i
t
e
m
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle,
c
y
c
l
e
,
recording
r
e
c
o
r
d
i
n
g
and
a
n
d
reporting
r
e
p
o
r
t
i
n
g
the
t
h
e
status
s
t
a
t
u
s
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
and
a
n
d
change
c
h
a
n
g
e
requests
r
e
q
u
e
s
t
s
and
a
n
d
verifying
v
e
r
i
f
y
i
n
g
the
t
h
e
completeness
c
o
m
p
l
e
t
e
n
e
s
s
and
a
n
d
correctness
c
o
r
r
e
c
t
n
e
s
s
of
o
f
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items.
i
t
e
m
s
.
(2)
(
2
)
A
A
discipline
d
i
s
c
i
p
l
i
n
e
applying
a
p
p
l
y
i
n
g
technical
t
e
c
h
n
i
c
a
l
and
a
n
d
administrative
a
d
m
i
n
i
s
t
r
a
t
i
v
e
direction
d
i
r
e
c
t
i
o
n
and
a
n
d
surveillance
s
u
r
v
e
i
l
l
a
n
c
e
to
t
o
(a)
(
a
)
identify
i
d
e
n
t
i
f
y
and
a
n
d
record
r
e
c
o
r
d
the
t
h
e
functional
f
u
n
c
t
i
o
n
a
l
and
a
n
d
physical
p
h
y
s
i
c
a
l
characteristics
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
of
o
f
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item,
i
t
e
m
,
(b)
(
b
)
control
c
o
n
t
r
o
l
changes
c
h
a
n
g
e
s
to
t
o
those
t
h
o
s
e
characteristics,
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
,
and
a
n
d
(c)
(
c
)
record
r
e
c
o
r
d
and
a
n
d
report
r
e
p
o
r
t
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
processing
p
r
o
c
e
s
s
i
n
g
and
a
n
d
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
status.
s
t
a
t
u
s
.
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
status
s
t
a
t
u
s
accounting
a
c
c
o
u
n
t
i
n
g
-
-
The
T
h
e
recording
r
e
c
o
r
d
i
n
g
and
a
n
d
reporting
r
e
p
o
r
t
i
n
g
of
o
f
the
t
h
e
information
i
n
f
o
r
m
a
t
i
o
n
necessary
n
e
c
e
s
s
a
r
y
to
t
o
manage
m
a
n
a
g
e
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
effectively,
e
f
f
e
c
t
i
v
e
l
y
,
including
i
n
c
l
u
d
i
n
g
a
a
listing
l
i
s
t
i
n
g
of
o
f
the
t
h
e
approved
a
p
p
r
o
v
e
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
the
t
h
e
status
s
t
a
t
u
s
of
o
f
proposed
p
r
o
p
o
s
e
d
changes
c
h
a
n
g
e
s
to
t
o
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
and
a
n
d
the
t
h
e
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
status
s
t
a
t
u
s
of
o
f
approved
a
p
p
r
o
v
e
d
changes.
c
h
a
n
g
e
s
.
Control
C
o
n
t
r
o
l
coupling
c
o
u
p
l
i
n
g
-
-
The
T
h
e
manner
m
a
n
n
e
r
or
o
r
degree
d
e
g
r
e
e
by
b
y
which
w
h
i
c
h
one
o
n
e
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
influences
i
n
f
l
u
e
n
c
e
s
the
t
h
e
execution
e
x
e
c
u
t
i
o
n
of
o
f
another
a
n
o
t
h
e
r
software
s
o
f
t
w
a
r
e
component.
c
o
m
p
o
n
e
n
t
.
Control
C
o
n
t
r
o
l
program
p
r
o
g
r
a
m
-
-
A
A
computer
c
o
m
p
u
t
e
r
program
p
r
o
g
r
a
m
designed
d
e
s
i
g
n
e
d
to
t
o
schedule
s
c
h
e
d
u
l
e
and
a
n
d
to
t
o
supervise
s
u
p
e
r
v
i
s
e
the
t
h
e
execution
e
x
e
c
u
t
i
o
n
of
o
f
programs
p
r
o
g
r
a
m
s
in
i
n
a
a
computer
c
o
m
p
u
t
e
r
system.
s
y
s
t
e
m
.
Coverage
C
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
-
-
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
determining
d
e
t
e
r
m
i
n
i
n
g
the
t
h
e
degree
d
e
g
r
e
e
to
t
o
which
w
h
i
c
h
a
a
proposed
p
r
o
p
o
s
e
d
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activity
a
c
t
i
v
i
t
y
satisfies
s
a
t
i
s
f
i
e
s
its
i
t
s
objective.
o
b
j
e
c
t
i
v
e
.
Database
D
a
t
a
b
a
s
e
-
-
A
A
set
s
e
t
of
o
f
data,
d
a
t
a
,
part
p
a
r
t
or
o
r
the
t
h
e
whole
w
h
o
l
e
of
o
f
another
a
n
o
t
h
e
r
set
s
e
t
of
o
f
data,
d
a
t
a
,
consisting
c
o
n
s
i
s
t
i
n
g
of
o
f
at
a
t
least
l
e
a
s
t
one
o
n
e
file
f
i
l
e
that
t
h
a
t
is
i
s
sufficient
s
u
f
f
i
c
i
e
n
t
for
f
o
r
a
a
given
g
i
v
e
n
purpose
p
u
r
p
o
s
e
or
o
r
for
f
o
r
a
a
given
g
i
v
e
n
data
d
a
t
a
processing
p
r
o
c
e
s
s
i
n
g
system.
s
y
s
t
e
m
.
Data
D
a
t
a
coupling
c
o
u
p
l
i
n
g
-
-
The
T
h
e
dependence
d
e
p
e
n
d
e
n
c
e
of
o
f
a
a
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
on
o
n
data
d
a
t
a
not
n
o
t
exclusively
e
x
c
l
u
s
i
v
e
l
y
under
u
n
d
e
r
the
t
h
e
control
c
o
n
t
r
o
l
of
o
f
that
t
h
a
t
software
s
o
f
t
w
a
r
e
component.
c
o
m
p
o
n
e
n
t
.
Data
D
a
t
a
dictionary
d
i
c
t
i
o
n
a
r
y
-
-
The
T
h
e
detailed
d
e
t
a
i
l
e
d
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
data,
d
a
t
a
,
parameters,
p
a
r
a
m
e
t
e
r
s
,
variables,
v
a
r
i
a
b
l
e
s
,
and
a
n
d
constants
c
o
n
s
t
a
n
t
s
used
u
s
e
d
by
b
y
the
t
h
e
system.
s
y
s
t
e
m
.
Data
D
a
t
a
type
t
y
p
e
-
-
A
A
class
c
l
a
s
s
of
o
f
data,
d
a
t
a
,
characterized
c
h
a
r
a
c
t
e
r
i
z
e
d
by
b
y
the
t
h
e
members
m
e
m
b
e
r
s
of
o
f
the
t
h
e
class
c
l
a
s
s
and
a
n
d
the
t
h
e
operations
o
p
e
r
a
t
i
o
n
s
that
t
h
a
t
can
c
a
n
be
b
e
applied
a
p
p
l
i
e
d
to
t
o
them.
t
h
e
m
.
Examples
E
x
a
m
p
l
e
s
are
a
r
e
character
c
h
a
r
a
c
t
e
r
types
t
y
p
e
s
and
a
n
d
enumeration
e
n
u
m
e
r
a
t
i
o
n
types.
t
y
p
e
s
.
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
-
-
Executable
E
x
e
c
u
t
a
b
l
e
object
o
b
j
e
c
t
code
c
o
d
e
(or
(
o
r
data)
d
a
t
a
)
which
w
h
i
c
h
by
b
y
design
d
e
s
i
g
n
is
i
s
either
e
i
t
h
e
r
(a)
(
a
)
not
n
o
t
intended
i
n
t
e
n
d
e
d
to
t
o
be
b
e
executed
e
x
e
c
u
t
e
d
(code)
(
c
o
d
e
)
or
o
r
used
u
s
e
d
(data),
(
d
a
t
a
)
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
a
a
part
p
a
r
t
of
o
f
a
a
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
component,
c
o
m
p
o
n
e
n
t
,
or
o
r
(b)
(
b
)
is
i
s
only
o
n
l
y
executed
e
x
e
c
u
t
e
d
(code)
(
c
o
d
e
)
or
o
r
used
u
s
e
d
(data)
(
d
a
t
a
)
in
i
n
certain
c
e
r
t
a
i
n
configurations
c
o
n
f
i
g
u
r
a
t
i
o
n
s
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment,
e
n
v
i
r
o
n
m
e
n
t
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
code
c
o
d
e
that
t
h
a
t
is
i
s
enabled
e
n
a
b
l
e
d
by
b
y
a
a
hardware
h
a
r
d
w
a
r
e
pin
p
i
n
selection
s
e
l
e
c
t
i
o
n
or
o
r
software
s
o
f
t
w
a
r
e
programmed
p
r
o
g
r
a
m
m
e
d
options.
o
p
t
i
o
n
s
.
Dead
D
e
a
d
code
c
o
d
e
-
-
Executable
E
x
e
c
u
t
a
b
l
e
object
o
b
j
e
c
t
code
c
o
d
e
(or
(
o
r
data)
d
a
t
a
)
which,
w
h
i
c
h
,
as
a
s
a
a
result
r
e
s
u
l
t
of
o
f
a
a
design
d
e
s
i
g
n
error
e
r
r
o
r
cannot
c
a
n
n
o
t
be
b
e
executed
e
x
e
c
u
t
e
d
(code)
(
c
o
d
e
)
or
o
r
used
u
s
e
d
(data)
(
d
a
t
a
)
in
i
n
a
a
operational
o
p
e
r
a
t
i
o
n
a
l
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
of
o
f
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
environment
e
n
v
i
r
o
n
m
e
n
t
and
a
n
d
is
i
s
not
n
o
t
traceable
t
r
a
c
e
a
b
l
e
to
t
o
a
a
system
s
y
s
t
e
m
or
o
r
software
s
o
f
t
w
a
r
e
requirement
r
e
q
u
i
r
e
m
e
n
t
An
A
n
exception
e
x
c
e
p
t
i
o
n
is
i
s
embedded
e
m
b
e
d
d
e
d
identifiers.
i
d
e
n
t
i
f
i
e
r
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
82
8
2
Decision
D
e
c
i
s
i
o
n
-
-
A
A
Boolean
B
o
o
l
e
a
n
expression
e
x
p
r
e
s
s
i
o
n
composed
c
o
m
p
o
s
e
d
of
o
f
conditions
c
o
n
d
i
t
i
o
n
s
and
a
n
d
zero
z
e
r
o
or
o
r
more
m
o
r
e
Boolean
B
o
o
l
e
a
n
operators.
o
p
e
r
a
t
o
r
s
.
A
A
decision
d
e
c
i
s
i
o
n
without
w
i
t
h
o
u
t
a
a
Boolean
B
o
o
l
e
a
n
operator
o
p
e
r
a
t
o
r
is
i
s
a
a
condition.
c
o
n
d
i
t
i
o
n
.
If
I
f
a
a
condition
c
o
n
d
i
t
i
o
n
appears
a
p
p
e
a
r
s
more
m
o
r
e
than
t
h
a
n
once
o
n
c
e
in
i
n
a
a
decision,
d
e
c
i
s
i
o
n
,
each
e
a
c
h
occurrence
o
c
c
u
r
r
e
n
c
e
is
i
s
a
a
distinct
d
i
s
t
i
n
c
t
condition.
c
o
n
d
i
t
i
o
n
.
Decision
D
e
c
i
s
i
o
n
Coverage
C
o
v
e
r
a
g
e
-
-
Every
E
v
e
r
y
point
p
o
i
n
t
of
o
f
entry
e
n
t
r
y
and
a
n
d
exit
e
x
i
t
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
been
b
e
e
n
invoked
i
n
v
o
k
e
d
at
a
t
least
l
e
a
s
t
once
o
n
c
e
and
a
n
d
every
e
v
e
r
y
decision
d
e
c
i
s
i
o
n
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
taken
t
a
k
e
n
on
o
n
all
a
l
l
possible
p
o
s
s
i
b
l
e
outcomes
o
u
t
c
o
m
e
s
at
a
t
least
l
e
a
s
t
once.
o
n
c
e
.
Derived
D
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
-
-
Additional
A
d
d
i
t
i
o
n
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
resulting
r
e
s
u
l
t
i
n
g
from
f
r
o
m
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes,
p
r
o
c
e
s
s
e
s
,
which
w
h
i
c
h
may
m
a
y
not
n
o
t
be
b
e
directly
d
i
r
e
c
t
l
y
traceable
t
r
a
c
e
a
b
l
e
to
t
o
higher
h
i
g
h
e
r
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Emulator
E
m
u
l
a
t
o
r
-
-
A
A
device,
d
e
v
i
c
e
,
computer
c
o
m
p
u
t
e
r
program,
p
r
o
g
r
a
m
,
or
o
r
system
s
y
s
t
e
m
that
t
h
a
t
accepts
a
c
c
e
p
t
s
the
t
h
e
same
s
a
m
e
inputs
i
n
p
u
t
s
and
a
n
d
produces
p
r
o
d
u
c
e
s
the
t
h
e
same
s
a
m
e
output
o
u
t
p
u
t
as
a
s
a
a
given
g
i
v
e
n
system
s
y
s
t
e
m
using
u
s
i
n
g
the
t
h
e
same
s
a
m
e
object
o
b
j
e
c
t
code.
c
o
d
e
.
Equivalence
E
q
u
i
v
a
l
e
n
c
e
class
c
l
a
s
s
-
-
The
T
h
e
partition
p
a
r
t
i
t
i
o
n
of
o
f
the
t
h
e
input
i
n
p
u
t
domain
d
o
m
a
i
n
of
o
f
a
a
program
p
r
o
g
r
a
m
such
s
u
c
h
that
t
h
a
t
a
a
test
t
e
s
t
of
o
f
a
a
representative
r
e
p
r
e
s
e
n
t
a
t
i
v
e
value
v
a
l
u
e
of
o
f
the
t
h
e
class
c
l
a
s
s
is
i
s
equivalent
e
q
u
i
v
a
l
e
n
t
to
t
o
a
a
test
t
e
s
t
of
o
f
other
o
t
h
e
r
values
v
a
l
u
e
s
of
o
f
the
t
h
e
class.
c
l
a
s
s
.
Error
E
r
r
o
r
-
-
With
W
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
software,
s
o
f
t
w
a
r
e
,
a
a
mistake
m
i
s
t
a
k
e
in
i
n
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
design
d
e
s
i
g
n
or
o
r
code.
c
o
d
e
.
Failure
F
a
i
l
u
r
e
-
-
The
T
h
e
inability
i
n
a
b
i
l
i
t
y
of
o
f
a
a
system
s
y
s
t
e
m
or
o
r
system
s
y
s
t
e
m
component
c
o
m
p
o
n
e
n
t
to
t
o
perform
p
e
r
f
o
r
m
a
a
required
r
e
q
u
i
r
e
d
function
f
u
n
c
t
i
o
n
within
w
i
t
h
i
n
specified
s
p
e
c
i
f
i
e
d
limits.
l
i
m
i
t
s
.
A
A
failure
f
a
i
l
u
r
e
may
m
a
y
be
b
e
produced
p
r
o
d
u
c
e
d
when
w
h
e
n
a
a
fault
f
a
u
l
t
is
i
s
encountered.
e
n
c
o
u
n
t
e
r
e
d
.
Failure
F
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
-The
-
T
h
e
effect
e
f
f
e
c
t
on
o
n
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
its
i
t
s
occupants
o
c
c
u
p
a
n
t
s
both
b
o
t
h
direct
d
i
r
e
c
t
and
a
n
d
consequential,
c
o
n
s
e
q
u
e
n
t
i
a
l
,
caused
c
a
u
s
e
d
or
o
r
contributed
c
o
n
t
r
i
b
u
t
e
d
to
t
o
by
b
y
one
o
n
e
or
o
r
more
m
o
r
e
failures,
f
a
i
l
u
r
e
s
,
considering
c
o
n
s
i
d
e
r
i
n
g
relevant
r
e
l
e
v
a
n
t
adverse
a
d
v
e
r
s
e
operational
o
p
e
r
a
t
i
o
n
a
l
and
a
n
d
environmental
e
n
v
i
r
o
n
m
e
n
t
a
l
conditions.
c
o
n
d
i
t
i
o
n
s
.
A
A
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
is
i
s
classified
c
l
a
s
s
i
f
i
e
d
according
a
c
c
o
r
d
i
n
g
to
t
o
the
t
h
e
severity
s
e
v
e
r
i
t
y
of
o
f
its
i
t
s
effect
e
f
f
e
c
t
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
FAA
F
A
A
AC
A
C
25.1309-
2
5
.
1
3
0
9
-
1
1
A
A
or
o
r
JAA
J
A
A
AMJ
A
M
J
25.1309.
2
5
.
1
3
0
9
.
Fault
F
a
u
l
t
-
-
A
A
manifestation
m
a
n
i
f
e
s
t
a
t
i
o
n
of
o
f
an
a
n
error
e
r
r
o
r
in
i
n
software.
s
o
f
t
w
a
r
e
.
A
A
fault,
f
a
u
l
t
,
if
i
f
it
i
t
occurs,
o
c
c
u
r
s
,
may
m
a
y
cause
c
a
u
s
e
a
a
failure.
f
a
i
l
u
r
e
.
Fault
F
a
u
l
t
tolerance
t
o
l
e
r
a
n
c
e
-
-
The
T
h
e
built-in
b
u
i
l
t
-
i
n
capability
c
a
p
a
b
i
l
i
t
y
of
o
f
a
a
system
s
y
s
t
e
m
to
t
o
provide
p
r
o
v
i
d
e
continued
c
o
n
t
i
n
u
e
d
correct
c
o
r
r
e
c
t
execution
e
x
e
c
u
t
i
o
n
in
i
n
the
t
h
e
presence
p
r
e
s
e
n
c
e
of
o
f
a
a
limited
l
i
m
i
t
e
d
number
n
u
m
b
e
r
of
o
f
hardware
h
a
r
d
w
a
r
e
or
o
r
software
s
o
f
t
w
a
r
e
faults.
f
a
u
l
t
s
.
Formal
F
o
r
m
a
l
methods
m
e
t
h
o
d
s
-
-
Descriptive
D
e
s
c
r
i
p
t
i
v
e
notations
n
o
t
a
t
i
o
n
s
and
a
n
d
analytical
a
n
a
l
y
t
i
c
a
l
methods
m
e
t
h
o
d
s
used
u
s
e
d
to
t
o
construct,
c
o
n
s
t
r
u
c
t
,
develop
d
e
v
e
l
o
p
and
a
n
d
reason
r
e
a
s
o
n
about
a
b
o
u
t
mathematical
m
a
t
h
e
m
a
t
i
c
a
l
models
m
o
d
e
l
s
of
o
f
system
s
y
s
t
e
m
behavior.
b
e
h
a
v
i
o
r
.
Hardware/software
H
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration-
i
n
t
e
g
r
a
t
i
o
n
-
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
combining
c
o
m
b
i
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
into
i
n
t
o
the
t
h
e
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
-
-
Software
S
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
developed
d
e
v
e
l
o
p
e
d
from
f
r
o
m
analysis
a
n
a
l
y
s
i
s
of
o
f
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
system
s
y
s
t
e
m
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
Host
H
o
s
t
computer
c
o
m
p
u
t
e
r
-
-
The
T
h
e
computer
c
o
m
p
u
t
e
r
on
o
n
which
w
h
i
c
h
the
t
h
e
software
s
o
f
t
w
a
r
e
is
i
s
developed.
d
e
v
e
l
o
p
e
d
.
Independence
I
n
d
e
p
e
n
d
e
n
c
e
-
-
Separation
S
e
p
a
r
a
t
i
o
n
of
o
f
responsibilities
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
which
w
h
i
c
h
ensures
e
n
s
u
r
e
s
the
t
h
e
accomplishment
a
c
c
o
m
p
l
i
s
h
m
e
n
t
of
o
f
objective
o
b
j
e
c
t
i
v
e
evaluation.
e
v
a
l
u
a
t
i
o
n
.
(1)
(
1
)
For
F
o
r
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
activities,
a
c
t
i
v
i
t
i
e
s
,
independence
i
n
d
e
p
e
n
d
e
n
c
e
is
i
s
achieved
a
c
h
i
e
v
e
d
when
w
h
e
n
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
activity
a
c
t
i
v
i
t
y
is
i
s
performed
p
e
r
f
o
r
m
e
d
by
b
y
a
a
person(s)
p
e
r
s
o
n
(
s
)
other
o
t
h
e
r
than
t
h
a
n
the
t
h
e
developer
d
e
v
e
l
o
p
e
r
of
o
f
the
t
h
e
item
i
t
e
m
being
b
e
i
n
g
verified,
v
e
r
i
f
i
e
d
,
and
a
n
d
a
a
tool(s)
t
o
o
l
(
s
)
may
m
a
y
be
b
e
used
u
s
e
d
to
t
o
achieve
a
c
h
i
e
v
e
an
a
n
equivalence
e
q
u
i
v
a
l
e
n
c
e
to
t
o
the
t
h
e
human
h
u
m
a
n
verification
v
e
r
i
f
i
c
a
t
i
o
n
activity.
a
c
t
i
v
i
t
y
.
(2)
(
2
)
For
F
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process,
p
r
o
c
e
s
s
,
independence
i
n
d
e
p
e
n
d
e
n
c
e
also
a
l
s
o
includes
i
n
c
l
u
d
e
s
the
t
h
e
authority
a
u
t
h
o
r
i
t
y
to
t
o
ensure
e
n
s
u
r
e
corrective
c
o
r
r
e
c
t
i
v
e
action.
a
c
t
i
o
n
.
Integral
I
n
t
e
g
r
a
l
process
p
r
o
c
e
s
s
-
-
A
A
process
p
r
o
c
e
s
s
which
w
h
i
c
h
assists
a
s
s
i
s
t
s
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
other
o
t
h
e
r
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
and,
a
n
d
,
therefore,
t
h
e
r
e
f
o
r
e
,
remains
r
e
m
a
i
n
s
active
a
c
t
i
v
e
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
The
T
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
the
t
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process,
p
r
o
c
e
s
s
,
and
a
n
d
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process.
p
r
o
c
e
s
s
.
Interrupt
I
n
t
e
r
r
u
p
t
-
-
A
A
suspension
s
u
s
p
e
n
s
i
o
n
of
o
f
a
a
task,
t
a
s
k
,
such
s
u
c
h
as
a
s
the
t
h
e
execution
e
x
e
c
u
t
i
o
n
of
o
f
a
a
computer
c
o
m
p
u
t
e
r
program,
p
r
o
g
r
a
m
,
caused
c
a
u
s
e
d
by
b
y
an
a
n
event
e
v
e
n
t
external
e
x
t
e
r
n
a
l
to
t
o
that
t
h
a
t
task,
t
a
s
k
,
and
a
n
d
performed
p
e
r
f
o
r
m
e
d
in
i
n
such
s
u
c
h
a
a
way
w
a
y
that
t
h
a
t
the
t
h
e
task
t
a
s
k
can
c
a
n
be
b
e
resumed.
r
e
s
u
m
e
d
.
Low-level
L
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
-
-
Software
S
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
derived
d
e
r
i
v
e
d
from
f
r
o
m
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
derived
d
e
r
i
v
e
d
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
design
d
e
s
i
g
n
constraints
c
o
n
s
t
r
a
i
n
t
s
from
f
r
o
m
which
w
h
i
c
h
source
s
o
u
r
c
e
code
c
o
d
e
can
c
a
n
be
b
e
directly
d
i
r
e
c
t
l
y
implemented
i
m
p
l
e
m
e
n
t
e
d
without
w
i
t
h
o
u
t
further
f
u
r
t
h
e
r
information.
i
n
f
o
r
m
a
t
i
o
n
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
83
8
3
Means
M
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
-
-
The
T
h
e
intended
i
n
t
e
n
d
e
d
method(s)
m
e
t
h
o
d
(
s
)
to
t
o
be
b
e
used
u
s
e
d
by
b
y
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
stated
s
t
a
t
e
d
in
i
n
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
for
f
o
r
an
a
n
aircraft
a
i
r
c
r
a
f
t
or
o
r
engine.
e
n
g
i
n
e
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
statements,
s
t
a
t
e
m
e
n
t
s
,
drawings,
d
r
a
w
i
n
g
s
,
analyses,
a
n
a
l
y
s
e
s
,
calculations,
c
a
l
c
u
l
a
t
i
o
n
s
,
testing,
t
e
s
t
i
n
g
,
simulation,
s
i
m
u
l
a
t
i
o
n
,
inspection,
i
n
s
p
e
c
t
i
o
n
,
and
a
n
d
environmental
e
n
v
i
r
o
n
m
e
n
t
a
l
qualification.
q
u
a
l
i
f
i
c
a
t
i
o
n
.
Advisory
A
d
v
i
s
o
r
y
material
m
a
t
e
r
i
a
l
issued
i
s
s
u
e
d
by
b
y
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
is
i
s
used
u
s
e
d
if
i
f
appropriate.
a
p
p
r
o
p
r
i
a
t
e
.
Media
M
e
d
i
a
-
-
Devices
D
e
v
i
c
e
s
or
o
r
material
m
a
t
e
r
i
a
l
which
w
h
i
c
h
act
a
c
t
as
a
s
a
a
means
m
e
a
n
s
of
o
f
transferal
t
r
a
n
s
f
e
r
a
l
or
o
r
storage
s
t
o
r
a
g
e
of
o
f
software,
s
o
f
t
w
a
r
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
programmable
p
r
o
g
r
a
m
m
a
b
l
e
read-only
r
e
a
d
-
o
n
l
y
memory,
m
e
m
o
r
y
,
magnetic
m
a
g
n
e
t
i
c
tapes
t
a
p
e
s
or
o
r
discs,
d
i
s
c
s
,
and
a
n
d
paper.
p
a
p
e
r
.
Memory
M
e
m
o
r
y
device
d
e
v
i
c
e
-
-
An
A
n
article
a
r
t
i
c
l
e
of
o
f
hardware
h
a
r
d
w
a
r
e
capable
c
a
p
a
b
l
e
of
o
f
storing
s
t
o
r
i
n
g
machine-readable
m
a
c
h
i
n
e
-
r
e
a
d
a
b
l
e
computer
c
o
m
p
u
t
e
r
programs
p
r
o
g
r
a
m
s
and
a
n
d
associated
a
s
s
o
c
i
a
t
e
d
data.
d
a
t
a
.
It
I
t
may
m
a
y
be
b
e
an
a
n
integrated
i
n
t
e
g
r
a
t
e
d
circuit
c
i
r
c
u
i
t
chip,
c
h
i
p
,
a
a
circuit
c
i
r
c
u
i
t
card
c
a
r
d
containing
c
o
n
t
a
i
n
i
n
g
integrated
i
n
t
e
g
r
a
t
e
d
circuit
c
i
r
c
u
i
t
chips,
c
h
i
p
s
,
a
a
core
c
o
r
e
memory,
m
e
m
o
r
y
,
a
a
disk,
d
i
s
k
,
or
o
r
a
a
magnetic
m
a
g
n
e
t
i
c
tape.
t
a
p
e
.
Modified
M
o
d
i
f
i
e
d
Condition/Decision
C
o
n
d
i
t
i
o
n
/
D
e
c
i
s
i
o
n
Coverage
C
o
v
e
r
a
g
e
-
-
Every
E
v
e
r
y
point
p
o
i
n
t
of
o
f
entry
e
n
t
r
y
and
a
n
d
exit
e
x
i
t
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
been
b
e
e
n
invoked
i
n
v
o
k
e
d
at
a
t
least
l
e
a
s
t
once,
o
n
c
e
,
every
e
v
e
r
y
condition
c
o
n
d
i
t
i
o
n
in
i
n
a
a
decision
d
e
c
i
s
i
o
n
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
taken
t
a
k
e
n
all
a
l
l
possible
p
o
s
s
i
b
l
e
outcomes
o
u
t
c
o
m
e
s
at
a
t
least
l
e
a
s
t
once,
o
n
c
e
,
every
e
v
e
r
y
decision
d
e
c
i
s
i
o
n
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
taken
t
a
k
e
n
all
a
l
l
possible
p
o
s
s
i
b
l
e
outcomes
o
u
t
c
o
m
e
s
at
a
t
least
l
e
a
s
t
once,
o
n
c
e
,
and
a
n
d
each
e
a
c
h
condition
c
o
n
d
i
t
i
o
n
in
i
n
a
a
decision
d
e
c
i
s
i
o
n
has
h
a
s
been
b
e
e
n
shown
s
h
o
w
n
to
t
o
independently
i
n
d
e
p
e
n
d
e
n
t
l
y
affect
a
f
f
e
c
t
that
t
h
a
t
decision's
d
e
c
i
s
i
o
n
'
s
outcome.
o
u
t
c
o
m
e
.
A
A
condition
c
o
n
d
i
t
i
o
n
is
i
s
shown
s
h
o
w
n
to
t
o
independently
i
n
d
e
p
e
n
d
e
n
t
l
y
affect
a
f
f
e
c
t
a
a
decision's
d
e
c
i
s
i
o
n
'
s
outcome
o
u
t
c
o
m
e
by
b
y
varying
v
a
r
y
i
n
g
just
j
u
s
t
that
t
h
a
t
condition
c
o
n
d
i
t
i
o
n
while
w
h
i
l
e
holding
h
o
l
d
i
n
g
fixed
f
i
x
e
d
all
a
l
l
other
o
t
h
e
r
possible
p
o
s
s
i
b
l
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
Monitoring
M
o
n
i
t
o
r
i
n
g
-
-
(1)
(
1
)
[Safety]
[
S
a
f
e
t
y
]
Functionality
F
u
n
c
t
i
o
n
a
l
i
t
y
within
w
i
t
h
i
n
a
a
system
s
y
s
t
e
m
which
w
h
i
c
h
is
i
s
designed
d
e
s
i
g
n
e
d
to
t
o
detect
d
e
t
e
c
t
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
that
t
h
a
t
system.
s
y
s
t
e
m
.
(2)
(
2
)
[Quality
[
Q
u
a
l
i
t
y
Assurance]
A
s
s
u
r
a
n
c
e
]
The
T
h
e
act
a
c
t
of
o
f
witnessing
w
i
t
n
e
s
s
i
n
g
or
o
r
inspecting
i
n
s
p
e
c
t
i
n
g
selected
s
e
l
e
c
t
e
d
instances
i
n
s
t
a
n
c
e
s
of
o
f
test,
t
e
s
t
,
inspection,
i
n
s
p
e
c
t
i
o
n
,
or
o
r
other
o
t
h
e
r
activity,
a
c
t
i
v
i
t
y
,
or
o
r
records
r
e
c
o
r
d
s
of
o
f
those
t
h
o
s
e
activities,
a
c
t
i
v
i
t
i
e
s
,
to
t
o
assure
a
s
s
u
r
e
that
t
h
a
t
the
t
h
e
activity
a
c
t
i
v
i
t
y
is
i
s
under
u
n
d
e
r
control
c
o
n
t
r
o
l
and
a
n
d
that
t
h
a
t
the
t
h
e
reported
r
e
p
o
r
t
e
d
results
r
e
s
u
l
t
s
are
a
r
e
representative
r
e
p
r
e
s
e
n
t
a
t
i
v
e
of
o
f
the
t
h
e
expected
e
x
p
e
c
t
e
d
results.
r
e
s
u
l
t
s
.
Monitoring
M
o
n
i
t
o
r
i
n
g
is
i
s
usually
u
s
u
a
l
l
y
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
activities
a
c
t
i
v
i
t
i
e
s
done
d
o
n
e
over
o
v
e
r
an
a
n
extended
e
x
t
e
n
d
e
d
period
p
e
r
i
o
d
of
o
f
time
t
i
m
e
where
w
h
e
r
e
100%
1
0
0
%
witnessing
w
i
t
n
e
s
s
i
n
g
is
i
s
considered
c
o
n
s
i
d
e
r
e
d
impractical
i
m
p
r
a
c
t
i
c
a
l
or
o
r
unnecessary.
u
n
n
e
c
e
s
s
a
r
y
.
Monitoring
M
o
n
i
t
o
r
i
n
g
permits
p
e
r
m
i
t
s
authentication
a
u
t
h
e
n
t
i
c
a
t
i
o
n
that
t
h
a
t
the
t
h
e
claimed
c
l
a
i
m
e
d
activity
a
c
t
i
v
i
t
y
was
w
a
s
performed
p
e
r
f
o
r
m
e
d
as
a
s
planned.
p
l
a
n
n
e
d
.
Multiple-version
M
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
-
-
A
A
set
s
e
t
of
o
f
two
t
w
o
or
o
r
more
m
o
r
e
programs
p
r
o
g
r
a
m
s
developed
d
e
v
e
l
o
p
e
d
separately
s
e
p
a
r
a
t
e
l
y
to
t
o
satisfy
s
a
t
i
s
f
y
the
t
h
e
same
s
a
m
e
functional
f
u
n
c
t
i
o
n
a
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Errors
E
r
r
o
r
s
specific
s
p
e
c
i
f
i
c
to
t
o
one
o
n
e
of
o
f
the
t
h
e
versions
v
e
r
s
i
o
n
s
are
a
r
e
detected
d
e
t
e
c
t
e
d
by
b
y
comparison
c
o
m
p
a
r
i
s
o
n
of
o
f
the
t
h
e
multiple
m
u
l
t
i
p
l
e
outputs.
o
u
t
p
u
t
s
.
Object
O
b
j
e
c
t
Code
C
o
d
e
-
-
A
A
low-level
l
o
w
-
l
e
v
e
l
representation
r
e
p
r
e
s
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
computer
c
o
m
p
u
t
e
r
program
p
r
o
g
r
a
m
not
n
o
t
usually
u
s
u
a
l
l
y
in
i
n
a
a
form
f
o
r
m
directly
d
i
r
e
c
t
l
y
usable
u
s
a
b
l
e
by
b
y
the
t
h
e
target
t
a
r
g
e
t
computer
c
o
m
p
u
t
e
r
but
b
u
t
in
i
n
a
a
form
f
o
r
m
which
w
h
i
c
h
includes
i
n
c
l
u
d
e
s
relocation
r
e
l
o
c
a
t
i
o
n
information
i
n
f
o
r
m
a
t
i
o
n
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
the
t
h
e
processor
p
r
o
c
e
s
s
o
r
instruction
i
n
s
t
r
u
c
t
i
o
n
information.
i
n
f
o
r
m
a
t
i
o
n
.
Part
P
a
r
t
number
n
u
m
b
e
r
-
-
A
A
set
s
e
t
of
o
f
numbers,
n
u
m
b
e
r
s
,
letters
l
e
t
t
e
r
s
or
o
r
other
o
t
h
e
r
characters
c
h
a
r
a
c
t
e
r
s
used
u
s
e
d
to
t
o
identify
i
d
e
n
t
i
f
y
a
a
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item.
i
t
e
m
.
Process
P
r
o
c
e
s
s
-
-
A
A
modification
m
o
d
i
f
i
c
a
t
i
o
n
to
t
o
an
a
n
object
o
b
j
e
c
t
program,
p
r
o
g
r
a
m
,
in
i
n
which
w
h
i
c
h
one
o
n
e
or
o
r
more
m
o
r
e
of
o
f
the
t
h
e
planned
p
l
a
n
n
e
d
steps
s
t
e
p
s
of
o
f
re-compiling,
r
e
-
c
o
m
p
i
l
i
n
g
,
re-
r
e
-
assembling
a
s
s
e
m
b
l
i
n
g
or
o
r
re-linking
r
e
-
l
i
n
k
i
n
g
is
i
s
bypassed.
b
y
p
a
s
s
e
d
.
This
T
h
i
s
does
d
o
e
s
not
n
o
t
include
i
n
c
l
u
d
e
identifiers
i
d
e
n
t
i
f
i
e
r
s
embedded
e
m
b
e
d
d
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
product,
p
r
o
d
u
c
t
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
part
p
a
r
t
numbers
n
u
m
b
e
r
s
and
a
n
d
checksums.
c
h
e
c
k
s
u
m
s
.
Process
P
r
o
c
e
s
s
-
-
A
A
collection
c
o
l
l
e
c
t
i
o
n
of
o
f
activities
a
c
t
i
v
i
t
i
e
s
performed
p
e
r
f
o
r
m
e
d
in
i
n
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
to
t
o
produce
p
r
o
d
u
c
e
a
a
definable
d
e
f
i
n
a
b
l
e
output
o
u
t
p
u
t
or
o
r
product.
p
r
o
d
u
c
t
.
Product
P
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
-
-
A
A
contiguous
c
o
n
t
i
g
u
o
u
s
period
p
e
r
i
o
d
of
o
f
time
t
i
m
e
during
d
u
r
i
n
g
which
w
h
i
c
h
the
t
h
e
software
s
o
f
t
w
a
r
e
is
i
s
operated
o
p
e
r
a
t
e
d
within
w
i
t
h
i
n
a
a
known
k
n
o
w
n
environment,
e
n
v
i
r
o
n
m
e
n
t
,
and
a
n
d
during
d
u
r
i
n
g
which
w
h
i
c
h
successive
s
u
c
c
e
s
s
i
v
e
failures
f
a
i
l
u
r
e
s
are
a
r
e
recorded.
r
e
c
o
r
d
e
d
.
Proof
P
r
o
o
f
of
o
f
correctness
c
o
r
r
e
c
t
n
e
s
s
-A
-
A
logically
l
o
g
i
c
a
l
l
y
sound
s
o
u
n
d
argument
a
r
g
u
m
e
n
t
that
t
h
a
t
a
a
program
p
r
o
g
r
a
m
satisfies
s
a
t
i
s
f
i
e
s
its
i
t
s
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Release
R
e
l
e
a
s
e
-
-
The
T
h
e
act
a
c
t
of
o
f
formally
f
o
r
m
a
l
l
y
making
m
a
k
i
n
g
available
a
v
a
i
l
a
b
l
e
and
a
n
d
authorizing
a
u
t
h
o
r
i
z
i
n
g
the
t
h
e
use
u
s
e
of
o
f
a
a
retrievable
r
e
t
r
i
e
v
a
b
l
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item.
i
t
e
m
.
Reverse
R
e
v
e
r
s
e
engineering
e
n
g
i
n
e
e
r
i
n
g
-
-
The
T
h
e
method
m
e
t
h
o
d
of
o
f
extracting
e
x
t
r
a
c
t
i
n
g
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
information
i
n
f
o
r
m
a
t
i
o
n
from
f
r
o
m
the
t
h
e
source
s
o
u
r
c
e
code.
c
o
d
e
.
Robustness
R
o
b
u
s
t
n
e
s
s
-The
-
T
h
e
extent
e
x
t
e
n
t
to
t
o
which
w
h
i
c
h
software
s
o
f
t
w
a
r
e
can
c
a
n
continue
c
o
n
t
i
n
u
e
to
t
o
operate
o
p
e
r
a
t
e
correctly
c
o
r
r
e
c
t
l
y
despite
d
e
s
p
i
t
e
invalid
i
n
v
a
l
i
d
inputs.
i
n
p
u
t
s
.
Simulator
S
i
m
u
l
a
t
o
r
-
-
A
A
device,
d
e
v
i
c
e
,
computer
c
o
m
p
u
t
e
r
program
p
r
o
g
r
a
m
or
o
r
system
s
y
s
t
e
m
used
u
s
e
d
during
d
u
r
i
n
g
software
s
o
f
t
w
a
r
e
verification,
v
e
r
i
f
i
c
a
t
i
o
n
,
that
t
h
a
t
accepts
a
c
c
e
p
t
s
the
t
h
e
same
s
a
m
e
inputs
i
n
p
u
t
s
and
a
n
d
produces
p
r
o
d
u
c
e
s
the
t
h
e
same
s
a
m
e
output
o
u
t
p
u
t
as
a
s
a
a
given
g
i
v
e
n
system,
s
y
s
t
e
m
,
using
u
s
i
n
g
object
o
b
j
e
c
t
code
c
o
d
e
which
w
h
i
c
h
is
i
s
derived
d
e
r
i
v
e
d
from
f
r
o
m
the
t
h
e
original
o
r
i
g
i
n
a
l
object
o
b
j
e
c
t
code.
c
o
d
e
.
Software
S
o
f
t
w
a
r
e
-
-
Computer
C
o
m
p
u
t
e
r
programs
p
r
o
g
r
a
m
s
and,
a
n
d
,
possibly,
p
o
s
s
i
b
l
y
,
associated
a
s
s
o
c
i
a
t
e
d
documentation
d
o
c
u
m
e
n
t
a
t
i
o
n
and
a
n
d
data
d
a
t
a
pertaining
p
e
r
t
a
i
n
i
n
g
to
t
o
the
t
h
e
operation
o
p
e
r
a
t
i
o
n
of
o
f
a
a
computer
c
o
m
p
u
t
e
r
system.
s
y
s
t
e
m
.
Software
S
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
-
-
The
T
h
e
structure
s
t
r
u
c
t
u
r
e
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
selected
s
e
l
e
c
t
e
d
to
t
o
implement
i
m
p
l
e
m
e
n
t
the
t
h
e
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
84
8
4
Software
S
o
f
t
w
a
r
e
change
c
h
a
n
g
e
-
-
A
A
modification
m
o
d
i
f
i
c
a
t
i
o
n
in
i
n
source
s
o
u
r
c
e
code,
c
o
d
e
,
object
o
b
j
e
c
t
code,
c
o
d
e
,
executable
e
x
e
c
u
t
a
b
l
e
object
o
b
j
e
c
t
code,
c
o
d
e
,
or
o
r
its
i
t
s
related
r
e
l
a
t
e
d
documentation
d
o
c
u
m
e
n
t
a
t
i
o
n
from
f
r
o
m
its
i
t
s
baseline.
b
a
s
e
l
i
n
e
.
Software
S
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
-
-
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
combining
c
o
m
b
i
n
i
n
g
code
c
o
d
e
components.
c
o
m
p
o
n
e
n
t
s
.
Software
S
o
f
t
w
a
r
e
library
l
i
b
r
a
r
y
-
-
A
A
controlled
c
o
n
t
r
o
l
l
e
d
repository
r
e
p
o
s
i
t
o
r
y
containing
c
o
n
t
a
i
n
i
n
g
a
a
collection
c
o
l
l
e
c
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
and
a
n
d
related
r
e
l
a
t
e
d
data
d
a
t
a
and
a
n
d
documents
d
o
c
u
m
e
n
t
s
designed
d
e
s
i
g
n
e
d
to
t
o
aid
a
i
d
in
i
n
software
s
o
f
t
w
a
r
e
development,
d
e
v
e
l
o
p
m
e
n
t
,
use
u
s
e
or
o
r
modification.
m
o
d
i
f
i
c
a
t
i
o
n
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
library,
l
i
b
r
a
r
y
,
master
m
a
s
t
e
r
library,
l
i
b
r
a
r
y
,
production
p
r
o
d
u
c
t
i
o
n
library,
l
i
b
r
a
r
y
,
program
p
r
o
g
r
a
m
library
l
i
b
r
a
r
y
and
a
n
d
software
s
o
f
t
w
a
r
e
repository.
r
e
p
o
s
i
t
o
r
y
.
Software
S
o
f
t
w
a
r
e
life
l
i
f
e
cycle-
c
y
c
l
e
-
(1)
(
1
)
An
A
n
ordered
o
r
d
e
r
e
d
collection
c
o
l
l
e
c
t
i
o
n
of
o
f
processes
p
r
o
c
e
s
s
e
s
determined
d
e
t
e
r
m
i
n
e
d
by
b
y
an
a
n
organization
o
r
g
a
n
i
z
a
t
i
o
n
to
t
o
be
b
e
sufficient
s
u
f
f
i
c
i
e
n
t
and
a
n
d
adequate
a
d
e
q
u
a
t
e
to
t
o
produce
p
r
o
d
u
c
e
a
a
software
s
o
f
t
w
a
r
e
product.
p
r
o
d
u
c
t
.
(2)
(
2
)
The
T
h
e
period
p
e
r
i
o
d
of
o
f
time
t
i
m
e
that
t
h
a
t
begins
b
e
g
i
n
s
with
w
i
t
h
the
t
h
e
decision
d
e
c
i
s
i
o
n
to
t
o
produce
p
r
o
d
u
c
e
or
o
r
modify
m
o
d
i
f
y
a
a
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
and
a
n
d
ends
e
n
d
s
when
w
h
e
n
the
t
h
e
product
p
r
o
d
u
c
t
is
i
s
retired
r
e
t
i
r
e
d
from
f
r
o
m
service.
s
e
r
v
i
c
e
.
Software
S
o
f
t
w
a
r
e
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
-
-
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
separating,
s
e
p
a
r
a
t
i
n
g
,
usually
u
s
u
a
l
l
y
with
w
i
t
h
the
t
h
e
express
e
x
p
r
e
s
s
purpose
p
u
r
p
o
s
e
of
o
f
isolating
i
s
o
l
a
t
i
n
g
one
o
n
e
or
o
r
more
m
o
r
e
attributes
a
t
t
r
i
b
u
t
e
s
of
o
f
the
t
h
e
software,
s
o
f
t
w
a
r
e
,
to
t
o
prevent
p
r
e
v
e
n
t
specific
s
p
e
c
i
f
i
c
interactions
i
n
t
e
r
a
c
t
i
o
n
s
and
a
n
d
cross-coupling
c
r
o
s
s
-
c
o
u
p
l
i
n
g
interference.
i
n
t
e
r
f
e
r
e
n
c
e
.
Software
S
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
-
-
The
T
h
e
set
s
e
t
of
o
f
computer
c
o
m
p
u
t
e
r
programs,
p
r
o
g
r
a
m
s
,
and
a
n
d
associated
a
s
s
o
c
i
a
t
e
d
documentation
d
o
c
u
m
e
n
t
a
t
i
o
n
and
a
n
d
data,
d
a
t
a
,
designated
d
e
s
i
g
n
a
t
e
d
for
f
o
r
delivery
d
e
l
i
v
e
r
y
to
t
o
a
a
user.
u
s
e
r
.
In
I
n
the
t
h
e
context
c
o
n
t
e
x
t
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
this
t
h
i
s
term
t
e
r
m
refers
r
e
f
e
r
s
to
t
o
software
s
o
f
t
w
a
r
e
intended
i
n
t
e
n
d
e
d
for
f
o
r
use
u
s
e
in
i
n
airborne
a
i
r
b
o
r
n
e
applications
a
p
p
l
i
c
a
t
i
o
n
s
and
a
n
d
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data.
d
a
t
a
.
Software
S
o
f
t
w
a
r
e
requirement
r
e
q
u
i
r
e
m
e
n
t
-
-
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
what
w
h
a
t
is
i
s
to
t
o
be
b
e
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
given
g
i
v
e
n
the
t
h
e
inputs
i
n
p
u
t
s
and
a
n
d
constraints.
c
o
n
s
t
r
a
i
n
t
s
.
Software
S
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
include
i
n
c
l
u
d
e
both
b
o
t
h
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Software
S
o
f
t
w
a
r
e
tool
t
o
o
l
-
-
A
A
computer
c
o
m
p
u
t
e
r
program
p
r
o
g
r
a
m
used
u
s
e
d
to
t
o
help
h
e
l
p
develop,
d
e
v
e
l
o
p
,
test,
t
e
s
t
,
analyze,
a
n
a
l
y
z
e
,
produce
p
r
o
d
u
c
e
or
o
r
modify
m
o
d
i
f
y
another
a
n
o
t
h
e
r
program
p
r
o
g
r
a
m
or
o
r
its
i
t
s
documentation.
d
o
c
u
m
e
n
t
a
t
i
o
n
.
Examples
E
x
a
m
p
l
e
s
are
a
r
e
an
a
n
automated
a
u
t
o
m
a
t
e
d
design
d
e
s
i
g
n
tool,
t
o
o
l
,
a
a
compiler,
c
o
m
p
i
l
e
r
,
test
t
e
s
t
tools
t
o
o
l
s
and
a
n
d
modification
m
o
d
i
f
i
c
a
t
i
o
n
tools.
t
o
o
l
s
.
Source
S
o
u
r
c
e
code
c
o
d
e
-
-
Code
C
o
d
e
written
w
r
i
t
t
e
n
in
i
n
source
s
o
u
r
c
e
languages,
l
a
n
g
u
a
g
e
s
,
such
s
u
c
h
as
a
s
assembly
a
s
s
e
m
b
l
y
language
l
a
n
g
u
a
g
e
and/or
a
n
d
/
o
r
high
h
i
g
h
level
l
e
v
e
l
language,
l
a
n
g
u
a
g
e
,
in
i
n
a
a
machine-readable
m
a
c
h
i
n
e
-
r
e
a
d
a
b
l
e
form
f
o
r
m
for
f
o
r
input
i
n
p
u
t
to
t
o
an
a
n
assembler
a
s
s
e
m
b
l
e
r
or
o
r
a
a
compiler.
c
o
m
p
i
l
e
r
.
Standard
S
t
a
n
d
a
r
d
-
-
A
A
rule
r
u
l
e
or
o
r
basis
b
a
s
i
s
of
o
f
comparison
c
o
m
p
a
r
i
s
o
n
used
u
s
e
d
to
t
o
provide
p
r
o
v
i
d
e
both
b
o
t
h
guidance
g
u
i
d
a
n
c
e
in
i
n
and
a
n
d
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
performance
p
e
r
f
o
r
m
a
n
c
e
of
o
f
a
a
given
g
i
v
e
n
activity
a
c
t
i
v
i
t
y
or
o
r
the
t
h
e
content
c
o
n
t
e
n
t
of
o
f
a
a
specified
s
p
e
c
i
f
i
e
d
data
d
a
t
a
item.
i
t
e
m
.
Statement
S
t
a
t
e
m
e
n
t
coverage
c
o
v
e
r
a
g
e
-
-
Every
E
v
e
r
y
statement
s
t
a
t
e
m
e
n
t
in
i
n
the
t
h
e
program
p
r
o
g
r
a
m
has
h
a
s
been
b
e
e
n
invoked
i
n
v
o
k
e
d
at
a
t
least
l
e
a
s
t
once.
o
n
c
e
.
Static
S
t
a
t
i
c
analyzer
a
n
a
l
y
z
e
r
-
-
A
A
software
s
o
f
t
w
a
r
e
tool
t
o
o
l
that
t
h
a
t
helps
h
e
l
p
s
to
t
o
reveal
r
e
v
e
a
l
certain
c
e
r
t
a
i
n
properties
p
r
o
p
e
r
t
i
e
s
of
o
f
a
a
program
p
r
o
g
r
a
m
without
w
i
t
h
o
u
t
executing
e
x
e
c
u
t
i
n
g
the
t
h
e
program.
p
r
o
g
r
a
m
.
Structure
S
t
r
u
c
t
u
r
e
-
-
A
A
specified
s
p
e
c
i
f
i
e
d
arrangement
a
r
r
a
n
g
e
m
e
n
t
or
o
r
interrelation
i
n
t
e
r
r
e
l
a
t
i
o
n
of
o
f
parts
p
a
r
t
s
to
t
o
form
f
o
r
m
a
a
whole.
w
h
o
l
e
.
System
S
y
s
t
e
m
-
-
A
A
collection
c
o
l
l
e
c
t
i
o
n
of
o
f
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
organized
o
r
g
a
n
i
z
e
d
to
t
o
accomplish
a
c
c
o
m
p
l
i
s
h
a
a
specific
s
p
e
c
i
f
i
c
function
f
u
n
c
t
i
o
n
or
o
r
set
s
e
t
of
o
f
functions.
f
u
n
c
t
i
o
n
s
.
System
S
y
s
t
e
m
architecture
a
r
c
h
i
t
e
c
t
u
r
e
-
-
The
T
h
e
structure
s
t
r
u
c
t
u
r
e
of
o
f
the
t
h
e
hardware
h
a
r
d
w
a
r
e
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
selected
s
e
l
e
c
t
e
d
to
t
o
implement
i
m
p
l
e
m
e
n
t
the
t
h
e
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
System
S
y
s
t
e
m
safely
s
a
f
e
l
y
assessment
a
s
s
e
s
s
m
e
n
t
-
-
An
A
n
ongoing,
o
n
g
o
i
n
g
,
systematic,
s
y
s
t
e
m
a
t
i
c
,
comprehensive
c
o
m
p
r
e
h
e
n
s
i
v
e
evaluation
e
v
a
l
u
a
t
i
o
n
of
o
f
the
t
h
e
proposed
p
r
o
p
o
s
e
d
system
s
y
s
t
e
m
to
t
o
show
s
h
o
w
that
t
h
a
t
relevant
r
e
l
e
v
a
n
t
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
satisfied.
s
a
t
i
s
f
i
e
d
.
System
S
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
-
-
Those
T
h
o
s
e
activities
a
c
t
i
v
i
t
i
e
s
which
w
h
i
c
h
demonstrate
d
e
m
o
n
s
t
r
a
t
e
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
associated
a
s
s
o
c
i
a
t
e
d
guidance
g
u
i
d
a
n
c
e
material,
m
a
t
e
r
i
a
l
,
such
s
u
c
h
as,
a
s
,
JAA
J
A
A
AMJ/FAA
A
M
J
/
F
A
A
AC
A
C
25.1309.,The
2
5
.
1
3
0
9
.
,
T
h
e
major
m
a
j
o
r
activities
a
c
t
i
v
i
t
i
e
s
within
w
i
t
h
i
n
this
t
h
i
s
process
p
r
o
c
e
s
s
include:
i
n
c
l
u
d
e
:
functional
f
u
n
c
t
i
o
n
a
l
hazard
h
a
z
a
r
d
assessment,
a
s
s
e
s
s
m
e
n
t
,
preliminary
p
r
e
l
i
m
i
n
a
r
y
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment,
a
s
s
e
s
s
m
e
n
t
,
and
a
n
d
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment.
a
s
s
e
s
s
m
e
n
t
.
The
T
h
e
rigor
r
i
g
o
r
of
o
f
the
t
h
e
activities
a
c
t
i
v
i
t
i
e
s
will
w
i
l
l
depend
d
e
p
e
n
d
on
o
n
the
t
h
e
criticality,
c
r
i
t
i
c
a
l
i
t
y
,
complexity,
c
o
m
p
l
e
x
i
t
y
,
novelty,
n
o
v
e
l
t
y
,
and
a
n
d
relevant
r
e
l
e
v
a
n
t
service
s
e
r
v
i
c
e
experience
e
x
p
e
r
i
e
n
c
e
of
o
f
the
t
h
e
system
s
y
s
t
e
m
concerned.
c
o
n
c
e
r
n
e
d
.
Task
T
a
s
k
-
-
The
T
h
e
basic
b
a
s
i
c
unit
u
n
i
t
of
o
f
work
w
o
r
k
from
f
r
o
m
the
t
h
e
standpoint
s
t
a
n
d
p
o
i
n
t
of
o
f
a
a
control
c
o
n
t
r
o
l
program.
p
r
o
g
r
a
m
.
Test
T
e
s
t
case
c
a
s
e
-
-
A
A
set
s
e
t
of
o
f
test
t
e
s
t
inputs,
i
n
p
u
t
s
,
execution
e
x
e
c
u
t
i
o
n
conditions,
c
o
n
d
i
t
i
o
n
s
,
and
a
n
d
expected
e
x
p
e
c
t
e
d
results
r
e
s
u
l
t
s
developed
d
e
v
e
l
o
p
e
d
for
f
o
r
a
a
particular
p
a
r
t
i
c
u
l
a
r
objective,
o
b
j
e
c
t
i
v
e
,
such
s
u
c
h
as
a
s
to
t
o
exercise
e
x
e
r
c
i
s
e
a
a
particular
p
a
r
t
i
c
u
l
a
r
program
p
r
o
g
r
a
m
path
p
a
t
h
or
o
r
to
t
o
verify
v
e
r
i
f
y
compliance
c
o
m
p
l
i
a
n
c
e
with
w
i
t
h
a
a
specific
s
p
e
c
i
f
i
c
requirement.
r
e
q
u
i
r
e
m
e
n
t
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
85
8
5
Testing
T
e
s
t
i
n
g
-
-
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
exercising
e
x
e
r
c
i
s
i
n
g
a
a
system
s
y
s
t
e
m
or
o
r
system
s
y
s
t
e
m
component
c
o
m
p
o
n
e
n
t
to
t
o
verify
v
e
r
i
f
y
that
t
h
a
t
it
i
t
satisfies
s
a
t
i
s
f
i
e
s
specified
s
p
e
c
i
f
i
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
to
t
o
detect
d
e
t
e
c
t
errors.
e
r
r
o
r
s
.
Test
T
e
s
t
procedure
p
r
o
c
e
d
u
r
e
-
-
Detailed
D
e
t
a
i
l
e
d
instructions
i
n
s
t
r
u
c
t
i
o
n
s
for
f
o
r
the
t
h
e
set-up
s
e
t
-
u
p
and
a
n
d
execution
e
x
e
c
u
t
i
o
n
of
o
f
a
a
given
g
i
v
e
n
set
s
e
t
of
o
f
test
t
e
s
t
cases,
c
a
s
e
s
,
and
a
n
d
instructions
i
n
s
t
r
u
c
t
i
o
n
s
for
f
o
r
the
t
h
e
evaluation
e
v
a
l
u
a
t
i
o
n
of
o
f
results
r
e
s
u
l
t
s
of
o
f
executing
e
x
e
c
u
t
i
n
g
the
t
h
e
test
t
e
s
t
cases.
c
a
s
e
s
.
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
-
-
The
T
h
e
process
p
r
o
c
e
s
s
necessary
n
e
c
e
s
s
a
r
y
to
t
o
obtain
o
b
t
a
i
n
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
for
f
o
r
a
a
software
s
o
f
t
w
a
r
e
tool
t
o
o
l
within
w
i
t
h
i
n
the
t
h
e
context
c
o
n
t
e
x
t
of
o
f
a
a
specific
s
p
e
c
i
f
i
c
airborne
a
i
r
b
o
r
n
e
system.
s
y
s
t
e
m
.
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
-
-
The
T
h
e
evidence
e
v
i
d
e
n
c
e
of
o
f
an
a
n
association
a
s
s
o
c
i
a
t
i
o
n
between
b
e
t
w
e
e
n
items,
i
t
e
m
s
,
such
s
u
c
h
as
a
s
between
b
e
t
w
e
e
n
process
p
r
o
c
e
s
s
outputs,
o
u
t
p
u
t
s
,
between
b
e
t
w
e
e
n
an
a
n
output
o
u
t
p
u
t
and
a
n
d
its
i
t
s
originating
o
r
i
g
i
n
a
t
i
n
g
process,
p
r
o
c
e
s
s
,
or
o
r
between
b
e
t
w
e
e
n
a
a
requirement
r
e
q
u
i
r
e
m
e
n
t
and
a
n
d
its
i
t
s
implementation.
i
m
p
l
e
m
e
n
t
a
t
i
o
n
.
Transition
T
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
-
-
The
T
h
e
minimum
m
i
n
i
m
u
m
conditions,
c
o
n
d
i
t
i
o
n
s
,
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process,
p
r
o
c
e
s
s
,
to
t
o
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
to
t
o
enter
e
n
t
e
r
a
a
process.
p
r
o
c
e
s
s
.
Validation
V
a
l
i
d
a
t
i
o
n
-The
-
T
h
e
process
p
r
o
c
e
s
s
of
o
f
determining
d
e
t
e
r
m
i
n
i
n
g
that
t
h
a
t
the
t
h
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
are
a
r
e
the
t
h
e
correct
c
o
r
r
e
c
t
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
that
t
h
a
t
they
t
h
e
y
are
a
r
e
complete.
c
o
m
p
l
e
t
e
.
The
T
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
may
m
a
y
use
u
s
e
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
in
i
n
system
s
y
s
t
e
m
validation.
v
a
l
i
d
a
t
i
o
n
.
Verification
V
e
r
i
f
i
c
a
t
i
o
n
-
-
The
T
h
e
evaluation
e
v
a
l
u
a
t
i
o
n
of
o
f
the
t
h
e
results
r
e
s
u
l
t
s
of
o
f
a
a
process
p
r
o
c
e
s
s
to
t
o
ensure
e
n
s
u
r
e
correctness
c
o
r
r
e
c
t
n
e
s
s
and
a
n
d
consistency
c
o
n
s
i
s
t
e
n
c
y
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
the
t
h
e
inputs
i
n
p
u
t
s
and
a
n
d
standards
s
t
a
n
d
a
r
d
s
provided
p
r
o
v
i
d
e
d
to
t
o
that
t
h
a
t
process.
p
r
o
c
e
s
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
APPENDICES
A
P
P
E
N
D
I
C
E
S
APPENDIX
A
P
P
E
N
D
I
X
A
A
BACKGROUND
B
A
C
K
G
R
O
U
N
D
OF
O
F
DOCUMENT
D
O
C
U
M
E
N
T
DO-178
D
O
-
1
7
8
APPENDIX
A
P
P
E
N
D
I
X
B
B
COMMITTEE
C
O
M
M
I
T
T
E
E
MEMBERSHIP
M
E
M
B
E
R
S
H
I
P
APPENDIX
A
P
P
E
N
D
I
X
C
C
INDEX
I
N
D
E
X
OF
O
F
TERMS
T
E
R
M
S
APPENDIX
A
P
P
E
N
D
I
X
D
D
IMPROVEMENT
I
M
P
R
O
V
E
M
E
N
T
SUGGESTION
S
U
G
G
E
S
T
I
O
N
FORM
F
O
R
M
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
APPENDIX
A
P
P
E
N
D
I
X
A
A
BACKGROUND
B
A
C
K
G
R
O
U
N
D
OF
O
F
DOCUMENT
D
O
C
U
M
E
N
T
DO-178
D
O
-
1
7
8
1.0
1
.
0
Prior
P
r
i
o
r
Document
D
o
c
u
m
e
n
t
Version
V
e
r
s
i
o
n
History
H
i
s
t
o
r
y
A-1
A
-
1
In
I
n
May
M
a
y
1980,
1
9
8
0
,
the
t
h
e
Radio
R
a
d
i
o
Technical
T
e
c
h
n
i
c
a
l
Commission
C
o
m
m
i
s
s
i
o
n
for
f
o
r
Aeronautics,
A
e
r
o
n
a
u
t
i
c
s
,
now
n
o
w
RTCA,
R
T
C
A
,
Inc.,
I
n
c
.
,
established
e
s
t
a
b
l
i
s
h
e
d
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
145
1
4
5
(SC-145),
(
S
C
-
1
4
5
)
,
"Digital
"
D
i
g
i
t
a
l
Avionics
A
v
i
o
n
i
c
s
Software",
S
o
f
t
w
a
r
e
"
,
to
t
o
develop
d
e
v
e
l
o
p
and
a
n
d
document
d
o
c
u
m
e
n
t
software
s
o
f
t
w
a
r
e
practices
p
r
a
c
t
i
c
e
s
that
t
h
a
t
would
w
o
u
l
d
support
s
u
p
p
o
r
t
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
software-based
s
o
f
t
w
a
r
e
-
b
a
s
e
d
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment.
e
q
u
i
p
m
e
n
t
.
The
T
h
e
European
E
u
r
o
p
e
a
n
Organisation
O
r
g
a
n
i
s
a
t
i
o
n
for
f
o
r
Civil
C
i
v
i
l
Aviation
A
v
i
a
t
i
o
n
Electronics,
E
l
e
c
t
r
o
n
i
c
s
,
now
n
o
w
the
t
h
e
European
E
u
r
o
p
e
a
n
Organisation
O
r
g
a
n
i
s
a
t
i
o
n
for
f
o
r
Civil
C
i
v
i
l
Aviation
A
v
i
a
t
i
o
n
Equipment
E
q
u
i
p
m
e
n
t
(EUROCAE),
(
E
U
R
O
C
A
E
)
,
had
h
a
d
previously
p
r
e
v
i
o
u
s
l
y
established
e
s
t
a
b
l
i
s
h
e
d
Working
W
o
r
k
i
n
g
Group
G
r
o
u
p
12
1
2
(WG-12)
(
W
G
-
1
2
)
to
t
o
produce
p
r
o
d
u
c
e
a
a
similar
s
i
m
i
l
a
r
document
d
o
c
u
m
e
n
t
and,
a
n
d
,
in
i
n
October
O
c
t
o
b
e
r
1980,
1
9
8
0
,
was
w
a
s
ready
r
e
a
d
y
to
t
o
publish
p
u
b
l
i
s
h
document
d
o
c
u
m
e
n
t
ED
E
D
-35,
-
3
5
,
"Recommendations
"
R
e
c
o
m
m
e
n
d
a
t
i
o
n
s
on
o
n
Software
S
o
f
t
w
a
r
e
Practice
P
r
a
c
t
i
c
e
and
a
n
d
Documentation
D
o
c
u
m
e
n
t
a
t
i
o
n
for
f
o
r
Airborne
A
i
r
b
o
r
n
e
Systems."
S
y
s
t
e
m
s
.
"
EUROCAE
E
U
R
O
C
A
E
elected
e
l
e
c
t
e
d
to
t
o
withhold
w
i
t
h
h
o
l
d
publication
p
u
b
l
i
c
a
t
i
o
n
of
o
f
its
i
t
s
document
d
o
c
u
m
e
n
t
and,
a
n
d
,
instead,
i
n
s
t
e
a
d
,
to
t
o
work
w
o
r
k
in
i
n
concert
c
o
n
c
e
r
t
with
w
i
t
h
RTCA
R
T
C
A
to
t
o
develop
d
e
v
e
l
o
p
a
a
common
c
o
m
m
o
n
set
s
e
t
of
o
f
guidelines.
g
u
i
d
e
l
i
n
e
s
.
SC-145
S
C
-
1
4
5
produced
p
r
o
d
u
c
e
d
RTCA
R
T
C
A
Document
D
o
c
u
m
e
n
t
DO-178,
D
O
-
1
7
8
,
"Software
"
S
o
f
t
w
a
r
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
Airborne
A
i
r
b
o
r
n
e
Systems
S
y
s
t
e
m
s
and
a
n
d
Equipment
E
q
u
i
p
m
e
n
t
Certification",
C
e
r
t
i
f
i
c
a
t
i
o
n
"
,
which
w
h
i
c
h
was
w
a
s
approved
a
p
p
r
o
v
e
d
by
b
y
the
t
h
e
RTCA
R
T
C
A
Executive
E
x
e
c
u
t
i
v
e
Committee
C
o
m
m
i
t
t
e
e
and
a
n
d
published
p
u
b
l
i
s
h
e
d
by
b
y
RTCA
R
T
C
A
in
i
n
January
J
a
n
u
a
r
y
1982.
1
9
8
2
.
EUROCAE
E
U
R
O
C
A
E
published
p
u
b
l
i
s
h
e
d
ED-12
E
D
-
1
2
shortly
s
h
o
r
t
l
y
thereafter.
t
h
e
r
e
a
f
t
e
r
.
Early
E
a
r
l
y
in
i
n
1983
1
9
8
3
the
t
h
e
RTCA
R
T
C
A
Executive
E
x
e
c
u
t
i
v
e
Committee
C
o
m
m
i
t
t
e
e
determined
d
e
t
e
r
m
i
n
e
d
that
t
h
a
t
DO-178
D
O
-
1
7
8
should
s
h
o
u
l
d
be
b
e
revised
r
e
v
i
s
e
d
to
t
o
reflect
r
e
f
l
e
c
t
the
t
h
e
experience
e
x
p
e
r
i
e
n
c
e
gained
g
a
i
n
e
d
in
i
n
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
and
a
n
d
engines
e
n
g
i
n
e
s
containing
c
o
n
t
a
i
n
i
n
g
software
s
o
f
t
w
a
r
e
based
b
a
s
e
d
systems
s
y
s
t
e
m
s
and
a
n
d
equipment.
e
q
u
i
p
m
e
n
t
.
It
I
t
established
e
s
t
a
b
l
i
s
h
e
d
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
152
1
5
2
(SC-152)
(
S
C
-
1
5
2
)
for
f
o
r
this
t
h
i
s
purpose.
p
u
r
p
o
s
e
.
As
A
s
a
a
result
r
e
s
u
l
t
of
o
f
this
t
h
i
s
committee's
c
o
m
m
i
t
t
e
e
'
s
work,
w
o
r
k
,
a
a
revised
r
e
v
i
s
e
d
RTCA
R
T
C
A
document,
d
o
c
u
m
e
n
t
,
DO-178A,
D
O
-
1
7
8
A
,
"Software
"
S
o
f
t
w
a
r
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
Airborne
A
i
r
b
o
r
n
e
Systems
S
y
s
t
e
m
s
and
a
n
d
Equipment
E
q
u
i
p
m
e
n
t
Certification",
C
e
r
t
i
f
i
c
a
t
i
o
n
"
,
was
w
a
s
published
p
u
b
l
i
s
h
e
d
in
i
n
1985.
1
9
8
5
.
Shortly
S
h
o
r
t
l
y
thereafter,
t
h
e
r
e
a
f
t
e
r
,
EUROCAE
E
U
R
O
C
A
E
published
p
u
b
l
i
s
h
e
d
ED-12A,
E
D
-
1
2
A
,
which
w
h
i
c
h
was
w
a
s
identical
i
d
e
n
t
i
c
a
l
in
i
n
technical
t
e
c
h
n
i
c
a
l
content
c
o
n
t
e
n
t
to
t
o
DO-178A.
D
O
-
1
7
8
A
.
2.0
2
.
0
RTCA
R
T
C
A
/
/
EUROCAE
E
U
R
O
C
A
E
Committee
C
o
m
m
i
t
t
e
e
Activities
A
c
t
i
v
i
t
i
e
s
in
i
n
the
t
h
e
Production
P
r
o
d
u
c
t
i
o
n
of
o
f
This
T
h
i
s
Document
D
o
c
u
m
e
n
t
In
I
n
early
e
a
r
l
y
1989,
1
9
8
9
,
the
t
h
e
Federal
F
e
d
e
r
a
l
Aviation
A
v
i
a
t
i
o
n
Administration
A
d
m
i
n
i
s
t
r
a
t
i
o
n
(FAA)
(
F
A
A
)
fo
f
o
rmally
r
m
a
l
l
y
requested
r
e
q
u
e
s
t
e
d
that
t
h
a
t
RTCA
R
T
C
A
establish
e
s
t
a
b
l
i
s
h
a
a
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
for
f
o
r
the
t
h
e
review
r
e
v
i
e
w
and
a
n
d
revision
r
e
v
i
s
i
o
n
of
o
f
DO-178A.
D
O
-
1
7
8
A
.
Since
S
i
n
c
e
its
i
t
s
release
r
e
l
e
a
s
e
in
i
n
1985,
1
9
8
5
,
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
manufacturers,
m
a
n
u
f
a
c
t
u
r
e
r
s
,
the
t
h
e
avionics
a
v
i
o
n
i
c
s
industry
i
n
d
u
s
t
r
y
and
a
n
d
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authorities
a
u
t
h
o
r
i
t
i
e
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
world
w
o
r
l
d
have
h
a
v
e
used
u
s
e
d
DO-178A
D
O
-
1
7
8
A
or
o
r
the
t
h
e
equivalent
e
q
u
i
v
a
l
e
n
t
EUROCAE
E
U
R
O
C
A
E
ED
E
D
-12A
-
1
2
A
as
a
s
the
t
h
e
primary
p
r
i
m
a
r
y
source
s
o
u
r
c
e
of
o
f
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
to
t
o
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
acceptability
a
c
c
e
p
t
a
b
i
l
i
t
y
of
o
f
systems
s
y
s
t
e
m
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
containing
c
o
n
t
a
i
n
i
n
g
software.
s
o
f
t
w
a
r
e
.
However,
H
o
w
e
v
e
r
,
rapid
r
a
p
i
d
advances
a
d
v
a
n
c
e
s
in
i
n
software
s
o
f
t
w
a
r
e
technology,
t
e
c
h
n
o
l
o
g
y
,
which
w
h
i
c
h
were
w
e
r
e
not
n
o
t
envisioned
e
n
v
i
s
i
o
n
e
d
by
b
y
SC-152,
S
C
-
1
5
2
,
and
a
n
d
differing
d
i
f
f
e
r
i
n
g
interpretations
i
n
t
e
r
p
r
e
t
a
t
i
o
n
s
which
w
h
i
c
h
were
w
e
r
e
applied
a
p
p
l
i
e
d
to
t
o
some
s
o
m
e
crucial
c
r
u
c
i
a
l
areas,
a
r
e
a
s
,
indicated
i
n
d
i
c
a
t
e
d
that
t
h
a
t
the
t
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
required
r
e
q
u
i
r
e
d
revision.
r
e
v
i
s
i
o
n
.
Accordingly,
A
c
c
o
r
d
i
n
g
l
y
,
an
a
n
RTCA
R
T
C
A
ad
a
d
hoc
h
o
c
group
g
r
o
u
p
was
w
a
s
formed
f
o
r
m
e
d
with
w
i
t
h
representatives
r
e
p
r
e
s
e
n
t
a
t
i
v
e
s
from
f
r
o
m
ARINC,
A
R
I
N
C
,
the
t
h
e
Airline
A
i
r
l
i
n
e
Pilots
P
i
l
o
t
s
Association,
A
s
s
o
c
i
a
t
i
o
n
,
the
t
h
e
National
N
a
t
i
o
n
a
l
Business
B
u
s
i
n
e
s
s
Aircraft
A
i
r
c
r
a
f
t
Association,
A
s
s
o
c
i
a
t
i
o
n
,
the
t
h
e
Air
A
i
r
Transport
T
r
a
n
s
p
o
r
t
Association
A
s
s
o
c
i
a
t
i
o
n
and
a
n
d
the
t
h
e
FAA
F
A
A
to
t
o
consider
c
o
n
s
i
d
e
r
the
t
h
e
FAA
F
A
A
request.
r
e
q
u
e
s
t
.
The
T
h
e
group
g
r
o
u
p
reviewed
r
e
v
i
e
w
e
d
the
t
h
e
issues
i
s
s
u
e
s
and
a
n
d
experience
e
x
p
e
r
i
e
n
c
e
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
e
application
a
p
p
l
i
c
a
t
i
o
n
of
o
f
DO-178A
D
O
-
1
7
8
A
and
a
n
d
concluded
c
o
n
c
l
u
d
e
d
that
t
h
a
t
a
a
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
should
s
h
o
u
l
d
be
b
e
authorized
a
u
t
h
o
r
i
z
e
d
to
t
o
revise
r
e
v
i
s
e
DO-178A.
D
O
-
1
7
8
A
.
The
T
h
e
RTCA
R
T
C
A
Executive
E
x
e
c
u
t
i
v
e
Committee
C
o
m
m
i
t
t
e
e
established
e
s
t
a
b
l
i
s
h
e
d
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
167
1
6
7
(SC-
(
S
C
-
167)
1
6
7
)
during
d
u
r
i
n
g
the
t
h
e
autumn
a
u
t
u
m
n
of
o
f
1989
1
9
8
9
to
t
o
accomplish
a
c
c
o
m
p
l
i
s
h
this
t
h
i
s
task,
t
a
s
k
,
and
a
n
d
agreed
a
g
r
e
e
d
to
t
o
these
t
h
e
s
e
Terms
T
e
r
m
s
of
o
f
Reference:
R
e
f
e
r
e
n
c
e
:
"Special
"
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
167
1
6
7
shall
s
h
a
l
l
review
r
e
v
i
e
w
and
a
n
d
revise,
r
e
v
i
s
e
,
as
a
s
necessary,
n
e
c
e
s
s
a
r
y
,
RTCA
R
T
C
A
Document
D
o
c
u
m
e
n
t
DO-178A,
D
O
-
1
7
8
A
,
"Software
"
S
o
f
t
w
a
r
e
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
Airborne
A
i
r
b
o
r
n
e
Systems
S
y
s
t
e
m
s
and
a
n
d
Equipment
E
q
u
i
p
m
e
n
t
Certification."
C
e
r
t
i
f
i
c
a
t
i
o
n
.
"
GUIDANCE:
G
U
I
D
A
N
C
E
:
SC-167
S
C
-
1
6
7
should
s
h
o
u
l
d
recognize
r
e
c
o
g
n
i
z
e
the
t
h
e
dynamic,
d
y
n
a
m
i
c
,
evolving
e
v
o
l
v
i
n
g
environment
e
n
v
i
r
o
n
m
e
n
t
for
f
o
r
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
design,
d
e
s
i
g
n
,
code
c
o
d
e
generation,
g
e
n
e
r
a
t
i
o
n
,
testing
t
e
s
t
i
n
g
and
a
n
d
documentation;
d
o
c
u
m
e
n
t
a
t
i
o
n
;
and
a
n
d
formulate
f
o
r
m
u
l
a
t
e
a
a
revised
r
e
v
i
s
e
d
document
d
o
c
u
m
e
n
t
that
t
h
a
t
can
c
a
n
accommodate
a
c
c
o
m
m
o
d
a
t
e
this
t
h
i
s
environment
e
n
v
i
r
o
n
m
e
n
t
while
w
h
i
l
e
recommending
r
e
c
o
m
m
e
n
d
i
n
g
suitably
s
u
i
t
a
b
l
y
rigorous
r
i
g
o
r
o
u
s
techniques.
t
e
c
h
n
i
q
u
e
s
.
SC-167
S
C
-
1
6
7
should
s
h
o
u
l
d
also
a
l
s
o
recognize
r
e
c
o
g
n
i
z
e
the
t
h
e
international
i
n
t
e
r
n
a
t
i
o
n
a
l
implications
i
m
p
l
i
c
a
t
i
o
n
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
and,
a
n
d
,
therefore,
t
h
e
r
e
f
o
r
e
,
should
s
h
o
u
l
d
establish
e
s
t
a
b
l
i
s
h
a
a
close
c
l
o
s
e
working
w
o
r
k
i
n
g
relationship
r
e
l
a
t
i
o
n
s
h
i
p
with
w
i
t
h
EUROCAE,
E
U
R
O
C
A
E
,
which
w
h
i
c
h
has
h
a
s
become
b
e
c
o
m
e
the
t
h
e
normal
n
o
r
m
a
l
practice
p
r
a
c
t
i
c
e
in
i
n
RTCA
R
T
C
A
committees.
c
o
m
m
i
t
t
e
e
s
.
To
T
o
accomplish
a
c
c
o
m
p
l
i
s
h
this
t
h
i
s
revision,
r
e
v
i
s
i
o
n
,
the
t
h
e
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
should
s
h
o
u
l
d
consider
c
o
n
s
i
d
e
r
the
t
h
e
experience
e
x
p
e
r
i
e
n
c
e
gained
g
a
i
n
e
d
through
t
h
r
o
u
g
h
the
t
h
e
field
f
i
e
l
d
application
a
p
p
l
i
c
a
t
i
o
n
of
o
f
the
t
h
e
guidance
g
u
i
d
a
n
c
e
material
m
a
t
e
r
i
a
l
contained
c
o
n
t
a
i
n
e
d
in
i
n
DO-178
D
O
-
1
7
8
and
a
n
d
DO-178A,
D
O
-
1
7
8
A
,
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
A-2
A
-
2
as
a
s
well
w
e
l
l
as
a
s
the
t
h
e
as
a
s
results
r
e
s
u
l
t
s
of
o
f
recent
r
e
c
e
n
t
research
r
e
s
e
a
r
c
h
in
i
n
software
s
o
f
t
w
a
r
e
engineering.
e
n
g
i
n
e
e
r
i
n
g
.
The
T
h
e
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
should
s
h
o
u
l
d
focus
f
o
c
u
s
this
t
h
i
s
review
r
e
v
i
e
w
to
t
o
address
a
d
d
r
e
s
s
these
t
h
e
s
e
areas:
a
r
e
a
s
:
-
Examine
E
x
a
m
i
n
e
existing
e
x
i
s
t
i
n
g
industry
i
n
d
u
s
t
r
y
and
a
n
d
government
g
o
v
e
r
n
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
and
a
n
d
consider
c
o
n
s
i
d
e
r
for
f
o
r
possible
p
o
s
s
i
b
l
e
adaptation
a
d
a
p
t
a
t
i
o
n
or
o
r
reference,
r
e
f
e
r
e
n
c
e
,
where
w
h
e
r
e
relevant.
r
e
l
e
v
a
n
t
.
2
2
Assess
A
s
s
e
s
s
the
t
h
e
adequacy
a
d
e
q
u
a
c
y
of
o
f
existing
e
x
i
s
t
i
n
g
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
and
a
n
d
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
nature
n
a
t
u
r
e
and
a
n
d
degree
d
e
g
r
e
e
of
o
f
analysis,
a
n
a
l
y
s
i
s
,
verification,
v
e
r
i
f
i
c
a
t
i
o
n
,
test
t
e
s
t
and
a
n
d
assurance
a
s
s
u
r
a
n
c
e
activities.
a
c
t
i
v
i
t
i
e
s
.
The
T
h
e
revised
r
e
v
i
s
e
d
process
p
r
o
c
e
s
s
criteria
c
r
i
t
e
r
i
a
should
s
h
o
u
l
d
be
b
e
structured
s
t
r
u
c
t
u
r
e
d
to
t
o
support
s
u
p
p
o
r
t
objective
o
b
j
e
c
t
i
v
e
compliance
c
o
m
p
l
i
a
n
c
e
demonstration.
d
e
m
o
n
s
t
r
a
t
i
o
n
.
3.
3
.
Examine
E
x
a
m
i
n
e
the
t
h
e
criteria
c
r
i
t
e
r
i
a
for
f
o
r
tools
t
o
o
l
s
to
t
o
be
b
e
used
u
s
e
d
for
f
o
r
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit,
c
r
e
d
i
t
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
tools
t
o
o
l
s
for
f
o
r
software
s
o
f
t
w
a
r
e
development,
d
e
v
e
l
o
p
m
e
n
t
,
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
and
a
n
d
software
s
o
f
t
w
a
r
e
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
4.
4
.
Examine
E
x
a
m
i
n
e
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
software,
s
o
f
t
w
a
r
e
,
databases
d
a
t
a
b
a
s
e
s
and
a
n
d
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
for
f
o
r
the
t
h
e
system
s
y
s
t
e
m
to
t
o
be
b
e
certified.
c
e
r
t
i
f
i
e
d
.
5.
5
.
Examine
E
x
a
m
i
n
e
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
criteria
c
r
i
t
e
r
i
a
for
f
o
r
architectural
a
r
c
h
i
t
e
c
t
u
r
a
l
and
a
n
d
methodical
m
e
t
h
o
d
i
c
a
l
strategies
s
t
r
a
t
e
g
i
e
s
used
u
s
e
d
to
t
o
reduce
r
e
d
u
c
e
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
or
o
r
to
t
o
provide
p
r
o
v
i
d
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
coverage,
c
o
v
e
r
a
g
e
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
and
a
n
d
dissimilar
d
i
s
s
i
m
i
l
a
r
software.
s
o
f
t
w
a
r
e
.
6.
6
.
Examine
E
x
a
m
i
n
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
control
c
o
n
t
r
o
l
guidelines,
g
u
i
d
e
l
i
n
e
s
,
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
guidelines
g
u
i
d
e
l
i
n
e
s
and
a
n
d
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
conventions;
c
o
n
v
e
n
t
i
o
n
s
;
and
a
n
d
their
t
h
e
i
r
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
existing
e
x
i
s
t
i
n
g
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
requirements
r
e
q
u
i
r
e
m
e
n
t
s
for
f
o
r
type
t
y
p
e
certification,
c
e
r
t
i
f
i
c
a
t
i
o
n
,
in-service
i
n
-
s
e
r
v
i
c
e
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
approval.
a
p
p
r
o
v
a
l
.
7.
7
.
Consider
C
o
n
s
i
d
e
r
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
new
n
e
w
technology,
t
e
c
h
n
o
l
o
g
y
,
such
s
u
c
h
as,
a
s
,
modular
m
o
d
u
l
a
r
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
data
d
a
t
a
loading,
l
o
a
d
i
n
g
,
packaging,
p
a
c
k
a
g
i
n
g
,
and
a
n
d
memory
m
e
m
o
r
y
technology.
t
e
c
h
n
o
l
o
g
y
.
8.
8
.
Examine
E
x
a
m
i
n
e
the
t
h
e
need,
n
e
e
d
,
content
c
o
n
t
e
n
t
and
a
n
d
delivery
d
e
l
i
v
e
r
y
requirements
r
e
q
u
i
r
e
m
e
n
t
s
of
o
f
all
a
l
l
documents,
d
o
c
u
m
e
n
t
s
,
with
w
i
t
h
special
s
p
e
c
i
a
l
emphasis
e
m
p
h
a
s
i
s
on
o
n
the
t
h
e
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary.
S
u
m
m
a
r
y
.
9.
9
.
Define
D
e
f
i
n
e
and
a
n
d
consider
c
o
n
s
i
d
e
r
the
t
h
e
interfaces
i
n
t
e
r
f
a
c
e
s
between
b
e
t
w
e
e
n
the
t
h
e
software
s
o
f
t
w
a
r
e
and
a
n
d
system
s
y
s
t
e
m
life
l
i
f
e
cycles.
c
y
c
l
e
s
.
10.
1
0
.
Review
R
e
v
i
e
w
the
t
h
e
criteria
c
r
i
t
e
r
i
a
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
making
m
a
k
i
n
g
pre-
p
r
e
-
and
a
n
d
post-certification
p
o
s
t
-
c
e
r
t
i
f
i
c
a
t
i
o
n
changes
c
h
a
n
g
e
s
to
t
o
a
a
system.
s
y
s
t
e
m
.
11.
1
1
.
Consider
C
o
n
s
i
d
e
r
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
evolutionary
e
v
o
l
u
t
i
o
n
a
r
y
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
other
o
t
h
e
r
alternative
a
l
t
e
r
n
a
t
i
v
e
life
l
i
f
e
cycles
c
y
c
l
e
s
to
t
o
the
t
h
e
model
m
o
d
e
l
implied
i
m
p
l
i
e
d
by
b
y
DO-178A.
D
O
-
1
7
8
A
.
EUROCAE
E
U
R
O
C
A
E
WG-12
W
G
-
1
2
was
w
a
s
re-established
r
e
-
e
s
t
a
b
l
i
s
h
e
d
to
t
o
work
w
o
r
k
with
w
i
t
h
SC-167
S
C
-
1
6
7
and,
a
n
d
,
to
t
o
accomplish
a
c
c
o
m
p
l
i
s
h
the
t
h
e
task,
t
a
s
k
,
five
f
i
v
e
joint
j
o
i
n
t
RTCA/EUROCAE
R
T
C
A
/
E
U
R
O
C
A
E
working
w
o
r
k
i
n
g
groups
g
r
o
u
p
s
were
w
e
r
e
formed
f
o
r
m
e
d
to
t
o
address
a
d
d
r
e
s
s
these
t
h
e
s
e
topics:
t
o
p
i
c
s
:
-
Documentation
D
o
c
u
m
e
n
t
a
t
i
o
n
Integration
I
n
t
e
g
r
a
t
i
o
n
and
a
n
d
Production.
P
r
o
d
u
c
t
i
o
n
.
-
System
S
y
s
t
e
m
Issues.
I
s
s
u
e
s
.
-
Software
S
o
f
t
w
a
r
e
Development.
D
e
v
e
l
o
p
m
e
n
t
.
-
Software
S
o
f
t
w
a
r
e
Verification.
V
e
r
i
f
i
c
a
t
i
o
n
.
-
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
and
a
n
d
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance.
A
s
s
u
r
a
n
c
e
.
The
T
h
e
cooperative
c
o
o
p
e
r
a
t
i
v
e
efforts
e
f
f
o
r
t
s
of
o
f
SC-167
S
C
-
1
6
7
and
a
n
d
WG-12
W
G
-
1
2
culminated
c
u
l
m
i
n
a
t
e
d
in
i
n
the
t
h
e
publication
p
u
b
l
i
c
a
t
i
o
n
of
o
f
RTCA
R
T
C
A
document
d
o
c
u
m
e
n
t
DO-178B
D
O
-
1
7
8
B
and
a
n
d
EUROCAE
E
U
R
O
C
A
E
document
d
o
c
u
m
e
n
t
ED-12B.
E
D
-
1
2
B
.
3.0
3
.
0
Summary
S
u
m
m
a
r
y
Of
O
f
Differences
D
i
f
f
e
r
e
n
c
e
s
between
b
e
t
w
e
e
n
DO-178B
D
O
-
1
7
8
B
and
a
n
d
DO-178A
D
O
-
1
7
8
A
This
T
h
i
s
is
i
s
a
a
complete
c
o
m
p
l
e
t
e
rewrite
r
e
w
r
i
t
e
of
o
f
DO-178A.
D
O
-
1
7
8
A
.
It
I
t
is
i
s
suggested
s
u
g
g
e
s
t
e
d
that
t
h
a
t
the
t
h
e
entire
e
n
t
i
r
e
document
d
o
c
u
m
e
n
t
be
b
e
read
r
e
a
d
before
b
e
f
o
r
e
using
u
s
i
n
g
any
a
n
y
of
o
f
the
t
h
e
sections
s
e
c
t
i
o
n
s
or
o
r
tables
t
a
b
l
e
s
in
i
n
isolation.
i
s
o
l
a
t
i
o
n
.
DO-178B
D
O
-
1
7
8
B
is
i
s
primarily
p
r
i
m
a
r
i
l
y
a
a
process-oriented
p
r
o
c
e
s
s
-
o
r
i
e
n
t
e
d
document.
d
o
c
u
m
e
n
t
.
For
F
o
r
each
e
a
c
h
process,
p
r
o
c
e
s
s
,
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
defined
d
e
f
i
n
e
d
and
a
n
d
a
a
means
m
e
a
n
s
of
o
f
satisfying
s
a
t
i
s
f
y
i
n
g
these
t
h
e
s
e
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
described.
d
e
s
c
r
i
b
e
d
.
A
A
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
which
w
h
i
c
h
shows
s
h
o
w
s
that
t
h
a
t
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
have
h
a
v
e
been
b
e
e
n
satisfied
s
a
t
i
s
f
i
e
d
is
i
s
provided.
p
r
o
v
i
d
e
d
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
each
e
a
c
h
process
p
r
o
c
e
s
s
are
a
r
e
summarized
s
u
m
m
a
r
i
z
e
d
in
i
n
tables
t
a
b
l
e
s
and
a
n
d
the
t
h
e
effect
e
f
f
e
c
t
of
o
f
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
on
o
n
the
t
h
e
applicability
a
p
p
l
i
c
a
b
i
l
i
t
y
and
a
n
d
independence
i
n
d
e
p
e
n
d
e
n
c
e
of
o
f
these
t
h
e
s
e
objectives
o
b
j
e
c
t
i
v
e
s
is
i
s
specified
s
p
e
c
i
f
i
e
d
in
i
n
the
t
h
e
tables.
t
a
b
l
e
s
.
The
T
h
e
variation
v
a
r
i
a
t
i
o
n
by
b
y
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
in
i
n
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
rigor
r
i
g
o
r
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
is
i
s
also
a
l
s
o
in
i
n
the
t
h
e
tables.
t
a
b
l
e
s
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
A-3
A
-
3
DO-178B
D
O
-
1
7
8
B
recognizes
r
e
c
o
g
n
i
z
e
s
that
t
h
a
t
many
m
a
n
y
different
d
i
f
f
e
r
e
n
t
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycles
c
y
c
l
e
s
are
a
r
e
acceptable
a
c
c
e
p
t
a
b
l
e
for
f
o
r
developing
d
e
v
e
l
o
p
i
n
g
software
s
o
f
t
w
a
r
e
for
f
o
r
airborne
a
i
r
b
o
r
n
e
systems
s
y
s
t
e
m
s
and
a
n
d
equipment.
e
q
u
i
p
m
e
n
t
.
DO-178B
D
O
-
1
7
8
B
emphasizes
e
m
p
h
a
s
i
z
e
s
that
t
h
a
t
the
t
h
e
chosen
c
h
o
s
e
n
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle(s)
c
y
c
l
e
(
s
)
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
during
d
u
r
i
n
g
the
t
h
e
planning
p
l
a
n
n
i
n
g
for
f
o
r
a
a
project.
p
r
o
j
e
c
t
.
The
T
h
e
processes
p
r
o
c
e
s
s
e
s
which
w
h
i
c
h
comprise
c
o
m
p
r
i
s
e
a
a
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
project,
p
r
o
j
e
c
t
,
no
n
o
matter
m
a
t
t
e
r
which
w
h
i
c
h
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
was
w
a
s
chosen,
c
h
o
s
e
n
,
are
a
r
e
described.
d
e
s
c
r
i
b
e
d
.
These
T
h
e
s
e
processes
p
r
o
c
e
s
s
e
s
fall
f
a
l
l
into
i
n
t
o
three
t
h
r
e
e
categories:
c
a
t
e
g
o
r
i
e
s
:
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process,
p
r
o
c
e
s
s
,
the
t
h
e
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes,
p
r
o
c
e
s
s
e
s
,
which
w
h
i
c
h
include
i
n
c
l
u
d
e
software
s
o
f
t
w
a
r
e
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
software
s
o
f
t
w
a
r
e
design,
d
e
s
i
g
n
,
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
and
a
n
d
integration;
i
n
t
e
g
r
a
t
i
o
n
;
and
a
n
d
the
t
h
e
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
which
w
h
i
c
h
include
i
n
c
l
u
d
e
software
s
o
f
t
w
a
r
e
verification,
v
e
r
i
f
i
c
a
t
i
o
n
,
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance,
a
s
s
u
r
a
n
c
e
,
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
and
a
n
d
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison.
l
i
a
i
s
o
n
.
Integral
I
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
active
a
c
t
i
v
e
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle.
c
y
c
l
e
.
DO-178B
D
O
-
1
7
8
B
requires
r
e
q
u
i
r
e
s
that
t
h
a
t
criteria
c
r
i
t
e
r
i
a
which
w
h
i
c
h
control
c
o
n
t
r
o
l
the
t
h
e
transitions
t
r
a
n
s
i
t
i
o
n
s
between
b
e
t
w
e
e
n
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
should
s
h
o
u
l
d
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
during
d
u
r
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
The
T
h
e
relationship
r
e
l
a
t
i
o
n
s
h
i
p
between
b
e
t
w
e
e
n
the
t
h
e
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
is
i
s
further
f
u
r
t
h
e
r
defined.
d
e
f
i
n
e
d
.
Failure
F
a
i
l
u
r
e
conditions
c
o
n
d
i
t
i
o
n
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
functions
f
u
n
c
t
i
o
n
s
which
w
h
i
c
h
are
a
r
e
to
t
o
be
b
e
implemented
i
m
p
l
e
m
e
n
t
e
d
in
i
n
software
s
o
f
t
w
a
r
e
need
n
e
e
d
to
t
o
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
during
d
u
r
i
n
g
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process.
p
r
o
c
e
s
s
.
This
T
h
i
s
is
i
s
the
t
h
e
basis
b
a
s
i
s
for
f
o
r
establishing
e
s
t
a
b
l
i
s
h
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
The
T
h
e
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
are
a
r
e
now
n
o
w
Level
L
e
v
e
l
A,
A
,
Level
L
e
v
e
l
B,
B
,
Level
L
e
v
e
l
C,
C
,
Level
L
e
v
e
l
D,
D
,
and
a
n
d
Level
L
e
v
e
l
E.
E
.
The
T
h
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
section
s
e
c
t
i
o
n
emphasizes
e
m
p
h
a
s
i
z
e
s
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
testing,
t
e
s
t
i
n
g
,
which
w
h
i
c
h
is
i
s
supplemented
s
u
p
p
l
e
m
e
n
t
e
d
with
w
i
t
h
structural
s
t
r
u
c
t
u
r
a
l
coverage.
c
o
v
e
r
a
g
e
.
The
T
h
e
items
i
t
e
m
s
that
t
h
a
t
are
a
r
e
to
t
o
be
b
e
delivered
d
e
l
i
v
e
r
e
d
and
a
n
d
other
o
t
h
e
r
data
d
a
t
a
items
i
t
e
m
s
are
a
r
e
further
f
u
r
t
h
e
r
defined,
d
e
f
i
n
e
d
,
as
a
s
well
w
e
l
l
as
a
s
the
t
h
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
required.
r
e
q
u
i
r
e
d
.
A
A
section
s
e
c
t
i
o
n
covering
c
o
v
e
r
i
n
g
additional
a
d
d
i
t
i
o
n
a
l
topics
t
o
p
i
c
s
has
h
a
s
been
b
e
e
n
added
a
d
d
e
d
to
t
o
provide
p
r
o
v
i
d
e
guidance
g
u
i
d
a
n
c
e
in
i
n
areas
a
r
e
a
s
previously
p
r
e
v
i
o
u
s
l
y
not
n
o
t
addressed
a
d
d
r
e
s
s
e
d
in
i
n
DO-178A.
D
O
-
1
7
8
A
.
These
T
h
e
s
e
topics
t
o
p
i
c
s
include
i
n
c
l
u
d
e
the
t
h
e
use
u
s
e
of
o
f
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software,
s
o
f
t
w
a
r
e
,
tool
t
o
o
l
qualification,
q
u
a
l
i
f
i
c
a
t
i
o
n
,
and
a
n
d
the
t
h
e
use
u
s
e
of
o
f
alternative
a
l
t
e
r
n
a
t
i
v
e
methods,
m
e
t
h
o
d
s
,
including
i
n
c
l
u
d
i
n
g
formal
f
o
r
m
a
l
methods,
m
e
t
h
o
d
s
,
exhaustive
e
x
h
a
u
s
t
i
v
e
input
i
n
p
u
t
testing,
t
e
s
t
i
n
g
,
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
verification,
v
e
r
i
f
i
c
a
t
i
o
n
,
software
s
o
f
t
w
a
r
e
reliability
r
e
l
i
a
b
i
l
i
t
y
models,
m
o
d
e
l
s
,
and
a
n
d
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
The
T
h
e
glossary
g
l
o
s
s
a
r
y
of
o
f
terms
t
e
r
m
s
has
h
a
s
been
b
e
e
n
reviewed
r
e
v
i
e
w
e
d
for
f
o
r
redundant
r
e
d
u
n
d
a
n
t
or
o
r
conflicting
c
o
n
f
l
i
c
t
i
n
g
terminology
t
e
r
m
i
n
o
l
o
g
y
and,
a
n
d
,
where
w
h
e
r
e
possible,
p
o
s
s
i
b
l
e
,
industry-accepted
i
n
d
u
s
t
r
y
-
a
c
c
e
p
t
e
d
definitions
d
e
f
i
n
i
t
i
o
n
s
adopted.
a
d
o
p
t
e
d
.
The
T
h
e
guidelines
g
u
i
d
e
l
i
n
e
s
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
were
w
e
r
e
compared
c
o
m
p
a
r
e
d
with
w
i
t
h
international
i
n
t
e
r
n
a
t
i
o
n
a
l
standards:
s
t
a
n
d
a
r
d
s
:
ISO
I
S
O
9000-3
9
0
0
0
-
3
(1991),
(
1
9
9
1
)
,
"Guidelines
"
G
u
i
d
e
l
i
n
e
s
for
f
o
r
the
t
h
e
Application
A
p
p
l
i
c
a
t
i
o
n
of
o
f
ISO
I
S
O
9001
9
0
0
1
to
t
o
the
t
h
e
Development,
D
e
v
e
l
o
p
m
e
n
t
,
Supply
S
u
p
p
l
y
and
a
n
d
Maintenance
M
a
i
n
t
e
n
a
n
c
e
of
o
f
Software,"
S
o
f
t
w
a
r
e
,
"
and
a
n
d
IEC
I
E
C
65A
6
5
A
(Secretariat)122
(
S
e
c
r
e
t
a
r
i
a
t
)
1
2
2
(Draft
(
D
r
a
f
t
-
-
November
N
o
v
e
m
b
e
r
1991),
1
9
9
1
)
,
"Software
"
S
o
f
t
w
a
r
e
for
f
o
r
Computers
C
o
m
p
u
t
e
r
s
in
i
n
the
t
h
e
Application
A
p
p
l
i
c
a
t
i
o
n
of
o
f
Industrial
I
n
d
u
s
t
r
i
a
l
Safety-Related
S
a
f
e
t
y
-
R
e
l
a
t
e
d
Systems."
S
y
s
t
e
m
s
.
"
These
T
h
e
s
e
guidelines
g
u
i
d
e
l
i
n
e
s
are
a
r
e
considered
c
o
n
s
i
d
e
r
e
d
to
t
o
generally
g
e
n
e
r
a
l
l
y
satisfy
s
a
t
i
s
f
y
the
t
h
e
intent
i
n
t
e
n
t
of
o
f
those
t
h
o
s
e
standards.
s
t
a
n
d
a
r
d
s
.
A
A
comprehensive
c
o
m
p
r
e
h
e
n
s
i
v
e
index
i
n
d
e
x
is
i
s
provided
p
r
o
v
i
d
e
d
to
t
o
assist
a
s
s
i
s
t
in
i
n
the
t
h
e
application
a
p
p
l
i
c
a
t
i
o
n
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
APPENDIX
A
P
P
E
N
D
I
X
B
B
B-1
B
-
1
COMMITTEE
C
O
M
M
I
T
T
E
E
MEMBERSHIP
M
E
M
B
E
R
S
H
I
P
Chairmen:
C
h
a
i
r
m
e
n
:
RTCA
R
T
C
A
SC-167:
S
C
-
1
6
7
:
Roger
R
o
g
e
r
A.
A
.
Seeman
S
e
e
m
a
n
Boeing
B
o
e
i
n
g
EUROCAE
E
U
R
O
C
A
E
WG-12
W
G
-
1
2
Daniel
D
a
n
i
e
l
J.
J
.
Hawkes
H
a
w
k
e
s
UK
U
K
CAA
C
A
A
Secretaries:
S
e
c
r
e
t
a
r
i
e
s
:
RTCA
R
T
C
A
SC-167:
S
C
-
1
6
7
:
Michael
M
i
c
h
a
e
l
DeWalt
D
e
W
a
l
t
FAA
F
A
A
EUROCAE
E
U
R
O
C
A
E
WG-12
W
G
-
1
2
Jean-Michel
J
e
a
n
-
M
i
c
h
e
l
Nogué
N
o
g
u
é
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Working/Sub-Group
W
o
r
k
i
n
g
/
S
u
b
-
G
r
o
u
p
Chairmen/Secretaries:
C
h
a
i
r
m
e
n
/
S
e
c
r
e
t
a
r
i
e
s
:
Group
G
r
o
u
p
1
1
Group
G
r
o
u
p
4
4
B.
B
.
Pflug
P
f
l
u
g
Boeing
B
o
e
i
n
g
J.
J
.
Angerinayer
A
n
g
e
r
i
n
a
y
e
r
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
ATAD
A
T
A
D
J-M.
J
-
M
.
Astruc
A
s
t
r
u
c
Veridatas
V
e
r
i
d
a
t
a
s
Group
G
r
o
u
p
2
2
G.
G
.
Finelli
F
i
n
e
l
l
i
NASA
N
A
S
A
D.
D
.
Allen
A
l
l
e
n
Boeing
B
o
e
i
n
g
J.
J
.
Williams
W
i
l
l
i
a
m
s
FAA
F
A
A
M.
M
.
DeWalt
D
e
W
a
l
t
FAA
F
A
A
J-M.
J
-
M
.
Nogué
N
o
g
u
é
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Group
G
r
o
u
p
5
5
Group
G
r
o
u
p
3
3
T.
T
.
Drake
D
r
a
k
e
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
J.
J
.
Krodel
K
r
o
d
e
l
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
R.
R
.
Hannan
H
a
n
n
a
n
Smiths
S
m
i
t
h
s
Industries
I
n
d
u
s
t
r
i
e
s
N.
N
.
Smith
S
m
i
t
h
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
M.
M
.
Kress
K
r
e
s
s
Boeing
B
o
e
i
n
g
Editorial
E
d
i
t
o
r
i
a
l
Group:
G
r
o
u
p
:
-
Coupier
C
o
u
p
i
e
r
CEAT
C
E
A
T
B.
B
.
Pflug
P
f
l
u
g
Boeing
B
o
e
i
n
g
R.
R
.
Hannan
H
a
n
n
a
n
Smiths
S
m
i
t
h
s
Industries
I
n
d
u
s
t
r
i
e
s
C.
C
.
Secher
S
e
c
h
e
r
DGAC
D
G
A
C
France
F
r
a
n
c
e
E.
E
.
Kosowski
K
o
s
o
w
s
k
i
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
N.
N
.
Smith
S
m
i
t
h
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
T.
T
.
Kraft
K
r
a
f
t
FAA
F
A
A
J.
J
.
Stesney
S
t
e
s
n
e
y
Litton
L
i
t
t
o
n
Aero
A
e
r
o
F.
F
.
Moyer
M
o
y
e
r
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
W.
W
.
Struck
S
t
r
u
c
k
Boeing
B
o
e
i
n
g
J-M.
J
-
M
.
Nogué
N
o
g
u
é
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
L.
L
.
Tripp
T
r
i
p
p
Boeing
B
o
e
i
n
g
K.
K
.
Peterson
P
e
t
e
r
s
o
n
Honeywell
H
o
n
e
y
w
e
l
l
B.
B
.
Weiser
W
e
i
s
e
r
Honeywell
H
o
n
e
y
w
e
l
l
Federal
F
e
d
e
r
a
l
Aviation
A
v
i
a
t
i
o
n
Administration
A
d
m
i
n
i
s
t
r
a
t
i
o
n
Representative:
R
e
p
r
e
s
e
n
t
a
t
i
v
e
:
G.
G
.
McIntyre
M
c
I
n
t
y
r
e
FAA
F
A
A
Research
R
e
s
e
a
r
c
h
and
a
n
d
Development
D
e
v
e
l
o
p
m
e
n
t
RTCA
R
T
C
A
Representatives
R
e
p
r
e
s
e
n
t
a
t
i
v
e
s
EUROCAE
E
U
R
O
C
A
E
Representative:
R
e
p
r
e
s
e
n
t
a
t
i
v
e
:
J.
J
.
Lohr
L
o
h
r
B.
B
.
Perret
P
e
r
r
e
t
D.
D
.
Watrous
W
a
t
r
o
u
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
B-2
B
-
2
MEMBERS
M
E
M
B
E
R
S
Allen,
A
l
l
e
n
,
D.
D
.
Boeing
B
o
e
i
n
g
Cucchiara,
C
u
c
c
h
i
a
r
a
,
P.
P
.
Kollsman
K
o
l
l
s
m
a
n
Ammann,
A
m
m
a
n
n
,
P.
P
.
George
G
e
o
r
g
e
Mason
M
a
s
o
n
University
U
n
i
v
e
r
s
i
t
y
Davidson,
D
a
v
i
d
s
o
n
,
D.
D
.
Honeywell
H
o
n
e
y
w
e
l
l
Anderson,
A
n
d
e
r
s
o
n
,
C.
C
.
Sundstrand
S
u
n
d
s
t
r
a
n
d
Decker,
D
e
c
k
e
r
,
B.
B
.
Douglas
D
o
u
g
l
a
s
Aircraft
A
i
r
c
r
a
f
t
Angermayer,
A
n
g
e
r
m
a
y
e
r
,
J.
J
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
Dehlin,
D
e
h
l
i
n
,
G.
G
.
Honeywell
H
o
n
e
y
w
e
l
l
Anton,
A
n
t
o
n
,
T.
T
.
ARINC
A
R
I
N
C
Deller,
D
e
l
l
e
r
,
S.
S
.
Verdix
V
e
r
d
i
x
Ashpole,
A
s
h
p
o
l
e
,
R.
R
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Delong,
D
e
l
o
n
g
,
C.
C
.
Westar
W
e
s
t
a
r
Ashworth,
A
s
h
w
o
r
t
h
,
D.
D
.
Teledyne
T
e
l
e
d
y
n
e
Avionics
A
v
i
o
n
i
c
s
DeWalt,
D
e
W
a
l
t
,
M.
M
.
FAA
F
A
A
Astruc,
A
s
t
r
u
c
,
J.
J
.
Veridatas
V
e
r
i
d
a
t
a
s
Dewshi,
D
e
w
s
h
i
,
M.
M
.
Dowty
D
o
w
t
y
Controls
C
o
n
t
r
o
l
s
Awad,
A
w
a
d
,
S.
S
.
Canadair
C
a
n
a
d
a
i
r
Dick,
D
i
c
k
,
A.
A
.
GEC
G
E
C
Ferranti
F
e
r
r
a
n
t
i
Balivet,
B
a
l
i
v
e
t
,
E.
E
.
SNECMA
S
N
E
C
M
A
Dolman,
D
o
l
m
a
n
,
W.
W
.
Lucas
L
u
c
a
s
Aerospace
A
e
r
o
s
p
a
c
e
Barton,
B
a
r
t
o
n
,
D.
D
.
Intennetrics
I
n
t
e
n
n
e
t
r
i
c
s
Drake,
D
r
a
k
e
,
T.
T
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Beaman,
B
e
a
m
a
n
,
B.
B
.
Woodward
W
o
o
d
w
a
r
d
Governor
G
o
v
e
r
n
o
r
Drtil,
D
r
t
i
l
,
H.
H
.
Bodenseewerk
B
o
d
e
n
s
e
e
w
e
r
k
Geraetetechnik
G
e
r
a
e
t
e
t
e
c
h
n
i
k
Bearn,
B
e
a
r
n
,
W.
W
.
SDC
S
D
C
ASD
A
S
D
Dunham,
D
u
n
h
a
m
,
J.
J
.
Research
R
e
s
e
a
r
c
h
Triangle
T
r
i
a
n
g
l
e
Beaulieu,
B
e
a
u
l
i
e
u
,
G.
G
.
GE
G
E
Aircraft
A
i
r
c
r
a
f
t
Engines
E
n
g
i
n
e
s
Dunst,
D
u
n
s
t
,
A.
A
.
Smiths
S
m
i
t
h
s
Industries
I
n
d
u
s
t
r
i
e
s
Beijard,
B
e
i
j
a
r
d
,
J.
J
.
CEAT
C
E
A
T
Durgeat,
D
u
r
g
e
a
t
,
E.
E
.
Sextant
S
e
x
t
a
n
t
Avionique
A
v
i
o
n
i
q
u
e
Belcher,
B
e
l
c
h
e
r
,
G.
G
.
GEC
G
E
C
Avionics,
A
v
i
o
n
i
c
s
,
Ltd.
L
t
d
.
Dvorak,
D
v
o
r
a
k
,
E.
E
.
FAA
F
A
A
Bennet,
B
e
n
n
e
t
,
P.
P
.
CSE
C
S
E
Eckmann,
E
c
k
m
a
n
n
,
B.
B
.
Microcomputer
M
i
c
r
o
c
o
m
p
u
t
e
r
Berna,
B
e
r
n
a
,
P.
P
.
Sextant
S
e
x
t
a
n
t
Avionique
A
v
i
o
n
i
q
u
e
Ehrhart,
E
h
r
h
a
r
t
,
M.
M
.
FAA
F
A
A
Bisiaux,
B
i
s
i
a
u
x
,
M.
M
.
Eurocontrol
E
u
r
o
c
o
n
t
r
o
l
Fakhouri,
F
a
k
h
o
u
r
i
,
0.
0
.
Rogerson
R
o
g
e
r
s
o
n
Kratos
K
r
a
t
o
s
Blackburn,
B
l
a
c
k
b
u
r
n
,
M.
M
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
ATAD
A
T
A
D
Farrell,
F
a
r
r
e
l
l
,
J.
J
.
Westinghouse
W
e
s
t
i
n
g
h
o
u
s
e
Blair,
B
l
a
i
r
,
K.
K
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
Ferrell,
F
e
r
r
e
l
l
,
T.
T
.
Boeing
B
o
e
i
n
g
Bosco,
B
o
s
c
o
,
C.
C
.
FAA
F
A
A
Fieldstad,
F
i
e
l
d
s
t
a
d
,
K.
K
.
II
I
I
Morrow
M
o
r
r
o
w
Inc
I
n
c
Bowers,
B
o
w
e
r
s
,
R.
R
.
Air
A
i
r
Transport
T
r
a
n
s
p
o
r
t
Association
A
s
s
o
c
i
a
t
i
o
n
Finelli,
F
i
n
e
l
l
i
,
G.
G
.
NASA
N
A
S
A
Bradley,
B
r
a
d
l
e
y
,
S.
S
.
Mitre
M
i
t
r
e
Follet,
F
o
l
l
e
t
,
H.
H
.
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Branch,
B
r
a
n
c
h
,
C.
C
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
ATAD
A
T
A
D
Fortier,
F
o
r
t
i
e
r
,
S.
S
.
Columbia
C
o
l
u
m
b
i
a
Services
S
e
r
v
i
c
e
s
Group
G
r
o
u
p
Brazell,
B
r
a
z
e
l
l
,
R.
R
.
Vevas
V
e
v
a
s
Inc.
I
n
c
.
Franck,
F
r
a
n
c
k
,
P.
P
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Bretschneider,
B
r
e
t
s
c
h
n
e
i
d
e
r
,
M.
M
.
Deutsche
D
e
u
t
s
c
h
e
Airbus
A
i
r
b
u
s
Furstnau,
F
u
r
s
t
n
a
u
,
R.
R
.
Allison
A
l
l
i
s
o
n
Gas
G
a
s
Turbine
T
u
r
b
i
n
e
Brewer,
B
r
e
w
e
r
,
A.
A
.
Softech
S
o
f
t
e
c
h
Gale,
G
a
l
e
,
R.
R
.
Martin
M
a
r
t
i
n
Marietta
M
a
r
i
e
t
t
a
ATS
A
T
S
Brown,
B
r
o
w
n
,
P.
P
.
UK
U
K
MOD
M
O
D
Gamie,
G
a
m
i
e
,
G.
G
.
Aike
A
i
k
e
Brown,
B
r
o
w
n
,
W.
W
.
Sundstrand
S
u
n
d
s
t
r
a
n
d
Ganz,
G
a
n
z
,
H.
H
.
Airbus
A
i
r
b
u
s
Industrie
I
n
d
u
s
t
r
i
e
Burtenshaw,
B
u
r
t
e
n
s
h
a
w
,
G.
G
.
UK
U
K
CAA
C
A
A
Garroway,
G
a
r
r
o
w
a
y
,
L.
L
.
Westinghouse
W
e
s
t
i
n
g
h
o
u
s
e
Byers,
B
y
e
r
s
,
P.
P
.
Smith
S
m
i
t
h
Associates
A
s
s
o
c
i
a
t
e
s
Gasiorowski,
G
a
s
i
o
r
o
w
s
k
i
,
M
M
Honeywell
H
o
n
e
y
w
e
l
l
Caling,
C
a
l
i
n
g
,
J.
J
.
Avtech
A
v
t
e
c
h
Germanicus,
G
e
r
m
a
n
i
c
u
s
,
P.
P
.
Intertechnique
I
n
t
e
r
t
e
c
h
n
i
q
u
e
Campbell,
C
a
m
p
b
e
l
l
,
J.
J
.
US
U
S
Coast
C
o
a
s
t
Guard
G
u
a
r
d
Glasser,
G
l
a
s
s
e
r
,
J.
J
.
Teledyne
T
e
l
e
d
y
n
e
Carré,
C
a
r
r
é
,
B.
B
.
Program
P
r
o
g
r
a
m
Validation,
V
a
l
i
d
a
t
i
o
n
,
Ltd
L
t
d
Glenn,
G
l
e
n
n
,
E.
E
.
Teledyne
T
e
l
e
d
y
n
e
Castonguay,
C
a
s
t
o
n
g
u
a
y
,
R.
R
.
ELDEC
E
L
D
E
C
Goel,
G
o
e
l
,
A.
A
.
Syracuse
S
y
r
a
c
u
s
e
University
U
n
i
v
e
r
s
i
t
y
Chandler,
C
h
a
n
d
l
e
r
,
J.
J
.
Lucas
L
u
c
a
s
Aerospace
A
e
r
o
s
p
a
c
e
Ltd.
L
t
d
.
Griffith,
G
r
i
f
f
i
t
h
,
E.
E
.
II
I
I
Morrow
M
o
r
r
o
w
Inc
I
n
c
Cheney,
C
h
e
n
e
y
,
N.
N
.
Hamilton
H
a
m
i
l
t
o
n
Standard
S
t
a
n
d
a
r
d
Grimshaw,
G
r
i
m
s
h
a
w
,
A.
A
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Clemence,
C
l
e
m
e
n
c
e
,
G.
G
.
Chandler
C
h
a
n
d
l
e
r
Evans
E
v
a
n
s
Hainmar,
H
a
i
n
m
a
r
,
J.
J
.
Search
S
e
a
r
c
h
Technology
T
e
c
h
n
o
l
o
g
y
Climie,
C
l
i
m
i
e
,
B.
B
.
Honeywell
H
o
n
e
y
w
e
l
l
(Consult.)
(
C
o
n
s
u
l
t
.
)
Hall,
H
a
l
l
,
B.
B
.
Airline
A
i
r
l
i
n
e
Pilots
P
i
l
o
t
s
Association
A
s
s
o
c
i
a
t
i
o
n
Coffman,
C
o
f
f
m
a
n
,
K.
K
.
Simmonds
S
i
m
m
o
n
d
s
Hall,
H
a
l
l
,
B.
B
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Cohen,
C
o
h
e
n
,
N.
N
.
Honeywell
H
o
n
e
y
w
e
l
l
Halverson,
H
a
l
v
e
r
s
o
n
,
K.
K
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Coleman,
C
o
l
e
m
a
n
,
J.
J
.
Hamilton
H
a
m
i
l
t
o
n
Standard
S
t
a
n
d
a
r
d
Hannah,
H
a
n
n
a
h
,
J.
J
.
Info
I
n
f
o
Spectrum
S
p
e
c
t
r
u
m
Inc
I
n
c
Coley,
C
o
l
e
y
,
D.
D
.
Northstar
N
o
r
t
h
s
t
a
r
Avionics
A
v
i
o
n
i
c
s
Hannan,
H
a
n
n
a
n
,
R.
R
.
Smiths
S
m
i
t
h
s
Industries
I
n
d
u
s
t
r
i
e
s
Collins,
C
o
l
l
i
n
s
,
B.
B
.
Dowty
D
o
w
t
y
Controls
C
o
n
t
r
o
l
s
Hannert,
H
a
n
n
e
r
t
,
L.
L
.
Honeywell
H
o
n
e
y
w
e
l
l
Coupier,
C
o
u
p
i
e
r
,
A.
A
.
CEAT
C
E
A
T
Harrison,
H
a
r
r
i
s
o
n
,
W.
W
.
Advanced
A
d
v
a
n
c
e
d
System
S
y
s
t
e
m
Tech.
T
e
c
h
.
Crout,
C
r
o
u
t
,
J.
J
.
Gables
G
a
b
l
e
s
Engineering,
E
n
g
i
n
e
e
r
i
n
g
,
Inc.
I
n
c
.
Hawkes,
H
a
w
k
e
s
,
D.
D
.
UK
U
K
CAA
C
A
A
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
B-3
B
-
3
Heller,
H
e
l
l
e
r
,
P.
P
.
Deutsche
D
e
u
t
s
c
h
e
Airbus
A
i
r
b
u
s
McDonald,
M
c
D
o
n
a
l
d
,
W.
W
.
Sundstrand
S
u
n
d
s
t
r
a
n
d
Hendrickson,
H
e
n
d
r
i
c
k
s
o
n
,
T.
T
.
Boeing
B
o
e
i
n
g
McIntyre
M
c
I
n
t
y
r
e
FAAR&D
F
A
A
R
&
D
Hill,
H
i
l
l
,
K.
K
.
Boeing
B
o
e
i
n
g
McKinlay,
M
c
K
i
n
l
a
y
,
A.
A
.
Douglas
D
o
u
g
l
a
s
Aircraft
A
i
r
c
r
a
f
t
Hopf,
H
o
p
f
,
R.
R
.
GE
G
E
Aircraft
A
i
r
c
r
a
f
t
Engines
E
n
g
i
n
e
s
McKown,
M
c
K
o
w
n
,
B.
B
.
Boeing
B
o
e
i
n
g
Hopkins,
H
o
p
k
i
n
s
,
D.
D
.
Pratt
P
r
a
t
t
&
&
Whitney,
W
h
i
t
n
e
y
,
Canada
C
a
n
a
d
a
Meyer,
M
e
y
e
r
,
K.
K
.
Integsystems
I
n
t
e
g
s
y
s
t
e
m
s
Hostert,
H
o
s
t
e
r
t
,
S.
S
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Miller,
M
i
l
l
e
r
,
D.
D
.
George
G
e
o
r
g
e
Mason
M
a
s
o
n
University
U
n
i
v
e
r
s
i
t
y
Hung,
H
u
n
g
,
B.
B
.
MITRE
M
I
T
R
E
Mischkot,
M
i
s
c
h
k
o
t
,
E.
E
.
Garrett
G
a
r
r
e
t
t
Canada
C
a
n
a
d
a
Hutchinson,
H
u
t
c
h
i
n
s
o
n
,
S.
S
.
ARINC
A
R
I
N
C
Monavon,
M
o
n
a
v
o
n
,
M.
M
.
SNECMA
S
N
E
C
M
A
Ion,
I
o
n
,
J.
J
.
Lohr
L
o
h
r
Systems
S
y
s
t
e
m
s
Montgomery,
M
o
n
t
g
o
m
e
r
y
,
S.
S
.
Simmonds
S
i
m
m
o
n
d
s
Jack,
J
a
c
k
,
C.
C
.
Rolls
R
o
l
l
s
-Royce
-
R
o
y
c
e
Moore,
M
o
o
r
e
,
L.
L
.
Honeywell
H
o
n
e
y
w
e
l
l
Janelle,
J
a
n
e
l
l
e
,
J.
J
.
Honeywell
H
o
n
e
y
w
e
l
l
Morrice,
M
o
r
r
i
c
e
,
G.
G
.
GEC
G
E
C
Ferranti
F
e
r
r
a
n
t
i
Defence
D
e
f
e
n
c
e
Johnson,
J
o
h
n
s
o
n
,
R.
R
.
Delco
D
e
l
c
o
Systems
S
y
s
t
e
m
s
Ops
O
p
s
Morse,
M
o
r
s
e
,
T.
T
.
Boeing
B
o
e
i
n
g
Karis,
K
a
r
i
s
,
C.
C
.
GE-ACSD
G
E
-
A
C
S
D
Moyer,
M
o
y
e
r
,
F.
F
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Keizer,
K
e
i
z
e
r
,
K.
K
.
Microcomputer
M
i
c
r
o
c
o
m
p
u
t
e
r
Mueller,
M
u
e
l
l
e
r
,
H.
H
.
FAA
F
A
A
Keller,
K
e
l
l
e
r
,
F.
F
.
FAA
F
A
A
Myers,
M
y
e
r
s
,
J.
J
.
Simmonds
S
i
m
m
o
n
d
s
Kerr,
K
e
r
r
,
R.
R
.
Honeywell
H
o
n
e
y
w
e
l
l
Neilan,
N
e
i
l
a
n
,
P.
P
.
UK
U
K
CAA
C
A
A
Kilbane,
K
i
l
b
a
n
e
,
T.
T
.
Westinghouse
W
e
s
t
i
n
g
h
o
u
s
e
Nelson,
N
e
l
s
o
n
,
K
K
Woodward
W
o
o
d
w
a
r
d
Govemor
G
o
v
e
m
o
r
Kirby,
K
i
r
b
y
,
N.
N
.
Boeing
B
o
e
i
n
g
Newton,
N
e
w
t
o
n
,
1.
1
.
GEC
G
E
C
Avionics,
A
v
i
o
n
i
c
s
,
Ltd.
L
t
d
.
Kleine-Beek,
K
l
e
i
n
e
-
B
e
e
k
,
W.
W
.
LBA
L
B
A
Nogué,
N
o
g
u
é
,
J-M.
J
-
M
.
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Klinka,
K
l
i
n
k
a
,
B.
B
.
FAA
F
A
A
Norris,
N
o
r
r
i
s
,
J.
J
.
ELDEC
E
L
D
E
C
Kosowski,
K
o
s
o
w
s
k
i
,
E.
E
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Nutaro,
N
u
t
a
r
o
,
J.
J
.
Honeywell
H
o
n
e
y
w
e
l
l
Kraft,
K
r
a
f
t
,
T.
T
.
FAA
F
A
A
Oberg,
O
b
e
r
g
,
M.
M
.
Boeing
B
o
e
i
n
g
Kress,
K
r
e
s
s
,
M.
M
.
Boeing
B
o
e
i
n
g
Ochs,
O
c
h
s
,
D.
D
.
Cessna
C
e
s
s
n
a
Aircraft
A
i
r
c
r
a
f
t
Krodel,
K
r
o
d
e
l
,
J.
J
.
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
Olivier,
O
l
i
v
i
e
r
,
E.
E
.
Hamilton
H
a
m
i
l
t
o
n
Standard
S
t
a
n
d
a
r
d
Kuhl,
K
u
h
l
,
F.
F
.
Mitre
M
i
t
r
e
Oss,
O
s
s
,
J.
J
.
Honeywell
H
o
n
e
y
w
e
l
l
Kuhn,
K
u
h
n
,
R.
R
.
NIST
N
I
S
T
Paasch,
P
a
a
s
c
h
,
S.
S
.
FAA
F
A
A
Kurowsky,
K
u
r
o
w
s
k
y
,
R.
R
.
US
U
S
Anny
A
n
n
y
Patterson,
P
a
t
t
e
r
s
o
n
,
W.
W
.
Westinghouse
W
e
s
t
i
n
g
h
o
u
s
e
Ladier,
L
a
d
i
e
r
,
G.
G
.
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Peak,
P
e
a
k
,
A.
A
.
Ametek
A
m
e
t
e
k
Aerospace
A
e
r
o
s
p
a
c
e
Lampton,
L
a
m
p
t
o
n
,
M.
M
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Pearce,
P
e
a
r
c
e
,
M.
M
.
GEC
G
E
C
Ferranti
F
e
r
r
a
n
t
i
Defence
D
e
f
e
n
c
e
Langumier,
L
a
n
g
u
m
i
e
r
,
P.
P
.
DGAC
D
G
A
C
France
F
r
a
n
c
e
Penny,
P
e
n
n
y
,
J.
J
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
lapicca,
l
a
p
i
c
c
a
,
C.
C
.
ALENIA
A
L
E
N
I
A
(Aeritalia)
(
A
e
r
i
t
a
l
i
a
)
Perini,
P
e
r
i
n
i
,
M.
M
.
FAA
F
A
A
LaPietra,
L
a
P
i
e
t
r
a
,
P.
P
.
GE
G
E
Aircraft
A
i
r
c
r
a
f
t
Engines
E
n
g
i
n
e
s
Perret,
P
e
r
r
e
t
,
B.
B
.
EUROCAE
E
U
R
O
C
A
E
Laurent,
L
a
u
r
e
n
t
,
0.
0
.
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Peterson,
P
e
t
e
r
s
o
n
,
K.
K
.
Honeywell
H
o
n
e
y
w
e
l
l
Leveson,
L
e
v
e
s
o
n
,
N.
N
.
University
U
n
i
v
e
r
s
i
t
y
of
o
f
California
C
a
l
i
f
o
r
n
i
a
Pflug,
P
f
l
u
g
,
B.
B
.
Boeing
B
o
e
i
n
g
Lewis,
L
e
w
i
s
,
D.
D
.
Boeing
B
o
e
i
n
g
Pharr,
P
h
a
r
r
,
J.
J
.
Teledyne
T
e
l
e
d
y
n
e
Avionics
A
v
i
o
n
i
c
s
Lillis,
L
i
l
l
i
s
,
M.
M
.
Hamilton
H
a
m
i
l
t
o
n
Standard
S
t
a
n
d
a
r
d
Piper,
P
i
p
e
r
,
E.
E
.
Douglas
D
o
u
g
l
a
s
Aircraft
A
i
r
c
r
a
f
t
Lin,
L
i
n
,
M.
M
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Porter,
P
o
r
t
e
r
,
C.
C
.
Kollsman
K
o
l
l
s
m
a
n
Littlewood,
L
i
t
t
l
e
w
o
o
d
,
B.
B
.
Centre
C
e
n
t
r
e
for
f
o
r
SW
S
W
Reliability
R
e
l
i
a
b
i
l
i
t
y
Prisaznuk,
P
r
i
s
a
z
n
u
k
,
P.
P
.
ARINC
A
R
I
N
C
-
-
AEEC
A
E
E
C
Lleres,
L
l
e
r
e
s
,
J.
J
.
SNECMA
S
N
E
C
M
A
Quinby,
Q
u
i
n
b
y
,
G.
G
.
Narco
N
a
r
c
o
Avionics
A
v
i
o
n
i
c
s
Lock,
L
o
c
k
,
H.
H
.
ARINC
A
R
I
N
C
-
-
AEEC
A
E
E
C
Ramji,
R
a
m
j
i
,
S.
S
.
Canadian
C
a
n
a
d
i
a
n
Marconi
M
a
r
c
o
n
i
Lohr,
L
o
h
r
,
J.
J
.
RTCA
R
T
C
A
Rao,
R
a
o
,
R.
R
.
Transport
T
r
a
n
s
p
o
r
t
Canada
C
a
n
a
d
a
Luck,
L
u
c
k
,
H.
H
.
Aero-Radui
A
e
r
o
-
R
a
d
u
i
Rawas,
R
a
w
a
s
,
M.
M
.
Beech
B
e
e
c
h
Aircraft
A
i
r
c
r
a
f
t
Marchand,
M
a
r
c
h
a
n
d
,
M.
M
.
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Reich,
R
e
i
c
h
,
A.
A
.
Racal
R
a
c
a
l
Avionics
A
v
i
o
n
i
c
s
Marzke,
M
a
r
z
k
e
,
L.
L
.
Kollsman
K
o
l
l
s
m
a
n
Reige,
R
e
i
g
e
,
J.
J
.
Woodward
W
o
o
d
w
a
r
d
Govemor
G
o
v
e
m
o
r
Mastantvoild,
M
a
s
t
a
n
t
v
o
i
l
d
,
P.
P
.
DGAC
D
G
A
C
France
F
r
a
n
c
e
Reitz,
R
e
i
t
z
,
G.
G
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Mattissek,
M
a
t
t
i
s
s
e
k
,
A.
A
.
LITEF
L
I
T
E
F
Reynold,
R
e
y
n
o
l
d
,
B.
B
.
Douglas
D
o
u
g
l
a
s
Aircraft
A
i
r
c
r
a
f
t
Mayor,
M
a
y
o
r
,
M.
M
.
Boeing
B
o
e
i
n
g
of
o
f
Canada
C
a
n
a
d
a
Roberts,
R
o
b
e
r
t
s
,
F.
F
.
Douglas
D
o
u
g
l
a
s
Aircraft
A
i
r
c
r
a
f
t
McCallister,
M
c
C
a
l
l
i
s
t
e
r
,
R.
R
.
FAA
F
A
A
Robinson,
R
o
b
i
n
s
o
n
,
P.
P
.
Rolls
R
o
l
l
s
-Royce
-
R
o
y
c
e
McCormick,
M
c
C
o
r
m
i
c
k
,
T.
T
.
Allied-Signal
A
l
l
i
e
d
-
S
i
g
n
a
l
Canada
C
a
n
a
d
a
Rodgers,
R
o
d
g
e
r
s
,
D.
D
.
Boeing
B
o
e
i
n
g
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
B-4
B
-
4
Roth,
R
o
t
h
,
T.
T
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
Van
V
a
n
De
D
e
Hulst,
H
u
l
s
t
,
H.
H
.
Fokker
F
o
k
k
e
r
Rowe,
R
o
w
e
,
W.
W
.
Westinghouse
W
e
s
t
i
n
g
h
o
u
s
e
Van
V
a
n
Houtte,
H
o
u
t
t
e
,
E.
E
.
ARINC
A
R
I
N
C
Ruana,
R
u
a
n
a
,
R.
R
.
Jeppesen
J
e
p
p
e
s
e
n
Vaughn,
V
a
u
g
h
n
,
R.
R
.
FAA
F
A
A
Russell,
R
u
s
s
e
l
l
,
W.
W
.
Air
A
i
r
Transport
T
r
a
n
s
p
o
r
t
Association
A
s
s
o
c
i
a
t
i
o
n
Vincent,
V
i
n
c
e
n
t
,
J.
J
.
UK
U
K
CAA
C
A
A
Ryburn,
R
y
b
u
r
n
,
R.
R
.
FAA
F
A
A
Wade,
W
a
d
e
,
M.
M
.
FAA
F
A
A
Saraceni,
S
a
r
a
c
e
n
i
,
P.
P
.
FAA
F
A
A
Walker,
W
a
l
k
e
r
,
T.
T
.
GE
G
E
Aircraft
A
i
r
c
r
a
f
t
Engines
E
n
g
i
n
e
s
Sarich,
S
a
r
i
c
h
,
C.
C
.
FAA
F
A
A
Ward,
W
a
r
d
,
J.
J
.
Gulfstreatn
G
u
l
f
s
t
r
e
a
t
n
Aero
A
e
r
o
Satyen,
S
a
t
y
e
n
,
U.
U
.
MITRE
M
I
T
R
E
Watrous,
W
a
t
r
o
u
s
,
D.
D
.
RTCA
R
T
C
A
Sayegh,S.
S
a
y
e
g
h
,
S
.
Canadian
C
a
n
a
d
i
a
n
Marconi
M
a
r
c
o
n
i
Watson,
W
a
t
s
o
n
,
J.
J
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
Schad,L.
S
c
h
a
d
,
L
.
Boeing
B
o
e
i
n
g
Watts,
W
a
t
t
s
,
R.
R
.
Honeywell
H
o
n
e
y
w
e
l
l
Schirle,
S
c
h
i
r
l
e
,
P.
P
.
Dassault
D
a
s
s
a
u
l
t
Aviation
A
v
i
a
t
i
o
n
Weadon,
W
e
a
d
o
n
,
T.
T
.
Honeywell
H
o
n
e
y
w
e
l
l
Schmitz,
S
c
h
m
i
t
z
,
S.
S
.
Alcatel
A
l
c
a
t
e
l
TITN
T
I
T
N
Weiser,
W
e
i
s
e
r
,
B.
B
.
Honeywell
H
o
n
e
y
w
e
l
l
Scott,
S
c
o
t
t
,
R.
R
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Wells,
W
e
l
l
s
,
R.
R
.
Boeing
B
o
e
i
n
g
Secher,C.
S
e
c
h
e
r
,
C
.
DGAC
D
G
A
C
France
F
r
a
n
c
e
Wilkinson,
W
i
l
k
i
n
s
o
n
,
M.
M
.
Smith
S
m
i
t
h
Associates
A
s
s
o
c
i
a
t
e
s
Seeman,
S
e
e
m
a
n
,
R.
R
.
Boeing
B
o
e
i
n
g
Willimns,
W
i
l
l
i
m
n
s
,
J.
J
.
FAA
F
A
A
Semmakie,
S
e
m
m
a
k
i
e
,
E.
E
.
British
B
r
i
t
i
s
h
Airways
A
i
r
w
a
y
s
Wilson,
W
i
l
s
o
n
,
W.
W
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Shagnea,A.
S
h
a
g
n
e
a
,
A
.
Research
R
e
s
e
a
r
c
h
Triangle
T
r
i
a
n
g
l
e
Wojciech,
W
o
j
c
i
e
c
h
,
J.
J
.
FAA
F
A
A
Shahijanian,
S
h
a
h
i
j
a
n
i
a
n
,
P.
P
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Wolf,
W
o
l
f
,
C.
C
.
FAA
F
A
A
Shimmin,
S
h
i
m
m
i
n
,
A.
A
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Wolf,
W
o
l
f
,
R.
R
.
Teledyne
T
e
l
e
d
y
n
e
Shore,
S
h
o
r
e
,
D.
D
.
Honeywell
H
o
n
e
y
w
e
l
l
Wolfley,
W
o
l
f
l
e
y
,
K.
K
.
FAA
F
A
A
Silver,
S
i
l
v
e
r
,
S.
S
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Wong,
W
o
n
g
,
A.
A
.
FAA
F
A
A
Simmons,
S
i
m
m
o
n
s
,
J.
J
.
Woodward
W
o
o
d
w
a
r
d
Govemor
G
o
v
e
m
o
r
Wood,
W
o
o
d
,
B.
B
.
CMU/SEI
C
M
U
/
S
E
I
Simonetti,
S
i
m
o
n
e
t
t
i
,
A.
A
.
Veridatas
V
e
r
i
d
a
t
a
s
Woodfield,
W
o
o
d
f
i
e
l
d
,
D.
D
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Sitz,
S
i
t
z
,
J.
J
.
NASA
N
A
S
A
Wright,
W
r
i
g
h
t
,
C.
C
.
FAA
F
A
A
Skaves,
S
k
a
v
e
s
,
P.
P
.
FAA
F
A
A
Wright,
W
r
i
g
h
t
,
K.
K
.
Smiths
S
m
i
t
h
s
Industries
I
n
d
u
s
t
r
i
e
s
Smart,
S
m
a
r
t
,
J.
J
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Young
Y
o
u
n
g
K.
K
.
Honeywell
H
o
n
e
y
w
e
l
l
Smith,
S
m
i
t
h
,
N.
N
.
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Yuen,
Y
u
e
n
,
J.
J
.
Canadian
C
a
n
a
d
i
a
n
Marconi
M
a
r
c
o
n
i
Smith,
S
m
i
t
h
,
W.
W
.
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Spoor,
S
p
o
o
r
,
H.
H
.
GEC
G
E
C
Ferranti
F
e
r
r
a
n
t
i
Stack,
S
t
a
c
k
,
N.
N
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Stallivitz,
S
t
a
l
l
i
v
i
t
z
,
C.
C
.
Beech
B
e
e
c
h
Aircraft
A
i
r
c
r
a
f
t
Stesney,
S
t
e
s
n
e
y
,
J.
J
.
Litton
L
i
t
t
o
n
Aero
A
e
r
o
Products
P
r
o
d
u
c
t
s
Stihl,
S
t
i
h
l
,
D.
D
.
Douglas
D
o
u
g
l
a
s
Aircraft
A
i
r
c
r
a
f
t
Stolzenthaler,
S
t
o
l
z
e
n
t
h
a
l
e
r
,
J.
J
.
Hamilton
H
a
m
i
l
t
o
n
Standard
S
t
a
n
d
a
r
d
Struck,
S
t
r
u
c
k
,
W.
W
.
Boeing
B
o
e
i
n
g
Summers,
S
u
m
m
e
r
s
,
P.
P
.
Rolls
R
o
l
l
s
Royce
R
o
y
c
e
Teichert,
T
e
i
c
h
e
r
t
,
P.
P
.
LBA
L
B
A
Germany
G
e
r
m
a
n
y
Temprement,
T
e
m
p
r
e
m
e
n
t
,
M.
M
.
Sextant
S
e
x
t
a
n
t
Avionique
A
v
i
o
n
i
q
u
e
Tessier,
T
e
s
s
i
e
r
,
B.
B
.
FAA
F
A
A
Theodore,
T
h
e
o
d
o
r
e
,
A.
A
.
Bendix/King
B
e
n
d
i
x
/
K
i
n
g
ATAD
A
T
A
D
Thompson,
T
h
o
m
p
s
o
n
,
L.
L
.
Honeywell
H
o
n
e
y
w
e
l
l
Toldo,
T
o
l
d
o
,
D.
D
.
SNECMA
S
N
E
C
M
A
Tomasi,
T
o
m
a
s
i
,
J.
J
.
Aerospatiale
A
e
r
o
s
p
a
t
i
a
l
e
Tourret,
T
o
u
r
r
e
t
,
0.
0
.
STTE
S
T
T
E
Tripp,
T
r
i
p
p
,
L.
L
.
Boeing
B
o
e
i
n
g
Tucker,
T
u
c
k
e
r
,
R.
R
.
Teledyne
T
e
l
e
d
y
n
e
Controls
C
o
n
t
r
o
l
s
Tucker,
T
u
c
k
e
r
,
S.
S
.
GTE
G
T
E
Airfone
A
i
r
f
o
n
e
Turton,
T
u
r
t
o
n
,
J.
J
.
UK
U
K
MOD
M
O
D
Van
V
a
n
Baal,
B
a
a
l
,
J.
J
.
RLD
R
L
D
The
T
h
e
Netherlands
N
e
t
h
e
r
l
a
n
d
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
C-1
C
-
1
APPENDIX
A
P
P
E
N
D
I
X
C
C
INDEX
I
N
D
E
X
OF
O
F
TERMS
T
E
R
M
S
This
T
h
i
s
index
i
n
d
e
x
includes
i
n
c
l
u
d
e
s
these
t
h
e
s
e
terms:
t
e
r
m
s
:
-
Items
I
t
e
m
s
identified
i
d
e
n
t
i
f
i
e
d
in
i
n
the
t
h
e
glossary
g
l
o
s
s
a
r
y
-
Terms
T
e
r
m
s
of
o
f
Reference
R
e
f
e
r
e
n
c
e
-
Useful
U
s
e
f
u
l
alternative
a
l
t
e
r
n
a
t
i
v
e
nomenclature
n
o
m
e
n
c
l
a
t
u
r
e
for
f
o
r
important
i
m
p
o
r
t
a
n
t
concepts
c
o
n
c
e
p
t
s
All
A
l
l
indexed
i
n
d
e
x
e
d
terms
t
e
r
m
s
are
a
r
e
followed
f
o
l
l
o
w
e
d
by
b
y
page
p
a
g
e
number
n
u
m
b
e
r
references.
r
e
f
e
r
e
n
c
e
s
.
The
T
h
e
underlined
u
n
d
e
r
l
i
n
e
d
page
p
a
g
e
number(s)
n
u
m
b
e
r
(
s
)
indicates
i
n
d
i
c
a
t
e
s
the
t
h
e
page
p
a
g
e
where
w
h
e
r
e
the
t
h
e
term
t
e
r
m
is
i
s
defined.
d
e
f
i
n
e
d
.
acceptance
a
c
c
e
p
t
a
n
c
e
58
5
8
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
1,
1
,
2,
2
,
43,
4
3
,
45,
4
5
,
47,
4
7
,
48
4
8
agreement(s)
a
g
r
e
e
m
e
n
t
(
s
)
2,
2
,
16,
1
6
,
43,
4
3
,
45,
4
5
,
62
6
2
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
requirements
r
e
q
u
i
r
e
m
e
n
t
s
6,
6
,
7,
7
,
41,
4
1
,
57
5
7
aircraft
a
i
r
c
r
a
f
t
1,
1
,
2,
2
,
6,
6
,
7,
7
,
8,
8
,
11,
1
1
,
13,
1
3
,
16,
1
6
,
21,
2
1
,
23,
2
3
,
33,
3
3
,
45,
4
5
,
57
5
7
change
c
h
a
n
g
e
control
c
o
n
t
r
o
l
15,
1
5
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
39,
3
9
,
50,
5
0
,
59
5
9
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
1,
1
,
8
8
change
c
h
a
n
g
e
history
h
i
s
t
o
r
y
37,
3
7
,
55
5
5
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
1,
1
,
15,
1
5
,
38
3
8
change
c
h
a
n
g
e
review
r
e
v
i
e
w
37,
3
7
,
39,
3
9
,
50
5
0
algorithm(s)
a
l
g
o
r
i
t
h
m
(
s
)
27,
2
7
,
28,
2
8
,
32,
3
2
,
52
5
2
code
c
o
d
e
structure
s
t
r
u
c
t
u
r
e
11,
1
1
,
26,
2
6
,
33
3
3
alternative
a
l
t
e
r
n
a
t
i
v
e
method(s)
m
e
t
h
o
d
(
s
)
2,
2
,
48,
4
8
,
57,
5
7
,
62,
6
2
,
63
6
3
commercial
c
o
m
m
e
r
c
i
a
l
off-the-shelf
o
f
f
-
t
h
e
-
s
h
e
l
f
(COTS)
(
C
O
T
S
)
software
s
o
f
t
w
a
r
e
5,
5
,
10,
1
0
,
48,
4
8
,
58
5
8
analysis(es)
a
n
a
l
y
s
i
s
(
e
s
)
6,
6
,
19,
1
9
,
23,
2
3
,
25,
2
5
,
26,
2
6
,
27,
2
7
,
28,
2
8
,
29,
2
9
,
31,
3
1
,
33,
3
3
,
49,
4
9
,
53,
5
3
,
57,
5
7
,
59,
5
9
,
61,
6
1
,
62,
6
2
,
63,
6
3
,
66,
6
6
,
67
6
7
compiler(s)
c
o
m
p
i
l
e
r
(
s
)
17,
1
7
,
18,
1
8
,
23,
2
3
,
33,
3
3
,
39,
3
9
,
49,
4
9
,
53,
5
3
,
54,
5
4
,
58,
5
8
,
64,
6
4
,
65
6
5
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
7,
7
,
8,
8
,
11,
1
1
,
36,
3
6
,
54,
5
4
,
63
6
3
component(s)
c
o
m
p
o
n
e
n
t
(
s
)
6,
6
,
8,
8
,
9,
9
,
10,
1
0
,
11,
1
1
,
13,
1
3
,
16,
1
6
,
21,
2
1
,
26,
2
6
,
28,
2
8
,
29,
2
9
,
32,
3
2
,
33,
3
3
,
35,
3
5
,
36,
3
6
,
47,
4
7
,
51,
5
1
,
52,
5
2
,
54,
5
4
,
66
6
6
applicant
a
p
p
l
i
c
a
n
t
1,
1
,
2,
2
,
8,
8
,
21,
2
1
,
43,
4
3
,
45,
4
5
,
48,
4
8
,
49,
4
9
,
57,
5
7
,
59,
5
9
,
60,
6
0
,
62,
6
2
,
63,
6
3
,
condition(s)
c
o
n
d
i
t
i
o
n
(
s
)
10,
1
0
,
20,
2
0
,
23,
2
3
,
29,
2
9
,
31,
3
1
,
32,
3
2
,
51,
5
1
,
52,
5
2
,
53
5
3
64,
6
4
,
65,
6
5
,
66
6
6
approve
a
p
p
r
o
v
e
(d,
(
d
,
al)
a
l
)
2,
2
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
38,
3
8
,
41,
4
1
,
42,
4
2
,
44,
4
4
,
45,
4
5
,
51
5
1
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
11,
1
1
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
39,
3
9
,
50,
5
0
,
61
6
1
archive(s)
a
r
c
h
i
v
e
(
s
)
35,
3
5
,
38,
3
8
,
42,
4
2
,
50,
5
0
,
54,
5
4
,
55
5
5
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item(s)
i
t
e
m
(
s
)
14,
1
4
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
38,
3
8
,
50,
5
0
,
53,
5
3
,
54
5
4
assurance
a
s
s
u
r
a
n
c
e
18,
1
8
,
41,
4
1
,
42,
4
2
,
59,
5
9
,
66
6
6
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process
p
r
o
c
e
s
s
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
status
s
t
a
t
u
s
accounting
a
c
c
o
u
n
t
i
n
g
37,
3
7
,
39,
3
9
,
50
5
0
audit(s)
a
u
d
i
t
(
s
)
41,
4
1
,
42,
4
2
,
51,
5
1
,
55
5
5
control(s)
c
o
n
t
r
o
l
(
s
)
13,
1
3
,
25
2
5
,28,
,
2
8
,
30,
3
0
,
32,
3
2
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
39,
3
9
,
42,
4
2
,
47,
4
7
,
50,
5
0
,
51
5
1
authority
a
u
t
h
o
r
i
t
y
38,
3
8
,
41,
4
1
,
50,
5
0
,
51
5
1
control
c
o
n
t
r
o
l
category(ies)
c
a
t
e
g
o
r
y
(
i
e
s
)
39,
3
9
,
42,
4
2
,
47
4
7
baseline(s)
b
a
s
e
l
i
n
e
(
s
)
10,
1
0
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
39,
3
9
,
42,
4
2
,
49,
4
9
,
50,
5
0
,
53,
5
3
,
55,
5
5
,
57,
5
7
,
58,
5
8
,
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
1
1
(CC1)
(
C
C
1
)
39,
3
9
,
47,
4
7
,
50,
5
0
,
61
6
1
59
5
9
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
1,
1
,
2,
2
,
42,
4
2
,
43,
4
3
,
45,
4
5
,
47,
4
7
,
48,
4
8
,
55,
5
5
,
57,
5
7
,
58,
5
8
,
62
6
2
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
(CC2)
(
C
C
2
)
39,
3
9
,
47,
4
7
,
50,
5
0
,
61
6
1
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
application
a
p
p
l
i
c
a
t
i
o
n
42
4
2
control
c
o
n
t
r
o
l
coupling
c
o
u
p
l
i
n
g
9,
9
,
33
3
3
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
2,
2
,
7,
7
,
16,
1
6
,
35,
3
5
,
38,
3
8
,
43,
4
3
,
44,
4
4
,
45,
4
5
,
47,
4
7
,
48,
4
8
,
55,
5
5
,
60,
6
0
,
62,
6
2
,
64,
6
4
,
65,
6
5
,
67
6
7
control
c
o
n
t
r
o
l
flow
f
l
o
w
21,
2
1
,
28,
2
8
,
52,
5
2
,
61
6
1
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
review(s)
r
e
v
i
e
w
(
s
)
10,
1
0
,
38,
3
8
,
43
4
3
control
c
o
n
t
r
o
l
flow
f
l
o
w
analysis
a
n
a
l
y
s
i
s
57
5
7
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
basis
b
a
s
i
s
43,
4
3
,
45,
4
5
,
48,
4
8
,
57
5
7
corrective
c
o
r
r
e
c
t
i
v
e
action
a
c
t
i
o
n
36,
3
6
,
37,
3
7
,
41,
4
1
,
51,
5
1
,
54
5
4
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
credit
c
r
e
d
i
t
17,
1
7
,
30,
3
0
,
36,
3
6
,
42,
4
2
,
61,
6
1
,
62,
6
2
,
65
6
5
coupling
c
o
u
p
l
i
n
g
28,
2
8
,
52,
5
2
,
57
5
7
see
s
e
e
also
a
l
s
o
control
c
o
n
t
r
o
l
coupling
c
o
u
p
l
i
n
g
and
a
n
d
data
d
a
t
a
coupling
c
o
u
p
l
i
n
g
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process
p
r
o
c
e
s
s
13,
1
3
,
43,
4
3
,
48
4
8
coverage
c
o
v
e
r
a
g
e
11,
1
1
,
17,
1
7
,
18,
1
8
,
31,
3
1
,
33,
3
3
,
53,
5
3
,
60,
6
0
,
64
6
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
C-2
C
-
2
coverage
c
o
v
e
r
a
g
e
analysis(es)
a
n
a
l
y
s
i
s
(
e
s
)
11,17,
1
1
,
1
7
,
18,
1
8
,
26,
2
6
,
29,
2
9
,
33,
3
3
,
49,
4
9
,
53,
5
3
,
host
h
o
s
t
computer
c
o
m
p
u
t
e
r
18,
1
8
,
30
3
0
60,
6
0
,
61,
6
1
,
64,
6
4
,
65
6
5
data
d
a
t
a
coupling
c
o
u
p
l
i
n
g
9,
9
,
33
3
3
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
36,
3
6
,
37,
3
7
,
38,
3
8
,
39,
3
9
,
48,
4
8
,
50,
5
0
,
53,
5
3
,
54,
5
4
,
55
5
5
data
d
a
t
a
dictionary
d
i
c
t
i
o
n
a
r
y
52
5
2
independence
i
n
d
e
p
e
n
d
e
n
c
e
10,
1
0
,
18,
1
8
,
25,
2
5
,
41,
4
1
,
49,
4
9
,
51,
5
1
,
64
6
4
data
d
a
t
a
flow
f
l
o
w
21,
2
1
,
28,
2
8
,
51,
5
1
,
52,
5
2
,
61
6
1
integral
i
n
t
e
g
r
a
l
process(es)
p
r
o
c
e
s
s
(
e
s
)
13,
1
3
,
14,
1
4
,
15,
1
5
,
16,
1
6
,
20,
2
0
,
22,
2
2
,
37,
3
7
,
41,
4
1
,
55
5
5
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process,
p
r
o
c
e
s
s
,
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
process,
p
r
o
c
e
s
s
,
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
process,
p
r
o
c
e
s
s
,
and
a
n
d
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
liaison
l
i
a
i
s
o
n
process
p
r
o
c
e
s
s
data
d
a
t
a
flow
f
l
o
w
analysis
a
n
a
l
y
s
i
s
57
5
7
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
13,
1
3
,
14,
1
4
,
18,
1
8
,
19,
1
9
,
22,
2
2
,
23,
2
3
,
29
2
9
data
d
a
t
a
retention
r
e
t
e
n
t
i
o
n
38,
3
8
,
39,
3
9
,
50
5
0
interrupt(s)
i
n
t
e
r
r
u
p
t
(
s
)
9,
9
,
19,
1
9
,
28,
2
8
,
32,
3
2
,
51,
5
1
,
53
5
3
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
10,
1
0
,
16,
1
6
,
23,
2
3
,
33,
3
3
,
53
5
3
linking
l
i
n
k
i
n
g
and
a
n
d
loading
l
o
a
d
i
n
g
data
d
a
t
a
22,
2
2
,
29,
2
9
,
53
5
3
dead
d
e
a
d
code
c
o
d
e
23,
2
3
,
33
3
3
low-level
l
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
19,
1
9
,
20,
2
0
,
21,
2
1
,
22,
2
2
,
23,
2
3
,
25,
2
5
,
27,
2
7
,
28,
2
8
,
29,
2
9
,
32,
3
2
,
51,
5
1
,
52,
5
2
,
59
5
9
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
decision(s)
d
e
c
i
s
i
o
n
(
s
)
32
3
2
low-level
l
o
w
-
l
e
v
e
l
testing
t
e
s
t
i
n
g
29,
2
9
,
31,
3
1
,
32
3
2
derivative
d
e
r
i
v
a
t
i
v
e
baseline
b
a
s
e
l
i
n
e
36
3
6
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
16,
1
6
,
43,
4
3
,
45,
4
5
,
48
4
8
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
19,
1
9
,
20,
2
0
,
21,
2
1
,
23,
2
3
,
27,
2
7
,
51,
5
1
,
52,
5
2
,
53
5
3
media
m
e
d
i
a
38,
3
8
,
39,
3
9
,
47,
4
7
,
54
5
4
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
20,
2
0
,
22,
2
2
,
44,
4
4
,
51,
5
1
,
52,
5
2
,
53
5
3
memory
m
e
m
o
r
y
device(s)
d
e
v
i
c
e
(
s
)
9,
9
,
38
3
8
development
d
e
v
e
l
o
p
m
e
n
t
baseline(s)
b
a
s
e
l
i
n
e
(
s
)
10,
1
0
,
57,
5
7
,
58,
5
8
,
59
5
9
modification
m
o
d
i
f
i
c
a
t
i
o
n
(s)
(
s
)
6,
6
,
10,
1
0
,
35,
3
5
,
36,
3
6
,
38,
3
8
,
42,
4
2
,
45,
4
5
,
47,
4
7
,
49,
4
9
,
54,
5
4
,
57,
5
7
,
58,
5
8
,
66
6
6
dissimilar(ity)
d
i
s
s
i
m
i
l
a
r
(
i
t
y
)
6,
6
,
9,
9
,
16,
1
6
,
64,
6
4
,
65
6
5
modified
m
o
d
i
f
i
e
d
condition/decision
c
o
n
d
i
t
i
o
n
/
d
e
c
i
s
i
o
n
coverage
c
o
v
e
r
a
g
e
31
3
1
see
s
e
e
also
a
l
s
o
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
emulator
e
m
u
l
a
t
o
r
18,
1
8
,
30,
3
0
,
49
4
9
monitoring
m
o
n
i
t
o
r
i
n
g
30,
3
0
,
42,
4
2
,
51
5
1
engine(s)
e
n
g
i
n
e
(
s
)
1,
1
,
2,
2
,
13,
1
3
,
16,
1
6
,
23,
2
3
,
33,
3
3
,
45
4
5
multiple-version
m
u
l
t
i
p
l
e
-
v
e
r
s
i
o
n
dissimilar
d
i
s
s
i
m
i
l
a
r
software
s
o
f
t
w
a
r
e
8,
8
,
9,
9
,
15,
1
5
,
48,
4
8
,
49,
4
9
,
53,
5
3
,
63,
6
3
,
65
6
5
normal
n
o
r
m
a
l
range
r
a
n
g
e
test
t
e
s
t
cases
c
a
s
e
s
30,
3
0
,
31
3
1
equivalence
e
q
u
i
v
a
l
e
n
c
e
class(es)
c
l
a
s
s
(
e
s
)
31
3
1
object
o
b
j
e
c
t
code
c
o
d
e
17,
1
7
,
22,
2
2
,
33,
3
3
,
53,
5
3
,
58,
5
8
,
64,
6
4
,
65
6
5
error(s)
e
r
r
o
r
(
s
)
6,
6
,
8,
8
,
9,
9
,
10,
1
0
,
15,
1
5
,
16,
1
6
,
17,
1
7
,
25,
2
5
,
26,
2
6
,
27,
2
7
,
28,
2
8
,
29,
2
9
,
30,
3
0
,
operation
o
p
e
r
a
t
i
o
n
(al)
(
a
l
)
(ing)
(
i
n
g
)
1,
1
,
6,
6
,
7,
7
,
8,
8
,
11,
1
1
,
17,
1
7
,
21,
2
1
,
28,
2
8
,
29,
2
9
,
31,
3
1
,
32,
3
2
,
31,
3
1
,
32,
3
2
,
37,
3
7
,
38,
3
8
,
49,
4
9
,
57,
5
7
,
59,
5
9
,
60,
6
0
,
61,
6
1
,
63,
6
3
,
64,
6
4
,
65,
6
5
,
66
6
6
33,
3
3
,
52,
5
2
,
60,
6
0
,
61,
6
1
,
62,
6
2
,
63,
6
3
,
64,
6
4
,
66
6
6
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
22,
2
2
,
25,
2
5
,
26,35,
2
6
,
3
5
,
36,
3
6
,
38,
3
8
,
39,
3
9
,
42,
4
2
,
option-selectable
o
p
t
i
o
n
-
s
e
l
e
c
t
a
b
l
e
software
s
o
f
t
w
a
r
e
5,
5
,
10,
1
0
,
48
4
8
44,
4
4
,
49,
4
9
,
53,
5
3
,
54,
5
4
,
55,
5
5
,
60,
6
0
,
64,
6
4
,
66
6
6
exhaustive
e
x
h
a
u
s
t
i
v
e
testing
t
e
s
t
i
n
g
63
6
3
part
p
a
r
t
number(ing)
n
u
m
b
e
r
(
i
n
g
)
36,
3
6
,
38,
3
8
,
50,
5
0
,
55
5
5
failure(s)
f
a
i
l
u
r
e
(
s
)
7,
7
,
8,
8
,
9,
9
,
21,
2
1
,
31,
3
1
,
32,
3
2
,
52,
5
2
,
55,
5
5
,
60
6
0
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
6,
6
,
9,
9
,
21,
2
1
,
28,
2
8
,
32,
3
2
,
48,
4
8
,
49,
4
9
,
52,
5
2
,
53,
5
3
,
55,
5
5
,
59,
5
9
,
60,
6
0
,
64
6
4
failure
f
a
i
l
u
r
e
condition(s)
c
o
n
d
i
t
i
o
n
(
s
)
5,
5
,
6,
6
,
7,
7
,
8,
8
,
9,
9
,
10,
1
0
,
11,
1
1
,
16,
1
6
,
21,
2
1
,
29,
2
9
,
48,
4
8
,
patch(es)
p
a
t
c
h
(
e
s
)
23
2
3
52,
5
2
,
58
5
8
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
category(ies)
c
a
t
e
g
o
r
y
(
i
e
s
)
6,
6
,
7,
7
,
8,
8
,
9,
9
,
10
1
0
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
16,
1
6
,
43,
4
3
,
45,
4
5
,
47,
4
7
,
48,
4
8
,
55,
5
5
,
57,
5
7
,
59,
5
9
,
60,
6
0
,
61,
6
1
,
62,
6
2
,
65,
6
5
,
66
6
6
fault(s)
f
a
u
l
t
(
s
)
6,
6
,
9,
9
,
10,
1
0
,
32
3
2
previously
p
r
e
v
i
o
u
s
l
y
developed
d
e
v
e
l
o
p
e
d
software
s
o
f
t
w
a
r
e
2,
2
,
13,
1
3
,
42,
4
2
,
48,
4
8
,
49,
4
9
,
54,
5
4
,
57,
5
7
,
59
5
9
fault
f
a
u
l
t
detection
d
e
t
e
c
t
i
o
n
6
6
problem
p
r
o
b
l
e
m
report(s)
r
e
p
o
r
t
(
s
)
36,
3
6
,
37,
3
7
,
42,
4
2
,
50,
5
0
,
54,
5
4
,
55,
5
5
,
66
6
6
fault
f
a
u
l
t
tolerance
t
o
l
e
r
a
n
c
e
6,
6
,
16,
1
6
,
17,
1
7
,
48
4
8
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
14,
1
4
,
36,
3
6
,
39,
3
9
,
41,
4
1
,
50,
5
0
,
51,
5
1
,
59,
5
9
,
66
6
6
field
f
i
e
l
d
loading
l
o
a
d
i
n
g
11,
1
1
,
38
3
8
product
p
r
o
d
u
c
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
10,
1
0
,
48,
4
8
,
59,
5
9
,
65,
6
5
,
66
6
6
field-loadable
f
i
e
l
d
-
l
o
a
d
a
b
l
e
software
s
o
f
t
w
a
r
e
5,
5
,
11,
1
1
,
32,
3
2
,
36,
3
6
,
48
4
8
programming
p
r
o
g
r
a
m
m
i
n
g
language(s)
l
a
n
g
u
a
g
e
(
s
)
16,
1
6
,
17,
1
7
,
49,
4
9
,
52,
5
2
,
58,
5
8
,
64,
6
4
,
65
6
5
formal
f
o
r
m
a
l
methods
m
e
t
h
o
d
s
62,
6
2
,
63
6
3
release,
r
e
l
e
a
s
e
,
37,
3
7
,
38,
3
8
,
39,
3
9
,
50,
5
0
,
54,
5
4
,
55
5
5
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
22,
2
2
,
37,
3
7
,
58
5
8
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
test(s)
t
e
s
t
(
s
)
(ing)
(
i
n
g
)
29,
2
9
,
31,
3
1
,
58
5
8
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
11,
1
1
,
19,
1
9
,
20,
2
0
,
23,
2
3
,
25,
2
5
,
26,
2
6
,
27,
2
7
,
28,
2
8
,
32,
3
2
,
51,
5
1
,
52,
5
2
,
60,
6
0
,
63
6
3
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
29,
2
9
,
30
3
0
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
environment
e
n
v
i
r
o
n
m
e
n
t
(s)
(
s
)
17,
1
7
,
23,
2
3
,
41,
4
1
,
48,
4
8
,
64
6
4
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
26,
2
6
,
29,
2
9
,
30,
3
0
,
33,
3
3
,
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan
P
l
a
n
16,
1
6
,
19,
1
9
,
20,
2
0
,
22,
2
2
,
48,
4
8
,
49
4
9
60
6
0
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
case(s)
c
a
s
e
(
s
)
30,
3
0
,
33,
3
3
,
64
6
4
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
process(es)
p
r
o
c
e
s
s
(
e
s
)
6,
6
,
13,
1
3
,
14,
1
4
,
15,
1
5
,
16,
1
6
,
18,
1
8
,
19,
1
9
,
23,
2
3
,
25,
2
5
,
26,
2
6
,
31,
3
1
,
41,
4
1
,
48,
4
8
,
55,
5
5
,
60,
6
0
,
61,
6
1
,
62,
6
2
,
63,
6
3
,
64
6
4
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process,
p
r
o
c
e
s
s
,
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process,
p
r
o
c
e
s
s
,
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
and
a
n
d
integration
i
n
t
e
g
r
a
t
i
o
n
process
p
r
o
c
e
s
s
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
33
3
3
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
standards
s
t
a
n
d
a
r
d
s
15,
1
5
,
17,
1
7
,
18,
1
8
,
25,
2
5
,
59
5
9
see
s
e
e
also
a
l
s
o
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards,
S
t
a
n
d
a
r
d
s
,
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards,
S
t
a
n
d
a
r
d
s
,
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards,
S
t
a
n
d
a
r
d
s
,
and
a
n
d
standards
s
t
a
n
d
a
r
d
s
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
testing
t
e
s
t
i
n
g
30,
3
0
,
31,
3
1
,
32,
3
2
,
33,
3
3
,
64
6
4
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools
t
o
o
l
s
17,
1
7
,
54,
5
4
,
58,
5
8
,
59,
5
9
,
60,
6
0
,
61,
6
1
,
65
6
5
see
s
e
e
see
s
e
e
also
a
l
s
o
testing.
t
e
s
t
i
n
g
.
also
a
l
s
o
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
retrieval
r
e
t
r
i
e
v
a
l
38,
3
8
,
39,
3
9
,
44,
4
4
,
47,
4
7
,
50
5
0
Software
S
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
a
t
i
o
n
testing
t
e
s
t
i
n
g
29,
2
9
,
31,
3
1
,
32
3
2
reverse
r
e
v
e
r
s
e
engineering
e
n
g
i
n
e
e
r
i
n
g
58
5
8
software
s
o
f
t
w
a
r
e
level(s)
l
e
v
e
l
(
s
)
2,
2
,
5,
5
,
6,
6
,
7,
7
,
8,
8
,
9,
9
,
11,
1
1
,
14,
1
4
,
15,
1
5
,
17,
1
7
,
19,
1
9
,
21,
2
1
,
25,
2
5
,
33,
3
3
,
35,
3
5
,
39,
3
9
,
41,
4
1
,
43,
4
3
,
45,
4
5
,
47,
4
7
,
48,
4
8
,
49,
4
9
,
52,
5
2
,
57,
5
7
,
58,
5
8
,
59,
5
9
,
60,
6
0
,
61,
6
1
,
62
6
2
review(s)
r
e
v
i
e
w
(
s
)
14,
1
4
,
15,
1
5
,
18,
1
8
,
25,
2
5
,
26,
2
6
,
27,
2
7
,
28,
2
8
,
29,
2
9
,
31,
3
1
,
35,
3
5
,
41,
4
1
,
42,
4
2
,
43,
4
3
,
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
1,
1
,
2,
2
,
6,
6
,
13,
1
3
,
14,
1
4
,
15,
1
5
,
16,
1
6
,
18,
1
8
,
35,
3
5
,
37,
3
7
,
41,
4
1
,
47,
4
7
,
48,
4
8
,
49,
4
9
,
51,
5
1
,
53,
5
3
,
55,
5
5
,
58,
5
8
,
60
6
0
43,
4
3
,
44,
4
4
,
45,
4
5
,
47,
4
7
,
48,
4
8
,
50,
5
0
,
51,
5
1
,
55,
5
5
,
58,
5
8
,
59
5
9
robustness
r
o
b
u
s
t
n
e
s
s
18,
1
8
,
30
3
0
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
8,
8
,
10,
1
0
,
16,
1
6
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
38,
3
8
,
39,
3
9
,
41,
4
1
,
42,
4
2
,
43,
4
3
,
47,
4
7
,
48,
4
8
,
56,
5
6
,
58,
5
8
,
61,
6
1
,
62
6
2
robustness
r
o
b
u
s
t
n
e
s
s
testing
t
e
s
t
i
n
g
and
a
n
d
test
t
e
s
t
cases
c
a
s
e
s
25,
2
5
,
31,
3
1
,
33,
3
3
,
61
6
1
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
15,
1
5
,
16,
1
6
,
39,
3
9
,
53
5
3
safety
s
a
f
e
t
y
monitoring
m
o
n
i
t
o
r
i
n
g
6,
6
,
8,
8
,
9,
9
,
10,
1
0
,
52
5
2
Software
S
o
f
t
w
a
r
e
Life
L
i
f
e
Cycle
C
y
c
l
e
Environment
E
n
v
i
r
o
n
m
e
n
t
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
(SECI)
(
S
E
C
I
)
39,
3
9
,
50,
5
0
,
53,
5
3
,
54
5
4
safety
s
a
f
e
t
y
objective
o
b
j
e
c
t
i
v
e
(s)
(
s
)
21,
2
1
,
28,
2
8
,
57,
5
7
,
58,
5
8
,
59,
5
9
,
62,
6
2
,
66
6
6
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
environment
e
n
v
i
r
o
n
m
e
n
t
control(s)
c
o
n
t
r
o
l
(
s
)
39,
3
9
,
50
5
0
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
6,
6
,
10,
1
0
,
16,
1
6
,
18,
1
8
,
19,
1
9
,
21,
2
1
,
27,
2
7
,
42,
4
2
,
52
5
2
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process(es)
p
r
o
c
e
s
s
(
e
s
)
1,
1
,
2,
2
,
5,
5
,
6,
6
,
9,
9
,
11,
1
1
,
13,
1
3
,
14,
1
4
,
15,
1
5
,
43,
4
3
,
45,
4
5
,
47,
4
7
,
48,
4
8
,
49,
4
9
,
50,
5
0
,
51,
5
1
,
54,
5
4
,
58,
5
8
,
59,
5
9
,
62
6
2
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process,
p
r
o
c
e
s
s
,
integral
i
n
t
e
g
r
a
l
processes,
p
r
o
c
e
s
s
e
s
,
and
a
n
d
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
scope
s
c
o
p
e
1,
1
,
9,
9
,
11,
1
1
,
32,
3
2
,
38,
3
8
,
51,
5
1
,
53,
5
3
,
66
6
6
software
s
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
38,
3
8
,
50
5
0
simu
s
i
m
u
lator(s)
l
a
t
o
r
(
s
)
18,
1
8
,
30,
3
0
,
49,
4
9
,
65
6
5
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
13,
1
3
,
15,
1
5
,
18,
1
8
,
19,
1
9
,
21,
2
1
,
22,
2
2
,
25,
2
5
,
35,
3
5
,
37,
3
7
,
39,
3
9
,
41,
4
1
,
43
4
3
Software
S
o
f
t
w
a
r
e
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
23,
2
3
,
43,
4
3
,
44,
4
4
,
45,
4
5
,
47,
4
7
,
55,
5
5
,
software
s
o
f
t
w
a
r
e
plans,
p
l
a
n
s
,
15,
1
5
,
16,
1
6
,
18,
1
8
,
36,
3
6
,
41,
4
1
,
42,
4
2
,
43,
4
3
,
45,
4
5
,
48,
4
8
,
54,
5
4
,
56,
5
6
,
61,
6
1
,
62
6
2
59,
5
9
,
62
6
2
see
s
e
e
also
a
l
s
o
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
Aspects
A
s
p
e
c
t
s
of
o
f
Certification,
C
e
r
t
i
f
i
c
a
t
i
o
n
,
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Plan,
P
l
a
n
,
Software,
S
o
f
t
w
a
r
e
,
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
Plan,
P
l
a
n
,
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
Plan
P
l
a
n
and
a
n
d
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
software
s
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
6,
6
,
19,
1
9
,
20,
2
0
,
21,
2
1
,
22,
2
2
,
25,
2
5
,
26,
2
6
,
28,
2
8
,
29,
2
9
,
32,
3
2
,
51,
5
1
,
software
s
o
f
t
w
a
r
e
product(s)
p
r
o
d
u
c
t
(
s
)
13,
1
3
,
16,
1
6
,
17,
1
7
,
18,
1
8
,
35,
3
5
,
36,
3
6
,
37,
3
7
,
38,
3
8
,
41,
4
1
,
42,
4
2
,
52,
5
2
,
57,
5
7
,
63,
6
3
,
64
6
4
47,
4
7
,
50,
5
0
,
51,
5
1
,
54,
5
4
,
58
5
8
software
s
o
f
t
w
a
r
e
changes
c
h
a
n
g
e
s
16,
1
6
,
37,
3
7
,
55
5
5
software
s
o
f
t
w
a
r
e
product
p
r
o
d
u
c
t
baseline
b
a
s
e
l
i
n
e
36,
3
6
,
42
4
2
see
s
e
e
also
a
l
s
o
modification
m
o
d
i
f
i
c
a
t
i
o
n
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
18,
1
8
,
22,
2
2
,
28,
2
8
,
48,
4
8
,
52,
5
2
,
64
6
4
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
(SQA)
(
S
Q
A
)
10,
1
0
,
41
4
1
software
s
o
f
t
w
a
r
e
coding
c
o
d
i
n
g
process
p
r
o
c
e
s
s
13,
1
3
,
17,
1
7
,
19,
1
9
,
21,
2
1
,
22,
2
2
,
28
2
8
software
s
o
f
t
w
a
r
e
component(s)
c
o
m
p
o
n
e
n
t
(
s
)
8,
8
,
9,
9
,
18,
1
8
,
26,
2
6
,
28,
2
8
,
29,
2
9
,
30,
3
0
,
32,
3
2
,
52,
5
2
,
53,
5
3
,
57,
5
7
,
59,
5
9
,
63,
6
3
,
66
6
6
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index
I
n
d
e
x
36,
3
6
,
38,
3
8
,
43,
4
3
,
44,
4
4
,
50,
5
0
,
54
5
4
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
(SCM)
(
S
C
M
)
Plan
P
l
a
n
16,
1
6
,
35,
3
5
,
41,
4
1
,
50
5
0
software
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
management
m
a
n
a
g
e
m
e
n
t
(SCM)
(
S
C
M
)
process
p
r
o
c
e
s
s
13,
1
3
,
16,
1
6
,
23,
2
3
,
35,
3
5
,
39,
3
9
,
50,
5
0
,
55,
5
5
,
59,
5
9
,
60
6
0
Software
S
o
f
t
w
a
r
e
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Management
M
a
n
a
g
e
m
e
n
t
(SCM)
(
S
C
M
)
Records
R
e
c
o
r
d
s
35,
3
5
,
55
5
5
software
s
o
f
t
w
a
r
e
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
42,
4
2
,
51,
5
1
,
55
5
5
software
s
o
f
t
w
a
r
e
data
d
a
t
a
loading
l
o
a
d
i
n
g
10,
1
0
,
53
5
3
software
s
o
f
t
w
a
r
e
design
d
e
s
i
g
n
process
p
r
o
c
e
s
s
6,
6
,
13,
1
3
,
17,
1
7
,
19,
1
9
,
20,
2
0
,
21,
2
1
,
22,
2
2
,
23,
2
3
,
27,
2
7
,
28,
2
8
,
53
5
3
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
18,
1
8
,
20,
2
0
,
21,
2
1
,
27,
2
7
,
28,
2
8
,
48,
4
8
,
51,
5
1
,
64
6
4
C-3
C
-
3
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
C-4
C
-
4
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
(SQA)
(
S
Q
A
)
Plan
P
l
a
n
16,
1
6
,
41,
4
1
,
51
5
1
system
s
y
s
t
e
m
life
l
i
f
e
cycle
c
y
c
l
e
process(es)
p
r
o
c
e
s
s
(
e
s
)
1,
1
,
5,
5
,
6,
6
,
19,
1
9
,
21,
2
1
,
48,
4
8
,
51
5
1
software
s
o
f
t
w
a
r
e
quality
q
u
a
l
i
t
y
assurance
a
s
s
u
r
a
n
c
e
(SQA)
(
S
Q
A
)
process
p
r
o
c
e
s
s
13,
1
3
,
16,
1
6
,
41,
4
1
,
system
s
y
s
t
e
m
requirement(s)
r
e
q
u
i
r
e
m
e
n
t
(
s
)
5,
5
,
6,
6
,
8,
8
,
9,
9
,
10,
1
0
,
13,
1
3
,
15,
1
5
,
17,
1
7
,
19,
1
9
,
20,
2
0
,
23,
2
3
,
42,
4
2
,
51,
5
1
,
55,
5
5
,
59,
5
9
,
60
6
0
25,
2
5
,
26,
2
6
,
27,
2
7
,
42,
4
2
,
52,
5
2
,
53,
5
3
,
60,
6
0
,
63,
6
3
,
66
6
6
Software
S
o
f
t
w
a
r
e
Quality
Q
u
a
l
i
t
y
Assurance
A
s
s
u
r
a
n
c
e
(SQA)
(
S
Q
A
)
Records
R
e
c
o
r
d
s
41,
4
1
,
55
5
5
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
6,
6
,
10,
1
0
,
11,
1
1
,
15,
1
5
,
16,
1
6
,
28,
2
8
,
59,
5
9
,
62,
6
2
,
66
6
6
software
s
o
f
t
w
a
r
e
reliability
r
e
l
i
a
b
i
l
i
t
y
8,
8
,
65
6
5
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
assessment
a
s
s
e
s
s
m
e
n
t
process
p
r
o
c
e
s
s
1,
1
,
5,
5
,
6,
6
,
7,
7
,
8,
8
,
9,
9
,
10,
1
0
,
11,
1
1
,
16,
1
6
,
17,
1
7
,
19,
1
9
,
20,
2
0
,
21,
2
1
,
29,
2
9
,
37,
3
7
,
41,
4
1
,
43,
4
3
,
45,
4
5
,
48,
4
8
,
57,
5
7
,
58
5
8
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
6,
6
,
10,
1
0
,
13,
1
3
,
19,
1
9
,
23,
2
3
,
25,
2
5
,
26,
2
6
,
27,
2
7
,
28,
2
8
,
system
s
y
s
t
e
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
5,
5
,
6,
6
,
11
1
1
29,
2
9
,
31,
3
1
,
32,
3
2
,
33,
3
3
,
42,
4
2
,
51,
5
1
,
57,
5
7
,
62,
6
2
,
64,
6
4
,
66
6
6
see
s
e
e
also
a
l
s
o
high-level
h
i
g
h
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
low-level
l
o
w
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
and
a
n
d
derived
d
e
r
i
v
e
d
requirements
r
e
q
u
i
r
e
m
e
n
t
s
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Data
D
a
t
a
19,
1
9
,
20,
2
0
,
44,
4
4
,
52,
5
2
,
61
6
1
task(s)(ing)
t
a
s
k
(
s
)
(
i
n
g
)
28,
2
8
,
51,
5
1
,
52,
5
2
,
53
5
3
software
s
o
f
t
w
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
process
p
r
o
c
e
s
s
13,
1
3
,
17,
1
7
,
19,
1
9
,
20,
2
0
,
21,
2
1
,
22,
2
2
,
test
t
e
s
t
case(s)
c
a
s
e
(
s
)
17,
1
7
,
26,
2
6
,
29,
2
9
,
30,
3
0
,
31,
3
1
,
32,
3
2
,
33,
3
3
,
49,
4
9
,
53,
5
3
,
63,
6
3
,
64
6
4
27
2
7
Software
S
o
f
t
w
a
r
e
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
18,
1
8
,
19,
1
9
,
20,
2
0
,
27,
2
7
,
48,
4
8
,
test
t
e
s
t
coverage
c
o
v
e
r
a
g
e
25
2
5
51,
5
1
,
64
6
4
software
s
o
f
t
w
a
r
e
testing
t
e
s
t
i
n
g
29,
2
9
,
30
3
0
test
t
e
s
t
coverage
c
o
v
e
r
a
g
e
analysis(es)
a
n
a
l
y
s
i
s
(
e
s
)
33,
3
3
,
64
6
4
see
s
e
e
also
a
l
s
o
testing
t
e
s
t
i
n
g
software
s
o
f
t
w
a
r
e
tools
t
o
o
l
s
57,
5
7
,
59
5
9
test
t
e
s
t
environment(s)
e
n
v
i
r
o
n
m
e
n
t
(
s
)
18,
1
8
,
26,
2
6
,
30,
3
0
,
31,
3
1
,
49,
4
9
,
54,
5
4
,
64
6
4
see
s
e
e
also
a
l
s
o
software
s
o
f
t
w
a
r
e
cycle
c
y
c
l
e
environment,
e
n
v
i
r
o
n
m
e
n
t
,
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
tools,
t
o
o
l
s
,
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools,
t
o
o
l
s
,
and
a
n
d
tools
t
o
o
l
s
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
5,
5
,
10,
1
0
,
11,
1
1
,
17,
1
7
,
26,
2
6
,
49,
4
9
,
64
6
4
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
26,
2
6
,
29,
2
9
,
33,
3
3
,
49,
4
9
,
53,
5
3
,
63
6
3
see
s
e
e
also
a
l
s
o
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Procedures
P
r
o
c
e
d
u
r
e
s
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Cases
C
a
s
e
s
and
a
n
d
Procedures
P
r
o
c
e
d
u
r
e
s
26,
2
6
,
53
5
3
test
t
e
s
t
result(s)
r
e
s
u
l
t
(
s
)
29,
2
9
,
49,
4
9
,
53,
5
3
,
58,
5
8
,
63
6
3
see
s
e
e
also
a
l
s
o
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results
R
e
s
u
l
t
s
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
16,
1
6
,
18,
1
8
,
25,
2
5
,
26,
2
6
,
49,
4
9
,
53
5
3
testing
t
e
s
t
i
n
g
18,
1
8
,
25,
2
5
,
29,
2
9
,
30,
3
0
,
31,
3
1
,
32,
3
2
,
33,
3
3
,
49,
4
9
,
54,
5
4
,
61,
6
1
,
62,
6
2
,
63
6
3
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Procedures
P
r
o
c
e
d
u
r
e
s
25,
2
5
,
26,
2
6
,
53
5
3
testing
t
e
s
t
i
n
g
method(s)
m
e
t
h
o
d
(
s
)
31,
3
1
,
32,
3
2
,
49
4
9
see
s
e
e
also
a
l
s
o
verification
v
e
r
i
f
i
c
a
t
i
o
n
methods
m
e
t
h
o
d
s
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
process
p
r
o
c
e
s
s
9,
9
,
10,
1
0
,
11,
1
1
,
13,
1
3
,
14,
1
4
,
16,
1
6
,
17,
1
7
,
timing
t
i
m
i
n
g
and
a
n
d
timing
t
i
m
i
n
g
analysis
a
n
a
l
y
s
i
s
28,
2
8
,
48,
4
8
,
52,
5
2
,
55,
5
5
,
57
5
7
18,
1
8
,
23,
2
3
,
25,
2
5
,
33,
3
3
,
49,
4
9
,
53,
5
3
,
58,
5
8
,
59,
5
9
,
60,
6
0
,
63,
6
3
,
64
6
4
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results
R
e
s
u
l
t
s
26,
2
6
,
53
5
3
tool(s)
t
o
o
l
(
s
)
6,
6
,
15,
1
5
,
16,
1
6
,
17,
1
7
,
18,
1
8
,
21,
2
1
,
39,
3
9
,
47,
4
7
,
49,
4
9
,
50,
5
0
,
51,
5
1
,
52,
5
2
,
54,
5
4
,
57,
5
7
,
see
s
e
e
also
a
l
s
o
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analysis,
a
n
a
l
y
s
i
s
,
coverage
c
o
v
e
r
a
g
e
analysis,
a
n
a
l
y
s
i
s
,
58,
5
8
,
59,
5
9
,
60,
6
0
,
61,
6
1
,
62,
6
2
,
65
6
5
test
t
e
s
t
results,
r
e
s
u
l
t
s
,
and
a
n
d
test
t
e
s
t
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
tools
t
o
o
l
s
54,
5
4
,
59,
5
9
,
61,
6
1
,
62
6
2
Tool
T
o
o
l
Operational
O
p
e
r
a
t
i
o
n
a
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
60,
6
0
,
61,
6
1
,
62
6
2
Source
S
o
u
r
c
e
Code
C
o
d
e
13,
1
3
,
17,
1
7
,
19,
1
9
,
20,
2
0
,
21,
2
1
,
22,
2
2
,
23,
2
3
,
25,
2
5
,
26,
2
6
,
28,
2
8
,
33,
3
3
,
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
2,
2
,
17,
1
7
,
48,
4
8
,
58,
5
8
,
59,
5
9
,
60,
6
0
,
61,
6
1
,
62,
6
2
,
65
6
5
42,
4
2
,
44,
4
4
,
52,
5
2
,
53
5
3
54,
5
4
,
59,
5
9
,
60,
6
0
,
64,
6
4
,
65
6
5
standards
s
t
a
n
d
a
r
d
s
1,
1
,
15,
1
5
,
16,
1
6
,
18,
1
8
,
22,
2
2
,
27,
2
7
,
28,
2
8
,
36,
3
6
,
41,
4
1
,
42,
4
2
,
48,
4
8
,
50,
5
0
,
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
data
d
a
t
a
54,
5
4
,
61
6
1
51,
5
1
,
52,
5
2
,
54,
5
4
,
56,
5
6
,
60
6
0
statement
s
t
a
t
e
m
e
n
t
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
55
5
5
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
61,
6
1
,
62
6
2
static
s
t
a
t
i
c
analyzer
a
n
a
l
y
z
e
r
59
5
9
traceability
t
r
a
c
e
a
b
i
l
i
t
y
6,
6
,
23,
2
3
,
26,
2
6
,
27,
2
7
,
28,
2
8
,
35,
3
5
,
36,
3
6
,
39,
3
9
,
49,
4
9
,
50,
5
0
,
59
5
9
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
29,
2
9
,
30,
3
0
,
33,
3
3
,
58
5
8
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analysis(es)
a
n
a
l
y
s
i
s
(
e
s
)
14,
1
4
,
26,
2
6
,
53,
5
3
,
57
5
7
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
17,
1
7
,
26,
2
6
,
29,
2
9
,
33,
3
3
,
61,
6
1
,
65
6
5
transition
t
r
a
n
s
i
t
i
o
n
criteria
c
r
i
t
e
r
i
a
13,
1
3
,
14,
1
4
,
15,
1
5
,
19,
1
9
,
20,
2
0
,
22,
2
2
,
41,
4
1
,
42,
4
2
,
48,
4
8
,
49,
4
9
,
50,
5
0
,
51
5
1
structure(s)
s
t
r
u
c
t
u
r
e
(
s
)
19,
1
9
,
28,
2
8
,
29,
2
9
,
33,
3
3
,
47,
4
7
,
51,
5
1
,
52
5
2
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
data
d
a
t
a
1
1
see
s
e
e
also
a
l
s
o
code
c
o
d
e
structure
s
t
r
u
c
t
u
r
e
system
s
y
s
t
e
m
architecture
a
r
c
h
i
t
e
c
t
u
r
e
8,
8
,
19
1
9
user-modifiable
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
5,
5
,
10,
1
0
,
21,
2
1
,
36,
3
6
,
48,
4
8
,
53
5
3
system
s
y
s
t
e
m
design
d
e
s
i
g
n
(process)
(
p
r
o
c
e
s
s
)
5,
5
,
6,
6
,
8,
8
,
9
9
validation
v
a
l
i
d
a
t
i
o
n
1
1
system
s
y
s
t
e
m
fault
f
a
u
l
t
coverage
c
o
v
e
r
a
g
e
10
1
0
verification
v
e
r
i
f
i
c
a
t
i
o
n
–
–
see
s
e
e
software
s
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
APPENDIX
A
P
P
E
N
D
I
X
D
D
IMPROVEMENT
I
M
P
R
O
V
E
M
E
N
T
SUGGESTION
S
U
G
G
E
S
T
I
O
N
FORM
F
O
R
M
D-1
D
-
1
Na
N
a
me:____________________________Company
m
e
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
C
o
m
p
a
n
y
Name:_____________________
N
a
m
e
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Address:______________________________________________________________
A
d
d
r
e
s
s
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
City:__________________
C
i
t
y
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
State,
S
t
a
t
e
,
Postal
P
o
s
t
a
l
Code,
C
o
d
e
,
Country:_______________________
C
o
u
n
t
r
y
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Phone:________________________________
P
h
o
n
e
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Date:__________________________
D
a
t
e
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Document:
D
o
c
u
m
e
n
t
:
DO-178/ED
D
O
-
1
7
8
/
E
D
-12
-
1
2
Revision
R
e
v
i
s
i
o
n
B
B
Sec:_________Page:________Line:__________
S
e
c
:
_
_
_
_
_
_
_
_
_
P
a
g
e
:
_
_
_
_
_
_
_
_
L
i
n
e
:
_
_
_
_
_
_
_
_
_
_
[
[
]
]
Documentation
D
o
c
u
m
e
n
t
a
t
i
o
n
error
e
r
r
o
r
(Format,
(
F
o
r
m
a
t
,
punctuation,
p
u
n
c
t
u
a
t
i
o
n
,
spelling)
s
p
e
l
l
i
n
g
)
[
[
]
]
Content
C
o
n
t
e
n
t
error
e
r
r
o
r
[
[
]
]
Enhancement
E
n
h
a
n
c
e
m
e
n
t
or
o
r
refinement
r
e
f
i
n
e
m
e
n
t
Rationale
R
a
t
i
o
n
a
l
e
(Describe
(
D
e
s
c
r
i
b
e
the
t
h
e
error
e
r
r
o
r
or
o
r
justification
j
u
s
t
i
f
i
c
a
t
i
o
n
for
f
o
r
enhancement):_____________________
e
n
h
a
n
c
e
m
e
n
t
)
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Proposed
P
r
o
p
o
s
e
d
change
c
h
a
n
g
e
(Attach
(
A
t
t
a
c
h
marked-up
m
a
r
k
e
d
-
u
p
text
t
e
x
t
or
o
r
proposed
p
r
o
p
o
s
e
d
rewrite):______________________
r
e
w
r
i
t
e
)
:
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Please
P
l
e
a
s
e
provide
p
r
o
v
i
d
e
any
a
n
y
general
g
e
n
e
r
a
l
comments
c
o
m
m
e
n
t
s
for
f
o
r
improvement
i
m
p
r
o
v
e
m
e
n
t
of
o
f
this
t
h
i
s
document:
d
o
c
u
m
e
n
t
:
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
________________________________________________________________________
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
_
Return
R
e
t
u
r
n
completed
c
o
m
p
l
e
t
e
d
form
f
o
r
m
to:
t
o
:
RTCA
R
T
C
A
Attention:
A
t
t
e
n
t
i
o
n
:
DO-178B
D
O
-
1
7
8
B
EUROCAE
E
U
R
O
C
A
E
1140
1
1
4
0
Connecticut
C
o
n
n
e
c
t
i
c
u
t
Ave.,
A
v
e
.
,
NW
N
W
Suite
S
u
i
t
e
1020
1
0
2
0
Attention:
A
t
t
e
n
t
i
o
n
:
Secretary-Genera
S
e
c
r
e
t
a
r
y
-
G
e
n
e
r
a
Washington,
W
a
s
h
i
n
g
t
o
n
,
D.C.
D
.
C
.
20036
2
0
0
3
6
USA
U
S
A
OR
O
R
17
1
7
Rue
R
u
e
Hamelin
H
a
m
e
l
i
n
Paris
P
a
r
i
s
Cedex
C
e
d
e
x
75783
7
5
7
8
3
France
F
r
a
n
c
e
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
THIS
T
H
I
S
PAGE
P
A
G
E
IS
I
S
INTENTIONALLY
I
N
T
E
N
T
I
O
N
A
L
L
Y
LEFT
L
E
F
T
BLANK.
B
L
A
N
K
.
000000FBFBFBE3E3E3797979AAAAAADDDDDD888888D6D6D6BDBDBD3333330E0E0E1C1C1C666666B2B2B2999999E9E9E9CCCCCC222222A0A0A0F3F3F36969697F7F7F4D4D4D3F3F3FC6C6C62828285F5F5B151515000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000FEFEFE
FBFBFBE3E3E3DDDDDDE9E9E9F3F3F30000001C1C1C2222223333333F3F3F6666665F5F5B797979888888999999CCCCCCD6D6D67F7F7FA0A0A06969692828284D4D4D1515150E0E0EBDBDBDB2B2B2C6C6C6AAAAAA000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
000000FEFEFE
0.00
0.00
0.00
0.00