First, the business analyst contacts the customer and analyses his explicit and potential requirements. Then these requirement specifications are documented and project management, software development and software configuration management plans made. Based on these, the design document is drawn up.

Development Life Cycle

The three main software life-cycle approaches are the “waterfall’, the ‘spiral’ and the ‘V’ models. At O2F, the choice of methodology adopted is project specific. Following are the various stages for which procedures are documented at O2F.

  • Requirement Specifications
  • Design, Coding, and Testing
  • Software Delivery
  • Implementation
  • User Training
  • Acceptance Testing
  • Phase Out
  • Maintenance

Support Processes

There are many other activities that do not in themselves contribute to the development of the final software product but without the support of which, it would be impossible to incorporate quality or deliver the product within a strict time frame and budget. These support processes interact with the main processes affecting every stage of the software development cycle.

  • Project Management
  • Configuration Management
  • Software quality Assurance
  • Casual Analysis


The software programmer then translates these specifications into computer language, i.e. coding and testing.


Finally the developed package is put for implementation; there are corrections, adaptations, enhancement and re-engineering done by the programmer.