01Independent verification

AI should not be the only reviewer of its own code

Visual Expert verifies PowerBuilder, Oracle PL/SQL and SQL Server T-SQL code with deterministic, rule-based analysis. The same rules give the same results at every analysis, whoever or whatever wrote the code.

  • Bugs, vulnerabilities and quality issues detected by inspection rules.
  • New defects reported for each analysis, so you see what a change introduced.
  • Continuous inspection in your CI/CD pipeline, before deployment.
SAME RULE SET · EVERY ANALYSISInitial codeAnalysis 1Developer changeAnalysis 2AI-assisted changeAnalysis 3NewDefectResolvedNewintroduced by the last change
The same rules run on every version of the code, whoever wrote the change.
02Application context

An AI assistant sees the code it is given, not the whole application

Visual Expert models the whole application: callers and callees, database tables and columns, and the dependencies between PowerBuilder, PL/SQL and T-SQL code. You see what a change can affect before you make it.

  • Impact analysis on functions, procedures, tables and columns.
  • Call graphs and reverse call graphs to follow chains of calls.
  • PowerBuilder and database code analyzed together in one project.
WHAT VISUAL EXPERT MAPSCALLERSCHANGEDATABASECode given to an AI assistantWindow eventPackageFunctionTableColumnViewChanged procedureAffected by the changeDependency found by the analysis
A change seen with its callers and the data it uses.
03Runtime evidence

AI can spot code that looks slow. Runtime data shows what is slow.

Visual Expert combines execution statistics with its model of the application, to locate the procedures, objects and call chains that actually slow it down.

  • Oracle and SQL Server: statistics collected from the database, ideally in production.
  • PowerBuilder: execution traces collected on user workstations in production.
  • Slowest code, cumulated execution time and execution time along a chain of calls.
EXECUTION TIME · MEASURED IN PRODUCTIONProcedure AWindow event BTrigger CFunction DProcedure EFunction FActual hotspot</> Looks inefficient in the codeALONG THE CALL CHAINWindow event BProcedure ATable
Measured execution time points to the real bottleneck.
04Managed remediation

More code changes mean more findings to review, decide and track

Visual Expert keeps the status, decisions and history of each finding across analyses, and the next analysis confirms whether a fix worked.

  • Qualify findings: false positive, accepted risk or on hold.
  • Assign a defect and a task is created, with an assignee, a priority and a due date.
  • Mark as fixed: the defect waits in Pending Validation until the next analysis checks it.

Defect lifecycle

OpenPending ValidationResolved
Developer marks it as fixedSet by the next analysis

Reviewed defects can also be set aside. Their history is kept.

Risk AcceptedFalse PositiveOn Hold

Your AI tools write code. Visual Expert verifies it.

Visual Expert does not replace the AI tools your developers use. It adds an independent verification step around them.

Your developersand their AI tools
Visual Expert
01Generate
AI assistants, coding agents or developers write or change the code.
02Verify
Same rules, every analysis. New defects are flagged.
03Understand
Callers, data usage and the impact of the change.
04Fix
Developers fix the code, with or without AI.
Tasks and owners. Built-in AI suggests fixes in context.
05Verify again
A new analysis confirms the fix.
AI can suggest. Analysis can verify. Governance determines what gets accepted.
Built-in AI that works in context

Visual Expert's AI explains code and suggests fixes from the selected code, its dependencies and database usage, as identified by the analysis.

Visual Expert AI

Verify your own code with Visual Expert

Try it on your PowerBuilder, Oracle or SQL Server code, or ask our team for a demo.