Skip to content
Avecas
Avecas

SYSTEM-LEVEL TEST

System-level test

Exercise silicon in representative system workloads.

Discuss your requirements
Hands holding electrical measurement probes

Representative photograph · Hands holding electrical measurement probes.

THE ENGINEERING SCOPE

Built around
your requirements.

Explore the approach ↓
01

Technical starting point

Application scenarios, boards, firmware and environmental limits.

02

Acceptance evidence

Long-run stability, interactions, throughput and recovery.

03

Delivery package

SLT scenarios, automation, logs and issue summaries.

CLIENT GUIDE

Scope system-level test with the right evidence.

Use these technical checkpoints to make the first project review productive.

Provide before the review

  • Application scenarios
  • Boards
  • Firmware and environmental limits

Review during execution

  • Long-run stability
  • Interactions
  • Throughput and recovery

Agree for delivery

  • Slt scenarios
  • Automation
  • Logs and issue summaries

HOW WE WORK

Clarity at each stage.

01

Build workload matrix

The initial review establishes the baseline using application scenarios, boards, firmware and environmental limits. Record gaps and dependencies before implementation.

02

Automate execution

Carry out the agreed work against the reviewed baseline. For system-level test, keep the interfaces and configuration used by this stage visible to the receiving team.

03

Capture telemetry

Retain the intermediate artifacts and review long-run stability, interactions, throughput and recovery. Investigate failures before using these results as an input to the next stage.

04

Triage system failures

Package SLT scenarios, automation, logs and issue summaries. Review unresolved findings against the agreed acceptance criteria and assign ownership for follow-up.

PROJECT DECISIONS

Know what moves the work forward.

Use these gates to agree readiness, review evidence and responsibility at each stage.

  1. 01

    Baseline ready

    Are the starting inputs complete enough to proceed?

    Review method and evidence

    Application scenarios, boards, firmware and environmental limits.

    Review evidence

    Record input revisions, missing material and who can resolve each dependency.

  2. 02

    Implementation reviewed

    Has the work addressed the agreed technical objective?

    Review method and evidence

    Exercise silicon in representative system workloads.

    Review evidence

    Keep the intermediate artifacts with review comments and the decisions that changed the design.

  3. 03

    Evidence checked

    Can the result be reproduced and interpreted?

    Review method and evidence

    Long-run stability, interactions, throughput and recovery.

    Review evidence

    Capture the configuration, expected result, observed result and unresolved findings.

  4. 04

    Handoff accepted

    Can the receiving team use the delivery package?

    Review method and evidence

    SLT scenarios, automation, logs and issue summaries.

    Review evidence

    Review build or execution instructions, known limitations and ownership of follow-up actions.

INPUTS & OUTPUTS

What the work involves.

The final statement of work defines the scope and acceptance criteria.

Client inputs
Application scenarios, boards, firmware and environmental limits.
Engineering sequence
Build workload matrix; automate execution; capture telemetry; triage system failures.
Outputs to agree
SLT scenarios, automation, logs and issue summaries.

TECHNICAL DECISIONS

Planning system-level test.

Read the technical guide

The engineering objective

Exercise silicon in representative system workloads.

The work starts from application scenarios, boards, firmware and environmental limits. The team should identify the authoritative revision of each input and record any assumptions needed to proceed. This prevents a later result from being interpreted against a different specification or configuration.

What needs technical attention

System tests complement structural tests; neither replaces the other.

The review centres on long-run stability, interactions, throughput and recovery. Each finding should identify the input revision, observed behaviour and supporting evidence. Distinguish a confirmed defect from a configuration issue, an unsupported case or an open engineering question before deciding how to resolve it.

How the work is reviewed

The practical sequence is: build workload matrix; automate execution; capture telemetry; triage system failures. Intermediate reviews allow the client to resolve decisions while changes are still manageable. If an input changes, identify the affected activities and repeat the checks that depend on it.

The expected package comprises SLT scenarios, automation, logs and issue summaries. Acceptance criteria should specify what the receiving team needs to reproduce, inspect or integrate these artifacts. Include known limitations and outstanding actions in that package, rather than assuming that delivery of a file implies acceptance.

Link measurements to configuration and sample history

Test and manufacturing-support work relies on traceable device, board and measurement information. Keep sample identity, lot or revision, fixture version, instrument settings and environmental conditions with the results. Establish how limits are chosen and which reference measurements support them. A result without these conditions can be difficult to compare after a fixture, device or software change.

Correlation should precede optimisation. Compare repeated measurements, investigate setup sensitivity and distinguish contact or fixture failures from device behaviour. When looking at yield, segment data by the relevant conditions instead of treating an aggregate trend as a root-cause finding. Changes to test order, settling time or limits can affect the distribution and must be recorded.

Coordinate release requirements with the actual assembly, test or fabrication partner. Confirm the format and ownership of interface files, test programs and acceptance records. Design engineering support does not imply ownership of a manufacturing line, procurement responsibility or qualification authority. Destructive analysis, stress testing and sample consumption need a defined sequence and approval boundary within the project plan.

An illustrative review scenario

A device appears to fail only on one fixture. Repeat the measurement under controlled conditions, compare contacts and calibration, and use a known-good reference where available. Preserve the original failing data before changing the setup. The aim is to distinguish device failure from the measurement chain; this illustration does not establish a diagnosis for an actual sample.

Turn a system requirement into a reproducible test

Choose a scenario that crosses the relevant hardware and software boundaries. State the board revision, firmware build, peripheral configuration, input stimulus and expected observation. For example, an interface recovery test needs a defined fault, a permitted recovery interval and a clear condition for successful resumption. Capture time-correlated logs so a symptom can be traced across layers instead of being attributed immediately to one component.

Define the conditions around the test as carefully as the main action. Power state, network availability, storage contents and prior resets can affect the outcome. Include nominal operation, boundary conditions and recovery after interruption where these are in scope. Repeat failures with the same configuration before changing several variables at once. Record when a test cannot run because of a missing fixture or unavailable instrument; a blocked case is not a passed case.

The handoff should contain the procedure, configuration, observations and disposition of failures. Identify which results come from physical hardware and which come from simulation or a host-based environment. Agree the representative system configurations rather than implying that one result covers every product variant.

BEFORE WE BEGIN

Project questions.

A clear conversation is the start of a strong engineering relationship.

What inputs are needed for system-level test?

The starting review needs application scenarios, boards, firmware and environmental limits. Share the current revision and known limitations so the scope reflects the actual design state.

What does the system-level test handoff include?

The statement of work can define SLT scenarios, automation, logs and issue summaries. The final package should include review results and any open actions.

Which technical risks need particular attention?

System tests complement structural tests; neither replaces the other.

Can we start with a focused technical review?

The first work package can be a review of the available inputs and the engineering questions that must be resolved. Agree its boundaries, access requirements and expected findings before committing to a larger implementation. A review should leave an actionable list of decisions, dependencies and next steps.

How are changes and unresolved findings handled?

Tie each finding to the relevant revision and supporting evidence. A change should identify the affected interfaces, activities and checks. Confirm its effect on scope and delivery with the responsible owner. At handoff, distinguish closed findings, accepted limitations and open work so that a file transfer is not mistaken for technical acceptance.

PUT THE WORKFLOW IN CONTEXT

Explore the engineering decisions.

Practical reading to help prepare your project discussion. Studies are illustrative; they do not report client results.

Connecting DFT deliverables to manufacturing test ↗

YOUR NEXT CHAPTER STARTS HERE

What will you
build next?

Bring us your engineering challenge.
Let’s define the path from idea to implementation.

Start a conversation