1. The SUPPPPLIER shall ensure that computer software, when used or developed in conjunction with PO, performs its intended specific functions in relation to the delivery of the items. Work processes involving such software must be developed and implemented using national or international consensus standards, such as IEEE Std 730, that provide an adequate level of quality assurance.
2. Software quality assurance (SQA) includes activities such as:
• Software project management and quality planning;
• Software risk management;
• Software configuration control;
• Software procurement and supplier management;
• Software requirements identification and management;
• Software design and implementation;
• Software safety;
• Software verification and validation;
• Software problem reporting and corrective action; and
• Training of personnel in the design, development, use, and evaluation of software.
3. The SUPPPLIES shall establish and implement a SQA procedure for defining and controlling SQA activities relevant to the PO.
4. The SUPPPLIES shall submit the SQA procedure to the BUYER for review and acceptance prior to PO implementation.
LSThill is right you SHOULD verify the program internally before you use it. Don't assume the author is qualified or even if they are that they haven't made mistakes. You can't use a spreadsheet w/o considering QA.
Have you done this sort of work before? Wouldn't you already have a program (either proprietary or internally developed) to do this? If you haven't then you probably shouldn't be doing this type of work commercially.
If you do have people qualified to verify the program then why not create one since you will use it again.
If this is a uni project then either you wouldn't be expected to do it or you would be required to do it by hand.