The top-down modular approach is useful in program design because it creates a set of instructions so that the program can be developed by many programmers working independently.
The top-down modular approach is useful in not only program design, but also with simple everyday activities of life such as giving simple directions to a location. For example, the top-down approach can most easily be explained (with directions to a specific location) by first familiarizing one with a particular area so they can grasp the where to start. After that, one gets more specific by using street names and/or buildings close by. Then locating the neighborhood and then most specifically the color and look of the location. With the top-down modular approach in program design, analysts try to employ the same type of situations with their systems. They first create a high-level diagram that shows various components of the program, then how the components should be organized and the finally how they interrelate. The most broad part of the spectrum first then leading to much more specific pieces of code that form the design.
In the top-down modular approach, it's useful in that of conveying more detailed information later in the process. It first starts out as a broad category, moves, then, to more logical pieces and the more information that is added the more details come about.
Another useful thing that it provides is that each modular can change without affecting any of the others, making it easier to develop and change information.
A top-down modular approach is useful because it shows the various components of a program, how the components should be organized, and how components interrelate. It is also useful when the project team plans to write code from scratch or when existing pieces of code will be assembled to build the system.
The top-down modular approach is useful in program design for many reasons. Top down design is both modular and flexible, that is, it explains the program in modules starting from the most general to the most detailed. With this approach the program is easier developed and changed because of the separate modules. Furthermore once the general outline is created programmers can add the detailed specifications for the program.
Using a top-down modular approach when designing a program is useful because it creates a design that is modular and flexible. The text uses the example of giving someone driving directions on page 371, I will use the example of a recipe. The same concept holds true, before telling somewhat what proportions to mix together you must express what ingredients are needed, next the steps can be presented in easy to understand modules that express 'first do this....then do this... mix together... and bake at...' By using this top-down approach the other person viewing the program can become oriented and see the big picture of what the final product may look like.
The top-down approach is useful because it is flexible and provides detail later on, rather than in the beginning to make it easier to understand. It's useful for organization and creating a clear message. Starting broad, with the end result in sight, then adding details makes it easier to understand.
The top-down modular approach is useful in program design because it creates a set of instructions so that the program can be developed by many programmers working independently.
ReplyDeleteThe top-down modular approach is useful in not only program design, but also with simple everyday activities of life such as giving simple directions to a location. For example, the top-down approach can most easily be explained (with directions to a specific location) by first familiarizing one with a particular area so they can grasp the where to start. After that, one gets more specific by using street names and/or buildings close by. Then locating the neighborhood and then most specifically the color and look of the location. With the top-down modular approach in program design, analysts try to employ the same type of situations with their systems. They first create a high-level diagram that shows various components of the program, then how the components should be organized and the finally how they interrelate. The most broad part of the spectrum first then leading to much more specific pieces of code that form the design.
ReplyDeleteIn the top-down modular approach, it's useful in that of conveying more detailed information later in the process. It first starts out as a broad category, moves, then, to more logical pieces and the more information that is added the more details come about.
ReplyDeleteAnother useful thing that it provides is that each modular can change without affecting any of the others, making it easier to develop and change information.
This comment has been removed by the author.
ReplyDeleteA top-down modular approach is useful because it shows the various components of a program, how the components should be organized, and how components interrelate. It is also useful when the project team plans to write code from scratch or when existing pieces of code will be assembled to build the system.
ReplyDeleteThe top-down modular approach is useful in program design for many reasons. Top down design is both modular and flexible, that is, it explains the program in modules starting from the most general to the most detailed. With this approach the program is easier developed and changed because of the separate modules. Furthermore once the general outline is created programmers can add the detailed specifications for the program.
ReplyDeleteUsing a top-down modular approach when designing a program is useful because it creates a design that is modular and flexible.
ReplyDeleteThe text uses the example of giving someone driving directions on page 371, I will use the example of a recipe. The same concept holds true, before telling somewhat what proportions to mix together you must express what ingredients are needed, next the steps can be presented in easy to understand modules that express 'first do this....then do this... mix together... and bake at...'
By using this top-down approach the other person viewing the program can become oriented and see the big picture of what the final product may look like.
The top-down approach is useful because it is flexible and provides detail later on, rather than in the beginning to make it easier to understand. It's useful for organization and creating a clear message. Starting broad, with the end result in sight, then adding details makes it easier to understand.
ReplyDelete