Custom Application Development ERP Contract Programming eBusiness Solutions Web Design
Outsourced Product Development Application Maintenance Application Testing What is Software Testing? Testing Services & Types
Technology Based Software Testing Testing Life Cycle Test Deliverables & Metrics Testing Tool Capabilities  
Delivery Model
The generic service delivery model followed by Seanergy Softech Practice are given below.
  • Resources at onsite location
  • Complete project execution onsite
  • Project reporting to Onsite Manager
  • Resources at onsite and offshore locations
  • Project execution at both onsite and offshore
  • Project transition to offshore
  • Project reporting to Offshore Manager
  • Project backed by proven processes methodologies and support
  • Entire project execution offshore
  • Project reporting to Offshore Manager
  • All the Software/ tools Installation and configuration
  • Project backed by proven processes methodologies and support functions
Seanergy Softech selects the ideal delivery model based on each customer's specific business case.

A very high-level workflow of the interaction process between the customer and Seanergy Softech is illustrated below:
  1. The client sends the introductory mail mentioning the outline of the QA job that he/she is looking for.
  2. The QA Manager goes through it and responds with a set of queries.
  3. The client responds and asks for the test plan and sample test cases.
  4. The QA Manager prepares the test plan and mails it along with a few sample test cases.
  5. The test plan is reviewed and finalized by both the parties.
  6. The QA Manager discusses the project with the team members and the test cases are prepared.
  7. Test cases are executed for a particular version of the product, reviewed and mailed to the client.
  8. The bugs are approved by the client and debugged by his/her development team.
  9. Depending on the project requirements, the client releases the next version of the project for QA and the test plan and test cases are updated, accordingly.
  10. The same process is repeated. Once all the bugs have been reported, and the project is re-tested and de-bugged, the QA process concludes.