Shulou(Shulou.com)05/31 Report--

Most people do not understand the knowledge points of this article "what is the java software architecture?", so the editor summarizes the following content, detailed content, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this "what is the java software architecture" article.

What is software architecture?

Software architecture is an abstract description of the overall structure and components, which is used to guide the design of large projects in all aspects.

Analysis diagram:

1. The most important part of an architecture is the relevant parties, including customers, bosses, developers, testers, operators and maintenance personnel, and people related to the project can all be called relevant parties.

2. The concerns of relevant parties generate architectural requirements, and the whole architecture is analyzed based on concerns.

3. The whole process is to make a system for the relevant parties, and the capabilities provided by the system should meet the requirements of the relevant parties.

4. Architecture is the technical support and implementation of the system, and all systems are supported by architecture.

5. Architecture upgrade needs the support of architecture documents, which are mainly output to relevant parties as the standard support of architecture.

6. The architecture document requires the composition of the schema view, including the 41st view model, to integrate the concerns.

7. The architecture is mainly divided into two elements, the key between the architectural elements and the elements, the elements include modules, components, packages, classes, etc., the relationships include implementation, integration, aggregation, association, etc., and the building relationships of elements are divided into static relationships and dynamic relationships.

Redefine architect

An architect is a person's job title, the one who does and replicates the system; the architect is not a position but a role, and anyone can be the architect of the company, but the position is not necessarily the one responsible.

How to improve your ability to be an architect?

1. You need to have a corresponding architectural approach to support your design

2. the architecture model needs to depend on the situation, and we can't do the structure for the sake of the architecture. according to the ability of the company and the business design framework, there is no best architecture framework, only the one that is most suitable for the company.

3. As an architect, you must have enough practical experience and real scenes.

4. Learn the ability of drawing, summarizing and communicating

If you do the architecture,

Software architecture is composed of elements, forms and relational constraints, and a single view can not express the overall architecture.

4x1 Schema View

Logical View (Logical View): the object model of design

Process View (Process View): captures the concurrency and synchronization characteristics of a design

Physical view (Physical View): describes the software-to-hardware mapping, reflecting deployment characteristics

Development View (Development View): describes the static organizational structure of software in a development environment

Scenario View (scenarios): describes the use case scenario

Logical view

Interested parties: customers, users, managers of development organizations

Element composition: system, subsystem, function module, sub-function module, interface

Purpose: the role of development organization division and cost schedule evaluation

Development view

Interested parties: developer and tester

Element composition: describe the layers, partitions, packages, frameworks, system common services, business common services, classes and interfaces, system platforms and related basic frameworks of the system

Purpose: know the development, organization, design, development and implementation

Physical view

Related parties: system integrator, system operation and maintenance personnel

Element composition: physical deployment of system logical components to physical nodes and physical network configuration between nodes

Purpose: physical node and node communication function

Process view

Related parties: performance optimization, development related personnel

Element composition: system processes, threads, processing queues, etc.

Purpose: to assist in solving performance optimization and system bottleneck points

Scene View

Interested parties: users, designers and developers.

Purpose: clarify the breadth of the architecture or the way many architectural elements operate

How to build a model

1. Model is a concept abstracted from the whole system, and the solution is based on the understanding and understanding of the model.

2. The specific model is to solve the problem in a certain field, and the process of the problem is the process of mapping the problem to the model.

3. The process of establishing the model is as follows: first identify the domain problem, construct a conceptual model through analysis and extraction, extract the architectural requirements from this model, and finally provide the solution.

4. The cost of building a model is much less than that of time development.

5. Facilitate the accumulation of personnel and document assets among systems.

6. communicate and use in situations where there are many discussion scenarios or meetings.

7. Different types of pictures can be drawn according to different scenes through whiteboard and drawing tools.

UML modeling

UML, the full name of Unifiled Modeling Language, Unified Modeling language, has become a universally recognized language form of architecture communication, which can describe specific problems in a certain field, and architecture or software implementation in the design phase.

UML graph classification

Static diagrams: describe the immutable logic in software elements by describing classes, objects, and data structures and the relationships between them; common static diagrams are:

Use case diagram (Use Case Diagrams), object diagram (Object Diagrams), class diagram (Calss Diagrams), component diagram (Component Diagrams), package diagram (Package Diagrams), deployment diagram (Deployment Diagrams)

Dynamic diagrams: show the transformation process of software entities in the execution process by describing the execution process or entity state changes. Common dynamic diagrams are: collaboration diagram (Collaboration Diagrams), sequence diagram (Sequence Diagrams), activity diagram (Activity Diagrams), state diagram (State Diagrams).

A general model for drawing

Common model elements: classes, objects, nodes, packages, and components

General relationship:

Associations: connecting model elements and linked instances

Dependency: indicates that one element depends on another in some way.

Generalization: indicates the relationship between general and special

Aggregation: represents the relationship between the whole and the part

The above is the content of this article on "what is the java Software Architecture". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more about the relevant knowledge, please follow the industry information channel.

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.