| Method and system for enforcing ontological context rules for object-oriented programs -> Monitor Keywords |
|
|
 
Method and system for enforcing ontological context rules for object-oriented programsRelated Patent Categories: Data Processing: Software Development, Installation, And Management, Software Program Development Tool (e.g., Integrated Case Tool Or Stand-alone Development Tool)Method and system for enforcing ontological context rules for object-oriented programs description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20050289501, Method and system for enforcing ontological context rules for object-oriented programs. Brief Patent Description - Full Patent Description - Patent Application Claims
LIMITED COPYRIGHT WAIVER [0001] A portion of the disclosure of this patent document contains material to which the claim of copyright protection is made. The copyright owner has no objection to the facsimile reproduction by any person of the patent document or the patent disclosure as it appears in the U.S. Patent and Trademark Office file or records, but reserves all other rights whatsoever. FIELD [0002] This invention relates generally to the field of software and more particularly to enforcing ontological context rules for object-oriented programs. BACKGROUND [0003] Most programming languages include a set of parameter/message passing mechanisms to pass data from one function or method to another. These mechanisms are often based on a mechanical metaphor that defines a "machine," which is insensitive to its context. Traditionally, reducing context sensitivity was important to sound machine design. Soundly designed machines traditionally have a rigidly defined small number of inputs and outputs. Machines are analogous to software functions and methods. Machine input/output interfaces are analogous to programming language parameter/message passing mechanisms. In the mechanical metaphor, a user determines the machine inputs. Thus "agency" is never in the machine, but is rather always in the machine user. Similarly, in the programming language paradigm, the "user" of the function or method determines what the inputs and outputs will be. [0004] Although the mechanical metaphor is good for repeatedly performing simple tasks accurately, one disadvantage of machines, and thus mechanisms, is that machines do not react well to environmental changes. When environments change, machines do not typically adapt to such environmental changes. Similarly, typical programming language parameter/message passing mechanisms have an inherent mechanical rigidity, which inhibits adaptation to environmental changes. For example, a business application system is a computer model of a frequently changing human process. Human processes are complex adaptive systems, as they adapt to environmental changes. However, application software is typically very difficult to change because it uses parameter-passing mechanisms that "lock in" an original design, which becomes outdated as the human process changes. A disadvantage of typical programming language parameter/message passing mechanisms is that they have an inherent mechanical rigidity, which inhibits systems from adapting to environmental changes. [0005] According to one prior art programming language, functions and their parameters must be declared at design time. Additionally, callers of a function must call the function using the function's name and its parameter names and types. With many parameter/message passing mechanisms, both calling and called routines must specify how parameters will be represented and interpreted. Parameter/message passing mechanisms also require that parameter representations be expressed at design time. When systems are modified, the parameter representations must be modified everywhere they are called. In large systems, parameters can be difficult to find and therefore, modifying parameters can be extremely difficult and expensive. [0006] According to another prior art programming language, all parameter evaluations are done before the called routine or function begins to execute. One disadvantage of this prior art programming language is that early parameter evaluation can lead to redundant computation when certain parameters are not used within the routine or function. BRIEF DESCRIPTION OF THE FIGURES [0007] The present invention is illustrated by way of example and is limited in the Figures of the accompanying drawings in which: [0008] FIG. 1 is a diagrammatic representation of relationships between object-oriented classes, according to exemplary embodiments of the invention; [0009] FIG. 2 is a tree diagram illustrating a class aggregation hierarchy defining reachable ontological contexts for field classes within a business class; [0010] FIG. 3 is a diagrammatic representation of relationships between fields in an employee master business class, according to exemplary embodiments of the invention; [0011] FIG. 4 is a tree diagram illustrating a class hierarchy defining reachable ontological contexts for field classes within a business class; [0012] FIG. 5 is a block diagram illustrating a system for storing and processing programming language code containing ontological context rules; [0013] FIG. 6 is a flow diagram illustrating general operations for translating pattern language code into high-level object-oriented code; [0014] FIG. 7 is a flow diagram illustrating operations for generating field and business class definitions that use the concepts of ontological context, according to embodiments of the invention; [0015] FIG. 8 is a flow diagram illustrating operations for validating ontological context rules; [0016] FIG. 9 is a flow diagram illustrating operations for instantiating a business class, according to exemplary embodiments of the invention; [0017] FIG. 10 is a flow diagram illustrating more detailed operations for creating an instance of a business class (see block 904), according to exemplary embodiments of the invention; [0018] FIG. 11 is a flow diagram illustrating operations for enforcing ontological context rules; and [0019] FIG. 12 illustrates an exemplary computer system used with certain embodiments of the invention. DESCRIPTION OF THE EMBODIMENTS Continue reading about Method and system for enforcing ontological context rules for object-oriented programs... Full patent description for Method and system for enforcing ontological context rules for object-oriented programs Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Method and system for enforcing ontological context rules for object-oriented programs patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Method and system for enforcing ontological context rules for object-oriented programs or other areas of interest. ### Previous Patent Application: Infrastructure-aware application development Next Patent Application: System for identifying project status and velocity through predictive metrics Industry Class: Data processing: software development, installation, and management ### FreshPatents.com Support Thank you for viewing the Method and system for enforcing ontological context rules for object-oriented programs patent info. IP-related news and info Results in 0.10357 seconds Other interesting Feshpatents.com categories: Medical: Surgery , Surgery(2) , Surgery(3) , Drug , Drug(2) , Prosthesis , Dentistry 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
