Conclusion

Throughout the course of this book we use the Unified Process lifecycle model. This decision is based on the following reasoning.

Because the requirements for the project are more or less static, the Unified Process is a good choice. UP also enables us to explore the technological uncertainty at the beginning of the project by building a throw-away prototype. In addition, the traditional, well-structured approach with go/no-go decision points lets us track our progress and identify problems at the end of each iteration.

Within the iterations, we use the following icons to identify the core workflows:

Requirements

Analysis

Design

Implementation

Test

The following icons are used to differentiate programming and software engineering sections throughout the rest of the book:

Programming Section

Software Engineering Section