Abstract
Most software developers have a strong tendency to define object-oriented concepts in terms of the specific object-oriented programming languages (OOPLs) they know. Unfortunately, these definitions also soffer the same limitations of the OOPLs. This, in turn, has tended to limit the power of object-oriented requirements analysis and logical design, which should be language independent. Many examples of this phenomenon exist, including lack of support for dynamic and multiple classification, equating objects and classes with encapsulations of attributes and operations (which is how many OOPLs implement then) rather than as software models of application domain entities, and defining a message as a dynamically bound call to a corresponding operation (a.k.a., method) of an object or class. This paper addresses this latter, arbitrary forced, one-to-one mapping of messages to operations.
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call