> Appendices A and B

< Migration for Web environment - Use of the Engine and Execution

Migration of Applications for Web Environment - A Practical Approach

Maintenance in the application and its reflection in the Interface

To illustrate the possible impact on the maintenance and upgrade of the application, it is assumed here that it is necessary to include a new attribute in the structure of customers, information from your e-mail, as shown in table 5.

Table 5 - Table system

Clients - maintenance

To implement this change in the demonstration application is basically through the layers of the system, informing the new requirements and to be doing this, have been given the opportunity to observe the degree of effort required for its effectiveness, particularly with regard to user interface.

Initially changes to the layer of access to data, as the figure 37, entering the attribute email, [line 6] in "app_register_client_data.sh module".

Figure 37 - Module app_register_client_data.sh - current

Below the layer concerning the business, which returns the value of editing, [line 9] and where the test include the new content of the e-mail, [line 15], in the module "app_register_client_business.sh" as the Figure 38 :

Figure 38 - Module "app_register_client_business.sh" - current

And finally, the call to the interface layer, in the script "app_register_client_sh" add up the references necessary for the release of e-mail, including the name, [line 18], size, [line 21], value, [line 25 ] and prompt, [line 29], as Figure 39:

Figure 39 - Module "app_register_client.sh" - current

Having made the changes, and then asked to implementation are already presented the results shown in Figures 40 and 41.

Figure 40 - Result of the maintenance character mode

Figure 41 - Result of the maintenance Web mode

Conclusion

The adoption of standards in the development of interfaces, such as the use of layers, methods based on common interface and procedures for automatic generation, bring significant results, not only in the development phase, but also in the maintenance, in addition to providing a facilitating factor in their migration to the Web environment Because its features, allows for simpler way the iterative process of development, a large volume of tests, the creation of a corporate culture in the operation of the interface, reducing training costs and allowing greater openness to adapt to new technologies that are present .

In the search for solutions to service these requirements, should be considered in addition to products ready, paid or free, which can be developed through own resources, which are the raw material the use of existing knowledge in organisations. However, in practice there is no single solution for all cases. According to each reality, can be used either way, or a combination of the existing ones. In addition, issues such as standardization often face the cultural characteristics of each organization. It is not easy to establish a consensus on a certain pattern in a group, even if small. Usually technicians do the same company, have different postures and viable for the solution of the same problem. It is the organization, if the interest of their business and through an ongoing management, choose the best route to be followed.

> Appendices A and B

< Migration for Web environment - Use of the Engine and Execution

Migration of Applications for Web Environment - A Practical Approach