INTERNSHIP THESIS PROPOSAL ON PT.

PROGRAMA REKA
PIRANTI WEB BASED SCHOOL MANAGEMENT INFORMATION
SYSTEMS OF TZU CHI FOUNDATION

Ignatius Albert

1501144566

Albertus Andika

1501152050

Felix

1501167866

Class / Group: 06 PLM

Universitas Bina Nusantara

Jakarta
2014

INTERNSHIP THESIS PROPOSAL ON PT. PROGRAMA REKA

PIRANTI WEB BASED SCHOOL MANAGEMENT INFORMATION
SYSTEMS OF TZU CHI FOUNDATION

Proposed as a Requirement
For Completion of
Major of Information System
Bachelor Education Degree

Ignatius Albert

1501144566

Albertus Andika

1501152050

Felix

1501167866

Class: 06 PLM

Universitas Bina Nusantara

Jakarta
2014

INTERNSHIP THESIS PROPOSAL ON PT. PROGRAMA REKA

PIRANTI WEB BASED SCHOOL MANAGEMENT INFORMATION
SYSTEMS OF TZU CHI FOUNDATION

Composed by:

Ignatius Albert

Albertus Andika

Felix

1501144566

1501152050

1501167866

Approved by:

Anindito ,S.Kom. MTI.

Lecturer Code: D4631

ii

UNIVERSITAS BINA NUSANTARA

Major of Information System

School of Information System
Thesis
Odd Semester, Year of 2014 / 2015

SYSTEM ANALYSIS AND DESIGN

Ignatius Albert

1501144566

Albertus Andika

1501152050

Felix

1501167866

Class / Group: 06 PLM / 04

Abstract
OBJECT OF THIS RESEARCH, is to design an internship thesis proposal on
PT. Programa Reka Piranti web based school management information systems
that will provide leverage for Tzu Chi School whom need the application to
support the efficiency and effectivity of lerning, teaching, and administration
purposes.
ANALYSIS METHODOLOGY, composed from two methods, which is current
system analysis methodology, supported by recommended system planning
methodology. Current System analysis methodology include direct survey to
Company, interview, and research from literature. System design and
recommendation methodology based on OOAD (Object Oriented Analysis and
Design) written by Satzinger, Jackson, and Burd. Unified Modeling notation.
In the process of creating thesis, we have desire to create web that able and will
provide solution to Tzu Chi School and support the growth of their institution in
more structured manner.
SUMMARY of this research is to be the provide leverage for Tzu Chi School
whom need the application to support the efficiency and effectivity of lerning,
teaching, and administration purposes. We provide solution in form of web based
school management information system.
Keyword
School, absence, registration, information system, reporting, scheduling, asset
management
iii

Preface
We express praise and thanks to one and only God for his blessings and graces so
that we able to finish thesis with title INTERNSHIP THESIS PROPOSAL ON
PT. PROGRAMA REKA PIRANTI WEB BASED SCHOOL MANAGEMENT
INFORMATION SYSTEMS OF TZU CHI FOUNDATION.
The final results of the following Thesis cannot be finished without support and
cooperation. Therefore, we express our deepest gratitude for the aid, cooperation,
and support to:
1. Our parents that support us and always pray for us.
2. Mr. Anindito ,S.Kom. MTI. as Supervisor
3. Mr. Wellie Boenawan as the Information Technology department general
manager on PT. Programa Reka Piranti
4. Lecturer of Binus University that provide us knowledge and support to
author.
5. Friends, which share their knowledge and suggestion for the purpose of
project improvement.
And all people and organization that involved in the process of composing the
Thesis and can not mentioned one by one.
Last but not least, we hope this thesis will provide useful information for the
reader. The author realize, that this Thesis is not perfect and need improvement,
therefore the author will gladly accept constructive criticism and suggestions for
this writing improvement in the future.

Jakarta, May 15, 2014

Author

iv

Table of Contents

CHAPTER 1: INTRODUCTION ................................................................................ 1

1.1.

Background .................................................................................................. 1

1.2.

Scope ............................................................................................................ 2

1.2.1.

Development Environment .................................................................... 2

1.2.2.

Module List ............................................................................................ 2

1.3.

Purpose and Benefit ..................................................................................... 4

1.3.1.

Purpose ................................................................................................... 4

1.3.2.

Benefit for Tzu Ci School ...................................................................... 4

1.3.3.

Benefit for PT.Programa Reka Piranti ................................................... 5

1.4.

Methodology ................................................................................................ 5

1.4.1.

Current System Analysis Methodology ................................................. 5

1.4.2.

Recommended System Planning Methodology ..................................... 5

1.5.

Writing Systematic ....................................................................................... 6

CHAPTER 1: INTRODUCTION

1.1. Background
Tzu Chi is a non-profit social foundation that focus on
instructing rich people and helping poor people. Theyve built
hospitals, schools, and done many charity works by gathering
volunteers from all over the world. Tzu Chis branches has
distributed to over 40 countries and regions in the world. In
Indonesia, Tzu Chi wants to help and reach the kids and give them
not only educational lesson but also humanity lesson.

Tzu Chi conducts its mission via an international network

of volunteers. They are easily recognized by their blue and white
uniforms, often referred to as 'blue sky, white clouds' by
volunteers, and Tzu Chi relief workers have been called "blue
angels" for their uniforms.

Unfortunately, there are not so many schools or foundation

that are urged to move and give services like Tzu Chi does. They try
to create a great educational services and deliver it to people that are
in need. They believe with a help from a system that can optimize
their work, Tzu Chi can spread their services even more.

Thats why we proposed to create the web based school

panel service to help them minimize their workforce, but maximize
their efficientcy in services. We believe that by using this system,
Tzu Chi can focus on other things to improve their educational
services or methods to give something better to the kids.

1.2. Scope
Analysis and design of information systems is limited by the scope
of the following:

1.2.1. Development Environment

Moodle content management system
Adobe Dreamweaver Application

MySQL database

CSS Programming Language

PHP Programming Language

XML programming language

1.2.2. Module List

Registration: For student to register or re-register their

enrollment using digitized form and barcode. This make the
student recored retrival to be fast, more structured, and
accessible.

Re-registration: every new academic year, parent have to re

register and re-fill the form. We made the process simpler
by giving the parents email when the re-registration time is
near that contain barcode. If no student data did not have
any update or changes, parents just need to print and bring
the barcode. If, however there is any changes to the data the
parents will have to correct the data using linked form and
print the generated barcode after finishing the update.

Absence: Absence for employee to measure their clock in

and clock out time. The system will be integrated with
biometric sensor to increase security and improve
authentication process so it will become more accurate.

Extracuricullar: to register, interact, and report the

attendace of students extracuricullar activities

Admin backend: for controlling the data, retrieving report

and altering database.
o Reporting: To show the statistics of teacher and
student attendance and punctuality.
o Scheduling: to schedule subject primary and
substitute teacher in case if the appointed teacher
did not attend the class.
o Assets management: to manage the class assets and
infrastructure such as chair, desk, television,
projector, and so on.

The analysis is about portal system that is being established for

connecting between Client and the company.

1.3. Purpose and Benefit

1.3.1. Purpose
The main purpose of this Thesis project is to improve the
effectiveness of student reports, registration, re-registration,
extracuricullar, and administration process while keeping the
operational cost to minimum by utilizing web based, user
friendly web that scalable, accessible, efficient, and effective.
With this function, Tzu Chi School as PT. Programa Reka
Piranti client can reduce the time needed to manage, register, reregister their student, teacher, and manage the school assets
allocation into the system.

1.3.2. Benefit for Tzu Ci School

Time Effective

Paperless

Reduce queue as their main concern

Minimize staff allocation and mistakes

Reporting module and administrator dashboard thet will

enable the administrator to process the digitized, structured
data.

1.3.3. Benefit for PT.Programa Reka Piranti

Pilot Project in Web Based Application

Monetary benefit

A chance to open a new recruit to Web Division

1.4. Methodology
The methodologies that are used:

1.4.1. Current System Analysis Methodology

Direct survey to company

Interview with involved party for analysis purpose

Literature study regarding topics that needed for analysis

purpose

1.4.2. Recommended System Planning Methodology

Based on OOAD with UP (Object Oriented Analysis and
Design) book, written by Satzinger, Jackson, and Burd. UML
diagram and notation, we utilize Unified Process which contain
the following discipline:

Requirement: Flowchart, Activity Diagram, Event Table,

Usecase Diagram, Usecase Description, Domain
Model, Statechart
Design

First Cut Class Diagram, Sequence Diagram,

Multilayer Sequence Diagram, Communication

Diagram, Updated Design Class Diagram,
Package Diagram, Entity Relationship Diagram,
and

Software

Deployment,

Architecture

Deployment.

1.5. Writing Systematic

The writing systematic within this report consists of 5
subchapters, which is:

CHAPTER 1: Introduction
This chapter is a briefly explain the whole content of this report. The
writing systematic within this chapter consists of 5 subchapters, which is:
1.1.

Background

Brief essay about the problem that author strive to solve and what we will
do to solve it.

1.2.

Scope

Explain limit of subjects and prevent irrelevant information outside the

topics. It also serve purpose to focus attention to relevant subjects.

1.3.

Purpose and Benefit

Purpose explain what this site is used for and desired end results.

Benefit explain about what benefit that the solution provider, small to
medium enterprises, and writer will gain from the completion of the
following sales and sistribution web based enterprise resource planning.

1.4.

Methodology

Explain the method that author use in designing the web based
crowdsourcing application.

1.5.

Writing Systematic

Explain about the content of thesis

CHAPTER 2: Theoretical Base

Explain about theories regarding Information System and Crowd Sourcing
in relevant, orderly, and timely manner. The writing systematic within this
chapter consists of 3 subchapters, which is:

2.1.

General Theory
2.1.1. Definition of Information System
Explain about what is Information System, based on expert
theories.
2.1.2. Definition of Sales
Explain about what sales is, based on expert theories.
2.1.3. Definition of Distribution
Explain about what distribution is, based on expert theories.

2.2.

Technical Theory
2.2.1. Definition of System Analysis
2.2.2. Business Model Generation Business Canvas

2.3.

Overview of Object-Oriented Concepts

2.3.1

Object Oriented Approach

2.3.2

The Unified Process Life Cycle

Information System Analysis and Design of Web Based Sales and

Distribution
Explain how author apply Information System Analysis and Design to web
based sales and distribution
2.3.1. Definition of System Analysis

CHAPTER 3: Preliminary Study

Explain about how crowdfunding work from information system
perspective using the result of System Analysis Methodology that has been
used to construct the web to solve present problems and anticipate
problems in the future. Author present the components that work as system
and how they work to form business process will in Activity Diagram. The
writing systematic within this chapter consists of eleven subchapters,
which is:

CHAPTER 4: Information System Analysis and Design

The writing systematic within this report consists of 2 subchapters, which
is:
4.1.

Modeling and the Requirement Discipline

4.1.1. The Requirement Discipline
4.1.1.1. Activity Diagram

4.1.2. Use Case and Domain Classes

4.1.2.1. Event Table
4.1.2.2. Use Case Diagram
4.1.2.3. Use Case Description
4.1.2.4. Domain Model Class Diagram
4.1.2.5. Statechart Diagram

4.2.

The Design Discipline

4.2.1. Use Case Realization
4.2.1.1. Developing the First Cut Design Class
Diagram
4.2.1.2. System Sequence Diagram
4.2.1.3. Multilayer Design System Sequence Diagram
4.2.1.4. Designing with Communication Diagram
4.2.1.5. Updated Class Diagram
4.2.1.6. Package Diagram

4.2.1.7. User Interface

4.2.1.8. Navigation Diagram/Story Board
4.2.1.9. Persistence Object

4.2.2. Design Activities and Environment

4.2.2.1. Deployment Environment
4.2.2.2. Software Architecture

CHAPTER 5: Conclusion and Suggestions

The writing systematic within this report consists of 2 subchapters, which
is:

5.1.

Conclusion

Summary from previously conducted project design analysis in brief,

descriptive manner in form of short paragraph. While 4th chapter describe
about author expectation in designing system, the 5th chapter describe
about the final results in as-is condition.

5.2.

Suggestions

Contain suggestions that give motivation for author and the reader of this
IS Minor Project report for future improvements.

10

11

1.6. Activity Plan

The following activity plan for project timeline and milestones will be presented in form of Gantt chart and table of schedule.

Software development template complete

Post Implementation Review
Deployment
Pilot
Documentation
Training
Testing
Development
Design
Analysis/Software Requirements
Scope
0 days

10 days

20 days

30 days

40 days

50 days

60 days

Scheduled Duration

Figure 1: Web based school management activity plan

12

70 days

80 days

90 days

100 days

Table 1: Web based school management activity plan

Task Name

Duration

Software Development

119.44 days Wed 5/14/14

Tue 10/28/14

2.06 days

Wed 5/14/14

Fri 5/16/14

Determine project scope

20 mins

Wed 5/14/14

Wed 5/14/14

Secure project sponsorship

1 day

Wed 5/14/14

Thu 5/15/14

Define preliminary resources

1 day

Thu 5/15/14

Fri 5/16/14

Secure core resources

10 mins

Fri 5/16/14

Fri 5/16/14

Scope complete

0 days

Fri 5/16/14

Fri 5/16/14

9.88 days

Fri 5/16/14

Thu 5/29/14

Conduct needs analysis

4 days

Fri 5/16/14

Thu 5/22/14

Draft preliminary software specifications

1 day

Thu 5/22/14

Fri 5/23/14

Develop preliminary budget

1 day

Fri 5/23/14

Mon 5/26/14

Review software specifications/budget with team

1 hr

Mon 5/26/14

Mon 5/26/14

10

Incorporate feedback on software specifications

1 day

Mon 5/26/14

Tue 5/27/14

11

Develop delivery timeline

1 day

Tue 5/27/14

Wed 5/28/14

12

Obtain approvals to proceed (concept, timeline, budget)

6 hrs

Wed 5/28/14

Wed 5/28/14

13

Secure required resources

1 day

Wed 5/28/14

Thu 5/29/14

14

Scope

Analysis/Software Requirements

13

Start

Finish

Predecessors

Analysis complete

0 days

Thu 5/29/14

Thu 5/29/14

14.5 days

Thu 5/29/14

Thu 6/19/14

Review preliminary software specifications

2 days

Thu 5/29/14

Mon 6/2/14

16

Develop functional specifications

5 days

Mon 6/2/14

Mon 6/9/14

18

Develop prototype based on functional specifications

4 days

Mon 6/9/14

Fri 6/13/14

19

Review functional specifications

2 days

Fri 6/13/14

Tue 6/17/14

20

Incorporate feedback into functional specifications

1 day

Tue 6/17/14

Wed 6/18/14

21

Obtain approval to proceed

4 hrs

Wed 6/18/14

Thu 6/19/14

22

Design complete

0 days

Thu 6/19/14

Thu 6/19/14

23

93 days

Thu 6/19/14

Tue 10/28/14

Review functional specifications

1 day

Thu 6/19/14

Fri 6/20/14

24

Identify modular/tiered design parameters

1 day

Fri 6/20/14

Mon 6/23/14

26

Assign development staff

1 day

Mon 6/23/14

Tue 6/24/14

27

Develop code

90 days

Tue 6/24/14

Tue 10/28/14

28

Developer testing (primary debugging)

3 days

Thu 7/24/14

Tue 7/29/14

29FS-75%

Development complete

0 days

Tue 7/29/14

Tue 7/29/14

30

55.5 days

Thu 6/19/14

Thu 9/4/14

4 days

Thu 6/19/14

Wed 6/25/14

Design

Development

Testing
Develop unit test plans using product specifications

14

15

24

Develop integration test plans using product specifications

4 days

Thu 6/19/14

Wed 6/25/14

Unit Testing

15 days

Tue 7/29/14

Tue 8/19/14

Review modular code

5 days

Tue 7/29/14

Tue 8/5/14

33,31

Test component modules to product specifications

2 days

Tue 8/5/14

Thu 8/7/14

31,36

Identify anomalies to product specifications

3 days

Thu 8/7/14

Tue 8/12/14

37

Modify code

3 days

Tue 8/12/14

Fri 8/15/14

38

Re-test modified code

2 days

Fri 8/15/14

Tue 8/19/14

39

Unit testing complete

0 days

Tue 8/19/14

Tue 8/19/14

40

12 days

Tue 8/19/14

Thu 9/4/14

Test module integration

5 days

Tue 8/19/14

Tue 8/26/14

41

Identify anomalies to specifications

2 days

Tue 8/26/14

Thu 8/28/14

43

Modify code

3 days

Thu 8/28/14

Tue 9/2/14

44

Re-test modified code

2 days

Tue 9/2/14

Thu 9/4/14

45

Integration testing complete

0 days

Thu 9/4/14

Thu 9/4/14

46

52.5 days

Thu 6/19/14

Mon 9/1/14

Develop training specifications for end users

3 days

Thu 6/19/14

Tue 6/24/14

24

Develop training specifications for helpdesk support staff

3 days

Thu 6/19/14

Tue 6/24/14

24

Identify training delivery methodology (computer based

2 days

Thu 6/19/14

Mon 6/23/14

24

Integration Testing

Training

15

24

training, classroom, etc.)

Develop training materials

3 wks

Tue 7/29/14

Tue 8/19/14

49,31,50,51

Conduct training usability study

4 days

Tue 8/19/14

Mon 8/25/14

52

Finalize training materials

3 days

Mon 8/25/14

Thu 8/28/14

53

Develop training delivery mechanism

2 days

Thu 8/28/14

Mon 9/1/14

54

Training materials complete

0 days

Mon 9/1/14

Mon 9/1/14

55

68 days

Thu 6/19/14

Tue 9/23/14

Develop Help specification

1 day

Thu 6/19/14

Fri 6/20/14

24

Develop Help system

3 wks

Tue 8/26/14

Tue 9/16/14

58,29FS-50%

Review Help documentation

3 days

Tue 9/16/14

Fri 9/19/14

59

Incorporate Help documentation feedback

2 days

Fri 9/19/14

Tue 9/23/14

60

Develop user manuals specifications

2 days

Thu 6/19/14

Mon 6/23/14

24

Develop user manuals

3 wks

Tue 8/26/14

Tue 9/16/14

62,29FS-50%

Review all user documentation

2 days

Tue 9/16/14

Thu 9/18/14

63

Incorporate user documentation feedback

2 days

Thu 9/18/14

Mon 9/22/14

64

Documentation complete

0 days

Tue 9/23/14

Tue 9/23/14

65,61

89.5 days

Thu 5/29/14

Thu 10/2/14

1 day

Thu 5/29/14

Fri 5/30/14

Documentation

Pilot
Identify test group

16

16

Develop software delivery mechanism

1 day

Fri 5/30/14

Mon 6/2/14

68

Install/deploy software

1 day

Tue 9/23/14

Wed 9/24/14

47,69,66,56

Obtain user feedback

1 wk

Wed 9/24/14

Wed 10/1/14

70

Evaluate testing information

1 day

Wed 10/1/14

Thu 10/2/14

71

Pilot complete

0 days

Thu 10/2/14

Thu 10/2/14

72

5 days

Thu 10/2/14

Thu 10/9/14

Determine final deployment strategy

1 day

Thu 10/2/14

Fri 10/3/14

73

Develop deployment methodology

1 day

Fri 10/3/14

Mon 10/6/14

75

Secure deployment resources

1 day

Mon 10/6/14

Tue 10/7/14

76

Train support staff

1 day

Tue 10/7/14

Wed 10/8/14

77

Deploy software

1 day

Wed 10/8/14

Thu 10/9/14

78

Deployment complete

0 days

Thu 10/9/14

Thu 10/9/14

79

Post Implementation Review

3 days

Thu 10/9/14

Tue 10/14/14

Document lessons learned

1 day

Thu 10/9/14

Fri 10/10/14

80

Distribute to team members

1 day

Fri 10/10/14

Mon 10/13/14

82

Create software maintenance team

1 day

Mon 10/13/14

Tue 10/14/14

83

Post implementation review complete

0 days

Tue 10/14/14

Tue 10/14/14

84

0 days

Tue 10/14/14

Tue 10/14/14

85

Deployment

Software development template complete

17

18