Developing software

HCL VersionVault provides a flexible set of tools that your organization uses to implement its development and change management policies.

HCL VersionVault is a comprehensive configuration management (CM) system that manages multiple variants of evolving software systems and tracks changes. Using HCL VersionVault, your organization can maintain a complete version history of all software development elements, including code, requirements, models, scripts, test assets, and directory structures. HCL VersionVault enables your team to perform audited system builds, enforce site-specific development policies, offer multiple developer workspaces, and provide advanced support for parallel development. HCL VersionVault includes Unified Change Management (UCM), an optional, out-of-the-box process for organizing software development teams and their work products. UCM structures the efforts of your software development team into a defined, repeatable process.

To use these tools for developing software, you need to understand the following concepts:
  • Elements and versions
  • Views
  • VOBs
  • Parallel development

Your project manager determines which environment your team works in: base VersionVault or UCM. In addition to the general HCL VersionVault concepts, you need to understand some environment-specific concepts in order to use the tools effectively.

The following are basic concepts that you need to understand if you are working in a base VersionVault environment:
  • Config specs
  • Extended namespace
  • Branches
  • Merging files and directories
  • Mastership in HCL VersionVault MultiSite projects (if your project uses HCL VersionVault MultiSite)
The following are basic concepts that you need to understand if you are working in a UCM environment:
  • Projects
  • Activities
  • Streams
  • Baselines
  • Components, PVOBS