phaed
2016-09-09T22:56:13-04:00
2016-09-09T22:56:13-04:00
Microsoft: Print To PDF
DO-178C.pdf
engines={image=false textcolor=true vector=false text=true} tetml={filename={D:\drim\repository\projects\drim_124_0\metadata\4\f\4f277decb8aa853d2bbc94c876f89af0\4f277decb8aa853d2bbc94c876f89af0.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
.
1150
1
1
5
0
18
1
8
th
t
h
Street,
S
t
r
e
e
t
,
NW,
N
W
,
Suite
S
u
i
t
e
910
9
1
0
Washington,
W
a
s
h
i
n
g
t
o
n
,
DC
D
C
20036-3816
2
0
0
3
6
-
3
8
1
6
USA
U
S
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
RTCA
R
T
C
A
DO-178C
D
O
-
1
7
8
C
Prepared
P
r
e
p
a
r
e
d
by:
b
y
:
SC-205
S
C
-
2
0
5
December
D
e
c
e
m
b
e
r
13,
1
3
,
2011
2
0
1
1
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
.
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
Internet:
I
n
t
e
r
n
e
t
:
www.rtca.org
w
w
w
.
r
t
c
a
.
o
r
g
Please
P
l
e
a
s
e
visit
v
i
s
i
t
the
t
h
e
RTCA
R
T
C
A
Online
O
n
l
i
n
e
Store
S
t
o
r
e
for
f
o
r
document
d
o
c
u
m
e
n
t
pricing
p
r
i
c
i
n
g
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
report
r
e
p
o
r
t
was
w
a
s
prepared
p
r
e
p
a
r
e
d
by
b
y
RTCA
R
T
C
A
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
205
2
0
5
(SC-205)
(
S
C
-
2
0
5
)
and
a
n
d
EUROCAE
E
U
R
O
C
A
E
Working
W
o
r
k
i
n
g
Group
G
r
o
u
p
71
7
1
(WG-71)
(
W
G
-
7
1
)
and
a
n
d
approved
a
p
p
r
o
v
e
d
by
b
y
the
t
h
e
RTCA
R
T
C
A
Program
P
r
o
g
r
a
m
Management
M
a
n
a
g
e
m
e
n
t
Committee
C
o
m
m
i
t
t
e
e
(PMC)
(
P
M
C
)
on
o
n
December
D
e
c
e
m
b
e
r
13,
1
3
,
2011.
2
0
1
1
.
RTCA,
R
T
C
A
,
Incorporated
I
n
c
o
r
p
o
r
a
t
e
d
is
i
s
a
a
not-for-profit
n
o
t
-
f
o
r
-
p
r
o
f
i
t
corporation
c
o
r
p
o
r
a
t
i
o
n
formed
f
o
r
m
e
d
to
t
o
advance
a
d
v
a
n
c
e
the
t
h
e
art
a
r
t
and
a
n
d
science
s
c
i
e
n
c
e
of
o
f
aviation
a
v
i
a
t
i
o
n
and
a
n
d
aviation
a
v
i
a
t
i
o
n
electronic
e
l
e
c
t
r
o
n
i
c
systems
s
y
s
t
e
m
s
for
f
o
r
the
t
h
e
benefit
b
e
n
e
f
i
t
of
o
f
the
t
h
e
public.
p
u
b
l
i
c
.
The
T
h
e
organization
o
r
g
a
n
i
z
a
t
i
o
n
functions
f
u
n
c
t
i
o
n
s
as
a
s
a
a
Federal
F
e
d
e
r
a
l
Advisory
A
d
v
i
s
o
r
y
Committee
C
o
m
m
i
t
t
e
e
and
a
n
d
develops
d
e
v
e
l
o
p
s
consensus-based
c
o
n
s
e
n
s
u
s
-
b
a
s
e
d
recommendations
r
e
c
o
m
m
e
n
d
a
t
i
o
n
s
on
o
n
contemporary
c
o
n
t
e
m
p
o
r
a
r
y
aviation
a
v
i
a
t
i
o
n
issues.
i
s
s
u
e
s
.
RTCA’s
R
T
C
A
’
s
objectives
o
b
j
e
c
t
i
v
e
s
include
i
n
c
l
u
d
e
but
b
u
t
are
a
r
e
not
n
o
t
limited
l
i
m
i
t
e
d
to:
t
o
:
coalescing
c
o
a
l
e
s
c
i
n
g
aviation
a
v
i
a
t
i
o
n
system
s
y
s
t
e
m
user
u
s
e
r
and
a
n
d
provider
p
r
o
v
i
d
e
r
technical
t
e
c
h
n
i
c
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
in
i
n
a
a
manner
m
a
n
n
e
r
that
t
h
a
t
helps
h
e
l
p
s
government
g
o
v
e
r
n
m
e
n
t
and
a
n
d
industry
i
n
d
u
s
t
r
y
meet
m
e
e
t
their
t
h
e
i
r
mutual
m
u
t
u
a
l
objectives
o
b
j
e
c
t
i
v
e
s
and
a
n
d
responsibilities;
r
e
s
p
o
n
s
i
b
i
l
i
t
i
e
s
;
analyzing
a
n
a
l
y
z
i
n
g
and
a
n
d
recommending
r
e
c
o
m
m
e
n
d
i
n
g
solutions
s
o
l
u
t
i
o
n
s
to
t
o
the
t
h
e
system
s
y
s
t
e
m
technical
t
e
c
h
n
i
c
a
l
issues
i
s
s
u
e
s
that
t
h
a
t
aviation
a
v
i
a
t
i
o
n
faces
f
a
c
e
s
as
a
s
it
i
t
continues
c
o
n
t
i
n
u
e
s
to
t
o
pursue
p
u
r
s
u
e
increased
i
n
c
r
e
a
s
e
d
safety,
s
a
f
e
t
y
,
system
s
y
s
t
e
m
capacity,
c
a
p
a
c
i
t
y
,
and
a
n
d
efficiency;
e
f
f
i
c
i
e
n
c
y
;
developing
d
e
v
e
l
o
p
i
n
g
consensus
c
o
n
s
e
n
s
u
s
on
o
n
the
t
h
e
application
a
p
p
l
i
c
a
t
i
o
n
of
o
f
pertinent
p
e
r
t
i
n
e
n
t
technology
t
e
c
h
n
o
l
o
g
y
to
t
o
fulfill
f
u
l
f
i
l
l
user
u
s
e
r
and
a
n
d
provider
p
r
o
v
i
d
e
r
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
including
i
n
c
l
u
d
i
n
g
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
minimum
m
i
n
i
m
u
m
operational
o
p
e
r
a
t
i
o
n
a
l
performance
p
e
r
f
o
r
m
a
n
c
e
standards
s
t
a
n
d
a
r
d
s
for
f
o
r
electronic
e
l
e
c
t
r
o
n
i
c
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
support
s
u
p
p
o
r
t
aviation;
a
v
i
a
t
i
o
n
;
and
a
n
d
assisting
a
s
s
i
s
t
i
n
g
in
i
n
developing
d
e
v
e
l
o
p
i
n
g
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
technical
t
e
c
h
n
i
c
a
l
material
m
a
t
e
r
i
a
l
upon
u
p
o
n
which
w
h
i
c
h
positions
p
o
s
i
t
i
o
n
s
for
f
o
r
the
t
h
e
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Civil
C
i
v
i
l
Aviation
A
v
i
a
t
i
o
n
Organization
O
r
g
a
n
i
z
a
t
i
o
n
and
a
n
d
the
t
h
e
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Telecommunication
T
e
l
e
c
o
m
m
u
n
i
c
a
t
i
o
n
Union
U
n
i
o
n
and
a
n
d
other
o
t
h
e
r
appropriate
a
p
p
r
o
p
r
i
a
t
e
international
i
n
t
e
r
n
a
t
i
o
n
a
l
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
can
c
a
n
be
b
e
based.
b
a
s
e
d
.
The
T
h
e
organization’s
o
r
g
a
n
i
z
a
t
i
o
n
’
s
recommendations
r
e
c
o
m
m
e
n
d
a
t
i
o
n
s
are
a
r
e
often
o
f
t
e
n
used
u
s
e
d
as
a
s
the
t
h
e
basis
b
a
s
i
s
for
f
o
r
government
g
o
v
e
r
n
m
e
n
t
and
a
n
d
private
p
r
i
v
a
t
e
sector
s
e
c
t
o
r
decisions
d
e
c
i
s
i
o
n
s
as
a
s
well
w
e
l
l
as
a
s
the
t
h
e
foundation
f
o
u
n
d
a
t
i
o
n
for
f
o
r
many
m
a
n
y
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
Technical
T
e
c
h
n
i
c
a
l
Standard
S
t
a
n
d
a
r
d
Orders.
O
r
d
e
r
s
.
Since
S
i
n
c
e
the
t
h
e
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
U.S.
U
.
S
.
government
g
o
v
e
r
n
m
e
n
t
organization
o
r
g
a
n
i
z
a
t
i
o
n
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
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Illustration
I
l
l
u
s
t
r
a
t
i
o
n
provided
p
r
o
v
i
d
e
d
by
b
y
Pat
P
a
t
Neilan,
N
e
i
l
a
n
,
UK
U
K
CAA
C
A
A
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
]
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
-
INTRODUCTION
I
N
T
R
O
D
U
C
T
I
O
N
.......................................................................................................................1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
Purpose
P
u
r
p
o
s
e
.......................................................................................................................1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
-
Scope
S
c
o
p
e
.......................................................................................................................1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
..................................................................................................2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
-
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
...........................................................................................................2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
-
Document
D
o
c
u
m
e
n
t
Overview.......................................................................................................................4
O
v
e
r
v
i
e
w
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
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..........................................7
D
E
V
E
L
O
P
M
E
N
T
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
2.1
2
.
1
System
S
y
s
t
e
m
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Allocation
A
l
l
o
c
a
t
i
o
n
to
t
o
Software................................................................................7
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
2.2
2
.
2
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
.....................................10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
2.2.1
2
.
2
.
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.........................................10
P
r
o
c
e
s
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
2.2.2
2
.
2
.
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.........................................10
P
r
o
c
e
s
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
2.2.3
2
.
2
.
3
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
Software
S
o
f
t
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
and
a
n
d
Hardware
H
a
r
d
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
............................11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
2.3
2
.
3
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
Software
S
o
f
t
w
a
r
e
Level..............................................................11
L
e
v
e
l
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
2.3.1
2
.
3
.
1
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
Errors
E
r
r
o
r
s
and
a
n
d
Failure
F
a
i
l
u
r
e
Conditions
C
o
n
d
i
t
i
o
n
s
............................................12
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
2
2.3.2
2
.
3
.
2
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
Categorization..........................................................................................13
C
a
t
e
g
o
r
i
z
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
3
2.3.3
2
.
3
.
3
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Definition.....................................................................................................14
D
e
f
i
n
i
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
4
2.3.4
2
.
3
.
4
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
..............................................................................................14
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
4
2.4
2
.
4
Architectural
A
r
c
h
i
t
e
c
t
u
r
a
l
Considerations........................................................................................................15
C
o
n
s
i
d
e
r
a
t
i
o
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
5
2.4.1
2
.
4
.
1
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
.....................................................................................................................15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
5
2.4.2
2
.
4
.
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..................................................................................16
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
6
2.4.3
2
.
4
.
3
Safety
S
a
f
e
t
y
Monitoring
M
o
n
i
t
o
r
i
n
g
.................................................................................................................16
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
6
2.5
2
.
5
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
Life
L
i
f
e
Cycle
C
y
c
l
e
Processes
P
r
o
c
e
s
s
e
s
...........................................................17
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
7
2.5.1
2
.
5
.
1
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Items
I
t
e
m
s
............................................................................................................17
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
7
2.5.2
2
.
5
.
2
User-Modifiable
U
s
e
r
-
M
o
d
i
f
i
a
b
l
e
Software.....................................................................................................18
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
8
2.5.3
2
.
5
.
3
Commercial-Off-The-Shelf
C
o
m
m
e
r
c
i
a
l
-
O
f
f
-
T
h
e
-
S
h
e
l
f
Software
S
o
f
t
w
a
r
e
...................................................................................19
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
2.5.4
2
.
5
.
4
Option-Selectable
O
p
t
i
o
n
-
S
e
l
e
c
t
a
b
l
e
Software...................................................................................................19
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
2.5.5
2
.
5
.
5
Field-Loadable
F
i
e
l
d
-
L
o
a
d
a
b
l
e
Software.......................................................................................................19
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
9
2.5.6
2
.
5
.
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
..................................................................20
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
0
2.6
2
.
6
System
S
y
s
t
e
m
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
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
...........................................................20
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
0
3.0
3
.
0
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE.............................................................................................................21
C
Y
C
L
E
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
1
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
.....................................................................................................21
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
1
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
....................................................................................................21
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
1
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.........................................................................................22
P
r
o
c
e
s
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
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
............................................................................................25
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
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
O
b
j
e
c
t
i
v
e
s
.........................................................................................25
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
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...........................................................................................25
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
5
4.3
4
.
3
Software
S
o
f
t
w
a
r
e
Plans
P
l
a
n
s
.....................................................................................................................26
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
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.................................................................................27
P
l
a
n
n
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
7
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....................................................................................28
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
8
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
...............................................................................28
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
8
4.4.3
4
.
4
.
3
Software
S
o
f
t
w
a
r
e
Test
T
e
s
t
Environment...................................................................................................29
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
9
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
S
t
a
n
d
a
r
d
s
................................................................................................29
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
9
4.6
4
.
6
Review
R
e
v
i
e
w
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....................................................................................30
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
0
i
i
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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...............................................................................31
P
R
O
C
E
S
S
E
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
1
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
...................................................................................................32
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
2
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..........................................................................32
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
2
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............................................................................32
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
2
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
..............................................................................................................33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
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.....................................................................................33
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
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
......................................................................................33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
3
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..............................................................................34
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
4
5.2.4
5
.
2
.
4
Designing
D
e
s
i
g
n
i
n
g
for
f
o
r
Deactivated
D
e
a
c
t
i
v
a
t
e
d
Code
C
o
d
e
...........................................................................................34
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
4
5.3
5
.
3
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
Process..............................................................................................................35
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
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
....................................................................................35
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
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......................................................................................35
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
5.4
5
.
4
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
.....................................................................................................................35
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
5
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..............................................................................................36
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
6
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................................................................................................36
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
6
5.5
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
Traceability................................................................................37
T
r
a
c
e
a
b
i
l
i
t
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
7
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.....................................................................................39
P
R
O
C
E
S
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
9
6.1
6
.
1
Purpose
P
u
r
p
o
s
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
.................................................................................................39
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3
9
6.2
6
.
2
Overview
O
v
e
r
v
i
e
w
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.................................................................40
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
0
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...................................................................................................41
A
n
a
l
y
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
1
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
High-Level
H
i
g
h
-
L
e
v
e
l
Requirements............................................................41
R
e
q
u
i
r
e
m
e
n
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
1
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
Low-Level
L
o
w
-
L
e
v
e
l
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
............................................................42
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
2
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
Software
S
o
f
t
w
a
r
e
Architecture..................................................................42
A
r
c
h
i
t
e
c
t
u
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
2
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
Source
S
o
u
r
c
e
Code.................................................................................43
C
o
d
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
3
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.........................................44
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
4
6.4
6
.
4
Software
S
o
f
t
w
a
r
e
Testing
T
e
s
t
i
n
g
.....................................................................................................................44
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
4
6.4.1
6
.
4
.
1
Test
T
e
s
t
Environment..................................................................................................................46
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
6
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
Selection......................................................................................46
S
e
l
e
c
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
6
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..............................................................................................46
C
a
s
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
6
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
...................................................................................................47
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
7
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..................................................................................47
M
e
t
h
o
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
7
6.4.4
6
.
4
.
4
Test
T
e
s
t
Coverage
C
o
v
e
r
a
g
e
Analysis.........................................................................................................49
A
n
a
l
y
s
i
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
9
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
...............................................................49
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
9
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.........................................................................................49
A
n
a
l
y
s
i
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
9
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
......................................................................50
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
0
6.4.5
6
.
4
.
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
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............................................51
R
e
s
u
l
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1
6.5
6
.
5
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
Traceability..................................................................................51
T
r
a
c
e
a
b
i
l
i
t
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1
6.6
6
.
6
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Items...........................................................................................51
I
t
e
m
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
1
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
..................................................53
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
3
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
...........................................................53
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
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.............................................................54
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
4
7.2.1
7
.
2
.
1
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Identification..................................................................................................54
I
d
e
n
t
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
4
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
....................................................................................................55
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
5
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
..........................................................55
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
5
7.2.4
7
.
2
.
4
Change
C
h
a
n
g
e
Control
C
o
n
t
r
o
l
.....................................................................................................................56
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
6
7.2.5
7
.
2
.
5
Change
C
h
a
n
g
e
Review
R
e
v
i
e
w
.....................................................................................................................56
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
6
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..........................................................................................56
A
c
c
o
u
n
t
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
6
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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}
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
............................................................................................57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
7
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
...............................................................................................................58
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
8
7.4
7
.
4
Software
S
o
f
t
w
a
r
e
Load
L
o
a
d
Control
C
o
n
t
r
o
l
.................................................................................................................58
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
8
7.5
7
.
5
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...................................................................................59
C
o
n
t
r
o
l
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
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
......................................................................61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
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..........................................................................61
O
b
j
e
c
t
i
v
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
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
...........................................................................61
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
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.......................................................................................................62
R
e
v
i
e
w
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
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
P
R
O
C
E
S
S
........................................................................................65
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
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.............................................................................................65
P
l
a
n
n
i
n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
9.2
9
.
2
Compliance
C
o
m
p
l
i
a
n
c
e
Substantiation...........................................................................................................65
S
u
b
s
t
a
n
t
i
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
5
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
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.................................66
A
u
t
h
o
r
i
t
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
6
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
......................................................................66
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
6
10.0
1
0
.
0
OVERVIEW
O
V
E
R
V
I
E
W
OF
O
F
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
PROCESS
P
R
O
C
E
S
S
.........................................................................67
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
7
10.1
1
0
.
1
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Basis.....................................................................................................................67
B
a
s
i
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
7
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.............................................................................................67
C
e
r
t
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
7
10.3
1
0
.
3
Compliance
C
o
m
p
l
i
a
n
c
e
Determination.......................................................................................................67
D
e
t
e
r
m
i
n
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
7
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.............................................................................................69
D
A
T
A
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6
9
11.1
1
1
.
1
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
...............................................................................70
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
0
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
P
l
a
n
.....................................................................................................71
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
1
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........................................................................................................71
P
l
a
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
Plan...............................................................................72
P
l
a
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
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
Plan
P
l
a
n
.............................................................................................73
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
3
-
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
............................................................................................74
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
4
-
Software
S
o
f
t
w
a
r
e
Design
D
e
s
i
g
n
Standards.......................................................................................................74
S
t
a
n
d
a
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
4
-
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards..........................................................................................................75
S
t
a
n
d
a
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
5
-
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
....................................................................................................75
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
5
-
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
...................................................................................................................75
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
5
-
Source
S
o
u
r
c
e
Code
C
o
d
e
.....................................................................................................................76
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
6
-
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code............................................................................................................76
C
o
d
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
6
-
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............................................................................76
P
r
o
c
e
d
u
r
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
6
-
Software
S
o
f
t
w
a
r
e
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Results...................................................................................................77
R
e
s
u
l
t
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
7
-
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...........................................................77
I
n
d
e
x
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
7
-
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
..................................................................................................77
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
7
-
Problem
P
r
o
b
l
e
m
Reports
R
e
p
o
r
t
s
.....................................................................................................................78
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
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
Records.........................................................................78
R
e
c
o
r
d
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
8
-
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
.......................................................................................79
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
9
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
.......................................................................................79
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
9
11.21
1
1
.
2
1
Trace
T
r
a
c
e
Data
D
a
t
a
.....................................................................................................................80
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
0
11.22
1
1
.
2
2
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
..........................................................................................................80
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
0
12.0
1
2
.
0
ADDITIONAL
A
D
D
I
T
I
O
N
A
L
CONSIDERATIONS..........................................................................................81
C
O
N
S
I
D
E
R
A
T
I
O
N
S
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
1
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
....................................................................................81
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
1
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.................................................................81
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
1
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..............................................................................................81
I
n
s
t
a
l
l
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
1
iii
i
i
i
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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..........................................................82
E
n
v
i
r
o
n
m
e
n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
2
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......................................................................................83
B
a
s
e
l
i
n
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
3
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
..........................................................84
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
4
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.........................................................................84
C
o
n
s
i
d
e
r
a
t
i
o
n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
4
12.2
1
2
.
2
Tool
T
o
o
l
Qualification.....................................................................................................................84
Q
u
a
l
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
4
12.2.1
1
2
.
2
.
1
Determining
D
e
t
e
r
m
i
n
i
n
g
if
i
f
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
is
i
s
Needed........................................................................84
N
e
e
d
e
d
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
4
12.2.2
1
2
.
2
.
2
Determining
D
e
t
e
r
m
i
n
i
n
g
the
t
h
e
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Level............................................................................85
L
e
v
e
l
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
5
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
Process....................................................................................................85
P
r
o
c
e
s
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
5
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
.................................................................................................................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
86
8
6
12.3.1
1
2
.
3
.
1
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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
86
8
6
12.3.2
1
2
.
3
.
2
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
...............................86
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
6
12.3.2.1
1
2
.
3
.
2
.
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
...............................................87
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
7
12.3.2.2
1
2
.
3
.
2
.
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
.......................................................................88
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
8
12.3.2.3
1
2
.
3
.
2
.
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..................................................................88
V
e
r
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
8
12.3.2.4
1
2
.
3
.
2
.
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.......................................88
S
o
f
t
w
a
r
e
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
8
12.3.2.5
1
2
.
3
.
2
.
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
............................................................................88
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
8
12.3.3
1
2
.
3
.
3
Software
S
o
f
t
w
a
r
e
Reliability
R
e
l
i
a
b
i
l
i
t
y
Models..................................................................................................89
M
o
d
e
l
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
9
12.3.4
1
2
.
3
.
4
Product
P
r
o
d
u
c
t
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
........................................................................................................89
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
9
12.3.4.1
1
2
.
3
.
4
.
1
Relevance
R
e
l
e
v
a
n
c
e
of
o
f
Service
S
e
r
v
i
c
e
History.........................................................................................90
H
i
s
t
o
r
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
0
12.3.4.2
1
2
.
3
.
4
.
2
Sufficiency
S
u
f
f
i
c
i
e
n
c
y
of
o
f
Accumulated
A
c
c
u
m
u
l
a
t
e
d
Service
S
e
r
v
i
c
e
History.................................................................91
H
i
s
t
o
r
y
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
1
12.3.4.3
1
2
.
3
.
4
.
3
Collection,
C
o
l
l
e
c
t
i
o
n
,
Reporting,
R
e
p
o
r
t
i
n
g
,
and
a
n
d
Analysis
A
n
a
l
y
s
i
s
of
o
f
Problems
P
r
o
b
l
e
m
s
Found
F
o
u
n
d
During
D
u
r
i
n
g
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
........91
.
.
.
.
.
.
.
.
9
1
12.3.4.4
1
2
.
3
.
4
.
4
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
Information
I
n
f
o
r
m
a
t
i
o
n
to
t
o
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...................................................................................................................92
C
e
r
t
i
f
i
c
a
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
2
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..............................95
L
E
V
E
L
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
5
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
T
E
R
M
S
..................................................................107
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
7
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
DO-178/ED-12
D
O
-
1
7
8
/
E
D
-
1
2
DOCUMENT
D
O
C
U
M
E
N
T
...................................................A-1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
A
-
1
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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}
LIST
L
I
S
T
OF
O
F
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
...................................................................................................................5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
Figure
F
i
g
u
r
e
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
....................................9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
Figure
F
i
g
u
r
e
2-2
2
-
2
Sequence
S
e
q
u
e
n
c
e
of
o
f
Events
E
v
e
n
t
s
for
f
o
r
Software
S
o
f
t
w
a
r
e
Error
E
r
r
o
r
Leading
L
e
a
d
i
n
g
to
t
o
a
a
Failure
F
a
i
l
u
r
e
Condition...................................12
C
o
n
d
i
t
i
o
n
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
2
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.......................22
S
e
q
u
e
n
c
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
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
Activities.......................................................................................................45
A
c
t
i
v
i
t
i
e
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4
5
LIST
L
I
S
T
OF
O
F
TABLES
T
A
B
L
E
S
Table
T
a
b
l
e
2-1
2
-
1
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
Descriptions
D
e
s
c
r
i
p
t
i
o
n
s
...................................................................................13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
3
Table
T
a
b
l
e
7-1
7
-
1
SCM
S
C
M
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
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....................................................58
D
a
t
a
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5
8
Table
T
a
b
l
e
12-1
1
2
-
1
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Level
L
e
v
e
l
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
..................................................................................85
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
5
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
........................................................................................................96
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
6
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
..............................................................................................97
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
7
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
......................................................98
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
8
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
.................................................................99
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9
9
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
....................................100
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
0
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
...............................................................................101
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
1
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
...........................................................................102
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
2
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
........................................................................103
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
3
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
.......................................................................................104
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
4
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
.................................................................................................105
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
0
5
v
v
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
INTRODUCTION
I
N
T
R
O
D
U
C
T
I
O
N
-
Purpose
P
u
r
p
o
s
e
-
Scope
S
c
o
p
e
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
Certification",
C
e
r
t
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
provides
p
r
o
v
i
d
e
s
the
t
h
e
background
b
a
c
k
g
r
o
u
n
d
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
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
guidance
g
u
i
d
a
n
c
e
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
.
This
T
h
i
s
guidance
g
u
i
d
a
n
c
e
includes:
i
n
c
l
u
d
e
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
processes.
p
r
o
c
e
s
s
e
s
.
Activities
A
c
t
i
v
i
t
i
e
s
that
t
h
a
t
provide
p
r
o
v
i
d
e
a
a
means
m
e
a
n
s
for
f
o
r
satisfying
s
a
t
i
s
f
y
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
in
i
n
the
t
h
e
form
f
o
r
m
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
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
.
Variations
V
a
r
i
a
t
i
o
n
s
in
i
n
the
t
h
e
objectives,
o
b
j
e
c
t
i
v
e
s
,
independence,
i
n
d
e
p
e
n
d
e
n
c
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
,
and
a
n
d
control
c
o
n
t
r
o
l
categories
c
a
t
e
g
o
r
i
e
s
by
b
y
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
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
(for
(
f
o
r
example,
e
x
a
m
p
l
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
)
that
t
h
a
t
are
a
r
e
applicable
a
p
p
l
i
c
a
b
l
e
to
t
o
certain
c
e
r
t
a
i
n
applications.
a
p
p
l
i
c
a
t
i
o
n
s
.
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
terms
t
e
r
m
s
provided
p
r
o
v
i
d
e
d
in
i
n
the
t
h
e
glossary.
g
l
o
s
s
a
r
y
.
In
I
n
addition
a
d
d
i
t
i
o
n
to
t
o
guidance,
g
u
i
d
a
n
c
e
,
supporting
s
u
p
p
o
r
t
i
n
g
information
i
n
f
o
r
m
a
t
i
o
n
is
i
s
provided
p
r
o
v
i
d
e
d
to
t
o
assist
a
s
s
i
s
t
the
t
h
e
reader’s
r
e
a
d
e
r
’
s
understanding.
u
n
d
e
r
s
t
a
n
d
i
n
g
.
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
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
,
engines,
e
n
g
i
n
e
s
,
propellers
p
r
o
p
e
l
l
e
r
s
and,
a
n
d
,
by
b
y
region,
r
e
g
i
o
n
,
auxiliary
a
u
x
i
l
i
a
r
y
power
p
o
w
e
r
units.
u
n
i
t
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
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
is
i
s
not
n
o
t
intended.
i
n
t
e
n
d
e
d
.
The
T
h
e
guidance
g
u
i
d
a
n
c
e
contained
c
o
n
t
a
i
n
e
d
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
does
d
o
e
s
not
n
o
t
define
d
e
f
i
n
e
or
o
r
imply
i
m
p
l
y
the
t
h
e
level
l
e
v
e
l
of
o
f
involvement
i
n
v
o
l
v
e
m
e
n
t
of
o
f
a
a
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
in
i
n
a
a
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
process.
p
r
o
c
e
s
s
.
To
T
o
understand
u
n
d
e
r
s
t
a
n
d
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
involvement,
i
n
v
o
l
v
e
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
refer
r
e
f
e
r
to
t
o
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
issued
i
s
s
u
e
d
by
b
y
the
t
h
e
relevant
r
e
l
e
v
a
n
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
2
2
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
attempt
a
t
t
e
m
p
t
to
t
o
define
d
e
f
i
n
e
firmware.
f
i
r
m
w
a
r
e
.
Firmware
F
i
r
m
w
a
r
e
should
s
h
o
u
l
d
be
b
e
classified
c
l
a
s
s
i
f
i
e
d
as
a
s
hardware
h
a
r
d
w
a
r
e
or
o
r
software
s
o
f
t
w
a
r
e
and
a
n
d
addressed
a
d
d
r
e
s
s
e
d
by
b
y
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
processes.
p
r
o
c
e
s
s
e
s
.
This
T
h
i
s
document
d
o
c
u
m
e
n
t
assumes
a
s
s
u
m
e
s
that
t
h
a
t
during
d
u
r
i
n
g
the
t
h
e
system
s
y
s
t
e
m
definition,
d
e
f
i
n
i
t
i
o
n
,
functions
f
u
n
c
t
i
o
n
s
have
h
a
v
e
been
b
e
e
n
allocated
a
l
l
o
c
a
t
e
d
to
t
o
either
e
i
t
h
e
r
software
s
o
f
t
w
a
r
e
or
o
r
hardware.
h
a
r
d
w
a
r
e
.
Other
O
t
h
e
r
documents
d
o
c
u
m
e
n
t
s
exist
e
x
i
s
t
that
t
h
a
t
provide
p
r
o
v
i
d
e
guidance
g
u
i
d
a
n
c
e
for
f
o
r
development
d
e
v
e
l
o
p
m
e
n
t
assurance
a
s
s
u
r
a
n
c
e
for
f
o
r
functions
f
u
n
c
t
i
o
n
s
that
t
h
a
t
are
a
r
e
allocated
a
l
l
o
c
a
t
e
d
to
t
o
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
in
i
n
hardware.
h
a
r
d
w
a
r
e
.
This
T
h
i
s
document
d
o
c
u
m
e
n
t
provides
p
r
o
v
i
d
e
s
guidance
g
u
i
d
a
n
c
e
for
f
o
r
functions
f
u
n
c
t
i
o
n
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
.
Note:
N
o
t
e
:
This
T
h
i
s
allows
a
l
l
o
w
s
an
a
n
efficient
e
f
f
i
c
i
e
n
t
method
m
e
t
h
o
d
of
o
f
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
and
a
n
d
development
d
e
v
e
l
o
p
m
e
n
t
assurance
a
s
s
u
r
a
n
c
e
to
t
o
be
b
e
determined
d
e
t
e
r
m
i
n
e
d
at
a
t
the
t
h
e
time
t
i
m
e
the
t
h
e
system
s
y
s
t
e
m
is
i
s
specified
s
p
e
c
i
f
i
e
d
and
a
n
d
functions
f
u
n
c
t
i
o
n
s
allocated.
a
l
l
o
c
a
t
e
d
.
All
A
l
l
parties
p
a
r
t
i
e
s
should
s
h
o
u
l
d
agree
a
g
r
e
e
with
w
i
t
h
this
t
h
i
s
system
s
y
s
t
e
m
decision
d
e
c
i
s
i
o
n
at
a
t
the
t
h
e
time
t
i
m
e
the
t
h
e
allocation
a
l
l
o
c
a
t
i
o
n
is
i
s
made.
m
a
d
e
.
Matters
M
a
t
t
e
r
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
commercial
c
o
m
m
e
r
c
i
a
l
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
,
and
a
n
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
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
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
It
I
t
is
i
s
recognized
r
e
c
o
g
n
i
z
e
d
that
t
h
a
t
projects
p
r
o
j
e
c
t
s
may
m
a
y
be
b
e
obliged,
o
b
l
i
g
e
d
,
through
t
h
r
o
u
g
h
contract
c
o
n
t
r
a
c
t
or
o
r
other
o
t
h
e
r
means,
m
e
a
n
s
,
to
t
o
comply
c
o
m
p
l
y
with
w
i
t
h
additional
a
d
d
i
t
i
o
n
a
l
standards
s
t
a
n
d
a
r
d
s
as
a
s
applied
a
p
p
l
i
e
d
by,
b
y
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
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
.
Such
S
u
c
h
standards
s
t
a
n
d
a
r
d
s
should
s
h
o
u
l
d
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
by
b
y
the
t
h
e
planning
p
l
a
n
n
i
n
g
process
p
r
o
c
e
s
s
and
a
n
d
considered,
c
o
n
s
i
d
e
r
e
d
,
as
a
s
appropriate,
a
p
p
r
o
p
r
i
a
t
e
,
when
w
h
e
n
applying
a
p
p
l
y
i
n
g
supplier
s
u
p
p
l
i
e
r
oversight.
o
v
e
r
s
i
g
h
t
.
-
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
The
T
h
e
following
f
o
l
l
o
w
i
n
g
points
p
o
i
n
t
s
should
s
h
o
u
l
d
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
:
-
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
denote
d
e
n
o
t
e
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
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
product
p
r
o
d
u
c
t
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
an
a
n
aircraft,
a
i
r
c
r
a
f
t
,
engine).
e
n
g
i
n
e
)
.
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
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
guidance
g
u
i
d
a
n
c
e
herein
h
e
r
e
i
n
is
i
s
not
n
o
t
mandated
m
a
n
d
a
t
e
d
by
b
y
law,
l
a
w
,
but
b
u
t
represents
r
e
p
r
e
s
e
n
t
s
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
.
-
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
as
a
s
a
a
means
m
e
a
n
s
of
o
f
compliance,
c
o
m
p
l
i
a
n
c
e
,
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
satisfy
s
a
t
i
s
f
y
all
a
l
l
applicable
a
p
p
l
i
c
a
b
l
e
objectives.
o
b
j
e
c
t
i
v
e
s
.
This
T
h
i
s
document
d
o
c
u
m
e
n
t
should
s
h
o
u
l
d
apply
a
p
p
l
y
to
t
o
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
and
a
n
d
any
a
n
y
of
o
f
its
i
t
s
suppliers,
s
u
p
p
l
i
e
r
s
,
who
w
h
o
are
a
r
e
involved
i
n
v
o
l
v
e
d
with
w
i
t
h
any
a
n
y
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
or
o
r
the
t
h
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
outputs
o
u
t
p
u
t
s
of
o
f
those
t
h
o
s
e
processes
p
r
o
c
e
s
s
e
s
described
d
e
s
c
r
i
b
e
d
herein.
h
e
r
e
i
n
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
is
i
s
responsible
r
e
s
p
o
n
s
i
b
l
e
for
f
o
r
oversight
o
v
e
r
s
i
g
h
t
of
o
f
all
a
l
l
of
o
f
its
i
t
s
suppliers.
s
u
p
p
l
i
e
r
s
.
3
3
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
plan
p
l
a
n
a
a
set
s
e
t
of
o
f
activities
a
c
t
i
v
i
t
i
e
s
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
.
This
T
h
i
s
document
d
o
c
u
m
e
n
t
describes
d
e
s
c
r
i
b
e
s
activities
a
c
t
i
v
i
t
i
e
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
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
may
m
a
y
plan
p
l
a
n
and,
a
n
d
,
subject
s
u
b
j
e
c
t
to
t
o
the
t
h
e
approval
a
p
p
r
o
v
a
l
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
,
adopt
a
d
o
p
t
alternative
a
l
t
e
r
n
a
t
i
v
e
activities
a
c
t
i
v
i
t
i
e
s
to
t
o
those
t
h
o
s
e
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
applicant
a
p
p
l
i
c
a
n
t
may
m
a
y
also
a
l
s
o
plan
p
l
a
n
and
a
n
d
conduct
c
o
n
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
that
t
h
a
t
are
a
r
e
determined
d
e
t
e
r
m
i
n
e
d
to
t
o
be
b
e
necessary.
n
e
c
e
s
s
a
r
y
.
-
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
address
a
d
d
r
e
s
s
any
a
n
y
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
in
i
n
its
i
t
s
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
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
perform
p
e
r
f
o
r
m
the
t
h
e
planned
p
l
a
n
n
e
d
activities
a
c
t
i
v
i
t
i
e
s
and
a
n
d
provide
p
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
e
as
a
s
indicated
i
n
d
i
c
a
t
e
d
in
i
n
section
s
e
c
t
i
o
n
11
1
1
to
t
o
substantiate
s
u
b
s
t
a
n
t
i
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
.
-
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
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
provides
p
r
o
v
i
d
e
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
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
.
-
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
,
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
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
project.
p
r
o
j
e
c
t
.
-
Annex
A
n
n
e
x
A
A
specifies
s
p
e
c
i
f
i
e
s
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
,
activities,
a
c
t
i
v
i
t
i
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
data
d
a
t
a
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
as
a
s
well
w
e
l
l
as
a
s
the
t
h
e
variation
v
a
r
i
a
t
i
o
n
in
i
n
the
t
h
e
independence
i
n
d
e
p
e
n
d
e
n
c
e
and
a
n
d
control
c
o
n
t
r
o
l
categories
c
a
t
e
g
o
r
i
e
s
for
f
o
r
each
e
a
c
h
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
In
I
n
order
o
r
d
e
r
to
t
o
fully
f
u
l
l
y
understand
u
n
d
e
r
s
t
a
n
d
the
t
h
e
guidance,
g
u
i
d
a
n
c
e
,
the
t
h
e
full
f
u
l
l
body
b
o
d
y
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
considered.
c
o
n
s
i
d
e
r
e
d
.
-
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
guidance
g
u
i
d
a
n
c
e
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
.
In
I
n
these
t
h
e
s
e
cases,
c
a
s
e
s
,
the
t
h
e
examples
e
x
a
m
p
l
e
s
are
a
r
e
considered
c
o
n
s
i
d
e
r
e
d
supporting
s
u
p
p
o
r
t
i
n
g
information.
i
n
f
o
r
m
a
t
i
o
n
.
-
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
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
are
a
r
e
supporting
s
u
p
p
o
r
t
i
n
g
information
i
n
f
o
r
m
a
t
i
o
n
used
u
s
e
d
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
.
-
Major
M
a
j
o
r
sections
s
e
c
t
i
o
n
s
are
a
r
e
numbered
n
u
m
b
e
r
e
d
as
a
s
X.0
X
.
0
throughout
t
h
r
o
u
g
h
o
u
t
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
It
I
t
should
s
h
o
u
l
d
be
b
e
noted
n
o
t
e
d
that
t
h
a
t
references
r
e
f
e
r
e
n
c
e
s
to
t
o
an
a
n
entire
e
n
t
i
r
e
section
s
e
c
t
i
o
n
are
a
r
e
identified
i
d
e
n
t
i
f
i
e
d
as
a
s
“section
“
s
e
c
t
i
o
n
X”;
X
”
;
whereas,
w
h
e
r
e
a
s
,
references
r
e
f
e
r
e
n
c
e
s
to
t
o
the
t
h
e
content
c
o
n
t
e
n
t
between
b
e
t
w
e
e
n
section
s
e
c
t
i
o
n
headers
h
e
a
d
e
r
s
X.0
X
.
0
and
a
n
d
X.1
X
.
1
are
a
r
e
referenced
r
e
f
e
r
e
n
c
e
d
as
a
s
“section
“
s
e
c
t
i
o
n
X.0”.
X
.
0
”
.
-
One
O
n
e
or
o
r
more
m
o
r
e
supplements
s
u
p
p
l
e
m
e
n
t
s
to
t
o
this
t
h
i
s
document
d
o
c
u
m
e
n
t
exist
e
x
i
s
t
and
a
n
d
extend
e
x
t
e
n
d
the
t
h
e
guidance
g
u
i
d
a
n
c
e
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
a
a
specific
s
p
e
c
i
f
i
c
technique.
t
e
c
h
n
i
q
u
e
.
Supplements
S
u
p
p
l
e
m
e
n
t
s
are
a
r
e
used
u
s
e
d
in
i
n
conjunction
c
o
n
j
u
n
c
t
i
o
n
with
w
i
t
h
this
t
h
i
s
document
d
o
c
u
m
e
n
t
and
a
n
d
may
m
a
y
be
b
e
used
u
s
e
d
in
i
n
conjunction
c
o
n
j
u
n
c
t
i
o
n
with
w
i
t
h
one
o
n
e
another.
a
n
o
t
h
e
r
.
Unless
U
n
l
e
s
s
alternatives
a
l
t
e
r
n
a
t
i
v
e
s
are
a
r
e
used
u
s
e
d
(see
(
s
e
e
1.4.i),
1
.
4
.
i
)
,
if
i
f
a
a
supplement
s
u
p
p
l
e
m
e
n
t
exists
e
x
i
s
t
s
for
f
o
r
a
a
specific
s
p
e
c
i
f
i
c
technique,
t
e
c
h
n
i
q
u
e
,
the
t
h
e
supplement
s
u
p
p
l
e
m
e
n
t
should
s
h
o
u
l
d
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
4
4
be
b
e
used
u
s
e
d
to
t
o
add,
a
d
d
,
delete,
d
e
l
e
t
e
,
or
o
r
otherwise
o
t
h
e
r
w
i
s
e
modify
m
o
d
i
f
y
objectives,
o
b
j
e
c
t
i
v
e
s
,
activities,
a
c
t
i
v
i
t
i
e
s
,
explanatory
e
x
p
l
a
n
a
t
o
r
y
text,
t
e
x
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
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
address
a
d
d
r
e
s
s
that
t
h
a
t
technique,
t
e
c
h
n
i
q
u
e
,
as
a
s
defined
d
e
f
i
n
e
d
appropriately
a
p
p
r
o
p
r
i
a
t
e
l
y
in
i
n
each
e
a
c
h
supplement.
s
u
p
p
l
e
m
e
n
t
.
It
I
t
is
i
s
the
t
h
e
responsibility
r
e
s
p
o
n
s
i
b
i
l
i
t
y
of
o
f
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
the
t
h
e
supplement’s
s
u
p
p
l
e
m
e
n
t
’
s
use
u
s
e
is
i
s
acceptable
a
c
c
e
p
t
a
b
l
e
to
t
o
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
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
part
p
a
r
t
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
,
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
review
r
e
v
i
e
w
all
a
l
l
potentially
p
o
t
e
n
t
i
a
l
l
y
relevant
r
e
l
e
v
a
n
t
supplements
s
u
p
p
l
e
m
e
n
t
s
and
a
n
d
identify
i
d
e
n
t
i
f
y
those
t
h
o
s
e
that
t
h
a
t
will
w
i
l
l
be
b
e
used.
u
s
e
d
.
The
T
h
e
information
i
n
f
o
r
m
a
t
i
o
n
in
i
n
supplements
s
u
p
p
l
e
m
e
n
t
s
should
s
h
o
u
l
d
be
b
e
used
u
s
e
d
with
w
i
t
h
and
a
n
d
in
i
n
the
t
h
e
same
s
a
m
e
way
w
a
y
as
a
s
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Annex
A
n
n
e
x
A
A
of
o
f
each
e
a
c
h
supplement
s
u
p
p
l
e
m
e
n
t
identifies
i
d
e
n
t
i
f
i
e
s
how
h
o
w
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
are
a
r
e
revised
r
e
v
i
s
e
d
relative
r
e
l
a
t
i
v
e
to
t
o
the
t
h
e
specific
s
p
e
c
i
f
i
c
technique
t
e
c
h
n
i
q
u
e
addressed
a
d
d
r
e
s
s
e
d
by
b
y
the
t
h
e
supplement.
s
u
p
p
l
e
m
e
n
t
.
-
Compliance
C
o
m
p
l
i
a
n
c
e
is
i
s
achieved
a
c
h
i
e
v
e
d
when
w
h
e
n
all
a
l
l
applicable
a
p
p
l
i
c
a
b
l
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
by
b
y
performing
p
e
r
f
o
r
m
i
n
g
all
a
l
l
planned
p
l
a
n
n
e
d
activities
a
c
t
i
v
i
t
i
e
s
and
a
n
d
capturing
c
a
p
t
u
r
i
n
g
the
t
h
e
related
r
e
l
a
t
e
d
evidence.
e
v
i
d
e
n
c
e
.
-
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
5
5
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
–
–
SECTION
S
E
C
T
I
O
N
2
2
SOFTWARE
S
O
F
T
W
A
R
E
LIFE
L
I
F
E
CYCLE
C
Y
C
L
E
–
–
SECTION
S
E
C
T
I
O
N
3
3
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
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
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
–
–
SECTION
S
E
C
T
I
O
N
5
5
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
INTEGRATION
I
N
T
E
G
R
A
T
I
O
N
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
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
–
–
SECTION
S
E
C
T
I
O
N
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
MANAGEMENT
M
A
N
A
G
E
M
E
N
T
PROCESS
P
R
O
C
E
S
S
–
–
SECTION
S
E
C
T
I
O
N
7
7
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
–
–
SECTION
S
E
C
T
I
O
N
8
8
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
–
–
SECTION
S
E
C
T
I
O
N
9
9
OVERVIEW
O
V
E
R
V
I
E
W
OF
O
F
CERTIFICATION
C
E
R
T
I
F
I
C
A
T
I
O
N
PROCESS
P
R
O
C
E
S
S
–
–
SECTION
S
E
C
T
I
O
N
10
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
–
–
SECTION
S
E
C
T
I
O
N
11
1
1
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
–
–
SECTION
S
E
C
T
I
O
N
12
1
2
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
7
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
D
E
V
E
L
O
P
M
E
N
T
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
.
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
can
c
a
n
be
b
e
found
f
o
u
n
d
in
i
n
other
o
t
h
e
r
industry
i
n
d
u
s
t
r
y
documents
d
o
c
u
m
e
n
t
s
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
SAE
S
A
E
ARP4754A).
A
R
P
4
7
5
4
A
)
.
Discussed
D
i
s
c
u
s
s
e
d
in
i
n
this
t
h
i
s
section
s
e
c
t
i
o
n
are:
a
r
e
:
System
S
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocation
a
l
l
o
c
a
t
i
o
n
to
t
o
software
s
o
f
t
w
a
r
e
(see
(
s
e
e
2.1).
2
.
1
)
.
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
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
and
a
n
d
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
hardware
h
a
r
d
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
(see
(
s
e
e
2.2).
2
.
2
)
.
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
,
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
level
l
e
v
e
l
definitions,
d
e
f
i
n
i
t
i
o
n
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
(see
(
s
e
e
2.3).
2
.
3
)
.
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
(see
(
s
e
e
2.4).
2
.
4
)
.
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
life
l
i
f
e
cycle
c
y
c
l
e
processes
p
r
o
c
e
s
s
e
s
(see
(
s
e
e
2.5).
2
.
5
)
.
System
S
y
s
t
e
m
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
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
(see
(
s
e
e
2.6).
2
.
6
)
.
The
T
h
e
term
t
e
r
m
“system”
“
s
y
s
t
e
m
”
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
refers
r
e
f
e
r
s
to
t
o
the
t
h
e
airborne
a
i
r
b
o
r
n
e
system
s
y
s
t
e
m
and
a
n
d
equipment
e
q
u
i
p
m
e
n
t
only,
o
n
l
y
,
not
n
o
t
to
t
o
the
t
h
e
wider
w
i
d
e
r
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
a
a
system
s
y
s
t
e
m
that
t
h
a
t
might
m
i
g
h
t
include
i
n
c
l
u
d
e
operators,
o
p
e
r
a
t
o
r
s
,
operational
o
p
e
r
a
t
i
o
n
a
l
procedures,
p
r
o
c
e
d
u
r
e
s
,
etc.
e
t
c
.
2.1
2
.
1
System
S
y
s
t
e
m
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Allocation
A
l
l
o
c
a
t
i
o
n
to
t
o
Software
S
o
f
t
w
a
r
e
As
A
s
part
p
a
r
t
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
,
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
other
o
t
h
e
r
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
such
s
u
c
h
as
a
s
safety-related,
s
a
f
e
t
y
-
r
e
l
a
t
e
d
,
security,
s
e
c
u
r
i
t
y
,
and
a
n
d
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
.
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
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
,
and
a
n
d
may
m
a
y
include
i
n
c
l
u
d
e
functional,
f
u
n
c
t
i
o
n
a
l
,
integrity,
i
n
t
e
g
r
i
t
y
,
and
a
n
d
reliability
r
e
l
i
a
b
i
l
i
t
y
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
as
a
s
well
w
e
l
l
as
a
s
design
d
e
s
i
g
n
constraints.
c
o
n
s
t
r
a
i
n
t
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
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
,
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
defined
d
e
f
i
n
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
system
s
y
s
t
e
m
by
b
y
specifying
s
p
e
c
i
f
y
i
n
g
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
identified
i
d
e
n
t
i
f
i
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
,
fault
f
a
u
l
t
tolerance,
t
o
l
e
r
a
n
c
e
,
fault
f
a
u
l
t
removal,
r
e
m
o
v
a
l
,
and
a
n
d
fault
f
a
u
l
t
avoidance.
a
v
o
i
d
a
n
c
e
.
The
T
h
e
system
s
y
s
t
e
m
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
responsible
r
e
s
p
o
n
s
i
b
l
e
for
f
o
r
the
t
h
e
refinement
r
e
f
i
n
e
m
e
n
t
and
a
n
d
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
hardware
h
a
r
d
w
a
r
e
and/or
a
n
d
/
o
r
software
s
o
f
t
w
a
r
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
architecture.
a
r
c
h
i
t
e
c
t
u
r
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
,
including
i
n
c
l
u
d
i
n
g
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
developed
d
e
v
e
l
o
p
e
d
and
a
n
d
refined
r
e
f
i
n
e
d
into
i
n
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
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
.
These
T
h
e
s
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
verification
v
e
r
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
establish
e
s
t
a
b
l
i
s
h
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
performs
p
e
r
f
o
r
m
s
its
i
t
s
intended
i
n
t
e
n
d
e
d
functions
f
u
n
c
t
i
o
n
s
under
u
n
d
e
r
any
a
n
y
foreseeable
f
o
r
e
s
e
e
a
b
l
e
operating
o
p
e
r
a
t
i
n
g
condition.
c
o
n
d
i
t
i
o
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
may
m
a
y
include:
i
n
c
l
u
d
e
:
-
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
.
-
Interface
I
n
t
e
r
f
a
c
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
8
8
-
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
.
-
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
,
including
i
n
c
l
u
d
i
n
g
safety
s
a
f
e
t
y
strategies,
s
t
r
a
t
e
g
i
e
s
,
design
d
e
s
i
g
n
constraints
c
o
n
s
t
r
a
i
n
t
s
and
a
n
d
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
.
In
I
n
cases
c
a
s
e
s
where
w
h
e
r
e
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
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
other
o
t
h
e
r
system
s
y
s
t
e
m
may
m
a
y
also
a
l
s
o
form
f
o
r
m
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software.
s
o
f
t
w
a
r
e
.
-
Security
S
e
c
u
r
i
t
y
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Maintenance
M
a
i
n
t
e
n
a
n
c
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
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
any
a
n
y
applicable
a
p
p
l
i
c
a
b
l
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
regulations,
r
e
g
u
l
a
t
i
o
n
s
,
issue
i
s
s
u
e
papers,
p
a
p
e
r
s
,
etc.
e
t
c
.
-
Additional
A
d
d
i
t
i
o
n
a
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
needed
n
e
e
d
e
d
to
t
o
aid
a
i
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
9
9
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
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
Approval
A
p
p
r
o
v
a
l
Activities
A
c
t
i
v
i
t
i
e
s
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
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
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
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
System
S
y
s
t
e
m
Integration
I
n
t
e
g
r
a
t
i
o
n
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
Hardware
H
a
r
d
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
HARDWARE
H
A
R
D
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
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
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Coordination
C
o
o
r
d
i
n
a
t
i
o
n
and
a
n
d
Feedback
F
e
e
d
b
a
c
k
Identified
I
d
e
n
t
i
f
i
e
d
Hardware/Software
H
a
r
d
w
a
r
e
/
S
o
f
t
w
a
r
e
Incompatibilities
I
n
c
o
m
p
a
t
i
b
i
l
i
t
i
e
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
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
Software
S
o
f
t
w
a
r
e
Level(s)
L
e
v
e
l
(
s
)
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
Design
D
e
s
i
g
n
Constraints
C
o
n
s
t
r
a
i
n
t
s
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
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
to
t
o
be
b
e
Performed
P
e
r
f
o
r
m
e
d
by
b
y
Software
S
o
f
t
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
Definition
D
e
f
i
n
i
t
i
o
n
and
a
n
d
Evidence
E
v
i
d
e
n
c
e
of
o
f
any
a
n
y
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
Performed
P
e
r
f
o
r
m
e
d
by
b
y
System
S
y
s
t
e
m
Processes
P
r
o
c
e
s
s
e
s
Evidence
E
v
i
d
e
n
c
e
of
o
f
Acceptability
A
c
c
e
p
t
a
b
i
l
i
t
y
of
o
f
Data
D
a
t
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
Architecture
A
r
c
h
i
t
e
c
t
u
r
e
Evidence
E
v
i
d
e
n
c
e
of
o
f
any
a
n
y
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
Performed
P
e
r
f
o
r
m
e
d
Any
A
n
y
Limitation
L
i
m
i
t
a
t
i
o
n
of
o
f
Use
U
s
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
Data
D
a
t
a
Data
D
a
t
a
to
t
o
Facilitate
F
a
c
i
l
i
t
a
t
e
Integration
I
n
t
e
g
r
a
t
i
o
n
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
to
t
o
be
b
e
Performed
P
e
r
f
o
r
m
e
d
by
b
y
System
S
y
s
t
e
m
Processes
P
r
o
c
e
s
s
e
s
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
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
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
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
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
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
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Process
P
r
o
c
e
s
s
Problem
P
r
o
b
l
e
m
or
o
r
Change
C
h
a
n
g
e
Documentation
D
o
c
u
m
e
n
t
a
t
i
o
n
Software
S
o
f
t
w
a
r
e
Coding
C
o
d
i
n
g
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
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
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
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
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
2.2
2
.
2
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
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
.
This
T
h
i
s
information
i
n
f
o
r
m
a
t
i
o
n
flow
f
l
o
w
includes
i
n
c
l
u
d
e
s
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
aspects.
a
s
p
e
c
t
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
.
2.2.1
2
.
2
.
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
following
f
o
l
l
o
w
i
n
g
data
d
a
t
a
is
i
s
passed
p
a
s
s
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
system
s
y
s
t
e
m
processes
p
r
o
c
e
s
s
e
s
either
e
i
t
h
e
r
as
a
s
part
p
a
r
t
of
o
f
the
t
h
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
allocation
a
l
l
o
c
a
t
i
o
n
or
o
r
during
d
u
r
i
n
g
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
life
l
i
f
e
cycle:
c
y
c
l
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
.
-
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
.
-
Software
S
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
and
a
n
d
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
associated
a
s
s
o
c
i
a
t
e
d
failure
f
a
i
l
u
r
e
condition(s),
c
o
n
d
i
t
i
o
n
(
s
)
,
if
i
f
applicable.
a
p
p
l
i
c
a
b
l
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
.
-
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
external
e
x
t
e
r
n
a
l
interfaces,
i
n
t
e
r
f
a
c
e
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
,
etc.
e
t
c
.
-
Details
D
e
t
a
i
l
s
of
o
f
any
a
n
y
system
s
y
s
t
e
m
activities
a
c
t
i
v
i
t
i
e
s
proposed
p
r
o
p
o
s
e
d
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
as
a
s
part
p
a
r
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
.
Note
N
o
t
e
that
t
h
a
t
system
s
y
s
t
e
m
requirement
r
e
q
u
i
r
e
m
e
n
t
validation
v
a
l
i
d
a
t
i
o
n
is
i
s
not
n
o
t
usually
u
s
u
a
l
l
y
part
p
a
r
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
processes.
p
r
o
c
e
s
s
e
s
.
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
are
a
r
e
responsible
r
e
s
p
o
n
s
i
b
l
e
for
f
o
r
assuring
a
s
s
u
r
i
n
g
any
a
n
y
system
s
y
s
t
e
m
activities
a
c
t
i
v
i
t
i
e
s
proposed
p
r
o
p
o
s
e
d
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
as
a
s
part
p
a
r
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
.
-
Evidence
E
v
i
d
e
n
c
e
of
o
f
the
t
h
e
acceptability,
a
c
c
e
p
t
a
b
i
l
i
t
y
,
or
o
r
otherwise,
o
t
h
e
r
w
i
s
e
,
of
o
f
any
a
n
y
data
d
a
t
a
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
processes
p
r
o
c
e
s
s
e
s
to
t
o
the
t
h
e
system
s
y
s
t
e
m
processes
p
r
o
c
e
s
s
e
s
on
o
n
which
w
h
i
c
h
any
a
n
y
activity
a
c
t
i
v
i
t
y
has
h
a
s
been
b
e
e
n
conducted
c
o
n
d
u
c
t
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
processes.
p
r
o
c
e
s
s
e
s
.
Examples
E
x
a
m
p
l
e
s
of
o
f
such
s
u
c
h
activity
a
c
t
i
v
i
t
y
are
a
r
e
the
t
h
e
system
s
y
s
t
e
m
processes’
p
r
o
c
e
s
s
e
s
’
evaluations
e
v
a
l
u
a
t
i
o
n
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
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
processes
p
r
o
c
e
s
s
e
s
to
t
o
determine
d
e
t
e
r
m
i
n
e
if
i
f
there
t
h
e
r
e
is
i
s
any
a
n
y
impact
i
m
p
a
c
t
on
o
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
and
a
n
d
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Issues
I
s
s
u
e
s
raised
r
a
i
s
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
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
the
t
h
e
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
of
o
f
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
.
-
Evidence
E
v
i
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
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
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
,
if
i
f
any.
a
n
y
.
Any
A
n
y
evidence
e
v
i
d
e
n
c
e
provided
p
r
o
v
i
d
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
processes
p
r
o
c
e
s
s
e
s
(see
(
s
e
e
2.2.1.f
2
.
2
.
1
.
f
and
a
n
d
2.2.1.g)
2
.
2
.
1
.
g
)
should
s
h
o
u
l
d
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
by
b
y
the
t
h
e
software
s
o
f
t
w
a
r
e
processes
p
r
o
c
e
s
s
e
s
to
t
o
be
b
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
(see
(
s
e
e
11.14).
1
1
.
1
4
)
.
2.2.2
2
.
2
.
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
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
analyze
a
n
a
l
y
z
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
as
a
s
part
p
a
r
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
process.
p
r
o
c
e
s
s
.
If
I
f
such
s
u
c
h
an
a
n
analysis
a
n
a
l
y
s
i
s
identifies
i
d
e
n
t
i
f
i
e
s
any
a
n
y
system
s
y
s
t
e
m
requirements
r
e
q
u
i
r
e
m
e
n
t
s
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
,
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
capture
c
a
p
t
u
r
e
the
t
h
e
issues
i
s
s
u
e
s
and
a
n
d
refer
r
e
f
e
r
them
t
h
e
m
to
t
o
the
t
h
e
system
s
y
s
t
e
m
processes
p
r
o
c
e
s
s
e
s
for
f
o
r
resolution.
r
e
s
o
l
u
t
i
o
n
.
Furthermore,
F
u
r
t
h
e
r
m
o
r
e
,
as
a
s
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
evolves,
e
v
o
l
v
e
s
,
details
d
e
t
a
i
l
s
are
a
r
e
added
a
d
d
e
d
and
a
n
d
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
made
m
a
d
e
that
t
h
a
t
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
assessment
a
s
s
e
s
s
m
e
n
t
and
a
n
d
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
To
T
o
aid
a
i
d
the
t
h
e
evaluation
e
v
a
l
u
a
t
i
o
n
of
o
f
the
t
h
e
evolving
e
v
o
l
v
i
n
g
design
d
e
s
i
g
n
and
a
n
d
changes
c
h
a
n
g
e
s
to
t
o
the
t
h
e
design,
d
e
s
i
g
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
should
s
h
o
u
l
d
make
m
a
k
e
data
d
a
t
a
available
a
v
a
i
l
a
b
l
e
to
t
o
the
t
h
e
system
s
y
s
t
e
m
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
process.
p
r
o
c
e
s
s
.
This
T
h
i
s
data
d
a
t
a
will
w
i
l
l
facilitate
f
a
c
i
l
i
t
a
t
e
analyses
a
n
a
l
y
s
e
s
and
a
n
d
evaluations
e
v
a
l
u
a
t
i
o
n
s
to
t
o
establish
e
s
t
a
b
l
i
s
h
the
t
h
e
effect
e
f
f
e
c
t
on
o
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
and
a
n
d
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
It
I
t
may
m
a
y
be
b
e
advantageous
a
d
v
a
n
t
a
g
e
o
u
s
for
f
o
r
such
s
u
c
h
analyses
a
n
a
l
y
s
e
s
and
a
n
d
evaluations
e
v
a
l
u
a
t
i
o
n
s
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
jointly
j
o
i
n
t
l
y
by
b
y
the
t
h
e
systems
s
y
s
t
e
m
s
and
a
n
d
software
s
o
f
t
w
a
r
e
processes.
p
r
o
c
e
s
s
e
s
.
Such
S
u
c
h
data
d
a
t
a
includes:
i
n
c
l
u
d
e
s
:
11
1
1
-
Details
D
e
t
a
i
l
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
created
c
r
e
a
t
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
processes.
p
r
o
c
e
s
s
e
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
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
including
i
n
c
l
u
d
i
n
g
software
s
o
f
t
w
a
r
e
partitioning.
p
a
r
t
i
t
i
o
n
i
n
g
.
-
Evidence
E
v
i
d
e
n
c
e
of
o
f
system
s
y
s
t
e
m
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
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
,
if
i
f
any.
a
n
y
.
-
Problem
P
r
o
b
l
e
m
or
o
r
change
c
h
a
n
g
e
documentation,
d
o
c
u
m
e
n
t
a
t
i
o
n
,
including
i
n
c
l
u
d
i
n
g
problems
p
r
o
b
l
e
m
s
identified
i
d
e
n
t
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
and
a
n
d
identified
i
d
e
n
t
i
f
i
e
d
incompatibilities
i
n
c
o
m
p
a
t
i
b
i
l
i
t
i
e
s
between
b
e
t
w
e
e
n
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
.
-
Any
A
n
y
limitations
l
i
m
i
t
a
t
i
o
n
s
of
o
f
use.
u
s
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
and
a
n
d
any
a
n
y
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
status
s
t
a
t
u
s
constraints.
c
o
n
s
t
r
a
i
n
t
s
.
-
Performance,
P
e
r
f
o
r
m
a
n
c
e
,
timing,
t
i
m
i
n
g
,
and
a
n
d
accuracy
a
c
c
u
r
a
c
y
characteristics.
c
h
a
r
a
c
t
e
r
i
s
t
i
c
s
.
-
Data
D
a
t
a
to
t
o
facilitate
f
a
c
i
l
i
t
a
t
e
integration
i
n
t
e
g
r
a
t
i
o
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
into
i
n
t
o
the
t
h
e
system.
s
y
s
t
e
m
.
-
Details
D
e
t
a
i
l
s
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
activities
a
c
t
i
v
i
t
i
e
s
proposed
p
r
o
p
o
s
e
d
to
t
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
during
d
u
r
i
n
g
system
s
y
s
t
e
m
verification,
v
e
r
i
f
i
c
a
t
i
o
n
,
if
i
f
any.
a
n
y
.
2.2.3
2
.
2
.
3
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
Software
S
o
f
t
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
and
a
n
d
Hardware
H
a
r
d
w
a
r
e
Processes
P
r
o
c
e
s
s
e
s
Data
D
a
t
a
is
i
s
passed
p
a
s
s
e
d
between
b
e
t
w
e
e
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
process
p
r
o
c
e
s
s
and
a
n
d
the
t
h
e
hardware
h
a
r
d
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
process
p
r
o
c
e
s
s
either
e
i
t
h
e
r
as
a
s
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
allocation
a
l
l
o
c
a
t
i
o
n
or
o
r
during
d
u
r
i
n
g
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
life
l
i
f
e
cycles.
c
y
c
l
e
s
.
Such
S
u
c
h
data
d
a
t
a
includes:
i
n
c
l
u
d
e
s
:
-
All
A
l
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
including
i
n
c
l
u
d
i
n
g
derived
d
e
r
i
v
e
d
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
needed
n
e
e
d
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
,
such
s
u
c
h
as
a
s
definition
d
e
f
i
n
i
t
i
o
n
of
o
f
protocols,
p
r
o
t
o
c
o
l
s
,
timing
t
i
m
i
n
g
constraints,
c
o
n
s
t
r
a
i
n
t
s
,
and
a
n
d
addressing
a
d
d
r
e
s
s
i
n
g
schemes
s
c
h
e
m
e
s
for
f
o
r
the
t
h
e
interface
i
n
t
e
r
f
a
c
e
between
b
e
t
w
e
e
n
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software.
s
o
f
t
w
a
r
e
.
-
Instances
I
n
s
t
a
n
c
e
s
where
w
h
e
r
e
hardware
h
a
r
d
w
a
r
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
activities
a
c
t
i
v
i
t
i
e
s
require
r
e
q
u
i
r
e
coordination.
c
o
o
r
d
i
n
a
t
i
o
n
.
-
Identified
I
d
e
n
t
i
f
i
e
d
incompatibilities
i
n
c
o
m
p
a
t
i
b
i
l
i
t
i
e
s
between
b
e
t
w
e
e
n
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
.
2.3
2
.
3
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
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
This
T
h
i
s
section
s
e
c
t
i
o
n
provides
p
r
o
v
i
d
e
s
a
a
brief
b
r
i
e
f
introduction
i
n
t
r
o
d
u
c
t
i
o
n
to
t
o
how
h
o
w
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
is
i
s
determined
d
e
t
e
r
m
i
n
e
d
and
a
n
d
how
h
o
w
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
may
m
a
y
influence
i
n
f
l
u
e
n
c
e
the
t
h
e
allocation
a
l
l
o
c
a
t
i
o
n
of
o
f
a
a
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
It
I
t
is
i
s
not
n
o
t
the
t
h
e
intent
i
n
t
e
n
t
of
o
f
this
t
h
i
s
document
d
o
c
u
m
e
n
t
to
t
o
prescribe
p
r
e
s
c
r
i
b
e
how
h
o
w
these
t
h
e
s
e
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
performed;
p
e
r
f
o
r
m
e
d
;
this
t
h
i
s
has
h
a
s
to
t
o
be
b
e
established
e
s
t
a
b
l
i
s
h
e
d
and
a
n
d
performed
p
e
r
f
o
r
m
e
d
as
a
s
part
p
a
r
t
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
.
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
of
o
f
a
a
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
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
by
b
y
establishing
e
s
t
a
b
l
i
s
h
i
n
g
how
h
o
w
an
a
n
error
e
r
r
o
r
in
i
n
a
a
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
relates
r
e
l
a
t
e
s
to
t
o
the
t
h
e
system
s
y
s
t
e
m
failure
f
a
i
l
u
r
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
12
1
2
condition(s)
c
o
n
d
i
t
i
o
n
(
s
)
and
a
n
d
the
t
h
e
severity
s
e
v
e
r
i
t
y
of
o
f
that
t
h
a
t
failure
f
a
i
l
u
r
e
condition(s).
c
o
n
d
i
t
i
o
n
(
s
)
.
The
T
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
establishes
e
s
t
a
b
l
i
s
h
e
s
the
t
h
e
rigor
r
i
g
o
r
necessary
n
e
c
e
s
s
a
r
y
to
t
o
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
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
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
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
in
i
n
the
t
h
e
same
s
a
m
e
way
w
a
y
as
a
s
hardware
h
a
r
d
w
a
r
e
failure
f
a
i
l
u
r
e
rates.
r
a
t
e
s
.
Only
O
n
l
y
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
(see
(
s
e
e
2.4.1)
2
.
4
.
1
)
can
c
a
n
be
b
e
assigned
a
s
s
i
g
n
e
d
individual
i
n
d
i
v
i
d
u
a
l
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
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
.
If
I
f
partitioning
p
a
r
t
i
t
i
o
n
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
cannot
c
a
n
n
o
t
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
components
c
o
m
p
o
n
e
n
t
s
should
s
h
o
u
l
d
be
b
e
viewed
v
i
e
w
e
d
as
a
s
a
a
single
s
i
n
g
l
e
component
c
o
m
p
o
n
e
n
t
when
w
h
e
n
assigning
a
s
s
i
g
n
i
n
g
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
(that
(
t
h
a
t
is,
i
s
,
all
a
l
l
components
c
o
m
p
o
n
e
n
t
s
are
a
r
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
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
to
t
o
which
w
h
i
c
h
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
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
establish
e
s
t
a
b
l
i
s
h
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
to
t
o
be
b
e
used
u
s
e
d
based
b
a
s
e
d
on
o
n
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
guidance.
g
u
i
d
a
n
c
e
.
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
software
s
o
f
t
w
a
r
e
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
then
t
h
e
n
be
b
e
assigned
a
s
s
i
g
n
e
d
based
b
a
s
e
d
on
o
n
this
t
h
i
s
process
p
r
o
c
e
s
s
and
a
n
d
agreed
a
g
r
e
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
authorities.
a
u
t
h
o
r
i
t
i
e
s
.
2.3.1
2
.
3
.
1
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
Errors
E
r
r
o
r
s
and
a
n
d
Failure
F
a
i
l
u
r
e
Conditions
C
o
n
d
i
t
i
o
n
s
Figure
F
i
g
u
r
e
2-2
2
-
2
shows
s
h
o
w
s
a
a
sequence
s
e
q
u
e
n
c
e
of
o
f
events
e
v
e
n
t
s
in
i
n
which
w
h
i
c
h
a
a
software
s
o
f
t
w
a
r
e
error
e
r
r
o
r
leads
l
e
a
d
s
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
at
a
t
aircraft
a
i
r
c
r
a
f
t
level.
l
e
v
e
l
.
A
A
software
s
o
f
t
w
a
r
e
error
e
r
r
o
r
may
m
a
y
be
b
e
latent
l
a
t
e
n
t
and,
a
n
d
,
thus,
t
h
u
s
,
not
n
o
t
immediately
i
m
m
e
d
i
a
t
e
l
y
produce
p
r
o
d
u
c
e
a
a
failure.
f
a
i
l
u
r
e
.
This
T
h
i
s
model
m
o
d
e
l
is
i
s
intentionally
i
n
t
e
n
t
i
o
n
a
l
l
y
a
a
simple,
s
i
m
p
l
e
,
linear
l
i
n
e
a
r
representation.
r
e
p
r
e
s
e
n
t
a
t
i
o
n
.
In
I
n
actual
a
c
t
u
a
l
operation,
o
p
e
r
a
t
i
o
n
,
the
t
h
e
sequence
s
e
q
u
e
n
c
e
of
o
f
events
e
v
e
n
t
s
that
t
h
a
t
leads
l
e
a
d
s
from
f
r
o
m
a
a
software
s
o
f
t
w
a
r
e
error
e
r
r
o
r
to
t
o
a
a
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
may
m
a
y
be
b
e
complex
c
o
m
p
l
e
x
and
a
n
d
not
n
o
t
easily
e
a
s
i
l
y
represented
r
e
p
r
e
s
e
n
t
e
d
by
b
y
a
a
sequence
s
e
q
u
e
n
c
e
of
o
f
events,
e
v
e
n
t
s
,
as
a
s
shown
s
h
o
w
n
in
i
n
Figure
F
i
g
u
r
e
2-2.
2
-
2
.
It
I
t
is
i
s
important
i
m
p
o
r
t
a
n
t
to
t
o
realize
r
e
a
l
i
z
e
that
t
h
a
t
the
t
h
e
likelihood
l
i
k
e
l
i
h
o
o
d
that
t
h
a
t
the
t
h
e
software
s
o
f
t
w
a
r
e
contains
c
o
n
t
a
i
n
s
an
a
n
error
e
r
r
o
r
cannot
c
a
n
n
o
t
be
b
e
quantified
q
u
a
n
t
i
f
i
e
d
in
i
n
the
t
h
e
same
s
a
m
e
way
w
a
y
as
a
s
for
f
o
r
random
r
a
n
d
o
m
hardware
h
a
r
d
w
a
r
e
failures.
f
a
i
l
u
r
e
s
.
System
S
y
s
t
e
m
Boundary
B
o
u
n
d
a
r
y
Software
S
o
f
t
w
a
r
e
Boundary
B
o
u
n
d
a
r
y
Latent
L
a
t
e
n
t
Software
S
o
f
t
w
a
r
e
Error
E
r
r
o
r
in
i
n
Data
D
a
t
a
or
o
r
Executable
E
x
e
c
u
t
a
b
l
e
Code
C
o
d
e
Fault
F
a
u
l
t
System
S
y
s
t
e
m
Failure
F
a
i
l
u
r
e
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
(Effect
(
E
f
f
e
c
t
at
a
t
Aircraft
A
i
r
c
r
a
f
t
Level)
L
e
v
e
l
)
Figure
F
i
g
u
r
e
2-2
2
-
2
Sequence
S
e
q
u
e
n
c
e
of
o
f
Events
E
v
e
n
t
s
for
f
o
r
Software
S
o
f
t
w
a
r
e
Error
E
r
r
o
r
Leading
L
e
a
d
i
n
g
to
t
o
a
a
Failure
F
a
i
l
u
r
e
Condition
C
o
n
d
i
t
i
o
n
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
(see
(
s
e
e
2.4)
2
.
4
)
and/or
a
n
d
/
o
r
system
s
y
s
t
e
m
external
e
x
t
e
r
n
a
l
factors
f
a
c
t
o
r
s
may
m
a
y
also
a
l
s
o
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
as
a
s
part
p
a
r
t
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
when
w
h
e
n
identifying
i
d
e
n
t
i
f
y
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
categories
c
a
t
e
g
o
r
i
e
s
and
a
n
d
assigning
a
s
s
i
g
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
to
t
o
each
e
a
c
h
software
s
o
f
t
w
a
r
e
component.
c
o
m
p
o
n
e
n
t
.
2.3.2
2
.
3
.
2
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
,
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
refer
r
e
f
e
r
to
t
o
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
issued
i
s
s
u
e
d
by
b
y
the
t
h
e
relevant
r
e
l
e
v
a
n
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
.
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
in
i
n
Table
T
a
b
l
e
2-1
2
-
1
are
a
r
e
valid
v
a
l
i
d
for
f
o
r
large
l
a
r
g
e
transport
t
r
a
n
s
p
o
r
t
aircraft
a
i
r
c
r
a
f
t
based
b
a
s
e
d
on
o
n
established
e
s
t
a
b
l
i
s
h
e
d
advisory
a
d
v
i
s
o
r
y
material
m
a
t
e
r
i
a
l
for
f
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
,
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
.
13
1
3
Table
T
a
b
l
e
2-1
2
-
1
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
Descriptions
D
e
s
c
r
i
p
t
i
o
n
s
Category
C
a
t
e
g
o
r
y
Description
D
e
s
c
r
i
p
t
i
o
n
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
result
r
e
s
u
l
t
in
i
n
multiple
m
u
l
t
i
p
l
e
fatalities,
f
a
t
a
l
i
t
i
e
s
,
usually
u
s
u
a
l
l
y
with
w
i
t
h
the
t
h
e
loss
l
o
s
s
of
o
f
the
t
h
e
airplane.
a
i
r
p
l
a
n
e
.
Hazardous
H
a
z
a
r
d
o
u
s
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
airplane
a
i
r
p
l
a
n
e
or
o
r
the
t
h
e
ability
a
b
i
l
i
t
y
of
o
f
the
t
h
e
flight
f
l
i
g
h
t
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
excessive
e
x
c
e
s
s
i
v
e
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
cannot
c
a
n
n
o
t
be
b
e
relied
r
e
l
i
e
d
upon
u
p
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
Serious
S
e
r
i
o
u
s
or
o
r
fatal
f
a
t
a
l
injury
i
n
j
u
r
y
to
t
o
a
a
relatively
r
e
l
a
t
i
v
e
l
y
small
s
m
a
l
l
number
n
u
m
b
e
r
of
o
f
the
t
h
e
occupants
o
c
c
u
p
a
n
t
s
other
o
t
h
e
r
than
t
h
a
n
the
t
h
e
flight
f
l
i
g
h
t
crew.
c
r
e
w
.
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
airplane
a
i
r
p
l
a
n
e
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
the
t
h
e
flight
f
l
i
g
h
t
crew,
c
r
e
w
,
or
o
r
physical
p
h
y
s
i
c
a
l
distress
d
i
s
t
r
e
s
s
to
t
o
passengers
p
a
s
s
e
n
g
e
r
s
or
o
r
cabin
c
a
b
i
n
crew,
c
r
e
w
,
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
airplane
a
i
r
p
l
a
n
e
safety,
s
a
f
e
t
y
,
and
a
n
d
which
w
h
i
c
h
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
physical
p
h
y
s
i
c
a
l
discomfort
d
i
s
c
o
m
f
o
r
t
to
t
o
passengers
p
a
s
s
e
n
g
e
r
s
or
o
r
cabin
c
a
b
i
n
crew.
c
r
e
w
.
No
N
o
Safety
S
a
f
e
t
y
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
that
t
h
a
t
would
w
o
u
l
d
have
h
a
v
e
no
n
o
effect
e
f
f
e
c
t
on
o
n
safety;
s
a
f
e
t
y
;
for
f
o
r
example,
e
x
a
m
p
l
e
,
Failure
F
a
i
l
u
r
e
Conditions
C
o
n
d
i
t
i
o
n
s
that
t
h
a
t
would
w
o
u
l
d
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
airplane
a
i
r
p
l
a
n
e
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
2.3.3
2
.
3
.
3
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Definition
D
e
f
i
n
i
t
i
o
n
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
five
f
i
v
e
software
s
o
f
t
w
a
r
e
levels,
l
e
v
e
l
s
,
Level
L
e
v
e
l
A
A
to
t
o
Level
L
e
v
e
l
E.
E
.
For
F
o
r
the
t
h
e
example
e
x
a
m
p
l
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
in
i
n
section
s
e
c
t
i
o
n
2.3.2,
2
.
3
.
2
,
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
these
t
h
e
s
e
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
conditions
c
o
n
d
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
h
a
z
a
r
d
o
u
s
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
.
If
I
f
a
a
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
is
i
s
determined
d
e
t
e
r
m
i
n
e
d
to
t
o
be
b
e
Level
L
e
v
e
l
E
E
and
a
n
d
this
t
h
i
s
is
i
s
confirmed
c
o
n
f
i
r
m
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
,
no
n
o
further
f
u
r
t
h
e
r
guidance
g
u
i
d
a
n
c
e
contained
c
o
n
t
a
i
n
e
d
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
applies.
a
p
p
l
i
e
s
.
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
always
a
l
w
a
y
s
consider
c
o
n
s
i
d
e
r
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
guidance
g
u
i
d
a
n
c
e
and
a
n
d
system
s
y
s
t
e
m
development
d
e
v
e
l
o
p
m
e
n
t
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
for
f
o
r
categorizing
c
a
t
e
g
o
r
i
z
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
severity
s
e
v
e
r
i
t
y
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
2.3.4
2
.
3
.
4
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
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
based
b
a
s
e
d
upon
u
p
o
n
the
t
h
e
failure
f
a
i
l
u
r
e
condition
c
o
n
d
i
t
i
o
n
which
w
h
i
c
h
may
m
a
y
result
r
e
s
u
l
t
from
f
r
o
m
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
.
The
T
h
e
impact
i
m
p
a
c
t
of,
o
f
,
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
should
s
h
o
u
l
d
be
b
e
analyzed.
a
n
a
l
y
z
e
d
.
External
E
x
t
e
r
n
a
l
factors
f
a
c
t
o
r
s
such
s
u
c
h
as
a
s
adverse
a
d
v
e
r
s
e
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
as
a
s
well
w
e
l
l
as
a
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
(as
(
a
s
described
d
e
s
c
r
i
b
e
d
in
i
n
section
s
e
c
t
i
o
n
2.4)
2
.
4
)
may
m
a
y
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
when
w
h
e
n
identifying
i
d
e
n
t
i
f
y
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
categories
c
a
t
e
g
o
r
i
e
s
and
a
n
d
determining
d
e
t
e
r
m
i
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
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
.
Note
N
o
t
e
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
,
a
a
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
.
15
1
5
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
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
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
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
to
t
o
which
w
h
i
c
h
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
,
including
i
n
c
l
u
d
i
n
g
combined
c
o
m
b
i
n
e
d
failure
f
a
i
l
u
r
e
conditions.
c
o
n
d
i
t
i
o
n
s
.
-
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
This
T
h
i
s
section
s
e
c
t
i
o
n
provides
p
r
o
v
i
d
e
s
information
i
n
f
o
r
m
a
t
i
o
n
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
failures,
f
a
i
l
u
r
e
s
,
or
o
r
detect
d
e
t
e
c
t
failures
f
a
i
l
u
r
e
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
them.
t
h
e
m
.
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
typically
t
y
p
i
c
a
l
l
y
identified
i
d
e
n
t
i
f
i
e
d
during
d
u
r
i
n
g
system
s
y
s
t
e
m
design
d
e
s
i
g
n
and
a
n
d
should
s
h
o
u
l
d
not
n
o
t
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
.
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
.
In
I
n
implementations
i
m
p
l
e
m
e
n
t
a
t
i
o
n
s
where
w
h
e
r
e
anomalous
a
n
o
m
a
l
o
u
s
behavior
b
e
h
a
v
i
o
r
of
o
f
two
t
w
o
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
is
i
s
needed
n
e
e
d
e
d
in
i
n
order
o
r
d
e
r
to
t
o
cause
c
a
u
s
e
the
t
h
e
failure
f
a
i
l
u
r
e
condition,
c
o
n
d
i
t
i
o
n
,
this
t
h
i
s
may
m
a
y
be
b
e
taken
t
a
k
e
n
into
i
n
t
o
consideration
c
o
n
s
i
d
e
r
a
t
i
o
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
when
w
h
e
n
assigning
a
s
s
i
g
n
i
n
g
the
t
h
e
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
for
f
o
r
these
t
h
e
s
e
software
s
o
f
t
w
a
r
e
components.
c
o
m
p
o
n
e
n
t
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
needs
n
e
e
d
s
to
t
o
establish
e
s
t
a
b
l
i
s
h
that
t
h
a
t
sufficient
s
u
f
f
i
c
i
e
n
t
independence
i
n
d
e
p
e
n
d
e
n
c
e
exists
e
x
i
s
t
s
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
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
both
b
o
t
h
function
f
u
n
c
t
i
o
n
(that
(
t
h
a
t
is,
i
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
design
d
e
s
i
g
n
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
common
c
o
m
m
o
n
design
d
e
s
i
g
n
elements,
e
l
e
m
e
n
t
s
,
languages,
l
a
n
g
u
a
g
e
s
,
and
a
n
d
tools).
t
o
o
l
s
)
.
If
I
f
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
and
a
n
d
independence
i
n
d
e
p
e
n
d
e
n
c
e
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
cannot
c
a
n
n
o
t
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
components
c
o
m
p
o
n
e
n
t
s
should
s
h
o
u
l
d
be
b
e
viewed
v
i
e
w
e
d
as
a
s
a
a
single
s
i
n
g
l
e
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
when
w
h
e
n
assigning
a
s
s
i
g
n
i
n
g
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
(that
(
t
h
a
t
is,
i
s
,
all
a
l
l
components
c
o
m
p
o
n
e
n
t
s
are
a
r
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
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
to
t
o
which
w
h
i
c
h
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
)
.
-
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
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
.
Partitioning
P
a
r
t
i
t
i
o
n
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
may
m
a
y
be
b
e
achieved
a
c
h
i
e
v
e
d
by
b
y
allocating
a
l
l
o
c
a
t
i
n
g
unique
u
n
i
q
u
e
hardware
h
a
r
d
w
a
r
e
resources
r
e
s
o
u
r
c
e
s
to
t
o
each
e
a
c
h
component
c
o
m
p
o
n
e
n
t
(that
(
t
h
a
t
is,
i
s
,
only
o
n
l
y
one
o
n
e
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
is
i
s
executed
e
x
e
c
u
t
e
d
on
o
n
each
e
a
c
h
hardware
h
a
r
d
w
a
r
e
platform
p
l
a
t
f
o
r
m
in
i
n
a
a
system).
s
y
s
t
e
m
)
.
Alternatively,
A
l
t
e
r
n
a
t
i
v
e
l
y
,
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
provisions
p
r
o
v
i
s
i
o
n
s
may
m
a
y
be
b
e
made
m
a
d
e
to
t
o
allow
a
l
l
o
w
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
to
t
o
run
r
u
n
on
o
n
the
t
h
e
same
s
a
m
e
hardware
h
a
r
d
w
a
r
e
platform.
p
l
a
t
f
o
r
m
.
Regardless
R
e
g
a
r
d
l
e
s
s
of
o
f
the
t
h
e
method,
m
e
t
h
o
d
,
the
t
h
e
following
f
o
l
l
o
w
i
n
g
should
s
h
o
u
l
d
be
b
e
ensured
e
n
s
u
r
e
d
for
f
o
r
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
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
should
s
h
o
u
l
d
not
n
o
t
be
b
e
allowed
a
l
l
o
w
e
d
to
t
o
contaminate
c
o
n
t
a
m
i
n
a
t
e
another
a
n
o
t
h
e
r
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
component’s
c
o
m
p
o
n
e
n
t
’
s
code,
c
o
d
e
,
input/output
i
n
p
u
t
/
o
u
t
p
u
t
(I/O),
(
I
/
O
)
,
or
o
r
data
d
a
t
a
storage
s
t
o
r
a
g
e
areas.
a
r
e
a
s
.
-
A
A
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
should
s
h
o
u
l
d
be
b
e
allowed
a
l
l
o
w
e
d
to
t
o
consume
c
o
n
s
u
m
e
shared
s
h
a
r
e
d
processor
p
r
o
c
e
s
s
o
r
resources
r
e
s
o
u
r
c
e
s
only
o
n
l
y
during
d
u
r
i
n
g
its
i
t
s
scheduled
s
c
h
e
d
u
l
e
d
period
p
e
r
i
o
d
of
o
f
execution.
e
x
e
c
u
t
i
o
n
.
-
Failures
F
a
i
l
u
r
e
s
of
o
f
hardware
h
a
r
d
w
a
r
e
unique
u
n
i
q
u
e
to
t
o
a
a
partitioned
p
a
r
t
i
t
i
o
n
e
d
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
should
s
h
o
u
l
d
not
n
o
t
cause
c
a
u
s
e
adverse
a
d
v
e
r
s
e
effects
e
f
f
e
c
t
s
on
o
n
other
o
t
h
e
r
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
Any
A
n
y
software
s
o
f
t
w
a
r
e
providing
p
r
o
v
i
d
i
n
g
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
should
s
h
o
u
l
d
have
h
a
v
e
the
t
h
e
same
s
a
m
e
or
o
r
higher
h
i
g
h
e
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
as
a
s
the
t
h
e
highest
h
i
g
h
e
s
t
level
l
e
v
e
l
assigned
a
s
s
i
g
n
e
d
to
t
o
any
a
n
y
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
.
-
Any
A
n
y
hardware
h
a
r
d
w
a
r
e
providing
p
r
o
v
i
d
i
n
g
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
should
s
h
o
u
l
d
be
b
e
assessed
a
s
s
e
s
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
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
it
i
t
does
d
o
e
s
not
n
o
t
adversely
a
d
v
e
r
s
e
l
y
affect
a
f
f
e
c
t
safety.
s
a
f
e
t
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
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
.
These
T
h
e
s
e
include
i
n
c
l
u
d
e
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
.
-
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
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
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-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
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
,
multi-version
m
u
l
t
i
-
v
e
r
s
i
o
n
independent
i
n
d
e
p
e
n
d
e
n
t
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
may
m
a
y
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
that
t
h
a
t
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
using
u
s
i
n
g
comparator
c
o
m
p
a
r
a
t
o
r
differences
d
i
f
f
e
r
e
n
c
e
s
greater
g
r
e
a
t
e
r
than
t
h
a
n
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
section
s
e
c
t
i
o
n
12.3.2.
1
2
.
3
.
2
.
-
Safety
S
a
f
e
t
y
Monitoring
M
o
n
i
t
o
r
i
n
g
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
that
t
h
a
t
would
w
o
u
l
d
result
r
e
s
u
l
t
in
i
n
a
a
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
software
s
o
f
t
w
a
r
e
may
m
a
y
be
b
e
assigned
a
s
s
i
g
n
e
d
a
a
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
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
assignment,
a
s
s
i
g
n
m
e
n
t
,
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
:
-
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
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
.
17
1
7
-
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
that
t
h
a
t
causes
c
a
u
s
e
s
the
t
h
e
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
-
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
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
provides
p
r
o
v
i
d
e
s
an
a
n
overview
o
v
e
r
v
i
e
w
of
o
f
those
t
h
o
s
e
software-related
s
o
f
t
w
a
r
e
-
r
e
l
a
t
e
d
issues
i
s
s
u
e
s
(not
(
n
o
t
necessarily
n
e
c
e
s
s
a
r
i
l
y
mutually
m
u
t
u
a
l
l
y
exclusive)
e
x
c
l
u
s
i
v
e
)
that
t
h
a
t
should
s
h
o
u
l
d
be
b
e
considered,
c
o
n
s
i
d
e
r
e
d
,
as
a
s
appropriate,
a
p
p
r
o
p
r
i
a
t
e
,
by
b
y
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
:
-
Parameter
P
a
r
a
m
e
t
e
r
data
d
a
t
a
items.
i
t
e
m
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
.
-
Commercial-Off-The-Shelf
C
o
m
m
e
r
c
i
a
l
-
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
.
-
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
.
-
Field-loadable
F
i
e
l
d
-
l
o
a
d
a
b
l
e
software.
s
o
f
t
w
a
r
e
.
-
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
.
2.5.1
2
.
5
.
1
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Items
I
t
e
m
s
Software
S
o
f
t
w
a
r
e
consists
c
o
n
s
i
s
t
s
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
and/or
a
n
d
/
o
r
data,
d
a
t
a
,
and
a
n
d
can
c
a
n
comprise
c
o
m
p
r
i
s
e
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
.
A
A
data
d
a
t
a
set
s
e
t
that
t
h
a
t
influences
i
n
f
l
u
e
n
c
e
s
the
t
h
e
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
without
w
i
t
h
o
u
t
modifying
m
o
d
i
f
y
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
and
a
n
d
is
i
s
managed
m
a
n
a
g
e
d
as
a
s
a
a
separate
s
e
p
a
r
a
t
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item
i
t
e
m
is
i
s
called
c
a
l
l
e
d
a
a
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item.
i
t
e
m
.
That
T
h
a
t
is,
i
s
,
when
w
h
e
n
discussing
d
i
s
c
u
s
s
i
n
g
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
and
a
n
d
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code,
C
o
d
e
,
it
i
t
is
i
s
implied
i
m
p
l
i
e
d
that
t
h
a
t
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
are
a
r
e
not
n
o
t
part
p
a
r
t
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
.
A
A
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
comprises
c
o
m
p
r
i
s
e
s
a
a
structure
s
t
r
u
c
t
u
r
e
of
o
f
individual
i
n
d
i
v
i
d
u
a
l
elements
e
l
e
m
e
n
t
s
where
w
h
e
r
e
each
e
a
c
h
element
e
l
e
m
e
n
t
can
c
a
n
be
b
e
assigned
a
s
s
i
g
n
e
d
a
a
single
s
i
n
g
l
e
value.
v
a
l
u
e
.
Each
E
a
c
h
element
e
l
e
m
e
n
t
has
h
a
s
attributes
a
t
t
r
i
b
u
t
e
s
such
s
u
c
h
as
a
s
type,
t
y
p
e
,
range,
r
a
n
g
e
,
or
o
r
set
s
e
t
of
o
f
allowed
a
l
l
o
w
e
d
values.
v
a
l
u
e
s
.
Examples
E
x
a
m
p
l
e
s
of
o
f
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
include
i
n
c
l
u
d
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
tables
t
a
b
l
e
s
and
a
n
d
databases
d
a
t
a
b
a
s
e
s
but
b
u
t
not
n
o
t
aeronautical
a
e
r
o
n
a
u
t
i
c
a
l
data
d
a
t
a
as
a
s
they
t
h
e
y
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
.
Parameter
P
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
may
m
a
y
contain
c
o
n
t
a
i
n
data
d
a
t
a
that
t
h
a
t
can:
c
a
n
:
-
Influence
I
n
f
l
u
e
n
c
e
paths
p
a
t
h
s
executed
e
x
e
c
u
t
e
d
through
t
h
r
o
u
g
h
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
.
-
Activate
A
c
t
i
v
a
t
e
or
o
r
deactivate
d
e
a
c
t
i
v
a
t
e
software
s
o
f
t
w
a
r
e
components
c
o
m
p
o
n
e
n
t
s
and
a
n
d
functions.
f
u
n
c
t
i
o
n
s
.
-
Adapt
A
d
a
p
t
the
t
h
e
software
s
o
f
t
w
a
r
e
computations
c
o
m
p
u
t
a
t
i
o
n
s
to
t
o
the
t
h
e
system
s
y
s
t
e
m
configuration.
c
o
n
f
i
g
u
r
a
t
i
o
n
.
-
Be
B
e
used
u
s
e
d
as
a
s
computational
c
o
m
p
u
t
a
t
i
o
n
a
l
data.
d
a
t
a
.
-
Establish
E
s
t
a
b
l
i
s
h
time
t
i
m
e
and
a
n
d
memory
m
e
m
o
r
y
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
allotments.
a
l
l
o
t
m
e
n
t
s
.
-
Provide
P
r
o
v
i
d
e
initial
i
n
i
t
i
a
l
values
v
a
l
u
e
s
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
component.
c
o
m
p
o
n
e
n
t
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Depending
D
e
p
e
n
d
i
n
g
on
o
n
how
h
o
w
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
is
i
s
to
t
o
be
b
e
used
u
s
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
,
the
t
h
e
following
f
o
l
l
o
w
i
n
g
should
s
h
o
u
l
d
be
b
e
addressed:
a
d
d
r
e
s
s
e
d
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
.
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
guidance.
g
u
i
d
a
n
c
e
.
In
I
n
cases
c
a
s
e
s
where
w
h
e
r
e
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
activates
a
c
t
i
v
a
t
e
s
or
o
r
deactivates
d
e
a
c
t
i
v
a
t
e
s
functions,
f
u
n
c
t
i
o
n
s
,
the
t
h
e
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
should
s
h
o
u
l
d
be
b
e
addressed
a
d
d
r
e
s
s
e
d
as
a
s
well.
w
e
l
l
.
Field-loadable
F
i
e
l
d
-
l
o
a
d
a
b
l
e
software
s
o
f
t
w
a
r
e
guidance.
g
u
i
d
a
n
c
e
.
Of
O
f
particular
p
a
r
t
i
c
u
l
a
r
concern
c
o
n
c
e
r
n
is
i
s
detection
d
e
t
e
c
t
i
o
n
of
o
f
corrupted
c
o
r
r
u
p
t
e
d
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items,
i
t
e
m
s
,
as
a
s
well
w
e
l
l
as
a
s
incompatibility
i
n
c
o
m
p
a
t
i
b
i
l
i
t
y
between
b
e
t
w
e
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
and
a
n
d
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items.
i
t
e
m
s
.
The
T
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
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
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
as
a
s
the
t
h
e
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
using
u
s
i
n
g
it.
i
t
.
For
F
o
r
more
m
o
r
e
information
i
n
f
o
r
m
a
t
i
o
n
regarding
r
e
g
a
r
d
i
n
g
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items,
i
t
e
m
s
,
see
s
e
e
6.6.
6
.
6
.
-
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
A
A
user-modifiable
u
s
e
r
-
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
may
m
a
y
be
b
e
changed
c
h
a
n
g
e
d
by
b
y
the
t
h
e
user
u
s
e
r
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
.
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
.
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-
u
s
e
r
-
modifiable
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
section
s
e
c
t
i
o
n
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-
n
o
n
-
modifiable
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
is
i
s
discussed
d
i
s
c
u
s
s
e
d
in
i
n
section
s
e
c
t
i
o
n
12.1.1.
1
2
.
1
.
1
.
Guidance
G
u
i
d
a
n
c
e
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
includes:
i
n
c
l
u
d
e
s
:
-
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
should
s
h
o
u
l
d
not
n
o
t
adversely
a
d
v
e
r
s
e
l
y
affect
a
f
f
e
c
t
safety,
s
a
f
e
t
y
,
operational
o
p
e
r
a
t
i
o
n
a
l
capabilities,
c
a
p
a
b
i
l
i
t
i
e
s
,
flight
f
l
i
g
h
t
crew
c
r
e
w
workload,
w
o
r
k
l
o
a
d
,
any
a
n
y
non-modifiable
n
o
n
-
m
o
d
i
f
i
a
b
l
e
software
s
o
f
t
w
a
r
e
components,
c
o
m
p
o
n
e
n
t
s
,
or
o
r
any
a
n
y
software
s
o
f
t
w
a
r
e
protection
p
r
o
t
e
c
t
i
o
n
mechanism
m
e
c
h
a
n
i
s
m
used.
u
s
e
d
.
Unless
U
n
l
e
s
s
this
t
h
i
s
can
c
a
n
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
may
m
a
y
not
n
o
t
be
b
e
classified
c
l
a
s
s
i
f
i
e
d
as
a
s
user-modifiable.
u
s
e
r
-
m
o
d
i
f
i
a
b
l
e
.
The
T
h
e
safety
s
a
f
e
t
y
impact
i
m
p
a
c
t
of
o
f
displaying
d
i
s
p
l
a
y
i
n
g
information
i
n
f
o
r
m
a
t
i
o
n
based
b
a
s
e
d
on
o
n
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
should
s
h
o
u
l
d
also
a
l
s
o
be
b
e
considered.
c
o
n
s
i
d
e
r
e
d
.
-
When
W
h
e
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
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
,
then
t
h
e
n
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
.
-
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
that
t
h
a
t
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
that
t
h
a
t
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
.
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
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
provide
p
r
o
v
i
d
e
the
t
h
e
necessary
n
e
c
e
s
s
a
r
y
information
i
n
f
o
r
m
a
t
i
o
n
to
t
o
enable
e
n
a
b
l
e
the
t
h
e
user
u
s
e
r
to
t
o
manage
m
a
n
a
g
e
the
t
h
e
software
s
o
f
t
w
a
r
e
in
i
n
such
s
u
c
h
a
a
way
w
a
y
that
t
h
a
t
the
t
h
e
safety
s
a
f
e
t
y
of
o
f
the
t
h
e
aircraft
a
i
r
c
r
a
f
t
is
i
s
not
n
o
t
compromised.
c
o
m
p
r
o
m
i
s
e
d
.
19
1
9
-
Commercial-Off-The-Shelf
C
o
m
m
e
r
c
i
a
l
-
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
guidance
g
u
i
d
a
n
c
e
in
i
n
section
s
e
c
t
i
o
n
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
,
and
a
n
d
section
s
e
c
t
i
o
n
12.3.4,
1
2
.
3
.
4
,
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
.
-
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
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
that
t
h
a
t
may
m
a
y
be
b
e
selected
s
e
l
e
c
t
e
d
by
b
y
software-programmed
s
o
f
t
w
a
r
e
-
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
4.2.h,
4
.
2
.
h
,
5.2.4,
5
.
2
.
4
,
and
a
n
d
6.4.4.3.d.2
6
.
4
.
4
.
3
.
d
.
2
for
f
o
r
guidance
g
u
i
d
a
n
c
e
on
o
n
deactivated
d
e
a
c
t
i
v
a
t
e
d
code.
c
o
d
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
,
a
a
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
.
-
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
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
with
w
i
t
h
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
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
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
,
then
t
h
e
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
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-loading
f
i
e
l
d
-
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
recovers
r
e
c
o
v
e
r
s
to
t
o
a
a
default
d
e
f
a
u
l
t
mode
m
o
d
e
or
o
r
safe
s
a
f
e
state
s
t
a
t
e
upon
u
p
o
n
detection
d
e
t
e
c
t
i
o
n
of
o
f
a
a
corrupted
c
o
r
r
u
p
t
e
d
or
o
r
inappropriate
i
n
a
p
p
r
o
p
r
i
a
t
e
software
s
o
f
t
w
a
r
e
load,
l
o
a
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
recovery
r
e
c
o
v
e
r
y
to
t
o
and
a
n
d
operation
o
p
e
r
a
t
i
o
n
in
i
n
this
t
h
i
s
mode.
m
o
d
e
.
Interfacing
I
n
t
e
r
f
a
c
i
n
g
systems
s
y
s
t
e
m
s
may
m
a
y
also
a
l
s
o
need
n
e
e
d
to
t
o
be
b
e
reviewed
r
e
v
i
e
w
e
d
for
f
o
r
proper
p
r
o
p
e
r
operation
o
p
e
r
a
t
i
o
n
with
w
i
t
h
the
t
h
e
default
d
e
f
a
u
l
t
mode.
m
o
d
e
.
-
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
the
t
h
e
software
s
o
f
t
w
a
r
e
consists
c
o
n
s
i
s
t
s
of
o
f
multiple
m
u
l
t
i
p
l
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
items,
i
t
e
m
s
,
their
t
h
e
i
r
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
should
s
h
o
u
l
d
be
b
e
ensured.
e
n
s
u
r
e
d
.
-
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
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
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
.
-
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
and
a
n
d
may
m
a
y
be
b
e
able
a
b
l
e
to
t
o
satisfy
s
a
t
i
s
f
y
some
s
o
m
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
objectives.
o
b
j
e
c
t
i
v
e
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
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
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
Credit
C
r
e
d
i
t
may
m
a
y
be
b
e
taken
t
a
k
e
n
from
f
r
o
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
for
f
o
r
the
t
h
e
satisfaction,
s
a
t
i
s
f
a
c
t
i
o
n
,
or
o
r
partial
p
a
r
t
i
a
l
satisfaction,
s
a
t
i
s
f
a
c
t
i
o
n
,
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
objectives
o
b
j
e
c
t
i
v
e
s
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
In
I
n
such
s
u
c
h
cases,
c
a
s
e
s
,
the
t
h
e
system
s
y
s
t
e
m
activities
a
c
t
i
v
i
t
i
e
s
for
f
o
r
which
w
h
i
c
h
credit
c
r
e
d
i
t
is
i
s
being
b
e
i
n
g
sought
s
o
u
g
h
t
should
s
h
o
u
l
d
be
b
e
shown
s
h
o
w
n
to
t
o
meet
m
e
e
t
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
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
with
w
i
t
h
evidence
e
v
i
d
e
n
c
e
of
o
f
the
t
h
e
completion
c
o
m
p
l
e
t
i
o
n
of
o
f
planned
p
l
a
n
n
e
d
activities
a
c
t
i
v
i
t
i
e
s
and
a
n
d
their
t
h
e
i
r
outputs
o
u
t
p
u
t
s
identified
i
d
e
n
t
i
f
i
e
d
as
a
s
part
p
a
r
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
3.0
3
.
0
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
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
.
This
T
h
i
s
document
d
o
c
u
m
e
n
t
does
d
o
e
s
not
n
o
t
prescribe
p
r
e
s
c
r
i
b
e
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(s)
o
r
g
a
n
i
z
a
t
i
o
n
(
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(s)
c
y
c
l
e
(
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
and
a
n
d
control
c
o
n
t
r
o
l
of,
o
f
,
and
a
n
d
confidence
c
o
n
f
i
d
e
n
c
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
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
planning
p
l
a
n
n
i
n
g
and
a
n
d
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(s)
c
y
c
l
e
(
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
software,
s
o
f
t
w
a
r
e
,
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
requirements,
r
e
q
u
i
r
e
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
product.
p
r
o
d
u
c
t
.
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
.
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
selected
s
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
.
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
Software
S
o
f
t
w
a
r
e
Components:
C
o
m
p
o
n
e
n
t
s
:
Component
C
o
m
p
o
n
e
n
t
W
W
……..
…
…
.
.
R-D-C-I
R
-
D
-
C
-
I
Component
C
o
m
p
o
n
e
n
t
X
X
……..
…
…
.
.
R-I
R
-
I
Component
C
o
m
p
o
n
e
n
t
Y
Y
……..
…
…
.
.
R-C-I
R
-
C
-
I
Component
C
o
m
p
o
n
e
n
t
Z
Z
……..
…
…
.
.
R-C-I-C-I-R-D-C-I
R
-
C
-
I
-
C
-
I
-
R
-
D
-
C
-
I
Legend:
L
e
g
e
n
d
:
Software
S
o
f
t
w
a
r
e
Product
P
r
o
d
u
c
t
R
R
D
D
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Design
D
e
s
i
g
n
C
C
I
I
Coding
C
o
d
i
n
g
Integration
I
n
t
e
g
r
a
t
i
o
n
Note:
N
o
t
e
:
For
F
o
r
simplicity,
s
i
m
p
l
i
c
i
t
y
,
the
t
h
e
software
s
o
f
t
w
a
r
e
planning
p
l
a
n
n
i
n
g
and
a
n
d
integral
i
n
t
e
g
r
a
l
processes
p
r
o
c
e
s
s
e
s
are
a
r
e
not
n
o
t
shown.
s
h
o
w
n
.
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
.
The
T
h
e
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
is
i
s
problem
p
r
o
b
l
e
m
reporting.
r
e
p
o
r
t
i
n
g
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
that
t
h
a
t
may
m
a
y
be
b
e
chosen
c
h
o
s
e
n
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
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
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
Not
N
o
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
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
.
23
2
3
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
,
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
should
s
h
o
u
l
d
be
b
e
examined
e
x
a
m
i
n
e
d
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
they
t
h
e
y
meet
m
e
e
t
transition
t
r
a
n
s
i
t
i
o
n
criteria.
c
r
i
t
e
r
i
a
.
Also,
A
l
s
o
,
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
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
that
t
h
a
t
will
w
i
l
l
satisfy
s
a
t
i
s
f
y
its
i
t
s
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
that
t
h
a
t
is
i
s
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
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
(see
(
s
e
e
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
(see
(
s
e
e
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
has
h
a
s
been
b
e
e
n
selected
s
e
l
e
c
t
e
d
and
a
n
d
defined
d
e
f
i
n
e
d
(see
(
s
e
e
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
(see
(
s
e
e
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
sections
s
e
c
t
i
o
n
s
4.3
4
.
3
and
a
n
d
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
(see
(
s
e
e
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
guidance
g
u
i
d
a
n
c
e
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Activities
A
c
t
i
v
i
t
i
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
include:
i
n
c
l
u
d
e
:
-
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
that
t
h
a
t
provide
p
r
o
v
i
d
e
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
life
l
i
f
e
cycle
c
y
c
l
e
processes.
p
r
o
c
e
s
s
e
s
.
See
S
e
e
also
a
l
s
o
9.1.
9
.
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
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
aid
a
i
d
error
e
r
r
o
r
prevention
p
r
e
v
e
n
t
i
o
n
and
a
n
d
provide
p
r
o
v
i
d
e
defect
d
e
f
e
c
t
detection
d
e
t
e
c
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
means
m
e
a
n
s
should
s
h
o
u
l
d
be
b
e
specified
s
p
e
c
i
f
i
e
d
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
dissimilarity
d
i
s
s
i
m
i
l
a
r
i
t
y
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
-
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
(see
(
s
e
e
4.6).
4
.
6
)
.
-
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
,
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
deactivation
d
e
a
c
t
i
v
a
t
i
o
n
mechanism
m
e
c
h
a
n
i
s
m
and
a
n
d
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
will
w
i
l
l
be
b
e
defined
d
e
f
i
n
e
d
and
a
n
d
verified
v
e
r
i
f
i
e
d
to
t
o
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
.
-
If
I
f
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
planned,
p
l
a
n
n
e
d
,
related
r
e
l
a
t
e
d
processes,
p
r
o
c
e
s
s
e
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
design
d
e
s
i
g
n
(see
(
s
e
e
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
.
-
When
W
h
e
n
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
are
a
r
e
planned,
p
l
a
n
n
e
d
,
the
t
h
e
following
f
o
l
l
o
w
i
n
g
should
s
h
o
u
l
d
be
b
e
addressed:
a
d
d
r
e
s
s
e
d
:
-
The
T
h
e
way
w
a
y
that
t
h
a
t
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
are
a
r
e
used.
u
s
e
d
.
-
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
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items.
i
t
e
m
s
.
-
The
T
h
e
processes
p
r
o
c
e
s
s
e
s
to
t
o
develop,
d
e
v
e
l
o
p
,
verify,
v
e
r
i
f
y
,
and
a
n
d
modify
m
o
d
i
f
y
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items,
i
t
e
m
s
,
and
a
n
d
any
a
n
y
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
.
-
Software
S
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
and
a
n
d
compatibility.
c
o
m
p
a
t
i
b
i
l
i
t
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
should
s
h
o
u
l
d
address
a
d
d
r
e
s
s
any
a
n
y
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
that
t
h
a
t
are
a
r
e
applicable.
a
p
p
l
i
c
a
b
l
e
.
-
If
I
f
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
activities
a
c
t
i
v
i
t
i
e
s
will
w
i
l
l
be
b
e
performed
p
e
r
f
o
r
m
e
d
by
b
y
a
a
supplier,
s
u
p
p
l
i
e
r
,
planning
p
l
a
n
n
i
n
g
should
s
h
o
u
l
d
address
a
d
d
r
e
s
s
supplier
s
u
p
p
l
i
e
r
oversight.
o
v
e
r
s
i
g
h
t
.
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
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
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
satisfied.
s
a
t
i
s
f
i
e
d
.
-
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
plans
p
l
a
n
s
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
(see
(
s
e
e
11.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
(see
(
s
e
e
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(s),
c
y
c
l
e
(
s
)
,
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
,
and
a
n
d
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
development
d
e
v
e
l
o
p
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
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Plan
P
l
a
n
(see
(
s
e
e
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
(see
(
s
e
e
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
.
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
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
(see
(
s
e
e
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
.
27
2
7
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
the
t
h
e
software
s
o
f
t
w
a
r
e
plans
p
l
a
n
s
include:
i
n
c
l
u
d
e
:
-
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
transition
t
r
a
n
s
i
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
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
product.
p
r
o
d
u
c
t
.
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
.
-
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
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
defines
d
e
f
i
n
e
s
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
(see
(
s
e
e
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
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
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
.
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
(see
(
s
e
e
12.2).
1
2
.
2
)
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
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
.
Activities
A
c
t
i
v
i
t
i
e
s
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
include:
i
n
c
l
u
d
e
:
-
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
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
reduce
r
e
d
u
c
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
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
.
-
The
T
h
e
use
u
s
e
of
o
f
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
.
This
T
h
i
s
selection
s
e
l
e
c
t
i
o
n
includes
i
n
c
l
u
d
e
s
the
t
h
e
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
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
.
-
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
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
reduce
r
e
d
u
c
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
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
.
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
for
f
o
r
compilers
c
o
m
p
i
l
e
r
s
and
a
n
d
autocode
a
u
t
o
c
o
d
e
generators.
g
e
n
e
r
a
t
o
r
s
.
-
Known
K
n
o
w
n
tool
t
o
o
l
problems
p
r
o
b
l
e
m
s
and
a
n
d
limitations
l
i
m
i
t
a
t
i
o
n
s
should
s
h
o
u
l
d
be
b
e
assessed
a
s
s
e
s
s
e
d
and
a
n
d
those
t
h
o
s
e
issues
i
s
s
u
e
s
which
w
h
i
c
h
can
c
a
n
adversely
a
d
v
e
r
s
e
l
y
affect
a
f
f
e
c
t
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
be
b
e
addressed.
a
d
d
r
e
s
s
e
d
.
-
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
needs
n
e
e
d
s
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
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
.
Additional
A
d
d
i
t
i
o
n
a
l
information
i
n
f
o
r
m
a
t
i
o
n
can
c
a
n
be
b
e
found
f
o
u
n
d
in
i
n
section
s
e
c
t
i
o
n
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-in
b
u
i
l
t
-
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
(see
(
s
e
e
6.4.4.2.b).
6
.
4
.
4
.
2
.
b
)
.
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
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
should
s
h
o
u
l
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
reverification
r
e
v
e
r
i
f
i
c
a
t
i
o
n
that
t
h
a
t
is
i
s
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
sections
s
e
c
t
i
o
n
s
6
6
and
a
n
d
12.1.3.
1
2
.
1
.
3
.
29
2
9
Note:
N
o
t
e
:
Although
A
l
t
h
o
u
g
h
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
once
o
n
c
e
all
a
l
l
of
o
f
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
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
compiler
c
o
m
p
i
l
e
r
is
i
s
only
o
n
l
y
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
and
a
n
d
not
n
o
t
necessarily
n
e
c
e
s
s
a
r
i
l
y
for
f
o
r
other
o
t
h
e
r
products.
p
r
o
d
u
c
t
s
.
-
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
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
defines
d
e
f
i
n
e
s
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
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
section
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
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
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
.
-
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
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
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
.
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
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
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
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
.
-
Robustness
R
o
b
u
s
t
n
e
s
s
should
s
h
o
u
l
d
be
b
e
considered
c
o
n
s
i
d
e
r
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
standards.
s
t
a
n
d
a
r
d
s
.
Note
N
o
t
e
1:
1
:
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
.
Note
N
o
t
e
2:
2
:
If
I
f
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
by
b
y
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
practices
p
r
a
c
t
i
c
e
s
to
t
o
detect
d
e
t
e
c
t
and
a
n
d
control
c
o
n
t
r
o
l
errors
e
r
r
o
r
s
in
i
n
stored
s
t
o
r
e
d
data,
d
a
t
a
,
and
a
n
d
refresh
r
e
f
r
e
s
h
and
a
n
d
monitor
m
o
n
i
t
o
r
hardware
h
a
r
d
w
a
r
e
status
s
t
a
t
u
s
and
a
n
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
may
m
a
y
be
b
e
used
u
s
e
d
to
t
o
mitigate
m
i
t
i
g
a
t
e
single
s
i
n
g
l
e
event
e
v
e
n
t
upsets.
u
p
s
e
t
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
Review
R
e
v
i
e
w
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
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
guidance
g
u
i
d
a
n
c
e
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Methods
M
e
t
h
o
d
s
are
a
r
e
chosen
c
h
o
s
e
n
that
t
h
a
t
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
.
-
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
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
(see
(
s
e
e
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
(see
(
s
e
e
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
coding
c
o
d
i
n
g
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
guidance
g
u
i
d
a
n
c
e
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
.
Note:
N
o
t
e
:
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
may
m
a
y
be
b
e
required
r
e
q
u
i
r
e
d
to
t
o
justify
j
u
s
t
i
f
y
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
a
a
single
s
i
n
g
l
e
level
l
e
v
e
l
of
o
f
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
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
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
.
Some
S
o
m
e
examples
e
x
a
m
p
l
e
s
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
might
m
i
g
h
t
be
b
e
determined
d
e
t
e
r
m
i
n
e
d
to
t
o
be
b
e
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
:
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
.
The
T
h
e
specification
s
p
e
c
i
f
i
c
a
t
i
o
n
of
o
f
a
a
periodic
p
e
r
i
o
d
i
c
monitor’s
m
o
n
i
t
o
r
’
s
iteration
i
t
e
r
a
t
i
o
n
rate
r
a
t
e
when
w
h
e
n
not
n
o
t
specified
s
p
e
c
i
f
i
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software.
s
o
f
t
w
a
r
e
.
The
T
h
e
addition
a
d
d
i
t
i
o
n
of
o
f
scaling
s
c
a
l
i
n
g
limits
l
i
m
i
t
s
when
w
h
e
n
using
u
s
i
n
g
fixed
f
i
x
e
d
point
p
o
i
n
t
arithmetic.
a
r
i
t
h
m
e
t
i
c
.
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
.
In
I
n
order
o
r
d
e
r
to
t
o
determine
d
e
t
e
r
m
i
n
e
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
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
system
s
y
s
t
e
m
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
all
a
l
l
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
made
m
a
d
e
available
a
v
a
i
l
a
b
l
e
to
t
o
the
t
h
e
system
s
y
s
t
e
m
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
process.
p
r
o
c
e
s
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
processes
p
r
o
c
e
s
s
e
s
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
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
defined
d
e
f
i
n
e
d
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
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
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
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
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
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
(see
(
s
e
e
11.9).
1
1
.
9
)
.
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
.
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
this
t
h
i
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
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
analyzed
a
n
a
l
y
z
e
d
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-
h
i
g
h
-
level
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
.
-
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
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
should
s
h
o
u
l
d
be
b
e
defined.
d
e
f
i
n
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
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
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
process.
p
r
o
c
e
s
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
If
I
f
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
are
a
r
e
planned,
p
l
a
n
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
describe
d
e
s
c
r
i
b
e
how
h
o
w
any
a
n
y
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
is
i
s
used
u
s
e
d
by
b
y
the
t
h
e
software.
s
o
f
t
w
a
r
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
also
a
l
s
o
specify
s
p
e
c
i
f
y
their
t
h
e
i
r
structure,
s
t
r
u
c
t
u
r
e
,
the
t
h
e
attributes
a
t
t
r
i
b
u
t
e
s
for
f
o
r
each
e
a
c
h
of
o
f
their
t
h
e
i
r
data
d
a
t
a
elements,
e
l
e
m
e
n
t
s
,
and,
a
n
d
,
when
w
h
e
n
applicable,
a
p
p
l
i
c
a
b
l
e
,
the
t
h
e
value
v
a
l
u
e
of
o
f
each
e
a
c
h
element.
e
l
e
m
e
n
t
.
The
T
h
e
values
v
a
l
u
e
s
of
o
f
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
elements
e
l
e
m
e
n
t
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
structure
s
t
r
u
c
t
u
r
e
of
o
f
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
and
a
n
d
the
t
h
e
attributes
a
t
t
r
i
b
u
t
e
s
of
o
f
its
i
t
s
data
d
a
t
a
elements.
e
l
e
m
e
n
t
s
.
33
3
3
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
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-
h
i
g
h
-
level
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
defined
d
e
f
i
n
e
d
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
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
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-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
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
(see
(
s
e
e
11.10)
1
1
.
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
.
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
include:
i
n
c
l
u
d
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
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
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
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
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
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
process.
p
r
o
c
e
s
s
.
-
Interfaces
I
n
t
e
r
f
a
c
e
s
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
,
in
i
n
the
t
h
e
form
f
o
r
m
of
o
f
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
,
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
to
t
o
be
b
e
consistent
c
o
n
s
i
s
t
e
n
t
between
b
e
t
w
e
e
n
the
t
h
e
components.
c
o
m
p
o
n
e
n
t
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
34
3
4
-
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
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
,
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
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
.
While
W
h
i
l
e
no
n
o
objective
o
b
j
e
c
t
i
v
e
guidance
g
u
i
d
a
n
c
e
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
more
m
o
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-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
.
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
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
designed
d
e
s
i
g
n
e
d
to
t
o
be
b
e
modified
m
o
d
i
f
i
e
d
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-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
.
User-
U
s
e
r
-
modifiable
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
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
.
The
T
h
e
activities
a
c
t
i
v
i
t
i
e
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
include:
i
n
c
l
u
d
e
:
-
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
.
If
I
f
the
t
h
e
protection
p
r
o
t
e
c
t
i
o
n
is
i
s
provided
p
r
o
v
i
d
e
d
by
b
y
software,
s
o
f
t
w
a
r
e
,
it
i
t
should
s
h
o
u
l
d
be
b
e
designed
d
e
s
i
g
n
e
d
and
a
n
d
verified
v
e
r
i
f
i
e
d
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
non-modifiable
n
o
n
-
m
o
d
i
f
i
a
b
l
e
software.
s
o
f
t
w
a
r
e
.
If
I
f
the
t
h
e
protection
p
r
o
t
e
c
t
i
o
n
is
i
s
provided
p
r
o
v
i
d
e
d
by
b
y
a
a
tool,
t
o
o
l
,
the
t
h
e
tool
t
o
o
l
should
s
h
o
u
l
d
be
b
e
categorized
c
a
t
e
g
o
r
i
z
e
d
and
a
n
d
qualified
q
u
a
l
i
f
i
e
d
as
a
s
defined
d
e
f
i
n
e
d
in
i
n
section
s
e
c
t
i
o
n
12.2.
1
2
.
2
.
-
The
T
h
e
means
m
e
a
n
s
provided
p
r
o
v
i
d
e
d
to
t
o
change
c
h
a
n
g
e
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
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.2.4
5
.
2
.
4
Designing
D
e
s
i
g
n
i
n
g
for
f
o
r
Deactivated
D
e
a
c
t
i
v
a
t
e
d
Code
C
o
d
e
Systems
S
y
s
t
e
m
s
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
,
such
s
u
c
h
as
a
s
unselected
u
n
s
e
l
e
c
t
e
d
functionality
f
u
n
c
t
i
o
n
a
l
i
t
y
or
o
r
unused
u
n
u
s
e
d
library
l
i
b
r
a
r
y
functions,
f
u
n
c
t
i
o
n
s
,
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
.
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
differs
d
i
f
f
e
r
s
from
f
r
o
m
dead
d
e
a
d
code.
c
o
d
e
.
The
T
h
e
activities
a
c
t
i
v
i
t
i
e
s
for
f
o
r
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
include:
i
n
c
l
u
d
e
:
-
A
A
mechanism
m
e
c
h
a
n
i
s
m
should
s
h
o
u
l
d
be
b
e
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
to
t
o
assure
a
s
s
u
r
e
that
t
h
a
t
deactivated
d
e
a
c
t
i
v
a
t
e
d
functions
f
u
n
c
t
i
o
n
s
or
o
r
components
c
o
m
p
o
n
e
n
t
s
have
h
a
v
e
no
n
o
adverse
a
d
v
e
r
s
e
impact
i
m
p
a
c
t
on
o
n
active
a
c
t
i
v
e
functions
f
u
n
c
t
i
o
n
s
or
o
r
components.
c
o
m
p
o
n
e
n
t
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
execution
e
x
e
c
u
t
i
o
n
of
o
f
deactivated
d
e
a
c
t
i
v
a
t
e
d
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
execution
e
x
e
c
u
t
i
o
n
of
o
f
activated
a
c
t
i
v
a
t
e
d
code.
c
o
d
e
.
35
3
5
-
The
T
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
deactivated
d
e
a
c
t
i
v
a
t
e
d
code,
c
o
d
e
,
like
l
i
k
e
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
the
t
h
e
active
a
c
t
i
v
e
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
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
.
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
.
Note:
N
o
t
e
:
For
F
o
r
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
,
compiling,
c
o
m
p
i
l
i
n
g
,
linking,
l
i
n
k
i
n
g
,
and
a
n
d
loading
l
o
a
d
i
n
g
are
a
r
e
dealt
d
e
a
l
t
with
w
i
t
h
under
u
n
d
e
r
the
t
h
e
Integration
I
n
t
e
g
r
a
t
i
o
n
Process
P
r
o
c
e
s
s
(see
(
s
e
e
5.4).
5
.
4
)
.
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
from
f
r
o
m
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.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
,
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
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
Source
S
o
u
r
c
e
Code
C
o
d
e
(see
(
s
e
e
11.11).
1
1
.
1
1
)
.
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
.
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
include:
i
n
c
l
u
d
e
:
-
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
.
-
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
,
and/or
a
n
d
/
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
.
-
Use
U
s
e
of
o
f
autocode
a
u
t
o
c
o
d
e
generators
g
e
n
e
r
a
t
o
r
s
should
s
h
o
u
l
d
conform
c
o
n
f
o
r
m
to
t
o
the
t
h
e
constraints
c
o
n
s
t
r
a
i
n
t
s
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
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
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
compiling,
c
o
m
p
i
l
i
n
g
,
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
(see
(
s
e
e
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
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
and
a
n
d
its
i
t
s
associated
a
s
s
o
c
i
a
t
e
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
are
a
r
e
produced
p
r
o
d
u
c
e
d
and
a
n
d
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
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
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
(see
(
s
e
e
11.12);
1
1
.
1
2
)
;
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
(see
(
s
e
e
11.22);
1
1
.
2
2
)
;
and
a
n
d
the
t
h
e
compiling,
c
o
m
p
i
l
i
n
g
,
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
.
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
this
t
h
i
s
process
p
r
o
c
e
s
s
include:
i
n
c
l
u
d
e
:
-
The
T
h
e
object
o
b
j
e
c
t
code
c
o
d
e
and
a
n
d
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
Code
C
o
d
e
and
a
n
d
compiling,
c
o
m
p
i
l
i
n
g
,
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
.
Any
A
n
y
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
should
s
h
o
u
l
d
be
b
e
generated.
g
e
n
e
r
a
t
e
d
.
-
Software
S
o
f
t
w
a
r
e
integration
i
n
t
e
g
r
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
a
a
host
h
o
s
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
the
t
h
e
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
-
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
.
-
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
product
p
r
o
d
u
c
t
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
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
.
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
:
-
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
.
-
An
A
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
patched
p
a
t
c
h
e
d
software
s
o
f
t
w
a
r
e
satisfies
s
a
t
i
s
f
i
e
s
all
a
l
l
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
objectives.
o
b
j
e
c
t
i
v
e
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
use
u
s
e
of
o
f
a
a
patch.
p
a
t
c
h
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
5.5
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
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
37
3
7
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
traceability
t
r
a
c
e
a
b
i
l
i
t
y
activities
a
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Trace
T
r
a
c
e
Data,
D
a
t
a
,
showing
s
h
o
w
i
n
g
the
t
h
e
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
association
a
s
s
o
c
i
a
t
i
o
n
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
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
,
is
i
s
developed.
d
e
v
e
l
o
p
e
d
.
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
this
t
h
i
s
Trace
T
r
a
c
e
Data
D
a
t
a
is
i
s
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software.
s
o
f
t
w
a
r
e
.
-
Give
G
i
v
e
visibility
v
i
s
i
b
i
l
i
t
y
to
t
o
those
t
h
o
s
e
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
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
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Trace
T
r
a
c
e
Data,
D
a
t
a
,
showing
s
h
o
w
i
n
g
the
t
h
e
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
association
a
s
s
o
c
i
a
t
i
o
n
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
low-level
l
o
w
-
l
e
v
e
l
requirements,
r
e
q
u
i
r
e
m
e
n
t
s
,
is
i
s
developed.
d
e
v
e
l
o
p
e
d
.
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
this
t
h
i
s
Trace
T
r
a
c
e
Data
D
a
t
a
is
i
s
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
high-level
h
i
g
h
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
-
Give
G
i
v
e
visibility
v
i
s
i
b
i
l
i
t
y
to
t
o
those
t
h
o
s
e
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
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
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
to
t
o
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
.
-
Trace
T
r
a
c
e
Data,
D
a
t
a
,
showing
s
h
o
w
i
n
g
the
t
h
e
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
association
a
s
s
o
c
i
a
t
i
o
n
between
b
e
t
w
e
e
n
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
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
.
The
T
h
e
purpose
p
u
r
p
o
s
e
of
o
f
this
t
h
i
s
Trace
T
r
a
c
e
Data
D
a
t
a
is
i
s
to:
t
o
:
-
Enable
E
n
a
b
l
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
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
.
-
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
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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}
39
3
9
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
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
,
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
(see
(
s
e
e
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
(see
(
s
e
e
11.3).
1
1
.
3
)
.
See
S
e
e
4.6
4
.
6
for
f
o
r
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
outputs
o
u
t
p
u
t
s
of
o
f
the
t
h
e
planning
p
l
a
n
n
i
n
g
process.
p
r
o
c
e
s
s
.
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
sections
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
"
to
t
o
discuss
d
i
s
c
u
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
activities,
a
c
t
i
v
i
t
i
e
s
,
which
w
h
i
c
h
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
tests.
t
e
s
t
s
.
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
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
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
.
6.1
6
.
1
Purpose
P
u
r
p
o
s
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
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
.
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
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
verifies
v
e
r
i
f
i
e
s
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
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-
l
o
w
-
level
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
40
4
0
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
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
(that
(
t
h
a
t
is,
i
s
,
intended
i
n
t
e
n
d
e
d
function),
f
u
n
c
t
i
o
n
)
,
and
a
n
d
provides
p
r
o
v
i
d
e
s
confidence
c
o
n
f
i
d
e
n
c
e
in
i
n
the
t
h
e
absence
a
b
s
e
n
c
e
of
o
f
unintended
u
n
i
n
t
e
n
d
e
d
functionality.
f
u
n
c
t
i
o
n
a
l
i
t
y
.
-
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
robust
r
o
b
u
s
t
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
such
s
u
c
h
that
t
h
a
t
it
i
t
can
c
a
n
respond
r
e
s
p
o
n
d
correctly
c
o
r
r
e
c
t
l
y
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
.
-
The
T
h
e
means
m
e
a
n
s
used
u
s
e
d
to
t
o
perform
p
e
r
f
o
r
m
this
t
h
i
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
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
.
6.2
6
.
2
Overview
O
v
e
r
v
i
e
w
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
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
and
a
n
d
procedures
p
r
o
c
e
d
u
r
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
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
,
software
s
o
f
t
w
a
r
e
architecture,
a
r
c
h
i
t
e
c
t
u
r
e
,
Trace
T
r
a
c
e
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
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
Cases
C
a
s
e
s
and
a
n
d
Procedures
P
r
o
c
e
d
u
r
e
s
(see
(
s
e
e
11.13),
1
1
.
1
3
)
,
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
(see
(
s
e
e
11.14),
1
1
.
1
4
)
,
and
a
n
d
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
Trace
T
r
a
c
e
Data
D
a
t
a
(see
(
s
e
e
11.21).
1
1
.
2
1
)
.
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
.
Software
S
o
f
t
w
a
r
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
include:
i
n
c
l
u
d
e
:
-
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
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
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
as
a
s
applicable.
a
p
p
l
i
c
a
b
l
e
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Reverification
R
e
v
e
r
i
f
i
c
a
t
i
o
n
should
s
h
o
u
l
d
be
b
e
conducted
c
o
n
d
u
c
t
e
d
following
f
o
l
l
o
w
i
n
g
corrective
c
o
r
r
e
c
t
i
v
e
actions
a
c
t
i
o
n
s
and/or
a
n
d
/
o
r
changes
c
h
a
n
g
e
s
that
t
h
a
t
could
c
o
u
l
d
impact
i
m
p
a
c
t
the
t
h
e
previously
p
r
e
v
i
o
u
s
l
y
verified
v
e
r
i
f
i
e
d
functionality.
f
u
n
c
t
i
o
n
a
l
i
t
y
.
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
the
t
h
e
modification
m
o
d
i
f
i
c
a
t
i
o
n
has
h
a
s
been
b
e
e
n
correctly
c
o
r
r
e
c
t
l
y
implemented.
i
m
p
l
e
m
e
n
t
e
d
.
41
4
1
-
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
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
.
A
A
tool
t
o
o
l
may
m
a
y
be
b
e
used
u
s
e
d
to
t
o
achieve
a
c
h
i
e
v
e
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
.
For
F
o
r
independence,
i
n
d
e
p
e
n
d
e
n
c
e
,
the
t
h
e
person
p
e
r
s
o
n
who
w
h
o
created
c
r
e
a
t
e
d
a
a
set
s
e
t
of
o
f
low-level
l
o
w
-
l
e
v
e
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
should
s
h
o
u
l
d
not
n
o
t
be
b
e
the
t
h
e
same
s
a
m
e
person
p
e
r
s
o
n
who
w
h
o
developed
d
e
v
e
l
o
p
e
d
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
Source
S
o
u
r
c
e
Code
C
o
d
e
from
f
r
o
m
those
t
h
o
s
e
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
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
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
.
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
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
There
T
h
e
r
e
may
m
a
y
be
b
e
cases
c
a
s
e
s
where
w
h
e
r
e
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
objectives
o
b
j
e
c
t
i
v
e
s
described
d
e
s
c
r
i
b
e
d
in
i
n
this
t
h
i
s
section
s
e
c
t
i
o
n
cannot
c
a
n
n
o
t
be
b
e
completely
c
o
m
p
l
e
t
e
l
y
satisfied
s
a
t
i
s
f
i
e
d
via
v
i
a
reviews
r
e
v
i
e
w
s
and
a
n
d
analyses
a
n
a
l
y
s
e
s
alone.
a
l
o
n
e
.
In
I
n
such
s
u
c
h
cases,
c
a
s
e
s
,
those
t
h
o
s
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
objectives
o
b
j
e
c
t
i
v
e
s
may
m
a
y
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
with
w
i
t
h
additional
a
d
d
i
t
i
o
n
a
l
testing
t
e
s
t
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
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
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
tests
t
e
s
t
s
may
m
a
y
be
b
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
establish
e
s
t
a
b
l
i
s
h
the
t
h
e
worst-
w
o
r
s
t
-
case
c
a
s
e
execution
e
x
e
c
u
t
i
o
n
time
t
i
m
e
or
o
r
verification
v
e
r
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
stack
s
t
a
c
k
usage.
u
s
a
g
e
.
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
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
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-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
are
a
r
e
satisfied
s
a
t
i
s
f
i
e
d
by
b
y
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
,
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
.
b.
b
.
c.
c
.
d.
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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-
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
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
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
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
confirm
c
o
n
f
i
r
m
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
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
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
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
.
b.
b
.
c.
c
.
d.
d
.
e.
e
.
f.
f
.
-
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
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
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
.
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
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
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
.
If
I
f
the
t
h
e
interface
i
n
t
e
r
f
a
c
e
is
i
s
to
t
o
a
a
component
c
o
m
p
o
n
e
n
t
of
o
f
a
a
lower
l
o
w
e
r
software
s
o
f
t
w
a
r
e
level,
l
e
v
e
l
,
it
i
t
should
s
h
o
u
l
d
also
a
l
s
o
be
b
e
confirmed
c
o
n
f
i
r
m
e
d
that
t
h
a
t
the
t
h
e
higher
h
i
g
h
e
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
component
c
o
m
p
o
n
e
n
t
has
h
a
s
appropriate
a
p
p
r
o
p
r
i
a
t
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
protection
p
r
o
t
e
c
t
i
o
n
mechanisms
m
e
c
h
a
n
i
s
m
s
in
i
n
place
p
l
a
c
e
to
t
o
protect
p
r
o
t
e
c
t
itself
i
t
s
e
l
f
from
f
r
o
m
potential
p
o
t
e
n
t
i
a
l
erroneous
e
r
r
o
n
e
o
u
s
inputs
i
n
p
u
t
s
from
f
r
o
m
the
t
h
e
lower
l
o
w
e
r
software
s
o
f
t
w
a
r
e
level
l
e
v
e
l
component.
c
o
m
p
o
n
e
n
t
.
43
4
3
-
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
.
d.
d
.
e.
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
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
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
deviations
d
e
v
i
a
t
i
o
n
s
to
t
o
complexity
c
o
m
p
l
e
x
i
t
y
restriction
r
e
s
t
r
i
c
t
i
o
n
and
a
n
d
design
d
e
s
i
g
n
construct
c
o
n
s
t
r
u
c
t
rules.
r
u
l
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
.
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
Source
S
o
u
r
c
e
Code
C
o
d
e
These
T
h
e
s
e
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
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
.
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
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
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
and
a
n
d
confirm
c
o
n
f
i
r
m
that
t
h
a
t
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
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
:
-
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
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
.
b.
b
.
c.
c
.
d.
d
.
e.
e
.
-
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
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
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
.
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
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
,
memory
m
e
m
o
r
y
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
,
floating-point
f
l
o
a
t
i
n
g
-
p
o
i
n
t
arithmetic,
a
r
i
t
h
m
e
t
i
c
,
resource
r
e
s
o
u
r
c
e
contention
c
o
n
t
e
n
t
i
o
n
and
a
n
d
limitations,
l
i
m
i
t
a
t
i
o
n
s
,
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
,
cache
c
a
c
h
e
management,
m
a
n
a
g
e
m
e
n
t
,
unused
u
n
u
s
e
d
variables,
v
a
r
i
a
b
l
e
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
interrupt
i
n
t
e
r
r
u
p
t
conflicts.
c
o
n
f
l
i
c
t
s
.
The
T
h
e
compiler
c
o
m
p
i
l
e
r
(including
(
i
n
c
l
u
d
i
n
g
its
i
t
s
options),
o
p
t
i
o
n
s
)
,
the
t
h
e
linker
l
i
n
k
e
r
(including
(
i
n
c
l
u
d
i
n
g
its
i
t
s
options),
o
p
t
i
o
n
s
)
,
and
a
n
d
some
s
o
m
e
hardware
h
a
r
d
w
a
r
e
features
f
e
a
t
u
r
e
s
may
m
a
y
have
h
a
v
e
an
a
n
impact
i
m
p
a
c
t
on
o
n
the
t
h
e
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
and
a
n
d
this
t
h
i
s
impact
i
m
p
a
c
t
should
s
h
o
u
l
d
be
b
e
assessed.
a
s
s
e
s
s
e
d
.
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
These
T
h
e
s
e
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
e
s
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
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
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
complete
c
o
m
p
l
e
t
e
and
a
n
d
correct.
c
o
r
r
e
c
t
.
Activities
A
c
t
i
v
i
t
i
e
s
include
i
n
c
l
u
d
e
conducting
c
o
n
d
u
c
t
i
n
g
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
compiling,
c
o
m
p
i
l
i
n
g
,
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
.
Typical
T
y
p
i
c
a
l
examples
e
x
a
m
p
l
e
s
of
o
f
potential
p
o
t
e
n
t
i
a
l
errors
e
r
r
o
r
s
include:
i
n
c
l
u
d
e
:
Compiler
C
o
m
p
i
l
e
r
warnings.
w
a
r
n
i
n
g
s
.
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
.
6.4
6
.
4
Software
S
o
f
t
w
a
r
e
Testing
T
e
s
t
i
n
g
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
.
Software
S
o
f
t
w
a
r
e
testing
t
e
s
t
i
n
g
is
i
s
used
u
s
e
d
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
and
a
n
d
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
that
t
h
a
t
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
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
software
s
o
f
t
w
a
r
e
testing
t
e
s
t
i
n
g
are
a
r
e
to
t
o
execute
e
x
e
c
u
t
e
the
t
h
e
software
s
o
f
t
w
a
r
e
to
t
o
confirm
c
o
n
f
i
r
m
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
complies
c
o
m
p
l
i
e
s
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
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
robust
r
o
b
u
s
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
.
-
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
complies
c
o
m
p
l
i
e
s
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
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
robust
r
o
b
u
s
t
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
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
compatible
c
o
m
p
a
t
i
b
l
e
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
.
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
activities
a
c
t
i
v
i
t
i
e
s
that
t
h
a
t
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
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
.
The
T
h
e
diagram
d
i
a
g
r
a
m
shows
s
h
o
w
s
three
t
h
r
e
e
types
t
y
p
e
s
of
o
f
testing,
t
e
s
t
i
n
g
,
which
w
h
i
c
h
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
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
:
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
.
45
4
5
From
F
r
o
m
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
(Section
(
S
e
c
t
i
o
n
5)
5
)
Software
S
o
f
t
w
a
r
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
Generation
G
e
n
e
r
a
t
i
o
n
(6.4.2.1,
(
6
.
4
.
2
.
1
,
6.4.2.2)
6
.
4
.
2
.
2
)
Additional
A
d
d
i
t
i
o
n
a
l
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
(6.2.b)
(
6
.
2
.
b
)
Low-Level
L
o
w
-
L
e
v
e
l
Tests
T
e
s
t
s
(6.4.3.c)
(
6
.
4
.
3
.
c
)
Software
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
(6.4.3.b)
(
6
.
4
.
3
.
b
)
Hardware/
H
a
r
d
w
a
r
e
/
Software
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
(6.4.3.a)
(
6
.
4
.
3
.
a
)
Software
S
o
f
t
w
a
r
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
(6.4.4.1)
(
6
.
4
.
4
.
1
)
(6.4.4.1.a,
(
6
.
4
.
4
.
1
.
a
,
b,
b
,
c,
c
,
d)
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
Process
P
r
o
c
e
s
s
(Section
(
S
e
c
t
i
o
n
5)
5
)
(6.4.4.3.b,
(
6
.
4
.
4
.
3
.
b
,
6.4.4.3.c)
6
.
4
.
4
.
3
.
c
)
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
(6.4.4.2,
(
6
.
4
.
4
.
2
,
6.4.4.3)
6
.
4
.
4
.
3
)
(6.4.4.3.a)
(
6
.
4
.
4
.
3
.
a
)
(6.4.4.3.a,
(
6
.
4
.
4
.
3
.
a
,
6.4.4.3.d)
6
.
4
.
4
.
3
.
d
)
Direct
D
i
r
e
c
t
Path
P
a
t
h
Conditional
C
o
n
d
i
t
i
o
n
a
l
Path
P
a
t
h
End
E
n
d
of
o
f
Testing
T
e
s
t
i
n
g
Extraneous,
E
x
t
r
a
n
e
o
u
s
,
Dead
D
e
a
d
and
a
n
d
Deactivated
D
e
a
c
t
i
v
a
t
e
d
Code
C
o
d
e
Resolution
R
e
s
o
l
u
t
i
o
n
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
Activities
A
c
t
i
v
i
t
i
e
s
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
46
4
6
6.4.1
6
.
4
.
1
Test
T
e
s
t
Environment
E
n
v
i
r
o
n
m
e
n
t
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
.
A
A
preferred
p
r
e
f
e
r
r
e
d
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
an
a
n
environment
e
n
v
i
r
o
n
m
e
n
t
that
t
h
a
t
closely
c
l
o
s
e
l
y
resembles
r
e
s
e
m
b
l
e
s
the
t
h
e
behavior
b
e
h
a
v
i
o
r
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
.
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
test
t
e
s
t
environment
e
n
v
i
r
o
n
m
e
n
t
include:
i
n
c
l
u
d
e
:
-
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
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
.
Activities
A
c
t
i
v
i
t
i
e
s
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
selection
s
e
l
e
c
t
i
o
n
include:
i
n
c
l
u
d
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
to
t
o
include
i
n
c
l
u
d
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
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
.
-
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
.
Note:
N
o
t
e
:
Robustness
R
o
b
u
s
t
n
e
s
s
test
t
e
s
t
cases
c
a
s
e
s
are
a
r
e
requirements-based.
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
.
The
T
h
e
robustness
r
o
b
u
s
t
n
e
s
s
testing
t
e
s
t
i
n
g
criteria
c
r
i
t
e
r
i
a
cannot
c
a
n
n
o
t
be
b
e
fully
f
u
l
l
y
satisfied
s
a
t
i
s
f
i
e
d
if
i
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
do
d
o
not
n
o
t
specify
s
p
e
c
i
f
y
the
t
h
e
correct
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
abnormal
a
b
n
o
r
m
a
l
conditions
c
o
n
d
i
t
i
o
n
s
and
a
n
d
inputs.
i
n
p
u
t
s
.
The
T
h
e
test
t
e
s
t
cases
c
a
s
e
s
may
m
a
y
reveal
r
e
v
e
a
l
inadequacies
i
n
a
d
e
q
u
a
c
i
e
s
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
,
in
i
n
which
w
h
i
c
h
case
c
a
s
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
should
s
h
o
u
l
d
be
b
e
modified.
m
o
d
i
f
i
e
d
.
Conversely,
C
o
n
v
e
r
s
e
l
y
,
if
i
f
a
a
complete
c
o
m
p
l
e
t
e
set
s
e
t
of
o
f
requirements
r
e
q
u
i
r
e
m
e
n
t
s
exists
e
x
i
s
t
s
that
t
h
a
t
covers
c
o
v
e
r
s
all
a
l
l
abnormal
a
b
n
o
r
m
a
l
conditions
c
o
n
d
i
t
i
o
n
s
and
a
n
d
inputs,
i
n
p
u
t
s
,
the
t
h
e
robustness
r
o
b
u
s
t
n
e
s
s
test
t
e
s
t
cases
c
a
s
e
s
will
w
i
l
l
follow
f
o
l
l
o
w
from
f
r
o
m
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
.
-
Test
T
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
are
a
r
e
generated
g
e
n
e
r
a
t
e
d
from
f
r
o
m
the
t
h
e
test
t
e
s
t
cases.
c
a
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
Normal
N
o
r
m
a
l
range
r
a
n
g
e
test
t
e
s
t
cases
c
a
s
e
s
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
.
Activities
A
c
t
i
v
i
t
i
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
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
.
47
4
7
-
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
.
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
Robustness
R
o
b
u
s
t
n
e
s
s
test
t
e
s
t
cases
c
a
s
e
s
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
.
Activities
A
c
t
i
v
i
t
i
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
.
-
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
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
methods
m
e
t
h
o
d
s
discussed
d
i
s
c
u
s
s
e
d
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
are
a
r
e
requirements-
r
e
q
u
i
r
e
m
e
n
t
s
-
based
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
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
.
Requirements-
R
e
q
u
i
r
e
m
e
n
t
s
-
based
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
ensures
e
n
s
u
r
e
s
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
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
control
c
o
n
t
r
o
l
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
.
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
ensures
e
n
s
u
r
e
s
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
.
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
ensures
e
n
s
u
r
e
s
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
.
49
4
9
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
.
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
to
t
o
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
coverage
c
o
v
e
r
a
g
e
criteria.
c
r
i
t
e
r
i
a
.
If
I
f
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
showed
s
h
o
w
e
d
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
coverage
c
o
v
e
r
a
g
e
was
w
a
s
not
n
o
t
met,
m
e
t
,
additional
a
d
d
i
t
i
o
n
a
l
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
identified
i
d
e
n
t
i
f
i
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
(see
(
s
e
e
6.4.4.3)
6
.
4
.
4
.
3
)
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
for
f
o
r
test
t
e
s
t
coverage
c
o
v
e
r
a
g
e
analysis
a
n
a
l
y
s
i
s
are:
a
r
e
:
-
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
-
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
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
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
-
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
structure
s
t
r
u
c
t
u
r
e
to
t
o
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
coverage
c
o
v
e
r
a
g
e
criteria
c
r
i
t
e
r
i
a
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
-
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
structure,
s
t
r
u
c
t
u
r
e
,
both
b
o
t
h
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
,
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
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
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Analysis,
A
n
a
l
y
s
i
s
,
using
u
s
i
n
g
the
t
h
e
associated
a
s
s
o
c
i
a
t
e
d
Trace
T
r
a
c
e
Data,
D
a
t
a
,
to
t
o
confirm
c
o
n
f
i
r
m
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
.
-
Analysis
A
n
a
l
y
s
i
s
to
t
o
confirm
c
o
n
f
i
r
m
that
t
h
a
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
section
s
e
c
t
i
o
n
6.4.2.
6
.
4
.
2
.
-
Resolution
R
e
s
o
l
u
t
i
o
n
of
o
f
any
a
n
y
deficiencies
d
e
f
i
c
i
e
n
c
i
e
s
identified
i
d
e
n
t
i
f
i
e
d
in
i
n
the
t
h
e
analysis.
a
n
a
l
y
s
i
s
.
Possible
P
o
s
s
i
b
l
e
solutions
s
o
l
u
t
i
o
n
s
are
a
r
e
adding
a
d
d
i
n
g
or
o
r
enhancing
e
n
h
a
n
c
i
n
g
test
t
e
s
t
cases.
c
a
s
e
s
.
-
Analysis
A
n
a
l
y
s
i
s
to
t
o
confirm
c
o
n
f
i
r
m
that
t
h
a
t
all
a
l
l
the
t
h
e
test
t
e
s
t
cases,
c
a
s
e
s
,
and
a
n
d
thus
t
h
u
s
all
a
l
l
the
t
h
e
test
t
e
s
t
procedures,
p
r
o
c
e
d
u
r
e
s
,
used
u
s
e
d
to
t
o
achieve
a
c
h
i
e
v
e
structural
s
t
r
u
c
t
u
r
a
l
coverage,
c
o
v
e
r
a
g
e
,
are
a
r
e
traceable
t
r
a
c
e
a
b
l
e
to
t
o
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
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
This
T
h
i
s
analysis
a
n
a
l
y
s
i
s
determines
d
e
t
e
r
m
i
n
e
s
which
w
h
i
c
h
code
c
o
d
e
structure,
s
t
r
u
c
t
u
r
e
,
including
i
n
c
l
u
d
i
n
g
interfaces
i
n
t
e
r
f
a
c
e
s
between
b
e
t
w
e
e
n
components,
c
o
m
p
o
n
e
n
t
s
,
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
,
including
i
n
c
l
u
d
i
n
g
interfaces,
i
n
t
e
r
f
a
c
e
s
,
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
Analysis
A
n
a
l
y
s
i
s
of
o
f
the
t
h
e
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
information
i
n
f
o
r
m
a
t
i
o
n
collected
c
o
l
l
e
c
t
e
d
during
d
u
r
i
n
g
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
to
t
o
confirm
c
o
n
f
i
r
m
that
t
h
a
t
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
is
i
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
level.
l
e
v
e
l
.
-
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
,
object
o
b
j
e
c
t
code,
c
o
d
e
,
or
o
r
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
Independent
I
n
d
e
p
e
n
d
e
n
t
of
o
f
the
t
h
e
code
c
o
d
e
form
f
o
r
m
on
o
n
which
w
h
i
c
h
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
is
i
s
performed,
p
e
r
f
o
r
m
e
d
,
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
A
A
and
a
n
d
a
a
compiler,
c
o
m
p
i
l
e
r
,
linker,
l
i
n
k
e
r
,
or
o
r
other
o
t
h
e
r
means
m
e
a
n
s
generates
g
e
n
e
r
a
t
e
s
additional
a
d
d
i
t
i
o
n
a
l
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
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
.
Note:
N
o
t
e
:
“Additional
“
A
d
d
i
t
i
o
n
a
l
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
”
is
i
s
code
c
o
d
e
that
t
h
a
t
introduces
i
n
t
r
o
d
u
c
e
s
branches
b
r
a
n
c
h
e
s
or
o
r
side
s
i
d
e
effects
e
f
f
e
c
t
s
that
t
h
a
t
are
a
r
e
not
n
o
t
immediately
i
m
m
e
d
i
a
t
e
l
y
apparent
a
p
p
a
r
e
n
t
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
.
This
T
h
i
s
means
m
e
a
n
s
that
t
h
a
t
compiler-generated
c
o
m
p
i
l
e
r
-
g
e
n
e
r
a
t
e
d
array-
a
r
r
a
y
-
bound
b
o
u
n
d
checks,
c
h
e
c
k
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
are
a
r
e
not
n
o
t
considered
c
o
n
s
i
d
e
r
e
d
to
t
o
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
Source
S
o
u
r
c
e
Code
C
o
d
e
statements
s
t
a
t
e
m
e
n
t
s
for
f
o
r
the
t
h
e
purposes
p
u
r
p
o
s
e
s
of
o
f
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
,
and
a
n
d
should
s
h
o
u
l
d
be
b
e
subjected
s
u
b
j
e
c
t
e
d
to
t
o
additional
a
d
d
i
t
i
o
n
a
l
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
-
Analysis
A
n
a
l
y
s
i
s
to
t
o
confirm
c
o
n
f
i
r
m
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
testing
t
e
s
t
i
n
g
has
h
a
s
exercised
e
x
e
r
c
i
s
e
d
the
t
h
e
data
d
a
t
a
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
code
c
o
d
e
components.
c
o
m
p
o
n
e
n
t
s
.
-
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
(see
(
s
e
e
6.4.4.3).
6
.
4
.
4
.
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
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
including
i
n
c
l
u
d
i
n
g
interfaces
i
n
t
e
r
f
a
c
e
s
that
t
h
a
t
were
w
e
r
e
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
will
w
i
l
l
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
.
Causes
C
a
u
s
e
s
of
o
f
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
including
i
n
c
l
u
d
i
n
g
interfaces,
i
n
t
e
r
f
a
c
e
s
,
and
a
n
d
associated
a
s
s
o
c
i
a
t
e
d
activities
a
c
t
i
v
i
t
i
e
s
to
t
o
resolve
r
e
s
o
l
v
e
them
t
h
e
m
include:
i
n
c
l
u
d
e
:
-
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
augmented
a
u
g
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
.
b.
b
.
c.
c
.
-
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
.
Extraneous
E
x
t
r
a
n
e
o
u
s
code,
c
o
d
e
,
including
i
n
c
l
u
d
i
n
g
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
.
If
I
f
extraneous
e
x
t
r
a
n
e
o
u
s
code
c
o
d
e
is
i
s
found
f
o
u
n
d
at
a
t
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
or
o
r
object
o
b
j
e
c
t
code
c
o
d
e
level,
l
e
v
e
l
,
it
i
t
may
m
a
y
be
b
e
allowed
a
l
l
o
w
e
d
to
t
o
remain
r
e
m
a
i
n
only
o
n
l
y
if
i
f
analysis
a
n
a
l
y
s
i
s
shows
s
h
o
w
s
it
i
t
does
d
o
e
s
not
n
o
t
exist
e
x
i
s
t
in
i
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
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
due
d
u
e
to
t
o
smart
s
m
a
r
t
compiling,
c
o
m
p
i
l
i
n
g
,
linking,
l
i
n
k
i
n
g
,
or
o
r
some
s
o
m
e
other
o
t
h
e
r
mechanism),
m
e
c
h
a
n
i
s
m
)
,
and
a
n
d
procedures
p
r
o
c
e
d
u
r
e
s
are
a
r
e
in
i
n
place
p
l
a
c
e
to
t
o
prevent
p
r
e
v
e
n
t
inclusion
i
n
c
l
u
s
i
o
n
in
i
n
future
f
u
t
u
r
e
builds.
b
u
i
l
d
s
.
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code:
c
o
d
e
:
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
should
s
h
o
u
l
d
be
b
e
handled
h
a
n
d
l
e
d
in
i
n
one
o
n
e
of
o
f
two
t
w
o
ways,
w
a
y
s
,
depending
d
e
p
e
n
d
i
n
g
upon
u
p
o
n
its
i
t
s
defined
d
e
f
i
n
e
d
category:
c
a
t
e
g
o
r
y
:
1.
1
.
Category
C
a
t
e
g
o
r
y
One:
O
n
e
:
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
that
t
h
a
t
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
current
c
u
r
r
e
n
t
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
any
a
n
y
certified
c
e
r
t
i
f
i
e
d
product.
p
r
o
d
u
c
t
.
For
F
o
r
this
t
h
i
s
category,
c
a
t
e
g
o
r
y
,
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
the
t
h
e
deactivated
d
e
a
c
t
i
v
a
t
e
d
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
.
Any
A
n
y
reassignment
r
e
a
s
s
i
g
n
m
e
n
t
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
Category
C
a
t
e
g
o
r
y
One
O
n
e
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
should
s
h
o
u
l
d
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
and
a
n
d
documented
d
o
c
u
m
e
n
t
e
d
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
.
Similarly,
S
i
m
i
l
a
r
l
y
,
any
a
n
y
alleviation
a
l
l
e
v
i
a
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
for
f
o
r
Category
C
a
t
e
g
o
r
y
One
O
n
e
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
should
s
h
o
u
l
d
be
b
e
justified
j
u
s
t
i
f
i
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
documented
d
o
c
u
m
e
n
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
.
51
5
1
2.
2
.
Category
C
a
t
e
g
o
r
y
Two:
T
w
o
:
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
that
t
h
a
t
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
approved
a
p
p
r
o
v
e
d
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
.
6.4.5
6
.
4
.
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
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
These
T
h
e
s
e
review
r
e
v
i
e
w
and
a
n
d
analysis
a
n
a
l
y
s
i
s
activities
a
c
t
i
v
i
t
i
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
testing
t
e
s
t
i
n
g
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
:
-
Test
T
e
s
t
cases:
c
a
s
e
s
:
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
related
r
e
l
a
t
e
d
to
t
o
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
are
a
r
e
presented
p
r
e
s
e
n
t
e
d
in
i
n
sections
s
e
c
t
i
o
n
s
6.4.4.a
6
.
4
.
4
.
a
and
a
n
d
6.4.4.b.
6
.
4
.
4
.
b
.
b.
b
.
-
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
,
including
i
n
c
l
u
d
i
n
g
expected
e
x
p
e
c
t
e
d
results,
r
e
s
u
l
t
s
,
were
w
e
r
e
correctly
c
o
r
r
e
c
t
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
.
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.5
6
.
5
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
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
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
traceability
t
r
a
c
e
a
b
i
l
i
t
y
activities
a
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Trace
T
r
a
c
e
Data,
D
a
t
a
,
showing
s
h
o
w
i
n
g
the
t
h
e
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
association
a
s
s
o
c
i
a
t
i
o
n
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
test
t
e
s
t
cases,
c
a
s
e
s
,
is
i
s
developed.
d
e
v
e
l
o
p
e
d
.
This
T
h
i
s
Trace
T
r
a
c
e
Data
D
a
t
a
supports
s
u
p
p
o
r
t
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
.
-
Trace
T
r
a
c
e
Data,
D
a
t
a
,
showing
s
h
o
w
i
n
g
the
t
h
e
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
association
a
s
s
o
c
i
a
t
i
o
n
between
b
e
t
w
e
e
n
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
,
is
i
s
developed.
d
e
v
e
l
o
p
e
d
.
This
T
h
i
s
Trace
T
r
a
c
e
Data
D
a
t
a
enables
e
n
a
b
l
e
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
that
t
h
a
t
the
t
h
e
complete
c
o
m
p
l
e
t
e
set
s
e
t
of
o
f
test
t
e
s
t
cases
c
a
s
e
s
has
h
a
s
been
b
e
e
n
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
.
-
Trace
T
r
a
c
e
Data,
D
a
t
a
,
showing
s
h
o
w
i
n
g
the
t
h
e
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
association
a
s
s
o
c
i
a
t
i
o
n
between
b
e
t
w
e
e
n
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
,
is
i
s
developed.
d
e
v
e
l
o
p
e
d
.
This
T
h
i
s
Trace
T
r
a
c
e
Data
D
a
t
a
enables
e
n
a
b
l
e
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
that
t
h
a
t
the
t
h
e
complete
c
o
m
p
l
e
t
e
set
s
e
t
of
o
f
test
t
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
has
h
a
s
been
b
e
e
n
executed.
e
x
e
c
u
t
e
d
.
6.6
6
.
6
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Items
I
t
e
m
s
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
a
a
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
can
c
a
n
be
b
e
conducted
c
o
n
d
u
c
t
e
d
separately
s
e
p
a
r
a
t
e
l
y
from
f
r
o
m
the
t
h
e
verification
v
e
r
i
f
i
c
a
t
i
o
n
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
if
i
f
all
a
l
l
of
o
f
the
t
h
e
following
f
o
l
l
o
w
i
n
g
apply:
a
p
p
l
y
:
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
has
h
a
s
been
b
e
e
n
developed
d
e
v
e
l
o
p
e
d
and
a
n
d
verified
v
e
r
i
f
i
e
d
by
b
y
normal
n
o
r
m
a
l
range
r
a
n
g
e
testing
t
e
s
t
i
n
g
to
t
o
correctly
c
o
r
r
e
c
t
l
y
handle
h
a
n
d
l
e
all
a
l
l
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files
F
i
l
e
s
that
t
h
a
t
comply
c
o
m
p
l
y
with
w
i
t
h
their
t
h
e
i
r
defined
d
e
f
i
n
e
d
structure
s
t
r
u
c
t
u
r
e
and
a
n
d
attributes.
a
t
t
r
i
b
u
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
is
i
s
robust
r
o
b
u
s
t
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files
F
i
l
e
s
structures
s
t
r
u
c
t
u
r
e
s
and
a
n
d
attributes.
a
t
t
r
i
b
u
t
e
s
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
All
A
l
l
behavior
b
e
h
a
v
i
o
r
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
resulting
r
e
s
u
l
t
i
n
g
from
f
r
o
m
the
t
h
e
contents
c
o
n
t
e
n
t
s
of
o
f
the
t
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
can
c
a
n
be
b
e
verified.
v
e
r
i
f
i
e
d
.
The
T
h
e
structure
s
t
r
u
c
t
u
r
e
of
o
f
the
t
h
e
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
allows
a
l
l
o
w
s
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
to
t
o
be
b
e
managed
m
a
n
a
g
e
d
separately.
s
e
p
a
r
a
t
e
l
y
.
Unless
U
n
l
e
s
s
all
a
l
l
conditions
c
o
n
d
i
t
i
o
n
s
above
a
b
o
v
e
are
a
r
e
met,
m
e
t
,
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
should
s
h
o
u
l
d
not
n
o
t
be
b
e
verified
v
e
r
i
f
i
e
d
separately
s
e
p
a
r
a
t
e
l
y
from
f
r
o
m
the
t
h
e
rest
r
e
s
t
of
o
f
the
t
h
e
software.
s
o
f
t
w
a
r
e
.
In
I
n
this
t
h
i
s
case,
c
a
s
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
and
a
n
d
the
t
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files
F
i
l
e
s
should
s
h
o
u
l
d
be
b
e
verified
v
e
r
i
f
i
e
d
together.
t
o
g
e
t
h
e
r
.
For
F
o
r
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items
i
t
e
m
s
that
t
h
a
t
can
c
a
n
be
b
e
verified
v
e
r
i
f
i
e
d
separately
s
e
p
a
r
a
t
e
l
y
from
f
r
o
m
verification
v
e
r
i
f
i
c
a
t
i
o
n
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
objectives
o
b
j
e
c
t
i
v
e
s
identified
i
d
e
n
t
i
f
i
e
d
below
b
e
l
o
w
apply.
a
p
p
l
y
.
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
below
b
e
l
o
w
may
m
a
y
be
b
e
achieved
a
c
h
i
e
v
e
d
by
b
y
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
tests,
t
e
s
t
s
,
analyses,
a
n
a
l
y
s
e
s
,
and
a
n
d
reviews.
r
e
v
i
e
w
s
.
-
The
T
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
should
s
h
o
u
l
d
be
b
e
verified
v
e
r
i
f
i
e
d
to
t
o
comply
c
o
m
p
l
y
with
w
i
t
h
its
i
t
s
structure
s
t
r
u
c
t
u
r
e
as
a
s
defined
d
e
f
i
n
e
d
by
b
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
;
this
t
h
i
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
includes
i
n
c
l
u
d
e
s
ensuring
e
n
s
u
r
i
n
g
that
t
h
a
t
the
t
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
does
d
o
e
s
not
n
o
t
contain
c
o
n
t
a
i
n
any
a
n
y
elements
e
l
e
m
e
n
t
s
not
n
o
t
defined
d
e
f
i
n
e
d
by
b
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
.
Each
E
a
c
h
data
d
a
t
a
element
e
l
e
m
e
n
t
in
i
n
the
t
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
should
s
h
o
u
l
d
also
a
l
s
o
be
b
e
shown
s
h
o
w
n
to
t
o
have
h
a
v
e
the
t
h
e
correct
c
o
r
r
e
c
t
value,
v
a
l
u
e
,
to
t
o
be
b
e
consistent
c
o
n
s
i
s
t
e
n
t
with
w
i
t
h
other
o
t
h
e
r
data
d
a
t
a
elements,
e
l
e
m
e
n
t
s
,
and
a
n
d
to
t
o
comply
c
o
m
p
l
y
with
w
i
t
h
its
i
t
s
attributes
a
t
t
r
i
b
u
t
e
s
as
a
s
defined
d
e
f
i
n
e
d
by
b
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
.
Note:
N
o
t
e
:
For
F
o
r
certain
c
e
r
t
a
i
n
data
d
a
t
a
elements,
e
l
e
m
e
n
t
s
,
their
t
h
e
i
r
attributes
a
t
t
r
i
b
u
t
e
s
may
m
a
y
be
b
e
the
t
h
e
only
o
n
l
y
aspect
a
s
p
e
c
t
that
t
h
a
t
needs
n
e
e
d
s
to
t
o
be
b
e
verified.
v
e
r
i
f
i
e
d
.
In
I
n
other
o
t
h
e
r
cases,
c
a
s
e
s
,
the
t
h
e
value
v
a
l
u
e
of
o
f
the
t
h
e
data
d
a
t
a
element
e
l
e
m
e
n
t
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
verified.
v
e
r
i
f
i
e
d
.
-
All
A
l
l
elements
e
l
e
m
e
n
t
s
of
o
f
the
t
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
have
h
a
v
e
been
b
e
e
n
covered
c
o
v
e
r
e
d
during
d
u
r
i
n
g
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
If
I
f
changes
c
h
a
n
g
e
s
are
a
r
e
made
m
a
d
e
to
t
o
the
t
h
e
structure
s
t
r
u
c
t
u
r
e
or
o
r
attributes
a
t
t
r
i
b
u
t
e
s
of
o
f
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item,
i
t
e
m
,
then
t
h
e
n
the
t
h
e
need
n
e
e
d
for
f
o
r
modification
m
o
d
i
f
i
c
a
t
i
o
n
and
a
n
d
reverification
r
e
v
e
r
i
f
i
c
a
t
i
o
n
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
should
s
h
o
u
l
d
be
b
e
analyzed.
a
n
a
l
y
z
e
d
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
(see
(
s
e
e
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
(see
(
s
e
e
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
(see
(
s
e
e
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
.
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
:
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Assessing
A
s
s
e
s
s
i
n
g
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
.
-
Ensuring
E
n
s
u
r
i
n
g
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
.
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
objectives
o
b
j
e
c
t
i
v
e
s
are:
a
r
e
:
-
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
are
a
r
e
labeled
l
a
b
e
l
e
d
unambiguously
u
n
a
m
b
i
g
u
o
u
s
l
y
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
.
-
Baselines
B
a
s
e
l
i
n
e
s
are
a
r
e
defined
d
e
f
i
n
e
d
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
.
-
The
T
h
e
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
process
p
r
o
c
e
s
s
records
r
e
c
o
r
d
s
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
,
records
r
e
c
o
r
d
s
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
,
records
r
e
c
o
r
d
s
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
ensures
e
n
s
u
r
e
s
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
.
-
Change
C
h
a
n
g
e
control
c
o
n
t
r
o
l
provides
p
r
o
v
i
d
e
s
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
Change
C
h
a
n
g
e
review
r
e
v
i
e
w
ensures
e
n
s
u
r
e
s
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
.
-
Status
S
t
a
t
u
s
accounting
a
c
c
o
u
n
t
i
n
g
provides
p
r
o
v
i
d
e
s
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
.
-
Archival
A
r
c
h
i
v
a
l
and
a
n
d
retrieval
r
e
t
r
i
e
v
a
l
ensures
e
n
s
u
r
e
s
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
.
-
Software
S
o
f
t
w
a
r
e
load
l
o
a
d
control
c
o
n
t
r
o
l
ensures
e
n
s
u
r
e
s
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
are
a
r
e
loaded
l
o
a
d
e
d
into
i
n
t
o
the
t
h
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
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
ensures
e
n
s
u
r
e
s
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
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
(see
(
s
e
e
7.3).
7
.
3
)
.
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.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
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
approved
a
p
p
r
o
v
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
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
If
I
f
software
s
o
f
t
w
a
r
e
life
l
i
f
e
cycle
c
y
c
l
e
activities
a
c
t
i
v
i
t
i
e
s
will
w
i
l
l
be
b
e
performed
p
e
r
f
o
r
m
e
d
by
b
y
a
a
supplier,
s
u
p
p
l
i
e
r
,
then
t
h
e
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
activities
a
c
t
i
v
i
t
i
e
s
should
s
h
o
u
l
d
be
b
e
applied
a
p
p
l
i
e
d
to
t
o
the
t
h
e
supplier.
s
u
p
p
l
i
e
r
.
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
Activities
A
c
t
i
v
i
t
i
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
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
c
o
n
f
i
g
u
r
a
t
i
o
n
identified
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
analysis.
a
n
a
l
y
s
i
s
.
-
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
c
o
n
f
i
g
u
r
a
t
i
o
n
identified
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
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
that
t
h
a
t
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
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
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
.
55
5
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
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
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
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
(see
(
s
e
e
11.16).
1
1
.
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
,
whether
w
h
e
t
h
e
r
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
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
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
section
s
e
c
t
i
o
n
11.17.
1
1
.
1
7
.
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
.
-
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
.
7.2.4
7
.
2
.
4
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
include:
i
n
c
l
u
d
e
:
-
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
to
t
o
produce
p
r
o
d
u
c
e
derivative
d
e
r
i
v
a
t
i
v
e
baselines
b
a
s
e
l
i
n
e
s
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
.
7.2.5
7
.
2
.
5
Change
C
h
a
n
g
e
Review
R
e
v
i
e
w
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
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
of
o
f
the
t
h
e
problem
p
r
o
b
l
e
m
or
o
r
proposed
p
r
o
p
o
s
e
d
change
c
h
a
n
g
e
on
o
n
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Feedback
F
e
e
d
b
a
c
k
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
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
process,
p
r
o
c
e
s
s
,
and
a
n
d
any
a
n
y
responses
r
e
s
p
o
n
s
e
s
from
f
r
o
m
the
t
h
e
system
s
y
s
t
e
m
processes
p
r
o
c
e
s
s
e
s
should
s
h
o
u
l
d
be
b
e
assessed.
a
s
s
e
s
s
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
of
o
f
the
t
h
e
problem
p
r
o
b
l
e
m
or
o
r
proposed
p
r
o
p
o
s
e
d
change
c
h
a
n
g
e
on
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
identifying
i
d
e
n
t
i
f
y
i
n
g
changes
c
h
a
n
g
e
s
to
t
o
be
b
e
made
m
a
d
e
and
a
n
d
actions
a
c
t
i
o
n
s
to
t
o
be
b
e
taken.
t
a
k
e
n
.
-
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
.
-
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
Activities
A
c
t
i
v
i
t
i
e
s
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
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
.
57
5
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
R
e
l
e
a
s
e
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
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
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
,
an
a
n
archive
a
r
c
h
i
v
e
at
a
t
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
.
-
Preventing
P
r
e
v
e
n
t
i
n
g
loss
l
o
s
s
or
o
r
corruption
c
o
r
r
u
p
t
i
o
n
of
o
f
data
d
a
t
a
over
o
v
e
r
time.
t
i
m
e
.
Depending
D
e
p
e
n
d
i
n
g
on
o
n
the
t
h
e
storage
s
t
o
r
a
g
e
media
m
e
d
i
a
used,
u
s
e
d
,
this
t
h
i
s
may
m
a
y
include
i
n
c
l
u
d
e
periodically
p
e
r
i
o
d
i
c
a
l
l
y
exercising
e
x
e
r
c
i
s
i
n
g
the
t
h
e
media
m
e
d
i
a
or
o
r
refreshing
r
e
f
r
e
s
h
i
n
g
the
t
h
e
archived
a
r
c
h
i
v
e
d
data.
d
a
t
a
.
-
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any
a
n
y
-
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
should
s
h
o
u
l
d
be
b
e
released.
r
e
l
e
a
s
e
d
.
This
T
h
i
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
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
.
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
.
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
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
control
c
o
n
t
r
o
l
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
)
.
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
activities
a
c
t
i
v
i
t
i
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
the
t
h
e
minimum
m
i
n
i
m
u
m
activities
a
c
t
i
v
i
t
i
e
s
that
t
h
a
t
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
.
CC2
C
C
2
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
a
a
subset
s
u
b
s
e
t
of
o
f
the
t
h
e
CC1
C
C
1
activities.
a
c
t
i
v
i
t
i
e
s
.
The
T
h
e
Annex
A
n
n
e
x
A
A
tables
t
a
b
l
e
s
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
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
items.
i
t
e
m
s
.
Table
T
a
b
l
e
7-1
7
-
1
SCM
S
C
M
Process
P
r
o
c
e
s
s
Activities
A
c
t
i
v
i
t
i
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
SCM
S
C
M
Process
P
r
o
c
e
s
s
Activity
A
c
t
i
v
i
t
y
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
7.2.1
7
.
2
.
1
Baselines
B
a
s
e
l
i
n
e
s
7.2.2.a
7
.
2
.
2
.
a
7.2.2.b
7
.
2
.
2
.
b
7.2.2.c
7
.
2
.
2
.
c
7.2.2.d
7
.
2
.
2
.
d
7.2.2.e
7
.
2
.
2
.
e
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
7.2.2.f
7
.
2
.
2
.
f
7.2.2.g
7
.
2
.
2
.
g
Problem
P
r
o
b
l
e
m
Reporting
R
e
p
o
r
t
i
n
g
7.2.3
7
.
2
.
3
Change
C
h
a
n
g
e
Control
C
o
n
t
r
o
l
-
-
integrity
i
n
t
e
g
r
i
t
y
and
a
n
d
identification
i
d
e
n
t
i
f
i
c
a
t
i
o
n
7.2.4.a
7
.
2
.
4
.
a
7.2.4.b
7
.
2
.
4
.
b
Change
C
h
a
n
g
e
Control
C
o
n
t
r
o
l
-
-
tracking
t
r
a
c
k
i
n
g
7.2.4.c
7
.
2
.
4
.
c
7.2.4.d
7
.
2
.
4
.
d
7.2.4.e
7
.
2
.
4
.
e
Change
C
h
a
n
g
e
Review
R
e
v
i
e
w
7.2.5
7
.
2
.
5
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
7.2.6
7
.
2
.
6
Retrieval
R
e
t
r
i
e
v
a
l
7.2.7.a
7
.
2
.
7
.
a
Protection
P
r
o
t
e
c
t
i
o
n
against
a
g
a
i
n
s
t
Unauthorized
U
n
a
u
t
h
o
r
i
z
e
d
Changes
C
h
a
n
g
e
s
7.2.7.b.1
7
.
2
.
7
.
b
.
1
Media
M
e
d
i
a
Selection,
S
e
l
e
c
t
i
o
n
,
Refreshing,
R
e
f
r
e
s
h
i
n
g
,
Duplication
D
u
p
l
i
c
a
t
i
o
n
7.2.7.b.2
7
.
2
.
7
.
b
.
2
7.2.7.b.3
7
.
2
.
7
.
b
.
3
7.2.7.b.4
7
.
2
.
7
.
b
.
4
7.2.7.c
7
.
2
.
7
.
c
Release
R
e
l
e
a
s
e
7.2.7.d
7
.
2
.
7
.
d
Data
D
a
t
a
Retention
R
e
t
e
n
t
i
o
n
7.2.7.e
7
.
2
.
7
.
e
Reference
R
e
f
e
r
e
n
c
e
CC1
C
C
1
CC2
C
C
2
7.4
7
.
4
Software
S
o
f
t
w
a
r
e
Load
L
o
a
d
Control
C
o
n
t
r
o
l
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
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
pre-programmed
p
r
e
-
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
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
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
.
59
5
9
7.5
7
.
5
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
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
(see
(
s
e
e
11.15).
1
1
.
1
5
)
.
Activities
A
c
t
i
v
i
t
i
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
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
1
1
or
o
r
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
data
d
a
t
a
(see
(
s
e
e
7.3),
7
.
3
)
,
according
a
c
c
o
r
d
i
n
g
to
t
o
the
t
h
e
guidance
g
u
i
d
a
n
c
e
provided
p
r
o
v
i
d
e
d
by
b
y
section
s
e
c
t
i
o
n
12.2.3.
1
2
.
2
.
3
.
-
Unless
U
n
l
e
s
s
section
s
e
c
t
i
o
n
7.5b
7
.
5
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
,
for
f
o
r
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
,
and
a
n
d
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
61
6
1
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
(see
(
s
e
e
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
(see
(
s
e
e
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
(see
(
s
e
e
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
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
,
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
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
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
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
for
f
o
r
consistency.
c
o
n
s
i
s
t
e
n
c
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
,
including
i
n
c
l
u
d
i
n
g
those
t
h
o
s
e
of
o
f
suppliers,
s
u
p
p
l
i
e
r
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
.
Table
T
a
b
l
e
A-9
A
-
9
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
SQA
S
Q
A
process.
p
r
o
c
e
s
s
.
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
Activities
A
c
t
i
v
i
t
i
e
s
for
f
o
r
satisfying
s
a
t
i
s
f
y
i
n
g
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
include:
i
n
c
l
u
d
e
:
-
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
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
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
life
l
i
f
e
cycle
c
y
c
l
e
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
:
1.
1
.
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
section
s
e
c
t
i
o
n
4.2.
4
.
2
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
2.
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
activities
a
c
t
i
v
i
t
i
e
s
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
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
system
s
y
s
t
e
m
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
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
.
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
section
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
(see
(
s
e
e
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
.
-
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
supplier
s
u
p
p
l
i
e
r
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
outputs
o
u
t
p
u
t
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
.
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
purpose
p
u
r
p
o
s
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
assurance,
a
s
s
u
r
a
n
c
e
,
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
are
a
r
e
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Evidence
E
v
i
d
e
n
c
e
exists
e
x
i
s
t
s
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
have
h
a
v
e
been
b
e
e
n
produced
p
r
o
d
u
c
e
d
in
i
n
accordance
a
c
c
o
r
d
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
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
.
63
6
3
-
Evidence
E
v
i
d
e
n
c
e
exists
e
x
i
s
t
s
that
t
h
a
t
Problem
P
r
o
b
l
e
m
Reports
R
e
p
o
r
t
s
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
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
.
-
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-
r
e
-
evaluated
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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}
65
6
5
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
objectives
o
b
j
e
c
t
i
v
e
s
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
are
a
r
e
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
assist
a
s
s
i
s
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
.
-
Gain
G
a
i
n
agreement
a
g
r
e
e
m
e
n
t
on
o
n
the
t
h
e
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
through
t
h
r
o
u
g
h
approval
a
p
p
r
o
v
a
l
of
o
f
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
.
-
Provide
P
r
o
v
i
d
e
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
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
(see
(
s
e
e
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
(see
(
s
e
e
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
(see
(
s
e
e
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Submitting
S
u
b
m
i
t
t
i
n
g
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
.
-
Resolving
R
e
s
o
l
v
i
n
g
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
.
-
Obtaining
O
b
t
a
i
n
i
n
g
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
,
by
b
y
making
m
a
k
i
n
g
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
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
.
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
various
v
a
r
i
o
u
s
facilities.
f
a
c
i
l
i
t
i
e
s
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
the
t
h
e
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
,
the
t
h
e
applicant's
a
p
p
l
i
c
a
n
t
'
s
supplier's
s
u
p
p
l
i
e
r
'
s
facilities,
f
a
c
i
l
i
t
i
e
s
,
or
o
r
at
a
t
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
authority’s
a
u
t
h
o
r
i
t
y
’
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Resolving
R
e
s
o
l
v
i
n
g
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
.
-
Submitting
S
u
b
m
i
t
t
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
(see
(
s
e
e
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
(see
(
s
e
e
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
Submitting
S
u
b
m
i
t
t
i
n
g
or
o
r
making
m
a
k
i
n
g
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
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
.
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
of
o
f
the
t
h
e
product
p
r
o
d
u
c
t
to
t
o
be
b
e
certified
c
e
r
t
i
f
i
e
d
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any.
a
n
y
.
-
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
10.0
1
0
.
0
OVERVIEW
O
V
E
R
V
I
E
W
OF
O
F
CERTIFICATION
C
E
R
T
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
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
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
airborne
a
i
r
b
o
r
n
e
community
c
o
m
m
u
n
i
t
y
and
a
n
d
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
use
u
s
e
several
s
e
v
e
r
a
l
terms
t
e
r
m
s
related
r
e
l
a
t
e
d
to
t
o
aircraft
a
i
r
c
r
a
f
t
approval
a
p
p
r
o
v
a
l
for
f
o
r
flight
f
l
i
g
h
t
with
w
i
t
h
its
i
t
s
associated
a
s
s
o
c
i
a
t
e
d
equipment.
e
q
u
i
p
m
e
n
t
.
The
T
h
e
terms
t
e
r
m
s
used
u
s
e
d
are
a
r
e
“certification”,
“
c
e
r
t
i
f
i
c
a
t
i
o
n
”
,
“approval”,
“
a
p
p
r
o
v
a
l
”
,
and,
a
n
d
,
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
tools,
t
o
o
l
s
,
“qualification”.
“
q
u
a
l
i
f
i
c
a
t
i
o
n
”
.
“Certification”
“
C
e
r
t
i
f
i
c
a
t
i
o
n
”
applies
a
p
p
l
i
e
s
to
t
o
aircraft,
a
i
r
c
r
a
f
t
,
engines,
e
n
g
i
n
e
s
,
or
o
r
propellers;
p
r
o
p
e
l
l
e
r
s
;
and,
a
n
d
,
in
i
n
respect
r
e
s
p
e
c
t
of
o
f
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
,
auxiliary
a
u
x
i
l
i
a
r
y
power
p
o
w
e
r
units.
u
n
i
t
s
.
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
consider
c
o
n
s
i
d
e
r
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
certified
c
e
r
t
i
f
i
e
d
product;
p
r
o
d
u
c
t
;
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
authorities
a
u
t
h
o
r
i
t
i
e
s
do
d
o
not
n
o
t
certify
c
e
r
t
i
f
y
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
.
Systems
S
y
s
t
e
m
s
and
a
n
d
equipment,
e
q
u
i
p
m
e
n
t
,
including
i
n
c
l
u
d
i
n
g
embedded
e
m
b
e
d
d
e
d
software,
s
o
f
t
w
a
r
e
,
should
s
h
o
u
l
d
be
b
e
“approved”
“
a
p
p
r
o
v
e
d
”
in
i
n
order
o
r
d
e
r
to
t
o
be
b
e
accepted
a
c
c
e
p
t
e
d
as
a
s
a
a
part
p
a
r
t
of
o
f
a
a
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
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
authorities
a
u
t
h
o
r
i
t
i
e
s
is
i
s
given
g
i
v
e
n
dependent
d
e
p
e
n
d
e
n
t
upon
u
p
o
n
a
a
successful
s
u
c
c
e
s
s
f
u
l
demonstration
d
e
m
o
n
s
t
r
a
t
i
o
n
or
o
r
by
b
y
review
r
e
v
i
e
w
of
o
f
the
t
h
e
products
p
r
o
d
u
c
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
.
Any
A
n
y
such
s
u
c
h
approval
a
p
p
r
o
v
a
l
currently
c
u
r
r
e
n
t
l
y
has
h
a
s
significance
s
i
g
n
i
f
i
c
a
n
c
e
only
o
n
l
y
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
certification.
c
e
r
t
i
f
i
c
a
t
i
o
n
.
Tool
T
o
o
l
“qualification”
“
q
u
a
l
i
f
i
c
a
t
i
o
n
”
is
i
s
discussed
d
i
s
c
u
s
s
e
d
in
i
n
section
s
e
c
t
i
o
n
12.2.
1
2
.
2
.
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
product
p
r
o
d
u
c
t
to
t
o
be
b
e
certified
c
e
r
t
i
f
i
e
d
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
to
t
o
be
b
e
applied
a
p
p
l
i
e
d
beyond
b
e
y
o
n
d
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
.
When
W
h
e
n
certified
c
e
r
t
i
f
i
e
d
products
p
r
o
d
u
c
t
s
are
a
r
e
being
b
e
i
n
g
modified,
m
o
d
i
f
i
e
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
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
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
.
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
product
p
r
o
d
u
c
t
to
t
o
be
b
e
certified,
c
e
r
t
i
f
i
e
d
,
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
section
s
e
c
t
i
o
n
9.2.
9
.
2
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
69
6
9
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
.
-
Characteristics:
C
h
a
r
a
c
t
e
r
i
s
t
i
c
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
should
s
h
o
u
l
d
be:
b
e
:
1.
1
.
2.
2
.
3.
3
.
4.
4
.
5.
5
.
6.
6
.
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
and
a
n
d
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
,
consistently,
c
o
n
s
i
s
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
.
-
Form:
F
o
r
m
:
The
T
h
e
form
f
o
r
m
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
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
life
l
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
be
b
e
held
h
e
l
d
in
i
n
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
,
held
h
e
l
d
electronically
e
l
e
c
t
r
o
n
i
c
a
l
l
y
or
o
r
in
i
n
printed
p
r
i
n
t
e
d
form).
f
o
r
m
)
.
Note
N
o
t
e
2:
2
:
The
T
h
e
applicant
a
p
p
l
i
c
a
n
t
may
m
a
y
package
p
a
c
k
a
g
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
items
i
t
e
m
s
in
i
n
any
a
n
y
manner
m
a
n
n
e
r
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
finds
f
i
n
d
s
convenient
c
o
n
v
e
n
i
e
n
t
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
as
a
s
individual
i
n
d
i
v
i
d
u
a
l
data
d
a
t
a
items
i
t
e
m
s
or
o
r
as
a
s
a
a
combined
c
o
m
b
i
n
e
d
data
d
a
t
a
item).
i
t
e
m
)
.
Note
N
o
t
e
3:
3
:
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
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
.
Note
N
o
t
e
4:
4
:
The
T
h
e
term
t
e
r
m
“data”
“
d
a
t
a
”
refers
r
e
f
e
r
s
to
t
o
evidence
e
v
i
d
e
n
c
e
and
a
n
d
other
o
t
h
e
r
information
i
n
f
o
r
m
a
t
i
o
n
and
a
n
d
does
d
o
e
s
not
n
o
t
imply
i
m
p
l
y
the
t
h
e
format
f
o
r
m
a
t
such
s
u
c
h
data
d
a
t
a
should
s
h
o
u
l
d
take.
t
a
k
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
:
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
:
CC1
C
C
1
and
a
n
d
CC2
C
C
2
(see
(
s
e
e
7.3).
7
.
3
)
.
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
the
t
h
e
tables
t
a
b
l
e
s
of
o
f
Annex
A
n
n
e
x
A.
A
.
If
I
f
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
additional
a
d
d
i
t
i
o
n
a
l
data
d
a
t
a
items
i
t
e
m
s
than
t
h
a
n
those
t
h
o
s
e
described
d
e
s
c
r
i
b
e
d
herein
h
e
r
e
i
n
are
a
r
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
,
they
t
h
e
y
should
s
h
o
u
l
d
be,
b
e
,
as
a
s
a
a
minimum,
m
i
n
i
m
u
m
,
under
u
n
d
e
r
CC2
C
C
2
controls.
c
o
n
t
r
o
l
s
.
-
Content:
C
o
n
t
e
n
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
descriptions
d
e
s
c
r
i
p
t
i
o
n
s
provided
p
r
o
v
i
d
e
d
in
i
n
the
t
h
e
following
f
o
l
l
o
w
i
n
g
sections
s
e
c
t
i
o
n
s
identify
i
d
e
n
t
i
f
y
the
t
h
e
data
d
a
t
a
that
t
h
a
t
is
i
s
generally
g
e
n
e
r
a
l
l
y
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
.
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
that
t
h
a
t
may
m
a
y
be
b
e
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
.
The
T
h
e
descriptions
d
e
s
c
r
i
p
t
i
o
n
s
of
o
f
the
t
h
e
content
c
o
n
t
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
items
i
t
e
m
s
provided
p
r
o
v
i
d
e
d
herein
h
e
r
e
i
n
are
a
r
e
not
n
o
t
all
a
l
l
encompassing
e
n
c
o
m
p
a
s
s
i
n
g
and
a
n
d
should
s
h
o
u
l
d
be
b
e
read
r
e
a
d
in
i
n
conjunction
c
o
n
j
u
n
c
t
i
o
n
with
w
i
t
h
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
and
a
n
d
adapted
a
d
a
p
t
e
d
to
t
o
the
t
h
e
needs
n
e
e
d
s
of
o
f
the
t
h
e
applicant.
a
p
p
l
i
c
a
n
t
.
-
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
(PSAC)
(
P
S
A
C
)
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
.
b.
b
.
c.
c
.
d.
d
.
e.
e
.
f.
f
.
-
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
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
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
,
fault
f
a
u
l
t
tolerance,
t
o
l
e
r
a
n
c
e
,
mitigation
m
i
t
i
g
a
t
i
o
n
of
o
f
single
s
i
n
g
l
e
event
e
v
e
n
t
upset,
u
p
s
e
t
,
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
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
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
the
t
h
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
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
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
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
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-
u
s
e
r
-
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
71
7
1
modifiable
m
o
d
i
f
i
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
deactivated
d
e
a
c
t
i
v
a
t
e
d
code,
c
o
d
e
,
COTS
C
O
T
S
software,
s
o
f
t
w
a
r
e
,
field-loadable
f
i
e
l
d
-
l
o
a
d
a
b
l
e
software,
s
o
f
t
w
a
r
e
,
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items,
i
t
e
m
s
,
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
.
-
Supplier
S
u
p
p
l
i
e
r
oversight:
o
v
e
r
s
i
g
h
t
:
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
of
o
f
ensuring
e
n
s
u
r
i
n
g
that
t
h
a
t
supplier
s
u
p
p
l
i
e
r
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
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
.
-
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
(SDP)
(
S
D
P
)
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
development
d
e
v
e
l
o
p
m
e
n
t
procedures
p
r
o
c
e
d
u
r
e
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
to
t
o
satisfy
s
a
t
i
s
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
process
p
r
o
c
e
s
s
objectives.
o
b
j
e
c
t
i
v
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
.
b.
b
.
-
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
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
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
:
-
The
T
h
e
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
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
coding
c
o
d
i
n
g
method(s),
m
e
t
h
o
d
(
s
)
,
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
tool(s)
t
o
o
l
(
s
)
to
t
o
be
b
e
used,
u
s
e
d
,
and
a
n
d
when
w
h
e
n
applicable,
a
p
p
l
i
c
a
b
l
e
,
options
o
p
t
i
o
n
s
and
a
n
d
constraints
c
o
n
s
t
r
a
i
n
t
s
of
o
f
autocode
a
u
t
o
c
o
d
e
generators.
g
e
n
e
r
a
t
o
r
s
.
-
The
T
h
e
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
.
-
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
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
(SVP)
(
S
V
P
)
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
be
b
e
used
u
s
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
.
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
.
b.
b
.
-
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
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
the
t
h
e
method
m
e
t
h
o
d
for
f
o
r
selecting
s
e
l
e
c
t
i
n
g
test
t
e
s
t
cases,
c
a
s
e
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
.
-
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
how
h
o
w
to
t
o
apply
a
p
p
l
y
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
.
Section
S
e
c
t
i
o
n
4.4.3b
4
.
4
.
3
b
provides
p
r
o
v
i
d
e
s
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
.
e.
e
.
f.
f
.
g.
g
.
h.
h
.
i.
i
.
-
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
.
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
(see
(
s
e
e
4.4.2).
4
.
4
.
2
)
.
Reverification
R
e
v
e
r
i
f
i
c
a
t
i
o
n
method:
m
e
t
h
o
d
:
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
,
analyzing,
a
n
a
l
y
z
i
n
g
,
and
a
n
d
verifying
v
e
r
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
.
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
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
.
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
,
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
(see
(
s
e
e
12.3.2).
1
2
.
3
.
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
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
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
:
1.
1
.
2.
2
.
-
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
the
t
h
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
73
7
3
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
.
5.
5
.
6.
6
.
7.
7
.
8.
8
.
9.
9
.
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
sections
s
e
c
t
i
o
n
s
11.4.b.1
1
1
.
4
.
b
.
1
through
t
h
r
o
u
g
h
11.4.b.7.
1
1
.
4
.
b
.
7
.
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
.
10.
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
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
CC1
C
C
1
and
a
n
d
CC2
C
C
2
data.
d
a
t
a
.
c.
c
.
d.
d
.
-
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
suppliers.
s
u
p
p
l
i
e
r
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
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
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
.
b.
b
.
-
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
SQA
S
Q
A
approval
a
p
p
r
o
v
a
l
of
o
f
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
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
.
e.
e
.
f.
f
.
-
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
oversight:
o
v
e
r
s
i
g
h
t
:
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
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
plans
p
l
a
n
s
and
a
n
d
standards.
s
t
a
n
d
a
r
d
s
.
-
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
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
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
tools
t
o
o
l
s
used
u
s
e
d
for
f
o
r
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
.
-
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
processes.
p
r
o
c
e
s
s
e
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
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
75
7
5
Software
S
o
f
t
w
a
r
e
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
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-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
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
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
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
.
-
Source
S
o
u
r
c
e
Code
C
o
d
e
-
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
.
-
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-rigid
t
i
m
e
-
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
.
-
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
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-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
.
-
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
)
.
The
T
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
used
u
s
e
d
with
w
i
t
h
the
t
h
e
compiling,
c
o
m
p
i
l
i
n
g
,
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
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
system
s
y
s
t
e
m
or
o
r
equipment.
e
q
u
i
p
m
e
n
t
.
For
F
o
r
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
,
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
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
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
:
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
,
in
i
n
addition
a
d
d
i
t
i
o
n
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
77
7
7
-
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
procedures:
p
r
o
c
e
d
u
r
e
s
:
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
.
Any
A
n
y
discrepancies
d
i
s
c
r
e
p
a
n
c
i
e
s
found
f
o
u
n
d
should
s
h
o
u
l
d
be
b
e
recorded
r
e
c
o
r
d
e
d
and
a
n
d
tracked
t
r
a
c
k
e
d
via
v
i
a
problem
p
r
o
b
l
e
m
reporting.
r
e
p
o
r
t
i
n
g
.
Additionally,
A
d
d
i
t
i
o
n
a
l
l
y
,
evidence
e
v
i
d
e
n
c
e
provided
p
r
o
v
i
d
e
d
in
i
n
support
s
u
p
p
o
r
t
of
o
f
the
t
h
e
system
s
y
s
t
e
m
processes’
p
r
o
c
e
s
s
e
s
’
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
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
processes
p
r
o
c
e
s
s
e
s
(see
(
s
e
e
2.2.1.f
2
.
2
.
1
.
f
and
a
n
d
2.2.1.g)
2
.
2
.
1
.
g
)
should
s
h
o
u
l
d
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
to
t
o
be
b
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
.
-
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
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
tools
t
o
o
l
s
to
t
o
be
b
e
used
u
s
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
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
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
,
loaders,
l
o
a
d
e
r
s
,
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
,
and
a
n
d
any
a
n
y
autocode
a
u
t
o
c
o
d
e
generator
g
e
n
e
r
a
t
o
r
with
w
i
t
h
its
i
t
s
associated
a
s
s
o
c
i
a
t
e
d
options.
o
p
t
i
o
n
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
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
.
-
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
.
Specific
S
p
e
c
i
f
i
c
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identifiers
i
d
e
n
t
i
f
i
e
r
s
and
a
n
d
version
v
e
r
s
i
o
n
identifiers
i
d
e
n
t
i
f
i
e
r
s
should
s
h
o
u
l
d
be
b
e
provided.
p
r
o
v
i
d
e
d
.
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
78
7
8
The
T
h
e
SCI
S
C
I
should
s
h
o
u
l
d
identify:
i
d
e
n
t
i
f
y
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
-
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any.
a
n
y
.
-
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
and
a
n
d
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
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
(see
(
s
e
e
11.15),
1
1
.
1
5
)
,
if
i
f
it
i
t
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
.
-
Procedures,
P
r
o
c
e
d
u
r
e
s
,
methods,
m
e
t
h
o
d
s
,
and
a
n
d
tools
t
o
o
l
s
for
f
o
r
making
m
a
k
i
n
g
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
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
,
if
i
f
any.
a
n
y
.
-
Procedures
P
r
o
c
e
d
u
r
e
s
and
a
n
d
methods
m
e
t
h
o
d
s
for
f
o
r
loading
l
o
a
d
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
hardware.
h
a
r
d
w
a
r
e
.
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
.
The
T
h
e
problem
p
r
o
b
l
e
m
description
d
e
s
c
r
i
p
t
i
o
n
should
s
h
o
u
l
d
contain
c
o
n
t
a
i
n
sufficient
s
u
f
f
i
c
i
e
n
t
detail
d
e
t
a
i
l
to
t
o
facilitate
f
a
c
i
l
i
t
a
t
e
the
t
h
e
assessment
a
s
s
e
s
s
m
e
n
t
of
o
f
the
t
h
e
potential
p
o
t
e
n
t
i
a
l
safety
s
a
f
e
t
y
or
o
r
functional
f
u
n
c
t
i
o
n
a
l
effects
e
f
f
e
c
t
s
of
o
f
the
t
h
e
problem.
p
r
o
b
l
e
m
.
-
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
.
-
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
that
t
h
a
t
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
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
79
7
9
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
.
b.
b
.
c.
c
.
d.
d
.
e.
e
.
f.
f
.
g.
g
.
-
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
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
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
proposals
p
r
o
p
o
s
a
l
s
made
m
a
d
e
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
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
,
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
the
t
h
e
data
d
a
t
a
was
w
a
s
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
explicitly
e
x
p
l
i
c
i
t
l
y
references,
r
e
f
e
r
e
n
c
e
s
,
by
b
y
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identifiers
i
d
e
n
t
i
f
i
e
r
s
and
a
n
d
version,
v
e
r
s
i
o
n
,
the
t
h
e
applicable
a
p
p
l
i
c
a
b
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
Index
I
n
d
e
x
and
a
n
d
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
.
Detailed
D
e
t
a
i
l
e
d
information
i
n
f
o
r
m
a
t
i
o
n
regarding
r
e
g
a
r
d
i
n
g
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
identifiers
i
d
e
n
t
i
f
i
e
r
s
and
a
n
d
specific
s
p
e
c
i
f
i
c
versions
v
e
r
s
i
o
n
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
is
i
s
provided
p
r
o
v
i
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
.
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
any
a
n
y
specific
s
p
e
c
i
f
i
c
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
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
.
It
I
t
explains
e
x
p
l
a
i
n
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
proposals
p
r
o
p
o
s
a
l
s
contained
c
o
n
t
a
i
n
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
regarding
r
e
g
a
r
d
i
n
g
such
s
u
c
h
considerations.
c
o
n
s
i
d
e
r
a
t
i
o
n
s
.
Reference
R
e
f
e
r
e
n
c
e
should
s
h
o
u
l
d
be
b
e
made
m
a
d
e
to
t
o
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
matters,
m
a
t
t
e
r
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
.
Supplier
S
u
p
p
l
i
e
r
oversight:
o
v
e
r
s
i
g
h
t
:
This
T
h
i
s
section
s
e
c
t
i
o
n
describes
d
e
s
c
r
i
b
e
s
how
h
o
w
supplier
s
u
p
p
l
i
e
r
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
outputs
o
u
t
p
u
t
s
comply
c
o
m
p
l
y
with
w
i
t
h
plans
p
l
a
n
s
and
a
n
d
standards.
s
t
a
n
d
a
r
d
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
margins
m
a
r
g
i
n
s
including
i
n
c
l
u
d
i
n
g
worst-case
w
o
r
s
t
-
c
a
s
e
execution
e
x
e
c
u
t
i
o
n
time,
t
i
m
e
,
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
used
u
s
e
d
for
f
o
r
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
.
j.
j
.
k.
k
.
-
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
any
a
n
y
changes
c
h
a
n
g
e
s
from
f
r
o
m
and
a
n
d
improvements
i
m
p
r
o
v
e
m
e
n
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
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
.
The
T
h
e
Problem
P
r
o
b
l
e
m
Report
R
e
p
o
r
t
summary
s
u
m
m
a
r
y
includes
i
n
c
l
u
d
e
s
a
a
description
d
e
s
c
r
i
p
t
i
o
n
of
o
f
each
e
a
c
h
problem
p
r
o
b
l
e
m
and
a
n
d
any
a
n
y
associated
a
s
s
o
c
i
a
t
e
d
errors,
e
r
r
o
r
s
,
functional
f
u
n
c
t
i
o
n
a
l
limitations,
l
i
m
i
t
a
t
i
o
n
s
,
operational
o
p
e
r
a
t
i
o
n
a
l
restrictions,
r
e
s
t
r
i
c
t
i
o
n
s
,
potential
p
o
t
e
n
t
i
a
l
adverse
a
d
v
e
r
s
e
effect(s)
e
f
f
e
c
t
(
s
)
on
o
n
safety
s
a
f
e
t
y
together
t
o
g
e
t
h
e
r
with
w
i
t
h
a
a
justification
j
u
s
t
i
f
i
c
a
t
i
o
n
for
f
o
r
allowing
a
l
l
o
w
i
n
g
the
t
h
e
Problem
P
r
o
b
l
e
m
Report
R
e
p
o
r
t
to
t
o
remain
r
e
m
a
i
n
open,
o
p
e
n
,
and
a
n
d
details
d
e
t
a
i
l
s
of
o
f
any
a
n
y
mitigating
m
i
t
i
g
a
t
i
n
g
action
a
c
t
i
o
n
that
t
h
a
t
has
h
a
s
been
b
e
e
n
or
o
r
needs
n
e
e
d
s
to
t
o
be
b
e
carried
c
a
r
r
i
e
d
out.
o
u
t
.
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
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
compliance
c
o
m
p
l
i
a
n
c
e
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
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
made
m
a
d
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
and
a
n
d
any
a
n
y
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
not
n
o
t
covered
c
o
v
e
r
e
d
elsewhere
e
l
s
e
w
h
e
r
e
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
.
11.21
1
1
.
2
1
Trace
T
r
a
c
e
Data
D
a
t
a
Trace
T
r
a
c
e
Data
D
a
t
a
establishes
e
s
t
a
b
l
i
s
h
e
s
the
t
h
e
associations
a
s
s
o
c
i
a
t
i
o
n
s
between
b
e
t
w
e
e
n
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
items
i
t
e
m
s
contents.
c
o
n
t
e
n
t
s
.
Trace
T
r
a
c
e
Data
D
a
t
a
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
that
t
h
a
t
demonstrates
d
e
m
o
n
s
t
r
a
t
e
s
bi-directional
b
i
-
d
i
r
e
c
t
i
o
n
a
l
associations
a
s
s
o
c
i
a
t
i
o
n
s
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
allocated
a
l
l
o
c
a
t
e
d
to
t
o
software
s
o
f
t
w
a
r
e
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
.
-
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
.
-
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
Source
S
o
u
r
c
e
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
and
a
n
d
test
t
e
s
t
cases.
c
a
s
e
s
.
-
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
.
-
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
.
11.22
1
1
.
2
2
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
The
T
h
e
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
consists
c
o
n
s
i
s
t
s
of
o
f
a
a
form
f
o
r
m
of
o
f
data
d
a
t
a
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
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
.
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
should
s
h
o
u
l
d
be
b
e
produced
p
r
o
d
u
c
e
d
for
f
o
r
each
e
a
c
h
instantiation
i
n
s
t
a
n
t
i
a
t
i
o
n
of
o
f
a
a
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item.
I
t
e
m
.
If
I
f
packaged
p
a
c
k
a
g
e
d
separately,
s
e
p
a
r
a
t
e
l
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
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
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
associated
a
s
s
o
c
i
a
t
e
d
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
as
a
s
described
d
e
s
c
r
i
b
e
d
in
i
n
those
t
h
o
s
e
sections.
s
e
c
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
guidance
g
u
i
d
a
n
c
e
on
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
where
w
h
e
r
e
objectives
o
b
j
e
c
t
i
v
e
s
and/or
a
n
d
/
o
r
activities
a
c
t
i
v
i
t
i
e
s
may
m
a
y
replace,
r
e
p
l
a
c
e
,
modify,
m
o
d
i
f
y
,
or
o
r
add
a
d
d
to
t
o
some
s
o
m
e
or
o
r
all
a
l
l
of
o
f
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
and/or
a
n
d
/
o
r
activities
a
c
t
i
v
i
t
i
e
s
defined
d
e
f
i
n
e
d
in
i
n
the
t
h
e
rest
r
e
s
t
of
o
f
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
The
T
h
e
use
u
s
e
of
o
f
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
and
a
n
d
the
t
h
e
proposed
p
r
o
p
o
s
e
d
impact
i
m
p
a
c
t
on
o
n
the
t
h
e
guidance
g
u
i
d
a
n
c
e
provided
p
r
o
v
i
d
e
d
in
i
n
the
t
h
e
other
o
t
h
e
r
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
should
s
h
o
u
l
d
be
b
e
agreed
a
g
r
e
e
d
on
o
n
a
a
case-by-case
c
a
s
e
-
b
y
-
c
a
s
e
basis
b
a
s
i
s
with
w
i
t
h
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
.
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
guidance
g
u
i
d
a
n
c
e
of
o
f
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
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
.
Unresolved
U
n
r
e
s
o
l
v
e
d
Problem
P
r
o
b
l
e
m
Reports
R
e
p
o
r
t
s
associated
a
s
s
o
c
i
a
t
e
d
with
w
i
t
h
the
t
h
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
should
s
h
o
u
l
d
be
b
e
evaluated
e
v
a
l
u
a
t
e
d
for
f
o
r
impact.
i
m
p
a
c
t
.
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
.
Activities
A
c
t
i
v
i
t
i
e
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
guidance
g
u
i
d
a
n
c
e
of
o
f
section
s
e
c
t
i
o
n
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
the
t
h
e
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
,
traceability
t
r
a
c
e
a
b
i
l
i
t
y
analysis,
a
n
a
l
y
s
i
s
,
or
o
r
a
a
combination
c
o
m
b
i
n
a
t
i
o
n
of
o
f
these
t
h
e
s
e
analyses.
a
n
a
l
y
s
e
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
in
i
n
accordance
a
c
c
o
r
d
a
n
c
e
with
w
i
t
h
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
that
t
h
a
t
has
h
a
s
been
b
e
e
n
previously
p
r
e
v
i
o
u
s
l
y
"approved"
"
a
p
p
r
o
v
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
-
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
guidance
g
u
i
d
a
n
c
e
of
o
f
section
s
e
c
t
i
o
n
12.1.1
1
2
.
1
.
1
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
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
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
guidance
g
u
i
d
a
n
c
e
of
o
f
section
s
e
c
t
i
o
n
12.1.4
1
2
.
1
.
4
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
Development
D
e
v
e
l
o
p
m
e
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
.
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
that
t
h
a
t
address
a
d
d
r
e
s
s
modifications.
m
o
d
i
f
i
c
a
t
i
o
n
s
.
Changes
C
h
a
n
g
e
s
to
t
o
an
a
n
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
should
s
h
o
u
l
d
be
b
e
identified,
i
d
e
n
t
i
f
i
e
d
,
analyzed,
a
n
a
l
y
z
e
d
,
and
a
n
d
reverified.
r
e
v
e
r
i
f
i
e
d
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
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
tools,
t
o
o
l
s
,
the
t
h
e
guidance
g
u
i
d
a
n
c
e
of
o
f
section
s
e
c
t
i
o
n
12.2
1
2
.
2
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-oriented
o
b
j
e
c
t
-
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
.
-
Using
U
s
i
n
g
a
a
different
d
i
f
f
e
r
e
n
t
autocode
a
u
t
o
c
o
d
e
generator
g
e
n
e
r
a
t
o
r
or
o
r
a
a
different
d
i
f
f
e
r
e
n
t
set
s
e
t
of
o
f
autocode
a
u
t
o
c
o
d
e
generator
g
e
n
e
r
a
t
o
r
options
o
p
t
i
o
n
s
may
m
a
y
change
c
h
a
n
g
e
the
t
h
e
Source
S
o
u
r
c
e
Code
C
o
d
e
or
o
r
object
o
b
j
e
c
t
code
c
o
d
e
generated.
g
e
n
e
r
a
t
e
d
.
The
T
h
e
impact
i
m
p
a
c
t
of
o
f
any
a
n
y
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
.
-
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
a
a
change
c
h
a
n
g
e
impact
i
m
p
a
c
t
analysis
a
n
a
l
y
s
i
s
is
i
s
performed
p
e
r
f
o
r
m
e
d
to
t
o
determine:
d
e
t
e
r
m
i
n
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
are
a
r
e
new
n
e
w
or
o
r
will
w
i
l
l
need
n
e
e
d
to
t
o
be
b
e
modified
m
o
d
i
f
i
e
d
as
a
s
a
a
result
r
e
s
u
l
t
of
o
f
changing
c
h
a
n
g
i
n
g
the
t
h
e
processor,
p
r
o
c
e
s
s
o
r
,
including
i
n
c
l
u
d
i
n
g
any
a
n
y
modification
m
o
d
i
f
i
c
a
t
i
o
n
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
that
t
h
a
t
may
m
a
y
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
.
83
8
3
-
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
that
t
h
a
t
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
.
It
I
t
is
i
s
expected
e
x
p
e
c
t
e
d
that
t
h
a
t
there
t
h
e
r
e
will
w
i
l
l
always
a
l
w
a
y
s
be
b
e
a
a
minimal
m
i
n
i
m
a
l
set
s
e
t
of
o
f
tests
t
e
s
t
s
to
t
o
be
b
e
run.
r
u
n
.
-
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
that
t
h
a
t
may
m
a
y
be
b
e
necessary.
n
e
c
e
s
s
a
r
y
.
-
If
I
f
a
a
hardware
h
a
r
d
w
a
r
e
item,
i
t
e
m
,
other
o
t
h
e
r
than
t
h
a
n
the
t
h
e
processor,
p
r
o
c
e
s
s
o
r
,
is
i
s
changed
c
h
a
n
g
e
d
and
a
n
d
the
t
h
e
design
d
e
s
i
g
n
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
isolates
i
s
o
l
a
t
e
s
the
t
h
e
interfacing
i
n
t
e
r
f
a
c
i
n
g
modules
m
o
d
u
l
e
s
from
f
r
o
m
other
o
t
h
e
r
modules
m
o
d
u
l
e
s
then
t
h
e
n
a
a
change
c
h
a
n
g
e
impact
i
m
p
a
c
t
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
be
b
e
performed
p
e
r
f
o
r
m
e
d
to:
t
o
:
-
Determine
D
e
t
e
r
m
i
n
e
the
t
h
e
software
s
o
f
t
w
a
r
e
modules
m
o
d
u
l
e
s
or
o
r
interfaces
i
n
t
e
r
f
a
c
e
s
that
t
h
a
t
are
a
r
e
new
n
e
w
or
o
r
will
w
i
l
l
be
b
e
modified
m
o
d
i
f
i
e
d
to
t
o
accommodate
a
c
c
o
m
m
o
d
a
t
e
the
t
h
e
changed
c
h
a
n
g
e
d
hardware
h
a
r
d
w
a
r
e
component.
c
o
m
p
o
n
e
n
t
.
-
Determine
D
e
t
e
r
m
i
n
e
the
t
h
e
extent
e
x
t
e
n
t
of
o
f
reverification
r
e
v
e
r
i
f
i
c
a
t
i
o
n
required.
r
e
q
u
i
r
e
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
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
.
A
A
change
c
h
a
n
g
e
impact
i
m
p
a
c
t
analysis
a
n
a
l
y
s
i
s
may
m
a
y
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
extent
e
x
t
e
n
t
of
o
f
reverification
r
e
v
e
r
i
f
i
c
a
t
i
o
n
required.
r
e
q
u
i
r
e
d
.
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
Guidance
G
u
i
d
a
n
c
e
follows
f
o
l
l
o
w
s
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
requirements
r
e
q
u
i
r
e
m
e
n
t
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
.
This
T
h
i
s
guidance
g
u
i
d
a
n
c
e
is
i
s
intended
i
n
t
e
n
d
e
d
to
t
o
aid
a
i
d
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
when
w
h
e
n
applied
a
p
p
l
i
e
d
to:
t
o
:
COTS
C
O
T
S
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
guidance.
g
u
i
d
a
n
c
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
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
.
Activities
A
c
t
i
v
i
t
i
e
s
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
include:
i
n
c
l
u
d
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
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
that
t
h
a
t
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
to
t
o
the
t
h
e
necessary
n
e
c
e
s
s
a
r
y
level
l
e
v
e
l
of
o
f
rigor
r
i
g
o
r
and
a
n
d
independence.
i
n
d
e
p
e
n
d
e
n
c
e
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
-
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
.
-
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
,
section
s
e
c
t
i
o
n
12.3.4
1
2
.
3
.
4
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
accomplishing
a
c
c
o
m
p
l
i
s
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
activities
a
c
t
i
v
i
t
i
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
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
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
section
s
e
c
t
i
o
n
7:
7
:
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
activities
a
c
t
i
v
i
t
i
e
s
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
activities
a
c
t
i
v
i
t
i
e
s
of
o
f
section
s
e
c
t
i
o
n
8:
8
:
-
Providing
P
r
o
v
i
d
i
n
g
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
.
-
Providing
P
r
o
v
i
d
i
n
g
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
12.2.1
1
2
.
2
.
1
Determining
D
e
t
e
r
m
i
n
i
n
g
if
i
f
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
is
i
s
Needed
N
e
e
d
e
d
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
purpose
p
u
r
p
o
s
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
.
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
to
t
o
a
a
single
s
i
n
g
l
e
tool,
t
o
o
l
,
a
a
collection
c
o
l
l
e
c
t
i
o
n
of
o
f
tools,
t
o
o
l
s
,
or
o
r
one
o
n
e
or
o
r
more
m
o
r
e
functions
f
u
n
c
t
i
o
n
s
within
w
i
t
h
i
n
a
a
tool.
t
o
o
l
.
For
F
o
r
a
a
tool
t
o
o
l
with
w
i
t
h
multiple
m
u
l
t
i
p
l
e
functions,
f
u
n
c
t
i
o
n
s
,
if
i
f
protection
p
r
o
t
e
c
t
i
o
n
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
processes,
p
r
o
c
e
s
s
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
.
Protection
P
r
o
t
e
c
t
i
o
n
is
i
s
the
t
h
e
use
u
s
e
of
o
f
a
a
mechanism
m
e
c
h
a
n
i
s
m
to
t
o
ensure
e
n
s
u
r
e
that
t
h
a
t
a
a
tool
t
o
o
l
function
f
u
n
c
t
i
o
n
cannot
c
a
n
n
o
t
adversely
a
d
v
e
r
s
e
l
y
impact
i
m
p
a
c
t
another
a
n
o
t
h
e
r
tool
t
o
o
l
function.
f
u
n
c
t
i
o
n
.
A
A
tool
t
o
o
l
is
i
s
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
that
t
h
a
t
supports
s
u
p
p
o
r
t
s
the
t
h
e
system.
s
y
s
t
e
m
.
If
I
f
a
a
tool
t
o
o
l
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
previously
p
r
e
v
i
o
u
s
l
y
qualified
q
u
a
l
i
f
i
e
d
on
o
n
one
o
n
e
system
s
y
s
t
e
m
is
i
s
proposed
p
r
o
p
o
s
e
d
for
f
o
r
use
u
s
e
on
o
n
another
a
n
o
t
h
e
r
system,
s
y
s
t
e
m
,
it
i
t
should
s
h
o
u
l
d
be
b
e
re-
r
e
-
qualified
q
u
a
l
i
f
i
e
d
within
w
i
t
h
i
n
the
t
h
e
context
c
o
n
t
e
x
t
of
o
f
that
t
h
a
t
other
o
t
h
e
r
system.
s
y
s
t
e
m
.
85
8
5
12.2.2
1
2
.
2
.
2
Determining
D
e
t
e
r
m
i
n
i
n
g
the
t
h
e
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Level
L
e
v
e
l
If
I
f
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
is
i
s
needed,
n
e
e
d
e
d
,
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
tool
t
o
o
l
use
u
s
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
processes
p
r
o
c
e
s
s
e
s
should
s
h
o
u
l
d
be
b
e
assessed
a
s
s
e
s
s
e
d
in
i
n
order
o
r
d
e
r
to
t
o
determine
d
e
t
e
r
m
i
n
e
its
i
t
s
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
level
l
e
v
e
l
(TQL).
(
T
Q
L
)
.
The
T
h
e
following
f
o
l
l
o
w
i
n
g
criteria
c
r
i
t
e
r
i
a
should
s
h
o
u
l
d
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
impact
i
m
p
a
c
t
of
o
f
the
t
h
e
tool:
t
o
o
l
:
-
Criteria
C
r
i
t
e
r
i
a
1:
1
:
A
A
tool
t
o
o
l
whose
w
h
o
s
e
output
o
u
t
p
u
t
is
i
s
part
p
a
r
t
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
and
a
n
d
thus
t
h
u
s
could
c
o
u
l
d
insert
i
n
s
e
r
t
an
a
n
error.
e
r
r
o
r
.
-
Criteria
C
r
i
t
e
r
i
a
2:
2
:
A
A
tool
t
o
o
l
that
t
h
a
t
automates
a
u
t
o
m
a
t
e
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
process(es)
p
r
o
c
e
s
s
(
e
s
)
and
a
n
d
thus
t
h
u
s
could
c
o
u
l
d
fail
f
a
i
l
to
t
o
detect
d
e
t
e
c
t
an
a
n
error,
e
r
r
o
r
,
and
a
n
d
whose
w
h
o
s
e
output
o
u
t
p
u
t
is
i
s
used
u
s
e
d
to
t
o
justify
j
u
s
t
i
f
y
the
t
h
e
elimination
e
l
i
m
i
n
a
t
i
o
n
or
o
r
reduction
r
e
d
u
c
t
i
o
n
of:
o
f
:
-
Verification
V
e
r
i
f
i
c
a
t
i
o
n
process(es)
p
r
o
c
e
s
s
(
e
s
)
other
o
t
h
e
r
than
t
h
a
n
that
t
h
a
t
automated
a
u
t
o
m
a
t
e
d
by
b
y
the
t
h
e
tool,
t
o
o
l
,
or
o
r
-
Development
D
e
v
e
l
o
p
m
e
n
t
process(es)
p
r
o
c
e
s
s
(
e
s
)
that
t
h
a
t
could
c
o
u
l
d
have
h
a
v
e
an
a
n
impact
i
m
p
a
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
.
-
Criteria
C
r
i
t
e
r
i
a
3:
3
:
A
A
tool
t
o
o
l
that,
t
h
a
t
,
within
w
i
t
h
i
n
the
t
h
e
scope
s
c
o
p
e
of
o
f
its
i
t
s
intended
i
n
t
e
n
d
e
d
use,
u
s
e
,
could
c
o
u
l
d
fail
f
a
i
l
to
t
o
detect
d
e
t
e
c
t
an
a
n
error.
e
r
r
o
r
.
If
I
f
the
t
h
e
tool
t
o
o
l
eliminates,
e
l
i
m
i
n
a
t
e
s
,
reduces,
r
e
d
u
c
e
s
,
or
o
r
automates
a
u
t
o
m
a
t
e
s
processes
p
r
o
c
e
s
s
e
s
in
i
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
and
a
n
d
its
i
t
s
output
o
u
t
p
u
t
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
,
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
e
TQL
T
Q
L
is
i
s
as
a
s
shown
s
h
o
w
n
in
i
n
Table
T
a
b
l
e
12-1.
1
2
-
1
.
Five
F
i
v
e
levels
l
e
v
e
l
s
of
o
f
tool
t
o
o
l
qualification,
q
u
a
l
i
f
i
c
a
t
i
o
n
,
TQL-1
T
Q
L
-
1
to
t
o
TQL-5,
T
Q
L
-
5
,
are
a
r
e
identified
i
d
e
n
t
i
f
i
e
d
based
b
a
s
e
d
on
o
n
the
t
h
e
tool
t
o
o
l
use
u
s
e
and
a
n
d
its
i
t
s
potential
p
o
t
e
n
t
i
a
l
impact
i
m
p
a
c
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
processes.
p
r
o
c
e
s
s
e
s
.
TQL-1
T
Q
L
-
1
is
i
s
the
t
h
e
most
m
o
s
t
rigorous
r
i
g
o
r
o
u
s
level
l
e
v
e
l
and
a
n
d
TQL-5
T
Q
L
-
5
is
i
s
the
t
h
e
least
l
e
a
s
t
rigorous
r
i
g
o
r
o
u
s
level.
l
e
v
e
l
.
When
W
h
e
n
assessing
a
s
s
e
s
s
i
n
g
the
t
h
e
impact
i
m
p
a
c
t
of
o
f
a
a
given
g
i
v
e
n
tool,
t
o
o
l
,
the
t
h
e
criteria
c
r
i
t
e
r
i
a
should
s
h
o
u
l
d
be
b
e
considered
c
o
n
s
i
d
e
r
e
d
sequentially
s
e
q
u
e
n
t
i
a
l
l
y
from
f
r
o
m
criteria
c
r
i
t
e
r
i
a
1
1
to
t
o
criteria
c
r
i
t
e
r
i
a
3.
3
.
The
T
h
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
level
l
e
v
e
l
should
s
h
o
u
l
d
be
b
e
coordinated
c
o
o
r
d
i
n
a
t
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
as
a
s
early
e
a
r
l
y
as
a
s
possible.
p
o
s
s
i
b
l
e
.
Table
T
a
b
l
e
12-1
1
2
-
1
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Level
L
e
v
e
l
Determination
D
e
t
e
r
m
i
n
a
t
i
o
n
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Criteria
C
r
i
t
e
r
i
a
1
1
2
2
3
3
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
Process
P
r
o
c
e
s
s
A
A
TQL-1
T
Q
L
-
1
TQL-4
T
Q
L
-
4
TQL-5
T
Q
L
-
5
B
B
TQL-2
T
Q
L
-
2
TQL-4
T
Q
L
-
4
TQL-5
T
Q
L
-
5
C
C
TQL-3
T
Q
L
-
3
TQL-5
T
Q
L
-
5
TQL-5
T
Q
L
-
5
D
D
TQL-4
T
Q
L
-
4
TQL-5
T
Q
L
-
5
TQL-5
T
Q
L
-
5
The
T
h
e
objectives,
o
b
j
e
c
t
i
v
e
s
,
activities,
a
c
t
i
v
i
t
i
e
s
,
guidance,
g
u
i
d
a
n
c
e
,
and
a
n
d
life
l
i
f
e
cycle
c
y
c
l
e
data
d
a
t
a
required
r
e
q
u
i
r
e
d
for
f
o
r
each
e
a
c
h
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Level
L
e
v
e
l
are
a
r
e
described
d
e
s
c
r
i
b
e
d
in
i
n
DO-330,
D
O
-
3
3
0
,
“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
Considerations.”
C
o
n
s
i
d
e
r
a
t
i
o
n
s
.
”
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
86
8
6
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
section
s
e
c
t
i
o
n
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
in
i
n
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
,
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
.
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
or
o
r
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
supplement.
s
u
p
p
l
e
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
that
t
h
a
t
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
.
One
O
n
e
technique
t
e
c
h
n
i
q
u
e
for
f
o
r
presenting
p
r
e
s
e
n
t
i
n
g
the
t
h
e
rationale
r
a
t
i
o
n
a
l
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
is
i
s
an
a
n
assurance
a
s
s
u
r
a
n
c
e
case,
c
a
s
e
,
in
i
n
which
w
h
i
c
h
arguments
a
r
g
u
m
e
n
t
s
are
a
r
e
explicitly
e
x
p
l
i
c
i
t
l
y
given
g
i
v
e
n
to
t
o
link
l
i
n
k
the
t
h
e
evidence
e
v
i
d
e
n
c
e
to
t
o
the
t
h
e
claims
c
l
a
i
m
s
of
o
f
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
.
-
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
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
one
o
n
e
or
o
r
more
m
o
r
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
activities
a
c
t
i
v
i
t
i
e
s
identified
i
d
e
n
t
i
f
i
e
d
in
i
n
section
s
e
c
t
i
o
n
6.
6
.
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
,
activities
a
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
-
Defining
D
e
f
i
n
i
n
g
the
t
h
e
complete
c
o
m
p
l
e
t
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
.
-
Performing
P
e
r
f
o
r
m
i
n
g
an
a
n
analysis
a
n
a
l
y
s
i
s
that
t
h
a
t
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
.
-
Developing
D
e
v
e
l
o
p
i
n
g
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
.
-
Developing
D
e
v
e
l
o
p
i
n
g
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.2
1
2
.
3
.
2
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
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
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-
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
.
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
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
use
u
s
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
,
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
.
87
8
7
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
in
i
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
:
-
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
.
-
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
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.2.1
1
2
.
3
.
2
.
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
.
Activities
A
c
t
i
v
i
t
i
e
s
include:
i
n
c
l
u
d
e
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
88
8
8
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
-
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
.
Note:
N
o
t
e
:
Section
S
e
c
t
i
o
n
12.3.2.1
1
2
.
3
.
2
.
1
only
o
n
l
y
addresses
a
d
d
r
e
s
s
e
s
the
t
h
e
subject
s
u
b
j
e
c
t
of
o
f
independence.
i
n
d
e
p
e
n
d
e
n
c
e
.
Reduction
R
e
d
u
c
t
i
o
n
of
o
f
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
is
i
s
not
n
o
t
discussed
d
i
s
c
u
s
s
e
d
or
o
r
intended.
i
n
t
e
n
d
e
d
.
12.3.2.2
1
2
.
3
.
2
.
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
(see
(
s
e
e
6.4.3.a)
6
.
4
.
3
.
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-compared
c
r
o
s
s
-
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
complete
c
o
m
p
l
e
t
e
the
t
h
e
following
f
o
l
l
o
w
i
n
g
activities:
a
c
t
i
v
i
t
i
e
s
:
-
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
.
-
Show
S
h
o
w
that
t
h
a
t
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
.
-
Show
S
h
o
w
that
t
h
a
t
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.2.3
1
2
.
3
.
2
.
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
guidance
g
u
i
d
a
n
c
e
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
(see
(
s
e
e
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
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
.
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
,
the
t
h
e
accompanying
a
c
c
o
m
p
a
n
y
i
n
g
Level
L
e
v
e
l
A
A
activity
a
c
t
i
v
i
t
y
(see
(
s
e
e
6.4.4.2.b)
6
.
4
.
4
.
2
.
b
)
to
t
o
evaluate
e
v
a
l
u
a
t
e
any
a
n
y
additional
a
d
d
i
t
i
o
n
a
l
code
c
o
d
e
(generated
(
g
e
n
e
r
a
t
e
d
by
b
y
a
a
compiler,
c
o
m
p
i
l
e
r
,
linker,
l
i
n
k
e
r
,
or
o
r
other
o
t
h
e
r
means)
m
e
a
n
s
)
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
need
n
e
e
d
not
n
o
t
be
b
e
done
d
o
n
e
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
completes
c
o
m
p
l
e
t
e
s
the
t
h
e
following
f
o
l
l
o
w
i
n
g
activities:
a
c
t
i
v
i
t
i
e
s
:
-
Show
S
h
o
w
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
.
-
Show
S
h
o
w
that
t
h
a
t
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.2.4
1
2
.
3
.
2
.
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
tools
t
o
o
l
s
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
process
p
r
o
c
e
s
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
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
complete
c
o
m
p
l
e
t
e
the
t
h
e
following
f
o
l
l
o
w
i
n
g
activities:
a
c
t
i
v
i
t
i
e
s
:
-
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
.
-
Show
S
h
o
w
that
t
h
a
t
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.2.5
1
2
.
3
.
2
.
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
the
t
h
e
approach
a
p
p
r
o
a
c
h
to
t
o
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
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
,
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
should
s
h
o
u
l
d
complete
c
o
m
p
l
e
t
e
the
t
h
e
following
f
o
l
l
o
w
i
n
g
activities:
a
c
t
i
v
i
t
i
e
s
:
89
8
9
-
Provide
P
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
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
.
-
Provide
P
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
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
.
-
Provide
P
r
o
v
i
d
e
evidence
e
v
i
d
e
n
c
e
that
t
h
a
t
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
,
for
f
o
r
example,
e
x
a
m
p
l
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.3
1
2
.
3
.
3
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
Many
M
a
n
y
methods
m
e
t
h
o
d
s
for
f
o
r
predicting
p
r
e
d
i
c
t
i
n
g
software
s
o
f
t
w
a
r
e
reliability
r
e
l
i
a
b
i
l
i
t
y
based
b
a
s
e
d
on
o
n
developmental
d
e
v
e
l
o
p
m
e
n
t
a
l
metrics
m
e
t
r
i
c
s
have
h
a
v
e
been
b
e
e
n
published,
p
u
b
l
i
s
h
e
d
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
software
s
o
f
t
w
a
r
e
structure,
s
t
r
u
c
t
u
r
e
,
defect
d
e
f
e
c
t
detection
d
e
t
e
c
t
i
o
n
rate,
r
a
t
e
,
etc.
e
t
c
.
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
those
t
h
o
s
e
types
t
y
p
e
s
of
o
f
methods,
m
e
t
h
o
d
s
,
because
b
e
c
a
u
s
e
at
a
t
the
t
h
e
time
t
i
m
e
of
o
f
writing,
w
r
i
t
i
n
g
,
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
did
d
i
d
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
.
12.3.4
1
2
.
3
.
4
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
:
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
.
Length
L
e
n
g
t
h
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
.
Actual
A
c
t
u
a
l
error
e
r
r
o
r
rates
r
a
t
e
s
in
i
n
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
.
Impact
I
m
p
a
c
t
of
o
f
modifications.
m
o
d
i
f
i
c
a
t
i
o
n
s
.
Use
U
s
e
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
data
d
a
t
a
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
is
i
s
predicated
p
r
e
d
i
c
a
t
e
d
upon
u
p
o
n
sufficiency,
s
u
f
f
i
c
i
e
n
c
y
,
relevance,
r
e
l
e
v
a
n
c
e
,
and
a
n
d
types
t
y
p
e
s
of
o
f
problems
p
r
o
b
l
e
m
s
occurring
o
c
c
u
r
r
i
n
g
during
d
u
r
i
n
g
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period.
p
e
r
i
o
d
.
The
T
h
e
use,
u
s
e
,
conditions
c
o
n
d
i
t
i
o
n
s
of
o
f
use,
u
s
e
,
and
a
n
d
results
r
e
s
u
l
t
s
of
o
f
software
s
o
f
t
w
a
r
e
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
defined,
d
e
f
i
n
e
d
,
assessed
a
s
s
e
s
s
e
d
by
b
y
the
t
h
e
system
s
y
s
t
e
m
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
process,
p
r
o
c
e
s
s
,
and
a
n
d
submitted
s
u
b
m
i
t
t
e
d
to
t
o
the
t
h
e
appropriate
a
p
p
r
o
p
r
i
a
t
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
.
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
applicability
a
p
p
l
i
c
a
b
i
l
i
t
y
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
and
a
n
d
the
t
h
e
length
l
e
n
g
t
h
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
needed
n
e
e
d
e
d
is
i
s
presented
p
r
e
s
e
n
t
e
d
below.
b
e
l
o
w
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
90
9
0
12.3.4.1
1
2
.
3
.
4
.
1
Relevance
R
e
l
e
v
a
n
c
e
of
o
f
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
The
T
h
e
following
f
o
l
l
o
w
i
n
g
applies
a
p
p
l
i
e
s
for
f
o
r
establishing
e
s
t
a
b
l
i
s
h
i
n
g
the
t
h
e
relevance
r
e
l
e
v
a
n
c
e
of
o
f
service
s
e
r
v
i
c
e
history:
h
i
s
t
o
r
y
:
-
Type
T
y
p
e
of
o
f
service
s
e
r
v
i
c
e
history:
h
i
s
t
o
r
y
:
Service
S
e
r
v
i
c
e
history
h
i
s
t
o
r
y
to
t
o
be
b
e
used
u
s
e
d
should
s
h
o
u
l
d
be
b
e
defined
d
e
f
i
n
e
d
and
a
n
d
agreement
a
g
r
e
e
m
e
n
t
obtained
o
b
t
a
i
n
e
d
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
.
Service
S
e
r
v
i
c
e
history
h
i
s
t
o
r
y
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
using
u
s
i
n
g
a
a
measure
m
e
a
s
u
r
e
relevant
r
e
l
e
v
a
n
t
to
t
o
the
t
h
e
operations
o
p
e
r
a
t
i
o
n
s
of
o
f
the
t
h
e
system.
s
y
s
t
e
m
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
flight
f
l
i
g
h
t
hours
h
o
u
r
s
is
i
s
an
a
n
appropriate
a
p
p
r
o
p
r
i
a
t
e
measure
m
e
a
s
u
r
e
for
f
o
r
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
used
u
s
e
d
continuously
c
o
n
t
i
n
u
o
u
s
l
y
during
d
u
r
i
n
g
flight,
f
l
i
g
h
t
,
such
s
u
c
h
as
a
s
flight
f
l
i
g
h
t
control
c
o
n
t
r
o
l
software,
s
o
f
t
w
a
r
e
,
and
a
n
d
the
t
h
e
number
n
u
m
b
e
r
of
o
f
demands
d
e
m
a
n
d
s
is
i
s
an
a
n
appropriate
a
p
p
r
o
p
r
i
a
t
e
measure
m
e
a
s
u
r
e
for
f
o
r
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
executed
e
x
e
c
u
t
e
d
on
o
n
demand,
d
e
m
a
n
d
,
such
s
u
c
h
as
a
s
landing
l
a
n
d
i
n
g
gear
g
e
a
r
software.
s
o
f
t
w
a
r
e
.
b.
b
.
-
Known
K
n
o
w
n
configuration:
c
o
n
f
i
g
u
r
a
t
i
o
n
:
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
.
Operating
O
p
e
r
a
t
i
n
g
time
t
i
m
e
collection
c
o
l
l
e
c
t
i
o
n
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
show
s
h
o
w
that
t
h
a
t
the
t
h
e
means
m
e
a
n
s
of
o
f
collecting
c
o
l
l
e
c
t
i
n
g
and
a
n
d
calculating
c
a
l
c
u
l
a
t
i
n
g
flight
f
l
i
g
h
t
hours
h
o
u
r
s
for
f
o
r
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
used
u
s
e
d
continuously
c
o
n
t
i
n
u
o
u
s
l
y
during
d
u
r
i
n
g
flight
f
l
i
g
h
t
or
o
r
number
n
u
m
b
e
r
of
o
f
demands
d
e
m
a
n
d
s
for
f
o
r
software
s
o
f
t
w
a
r
e
that
t
h
a
t
is
i
s
executed
e
x
e
c
u
t
e
d
on
o
n
demand
d
e
m
a
n
d
is
i
s
sufficiently
s
u
f
f
i
c
i
e
n
t
l
y
accurate
a
c
c
u
r
a
t
e
and
a
n
d
complete.
c
o
m
p
l
e
t
e
.
Flight
F
l
i
g
h
t
hours
h
o
u
r
s
or
o
r
number
n
u
m
b
e
r
of
o
f
demands
d
e
m
a
n
d
s
should
s
h
o
u
l
d
account
a
c
c
o
u
n
t
for
f
o
r
changes
c
h
a
n
g
e
s
in
i
n
any
a
n
y
factors
f
a
c
t
o
r
s
that
t
h
a
t
are
a
r
e
important
i
m
p
o
r
t
a
n
t
to
t
o
the
t
h
e
intended
i
n
t
e
n
d
e
d
application
a
p
p
l
i
c
a
t
i
o
n
including
i
n
c
l
u
d
i
n
g
but
b
u
t
not
n
o
t
limited
l
i
m
i
t
e
d
to:
t
o
:
-
Software
S
o
f
t
w
a
r
e
and
a
n
d
system
s
y
s
t
e
m
configuration.
c
o
n
f
i
g
u
r
a
t
i
o
n
.
-
Operational
O
p
e
r
a
t
i
o
n
a
l
mode
m
o
d
e
or
o
r
state.
s
t
a
t
e
.
-
Operating
O
p
e
r
a
t
i
n
g
environment.
e
n
v
i
r
o
n
m
e
n
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
:
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
.
An
A
n
analysis
a
n
a
l
y
s
i
s
should
s
h
o
u
l
d
be
b
e
conducted
c
o
n
d
u
c
t
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
whether
w
h
e
t
h
e
r
the
t
h
e
changes
c
h
a
n
g
e
s
made
m
a
d
e
to
t
o
the
t
h
e
software
s
o
f
t
w
a
r
e
alter
a
l
t
e
r
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
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
data
d
a
t
a
for
f
o
r
the
t
h
e
period
p
e
r
i
o
d
preceding
p
r
e
c
e
d
i
n
g
the
t
h
e
changes.
c
h
a
n
g
e
s
.
-
Usage
U
s
a
g
e
and
a
n
d
Environment:
E
n
v
i
r
o
n
m
e
n
t
:
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
.
-
It
I
t
should
s
h
o
u
l
d
be
b
e
assured
a
s
s
u
r
e
d
that
t
h
a
t
software
s
o
f
t
w
a
r
e
capabilities
c
a
p
a
b
i
l
i
t
i
e
s
to
t
o
be
b
e
used
u
s
e
d
are
a
r
e
exercised
e
x
e
r
c
i
s
e
d
in
i
n
all
a
l
l
operational
o
p
e
r
a
t
i
o
n
a
l
modes.
m
o
d
e
s
.
-
Analysis
A
n
a
l
y
s
i
s
should
s
h
o
u
l
d
also
a
l
s
o
be
b
e
performed
p
e
r
f
o
r
m
e
d
to
t
o
assure
a
s
s
u
r
e
that
t
h
a
t
relevant
r
e
l
e
v
a
n
t
permutations
p
e
r
m
u
t
a
t
i
o
n
s
of
o
f
input
i
n
p
u
t
data
d
a
t
a
are
a
r
e
executed.
e
x
e
c
u
t
e
d
.
-
The
T
h
e
operating
o
p
e
r
a
t
i
n
g
environment
e
n
v
i
r
o
n
m
e
n
t
used
u
s
e
d
to
t
o
collect
c
o
l
l
e
c
t
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
assessed
a
s
s
e
s
s
e
d
to
t
o
show
s
h
o
w
relevance
r
e
l
e
v
a
n
c
e
to
t
o
the
t
h
e
intended
i
n
t
e
n
d
e
d
use
u
s
e
in
i
n
the
t
h
e
proposed
p
r
o
p
o
s
e
d
application.
a
p
p
l
i
c
a
t
i
o
n
.
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
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
in
i
n
the
t
h
e
target
t
a
r
g
e
t
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
If
I
f
credit
c
r
e
d
i
t
is
i
s
being
b
e
i
n
g
sought
s
o
u
g
h
t
for
f
o
r
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
the
t
h
e
hardware
h
a
r
d
w
a
r
e
environment,
e
n
v
i
r
o
n
m
e
n
t
,
then
t
h
e
n
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
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
and
a
n
d
the
t
h
e
intended
i
n
t
e
n
d
e
d
environment
e
n
v
i
r
o
n
m
e
n
t
should
s
h
o
u
l
d
be
b
e
addressed.
a
d
d
r
e
s
s
e
d
.
The
T
h
e
impact
i
m
p
a
c
t
of
o
f
any
a
n
y
hardware
h
a
r
d
w
a
r
e
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
during
d
u
r
i
n
g
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period
p
e
r
i
o
d
should
s
h
o
u
l
d
also
a
l
s
o
be
b
e
assessed.
a
s
s
e
s
s
e
d
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
Deactivated
D
e
a
c
t
i
v
a
t
e
d
code:
c
o
d
e
:
Analysis
A
n
a
l
y
s
i
s
should
s
h
o
u
l
d
be
b
e
performed
p
e
r
f
o
r
m
e
d
to
t
o
show
s
h
o
w
that
t
h
a
t
any
a
n
y
code
c
o
d
e
that
t
h
a
t
was
w
a
s
deactivated
d
e
a
c
t
i
v
a
t
e
d
during
d
u
r
i
n
g
the
t
h
e
period
p
e
r
i
o
d
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
is
i
s
not
n
o
t
activated
a
c
t
i
v
a
t
e
d
in
i
n
the
t
h
e
new
n
e
w
environment.
e
n
v
i
r
o
n
m
e
n
t
.
If
I
f
it
i
t
is
i
s
found
f
o
u
n
d
that
t
h
a
t
previously
p
r
e
v
i
o
u
s
l
y
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
is
i
s
activated
a
c
t
i
v
a
t
e
d
in
i
n
the
t
h
e
new
n
e
w
environment,
e
n
v
i
r
o
n
m
e
n
t
,
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
conducted.
c
o
n
d
u
c
t
e
d
.
91
9
1
12.3.4.2
1
2
.
3
.
4
.
2
Sufficiency
S
u
f
f
i
c
i
e
n
c
y
of
o
f
Accumulated
A
c
c
u
m
u
l
a
t
e
d
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
The
T
h
e
required
r
e
q
u
i
r
e
d
amount
a
m
o
u
n
t
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
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
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
and
a
n
d
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
-
Any
A
n
y
differences
d
i
f
f
e
r
e
n
c
e
s
in
i
n
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
and
a
n
d
system
s
y
s
t
e
m
operational
o
p
e
r
a
t
i
o
n
a
l
environment.
e
n
v
i
r
o
n
m
e
n
t
.
-
The
T
h
e
objectives
o
b
j
e
c
t
i
v
e
s
from
f
r
o
m
sections
s
e
c
t
i
o
n
s
4
4
to
t
o
9
9
being
b
e
i
n
g
addressed
a
d
d
r
e
s
s
e
d
by
b
y
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
-
Evidence,
E
v
i
d
e
n
c
e
,
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
service
s
e
r
v
i
c
e
history,
h
i
s
t
o
r
y
,
addressing
a
d
d
r
e
s
s
i
n
g
those
t
h
o
s
e
objectives.
o
b
j
e
c
t
i
v
e
s
.
12.3.4.3
1
2
.
3
.
4
.
3
Collection,
C
o
l
l
e
c
t
i
o
n
,
Reporting,
R
e
p
o
r
t
i
n
g
,
and
a
n
d
Analysis
A
n
a
l
y
s
i
s
of
o
f
Problems
P
r
o
b
l
e
m
s
Found
F
o
u
n
d
During
D
u
r
i
n
g
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
-
Problem
P
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
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
show
s
h
o
w
that
t
h
a
t
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
period
p
e
r
i
o
d
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
problems
p
r
o
b
l
e
m
s
during
d
u
r
i
n
g
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period
p
e
r
i
o
d
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
.
-
The
T
h
e
specific
s
p
e
c
i
f
i
c
data
d
a
t
a
to
t
o
be
b
e
collected
c
o
l
l
e
c
t
e
d
should
s
h
o
u
l
d
be
b
e
agreed
a
g
r
e
e
d
on
o
n
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
and
a
n
d
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
the
t
h
e
following
f
o
l
l
o
w
i
n
g
for
f
o
r
each
e
a
c
h
recorded
r
e
c
o
r
d
e
d
problem,
p
r
o
b
l
e
m
,
in
i
n
addition
a
d
d
i
t
i
o
n
to
t
o
the
t
h
e
items
i
t
e
m
s
in
i
n
section
s
e
c
t
i
o
n
11.17:
1
1
.
1
7
:
-
The
T
h
e
hardware/software
h
a
r
d
w
a
r
e
/
s
o
f
t
w
a
r
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
in
i
n
effect
e
f
f
e
c
t
when
w
h
e
n
the
t
h
e
problem
p
r
o
b
l
e
m
occurred.
o
c
c
u
r
r
e
d
.
-
The
T
h
e
operating
o
p
e
r
a
t
i
n
g
environment
e
n
v
i
r
o
n
m
e
n
t
within
w
i
t
h
i
n
which
w
h
i
c
h
the
t
h
e
problem
p
r
o
b
l
e
m
occurred.
o
c
c
u
r
r
e
d
.
-
The
T
h
e
operating
o
p
e
r
a
t
i
n
g
mode
m
o
d
e
or
o
r
state
s
t
a
t
e
within
w
i
t
h
i
n
which
w
h
i
c
h
the
t
h
e
problem
p
r
o
b
l
e
m
occurred.
o
c
c
u
r
r
e
d
.
iv.
i
v
.
Any
A
n
y
application-specific
a
p
p
l
i
c
a
t
i
o
n
-
s
p
e
c
i
f
i
c
information
i
n
f
o
r
m
a
t
i
o
n
needed
n
e
e
d
e
d
for
f
o
r
problem
p
r
o
b
l
e
m
assessment.
a
s
s
e
s
s
m
e
n
t
.
v.
v
.
Classification
C
l
a
s
s
i
f
i
c
a
t
i
o
n
of
o
f
the
t
h
e
problem
p
r
o
b
l
e
m
with
w
i
t
h
respect
r
e
s
p
e
c
t
to
t
o
severity,
s
e
v
e
r
i
t
y
,
safety
s
a
f
e
t
y
significance,
s
i
g
n
i
f
i
c
a
n
c
e
,
and
a
n
d
whether
w
h
e
t
h
e
r
the
t
h
e
problem
p
r
o
b
l
e
m
was
w
a
s
the
t
h
e
result
r
e
s
u
l
t
of
o
f
a
a
change
c
h
a
n
g
e
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
since
s
i
n
c
e
the
t
h
e
start
s
t
a
r
t
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
data
d
a
t
a
collection.
c
o
l
l
e
c
t
i
o
n
.
vi.
v
i
.
Assessment
A
s
s
e
s
s
m
e
n
t
of
o
f
whether
w
h
e
t
h
e
r
the
t
h
e
problem
p
r
o
b
l
e
m
was:
w
a
s
:
Reproducible.
R
e
p
r
o
d
u
c
i
b
l
e
.
Recoverable.
R
e
c
o
v
e
r
a
b
l
e
.
Related
R
e
l
a
t
e
d
to
t
o
other
o
t
h
e
r
previously
p
r
e
v
i
o
u
s
l
y
reported
r
e
p
o
r
t
e
d
problems,
p
r
o
b
l
e
m
s
,
including,
i
n
c
l
u
d
i
n
g
,
but
b
u
t
not
n
o
t
limited
l
i
m
i
t
e
d
to,
t
o
,
a
a
common
c
o
m
m
o
n
cause.
c
a
u
s
e
.
-
The
T
h
e
chronological
c
h
r
o
n
o
l
o
g
i
c
a
l
trend
t
r
e
n
d
of
o
f
Problem
P
r
o
b
l
e
m
Reports
R
e
p
o
r
t
s
should
s
h
o
u
l
d
be
b
e
evaluated
e
v
a
l
u
a
t
e
d
and
a
n
d
any
a
n
y
increasing
i
n
c
r
e
a
s
i
n
g
trend
t
r
e
n
d
explained.
e
x
p
l
a
i
n
e
d
.
-
The
T
h
e
completeness
c
o
m
p
l
e
t
e
n
e
s
s
of
o
f
the
t
h
e
software’s
s
o
f
t
w
a
r
e
’
s
error
e
r
r
o
r
history
h
i
s
t
o
r
y
should
s
h
o
u
l
d
also
a
l
s
o
be
b
e
addressed.
a
d
d
r
e
s
s
e
d
.
This
T
h
i
s
includes:
i
n
c
l
u
d
e
s
:
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
92
9
2
-
The
T
h
e
ability
a
b
i
l
i
t
y
to
t
o
detect
d
e
t
e
c
t
faults
f
a
u
l
t
s
and
a
n
d
maintain
m
a
i
n
t
a
i
n
a
a
fault
f
a
u
l
t
log.
l
o
g
.
-
The
T
h
e
means
m
e
a
n
s
for
f
o
r
operators
o
p
e
r
a
t
o
r
s
to
t
o
report
r
e
p
o
r
t
problems.
p
r
o
b
l
e
m
s
.
-
The
T
h
e
completeness
c
o
m
p
l
e
t
e
n
e
s
s
of
o
f
the
t
h
e
problem
p
r
o
b
l
e
m
reporting
r
e
p
o
r
t
i
n
g
records.
r
e
c
o
r
d
s
.
iv.
i
v
.
The
T
h
e
means
m
e
a
n
s
for
f
o
r
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
to
t
o
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
system
s
y
s
t
e
m
safety
s
a
f
e
t
y
impact
i
m
p
a
c
t
of
o
f
any
a
n
y
open
o
p
e
n
Problem
P
r
o
b
l
e
m
Reports,
R
e
p
o
r
t
s
,
and
a
n
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
whether
w
h
e
t
h
e
r
problems
p
r
o
b
l
e
m
s
that
t
h
a
t
were
w
e
r
e
not
n
o
t
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
during
d
u
r
i
n
g
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
will
w
i
l
l
be
b
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
in
i
n
the
t
h
e
intended
i
n
t
e
n
d
e
d
environment.
e
n
v
i
r
o
n
m
e
n
t
.
Problems
P
r
o
b
l
e
m
s
that
t
h
a
t
were
w
e
r
e
not
n
o
t
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
in
i
n
the
t
h
e
service
s
e
r
v
i
c
e
experience
e
x
p
e
r
i
e
n
c
e
environment,
e
n
v
i
r
o
n
m
e
n
t
,
but
b
u
t
which
w
h
i
c
h
will
w
i
l
l
be
b
e
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
in
i
n
the
t
h
e
intended
i
n
t
e
n
d
e
d
environment,
e
n
v
i
r
o
n
m
e
n
t
,
might
m
i
g
h
t
indicate
i
n
d
i
c
a
t
e
the
t
h
e
need
n
e
e
d
for
f
o
r
additional
a
d
d
i
t
i
o
n
a
l
verification.
v
e
r
i
f
i
c
a
t
i
o
n
.
v.
v
.
The
T
h
e
means
m
e
a
n
s
for
f
o
r
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
to
t
o
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
number
n
u
m
b
e
r
of
o
f
occurrences
o
c
c
u
r
r
e
n
c
e
s
of
o
f
a
a
specific
s
p
e
c
i
f
i
c
problem.
p
r
o
b
l
e
m
.
-
Process-related
P
r
o
c
e
s
s
-
r
e
l
a
t
e
d
problems:
p
r
o
b
l
e
m
s
:
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
.
-
Safety-related
S
a
f
e
t
y
-
r
e
l
a
t
e
d
problems:
p
r
o
b
l
e
m
s
:
All
A
l
l
in-service
i
n
-
s
e
r
v
i
c
e
problems
p
r
o
b
l
e
m
s
should
s
h
o
u
l
d
be
b
e
evaluated
e
v
a
l
u
a
t
e
d
to
t
o
determine
d
e
t
e
r
m
i
n
e
which
w
h
i
c
h
problems
p
r
o
b
l
e
m
s
were
w
e
r
e
safety-related,
s
a
f
e
t
y
-
r
e
l
a
t
e
d
,
and
a
n
d
to
t
o
confirm
c
o
n
f
i
r
m
that
t
h
a
t
all
a
l
l
safety-related
s
a
f
e
t
y
-
r
e
l
a
t
e
d
problems
p
r
o
b
l
e
m
s
have
h
a
v
e
been
b
e
e
n
corrected.
c
o
r
r
e
c
t
e
d
.
12.3.4.4
1
2
.
3
.
4
.
4
Service
S
e
r
v
i
c
e
History
H
i
s
t
o
r
y
Information
I
n
f
o
r
m
a
t
i
o
n
to
t
o
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
The
T
h
e
following
f
o
l
l
o
w
i
n
g
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
and
a
n
d
agreed
a
g
r
e
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
when
w
h
e
n
seeking
s
e
e
k
i
n
g
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
service
s
e
r
v
i
c
e
history:
h
i
s
t
o
r
y
:
-
Rationale
R
a
t
i
o
n
a
l
e
for
f
o
r
claiming
c
l
a
i
m
i
n
g
relevant
r
e
l
e
v
a
n
t
service
s
e
r
v
i
c
e
history,
h
i
s
t
o
r
y
,
addressing
a
d
d
r
e
s
s
i
n
g
the
t
h
e
items
i
t
e
m
s
in
i
n
section
s
e
c
t
i
o
n
12.3.4.1.
1
2
.
3
.
4
.
1
.
-
Amount
A
m
o
u
n
t
of
o
f
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
needed
n
e
e
d
e
d
together
t
o
g
e
t
h
e
r
with
w
i
t
h
the
t
h
e
rationale.
r
a
t
i
o
n
a
l
e
.
This
T
h
i
s
should
s
h
o
u
l
d
include
i
n
c
l
u
d
e
the
t
h
e
items
i
t
e
m
s
in
i
n
section
s
e
c
t
i
o
n
12.3.4.2,
1
2
.
3
.
4
.
2
,
any
a
n
y
censoring
c
e
n
s
o
r
i
n
g
rules
r
u
l
e
s
for
f
o
r
data
d
a
t
a
used
u
s
e
d
in
i
n
estimation,
e
s
t
i
m
a
t
i
o
n
,
and
a
n
d
measured
m
e
a
s
u
r
e
d
parameters,
p
a
r
a
m
e
t
e
r
s
,
if
i
f
applicable.
a
p
p
l
i
c
a
b
l
e
.
This
T
h
i
s
data
d
a
t
a
should
s
h
o
u
l
d
be
b
e
provided
p
r
o
v
i
d
e
d
using
u
s
i
n
g
measures
m
e
a
s
u
r
e
s
relevant
r
e
l
e
v
a
n
t
to
t
o
the
t
h
e
operations
o
p
e
r
a
t
i
o
n
s
of
o
f
the
t
h
e
system.
s
y
s
t
e
m
.
-
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
total
t
o
t
a
l
relevant
r
e
l
e
v
a
n
t
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period,
p
e
r
i
o
d
,
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
.
”
Note:
N
o
t
e
:
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
.
The
T
h
e
length
l
e
n
g
t
h
of
o
f
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period
p
e
r
i
o
d
may
m
a
y
need
n
e
e
d
to
t
o
be
b
e
extended
e
x
t
e
n
d
e
d
or
o
r
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
may
m
a
y
be
b
e
inapplicable
i
n
a
p
p
l
i
c
a
b
l
e
as
a
s
an
a
n
alternative
a
l
t
e
r
n
a
t
i
v
e
means
m
e
a
n
s
of
o
f
compliance.
c
o
m
p
l
i
a
n
c
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
.
This
T
h
i
s
should
s
h
o
u
l
d
address
a
d
d
r
e
s
s
the
t
h
e
items
i
t
e
m
s
in
i
n
section
s
e
c
t
i
o
n
12.3.4.3a.
1
2
.
3
.
4
.
3
a
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
-
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
.
This
T
h
i
s
should
s
h
o
u
l
d
address
a
d
d
r
e
s
s
the
t
h
e
items
i
t
e
m
s
in
i
n
sections
s
e
c
t
i
o
n
s
12.3.4.3b
1
2
.
3
.
4
.
3
b
and
a
n
d
12.3.4.3c.
1
2
.
3
.
4
.
3
c
.
93
9
3
-
Definition
D
e
f
i
n
i
t
i
o
n
of
o
f
criteria
c
r
i
t
e
r
i
a
for
f
o
r
problems
p
r
o
b
l
e
m
s
that
t
h
a
t
would
w
o
u
l
d
invalidate
i
n
v
a
l
i
d
a
t
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
under
u
n
d
e
r
section
s
e
c
t
i
o
n
12.3.4.3
1
2
.
3
.
4
.
3
or
o
r
for
f
o
r
other
o
t
h
e
r
reasons.
r
e
a
s
o
n
s
.
-
Criteria
C
r
i
t
e
r
i
a
for
f
o
r
errors
e
r
r
o
r
s
that
t
h
a
t
will
w
i
l
l
be
b
e
corrected;
c
o
r
r
e
c
t
e
d
;
how
h
o
w
they
t
h
e
y
will
w
i
l
l
be
b
e
corrected
c
o
r
r
e
c
t
e
d
and
a
n
d
verified;
v
e
r
i
f
i
e
d
;
and
a
n
d
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
any
a
n
y
defects
d
e
f
e
c
t
s
for
f
o
r
which
w
h
i
c
h
no
n
o
action
a
c
t
i
o
n
will
w
i
l
l
be
b
e
taken.
t
a
k
e
n
.
-
Objectives
O
b
j
e
c
t
i
v
e
s
in
i
n
sections
s
e
c
t
i
o
n
s
4
4
to
t
o
9
9
to
t
o
be
b
e
addressed
a
d
d
r
e
s
s
e
d
through
t
h
r
o
u
g
h
the
t
h
e
use
u
s
e
of
o
f
service
s
e
r
v
i
c
e
history.
h
i
s
t
o
r
y
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
95
9
5
References
R
e
f
e
r
e
n
c
e
s
in
i
n
these
t
h
e
s
e
tables
t
a
b
l
e
s
point
p
o
i
n
t
to
t
o
those
t
h
o
s
e
sections
s
e
c
t
i
o
n
s
in
i
n
the
t
h
e
text
t
e
x
t
that
t
h
a
t
define
d
e
f
i
n
e
the
t
h
e
particular
p
a
r
t
i
c
u
l
a
r
objectives,
o
b
j
e
c
t
i
v
e
s
,
related
r
e
l
a
t
e
d
activities,
a
c
t
i
v
i
t
i
e
s
,
and
a
n
d
outputs.
o
u
t
p
u
t
s
.
The
T
h
e
tables
t
a
b
l
e
s
include
i
n
c
l
u
d
e
guidance
g
u
i
d
a
n
c
e
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
2.3.3.
2
.
3
.
3
.
-
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
(see
(
s
e
e
7.3).
7
.
3
)
.
These
T
h
e
s
e
tables
t
a
b
l
e
s
should
s
h
o
u
l
d
not
n
o
t
be
b
e
used
u
s
e
d
as
a
s
a
a
checklist.
c
h
e
c
k
l
i
s
t
.
These
T
h
e
s
e
tables
t
a
b
l
e
s
do
d
o
not
n
o
t
reflect
r
e
f
l
e
c
t
all
a
l
l
aspects
a
s
p
e
c
t
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
to
t
o
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
In
I
n
order
o
r
d
e
r
to
t
o
fully
f
u
l
l
y
understand
u
n
d
e
r
s
t
a
n
d
the
t
h
e
guidance,
g
u
i
d
a
n
c
e
,
the
t
h
e
full
f
u
l
l
body
b
o
d
y
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
considered.
c
o
n
s
i
d
e
r
e
d
.
The
T
h
e
following
f
o
l
l
o
w
i
n
g
legend
l
e
g
e
n
d
applies
a
p
p
l
i
e
s
to
t
o
“Applicability
“
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level”
L
e
v
e
l
”
and
a
n
d
“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
all
a
l
l
tables:
t
a
b
l
e
s
:
LEGEND:
L
E
G
E
N
D
:
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
should
s
h
o
u
l
d
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
with
w
i
t
h
independence.
i
n
d
e
p
e
n
d
e
n
c
e
.
The
T
h
e
objective
o
b
j
e
c
t
i
v
e
should
s
h
o
u
l
d
be
b
e
satisfied.
s
a
t
i
s
f
i
e
d
.
Blank
B
l
a
n
k
Satisfaction
S
a
t
i
s
f
a
c
t
i
o
n
of
o
f
objective
o
b
j
e
c
t
i
v
e
is
i
s
at
a
t
applicant’s
a
p
p
l
i
c
a
n
t
’
s
discretion.
d
i
s
c
r
e
t
i
o
n
.
Data
D
a
t
a
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
1
1
(CC1).
(
C
C
1
)
.
Data
D
a
t
a
satisfies
s
a
t
i
s
f
i
e
s
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
of
o
f
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
(CC2).
(
C
C
2
)
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
96
9
6
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
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
are
a
r
e
defined.
d
e
f
i
n
e
d
.
4.1.a
4
.
1
.
a
4.2.a
4
.
2
.
a
4.2.c
4
.
2
.
c
4.2.d
4
.
2
.
d
4.2.e
4
.
2
.
e
4.2.g
4
.
2
.
g
4.2.i
4
.
2
.
i
4.2.l
4
.
2
.
l
4.3.c
4
.
3
.
c
PSAC
P
S
A
C
11.1
1
1
.
1
SDP
S
D
P
11.2
1
1
.
2
SVP
S
V
P
11.3
1
1
.
3
SCM
S
C
M
Plan
P
l
a
n
11.4
1
1
.
4
SQA
S
Q
A
Plan
P
l
a
n
11.5
1
1
.
5
2
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
,
is
i
s
defined.
d
e
f
i
n
e
d
.
4.1.b
4
.
1
.
b
4.2i
4
.
2
i
4.3.b
4
.
3
.
b
PSAC
P
S
A
C
11.1
1
1
.
1
SDP
S
D
P
11.2
1
1
.
2
SVP
S
V
P
11.3
1
1
.
3
SCM
S
C
M
Plan
P
l
a
n
11.4
1
1
.
4
SQA
S
Q
A
Plan
P
l
a
n
11.5
1
1
.
5
3
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
is
i
s
selected
s
e
l
e
c
t
e
d
and
a
n
d
defined.
d
e
f
i
n
e
d
.
4.1.c
4
.
1
.
c
4.4.1
4
.
4
.
1
4.4.2.a
4
.
4
.
2
.
a
4.4.2.b
4
.
4
.
2
.
b
4.4.2.c
4
.
4
.
2
.
c
4.4.3
4
.
4
.
3
PSAC
P
S
A
C
11.1
1
1
.
1
SDP
S
D
P
11.2
1
1
.
2
SVP
S
V
P
11.3
1
1
.
3
SCM
S
C
M
Plan
P
l
a
n
11.4
1
1
.
4
SQA
S
Q
A
Plan
P
l
a
n
11.5
1
1
.
5
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
are
a
r
e
addressed.
a
d
d
r
e
s
s
e
d
.
4.1.d
4
.
1
.
d
4.2.f
4
.
2
.
f
4.2.h
4
.
2
.
h
4.2.i
4
.
2
.
i
4.2.j
4
.
2
.
j
4.2.k
4
.
2
.
k
PSAC
P
S
A
C
11.1
1
1
.
1
SDP
S
D
P
11.2
1
1
.
2
SVP
S
V
P
11.3
1
1
.
3
SCM
S
C
M
Plan
P
l
a
n
11.4
1
1
.
4
SQA
S
Q
A
Plan
P
l
a
n
11.5
1
1
.
5
5
5
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
are
a
r
e
defined.
d
e
f
i
n
e
d
.
4.1.e
4
.
1
.
e
4.2.b
4
.
2
.
b
4.2.g
4
.
2
.
g
4.5
4
.
5
SW
S
W
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
Standards
S
t
a
n
d
a
r
d
s
11.6
1
1
.
6
SW
S
W
Design
D
e
s
i
g
n
Standards
S
t
a
n
d
a
r
d
s
11.7
1
1
.
7
SW
S
W
Code
C
o
d
e
Standards
S
t
a
n
d
a
r
d
s
11.8
1
1
.
8
6
6
Software
S
o
f
t
w
a
r
e
plans
p
l
a
n
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
.
4.1.f
4
.
1
.
f
4.3.a
4
.
3
.
a
4.6
4
.
6
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
11.14
1
1
.
1
4
7
7
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
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
.
4.1.g
4
.
1
.
g
4.2.g
4
.
2
.
g
4.6
4
.
6
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
11.14
1
1
.
1
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
97
9
7
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
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
.
5.1.1.a
5
.
1
.
1
.
a
5.1.2.a
5
.
1
.
2
.
a
5.1.2.b
5
.
1
.
2
.
b
5.1.2.c
5
.
1
.
2
.
c
5.1.2.d
5
.
1
.
2
.
d
5.1.2.e
5
.
1
.
2
.
e
5.1.2.f
5
.
1
.
2
.
f
5.1.2.g
5
.
1
.
2
.
g
5.1.2.j
5
.
1
.
2
.
j
5.5.a
5
.
5
.
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
11.9
1
1
.
9
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
2
2
Derived
D
e
r
i
v
e
d
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
defined
d
e
f
i
n
e
d
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
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
process.
p
r
o
c
e
s
s
.
5.1.1.b
5
.
1
.
1
.
b
5.1.2.h
5
.
1
.
2
.
h
5.1.2.i
5
.
1
.
2
.
i
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
11.9
1
1
.
9
3
3
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
developed.
d
e
v
e
l
o
p
e
d
.
5.2.1.a
5
.
2
.
1
.
a
5.2.2.a
5
.
2
.
2
.
a
5.2.2.d
5
.
2
.
2
.
d
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
11.10
1
1
.
1
0
4
4
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
.
5.2.1.a
5
.
2
.
1
.
a
5.2.2.a
5
.
2
.
2
.
a
5.2.2.e
5
.
2
.
2
.
e
5.2.2.f
5
.
2
.
2
.
f
5.2.2.g
5
.
2
.
2
.
g
5.2.3.a
5
.
2
.
3
.
a
5.2.3.b
5
.
2
.
3
.
b
5.2.4.a
5
.
2
.
4
.
a
5.2.4.b
5
.
2
.
4
.
b
5.2.4.c
5
.
2
.
4
.
c
5.5.b
5
.
5
.
b
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
11.10
1
1
.
1
0
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
5
5
Derived
D
e
r
i
v
e
d
low-
l
o
w
-
level
l
e
v
e
l
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
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
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
process.
p
r
o
c
e
s
s
.
5.2.1.b
5
.
2
.
1
.
b
5.2.2.b
5
.
2
.
2
.
b
5.2.2.c
5
.
2
.
2
.
c
Design
D
e
s
i
g
n
Description
D
e
s
c
r
i
p
t
i
o
n
11.10
1
1
.
1
0
6
6
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
.
5.3.1.a
5
.
3
.
1
.
a
5.3.2.a
5
.
3
.
2
.
a
5.3.2.b
5
.
3
.
2
.
b
5.3.2.c
5
.
3
.
2
.
c
5.3.2.d
5
.
3
.
2
.
d
5.5.c
5
.
5
.
c
Source
S
o
u
r
c
e
Code
C
o
d
e
11.11
1
1
.
1
1
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
7
7
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
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
Files,
F
i
l
e
s
,
if
i
f
any,
a
n
y
,
are
a
r
e
produced
p
r
o
d
u
c
e
d
and
a
n
d
loaded
l
o
a
d
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
.
5.4.1.a
5
.
4
.
1
.
a
5.4.2.a
5
.
4
.
2
.
a
5.4.2.b
5
.
4
.
2
.
b
5.4.2.c
5
.
4
.
2
.
c
5.4.2.d
5
.
4
.
2
.
d
5.4.2.e
5
.
4
.
2
.
e
5.4.2.f
5
.
4
.
2
.
f
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
11.12
1
1
.
1
2
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
11.22
1
1
.
2
2
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
98
9
8
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
comply
c
o
m
p
l
y
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
.
6.3.1.a
6
.
3
.
1
.
a
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
2
2
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
accurate
a
c
c
u
r
a
t
e
and
a
n
d
consistent.
c
o
n
s
i
s
t
e
n
t
.
6.3.1.b
6
.
3
.
1
.
b
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
3
3
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
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
6.3.1.c
6
.
3
.
1
.
c
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
4
4
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
verifiable.
v
e
r
i
f
i
a
b
l
e
.
6.3.1.d
6
.
3
.
1
.
d
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
5
5
High-level
H
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
conform
c
o
n
f
o
r
m
to
t
o
standards.
s
t
a
n
d
a
r
d
s
.
6.3.1.e
6
.
3
.
1
.
e
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
6
6
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
traceable
t
r
a
c
e
a
b
l
e
to
t
o
system
s
y
s
t
e
m
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.3.1.f
6
.
3
.
1
.
f
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
7
7
Algorithms
A
l
g
o
r
i
t
h
m
s
are
a
r
e
accurate.
a
c
c
u
r
a
t
e
.
6.3.1.g
6
.
3
.
1
.
g
6.3.1
6
.
3
.
1
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
11.14
1
1
.
1
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
99
9
9
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
Low-level
L
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
comply
c
o
m
p
l
y
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
.
6.3.2.a
6
.
3
.
2
.
a
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
2
2
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
accurate
a
c
c
u
r
a
t
e
and
a
n
d
consistent.
c
o
n
s
i
s
t
e
n
t
.
6.3.2.b
6
.
3
.
2
.
b
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
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
are
a
r
e
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
6.3.2.c
6
.
3
.
2
.
c
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
4
4
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
verifiable.
v
e
r
i
f
i
a
b
l
e
.
6.3.2.d
6
.
3
.
2
.
d
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
5
5
Low-level
L
o
w
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
conform
c
o
n
f
o
r
m
to
t
o
standards.
s
t
a
n
d
a
r
d
s
.
6.3.2.e
6
.
3
.
2
.
e
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
6
6
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
traceable
t
r
a
c
e
a
b
l
e
to
t
o
high-
h
i
g
h
-
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.3.2.f
6
.
3
.
2
.
f
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
7
7
Algorithms
A
l
g
o
r
i
t
h
m
s
are
a
r
e
accurate.
a
c
c
u
r
a
t
e
.
6.3.2.g
6
.
3
.
2
.
g
6.3.2
6
.
3
.
2
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
11.14
1
1
.
1
4
8
8
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
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
high-
h
i
g
h
-
level
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.3.3.a
6
.
3
.
3
.
a
6.3.3
6
.
3
.
3
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
11.14
1
1
.
1
4
9
9
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
consistent.
c
o
n
s
i
s
t
e
n
t
.
6.3.3.b
6
.
3
.
3
.
b
6.3.3
6
.
3
.
3
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
11.14
1
1
.
1
4
10
1
0
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
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
6.3.3.c
6
.
3
.
3
.
c
6.3.3
6
.
3
.
3
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
11.14
1
1
.
1
4
11
1
1
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
verifiable.
v
e
r
i
f
i
a
b
l
e
.
6.3.3.d
6
.
3
.
3
.
d
6.3.3
6
.
3
.
3
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
11.14
1
1
.
1
4
12
1
2
Software
S
o
f
t
w
a
r
e
architecture
a
r
c
h
i
t
e
c
t
u
r
e
conforms
c
o
n
f
o
r
m
s
to
t
o
standards.
s
t
a
n
d
a
r
d
s
.
6.3.3.e
6
.
3
.
3
.
e
6.3.3
6
.
3
.
3
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
11.14
1
1
.
1
4
13
1
3
Software
S
o
f
t
w
a
r
e
partitioning
p
a
r
t
i
t
i
o
n
i
n
g
integrity
i
n
t
e
g
r
i
t
y
is
i
s
confirmed.
c
o
n
f
i
r
m
e
d
.
6.3.3.f
6
.
3
.
3
.
f
6.3.3
6
.
3
.
3
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
11.14
1
1
.
1
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
100
1
0
0
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
Source
S
o
u
r
c
e
Code
C
o
d
e
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.3.4.a
6
.
3
.
4
.
a
6.3.4
6
.
3
.
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
11.14
1
1
.
1
4
2
2
Source
S
o
u
r
c
e
Code
C
o
d
e
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
software
s
o
f
t
w
a
r
e
architecture.
a
r
c
h
i
t
e
c
t
u
r
e
.
6.3.4.b
6
.
3
.
4
.
b
6.3.4
6
.
3
.
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
11.14
1
1
.
1
4
3
3
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
verifiable.
v
e
r
i
f
i
a
b
l
e
.
6.3.4.c
6
.
3
.
4
.
c
6.3.4
6
.
3
.
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
11.14
1
1
.
1
4
4
4
Source
S
o
u
r
c
e
Code
C
o
d
e
conforms
c
o
n
f
o
r
m
s
to
t
o
standards.
s
t
a
n
d
a
r
d
s
.
6.3.4.d
6
.
3
.
4
.
d
6.3.4
6
.
3
.
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
11.14
1
1
.
1
4
5
5
Source
S
o
u
r
c
e
Code
C
o
d
e
is
i
s
traceable
t
r
a
c
e
a
b
l
e
to
t
o
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.3.4.e
6
.
3
.
4
.
e
6.3.4
6
.
3
.
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
11.14
1
1
.
1
4
6
6
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
consistent.
c
o
n
s
i
s
t
e
n
t
.
6.3.4.f
6
.
3
.
4
.
f
6.3.4
6
.
3
.
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
11.14
1
1
.
1
4
7
7
Output
O
u
t
p
u
t
of
o
f
software
s
o
f
t
w
a
r
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
and
a
n
d
correct.
c
o
r
r
e
c
t
.
6.3.5.a
6
.
3
.
5
.
a
6.3.5
6
.
3
.
5
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
11.14
1
1
.
1
4
8
8
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
is
i
s
correct
c
o
r
r
e
c
t
and
a
n
d
complete
c
o
m
p
l
e
t
e
6.6.a
6
.
6
.
a
6.6
6
.
6
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
11.13
1
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
Results
R
e
s
u
l
t
s
11.14
1
1
.
1
4
9
9
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.6.b
6
.
6
.
b
6.6
6
.
6
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
11.14
1
1
.
1
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
101
1
0
1
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
complies
c
o
m
p
l
i
e
s
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
.
6.4.a
6
.
4
.
a
6.4.2
6
.
4
.
2
6.4.2.1
6
.
4
.
2
.
1
6.4.3
6
.
4
.
3
6.5
6
.
5
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
11.13
1
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
Results
R
e
s
u
l
t
s
11.14
1
1
.
1
4
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
2
2
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
robust
r
o
b
u
s
t
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
.
6.4.b
6
.
4
.
b
6.4.2
6
.
4
.
2
6.4.2.2
6
.
4
.
2
.
2
6.4.3
6
.
4
.
3
6.5
6
.
5
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
11.13
1
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
Results
R
e
s
u
l
t
s
11.14
1
1
.
1
4
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
3
3
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
complies
c
o
m
p
l
i
e
s
with
w
i
t
h
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.4.c
6
.
4
.
c
6.4.2
6
.
4
.
2
6.4.2.1
6
.
4
.
2
.
1
6.4.3
6
.
4
.
3
6.5
6
.
5
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
11.13
1
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
Results
R
e
s
u
l
t
s
11.14
1
1
.
1
4
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
4
4
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
robust
r
o
b
u
s
t
with
w
i
t
h
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
6.4.d
6
.
4
.
d
6.4.2
6
.
4
.
2
6.4.2.2
6
.
4
.
2
.
2
6.4.3
6
.
4
.
3
6.5
6
.
5
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
11.13
1
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
Results
R
e
s
u
l
t
s
11.14
1
1
.
1
4
Trace
T
r
a
c
e
Data
D
a
t
a
11.21
1
1
.
2
1
5
5
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
compatible
c
o
m
p
a
t
i
b
l
e
with
w
i
t
h
target
t
a
r
g
e
t
computer.
c
o
m
p
u
t
e
r
.
6.4.e
6
.
4
.
e
6.4.1.a
6
.
4
.
1
.
a
6.4.3.a
6
.
4
.
3
.
a
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
11.13
1
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
Results
R
e
s
u
l
t
s
11.14
1
1
.
1
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
102
1
0
2
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
Test
T
e
s
t
procedures
p
r
o
c
e
d
u
r
e
s
are
a
r
e
correct.
c
o
r
r
e
c
t
.
6.4.5.b
6
.
4
.
5
.
b
6.4.5
6
.
4
.
5
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
11.14
1
1
.
1
4
2
2
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
discrepancies
d
i
s
c
r
e
p
a
n
c
i
e
s
explained.
e
x
p
l
a
i
n
e
d
.
6.4.5.c
6
.
4
.
5
.
c
6.4.5
6
.
4
.
5
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
11.14
1
1
.
1
4
3
3
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
high-level
h
i
g
h
-
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.a
6
.
4
.
4
.
a
6.4.4.1
6
.
4
.
4
.
1
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
11.14
1
1
.
1
4
4
4
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
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
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.b
6
.
4
.
4
.
b
6.4.4.1
6
.
4
.
4
.
1
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
11.14
1
1
.
1
4
5
5
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
structure
s
t
r
u
c
t
u
r
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
)
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.c
6
.
4
.
4
.
c
6.4.4.2.a
6
.
4
.
4
.
2
.
a
6.4.4.2.b
6
.
4
.
4
.
2
.
b
6.4.4.2.d
6
.
4
.
4
.
2
.
d
6.4.4.3
6
.
4
.
4
.
3
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
11.14
1
1
.
1
4
6
6
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
structure
s
t
r
u
c
t
u
r
e
(decision
(
d
e
c
i
s
i
o
n
coverage)
c
o
v
e
r
a
g
e
)
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.c
6
.
4
.
4
.
c
6.4.4.2.a
6
.
4
.
4
.
2
.
a
6.4.4.2.b
6
.
4
.
4
.
2
.
b
6.4.4.2.d
6
.
4
.
4
.
2
.
d
6.4.4.3
6
.
4
.
4
.
3
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
11.14
1
1
.
1
4
7
7
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
structure
s
t
r
u
c
t
u
r
e
(statement
(
s
t
a
t
e
m
e
n
t
coverage)
c
o
v
e
r
a
g
e
)
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.c
6
.
4
.
4
.
c
6.4.4.2.a
6
.
4
.
4
.
2
.
a
6.4.4.2.b
6
.
4
.
4
.
2
.
b
6.4.4.2.d
6
.
4
.
4
.
2
.
d
6.4.4.3
6
.
4
.
4
.
3
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
11.14
1
1
.
1
4
8
8
Test
T
e
s
t
coverage
c
o
v
e
r
a
g
e
of
o
f
software
s
o
f
t
w
a
r
e
structure
s
t
r
u
c
t
u
r
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
)
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.d
6
.
4
.
4
.
d
6.4.4.2.c
6
.
4
.
4
.
2
.
c
6.4.4.2.d
6
.
4
.
4
.
2
.
d
6.4.4.3
6
.
4
.
4
.
3
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
11.14
1
1
.
1
4
9
9
Verification
V
e
r
i
f
i
c
a
t
i
o
n
of
o
f
additional
a
d
d
i
t
i
o
n
a
l
code,
c
o
d
e
,
that
t
h
a
t
cannot
c
a
n
n
o
t
be
b
e
traced
t
r
a
c
e
d
to
t
o
Source
S
o
u
r
c
e
Code,
C
o
d
e
,
is
i
s
achieved.
a
c
h
i
e
v
e
d
.
6.4.4.c
6
.
4
.
4
.
c
6.4.4.2.b
6
.
4
.
4
.
2
.
b
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
11.14
1
1
.
1
4
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
103
1
0
3
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
items
i
t
e
m
s
are
a
r
e
identified.
i
d
e
n
t
i
f
i
e
d
.
7.1.a
7
.
1
.
a
7.2.1
7
.
2
.
1
SCM
S
C
M
Records
R
e
c
o
r
d
s
11.18
1
1
.
1
8
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
are
a
r
e
established.
e
s
t
a
b
l
i
s
h
e
d
.
7.1.b
7
.
1
.
b
7.2.2
7
.
2
.
2
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
11.16
1
1
.
1
6
SCM
S
C
M
Records
R
e
c
o
r
d
s
11.18
1
1
.
1
8
3
3
Problem
P
r
o
b
l
e
m
reporting,
r
e
p
o
r
t
i
n
g
,
change
c
h
a
n
g
e
control,
c
o
n
t
r
o
l
,
change
c
h
a
n
g
e
review,
r
e
v
i
e
w
,
and
a
n
d
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
are
a
r
e
established.
e
s
t
a
b
l
i
s
h
e
d
.
7.1.c
7
.
1
.
c
7.1.d
7
.
1
.
d
7.1.e
7
.
1
.
e
7.1.f
7
.
1
.
f
7.2.3
7
.
2
.
3
7.2.4
7
.
2
.
4
7.2.5
7
.
2
.
5
7.2.6
7
.
2
.
6
Problem
P
r
o
b
l
e
m
Reports
R
e
p
o
r
t
s
11.17
1
1
.
1
7
SCM
S
C
M
Records
R
e
c
o
r
d
s
11.18
1
1
.
1
8
4
4
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
are
a
r
e
established.
e
s
t
a
b
l
i
s
h
e
d
.
7.1.g
7
.
1
.
g
7.2.7
7
.
2
.
7
SCM
S
C
M
Records
R
e
c
o
r
d
s
11.18
1
1
.
1
8
5
5
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
established.
e
s
t
a
b
l
i
s
h
e
d
.
7.1.h
7
.
1
.
h
7.4
7
.
4
SCM
S
C
M
Records
R
e
c
o
r
d
s
11.18
1
1
.
1
8
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
c
o
n
t
r
o
l
is
i
s
established.
e
s
t
a
b
l
i
s
h
e
d
.
7.1.i
7
.
1
.
i
7.5
7
.
5
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
11.15
1
1
.
1
5
SCM
S
C
M
Records
R
e
c
o
r
d
s
11.18
1
1
.
1
8
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
104
1
0
4
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
1
1
Assurance
A
s
s
u
r
a
n
c
e
is
i
s
obtained
o
b
t
a
i
n
e
d
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
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
for
f
o
r
consistency.
c
o
n
s
i
s
t
e
n
c
y
.
8.1.a
8
.
1
.
a
8.2.b
8
.
2
.
b
8.2.h
8
.
2
.
h
8.2.i
8
.
2
.
i
SQA
S
Q
A
Records
R
e
c
o
r
d
s
11.19
1
1
.
1
9
2
2
Assurance
A
s
s
u
r
a
n
c
e
is
i
s
obtained
o
b
t
a
i
n
e
d
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
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
.
8.1.b
8
.
1
.
b
8.2.a
8
.
2
.
a
8.2.c
8
.
2
.
c
8.2.d
8
.
2
.
d
8.2.f
8
.
2
.
f
8.2.h
8
.
2
.
h
8.2.i
8
.
2
.
i
SQA
S
Q
A
Records
R
e
c
o
r
d
s
11.19
1
1
.
1
9
3
3
Assurance
A
s
s
u
r
a
n
c
e
is
i
s
obtained
o
b
t
a
i
n
e
d
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
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
standards.
s
t
a
n
d
a
r
d
s
.
8.1.b
8
.
1
.
b
8.2.a
8
.
2
.
a
8.2.c
8
.
2
.
c
8.2.d
8
.
2
.
d
8.2.f
8
.
2
.
f
8.2.h
8
.
2
.
h
8.2.i
8
.
2
.
i
SQA
S
Q
A
Records
R
e
c
o
r
d
s
11.19
1
1
.
1
9
4
4
Assurance
A
s
s
u
r
a
n
c
e
is
i
s
obtained
o
b
t
a
i
n
e
d
that
t
h
a
t
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
.
8.1.c
8
.
1
.
c
8.2.e
8
.
2
.
e
8.2.h
8
.
2
.
h
8.2.i
8
.
2
.
i
SQA
S
Q
A
Records
R
e
c
o
r
d
s
11.19
1
1
.
1
9
5
5
Assurance
A
s
s
u
r
a
n
c
e
is
i
s
obtained
o
b
t
a
i
n
e
d
that
t
h
a
t
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
conducted.
c
o
n
d
u
c
t
e
d
.
8.1.d
8
.
1
.
d
8.2.g
8
.
2
.
g
8.2.h
8
.
2
.
h
8.3
8
.
3
SQA
S
Q
A
Records
R
e
c
o
r
d
s
11.19
1
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}
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
105
1
0
5
1
1
2
2
3
3
Objective
O
b
j
e
c
t
i
v
e
Activity
A
c
t
i
v
i
t
y
Applicability
A
p
p
l
i
c
a
b
i
l
i
t
y
by
b
y
Software
S
o
f
t
w
a
r
e
Level
L
e
v
e
l
Output
O
u
t
p
u
t
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
Description
D
e
s
c
r
i
p
t
i
o
n
Ref
R
e
f
Ref
R
e
f
A
A
B
B
C
C
D
D
Data
D
a
t
a
Item
I
t
e
m
Ref
R
e
f
A
A
B
B
C
C
D
D
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
9.1.b
9
.
1
.
b
Plan
P
l
a
n
for
f
o
r
Software
S
o
f
t
w
a
r
e
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
and
a
n
d
the
t
h
e
9.a
9
.
a
11.1
1
1
.
1
9.1.c
9
.
1
.
c
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
authority
a
u
t
h
o
r
i
t
y
is
i
s
established.
e
s
t
a
b
l
i
s
h
e
d
.
The
T
h
e
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
is
i
s
proposed
p
r
o
p
o
s
e
d
and
a
n
d
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
is
i
s
obtained.
o
b
t
a
i
n
e
d
.
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
is
i
s
provided.
p
r
o
v
i
d
e
d
.
9.b
9
.
b
9.c
9
.
c
9.1.a
9
.
1
.
a
9.1.b
9
.
1
.
b
9.1.c
9
.
1
.
c
9.2.a
9
.
2
.
a
9.2.b
9
.
2
.
b
9.2.c
9
.
2
.
c
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
Accomplishment
A
c
c
o
m
p
l
i
s
h
m
e
n
t
Summary
S
u
m
m
a
r
y
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
11.1
1
1
.
1
11.20
1
1
.
2
0
11.16
1
1
.
1
6
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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}
107
1
0
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
T
E
R
M
S
Acronym
A
c
r
o
n
y
m
Meaning
M
e
a
n
i
n
g
ARP
A
R
P
Aerospace
A
e
r
o
s
p
a
c
e
Recommended
R
e
c
o
m
m
e
n
d
e
d
Practice
P
r
a
c
t
i
c
e
ATM
A
T
M
Air
A
i
r
Traffic
T
r
a
f
f
i
c
Management
M
a
n
a
g
e
m
e
n
t
CAST
C
A
S
T
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
Team
T
e
a
m
CC1
C
C
1
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
1
1
CC2
C
C
2
Control
C
o
n
t
r
o
l
Category
C
a
t
e
g
o
r
y
2
2
CNS
C
N
S
Communication,
C
o
m
m
u
n
i
c
a
t
i
o
n
,
Navigation
N
a
v
i
g
a
t
i
o
n
and
a
n
d
Surveillance
S
u
r
v
e
i
l
l
a
n
c
e
COTS
C
O
T
S
Commercial-Off-The-Shelf
C
o
m
m
e
r
c
i
a
l
-
O
f
f
-
T
h
e
-
S
h
e
l
f
CRC
C
R
C
Cyclic
C
y
c
l
i
c
Redundancy
R
e
d
u
n
d
a
n
c
y
Check
C
h
e
c
k
DO
D
O
Document
D
o
c
u
m
e
n
t
EASA
E
A
S
A
European
E
u
r
o
p
e
a
n
Aviation
A
v
i
a
t
i
o
n
Safety
S
a
f
e
t
y
Agency
A
g
e
n
c
y
EUROCAE
E
U
R
O
C
A
E
European
E
u
r
o
p
e
a
n
Organization
O
r
g
a
n
i
z
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
IDAL
I
D
A
L
Item
I
t
e
m
Development
D
e
v
e
l
o
p
m
e
n
t
Assurance
A
s
s
u
r
a
n
c
e
Level
L
e
v
e
l
I/O
I
/
O
Input/Output
I
n
p
u
t
/
O
u
t
p
u
t
MC/DC
M
C
/
D
C
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
PMC
P
M
C
Program
P
r
o
g
r
a
m
Management
M
a
n
a
g
e
m
e
n
t
Committee
C
o
m
m
i
t
t
e
e
PSAC
P
S
A
C
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
RTCA
R
T
C
A
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
SAE
S
A
E
Society
S
o
c
i
e
t
y
of
o
f
Automotive
A
u
t
o
m
o
t
i
v
e
Engineers
E
n
g
i
n
e
e
r
s
SC
S
C
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
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
SDP
S
D
P
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
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
108
1
0
8
Acronym
A
c
r
o
n
y
m
Meaning
M
e
a
n
i
n
g
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
SVP
S
V
P
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
SW
S
W
Software
S
o
f
t
w
a
r
e
TOR
T
O
R
Terms
T
e
r
m
s
of
o
f
Reference
R
e
f
e
r
e
n
c
e
TQL
T
Q
L
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Level
L
e
v
e
l
U.S.A.
U
.
S
.
A
.
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
WG
W
G
Working
W
o
r
k
i
n
g
Group
G
r
o
u
p
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
GLOSSARY
G
L
O
S
S
A
R
Y
109
1
0
9
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
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
.
Activity
A
c
t
i
v
i
t
y
–
–
Tasks
T
a
s
k
s
that
t
h
a
t
provide
p
r
o
v
i
d
e
a
a
means
m
e
a
n
s
of
o
f
meeting
m
e
e
t
i
n
g
the
t
h
e
objectives.
o
b
j
e
c
t
i
v
e
s
.
Aeronautical
A
e
r
o
n
a
u
t
i
c
a
l
data
d
a
t
a
–
–
Data
D
a
t
a
used
u
s
e
d
for
f
o
r
aeronautical
a
e
r
o
n
a
u
t
i
c
a
l
applications
a
p
p
l
i
c
a
t
i
o
n
s
such
s
u
c
h
as
a
s
navigation,
n
a
v
i
g
a
t
i
o
n
,
flight
f
l
i
g
h
t
planning,
p
l
a
n
n
i
n
g
,
flight
f
l
i
g
h
t
simulators,
s
i
m
u
l
a
t
o
r
s
,
terrain
t
e
r
r
a
i
n
awareness,
a
w
a
r
e
n
e
s
s
,
and
a
n
d
other
o
t
h
e
r
purposes.
p
u
r
p
o
s
e
s
.
Airborne
A
i
r
b
o
r
n
e
–
–
A
A
qualifier
q
u
a
l
i
f
i
e
r
used
u
s
e
d
to
t
o
denote
d
e
n
o
t
e
software,
s
o
f
t
w
a
r
e
,
equipment,
e
q
u
i
p
m
e
n
t
,
or
o
r
systems
s
y
s
t
e
m
s
onboard
o
n
b
o
a
r
d
an
a
n
aircraft.
a
i
r
c
r
a
f
t
.
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
give
g
i
v
e
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
.
Alternative
A
l
t
e
r
n
a
t
i
v
e
method
m
e
t
h
o
d
–
–
Different
D
i
f
f
e
r
e
n
t
approach
a
p
p
r
o
a
c
h
to
t
o
satisfy
s
a
t
i
s
f
y
one
o
n
e
or
o
r
more
m
o
r
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
.
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
giving
g
i
v
i
n
g
formal
f
o
r
m
a
l
recognition
r
e
c
o
g
n
i
t
i
o
n
or
o
r
official
o
f
f
i
c
i
a
l
sanction.
s
a
n
c
t
i
o
n
.
Approved
A
p
p
r
o
v
e
d
source
s
o
u
r
c
e
–
–
The
T
h
e
location
l
o
c
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
data
d
a
t
a
to
t
o
be
b
e
retrieved
r
e
t
r
i
e
v
e
d
is
i
s
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
Configuration
C
o
n
f
i
g
u
r
a
t
i
o
n
Index.
I
n
d
e
x
.
The
T
h
e
"approved
"
a
p
p
r
o
v
e
d
source"
s
o
u
r
c
e
"
could
c
o
u
l
d
be
b
e
a
a
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
library,
l
i
b
r
a
r
y
,
an
a
n
electronic
e
l
e
c
t
r
o
n
i
c
archive,
a
r
c
h
i
v
e
,
or
o
r
an
a
n
organization
o
r
g
a
n
i
z
a
t
i
o
n
other
o
t
h
e
r
than
t
h
a
n
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
.
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
.
Autocode
A
u
t
o
c
o
d
e
generator
g
e
n
e
r
a
t
o
r
–
–
A
A
coding
c
o
d
i
n
g
tool
t
o
o
l
that
t
h
a
t
automatically
a
u
t
o
m
a
t
i
c
a
l
l
y
produces
p
r
o
d
u
c
e
s
Source
S
o
u
r
c
e
Code
C
o
d
e
or
o
r
object
o
b
j
e
c
t
code
c
o
d
e
from
f
r
o
m
low-level
l
o
w
-
l
e
v
e
l
requirements.
r
e
q
u
i
r
e
m
e
n
t
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
.
Boolean
B
o
o
l
e
a
n
expression
e
x
p
r
e
s
s
i
o
n
–
–
An
A
n
expression
e
x
p
r
e
s
s
i
o
n
that
t
h
a
t
results
r
e
s
u
l
t
s
in
i
n
a
a
TRUE
T
R
U
E
or
o
r
FALSE
F
A
L
S
E
value.
v
a
l
u
e
.
Boolean
B
o
o
l
e
a
n
operator
o
p
e
r
a
t
o
r
–
–
An
A
n
operator
o
p
e
r
a
t
o
r
with
w
i
t
h
Boolean
B
o
o
l
e
a
n
operands
o
p
e
r
a
n
d
s
that
t
h
a
t
yields
y
i
e
l
d
s
a
a
Boolean
B
o
o
l
e
a
n
result.
r
e
s
u
l
t
.
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
requirements
r
e
q
u
i
r
e
m
e
n
t
s
applicable
a
p
p
l
i
c
a
b
l
e
to
t
o
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
110
1
1
0
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
requirements
r
e
q
u
i
r
e
m
e
n
t
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
authority
a
u
t
h
o
r
i
t
y
–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
,
country,
c
o
u
n
t
r
y
,
or
o
r
other
o
t
h
e
r
relevant
r
e
l
e
v
a
n
t
body,
b
o
d
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
or
o
r
approval
a
p
p
r
o
v
a
l
of
o
f
a
a
product
p
r
o
d
u
c
t
in
i
n
accordance
a
c
c
o
r
d
a
n
c
e
with
w
i
t
h
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Note
N
o
t
e
1:
1
:
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
,
propeller
p
r
o
p
e
l
l
e
r
or,
o
r
,
by
b
y
region,
r
e
g
i
o
n
,
auxiliary
a
u
x
i
l
i
a
r
y
power
p
o
w
e
r
unit
u
n
i
t
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
.
Note
N
o
t
e
2:
2
:
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
use
u
s
e
a
a
system
s
y
s
t
e
m
under
u
n
d
e
r
which
w
h
i
c
h
the
t
h
e
actual
a
c
t
u
a
l
determinations
d
e
t
e
r
m
i
n
a
t
i
o
n
s
of
o
f
the
t
h
e
compliance
c
o
m
p
l
i
a
n
c
e
can
c
a
n
be
b
e
made
m
a
d
e
by
b
y
an
a
n
approved
a
p
p
r
o
v
e
d
design
d
e
s
i
g
n
organization
o
r
g
a
n
i
z
a
t
i
o
n
or
o
r
by
b
y
authorized
a
u
t
h
o
r
i
z
e
d
individuals.
i
n
d
i
v
i
d
u
a
l
s
.
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
.
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
process
p
r
o
c
e
s
s
that
t
h
a
t
establishes
e
s
t
a
b
l
i
s
h
e
s
communication,
c
o
m
m
u
n
i
c
a
t
i
o
n
,
understanding,
u
n
d
e
r
s
t
a
n
d
i
n
g
,
and
a
n
d
agreements
a
g
r
e
e
m
e
n
t
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
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
.
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
documents.
d
o
c
u
m
e
n
t
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-Off-The-Shelf
C
o
m
m
e
r
c
i
a
l
-
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
.
Compacted
C
o
m
p
a
c
t
e
d
expressions
e
x
p
r
e
s
s
i
o
n
s
–
–
Representations
R
e
p
r
e
s
e
n
t
a
t
i
o
n
s
of
o
f
Source
S
o
u
r
c
e
Code
C
o
d
e
where
w
h
e
r
e
many
m
a
n
y
constructs
c
o
n
s
t
r
u
c
t
s
are
a
r
e
combined
c
o
m
b
i
n
e
d
into
i
n
t
o
a
a
single
s
i
n
g
l
e
expression.
e
x
p
r
e
s
s
i
o
n
.
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
that
t
h
a
t
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
except
e
x
c
e
p
t
for
f
o
r
the
t
h
e
unary
u
n
a
r
y
operator
o
p
e
r
a
t
o
r
(NOT).
(
N
O
T
)
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
111
1
1
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
–
–
(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
(a)
(
a
)
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
;
(b)
(
b
)
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
;
(c)
(
c
)
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
Problem
P
r
o
b
l
e
m
Reports;
R
e
p
o
r
t
s
;
and
a
n
d
(d)
(
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
category
c
a
t
e
g
o
r
y
–
–
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
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
two
t
w
o
categories,
c
a
t
e
g
o
r
i
e
s
,
CC1
C
C
1
and
a
n
d
CC2,
C
C
2
,
define
d
e
f
i
n
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
management
m
a
n
a
g
e
m
e
n
t
processes
p
r
o
c
e
s
s
e
s
and
a
n
d
activities
a
c
t
i
v
i
t
i
e
s
applied
a
p
p
l
i
e
d
to
t
o
control
c
o
n
t
r
o
l
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
.
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
.
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
.
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
.
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
)
that
t
h
a
t
is
i
s
traceable
t
r
a
c
e
a
b
l
e
to
t
o
a
a
requirement
r
e
q
u
i
r
e
m
e
n
t
and,
a
n
d
,
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
such
s
u
c
h
as
a
s
unused
u
n
u
s
e
d
legacy
l
e
g
a
c
y
code,
c
o
d
e
,
unused
u
n
u
s
e
d
library
l
i
b
r
a
r
y
functions,
f
u
n
c
t
i
o
n
s
,
or
o
r
future
f
u
t
u
r
e
growth
g
r
o
w
t
h
code;
c
o
d
e
;
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
.
The
T
h
e
following
f
o
l
l
o
w
i
n
g
examples
e
x
a
m
p
l
e
s
are
a
r
e
often
o
f
t
e
n
mistakenly
m
i
s
t
a
k
e
n
l
y
categorized
c
a
t
e
g
o
r
i
z
e
d
as
a
s
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
but
b
u
t
should
s
h
o
u
l
d
be
b
e
identified
i
d
e
n
t
i
f
i
e
d
as
a
s
required
r
e
q
u
i
r
e
d
for
f
o
r
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
design/requirements:
d
e
s
i
g
n
/
r
e
q
u
i
r
e
m
e
n
t
s
:
defensive
d
e
f
e
n
s
i
v
e
programming
p
r
o
g
r
a
m
m
i
n
g
structures
s
t
r
u
c
t
u
r
e
s
inserted
i
n
s
e
r
t
e
d
for
f
o
r
robustness,
r
o
b
u
s
t
n
e
s
s
,
including
i
n
c
l
u
d
i
n
g
compiler-inserted
c
o
m
p
i
l
e
r
-
i
n
s
e
r
t
e
d
object
o
b
j
e
c
t
code
c
o
d
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
112
1
1
2
for
f
o
r
range
r
a
n
g
e
and
a
n
d
array
a
r
r
a
y
index
i
n
d
e
x
checks,
c
h
e
c
k
s
,
error
e
r
r
o
r
or
o
r
exception
e
x
c
e
p
t
i
o
n
handling
h
a
n
d
l
i
n
g
routines,
r
o
u
t
i
n
e
s
,
bounds
b
o
u
n
d
s
and
a
n
d
reasonableness
r
e
a
s
o
n
a
b
l
e
n
e
s
s
checking,
c
h
e
c
k
i
n
g
,
queuing
q
u
e
u
i
n
g
controls,
c
o
n
t
r
o
l
s
,
and
a
n
d
time
t
i
m
e
stamps.
s
t
a
m
p
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
exists
e
x
i
s
t
s
as
a
s
a
a
result
r
e
s
u
l
t
of
o
f
a
a
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
error
e
r
r
o
r
but
b
u
t
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
any
a
n
y
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
.
It
I
t
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
.
The
T
h
e
following
f
o
l
l
o
w
i
n
g
exceptions
e
x
c
e
p
t
i
o
n
s
are
a
r
e
often
o
f
t
e
n
mistakenly
m
i
s
t
a
k
e
n
l
y
categorized
c
a
t
e
g
o
r
i
z
e
d
as
a
s
dead
d
e
a
d
code
c
o
d
e
but
b
u
t
are
a
r
e
necessary
n
e
c
e
s
s
a
r
y
for
f
o
r
implementation
i
m
p
l
e
m
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
requirements/design:
r
e
q
u
i
r
e
m
e
n
t
s
/
d
e
s
i
g
n
:
embedded
e
m
b
e
d
d
e
d
identifiers,
i
d
e
n
t
i
f
i
e
r
s
,
defensive
d
e
f
e
n
s
i
v
e
programming
p
r
o
g
r
a
m
m
i
n
g
structures
s
t
r
u
c
t
u
r
e
s
to
t
o
improve
i
m
p
r
o
v
e
robustness,
r
o
b
u
s
t
n
e
s
s
,
and
a
n
d
deactivated
d
e
a
c
t
i
v
a
t
e
d
code
c
o
d
e
such
s
u
c
h
as
a
s
unused
u
n
u
s
e
d
library
l
i
b
r
a
r
y
functions.
f
u
n
c
t
i
o
n
s
.
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
.
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
–
–
Requirements
R
e
q
u
i
r
e
m
e
n
t
s
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
which
w
h
i
c
h
(a)
(
a
)
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
,
and/or
a
n
d
/
o
r
(b)
(
b
)
specify
s
p
e
c
i
f
y
behavior
b
e
h
a
v
i
o
r
beyond
b
e
y
o
n
d
that
t
h
a
t
specified
s
p
e
c
i
f
i
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
or
o
r
the
t
h
e
higher
h
i
g
h
e
r
level
l
e
v
e
l
software
s
o
f
t
w
a
r
e
requirements.
r
e
q
u
i
r
e
m
e
n
t
s
.
Embedded
E
m
b
e
d
d
e
d
identifier
i
d
e
n
t
i
f
i
e
r
–
–
Identification
I
d
e
n
t
i
f
i
c
a
t
i
o
n
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
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
creation
c
r
e
a
t
i
o
n
date,
d
a
t
e
,
part
p
a
r
t
number,
n
u
m
b
e
r
,
linker
l
i
n
k
e
r
integrity
i
n
t
e
g
r
i
t
y
verification
v
e
r
i
f
i
c
a
t
i
o
n
checksum
c
h
e
c
k
s
u
m
or
o
r
cyclic
c
y
c
l
i
c
redundancy
r
e
d
u
n
d
a
n
c
y
check
c
h
e
c
k
(CRC),
(
C
R
C
)
,
or
o
r
version
v
e
r
s
i
o
n
identification,
i
d
e
n
t
i
f
i
c
a
t
i
o
n
,
included
i
n
c
l
u
d
e
d
in
i
n
the
t
h
e
target
t
a
r
g
e
t
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code.
C
o
d
e
.
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
.
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
–
–
Measure
M
e
a
s
u
r
e
of
o
f
the
t
h
e
numerical
n
u
m
e
r
i
c
a
l
precision
p
r
e
c
i
s
i
o
n
resulting
r
e
s
u
l
t
i
n
g
from
f
r
o
m
computations
c
o
m
p
u
t
a
t
i
o
n
s
through
t
h
r
o
u
g
h
the
t
h
e
integrated
i
n
t
e
g
r
a
t
e
d
system.
s
y
s
t
e
m
.
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
.
Equivalent
E
q
u
i
v
a
l
e
n
t
safety
s
a
f
e
t
y
–
–
Level
L
e
v
e
l
of
o
f
safety
s
a
f
e
t
y
achieved
a
c
h
i
e
v
e
d
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
to
t
o
satisfy
s
a
t
i
s
f
y
both
b
o
t
h
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
and
a
n
d
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
.
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
.
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
–
–
A
A
form
f
o
r
m
of
o
f
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
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
,
a
a
compiled,
c
o
m
p
i
l
e
d
,
assembled,
a
s
s
e
m
b
l
e
d
,
and
a
n
d
linked
l
i
n
k
e
d
binary
b
i
n
a
r
y
image
i
m
a
g
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
target
t
a
r
g
e
t
computing
c
o
m
p
u
t
i
n
g
hardware.
h
a
r
d
w
a
r
e
.
Extraneous
E
x
t
r
a
n
e
o
u
s
code
c
o
d
e
–
–
Code
C
o
d
e
(or
(
o
r
data)
d
a
t
a
)
that
t
h
a
t
is
i
s
not
n
o
t
traceable
t
r
a
c
e
a
b
l
e
to
t
o
any
a
n
y
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
example
e
x
a
m
p
l
e
of
o
f
extraneous
e
x
t
r
a
n
e
o
u
s
code
c
o
d
e
is
i
s
legacy
l
e
g
a
c
y
code
c
o
d
e
that
t
h
a
t
was
w
a
s
incorrectly
i
n
c
o
r
r
e
c
t
l
y
retained
r
e
t
a
i
n
e
d
although
a
l
t
h
o
u
g
h
its
i
t
s
requirements
r
e
q
u
i
r
e
m
e
n
t
s
and
a
n
d
test
t
e
s
t
cases
c
a
s
e
s
were
w
e
r
e
removed.
r
e
m
o
v
e
d
.
Another
A
n
o
t
h
e
r
example
e
x
a
m
p
l
e
of
o
f
extraneous
e
x
t
r
a
n
e
o
u
s
code
c
o
d
e
is
i
s
dead
d
e
a
d
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
113
1
1
3
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
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
.
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
.
A
A
formal
f
o
r
m
a
l
method
m
e
t
h
o
d
is
i
s
a
a
formal
f
o
r
m
a
l
analysis
a
n
a
l
y
s
i
s
carried
c
a
r
r
i
e
d
out
o
u
t
on
o
n
a
a
formal
f
o
r
m
a
l
model.
m
o
d
e
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
–
–
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
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
.
Integrity
I
n
t
e
g
r
i
t
y
–
–
An
A
n
attribute
a
t
t
r
i
b
u
t
e
of
o
f
the
t
h
e
system
s
y
s
t
e
m
or
o
r
an
a
n
item
i
t
e
m
indicating
i
n
d
i
c
a
t
i
n
g
that
t
h
a
t
it
i
t
can
c
a
n
be
b
e
relied
r
e
l
i
e
d
upon
u
p
o
n
to
t
o
work
w
o
r
k
correctly
c
o
r
r
e
c
t
l
y
on
o
n
demand.
d
e
m
a
n
d
.
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
developed
d
e
v
e
l
o
p
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
.
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
,
engine,
e
n
g
i
n
e
,
propeller,
p
r
o
p
e
l
l
e
r
,
or,
o
r
,
by
b
y
region,
r
e
g
i
o
n
,
auxiliary
a
u
x
i
l
i
a
r
y
power
p
o
w
e
r
unit.
u
n
i
t
.
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
114
1
1
4
Media
M
e
d
i
a
–
–
Devices
D
e
v
i
c
e
s
or
o
r
materials
m
a
t
e
r
i
a
l
s
which
w
h
i
c
h
act
a
c
t
as
a
s
a
a
means
m
e
a
n
s
of
o
f
transferring
t
r
a
n
s
f
e
r
r
i
n
g
or
o
r
storing
s
t
o
r
i
n
g
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
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
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
:
(1)
(
1
)
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
,
or
o
r
(2)
(
2
)
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
that
t
h
a
t
could
c
o
u
l
d
affect
a
f
f
e
c
t
the
t
h
e
outcome.
o
u
t
c
o
m
e
.
Monitoring
M
o
n
i
t
o
r
i
n
g
–
–
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
–
–
Two
T
w
o
or
o
r
more
m
o
r
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
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
,
but
b
u
t
are
a
r
e
intentionally
i
n
t
e
n
t
i
o
n
a
l
l
y
different
d
i
f
f
e
r
e
n
t
from
f
r
o
m
one
o
n
e
another.
a
n
o
t
h
e
r
.
Example
E
x
a
m
p
l
e
approaches
a
p
p
r
o
a
c
h
e
s
include
i
n
c
l
u
d
e
the
t
h
e
use
u
s
e
of
o
f
separate
s
e
p
a
r
a
t
e
development
d
e
v
e
l
o
p
m
e
n
t
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
or
o
r
the
t
h
e
use
u
s
e
of
o
f
different
d
i
f
f
e
r
e
n
t
development
d
e
v
e
l
o
p
m
e
n
t
techniques.
t
e
c
h
n
i
q
u
e
s
.
Common
C
o
m
m
o
n
mode
m
o
d
e
errors
e
r
r
o
r
s
may
m
a
y
be
b
e
minimized
m
i
n
i
m
i
z
e
d
by
b
y
using
u
s
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
techniques.
t
e
c
h
n
i
q
u
e
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
.
Objective
O
b
j
e
c
t
i
v
e
–
–
When
W
h
e
n
this
t
h
i
s
document
d
o
c
u
m
e
n
t
is
i
s
identified
i
d
e
n
t
i
f
i
e
d
as
a
s
a
a
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
to
t
o
the
t
h
e
regulations,
r
e
g
u
l
a
t
i
o
n
s
,
the
t
h
e
objectives
o
b
j
e
c
t
i
v
e
s
are
a
r
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
that
t
h
a
t
should
s
h
o
u
l
d
be
b
e
met
m
e
t
to
t
o
demonstrate
d
e
m
o
n
s
t
r
a
t
e
compliance.
c
o
m
p
l
i
a
n
c
e
.
Parameter
P
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
–
–
A
A
set
s
e
t
of
o
f
data
d
a
t
a
that,
t
h
a
t
,
when
w
h
e
n
in
i
n
the
t
h
e
form
f
o
r
m
of
o
f
a
a
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File,
F
i
l
e
,
influence
i
n
f
l
u
e
n
c
e
the
t
h
e
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
without
w
i
t
h
o
u
t
modifying
m
o
d
i
f
y
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
and
a
n
d
that
t
h
a
t
is
i
s
managed
m
a
n
a
g
e
d
as
a
s
a
a
separate
s
e
p
a
r
a
t
e
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
item.
i
t
e
m
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
databases
d
a
t
a
b
a
s
e
s
and
a
n
d
configuration
c
o
n
f
i
g
u
r
a
t
i
o
n
tables.
t
a
b
l
e
s
.
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
–
–
The
T
h
e
representation
r
e
p
r
e
s
e
n
t
a
t
i
o
n
of
o
f
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
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
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
.
A
A
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
is
i
s
an
a
n
instantiation
i
n
s
t
a
n
t
i
a
t
i
o
n
of
o
f
the
t
h
e
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
item
i
t
e
m
containing
c
o
n
t
a
i
n
i
n
g
defined
d
e
f
i
n
e
d
values
v
a
l
u
e
s
for
f
o
r
each
e
a
c
h
data
d
a
t
a
element.
e
l
e
m
e
n
t
.
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
.
Partitioning
P
a
r
t
i
t
i
o
n
i
n
g
–
–
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
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
115
1
1
5
Patch
P
a
t
c
h
–
–
Modification
M
o
d
i
f
i
c
a
t
i
o
n
to
t
o
Executable
E
x
e
c
u
t
a
b
l
e
Object
O
b
j
e
c
t
Code
C
o
d
e
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-assembling,
r
e
-
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
embedded
e
m
b
e
d
d
e
d
identifiers.
i
d
e
n
t
i
f
i
e
r
s
.
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
–
–
Software
S
o
f
t
w
a
r
e
already
a
l
r
e
a
d
y
developed
d
e
v
e
l
o
p
e
d
for
f
o
r
use.
u
s
e
.
This
T
h
i
s
encompasses
e
n
c
o
m
p
a
s
s
e
s
a
a
wide
w
i
d
e
range
r
a
n
g
e
of
o
f
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
through
t
h
r
o
u
g
h
software
s
o
f
t
w
a
r
e
developed
d
e
v
e
l
o
p
e
d
to
t
o
previous
p
r
e
v
i
o
u
s
or
o
r
current
c
u
r
r
e
n
t
software
s
o
f
t
w
a
r
e
guidance.
g
u
i
d
a
n
c
e
.
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
.
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
.
Reverification
R
e
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
modification
m
o
d
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
correction
c
o
r
r
e
c
t
i
o
n
of
o
f
errors
e
r
r
o
r
s
or
o
r
the
t
h
e
introduction
i
n
t
r
o
d
u
c
t
i
o
n
of
o
f
new
n
e
w
or
o
r
additional
a
d
d
i
t
i
o
n
a
l
functionality,
f
u
n
c
t
i
o
n
a
l
i
t
y
,
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
.
Reverse
R
e
v
e
r
s
e
engineering
e
n
g
i
n
e
e
r
i
n
g
–
–
The
T
h
e
process
p
r
o
c
e
s
s
of
o
f
developing
d
e
v
e
l
o
p
i
n
g
higher
h
i
g
h
e
r
level
l
e
v
e
l
software
s
o
f
t
w
a
r
e
data
d
a
t
a
from
f
r
o
m
existing
e
x
i
s
t
i
n
g
software
s
o
f
t
w
a
r
e
data.
d
a
t
a
.
Examples
E
x
a
m
p
l
e
s
include
i
n
c
l
u
d
e
developing
d
e
v
e
l
o
p
i
n
g
Source
S
o
u
r
c
e
Code
C
o
d
e
from
f
r
o
m
object
o
b
j
e
c
t
code
c
o
d
e
or
o
r
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
developing
d
e
v
e
l
o
p
i
n
g
high
h
i
g
h
level
l
e
v
e
l
requirements
r
e
q
u
i
r
e
m
e
n
t
s
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
.
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
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
.
Safety
S
a
f
e
t
y
monitoring
m
o
n
i
t
o
r
i
n
g
–
–
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
that
t
h
a
t
would
w
o
u
l
d
result
r
e
s
u
l
t
in
i
n
a
a
failure
f
a
i
l
u
r
e
condition.
c
o
n
d
i
t
i
o
n
.
Service
S
e
r
v
i
c
e
experience
e
x
p
e
r
i
e
n
c
e
–
–
Intervals
I
n
t
e
r
v
a
l
s
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
relevant
r
e
l
e
v
a
n
t
and
a
n
d
controlled
c
o
n
t
r
o
l
l
e
d
environment,
e
n
v
i
r
o
n
m
e
n
t
,
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
.
Service
S
e
r
v
i
c
e
history
h
i
s
t
o
r
y
data
d
a
t
a
–Data
–
D
a
t
a
collected
c
o
l
l
e
c
t
e
d
during
d
u
r
i
n
g
the
t
h
e
service
s
e
r
v
i
c
e
history
h
i
s
t
o
r
y
period.
p
e
r
i
o
d
.
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
that
t
h
a
t
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
.
Single
S
i
n
g
l
e
event
e
v
e
n
t
upset
u
p
s
e
t
–
–
Random
R
a
n
d
o
m
bit
b
i
t
flip
f
l
i
p
in
i
n
data
d
a
t
a
that
t
h
a
t
can
c
a
n
occur
o
c
c
u
r
in
i
n
hardware.
h
a
r
d
w
a
r
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
.
Software
S
o
f
t
w
a
r
e
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
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
software
s
o
f
t
w
a
r
e
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
116
1
1
6
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
conformity
c
o
n
f
o
r
m
i
t
y
review
r
e
v
i
e
w
–
–
A
A
review,
r
e
v
i
e
w
,
typically
t
y
p
i
c
a
l
l
y
conducted
c
o
n
d
u
c
t
e
d
at
a
t
the
t
h
e
end
e
n
d
of
o
f
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
,
for
f
o
r
the
t
h
e
purpose
p
u
r
p
o
s
e
of
o
f
assuring
a
s
s
u
r
i
n
g
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
.
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
–Standards
–
S
t
a
n
d
a
r
d
s
which
w
h
i
c
h
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
.
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
level
l
e
v
e
l
–
–
The
T
h
e
designation
d
e
s
i
g
n
a
t
i
o
n
that
t
h
a
t
is
i
s
assigned
a
s
s
i
g
n
e
d
to
t
o
a
a
software
s
o
f
t
w
a
r
e
component
c
o
m
p
o
n
e
n
t
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
establishes
e
s
t
a
b
l
i
s
h
e
s
the
t
h
e
rigor
r
i
g
o
r
necessary
n
e
c
e
s
s
a
r
y
to
t
o
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
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
Note:
N
o
t
e
:
Other
O
t
h
e
r
industry
i
n
d
u
s
t
r
y
documents
d
o
c
u
m
e
n
t
s
may
m
a
y
use
u
s
e
a
a
different
d
i
f
f
e
r
e
n
t
term
t
e
r
m
for
f
o
r
the
t
h
e
designation
d
e
s
i
g
n
a
t
i
o
n
resulting
r
e
s
u
l
t
i
n
g
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
.
One
O
n
e
example
e
x
a
m
p
l
e
is
i
s
the
t
h
e
term
t
e
r
m
“item
“
i
t
e
m
development
d
e
v
e
l
o
p
m
e
n
t
assurance
a
s
s
u
r
a
n
c
e
level”
l
e
v
e
l
”
(IDAL),
(
I
D
A
L
)
,
which
w
h
i
c
h
for
f
o
r
software
s
o
f
t
w
a
r
e
is
i
s
synonymous
s
y
n
o
n
y
m
o
u
s
with
w
i
t
h
the
t
h
e
term
t
e
r
m
“software
“
s
o
f
t
w
a
r
e
level.”
l
e
v
e
l
.
”
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
,
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-
c
r
o
s
s
-
coupling
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
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
.
117
1
1
7
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
.
Note:
N
o
t
e
:
Statement
S
t
a
t
e
m
e
n
t
is
i
s
as
a
s
defined
d
e
f
i
n
e
d
by
b
y
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
.
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
–
–
An
A
n
evaluation
e
v
a
l
u
a
t
i
o
n
of
o
f
the
t
h
e
code
c
o
d
e
structure,
s
t
r
u
c
t
u
r
e
,
including
i
n
c
l
u
d
i
n
g
interfaces,
i
n
t
e
r
f
a
c
e
s
,
exercised
e
x
e
r
c
i
s
e
d
during
d
u
r
i
n
g
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
.
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
.
Supplement
S
u
p
p
l
e
m
e
n
t
–
–
Guidance
G
u
i
d
a
n
c
e
used
u
s
e
d
in
i
n
conjunction
c
o
n
j
u
n
c
t
i
o
n
with
w
i
t
h
this
t
h
i
s
document
d
o
c
u
m
e
n
t
that
t
h
a
t
addresses
a
d
d
r
e
s
s
e
s
the
t
h
e
unique
u
n
i
q
u
e
nature
n
a
t
u
r
e
of
o
f
a
a
specific
s
p
e
c
i
f
i
c
approach,
a
p
p
r
o
a
c
h
,
method,
m
e
t
h
o
d
,
or
o
r
technique.
t
e
c
h
n
i
q
u
e
.
A
A
supplement
s
u
p
p
l
e
m
e
n
t
adds,
a
d
d
s
,
deletes,
d
e
l
e
t
e
s
,
or
o
r
otherwise
o
t
h
e
r
w
i
s
e
modifies:
m
o
d
i
f
i
e
s
:
objectives,
o
b
j
e
c
t
i
v
e
s
,
activities,
a
c
t
i
v
i
t
i
e
s
,
explanatory
e
x
p
l
a
n
a
t
o
r
y
text,
t
e
x
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
in
i
n
this
t
h
i
s
document.
d
o
c
u
m
e
n
t
.
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
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
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
.
The
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
.
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
.
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
.
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
.
Trace
T
r
a
c
e
data
d
a
t
a
–
–
Data
D
a
t
a
providing
p
r
o
v
i
d
i
n
g
evidence
e
v
i
d
e
n
c
e
of
o
f
traceability
t
r
a
c
e
a
b
i
l
i
t
y
of
o
f
development
d
e
v
e
l
o
p
m
e
n
t
and
a
n
d
verification
v
e
r
i
f
i
c
a
t
i
o
n
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
data
d
a
t
a
without
w
i
t
h
o
u
t
implying
i
m
p
l
y
i
n
g
the
t
h
e
production
p
r
o
d
u
c
t
i
o
n
of
o
f
any
a
n
y
particular
p
a
r
t
i
c
u
l
a
r
artifact.
a
r
t
i
f
a
c
t
.
Trace
T
r
a
c
e
data
d
a
t
a
may
m
a
y
show
s
h
o
w
linkages,
l
i
n
k
a
g
e
s
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
through
t
h
r
o
u
g
h
the
t
h
e
use
u
s
e
of
o
f
naming
n
a
m
i
n
g
conventions
c
o
n
v
e
n
t
i
o
n
s
or
o
r
through
t
h
r
o
u
g
h
the
t
h
e
use
u
s
e
of
o
f
references
r
e
f
e
r
e
n
c
e
s
or
o
r
pointers
p
o
i
n
t
e
r
s
either
e
i
t
h
e
r
embedded
e
m
b
e
d
d
e
d
in
i
n
or
o
r
external
e
x
t
e
r
n
a
l
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
.
Traceability
T
r
a
c
e
a
b
i
l
i
t
y
–
–
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
granularity=word tetml={elements={line} glyphdetails={all}} contentanalysis={punctuationbreaks=false dehyphenate=false shadowdetect=false} layoutanalysis={tabledetect=0 layoutdetect=3} structureanalysis={list=true}
118
1
1
8
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
.
Type
T
y
p
e
design
d
e
s
i
g
n
–
–
For
F
o
r
the
t
h
e
purposes
p
u
r
p
o
s
e
s
of
o
f
this
t
h
i
s
document,
d
o
c
u
m
e
n
t
,
the
t
h
e
type
t
y
p
e
design
d
e
s
i
g
n
consists
c
o
n
s
i
s
t
s
of
o
f
the
t
h
e
following:
f
o
l
l
o
w
i
n
g
:
(1)
(
1
)
The
T
h
e
drawings
d
r
a
w
i
n
g
s
and
a
n
d
specifications,
s
p
e
c
i
f
i
c
a
t
i
o
n
s
,
and
a
n
d
a
a
listing
l
i
s
t
i
n
g
of
o
f
those
t
h
o
s
e
drawings
d
r
a
w
i
n
g
s
and
a
n
d
specifications,
s
p
e
c
i
f
i
c
a
t
i
o
n
s
,
necessary
n
e
c
e
s
s
a
r
y
to
t
o
define
d
e
f
i
n
e
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
design
d
e
s
i
g
n
features
f
e
a
t
u
r
e
s
of
o
f
the
t
h
e
certified
c
e
r
t
i
f
i
e
d
product
p
r
o
d
u
c
t
shown
s
h
o
w
n
to
t
o
comply
c
o
m
p
l
y
with
w
i
t
h
the
t
h
e
requirements
r
e
q
u
i
r
e
m
e
n
t
s
for
f
o
r
that
t
h
a
t
product;
p
r
o
d
u
c
t
;
(2)
(
2
)
Any
A
n
y
other
o
t
h
e
r
data
d
a
t
a
necessary
n
e
c
e
s
s
a
r
y
to
t
o
allow,
a
l
l
o
w
,
by
b
y
comparison,
c
o
m
p
a
r
i
s
o
n
,
the
t
h
e
determination
d
e
t
e
r
m
i
n
a
t
i
o
n
of
o
f
the
t
h
e
airworthiness
a
i
r
w
o
r
t
h
i
n
e
s
s
of
o
f
later
l
a
t
e
r
products
p
r
o
d
u
c
t
s
of
o
f
the
t
h
e
same
s
a
m
e
type.
t
y
p
e
.
Note:
N
o
t
e
:
Use
U
s
e
of
o
f
the
t
h
e
term
t
e
r
m
“product”
“
p
r
o
d
u
c
t
”
in
i
n
this
t
h
i
s
definition
d
e
f
i
n
i
t
i
o
n
refers
r
e
f
e
r
s
to
t
o
any
a
n
y
item
i
t
e
m
for
f
o
r
which
w
h
i
c
h
type
t
y
p
e
certificates
c
e
r
t
i
f
i
c
a
t
e
s
are
a
r
e
granted
g
r
a
n
t
e
d
by
b
y
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
,
for
f
o
r
example,
e
x
a
m
p
l
e
,
aircraft,
a
i
r
c
r
a
f
t
,
engines,
e
n
g
i
n
e
s
,
propellers,
p
r
o
p
e
l
l
e
r
s
,
and,
a
n
d
,
by
b
y
region,
r
e
g
i
o
n
,
auxiliary
a
u
x
i
l
i
a
r
y
power
p
o
w
e
r
units.
u
n
i
t
s
.
Unbounded
U
n
b
o
u
n
d
e
d
recursive
r
e
c
u
r
s
i
v
e
algorithm
a
l
g
o
r
i
t
h
m
–
–
An
A
n
algorithm
a
l
g
o
r
i
t
h
m
that
t
h
a
t
directly
d
i
r
e
c
t
l
y
invokes
i
n
v
o
k
e
s
itself
i
t
s
e
l
f
(self
(
s
e
l
f
recursion)
r
e
c
u
r
s
i
o
n
)
or
o
r
indirectly
i
n
d
i
r
e
c
t
l
y
invokes
i
n
v
o
k
e
s
itself
i
t
s
e
l
f
(mutual
(
m
u
t
u
a
l
recursion),
r
e
c
u
r
s
i
o
n
)
,
and
a
n
d
does
d
o
e
s
not
n
o
t
have
h
a
v
e
a
a
mechanism
m
e
c
h
a
n
i
s
m
to
t
o
limit
l
i
m
i
t
the
t
h
e
number
n
u
m
b
e
r
of
o
f
times
t
i
m
e
s
it
i
t
can
c
a
n
do
d
o
this
t
h
i
s
before
b
e
f
o
r
e
completing.
c
o
m
p
l
e
t
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
–
–
Software
S
o
f
t
w
a
r
e
intended
i
n
t
e
n
d
e
d
for
f
o
r
modification
m
o
d
i
f
i
c
a
t
i
o
n
without
w
i
t
h
o
u
t
review
r
e
v
i
e
w
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
airframe
a
i
r
f
r
a
m
e
manufacturer,
m
a
n
u
f
a
c
t
u
r
e
r
,
or
o
r
the
t
h
e
equipment
e
q
u
i
p
m
e
n
t
vendor,
v
e
n
d
o
r
,
if
i
f
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
established
e
s
t
a
b
l
i
s
h
e
d
during
d
u
r
i
n
g
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
project.
p
r
o
j
e
c
t
.
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
processes
p
r
o
c
e
s
s
e
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
outputs
o
u
t
p
u
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
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
A-1
A
-
1
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
DO-178/ED-12
D
O
-
1
7
8
/
E
D
-
1
2
DOCUMENT
D
O
C
U
M
E
N
T
-
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
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-35,
E
D
-
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
guidance.
g
u
i
d
a
n
c
e
.
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
;
its
i
t
s
technical
t
e
c
h
n
i
c
a
l
content
c
o
n
t
e
n
t
was
w
a
s
identical
i
d
e
n
t
i
c
a
l
to
t
o
DO-
D
O
-
178.
1
7
8
.
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
(through
(
t
h
r
o
u
g
h
WG-12),
W
G
-
1
2
)
,
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
.
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
)
formally
f
o
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
had
h
a
d
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-12A,
E
D
-
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
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
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
(or
(
o
r
WG-12),
W
G
-
1
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
guidance
g
u
i
d
a
n
c
e
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
committee
c
o
m
m
i
t
t
e
e
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-167)
(
S
C
-
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
.
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
.
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
in
i
n
December
D
e
c
e
m
b
e
r
1992.
1
9
9
2
.
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-
E
D
-
12B,
1
2
B
,
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-178B.
D
O
-
1
7
8
B
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
A-2
A
-
2
-
RTCA/EUROCAE
R
T
C
A
/
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
Since
S
i
n
c
e
1992,
1
9
9
2
,
the
t
h
e
aviation
a
v
i
a
t
i
o
n
industry
i
n
d
u
s
t
r
y
and
a
n
d
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
around
a
r
o
u
n
d
the
t
h
e
world
w
o
r
l
d
have
h
a
v
e
used
u
s
e
d
the
t
h
e
considerations
c
o
n
s
i
d
e
r
a
t
i
o
n
s
in
i
n
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
as
a
s
an
a
n
acceptable
a
c
c
e
p
t
a
b
l
e
means
m
e
a
n
s
of
o
f
compliance
c
o
m
p
l
i
a
n
c
e
for
f
o
r
software
s
o
f
t
w
a
r
e
approval
a
p
p
r
o
v
a
l
in
i
n
the
t
h
e
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
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
.
As
A
s
experience
e
x
p
e
r
i
e
n
c
e
was
w
a
s
gained
g
a
i
n
e
d
in
i
n
the
t
h
e
use
u
s
e
of
o
f
DO-178B/ED-12B,
D
O
-
1
7
8
B
/
E
D
-
1
2
B
,
questions
q
u
e
s
t
i
o
n
s
arose
a
r
o
s
e
regarding
r
e
g
a
r
d
i
n
g
the
t
h
e
document’s
d
o
c
u
m
e
n
t
’
s
content
c
o
n
t
e
n
t
and
a
n
d
application.
a
p
p
l
i
c
a
t
i
o
n
.
Some
S
o
m
e
of
o
f
these
t
h
e
s
e
questions
q
u
e
s
t
i
o
n
s
were
w
e
r
e
addressed
a
d
d
r
e
s
s
e
d
through
t
h
r
o
u
g
h
the
t
h
e
work
w
o
r
k
of
o
f
SC-
S
C
-
190/WG-52
1
9
0
/
W
G
-
5
2
in
i
n
the
t
h
e
development
d
e
v
e
l
o
p
m
e
n
t
of
o
f
DO-248B/ED-94B.
D
O
-
2
4
8
B
/
E
D
-
9
4
B
.
However,
H
o
w
e
v
e
r
,
DO-248B/ED-94B
D
O
-
2
4
8
B
/
E
D
-
9
4
B
did
d
i
d
not
n
o
t
contain
c
o
n
t
a
i
n
additional
a
d
d
i
t
i
o
n
a
l
guidance
g
u
i
d
a
n
c
e
for
f
o
r
use
u
s
e
as
a
s
compliance,
c
o
m
p
l
i
a
n
c
e
,
only
o
n
l
y
clarifications.
c
l
a
r
i
f
i
c
a
t
i
o
n
s
.
Additionally,
A
d
d
i
t
i
o
n
a
l
l
y
,
advances
a
d
v
a
n
c
e
s
in
i
n
hardware
h
a
r
d
w
a
r
e
and
a
n
d
software
s
o
f
t
w
a
r
e
technology
t
e
c
h
n
o
l
o
g
y
resulted
r
e
s
u
l
t
e
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
methodologies
m
e
t
h
o
d
o
l
o
g
i
e
s
and
a
n
d
issues
i
s
s
u
e
s
which
w
h
i
c
h
were
w
e
r
e
not
n
o
t
adequately
a
d
e
q
u
a
t
e
l
y
addressed
a
d
d
r
e
s
s
e
d
in
i
n
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
or
o
r
DO-248B/ED-94B.
D
O
-
2
4
8
B
/
E
D
-
9
4
B
.
In
I
n
2004,
2
0
0
4
,
the
t
h
e
FAA
F
A
A
and
a
n
d
aviation
a
v
i
a
t
i
o
n
industry
i
n
d
u
s
t
r
y
representatives
r
e
p
r
e
s
e
n
t
a
t
i
v
e
s
initiated
i
n
i
t
i
a
t
e
d
a
a
discussion
d
i
s
c
u
s
s
i
o
n
with
w
i
t
h
RTCA
R
T
C
A
concerning
c
o
n
c
e
r
n
i
n
g
the
t
h
e
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
since
s
i
n
c
e
1992,
1
9
9
2
,
when
w
h
e
n
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
was
w
a
s
published.
p
u
b
l
i
s
h
e
d
.
RTCA
R
T
C
A
then
t
h
e
n
requested
r
e
q
u
e
s
t
e
d
a
a
Software
S
o
f
t
w
a
r
e
Ad
A
d
Hoc
H
o
c
committee
c
o
m
m
i
t
t
e
e
evaluate
e
v
a
l
u
a
t
e
the
t
h
e
issues
i
s
s
u
e
s
and
a
n
d
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
need
n
e
e
d
for
f
o
r
improved
i
m
p
r
o
v
e
d
guidance
g
u
i
d
a
n
c
e
in
i
n
light
l
i
g
h
t
of
o
f
these
t
h
e
s
e
advancements
a
d
v
a
n
c
e
m
e
n
t
s
in
i
n
technology.
t
e
c
h
n
o
l
o
g
y
.
The
T
h
e
Software
S
o
f
t
w
a
r
e
Ad
A
d
Hoc
H
o
c
committee,
c
o
m
m
i
t
t
e
e
,
which
w
h
i
c
h
included
i
n
c
l
u
d
e
d
European
E
u
r
o
p
e
a
n
participants,
p
a
r
t
i
c
i
p
a
n
t
s
,
recommended
r
e
c
o
m
m
e
n
d
e
d
to
t
o
RTCA
R
T
C
A
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
be
b
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
issues.
i
s
s
u
e
s
.
In
I
n
December
D
e
c
e
m
b
e
r
2004,
2
0
0
4
,
RTCA
R
T
C
A
and
a
n
d
EUROCAE
E
U
R
O
C
A
E
approved
a
p
p
r
o
v
e
d
the
t
h
e
sponsorship
s
p
o
n
s
o
r
s
h
i
p
of
o
f
such
s
u
c
h
a
a
joint
j
o
i
n
t
special
s
p
e
c
i
a
l
committee/working
c
o
m
m
i
t
t
e
e
/
w
o
r
k
i
n
g
group,
g
r
o
u
p
,
Special
S
p
e
c
i
a
l
Committee
C
o
m
m
i
t
t
e
e
205/Working
2
0
5
/
W
o
r
k
i
n
g
Group
G
r
o
u
p
71,
7
1
,
SC-205/WG-71.
S
C
-
2
0
5
/
W
G
-
7
1
.
-
The
T
h
e
Terms
T
e
r
m
s
of
o
f
Reference
R
e
f
e
r
e
n
c
e
(TORs)
(
T
O
R
s
)
provided
p
r
o
v
i
d
e
d
to
t
o
the
t
h
e
SC/WG
S
C
/
W
G
were:
w
e
r
e
:
-
Modify
M
o
d
i
f
y
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
to
t
o
become
b
e
c
o
m
e
DO-178C/ED-12C,
D
O
-
1
7
8
C
/
E
D
-
1
2
C
,
or
o
r
other
o
t
h
e
r
document
d
o
c
u
m
e
n
t
number.
n
u
m
b
e
r
.
-
Modify
M
o
d
i
f
y
DO-248B/ED-94B
D
O
-
2
4
8
B
/
E
D
-
9
4
B
to
t
o
become
b
e
c
o
m
e
DO-248C/ED-94C,
D
O
-
2
4
8
C
/
E
D
-
9
4
C
,
or
o
r
other
o
t
h
e
r
document
d
o
c
u
m
e
n
t
number.
n
u
m
b
e
r
.
-
Consolidate
C
o
n
s
o
l
i
d
a
t
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Guidance.
G
u
i
d
a
n
c
e
.
-
Consolidate
C
o
n
s
o
l
i
d
a
t
e
Software
S
o
f
t
w
a
r
e
Development
D
e
v
e
l
o
p
m
e
n
t
Guidelines.
G
u
i
d
e
l
i
n
e
s
.
-
Develop
D
e
v
e
l
o
p
and
a
n
d
document
d
o
c
u
m
e
n
t
technology-specific
t
e
c
h
n
o
l
o
g
y
-
s
p
e
c
i
f
i
c
or
o
r
method-specific
m
e
t
h
o
d
-
s
p
e
c
i
f
i
c
guidance
g
u
i
d
a
n
c
e
and
a
n
d
guidelines.
g
u
i
d
e
l
i
n
e
s
.
-
Determine,
D
e
t
e
r
m
i
n
e
,
document
d
o
c
u
m
e
n
t
and
a
n
d
report
r
e
p
o
r
t
the
t
h
e
effects
e
f
f
e
c
t
s
of
o
f
DO-178C/ED-12C
D
O
-
1
7
8
C
/
E
D
-
1
2
C
or
o
r
other
o
t
h
e
r
modified
m
o
d
i
f
i
e
d
documents
d
o
c
u
m
e
n
t
s
to
t
o
DO-278/ED-109
D
O
-
2
7
8
/
E
D
-
1
0
9
and
a
n
d
recommend
r
e
c
o
m
m
e
n
d
direction
d
i
r
e
c
t
i
o
n
to
t
o
ensure
e
n
s
u
r
e
consistency.
c
o
n
s
i
s
t
e
n
c
y
.
-
Develop
D
e
v
e
l
o
p
and
a
n
d
document
d
o
c
u
m
e
n
t
rationale
r
a
t
i
o
n
a
l
e
for
f
o
r
each
e
a
c
h
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
objective.
o
b
j
e
c
t
i
v
e
.
-
Evaluate
E
v
a
l
u
a
t
e
the
t
h
e
issues
i
s
s
u
e
s
in
i
n
the
t
h
e
‘Software
‘
S
o
f
t
w
a
r
e
Issues
I
s
s
u
e
s
List.xls’
L
i
s
t
.
x
l
s
’
spreadsheet
s
p
r
e
a
d
s
h
e
e
t
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
Ad
A
d
Hoc
H
o
c
committee
c
o
m
m
i
t
t
e
e
and
a
n
d
other
o
t
h
e
r
identified
i
d
e
n
t
i
f
i
e
d
issues.
i
s
s
u
e
s
.
Determine
D
e
t
e
r
m
i
n
e
‘if’,
‘
i
f
’
,
‘where’
‘
w
h
e
r
e
’
and
a
n
d
‘how’
‘
h
o
w
’
each
e
a
c
h
issue
i
s
s
u
e
should
s
h
o
u
l
d
be
b
e
addressed.
a
d
d
r
e
s
s
e
d
.
-
Coordinate
C
o
o
r
d
i
n
a
t
e
SC/WG
S
C
/
W
G
products
p
r
o
d
u
c
t
s
with
w
i
t
h
software
s
o
f
t
w
a
r
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
via
v
i
a
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
Team
T
e
a
m
(CAST)
(
C
A
S
T
)
or
o
r
other
o
t
h
e
r
appropriate
a
p
p
r
o
p
r
i
a
t
e
groups.
g
r
o
u
p
s
.
-
Coordinate
C
o
o
r
d
i
n
a
t
e
with
w
i
t
h
other
o
t
h
e
r
groups
g
r
o
u
p
s
and
a
n
d
existing
e
x
i
s
t
i
n
g
organizations
o
r
g
a
n
i
z
a
t
i
o
n
s
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
SAE
S
A
E
S18,
S
1
8
,
WG-63,
W
G
-
6
3
,
SC-200/WG-60),
S
C
-
2
0
0
/
W
G
-
6
0
)
,
as
a
s
appropriate.
a
p
p
r
o
p
r
i
a
t
e
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
A-3
A
-
3
-
Report
R
e
p
o
r
t
to
t
o
the
t
h
e
SC/WG’s
S
C
/
W
G
’
s
governing
g
o
v
e
r
n
i
n
g
body
b
o
d
y
the
t
h
e
direction
d
i
r
e
c
t
i
o
n
being
b
e
i
n
g
taken
t
a
k
e
n
by
b
y
the
t
h
e
committee
c
o
m
m
i
t
t
e
e
within
w
i
t
h
i
n
6-9
6
-
9
months
m
o
n
t
h
s
after
a
f
t
e
r
the
t
h
e
first
f
i
r
s
t
SC/WG
S
C
/
W
G
meeting.
m
e
e
t
i
n
g
.
-
Work
W
o
r
k
with
w
i
t
h
RTCA
R
T
C
A
and
a
n
d
EUROCAE
E
U
R
O
C
A
E
to
t
o
explore
e
x
p
l
o
r
e
and
a
n
d
implement
i
m
p
l
e
m
e
n
t
ways
w
a
y
s
of
o
f
expanding
e
x
p
a
n
d
i
n
g
the
t
h
e
usability
u
s
a
b
i
l
i
t
y
of
o
f
the
t
h
e
deliverables
d
e
l
i
v
e
r
a
b
l
e
s
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
hypertext
h
y
p
e
r
t
e
x
t
electronic
e
l
e
c
t
r
o
n
i
c
versions).
v
e
r
s
i
o
n
s
)
.
-
Modify
M
o
d
i
f
y
DO-278/ED-109
D
O
-
2
7
8
/
E
D
-
1
0
9
to
t
o
become
b
e
c
o
m
e
DO-278A/ED-109A,
D
O
-
2
7
8
A
/
E
D
-
1
0
9
A
,
or
o
r
other
o
t
h
e
r
document
d
o
c
u
m
e
n
t
number.
n
u
m
b
e
r
.
-
Submit
S
u
b
m
i
t
to
t
o
RTCA
R
T
C
A
and
a
n
d
EUROCAE
E
U
R
O
C
A
E
a
a
DO-178C/ED-12C
D
O
-
1
7
8
C
/
E
D
-
1
2
C
and
a
n
d
DO-278A/ED-109A
D
O
-
2
7
8
A
/
E
D
-
1
0
9
A
commonality
c
o
m
m
o
n
a
l
i
t
y
analysis
a
n
a
l
y
s
i
s
when
w
h
e
n
documents
d
o
c
u
m
e
n
t
s
are
a
r
e
finalized.
f
i
n
a
l
i
z
e
d
.
-
The
T
h
e
RTCA
R
T
C
A
Program
P
r
o
g
r
a
m
Management
M
a
n
a
g
e
m
e
n
t
Committee
C
o
m
m
i
t
t
e
e
(PMC)
(
P
M
C
)
directed
d
i
r
e
c
t
e
d
the
t
h
e
SC/WG
S
C
/
W
G
to
t
o
maintain
m
a
i
n
t
a
i
n
or
o
r
adhere
a
d
h
e
r
e
to
t
o
the
t
h
e
following
f
o
l
l
o
w
i
n
g
while
w
h
i
l
e
accomplishing
a
c
c
o
m
p
l
i
s
h
i
n
g
the
t
h
e
TORs:
T
O
R
s
:
-
Maintain
M
a
i
n
t
a
i
n
the
t
h
e
current
c
u
r
r
e
n
t
objective-based
o
b
j
e
c
t
i
v
e
-
b
a
s
e
d
approach
a
p
p
r
o
a
c
h
for
f
o
r
software
s
o
f
t
w
a
r
e
assurance.
a
s
s
u
r
a
n
c
e
.
-
Maintain
M
a
i
n
t
a
i
n
the
t
h
e
technology
t
e
c
h
n
o
l
o
g
y
independent
i
n
d
e
p
e
n
d
e
n
t
nature
n
a
t
u
r
e
of
o
f
the
t
h
e
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
and
a
n
d
DO-278/ED-109
D
O
-
2
7
8
/
E
D
-
1
0
9
objectives.
o
b
j
e
c
t
i
v
e
s
.
-
Evaluate
E
v
a
l
u
a
t
e
issues
i
s
s
u
e
s
as
a
s
brought
b
r
o
u
g
h
t
forth
f
o
r
t
h
to
t
o
the
t
h
e
SC/WG.
S
C
/
W
G
.
For
F
o
r
any
a
n
y
candidate
c
a
n
d
i
d
a
t
e
guidance
g
u
i
d
a
n
c
e
modifications
m
o
d
i
f
i
c
a
t
i
o
n
s
determine
d
e
t
e
r
m
i
n
e
if
i
f
the
t
h
e
issue
i
s
s
u
e
can
c
a
n
be
b
e
satisfied
s
a
t
i
s
f
i
e
d
first
f
i
r
s
t
in
i
n
guideline
g
u
i
d
e
l
i
n
e
related
r
e
l
a
t
e
d
documents.
d
o
c
u
m
e
n
t
s
.
-
Modifications
M
o
d
i
f
i
c
a
t
i
o
n
s
to
t
o
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
and
a
n
d
DO-278/ED-109
D
O
-
2
7
8
/
E
D
-
1
0
9
should:
s
h
o
u
l
d
:
-
In
I
n
the
t
h
e
context
c
o
n
t
e
x
t
of
o
f
maintaining
m
a
i
n
t
a
i
n
i
n
g
backward
b
a
c
k
w
a
r
d
compatibility
c
o
m
p
a
t
i
b
i
l
i
t
y
with
w
i
t
h
DO-178B/ED-
D
O
-
1
7
8
B
/
E
D
-
12B,
1
2
B
,
make
m
a
k
e
those
t
h
o
s
e
changes
c
h
a
n
g
e
s
to
t
o
the
t
h
e
existing
e
x
i
s
t
i
n
g
text
t
e
x
t
that
t
h
a
t
are
a
r
e
needed
n
e
e
d
e
d
to
t
o
adequately
a
d
e
q
u
a
t
e
l
y
address
a
d
d
r
e
s
s
the
t
h
e
current
c
u
r
r
e
n
t
states
s
t
a
t
e
s
of
o
f
the
t
h
e
art
a
r
t
and
a
n
d
practice
p
r
a
c
t
i
c
e
in
i
n
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
in
i
n
support
s
u
p
p
o
r
t
of
o
f
system
s
y
s
t
e
m
safety,
s
a
f
e
t
y
,
to
t
o
address
a
d
d
r
e
s
s
emerging
e
m
e
r
g
i
n
g
trends,
t
r
e
n
d
s
,
and
a
n
d
to
t
o
allow
a
l
l
o
w
change
c
h
a
n
g
e
with
w
i
t
h
technology.
t
e
c
h
n
o
l
o
g
y
.
-
Consider
C
o
n
s
i
d
e
r
the
t
h
e
economic
e
c
o
n
o
m
i
c
impact
i
m
p
a
c
t
relative
r
e
l
a
t
i
v
e
to
t
o
system
s
y
s
t
e
m
certification
c
e
r
t
i
f
i
c
a
t
i
o
n
or
o
r
approval
a
p
p
r
o
v
a
l
without
w
i
t
h
o
u
t
compromising
c
o
m
p
r
o
m
i
s
i
n
g
system
s
y
s
t
e
m
safety.
s
a
f
e
t
y
.
-
Address
A
d
d
r
e
s
s
clear
c
l
e
a
r
errors
e
r
r
o
r
s
or
o
r
inconsistencies
i
n
c
o
n
s
i
s
t
e
n
c
i
e
s
in
i
n
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
and
a
n
d
DO-
D
O
-
278/ED-109.
2
7
8
/
E
D
-
1
0
9
.
iv.
i
v
.
Fill
F
i
l
l
any
a
n
y
clear
c
l
e
a
r
gaps
g
a
p
s
in
i
n
DO-178B/ED-12B
D
O
-
1
7
8
B
/
E
D
-
1
2
B
and
a
n
d
DO-278/ED-109.
D
O
-
2
7
8
/
E
D
-
1
0
9
.
v.
v
.
Meet
M
e
e
t
a
a
documented
d
o
c
u
m
e
n
t
e
d
need
n
e
e
d
to
t
o
a
a
defined
d
e
f
i
n
e
d
assurance
a
s
s
u
r
a
n
c
e
benefit.
b
e
n
e
f
i
t
.
vi.
v
i
.
Report
R
e
p
o
r
t
any
a
n
y
proposed
p
r
o
p
o
s
e
d
changes
c
h
a
n
g
e
s
to
t
o
the
t
h
e
number
n
u
m
b
e
r
of
o
f
software
s
o
f
t
w
a
r
e
levels
l
e
v
e
l
s
or
o
r
mapping
m
a
p
p
i
n
g
of
o
f
levels
l
e
v
e
l
s
to
t
o
hazard
h
a
z
a
r
d
categories
c
a
t
e
g
o
r
i
e
s
to
t
o
the
t
h
e
SC/WG’s
S
C
/
W
G
’
s
governing
g
o
v
e
r
n
i
n
g
body
b
o
d
y
and
a
n
d
provide
p
r
o
v
i
d
e
a
a
documented
d
o
c
u
m
e
n
t
e
d
substantiated
s
u
b
s
t
a
n
t
i
a
t
e
d
need,
n
e
e
d
,
at
a
t
the
t
h
e
earliest
e
a
r
l
i
e
s
t
feasible
f
e
a
s
i
b
l
e
opportunity.
o
p
p
o
r
t
u
n
i
t
y
.
Communicate
C
o
m
m
u
n
i
c
a
t
e
back
b
a
c
k
to
t
o
the
t
h
e
SC/WG
S
C
/
W
G
at
a
t
large,
l
a
r
g
e
,
any
a
n
y
concerns
c
o
n
c
e
r
n
s
of
o
f
the
t
h
e
governing
g
o
v
e
r
n
i
n
g
body.
b
o
d
y
.
vii.
v
i
i
.
Ensure
E
n
s
u
r
e
that
t
h
a
t
all
a
l
l
deliverables
d
e
l
i
v
e
r
a
b
l
e
s
produced
p
r
o
d
u
c
e
d
by
b
y
the
t
h
e
committee
c
o
m
m
i
t
t
e
e
contain
c
o
n
t
a
i
n
consistent
c
o
n
s
i
s
t
e
n
t
and
a
n
d
complete
c
o
m
p
l
e
t
e
usability
u
s
a
b
i
l
i
t
y
mechanisms
m
e
c
h
a
n
i
s
m
s
(for
(
f
o
r
example,
e
x
a
m
p
l
e
,
indexes,
i
n
d
e
x
e
s
,
glossaries).
g
l
o
s
s
a
r
i
e
s
)
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
A-4
A
-
4
-
Seven
S
e
v
e
n
joint
j
o
i
n
t
RTCA/EUROCAE
R
T
C
A
/
E
U
R
O
C
A
E
sub-groups
s
u
b
-
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
the
t
h
e
TORs:
T
O
R
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
.
-
Issues
I
s
s
u
e
s
and
a
n
d
Rationale.
R
a
t
i
o
n
a
l
e
.
-
Tool
T
o
o
l
Qualification.
Q
u
a
l
i
f
i
c
a
t
i
o
n
.
-
Model-Based
M
o
d
e
l
-
B
a
s
e
d
Development
D
e
v
e
l
o
p
m
e
n
t
and
a
n
d
Verification.
V
e
r
i
f
i
c
a
t
i
o
n
.
-
Object-Oriented
O
b
j
e
c
t
-
O
r
i
e
n
t
e
d
Technology.
T
e
c
h
n
o
l
o
g
y
.
-
Formal
F
o
r
m
a
l
Methods.
M
e
t
h
o
d
s
.
-
Special
S
p
e
c
i
a
l
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
and
a
n
d
CNS/ATM.
C
N
S
/
A
T
M
.
-
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-205
S
C
-
2
0
5
and
a
n
d
WG-71
W
G
-
7
1
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-178C
D
O
-
1
7
8
C
and
a
n
d
EUROCAE
E
U
R
O
C
A
E
document
d
o
c
u
m
e
n
t
ED-12C.
E
D
-
1
2
C
.
-
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-178C
D
O
-
1
7
8
C
and
a
n
d
DO-178B
D
O
-
1
7
8
B
DO-178C
D
O
-
1
7
8
C
is
i
s
an
a
n
update
u
p
d
a
t
e
to
t
o
DO-178B.
D
O
-
1
7
8
B
.
The
T
h
e
DO-178C
D
O
-
1
7
8
C
updates
u
p
d
a
t
e
s
fall
f
a
l
l
into
i
n
t
o
a
a
variety
v
a
r
i
e
t
y
of
o
f
categories:
c
a
t
e
g
o
r
i
e
s
:
-
Errors
E
r
r
o
r
s
and
a
n
d
Inconsistencies:
I
n
c
o
n
s
i
s
t
e
n
c
i
e
s
:
DO-178C
D
O
-
1
7
8
C
addressed
a
d
d
r
e
s
s
e
d
DO-178B’s
D
O
-
1
7
8
B
’
s
known
k
n
o
w
n
errors
e
r
r
o
r
s
and
a
n
d
inconsistencies.
i
n
c
o
n
s
i
s
t
e
n
c
i
e
s
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
DO-178C
D
O
-
1
7
8
C
has
h
a
s
addressed
a
d
d
r
e
s
s
e
d
the
t
h
e
errata
e
r
r
a
t
a
of
o
f
DO-178B
D
O
-
1
7
8
B
and
a
n
d
has
h
a
s
removed
r
e
m
o
v
e
d
inconsistencies
i
n
c
o
n
s
i
s
t
e
n
c
i
e
s
between
b
e
t
w
e
e
n
the
t
h
e
different
d
i
f
f
e
r
e
n
t
tables
t
a
b
l
e
s
of
o
f
DO-178B
D
O
-
1
7
8
B
Annex
A
n
n
e
x
A.
A
.
b.
b
.
c.
c
.
d.
d
.
e.
e
.
-
Consistent
C
o
n
s
i
s
t
e
n
t
Terminology:
T
e
r
m
i
n
o
l
o
g
y
:
DO-178C
D
O
-
1
7
8
C
addressed
a
d
d
r
e
s
s
e
d
issues
i
s
s
u
e
s
regarding
r
e
g
a
r
d
i
n
g
the
t
h
e
use
u
s
e
of
o
f
specific
s
p
e
c
i
f
i
c
terms
t
e
r
m
s
such
s
u
c
h
as
a
s
“guidance”,
“
g
u
i
d
a
n
c
e
”
,
“guidelines”,
“
g
u
i
d
e
l
i
n
e
s
”
,
“purpose”,
“
p
u
r
p
o
s
e
”
,
“goal”,
“
g
o
a
l
”
,
“objective”,
“
o
b
j
e
c
t
i
v
e
”
,
and
a
n
d
“activity”
“
a
c
t
i
v
i
t
y
”
by
b
y
changing
c
h
a
n
g
i
n
g
the
t
h
e
text
t
e
x
t
so
s
o
that
t
h
a
t
the
t
h
e
use
u
s
e
of
o
f
those
t
h
o
s
e
terms
t
e
r
m
s
is
i
s
consistent
c
o
n
s
i
s
t
e
n
t
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
document.
d
o
c
u
m
e
n
t
.
Wording
W
o
r
d
i
n
g
Improvements:
I
m
p
r
o
v
e
m
e
n
t
s
:
DO-178C
D
O
-
1
7
8
C
made
m
a
d
e
wording
w
o
r
d
i
n
g
improvements
i
m
p
r
o
v
e
m
e
n
t
s
throughout
t
h
r
o
u
g
h
o
u
t
the
t
h
e
document.
d
o
c
u
m
e
n
t
.
All
A
l
l
such
s
u
c
h
changes
c
h
a
n
g
e
s
were
w
e
r
e
made
m
a
d
e
simply
s
i
m
p
l
y
to
t
o
make
m
a
k
e
the
t
h
e
document
d
o
c
u
m
e
n
t
more
m
o
r
e
precise;
p
r
e
c
i
s
e
;
they
t
h
e
y
were
w
e
r
e
not
n
o
t
meant
m
e
a
n
t
to
t
o
change
c
h
a
n
g
e
the
t
h
e
original
o
r
i
g
i
n
a
l
intent
i
n
t
e
n
t
of
o
f
DO-178B.
D
O
-
1
7
8
B
.
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
:
DO-178C
D
O
-
1
7
8
C
reinforced
r
e
i
n
f
o
r
c
e
d
the
t
h
e
point
p
o
i
n
t
that,
t
h
a
t
,
in
i
n
order
o
r
d
e
r
to
t
o
fully
f
u
l
l
y
understand
u
n
d
e
r
s
t
a
n
d
the
t
h
e
recommendations,
r
e
c
o
m
m
e
n
d
a
t
i
o
n
s
,
the
t
h
e
full
f
u
l
l
body
b
o
d
y
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
considered.
c
o
n
s
i
d
e
r
e
d
.
For
F
o
r
example,
e
x
a
m
p
l
e
,
Annex
A
n
n
e
x
A
A
now
n
o
w
includes
i
n
c
l
u
d
e
s
references
r
e
f
e
r
e
n
c
e
s
to
t
o
each
e
a
c
h
activity
a
c
t
i
v
i
t
y
as
a
s
well
w
e
l
l
as
a
s
to
t
o
each
e
a
c
h
objective;
o
b
j
e
c
t
i
v
e
;
and
a
n
d
section
s
e
c
t
i
o
n
1.4,
1
.
4
,
titled
t
i
t
l
e
d
“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
”
reinforces
r
e
i
n
f
o
r
c
e
s
the
t
h
e
point
p
o
i
n
t
that
t
h
a
t
activities
a
c
t
i
v
i
t
i
e
s
are
a
r
e
a
a
major
m
a
j
o
r
part
p
a
r
t
of
o
f
the
t
h
e
overall
o
v
e
r
a
l
l
guidance.
g
u
i
d
a
n
c
e
.
Supplements:
S
u
p
p
l
e
m
e
n
t
s
:
DO-178C
D
O
-
1
7
8
C
recognized
r
e
c
o
g
n
i
z
e
d
that
t
h
a
t
new
n
e
w
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
techniques
t
e
c
h
n
i
q
u
e
s
may
m
a
y
result
r
e
s
u
l
t
in
i
n
new
n
e
w
issues.
i
s
s
u
e
s
.
Rather
R
a
t
h
e
r
than
t
h
a
n
expanding
e
x
p
a
n
d
i
n
g
text
t
e
x
t
to
t
o
account
a
c
c
o
u
n
t
for
f
o
r
all
a
l
l
the
t
h
e
current
c
u
r
r
e
n
t
software
s
o
f
t
w
a
r
e
development
d
e
v
e
l
o
p
m
e
n
t
techniques
t
e
c
h
n
i
q
u
e
s
(and
(
a
n
d
being
b
e
i
n
g
revised
r
e
v
i
s
e
d
yet
y
e
t
again
a
g
a
i
n
to
t
o
account
a
c
c
o
u
n
t
for
f
o
r
future
f
u
t
u
r
e
techniques),
t
e
c
h
n
i
q
u
e
s
)
,
DO-178C
D
O
-
1
7
8
C
acknowledged
a
c
k
n
o
w
l
e
d
g
e
d
that
t
h
a
t
one
o
n
e
or
o
r
more
m
o
r
e
supplements
s
u
p
p
l
e
m
e
n
t
s
may
m
a
y
be
b
e
used
u
s
e
d
in
i
n
conjunction
c
o
n
j
u
n
c
t
i
o
n
with
w
i
t
h
DO-178C
D
O
-
1
7
8
C
to
t
o
modify
m
o
d
i
f
y
the
t
h
e
guidance
g
u
i
d
a
n
c
e
for
f
o
r
specific
s
p
e
c
i
f
i
c
techniques.
t
e
c
h
n
i
q
u
e
s
.
Section
S
e
c
t
i
o
n
12
1
2
was
w
a
s
impacted
i
m
p
a
c
t
e
d
since
s
i
n
c
e
planned
p
l
a
n
n
e
d
supplements
s
u
p
p
l
e
m
e
n
t
s
more
m
o
r
e
completely
c
o
m
p
l
e
t
e
l
y
address
a
d
d
r
e
s
s
those
t
h
o
s
e
specific
s
p
e
c
i
f
i
c
techniques.
t
e
c
h
n
i
q
u
e
s
.
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
(Section
(
S
e
c
t
i
o
n
12.2):
1
2
.
2
)
:
The
T
h
e
terms
t
e
r
m
s
"development
"
d
e
v
e
l
o
p
m
e
n
t
tool"
t
o
o
l
"
and
a
n
d
"verification
"
v
e
r
i
f
i
c
a
t
i
o
n
tool"
t
o
o
l
"
are
a
r
e
replaced
r
e
p
l
a
c
e
d
by
b
y
three
t
h
r
e
e
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
criteria
c
r
i
t
e
r
i
a
that
t
h
a
t
determine
d
e
t
e
r
m
i
n
e
the
t
h
e
applicable
a
p
p
l
i
c
a
b
l
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
A-5
A
-
5
tool
t
o
o
l
qualification
q
u
a
l
i
f
i
c
a
t
i
o
n
level
l
e
v
e
l
(TQL)
(
T
Q
L
)
in
i
n
regard
r
e
g
a
r
d
of
o
f
the
t
h
e
software
s
o
f
t
w
a
r
e
level.
l
e
v
e
l
.
The
T
h
e
guidance
g
u
i
d
a
n
c
e
to
t
o
qualify
q
u
a
l
i
f
y
a
a
tool
t
o
o
l
is
i
s
removed
r
e
m
o
v
e
d
in
i
n
DO-178C,
D
O
-
1
7
8
C
,
but
b
u
t
provided
p
r
o
v
i
d
e
d
in
i
n
a
a
domain
d
o
m
a
i
n
independent,
i
n
d
e
p
e
n
d
e
n
t
,
external
e
x
t
e
r
n
a
l
document,
d
o
c
u
m
e
n
t
,
referenced
r
e
f
e
r
e
n
c
e
d
in
i
n
section
s
e
c
t
i
o
n
12.2
1
2
.
2
-
Coordinated
C
o
o
r
d
i
n
a
t
e
d
System/Software
S
y
s
t
e
m
/
S
o
f
t
w
a
r
e
Aspects:
A
s
p
e
c
t
s
:
DO-178C
D
O
-
1
7
8
C
updated
u
p
d
a
t
e
d
section
s
e
c
t
i
o
n
2,
2
,
which
w
h
i
c
h
provides
p
r
o
v
i
d
e
s
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
,
to
t
o
reflect
r
e
f
l
e
c
t
current
c
u
r
r
e
n
t
system
s
y
s
t
e
m
practices.
p
r
a
c
t
i
c
e
s
.
The
T
h
e
updates
u
p
d
a
t
e
s
were
w
e
r
e
based
b
a
s
e
d
upon
u
p
o
n
coordination
c
o
o
r
d
i
n
a
t
i
o
n
with
w
i
t
h
the
t
h
e
committees
c
o
m
m
i
t
t
e
e
s
which
w
h
i
c
h
were
w
e
r
e
updating
u
p
d
a
t
i
n
g
ARP4754
A
R
P
4
7
5
4
(system-level
(
s
y
s
t
e
m
-
l
e
v
e
l
guidance)
g
u
i
d
a
n
c
e
)
at
a
t
the
t
h
e
same
s
a
m
e
time
t
i
m
e
SC-205/WG-71
S
C
-
2
0
5
/
W
G
-
7
1
was
w
a
s
updating
u
p
d
a
t
i
n
g
DO-178B
D
O
-
1
7
8
B
(software-level
(
s
o
f
t
w
a
r
e
-
l
e
v
e
l
guidance).
g
u
i
d
a
n
c
e
)
.
-
DO-178B
D
O
-
1
7
8
B
“Hidden”
“
H
i
d
d
e
n
”
Objectives:
O
b
j
e
c
t
i
v
e
s
:
DO-178C
D
O
-
1
7
8
C
added
a
d
d
e
d
the
t
h
e
so-called
s
o
-
c
a
l
l
e
d
“hidden
“
h
i
d
d
e
n
objectives”
o
b
j
e
c
t
i
v
e
s
”
to
t
o
Annex
A
n
n
e
x
A:
A
:
-
A
A
means
m
e
a
n
s
for
f
o
r
detecting
d
e
t
e
c
t
i
n
g
additional
a
d
d
i
t
i
o
n
a
l
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
and
a
n
d
a
a
means
m
e
a
n
s
to
t
o
ensure
e
n
s
u
r
e
its
i
t
s
verification
v
e
r
i
f
i
c
a
t
i
o
n
coverage
c
o
v
e
r
a
g
e
are
a
r
e
defined
d
e
f
i
n
e
d
(see
(
s
e
e
objective
o
b
j
e
c
t
i
v
e
9
9
of
o
f
Table
T
a
b
l
e
A-7).
A
-
7
)
.
-
Assurance
A
s
s
u
r
a
n
c
e
is
i
s
obtained
o
b
t
a
i
n
e
d
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
(see
(
s
e
e
objective
o
b
j
e
c
t
i
v
e
1
1
of
o
f
Table
T
a
b
l
e
A-9).
A
-
9
)
.
-
General
G
e
n
e
r
a
l
Topics:
T
o
p
i
c
s
:
DO-178C
D
O
-
1
7
8
C
addressed
a
d
d
r
e
s
s
e
d
some
s
o
m
e
general
g
e
n
e
r
a
l
topics
t
o
p
i
c
s
that
t
h
a
t
resulted
r
e
s
u
l
t
e
d
in
i
n
changes
c
h
a
n
g
e
s
to
t
o
several
s
e
v
e
r
a
l
sections
s
e
c
t
i
o
n
s
of
o
f
the
t
h
e
document.
d
o
c
u
m
e
n
t
.
The
T
h
e
topics
t
o
p
i
c
s
included
i
n
c
l
u
d
e
d
a
a
variety
v
a
r
i
e
t
y
of
o
f
subjects
s
u
b
j
e
c
t
s
such
s
u
c
h
as
a
s
applicant’s
a
p
p
l
i
c
a
n
t
’
s
oversight
o
v
e
r
s
i
g
h
t
of
o
f
suppliers,
s
u
p
p
l
i
e
r
s
,
parameter
p
a
r
a
m
e
t
e
r
data
d
a
t
a
items,
i
t
e
m
s
,
and
a
n
d
traceability.
t
r
a
c
e
a
b
i
l
i
t
y
.
In
I
n
addressing
a
d
d
r
e
s
s
i
n
g
these
t
h
e
s
e
topics,
t
o
p
i
c
s
,
two
t
w
o
additional
a
d
d
i
t
i
o
n
a
l
objectives
o
b
j
e
c
t
i
v
e
s
were
w
e
r
e
added
a
d
d
e
d
to
t
o
Annex
A
n
n
e
x
A:
A
:
-
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
is
i
s
correct
c
o
r
r
e
c
t
and
a
n
d
complete
c
o
m
p
l
e
t
e
(see
(
s
e
e
objective
o
b
j
e
c
t
i
v
e
8
8
of
o
f
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
Parameter
P
a
r
a
m
e
t
e
r
Data
D
a
t
a
Item
I
t
e
m
File
F
i
l
e
is
i
s
achieved
a
c
h
i
e
v
e
d
(see
(
s
e
e
objective
o
b
j
e
c
t
i
v
e
9
9
of
o
f
Table
T
a
b
l
e
A-
A
-
5).
5
)
.
Also,
A
l
s
o
,
Trace
T
r
a
c
e
Data
D
a
t
a
was
w
a
s
identified
i
d
e
n
t
i
f
i
e
d
as
a
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
(see
(
s
e
e
11.21,
1
1
.
2
1
,
Table
T
a
b
l
e
A-2,
A
-
2
,
and
a
n
d
Table
T
a
b
l
e
A-6).
A
-
6
)
.
-
DO-178B
D
O
-
1
7
8
B
Gaps
G
a
p
s
and
a
n
d
Clarifications:
C
l
a
r
i
f
i
c
a
t
i
o
n
s
:
DO-178C
D
O
-
1
7
8
C
addressed
a
d
d
r
e
s
s
e
d
several
s
e
v
e
r
a
l
specific
s
p
e
c
i
f
i
c
issues
i
s
s
u
e
s
that
t
h
a
t
resulted
r
e
s
u
l
t
e
d
in
i
n
change
c
h
a
n
g
e
to
t
o
only
o
n
l
y
one
o
n
e
or
o
r
two
t
w
o
paragraphs.
p
a
r
a
g
r
a
p
h
s
.
Each
E
a
c
h
such
s
u
c
h
change
c
h
a
n
g
e
may
m
a
y
have
h
a
v
e
an
a
n
impact
i
m
p
a
c
t
upon
u
p
o
n
the
t
h
e
applicant
a
p
p
l
i
c
a
n
t
as
a
s
these
t
h
e
s
e
changes
c
h
a
n
g
e
s
either
e
i
t
h
e
r
addressed
a
d
d
r
e
s
s
e
d
clear
c
l
e
a
r
gaps
g
a
p
s
in
i
n
DO-178B
D
O
-
1
7
8
B
or
o
r
clarified
c
l
a
r
i
f
i
e
d
guidance
g
u
i
d
a
n
c
e
that
t
h
a
t
was
w
a
s
subject
s
u
b
j
e
c
t
to
t
o
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
.
-
Examples
E
x
a
m
p
l
e
s
of
o
f
gaps
g
a
p
s
addressed
a
d
d
r
e
s
s
e
d
include:
i
n
c
l
u
d
e
:
-
The
T
h
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
”
(MC/DC)
(
M
C
/
D
C
)
definition
d
e
f
i
n
i
t
i
o
n
changed.
c
h
a
n
g
e
d
.
Masking
M
a
s
k
i
n
g
MC/DC
M
C
/
D
C
and
a
n
d
Short
S
h
o
r
t
Circuit,
C
i
r
c
u
i
t
,
as
a
s
well
w
e
l
l
as
a
s
DO-178B’s
D
O
-
1
7
8
B
’
s
interpretation
i
n
t
e
r
p
r
e
t
a
t
i
o
n
of
o
f
MC/DC
M
C
/
D
C
(often
(
o
f
t
e
n
termed
t
e
r
m
e
d
Unique-Cause
U
n
i
q
u
e
-
C
a
u
s
e
MC/DC),
M
C
/
D
C
)
,
are
a
r
e
now
n
o
w
allowed
a
l
l
o
w
e
d
(see
(
s
e
e
Glossary).
G
l
o
s
s
a
r
y
)
.
-
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
now
n
o
w
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
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
process,
p
r
o
c
e
s
s
,
rather
r
a
t
h
e
r
than
t
h
a
n
just
j
u
s
t
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
(see
(
s
e
e
5.1.1.b
5
.
1
.
1
.
b
and
a
n
d
5.2.1.b).
5
.
2
.
1
.
b
)
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
A-6
A
-
6
-
Examples
E
x
a
m
p
l
e
s
of
o
f
clarifications
c
l
a
r
i
f
i
c
a
t
i
o
n
s
include:
i
n
c
l
u
d
e
:
-
Clarified
C
l
a
r
i
f
i
e
d
that
t
h
a
t
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
of
o
f
data
d
a
t
a
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
code
c
o
d
e
components
c
o
m
p
o
n
e
n
t
s
should
s
h
o
u
l
d
be
b
e
achieved
a
c
h
i
e
v
e
d
by
b
y
assessing
a
s
s
e
s
s
i
n
g
the
t
h
e
results
r
e
s
u
l
t
s
of
o
f
the
t
h
e
requirements-based
r
e
q
u
i
r
e
m
e
n
t
s
-
b
a
s
e
d
tests
t
e
s
t
s
(see
(
s
e
e
6.4.4.2.c).
6
.
4
.
4
.
2
.
c
)
.
-
Clarified
C
l
a
r
i
f
i
e
d
that
t
h
a
t
all
a
l
l
tests
t
e
s
t
s
added
a
d
d
e
d
to
t
o
achieve
a
c
h
i
e
v
e
structural
s
t
r
u
c
t
u
r
a
l
coverage
c
o
v
e
r
a
g
e
are
a
r
e
based
b
a
s
e
d
on
o
n
requirements
r
e
q
u
i
r
e
m
e
n
t
s
(see
(
s
e
e
6.4.4.2.d).
6
.
4
.
4
.
2
.
d
)
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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
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
EXECUTIVE
E
X
E
C
U
T
I
V
E
COMMITTEE
C
O
M
M
I
T
T
E
E
MEMBERS
M
E
M
B
E
R
S
Jim
J
i
m
Krodel,
K
r
o
d
e
l
,
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
SC-205
S
C
-
2
0
5
Chair
C
h
a
i
r
Gérard
G
é
r
a
r
d
Ladier,
L
a
d
i
e
r
,
Airbus/Aerospace
A
i
r
b
u
s
/
A
e
r
o
s
p
a
c
e
Valley
V
a
l
l
e
y
WG-71
W
G
-
7
1
Chair
C
h
a
i
r
Mike
M
i
k
e
DeWalt,
D
e
W
a
l
t
,
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Services,
S
e
r
v
i
c
e
s
,
Inc./FAA
I
n
c
.
/
F
A
A
SC-205
S
C
-
2
0
5
Secretary
S
e
c
r
e
t
a
r
y
(until
(
u
n
t
i
l
March
M
a
r
c
h
2008)
2
0
0
8
)
Leslie
L
e
s
l
i
e
Alford,
A
l
f
o
r
d
,
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
SC-205
S
C
-
2
0
5
Secretary
S
e
c
r
e
t
a
r
y
(from
(
f
r
o
m
March
M
a
r
c
h
2008)
2
0
0
8
)
Ross
R
o
s
s
Hannan,
H
a
n
n
a
n
,
Sigma
S
i
g
m
a
Associates
A
s
s
o
c
i
a
t
e
s
(Aerospace)
(
A
e
r
o
s
p
a
c
e
)
WG-71
W
G
-
7
1
Secretary
S
e
c
r
e
t
a
r
y
Barbara
B
a
r
b
a
r
a
Lingberg,
L
i
n
g
b
e
r
g
,
FAA
F
A
A
FAA
F
A
A
Representative/CAST
R
e
p
r
e
s
e
n
t
a
t
i
v
e
/
C
A
S
T
Chair
C
h
a
i
r
Jean-Luc
J
e
a
n
-
L
u
c
Delamaide,
D
e
l
a
m
a
i
d
e
,
EASA
E
A
S
A
EASA
E
A
S
A
Representative
R
e
p
r
e
s
e
n
t
a
t
i
v
e
John
J
o
h
n
Coleman,
C
o
l
e
m
a
n
,
Dawson
D
a
w
s
o
n
Consulting
C
o
n
s
u
l
t
i
n
g
Sub-group
S
u
b
-
g
r
o
u
p
Liaison
L
i
a
i
s
o
n
Matt
M
a
t
t
Jaffe,
J
a
f
f
e
,
Embry-Riddle
E
m
b
r
y
-
R
i
d
d
l
e
Aeronautical
A
e
r
o
n
a
u
t
i
c
a
l
University
U
n
i
v
e
r
s
i
t
y
Web
W
e
b
Site
S
i
t
e
Liaison
L
i
a
i
s
o
n
Todd
T
o
d
d
R.
R
.
White,
W
h
i
t
e
,
L-3
L
-
3
Communications/Qualtech
C
o
m
m
u
n
i
c
a
t
i
o
n
s
/
Q
u
a
l
t
e
c
h
Collaborative
C
o
l
l
a
b
o
r
a
t
i
v
e
Technology
T
e
c
h
n
o
l
o
g
y
Software
S
o
f
t
w
a
r
e
Liaison
L
i
a
i
s
o
n
SG-1
S
G
-
1
–
–
Document
D
o
c
u
m
e
n
t
Integration
I
n
t
e
g
r
a
t
i
o
n
SUB-GROUP
S
U
B
-
G
R
O
U
P
LEADERSHIP
L
E
A
D
E
R
S
H
I
P
Ron
R
o
n
Ashpole,
A
s
h
p
o
l
e
,
SILVER
S
I
L
V
E
R
ATENA
A
T
E
N
A
SG-1
S
G
-
1
Co-chair
C
o
-
c
h
a
i
r
Tom
T
o
m
Ferrell,
F
e
r
r
e
l
l
,
Ferrell
F
e
r
r
e
l
l
and
a
n
d
Associates
A
s
s
o
c
i
a
t
e
s
Consulting
C
o
n
s
u
l
t
i
n
g
SG-1
S
G
-
1
Co-chair
C
o
-
c
h
a
i
r
(until
(
u
n
t
i
l
March
M
a
r
c
h
2008)
2
0
0
8
)
Marty
M
a
r
t
y
Gasiorowski,
G
a
s
i
o
r
o
w
s
k
i
,
Worldwide
W
o
r
l
d
w
i
d
e
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Services
S
e
r
v
i
c
e
s
SG-1
S
G
-
1
Co-chair
C
o
-
c
h
a
i
r
(from
(
f
r
o
m
March
M
a
r
c
h
2008)
2
0
0
8
)
Tom
T
o
m
Roth,
R
o
t
h
,
Airborne
A
i
r
b
o
r
n
e
Software
S
o
f
t
w
a
r
e
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Consulting
C
o
n
s
u
l
t
i
n
g
SG-1
S
G
-
1
Secretary
S
e
c
r
e
t
a
r
y
SG-2
S
G
-
2
–
–
Issues
I
s
s
u
e
s
and
a
n
d
Rationale
R
a
t
i
o
n
a
l
e
Ross
R
o
s
s
Hannan,
H
a
n
n
a
n
,
Sigma
S
i
g
m
a
Associates
A
s
s
o
c
i
a
t
e
s
(Aerospace)
(
A
e
r
o
s
p
a
c
e
)
SG-2
S
G
-
2
Co-chair
C
o
-
c
h
a
i
r
Mike
M
i
k
e
DeWalt,
D
e
W
a
l
t
,
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Services,
S
e
r
v
i
c
e
s
,
Inc./FAA
I
n
c
.
/
F
A
A
SG-2
S
G
-
2
Co-chair
C
o
-
c
h
a
i
r
(until
(
u
n
t
i
l
March
M
a
r
c
h
2008)
2
0
0
8
)
Will
W
i
l
l
Struck,
S
t
r
u
c
k
,
FAA
F
A
A
SG-2
S
G
-
2
Co-chair
C
o
-
c
h
a
i
r
(until
(
u
n
t
i
l
March
M
a
r
c
h
2009)
2
0
0
9
)
Fred
F
r
e
d
Moyer,
M
o
y
e
r
,
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
SG-2
S
G
-
2
Co-chair
C
o
-
c
h
a
i
r
(from
(
f
r
o
m
April
A
p
r
i
l
2009)
2
0
0
9
)
John
J
o
h
n
Angermayer,
A
n
g
e
r
m
a
y
e
r
,
Mitre
M
i
t
r
e
SG-2
S
G
-
2
Secretary
S
e
c
r
e
t
a
r
y
SG-3
S
G
-
3
–
–
Tool
T
o
o
l
Qualification
Q
u
a
l
i
f
i
c
a
t
i
o
n
Frédéric
F
r
é
d
é
r
i
c
Pothon,
P
o
t
h
o
n
,
ACG
A
C
G
Solutions
S
o
l
u
t
i
o
n
s
SG-3
S
G
-
3
Co-chair
C
o
-
c
h
a
i
r
Leanna
L
e
a
n
n
a
Rierson,
R
i
e
r
s
o
n
,
Digital
D
i
g
i
t
a
l
Safety
S
a
f
e
t
y
Consulting
C
o
n
s
u
l
t
i
n
g
SG-3
S
G
-
3
Co-chair
C
o
-
c
h
a
i
r
Bernard
B
e
r
n
a
r
d
Dion,
D
i
o
n
,
Esterel
E
s
t
e
r
e
l
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
SG-3
S
G
-
3
Co-secretary
C
o
-
s
e
c
r
e
t
a
r
y
Gene
G
e
n
e
Kelly,
K
e
l
l
y
,
CertTech
C
e
r
t
T
e
c
h
SG-3
S
G
-
3
Co-secretary
C
o
-
s
e
c
r
e
t
a
r
y
(until
(
u
n
t
i
l
May
M
a
y
2009)
2
0
0
9
)
Mo
M
o
Piper,
P
i
p
e
r
,
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
SG-3
S
G
-
3
Co-secretary
C
o
-
s
e
c
r
e
t
a
r
y
(from
(
f
r
o
m
May
M
a
y
2009)
2
0
0
9
)
SG-4
S
G
-
4
–
–
Model-Based
M
o
d
e
l
-
B
a
s
e
d
Development
D
e
v
e
l
o
p
m
e
n
t
and
a
n
d
Verification
V
e
r
i
f
i
c
a
t
i
o
n
Pierre
P
i
e
r
r
e
Lionne,
L
i
o
n
n
e
,
EADS
E
A
D
S
APSYS
A
P
S
Y
S
SG-4
S
G
-
4
Co-chair
C
o
-
c
h
a
i
r
Mark
M
a
r
k
Lillis,
L
i
l
l
i
s
,
Goodrich
G
o
o
d
r
i
c
h
GPECS
G
P
E
C
S
SG-4
S
G
-
4
Co-chair
C
o
-
c
h
a
i
r
Hervé
H
e
r
v
é
Delseny,
D
e
l
s
e
n
y
,
Airbus
A
i
r
b
u
s
SG-4
S
G
-
4
Co-chair
C
o
-
c
h
a
i
r
Martha
M
a
r
t
h
a
Blankenberger,
B
l
a
n
k
e
n
b
e
r
g
e
r
,
Rolls-Royce
R
o
l
l
s
-
R
o
y
c
e
SG-4
S
G
-
4
Secretary
S
e
c
r
e
t
a
r
y
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-2
B
-
2
SG-5
S
G
-
5
–
–
Object-Oriented
O
b
j
e
c
t
-
O
r
i
e
n
t
e
d
Technology
T
e
c
h
n
o
l
o
g
y
Peter
P
e
t
e
r
Heller,
H
e
l
l
e
r
,
Airbus
A
i
r
b
u
s
Operations
O
p
e
r
a
t
i
o
n
s
GmbH
G
m
b
H
SG-5
S
G
-
5
Co-chair
C
o
-
c
h
a
i
r
(until
(
u
n
t
i
l
February
F
e
b
r
u
a
r
y
2009)
2
0
0
9
)
Jan-Hendrik
J
a
n
-
H
e
n
d
r
i
k
Boelens,
B
o
e
l
e
n
s
,
Eurocopter
E
u
r
o
c
o
p
t
e
r
SG-5
S
G
-
5
Co-chair
C
o
-
c
h
a
i
r
(Feb
(
F
e
b
2009
2
0
0
9
to
t
o
August
A
u
g
u
s
t
2010)
2
0
1
0
)
James
J
a
m
e
s
Hunt,
H
u
n
t
,
aicas
a
i
c
a
s
SG-5
S
G
-
5
Co-chair
C
o
-
c
h
a
i
r
(from
(
f
r
o
m
August
A
u
g
u
s
t
2010)
2
0
1
0
)
Jim
J
i
m
Chelini,
C
h
e
l
i
n
i
,
Verocel
V
e
r
o
c
e
l
SG-5
S
G
-
5
Co-chair
C
o
-
c
h
a
i
r
(until
(
u
n
t
i
l
Oct
O
c
t
2009)
2
0
0
9
)
Greg
G
r
e
g
Millican,
M
i
l
l
i
c
a
n
,
Honeywell
H
o
n
e
y
w
e
l
l
SG-5
S
G
-
5
Co-chair
C
o
-
c
h
a
i
r
(Oct
(
O
c
t
2009
2
0
0
9
to
t
o
August
A
u
g
u
s
t
2011)
2
0
1
1
)
Jim
J
i
m
Chelini,
C
h
e
l
i
n
i
,
Verocel
V
e
r
o
c
e
l
SG-5
S
G
-
5
Co-chair
C
o
-
c
h
a
i
r
(from
(
f
r
o
m
August
A
u
g
u
s
t
2011)
2
0
1
1
)
SG-6
S
G
-
6
–
–
Formal
F
o
r
m
a
l
Methods
M
e
t
h
o
d
s
Duncan
D
u
n
c
a
n
Brown,
B
r
o
w
n
,
Aero
A
e
r
o
Engine
E
n
g
i
n
e
Controls
C
o
n
t
r
o
l
s
(Rolls-Royce)
(
R
o
l
l
s
-
R
o
y
c
e
)
SG-6
S
G
-
6
Co-chair
C
o
-
c
h
a
i
r
Kelly
K
e
l
l
y
Hayhurst,
H
a
y
h
u
r
s
t
,
NASA
N
A
S
A
SG-6
S
G
-
6
Co-chair
C
o
-
c
h
a
i
r
SG-7
S
G
-
7
–
–
Special
S
p
e
c
i
a
l
Considerations
C
o
n
s
i
d
e
r
a
t
i
o
n
s
and
a
n
d
CNS/ATM
C
N
S
/
A
T
M
David
D
a
v
i
d
Hawken,
H
a
w
k
e
n
,
NATS
N
A
T
S
SG-7
S
G
-
7
Co-chair
C
o
-
c
h
a
i
r
(until
(
u
n
t
i
l
June
J
u
n
e
2010)
2
0
1
0
)
Jim
J
i
m
Stewart,
S
t
e
w
a
r
t
,
NATS
N
A
T
S
SG-7
S
G
-
7
Co-chair
C
o
-
c
h
a
i
r
(from
(
f
r
o
m
June
J
u
n
e
2010)
2
0
1
0
)
Don
D
o
n
Heck,
H
e
c
k
,
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
SG-7
S
G
-
7
Co-chair
C
o
-
c
h
a
i
r
Leslie
L
e
s
l
i
e
Alford,
A
l
f
o
r
d
,
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
SG-7
S
G
-
7
Secretary
S
e
c
r
e
t
a
r
y
(until
(
u
n
t
i
l
March
M
a
r
c
h
2008)
2
0
0
8
)
Marguerite
M
a
r
g
u
e
r
i
t
e
Baier,
B
a
i
e
r
,
Honeywell
H
o
n
e
y
w
e
l
l
SG-7
S
G
-
7
Secretary
S
e
c
r
e
t
a
r
y
(from
(
f
r
o
m
March
M
a
r
c
h
2008)
2
0
0
8
)
RTCA
R
T
C
A
Representative:
R
e
p
r
e
s
e
n
t
a
t
i
v
e
:
Rudy
R
u
d
y
Ruana
R
u
a
n
a
RTCA
R
T
C
A
Inc.
I
n
c
.
(until
(
u
n
t
i
l
September
S
e
p
t
e
m
b
e
r
2009)
2
0
0
9
)
Ray
R
a
y
Glennon
G
l
e
n
n
o
n
RTCA
R
T
C
A
Inc.
I
n
c
.
(until
(
u
n
t
i
l
March
M
a
r
c
h
2010)
2
0
1
0
)
Hal
H
a
l
Moses
M
o
s
e
s
RTCA
R
T
C
A
Inc.
I
n
c
.
(until
(
u
n
t
i
l
August
A
u
g
u
s
t
2010)
2
0
1
0
)
Cyndy
C
y
n
d
y
Brown
B
r
o
w
n
RTCA
R
T
C
A
Inc.
I
n
c
.
(until
(
u
n
t
i
l
August
A
u
g
u
s
t
2011)
2
0
1
1
)
Hal
H
a
l
Moses
M
o
s
e
s
RTCA
R
T
C
A
Inc.
I
n
c
.
(from
(
f
r
o
m
August
A
u
g
u
s
t
2011)
2
0
1
1
)
EUROCAE
E
U
R
O
C
A
E
Representative:
R
e
p
r
e
s
e
n
t
a
t
i
v
e
:
Gilbert
G
i
l
b
e
r
t
Amato
A
m
a
t
o
EUROCAE
E
U
R
O
C
A
E
(until
(
u
n
t
i
l
September
S
e
p
t
e
m
b
e
r
2009)
2
0
0
9
)
Roland
R
o
l
a
n
d
Mallwitz
M
a
l
l
w
i
t
z
EUROCAE
E
U
R
O
C
A
E
(from
(
f
r
o
m
October
O
c
t
o
b
e
r
2009)
2
0
0
9
)
EDITORIAL
E
D
I
T
O
R
I
A
L
COMMITTEE
C
O
M
M
I
T
T
E
E
Leanna
L
e
a
n
n
a
Rierson,
R
i
e
r
s
o
n
,
Digital
D
i
g
i
t
a
l
Safety
S
a
f
e
t
y
Consulting
C
o
n
s
u
l
t
i
n
g
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Chair
C
h
a
i
r
Ron
R
o
n
Ashpole,
A
s
h
p
o
l
e
,
SILVER
S
I
L
V
E
R
ATENA
A
T
E
N
A
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Alex
A
l
e
x
Ayzenberg,
A
y
z
e
n
b
e
r
g
,
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Patty
P
a
t
t
y
(Bartels)
(
B
a
r
t
e
l
s
)
Bath,
B
a
t
h
,
Esterline
E
s
t
e
r
l
i
n
e
AVISTA
A
V
I
S
T
A
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Dewi
D
e
w
i
Daniels,
D
a
n
i
e
l
s
,
Verocel
V
e
r
o
c
e
l
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Hervé
H
e
r
v
é
Delseny,
D
e
l
s
e
n
y
,
Airbus
A
i
r
b
u
s
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Andrew
A
n
d
r
e
w
Elliott,
E
l
l
i
o
t
t
,
Design
D
e
s
i
g
n
Assurance
A
s
s
u
r
a
n
c
e
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Kelly
K
e
l
l
y
Hayhurst,
H
a
y
h
u
r
s
t
,
NASA
N
A
S
A
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Barbara
B
a
r
b
a
r
a
Lingberg,
L
i
n
g
b
e
r
g
,
FAA
F
A
A
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Steven
S
t
e
v
e
n
C.
C
.
Martz,
M
a
r
t
z
,
Garmin
G
a
r
m
i
n
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Steve
S
t
e
v
e
Morton,
M
o
r
t
o
n
,
TBV
T
B
V
Associates
A
s
s
o
c
i
a
t
e
s
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
Marge
M
a
r
g
e
Sonnek,
S
o
n
n
e
k
,
Honeywell
H
o
n
e
y
w
e
l
l
Editorial
E
d
i
t
o
r
i
a
l
Committee
C
o
m
m
i
t
t
e
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-3
B
-
3
COMMITTEE
C
O
M
M
I
T
T
E
E
MEMBERSHIP
M
E
M
B
E
R
S
H
I
P
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Kyle
K
y
l
e
Achenbach
A
c
h
e
n
b
a
c
h
Rolls-Royce
R
o
l
l
s
-
R
o
y
c
e
Dana
D
a
n
a
E.
E
.
Adkins
A
d
k
i
n
s
Kidde
K
i
d
d
e
Aerospace
A
e
r
o
s
p
a
c
e
Leslie
L
e
s
l
i
e
Alford
A
l
f
o
r
d
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Carlo
C
a
r
l
o
Amalfitano
A
m
a
l
f
i
t
a
n
o
Certon
C
e
r
t
o
n
Software,
S
o
f
t
w
a
r
e
,
Inc
I
n
c
Gilbert
G
i
l
b
e
r
t
Amato
A
m
a
t
o
EUROCAE
E
U
R
O
C
A
E
Peter
P
e
t
e
r
Amey
A
m
e
y
Praxis
P
r
a
x
i
s
High
H
i
g
h
Integrity
I
n
t
e
g
r
i
t
y
Systems
S
y
s
t
e
m
s
Robert
R
o
b
e
r
t
Annis
A
n
n
i
s
GE
G
E
Aviation
A
v
i
a
t
i
o
n
Allan
A
l
l
a
n
Gilmour
G
i
l
m
o
u
r
Anderson
A
n
d
e
r
s
o
n
Embraer
E
m
b
r
a
e
r
Håkan
H
å
k
a
n
Anderwall
A
n
d
e
r
w
a
l
l
Saab
S
a
a
b
AB
A
B
Joseph
J
o
s
e
p
h
Angelo
A
n
g
e
l
o
NovAtel
N
o
v
A
t
e
l
Inc,
I
n
c
,
Canada
C
a
n
a
d
a
John
J
o
h
n
Charles
C
h
a
r
l
e
s
Angermayer
A
n
g
e
r
m
a
y
e
r
Mitre
M
i
t
r
e
Corp
C
o
r
p
Ron
R
o
n
Ashpole
A
s
h
p
o
l
e
SILVER
S
I
L
V
E
R
ATENA
A
T
E
N
A
Alex
A
l
e
x
Ayzenberg
A
y
z
e
n
b
e
r
g
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Marguerite
M
a
r
g
u
e
r
i
t
e
Baier
B
a
i
e
r
Honeywell
H
o
n
e
y
w
e
l
l
Fred
F
r
e
d
Barber
B
a
r
b
e
r
Avidyne
A
v
i
d
y
n
e
Clay
C
l
a
y
Barber
B
a
r
b
e
r
Garmin
G
a
r
m
i
n
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Gerald
G
e
r
a
l
d
F.
F
.
Barofsky
B
a
r
o
f
s
k
y
L-3
L
-
3
Communications
C
o
m
m
u
n
i
c
a
t
i
o
n
s
Patty
P
a
t
t
y
(Bartels)
(
B
a
r
t
e
l
s
)
Bath
B
a
t
h
Esterline
E
s
t
e
r
l
i
n
e
AVISTA
A
V
I
S
T
A
Brigitte
B
r
i
g
i
t
t
e
Bauer
B
a
u
e
r
Thales
T
h
a
l
e
s
Phillipe
P
h
i
l
l
i
p
e
Baufreton
B
a
u
f
r
e
t
o
n
SAGEM
S
A
G
E
M
DS
D
S
Safran
S
a
f
r
a
n
Group
G
r
o
u
p
Connie
C
o
n
n
i
e
Beane
B
e
a
n
e
ENEA
E
N
E
A
Embedded
E
m
b
e
d
d
e
d
Technology
T
e
c
h
n
o
l
o
g
y
Inc
I
n
c
Bernard
B
e
r
n
a
r
d
Beaudouin
B
e
a
u
d
o
u
i
n
EADS
E
A
D
S
APSYS
A
P
S
Y
S
Germain
G
e
r
m
a
i
n
Beaulieu
B
e
a
u
l
i
e
u
Independent
I
n
d
e
p
e
n
d
e
n
t
Consultant
C
o
n
s
u
l
t
a
n
t
Martin
M
a
r
t
i
n
Beeby
B
e
e
b
y
Seaweed
S
e
a
w
e
e
d
Systems
S
y
s
t
e
m
s
Scott
S
c
o
t
t
Beecher
B
e
e
c
h
e
r
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
Haik
H
a
i
k
Biglari
B
i
g
l
a
r
i
Fairchild
F
a
i
r
c
h
i
l
d
Controls
C
o
n
t
r
o
l
s
Peter
P
e
t
e
r
Billing
B
i
l
l
i
n
g
Aviya
A
v
i
y
a
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Inc
I
n
c
Denise
D
e
n
i
s
e
Black
B
l
a
c
k
Embedded
E
m
b
e
d
d
e
d
Plus
P
l
u
s
Engineering
E
n
g
i
n
e
e
r
i
n
g
Brad
B
r
a
d
Blackhurst
B
l
a
c
k
h
u
r
s
t
Independent
I
n
d
e
p
e
n
d
e
n
t
Consultant
C
o
n
s
u
l
t
a
n
t
Craig
C
r
a
i
g
Bladow
B
l
a
d
o
w
Woodward
W
o
o
d
w
a
r
d
Martha
M
a
r
t
h
a
Blankenberger
B
l
a
n
k
e
n
b
e
r
g
e
r
Rolls-Royce
R
o
l
l
s
-
R
o
y
c
e
Holger
H
o
l
g
e
r
Blasum
B
l
a
s
u
m
SYSGO
S
Y
S
G
O
Thomas
T
h
o
m
a
s
Bleichner
B
l
e
i
c
h
n
e
r
Rohde
R
o
h
d
e
&
&
Schwarz
S
c
h
w
a
r
z
Don
D
o
n
Bockenfeld
B
o
c
k
e
n
f
e
l
d
CMC
C
M
C
Electronics
E
l
e
c
t
r
o
n
i
c
s
Jan-Hendrik
J
a
n
-
H
e
n
d
r
i
k
Boelens
B
o
e
l
e
n
s
Eurocopter
E
u
r
o
c
o
p
t
e
r
Eric
E
r
i
c
Bonnafous
B
o
n
n
a
f
o
u
s
CommunicationSys
C
o
m
m
u
n
i
c
a
t
i
o
n
S
y
s
Jean-Christophe
J
e
a
n
-
C
h
r
i
s
t
o
p
h
e
Bonnet
B
o
n
n
e
t
CEAT
C
E
A
T
Hugues
H
u
g
u
e
s
Bonnin
B
o
n
n
i
n
Cap
C
a
p
Gemini
G
e
m
i
n
i
Matteo
M
a
t
t
e
o
Bordin
B
o
r
d
i
n
AdaCore
A
d
a
C
o
r
e
Feliks
F
e
l
i
k
s
Bortkiewicz
B
o
r
t
k
i
e
w
i
c
z
Boeing
B
o
e
i
n
g
Julien
J
u
l
i
e
n
Bourdeau
B
o
u
r
d
e
a
u
DND
D
N
D
(Canada)
(
C
a
n
a
d
a
)
Paul
P
a
u
l
Bousquet
B
o
u
s
q
u
e
t
Volpe
V
o
l
p
e
National
N
a
t
i
o
n
a
l
Transportation
T
r
a
n
s
p
o
r
t
a
t
i
o
n
Systems
S
y
s
t
e
m
s
Center
C
e
n
t
e
r
David
D
a
v
i
d
Bowen
B
o
w
e
n
EUROCAE
E
U
R
O
C
A
E
Elizabeth
E
l
i
z
a
b
e
t
h
Brandli
B
r
a
n
d
l
i
FAA
F
A
A
Andrew
A
n
d
r
e
w
Bridge
B
r
i
d
g
e
EASA
E
A
S
A
Paul
P
a
u
l
Brook
B
r
o
o
k
Thales
T
h
a
l
e
s
Daryl
D
a
r
y
l
Brooke
B
r
o
o
k
e
Universal
U
n
i
v
e
r
s
a
l
Avionics
A
v
i
o
n
i
c
s
Systems
S
y
s
t
e
m
s
Corporation
C
o
r
p
o
r
a
t
i
o
n
Cyndy
C
y
n
d
y
Brown
B
r
o
w
n
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
Duncan
D
u
n
c
a
n
Brown
B
r
o
w
n
Aero
A
e
r
o
Engine
E
n
g
i
n
e
Controls
C
o
n
t
r
o
l
s
(Rolls-Royce)
(
R
o
l
l
s
-
R
o
y
c
e
)
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-4
B
-
4
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Thomas
T
h
o
m
a
s
Buchberger
B
u
c
h
b
e
r
g
e
r
Siemens
S
i
e
m
e
n
s
AG
A
G
Brett
B
r
e
t
t
Burgeles
B
u
r
g
e
l
e
s
Consultant
C
o
n
s
u
l
t
a
n
t
Bernard
B
e
r
n
a
r
d
Buscail
B
u
s
c
a
i
l
Airbus
A
i
r
b
u
s
Bob
B
o
b
Busser
B
u
s
s
e
r
Systems
S
y
s
t
e
m
s
and
a
n
d
Software
S
o
f
t
w
a
r
e
Consortium
C
o
n
s
o
r
t
i
u
m
Christopher
C
h
r
i
s
t
o
p
h
e
r
Caines
C
a
i
n
e
s
QinetiQ
Q
i
n
e
t
i
Q
Cristiano
C
r
i
s
t
i
a
n
o
Campos
C
a
m
p
o
s
Almeida
A
l
m
e
i
d
a
De
D
e
Freitas
F
r
e
i
t
a
s
Embraer
E
m
b
r
a
e
r
Jean-Louis
J
e
a
n
-
L
o
u
i
s
Camus
C
a
m
u
s
Esterel
E
s
t
e
r
e
l
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Richard
R
i
c
h
a
r
d
Canis
C
a
n
i
s
EASA
E
A
S
A
Yann
Y
a
n
n
Carlier
C
a
r
l
i
e
r
DGAC
D
G
A
C
Luc
L
u
c
Casagrande
C
a
s
a
g
r
a
n
d
e
EADS
E
A
D
S
Apsys
A
p
s
y
s
Mark
M
a
r
k
Chapman
C
h
a
p
m
a
n
Hamilton
H
a
m
i
l
t
o
n
Sundstrand
S
u
n
d
s
t
r
a
n
d
Scott
S
c
o
t
t
Chapman
C
h
a
p
m
a
n
FAA
F
A
A
Jim
J
i
m
Chelini
C
h
e
l
i
n
i
Verocel
V
e
r
o
c
e
l
Daniel
D
a
n
i
e
l
Chevallier
C
h
e
v
a
l
l
i
e
r
Thales
T
h
a
l
e
s
John
J
o
h
n
Chilenski
C
h
i
l
e
n
s
k
i
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Subbiah
S
u
b
b
i
a
h
Chockalingam
C
h
o
c
k
a
l
i
n
g
a
m
HCL
H
C
L
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Chris
C
h
r
i
s
Clark
C
l
a
r
k
Sysgo
S
y
s
g
o
Darren
D
a
r
r
e
n
Cofer
C
o
f
e
r
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Keith
K
e
i
t
h
Coffman
C
o
f
f
m
a
n
Goodrich
G
o
o
d
r
i
c
h
John
J
o
h
n
Coleman
C
o
l
e
m
a
n
Dawson
D
a
w
s
o
n
Consulting
C
o
n
s
u
l
t
i
n
g
Cyrille
C
y
r
i
l
l
e
Comar
C
o
m
a
r
AdaCore
A
d
a
C
o
r
e
Ray
R
a
y
Conrad
C
o
n
r
a
d
Lockheed
L
o
c
k
h
e
e
d
Martin
M
a
r
t
i
n
Mirko
M
i
r
k
o
Conrad
C
o
n
r
a
d
The
T
h
e
MathWorks,
M
a
t
h
W
o
r
k
s
,
Inc.
I
n
c
.
Nathalie
N
a
t
h
a
l
i
e
Corbovianu
C
o
r
b
o
v
i
a
n
u
DGAC
D
G
A
C
Ana
A
n
a
Costanti
C
o
s
t
a
n
t
i
Embraer
E
m
b
r
a
e
r
Dewi
D
e
w
i
Daniels
D
a
n
i
e
l
s
Verocel
V
e
r
o
c
e
l
Eric
E
r
i
c
Danielson
D
a
n
i
e
l
s
o
n
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Henri
H
e
n
r
i
De
D
e
La
L
a
Vallée
V
a
l
l
é
e
Poussin
P
o
u
s
s
i
n
SABCA
S
A
B
C
A
Michael
M
i
c
h
a
e
l
Deitz
D
e
i
t
z
Gentex
G
e
n
t
e
x
Corporation
C
o
r
p
o
r
a
t
i
o
n
Jean-Luc
J
e
a
n
-
L
u
c
Delamaide
D
e
l
a
m
a
i
d
e
EASA
E
A
S
A
Hervé
H
e
r
v
é
Delseny
D
e
l
s
e
n
y
Airbus
A
i
r
b
u
s
Patrick
P
a
t
r
i
c
k
Desbiens
D
e
s
b
i
e
n
s
Transport
T
r
a
n
s
p
o
r
t
Canada
C
a
n
a
d
a
Mike
M
i
k
e
DeWalt
D
e
W
a
l
t
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Services,
S
e
r
v
i
c
e
s
,
Inc./FAA
I
n
c
.
/
F
A
A
Mansur
M
a
n
s
u
r
Dewshi
D
e
w
s
h
i
Ultra
U
l
t
r
a
Electronics
E
l
e
c
t
r
o
n
i
c
s
Controls
C
o
n
t
r
o
l
s
Bernard
B
e
r
n
a
r
d
Dion
D
i
o
n
Esterel
E
s
t
e
r
e
l
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Antonio
A
n
t
o
n
i
o
Jose
J
o
s
e
Vitorio
V
i
t
o
r
i
o
Domiciano
D
o
m
i
c
i
a
n
o
Embraer
E
m
b
r
a
e
r
Kurt
K
u
r
t
Doppelbauer
D
o
p
p
e
l
b
a
u
e
r
TTTech
T
T
T
e
c
h
Cheryl
C
h
e
r
y
l
Dorsey
D
o
r
s
e
y
Digital
D
i
g
i
t
a
l
Flight
F
l
i
g
h
t
Rick
R
i
c
k
Dorsey
D
o
r
s
e
y
Digital
D
i
g
i
t
a
l
Flight
F
l
i
g
h
t
John
J
o
h
n
Doughty
D
o
u
g
h
t
y
Garmin
G
a
r
m
i
n
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Vincent
V
i
n
c
e
n
t
Dovydaitis
D
o
v
y
d
a
i
t
i
s
III
I
I
I
Foliage
F
o
l
i
a
g
e
Software
S
o
f
t
w
a
r
e
Systems,
S
y
s
t
e
m
s
,
Inc.
I
n
c
.
Georges
G
e
o
r
g
e
s
Duchein
D
u
c
h
e
i
n
DGA
D
G
A
Branimir
B
r
a
n
i
m
i
r
Dulic
D
u
l
i
c
Transport
T
r
a
n
s
p
o
r
t
Canada
C
a
n
a
d
a
Gilles
G
i
l
l
e
s
Dulon
D
u
l
o
n
SAGEM
S
A
G
E
M
DS
D
S
Safran
S
a
f
r
a
n
Group
G
r
o
u
p
Paul
P
a
u
l
Dunn
D
u
n
n
Northrop
N
o
r
t
h
r
o
p
Grumman
G
r
u
m
m
a
n
Corporation
C
o
r
p
o
r
a
t
i
o
n
Andrew
A
n
d
r
e
w
Eaton
E
a
t
o
n
UK
U
K
CAA
C
A
A
Brian
B
r
i
a
n
Eckmann
E
c
k
m
a
n
n
Universal
U
n
i
v
e
r
s
a
l
Avionics
A
v
i
o
n
i
c
s
Systems
S
y
s
t
e
m
s
Corporation
C
o
r
p
o
r
a
t
i
o
n
Vladimir
V
l
a
d
i
m
i
r
Eliseev
E
l
i
s
e
e
v
Sukhoi
S
u
k
h
o
i
Civil
C
i
v
i
l
Aircraft
A
i
r
c
r
a
f
t
Company
C
o
m
p
a
n
y
(SCAC)
(
S
C
A
C
)
Andrew
A
n
d
r
e
w
Elliott
E
l
l
i
o
t
t
Design
D
e
s
i
g
n
Assurance
A
s
s
u
r
a
n
c
e
Mike
M
i
k
e
Elliott
E
l
l
i
o
t
t
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Joao
J
o
a
o
Esteves
E
s
t
e
v
e
s
Critical
C
r
i
t
i
c
a
l
Software
S
o
f
t
w
a
r
e
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-5
B
-
5
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Rowland
R
o
w
l
a
n
d
Evans
E
v
a
n
s
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
Canada
C
a
n
a
d
a
Louis
L
o
u
i
s
Fabre
F
a
b
r
e
Eurocopter
E
u
r
o
c
o
p
t
e
r
Martin
M
a
r
t
i
n
Fassl
F
a
s
s
l
Siemens
S
i
e
m
e
n
s
AG
A
G
Michael
M
i
c
h
a
e
l
Fee
F
e
e
Aero
A
e
r
o
Engine
E
n
g
i
n
e
Controls
C
o
n
t
r
o
l
s
(Rolls-Royce)
(
R
o
l
l
s
-
R
o
y
c
e
)
Tom
T
o
m
Ferrell
F
e
r
r
e
l
l
Ferrell
F
e
r
r
e
l
l
and
a
n
d
Associates
A
s
s
o
c
i
a
t
e
s
Consulting
C
o
n
s
u
l
t
i
n
g
Uma
U
m
a
Ferrell
F
e
r
r
e
l
l
Ferrell
F
e
r
r
e
l
l
and
a
n
d
Associates
A
s
s
o
c
i
a
t
e
s
Consulting
C
o
n
s
u
l
t
i
n
g
Lou
L
o
u
Fisk
F
i
s
k
GE
G
E
Aviation
A
v
i
a
t
i
o
n
Ade
A
d
e
Fountain
F
o
u
n
t
a
i
n
Penny
P
e
n
n
y
and
a
n
d
Giles
G
i
l
e
s
Claude
C
l
a
u
d
e
Fournier
F
o
u
r
n
i
e
r
Liebherr
L
i
e
b
h
e
r
r
Pierre
P
i
e
r
r
e
Francine
F
r
a
n
c
i
n
e
Thales
T
h
a
l
e
s
Timothy
T
i
m
o
t
h
y
Frey
F
r
e
y
Honeywell
H
o
n
e
y
w
e
l
l
Stephen
S
t
e
p
h
e
n
J.
J
.
Fridrick
F
r
i
d
r
i
c
k
GE
G
E
Aviation
A
v
i
a
t
i
o
n
Leonard
L
e
o
n
a
r
d
Fulcher
F
u
l
c
h
e
r
TTTech
T
T
T
e
c
h
Randall
R
a
n
d
a
l
l
Fulton
F
u
l
t
o
n
Seaweed
S
e
a
w
e
e
d
Systems
S
y
s
t
e
m
s
Francoise
F
r
a
n
c
o
i
s
e
Gachet
G
a
c
h
e
t
Dassault-Aviation
D
a
s
s
a
u
l
t
-
A
v
i
a
t
i
o
n
Victor
V
i
c
t
o
r
Galushkin
G
a
l
u
s
h
k
i
n
GosNIIAS
G
o
s
N
I
I
A
S
Marty
M
a
r
t
y
Gasiorowski
G
a
s
i
o
r
o
w
s
k
i
Worldwide
W
o
r
l
d
w
i
d
e
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Services
S
e
r
v
i
c
e
s
Stephanie
S
t
e
p
h
a
n
i
e
Gaudan
G
a
u
d
a
n
Thales
T
h
a
l
e
s
Jean-Louis
J
e
a
n
-
L
o
u
i
s
Gebel
G
e
b
e
l
Airbus
A
i
r
b
u
s
Dries
D
r
i
e
s
Geldof
G
e
l
d
o
f
BARCO
B
A
R
C
O
Dimitri
D
i
m
i
t
r
i
Gianesini
G
i
a
n
e
s
i
n
i
Airbus
A
i
r
b
u
s
Jim
J
i
m
Gibbons
G
i
b
b
o
n
s
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Dara
D
a
r
a
Gibson
G
i
b
s
o
n
FAA
F
A
A
Greg
G
r
e
g
Gicca
G
i
c
c
a
AdaCore
A
d
a
C
o
r
e
Steven
S
t
e
v
e
n
Gitelis
G
i
t
e
l
i
s
Lumina
L
u
m
i
n
a
Engineering
E
n
g
i
n
e
e
r
i
n
g
Ian
I
a
n
Glazebrook
G
l
a
z
e
b
r
o
o
k
WS
W
S
Atkins
A
t
k
i
n
s
Santiago
S
a
n
t
i
a
g
o
Golmayo
G
o
l
m
a
y
o
GMV
G
M
V
SA
S
A
Ben
B
e
n
Gorry
G
o
r
r
y
British
B
r
i
t
i
s
h
Aerospace
A
e
r
o
s
p
a
c
e
Systems
S
y
s
t
e
m
s
Florian
F
l
o
r
i
a
n
Gouleau
G
o
u
l
e
a
u
DGA
D
G
A
Techniques
T
e
c
h
n
i
q
u
e
s
Aéronautiques
A
é
r
o
n
a
u
t
i
q
u
e
s
Olivier
O
l
i
v
i
e
r
Graff
G
r
a
f
f
Intertechnique
I
n
t
e
r
t
e
c
h
n
i
q
u
e
-
-
Zodiac
Z
o
d
i
a
c
Russell
R
u
s
s
e
l
l
DeLoy
D
e
L
o
y
Graham
G
r
a
h
a
m
Garmin
G
a
r
m
i
n
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Robert
R
o
b
e
r
t
Green
G
r
e
e
n
BAE
B
A
E
Systems
S
y
s
t
e
m
s
Mark
M
a
r
k
Grindle
G
r
i
n
d
l
e
Systems
S
y
s
t
e
m
s
Enginuity
E
n
g
i
n
u
i
t
y
Peter
P
e
t
e
r
Grossinger
G
r
o
s
s
i
n
g
e
r
Pilatus
P
i
l
a
t
u
s
Aircraft
A
i
r
c
r
a
f
t
Mark
M
a
r
k
Gulick
G
u
l
i
c
k
Solers,
S
o
l
e
r
s
,
Inc.
I
n
c
.
Pierre
P
i
e
r
r
e
Guyot
G
u
y
o
t
Dassault
D
a
s
s
a
u
l
t
Aviation
A
v
i
a
t
i
o
n
Ibrahim
I
b
r
a
h
i
m
Habli
H
a
b
l
i
University
U
n
i
v
e
r
s
i
t
y
of
o
f
York
Y
o
r
k
Ross
R
o
s
s
Hannan
H
a
n
n
a
n
Sigma
S
i
g
m
a
Associates
A
s
s
o
c
i
a
t
e
s
(Aerospace)
(
A
e
r
o
s
p
a
c
e
)
Limited
L
i
m
i
t
e
d
Christopher
C
h
r
i
s
t
o
p
h
e
r
H.
H
.
Hansen
H
a
n
s
e
n
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Wue
W
u
e
Hao
H
a
o
Wen
W
e
n
Civil
C
i
v
i
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
of
o
f
China
C
h
i
n
a
(CAAC)
(
C
A
A
C
)
Keith
K
e
i
t
h
Harrison
H
a
r
r
i
s
o
n
HVR
H
V
R
Consulting
C
o
n
s
u
l
t
i
n
g
Services
S
e
r
v
i
c
e
s
Ltd
L
t
d
Bjorn
B
j
o
r
n
Hasselqvist
H
a
s
s
e
l
q
v
i
s
t
Saab
S
a
a
b
AB
A
B
Kevin
K
e
v
i
n
Hathaway
H
a
t
h
a
w
a
y
Aero
A
e
r
o
Engine
E
n
g
i
n
e
Controls
C
o
n
t
r
o
l
s
(Goodrich)
(
G
o
o
d
r
i
c
h
)
David
D
a
v
i
d
Hawken
H
a
w
k
e
n
NATS
N
A
T
S
Kelly
K
e
l
l
y
Hayhurst
H
a
y
h
u
r
s
t
NASA
N
A
S
A
Peter
P
e
t
e
r
Heath
H
e
a
t
h
Securaplane
S
e
c
u
r
a
p
l
a
n
e
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Myron
M
y
r
o
n
Hecht
H
e
c
h
t
Aerospace
A
e
r
o
s
p
a
c
e
Corporation
C
o
r
p
o
r
a
t
i
o
n
Don
D
o
n
Heck
H
e
c
k
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Peter
P
e
t
e
r
Heller
H
e
l
l
e
r
Airbus
A
i
r
b
u
s
Operations
O
p
e
r
a
t
i
o
n
s
GmbH
G
m
b
H
Barry
B
a
r
r
y
Hendrix
H
e
n
d
r
i
x
Lockheed
L
o
c
k
h
e
e
d
Martin
M
a
r
t
i
n
Michael
M
i
c
h
a
e
l
Hennell
H
e
n
n
e
l
l
LDRA
L
D
R
A
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-6
B
-
6
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Michael
M
i
c
h
a
e
l
Herring
H
e
r
r
i
n
g
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Ruth
R
u
t
h
Hirt
H
i
r
t
FAA
F
A
A
Kent
K
e
n
t
Hollinger
H
o
l
l
i
n
g
e
r
Mitre
M
i
t
r
e
Corp
C
o
r
p
C.
C
.
Michael
M
i
c
h
a
e
l
Holloway
H
o
l
l
o
w
a
y
NASA
N
A
S
A
Ian
I
a
n
Hopkins
H
o
p
k
i
n
s
Aero
A
e
r
o
Engine
E
n
g
i
n
e
Controls
C
o
n
t
r
o
l
s
(Rolls-Royce)
(
R
o
l
l
s
-
R
o
y
c
e
)
Gary
G
a
r
y
Horan
H
o
r
a
n
FAA
F
A
A
Chris
C
h
r
i
s
Hote
H
o
t
e
PolySpace
P
o
l
y
S
p
a
c
e
Inc.
I
n
c
.
Susan
S
u
s
a
n
Houston
H
o
u
s
t
o
n
FAA
F
A
A
James
J
a
m
e
s
Hummell
H
u
m
m
e
l
l
Embedded
E
m
b
e
d
d
e
d
Plus
P
l
u
s
Dr.
D
r
.
James
J
a
m
e
s
J.
J
.
Hunt
H
u
n
t
aicas
a
i
c
a
s
Rebecca
R
e
b
e
c
c
a
L.
L
.
Hunt
H
u
n
t
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Stuart
S
t
u
a
r
t
Hutchesson
H
u
t
c
h
e
s
s
o
n
Aero
A
e
r
o
Engine
E
n
g
i
n
e
Controls
C
o
n
t
r
o
l
s
(Rolls-Royce)
(
R
o
l
l
s
-
R
o
y
c
e
)
Rex
R
e
x
Hyde
H
y
d
e
Moog
M
o
o
g
Inc.
I
n
c
.
Aircraft
A
i
r
c
r
a
f
t
Group
G
r
o
u
p
Mario
M
a
r
i
o
Iacobelli
I
a
c
o
b
e
l
l
i
Mannarino
M
a
n
n
a
r
i
n
o
Systems
S
y
s
t
e
m
s
Melissa
M
e
l
i
s
s
a
Isaacs
I
s
a
a
c
s
FAA
F
A
A
Vladimir
V
l
a
d
i
m
i
r
Istomin
I
s
t
o
m
i
n
Sukhoi
S
u
k
h
o
i
Civil
C
i
v
i
l
Aircraft
A
i
r
c
r
a
f
t
Company
C
o
m
p
a
n
y
(SCAC)
(
S
C
A
C
)
Stephen
S
t
e
p
h
e
n
A.
A
.
Jacklin
J
a
c
k
l
i
n
NASA
N
A
S
A
Matt
M
a
t
t
Jaffe
J
a
f
f
e
Embry-Riddle
E
m
b
r
y
-
R
i
d
d
l
e
Aeronautical
A
e
r
o
n
a
u
t
i
c
a
l
University
U
n
i
v
e
r
s
i
t
y
Marek
M
a
r
e
k
Jaglarz
J
a
g
l
a
r
z
Pilatus
P
i
l
a
t
u
s
Aircraft
A
i
r
c
r
a
f
t
Myles
M
y
l
e
s
Jalalian
J
a
l
a
l
i
a
n
FAA
F
A
A
Merlin
M
e
r
l
i
n
James
J
a
m
e
s
Garmin
G
a
r
m
i
n
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Tomas
T
o
m
a
s
Jansson
J
a
n
s
s
o
n
Saab
S
a
a
b
AB
A
B
Eric
E
r
i
c
Jenn
J
e
n
n
Thales
T
h
a
l
e
s
Lars
L
a
r
s
Johannknecht
J
o
h
a
n
n
k
n
e
c
h
t
EADS
E
A
D
S
Rikard
R
i
k
a
r
d
Johansson
J
o
h
a
n
s
s
o
n
Saab
S
a
a
b
AB
A
B
John
J
o
h
n
Jorgensen
J
o
r
g
e
n
s
e
n
Universal
U
n
i
v
e
r
s
a
l
Avionics
A
v
i
o
n
i
c
s
Systems
S
y
s
t
e
m
s
Jeffrey
J
e
f
f
r
e
y
Joyce
J
o
y
c
e
Critical
C
r
i
t
i
c
a
l
Systems
S
y
s
t
e
m
s
Labs
L
a
b
s
Chris
C
h
r
i
s
Karis
K
a
r
i
s
Ensco
E
n
s
c
o
Gene
G
e
n
e
Kelly
K
e
l
l
y
CertTech
C
e
r
t
T
e
c
h
Anne-Cécile
A
n
n
e
-
C
é
c
i
l
e
Kerbrat
K
e
r
b
r
a
t
Aeroconseil
A
e
r
o
c
o
n
s
e
i
l
Randy
R
a
n
d
y
Key
K
e
y
FAA
F
A
A
Charles
C
h
a
r
l
e
s
W.
W
.
Kilgore
K
i
l
g
o
r
e
II
I
I
FAA
F
A
A
Wayne
W
a
y
n
e
King
K
i
n
g
Honeywell
H
o
n
e
y
w
e
l
l
Daniel
D
a
n
i
e
l
Kinney
K
i
n
n
e
y
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Judith
J
u
d
i
t
h
Klein
K
l
e
i
n
Lockheed
L
o
c
k
h
e
e
d
Martin
M
a
r
t
i
n
Joachim
J
o
a
c
h
i
m
Klichert
K
l
i
c
h
e
r
t
Diehl
D
i
e
h
l
Avionik
A
v
i
o
n
i
k
Systeme
S
y
s
t
e
m
e
Jeff
J
e
f
f
Knickerbocker
K
n
i
c
k
e
r
b
o
c
k
e
r
Sunrise
S
u
n
r
i
s
e
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
&
&
Consulting,
C
o
n
s
u
l
t
i
n
g
,
Inc.
I
n
c
.
John
J
o
h
n
Knight
K
n
i
g
h
t
University
U
n
i
v
e
r
s
i
t
y
of
o
f
Virginia
V
i
r
g
i
n
i
a
Rainer
R
a
i
n
e
r
Kollner
K
o
l
l
n
e
r
Verocel
V
e
r
o
c
e
l
Andrew
A
n
d
r
e
w
Kornecki
K
o
r
n
e
c
k
i
Embry-Riddle
E
m
b
r
y
-
R
i
d
d
l
e
Aeronautical
A
e
r
o
n
a
u
t
i
c
a
l
University
U
n
i
v
e
r
s
i
t
y
Igor
I
g
o
r
Koverninskiy
K
o
v
e
r
n
i
n
s
k
i
y
Gos
G
o
s
NIIAS
N
I
I
A
S
Jim
J
i
m
Krodel
K
r
o
d
e
l
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
Paramesh
P
a
r
a
m
e
s
h
Kunda
K
u
n
d
a
Pratt
P
r
a
t
t
&
&
Whitney
W
h
i
t
n
e
y
Canada
C
a
n
a
d
a
Sylvie
S
y
l
v
i
e
Lacabanne
L
a
c
a
b
a
n
n
e
AIRBUS
A
I
R
B
U
S
Gérard
G
é
r
a
r
d
Ladier
L
a
d
i
e
r
Airbus/Aerospace
A
i
r
b
u
s
/
A
e
r
o
s
p
a
c
e
Valley
V
a
l
l
e
y
Ron
R
o
n
Lambalot
L
a
m
b
a
l
o
t
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Boris
B
o
r
i
s
Langer
L
a
n
g
e
r
Diehl
D
i
e
h
l
Aerospace
A
e
r
o
s
p
a
c
e
Susanne
S
u
s
a
n
n
e
Lanzerstorfer
L
a
n
z
e
r
s
t
o
r
f
e
r
APAC
A
P
A
C
GesmbH
G
e
s
m
b
H
Gilles
G
i
l
l
e
s
Laplane
L
a
p
l
a
n
e
SAGEM
S
A
G
E
M
DS
D
S
Safran
S
a
f
r
a
n
Group
G
r
o
u
p
Jeanne
J
e
a
n
n
e
Larsen
L
a
r
s
e
n
Hamilton
H
a
m
i
l
t
o
n
Sundstrand
S
u
n
d
s
t
r
a
n
d
Emmanuel
E
m
m
a
n
u
e
l
Ledinot
L
e
d
i
n
o
t
Dassault
D
a
s
s
a
u
l
t
Aviation
A
v
i
a
t
i
o
n
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-7
B
-
7
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Stephane
S
t
e
p
h
a
n
e
Leriche
L
e
r
i
c
h
e
Thales
T
h
a
l
e
s
Hong
H
o
n
g
Leung
L
e
u
n
g
Bell
B
e
l
l
Helicopter
H
e
l
i
c
o
p
t
e
r
Textron
T
e
x
t
r
o
n
John
J
o
h
n
Lewis
L
e
w
i
s
FAA
F
A
A
John
J
o
h
n
Li
L
i
Thales
T
h
a
l
e
s
Mark
M
a
r
k
Lillis
L
i
l
l
i
s
Goodrich
G
o
o
d
r
i
c
h
GPECS
G
P
E
C
S
Barbara
B
a
r
b
a
r
a
Lingberg
L
i
n
g
b
e
r
g
FAA
F
A
A
Pierre
P
i
e
r
r
e
Lionne
L
i
o
n
n
e
EADS
E
A
D
S
APSYS
A
P
S
Y
S
Hoyt
H
o
y
t
Lougee
L
o
u
g
e
e
Foliage
F
o
l
i
a
g
e
Software
S
o
f
t
w
a
r
e
Systems
S
y
s
t
e
m
s
Howard
H
o
w
a
r
d
Lowe
L
o
w
e
GE
G
E
Aviation
A
v
i
a
t
i
o
n
Hauke
H
a
u
k
e
Luethje
L
u
e
t
h
j
e
NewTec
N
e
w
T
e
c
GmbH
G
m
b
H
Jonathan
J
o
n
a
t
h
a
n
Lynch
L
y
n
c
h
Honeywell
H
o
n
e
y
w
e
l
l
Françoise
F
r
a
n
ç
o
i
s
e
Magliozzi
M
a
g
l
i
o
z
z
i
Atos
A
t
o
s
Origin
O
r
i
g
i
n
Veronique
V
e
r
o
n
i
q
u
e
Magnier
M
a
g
n
i
e
r
EASA
E
A
S
A
Kristine
K
r
i
s
t
i
n
e
Maine
M
a
i
n
e
Aerospace
A
e
r
o
s
p
a
c
e
Corporation
C
o
r
p
o
r
a
t
i
o
n
Didier
D
i
d
i
e
r
Malescot
M
a
l
e
s
c
o
t
DSNA/DTI
D
S
N
A
/
D
T
I
Varun
V
a
r
u
n
Malik
M
a
l
i
k
Hamilton
H
a
m
i
l
t
o
n
Sundstrand
S
u
n
d
s
t
r
a
n
d
Patrick
P
a
t
r
i
c
k
Mana
M
a
n
a
EUROCONTROL
E
U
R
O
C
O
N
T
R
O
L
Joseph
J
o
s
e
p
h
Mangan
M
a
n
g
a
n
Coanda
C
o
a
n
d
a
Aerospace
A
e
r
o
s
p
a
c
e
Software
S
o
f
t
w
a
r
e
Ghilaine
G
h
i
l
a
i
n
e
Martinez
M
a
r
t
i
n
e
z
DGA
D
G
A
Techniques
T
e
c
h
n
i
q
u
e
s
Aéronautiques
A
é
r
o
n
a
u
t
i
q
u
e
s
Steven
S
t
e
v
e
n
C.
C
.
Martz
M
a
r
t
z
Garmin
G
a
r
m
i
n
International
I
n
t
e
r
n
a
t
i
o
n
a
l
Peter
P
e
t
e
r
Matthews
M
a
t
t
h
e
w
s
Independent
I
n
d
e
p
e
n
d
e
n
t
Consultant
C
o
n
s
u
l
t
a
n
t
Frank
F
r
a
n
k
McCormick
M
c
C
o
r
m
i
c
k
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Services
S
e
r
v
i
c
e
s
Inc
I
n
c
Scott
S
c
o
t
t
McCoy
M
c
C
o
y
Harris
H
a
r
r
i
s
Corporation
C
o
r
p
o
r
a
t
i
o
n
Thomas
T
h
o
m
a
s
McHugh
M
c
H
u
g
h
FAA
F
A
A
William
W
i
l
l
i
a
m
McMinn
M
c
M
i
n
n
Lockheed
L
o
c
k
h
e
e
d
Martin
M
a
r
t
i
n
Josh
J
o
s
h
McNeil
M
c
N
e
i
l
US
U
S
Army
A
r
m
y
AMCOM
A
M
C
O
M
SED
S
E
D
Kevin
K
e
v
i
n
Meier
M
e
i
e
r
Cessna
C
e
s
s
n
a
Aircraft
A
i
r
c
r
a
f
t
Company
C
o
m
p
a
n
y
Amanda
A
m
a
n
d
a
Melles
M
e
l
l
e
s
Bombardier
B
o
m
b
a
r
d
i
e
r
Marc
M
a
r
c
Meltzer
M
e
l
t
z
e
r
Belcan
B
e
l
c
a
n
Engineering
E
n
g
i
n
e
e
r
i
n
g
Steven
S
t
e
v
e
n
Miller
M
i
l
l
e
r
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Gregory
G
r
e
g
o
r
y
Millican
M
i
l
l
i
c
a
n
Honeywell
H
o
n
e
y
w
e
l
l
John
J
o
h
n
Minihan
M
i
n
i
h
a
n
Resource
R
e
s
o
u
r
c
e
Group
G
r
o
u
p
Martin
M
a
r
t
i
n
Momberg
M
o
m
b
e
r
g
Cassidian
C
a
s
s
i
d
i
a
n
Air
A
i
r
Systems
S
y
s
t
e
m
s
Pippa
P
i
p
p
a
Moore
M
o
o
r
e
UK
U
K
CAA
C
A
A
Emilio
E
m
i
l
i
o
Mora-Castro
M
o
r
a
-
C
a
s
t
r
o
EASA
E
A
S
A
Endrich
E
n
d
r
i
c
h
Moritz
M
o
r
i
t
z
Technical
T
e
c
h
n
i
c
a
l
University
U
n
i
v
e
r
s
i
t
y
Robert
R
o
b
e
r
t
Morris
M
o
r
r
i
s
CDL
C
D
L
Systems
S
y
s
t
e
m
s
Ltd.
L
t
d
.
Allan
A
l
l
a
n
Terry
T
e
r
r
y
Morris
M
o
r
r
i
s
NASA
N
A
S
A
Steve
S
t
e
v
e
Morton
M
o
r
t
o
n
TBV
T
B
V
Associates
A
s
s
o
c
i
a
t
e
s
Harold
H
a
r
o
l
d
Moses
M
o
s
e
s
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
Nadir
N
a
d
i
r
Mostefat
M
o
s
t
e
f
a
t
Mannarino
M
a
n
n
a
r
i
n
o
Systems
S
y
s
t
e
m
s
Fred
F
r
e
d
B.
B
.
Moyer
M
o
y
e
r
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Robert
R
o
b
e
r
t
D.
D
.
Mumme
M
u
m
m
e
Embedded
E
m
b
e
d
d
e
d
Plus
P
l
u
s
Engineering
E
n
g
i
n
e
e
r
i
n
g
Arun
A
r
u
n
Murthi
M
u
r
t
h
i
AERO&SPACE
A
E
R
O
&
S
P
A
C
E
USA
U
S
A
Armen
A
r
m
e
n
Nahapetian
N
a
h
a
p
e
t
i
a
n
Teledyne
T
e
l
e
d
y
n
e
Controls
C
o
n
t
r
o
l
s
Gerry
G
e
r
r
y
Ngu
N
g
u
EASA
E
A
S
A
Elisabeth
E
l
i
s
a
b
e
t
h
Nguyen
N
g
u
y
e
n
Aerospace
A
e
r
o
s
p
a
c
e
Corporation
C
o
r
p
o
r
a
t
i
o
n
Robert
R
o
b
e
r
t
Noel
N
o
e
l
Mitre
M
i
t
r
e
Corp
C
o
r
p
Sven
S
v
e
n
Nordhoff
N
o
r
d
h
o
f
f
SQS
S
Q
S
AG
A
G
Paula
P
a
u
l
a
Obeid
O
b
e
i
d
Embedded
E
m
b
e
d
d
e
d
Plus
P
l
u
s
Engineering
E
n
g
i
n
e
e
r
i
n
g
Eric
E
r
i
c
Oberle
O
b
e
r
l
e
Becker
B
e
c
k
e
r
Avionics
A
v
i
o
n
i
c
s
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-8
B
-
8
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Brenda
B
r
e
n
d
a
Ocker
O
c
k
e
r
FAA
F
A
A
Torsten
T
o
r
s
t
e
n
Ostermeier
O
s
t
e
r
m
e
i
e
r
Bundeswehr
B
u
n
d
e
s
w
e
h
r
Frederic
F
r
e
d
e
r
i
c
Painchaud
P
a
i
n
c
h
a
u
d
Defence
D
e
f
e
n
c
e
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
Canada
C
a
n
a
d
a
Sean
S
e
a
n
Parkinson
P
a
r
k
i
n
s
o
n
Resource
R
e
s
o
u
r
c
e
Group
G
r
o
u
p
Dennis
D
e
n
n
i
s
Patrick
P
a
t
r
i
c
k
Penza
P
e
n
z
a
AVISTA
A
V
I
S
T
A
Jean-Phillipe
J
e
a
n
-
P
h
i
l
l
i
p
e
Perrot
P
e
r
r
o
t
Turbomeca
T
u
r
b
o
m
e
c
a
Robin
R
o
b
i
n
Perry
P
e
r
r
y
GE
G
E
Aviation
A
v
i
a
t
i
o
n
David
D
a
v
i
d
Petesch
P
e
t
e
s
c
h
Hamilton
H
a
m
i
l
t
o
n
Sundstrand
S
u
n
d
s
t
r
a
n
d
John
J
o
h
n
Philbin
P
h
i
l
b
i
n
Northrop
N
o
r
t
h
r
o
p
Grumman
G
r
u
m
m
a
n
Integrated
I
n
t
e
g
r
a
t
e
d
Systems
S
y
s
t
e
m
s
Christophe
C
h
r
i
s
t
o
p
h
e
Piala
P
i
a
l
a
Thales
T
h
a
l
e
s
Avionics
A
v
i
o
n
i
c
s
Cyril
C
y
r
i
l
Picard
P
i
c
a
r
d
EADS
E
A
D
S
APSYS
A
P
S
Y
S
Francine
F
r
a
n
c
i
n
e
Pierre
P
i
e
r
r
e
Thales
T
h
a
l
e
s
Avionics
A
v
i
o
n
i
c
s
Patrick
P
a
t
r
i
c
k
Pierre
P
i
e
r
r
e
Thales
T
h
a
l
e
s
Avionics
A
v
i
o
n
i
c
s
Gerald
G
e
r
a
l
d
Pilj
P
i
l
j
FAA
F
A
A
Benoit
B
e
n
o
i
t
Pinta
P
i
n
t
a
Intertechnique
I
n
t
e
r
t
e
c
h
n
i
q
u
e
-
-
Zodiac
Z
o
d
i
a
c
Mo
M
o
Piper
P
i
p
e
r
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Andreas
A
n
d
r
e
a
s
Pistek
P
i
s
t
e
k
ITK
I
T
K
Engineering
E
n
g
i
n
e
e
r
i
n
g
AG
A
G
Laurent
L
a
u
r
e
n
t
Plateaux
P
l
a
t
e
a
u
x
DGA
D
G
A
Laurent
L
a
u
r
e
n
t
Pomies
P
o
m
i
e
s
Independent
I
n
d
e
p
e
n
d
e
n
t
Consultant
C
o
n
s
u
l
t
a
n
t
Jennifer
J
e
n
n
i
f
e
r
Popovich
P
o
p
o
v
i
c
h
Jeppesen
J
e
p
p
e
s
e
n
Inc.
I
n
c
.
Clifford
C
l
i
f
f
o
r
d
Porter
P
o
r
t
e
r
Aircell
A
i
r
c
e
l
l
LLC
L
L
C
Frédéric
F
r
é
d
é
r
i
c
Pothon
P
o
t
h
o
n
ACG
A
C
G
Solutions
S
o
l
u
t
i
o
n
s
Bill
B
i
l
l
Potter
P
o
t
t
e
r
The
T
h
e
MathWorks
M
a
t
h
W
o
r
k
s
Inc
I
n
c
Sunil
S
u
n
i
l
Prasad
P
r
a
s
a
d
HCL
H
C
L
Technologies,
T
e
c
h
n
o
l
o
g
i
e
s
,
Chennai,
C
h
e
n
n
a
i
,
India
I
n
d
i
a
Paul
P
a
u
l
J.
J
.
Prisaznuk
P
r
i
s
a
z
n
u
k
ARINC-AEEC
A
R
I
N
C
-
A
E
E
C
Naim
N
a
i
m
Rahmani
R
a
h
m
a
n
i
Transport
T
r
a
n
s
p
o
r
t
Canada
C
a
n
a
d
a
Angela
A
n
g
e
l
a
Rapaccini
R
a
p
a
c
c
i
n
i
ENAC
E
N
A
C
Lucas
L
u
c
a
s
Redding
R
e
d
d
i
n
g
Silver-Atena
S
i
l
v
e
r
-
A
t
e
n
a
David
D
a
v
i
d
Redman
R
e
d
m
a
n
Aerospace
A
e
r
o
s
p
a
c
e
Vehicle
V
e
h
i
c
l
e
Systems
S
y
s
t
e
m
s
Institute
I
n
s
t
i
t
u
t
e
(AVSI)
(
A
V
S
I
)
Tammy
T
a
m
m
y
Reeve
R
e
e
v
e
Patmos
P
a
t
m
o
s
Engineering
E
n
g
i
n
e
e
r
i
n
g
Services,
S
e
r
v
i
c
e
s
,
Inc.
I
n
c
.
Guy
G
u
y
Renault
R
e
n
a
u
l
t
SAGEM
S
A
G
E
M
DS
D
S
Safran
S
a
f
r
a
n
Group
G
r
o
u
p
Leanna
L
e
a
n
n
a
Rierson
R
i
e
r
s
o
n
Digital
D
i
g
i
t
a
l
Safety
S
a
f
e
t
y
Consulting
C
o
n
s
u
l
t
i
n
g
George
G
e
o
r
g
e
Romanski
R
o
m
a
n
s
k
i
Verocel
V
e
r
o
c
e
l
Cyrille
C
y
r
i
l
l
e
Rosay
R
o
s
a
y
EASA
E
A
S
A
Edward
E
d
w
a
r
d
Rosenbloom
R
o
s
e
n
b
l
o
o
m
Kollsman,
K
o
l
l
s
m
a
n
,
Inc
I
n
c
Tom
T
o
m
Roth
R
o
t
h
Airborne
A
i
r
b
o
r
n
e
Software
S
o
f
t
w
a
r
e
Certification
C
e
r
t
i
f
i
c
a
t
i
o
n
Consulting
C
o
n
s
u
l
t
i
n
g
Jamel
J
a
m
e
l
Rouahi
R
o
u
a
h
i
CEAT
C
E
A
T
Marielle
M
a
r
i
e
l
l
e
Roux
R
o
u
x
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
France
F
r
a
n
c
e
Benedito
B
e
n
e
d
i
t
o
Massayuki
M
a
s
s
a
y
u
k
i
Sakugawa
S
a
k
u
g
a
w
a
ANAC
A
N
A
C
Brazil
B
r
a
z
i
l
Almudena
A
l
m
u
d
e
n
a
Sanchez
S
a
n
c
h
e
z
GMV
G
M
V
SA
S
A
Vdot
V
d
o
t
Santhanam
S
a
n
t
h
a
n
a
m
Boeing
B
o
e
i
n
g
Company
C
o
m
p
a
n
y
Laurence
L
a
u
r
e
n
c
e
Scales
S
c
a
l
e
s
Thales
T
h
a
l
e
s
Deidre
D
e
i
d
r
e
Schilling
S
c
h
i
l
l
i
n
g
Hamilton
H
a
m
i
l
t
o
n
Sundstrand
S
u
n
d
s
t
r
a
n
d
Ernst
E
r
n
s
t
Schmidt
S
c
h
m
i
d
t
Bundeswehr
B
u
n
d
e
s
w
e
h
r
Peter
P
e
t
e
r
Schmitt
S
c
h
m
i
t
t
Universität
U
n
i
v
e
r
s
i
t
ä
t
Karlsruhe
K
a
r
l
s
r
u
h
e
Dr.
D
r
.
Achim
A
c
h
i
m
Schoenhoff
S
c
h
o
e
n
h
o
f
f
EADS
E
A
D
S
Military
M
i
l
i
t
a
r
y
Aircraft
A
i
r
c
r
a
f
t
Martin
M
a
r
t
i
n
Schwarz
S
c
h
w
a
r
z
TT
T
T
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Gabriel
G
a
b
r
i
e
l
Scolan
S
c
o
l
a
n
SAGEM
S
A
G
E
M
DS
D
S
Safran
S
a
f
r
a
n
Group
G
r
o
u
p
Christel
C
h
r
i
s
t
e
l
Seguin
S
e
g
u
i
n
ONERA
O
N
E
R
A
Beatrice
B
e
a
t
r
i
c
e
Sereno
S
e
r
e
n
o
Teuchos
T
e
u
c
h
o
s
SAFRAN
S
A
F
R
A
N
Phillip
P
h
i
l
l
i
p
L.
L
.
Shaffer
S
h
a
f
f
e
r
GE
G
E
Aviation
A
v
i
a
t
i
o
n
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-9
B
-
9
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Jagdish
J
a
g
d
i
s
h
Shah
S
h
a
h
Parker
P
a
r
k
e
r
Vadim
V
a
d
i
m
Shapiro
S
h
a
p
i
r
o
TetraTech/AMT
T
e
t
r
a
T
e
c
h
/
A
M
T
Jean
J
e
a
n
François
F
r
a
n
ç
o
i
s
Sicard
S
i
c
a
r
d
DGA
D
G
A
Techniques
T
e
c
h
n
i
q
u
e
s
Aéronautiques
A
é
r
o
n
a
u
t
i
q
u
e
s
Marten
M
a
r
t
e
n
Sjoestedt
S
j
o
e
s
t
e
d
t
Saab
S
a
a
b
AB
A
B
Peter
P
e
t
e
r
Skaves
S
k
a
v
e
s
FAA
F
A
A
Greg
G
r
e
g
Slater
S
l
a
t
e
r
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Claudine
C
l
a
u
d
i
n
e
Sokoloff
S
o
k
o
l
o
f
f
Atos
A
t
o
s
Origin
O
r
i
g
i
n
Marge
M
a
r
g
e
Sonnek
S
o
n
n
e
k
Honeywell
H
o
n
e
y
w
e
l
l
Guillaume
G
u
i
l
l
a
u
m
e
Soudain
S
o
u
d
a
i
n
EASA
E
A
S
A
Roger
R
o
g
e
r
Souter
S
o
u
t
e
r
FAA
F
A
A
Robin
R
o
b
i
n
L.
L
.
Sova
S
o
v
a
FAA
F
A
A
Richard
R
i
c
h
a
r
d
Spencer
S
p
e
n
c
e
r
FAA
F
A
A
Thomas
T
h
o
m
a
s
Sperling
S
p
e
r
l
i
n
g
The
T
h
e
Mathworks
M
a
t
h
w
o
r
k
s
William
W
i
l
l
i
a
m
StClair
S
t
C
l
a
i
r
LDRA
L
D
R
A
Roland
R
o
l
a
n
d
Stalford
S
t
a
l
f
o
r
d
Galileo
G
a
l
i
l
e
o
Industries
I
n
d
u
s
t
r
i
e
s
Spa
S
p
a
Jerry
J
e
r
r
y
Stamatopoulous
S
t
a
m
a
t
o
p
o
u
l
o
u
s
Aircell
A
i
r
c
e
l
l
LLC
L
L
C
Tom
T
o
m
Starnes
S
t
a
r
n
e
s
Cessna
C
e
s
s
n
a
Aircraft
A
i
r
c
r
a
f
t
Company
C
o
m
p
a
n
y
Jim
J
i
m
Stewart
S
t
e
w
a
r
t
NATS
N
A
T
S
Tim
T
i
m
Stockton
S
t
o
c
k
t
o
n
Certon
C
e
r
t
o
n
Victor
V
i
c
t
o
r
Strachan
S
t
r
a
c
h
a
n
Northrop-Grumman
N
o
r
t
h
r
o
p
-
G
r
u
m
m
a
n
John
J
o
h
n
Strasburger
S
t
r
a
s
b
u
r
g
e
r
FAA
F
A
A
Margarita
M
a
r
g
a
r
i
t
a
Strelnikova
S
t
r
e
l
n
i
k
o
v
a
Sukhoi
S
u
k
h
o
i
Civil
C
i
v
i
l
Aircraft
A
i
r
c
r
a
f
t
Company
C
o
m
p
a
n
y
(SCAC)
(
S
C
A
C
)
Ronald
R
o
n
a
l
d
Stroup
S
t
r
o
u
p
FAA
F
A
A
Will
W
i
l
l
Struck
S
t
r
u
c
k
FAA
F
A
A
Wladimir
W
l
a
d
i
m
i
r
Terzic
T
e
r
z
i
c
SAGEM
S
A
G
E
M
DS
D
S
Safran
S
a
f
r
a
n
Group
G
r
o
u
p
Wolfgang
W
o
l
f
g
a
n
g
Theurer
T
h
e
u
r
e
r
C-S
C
-
S
SI
S
I
Joel
J
o
e
l
Thornton
T
h
o
r
n
t
o
n
Tier5
T
i
e
r
5
Inc
I
n
c
Mikael
M
i
k
a
e
l
Thorvaldsson
T
h
o
r
v
a
l
d
s
s
o
n
KnowIT
K
n
o
w
I
T
Technowledge
T
e
c
h
n
o
w
l
e
d
g
e
Bozena
B
o
z
e
n
a
Brygida
B
r
y
g
i
d
a
Thrower
T
h
r
o
w
e
r
Hamilton
H
a
m
i
l
t
o
n
Sundstrand
S
u
n
d
s
t
r
a
n
d
Christophe
C
h
r
i
s
t
o
p
h
e
Travers
T
r
a
v
e
r
s
Dassault
D
a
s
s
a
u
l
t
Aviation
A
v
i
a
t
i
o
n
Fay
F
a
y
Trowbridge
T
r
o
w
b
r
i
d
g
e
Honeywell
H
o
n
e
y
w
e
l
l
Nick
N
i
c
k
Tudor
T
u
d
o
r
Tudor
T
u
d
o
r
Associates
A
s
s
o
c
i
a
t
e
s
Silpa
S
i
l
p
a
Uppalapati
U
p
p
a
l
a
p
a
t
i
FAA
F
A
A
Marie-Line
M
a
r
i
e
-
L
i
n
e
Valentin
V
a
l
e
n
t
i
n
Airbus
A
i
r
b
u
s
Jozef
J
o
z
e
f
Van
V
a
n
Baal
B
a
a
l
Civil
C
i
v
i
l
Aviation
A
v
i
a
t
i
o
n
Authorities
A
u
t
h
o
r
i
t
i
e
s
Netherlands
N
e
t
h
e
r
l
a
n
d
s
John
J
o
h
n
Van
V
a
n
Leeuwen
L
e
e
u
w
e
n
Sikorsky
S
i
k
o
r
s
k
y
Aircraft
A
i
r
c
r
a
f
t
Aulis
A
u
l
i
s
Viik
V
i
i
k
NAV
N
A
V
Canada
C
a
n
a
d
a
Bertrand
B
e
r
t
r
a
n
d
Voisin
V
o
i
s
i
n
Dassault
D
a
s
s
a
u
l
t
Aviation
A
v
i
a
t
i
o
n
Katherine
K
a
t
h
e
r
i
n
e
Volk
V
o
l
k
L-3
L
-
3
Communications
C
o
m
m
u
n
i
c
a
t
i
o
n
s
Dennis
D
e
n
n
i
s
Wallace
W
a
l
l
a
c
e
FAA
F
A
A
Andy
A
n
d
y
Wallington
W
a
l
l
i
n
g
t
o
n
Bell
B
e
l
l
Helicopter
H
e
l
i
c
o
p
t
e
r
Yunming
Y
u
n
m
i
n
g
Wang
W
a
n
g
Esterel
E
s
t
e
r
e
l
Technologies
T
e
c
h
n
o
l
o
g
i
e
s
Don
D
o
n
Ward
W
a
r
d
AVSI
A
V
S
I
Steve
S
t
e
v
e
Ward
W
a
r
d
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Patricia
P
a
t
r
i
c
i
a
Warner
W
a
r
n
e
r
Software
S
o
f
t
w
a
r
e
Engineering
E
n
g
i
n
e
e
r
i
n
g
Michael
M
i
c
h
a
e
l
Warren
W
a
r
r
e
n
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Rob
R
o
b
Weaver
W
e
a
v
e
r
NATS
N
A
T
S
Yu
Y
u
Wei
W
e
i
CAA
C
A
A
China
C
h
i
n
a
Terri
T
e
r
r
i
Weinstein
W
e
i
n
s
t
e
i
n
Parker
P
a
r
k
e
r
Hannifin
H
a
n
n
i
f
i
n
Marcus
M
a
r
c
u
s
Weiskirchner
W
e
i
s
k
i
r
c
h
n
e
r
EADS
E
A
D
S
Military
M
i
l
i
t
a
r
y
Aircraft
A
i
r
c
r
a
f
t
Daniel
D
a
n
i
e
l
Weisz
W
e
i
s
z
Sandel
S
a
n
d
e
l
Avionics,
A
v
i
o
n
i
c
s
,
Inc.
I
n
c
.
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
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-10
B
-
1
0
Name
N
a
m
e
Organization
O
r
g
a
n
i
z
a
t
i
o
n
Rich
R
i
c
h
Wendlandt
W
e
n
d
l
a
n
d
t
Quantum3D
Q
u
a
n
t
u
m
3
D
Michael
M
i
c
h
a
e
l
Whalen
W
h
a
l
e
n
Rockwell
R
o
c
k
w
e
l
l
Collins
C
o
l
l
i
n
s
Paul
P
a
u
l
Whiston
W
h
i
s
t
o
n
High
H
i
g
h
Integrity
I
n
t
e
g
r
i
t
y
Solutions
S
o
l
u
t
i
o
n
s
Ltd
L
t
d
Todd
T
o
d
d
R.
R
.
White
W
h
i
t
e
L-3
L
-
3
Communications/Qualtech
C
o
m
m
u
n
i
c
a
t
i
o
n
s
/
Q
u
a
l
t
e
c
h
Virginie
V
i
r
g
i
n
i
e
Wiels
W
i
e
l
s
ONERA
O
N
E
R
A
ElRoy
E
l
R
o
y
Wiens
W
i
e
n
s
Cessna
C
e
s
s
n
a
Aircraft
A
i
r
c
r
a
f
t
Company
C
o
m
p
a
n
y
Terrance
T
e
r
r
a
n
c
e
Williamson
W
i
l
l
i
a
m
s
o
n
Jeppesen
J
e
p
p
e
s
e
n
Inc.
I
n
c
.
Graham
G
r
a
h
a
m
Wisdom
W
i
s
d
o
m
BAE
B
A
E
Systems
S
y
s
t
e
m
s
Patricia
P
a
t
r
i
c
i
a
Wojnarowski
W
o
j
n
a
r
o
w
s
k
i
Boeing
B
o
e
i
n
g
Commercial
C
o
m
m
e
r
c
i
a
l
Airplanes
A
i
r
p
l
a
n
e
s
Joerg
J
o
e
r
g
Wolfrum
W
o
l
f
r
u
m
Diehl
D
i
e
h
l
Aerospace
A
e
r
o
s
p
a
c
e
Kurt
K
u
r
t
Woodham
W
o
o
d
h
a
m
NASA
N
A
S
A
Cai
C
a
i
Yong
Y
o
n
g
CAAC
C
A
A
C
(Civil
(
C
i
v
i
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
of
o
f
China)
C
h
i
n
a
)
Edward
E
d
w
a
r
d
Yoon
Y
o
o
n
Curtiss-Wright
C
u
r
t
i
s
s
-
W
r
i
g
h
t
Controls,
C
o
n
t
r
o
l
s
,
Inc
I
n
c
Robert
R
o
b
e
r
t
Young
Y
o
u
n
g
Rolls-Royce
R
o
l
l
s
-
R
o
y
c
e
William
W
i
l
l
i
a
m
Yu
Y
u
CAAC
C
A
A
C
China
C
h
i
n
a
Erhan
E
r
h
a
n
Yuceer
Y
u
c
e
e
r
Savunma
S
a
v
u
n
m
a
Teknolojileri
T
e
k
n
o
l
o
j
i
l
e
r
i
Muhendislik
M
u
h
e
n
d
i
s
l
i
k
ve
v
e
Ticaret
T
i
c
a
r
e
t
Uli
U
l
i
Zanker
Z
a
n
k
e
r
Liebherr
L
i
e
b
h
e
r
r
©
©
2011
2
0
1
1
RTCA,
R
T
C
A
,
Inc.
I
n
c
.
0.00
0.00
0.00
1.00
0.00
0.00
0.00
0.00
1.00