This, in turn, enables the development of Java stored procedures, compiled and optimized prior to runtime, that can significantly enhance data access performance and also are portable across the various tiers of a distributed e-commerce application. Given this progression of events, it's not surprising that object-oriented concepts have been extrapolated backward in the software lifecycle into the conceptualization perspective. The independence of data and function, one of the fundamental principles of data-oriented, relational thinking, is antithetical to object orientation. From an OO viewpoint, there is no concept of data existence, independent of function, within any IT architectural perspective from conceptualization through realization. The notion of a class is the fundamental building block of object orientation.
Persistence forms the infrastructure of a business organization's information assets.
Persistent data exists independent from processing. Whereas one of the primary objectives of object orientation is reuse of software, data is, without a doubt, one of the most highly-reusable assets of a business organization. Businesses ignore the benefits of enhanced data reusability at their peril. Many other established analysis and development approaches do indeed consider the data resource of a business independent of the functions to which it interfaces. A number of side effects result from marginalizing the independent existence of the data resource, mostly to the detriment of precision of specifications.