Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.2 Flowchart
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.
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.
(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.
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
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.
11
12
13
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.
14
15
16
17
18