Chapter 6. Implementation Model

• Persistence Choices

• Service Data Objects

• User Interface Choices

• JavaServer Faces

• Tying It Together

• Summary

The implementation model represents the physical composition of the implementation in terms of Implementation subsystems and implementation elements (directories and files, including source code, data, and executable files). The implementation subsystem is a way to reduce complexity in an implementation model containing hundreds of elements. A good way to think of the implementation subsystem is as the implementation model version of the design package. Like all the model-to-model mappings, the implementation model can be mapped very closely or very loosely to the design model. However you decide, it is best to keep the mapping one to one; that is, one design package should be mapped to one implementation subsystem. This allows for easy and seamless traceability from design to code.