Object oriented based methodology for modeling business functionality for enabling implementation in a web based environment

• US 7,533,366 B2
• Filed: 09/27/2004
• Issued: 05/12/2009
• Est. Priority Date: 08/03/2000
• Status: Expired due to Term

• Current Assignee: Ginegar LLC (K.Mizra LLC)
• Original Assignee: International Business Machines Corporation
• Inventors: Uppal, Rajiv K., Parikh, Devang I., Gupta, Arun K.
• Primary Examiner(s): Chavis; John
• Application Number:
  US10/951,262
• Publication Number:
  US 20050060684A1
• Time in Patent Office: 1,688 Days
• Field of Search: 717/105
• US Class Current: 717/105
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A computer method and apparatus defining Business Classes for modeling business activities comprising the steps of representing business activities as the interaction between one or more Business Classes, and entering into a computer and storing in an electronic format the Business Classes and the relationships existing between the Business Classes.

Claims

1. A computer method of modeling a business activity, comprising the steps of:

(a) defining one or more business classes including storing in a digital electronic format said one or more business classes as well as the relationships existing between said one or more business classes;

(b) representing a subject business activity as an interaction between one or more business classes; and

(c) tying business rules having states or tying methods which function as rules required to carry out a business rule to a next logical state, said tying of rules or methods being to individual instances of the business classes such that two instances of a same class can respond differently to a given business activity.

2. A method as claimed in claim 1 wherein the step of defining includes the steps of:

(a) defining one or more business states indicative of the status of a business class; and

(b) defining one or more business methods to logically define the steps required to move a business class between one or more business states.

3. A method as claimed in claim 1 further comprising the step of auto deleting a business class.

4. A method as claimed in claim 3 further comprising auto deallocating memory space storing business class data.

5. A method as claimed in claim 1 wherein the business classes form templates of run-time business objects, each business object being an instance of a respective business class.