4th Step: Implementation Design

by Penny P
In database analysis and design, there are three major steps that are followed: conceptual design, logical design, and physical design. The author of the article explains that there is a need to extend and include a fourth step: implementation design. This step would come in after the logical design and before the physical design. The current view of the implementation step is seen as a substep of either the logical or physical design. In other words, it’s lumped in with the design of the logical or the physical. By making the implementation design a separate step, designers can fulfill several important actions before the physical design is created. Doing so will allow the logical design to stay focused on tasks that need not consider them, such as how to implement the database when they move on to the next step. And for the physical design stage, the designer can better focus on the best way they could access the database with the DBMS.

With all design modifications, its goal is to enhance the performance. However, there is a possibility that the modification can either help database operations execute faster or end up slowing things down. With the designs being modified, it can also make the database more complex. This can result in more complex SQL commands. With more complexity, there can also be an increase of opportunities for user to make errors. So the main question is whether implementing the fourth step is worth the trouble.

I thought this article was helpful because it help lay out the key steps in database design. It also showed that there is a possibility that the creation of the fourth step can better improve the design process. It’s interesting to know that some people consider the implementation design as part of the logical design while others thought it was part of the physical. For beginners starting out on database design, I can see that it could be pretty confusing for them since there isn’t a set rule as to when to consider the implementation. With the creation of the fourth step, people can focus on the tasks at hand and build a better database. They won’t have to worry about things that will be solved in a later step.

 

Reference:

Martyn, Tim. (2000). “Implementation Design for Databases: The “Forgotten” Step.” IT Professional Magazine. (Mar/April 2000) P. 42-49. Retrieved from http://search.proquest.com/docview/206312115?accountid=10357.

4 thoughts on “4th Step: Implementation Design”

  1. I had no idea that there could be possibly be a 4th step in making a database. It does make sense and seems like a good idea so that the logical design can focus on there tasks while the physical design can focus on there tasks. I can also see how it can get complex because there are more steps being added which can make following a design harder. I think it all just depends on the need of the database, if it calls for a fourth step then do it and if not then just leave it out.

  2. I can see how some people would consider the of implementation design a logical part or a physical part. But I think it would be better if it were just it’s own part. This way, people would not confuse themselves as to what part they are on. This can also lead to enhanced system performance because instead of putting many parts into one step, we are able to divide and have each step be responsible for their own functions.

  3. I think out of all of those four steps you have listed, i would say the more difficult ones are logical and implementing. Its like coming up with how things are going to work, then it’s how to make all these things working. and testing would important also.

  4. I just read another blog about the physical step. And it turns out the physical step its just as important and difficult as rest of the steps

Comments are closed.