![]() |
|||||||||||||||||||||||||||||||
|
In House Development Processes at Codito
At Codito, adherence to industry standard tools and processes, with a means to achieving certifiable quality, is of paramount importance. Our strong beliefs in customer satisfaction and our eagerness to present the best solutions, which are tried and tested, drive every project executed here. When a customer seeks a solution from us, we carry out a detailed analysis of the problem statement. We believe that a well formed problem statement is essential to a good solution. This analysis leads to the outline of the Project Plan. The plan addresses all relevant issues such as task resource allocation, Risk Analysis, Estimated milestone delivery dates and Cost estimation. We believe that transparency and open communication with the customer is essential. As such the project is tracked at a fine granularity and weekly project reports are provided to our customers to keep them in the loop and aware of the situation at hand. A customer's say in the progress of the project is respected and essential updates are done, on request, in the Configuration Management Plan. This takes care of all the customer requested changes and tracks these changes using code versioning. Strict adherence to well-defined coding standards is a must here. The code is written lucidly and is well commented which will aid the customer during the end-stage knowledge transfer. Use of editors allowing consistent format settings for coding and use of version control mechanisms is a must. We use version control efficiently to have consistent development changes reflected appropriately and also use extra levels of versioning to avoid build breakage which can be a blocker. Once the coding stage is complete, the code undergoes critical testing. A test plan is created which is tailored for the customer's situation. As an example, the test harness provided by the Linux Test Project (LTP) is used to ascertain the robustness of the linux kernel ports done here. Also, the regression mechanisms provided by the Gnu Compiler Collection (GCC), are used to ensure that toolchains provided by us are bug-free. We use the Bugzilla system for reporting, removing and tracking bugs. Debug releases for testing are made and comprehensive bug reports are released when appropriate. Our committed quality assurance team ensures that all quality parameters are attended to before a release. All relevant documents and user manuals are generated for the ease of our customers and support is available as needed. For queries regarding our project management processes, interested parties may contact us at the following email address: |
||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||