startthat.work home

Steps 2 and 3: Rule out and choose analysis techniques

Step 2: Rule out techniques

Code tests every technique against the description of the material. A technique that fails a requirement is removed. The requirements are applied in this order.

  1. Personal information. A technique that cannot take personal information is removed when the material has it. It is kept, with a note, when de-identification is in the plan and runs before it. It is removed when the material is marked sensitive and the user has not agreed to de-identify.
  2. Requirements that always apply: content type, unit of analysis, level of detail available, number of sources and whether sources can be joined. A unit that a preparation technique can derive passes with a note.
  3. Requirements that apply in some cases: structure, time structure, how the sample was chosen, amount of material, known data problems, language, minimum amounts and additional sources needed. Each applies only when its stated condition is met.
  4. Each technique's own exclusions and inputs. A technique whose input cannot exist yet, or that needs an additional source (a comparator, a reference structure or an earlier period), is kept with a note naming what is missing.

One waiver applies. A technique that fails only on content type or structure is kept, with a note, when every prepared input it needs is produced by an eligible technique. The level of detail, the unit of analysis and the other requirements are never waived.

Step 2 also counts the eligible techniques that reach the strength of statement needed, and warns when none does.

Step 3: Choose analysis techniques

The model receives the brief and a one-line entry (ID, name, purpose, use when) for every eligible technique. The entries are ordered by a score for kind of finding and evidence status. The score changes the order only.

The model chooses at most 10 techniques, using these criteria in order:

  1. Every part of the request has at least one technique.
  2. At least one technique reaches the strength of statement needed, when an eligible one fits the request. If none fits, the model says so and gives the reason.
  3. The techniques match the kind of finding wanted, where the user gave one.
  4. Where two techniques serve the same part of the request, prefer a pair with different methods, so that their agreement adds confidence (section 7).

The model records a one-line reason for each chosen technique, naming the part of the request it serves. The reasons are kept with the plan (section 5). The chosen techniques are work (section 7), so the user sees them only where the application shows work. Where it does, the user can change the list but is not asked to choose from it.

Limits. All kinds of technique count towards the 10. Preparation techniques added for a chosen technique, de-identification and library checks do not count. Techniques the model wanted beyond the limit go on the reserve list. A follow-up round adds at most 5. The numbers are defaults chosen here, not measured.