CEF Platform Architecture

The CEF Platform Architecture is a reusable component of Cloud ERP Product Architecture. The platform is defined as a common foundation of the Cloud ERP Product, which is based on the Serviced Oriented Architecture Layer model. For the case of Cloud ERP, three types of platform will be proposed, those are platform as

user platform, system architecture platform, and lastly platform as the foundation component. Each type of platform carries a significant importance to the CEF Model as it ensures the type of product to be released.

4.4.2.1 Platform Component Objectives

i. Promote Reusability using object oriented and service oriented approach. ii. Promote Systematic Layer Model for Structured Programming.

iii. Promote Standard interface through single sign on use portal.

4.4.2.2 Platform Core Model Elements

Platform Architecture core model elements deals with the different type of platforms in the overall architecture. The core model elements are User Portal Platform, Software Architecture Platform, and Backup/Redundancy.

4.4.2.2.1 User Portal Platform

The CEF Model does not dictates the user portal platform features. However, the feature diagram shown in Figure 4.7 is recommended for management standardization and simplicity. The User Portal Platform is important element as it will provide user accessibility to the modules defined in the previous section. Users should be able to access the assigned modules as well as other features in the provided platform. User management, security management, and accessibility management are also able to be conducted in the User Portal Platform.

Figure 4.7 User Portal Platform Feature Diagram

4.4.2.2.2 System Architecture Platform

System Architecture Platform represents the architectural layer of programming services by functionality. In order for all Cloud ERP system modules to perform consistently, the software architecture platform is made to define the services layer by functionality as defined in Figure 4.8.

Figure 4.8 Software Architecture Platform Example

From the top are the user interface layer, system business object layer, foundation and built-in services layer, transaction and error log layer, access control layer,

security layer, data connectivity layer, and data source layer. Each layer has its own role, as defined in Table 4.7.

Table 4.7

Software Architecture Platform Layers

Layer Functionality Description

User Interface Layer System user interface using browser, mobile interface. System Business Object Layer System object connecting user interface layer to the

database. Each system object should provide services using transaction code for each event.

Foundation and Built-In Services Layer Common services defined by platform accessible to all system and built-in services.

Transaction and Error Log Layer

Records all successful transaction events and failed transactions into error logs.

Access Control Layer User accessibility services to manage user control. Security Layer User defined security measures in terms of connectivity

protocol.

Data Connectivity Layer Manage data source accessibility, scripts and passwords connecting system to the data source layer by creating connectivity ID for programmer’s reference.

Data Source Layer Manage database, text file, XML files connectivity by giving specific ID to each data source.

4.4.2.2.3 Backup / Redundancy

As Cloud ERP manage critical data for any organization, our CEF Model recommends a built-in data redundancy model to be integrated within the Cloud ERP platform. This can be achieved by having multiple instance of system and data distributed across multiple location. The system should provide real time replication between the primary and secondary system. In the event of disaster, the fail over process can be done by making the secondary system as the production system. The

primary system will be the publisher and the secondary system will be the subscriber as shown in Figure 4.9.

Figure 4.9 Example of Cloud ERP Redundancy Architecture

4.4.2.3 Platform Design Guidelines

Table 4.8 shows the design guidelines for the CEF Product component.

Table 4.8

CEF Platform Design Guidelines

No. Guidelines Model Element

1 User portal platform should be able to host all Cloud ERP modules. User Portal Platform 2 Developer platform should clearly separate all layers for scalability. System Architecture

Platform 3 System security and redundancy should be part of the overall

system security built in features.

Backup / Redundancy 4 Each platform’s functionality should work as a service object

within the platform’s layer.

System Architecture

Platform 5 All system modules should define their services with transaction

codes.

System Architecture Platform

Table 4.8 continued

6 All transaction should be captured in the transactions log. System Architecture Platform 7 All transaction services should define possible error logs. System Architecture

Platform 8 All system modules should provide debug features. System Architecture

Platform 9 Platform should provide multi-tenancy control for all system

modules.

User Portal Platform 10 All transaction must go through security layer object. System Architecture

Platform 11 All transaction must go through data connectivity layer object. System Architecture

Platform

12 Define audit methods. NA

4.4.2.4 Platform Summary

In summary, the Platform Architecture should be able to provide a structured method for the products developed by the factory. The implementation for the CEF Platform model can greatly improve the problems with security concerns within the Cloud Computing deployment method. Each element contributes to the ability of the platform to handle all the products as well as the security element needed for the platform to be secured.