What is java software architecture

What is software architecture?

Software architecture is an abstract description of the overall structure and components, used to guide the design of all aspects of large-scale projects;

Analysis diagram:

1. The most important thing about an architecture is the relevant parties. The relevant parties include customers, bosses, developers, testers, operation and maintenance personnel, and people related to the project can be called relevant parties;

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

3. The entire process is to build a system for relevant parties, and the capabilities provided by the system should satisfy the relevant parties;

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

5. Architecture upgrades require the support of architecture documents, which are mainly output to relevant parties as the standard support of the architecture;

6. Architecture documents require the composition of architectural views, including 4 1 view models, integrating concerns;

7. Architecture is mainly divided into two elements, architectural elements and the key between elements. Elements include modules, components, packages, classes, etc.; relationships include implementation, integration, aggregation, association, etc.; element-based relationships are divided into static relationships and dynamic relationships;

Redefining the Architect

Architect is a person's professional title, the person who builds the system and copies the system; architect is not a position but a role. Anyone may be the architect of the company, but the position is not necessarily the person in charge.

How to improve your ability as an architect?

1. There needs to be corresponding architectural methods to support the design you make

2. The architectural model needs to be determined according to the situation. You cannot do architecture just for the sake of doing architecture. According to the company's burden Capability and business design framework, there is no best architectural framework, only the most suitable framework for the company;

3. To be an architect, you must have enough practical experience and real scenarios;

4 , you must learn the ability to draw, summarize, and communicate;

If you want to do architecture

Software architecture is composed of elements, forms, and relationship constraints, and a single view cannot express the overall architecture.

4 1 Architecture view

Logical View: designed object model;

Process View: Capture the concurrency and synchronization characteristics of the design

Physical View (Physical View): Describes the mapping of software to hardware, reflecting deployment characteristics;

Development View (Development View): Describes the software in the development environment Static organizational structure;

Scenario views (scenarios): describe use case scenarios;

Logical view

Relevant parties: customers, users, development organization managers;

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

Purpose: development organization division, role of cost schedule assessment

Development view

Relevant parties: Development and testers

Element composition: Describe the system layers, partitions, packages, frameworks, system general services, business general services, classes and interfaces, system platforms and related basic frameworks;

Purpose: Know the development organization design and development implementation

Physical view

Related parties: system integrators, system operation and maintenance personnel;

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

Purpose: physical nodes and node communication functions;

Process view

Related parties: performance optimization, development related Personnel;

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

Purpose: to help solve performance optimization and system bottlenecks;

Scenario view

Stakeholders: users, designers and developers.

Purpose: To illustrate the breadth of the architecture or the way in which many architectural elements operate;

How to build a model

1. The model is the entire system An abstracted concept, the solution is based on the understanding and knowledge 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 building a model is: first determine the domain problem, construct a conceptual model through analysis and extraction, extract architectural requirements from this model, and finally provide a solution;

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

5. It facilitates the collaboration of personnel between systems and the accumulation of document assets;

6. In situations where there are many discussion scenarios or meetings Communication use;

7. You can use whiteboards and drawing tools to draw different types of diagrams according to different scenarios;

UML Modeling

UML stands for Unifiled Modeling Language, unified modeling Language has become a universally recognized language form for architectural communication, which can describe specific problems in a certain field, and the architecture or software implementation in the design phase.

UML diagram classification

Static diagram: 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 Diagrams, Object Diagrams, Class Diagrams, Component Diagrams, Package Diagrams, Deployment Diagrams

Dynamic diagram: By depicting the execution process or entity state changes, it shows the transformation process of software entities during execution. Common dynamic diagrams include: Collaboration Diagrams, Sequence Diagrams, Activity Diagrams ( Activity Diagrams), State Diagrams;

General model for drawing

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

General relationships:

Association: connecting model elements and link instances;

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

Generalization: expresses the relationship between general and special;

Aggregation: expresses the relationship between the whole and parts;

The above is the detailed content of What is java software architecture. For more information, please follow other related articles on the PHP Chinese website!