Posts Tagged: "software engineering"

When copying has occurred, much of the code may have changed by the time it’s examined due to the normal development process or to disguise the copying. For example identifiers may have been renamed, code reordered, instructions replaced with similar instructions, and so forth. However, perhaps one comment remains the same and it’s an unusual comment. Or a small sequence of critical instructions is identical. Correlation is designed to produce a relatively high value based on that comment or that sequence, to direct the detective toward that similarity. If correlation were simply a percentage of copied lines, the number could be small and thus missed entirely among the noise of normal similarities that occur in all programs.

When embarking on a software development project it is critical to understand that in order to maximize the chance of obtaining a patent you need to approach the task with an engineering mind set, as well as a healthy familiarity with Murphy’s Law. Anything that can go wrong will go wrong, and once you release the process to end users a human element will complicate what should otherwise be a predictable, linear, machine driven response. Embrace the uncertainty and challenges because the fact that software rarely, if ever, works like it should is what makes a working process patentable.

My position is that software must be patentable, or 500 years of patent laws make no sense. The reason that software must be patentable is that software can be an inseparable part of both manufacturing processes and electronic devices. A patent for such items must crucially include the software components of the invention, or the patent would be incomplete.