We handle broad range of software products for maintenance. We follow a strict but feature rich process to avoid end moment surprises.

eLapital organizes the maintenance process in seven phases. In addition to identifying the phases and their order of execution, for each phase, we identify input and output (deliverables), the activities grouped, related and supporting processes, the control, and a set of metrics.

Problem identification, classification, and prioritization: This is the phase in which the request for change (MR - modification request) issued by a user, a customer, a programmer, or a manager is assigned a maintenance category, a priority and a unique identifier.

The phase also includes activities to determine whether to accept or reject the request and to assign it to a batch of modifications scheduled for implementation.

Analysis: This phase devises a preliminary plan for design, implementation, test, and delivery. Analysis is conducted at two levels: feasibility analysis and detailed analysis. Feasibility analysis identifies alternative solutions and assess their impacts and costs, whereas detailed analysis defines the requirements for the modification, devises a test strategy, and develop an implementation plan.

Design: The modification to the system is actually designed in this phase. This entails using all current system and project documentation, existing software and databases, and the output of the analysis phase. Activities include the identification of affected software modules, the modification of software module documentation, the creation of test cases for the new design, and the identification of regression tests.

Implementation: This phase includes the activities of coding and unit testing, integration of the modified code, integration and regression testing, risk analysis, and review. The phase also includes a test-readiness review to asses preparedness fort system and regression testing.

Regression/system testing: This is the phase in which the entire system is tested to ensure compliance to the original requirements plus the modifications. In addition to functional and interface testing, the phase includes regression testing to validate that no new faults have been added. Finally, this phase is responsible for verifying preparedness for acceptance testing.

Acceptance testing: This level of testing is concerned with the fully integrated system and involves users, customers, or a third party designated by the customer. Acceptance testing comprises functional tests, interoperability tests, and regression tests.

Delivery: This is the phase in which the modified systems is released for installation and operation. It includes the activity of notifying the user community, performing installation and training, preparing and archival version for backup.