TABLE OF CONTENTS This chapter considers the implementation discipline of the Unified Process. This discipline is concerned with implementing the design produced by the design discipline (that is, in terms of Java, it concentrates on implementing classes and interfaces, creating packages and producing class files). It also deals with the remaining non-functional requirements and the deployment of the "executable" modules (in our case Java class files) onto nodes (such as specific processors). It must therefore deal with any implementation issues that have been left as too specific during the design discipline.
However, implementation still tends to pose unexpected design problems which you must solve. These decisions should be subject to, and determined by, the processes described in the remainder of this book.
You should treat the implementation of an object-oriented system in just the same way as you would treat the implementation of any software system. This means that it should be subject to, and controlled by, the same processes as any other implementation.
This chapter does not try to present the concepts behind current thinking in software engineering best practice for software implementation (that could take a whole book in itself); rather, it focuses on those aspects that are specific to the Unified Process.
In the remainder of this chapter the artefacts and activities of the implementation discipline are presented.
The primary artefacts produced by the implementation discipline are:
Implementation model. This describes how the design has moved forward into the implementation. That is, it...
