Object-oriented modeling: Difference between revisions

Revision as of 19:30, 20 May 2008

Revision as of 19:38, 20 May 2008

Line 5:

As an example, in a model of 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 Promote, Raise, etc.

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

An informal description or a Schema notation is translated by the programmer or a [[CASE|Computer-Aided Software Engineering]] tool in the case of Schema notation (created using a Module specific to the CASE tool application) into a specific programming language that supports [[Object-Oriented programming|Object-Oriented Programming]] (or a Class Type), a [[Declarative Language]] or into a [[Logical schema|Database schema]].