1

CHAPTER 3: SYSTEM DESIGN

3.1 System Architecture

Fig 1: System Architecture

The above figure 1 shows the overall architecture of our system. The input parameters

for the system are the tables and views provided. And, the output are real time

information and visualizations provided by the BI Dashboard. At the center of the

system lies PHP (CI framework) that manages all the interaction with other components

of the system. The data repository used in our system is MySQL. Data are queried

through PHP server script and occasionally data are inserted or modified or deleted

2

from the database using PHP codes. Various core BI components are designed and

implemented using PHP and front end framework (twitter bootstrap). The major BI

modules implemented are Enterprise Resource Management, Warehouse Management,

HR Management, Customer Relationship Management and Product Lifecycle

Management. The major functionalities that the system provides are user access and

security, transaction updates, data analytics, planning, budgeting, forecasting and report

generation. PHP interacts with R programming language to implement different mining

parameters and to visualize the aggregated data.

3

3.2 Flowchart

Fig 2: System Flowchart

4

The figure 2 above shows the Flowchart of the system. It shows the overall workflow

and processes of the system. Initially a webpage is viewed by the user. If the user is not

admin or member then the user can just view the webpage and forum of the system or

can signup to be the member. Members of the system can login using their credentials

and view dashboard, make predictions and access feature of data visualization. Admins

can access to the additional features such as User Management, CMS Management,

Topic Deletion and Replying to Mail. The relation between the major processes can be

seen in the flowchart above in form of ordered blocks.

5

3.3 Sequence Diagram

Fig 3: Sequence Diagram

6

The figure 3 above shows the sequence diagram of the system. It shows the interaction

of objects involved in the system and the sequence of the message exchanged between

the objects. It shows object interaction arranged in time sequence. As shown by the

diagram, the system consists of 5 different objects: Guests / User / Admin, EPM

Webpage, BI Dashboard, Data Integrates and Database. It shows the exact sequence of

the activities when a user interacts with the EPM system. Initially user visits webpage

and upon his authentication the application automatically provides interfaces with the

database and relevant views to generate required data. The only task user has to do is

to observe and interpret the results prior to finally logging out to the application.

7

3.4 Use Case Diagram

Fig 4: Use Case Diagram

The figure 4 above shows the use case diagram of the system. It shows how the external

factors interact with the system. Admin, Guest and User are the three external factors

8

(actors) that interact with the EPM system. Guest simply can view the website and

forum of the system. Viewing forum includes viewing of topic / replies, creating the

topic and Replying to them. User authentication are done by the system on the basis of

which users and admins are authenticated. The user is able to view forum, make

predictions and view reports. While making predictions data aggregation and result

integration are done. Data summarization is done as per requirement while viewing

reports. Admin is able to delete topic, manage user, manage CMS and respond to mail.

The diagram simply is the representation of an actor's interaction with the system and

the specific roles played by them.

3.5 Data Flow Diagram

3.5.1 Context Diagram (DFD Level 0)

Fig 5: Context Diagram of the System

9

The figure 5 above shows the context diagram of the system. It shows high level view

of the data flow in the system in terms of simple exchanges. EPM system interacts with

Admin, Users and Guests, major external entities of the system. Admin is responsible

to manage the user, control CMS (Content Management System) and configure

application and database of the system. EPM system then generates User report,

changes CMS accordingly, and generate application and database status to the admin.

User can login and provide analysis parameters to the system. EPM system provides

connection and generates report to the user. Guests can Login or Signup and see the

general information of the system. EPM system gets information about guest and

respond accordingly. In addition, the system also prove Forum and FAQ features to its

Users and Guests. It is data that flows throughout the process regardless of the way the

interaction between the system and external entities takes place.

10

3.5.2 DFD Level 1

Fig 6: DFD Level 1

The figure 6 above represents a Level 1 DFD which shows the overall flow of data in

the system. The system mainly consists of 3 major actors: User, Admin and Guest

(Viewer) and 5 major tables: User table, Forum table, CMS table, Module Table and

Data Store Table. User can login, view dashboard, view module, view forum, visualize

data and update data on Data store table. Admin can perform all the task the user can

along with additional tasks such as User Management, CMS Management and Deletion

11

of topic on forum. Guest can login if account is present or simply signup for new

account. The application aggregates the database and provides the aggregated result for

report generation.

3.5.3 DFD level 2: Login process

Fig 7: DFD Level 2 (Login process)

The figure 7 above shows the level 2 DFD diagram of login process. The login process

simply involves passing of login parameters by the user, then the login parameters are

corroborated with the user information stored in User table database. If the login

parameters are validated a System Dashboard is opened else Error message is displayed.

12

3.5.4 DFD level 2: View Dashboard process

Fig 8: DFD Level 2 (View Dashboard process)

The figure 8 above shows the level 2 DFD diagram of View Dashboard process. The

view dashboard process involves loading of modules in Dashboard of the application.

When the user login and access to dashboard, controller command required to load

models are sent to the open database. If all the modules are loaded then the dashboard

is loaded in the webpage, else error message is displayed.

3.5.5 DFD level 2: View Module process

13

Fig 9: DFD Level 2 (View Module process)

The figure 9 above shows the level 2 DFD diagram of View Module process. The view

module process involves viewing of modules necessary for Data visualization and

updating of data by the user. When the user passes parameters to Data visualization

process by selecting sub modules, reports and graphs are generated and when the user

passes the update queries by selecting sub modules, updation reports are generated.

Failure to do so displays an Error message.

3.5.6 DFD level 2: Update data process

Fig 10: DFD Level 2 (Update Data Process)

The figure 10 above shows the level 2 DFD diagram of Update Data process. The

update data process involves updation of data in the database by the user / admin. In

this process particular data to be updated is selected initially by passing search query.

14

Once the data is selected, a new data is entered and submitted to the Update process by

passing update query in Module table. Failure to do so displays an Error message.

3.5.7 DFD level 2: Data visualization process

Fig 11: DFD Level 2 (Data visualization process)

The figure 11 above shows the level 2 DFD diagram of Data Visualization process. The

data visualization process involves designing of data visualization. In this process, user

/ admin selects records that are later aggregated and integrated. Such aggregated data

are sent as parameters to R for retrieving an information. Then the information retrieved

from R are displayed as results in form of reports or graph. Failure to do so displays an

Error message.

15

3.5.8 DFD level 2: User management process

Fig 12: DFD Level 2 (User Management process)

The figure 12 above shows the level 2 DFD diagram of User Management process. The

user management process involves the addition and deletion of the users by an admin.

In this process, admin view users detail by passing selection parameter to user table and

creates new account by passing insert query to user table. Admin can also delete user

and revoke permission of the user by passing update / delete query to user table and

accept the member request as well.

16

3.5.9 DFD level 2: CMS Management process

Fig 13: DFD Level 2 (CMS Management Process)

The figure 13 shows the level 2 DFD diagram of CMS management process. The CMS

management process involves the management of the content of the system by an

admin. In this process, admin update contents of CMS tables by passing new layout

data in an update query. Failure to do so displays an Error message.

17

3.5.10 DFD level 2: Forum process

Fig 14: DFD Level 2 (Forum Process)

The figure 14 above shows the level 2 DFD diagram of Forum process. The forum

process involves Creation of topics, viewing of topics, replying to the topics and

deletion of the topics. In this process, User / Guest can only Create, View and Reply to

the topic while admin can delete the topic as well. Topics are created and replied by

passing insert query and are viewed by passing select query to forum table by admin /

users. Admin deletes the topic by passing delete query to forum table.

18

3.5.11 DFD level 2: Signup process

Fig 15: DFD Level 2 (Signup process)

The figure 15 above shows the level 2 DFD diagram of Signup Process. The signup

process involves creation of new users by an admin. In this process, Guest initially

submits the signup form and waits until accepted by an admin. Once the admin accept

the request insert query is passed to user tables by an admin. Failure to do so displays

and Error message.