Source: https://patents.justia.com/patent/5937189
Timestamp: 2019-10-20 03:48:15
Document Index: 455305328

Matched Legal Cases: ['Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 94', 'Application No. 95', 'Application No. 95', 'Application No. 95']

US Patent for Object oriented framework mechanism for determining configuration relations Patent (Patent # 5,937,189 issued August 10, 1999) - Justia Patents Search
Justia Patents US Patent for Object oriented framework mechanism for determining configuration relations Patent (Patent # 5,937,189)
Nov 12, 1996 - IBM
a main memory coupled to the central processing unit, the main memory containing an object-oriented framework mechanism that provides at least one configuration environment, the framework mechanism executing on the central processing unit, wherein the framework mechanism comprises a relationship generation class, the relationship generation class defining:
at least one relationship generation object corresponding to the at least one configuration environment; and
a first set of object methods to perform a plurality of predetermined functions to implement the configuration environment.
at least one object method that creates at least one configuration item list, each configuration item list containing a plurality of configuration items, each configuration item corresponding to one of the plurality of items, each configuration item list corresponding to one configuration environment;
at least one object method that establishes a plurality of possible relationships for the plurality of configuration items; and
at least one object method that reports the plurality of possible relationships among the plurality of configuration items and creates a plurality of actual relationships based on the plurality of possible relationships.
3. The computer system of claim 1 wherein the relationship generation class is a core class of the framework mechanism that is defined by the framework mechanism to implement the at least one configuration environment.
4. The computer system of claim 1 wherein the framework mechanism further comprises a configuration item class, a configuration item list class, and an assignment controller class,
the configuration item class defining:
a plurality of configuration item objects corresponding to the plurality of items; and
a second set of object methods for requesting that a required resource corresponding to one of the plurality of configuration objects report its relationship;
the configuration item list class defining:
at least one configuration item list object containing the plurality of configuration item objects; and
a third set of object methods for creating the plurality of configuration items and for reporting the relationship of each configuration item;
the assignment controller class defining:
at least one assignment controller object; and
a fourth set of object methods for establishing relationships between the plurality of configuration items.
5. The computer system of claim 4 wherein the framework mechanism further comprises an item class, a relationship class, and an item structure class,
the item class defining:
a plurality of item objects corresponding to the plurality of items;
the relationship class defining:
a plurality of relationship objects indicating relationships for a plurality of the item objects;
the item structure class defining:
at least one item structure object containing the plurality of item objects and the plurality of relationship objects; and
a fifth set of object methods to retrieve at least one of the plurality of items from the item structure object.
6. The computer system of claim 5 wherein the configuration item list class, the assignment controller class, the item class, the relationship class, and the item structure class are core classes of the framework mechanism, the implementation of which cannot be changed by a user.
7. The computer system of claim 5 wherein the framework mechanism further comprises a required resource class, the required resource class defining:
at least one required resource object; and
a sixth set of object methods for finding possible suppliers for the required resource object, for assigning one of the possible suppliers to the required resource object, for establishing and comparing assignment priority for the required resource object, and for reporting the relationship of the required resource object.
8. The computer system of claim 7 wherein the framework mechanism further comprises a resource class and a resource group class,
the resource class defining:
at least one resource object; and
a seventh set of object methods for checking the possible relationship of the resource object and for reporting the actual relationship of the resource object;
the resource group class defining:
at least one resource group object containing at least one resource object; and
an eighth set of object methods for adding possible users for the resource object, for assigning one of the possible users to the resource object, for checking a possible relationship for the resource object, and for reporting an assigned relationship of the resource object.
a required resource association class referencing a plurality of required resources, the required resource association class defining:
at least one required resource association object; and
a ninth set of object methods for finding possible suppliers for the required resources, for adding a possible supplier for the required resource, and for assigning one of the possible suppliers to the required resource.
10. The computer system of claim 9 wherein the framework mechanism further comprises:
a resource restriction class, the resource restriction class defining:
at least one resource restriction object; and
a tenth set of object methods for finding which of a plurality of possible relationships are valid relationships.
11. The computer system of claim 10 wherein the configuration item class, the required resource class, the resource class, the resource group class, the required resource association class, and the resource restriction class are extensible classes of the framework mechanism, the implementation of which by a user defines the at least one configuration environment.
16. The computer system of claim 1 wherein the framework mechanism comprises:
a main memory coupled to the central processing unit, the main memory containing an object-oriented framework mechanism that provides at least one configuration environment, the framework mechanism executing on the central processing unit, wherein the framework mechanism comprises an item class, a relationship class, and an item structure class,
a plurality of item objects corresponding to the plurality of items; the relationship class defining:
18. The computer system of claim 17 wherein the item class, the relationship class, and the item structure class are core classes of the framework mechanism that are defined by the framework mechanism to implement the at least one configuration environment.
a main memory coupled to the central processing unit, the main memory containing an object-oriented framework mechanism that provides at least one configuration environment, the framework mechanism executing on the central processing unit, wherein the framework mechanism comprises a required resource class, the required resource class defining:
a main memory coupled to the central processing unit, the main memory containing an object-oriented framework mechanism that provides at least one configuration environment, the framework mechanism executing on the central processing unit, wherein the framework mechanism comprises a resource class and a resource group class,
a main memory coupled to the central processing unit, the main memory containing an object-oriented framework mechanism that provides at least one configuration environment, the framework mechanism executing on the central processing unit, wherein the framework mechanism comprises:
23. A method for determining configuration relations between a plurality of items, the method comprising the steps of:
providing an extensible object oriented framework mechanism that determines the configuration relations between the plurality of items according to extended portions of the framework mechanism that are customized to provide a desired configuration environment;
executing the object oriented framework mechanism on a computer system, the executing object oriented framework mechanism performing the steps of;
(a) checking possible relationships among the plurality of items, wherein some of the items are users and some of the items are suppliers;
(b) determining which of the items are possible suppliers;
(c) determining which of the items are possible users;
(d) assigning at least one supplier from the possible suppliers; and
(e) assigning at least one user from the possible users.
extending the framework mechanism to define the desired configuration environment.
(f) building a configuration item list from the plurality of items; and
(g) reporting the relationships of the plurality of items.
26. The method of claim 25 wherein the step building the configuration item list includes the steps of:
creating an empty configuration item list object;
retrieving a plurality of the items; and
creating a plurality of configuration item objects contained within the configuration item list object, each of the configuration item objects corresponding to one of the retrieved plurality of items.
27. The method of claim 25 wherein the step of reporting the relationships of the plurality of items includes the step of creating a relationship only if a supplier is matched to a user.
(A) an object-oriented framework mechanism for determining the configuration relations among a plurality of items, the framework mechanism including an extensible configuration relations mechanism that determines the configuration relations according to extended portions of the framework mechanism wherein the framework mechanism comprises:
a first set of object methods to perform a plurality of predetermined functions to implement the configuration environment; and
31. The program product of claim 28 wherein the first set of object methods includes:
(A) an object-oriented framework mechanism for determining the configuration relations among a plurality of items, the framework mechanism including an extensible configuration relations mechanism that determines the configuration relations according to extended portions of the framework mechanism, wherein the framework mechanism comprises:
a fifth set of object methods to retrieve at least one of the plurality of items from the item structure object; and
a sixth set of object methods for finding possible suppliers for the required resource object, for assigning one of the possible suppliers to the required resource object, for establishing and comparing assignment priority for the required resource object, and for reporting the relationship of the required resource object; and
an eighth set of object methods for adding possible users for the resource object, for assigning one of the possible users to the resource object, for checking a possible relationship for the resource object, and for reporting an assigned relationship of the resource object; and
a ninth set of object methods for finding possible suppliers for a required resource, for adding a possible supplier for the required resource, and for assigning one of the possible suppliers to the required resource; and
a tenth set of object methods for finding which of a plurality of possible relationships are valid relationships; and
a plurality of configuration item objects corresponding to the plurality of items;
at least one configuration item list object containing the plurality of configuration item objects;
a fourth set of object methods for establishing relationships between the plurality of configuration items; and
38. A method for determining configuration relations for a plurality of items, the method comprising the steps of:
(A) providing a relationship generation object corresponding to the at least one configuration environment, the relationship generation object including a first set of object methods to perform a plurality of predetermined functions to implement the configuration environment;
(B) providing a plurality of configuration item objects corresponding to the plurality of items;
(C) providing a second set of object methods for requesting that a required resource corresponding to one of the plurality of configuration objects report its relationship;
(D) providing at least one configuration item list object containing the plurality of configuration item objects;
(E) providing a third set of object methods for creating the plurality of configuration items and for reporting the relationship of each configuration item;
(F) providing at least one assignment controller object;
(G) providing a fourth set of object methods for establishing relationships between the plurality of configuration items;
(H) providing a plurality of item objects corresponding to the plurality of items;
(I) providing a plurality of relationship objects indicating relationships for a plurality of the item objects;
(J) providing at least one item structure object containing the plurality of item objects and the plurality of relationship objects;
(K) providing a fifth set of object methods to retrieve at least one of the plurality of items from the item structure object;
(L) providing at least one required resource object;
(M) providing a sixth set of object methods for finding possible suppliers for the required resource object, for assigning one of the possible suppliers to the required resource object, for establishing and comparing assignment priority for the required resource object, and for reporting the relationship of the required resource object;
(N) providing at least one resource object;
(O) providing a seventh set of object methods for checking the possible relationship of the resource object and for reporting the actual relationship of the resource object;
(P) providing at least one resource group object containing at least one resource object;
(Q) providing an eighth set of object methods for adding possible users for the resource object, for assigning one of the possible users to the resource object, for checking a possible relationship for the resource object, and for reporting an assigned relationship of the resource object;
(R) providing at least one required resource association object;
(S) providing a ninth set of object methods for finding possible suppliers for a required resource, for adding a possible supplier for the required resource, and for assigning one of the possible suppliers to the required resource;
(T) providing at least one resource restriction object;
(U) a tenth set of object methods for finding which of a plurality of possible relationships are valid relationships; and
(V) executing the object oriented framework mechanism on a computer system to determine the configuration relations of the plurality of items.
(A) an object oriented framework mechanism for determining configuration relations for a plurality of items in at least one configuration environment, the framework mechanism including a relationship generation object corresponding to the at least one configuration environment, the relationship generation object including a first set of object methods to perform a plurality of predetermined functions to implement the configuration environment, the framework mechanism further including a plurality of configuration item objects corresponding to the plurality of items, the configuration item objects including a second set of object methods for requesting that a required resource corresponding to one of the plurality of configuration objects report its relationship, the framework mechanism further including at least one configuration item list object containing the plurality of configuration item objects, each configuration item list object including a third set of object methods for creating the plurality of configuration items and for reporting the relationship of each configuration item, the framework mechanism further including at least one assignment controller object, the assignment controller object including a fourth set of object methods for establishing relationships between the plurality of configuration items, the framework mechanism further including a plurality of item objects corresponding to the plurality of items, the plurality of item objects including a plurality of relationship objects indicating relationships for a plurality of the item objects, the framework mechanism further including at least one item structure object containing the plurality of item objects and the plurality of relationship objects, the item structure object including a fifth set of object methods to retrieve at least one of the plurality of items from the item structure object, the framework mechanism further including at least one required resource object, the required resource object including a sixth set of object methods for finding possible suppliers for the required resource object, for assigning one of the possible suppliers to the required resource object, for establishing and comparing assignment priority for the required resource object, and for reporting the relationship of the required resource object, the framework mechanism further including at least one resource object, the resource object including a seventh set of object methods for checking the possible relationship of the resource object and for reporting the actual relationship of the resource object, the framework mechanism further including at least one resource group object containing at least one resource object, the resource group object including an eighth set of object methods for adding possible users for the resource object, for assigning one of the possible users to the resource object, for checking a possible relationship for the resource object, and for reporting an assigned relationship of the resource object, the framework mechanism further including at least one required resource association object, the required resource association object including a ninth set of object methods for finding possible suppliers for a required resource, for adding a possible supplier for the required resource, and for assigning one of the possible suppliers to the required resource, the framework mechanism further including at least one resource restriction object, the resource restriction object including a tenth set of object methods for finding which of a plurality of possible relationships are valid relationships; and
45. An object oriented framework mechanism that determines configuration relations for a plurality of items, the framework mechanism comprising:
at least one extensible class wherein the implementation of the at least one extensible class is defined by the user of the framework mechanism, by extending the at least one extensible class, thereby defining at least one configuration environment;
a relationship generation object corresponding to the at least one configuration environment, the relationship generation object including a first set of object methods to perform a plurality of predetermined functions to implement the configuration environment;
at least one assignment controller object;
a fourth set of object methods for establishing relationships between the plurality of configuration items;
at least one item structure object containing the plurality of item objects and the plurality of relationship objects;
a fifth set of object methods to retrieve at least one of the plurality of items from the item structure object;
at least one required resource object;
a sixth set of object methods for finding possible suppliers for the required resource object, for assigning one of the possible suppliers to the required resource object, for establishing and comparing assignment priority for the required resource object, and for reporting the relationship of the required resource object;
at least one resource group object containing at least one resource object;
an eighth set of object methods for adding possible users for the resource object, for assigning one of the possible users to the resource object, for checking a possible relationship for the resource object, and for reporting an assigned relationship of the resource object;
at least one required resource association object;
a ninth set of object methods for finding possible suppliers for a required resource, for adding a possible supplier for the required resource, and for assigning one of the possible suppliers to the required resource;
46. A method for determining configuration relations for a plurality of items using a computer system having a central processing unit and a main memory, the main memory having an application program that provides an object oriented programming environment, the method comprising the steps of:
(A) providing in the program an object oriented framework mechanism that determines the configuration relations according to extended portions of the framework mechanism that are customized to provide a desired configuration environment, the framework mechanism including:
a set of core functions wherein the implementation of the core functions is defined by the framework mechanism and cannot be modified by a user of the framework mechanism; and
(B) extending the extensible functions in the framework mechanism to define particular classes having predetermined protocols and defining particular object methods that determine the configuration relations, the extensible functions defining the desired configuration environment;
(C) generating an executable configuration relations system by integrating together the extensible functions and the core functions; and
(D) executing the executable configuration relations system on the computer system to determine the configuration relations.
(E) checking possible relationships among the plurality of items, wherein some of the items are users and some of the items are suppliers;
(F) determining which of the items are possible suppliers;
(G) determining which of the items are possible users;
(H) assigning at least one supplier from the possible suppliers; and
(I) assigning at least one user from the possible users.
(J) building a configuration item list from the plurality of items; and
(K) reporting the relationships of the plurality of items.
49. The method of claim 48 wherein the step building the configuration item list includes the steps of:
50. The method of claim 49 wherein the step of reporting the relationships of the plurality of items includes the step of creating a relationship only if a supplier is matched to a user.
an object oriented framework mechanism for determining configuration relations for a plurality of items, the framework mechanism including at least one core function defined by relationships between a plurality of classes within the framework mechanism, wherein the implementation of the at least one core function is defined by the framework mechanism and cannot be modified by a user of the framework mechanism, the framework mechanism further including at least one extensible function defined by at least one extensible class, wherein the implementation of the at least one extensible class is defined by the user of the framework mechanism by extending the at least one extensible class, thereby defining a configuration environment that governs the operation of the framework mechanism; and
52. The program product of claim 51 wherein the signal bearing media comprises recordable media.
54. The program product of claim 51 wherein the framework mechanism comprises:
at least one resource restriction object;
a tenth set of object methods for finding which of a plurality of possible relationships are valid relationships;
wherein the object oriented framework mechanism determines the configuration relations according to extended portions of the framework mechanism that are customized to provide a desired configuration environment.
5257384 October 26, 1993 Farrand et al.
5293470 March 8, 1994 Birch et al.
Text of IBM Technical Disclosure Bulletin, vol. 37, DeBinder et al., Feb. 1994, "Results Folder Framework", pp. 431-432. Text of IBM Technical Disclosure Bulletin, vol. 36, Coskun, N., Jun. 1993, "Persistent Framework Independent Record/Playback Framework", pp. 261-264. Text of IBM Technical Disclosure Bulletin, Baker et al., Oct. 1991, "Model View Schema", pp. 321-322. Text of IBM Technical Disclosure Bulletin, Baker et al., Oct. 1991, "Office Container Class", pp. 309-310. Text of IBM Technical Disclosure Bulletin, Cavendish et al., Jul. 1991, "Icon Pane Class", pp. 118-119. Text of IBM Technical Disclosure Bulletin, Baker et al., Jun. 1991, "Distribution List Class", p. 159. Text of IBM Technical Disclosure Bulletin, Cavendish et al., Jun. 1991, "Object-Oriented Documentation Tool", pp. 50-51. Text of IBM Technical Disclosure Bulletin, Allard et al., Feb. 1990, "Object-Oriented Programming in C--the Linnaeus System", pp. 437-439. Text of IBM Technical Disclosure Bulletin, vol. 38, No. 1, Jan. 1995, pp. 411-414, J. Knapman, "Generating Specific Server Programs in Distributed Object-Oriented Customer Information Control System". Text of IBM Technical Disclosure Bulletin, vol. 37, No. 12, Dec. 1994, pp. 19-20, Al-Karmi et al., "Events Set for Event Tracing in Distributed Object-Oriented Systems". Text of IBM Technical Disclosure Bulletin, vol. 37, No. 12, Dec. 1994, pp. 375-378, Acker et al., "Automatically Generating Formatted Documentation for Object-Oriented Class Libraries". Text of IBM Technical Disclosure Bulletin, vol. 37, No. 11, Nov. 1994, pp. 71-72, Behrs et al., "Device Support Framework to Support ISO DPA 10175 and POSIX 1387.4". Text of IBM Technical Disclosure Bulletin, vol. 37, No. 7, Jul. 1994, pp. 145-146, Banda et al., "Exception Management Algorithm for Multi-Threaded Method Invocation". Text of IBM Technical Disclosure Bulletin, vol. 37, No. 6B, Jun. 1994, pp. 553-556, Gest et al., "Portable Object-Oriented Event Manager". Abstract of WIPO Patent Application No. WO 95/04966, F. T. Nguyen, Feb. 16, 1995, "Automatic Management of Components in Object-Oriented System". Abstract for U.S. Patent No. 5,388,264, Milne et al., Feb. 7, 1995, "Object-Oriented Framework System for Enabling Multimedia Presentation with Routing and Editing of MIDI Information". Abstract for WIPO Patent Application No. WO 94/23364, Heninger et al., Oct. 13, 1994, "Framework Processing Apparatus for Application Software". Abstract for U.S. Patent No. 5,369,766, Heninger et al., Nov. 29, 1994, "Object Oriented Application Processing Apparatus". Abstract from WIPO Patent Application No. WO 9422081, Sep. 29, 1994, "Hardware-Independent Interface for Interrupt Processing", G. O. Norman et al. Abstract for WIPO Patent Application No. 94/19752, Anderson et al., Sep. 1, 1994, "Concurrent Framework Processing Apparatus for Two or More Users". Abstract for WIPO Patent Application No. 94/19751, Anderson et al., Sep. 1, 1994, "Concurrent Framework Processing Apparatus for Application Users". Abstract for WIPO Patent Application No. 94/19740, Goldsmith et al., Sep. 1, 1994, "Framework Processor of Object-Oriented Application". Abstract from WIPO Patent Application No. 94/15286, Goldsmith et al., Jul. 7, 1994, "Object-Oriented Framework for Object Operating System". Abstract for WIPO Patent Application No. 94/15282, Anderson et al., Jul. 7, 1994, "Dialog System Object-Oriented System Software Platform". Abstract for WIPO Patent Application No. 94/15281, Anderson et al., Jul. 7, 1994, "Atomic Command Object-Oriented System Software Platform". Abstract for WIPO Patent Application No. WO 9415285, Jul. 7, 1994, "Object-Oriented Notification Framework System", D. R. Anderson et al. Abstract for U.S. Patent No. 5,119,475, Schoen et al., Jun. 2, 1992, "Object-Oriented Framework for Menu Definition". Abstract No. 95-091003/12, "Flexible Multi-Platform Partitioning for Computer Applications in Object Oriented System". Abstract for WIPO Patent Application No. 95/01610, Koko et al., Jan. 12, 1995, "Object Oriented Product Structure Management in Computer-Aided Product Design". Abstract fpr WIPO Patent Application No. 95/04967, Feb. 16, 1995, "Access Method to Data Held in Primary Memory Based Data Base". Abstract for WIPO Patent Application No. 95/02219, Helgeson et al., Jan. 19, 1995, "Distributed Computation Based on Movement, Execution and Insertion of Processes in Network". Abstract from U.S. Patent No. 5,371,891, "Object Constructions in Compiler in Object Oriented Programming Language", J. Gray et al., Dec. 6, 1994. Abstract from EPO Patent Applicaton No. EP 622730, "Encapsulation of Extracted Portions of Documents Into Objects", M. A. Malamud, Nov. 2, 1994. Abstract for EPO Patent No. 619544, S. Danforth, Oct. 12, 1994, "Language-Neutral Object-Oriented Programming". Abstract for WIPO Patent No. 94/20912, Sep. 15, 1994, "Object-Oriented System for Managing Financial Instruments". Inspec Abstract No. C9504-7460-043, Sells et al., 1995, "Implementation of the Architecture for a Time-Domain Dynamical System Stimulation in a Very High-Level Pictorial Object-Oriented". Inspec Abstract No. C9504-7460-042, Coleman et al., "An End-to-End Simulation of A Surveillance System Employing Architecture Independence, Variable Fidelity Components and Software Reuse". Inspec Abstract No. C9503-6140D-045, Satoh et al., 1995, "Process Algebra Semantics for a Real Time Object Oriented Programming Language". Inspec Abstract No. C9501-7160-020, C. Le Pape, 1993, "The Cost of Genericity: Experiments With Constraint-Based Representations of Time-Tables". Inspec Abstract No. C9501-6140D-005, S. Vinoski, 1994, "Mapping CORBA IDL Into C++". Inspec Abstract No. C9501-7330-007, Salminen et al., 1994, "Modelling Trees Using an Object-Oriented Scheme". Inspec Abstract No. C9412-6110B-221, Berghel et al., 1992, "A Generic Object-Oriented Concurrency Mechanism for Extensibility and Reuse of Synchronization Components". Inspec Abstract No. B9412-6210Q-016, from Oingzhong et al., 1992, "An Object-Oriented Model for Ingelligent Networks". Inspec Abstract No. C9412-7810-003, from Jung et al., 1993, "Development of an Object-Oriented Anthropometric Database for an Ergonomic Man Model". Inspec Abstract No. C9412-6110J-014 from Griss et al., 1994, "Object-Oriented Reuse". Inspec Abstract No. C9411-6130B-108, from Mili et al., 1992, "Building a Graphical Interface for a Reuse-Oriented CASE Tool". Inspec Abstract No. C9411-7100-029, from C. Le Pape, 1994, "Implementation of Resource Constraints in ILOG Schedule: A Library for the Development of Constraint-Based Scheduling Systems". Inspec Abstract No. C9411-6115-035, from Mili et al., 1991, "SoftClass: An Object-Oriented Tool for Software-Reuse". Inspec Abstract No. C9410-6180G-015, from Eichelberg et al., 1993, "Integrating Interactive 3D-Graphics into an Object-Oriented Application Framework". Inspec Abstract No. B9409-6210M-025, from Hellemans et al., 1994, "An Object-Oriented Approach to Dynamic Service Descriptions". Inspec Abstract No. C9409-6180-059, from Wang et al., 1993, "A Framework for User Customization". Inspec Abstract No. C9408-6110B-016, from Chen et al., 1994, "An Experimental Study of Using Reusable Software Design Frameworks to Achieve Software Reuse". Inspec Abstract No. C9408-7420-021, from Pirklbauer et al., 1994, "Object-Oriented Process Control Software". Inspec Abstract No. C9408-6110J-011, from Gyu-Chung et al., 1993, "System Methodologies of Object-Oriented Programs". Inspec Abstract No. C9407-7420D-045, from Desai et al., "Controller Structure Definition Via Intelligent Process Control". Inspec Abstract No. C9407-6140D-014, from Satoh et al., 1994, Semantics for a Real-Time Object-Oriented Programming Language. Inspec Abstract No. C9406-6150N-015, from Schmidt et al., 1994, "The Service Configurator Framework: An Extensible Architecture for Dynamically Configuring Concurrent, Multi-Service Network Daemons". Inspec Abstract No. C9405-6180G-031, from Woyak et al., 1993, "A Motif-Like Object-Oriented Interface Framework using PHIGS". Inspec Abstract No. C9403-6180-027, 1991, "An Event-Object Recovery Model for Object-Oriented User Interfaces" from Proceedings of ACMSymposium on User Interface Software & Technology. Inspec Abstract No. C9504-6130B-049, from A. van Dam, 1995, "VR as a Forcing Function: Software Implications of a New Paradigm". Inspec Abstract No. C9504-6140D-024, from Sheffler et al., 1995, "An Object-Oriented Approach to Nested Data Parallelism". Inspec Abstract No. C9503-6110B-045, from Rosiene et al., 1995, "A Data Modeling Framework for Queueing Network Models". Inspec Abstract No. B9503-8110B-023, from Mautref et al., 1995, "An Object-Oriented Framework for the Development of Interactive Decision Support Systems". Inspec Abstract No. C9502-7160-026, from Menga et al., 1995, "An Object-Oriented Framework for Enterprise Modelling". Inspec Abstract No. C9502-6130G-006, "Support for Enterprise Modelling in CSCW", P. Hennessy et al., 1994. Inspec Abstract No. C9502-7810C-058, from Lin et al., 1995, "Can CAL Software Be More Like Computer Games?". Inspec Abstract No. C9501-6115-039, from Elia et al., 1993, "G++: An Object Oriented Environment for Developing Distributed Applications". Inspec Abstract No. C9412-7330-186, from Righter et al., 1994, "An Object-Oriented Characterization of Spatial Ecosystem Information". Inspec Abstract No. C9412-6160J-025 from J. Livari, 1994, "Object-Oriented Information Systems Analysis: A Comparison of Six Object-Oriented Analysis Methods". Inspec Abstract No. C9412-6110J-006, from Lau et al., 1993, "Using SOM for Tool Integration". Inspec Abstract No. C9411-6160J-011, from Odberg et al., 1992, "A Framework for Managing Schema Versioning in Object-Oriented Databases". Inspec Abstract No. C9406-7490-012, "A Discrete-Event Object-Oriented Modeling Environment for Sawmill Simulation". Inspec Abstract No. C9406-6115-048, 1993, "Constructing Multi-View Editing Environments Using MViews". Inspec Abstract No. 4664213, "Maintaining Information about Persistent Replicated Objects in a Distributed System", 1993 IEEE Conference on Distributed Computing Systems. Inspec Abstract No. C9406-6110J-029, "A Comparison of Object-Oriented Analysis and Design Methods", Proceedings of C++ World 1993. Inspec Abstract No. C9406-0310F-011, 1993, "Cost-Benefit Analysis of Object-Oriented Technology". Inspec Abstract No. C9406-6110J-007, from J. D. Grimes, 1993, "Objects 101--An Implementation View", Proceedings of COMPCON 1994. Inspec Abstract No. 4647921, from Uhorchak et al., 1993, "An Object-Oriented Class Library for Creating Engineering Graphs Using PHIGS". Inspec Abstract No. 4642214, from Marshall et al., 1992, "Using VDM Within an Object-Oriented Framework". Inspec Abstract No. 4626386, from Arora et al., 1993, "Building Diverse Environments with PCTE Workbench". Inspec Abstract No. 4622794, from Campbell et al., 1993, "A Technique for Documenting the Framework of an Object-Oriented System". Inspec Abstract No. 4618974, from Bowers, 1993, "Some Principles for the Encapsulation of the Behaviour of Aggregate Objects". Inspec Abstract No. 461931, from Islan et al, 1993, "Uniform Co-Scheduling Using Object-Oriented Design Techniques". Inspec Abstract No. 4613481, from Thieme et al., 1993, "Schema Integration in Object-Oriented Databases". Inspec Abstract No. 4603430, from G. Booch, 1994, "Designing an Application Framework". Inspec Abstract No. 4596323, from Frank et al., 1993, "An Integrated Environment for Designing Object-Oriented Enterprise Models". Inspec Abstract No. 4593721, Periyasamy et al., 1993, "A Formal Framework for Design and Verification of Robotic Agents". Inspec Abstract No. 4588839, from L. Fisher, 1992, "Constructing a Class Library for Microsoft Windows". Inspec Abstract No. 4588834, from G. Olander, 1992, "Chembench: Redesign of a Large Commercial Application Using Object-Oriented Techniques". Inspec Abstract No. 4566447, from J. Rossazza, 1992, "An Object-Centered Fuzzy Representation". Inspec Abstract No. 4565630, from Karpovich et al, 1993, "A Parallel Object-Oriented Framework for Stencil Algorithms". Inspec Abstract No. C9402-6150G-002, from Bruegge et al., 1993, "A Framework for Dynamic Program Analyzers". Inspec Abstract No. 4550414, from Parrish et al., 1993, "Automated Flow Graph-Based Testing of Object-Oriented Software Modules". Inspec Abstract No. 4540729, from Bailes et al., "The Ecology of Class Refinement". Inspec Abstract No. 4534334, from Campbell et al., 1991, "A Technique for Documenting the Framework of an Object-Oriented System". Inspec Abstract No. 4534330, from Istavrinos et al., 1992, "Experiences with an Object-Oriented Mapper for Coherent Distributed Shared Memory". Inspec Abstract No. 4528985, from Beneventano et al., 1993, "Taxonomic Reasoning with Cycles in LOGIDATA+". Inspec Abstract No. 4525743, from Hakimzadeh et al., 1993, "Instance Variable Access Locking for Object-Oriented Databases". Inspec Abstract No. 4512593, from H. Sakai, 1993, "A Method for Contract Design and Delegation in Object Behavior Modeling". Inspec Abstract No. B9310-6210L-099, "Templates, Types and Classes in Open Distributed Processing", 1993. Inspec Abstract No. 4459325, from Kesim et al., 1992, "On the Evolution of Objects in a Logic Programming Framework". Inspec Abstract No. 4447153, from Klein et al., 1992, "An Object-Oriented Framework for Curves and Surfaces". Inspec Abstract No. 4426852, from Benveniste et al., 1992, "Concurrent Proramming Notations in the Object-Oriented Language Arche". Inspec Abstract No. 4425343, from Demurjian et al., 1993, "Programming Versus Databases in Object-Oriented Paradigm". Inspec Abstract No. 4417604, from Kraiem et al., 1992, "Mapping of Conceptual Specifications Into Object-Oriented Programs". Inspec Abstract No. 4417563, from E. Maim, 1992, "Recognizing Objects from Constraints". Inspec Abstract No. 4411998, from Yi Deng et al., 1992, "Unifying Multi-Paradigms in Software System Design". Inspec Abstract No. 4408394, from Allen et al., 1992, "GEM: Global Event Management in CAD Frameworks". Inspec Abstract No. 4400350, from Y. Shoham, 1993, "Agent-Oriented Programming". Inspec Abstract No. 4395549, from Hogstrom et al., 1992, "Portability and Data Structures in Scientific Computing-Object-Oriented Design of Utility Routines in Fortran". Inspec Abstract No. 4391388, from Thomas et al., 1992, "A Generic Object-Oriented Concurrency Mechanism for Extensibility and Reuse of Synchronization Components". Inspec Abstract No. 4387201, from Chu et al., 1992, "A Pattern Based Approach of Integrating Data and Knowledge to Support Cooperative Query Answering". Inspec Abstract No. 4366189, from Holt et al., 1992, "A Framework for Using Formal Methods in Object-Oriented Software Development". Inspec Abstract No. 4356300, from Bertino et al., 1993, "Path-Index: An Approach to the Efficient Execution of Object-Oriented Queries". Inspec Abstract No. 4341376, from Bertino et al., 1992, "Optimization of Object-Oriented Queries Using Path Indices". Inspec Abstract No. 4331060, from Lau et al., 1992, "An Object-Oriented Class Library for Scalable Parallel Heuristic Search". Inspec Abstract No. 4318465, from P. Madany, 1992, "Object-Oriented Framework for File Systems". Inspec Abstract No. 4302722, from Eggenschwiler et al., 1992, "ET++SwapsManager: Using Object Technology in the Financial Engineering Domain". Inspec Abstract No. 4298324, from S. Nichol, 1992, "Extending Turbo Vision". Inspec Abstract No. 4297404, from Tanaka et al., 1992, "Two-Level Schemata and Generalized Links for Hypertext Database Models". Inspec Abstract No. 4287814, from Natarajan et al., 1992, "Issues in Building Dynamic Real-Time Systems". Inspec Abstract No. 4281362, from Marshall et al., 1991, "Using VDM within an Object-Oriented Framework". Inspec Abstract No. 4275707, from Tsukamoto et al., 1991, "DOT: A Term Representation Using DOT Algebra for Knowledge-Bases". Inspec Abstract No. 4275698, from Van den Bussche et al., 1991, "Evaluation and Optimization of Complex Object Selections". Inspec Abstract No. 4275693, from Giannotti et al., 1991, "Non-Determinism in Deductive Databases". Inspec Abstract No. 4270361, from Artale et al., 1991, "Introducing Knowledge Representation Techniques in Database Models". Inspec Abstract No. 4270125, from Becker et al., 1991, "Reusable Object-Oriented Specifications for Decision Support Systems". Inspec Abstract No. 4258492, from M. Ball, 1992, "Inside Templates: Implementing C++ Strategies". Inspec Abstract No. 4258051, from Rundensteiner et al., 1992, "Set Operations in Object-Based Data Models". Inspec Abstract No. 4244023, from George et al., 1991, "An Object-Oriented Data Model to Represent Uncertainty in Coupled Artificial Intelligence-Database Systems". Inspec Abstract No. 4234438, from Madany et al., 1991, "Organizing and Typing Persistent Objects Within an Object-Oriented Framework". Inspec Abastract No. 4152687, from M. Wolczko, 1992, "Encapsulation, Delegation and Inheritance in Object-Oriented Languages". Inspec Abstract No. 4117514, from Wuwongse et al., 1991, "An Object-Oriented Approach to Model Management". Inspec Abstract No. C94204-6110J-017, "Choices, Frameworks and Refinement", R. H. Campbell et al., 1991. Inspec Abstract No. 4090970, from P. Kougiouris, 1991, "Device Management Framework for an Object-Oriented Operating System". Inspec Abstract No. 4077440, from A. Mahler, 1991, "Organizing Tools in a Uniform Environment Framework". Inspec Abstract No. 4067033, from Shaw et al., 1990, "Experiences with the ET++ Application Framework". Inspec Abstract No. 4060084, from Muller et al., 1990, "ODICE: Object-Oriented Hardware Description in CAD Environment". Inspec Abstract No. 4050569, from Di Giovanni et al., 1990, "HOOD Nets". Inspec Abstract No. C91072815, from Holtkamp et al, 1990, "DEMOM-A Description Based Media Object Data Model". Inspec Abstract No. C91072016, from a Lane, 1991, "/DOS/C++ -Application Frameworks". Inspec Abstract No. C91072574, from Hemery et al., "An Analysis of Communication and Multiprogramming in the Helios Operating System". Inspec Abstract No. C91064787, from Madany et al., 1989, "A Class Hierarchy for Building Stream-Oriented File Systems". Inspec Abstract No. C91064580, from Gamma et al., 1989, "Integration of a Programming Environment into ET++-A Case Study". Inspec Abstract No. C91058815, from Menga et al., 1990, "G++: An Environment for Object Oriented Analysis and Prototyping". Inspec Abstract No. B91052096, from Cusack et al., 1990, "Object-Oriented Specification in LOTOS and Z, or My Cat Really is Object Oriented|". Inspec Abstract No. C91053475, from Queinnec et al., 1988, "An Open Ended Data Representation Model for EU-LISP". Inspec Abstract No. C91053151, from E. Cusack, 1991, "Refinement, Conformance and Inheritance". Inspec Abstract No. C91042802, from T. Yokoyama, 1990, "An Object-Oriented and Constraint-Based Knowledge Representation System for Design Object Modeling". Inspec Abstract No. C91041980, from Choi et al., 1991, "Graph Interpretation of Methods: A Unifying Framework for Polymorphism in Object-Oriented Programming". Inspec Abstract No. C91042655, from Q. Li, 1991, "Extending Semantic Object Model: Towards More Unified View of Information Objects". Inspec Abstract No. C91024852, from Pierra et al., 1990, "An Object Oriented Approach to Ensure Portability of CAD Standard Parts Libraries". Inspec Abstract No. C91010951, from T. Helton, 1990, "Level5 Object". Inspec Abstract No. B90075006, from Gossain et al., 1989, "Designing a Class Hierarchy for Domain Representation and Reusability". Inspec Abstract No. C91003997, from J. Muys-Vasovic, 1989, "MacApp: An Object-Oriented Application Framework". Inspec Abstract No. C91004708, from Bertino et al., 1990, "Optimization of Queries Using Nested Indices". Inspec Abstract No. C90052277, from I. Tervonen, 1990, "Object-Oriented Development as a Multiview Software Construction Methodology". Inspec Abstract No. C90052627, from Schrefl et al., 1988, "A Knowledge-Based Approach to Overcome Structural Differences in Object Oriented Database Integration". Inspec Abstract No. C90047457, from Yokoyama et al., 1990, "A Constraint-Based and Object-Oriented Knowledge Representation". Inspec Abstract No. C90034818, from Q. Chen, 1988, "Extending the Object-Oriented Paradigm for Supporting Complex Objects". Inspec Abstract No. C90030609, from Forde et al., 1990, "Object-Oriented Finite Element Analysis". Inspec Abstract No. C90007733, from Weinand et al., 1989, "Design and Implementation of ET++, A Seamless Object-Oriented Application Framework". Inspec Abstract No. C89062837, from Pasquier-Boltuck et al., 1988, "Prototyping an Interactive Electronic Book System Using an Object-Oriented Approach". Inspec Abstract No. C89056727, from Campbell et al., 1989, "Principles of Object-Oriented Operating System Design". Inspec Abstract No. C89056859, from Hull et al., 1989, "On Accessing Object-Oriented Databases: Expressive Power, Complexity, and Restrictions". Inspec Abstract No. C89049257, from Madany et al., 1989, "Class Hierarchy for Building Stream-Oriented File Systems". Inspec Abstract No. C89039001, from Brophy et al., 1989, "A Framework for Multiple, Concurrent Graphical Representation". Inspec Abstract No. C89033226, from Corradi et al., 1988, "PO: An Object Model to Epxress Parallelism". Inspec Abstract No. C89014870, from R. King, 1988, "Semantic and Object-Oriented Database Support for Software Environments". Inspec Abstract No. 89003142, from Tenma et al., 1986, "A System for Generating Language-Oriented Editors". Inspec Abstract No. C88013915, from Woelk et al., 1987, "Multimedia Information Management in an Object-Oriented Database System". Inspec Abstract No. C88007447, from P. Allen, 1987, "A Framework for Implementing Multisensor Robotic Tasks". Inspec Abstract No. C87007043, from Whitted et al., 1986, "Exploiting Classes in Modeling and Display Software". Inspec Abstract No. C86039588, from K. Fukunaga., 1985; "PROMPTER: A Knowledge Based Support Tool for Code Understanding". Inspec Abstract No. C86024804, from Greenspan et al., 1986, "A Requirements Modeling Language and Its Logic". Inspec Abstract No. C84005713, from Meyer et al., 1983, "Towards a Two-Dimensional Programming Environment". Inspec Abstract No. C81005505, from Mylopoulos et al., 1980, "Some Features of the TAXIS Data Model".
Patent number: 5937189
Inventors: Michael John Branson (Rochester, MN), William Robert Taylor (Rochester, MN)
Application Number: 8/748,144
Current U.S. Class: 395/701; 395/702