The implementation phase translates the detailed design model into source code. The final layer of details is added to the code during this phase, as the design is NOT expected to be a complete interpretation of the required source code.

   This phase introduces requirements for dynamic testing. Although previous phases include static testing activities, the implementation phase provides the final basis for testing. At least two levels of testing are expected. Extra implementation constructs may be required to drive the testing activity (e.g. Testing Automation)

(select any activity or artifact for more information)