tangentum technologies    
 

Deutsch

   
   
 
   

Application Scenarios

Application Scenarios


CodeMonitorTM for Java may be successfully applied in many different usage scenarios. Some of these scenarios are listed below. The CodeMonitor is your product, therefore we are eager to hear from your special problems and the solutions CodeMonitor may provide.

1. Monitoring Java software

Monitoring its behaviour is crucial to ensure confidence in an application. Nowadays applications consist of many different components delivered by many different suppliers. To ensure consistent functionality has become difficult or sometimes even impossible.

Upgrading even a small part of an application, like a library from a third-party vendor, may blow up the whole system making you and your customer dissatisfied.

You have to depend on the promises made by your suppliers and have no chance to verify their statements, because the only effective statements they make, is the software which gets executed as part of your application.

Software is organized in many different ways to fulfill its function. But controlling its performance regarding its purpose is nearly impossible to do in the current technical situation established by your suppliers.

It is therefore necessary to have the ability to get a genuine insight into the software your business depends on.

Unreliable software will lower your ability to perform your business, which will cost you credibility, customers, and last but not least, money.

CodeMonitor is a first step to fundamentally change this inacceptable situation. It enables you to gain insight into the software you depend on.

1.1.

Monitoring access to external resources

With CodeMonitor it is easy to log the access to external resources like the file-system, sockets, or a database. Because the logging statements are woven in automatically into Java bytecode, it is possible to monitor already deployed software.

1.2.

Monitoring Java software already deployed to customer

In some cases, like field-tests and early-stage deployment, the delivered software may contain some bugs which only show up in the customer's set-up. The pressure to resolve these bugs fast is high, but these bugs are sometimes hard to find.

The engineers therefore need tools that help to analyze the behaviour of the software and seemlessly work in the user's run-time environment.

2. Testing Java software

Testing a software system before releasing it to the customer is an important task of the development process to meet some minimum quality criteria. CodeMonitor may support this task in its ability to generate much of the necessary logging code and to make testing more efficient as it is today.

2.1.

Integrated testing in larger projects

In larger projects it is sometimes necessary to integrate the testing activities. With debugging an integrated view on the behaviour of a software system is nearly impossible to gain. Logging enables teams to gather information from different parts of the software system. To make logging really helpful, the output must be homogeneous and flexibly generated. With manually written logging statements, which is state-of-the-art now, the technique of logging doesn't reach its heights and often called “poor man's debugging”. Automatic insertion of logging statements, as CodeMonitor does, complements logging and brings it to full potential.

2.2.

Field-testing

In some cases like field-tests the engineers must be able to check the software quickly under changing test scenarios. Each scenario normally tests different parts of the same software system under different aspects. Therefore the output generated by monitoring the software system depends on the tested scenario.

With CodeMonitor it is easy to systematically configure monitoring of the software system depending on the scenario tested. The engineers get a clearer focus in defining the behaviour of the software system which is relevant in the given scenario. The output generated by CodeMonitor helps to get a more concentrated to-the-point picture of the software system.