These last several chapters have hopefully given you at least a glimpse into all of the moving parts (outside the actual writing of code) in development efforts that are useful to be aware of in software engineering. The odds are good that any given team or company will have selected which methodology, and what pre- and post-development processes are going to be in play. Even so, knowing what to expect from them, or what might be causes for concern while working within their various combined contexts, is useful information, and often one of the expectations that divide programmers from software engineers.
With all of that said and out of the way, it's time to start looking in more depth and detail at the meat of any combination of these—the development processes themselves. To do that, we need a system—a project to work on.