Project settings

The ALM solution comes with a set of system-wide settings that provide the power to modify the solution to fit your enterprise without impacting the underlying schema.

Administrators can define categories of projects and label types that can help set policies for standardization, organization, and governance of projects. The Label records allow you to define a set of names which appear in the user interface, most often in the form of drop-down lists on records. Some examples of Label types are Work Type, Role, Resolution Code, and Category Type. These settings allow for reuse and consistent classification across multiple projects, and can adapt to the enterprise.

Over time the number of projects produced by an organization can be large. Project uniqueness and classifying features may be needed to identify projects. Additionally, large projects may be subdivided into smaller projects but share the same release version. Category and Release settings can be used to define project uniqueness.

You can define a set of Categories and Release Labels to help classify projects. The values you create can be used for any new project. Managers or team leads can use a Category to classify a project, and can use a Release to identify the version of the software the project will deliver. For example:
  1. An ALMAdmin user:
    1. Creates ALM Categories. You can create a hierarchy of categories to classify projects. Projects are identified by a Category, which helps to classify the product, feature or component that the project delivers. In some organizations a need arises to create more than one category tree. For example, a single organization may identify projects using some combination of product and service. Category Types are used to identify the classification scheme. For example, using the example above, two CategoryType records are created, one for product and one for service. Once your category types are defined, you create categories for that type. Categories can be hierarchical. First create CategoryType. Then create the categories for that type.
    2. Creates Release Labels. A Release which identifies the version of the software. Many organizations standardize on a nomenclature for release labels. The ALM solution supports this need by providing the Release Label record.
  2. A manager or team lead:
    1. Chooses a Category. When creating a project record, the available categories appear on a drop-down list. Choose a category that classifies this project.
    2. Chooses a Release. When creating the project, the available Release labels appear on a drop-down list.
For example, if you start with the out-of-the-box ALM schema that is included and you create a Project named myALM, set the Category to ALM and set the Release to 7.1.0.0, these three identifiers define the uniqueness of the project. A later project could use the same category name except changing the Release value to 7.1.1.0. Project names cannot be reused.

These topics describe system-wide settings, categories, security policies , and role labels.