DO-VERC001_1.

High Level Requirements review checklist

System / Sub System Name
Software Name DO-178B Level
Project Name Project Code
Review Phase Review Date
Item Name Item Revision Item Size Size Unit Author

Item(s) Under Review

Item Name Item Revision

Item(s) Referred

Reviewer Name Role Review Type (PH)

Planned Review Effort (PH)
Review Details Actual Review Effort (PH)
Planned Rework Effort (PH)
Actual Rework Effort (PH)
Applicable Problem Report(s)

Review Summary
Major - M 0
Minor - N 0
Trivial - T 0
Total Defects 0
Total Open Defects 0
Review Decision

Deviation Approval Required Approval Status Approved By

Verification Status Verified By Verified Date

Page 1 of 11
DO-VERC001_1.0

Accepted
Re-review
Condionally accepted

Open
Closed

Page 2 of 11
DO-VERC001_1.0

High Level Requirements Review Checklist

DO-178B
# Checkpoints Conformance Evidence / Justification
Reference
General
7.2.1
1 Are the review item(s) under configuration control?
A-8:1
7.2.1
2 Are the referenced items under configuration control?
A-8:1

7.2.4
3 Is a revision history provided and accurate?
A-8:3

7.2.1
4 Is the file naming convention followed as mentioned in SCMP?
A:8-1
7.2.3
Have all change control actions (Problem reporting,change review etc.) 7.2.4
5
relating to the review item been implemented and are correct? 7.2.5
A-8:3
7.2.5
6 Are the deferral of change control actions accurately justified?
A-8:3

7 Are the document references accurate? 7.1c

8 Is the acronym list accurate? N/A

9 Is justification provided for sections that are not applicable? N/A

Are the Table of Content, Table of Figures, Page numbering present and are
10 N/A
correct?

HLR Specific

11.9 a
11 Does the high level requirement document include system overview section? A-2:1, 2
2.2.1

Page 3 of 11
DO-VERC001_1.0

DO-178B
# Checkpoints Conformance Evidence / Justification
Reference
11.9 a
A-2:1, 2
Does the high level requirement document captures description of the
2.2.1
12 allocation of system requirements to software, safety-related requirements
5.1.1 a
and potential failure conditions?
6.3.1 a
A-3:1
Does the high level requirement document include functional and operational
requirements under each mode of operation? 11.9 b
A-2: 1, 2
13 Note: Modes of operation are unique based on the LRU functions and 5.1.1 a
capabilities. Examples include built in test, ground operation, standby, or 6.3.1 a
data load etc., A-3:1

11.9 b
A-2: 1, 2
Are derived requirements identified and justified? (I.e. is there a description
14 5.1.1 b
or reference describing why the requirement is derived)?
6.3.1 a
A-3:1
11.9 c
A-2: 1, 2
Does the high level requirement document identifies performance
15 5.1.1a
requirements (for example, precision and accuracy )?
6.3.1 a
A-3:1
11.9 d
Does the high level requirement document captures timing requirements and A-2: 1, 2
16
constraints? 5.1.1 a
6.3.1 a
11.9 e
A-2: 1, 2
Does the high level requirement document includes memory size
17 5.1.1 a
requireemnts and its constraints if any?
6.3.1 a
A-3:1
11.9 f
Does the high level requirement document includes hardware and software A-2: 1, 2
18 interfaces, for example, protocols, formats, frequency of inputs and 5.1.1 a
frequency of outputs? 6.3.1 a
A-3:1

11.9 f
Does the high level requirement document includes other external interfaces
19 A-2: 1, 2
like user interface, communication interfaces?
A-3:1

Page 4 of 11
DO-VERC001_1.0

DO-178B
# Checkpoints Conformance Evidence / Justification
Reference
11.9 g
A-2: 1, 2
Does the high level requirement document includes failure detection and
20 5.1.1 a
safety monitoring requirements?
6.3.1 a
5.1.2d

11.9 h
Does the high level requirement document include partitioning requirements A-2: 1, 2
21
allocated to software ?, 5.1.1 a
6.3.1 a

11.9 h
Does the high level requirement document describe how the partitioned A-2: 1, 2
22 software components interact with each other?, and the software level(s) of 5.1.1 a
each partition? 6.3.1 a
A-3:1

11.9 h
A-2: 1, 2
Does the high level requirement document captures software level(s) of each
23 5.1.1 a
partition?
6.3.1 a
A-3:1
6.3.1 f
Does each of the high level requirement is traceable to one or more of A-2: 1, 2
24
system requirements? 5.1.1 a
A-3:6
A-2: 1, 2
Has the defined requirement standard followed while developing high level 5.1.1 a
25
requirement document? 6.3.1 e
A-3:5
6.3.1 b
Each requirement is unique, unambiguous and does not conflict with other A-2: 1, 2
26
requirements? 5.1.1 a
A-3:2

6.3.1b
A-2: 1, 2
27 Does each requirement have only one interpretation?
5.1.1 a
A-3:2

Page 5 of 11
DO-VERC001_1.0

DO-178B
# Checkpoints Conformance Evidence / Justification
Reference

6.3.1b
A-2: 1, 2
28 Each requirement is accurate and sufficiently detailed?
A-3:2
5.1.1 a

6.3.1 c
Does each software high level requirement has compatability with the
A-2: 1, 2
29 hardware / software features of the target computer, especially, system
5.1.1 a
response times and input/output hardware.?
A-3:3
6.3.1 d
Does each high level requirement be identified as verifiable by testing, A-2: 1, 2
30
demonstration, inspection, or analysis? 5.1.1 a
A-3:4
6.3.1 d
Does each software requirement have measurable results including A-2: 1, 2
31
functional/non-functional requirement(s)? 5.1.1 a
A-3:4
6.3.1 d
Does each of the input characteristics like sources, accuracy, range values, A-2: 1, 2
32
frequencies and formats are specified? 5.1.1 a
A-3:4
6.3.1.d
Does each of the output characteristics like destinations, accuracy, range A-2: 1, 2
33
values, frequencies and formats are specified? 5.1.1 a
A-3:4

6.3.1 e
Does each requirement have a SHALL statement and is the requirement
34 A-2: 1, 2
written accordance with the requirement standards and the SDP?
5.1.1 a

6.3.1 e
Does each requirement have an unique Identifier? (e.g. DOORS ID Tag
35 A-2: 1, 2
SWRS-XXXX)
5.1.1 a

11.9 c
6.3.1 g
If mathematical algorithms or logic diagrams are used, are tolerances of
36 A-2: 1, 2
output values defined?
5.1.1 a
A-3:7

Page 6 of 11
DO-VERC001_1.0

DO-178B
# Checkpoints Conformance Evidence / Justification
Reference
6.3.1 g
If mathematical algorithms or logic diagrams are used, are initial conditions A-2: 1, 2
37
defined? 5.1.1 a
A-3:7
6.3.1 g
If mathematical algorithms or logic diagrams are used, are constants A-2: 1, 2
38
defined? 5.1.1 a
A-3:7
6.3.1 g
If mathematical algorithms or logic diagrams are used, are the boundaries of A-2: 1, 2
39
an algorithm/equation identified? i.e. overflow/underflow 5.1.1 a
A-3:7

6.3.1 g
If mathematical algorithms or logic diagrams are used, will the A-2: 1, 2
40
algorithm/equation prevent a divide by zero? 5.1.1 a
A-3:7

6.3.1 g
If mathematical algorithms or logic diagrams are used, are units defined and
41 A-2: 1, 2
used consistently?
5.1.1 a
A-3:7

6.3.1 g
If symbols (e.g. logic symbols) are used in the software requirements, are
A-2: 1, 2
42 they defined? (Items such as initial conditions, constants and behavior are
5.1.1 a
defined).
A-3:7

6.3.1 a
If signals are identified from the system requirements, do the signal names
43 A-2: 1, 2
comply with the Project Dictionary?
5.1.1 a
6.3.1 f
Is each system requirement allocated to software traceable to one or more A-2: 1, 2
44
software high-level requirements.? 5.1.2.h
A-3:6
A-2: 1, 2
5.1.1 a
45 Are deviation from requirement standard justified?
6.3.1 e
A-3:5

Page 7 of 11
DO-VERC001_1.0

DO-178B
# Checkpoints Conformance Evidence / Justification
Reference
Incase of modification to previously developed software required, the impact
46 of the software requirements changes and the consequences of 12.1.1c
software requirement changes upon other requirements analyzed ?

47 Is the DO 178B cross reference matrix complete and correct? N/A

Page 8 of 11
DO-VERC001_1.0

Yes

No

NA

Page 9 of 11
DO-VERC001_1.0

Review Findings
# Checkpoint Reference Defect Location Defect Description Severity Class Type of Defect Cause of Defect

Page 10 of 11
DO-VERC001_1.0

Action Taken Status Remarks

Page 11 of 11