I have been selling software applications for a decade now and it still amazes me how organizations go about acquiring new software systems. Many companies have no process in place for making large software acquisitions and many companies simply purchase based on past experience and minimal research. There is a saying in the industry that no one has ever been fired for purchasing "Big Blue". Requirements Management tools/systems are no different.

Can anyone tell me the best way to rate requirements along with a numbering system to it; for e.g Must have or Required , Not Required, Nice-to-have etc.

Many data professionals, particularly people focused on logical data modeling or meta-data management, will often adhere to the "one truth" philosophy. This philosophy says that it is desirable to have a single definition for a data element or business term, that there should be a common, shared definition for your master reference data and perhaps even your major business entities. The