Content deleted Content added
m Bot: Migrating 1 interwiki links, now provided by Wikidata on d:Q11292308 |
No edit summary |
||
Line 5:
The object-oriented paradigm assists the programmer to address the complexity of a [[problem ___domain]] by considering the problem not as a set of functions that can be performed but primarily as a set of related, interacting Objects. The modeling task then is specifying, for a specific context, those Objects (or the Class the Objects belongs to), their respective 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 [[Logical schema|schema]].
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.dd
The Model description or Schema may grow in complexity to require a Notation. Many notations have been proposed, based on different paradigms, diverged, and converged in a more popular one known as [[Unified Modeling Language|UML]].
Line 17:
[[Category:Software design]]
d
{{Comp-sci-stub}}
| |||