SOA Foundation Product Line: Product Structure

Layered Structure of Systems Built with SOA

SOA systems enhance flexibility and reusability through process and service layers. This approach requires new initiatives in the process and service layers compared to traditional system construction.

Diagram Description: A layered architecture diagram illustrating the SOA system structure. Layers include: Presentation Layer (User Interface), Process Layer (Composite Services), Service Layer (Primitive Services), Application Layer (Application), and Data Access Layer. It also shows the SOA Planning Phase (UI Design) and SOA Construction Phase (UI Development, Business Process Modeling, Business Process Development, Service Development).

NEC's SOA Foundation Product Line Structure

This product line comprehensively supports the realization of SOA, from business modeling to development, operation, monitoring, and analysis.

Diagram Description: The "Active Globe Process Convergence" suite is presented. Key components include Business Process Modeling tools (IDS, ARIS, iGrafx), Modeling, Simulation, Business Process Development, Developer's Studio, Process Definition, Service Definition, System Development, and Service Development. Integration components like Business Portal, BizEngine, WebSAM SECUREMASTER, WebOTX, and System Director are also shown.

Image of Service-Oriented Enterprise Systems

This section describes the realization of highly reliable and high-performance enterprise systems that leverage existing systems and enable continuous improvement of business processes.

Diagram Description: An illustration showing the integration of user interfaces (e.g., Business Portal), workflow, repository, business process integration, and a service bus connecting various backend systems (CRM, ERP, ACOS, RDBMS). Key benefits highlighted are integrated user interfaces, rapid development environments, real-time business process monitoring and analysis, business process automation, flexible system integration, and single sign-on (SSO) for inter-system authentication.

Flow of Service-Oriented Enterprise System Construction

Flow of Service-Oriented Enterprise System Construction: Role Division and Support Tools

The process flow for service-oriented enterprise system construction is outlined:

1. Business Process Modeling
2. Service Modeling
3. Application Development (Execution Process Model Creation, Service Creation)

Roles involved include Business Planning Staff, Business Design Staff, IT Architect, and System Developers. Screenshots of modeling tools (ARIS, iGrafx) and development tools (System Director, Developer's Studio) are presented.

Previous Flow of Enterprise System Construction

Previously, the process of creating execution processes by referencing modeling results during the system development phase was inefficient.

Diagram Description: A comparison showing the older, less efficient method involving manual documents and drawing tools versus the current, more efficient approach using tools like System Director and Developer's Studio.

Integration with Business Modeling Tools

The ability to import BPEL (Business Process Execution Language) output from modeling tools like ARIS and iGrafx enables seamless development from business process design to service construction and verification.

Diagram Description: This diagram illustrates the integration flow. Output from ARIS/iGrafx (modeling results, BPEL1.1) is fed into the BPEL Editor within System Director/Developer's Studio. Features include conversion to BPEL2.0 and an editor for defining the latest business process definition language.

BPEL Definition: BPEL (Business Process Execution Language) is an XML-based description language standardized by the OASIS consortium, used to define how business processes are combined.

System Construction Flow 1

The steps for system construction are:

1. Visualization and Analysis of Business (Business Process Modeling)
2. Derivation of Services (Service Modeling)
3. Execution Process Skeleton Creation (Execution Process Model Creation)
4. Modeling Data Integration (Execution Process Model Creation)
5. Execution Process and Service Creation
6. Execution

Business Process Modeling (ARIS Example)

Diagram Description: An example of business process modeling using ARIS. It displays process hierarchy, business scenarios, and detailed business processes, illustrating their relationships with strategy, organization, application, and data, including assignments.

Business Process Modeling (iGrafx Example)

Diagram Description: An example of business process modeling using iGrafx, showing a business process diagram within the iGrafx interface. This process visualizes organizational relationships and workflows, aiding in determining the scope of system implementation.

System Construction Flow 2, 3

This section reiterates the system construction steps, emphasizing Service Modeling and Execution Process Skeleton Creation.

Execution Process Skeleton Creation (ARIS Example)

Diagram Description: This diagram illustrates the transformation from a business process (ARIS) to a system process model, and then to a BPEL process model. It details the extraction of services and the systemization of process flows.

Execution Process Skeleton Creation (iGrafx Example)

Diagram Description: Similar to the ARIS example, this shows the transformation from a business process using iGrafx/BPMN notation to a system process model (execution level) and then to a BPEL process model. BPMN (Business Process Modeling Notation) is a notation rule for clearly illustrating and visualizing business procedures, standardized in May 2004.

System Construction Flow 4

This section reiterates the system construction steps, emphasizing Modeling Data Integration.

Integration of Modeling Tools with BPEL

Seamless development is achieved through the integration of modeling results.

Diagram Description: This diagram shows the integration flow from ARIS/IDS output to System Director Developer's Studio. It also depicts the conversion of iGrafx output (BPEL4WS1.1, WSDL1.1) to WS-BPEL2.0. Key features include the ability to convert and read modeling results into BPEL2.0 and an editor for defining the latest business process definition language.

BPEL Editor Functions

The BPEL Editor provides a seamless development environment from business process design to service construction and verification.

Diagram Description: The System Director Developer's Studio interface is shown, highlighting sections for Business Process, Detailing, Service Construction, Integration, and Verification.

Key Functions:

• WS-BPEL Process Design: Defines partner and service integration via Web service interfaces using workflow descriptions. Utilizes graphical tools for structured activity design.
• Input Assist, Source Formatting: Assists in XML editing by completing XML tag names and inserting indentation.
• Template Function: Allows adding created business processes as templates for management.
• Verification Function: Verifies WSDL structure, WS-I compliance, and executability in BizEngine/BPEL within the development environment, improving development efficiency.

BPEL Integration ~ Screen Details (ARIS Example)

Diagram Description: This section maps the output from the ARIS modeling tool to the BPEL editor in System Director Developer's Studio. It demonstrates how BPEL process skeletons created with modeling tools can be used to create execution processes.

BPEL Integration ~ Screen Details (iGrafx Example)

Diagram Description: This section maps iGrafx/BPMN notation to the BPEL editor in System Director Developer's Studio, illustrating the process of creating execution processes from BPEL process skeletons.

System Construction Flow 5, 6

This section reiterates the system construction steps, emphasizing Execution Process and Service Creation, and Execution.

Development of Execution Processes and Services

System Director Developer's Studio is used for process creation, registration, execution, and service creation, testing, and deployment.

Processes are completed by defining attributes and compensation handling based on the BPEL process skeleton. Existing logic is web-enabled, tested, and deployed.

Diagram Description: Shows the System Director Developer's Studio interface for creating, registering, and executing processes, as well as creating, testing, and deploying services.

Execution Image

Diagram Description: An illustration depicting a business scenario involving the Sales Department, Product Department, and BTO Department. It shows the flow of data and services, integrated via a corporate portal and business process integration, demonstrating the practical application of the described concepts.