Projects and project groupings

A project is a user-defined group of related files, directories, and other projects (called subprojects). A project normally represents a logical grouping of software, such as a library or an executable file, and it contains the directory structure of the files. For example, the software that implements an editor application might be stored in a project named editor.

Projects are identified by version like any other object. Different versions of the same project can contain different versions of the member objects, and even different members. For example, different versions of the editor project might represent the first release, editor/1.0, and follow-up releases, editor/1.1,
editor/1.2, and editor/2.0. The editor project for release editor/2.0 can contain new objects that did not exist in version 1.0. The project can also contain newer versions of many of the same objects. There can also be files that were in version 1.0 that are not part of the version 2.0 project.

A single object version can be a member of multiple projects. Even though the same object version appears in different projects, the object version exists only once in the Rational Synergy database.

A project can contain other projects. A project contained within another project is called a subproject. You can organize your software by grouping it into different projects. For example, you can set up a project for each executable file, and include them all as subprojects under a project that represents the entire application.

For any given project, several different versions can exist:

A project grouping groups working and build management projects by release and purpose. It is created and maintained automatically to provide a convenient reference point for a set of projects. For example, My 1.0 Insulated Development Projects groups all projects of a developer for the 1.0 release for insulated development. A project grouping also contains the tasks and baseline used when a project is updated. This process keeps the members selected to be in a project consistent for all projects in the grouping.

Think of a project grouping as a container into which you add different ingredients (properties), such as tasks, baseline, release, and project purpose, to create a group of projects with the right mix of members (files). Once you have created this project grouping, you can easily add, remove, or change the properties. You can also specify that you do not want tasks to be updated during a project update, refresh the baseline and tasks in the project grouping to get the latest set, and move a project from one project grouping to another. This process enables you to keep your projects grouped securely, yet gives you the flexibility to change things when you need to.


Feedback