● Presentation layer (Presentation): in Area 5 in Figure 1, a presentation platform is established through portal and other technologies to facilitate service requests on this interface.
● Business Process Modeling: In Area 4 in figure 1, the SOA meta-model inherits the platform-independent model from the MDA to model the business process. This part is independent of the service design and deployment layer. The main defect of model-driven architecture (MDA) is that the requirement is completely described in the model design phase and there is no feedback mechanism for demand changes. SOA uses the agile method AM to respond to changes in requirements.
● Service layer (services): Area 3 in Figure 1 shows the core layer of the entire SOA. It starts from the upper and lower layers, responds to the business model, and calls the relevant component groups to meet business requirements, form the SOA Transaction Processing Pattern of "business-driven services and service-driven technologies. Services can be layered by granularity. Although Fine Granularity provides more flexibility, it also means that the interaction mode may be more complex. Coarse granularity reduces interaction complexity, but agility decreases.
● Enterprise component layer (enterprise components): Area 2 in Figure 1. This is the place where related components play a role. These components are platform-related. At this layer, the features of many underlying software and hardware platforms are no longer transparent.
● System software layer (operational system): Area 1 in Figure 1. This layer includes the operating system, database management system, CRM, ERP, Bi, and other heterogeneous systems, is an integrated platform.
In addition, such as QoS and Security (Area 7 in Figure 1) it is also an integral part of the SOA architecture