Ankit Gupta
Week - 12
Software Technical Reviews   

A review process can be defined as a critical evaluation of an object. It includes techniques such as walkthroughs. The objective of the reviews is to search out design weaknesses, faulty designs, or designs which may be cost drivers. Problems can often be identified early from the data item submissions, and attempts can be made to clarify these problems on a case-by-case basis before the review to avoid major problems and surprises at the meetings. Program includes a functioning requirement Research and Development. Technical reviews would be basic to monitor growth. Program includes a functioning requirement but no Research and Development. The system is mostly commercial off the shelf gear. It could include some non-developmental items and limited trainer unique equipment like brackets or cabinets to mount the COTS equipment or maybe some panels built to simulate to body of weapon. Limited technical reviews held in conjunction with scheduled progress reviews would be necessary. Program includes a performance specification  but no Research and Development. The system is all commercial off the shelf equipment. It could include some non-developmental items but no trainer unique equipment. If the software were complex, then limited technical reviews held in conjunction with scheduled progress reviews would be necessary. If the software is not complex, then only progress reviews might be necessary. Program includes a functioning requirement and no Research and Development. The Government is mostly concerned with schedule in this case as implementation is already determined and the contract type will be fixed price. Scheduled progress reviews would be all that is basic.