Milestones, Schedule and Ownership

Milestones You will need to break your project down into a set of milestones. A project is broken down into a series of milestones in order to gauge progress and to break the project down into pieces that can be executed in parallel, as much as possible. Each milestone must be concisely described as a series of carefully-described tasks that can be executed by the responsible individual(s) with little or no need for further clarification. Milestones should be defined so that they have little interaction with each other and so that they follow the natural order required to complete the project. Note that testing and verification steps are an essential part of nearly all milestones. Once all of the milestones have been completed, the project should be completed.
Schedule The milestones must be tied to a schedule that you will carefully monitor during the completion of your project.
Ownership: Each milestone must be owned by one person. They are responsible to see that the milestone is completed by the prescribed date. In cases where a milestone consists of multiple tasks that will be completed by multiple individuals, the owner of the milestone must ensure that each of the tasks are completed on time.

Notes:

As with the specification, the milestones will need to be written using Word, Pages, or some equivalent. When submitted, it must be in PDF format. No other format will be accepted.
For small projects like this one, it is recommended that the tasks that comprise a milestone should be doable by a single software/hardware engineer.
Each milestone must contain a test/demo that, when executed, easily determines if the milestone was successfully completed. Important: this test/demo should be a go/no-go test. The outcome is pass/fail.
The schedule can be described using a graphical-drawing program, a spreadsheet, etc.

System Overview