We are trying to promote complete and professional services, by developing reliable and customized applications, meant to enhance the quality and competitivity of our partners.
This is why Evoluxis equally stresses all stages of execution of a project, starting with the project analysis, continuing with the editing of the specifications document and the implementation of the project and ending with an intensive testing process.
Creating customized software applications requires skills, know-how, time and cutting- edge technology. Developing and programming offshore software solutions has become common nowadays, due to the flexibility and expertness of the software companies specialized in outsourcing. Evoluxis is one of the companies specialized in creating or improving software systems.
The targets of this activity are the offshore"/ "nearshore" companies, who need customized software solutions in order to increase competitiveness and improve their standards.
The software maintenance involves up keeping or modifying a software product in order to adjust, improve or adapt it for a new operational environment or standards.
All our services have a warranty period which implies free technical support for a predefined period of time. Once the warranty period that the partners have agreed upon has expired, the price charged for modifications and improvements is established according to certain criteria: complexity, time, type of changes required, etc). For more details, please contact us by phone or by using the contact section.
In the software making process, maintenance plays an important part. The software maintenance involves up keeping or modifying a software product in order to adjust, improve or adapt it for a new operational environment. This international standard, from the point of view of developing software products, groups some processes:
» the preparation of the software program for implementation, the drawing up of a maintenance plan by identifying certain issues that might turn up during the development.
» the process of analysis, which starts concomitantly with the need of improvement/correction of the application. For each change request, there should be an analysis done and a solution found.
» the comparison between the solution found and the one requested by the user (from a technical point of view)
» the migration process, a very delicate process which is not part of the daily routine of the maintenance team. This process comes into discussion when the software product needs to be transposed on a different platform, without loosing/changing its functionality.
» another important process but rarely met is when the maintenance team intervenes upon a software product in order to eliminate one of the program’s functionalities.
There are some practical activities which are specific to the maintenance teams:
» transmission: a sequence coordinated by activities during which the system is progressively transferred from the development team to the maintenance team;
» comprehension of the service per levels and the specific maintenance;
» the analysis and documentation of the maintenance request: a process of documentation and prioritization of tasks, used by the maintenance team;
» the analysis of complexity/dimension: there is a possibility that the dimension or complexity of the changes requested need development processing;
The purpouse of maintenance departments is not only of repairing developing teams mistakes as some believe. Recents studies indicate that 80% of effort made by these departments has the purpouse to develop and optimize a software product.
The concepts of „software maintenance” and that of „system evolution” appeared in 1969. Lehman, the one who studied these concepts resumed his researches in 8 main ideas named the Laws of Evolution. He concluded that maintenance is a revolutionart system that deals with the impact of time on a software. As time goes by and the program evolves it becomes more complex and those who maintain it have the duty to reduce complexity and develope it.
There are 3 main categories of maintenance:
1.correction- the action of correcting mistakes of a soft after it’s being given for use;
2.adapting- the modifications brought to the software in order to meet the new standards or operating environments;
3.perfecting- modifications brought for improving software performance;