logo
 
 
  Application Development
  Application Management
  OFS Advantage
  Methodology
  Enterprise Integration
  Testing
  Product Development
  eBusiness Solutions
  eGovernance
  Embedded Solutions
  Industry Solutions
 
Methodology
Software maintenance is one of the activities in software engineering, and is the process of enhancing and optimizing deployed software (software release), as well as remedying defects. It is post-delivery activity and the support will be provided for the period as agreed in the contract, from the date of sign-off. The sign-off happens when all the functionalities as agreed in the requirements document are implemented for the application. A support team will be maintained and technical support will be provided as needed. This support will be on an on-call/mail basis.

Following are the wide range of activities performed as part of OFS maintenance process;

  • Identify the system for maintenance: This means identifying the system along with its version
  • Define scope for maintenance: Responsiveness to the client is the primary consideration in determining the scope of system maintenance. Scope (both in and out) of the maintenance will be tailored to satisfy operational response requirements of client. During the agreement period, corrections and enhancements may be required. Corrective maintenance will accommodate latent defects as reported by the client. Perfective and preventive maintenance will also take place depending upon the requirements of the client.
  • Specify support period: The period for maintenance (1,2,3..n years)
  • Follow the maintenance process, which consists of the following hi level activities;
    - Problem definition: The maintenance request is received, classified, and recorded
    - Problem analysis: Analysis of the impact of the maintenance request, effort/cost estimation
    - Solution design: Modification of the software design and design document
    - Solution implementation: Implementation of the change, recompiling and unit testing
    - System test: Complete regression test + new tests
    - Acceptance test: User validates the modified/enhanced functionality
    - Delivery: System is placed into production replacing the previous release

    Note: The above sequence of steps may involve necessary customization depending upon the nature of maintenance (corrective/adaptive/perfective/preventive)

 

 
Case Studies
More Case Studies >
 
White Papers
More White Papers >