Find it in the files, not the field.
Machine-speed analysis of technical specifications. Find contradictions, gaps, and duplicates before sign-off.
For quality assurance & test teams
Nothing ships until your tests pass, so every failure you cannot explain holds up the release. The cause sits somewhere in a specification of thousands of requirements, and finding it means walking back through the V, team by team, with hours of reading and asking around. Wyzer Detective matches the defect description against the specification and returns the few requirements the case is about: the neighbourhood of the needle, not the haystack. Export the specification, paste the description, and your team starts on the right requirements today.
The same defect, two ways through the process. The first is the one most QA teams know by heart.
An integration test fails now and then. When the CPU and RAM run hot, a module boots a little late, a timer expires before it answers, and the system falls back. You cannot reproduce it on demand, so you have a log and a build but no reliable steps. The cause could be in any of roughly 30,000 requirements.
Take the text you wrote for the ticket and give it to Wyzer Detective with the ReqIF export of the specification. Detective matches the description against every requirement and links the defect to the ones it concerns. The matching runs on Sherlock, Detective's analysis engine. Teams that script this step can use the Requirement Scan API (beta): it shows the cost first, runs the search once you approve, and returns the ranked list a page at a time.
What comes back is a short list: the requirements that govern the same signal, from every module, laid out in the relationship graph. Several of them define the timeout for the same signal with different values. Each reads fine alone, but they cannot all be met. The finding carries the requirement IDs and a severity.
The ticket no longer says "behaves inconsistently". It names the requirements that conflict, and notes which of them the software met. Engineering gets a precise pointer, product gets a question about the specification, and nobody has to defend a decision they did not make.
A body-control and powertrain integration build: roughly 30,000 requirements across twelve supplier-facing modules. A regression test fails sporadically, and nobody can reproduce it on demand: it may be nothing more than a boot delay, caused by CPU and RAM temperature, that times out a timer. The defect travels from the software team to the supplier to the system architect, and every hand-off costs a retest, because nobody can say quickly which requirements it touches. With the defect description matched to the specification, the first reviewer gets about ten requirements, two of them in conflict, and sees at once that it is a question about the specification.
This example illustrates the class of defect Wyzer Detective helps trace. It is not a specific customer engagement. Detective works on your specification, not on your defect tracker or test logs. You paste the description of the defect, and there is no integration to set up.
These are the release criteria QA is measured on and holds everyone else to. The bar stays where it is. With the relevant requirements attached to the defect, each one gets quicker to meet.
Indicator
Without a traced origin
With Wyzer Detective
Time to root cause
Days of reading the specification and asking around, while teams argue whether it is code, hardware or specification.
The few relevant requirements are found from the defect description, and any conflict between them is marked on the ticket.
Reopen rate
Fixed against one requirement, reopened because a second one still conflicts.
Every requirement in the same conflict is visible before anyone scopes the fix.
Defect leakage
Specification-origin defects are found last, at the most expensive point.
The same finding shows up when the specification is checked, before tests run against it.
Retest cycles
Retests spent confirming a fix for a requirement nobody had settled.
Ambiguous acceptance criteria are flagged, so the test has something definite to check.
Audit trail
A defect is closed with a note. The link to the specification, and to the standards the project says it follows, lives in people's heads.
The defect is tied to the requirements it concerns, so the standards you claim to follow can be checked against them.
QA teams see what the specification costs before anyone else does, which puts them in the best position to push for an earlier check, together with product and engineering. Each step below starts from a finding QA already holds, and the team on that side of the V can act on it without changing how it works.
Detective provides QA withThe requirements behind a failed test, with the conflicts between them marked and their IDs.
So that QA canask requirements engineers to run the same check before the next release of the specification, so this kind of defect never reaches a test.
Detective provides QA withThe signals and interfaces where requirements from different modules disagree.
So that QA canshow architects where a boundary is under-specified while it is still cheap to move.
Detective provides QA withThe neighbourhood of every requirement a fix touches, before the fix is scoped.
So that QA canhave developers close the whole conflict in one change instead of one requirement at a time, so the ticket stays closed.
Detective provides QA withA finding that names requirements and where they sit.
So that QA canopen the supplier conversation with a question about the specification instead of a dispute about fault.
It matches the text of the defect description against every requirement in the specification, by meaning and not only by keyword, and links the defect to the ones it concerns. Instead of reading the whole specification you get a short list, with conflicts, ambiguity and gaps among them marked. All you need is a ReqIF export of the specification, or of the subsystem your failure touches, and the description. Results come back within minutes.
No. You paste the description of the defect, and Detective matches it against your specification. Logs and field data stay where they are. That keeps the analysis traceable and means you can start without an integration project.
Yes, and that is where the search through the specification costs the most. A failure that depends on temperature or load gives you no steps to follow, but the description of what happened is enough to find the requirements that govern that behaviour, such as timeouts that disagree across modules. Detective does not reproduce the defect. It shows you where the specification may have allowed it.
Yes, through the Requirement Scan API, which is in beta. You send the defect description, with any tables or images, and it shows you the cost before anything is charged. The price is one credit per query, whatever the size of the specification, and paging through the results is free. If a search fails, the credit is refunded. It reads the analysis you have already run, so the specification must have been analysed first.
It gives the audit trail a link that usually sits in people's heads. The defect is tied to the requirements it concerns, so the standards your project claims to follow can be checked against them.
Both, working from the same findings. Requirements engineers run it before a specification is released. QA runs it afterwards, starting from a failure, to see whether the defect began in the specification. The report is the shared reference between the teams.
Bring them a finding from your own failure instead of a pitch. A conflict that already cost a retest is the strongest argument for checking earlier, and they can open the report and verify it themselves. The same analysis runs on any specification, so the check moves left without a new process.
Same day. Export a ReqIF baseline, upload it, and Sherlock returns quality scores, contradictions, and coverage gaps within minutes. No configuration, no training data, no integration project.
No. Customer data is not used to train the system and is not exposed to other customers or external models. Data is encrypted at rest.
In the EU. Wyzer's infrastructure runs in an EU region, isolated to your environment, with standard retention capped at 90 days by default.
No practical one. Sherlock has been tested to tens of thousands of requirements with no degradation in output quality: it processes specifications in parallel batches rather than reading them end to end.
No. Reviewers keep working in the requirements tool they already use. Wyzer Detective runs before or alongside the existing review, and relevant findings get applied back into that review. It's a quality-gate step, not a new system to adopt.
Credit-based pricing that scales with the number of requirements in your specification and how complex they are (plain text vs. requirements with tables or diagrams). There's no fixed per-seat licence. Get in touch for a quote sized to your specification. Searching a finished analysis with a defect or failure description (the Requirement Scan API, in beta) costs one credit per query, whatever the size of the specification.
Yes. Any ReqIF export works as the reference: a published standard, an internal template, last year's baseline, whatever you want the current spec measured against. The comparison runs requirement by requirement, not as a single aggregate score, so you can see exactly which ones fall short.
Export the specification your failing test touches, add the defect description, and get the relevant requirements back within minutes, with contradictions, ambiguity and gaps marked by requirement ID.
← See the full product