Phases of SQL System Development

In developing any system, you start at the beginning and go through to the end, and it's no different with SQL. The following list shows you what to consider at each phase of the SQL development lifecycle:

Definition Phase: Precisely define the problem to be solved, its magnitude, and who will work on it.

Requirements Phase: Develop a detailed description of exactly what the development effort will produce. Gather all relevant information and put it into a requirements document (Statement of Requirements). Get client signoff.

Evaluation Phase: Determine exactly how you will meet the requirements. What tools will you use? How will you deploy your development team? Determine whether the job is doable within time and budget constraints.

Design Phase: Create a database model and then design a database and database application that satisfy the terms of the requirements document.

Implementation Phase: Build the database and the database application. Include copious documentation within the code and in external documents.

Final Documentation and Testing Phase: Give the database and application a tough workout. Hit the system with every conceivable input condition and a few inconceivable ones. Try to overload it. See where it breaks. When it breaks, send it back to the implementers or even back to the designers. Document everything.

Maintenance Phase: Fix latent bugs as they arise. Provide updates and enhancements called for by the client.