What can we say?

A major part of design and development is driven by process, and process is most effective when optimized based on the nature of the project. We follow your process when one is in place. If you do not have processes in place, we can help you, and if you choose not to, we will rely upon our own processes for the work we perform.

Unless your process stipulates otherwise, we adhere to the following principles

• Design inputs flow directly from requirements analysis. Progress tracking and scope creep prevention are greatly simplified when there is one to one correlation between requirements and design artifacts.
• Your Development Team members are believers in proper documentation and requirements inheritance, regularly put that into practice.
• New software modules are “seeded” from the requirements specifications and those requirements are maintained within the implementation source files.
• Public programmatic interfaces are documented and maintained within the implementation.
• Embedded source code documentation is maintained in a format suitable for, and extracted using document generation tools such as Doxygen.