<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse-Engineering on Ole M.R. Rabanal</title><link>https://omrr.no/tags/reverse-engineering/</link><description>Recent content in Reverse-Engineering on Ole M.R. Rabanal</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 01 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://omrr.no/tags/reverse-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering the business logic from an integration platform</title><link>https://omrr.no/projects/integration-platform-recovery/</link><pubDate>Sat, 01 Oct 2022 00:00:00 +0000</pubDate><guid>https://omrr.no/projects/integration-platform-recovery/</guid><description>&lt;p&gt;A food company was building a new integration platform for products delivered&#10;by subcontractors. The system it was replacing was live, unversioned, and the&#10;only remaining record of a large amount of business logic.&lt;/p&gt;&#10;&lt;h2 id="context"&gt;Context&lt;/h2&gt;&#10;&lt;p&gt;August to October 2022, through Sopra Steria.&lt;/p&gt;&#10;&lt;p&gt;The legacy system had to move, but a great deal of its business logic was not&#10;easy to reach. The deployed Java was unversioned — no history to read and no&#10;intermediate states to compare, so the reasoning behind any given behaviour was&#10;not recoverable from the code alone. Alongside it sat databases whose stored&#10;procedures also needed investigating and documenting. The logic had to be&#10;improved and optimised on the way out, not simply transcribed.&lt;/p&gt;</description></item></channel></rss>