Integration environment generator

• US 8,689,177 B2
• Filed: 08/16/2010
• Issued: 04/01/2014
• Est. Priority Date: 08/31/2009
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Mahajan, Rahul, Pandey, Dinesh, Kirkby, Stephen
• Primary Examiner(s): AN, IG TAI
• Application Number:
  US12/857,217
• Publication Number:
  US 20110055807A1
• Time in Patent Office: 1,324 Days
• Field of Search: 717/107
• US Class Current: 717/107
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 8/61 Installation

Abstract

An integration environment generator receives an input file and converts the input file into a markup language file. The input file identifies modules for an application to be deployed, dependencies among the modules, test cases for testing the modules, and scheduling information. The integration environment generator receives rules and validates the markup language file against the rules. The rules specify a unified format for including the dependencies of the modules in the input file. The integration environment generator identifies the modules, the dependencies among the modules, and the scheduling information and the test cases from the validated markup language file. The integration environment generator selects a build script template for the identified dependencies, a scheduling script template for the identified scheduling information and a test case script template for the identified test cases and generates a build script, a scheduling script and a test case script from the templates.

Claims

1. An integration environment generator comprising:

a processor and a memory storing machine readable instructions executable by the processor to implement;

an input conversion module to receive an input file and convert the input file into a markup language file, the input file identifying modules for an application to be deployed, dependencies among the modules, test cases for testing the modules, and scheduling information;

a validation module to receive rules and validate the markup language file against the rules, the rules specifying a unified format for including the dependencies of the modules in the input file;

a traversal module to identify the modules, the dependencies among the modules, the scheduling information and the test cases from the validated markup language file;

a template selection module to select a build script template for the identified dependencies among the modules, a scheduling script template for the identified scheduling information and a test case script template for the identified test cases by identifying each template from a plurality of templates; and

a file generation module to generate a build script from the build script template, a scheduling script from the scheduling script template and a test case script from the test case script template, the template selection module to populate;

the build script template with the identified dependencies among the modules;

the scheduling script template with the identified scheduling information; and

the test case script template with the identified test cases.

2. The integration environment generator of claim 1, further comprising a recordation module to generate a tree structure reflecting the dependencies among the modules.

3. The integration environment generator of claim 1, wherein the markup language file is an XML file.

4. The integration environment generator of claim 1, wherein the build script is to create a deployable package.

5. The integration environment generator of claim 1, wherein the input file includes a Unified Modeling Language (UML) design.

6. The integration environment generator of claim 1, wherein the rules include a rule specifying that dependencies among the various modules are not to be cyclic.

7. The integration environment generator of claim 1, wherein the rules include a rule specifying that dependencies among the various modules are to be specified by <

<

use>

>

stereotype of Unified Modeling Language (UML).

8. A method for generating a build script, the method comprising:

converting, by a processor, an input file into a markup language file, the input file identifying modules for an application, dependencies among the modules, test cases for testing the modules, and scheduling information;

validating the markup language file against rules, the rules specifying a unified format for including the dependencies of the modules in the input file;

identifying the modules, the dependencies among the modules, the scheduling information and the test cases from the validated markup language file;

selecting a build script template for the identified dependencies among the modules, a scheduling script template for the identified scheduling information and a test case script template for the identified test cases by identifying each template from a plurality of templates; and

generating, by the processor, a build script from the build script template, a scheduling script from the scheduling script template and a test case script from the test case script template,

wherein the build script template is populated with the identified dependencies among the modules,

wherein the scheduling script template is populated with the identified scheduling information, and

wherein the test case script template is populated with the identified test cases.

9. The method of claim 8, further comprising:

generating a tree structure reflecting the dependencies among the modules.

10. The method of claim 8, wherein the markup language file is an XML file.

11. The method of claim 8, wherein the build script is used to create a deployable package.

12. The method of claim 8, wherein the input file includes a Unified Modeling Language (UML) design.

13. The method of claim 8, wherein the rules include a rule specifying the dependencies among the various modules are not to be cyclic.

14. The method of claim 8, wherein the rules include a rule specifying the dependencies among the various modules are to be specified by <

<

use>

>

stereotype of Unified Modeling Language (UML).

15. A non-transitory computer readable medium having stored thereon computer executable instructions for generating a build script, the computer executable instructions, when executed, cause a computer system to perform a method comprising:

converting an input file into a markup language file, the input file identifying modules for an application, dependencies among the modules, test cases for testing the modules, and scheduling information;

validating the markup language file against rules, the rules specifying a unified format for including the dependencies of the modules in the input file;

identifying the modules, the dependencies among the modules, the scheduling information and the test cases from the validated markup language file;

selecting a build script template for the identified dependencies among the modules, a scheduling script template for the identified scheduling information and a test case script template for the identified test cases by identifying each template from a plurality of templates; and

generating a build script from the build script template, a scheduling script from the scheduling script template and a test case script from the test case script template,

wherein the build script template is populated with the identified dependencies among the modules,

wherein the scheduling script template is populated with the identified scheduling information, and

wherein the test case script template is populated with the identified test cases.

16. The computer readable medium of claim 15, wherein the method further comprises:

generating a tree structure reflecting the dependencies among the modules.

17. The computer readable medium of claim 15, wherein the markup language file is an XML file.

18. The computer readable medium of claim 15, wherein the build script is used to create a deployable package.

19. The computer readable medium of claim 15, wherein the input file includes a Unified Modeling Language (UML) design.

20. The computer readable medium of claim 15, wherein the rules include a rule specifying the dependencies among the various modules are not to be cyclic.