There are two reasons for doing this at this time.

harunur01999

This is where you must make a difference. It is important to define all the application tables and their relationships before beginning interface development. Ideally, you should also have all the fields and indexes defined, but it is logical that this information will vary throughout the development. What we should try to avoid is having to change tables or relationships, for this reason before starting development we must have all the tables and their relationships fully defined.


Phase Data import Many, many years ago when I computerized a company that did not have software, the data had to be recorded manually, what times those were! : Today just the opposite happens. One of the big iss Senegal WhatsApp Number ues to resolve is the migration of information from the current system: application, spreadsheets... to the database of the new application. ‍ My recommendation at this point is that as an analystprogrammer you prioritize importing the data before starting to create the interface .







First of all, because when you develop the interface you will be able to see it with the real data, this helps to detect errors, also when the progress is shown to the client, they will be able to better understand its operation and can also detect errors in a simple way, something that they could not do. with information that is not familiar to you. Secondly, it is important to have a very refined and automated import of the data since when the critical moments of putting the application into production arrive, it will be necessary to do the data migration again, and if we have already resolved that we can address it with more peace of mind.