Explore chapters and articles related to this topic
Object-Oriented Programming
Published in Paul W. Ross, The Handbook of Software for Engineers and Scientists, 2018
OMT is an approach to object-oriented analysis and design that was developed at the General Electric Research and Development Center in Schenectady, and promoted in the text, Object-Oriented Modeling and Design, by Rumbaugh et al. (1991). It is supported by a CASE product called OMTool that is available from the Martin-Marietta Corp. (1992). OMT provides the analyst with a formalism and notation for constructing models, but it provides no additional formal support to the designer. The distinction between the analysis phase and the design phase is blurred, with the designer composing and refining previous models. The Fusion Method of Coleman et al. (1994) provides additional design models that will be briefly examined in the next section.
Assessing Students’ Object-Oriented Programming Skills with Java: The “Department-Employee” Project
Published in Journal of Computer Information Systems, 2020
Xihui Zhang, John D. Crabtree, Mark G. Terwilliger, Tyler T. Redman
OOP has always been difficult to define, but the concept of the “object” is certainly central to any definition.12,13 The focus on objects naturally led to object-oriented approaches to analysis and design. Many different approaches to problem decomposition in terms of objects and classes led to the “method wars” of the 1980s and 1990s. Many thought-leaders produced methodologies, along with their associated object notations and/or tools. Three authors who gained preeminence in the early 1990s published the following definitions: Grady Booch (Rational Rose): OOP is a method of implementation in which programs are organized as cooperative collections of objects, each of which represents an instance of some class, and whose classes are all members of a hierarchy of classes united via inheritance relationships14 (p. 36).James Rumbaugh (Object Modeling Technique): Superficially the term “object-oriented” means that we organize software as a collection of discrete objects that incorporate both data structure and behavior. This is in contrast to conventional programming in which data structure and behavior are only loosely connected. There is some dispute about exactly what characteristics are required by an object-oriented approach, but they generally include four aspects: identity, classification, polymorphism, and inheritance15 (p. 1).Ivar Jacobson (Objectory): In his chapter titled “What is object-orientation?”, Ivar Jacobson states that his aim is “to introduce the actual idea [of object-oriented technology], not to give strict and precise definitions”16 (p. 42). It is worth noting that in the 1990s Jacobson joined Booch and Rumbaugh in the collaboration that gave us the Unified Modeling Language (UML) and the Unified Process.