{"id":460,"date":"2015-01-29T13:17:05","date_gmt":"2015-01-29T11:17:05","guid":{"rendered":"http:\/\/patrick4pitss.wordpress.com\/?p=149"},"modified":"2017-09-19T13:13:50","modified_gmt":"2017-09-19T11:13:50","slug":"assessing-the-status-quo","status":"publish","type":"post","link":"https:\/\/pitss.org\/de\/assessing-the-status-quo\/","title":{"rendered":"Assessing the Status Quo"},"content":{"rendered":"

Status Quo Analysis at a glance<\/h2>\n

\"status<\/a>The Status Quo<\/a>\u00a0analysis provides you with all the important information about your Oracle Forms application, like the quantity structure, code allocation, program sizes, lines of code (LOC), lines of documentation (LOD) and a complexity analysis. You gain an initial assessment of your application and the amount of effort required for any development or modernization projects. The Status Quo Analysis of your Oracle Forms application is the central starting point to improving quality, optimizing projects, avoiding wrong decisions, preserving investments and saving money and time.<\/p>\n

Components in detail<\/h2>\n

Quantity Structure<\/h3>\n

Metrics for all the objects of an Oracle Forms application.
\nThis includes the number of database objects, forms, libraries and reports as
\nwell as their included objects such as windows, canvases, blocks, items,
\nprogram units, etc. This number can show if you handle a big, medium or small size application. They show the relation between Forms and Reports. It also indicates the the usage of PL\/SQL and Object Libraries. Also the relation between the Database and Forms\/Reports Modules is but in perspective.<\/p>\n

Graphical Elements<\/h3>\n

The Overview of the Graphical Elements gives you a detailed inside View of the Objects of your Application, that are used for the interaction with the user. These Key Numbers are necessary for a better understanding of the Complexity, Performance and Maintainability of your Application<\/p>\n

Lines of Code (LOC) \/ Lines of Documentation (LOD) \/ Empty Lines \/ Referenced Lines<\/h3>\n

LOC \u00a0are the sum of all Lines in your Application. LOD is a sub sum, of a count of all Lines with a Inline Comment. Empty Lines are all Lines with no Code or Comment, but maybe tab or space characters. Referenced Lines are the the number of Lines, that are referenced from a external Source (PLL, FMB, OLB). All these numbers can give a first impression on the quality of the Documentation and Modularization of your Application.<\/p>\n

Program Sizes<\/h3>\n

In this report we show the average values such as line length, number of lines, variables, arguments\u00a0for each program unit.
\nOne Indicator for Program Logic is a high usage of Variables and Arguments. Both are temporary data storage of a specific Datatype inside a Program Unit.<\/p>\n

Program Structure<\/h3>\n

Here you can get a view on the General structure of the program units under consideration of the program\u00a0blocks, anonymous program blocks and exception blocks.<\/p>\n

In the Program Structure we evaluate the Content of the Program Units. Program Units that only contain Oracle Forms Build-Ins that control the UI but have no SQL are called as\u201dPure GUI\u201d. In general they control the Navigation- and Access Logic.
\nProgram Units that contain whether Build-Ins nor SQL are marked as \u201cValidation\u201d Untis.
\nProgram Units that call SQL but no Build-Ins are highlighted as Business Logic. For the reason of Modernization and Performance these are candidates to move the logic to the DB.
\nAll the Rest is combined under the Title \u201cMixed\u201d and need further analysis, if they are more Navigation- and Access Control Logic or more Business Logic.<\/p>\n

Code Distribution<\/h3>\n

Is a Overview that shows the state of the program logic (e.g. validation,
\nnavigation, etc.) and the business logic (DML).<\/p>\n

Complexity Inspection<\/h3>\n

Her we perform a Inspection of the objects in relation to the metrics listed above, i.e.
\nwhere which objects are used how. It gives a\u00a0General overview of the number of complex PUs evaluated according to\u00a0the number of statements in %.<\/p>\n

Complex Part of your Application will reduce the Maintainability and make Enhancements harder. One of the main reasons of a to high complexity is the lack of Modularisation of part of your Application.
\nModules with a high Complexity should be seperated into several Sub Units. E.g. Extract rarely used smaller view into a new Module and pass the Data via Forms Parameters.<\/p>\n

Summary<\/h2>\n

The Status Quo Analysis gives you a great Overview of your Oracle Forms Application and Starting Point for further Analyses. If you like to enhance, extend, upgrade or Migrate your Application we can provide you with the right Information to make a decision on a solid ground.<\/p>\n

Please take a look at all of our Analysis we offer: Tool Supported Analyses<\/a><\/p>\n

You can also take a look at a previous Post about an Overview of our Analyses:\u00a0Getting an inside View of your Oracle Forms and Reports Application<\/a><\/p>\n

\"\"<\/a> \"\"<\/p>\n","protected":false},"excerpt":{"rendered":"

Status Quo Analysis at a glance The Status Quo analysis provides you with all the important information about your Oracle Forms application, like the quantity structure, code allocation, program sizes, lines of code (LOC), lines of documentation (LOD) and a complexity … Continue reading →<\/span><\/a>\"\"<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[112,113,82,105,106,100,114,98,109,84,101,81],"tags":[],"class_list":["post-460","post","type-post","status-publish","format-standard","hentry","category-analyse","category-entwicklung","category-forms","category-forms-analysis","category-forms-complexity","category-general","category-migration","category-oracle-forms","category-oracle-forms-development","category-pitss","category-pitss-con","category-tech-blog"],"_links":{"self":[{"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/posts\/460","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/comments?post=460"}],"version-history":[{"count":1,"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/posts\/460\/revisions"}],"predecessor-version":[{"id":17001,"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/posts\/460\/revisions\/17001"}],"wp:attachment":[{"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/media?parent=460"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/categories?post=460"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pitss.org\/de\/wp-json\/wp\/v2\/tags?post=460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}