Shulou(Shulou.com)06/03 Report--

This article mainly introduces "how to construct easel". In daily operation, I believe many people have doubts about how to construct easel. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts about "how to construct easel"! Next, please follow the editor to study!

I. Preface

Many programmers have a headache in easel composition and don't know what to draw and how to draw it!

Share, review, report, reply, as long as you are in the programmer industry, you can hardly do without drawing.

When it comes to drawing, many people want to stand up and shout, "scroll", "volume", "PPT engineer", but the program code itself is a concrete realization of mathematical logic. Without some charts and words, it is very difficult for everyone to communicate under a common consensus.

This is not like the liberal arts, "Babiao Liuyun clear night, Jiuxiaohua Moonlight Spring City" can be associated with what it is describing. However, the partial science code logic or architecture design can only show the abstract content in the form of charts, so that everyone can work together under the same consensus.

And the structure diagram, flow chart, structure diagram, function diagram, logic diagram and so on we draw need to be good-looking, easy to understand, easy to use, easy to do, because:

To look good is to improve the efficiency of communication.

Easy to understand is to enhance communication and consensus.

Easy to use is to improve the quality of delivery

Easy to do is to improve the speed of implementation.

This is like a gentleman in the pursuit of a beautiful girl, good-looking want to take the initiative to flirt, moral conduct and common values will soon make you say that I understand you, followed by delivery quality and implementation speed, which is also a natural thing.

OK, take it easy, and then we will concentrate on studying the architecture diagram, what is it, how to draw it, and how to use it.

2. What are the types of architecture diagrams?

Just talking about the technical architecture diagram, usually we? It refers to the system architecture that selects various technical components to support the whole service construction. However, there will be other classifications for different population ranges and different scenarios, as shown in figure 26-1.

Business architecture: the description of the results and processes of the business at the beginning of the demand is generally vague and may come from feedback from a boss, operator, or user. Customers said that Haier washing machine potato will be blocked, Haier immediately designed a special potato washing machine business direction is often the direction and results of the strategy, including business planning, business modules and processes, as well as a list of problem domains.

Application architecture: service reuse, cross-group collaboration, simplicity, flexibility and integration are the points that must be considered in the application architecture, just like you want to launch a chat feature. then the chat content input method, text recognition, public opinion monitoring, as well as video services, payment services, etc., are the products of precipitation to the platform under the layering of the application architecture, which are used by all parties.

Product architecture: business needs, product solutions, compared to the extensive business process, the product architecture will be more delicate and consider the layering and boundaries of each module.

Data architecture: data acquisition, data storage and data use are the three problems to be solved in the data architecture, such as database storage, big data summary, data analysis and so on.

Technical architecture: it is the closest architecture design to the programmer, it is not only the architecture diagram design of the system, but also includes the structure, function, process, logic and so on. Its specific description is the specific implementation scheme of how to land the whole system.

What is the Zachman framework?

Zachman framework, the first enterprise architecture theory founded by John Zachman (John Zachman) in 1987, is still regarded as the most authoritative theory in enterprise architecture design by the industry.

The Zachman framework (Zachman framework) is a logical structure that can represent enterprise information according to different categories and perspectives.

The Zachman framework looks at the enterprise from six horizontal perspectives, which can be divided into what content, how to work, where, who is responsible, and why (called W5H).

The column of the framework consists of a set of artifacts, divided into planners, owners, designers (architects), builders, subcontractors, products, or sometimes expressed as viewpoints: scope context, business concepts, system logic, technology, physics, component assembly and operation classes. The overall TOGAF Zachman framework is shown in figure 26-2.

The six horizontal items of the table represent a certain aspect of the information system, and the explanation of cleaning any thing in these basic aspects is enough to describe it clearly.

Data (What): what is business data, information, or objects?

How (that is, how does it work): how does the business work, that is, what is the business process?

Network (Where, where): where does the enterprise operate and deploy?

Who (i.e. who is responsible): who? What is the business unit and its hierarchy?

Time (When, that is, when): what is the business plan and workflow? When will it be implemented?

Reason (Why): why did you choose the solution? How did this come about?

The vertical six items of the table represent the perspectives used by people involved in the construction of information systems in describing information systems, including:

Scope / planner (Planner): this view describes the business purpose and policy and acts as the context in which other views will be derived and managed.

Business model / owner (Owner): this is a description of the organization in which the information system must operate.

System Model / designer (Designer): this view outlines how the system meets the information needs of the organization.

Technical Model / Builder (Builder): this is a representation of how the system is implemented, and it makes specific solutions and technologies obvious.

Detailed statement / subcontractor (Sub-Contractor): these representations explain the implementation-specific details of some system elements: parts that need further explanation before production begins.

Functional Systems / products (Functioning Enterprise): this line was not included in the 1987 paper ("A framework for information systems architecture"). In fact, this line is not within the scope of the architecture description, but it was eventually added in order to make the architecture Zachman framework's representation of the architecture more complete.

According to the definition of TOGAF, an enterprise is a collection of organizations with a series of common goals, and the architecture is to effectively achieve this series of goals.

In the process of implementation, it defines the conceptual blueprint of the structure and operation mode of the enterprise (SearchCIO), as well as a comprehensive description of all the key elements of the enterprise and their relationships (Zachman). The process of translating business vision and strategy into effective enterprise change (Gartner) by creating, communicating, and optimizing key principles and models that describe the future state and development of the enterprise.

Can this part of the content will be more around, but can be used as an extension of the knowledge of architectural design for learning, understanding and application.

Fourth, accompany you to draw a structure diagram

To put it simply, the architecture diagram is a demonstration of the implementation plan to reach a common understanding. You don't have to stick to some form. As long as you can draw it clearly, it is most appropriate to speak clearly.

1. Architecture selection diagram

Difficulty:?

Role: usually in the initial stage of new project development, we have to do some technical selection work. Choose the technology that is suitable for current development in terms of load, gateway, architecture, governance, framework, services, data, and environment and support services.

two。 Micro-service architecture

Difficulty:?

Function: after the technology selection is finished, the next step is the application of these technologies. The process is a bit like building blocks, filling each area with building blocks that fit the location. If it is a team start-up or a technology upgrade, then the process is relatively complex and requires a lot of verification. However, in fact, the technical layering and use of the Internet has been relatively stable, and it will not take too long to build such a micro-service.

3. Technical architecture diagram

Difficulty:?

Role: the technical architecture diagram is mainly for the R & D level to guide the technical implementation, it can clearly divide the system layering and implementation structure. In addition, the structure of the case project will be explained together, so that the team partners can quickly enter the development.

At this point, the study of "how to construct easel" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.