GizmoxTS - How to answer the question: Where do Software patents come from?

How to answer the question: Where do Software patents come from?

Thursday, 23 November 2017 12:48
(and in particular, could they support a claim for a sole supplier status in bids?)

mom and child


First there was an idea.  Even before that there was a need.  Some of us started to see a growing need for modernizing enterprise scale desktop applications based on the RAD tools of the 1990s such as VB6 and PowerBuilder.  These applications may be performing core business tasks in Insurance, government finance or manufacturing, but compared to current web based, mobile ready applications they were starting to show their age.

We can go even further back, when legacy application modernization had a very clear meaning – migrating mainframe applications, usually to open systems and with modern databases.  But legacy applications are a moving target and now we were faced with re-architecting monolithic or Client/Server desktop applications to a completely different architecture – that of a modern web application.



And then they start reading…



(Semantic code reading & DOM creation is unique…)
kids

Guy Peled, CTO and founder here at Gizmox Transposition has already described in detail the unique approach to application modernization  he has chosen which can be summed up as Semantic Code Understanding. 

Semantic Code Understanding uses compiler technology to let our tool build an internal representation of the source application which in turn allows the tool to re-create a new well architected version of the application on an entirely different platform while retaining the original functionality.  See here and here for a more detailed discussion of the actual process.

So Gizmox built a migration tool  based on Semantic Code Understanding and started to perform migrations with it.  This was already quite unique, and the quality of the re-architected applications was quite appealing.  But we saw that unsurprisingly, when delivering a project, the tool users still had ways to improve the migrated applications.  So the next step was adding an IDE which will not only use Semantic Code Understanding to re-architect a legacy application, it will harness the power of Semantic Code Understanding to interactively guide, enhance and safe guard the work of the architect performing the job.

And this is how Gizmox Transposition Studio came to be – a suite of architect tools that harness the power of advanced algorithms to digitally re-write and re-architect a legacy desktop application to a modern web or cloud based applications with full support for mobile experiences.  All of this while keeping the decades long investment in business rules and logic which are the valuable IP our clients need to keep using for application modernization.

Then graduation… how exciting!

(the claims that support sole supplier status for application modernization)


ScreenHunter 124 Sep. 13 17.25


And, the unique claims


This combination has proven to be so unique we just received a USA patent – quite an achievement given the difficulty to patent software processes.  The unique tool features result in the following advantages of the Gizmox Transposition process:

  • Semantic code understanding that allows re writing to the target platform and framework with faithful functional equivalence, and a best practices based architecture.
  • Code quality and maintainability resulting from the retention of the original code structure and business objects (unlike the completely new code which is the result of a re-write).
  • The opportunity to apply custom architectural changes such as adding layers or services, with the confidence and power of the tool based process (block operations).
  • The possibility of revising and improving security in an automatic, repeatable and reliable way – essential especially if migrating to the web.
  • Minimal code freeze requirement allowing continued development until several weeks before the start of QA – a result of the mapping rules mechanism.
  • Automatic translation of dynamically constructed SQL to parameterized LINQ – uniquely made possible through semantic understanding.
  • Last in the list but very significant - minimal requirement on the client’s resources, mostly because of the elimination of the re-specification phase and the reduction in re-training because of functional equivalence.