Get an overview of the architectural structure of your Forms application in relation to the table and program use as well as object and logic distribution
Do you want to learn about your applications dependencies, or if you have dead code in your applications that can be removed?
Would you like to know what libraries, tables, views, and other objects are no longer being used by the applications?
Identify Table & Program Use
Determine Object &┬áLogic Distribution
Develop Error Handling
Identify Security Vulnerabilities
Identify Unused Elements
Many Oracle Forms applications are ten, fifteen, twenty years old or older. During this time, the technical and technological know-how has advanced within┬áthe applications. In many cases, an application was initially written by external developers and further developed internally. The development teams may have changed over the years. The documentation becomes outdated. Parts of the application have been replaced or even decommissioned. Figure out what state the application is in so you can make informed decisions about how to move forward.
- Can we leave everything the way it is?
- Do we want to upgrade our Forms?
- How can we develop it further?
- How do we migrate to ADF or APEX?
- What makes sense for the specific application?
- Do we have enough resources?
- Do we have enough money and time?
With the Development Analysis, you will be provided with the basis to understand your system and improve it if necessary.
The PITSS Development Analysis builds upon the Status Quo Analysis and provides a more in-depth analysis of the results of the Status Quo Analysis. You will receive an overview of the architecture structure of your application in relation to the table and program use, as well as object and logic distribution. This also includes evaluation of error handling, security vulnerabilities, unused program code and tables, and redundancies. These are aspects that have lasting influences on the profitability, reliability, and sustainability of an┬áapplication.
The PITSS Development Analysis
Presentation of Documentation with the Following Metrics:
- Evaluation of objects and their references.
- Use of libraries, global variables, and package variables.
- Program dependencies.
- Distribution of business logic (select, insert, update, delete).
- How the tables are accessed (reading, writing).
- Table dependencies.
- Number of exceptions and exception blocks.
- Distribution of exceptions depending on program size.
- Frequency of use of the program units in a library.
- Frequency of use of a library (e.g. how many forms it is linked to).
- List of all libraries that are unused or used infrequently.
- List of all potential security vulnerabilities.┬á
- A list of all program units not queried.
- A list of all unused tables and views.
- A list of all un-referenced objects in the object libraries.
- Overview of possible savings in summary of program units.
- List of all redundant program units.
What you get:
- Cost evaluation
- Optimization potential
- Detailed documentation
Target Group: IT Managers, Project Managers, and┬áTeam Leaders
Duration:┬áOne Week or Less
Prerequisites: Status Quo Analysis