Development with SCM for project VRCs and applications

VRC structure

If SCM is enabled for project VRCs and applications, LN Studio generates two VRCs on the LN server for each activity: an Activity VRC and a Private VRC. In these VRCs, a software engineer can modify software components without disturbing other software engineers.

This diagram shows an example:

These VRCs are used:

• The 'old' VRC contains software components developed in a previous project.
• The Project VRC contains all finished software components for the project. From here, deliveries to customers are performed, once the project is completed.

  Note: The project VRC is the Export VRC linked to the Base VRC of the Application to which the project belongs. Therefore, the project VRC contains finished software components for other projects defined for the same application.

• The SCM Project VRC is derived from the project VRC. It is used to store checked out software components.
• The Activity VRC contains checked in software components for an activity. The activity VRC is generated automatically when you open the activity for the first time. The components in this VRC are only accessible for the software engineer to which the activity is assigned. However, other software engineers can access these components if they put this activity in the activity context of their own activity.

  See Activity context.

• The Private VRC is derived from the activity VRC. It contains the checked out components the software engineer is working on. The components in this VRC are only accessible by the software engineer to which the activity is assigned. The private VRC is generated automatically when you open the activity for the first time.