Naming conventions for Development projects

Every single feature/functionality should be developed using Visual Studio and each development task should be linked with related task in Azure DevOps with further delivery to production.

Notes:
It is not necessary to create separate project for bug fixing during functional and acceptance testing – task is developing with single solution.

Naming of development project (and solution) in Visual Studio should follow this rule:

PRJAAAAA_BBBBBBBBB_UUU, where

PRJ - acronym for current model (see Model naming)

AAAAA - task id / work item Id, padded with zeros to the left of 5 characters

BBBBBBBBB - hort name of the developing feature in UpperCamelCase

UUU – developer’s nickname\alias in UPPERCASE

Examples:

CNL00153_PurchWorkflowParticipants_IZA
CNL02001_SalesInvoicePrintToExcel_SAO
VG00021_ImportPurchLineFromExcel_RDO