Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:

Table of Contents

Target audience:

CAST Administrators

Summary: This section discusses the way CAST AIP analyzes PeopleSoft projects and describes the specific metrics that form part of the standard CAST Quality Model.

Architecture and analysis principles

The image below describes the entire process of computing quality assessments of PeopleSoft projects, from the extraction of the PeopleSoft source code and meta-data to the integration of the quality results into the standard CAST dashboard:

Discrimination process

The purpose of the discrimination process is to identify differences between the standard installation (also called Vanilla) and the project environment.


In order to identify these modifications, we require the source code delivery for the Project and the Vanilla. To integrate them, we create two Analysis Services:

  • Project Analysis Service: contains the results of the technical analysis of the current version of the PeopleSoft project
  • Vanilla Analysis Service: contains the results of the technical analysis of the baseline of a PeopleSoft implementation. This Analysis Service should not be undergo snapshot generation each time and for each project. It should instead undergo snapshot generation each time the Vanilla changes (patch, upgrade etc.). This Analysis Service can be used by multiple projects.

PeopleSoft technology coverage

The objects listed below are all the object types that a PeopleSoft analysis will deliver in the Analysis Service. With these objects, CAST is capable of supporting a set of quality rules to provide a customer with a good overview of the current technical status of a PeopleSoft application. It is not the intention of Cast to capture all details and syntaxes; a coupling between requirement and detection is made.

PeopleSoft artifacts and their relations

The PeopleSoft extension is now capable of detecting a much larger number of objects, properties and links. All of these artifacts are mentioned in this picture, but in essence, all PeopleSoft objects are supported:

  • User
  • Role
  • Permission List
  • Component Interface
  • Menu – We distinguish different types:
    • Menu
    • Popup
  • Component
  • Message Channel
  • Message Node
  • Message
  • Page – We distinguish different types:
    • Page
    • Sub
    • Secondary
  • Application Engine – We distinguish different types:
    • Standard
    • Upgrade only
    • Import only
    • Daemon only
  • Transform only
  • Style Sheet
  • Record – We distinguish different types:
    • Table
    • View
    • Derived
    • Sub
    • Dynamic
    • Query
    • Temp
  • SQL – We distinguish different types:
    • View
    • SQL
    • AE step
  • DBField
  • Application Package
  • Peoplecode – We distinguish different types:
    • Event
    • Function
    • Class
    • Method
  • Field format
  • Mobile Page
  • HTML
  • Query
  • File Layout
  • Business Process
  • Activity
  • Process group
  • Job
  • Process