Abstract: Mechanisms to support fine-grain namespacing are provided. When an object is to be loaded within a processing environment, a specific namespace for that object is dynamically resolved during the load. That namespace can be dynamically resolved via object inheritance, via specific object-attribute declaration, and/or via consultation with a namespace object.

Abstract: Mechanisms for sharing attributes between objects are provided. An object includes a special designation for at least one component, which is identified as a shared attribute. Data associated with the shared attribute is populated and managed from a central location within a processing environment. Multiple instances of a same object or of entirely different objects can reference, declare, and use the data from the central location.

Abstract: A system for detecting banking frauds in historical data and future transactions from a user supplied specimen set of fraudulent transactions, said specimen set of transactions defining one type of fraud identified by the user, said system comprises: means (301) to accept at least one set of banking transactions from the user and means to accept a type of fraud associated with each said set of transactions from the user (FIG. 3, Step 1); means (302) to run a set of atomic clue detectors on each said transaction for each said specimen (FIG. 3, Step 2); means (303) to store the output of said clue detectors for each said transactions for each said specimen fraudulent transactions (FIG. 3, Step 3); means (303) to compare the output of each said clue detector with a pre-defined threshold (FIG. 3, Step 3); means (304, 305) to assign weight to each said clue detector (FIG. 3, Step 4 and 5); means (306) to combine the clue detectors and their said weights into one fraud scenario (FIG.

Abstract: Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Abstract: Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user.

Abstract: Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available.