Home
Managing change and releases
Learn how to manage change and release in the product.
Using HCL Compass ALM
The application lifecycle management (ALM) packages and ALM schema provide out-of-the-box solutions for ensuring ALM best practices in your new or existing HCL Compass change management system.
Overview
An ALM schema provides the capabilities for security, governance, traceability, and workflow management.
Roles in an ALM process
The ALM packages provide support for a role-based change management (CM) system design through a collection of record types that apply to role-based development.
User roles
Users of a HCL Compass ALM user database work with specific types of tasks and activities based on roles.
Dev Lead
The Developer (Dev) Lead role can be filled by a development, testing, or other type of team lead.

Managing change and releases
Learn how to manage change and release in the product.
- Using your HCL Compass Web client
  HCL Compass Web is a browser-based interface to HCL Compass that runs on Windows, the UNIX system, and Linux. You can track defects and change requests in HCL Compass Web through this interface. When a session times out, you can re-authenticate and continue where you left off because the state of the user interface is retained.
- Using the HCL Compass Client
  Use the HCL Compass Client to submit, modify, and track change requests and to analyze project progress.
- Using HCL Compass for Windows® client
  You can use HCL Compass to perform daily activities after the schema developer and administrator define and set up the schema, schema repository, and user database.
- Using HCL Compass ALM
  The application lifecycle management (ALM) packages and ALM schema provide out-of-the-box solutions for ensuring ALM best practices in your new or existing HCL Compass change management system.
  - Overview
    An ALM schema provides the capabilities for security, governance, traceability, and workflow management.
    - HCL Compass ALM record types
      The set of records in the ALMProject package can provide the project context and work process in which work occurs.
    - Roles in an ALM process
      The ALM packages provide support for a role-based change management (CM) system design through a collection of record types that apply to role-based development.
      - Approved actions
        Each user role has a defined set of approved actions.
      - User roles
        Users of a HCL Compass ALM user database work with specific types of tasks and activities based on roles.
        Submitter
        Users of any role can submit Requests.
        Triage
        The Triage role can be filled by engineering, product, project, test, and documentation managers.
        Dev Lead
        The Developer (Dev) Lead role can be filled by a development, testing, or other type of team lead.
        Developer
        The Developer role can be filled by a developer, tester, or information developer.
        Release engineer
        The release engineer role creates baselines and builds.
        Tester
        The Tester role works on and completes test Activities.
    - 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.
  - Getting started for administrators
    Administrators can define roles and processes for each project, as well as security policies to allow access to projects.
  - Working with projects
    All work in the ALM schema is organized by a Project. The Project can help provide the context, access control, and security model for your work.
  - Managing work
    The work records contained in the ALMWork package provide a way of keeping track of the requests and tasks that must be addressed.
  - Tracking work and builds
    These topics describe how to create baseline and build records, and how to track and complete activities, tasks, and requests.
  - Sample data
    A sample database is provided to help get you started with the new schema.
  - Mandatory fields for ALM record types

Dev Lead

The Developer (Dev) Lead role can be filled by a development, testing, or other type of team lead.

The Dev Lead role is responsible for leading the development team, reviewing tasks and assigning development activities.

In an ALM work process, the Dev Lead role:

Reviews Tasks
Determines whether to address the Request or close the Task
Creates Activities for Developer (or Tester or other roles such as Doc Assessor) role users.
Reviews status of Activities

When a Dev Lead user chooses the CreateActivities utility action on a Task, a set of ALMActivity records is created according the project's work configuration policies.

Possible approved actions for the Dev Lead role include the following actions:

ALMRequest actions: Accept, CreateTask, Delete, DuplicateComplete, Import, MarkAsDuplicate, Modify, Open, QuestionOrComment, ReOpen, Reject_Request, Reject_Solution, Withdraw, WorksAsDesigned
ALMTask actions: Activate, Complete, CreateActivity, Delete, Import, Modify, Open, QuestionOrComment, ReOpen
ALMActivity actions: Activate, Complete, Import, Modify, Open, QuestionOrComment, ReOpen, ReadyToWaiting, Submit, WorkOn
ALMBaseline actions: Delete, Import, Modify, Submit
BTBuild actions: Complete, Delete, Failure, Import, Modify, ReSubmit, Retire, Submit