[Your Stakeholder Name] Requirements Inspection Checklist		status: draft security: YES safety: ASIL_B
tags: template realizes: wp__requirements_inspect

doc__stakeholder_name_req_inspection		Generic Document

Attention

The above directive must be updated according to your Stakeholder.

Modify Your Stakeholder Name to be your Stakeholder Name
Modify id to be your Stakeholder Name in lower snake case preceded by doc__ and followed by _req_inspection
Adjust status to be valid
Adjust safety, security and tags according to your needs

Stakeholder Requirement Inspection Checklist#

Purpose

The purpose of this requirement inspection checklist is to collect the topics to be checked during requirements inspection.

Conduct

As described in the concept Work product Inspections Co... (doc_concept__wp_inspections) the following “inspection roles” are expected to be filled:

author: these are the persons who did the last commits on the requirements in scope (can be derived from version mgt tool)

reviewer: these are all persons committing into this inspection document or giving a pull request verdict on it (can be derived from version mgt tool)

moderator: only needed for conflict resolution between author and reviewers, is the safety manager, security manager or quality manager called in as a reviewer (can be derived from version mgt tool)

test expert: <one of the reviewers explicitly named here, to cover REQ_08_01 as described>

Checklist

Table 76 Stakeholder Requirement Inspection Checklist#

Review ID

Acceptance Criteria

Guidance

Passed

Remarks

Issue link

REQ_01_01

Is the requirement formulation template used?

see Requirement Formulation Tem... (gd_temp__req_formulation), this includes the use of “shall”.

REQ_02_01

Is the requirement description comprehensible ?

If you think the requirement is hard to understand, comment here.

REQ_02_02

Is the requirement description unambiguous ?

Especially search for “weak words” like “about”, “etc.”, “relevant” and others (see the internet documentation on this). This check shall be supported by tooling.

REQ_02_03

Is the requirement description atomic ?

A good way to think about this is to consider if the requirement may be tested by one (positive) test case or needs more of these. The requirement formulation template should also avoid being non-atomic already. Note that there are cases where also non-atomic requirements are the better ones, for example if those are better understandable.

REQ_02_04

Is the requirement description feasible ?

If at the time of the inspection the requirement has already some implementation, the answer is yes. This can be checked via traces, but also Requirement attribute: link... (gd_req__req_attr_impl) shows this. In case the requirement has no implementation at the time of inspection (i.e. not implemented at least as “proof-of-concept”), a development expert should be invited to the Pull-Request review to explicitly check this item.

REQ_02_05

Is the requirement description independent from implementation ?

This checkpoint should improve requirements definition in the sense that the “what” is described and not the “how” - the latter should be described in architecture/design derived from the requirement. But there can also be a good reason for this, for example we would require using a file format like JSON and even specify the formatting standard already on stakeholder requirement level because we want to be compatible. A finding in this checkpoint does not mean there is a safety problem in the requirement.

REQ_03_01

Is the rationale correct?

Rationales explain why the top level requirements were created. Do those cover the requirement?

REQ_03_02

Is the linkage to the parent requirement correct?

Linkage to correct levels and ASIL attributes is checked automatically, but it needs checking if the child requirement implements (at least) a part of the parent requirement.

REQ_04_01

Is the requirement internally and externally consistent?

Does the requirement contradict other requirements within the same or higher levels?

REQ_05_01

Do the software requirements consider timing constraints?

This checkpoint encourages to think about timing constraints even if those are not explicitly mentioned in the parent requirement. If the reviewer of a requirement already knows or suspects that the code execution will be consuming a lot of time, one should think of the expectation of a “user”.

REQ_06_01

Does the requirement consider external interfaces?

The SW platform’s external interfaces (to the user and external systems) are defined, so the Feature and Component Requirements should determine the input data use and setting of output data for these interfaces. Are all output values defined?

REQ_07_01

Is the safety attribute set correctly?

For the top level requirements (and also all AoU) this needs to be checked manually for correctness.

REQ_07_02

Is the security attribute set correctly?

For the top level requirements (and also all AoU) this needs to be checked manually for correctness.

REQ_08_01

Is the requirement verifiable?

If at the time of the inspection already tests are created for the requirement, the answer is yes. This can be checked via traces, but also Requirement attribute: test... (gd_req__req_attr_test_covered) shows this. In case the requirement is not sufficiently traced to test cases already, a test expert is invited to the inspection to give his opinion whether the requirement is formulated in a way that supports test development and the available test infrastructure is sufficient to perform the test.

REQ_09_01

Do those requirements cover assumed safety mechanisms needed by the hardware and system?

Note that stakeholder requirements covering safety mechanisms come from rationales.

Note: If a Review ID is not applicable for your requirement, then state “”n/a” in status and comment accordingly in remarks. For example “no stakeholder requirement (no rationale needed)”

The following requirements in “valid” state and with “inspected” tag set are in the scope of this inspection:

No needs passed the filters

And also the following AoUs in “valid” state and with “inspected” tag set (for these please answer the questions above as if the AoUs are requirements, except questions REQ_03_01 and REQ_03_02):

No needs passed the filters

Attention

The above tables filtering must be updated according to your Stakeholder.

Modify stakeholder_name to be your Stakeholder Name in lower snake case

Review ID	Acceptance Criteria	Guidance
REQ_01_01	Is the requirement formulation template used?	see Requirement Formulation Tem... (gd_temp__req_formulation), this includes the use of “shall”.
REQ_02_01	Is the requirement description comprehensible ?	If you think the requirement is hard to understand, comment here.
REQ_02_02	Is the requirement description unambiguous ?	Especially search for “weak words” like “about”, “etc.”, “relevant” and others (see the internet documentation on this). This check shall be supported by tooling.
REQ_02_03	Is the requirement description atomic ?	A good way to think about this is to consider if the requirement may be tested by one (positive) test case or needs more of these. The requirement formulation template should also avoid being non-atomic already. Note that there are cases where also non-atomic requirements are the better ones, for example if those are better understandable.
REQ_02_04	Is the requirement description feasible ?	If at the time of the inspection the requirement has already some implementation, the answer is yes. This can be checked via traces, but also Requirement attribute: link... (gd_req__req_attr_impl) shows this. In case the requirement has no implementation at the time of inspection (i.e. not implemented at least as “proof-of-concept”), a development expert should be invited to the Pull-Request review to explicitly check this item.
REQ_02_05	Is the requirement description independent from implementation ?	This checkpoint should improve requirements definition in the sense that the “what” is described and not the “how” - the latter should be described in architecture/design derived from the requirement. But there can also be a good reason for this, for example we would require using a file format like JSON and even specify the formatting standard already on stakeholder requirement level because we want to be compatible. A finding in this checkpoint does not mean there is a safety problem in the requirement.
REQ_03_01	Is the rationale correct?	Rationales explain why the top level requirements were created. Do those cover the requirement?
REQ_03_02	Is the linkage to the parent requirement correct?	Linkage to correct levels and ASIL attributes is checked automatically, but it needs checking if the child requirement implements (at least) a part of the parent requirement.
REQ_04_01	Is the requirement internally and externally consistent?	Does the requirement contradict other requirements within the same or higher levels?
REQ_05_01	Do the software requirements consider timing constraints?	This checkpoint encourages to think about timing constraints even if those are not explicitly mentioned in the parent requirement. If the reviewer of a requirement already knows or suspects that the code execution will be consuming a lot of time, one should think of the expectation of a “user”.
REQ_06_01	Does the requirement consider external interfaces?	The SW platform’s external interfaces (to the user and external systems) are defined, so the Feature and Component Requirements should determine the input data use and setting of output data for these interfaces. Are all output values defined?
REQ_07_01	Is the safety attribute set correctly?	For the top level requirements (and also all AoU) this needs to be checked manually for correctness.
REQ_07_02	Is the security attribute set correctly?	For the top level requirements (and also all AoU) this needs to be checked manually for correctness.
REQ_08_01	Is the requirement verifiable?	If at the time of the inspection already tests are created for the requirement, the answer is yes. This can be checked via traces, but also Requirement attribute: test... (gd_req__req_attr_test_covered) shows this. In case the requirement is not sufficiently traced to test cases already, a test expert is invited to the inspection to give his opinion whether the requirement is formulated in a way that supports test development and the available test infrastructure is sufficient to perform the test.
REQ_09_01	Do those requirements cover assumed safety mechanisms needed by the hardware and system?	Note that stakeholder requirements covering safety mechanisms come from rationales.

Stakeholder Requirement Inspection Checklist#

This Page