Object-oriented modeling: Difference between revisions

Revision as of 12:07, 6 March 2006

Revision as of 12:23, 6 March 2006

Line 1:

Object-Oriented Modeling, or OOM, is a modeling paradigm mainly used in computer programming.

This paradigm assists the programmer to addresseaddress the complexity of a [[problem ___domain]] by considering it as a set of related Objects. WhereasModeling antask Objectthen is specifying, for a specific context, those Objects (or the Class the ObjectObjects belongs to), hasthere itsrespective set of Properties and Methods, shared by all Objects members of the Class. For more discussion, see [[Object-oriented analysis and design]] and [[Object-oriented]] programming.

The description of these Objects is a [[Schema]].

As an example, in a Payroll System, a Company is an Object. An Employee is another Object. Employment is a Relationship or Association. An Employee Class (or Object for simplicity) has Attributes like Name, Birthdate, etc. The Association itself may be considered as an Object, having Attributes, or Qualifiers like Position, etc. An Employee Method may be Pomote, Raise, etc.

The Model description or [[Schema]] may grow in complexity to require a Notation. Many notations has been proposed, based on different paradigms, diverged, and converged in a more popular one known as [[Object Modeling Language|OML]].