PESOI: Process Embedded Service-Oriented Architecture

Tsai Wei-Tek
2006 Journal of Software (Chinese)  
Service-Oriented Architecture (SOA) has drawn significant attention recently, and numerous architecture approaches have been proposed to represent SOA-based applications. The architecture of SOA-based applications is different from traditional software architecture, which is mainly static. The architecture of an SOA-based application is dynamic, i.e., the application can be composed at runtime using existing services, and thus the architecture is really determined at runtime, instead of design
more » ... ime. SOA applications have provided a new direction for software architecture study, where the architecture can be dynamically changed at runtime to meet the new application requirements. This paper proposes a Process-Embedded Service-Oriented Infrastructure to build SOA-based applications. This infrastructure embeds the entire software lifecycle management and service-oriented system engineering into the application developed on this infrastructure. Thus, the users can easily re-develop the applications during operation to meet the changing environments and requirements, through the supports provided by the embedded infrastructure. Recently, several studies have focused on dynamic software architecture, i.e., the software architecture that modifies its structure during execution [13] . The current research focuses on the formal specification techniques that can be used to reason and analyze dynamic architectures. A variety of reconfiguration rules such as graph rewriting rules, process algebra (such as CCS and CSP), predicate calculus, and architecture modification language (AML) [19] have been proposed to specify and analyze dynamic architectures [13] . However, these studies have not focused on the dynamic SOA yet. One significant difference between the existing dynamic architecture and SOA is that the dynamic architecture of SOA is fully integrated with many aspects of software development, such as service composition, code generation, and deployment.
doi:10.1360/jos171470 fatcat:lagt7pc7gzbhtigz2p4tcinmgi