WEBVTT

1
00:00:00.000 --> 00:00:03.264
A user requirement should communicate an
actual need.

2
00:00:03.414 --> 00:00:07.339
The phrase easy to clean is useful as a
concern but too vague

3
00:00:07.489 --> 00:00:09.068
to verify on its own.

4
00:00:09.218 --> 00:00:14.061
Ask what product residues are expected,
which surfaces must be accessible,

5
00:00:14.211 --> 00:00:18.520
what cleaning process is intended and how
the design will support it.

6
00:00:18.670 --> 00:00:23.747
Do not insert a universal surface finish
or residue limit simply because

7
00:00:23.897 --> 00:00:25.604
another project used it.

8
00:00:25.754 --> 00:00:29.551
The scientific basis belongs to the actual
application.

9
00:00:30.301 --> 00:00:34.909
For our fictional example, requirement
URS-01 states that

10
00:00:35.059 --> 00:00:39.859
product-contact materials must be
identified and supported by approved

11
00:00:40.009 --> 00:00:44.169
compatibility evidence for the defined
product and cleaning agents.

12
00:00:44.319 --> 00:00:47.135
The design review checks the proposed
materials.

13
00:00:47.285 --> 00:00:51.893
Later verification checks the installed
materials and supporting records.

14
00:00:52.043 --> 00:00:56.609
The requirement has an identifier, a clear
subject and an evidence path.

15
00:00:56.759 --> 00:01:01.537
The site defines the actual acceptance
criteria and document controls.

16
00:01:02.287 --> 00:01:06.746
Consider a training-only temperature
indication requirement: within the

17
00:01:06.896 --> 00:01:11.141
selected operating range, indication error
must remain within a

18
00:01:11.291 --> 00:01:16.643
project-defined tolerance when compared
with a suitable calibrated reference.

19
00:01:16.793 --> 00:01:21.465
The range and tolerance are not supplied
here because the process basis is

20
00:01:21.615 --> 00:01:22.705
still missing.

21
00:01:22.855 --> 00:01:26.396
This is a deliberate unresolved
requirement, not a pass.

22
00:01:26.546 --> 00:01:31.240
The exercise asks you to identify the
information needed to finalize it

23
00:01:31.390 --> 00:01:33.182
before procurement or testing.

24
00:01:33.932 --> 00:01:38.476
Requirements evolve as knowledge improves,
but uncontrolled changes break

25
00:01:38.626 --> 00:01:39.778
traceability.

26
00:01:39.928 --> 00:01:43.938
If the intended batch range changes,
assess effects on mixing,

27
00:01:44.088 --> 00:01:46.499
measurement, cleaning and verification.

28
00:01:46.649 --> 00:01:49.956
Retain the reason for the revision and the
approval trail.

29
00:01:50.106 --> 00:01:55.783
Do not silently edit a requirement after a
failed test to make the result pass.

30
00:01:55.933 --> 00:01:59.880
In the activity, rewrite three vague
statements and clearly mark any

31
00:02:00.030 --> 00:02:02.440
assumptions that require resolution.