Faculty of Science COMP3770/6770: EIS Implementation Project Report

Verified

Added on  2022/09/22

|11
|1231
|33
Project
AI Summary
This project report details the implementation of an Executive Information System (EIS) for the CEO in Aklan. It includes the project's deliverables, such as a Gantt chart, network diagram, and resource graphs. The report determines project aspects, including the scope, duration, and critical path, and discusses the project approach, including costing, timeframes, and staff allocation. The project aimed to provide the local chief executive with better reports for crucial decisions, transitioning from a manual process to an EIS for acquiring important reports with proper user account permissions. The project was completed within 82 days at a cost of $223,000.
tabler-icon-diamond-filled.svg

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Running head: IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
Implementing an EIS for the CEO in Aklan
Name of the Student
Name of the University
Author note
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
Table of Contents
1. The Deliverables for the Project..................................................................................................2
1.1 Gantt chart.............................................................................................................................2
1.2 Network Diagram..................................................................................................................2
1.3 Resource Graphs....................................................................................................................3
2. Determining Project Aspects.......................................................................................................6
2.1 The Project Scope..................................................................................................................6
2.2 Project Duration and its Calculation......................................................................................6
2.3 Critical Path for the Project...................................................................................................7
2.4 Discussion on Project Approach............................................................................................8
References......................................................................................................................................10
Document Page
2IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
1. The Deliverables for the Project
1.1 Gantt chart
ID Outline
Number
Task
Mode
Task Name Duration Start Finish
0 0 Implementing an EIS for
the CEO in Aklan
82 days Mon
13-04-20
Tue
04-08-20
1 1 Mapping out the present
functionality of the
business
7 days Mon
13-04-20
Tue
21-04-20
2 2 Determining a new
approach for the EIS
Implementation
5 days Wed
22-04-20
Tue
28-04-20
3 3 Approval request for the
EIS Implementation
7 days Wed
22-04-20
Thu
30-04-20
4 4 Documentation of the
technical report
15 days Fri 01-05-20 Thu
21-05-20
5 5 Approval for project start 5 days Fri 22-05-20 Thu
28-05-20
6 6 Development of the EIS
System
16 days Fri 29-05-20 Fri 19-06-20
7 7 Testing for system errors
and quality checks
20 days Mon
22-06-20
Fri 17-07-20
8 8 Documentation and
Handing over the system
12 days Mon
20-07-20
Tue
04-08-20
Administrative Staff
Business Analysts
Administrative Staff
Administrative Staff
Database Administrators,Project Manager
Software Engineers,System Developers
Software Engineers,System Develope
Administrative Staff
M T W T F S S M T W T
22 Mar '20 26 Apr '20 31 May '20 05 Jul '20 09 Aug '20
(Figure 1: The Gantt chart for the Project)
(Source: Created by author)
1.2 Network Diagram
Implementing an EIS for the CEO in Aklan
13-04-20 21-04-20
Dur: 7 days Slack: 0 days
13-04-20 21-04-20
22-04-20 28-04-20
Dur: 5 days Slack: 2 days
24-04-20 30-04-20
22-04-20 30-04-20
Dur: 7 days Slack: 0 days
22-04-20 30-04-20
01-05-20 21-05-20
Dur: 15 days Slack: 0 days
01-05-20 21-05-20
22-05-20 28-05-20
Dur: 5 days Slack: 0 days
22-05-20 28-05-20
29-05-20 19-06-20
Dur: 16 days Slack: 0 days
29-05-20 19-06-20
22-06-20 17-07-20
Dur: 20 days Slack: 0 days
22-06-20 17-07-20
20-07-20 04-08-20
Dur: 12 days Slack: 0 days
20-07-20 04-08-20
Mapping out the present
functionality of the
business
Determining a new
approach for the EIS
Implementation
Approval request for the
EIS Implementation
Documentation of the
technical report Approval for project start Development of the EIS
System
Testing for system errors
and quality checks
Documentation and Handing
over the system
(Figure 2: The Network Diagram for the Project)
(Source: Created by author)
Document Page
3IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
1.3 Resource Graphs
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
Document Page
5IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
Document Page
6IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
(Figure 3: The Resource Graphs for the Project)
(Source: Created by author)
2. Determining Project Aspects
2.1 The Project Scope
The project is focused on the discussion of an existing kind of manual working process
within the agency. It further aims towards providing a detailed aspects based on which the local
chief executive would be able to obtain better reports for making crucial decisions for the
agency. The reports are currently being performed in a manual process. Thus, the project is based
on the proposing of an Executive Information System (EIS), which would be necessary for
acquiring important reports with proper permissions from user account.
2.2 Project Duration and its Calculation
The figure 1 describes the Gantt chart diagram and the time that has been taken for the
completion of the project. In this case, it has been seen that the project would be completed
within 82 days. In order to calculate the time frame of the project completion, it can be seen that
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
there has been an allocation of project activities and the related number of days that would be
required for each concerned activity.
Hence predecessors has been determined accordingly to the ways in which each activity
needs to be followed next after completing of any single activity. Based on setting of
predecessors, the activities have been aligned accordingly. In the next part, resources are listed
for the project. These are assigned with costs according to their needs.
Resources are further allocated for each activity included within the project. They are
allocated to each activity based on their needs towards the project works. In the next part, costs
are automatically added within the Gantt chart since in the previous parts resources were
assigned to particular project costs.
2.3 Critical Path for the Project
(Figure 4: The Critical Path for the Project)
(Source: Created by author)
The calculation for finding the critical path for the project is calculated as follows:
Path 1: B-C-E-G-H-I Length = 7 + 15 + 5 + 16 + 20 + 12 = 75 days
Path 2: A-D-E-F-H-I Length = 5 + 15 + 5 + 16 + 20 + 12 = 73 days
Document Page
8IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
The critical path is considered as the longest path, which would be detected within the
network diagram. In the above figure, it can be seen that Path 1, B-C-E-G-H-I, is the critical path
for the project.
2.4 Discussion on Project Approach
The costing over the entire project have been determined based on the allocation of total
cost for the project. The total costs of the project had been estimated at $250,000. Based on
understanding the limitations towards the project on the cost factor, each of the resources were
divided cost accordingly. It was also kept in mind that the entire cost of the project should not
exceed than the limited budget available.
On the other hand, timeframes for the project were based on determining the time that
could have approximately taken for each underlined activity. In the case of the concerned
project, the activities have been underlined as per the needs of the project and related works.
Hence, an estimation of days that could be allocated for each activity was planned in such a way
that the project would be completed in a limited time period. In the description of the concerned
case, it was mentioned that the project need to be completed by the early of October 2020. These
activities were planned accordingly so that the project could be completed within the given time
range. Hence, the concerned project has been completed in August 2020.
On the other hand, the staff allocated for each activity were being planned and set as per
the needs of the various activities. The different staff in relation to the project are: Project
Manager, Business Analysts, System Developers, Software Engineers, Database Administrators
and Administrative Staff. The allocation of staff for each activity have thus been planned on
proper understanding of their needs in different activities as might be required for successful
Document Page
9IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
project accomplishment. After the allocation of resources to each activity, costs were
automatically adjusted as per their pre-defined rates, which were defined in the Resource Sheet
in the MS Project software. Thus, from the analysis of the entire project, it can be discussed that
the project had been completed in a period of 82 days by incurring a cost of $223,000.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10IMPLEMENTING AN EIS FOR THE CEO IN AKLAN
References
Corvello, V., Javernick-Will, A. and Ratta, A.M.L., 2017. Routine project scope management in
small construction enterprises. International Journal of Project Organisation and
Management, 9(1), pp.18-30.
Costantino, F., Di Gravio, G. and Nonino, F., 2015. Project selection in project portfolio
management: An artificial neural network model based on critical success factors. International
Journal of Project Management, 33(8), pp.1744-1754.
Duffield, S. and Whitty, S.J., 2015. Developing a systemic lessons learned knowledge model for
organisational learning through projects. International journal of project management, 33(2),
pp.311-324.
Hazır, Ö., 2015. A review of analytical models, approaches and decision support tools in project
monitoring and control. International Journal of Project Management, 33(4), pp.808-815.
Lampa, I.L., de Godoi Contessoto, A., Amorim, A.R., Zafalon, G.F.D., Valêncio, C.R. and de
Souza, R.C.G., 2017, April. Project Scope Management: A Strategy Oriented to the
Requirements Engineering. In International Conference on Enterprise Information Systems (Vol.
2, pp. 370-378). SCITEPRESS.
Sajad, M., Sadiq, M., Naveed, K. and Iqbal, M.S., 2016. Software Project Management: Tools
assessment, Comparison and suggestions for future development. International Journal of
Computer Science and Network Security (IJCSNS), 16(1), p.31.
chevron_up_icon
1 out of 11
circle_padding
hide_on_mobile
zoom_out_icon
logo.png

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]