All of this information is meta data. The first question in this article mentioned the use of meta data beyond the IT tools themselves. In this case, the modeling meta data remains in the CASE tool where no one other than the modelers can view it. The business names and definitions that originate as meta data in the CASE tool should be shared with knowledge workers and application developers that are interested in how the data of the organization is defined and related. Forcing compliance to IT standards is typically an ongoing battle.
Some companies are successful, some are less than successful.
Often the success or failure of following standards is a result of the corporation's environment - use of packages, merging companies and IT functions, centralization of IT service functions, etc. Other times, the success or failure is based on the company's ability or willingness to force individuals to comply to the rules of IT development. Most IT standards are based on meta data. Component naming, storage location and component interaction are a few examples of meta data that can play a significant role in IT standards. It can also be used to identify how many versions of each component exist and where they exist.