basic object modeling

Wow, that's a fairly broad question but I hope this will help you.

Object modeling should ultimately reflect the actual business model. You would want to 'map' each object that a business uses, makes, etc. You could create an AppUser object that would represent the user of your application. This user would need 'properties' such as: FirstName, LastName, UniqueID, Pay, Department, Title, etc. You would also want to create 'methods' for each AppUser such as: ClockIn, ClockOut, Update, Delete, etc. These properties and methods act as a gateway to your data (this, in combination with the user interface, is considered n-tier application development).

Once you have an object you may choose to group related objects in collections. Forexample, the company that you are modeling may have departments and you want to model this. You could set up a department object with a property of 'Employees' where employees is a collection of the AppUser object we spoke of earlier. You could then loop through the Employees collection to view the employees that were in say the accounting department.

There is so much more to learn about object modeling but I hope this gets your intellectual juices flowing.

Also, I should remind you that you will want a fully object oriented programming (OOP) language like C++, C#, or VB.NET, etc. so you can enjoy long, long nights of inheritence, overloading, and encapsulating!

Check out . . .
http://www.microsoft.com and search for 'OOP'.

Good Luck!

Let me give examples

Purchase Order is the Object (or Class)
Attributes are - supplier, item, qty, rate etc...
Operations include - Create PO, Modify PO, Forward PO to supplier

Every time a PO is created you essentially construct the object from the class above.

Is it clear now?