The term object-oriented is used so frequently today that it is difficult to decipher the true meaning. When we say that Backware is object-oriented, we mean your data is organized into units called objects which each belong to a class of objects. Each object has a set of properties or ways to describe it. The class that an object belongs to defines the set of properties that all its objects will use. For instance, suppose you have a golden delicious apple and a red delicious apple. Both of them are objects, and they are both of the class "Apple." The "Apple" class might define the set of properties for all apples to be "Name" and "Color." The specific values for the first apple would be "Golden Delicious" and "Yellow," while the property values for the second apple would be "Red Delicious" and "Red." So, there is one class with multiple objects that have the same set of descriptors but different values.
In object-oriented programming, objects will often contain methods which are ways to modify themselves or other objects. In our system, the objects themselves do not contain methods — only data. However, we provide a system called processes that allows a user to accomplish those same kinds of tasks with even greater flexibility. For instance, each process can have its own set of permissions, allowing only certain users to perform certain tasks. (For more details, please see The Processes Interface.) So, the important thing to recognize is that our processes exist outside of objects and manipulate them independently rather than being part of objects and changing them from the inside.
To view a demo of how our object-oriented approach works, you can click here, or you can go to our demo page.
Printer-friendly version PDF
+1.402.786.5111
Hours of Operation:
Monday-Friday
8:30 AM to 4:30 PM