System and method for software component dependency checking
AssigneeBEA Systems, Inc.
InventorReto Kramer
Life of this patent
Estimating the term…
Abstract
A system and method for use with an enterprise system or software development system, for determining or checking for dependencies between software components, or between other components of said system. The system utilizes a module architecture specification language and toolkit to check system code for compliance against a set of rules or requisites. The module architecture specification can be structured into product-wide groundrules applicable to all subsystems, subsystem-, layer-, module-specific, and thin-client/server rules. In accordance with one embodiment, the system can be used to allow, forbid, or constrain certain dependencies between software modules, or between the building blocks, organization components, or products that make up a large enterprise system.
Claims21
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.
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.
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.
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.
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.
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.
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.
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.
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.
Dependencies are inferred from the claim text.