The Njema assessment can be offered in various contractual scenarios to suit different business needs and project requirements. Here are some examples of potential scenarios:
Basis
A unique service from ITM. Creates a complete overview of all entities in the form of a report (PDF and CSV files) in a very short time. Verifies the consistency of the entire application landscape. Indicates certain incidents that require special attention in the subsequent project (see below).
Extended
The results from the „One-time“ scenario are imported into a graphical database (Neo4J). ITM presents links and properties of all entities in the application landscape and analyzes the graphical data on site according to customer requirements (result: graphs, reports and exported data). This variant should always be carried out before larger projects.
Ongoing
ITM provides the functionality of the Njema Assessment along with the customer’s current source code on a dedicated server. The customer has read-access to the entity repository and can query the graphical database. This option is often used during project implementation and for general quality assurance.
Notes on the Nomenclature Used
- A POOL is a logical grouping of entities, e.g., all PL/I programs or all procedures of application XY.
- An ALIEN is an entity for which no source code is available, and its purpose is unknown to us.
- A Known Alien is an entity whose function we know, but for which source code is not available, e.g., a utility.
- A PLUG is a construct that seeks a connection, and a SOCKET is the sought connection point.
- An INCIDENT is a code construct or situation that needs special consideration during the project, for example, requiring a workaround or needing particular attention during testing.
