Answer:
Step-by-step explanation:
Top-down design allows a programmer to take a complex idea, break it down into high-level tasks which can be further broken down into more detailed sub-tasks (Evans, Martin, & Poatsy, 2018). The larger a program gets, the more important it is to have a clear design. It is easier to fix an error during the design phase than the coding phase. If the design is flawed, a programmer can end up having to delete or rewrite large portions of code. Reworking large portions of a design is preferable to rewriting large portions of code. Even small programs can become overwhelming with a number of tasks to perform. Hierarchy Chart (hierarchical diagram) shows the breakdown of a system to its lowest manageable parts. It is a top-down modular design tool, constructed of rectangles (that represents the different modules in a system) and lines that connect them. The lines explain the connection and/or ownership between the different modules among the system just like in an organizational chart. main purpose is to describe the structure and hierarchy of an entity. This entity could be a strategy, event, software program, and so on. The hierarchy chart is suitable in any situation that aims to present the organized structure of a material or an abstract entity.