p06
It is a universal standard in programming, trying to identify the functionality of the variables, functions, applications, etc.
This identification implies an appointment seeking maximum simplicity and characterization of components.
The aim is to fight for a maintainable system that involves the least effort to learn the functionalities implemented.
Therefore, in addition to betting on a document management, we must also consider the appointment of components suitable as another important point to keep the architecture appropriately.
For example, one should view with only the name of it to know:
- What kind of view is, focusing on the guy format it.
- What content to display
- If the view are receiving and how many parameters would
- If the view are going to belong to a data type or is a general view
All this information should give it to us the name of the hearing.
Why is it important to complete coding systems?
Because our goal is to reuse the same view and to be able to diagnose the functionality we are valid or not without having to reach the moment of release.
Without doubt, this and many other architectural parameters are beginning to see its meaning when the number of views and number of sites increases dramatically.
There is nothing new, these techniques are contrasted and methodologies of systems, good programming practices in systematic approaches such as CMMI and ITIL today, are common features of any architecture.
