Object-oriented modeling: Difference between revisions

Revision as of 00:39, 12 June 2006

Revision as of 23:59, 8 August 2006

Line 4:

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

As an example, in a Payroll System, a Company is an ObjectOLOLbject. 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 This is a sentence in the midlle of a sentence. 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 [[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 [[Database schema]].