Can anyone offer examples of a class diagram that describes the simple CRUD of a typical "maintenance" program. I'm probably approaching this the wrong way, but I've got to start somewhere - I am documenting the current functionality in a fairly large legacy Purchasing system.
For example, "file maintenance" program that allows full CRUD of Vendor/Item relationships. The key objects as I see them are:
Vendor/Item - Ties a vendor to an item and allows the system to keep track of the vendor's product/item ID and stores two categories of costing classes for the link.
Item - Item must exist to have a valid Vendor/Item.
Vendor - Again, must exist to have a valid Vendor/Item. This also provides a couple of default values for Vendor/Item attributes.
Inventory Control - Determines whether or not the delete of a Vendor/Item should also look for an "Interchange" and delete it as well.
Interchange - Can be associated with a Vendor/Item and may need to be deleted (see above).
a couple of categories of cost class objects - If the Vendor/Item has cost methods assigned they have to point to valid cost classes.
From this list I created a class diagram with one class per object and filled in some relevant attributes. But, I'm not sure what (if any!) operations need to be given to these objects. I'm also not sure how to describe some of the other details like what happens when deleting a Vendor/Item. Right now the classes look like simple data containers...

I've been doing a ton of reading both on the web and in a couple of UML books. I have a feeling that I'm approaching this the wrong way, but again, I'm new to modelling and need to start somewhere.
Any comments or help would be greatly appreciated.
Jon