We learned the various design reviews during the application

We learned the various design reviews during the application life cycle. What is the role of DBA in each review stage? Who, other than DBA, should be involved at each stage and why? Do you think some of the design reviews may need to be reviewed again as a result of application development? Why or why not?

Solution

If it is the database application life cycle it is must that the DBA must be there to review each stage. There are 7 stages in lifecycle. The dba role in each stage is

Conceptual design review:- in this phase the DBA must check the presentation data and the general overview for the feasibility of the application.

Logical design review:- in this the review is conducted after first level of implementation of logical data model is done. In this dba checks that all the required data elements and relations are maintained or not.

Physical design review:- in this dba checks whether the transformation from logical to physical was correctly transformed and these are linked to the correct data objects in the database.

Organisation data review:- in this the DBA check how the system is reacting to the real data and how it is working with the other systems in the organisation

SQL design review:- in this the dba checks all the code and see how the performance can be improved by creating the indexes.

Pre-implementation design review:- in this stage they check for the overall process and to clean up any bugs at this stage.

Post-implementation design review:- in this they check that system is meeting its objectives or not.

Actually in this process there will be some other member from the application development team to check that all the things are going on fine in the development way.

It is must that all the design reviews must be reviewed again and again throughout the process to check whether all the process is correctly going. Sometimes it is possible to get some new flaws in the review process.