Oracle Forms Code Analysis with ORMIT-Analyzer 12c

Oracle Forms Code Analysis with ORMIT-Analyzer 12c

Can you afford the hidden costs and risks of under-optimal Oracle Forms Code Quality?

ORMIT-Analyzer identifies the risks and eliminates the surprises by accurately scanning the code of any Oracle® Forms and Reports Application for  upgrade, migration or development projects.

Analyze your Oracle Forms code with ORMIT™ today

  • Dead-Code, Redundant Code, Business Logic Distribution, Source Code Quality

  • Oracle Forms code X-Ray Scan Technology

  • Estimate the efforts of a Forms Upgrade to 12c or Migration to ADF

  • Oracle Forms Objects Dependencies Analysis

Can you afford the hidden costs and risks of under-optimal Oracle Forms Code Quality?

Customized Oracle Forms/Reports application development brings high levels of flexibility but with years of code maintenance and modifications, your application code documentation is obsolete 90% of the time.

ORMIT-Analyzer also helps prepare a potential application modernization project with the objective to protect the investment in the existing business logic and to achieve easier maintainable, more modern software architecture. 

Several factors can affect by your code quality such as its consistency, redundancy, dead-code:

  • Development staff turn-over throughout the years;
  • Functional & Technical application documentation inaccuracy; 
  • Mixed coding standards;
  • PL-SQL and SQL source code and business logic distribution.

ORMIT™-Analyzer gathers the following type of input

  • X-Ray Scan of all modules: Forms, Reports, PLLs, Object Libraries
  • Object count per module: Blocks, Items Canvases, Windows, LOVs, Program Units, Triggers, Built-ins
  • Ratio of unused objects (Dead-Code)
  • Ratio of redundant code
  • Business logic distribution
  • Source code quality
  • Source code dependencies
  • Runtime References : Host Calls, Run Reports User Exits
  • Analysis of references across Oracle Forms objects and modules: Type (dependent or independent), Static, Runtime.
  • Special Aspects considered: Triggers at the wrong level. Triggers with mouse navigation. Obsolete Items and Built-ins. Keywords conflicts.
  • Complexity calculations per module
  • Etc.