Success By Design & Practice (Book Summary)

Objective

Objective

The chapter objective is how the Author is practising system database schema design

to enterprise robust database engine for cloud computing architecture to reduce the

cost of development.

Introduction

Over a period, the Author has designed templates for integrated databases preparing

to run the software in the cloud architecture for multi-locations.

To reduce the cost of a software project, the Author has developed a template for defining a database engine for cloud architecture.

Database Engine design based on System study for Cloud Computing Architecture

modelling.


Success by Design & Practice


Business Data Processing Engine Overview in the cloud

The engine shows the components in the database engine deployed in the cloud. The significant features are Tables & Tables & attributes, Processes, Workflow, Functions

&

Procedures, Scheduled Scripts, Events, and Security. These components (Using

RDBMS objects) will take care of business processes mapped in the engine. The

engine will also maintain the Processing Log.

The SQL and PL/SQL are used for defining the functionality of the component. To

understand the functionality of the features, any third-party tool can be used (without

any change in the engine).

The engine provides Business Intelligence (BI) graphs from OLAP (Online analytical

processing) cube in the cloud, as shown below.

BI (Business Intelligent) Graphs (Bar Chart, Tree Map, and Location-wise in the Bing

map) show the percentage of all India sales branch-wise.


The author always considers at the time of Database Engine designing based on data,

information flow and feedback mechanism with documentation of the engine.

For designing database schema and database engine, ICOM methodology is used,

where (I) is input (C) control (Audit and control) of input (O) output for the following

process, printer, screen, and send through communication and (M) mechanism to

process data.


Success by Design & Practice

The following diagram shows a sample Purchase and Inventory ICOM diagram. The

chart will be handy at the time of backend and (UI) user interface programming.


As shown above, as a template, the author always practices ICOM methodology for

designing the Business Data and Information flow.

The DFD level – 1 and DFD level – 2 are also defined for tables' logical and physical

design as per ICOM methodology.

Example:


Success by Design & Practice

For Example, Inventory and Purchase ICOM


Success by Design & Practice


The author believes:

Based on a clear understanding of the business processes, the schema should be

designed as per the algorithm. The author also believes the database engine in the cloud

should be robust and cost-effective using the latest technology.

The engine should be designed to provide a process log, Business intelligence (BI),

Audit & control report and feedback mechanism.

Business Data Processing Engine Overview in the cloud.

The engine overview is shown in the form of components available in the engine. The

significant features are Attributes of tables, tables with a relationship with ER diagram,

Processes, Workflow, Functions & Procedures, Scheduled Scripts, Events, and

Security. These components will take care of business processes mapped in the engine.

The engine will also maintain the Process Log.

The SQL and PL/SQL are used for defining the functionality of the component. To

understand the functionality of the details, any third-party tool can be used (without

any change in the engine).

The Engine provides business processed data, available in an OLTP (Online

Transactional Processing) cube. After processing, the OLAP cube (Online analytical

processing) will provide reports and BI (Business Intelligence) Graphs and reports for

operation level to top management.

Author Business Data Processing Engine

There is always a need for matured software engines, which can be used for business data Processing. Keeping in mind Processing Engine requirements.

 The Business Processes are mapped with Data Input Capabilities, Output Capabilities,

 Processing Capabilities, and Audit & Trail capabilities. Engine ROI is also calculated.

Chapter – 2 provides examples of using the Integrated Business Application Software development engine.

RDBMS (ORACLE / Microsoft SQL Server)

The engine is designed in (ORACLE / SQL Server) RDBMS and deployed in cloud architecture. The Database Engine is packaged with Tables & Constraints, Functions

& Procedures, Triggers, Views, and Sequencers. The engine will take care of business processes as per chapter - 1.