Object-oriented modeling: Difference between revisions

Content deleted Content added
m typo
No edit summary
Line 1:
{{Unreferenced stub|auto=yes|date=December 2009}}
'''Object-Orientedoriented Modelingmodeling (OOM)''', oralso OOM, (Object Oriented Programmingcalled '''object-oriented programming (OOP)''' is a modeling paradigm mainly used in [[computer programming]]. Prior to the rise of OOM, the dominant paradigm was [[procedural programming]], which emphasized the use of discrete reusable code blocks that could stand on their own, take variables, perform a function on them, and return values.
 
The Objectobject-Orientedoriented 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 [[Objectobject-oriented analysis and design]] and [[Objectobject-oriented programming]]. The description of these Objectsobjects is a [[Logical schema|Schemaschema]].
 
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.