What are the characteristics of hierarchical software design thinking?

Hierarchical thinking is one of the most commonly used ideas in software engineering, and this series seeks to tell the story behind this idea through plain language.

When it comes to software engineering, many people learn software engineering just by learning a bunch of outdated technologies in school, only to find that most of the technologies are difficult to use after stepping into the workplace, so many people are questioning the value of software engineering.

There is a reason for this phenomenon, software engineering is a young discipline, and the engineering methods in actual development are changing all the time, and many times when the engineering methods are formed into teaching materials, they are already outdated; In addition, because software does not have the constraints of physical space, natural laws, etc. (perhaps the only constraint is Moore's Law), it is an exaggeration to say that it has infinite possibilities.

On the other hand, in practical applications, most software is directly oriented to "human" problems, and as long as there is a "human" factor in any problem, the complexity will increase exponentially, so it is difficult to take care of most situations and form consistent specifications like other fields of engineering. Therefore, it is impossible to become a qualified engineer by learning some specifications.

There is a lack of universal norms in software engineering (of course, it is now being gradually explored in different subdivisions), and many times the existing norms and methods can only be used as a reference, and creativity is more needed in practice.

The hierarchical software design idea has the characteristics of data and science, which can better design and make the whole software very convenient and scientific.

Hierarchical software design is to pay attention to a level when designing, and design your content or yours at different levels according to the different angles of your customers' needs.

What are the characteristics of hierarchical software design thinking?There are some software design ideas of the planning. The characteristics of reality, because with a sense of reality, this kind of software design will be more in line with human nature.

Hierarchical, boring. What is design and what are its characteristics? From this software. It's very good. There are often special. Peculiarity.

Hierarchical software designers will have the ability to analyze transparently or express clearly, and it is better to have separate levels and think out slowly.

What are the characteristics of hierarchical software design ideas?

What are the characteristics of a software designer? In this case, Fan Cheng eats three cities, which makes his thoughts clearer and clear at a glance.

The hierarchical software design idea has characteristics, and the software engineering adopts a hierarchical method, and the hierarchical structure is obvious, and each level includes three elements: process, method and tool.

The hierarchical software design idea has the characteristics of advanced and novel.

The hierarchical software design **full-text** is available in PDF format. Hierarchical software design Chinese and English vocabulary interpretation (interpretation), "hierarchical software design" various research materials, research reports, etc.

There are still a lot of ideas for this kind of urbanization drill design.

There are two approaches to hierarchical schematic design, which are as follows:

There are two methods for the design of hierarchical schematics: top-down and bottom-up, but there are some differences in the operation process in the middle, specifically:

1. From the top-down design of the booklet, it is the design idea of the total score, starting from the project as a whole, divided into different modules, first the whole and then the module.

2. Design from the bottom up, that is, the general design idea, starting from the functional module, combined into a whole, first there is a module and then there is a whole, I will design according to the level from top to bottom when designing a more complex item.

The significance of hierarchical circuit principle design:

The hierarchical schematic design method is to divide the entire project into several schematic diagrams. In order for multiple sub-schematics to unite to represent the same design project, some kind of connection must be established for the sub-schematic. The parent diagram of a hierarchical schematic diagram is a type of schematic diagram used to express the relationship between diagrams.

It is to divide a huge project into multiple functional modules, which are completed by multiple people, which facilitates the management of the project.

There is no difference between the two. Both refer to software architectures, which are sketches of software systems.

Software structure diagram and hierarchy diagram in software engineering are architectural design diagrams that reflect the interrelationships and constraints between components in a software system, and belong to a series of related abstract patterns to guide the design of various aspects of large-scale software systems.

A software architecture diagram (also known as a software architecture) typically illustrates the combination of components of an architecture in a hierarchical or time-phased manner. The objects described are the abstract components that directly make up the system, and the connections between the individual components describe the communication between the components in a clear and relatively detailed way.

The structure diagram is mainly used to present the relationship between various business modules

Hierarchical diagrams are mainly used to represent the content contained in different business layers:

First, from the conceptual point of view.

Structured software is a collection of functions that are rented early through modules and hierarchical invocation relationships between modules and modules;

Object-oriented software is a collection of things, realized through objects and the communication links between objects and objects;

Second, from the perspective of composition.

Structured software process data, process-centric;

The encapsulation of object-oriented software (data-oriented operations) is data-centric;

Third, from the perspective of operation control.

Structured software adopts a sequential processing method and is controlled by process drive;

Object-oriented software adopts interactive, parallel processing and is controlled by message-driven;

Fourth, from the perspective of development.

Structured Approach: Lu's focus is on design;

The focus of the object-oriented approach is on analysis;

In the structured approach, the analysis phase and the design phase are not coherent, and the data flow diagram with network features used in the analysis phase needs to be transformed into a structure diagram with hierarchical features used in the design phase, which is not the case in the object-oriented approach.

Fifth, from the application aspect.

The structured method is more suitable for the development of numerical calculation and data statistical management software with relatively simple data types.

The object-oriented approach is more suitable for the development of large-scale and complex human-computer interaction software and data statistics management software.

The implicit design model is event-driven, and it is based on the concept of broadcasting. A component does not directly call a procedure, but declares that one or more events have occurred. The other components then associate the program with the events that occur (called program registrations), and the system calls all of these registration programs.

The idea of the event-based implicit invocation style is that the component does not directly invoke a process, but rather publishes or broadcasts one or more events.

Other components in the system register the process for the event it is interested in.

When an event is published, the system automatically invokes all the procedures registered in the event, so that the publication of one event "implicitly" inspires the process in another module.

The implicit calling style is characterized by:

Applications: Used to integrate various tools in the programming environment;

Ensuring data consistency constraints in the database management system;

manage data in the user interface system;

as well as support for syntax checking in the instrument.

For example, in a system, the Widget and Variable Monitor can register (register) the breakpoint event for the corresponding debugger. When the debugger stops at a breakpoint, it declares the event, and the system automatically calls the handler interested in the event, such as the program can roll the screen to the breakpoint, and the variable monitor refreshes the variable value.

The debugger itself only declares events and doesn't care what these processes do.