SVP Checklist

(Engagement Name and Id)

(Client)

Document History

Version Date Author Changes

Review And Approval

Company Role Name Date Signature

Distribution

Company Name Number Media Action

Storage

Location Access Administrator

Company Confidential - Copyright © 2017 Capgemini - All rights reserved

Template Version Number (Same as template number mentioned in the Document Properties – Tags field)
 SVP Checklist

Project ID:

Project Name:

TLS / SOW / PO:

Deliverable:

Person Authorising Delivery

Engineer: Start Date:

Quality Checker: Delivery Date:

Check Points Quality Control II Re-Verification

Sl. No. Remarks
Level I Level II Level II

General

Are the revision/identification details and the signature

1
list correct on the front sheet?

2 Is the change history complete & correct?

3 Is the table of contents complete and correct?

4 Are all acronyms defined and correct?

Does all the review comments in the review log are

5
closed?

6 Are relevant Change Request (CR's) are closed ?

7 Are all referenced documents available in SVN?

Does all the review checklists used are latest and

8
approved?

Is all external and internal applicable documents are

9
included?
10 Is this document checked-in SVN?

Is this document complete, clear and consistent (easy

11
to follow)?

SVP Specific

Does the SVP contain a section describing

organizational responsibilities within the software
12
verification processes and interfaces with the other
software life cycle processes?

Does the SVP contain a section describing the methods

13 to achieve verification independence objective, when
required?

Does the SVP describe the review methods correctly

for all of applicable review activities ( Such as Review of
High Level and Low Level Requirements, Software
Architecture, Source Code, Output of Integration
14 Process and Verification Artifacts -Test Cases, Test
Procedures, Test Scripts and Test Results) and does it
describe the use of checklists during all of the
applicable review activities? Verification Methods (for
each activity of the s/w verification

Does the SVP contain a description of the testing

methods, including:
• - Guidelines establishing test case selection process

• - Test procedures to be used

15 • - Test data to be produced
[Requirements Based Testing Methods(Closed Box
(FVT), Open Box (HSIT), white Box (Unit Level
Testing), Robustness test cases, normal range test
cases, Software-Software Integration Testing (SSIT))
and resolution, if any?]

Does the SVP describe the Analysis for all of

16
applicable review activities including traceability?
 Does the SVP contain a description of the verification
Environment, including:
• Testing and analysis tools
17
• Guidelines for applying the tools
• Hardware Platform for tools
• Tool qualification,if any

Does the SVP contain a description of the transition

18
criteria for entering the SW verification process (es)?

If partitioning is used, does the SVP contain partitioning

19 considerations? (i.e., methods used to verify the
integrity of the partitioning)

Does the SVP contain any assumptions made about

20 the compiler? (e.g., assumptions made about the
correctness of compilers, linkage editor or loader)

Does the SVP contain re-verification guidelines for SW

modification, including:
• Methods identifying affected areas of the software
21
• Methods identifying changes to executable object
code
•Regression Testing

Does the SVP contain considerations for previously

22 developed software and/or COTS used? (e.g. a
description of the proof of evidence)

Does the SVP describes the methods to verify the

23
multiple version dissimilar software. (If used)
 ED-12/DO-178
Cross Reference

N/A

7.2.4
A-8:3
N/A
N/A

7.2.3
7.2.4
7.2.5
A-8:3

7.2.4
A-8:3

7.2.1
A-8:1

N/A

N/A
 7.2.1
A-8:1

N/A

11.3(a)
A-1:2
4.1.b

11.3(b)

11.3 (c.1)

11.3 (c.3)

11.3 (c.2)
11.3 d
A-1:3
4.1.c
4.4.3

11.3 e
A-1:2
4.1.b
4.3

11.3(f)
4.1.d

11.3(g)
A-1:3
4.1.c
4.2.c
4.4.2

11.3(h)

11.3(i)
A-1:4
4.1.d
12.1

11.3(j)
A-1:4
4.1.d
4.2.f
12.3.2