Create product. When a project involves creating a new product from scratch, the Dimensions CM administrator typically uses the Administration Console to create the new product.
For information on creating products and defining roles, see the Process Configuration Guide.
Create product item libraries. Next, the administrator creates the product item libraries, which are the folder structures in which the item files will be located.
Create item types and associated lifecycles. The administrator uses the Administration Console to define the types of item that are used within the product and the lifecycle stages that they will follow when they are tested and approved.
For information on object types and lifecycles, see the Process Configuration Guide.
Create project(s) or stream(s). The administrator then creates the projects/streams for use by project personnel. Whether you use projects or streams depends on your method of working. See Working with Streams for details of streams and how they differ from projects
You could have one project/stream that everyone uses, or you may have different projects/streams for people who have different roles or who work on different parts of the product.
For more information, see Creating a New Project or Creating a Stream.
If files already exist, upload them. You'll upload any existing files into the Dimensions CM database by using the Deliver command. Additional files can be created during development.
For more information, see Delivering Files to a Project.
Assign roles/privileges. The administrator uses the Administration Console to assign project personnel to groups, privileges, and/or roles. Privileges determine which functions people can perform on different classes of object or administrative areas. You can assign privileges to individual users, groups, or roles. Roles and their associated permissions determine what actions people can perform on different object types at different points in the development process and for different design parts.
For information on assigning privileges and roles, see the Process Configuration Guide.
Define request types and their associated lifecycles. The administrator uses the Administration Console to set up the request types that are used for tracking changes and reporting defects, and defines the lifecycles that they are to follow.
For information on object types and lifecycles, see the Process Configuration Guide.
Define work areas, deployment areas, and library cache areas, and assign them to projects/streams and users. The administrator uses the Administration Console to set up work areas that are used by developers for the items files they are working on. The administrator also sets up deployment areas to contain files at specific development stages for a project, and library cache areas to increase the efficiency when users access item files from remote servers.
For information on area definitions, see the Process Configuration Guide.
Set up baseline and release templates. The administrator uses the Administration Console to set up the rules for selecting item revisions to be included in baselines and releases. Baselines are used to capture versions of items at project milestones and to generate releases of the product.
For information on baseline and release templates, see the Process Configuration Guide.
The project is ready for development activities to begin.