Why use an ALM schema?

The ALM schema and packages provide a scalable change management workflow solution that captures the best practices of software development process design.

There is a significant performance benefit to using an ALM schema that relies on a set of record types, rather than relying on a more generic (and monolithic) record type. Each record type has a smaller set of operations associated with it, and less hook code. This set of record types offers fewer constraints to the maintainers of a system than broader and more monolithic record types.

In replicated environments a further advantage is that mastership issues are minimized, because roles-based record types tie record ownership and mastership to the change request resolution process so the correct owner and location always have mastership.

There are several advantages to using an ALM schema. For example, Administrators can identify and create a set of all supported product releases (or projects) that a customer can install such as:

• Full releases, fix packs, and other fixes or features.
• Bundles, offerings, collections, assemblies, common components, and shared common components.