Claims
- 1. A system for software platform-level dependency checking, said software platform including a plurality of interrelated software products, said system comprising:
a set of rules that define allowable and/or forbidden dependencies between said interrelated software products; a rules-based compliance checking routine that periodically runs test to examine the dependencies between two or more of said interrelated software products according to said rules; and, a report device that reports the results of said tests.
- 2. The system of claim 1 wherein the set of rules define the dependencies allowed, forbidden, or required for those software products.
- 3. The system of claim 1 wherein said software products comprise any of server products, integration products, portal products, or integrated development environment products.
- 4. A method for software platform-level dependency checking, said software platform including a plurality of interrelated software products, said method comprising the steps of:
defining a set of rules that define allowable and/or forbidden dependencies between said interrelated software products; periodically running tests to examine the dependencies between two or more of said interrelated software products according to said rules; and, reporting the results of said tests.
- 5. The method of claim 4 wherein the set of rules define the dependencies allowed, forbidden, or required for those software products.
- 6. The method of claim 4 wherein said software products comprise any of server products, integration products, portal products, or integrated development environment products.
- 7. A system for inter-software component dependency checking, comprising:
a set of rules that define allowable and/or forbidden dependencies between said software components; a rules-based compliance checking routine that runs test when a software component is modified, to examine the dependencies between two or more of said interrelated software component according to said rules; and, a report device that reports the results of said tests.
- 8. The system of claim 7 wherein the set of rules define the dependencies allowed, forbidden, or required for those software components.
- 9. The system of claim 8 wherein said software components comprise any of RMI, EJB, or JMS components or modules.
- 10. A method for inter-software component dependency checking, comprising the steps of:
defining a set of rules that define allowable and/or forbidden dependencies between said software components; running a rules-based compliance check when a software component is modified, to examine the dependencies between two or more of said interrelated software products according to said rules; and, reporting the results of said tests.
- 11. The method of claim 10 wherein the set of rules define the dependencies allowed, forbidden, or required for those software components.
- 12. The method of claim 10 wherein said software components comprise any of RMI, EJB, or JMS components or modules.
- 13. A system for client-server dependency checking comprising:
a set of rules that define allowable and/or forbidden dependencies between a client software system and a server; a rules-based compliance checking routine that runs test when said client software system is built, to examine the dependencies between said client software system and said server; and, a report device that reports the results of said tests or halts the build of said client software system.
- 14. The system of claim 13 wherein the set of rules define the dependencies allowed, forbidden, or required for the client and server.
- 15. The system of claim 13 wherein said client comprises any of thin clients, wireless devices, RMI clients, JMS clients, or Web Services.
- 16. A method for client-server dependency checking, comprising the steps of:
defining a set of rules that define allowable and/or forbidden dependencies between a client software system and a server; running a rules-based compliance checking routine at build time that runs test when said client software system is built, to examine the dependencies between said client software system and said server; and, reporting the results of said tests or halting the build of said client software system.
- 17. The method of claim 16 wherein the set of rules define the dependencies allowed, forbidden, or required for the client and server.
- 18. The method of claim 16 wherein said client comprises any of thin clients, wireless devices, RMI clients, JMS clients, or Web Services.
- 19. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:
defining a set of rules that define allowable and/or forbidden dependencies between said interrelated software products; periodically running tests to examine the dependencies between two or more of said interrelated software products according to said rules; and, reporting the results of said tests.
- 20. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:
defining a set of rules that define allowable and/or forbidden dependencies between said software components; running a rules-based compliance check when a software component is modified, to examine the dependencies between two or more of said interrelated software products according to said rules; and, reporting the results of said tests.
- 21. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:
defining a set of rules that define allowable and/or forbidden dependencies between a client software system and a server; running a rules-based compliance checking routine at build time that runs test when said client software system is built, to examine the dependencies between said client software system and said server; and, reporting the results of said tests or halting the build of said client software system.
CLAIM OF PRIORITY
[0001] This application claims priority to U.S. Provisional Patent Application 60/450,839, filed Feb. 28, 2003, entitled “SYSTEM AND METHOD FOR SOFTWARE COMPONENT DEPENDENCY CHECKING” (Atty. Docket No. BEAS-01336US0), and incorporated herein by reference. This application is also a Continuation-In-Part of copending U.S. patent application Ser. No. 10/655,059, filed Sep. 4, 2003 (Atty. Docket No. BEAS-01306US1), entitled “SYSTEM AND METHOD FOR SOFTWARE MODULE ARCHITECTURE LANGUAGE AND COMPLIANCE”; which claims priority from U.S. Provisional Patent Application No. 60/408,697 filed Sep. 5, 2002 (Atty. Docket No. BEAS-01306US0) entitled “SYSTEM AND METHOD FOR MODULE ARCHITECTURE LANGUAGE AND COMPLIANCE CHECKING”, both of which are incorporated by reference herein.
Provisional Applications (2)
|
Number |
Date |
Country |
|
60450839 |
Feb 2003 |
US |
|
60408697 |
Sep 2002 |
US |
Continuation in Parts (1)
|
Number |
Date |
Country |
Parent |
10655059 |
Sep 2003 |
US |
Child |
10785757 |
Feb 2004 |
US |