Yes. HUMASYS embraces the guidelines of IBM Rational Unified Process (RUP), which is one of the best proven practices for building and deploying software. 
Please read more about our process here 
We do have other processes in place too. It is standard for us to provide you with a full visibility into your project status through standard regular email, IM communications with your assigned project manager, direct online access to your project files in our version control system (usually VSS), bug and issue tracking system (usually Rational ClearQuest). It's needless to say that we have sophisticated QA procedures in place, including rigorous testing.

We usually define testing Methodology during initial phase of the project based on business and system requirements. Then we document testing methodology in the Test Plan and approve it with the client.

We usually follow client's existing process/methodology in order to seamlessly integrate into client's business process. When the client doesn't have a well established development process we suggest using our own, which is described here

Yes, we do have issues tracking process in place. The complete process can have several iterations and/or deviations, is fully manageable and traceable online. Below is a sample basic workflow:

• Client (or our QA representative, or any authorized person) submits an issue into our web-based issue tracking system;
• Responsible person (usually PM) reviews the issue and after it passes validation it is assigned to appropriate resource (usually a developer);
• Developer investigates and fixes the issue and notifies his/her project manager about progress and status;
• Once the issue is resolved the developer (or a PM) notifies QA representative that the solution must be tested;
• Once the issue is resolved the responsible person (usually PM) notifies client about issue resolution.

We have ongoing experience working over VPN channels at client's servers and/or creating required environments in offshore office using dedicated hardware and/or VMWare GSX and/or Microsoft virtual servers.

We would prefer to use client's source control system and procedures in order to make development process more effective and intuitive for the client. However we could offer using our own source control system with dedicated branch for our changes. These changes could be synchronized with client's sources on a weekly basis.

This is to be determined once the functional requirements are known.

We ensure quality and documentation of code changes by creation of appropriate standards, training and peer reviews of the code being changed. Depending on client's requirements it can be just comments in source code and notes during file check in or more complex solutions utilizing requirements (issues) traceability matrix providing visibility from issue to architecture and to appropriate source code piece.

Code maintainability usually depends on the system architecture chosen and coding standard used.

This will be mandated by functional requirements and is project specific.