System and method for modeling cloud rules for migration to the cloud

• US 9,772,830 B2
• Filed: 01/22/2013
• Issued: 09/26/2017
• Est. Priority Date: 01/19/2012
• Status: Active Grant

• Current Assignee: Atos France
• Original Assignee: Syntec Incorporated (Atos SE)
• Inventors: Balasubramanian, Ashok
• Primary Examiner(s): VU, TUAN A
• Application Number:
  US13/746,554
• Publication Number:
  US 20130212553A1
• Time in Patent Office: 1,708 Days
• Field of Search: 717 2, 717102, 717170, 717176, 707602, 726 1, 709218, 709224, 718 1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/51 Source to source
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A computerized system and method of migrating an application from a source platform to a target platform, such as a cloud platform. A set of rules are developed that represent aspect of the target platform and the source code of the application to be migrated is analyzed to determine whether it violates any of these rules. In some embodiments, the source code could be automatically modified to correct for violations of the rules.

Claims

1. A computerized method for modeling rules for migration to the cloud, the method comprising the steps of:

providing a computer including a processor and executable instructions stored on a memory coupled to the processor;

reviewing, using executed instructions on the computer, without further intervention of a user, architectures of a source platform and a target platform, wherein the architectures are the organizational structures of the source platform and the target platform, and the reviewing includes identifying the interaction between the architectures to determine constraints for migration of the source platform to the target platform;

defining, using executed instructions on the computer, without intervention of a user, a plurality of rules, wherein the plurality of rules implement the constraints of the target platform and the defining includes developing the plurality of rules in at least one programming language of the source platform and the target platform;

scanning, using executed instructions on the computer, without further intervention of a user, source code of an application intended to be migrated to the target platform to determine whether the application violates any of the plurality of rules;

correcting, using executed instructions on the computer, without further intervention of the user, via a code correction framework for at least one type of source code, one or more violations of the plurality of rules of the source code according to an original token, a location of the original token, and an alternate token for replacing the original token wherein the tokens are elements of the source code; and

generating, using executed instructions on the computer, without further intervention of a user, a report including any violations of the plurality of rules that have been corrected and any violations of the plurality of rules not corrected, the latter left for manual correction by the user;

wherein the correcting step includes automatically modifying, via a PDF report plugin, the source code of the application to correct the one or more violations of the plurality of rules.

2. The method of claim 1, wherein the method is compatible with a SONAR™

quality analysis tool.

3. The method of claim 2, further comprising the step of deploying the application to the target platform.

4. The method of claim 3, wherein the target platform is a cloud platform.

5. The method of claim 1, further comprising the step of estimating, using an estimation plugin on a computer, a monetary cost for modifying the source code of the application to correct one or more violations of the cloud commandments based a number of violations in the report.

6. The method of claim 1, wherein the scanning step analyzes the application for any violations of the plurality of rules at run-time.

7. The method of claim 6, wherein the scanning step records program flow of the application at run-time to capture flow until a violation occurs.

8. The method of claim 1, wherein the scanning step analyzes source code of the application to detect duplicate code.

9. The method of claim 1, wherein the scanning step analyzes source code of the application to calculate one or more of a number of statements in the source code, a number of functions in the source code, and a number of lines of code in the source code.

10. The method of claim 1, wherein the scanning step analyzes source code of the application to determine at least the following characteristics for any violations of the plurality of rules:

(1) file name, (2) path, and (3) line number.

11. The method of claim 1, further comprising the step of scanning database scripts to determine migration potential.

12. The method of claim 11, wherein migration potential is determined by scanning of a table structure of a database for compatibility with the target platform.

13. The method of claim 11, wherein migration potential is determined by scanning of stored procedures for compatibility with the target platform.

14. The method of claim 11, wherein migration potential is determined by an analysis of keys.

15. The method of claim 1, further comprising the step of scanning a server environment to determine migration dependencies.

16. A computerized method for modeling rules for migration to the cloud, the method comprising the steps of:

providing a computer including a processor and executable instructions stored on a memory coupled to the processor;

reviewing , using executed instructions on the computer, without further intervention of a user, architectures of a source platform and a target platform , wherein the architectures are the organizational structures of the source platform and the target platform, and the reviewing includes identifying the interaction between the architectures to determine constraints for migration of the source platform to the target platform;

defining, using executed instructions on the computer, without intervention of a user, a plurality of rules, wherein the plurality of rules implement the constraints of the target platform and the defining includes developing the plurality of rules in at least one programming language of the source platform and the target platform;

scanning, using executed instructions on the computer, without further intervention of a user, source code of an application intended to be migrated to the target platform to determine whether the application violates any of the plurality of rules;

analyzing, using executed instructions on the computer, without further intervention of a user, (a) one or more XML files including a configuration of the source code for violations of the plurality of rules, (b) one or more Java properties files associated with the source code for violations of the plurality of rules, or both (a) and (b);

correcting, using executed instructions on the computer, without further intervention of a user, via a code correction framework for at least one type of source code, the violations according to an original token, a location of the original token, and an alternate token for replacing the original token; and

generating, using executed instructions on the computer, without further intervention of a user, a report including any violations of the plurality of rules that have been corrected and any violations of the plurality of rules not corrected, the latter left for manual correction by the user;

wherein the correcting step includes automatically modifying, via a PDF report plugin, the source code of the application to correct the one or more violations of the plurality of rules.

17. The method of claim 16, wherein the analyzing step comprises analyzing (a) one or more XML files including a configuration of the source code for violations of the plurality of rules.

18. The method of claim 17, wherein the analyzing step comprises a static analysis of the one or more XML files.

19. The method of claim 16, wherein the analyzing step comprises analyzing (b) one or more Java properties files associated with the source code for violations of the plurality of rules.

20. The method of claim 19, wherein analyzing one or more Java properties files includes validating Java property keys according to user specifications;

and, wherein the report includes user-defined messages for property key violations.