Business Rule Identification and Extraction through Netron HotRod

How do you migrate from a legacy COBOL system to a modern architecture and ensure that your existing business functionality will still work?

For years you have relied on COBOL as your application development language –– and for batch processing huge amounts of data, it’s hard to beat. But now, your customers are demanding better access to their accounts; your operational units need real-time updates to their data; your supply channel partners insist on closer integration with their systems –– and it seems that just about everything needs integration with the Web.

While COBOL is still efficient at data processing, the language has become much less strategic to the future, because it has lagged in its support for the Internet, layered application architectures, distributed systems and code reuse. By comparison, modern language environments offer ready-to-use class libraries and application objects for Internet, data and Web Service access.

For these and other strategic reasons you have decided it’s time to convert your system to a modern development and deployment platform that will serve your business for the next decade. But can you afford to re-analyze, rebuild and rewrite everything from scratch? Converting to an object-oriented paradigm will require you to morph your business rules into a new class-based object architecture. The challenge in the conversion is getting the correct design requirements. The best definition of the existing requirements is in the current system, and you need to find them quickly. The most compelling reason to reuse your existing business logic is to accelerate the time to market for the replacement system. The next most compelling reason is to reduce risk –– by ensuring your requirements are complete.

The fact that your current system contains millions of lines of COBOL code compounds the problem. The presence of cloned logic further complicates the matter. You need something that can:

• quickly identify business rules in large COBOL systems
• associate the rules with the filmy porno related data;
• isolate this information into a component design with an interface;
• identify and help eliminate redundancies in the rules
• provide a means to document the rule and extract it from the old system
Netron HotRod™ is the most advanced solution for identifying business logic, isolating and documenting the code that supports the business functionality, and wrapping it in an interface that can be extracted and used to create the business objects in the new architecture.

Why testing?

Verifying that all requirements are analyzed correctly

Many serious software failures are often the result of wrong, missing or incomplete requirements formulated at the requirement analysis stage. Testing, therefore, verifies that requirements are relevant, coherent, traceable, complete and testable. This is the reason why testing really begins at the outset of a project during the requirements specification phase, prior to the generation of a single line of code.

Verifying that all requirements are implemented correctly

Adequate testing ensures that software operates as expected, providing correct user response and works as per requirement specification. Comprehensive Testing reduces the risk in the marketplace, minimizes system downtime, and increases the confidence in systems for customers and department staff. The key to software testing is trying to find the myriad of failure modes.
Any software application should be examined, tested and analyzed for risk of failure as per the requirement before it is launched into the market and used by the customer.

Identifying defects and ensuring they are addressed before software deployment

It is important to identify the defects at an early stage in the software engineering lifecycle otherwise it could pose a big problem at the time of deployment of the software application. If these defects are identified early and addressed properly it will reduce the cost of development to the extent of 10x as compared to a point when it gets identified after the deployment. The other major factor associated with this problem, not measurable in absolute terms but of more significance to the organization is losing the confidence of the customer and the resulting embarrassment.

Case study

– Simulation model of shipping system with multiple stockpiles around South East Australia, including ship scheduling.
– 20% production increase at Western Australian gold mine.
led benchmarking team to identify major improvement opportunities for a bulk handling wharf, including implementation planning.
simulation of a wharf operation to evaluate the impact of reducing the number of berths on ship delays.
– assisted a client to document business processes using IDEF0 methodology.
led client team to review service level and technology for an auxiliary site service.
– led client teams developing Performance Measures for an Australian wide distribution project.
– assisted a Tasmanian client with shipping contract negotiations.
developed first level benchmarks for a distribution project and designed second level benchmarking procedures.
– led consultant team to assist a Western Australian client renegotiate their 45 MW electricity contract. Prepared business analysis and negotiating case. – Prepared Negotiations Summary Document and presentation materials for meetings.
– Provided strategic advice and assisted with negotiations.
part of team reporting on the redevelopment of the North Hobart oval.
– Produced project evaluation section.