Content deleted Content added
Connection (talk | contribs) mNo edit summary |
Connection (talk | contribs) mNo edit summary |
||
Line 7:
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 [[Unified Modeling Language|UML]].
An informal description or a Schema notation is translated by the programmer or a [[CASE|Computer-Aided Software Engineerint]] tool into a specific programming language that supports [[OOP|Object-Oriented Programming]] (or a Class Type), a [[Declarative Language]] or inot a Database.
| |||