|
home > JCare > library > object oriented programming | |
|
|
Online User Library
|
![]()
|
Object-Oriented Technology: When you want to upgrade your car's radio to a complete sound system, you don't throw away the car. You change the stereo deck. If that produces the sound you're looking for, you're done; if not, you may change the speakers. It's all done using small parts, or objects. Object-oriented technology is similar to the car stereo analogy. It's all about the system's substance. An object is a "black box" which receives and sends messages. The object actually contains code (which can be Java, C++, Smalltalk or another language that directs the process) and data (which organizes your business's information into pieces that the system can utilize). In traditional programming, the code and data have been kept separate. In object-oriented programming, the code and data are merged into a single thing, an object. This has far-reaching effects on how your company conducts business both today and in the future.
Using technology investments to support business directions
Building for the future Object-oriented programming lets your system change and grow with your business by isolating specific business functions. Each business function is a little "black box" that performs a specific task and passes the information to the next task. If you need to make a change to any function, only that little black box needs to change.
Building to scale If that system had been architected using object-oriented programming and today's technology, it would be able to use multiple servers, not only for the database and application, but for the application itself. Tasks to run a commission cycle, process orders, update lineage changes, and track prospects could all run at the same time, with the same data on multiple servers. When the system knows that a new server is available, it could auto-load the balance. The object-oriented technology makes full use of your network's structural design.
Building to perform
Building for change One of the primary rules of object-oriented programming is that the user of an object should never need to know the code inside the object, only its business function. With object-oriented technology, changes to the business model only affect the corresponding business function. Changing a small component only affects that component. Using an object-oriented approach, the system is only sending data and receiving information from the object. All of the functionality "inside the little black box" has already been thoroughly coded, tested, and implemented in the original release. Thus, the capability to develop new programs is increased, because the code in the object is guaranteed to work. If properly used, this method of software development improves the maintenance, reusability, and modifiability of software. A major change (for example, major interface changes) probably will still result in major changes to the software. What object-oriented technology tries to avoid is a little change in requirements that results in major software changes, or the ripple effect that can occur. Because those ripple effects can have a direct impact on your bottom line, object-oriented approaches may become a critical decision factor for your business's future technology directions.
Summary
| |||