System to transition an enterprise to a distributed infrastructure

• US 5,960,200 A
• Filed: 09/16/1996
• Issued: 09/28/1999
• Est. Priority Date: 05/03/1996
• Status: Expired due to Fees

• Current Assignee: I-Cube
• Original Assignee: I-Cube
• Inventors: Aslanian, Edouard, Eager, Timothy, Anand, Madhav
• Primary Examiner(s): Hafiz, Tariq R.
• Assistant Examiner(s): DAM, TUAN QUANG
• Application Number:
  US08/714,205
• Time in Patent Office: 1,107 Days
• Field of Search: 395/705, 395/701, 395/702, 395/707, 395/708, 395/500, 395/200.31, 395/200.33, 395/682, 395/683, 705/7-11, 707/10, 707/100, 707/102-104, 364/578, 364/468.02, 364/468.03, 364/468.05, 364/468.09
• US Class Current: 717/147
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/427 Parsing

Abstract

An automated system transitions an entire enterprise to a distributed infrastructure. The system includes a process for organizing and managing the transition, a multi-tiered client/server architecture that adheres to open systems standards, a system to automate the transition of existing applications to this architecture, and a system to enable the creation or modification of applications based on this architecture.

Claims

1. A system to transition legacy applications operable on a legacy computing system to a distributed infrastructure, the system comprising:

a multi-tiered computer architecture including a process control tier for modeling an internal work flow of an enterprise and a functionality tier for performing work in accordance with the work flow of the enterprise; and

a legacy application inoperable on the multi-tiered computer architecture and

an automated converter to transition the legacy application to a target application operable on the multi-tiered computer architecture.

2. The system of claim 1 wherein the multi-tiered computer architecture is a client-server architecture having at least four tiers.

3. The system of claim 1 where the multi-tiered architecture further includes a presentation tier for interfacing with a user, a data retrieval tier, and a data storage tier.

4. The system of claim 1 wherein the converter includes an intermediate language, the language of the legacy application being translated to the intermediate language and from the intermediate language to the language of the target application.

5. The system of claim 1 wherein the target application is an internet accessible application.

6. The system of claim 1 wherein the target application is an object-oriented application.

7. The system of claim 1 further comprising an implementation plan which provides a prioritized list of legacy applications to be transitioned by the automated converter.

8. The system of claim 7 wherein the implementation plan further provides instructions for controlling the operation of the automated converter.

9. The system of claim 1 further comprising an implementation strategy which identifies inputs to a target system and provides a list of action items for obtaining the identified outputs from the legacy computing system.

10. A method for transitioning legacy applications operable on a legacy computing system to a distributed infrastructure, comprising the steps of:

providing a multi-tiered architecture including a process control tier for modeling an internal work flow of an enterprise and a functionality tier for performing work in accordance with the work flow of the enterprise; and

providing a legacy application inoperable on the multi-tiered computer architecture; and

in a computer, automatically converting the legacy application to a target application operable on the multi-tiered computer architecture.

11. The method of claim 10 wherein the step of providing a multi-tiered architecture comprises providing a client-server architecture having at least four tiers.

12. The method of claim 10 where the multi-tiered computer architecture further includes a presentation tier for interfacing with a user, a data retrieval tier, and a data storage tier.

13. The method of claim 10 wherein the step of converting comprises translating the language of the legacy application to an intermediate language and translating the intermediate language to the language of the target application.

14. The method of claim 10 wherein the target application is an internet accessible application.

15. The method of claim 10 wherein the target application is an object-oriented application.

16. The method of claim 10 further comprising the step of providing a prioritized list of legacy applications to be transitioned by the automated converter.

17. The method of claim 16 further comprising the step of controlling the operation of the automated converter based on the prioritized list.

18. The method of claim 10 further comprising the steps of:

identifying inputs to a target system including the target application; and

obtaining the identified outputs from the legacy applications from a list of action items.

19. In a computer, a converter for translating a legacy program component operating in a legacy language on a legacy computing system to a target program component operating in a target language on a distributed infrastructure includes a process control tier and a functionality tier, the converter comprising:

an intermediate language;

a first converter for translating the legacy program component from the legacy language to an intermediate component in the intermediate language wherein the legacy language is operable on a legacy processor; and

a second converter for translating the intermediate component from the intermediate language to the target program component in the target language wherein the target language is operable on a target processor different from the legacy processor.

20. The converter of claim 19 wherein the intermediate language is independent of the legacy language and the target language.

21. The converter of claim 19 wherein the intermediate language is inoperable on either the legacy processor or the target processor.

22. The converter of claim 19 wherein the first converter parses the legacy program component into a parse tree, the intermediate component representing the parse tree in a postfix notation.

23. In a computer, a method for translating a legacy program component operating in a legacy language on a legacy computing system to a target program component operating in a target language on a distributed infrastructure includes a process control tier and a functionality tier, comprising the steps of:

defining an intermediate language;

in a first converter, translating the legacy program component from the legacy language to an intermediate component in the intermediate language wherein the legacy language is operable on a legacy processor; and

in a second converter, translating the intermediate component from the intermediate language to the target program in the target language wherein the target language is operable on a target processor different from the legacy processor.

24. The method of claim 23 wherein the intermediate language independent of the legacy language and the target language.

25. The method of claim 23 wherein the intermediate language is inoperable on either the legacy processor or the target processor.

26. The method of claim 23 wherein the step of translating the legacy program component comprises:

parsing the legacy program component into a parse tree; and

representing the parse tree in a postfix notation.

27. A system to transition legacy applications operable on a legacy computing system to a distributed infrastructure, the system comprising:

a multi-tiered computer architecture including a process control tier for modeling an internal work flow of an enterprise and a functionality tier for performing work in accordance with the work flow of the enterprise; and

an automated converter having a first converter and a second converter to transition a legacy application to a target application operable on the multi-tiered computer architecture, the first converter translating the legacy application from a legacy language to an intermediate language and the second converter translating the translated legacy application from the intermediate language to the target application in a target language.

28. The system of claim 27 wherein the multi-tiered computer architecture is a client-server architecture having at least four tiers.

29. The system of claim 27 where the multi-tiered computer architecture further includes a presentation tier for interfacing with a user, a data retrieval tier, and a data storage tier.

30. The system of claim 27 wherein the intermediate language is independent of the legacy language and the target language.

31. The system of claim 27 wherein the target application is an internet accessible application.

32. The system of claim 27 wherein the target application is an object-oriented application.

33. The system of claim 27 further comprising an implementation plan which provides a prioritized list of legacy applications to be transitioned by the automated converter.

34. The system of claim 33 wherein the implementation plan further provides instructions for controlling the operation of the automated converter.

35. The system of claim 27 further comprising an implementation strategy which identifies inputs to a target system including the target applications and provides a list of action items for obtaining the identified outputs from the legacy applications.

36. A method for transitioning legacy applications operable on a legacy computing system to a distributed infrastructure, comprising the steps of:

providing a multi-tiered computer architecture including a process control tier for modeling an internal work flow of an enterprise and a functionality tier for performing work in accordance with the work flow of the enterprise; and

in a computer, automatically converting a legacy application to a target application operable on the multi-tiered computer architecture, the legacy application translated from a legacy language to an intermediate language and the translated legacy application being translated from the intermediate language to the target application in a target language.

37. The method of claim 36 wherein the step of providing comprises providing a client-server architecture having at least four tiers.

38. The method of claim 36 where the multi-tiered computer architecture further includes a presentation tier for interfacing with a user, a data retrieval tier, and a data storage tier.

39. The method of claim 36 wherein the step of converting comprises defining the intermediate language to be independent of the legacy language and the target language.

40. The method of claim 36 wherein the target application is an internet accessible application.

41. The method of claim 36 wherein the target application is an object-oriented application.

42. The method of claim 36 further comprising the step of prioritizing a list of legacy applications to be transitioned by the automated converter.

43. The method of claim 42 further comprising the step of controlling the operation of the automated converter based on the prioritized list.

44. The method of claim 36 further comprising the steps of:

identifying inputs to a target system including the target application; and

obtaining the identified outputs from the source applications using a list of action items.

45. A system for transitioning a legacy application operable on a legacy computing system to a distributed infrastructure includes a process control tier and a functionality tier, the system comprising:

an intermediate language;

a first converter for translating the legacy application component from a legacy language to an intermediate component in the intermediate language wherein the legacy language is operable on a legacy processor; and

a second converter for translating the intermediate component from the intermediate language to a target application component in a target language operable on the distributed infrastructure wherein the target language is operable on a target processor different from the legacy processor.

46. The system of claim 45 wherein the intermediate language is independent of the legacy language and the target language.

47. The system of claim 45 wherein the intermediate language is inoperable on either the legacy processor or the target processor.

48. The system of claim 45 wherein the first converter parses the legacy program component into a parse tree, the intermediate component representing the parse tree in a postfix notation.

49. The system of claim 45 further comprising a multi-tiered computer architecture.

50. A method for transitioning a legacy application operable on a legacy computing system to a distributed infrastructure includes a process control tier and a functionality tier, comprising the steps of:

defining an intermediate language;

in a first converter, translating the legacy application component from a legacy language to an intermediate component in the intermediate language wherein the legacy language is operable on a legacy processor; and

in a second converter, translating the intermediate component from the intermediate language to a target application component in a target language operable on the distributed infrastructure wherein the target language is operable on a target processor different from the legacy processor.

51. The method of claim 50 wherein the intermediate language independent of the legacy language and the target language.

52. The method of claim 50 wherein the intermediate language is inoperable on either the legacy processor or the target processor.

53. The method of claim 50 wherein the step of translating the legacy program component comprises:

parsing the legacy program component into a parse tree; and

representing the parse tree in a postfix notation.

54. The method of claim 50 further comprising the step of operating the target program on a multi-tiered computer architecture.