Method of modifying software via a network

• US 20030172367A1
• Filed: 01/07/2003
• Published: 09/11/2003
• Est. Priority Date: 01/24/2002
• Status: Abandoned Application

• Current Assignee: Computer Sciences Corporation (DXC Technology Company)
• Original Assignee: Computer Sciences Corporation (DXC Technology Company)
• Inventors: Kannenberg, Robert
• Application Number:
  US10/337,950
• Publication Number:
  US 20030172367A1
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs

Abstract

A system, method for modifying insurance transaction processing software are provided. A library of code packets may be stored in a database. One or more code packets may implement at least one business requirement of an insurance organization. If the organization changes one of the business requirements or develops a new business requirement, a user may modify an insurance transaction processing program to reflect the change via a rules engine. The rules engine may be operable to generate program code assembly instructions based on user input. The assembly instructions may be used by a code assembler to form program code for an insurance transaction processing program software module. The insurance transaction processing program may be changed by adding a formed software module.

Claims

1. A method, comprising:

receiving input defining at least one business rule;

configuring at least one code packet to implement at least one business rule; and

assembling at least one configured code packet with one or more other code packets to form program code of a software module.

2. The method of claim 1, further comprising providing a plurality of code packets in a memory.

3. The method of claim 1, wherein one or more software modules form an insurance transaction processing program that implements one or more business rules.

4. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises modifying one or more parameters.

5. The method of claim 1, further comprising modifying a data table, wherein the data table is referenced by at least one code packet during assembly of the software module.

6. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises modifying one or more allowable values associated with one or more attributes of the code packet.

7. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises accessing at least one code packet via a network.

8. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises selecting at least one code packet via a graphical user interface displayed on a display screen.

9. The method of claim 1, further comprising compiling the assembled software module

10. The method of claim 1, further comprising assembling a navigation software module to referencing the assembled software module.

11. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises associating program code in a target programming language with program code assembly instructions.

12. The method of claim 11, wherein the target programming language comprises the COBOL programming language.

13. The method of claim 1, wherein at least one code packet comprises a business rule template.

14. The method of claim 1, wherein at least one code packet comprises a business rule template, and wherein configuring at least one code packet to implement at least one business rule comprises providing values for parameters in a business rule template.

15. The method of claim 1, further comprising generating at least one program control code packet wherein a program control code packet comprises directions for assembling at least one configured code packet with one or more other code packets to form program code of the software module.

16. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises specifying at least one condition for execution of at least a portion of the business rule.

17. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises mapping at least one code packet to at least one assembly variable.

18. The method of claim 1, further comprising validating at least one configured code packet before assembling at least one configured code packet with one or more other code packets to form program code of the software module.

19. The method of claim 1, further comprising providing a list of terms;

and comparing at least one configured code packet to the list of terms to determine whether a term in at least one modified code packet appears in the list of terms.

20. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises assigning at least one allowable value to at least one attribute associated with at least one code packet.

21. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises defining at least one attribute set, wherein an attribute set comprises a reference to two or more attributes associated with a business rule.

22. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises defining one or more specifications, wherein a specification comprises an instruction of a business rule.

23. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises configuring two or more code packets to implement two or more business rules, wherein, after assembling the software module, at least one code packet implementing a first business rule references output of at least one code packet implementing a second business rule.

24. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises configuring two or more code packets to implement two or more business rules, wherein, during assembly of the software module, at least one code packet implementing a first business rule is incorporated into at least one code packet implementing a second business rule.

25. The method of claim 1, further comprising generating at least one program control code packet, wherein a program control code packet comprises software module assembly instructions and references to two or more code packets, and further comprising providing at least one program control code packet as input to a code assembler.

26. The method of claim 1, further comprising generating at least one specifications code packet, wherein a specifications code packet comprises software module assembly instructions and references to two or more code packets, and further comprising providing at least one specifications code packet as input to a code assembler.

27. The method of claim 1, wherein configuring at least one code packet to implement at least one business rule comprises providing at least one assembly variable in at least one code packet, wherein during assembly of at least one configured code packet with one or more other code packets to form program code of a software module, at least one assembly variable is replaced in at least one code packet.

28. The method of claim 1, wherein assembling at least one configured code packet with one or more other code packets to form program code of a software module comprises assigning a sort order to one or more code packets, and sorting one or more code packets according to the sort order.

29. The method of claim 1, further comprising testing at least one configured code packet before assembling at least one configured code packet with one or more other code packets to form program code of a software module.

30. The method of claim 29, wherein testing at least one configured code packet comprises generating test assembly instructions related to at least one configured code packet;

and assembling at least one configured code packet according to the test assembly instructions to form a test software module.

31. The method of claim 30, further comprising after testing at least one code packet generating software module assembly instructions based on the test assembly instructions.

32. A method, comprising:

determining at least one business requirement of a company;

defining at least one business rule, wherein at least one defined business rule is configured to implement at least one business requirement;

forming a code packet based on at least one business rule;

providing assembly directions for assembling program code for a software module using at least one code packets; and

forming program code for a software module, wherein the software module is configured to interface with an insurance transaction processing program to implement at least one defined business rule.

33. The method of claim 32, further comprising validating at least one code packet before forming program code for a software module.

34. The method of claim 32, further comprising selecting one or more business rule to be implemented in the insurance transaction processing program.

35. The method of claim 32, wherein two or more versions of at least one business rule are stored in a memory, and wherein the insurance transaction processing program formed implements a predetermined version of at least one business rule

36. The method of claim 32, wherein defining at least one business rule comprises defining one or more parameters of at least one business rule.

37. The method of claim 32, wherein defining at least one business rule comprises defining at least one data table to be referenced by a code packet implementing at least one business rule during forming of program code.

38. The method of claim 32, wherein defining at least one business rule comprises defining one or more allowable values associated with one or more attributes of the business rule.

39. The method of claim 32, wherein defining at least one business rule comprises specifying a condition which must be met if a portion of at least one business rule is to be executed.

40. The method of claim 32, further comprising testing at least one formed code packet before forming program code.

41. The method of claim 32, further comprising forming program code for at least one test software module, wherein a test software module comprises a software module formed for testing functionality of one or more formed code packets.

42. The method of claim 32, wherein providing assembly directions comprises forming test assembly directions for assembling a test software module to test functionality of at least one formed code packet, and forming assembly directions based on the test assembly directions.

43. A software module formed by the method of claim 32.

44. A method, comprising:

providing a first insurance transaction processing program comprising a first code packet configured to implement a first business rule;

displaying at least a portion of the first business rule in a graphical display;

altering the first business rule via the graphical display to form a second business rule;

forming a second insurance transaction procession program, wherein the second insurance transaction processing program comprises a second code packet, wherein the second code packet is configured to implement the second business rule.

45. The method of claim 44, wherein altering the first business rule comprises modifying a specification of the business rule, wherein a specification comprises a program instruction.

46. The method of claim 44, wherein altering the first business rule comprises modifying a condition of the business rule.

47. The method of claim 44, wherein altering the first business rule comprises modifying an attribute of the business rule.

48. The method of claim 44, wherein altering the first business rule comprises modifying an algorithm of the business rule.

49. The method of claim 44, wherein altering the first business rule comprises modifying a parameter of the business rule.

50. The method of claim 44, wherein displaying at least a portion of the first business rule comprises accessing the first business rule via a network.

51. The method of claim 44, further comprising validating the second business rule before forming the second insurance transaction processing program.

52. The method of claim 44, wherein altering the first business comprises modifying a data table referenced by the business rule.

53. The method of claim 44, wherein altering the first business rule comprises modifying one or more allowable values associated with one or more attributes of the business rule.

54. The method of claim 44, further comprising providing a list of terms;

and comparing the second business rule to the list of terms to determine whether each term in the second business rule appears in the list of terms.

55. The method of claim 44, further comprising testing the second business rule before forming the second insurance transaction processing program.

56. The method of claim 44, further comprising forming a test program, wherein the test program comprises the second code packet;

and testing the second code packet before forming the second insurance transaction processing program.

57. The method of claim 44, further comprising, before forming the second insurance transaction processing program, forming a test program, wherein the test program comprises the second code packet and test assembly instructions regarding the second code packet;

and generating assembly instructions for the second insurance transaction processing program based on the test assembly instructions regarding the second code packet.

58. An insurance transaction processing program formed by the method of claim 44.

59. A method, comprising:

providing a plurality of code packets, wherein at least one code packet is configured to at least partially implement at least one business requirement;

modifying one or more of the code packets;

generating software module assembly instructions, wherein software module assembly instructions direct assembly of one or more code packets to form one or more software modules; and

assembling one or more software modules to form an insurance transaction processing program.

60. The method of claim 59, wherein providing a plurality of code packets comprises segmenting an existing insurance transaction processing program into one or more code packets.

61. The method of claim 59, wherein at least one code packet comprises a business rule specification.

62. The method of claim 59, wherein at least one code packet comprises a technical specification.

63. The method of claim 59, wherein modifying one or more code packets comprises providing a graphical display of at least one code packet component and selecting at least one code packet component from the graphical display for use in at least one software module.

64. The method of claim 59, further comprising mapping at least one code packet to at least one technical specification before assembling one or more software modules, wherein at least one technical specification comprises software module assembly instructions.

65. The method of claim 59, wherein generating software module assembly instructions comprises mapping at least one code packet to at least one implementation point of a driver frame.

66. The method of claim 59, further comprising compiling one or more software modules to form executable code.

67. The method of claim 59, further comprising testing at least one modified code packet before assembling one or more software modules.

68. The method of claim 59, wherein generating software module assembly instructions comprises forming assembly instructions for at least one test software module;

and generating software module assembly instructions based on the assembly instructions for at least one test software module.

69. An insurance transaction processing program formed by the method of claim 59.

70. A system comprising:

at least one computer system;

at least one memory coupled to at least one computer system;

a plurality of code packets in at least one memory;

at least one rules engine in at least one memory, wherein at least one rules engine is executable to generate assembly instructions for at least one software module; and

at least one code assembler, wherein at least one code assembler is configured to assemble two or more code packets according to assembly instructions to form at least one software module.

71. The system of claim 70, wherein at least one code packet comprises at least one business rule specification.

72. The system of claim 70, wherein at least one code packet comprises a code template.

73. The system of claim 70, wherein at least one code packet comprises at least one technical specification.

74. The system of claim 70, further comprising at least one compiler program in at least one memory, wherein at least one compiler program is executable to compile at least one software module to form an executable program.

75. The system of claim 70, further comprising at least one graphical interface, wherein at least one graphical interface is configured to display at least a portion of at least one code packet.

76. The system of claim 70, further comprising at least one graphical interface, wherein at least one graphical interface is configured to receive input modifying at least one code packet.

77. The system of claim 70, wherein software module assembly instructions comprises references to placements with the software module for two or more code packets.

78. The system of claim 70, wherein software module assembly instructions comprises references to placements with the software module for two or more code packets and wherein assembling two or more code packet according to the assembly instructions comprises sorting portions of two or more packets into a desired placement order.

79. The system of claim 70, wherein the code generator and code assembler are further executable to form at least one navigation control software module, wherein a navigation control software module directs other software modules to the formed software module.

80. The system of claim 70, further comprising at least one test application, wherein at least one test application is operable generate assembly instructions for at least one software module based on test assembly instructions used to assemble one or more test software modules.

81. A system comprising:

at least one computer system;

at least one memory coupled to at least one computer system;

a plurality of code packets, wherein at least one code packets is configured to implement at least one business requirement of an insurance organization;

a rules engine in at least one memory, wherein the rules engine comprises program instructions which are executable to implement a method comprising;

configuring at least one code packet; and

forming software module assembly instructions for an insurance transaction processing program that includes functionality of at least one configured code packet.

82. The system of claim 81, further comprising at least one data table, wherein the rules engine is configured access to information in at least one data table to form the software module assembly instructions.

83. The system of claim 81, wherein the rules engine is further executable to receive input from and to configure at least one code packet based on the received input.

84. The system of claim 81, wherein at least one code packet comprises a business rule specification.

85. The system of claim 81, wherein at least one code packet comprises a code template.

86. The system of claim 81, wherein at least one code packet comprises a technical specification.

87. The system of claim 81, further comprising at least one compiler program in at least one memory, wherein at least one compiler program is executable to compile a software module to form an executable program.

88. The system of claim 81, wherein the rules engine is further executable to provide a graphical interface, wherein the graphical interface is configured to display at least a portion of at least one business rule, wherein at least one business rule corresponds to at least one code packet.

89. The system of claim 81, wherein the rules engine is further executable to validate the configuration of a code packet.

90. The system of claim 81, wherein the rules engine is further executable select one or more code packet for inclusion in a software module from the plurality of code packets.

91. The system of claim 81, further comprising a code assembly in at least one memory, wherein the code assembler is executable to assemble software module program code based on the software module assembly instructions.

92. The system of claim 81, wherein the rules engine is further executable to form test software module assembly instructions.

93. A method comprising:

providing a plurality of code packet in a memory coupled to a computer system, wherein at least one code packet is configured to implement at least one business requirement of an insurance organization;

providing at least one rules engine in a memory couple to the computer system, wherein at least one rules engine is executable to modify one or more code packets;

providing at least one code assembler in a memory coupled to the computer system, wherein the code assembler is executable to combine two or more code packets to form an insurance transaction processing program;

allowing at least one customer to interact with at least one rules engine to modify at least one code packet;

forming an insurance transaction processing program including at least one modified code packet; and

charging at least one customer a fee for interacting with at least one rules engine.

94. The method of claim 93, wherein at least one customer interacts with at least one rules engine via a network.

95. The method of claim 93, further comprising allowing at least one customer to test at least one modified code packet before forming an insurance transaction processing program.

96. The method of claim 93, further comprising testing at least one modified code packet before forming an insurance transaction processing program.

97. The method of claim 93, wherein at least one customer interacts with at least one rules engine via the Internet.

98. The method of claim 93, wherein interacting with at least one rules engine comprises selecting at least one code packet to include in the formed insurance transaction processing program.

99. The method of claim 93, wherein interacting with at least one rules engine comprises selecting at least one code packet to omit from the formed insurance transaction processing program.

100. The method of claim 93, wherein interacting with at least one rules engine to modify at least one code packet comprises modifying one or more parameters of at least one code packet.

101. The method of claim 93, wherein interacting with at least one rules engine to modify at least one code packet comprises modifying a data table referenced by at least one code packet.

102. The method of claim 93, wherein interacting with at least one rules engine to modify at least one code packet comprises modifying one or more allowable values associated with one or more attributes of at least one code packet.

103. The method of claim 93, further comprising compiling the formed insurance transaction processing program.

104. The method of claim 93, further comprising storing the formed insurance transaction processing program in a memory coupled to the computer system.

105. The method of claim 93, further comprising allowing at least one customer to execute the formed insurance transaction processing program on a computer system.

106. The method of claim 93, wherein interacting with at least one rules engine to modify at least one code packet comprises associating at least one code packet with at least one technical code packet, wherein a technical code packet comprises code assembly instructions.

107. The method of claim 93, wherein modifying at least one code packet comprises specifying a condition for at least one business requirement.

108. The method of claim 93, wherein modifying at least one code packet comprises mapping at least one code packet to at least one assembly variable of another code packet.

109. The method of claim 93, further comprising validating the modifications after at least one customer modifies at least one code packet.

110. The method of claim 93, further comprising providing a list of terms;

and comparing at least one modified code packet to the list of terms to determine whether terms in at least one modified code packet appear in the list of terms.

111. The method of claim 93, wherein allowing at least one customer to interact with at least one rules engine comprises providing indirect interaction with at least one rules engine via a telephone system.

112. A method comprising:

providing a rules engine on a computer system, wherein the rules engine is operable to generate program code assembly instructions for an insurance transaction process program;

providing a code assembler on the computer system, wherein the code assembler is operable to assemble two or more code packets based on code assembly instructions to form program code;

providing a plurality of code packets in a memory coupled to the computer system;

allowing a user to interact with at least one rules engine to configure at least one insurance transaction processing program;

forming at least one insurance transaction processing program based on the users configuration; and

charging the user a fee.

113. The method of claim 112, wherein the fee is charged according to a fee schedule.

114. The method of claim 112, wherein the user is allowed to interact with the rules engine via a network.

115. The method of claim 112, wherein the user is allowed to interact with the rules engine via the Internet.

116. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises modifying one or more code packets.

117. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises adding one or more code packets.

118. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises modifying at least one attribute of at least one code packet.

119. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises modifying at least one parameter of at least one code packet.

120. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises associating at least one code packet with at least one other code packet.

121. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises associating at least one code packet with at least one assembly variable.

122. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises adding at least one business rule.

123. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises modifying at least one business rule.

124. The method of claim 112, wherein configuring at least one insurance transaction processing program comprises selecting one or more code packets to use in forming at least one insurance transaction processing program.

125. The method of claim 112, wherein forming at least one insurance transaction processing program comprises combining at least portions of two or more code packets to form program code for at least one insurance transaction processing program.

126. A carrier medium comprising program instruction, wherein the program instructions are computer executable to:

receive input defining at least one business rule;

configure at least one code packet to implement at least one business rule; and

assemble at least one configured code packet with one or more other code packets to form program code of a software module.

127. A carrier medium comprising program instruction, wherein the program instructions are computer executable to:

determine at least one business requirement of a company;

define at least one business rule, wherein at least one defined business rule is configured to implement at least one business requirement;

form a code packet based on at least one business rule;

provide assembly directions for assembling program code for a software module using at least one code packets; and

form program code for a software module, wherein the software module is configured to interface with an insurance transaction processing program to implement at least one defined business rule.

128. A carrier medium comprising program instruction, wherein the program instructions are computer executable to:

provide a first insurance transaction processing program comprising a first code packet configured to implement a first business rule;

display at least a portion of a first business rule in a graphical display;

alter the first business rule via the graphical display to form a second business rule;

form a second insurance transaction procession program, wherein the second insurance transaction processing program comprises a second code packet, wherein the second code packet is configured to implement the second business rule.

129. A carrier medium comprising program instruction, wherein the program instructions are computer executable to:

access a plurality of code packets, wherein at least one code packet is configured to at least partially implement at least one business requirement;

modify one or more of the code packets;

generate software module assembly instructions, wherein software module assembly instructions direct assembly of one or more code packets to form one or more software modules; and

assemble one or more software modules to form an insurance transaction processing program.

130. A carrier medium comprising:

program instruction for at least one rules engine, wherein at least one rules engine is computer executable to generate assembly instructions for at least one software module; and

program instruction for at least one code assembler, wherein at least code assembler is computer executable to assemble two or more code packets according to assembly instructions to form at least one software module.

131. A carrier medium comprising program instruction, wherein the program instructions are computer executable to:

access a plurality of code packet in a memory coupled to a computer system, wherein at least one code packet is configured to implement at least one business requirement of an insurance organization;

access at least one rules engine in a memory couple to the computer system, wherein at least one rules engine is executable to modify one or more code packets;

access at least one code assembler in a memory coupled to the computer system, wherein the code assembler is executable to combine two or more code packets to form an insurance transaction processing program;

interact with a customer to execute at least one rules engine to modify at least one code packet;

form an insurance transaction processing program including at least one modified code packet; and

charge at least one customer a fee for interacting with at least one rules engine.

132. A carrier medium comprising program instruction, wherein the program instructions are computer executable to:

interact with a user to configure at least one insurance transaction processing program;

access a plurality of code packets in a memory;

generate program code assembly instructions for an insurance transaction process program;

assemble two or more code packets based on code assembly instructions to form program code; and

form at least one insurance transaction processing program based on the users configuration.