The production phase merges the approved visual design, functional elements, and content into one cohesive product. Interface graphics are assembled into final form with the content. Functional components move from prototype to beta, and, following a test cycle, to the final release version.
At this phase, all questions should have been answered in the previous two phases and should now be described in the functional specification as well as seen in the prototypes. The idea, is that the careful planning already completed will prevent any big revelations from occurring that might change the scope or nature of the project. This eliminates redundant efforts, wasted energy and in the end saves time and money. If major revelations/changes do need to happen, however, it may send the project back to stage one (that is, if the goals, audience, or messages sufficiently change), or at least, back into phase two. This is why it is so important to get those answers right at the beginning.
Specifically: Implementation of visual design (mockup all pages and all production art), programming (HTML, JavaScript, Java, Perl, CGI), technology integration (new servers, database, machines)
This phase concludes with delivery of the final product ( in beta )and confirmation that it meets the specifications outlined in the requirements definition document, functioning as expected and required under actual conditions.
When production is finished, the project still isnŐt yet. It still needs to be tested and made live.
Deliverables: Testing plan, beta product, user templates ( if necessary )