What are the relationships and concepts between requirement analysis, Architecture Analysis, domain analysis, and system analysis?

Requirement analysis refers to the need for developers to conduct detailed investigation and analysis to accurately understand user requirements. The basic principles for converting users' non-formal requirement statements into complete requirement definitions and then from requirement definitions to process requirement analysis of corresponding formal functions are as follows: (1) a complex problem can be decomposed by function and refined layer by layer. (2) data domains and functional domains that must be able to express and understand the problem. (3) create a model. The basic task of requirement analysis is to accurately understand the old system and define the target of the new system. Answer the question of what the system must do. 1 .. the problem is clearly defined; 2. export the logical model of the software; 3. document Writing; Requirement Analysis Method: Structural Analysis: 1) establish the physical model of the current system; 2) Abstract The Logical Model of the row system; 3) establish the logical model of the target system; 4) further Supplement and optimization; Data Flow Diagram (data flow, processing, data flow origin and destination), data dictionary, and processing logic description (structured language, decision table, Decision Tree) the iedf method is an architectural pattern that describes the basic structure organization or outline of a software system. An architecture pattern can often be divided into multiple design patterns for joint use.

Name	Description
Component-based
Based on plug-ins	For example, eclipse
Object-oriented
Aspect-Oriented
Resource-Oriented	Obtain resources	Search for services, such as JNDI
Delayed Loading
Load now
Partial loading
Manage resources	Cache
Pool
Distributed transactions
AOP Management
Release resources	Timeout
Policy
Service-oriented
Blackboard	Any team member can contribute a solution to the problem or make explanations, just as many people discuss it on the blackboard, In the AI field.
Event-driven
Separation presentation layer	Separates the processing logic of the user interface from the user interface (UI) view and user operation data, such as freemarker
Client-server	The system is divided into two applications, where the client sends service requests to the server 2-tier, N-tier, peer-to-peer, cloud computing all use this model