discuss about making a project http://sif.uin-suska.ac.id/ http://fst.uin-suska.ac.id/ http://www.uin-suska.ac.id/

1. MANAGEMENT PROYEK
PROJECT
Developing Academic Information System of
SMAN 1 Benai
GUSFA LEO FIRNANDO
Program Studi S1 Sistem Informasi
Fakultas Sains dan Teknologi
Universitas Islam Sultan Syarif Kasim Riau
http://sif.uin-suska.ac.id/
http://fst.uin-suska.ac.id/
http://www.uin-suska.ac.id/

2. Project Chapter
Project Name : Establish Academic Information System of SMAN 1
Benai
Project Start Date : January 23, 2017
Completed Project Date : June 12, 2017
Project Manager : Misriadi
Analys : Gusfa Leo Firnando
Programmer : Arta, Affan Noer
1. INTRODUCTION

3. Project Objectives
build an academic information system at SMAN 1 Benai that can provide technology and
information related to academic at SMAN 1 Benai which includes new student enrollment,
teacher data storage, active student data storage and alumni students per force, and so forth.
Thus it can provide convenience and advantages for the school and also students / i. The project
starts with analyzing existing system processes, designing systems, designing computer network
architectures to be used, network testing, to system implementation. This project will be done for 5
months with estimated cost of Rp. 7,000,000.00, -

4. The following are some of the critical success factors of the project:
Determinants of Success
Commitment and support from the management.
The availability of human resources in accordance with
their respective competencies.
Commitment and support of the project team
Good cooperation of all parties in accordance with their
respective competencies
Continuity of project implementation.
Discipline implementation in accordance with the project work
plan.
Good and complete project documentation ..
The availability of all project support facilities is appropriate
and adequate.
Good cooperation of all parties in accordance with their respective competencies

5. Expected Benefits
From the school side:
 Provide wider and faster information access to students.
 Improve the quality of education in SMAN 1 Benai.
From student / i:
 Improve the effectiveness of learning from the circulation of knowledge of technology and
information.
 Supporting educational facilities for students of SMAN 1 Benai.

6. 2. APPROACHES IN PROJECT MANAGEMENT
Stages of the Project Approach
o Analysis of the needs of computer users, hardware and software to be implemented.
o The design of computer network architecture.
o System development.
o Test computer network connectivity.
o Develop project cost estimation for implementation.

7. 3. COVERAGE OF PROJECT
The academic information system project is a project to build an
academic information system and design a computer network
system in the environment of SMAN 1 Benai. The system to be
implemented is a LAN network system (Local Area Network).

8. a. Specification of Functional Requirements
From the analysis needs of SMAN 1 Benai and the use of computers, required a LAN network
system. Here in is a list of system functional requirements needed campus and also its users (server
computers, client computers).
Function Name Description
Server Computer
To manage all activities performed by the admin, where data is entered
issued will be stored and managed on the server computer.
Computer Client
For use by the user as a means of delivering information and teaching
learning by students / i.

9. b. Non-Functional Requirement Specification
The following is a list of non-functional requirements of academic information
system of SMAN 1 Benai:
No Non-Functional Needs
1
All applications required in learning activities must be provided
on every computer.
2 The computer used must be of the best quality and speck.
3 Network connectivity should be quickly accessible.
4 The computer used should be safe for use by the user.

10. Description of Project Scope
 The device that will be used in this project is hardware, and other supporting software in SMAN 1
Benai.
 The modules developed include: network connectivity, network architecture, and reports required
when there are additions or complaints from the modules we develop.
 The network model used by LAN network, so that all existing connections can only be used in the
environment of SMAN 1 Benai.
 Academic information system is built by using PHP, mysql and xampp programming languages.

11. Submission of Project
Outputs that will be included in this project are reports of system malfunction, network
performance decryption, and others.
Criteria for Project Acceptance
Team pegembang will perform network testing in the final stages, after the installation of
applications on the server computer or client is done. In addition to testing from the developer, this
final test will also be performed by the client in this case is the SMAN 1 Benai, and if everything is
considered sufficient and can be smoothly then it will be submitted to the SMAN 1 Benai.

12. Limitations
 The information system built is academic information system of SMAN 1 Benai.
 The features that will be displayed on the system is home, student enrollment / i, teacher
menu, student menu, alumni menu, about.
 Applications are built using PHP, mysql and xampp programming languages
 Network system built using LAN network system.
 Internet access is only provided around the environment of SMAN 1 Benai.
 Restrict access to excessive bandwidth usage that can harm the SMAN 1 Benai.

13. 4. SCHEDULE OF PROJECT IMPLEMENTATION
Jadwal Tanggal
Mulai proyek 23 Januari 2017
Analisa sistem yang ada 25 Januari 2017
Project charter ditandatangani 27 Januari 2017
Proposal disetujui 27 Januari 2017
Perekrutan tim proyek 03 Februari 2017
Hasil analisa sistem disetujui 10 Februari 2017
Pembuatan laporan 28 Januari – 05 Juni 2017
Membangun sistem 15 Maret 2017
Penerapan instalasi jaringan komputer 17 April 2017
Penerapan Instalasi OS pada komputer server
dan client
02 Mei 2017
Testing jaringan 19 mei 2017
Seminar 10 Juni 2017
12 Juni 2017

14. 5. CHANGE MANAGEMENT PLAN
In the course of a project, there is almost always a demand for change. To anticipate this, it is
necessary to prepare a procedure. The procedure for controlling changes in a project is often called the
Change Control Procedure.
Any approved modifications or changes to the project schedule and cost should refer to the following
procedures:
• Submission of changes may come from each team member when necessary, especially for changes
that will affect the schedule and scope of work.
• Approval on the change request form indicates approval of changes to the schedule.
Change Control Procedures

15. CONTINUE..
Submission of Changes
 A change can be submitted to the project manager through formal communication (regular meetings) or non-
formal (other communications).
 Fill out the change request form.
 Every change is recorded on the change request note.
Monitor Perubahan
 When the change request form has been approved, work can begin.
 The project manager will change the project schedule or work plan to accommodate the agreed changes and present
them in the project progress meeting for approval.
 Progress in change control will be reported in project meetings, the project manager must sign the change request form
if the change has been completed.

16. 6. COMMUNICATION MANAGEMENT PLAN
Communicating Planning
Communication planning outlines the need for regular communication
among team members involved in the construction of the academic
information system development project of SMAN 1 Benai. Communication
should not be done formally, communication can be done openly and
informally to facilitate knowledge transfer between all parties involved /
interested

17. Preparation for the Meeting
Distributing the agenda of the meeting, at least one day before the meeting,
discussion of topics in order of importance begins with easy topics and each topic is
allocated time.
 Distributing meeting materials, agenda, as well as location and time information.
 Each member of the project team is responsible for preparing, attending and
participating actively in meetings.
 Leaders of meetings and facilitators ensure meetings are on track and effective, so
meeting objectives can be achieved.
 The meeting leader will appoint a notary to make the meeting documentation and
distribute appropriately.

18. Continue....
The meeting discussed at least the following topks:
 Activities that will soon be done
 Review of change controls

19. 7. PROJECT TEAM DIRECTORY
Nama Posisi Email Telephone
Misriadi Project Manajer adipangean1@gmail.com 082144991000
Gusfa Leo
Firnando
Analisa Perancangan
dan training operator
Gusfaleo13@gmail.com 085216422219
1. Arta Utama
2. Affan Noer
Konfigurasi server,
setting router, switch
dan hub
1. Artautama23@gmail.com
2. Akagami767@gmail.com
1. 082384455454
2. 085296780785

20. 8. MANAGEMENT PLAN COST
The project will use accepted value metrics to track and manage costs and the cost basis provides the
basis for reporting, tracking, and managing costs. The cost breakdown for the project to build the
academic information system of SMAN 1 Benai covers all budgeted costs for the successful completion of
the project. The details of the cost as follows:
Jenis Pengerjaan max Type Fee
Base
Calender
Project Manajer 100% Work 90.000/hari
Analisa Perancangan dan
Training Operator 100% Work 80.000/hari
Konfigurasi server, Setting
Router, Switch dan Hub 100% Work 75.000/hari

21. 9. MANAGEMENT PLAN CREATION PROJECT
Project scope management is the management of processes for defining and
controlling what is included and not included in the project. Implementation of the project
and all stakeholders should have the same perception of the outcome of the project and
the process that will be undertaken in making the project outcome. Project scope
management processes include:

22. Continue ..
1. Project initiation: the initial process of the project or the transition from one stage to the
next.
2. Planning coverage: the creation of documents to be used as the basis for decision making
in project implementation.
3. Screen definition: details of the final project result into smaller and more manageable
component parts
4. Verification of coverage: a formal process of approval of project coverage
5. Control of coverage changes: process control over changes in project scope.

23. COMPLETE
THANK YOU