Object Orientation Fallacies

摘要

At the beginning, no formal strategy was followed and so some researchers proposed a standard way for developing a system, usually called a methodology. In recent years, many expectations were created because of the increasing adoption of methodologies based on the Object Orientation (OO) paradigm. It seemed like a silver bullet that would solve all problems from application development. But which of the benefits stated by its defenders were true? In the present paper an analysis of this paradigm will be presented, based on our experience with real world applications in Brazil. What are the greatest obstacles faced to adopt an OO methodology as for example - Unified Process? Another point studied will be Functions versus Methods, what are the advantages and disadvantages? Also, are all other models from Unified Modeling used in practice or people just go ahead without them? Finally, a discussion about where should reside the business rules, in a persistence layer, inside a database, or in both places? And what about OO databases, are they really used? Our objective is to provoke the audience to think about the benefits and costs of adopting a new technology and discarding the previous one.