From Design Elements to Milestones

Each team identified the major software development aspects of their project during CS 410. We referred to these as design elements.

In 411W, we will transition them into milestones. The goal is to determine when each element is to begin and end.

To effectively schedule product development, you must determine which milestones have priority over others, and should begin earlier. Also, you need to determine which development aspects (tasks) can be completed in parallel.

For example, a team member may be providing authentication to your system at the same time another team member is installing database software.

Using “database” as a milestone, some associated tasks might be:

And so on…

Tasks 4 and 5 can be done at the same time, during the same week.

All other tasks must be completed serially, and each is dependent upon the previous.

During this module, create something similar for each of your hardware and software milestones.