As we have discuss in previous article the basics of AX Dev best practices
Today we are going to discuss the detail of The first step is conceptualize the application:
You must understand the problem you want to solve. One of the basic concepts when developing applications in Microsoft Dynamics AX is reuse. You may reuse functionality when you make a new application, or when you modify or extend an existing application. If you will add new functionality to an existing application, know the individual parts of the existing application. If you do not understand the existing application pattern, you may create functionality that was not necessary, or that already exists in the application.
Data model: Data modeling is a process used to analyze and define data requirements for the following purposes:
- Designing databases that support business requirements
- Integrating information systems
The following sections describe the three types of data models.
Conceptual object model: A conceptual object model is a technology-agnostic definition of the data and relationships.
Logical data model: A logical data model is a representation of the business data. It is organized in terms of entities and relationships. The logical data model is generally created during the detailed specification phase. The purpose of the logical data model is to represent the relevant business requirements relationally in Boyce-Cod normal form. The logical data model elaborates the conceptual object model structure to a level of detail where all required relation types (entity types and relationship types), relationships, and attribute types are represented.
Physical data model: A physical data model defines the details of the data design. It includes elements such as tables and indexes. The physical data model considers a specific database management system (DBMS) and is generally created in conjunction with the Development Design document. The physical data model is derived from the logical data model. You can de-normalize the model to improve performance. The de-normalized physical data model must implement the business requirements represented in the logical data model .
Further we will discuss Database objects in detail for example tables, Table design, Temporary tables, In memory and TempDB.