Content deleted Content added
Stevertigo (talk | contribs) mNo edit summary |
Stevertigo (talk | contribs) No edit summary |
||
Line 2:
This paradigm assists the programmer to address the complexity of a [[problem ___domain]] by considering it as a set of related Objects. Modeling task then is specifying, for a specific context, those Objects (or the Class the Objects belongs to), there 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 [[Schema]].
Line 9 ⟶ 8:
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]].
{{comsci-stub}}
| |||