Master Software, Inc. uses a style guide for deconstructing, organizing, coding and testing to make sure that nothing is missed. This guide includes:

• Makefile
• Library selection and use
• Normal and error exits
• Logging
• Signal handling
• Banners, protection and sccs revison control
• Command line handling
• OS Variables
• Argument Definition and Passing
• Testing and Verification Code
• Debugging Code
• Correlation with specifications

Master Software measures quality of code by adherence to our style guide, because we find that code that is compliant is maintainable and extendable. Our goal is to support a life cycle model of coding where code is enhanced and maintained over a long period of time. Our guide includes error location, diagnosis, compliance to new functional specification changes, upgrading of platforms, and identification of function of existing code. Our goal is to assure that the code will live cost effectively as long as the client wishes it to.

Master Software has many years of experience maintaining and upgrading coding originally done by others. We know what is necessary to put code on a sustainable and reliable basis.