Hogan® Systems is more than just one of the most trusted brands in the industry.

Hogan is high performance core banking software that is leading banks worldwide into
the future with real-time processing, scalability and lower total cost of ownership.
Hogan can help you drive new revenue opportunities, increase productivity and deepen
relationships with customers, employees, suppliers and stakeholders.

Hogan Systems is an integrated suite of applications that provides online, real-time

access to all of a bank’s customer relationships across the entire enterprise. This allows
a bank to offer its customers convenient, easy access to all of their accounts, how, when
and where they want it. With integrated core banking applications, banks can take
advantage of relationship packaging and pricing to support a bank’s cross-selling and
retention strategies.

1. How to create a customer in Hogan System(Which screen, what details etc.)

2. How to create an account in Hogan System(Which screen, what details etc.)

3. How to post a transaction

4. Where to check the address details of a customer(on what screen)

5. In which screen we can see the customers which are related to a certain customer(Except navigating to
ACRE screen for each account)

6. How to query the data to get appropriate test data(Where to write the query , with an example)

Analysis Tools for Hogan® Systems

Computer Sciences offers an industry-leading package of core banking software called Hogan
Systems. This highly customizable application enables banks to offer a vast array of services
unique to retail and small business customers; in effect, it is the software that makes a bank be a
bank.

Hogan's capability comes with corresponding complexity, which must be managed effectively by
the owning bank and its IT staff. Semantic Designs provides Component Connectivity (CC)
Tools to help the bank and its staff understand how a configured Hogan actually works, enabling
faster and more accurate impact analysis and updates of banking services to its client base.

Hogan is tens of millions of lines of code, organized as:

 Umbrella, the overall architecture

 PEM, which is a combination of:
o a huge metadata database, which is the key customization method for Hogan,
containing:
 Screen layouts and assignments to screen devices
  Data record layouts and assignments to files or databases
 Configuration data directing applications function and sequencing
o a database to store bank-selected record types
o an efficient I/O management facility, directing screen, sequential, heirarchical,
and DB2 database record I/O.
 Thousands of COBOL computation units which carry out actions as directed by the PEM
metadata. Normally these units perform I/O using PEM services, but in practical systems
applications do traditional I/O operations anyway.
 JCL scripts which manage the execution of COBOL jobs

How does one understand a Hogan System?

Bank analysts often want to understand what the bank actually does before deciding how to
approach a new implementation. The IT staff of a Hogan-based bank continually revise the PEM
configuration metadata to add and revise core banking capabilities to meet new demands from
bank management and business analysts. Clearly the raw code is available for inspection. But to
understand what a Hogan system does requires requires a deep understanding of how the PEM
meta-data drives how program elements are sequenced and which programs are accomplishing
which tasks on what databases. As a key example, analysts usually need to know how the Hogan
COBOL programs call one another; each COBOL program consults the meta-data to decide
whether and which other COBOL programs to invoke. Without the instance PEM meta-data, one
simply cannot determine the call structure. In general, almost all linkages between the Hogan
elements are completely controlled by the PEM instance meta-data. To plan a trip, you not only
need a map showing the cities, but you also need to know specifically how the roads connect
them (see GUI example below).

While helpful in exploring the PEM meta-data itself, the traditionally available Hogan inspection
tools from CSC do not handle the indirectness of the metadata control over application execution
and I/O, nor do they have any understanding of the actual source code. Conventional
COBOL/JCL source analysis tools provide no insight because the meta-data driven aspect
coupled with centralized I/O through PEM prevent them from understanding knowing
specifically how the meta data controls the application. Using such conventional tools is a big
improvement over just inspecting code manually, but does not address the key issues to make it
difficult for Hogan users to understand and adjust their Hogan applications. Such tools also
require that such users have deep knowledge of Hogan and code, which is increasingly rare in IT
environments with strained budgets. But failure to understand or revise the applications correctly
can lead to both severe internal and external issues, precisely because this is core banking
software. Owners of Hogan software are always clamoring for better ways to see how Hogan is
organized from their perspective.

SD's Component Connectivity (CC) tool for Hogan processes all the Hogan code elements,
especially PEM, and builds up a repository of information. This includes analysis of the COBOL
code with respect to the specific PEM meta-data. To address the key issue described earlier, the
CC tool uses precise global flow-analysis techniques from the compiler world, to determine
which CALL statements are controlled by which specific PEM meta-data values, and therefore
where such CALLs can lead. It performs similar analyses to determine file and screen accesses
as controlled by PEM. The results are provided in easy to navigate reports and user interfaces.
These reports and UIs provide direct answers the key questions of analysts and IT staff, enabling
them to accomplish their job more effectively and reliably.

The types of information captured by Component Connectivity for Hogan are:

 JCL elements, including Jobs and Procs, what programs are executed and what I/O
resources are assigned to those programs
 COBOL elements, including programs ("compilation units") and copylibs, which jobs
control them, and which files they access
 Screens used, and which programs interact with them
 Files and Database access, by which programs, whether through standard COBOL
facilities or as managed by PEM:
o Flat files used
o Heirachical files used
o DB2 data bases used; for EXEC DB2, provides tables and columns accessed

The Component Connectivity information is acquired using language-precise source code

scanners for COBOL, JCL, PEM and optionally HLASM, and special tools to combie the fine
detail of the elements into a integrated whole.
The information is provided both as an HTML report (with tens of thousands of pages) covering
the entire Hogan system, as well as via a GUI for easy navigation across the components (see
above). Where-used information is provided by program and is precise to source line number.
COBOL program structure is provided to help focus attention on the COBOL program parts
relevent to particular issues. An option provides access to the COBOL source code, hyperlinked
for full cross reference.

See a full Component Connectivity example with explanation.

Contact Semantic Designs for further details.

Hogan is a Registered Trademark of Computer Sciences Corporation.

Request a Free Migration Consultation

 Search SD

Topics

 Re-engineering
 Documentation
 Assessment
 Improvement
 Code Generation
 Hardware Description Languages
 All Topics

Language:
J ava

Product:
Front End

Semantic Designs- Our Goal

To enable our customers to produce and maintain timely, robust and economical software by
providing world-class Software Engineering tools using deep language and problem knowledge
with high degrees of automation.