This task order provides a good example of the typical kinds of things to include in a software development task order. The following highlight some of the main elements:

Section 4 contains the typical types of constraints that are put on a task.

Section 5 provides a comprehensive list of typical deliverables for a software development task. It also provides a very thorough list of minimum required content for such deliverables as the requirements, the test procedures and reports, the software version description document, the monthly status reports, and the joint review agendas and minutes etc.

Section 7 gives a schedule based on relative dates instead of calendar dates. This is often easier than specifying the actual calendar dates. Also, the schedule has the contractor providing a proposed plan, performing a prototype of the product to flush out the detailed requirements, and delivery of the detailed requirements according to the proposed plan. The requirements are accompanied by a revised plan based on a better understanding of the detailed requirements. This technique can be used when the detailed requirements are not fully known up front and utilizes prototyping to flush them out.

Section 8 gives an example of how to define joint reviews between the contractor and the acquirer and a good minimum set of joint reviews to hold.

Section 9 gives an example of the typical type of acceptance procedure and criteria for a software task.

Section 10 illustrates a simple method of performing risk management and provides a URL to both a Microsoft Word and Excel version of a template for tracking risks. The probability, impact and time frame values would be modified to fit the particular task (e.g. the time frames would be adjusted depending on the length of the task).

Section 11 provides an illustration of how to set up maintenance for the delivered product.