3 P and 1A (4) in software development-architecture Summary

1. What is architecture?
The common components abstracted from multiple products are organically linked to form an architecture.
At present, we abstract the commonalities of technology, called sea.
The sea architecture describes the elements contained in a software and the relationship between the elements to form a skeleton. On this basis, multiple products can be built.
The architecture is a static result, which can be reflected in the document or in the support library and development tools.

Ii. Why should we propose the architecture?
We are going to develop multiple products in a number of business areas, and then create custom versions from these benchmark versions,
In this way, we will have a huge product tree. Based on past experience, it is very easy to see product chaos and repeated development,
We want to use the architecture and development and management tools above it to avoid the above situations.

Iii. What role does the architecture play?
Currently, we have developed multiple products in the sea architecture and can play the following roles:
1. Separation of general and proprietary software
The sea architecture is an open system and will continue to absorb some common parts in the subsequent development process.
2. technically difficult separation
Most technical problems have been blocked by sea, and application product developers focus mainly on the business.
3. Development consistency between the online version and the standalone version
The sea architecture shields the network layer. For application developersProgramCoding, debugging, unit testing,
You can use a tool to generate a network version during release.

4. Different views of the Architecture
An architecture can be analyzed from multiple comparative perspectives:
1. Development/Operation
There are two types of software: Development edition and running edition;
The development version view involves how to organize and operate on the development version.
The running view involves the organization of execution files and how the software runs.
2. Logic/physical
Physical refers to a specific technical platform.
The logic is unrelated to the technical platform.
3. Static/dynamic
Source codeOrganizations and execution file organizations are all static.
How the development edition is converted to the running edition, and how the software runs is dynamic.
4. Technology/Business
Software is a combination of technology and business, and technology and business constitute two aspects of software.
Currently, SEA is a technical architecture, and whether the business can develop an architecture remains to be studied. You can refer to this field.

Each angle can be integrated for precise description.
For example, the static view of Physical Development describes the source of the development version on a technical platform.CodeOrganization.
The dynamic view of Physical Development describes how the design results and source code of the development version on a technical platform are converted to the running version.

5. Factors to consider for Architecture
Currently:
1. Reuse System
2. Operation Security
3. Copyright Security
4. Error Handling System
5. Commissioning System
6. Log System
7. interface framework
8. Or Map
9. Workflow

6. We hope the architecture can reach a high level.
1. Business Architecture
2. The architecture supports external collaboration