I would agree with Tom that when managing a very small application (less than 10 business objects) your method makes sense but what about a very large application with 70+ business objects that require these attributes and the rules associated with them?
For users of Aware that have been working in the product for several years and understand the need for this information (as we can tell from your expertise on this forum that you understand) this isn't necessary...other than the fact that an Aware user may have to view 80+ rules that are identical in an application that already has a ton of business rules...why clutter the space?. There are many new users who might not realize that they will require this information for whatever process they are attempting to create until they have already started using an application and then have a large number of records that exist without this necessary data.
I have also noticed in trying out various tools that are similar to Aware that most of them create these records (and other attributes) by default...I simply think that it is an intelligent way to add value to a system that's power is in the creation and connection of database objects with limited configurator involvement.
If a simple check box was added to the configuration tool that added these records by default when creating the object that would be great and it would also allow the configurator to deselect this automatic attribute addition process if the records were not necessary for the BO.
Less clutter, more consistency, less chance of missing this important step (in most cases), one less thing to worry about when creating a business object, an easier way to describe business rules that refer to these items (since a standard would be created)...etc.
