Rich programming rule

Rich Programming Rule -------------------------------------------------
Development in MorphX
Purpose
The document is to create programming rule for AX ERP customization program which include naming rule and function control rule. As we have lots of customizations in ERP system and there are several development units, even in one development unit, there is more than one developer, we need to create the naming rule to make the customization much easier to read and understand. Also, it helps us to separate the standard functions and customization functions. And for each site, it has difference function requests; we have to make good function control for difference function request in each site.

Development Team
As now on, we have serveral development units, we define the name of these teams. Development Team | Name | Description | Tectura-China | TEC | | Tectura-Indian | TEI | | Tectura-Vietnam | TEV | | Columbus IT | CIT | | 1. Systems Advisers Group | SAG | | ERP Competency Center | RPS | ERP CC support all of the site | Rich Graviss India | RGI | Currently, it is just for India |

Customization Type & Process
Project
* Description:
Before we prepare Enterprise Design Document (EDD), first we need to record the function change in our development list and get a number, the EDD will use this number as EDD number. When developers receive EDD, developers will use this number to create the project in AOT. * Process: * After investigate and survey, application consultant will prepare BPA documents, which describe current situation and future requirements detailedly. * Functional Requirement document (FRD) confirms the customization list, according to BPA, with project team, which includes Priority, Development team, estimation time, when this change is in a project. * Application consultant will prepare EDD according to FRD and ask technical leader to give an EDD number and record in the