# #
Business Standards
Technical Warranty
1 year since completion of project, and only valid if client does not make any change in source code.
Refund policy
We make 50 to 100% refund if the client is not happy with our services and claims a refund within 60 days of project completion.
Online Support
We provide 24X7 online support through our helpdesk and serve customers world-wide using instant messaging, phone and e-mail.
 
 
 
 
Programming Standards

  1. While working on web based applications, all form submissions should be subjected to appropriate nature and quanta of validations. Such validations may be JavaScript based client side validations OR server side programming based validations in case where client end users do not have access to JavaScript enabled browsers/ computers.

 

  1. The user supplied data related to credit-cards (viz. Card number, Card verification value and card expiry date) should be encrypted BEFORE being transmitted over internet to a website or its program(s). The data related to a credit-card should only be submitted to secured web form, having a dully assigned and valid  SSL certificate endorsing the legitimacy of the website/ web-form which is receiving the credit-card information. An exception to this rule can only be taken upon specific client request and it is strongly recommended that clients be warned of technical threats involved as soon as they request an exception to this rule.

 

  1. Programming logic and flow control should be designed to ensure minimum load on the server.

 

  1. Programming of Javascript/ PHP/Flash-Actionscript or VBScript based modules should be done with at least 1 line of code per 20 lines of source-code.  

 

  1. The programmers should maintain proper indentation in their program source code.

 

  1. The naming convention of the variables to be used in programs will have to be followed strictly as detailed below:-

 

    1. A variable should have two parts in its name. The two parts will be separated by a “-“ (underscore) character. 
    2. The first part of the variable name will have to be based on the name of the user-group, entity or object to whom this variable may be primarily related.
    3. The second part of the variable name should be based on the nature of attribute, quality, or nature of the information being stored in that variable.
    4. A variable name that represents a database  name should also be constructed in the manner as described above; only with the difference that the first part will be termed as “millennium” and the second part of name will be based on the project name/title itself.

 

  1. It will be a collective responsibility  of the programmers and the testing department employees to ensure that all guidelines mentioned in this chapter are closely adhered to and implemented in day-to-day working. 

 

Phone :
(+91)-532-2504242
Mobile :
+91-9335306283
E-Mail : support@ecomblaster.com
© Ecomblaster.Com 2005-2007    Pricing | Non-Disclosure | Privacy Policy | Terms Of Service