Method and System for Analyzing Interaction Among Software Artifacts

1. A system for analyzing interactions among software artifacts within enterprise business applications, wherein the enterprise business application comprises a server enterprise application executing on a server processing system and a client enterprise application executing on a client processing system, and wherein the server processing system and the client processing system comprises a processor and a memory, the system comprising: an artifact analyzer module, residing in the server processing system or in the client processing system or both, configured to extract interactions of software artifacts within enterprise business applications; the artifact analyzer module comprising: an artifact code parsing module for parsing software code for software objects in the enterprise business application; and an artifact token processing module for extracting artifact tokens associated with trigger points in which processing control passes between a first software object and a second software object using the parsed software code in the enterprise business application, and wherein the artifact token processing module comprises: an interaction token processing module for generating and analyzing tokens associated with software objects on different processing systems; and a multi-layer token processing module for generating and analyzing tokens associated with software objects within a multi-layer application architecture; and an interaction token repository for storing the artifact tokens, wherein the artifact tokens describe identity of the first software object, ownership of the first software object containing the trigger point, a location within first software object of the trigger point, and identity of the second software object.

2. The system according to claim 1 , wherein the artifact token further describes trigger point parameter data to define any data, state conditions, and other processing information needed to characterize the trigger point.

3. The system according to claim 1 , wherein the artifact code parsing module receives source code from a software development system for processing and analysis of artifact token data.

4. The system according to claim 3 , wherein the software development system is an external software development system.

5. The system according to claim 3 , wherein the artifact analyzer module is part of the software development system.

6. The system according to claim 1 , wherein the server enterprise application comprises a multi-layer application having a server presentation layer, a server services layer, a server methods layer and a server database layer.

7. The system according to claim 6 , wherein the layers of the server enterprise application interact with corresponding layers of the client enterprise application.

8. The system according to claim 1 , wherein the client enterprise application comprises a multi-layer application having a client presentation layer, a client services layer, a client methods layer and a client database layer.

9. A method for analyzing interactions among software artifacts within enterprise business applications, wherein the enterprise business application comprises: a server enterprise application executing on a server processing system and a client enterprise application executing on a client processing system, the method comprising: assigning an ownership function for every software object within the enterprise application; parsing software code for software objects in the enterprise application; extracting artifact tokens associated with trigger points in which processing control passes between a first software object and a second software object using the parsed code in the enterprise business application, and wherein the extracting of artifact tokens comprises an interaction token processing module and a multi-layer token processing module for generating and analyzing tokens associated with software objects on different processing systems and within a multi-layer application architecture, respectively; storing the artifact tokens within an interaction artifact repository; and analyzing interaction between the first and second software object using the artifact tokens and the assigned ownership function; wherein the artifact tokens describe identity of the first software object, ownership of the first software object containing the trigger point, a location within first software object of the trigger point, and identity of the second software object.

10. The method according to claim 9 , wherein the method further comprises storing artifact tokens within an interaction artifact repository.

11. The method according to claim 9 , wherein the artifact token further describes trigger point parameter data to define any data, state conditions, and other processing information needed to characterize the trigger point.

12. The method according to claim 9 , wherein the method further comprises receiving the software from a software development system for processing and analysis of artifact token data.

13. The method according to claim 12 , wherein the software development system is an external software development system.

14. The method according to claim 9 , wherein the server enterprise application comprises a multi-layer application having a server presentation layer, a server services layer, a server methods layer and a server database layer.

15. The method according to claim 9 , wherein the client enterprise application comprises a multi-layer application having a client presentation layer, a client services layer, a client methods layer and a client database layer.

16. The method according to claim 15 , wherein the layers of the server enterprise application interact with corresponding layers of the client enterprise application.

17. An article comprising: a storage medium having instructions that when executed by a computing platform, result in execution of a method for analyzing interactions among software artifacts within enterprise business applications, wherein the enterprise business application comprises: a server enterprise application executing on a server processing system and a client enterprise application executing on a client processing system, the method comprising: receiving the software from a software development system for processing and analysis of artifact token data; assigning for every software object within the enterprise application; parsing software code for software objects in the enterprise application; extracting artifact tokens associated with trigger points in which processing control passes between a first software object and a second software object using the parsed code in the enterprise business application, wherein the extracting of artifact tokens comprises an interaction token processing module and a multi-layer token processing module for generating and analyzing tokens associated with software objects on different processing systems and within a multi-layer application architecture, respectively; storing the artifact tokens within an interaction artifact repository; analyzing interaction between the first and second software object using the artifact tokens and the assigned ownership function; and wherein the artifact tokens describe identity of the first software object, ownership of the first software object containing the trigger point, a location within first software object of the trigger point, and identity of the second software object.

18. The article according to claim 17 , wherein the artifact token further describes trigger point parameter data to define any data, state conditions, and other processing information needed to characterize the trigger point.

19. The article according to claim 17 , wherein the software development system is an external software development system.

20. The article according to claim 17 , wherein the server enterprise application comprises a multi-layer application having a server presentation layer, a server services layer, a server methods layer and a server database layer.

21. The article according to claim 20 , wherein the layers of the server enterprise application interact with corresponding layers of the client enterprise application.

22. The article according to claim 17 , wherein the client enterprise application comprises a multi-layer application having a client presentation layer, a client services layer, a client methods layer and a client database layer.