Below are the steps followed for all new developments in StrategicERP which is derived from Rapid Application Development (RAD) Model.

1. Change request created with customer along with proper version target. This is tentative target and may change in future if any dependecy document is delayed beyond target dates.

2. Change request is approved by Project Head in 2 working days. They should also provide documents on how this is handled by other products in market.

3. Change request is studied by Product Team to calculate the cost in 2 working days. Change request processed by the product team only if proper SOW (Scope of Work) , DFD (Data flow Diagram) and formats (if require any ) are attached either by client or Project or Implementation manager.

4. Change request is approved by client based on the above cost calcuation. If required, we can involve Project Head and Sales Head.

5. Change request development has policy of 100% advance payment. We request all stakeholders to not create inconvenient situation by asking to start before payment.

6. Developer is assigned based on the recent similar developments done in the same or related forms. This will take upto 2 working days. Then developer will finalise the target version based on other tasks at hand and will communicate with the team members within 2 working days.

7. Unit testing completed by developer on cloud Test29 (t29) post completion of development on cloud 16.

8. Patch is created by developer and submitted to the Linux team along with Requirement, Development documents.

9. Patch is installed on the test server of client or product to complete the user acceptance test (UAT) by the domain expert at client side or product team. If any issue found, it will move to step 4.

10. Post UAT by domain expert, the patch is migrated on the live server of customer or staging cloud 29 server of new product.

11. Staging server copy is updated to product server cloud 29 at the end of every month.