MYINTERN :

INTERNSHIP PLACEMENT FOR STUDENT

MOHAMMAD ADLY BIN ALIMIN

BACHELOR OF COMPUTER SCIENCE

(SOFTWARE DEVELOPMENT)

UNIVERSITI SULTAN ZAINAL ABIDIN

2018
MYINTERN: INTERNSHIP PLACEMENT FOR STUDENT

MOHAMMAD ADLY BIN ALIMIN

Bachelor of Computer Science (Software Development)

Faculty of Informatics and Computing

Universiti Sultan Zainal Abidin, Terengganu, Malaysia

MAY 2018

i
 DECLARATION

I hereby declare that this report is based on my original work except for quotations and

citations, which have been duly acknowledged. I also declare that it has not been

previously or concurrently submitted for any other degree at Universiti Sultan Zainal

Abidin or other institutions.

________________________________

Name : ..................................................

Date : ..................................................

ii
 CONFIRMATION

This is to confirm that the project title MyIntern: Internship Placement for Student was

prepared and submitted by Mohammad Adly bin Alimin, matrix number

BTAL15040479 and has been found satisfactory in terms of scope, quality and

presentation as partial fulfilment of the requirement for the Bachelor of Computer

Science (Software Development) in Universiti Sultan Zainal Abidin (UniSZA). The

research conducted and the writing of this report was under my supervisor.

________________________________

Prof. Madya Dr. Syadiah Nor binti Wan Shamsuddin

Supervisor : ......................................................................................

Date : ..................................................

iii
 DEDICATION

First and foremost, praised be to Allah, the Most Gracious and the Most

Merciful for blessing me and giving me the opportunity to undergo and complete my

final year project, an application of MyIntern: Internship Placement for Student. I

would like to take this opportunity to express my utmost and heartiest gratitude to my

supervisor, Prof. Madya Dr. Syadiah Nor binti Wan Shamsuddin for her teaching,

kindness, patience and motivations toward this project. I was so proud to be supervised

by her with her guidance and invaluable advices.

A lot of thanks to Faculty of Informatics for given me a chance to expose and

explore myself with this project. I would like to thanks to my family, especially to my

father and mother for giving me endless support to complete my project. I would like

to express my gratitude also to all the lecturers in Faculty Informatics for giving me a

great opportunity to complete my final year project. Not to forget to all of my friends

in SMSKPP Batch 2015/2019 for their teaching, high technical supports and good

skills. I was very appreciating for their kindness.

iv
 ABSTRACT

Nowadays, student and work are not the same level. Work life is different based

by the environments of work. To make student know how the work life is their need to

complete the studies with internship. This is the critical part is to find the suitable

internship based on their studies and courses. This MyIntern is a platform to counter

this problem and make easy for student. This application development is based on the

problem that come from final year student that need to find internship. Student just need

to find the internship and see the status of application by the smartphone and direct

apply to the company. This platform is not only for student, it also for company that

need to offer the internship for student. This development are using the latest hybrid

mobile application technique. This application will used HTML5 and PhpMyAdmin as

the database. As the result this application can make student easy to find internship and

save their time.

v
 TABLE OF CONTENT

CHAPTER /TITLE PAGE

FRONT PAGE ....................................................................... Error! Bookmark not defined.

DECLARATION................................................................................................................................... ii
CONFIRMATION ............................................................................................................................... iii
DEDICATION...................................................................................................................................... iv
ABSTRACT ........................................................................................................................................... v
TABLE OF CONTENT ....................................................................................................................... vi
LIST OF FIGURES ............................................................................................................................. ix
LIST OF TABLES ................................................................................................................................ x
LIST OF ABBREVIATIONS / TERMS / SYMBOLS..................................................................... xii
CHAPTER 1 .......................................................................................................................................... 1
INTRODUCTION............................................................................................................................. 1
1.1 BACKGROUND ............................................................................................................... 1
1.2 PROBLEM STATEMENT .............................................................................................. 2
1.3 OBJECTIVES ................................................................................................................... 3
1.4 SCOPES ............................................................................................................................. 4
1.5 LIMITATION OF WORK ............................................................................................... 6
1.6 EXPECTED RESULT ...................................................................................................... 7
1.7 MILESTONE .................................................................................................................... 8
1.8 GANTT CHART ............................................................................................................. 10
CHAPTER 2 ........................................................................................................................................ 11
LITERATURE REVIEW .............................................................................................................. 11
2.1 INTRODUCTION........................................................................................................... 11
2.2 SUMMARY OF LITERATURE REVIEW .................................................................. 13
2.2.1 Development of Mobile Application for Internship Program ............................. 13
2.2.2 Android Application to Enhance Performance of Internship ............................. 14
2.2.3 Software Engineering Issues for Mobile Application Development ................... 16
2.3 RESEARCH ON EXISTING SYSTEM AND APPLICATION ................................. 17
2.4 ADDED VALUE ............................................................................................................. 19
CHAPTER 3 ........................................................................................................................................ 20
METHODOLOGY ......................................................................................................................... 20

vi
 3.1 INTRODUCTION........................................................................................................... 20
3.2 PROJECT METHODOLOGY ...................................................................................... 21
3.2.1 IDENTIFICATION PHASE .................................................................................. 22
3.2.2 DESIGN PHASE ..................................................................................................... 22
3.2.3 DEVELOPMENT PHASE ..................................................................................... 23
3.2.4 PROTOTYPING PHASE....................................................................................... 23
3.2.5 TESTING PHASE................................................................................................... 24
3.2.6 DEPLOYMENT PHASE ........................................................................................ 24
3.2.7 MAINTENANCE PHASE ...................................................................................... 25
3.3 DEVELOPMENT PHASE ............................................................................................. 26
3.3.1 HARDWARE .......................................................................................................... 26
3.3.2 SOFTWARE ............................................................................................................ 27
3.4 SYSTEM DESIGN .......................................................................................................... 28
3.4.1 CONTEXT DIAGRAM .......................................................................................... 28
3.4.2 DATA FLOW DIAGRAM (DFD) LEVEL 0 ........................................................ 30
3.4.3 DATA FLOW DIAGRAM (DFD) LEVEL 1 (MANAGE USER) ...................... 32
3.4.4 DATA FLOW DIAGRAM (DFD) LEVEL 1 (MANAGE INTERN) ................. 33
3.4.5 ENTITY RELATIONSHIP DIAGRAM ............................................................... 34
CHAPTER 4 ........................................................................................................................................ 35
IMPLEMENTATION AND RESULT .......................................................................................... 35
4.1 INTRODUCTION........................................................................................................... 35
4.2 PROTOTYPE .................................................................................................................. 36
4.2.1 ADMIN MODULE.................................................................................................. 37
4.2.2 COMPANY MODULE ........................................................................................... 39
4.2.3 STUDENT MODULE ............................................................................................. 43
4.2.4 STUDENT MODULE (Mobile Application View)............................................... 46
4.3 TECHNIQUE .................................................................................................................. 50
4.4 CHAPTER SUMMARY ................................................................................................. 51
CHAPTER 5 ........................................................................................................................................ 52
5.1 INTRODUCTION........................................................................................................... 52
5.2 ADMIN MODULE.......................................................................................................... 53
5.2.1 LOGIN ..................................................................................................................... 53
5.2.2 MANAGE COMPANY........................................................................................... 53
5.2.3 MANAGE STUDENT............................................................................................. 54
5.3 COMPANY MODULE ................................................................................................... 55
5.3.1 REGISTER .............................................................................................................. 55
5.3.2 COMPANY LOGIN ............................................................................................... 55
5.3.3 INTERNSHIP OFFER ........................................................................................... 56

vii
 5.3.4 APPROVE STUDENT ........................................................................................... 57
5.4 STUDENT MODULE ..................................................................................................... 58
5.4.1 REGISTER .............................................................................................................. 58
5.4.2 APPLY INTERNSHIP ........................................................................................... 58
CHAPTER 6 ........................................................................................................................................ 60
DISCUSSION AND CONCLUSION ............................................................................................ 60
6.1 INTRODUCTION........................................................................................................... 60
6.2 PRODUCT CONTRIBUTION ...................................................................................... 60
6.3 PORJECT CONSTRAINT ............................................................................................ 61
6.4 FUTURE WORKS .......................................................................................................... 61
6.5 CONCLUSION................................................................................................................ 62

viii
 LIST OF FIGURES

FIGURE TITLE PAGE

Figure 2.1 Fi-Int Application 17

Figure 3.1 Mobile Application Life Cycle 22

Figure 3.2 Context Diagram MyIntern Application 28
Figure 3.3 Data Flow Diagram Level 0 MyIntern Application 30
Figure 3.4 Data Flow Diagram Level 1 Manage User 32
Figure 3.5 Data Flow Diagram Level 1 Manage Intern 33
Figure 3.6 Entity Relationship Diagram MyIntern Application 34

ix
LIST OF TABLES

x
 LIST OF APPENDICES

APPENDIX TITLE PAGE

A Milestone 8-9

B Gantt Chart 10

xi
 LIST OF ABBREVIATIONS / TERMS / SYMBOLS

CD Context Diagram
DFD Data Flow Diagram
ERD Entity Relationship Diagram
FYP Final year project

xii
 CHAPTER 1

INTRODUCTION

1.1 BACKGROUND

Internship is part of as student in university, internship is place to improve and to show

student how industries works. Manual method and some online internship system are exposed

to the problem of misunderstanding information about the internship. This application can

solve relation student with company and to make communication with company easy.

Internship Application is an application that can find the proper internship for the student. This

application will connect the student with a company that needs internship student. Apart from

that this application will give detail of company that provides the internship so student not has

to call the company and asks if they any internship program.

1
 1.2 PROBLEM STATEMENT

This application is proposed to overcome several problems:

a) Student need spend some time to find the suitable company

• This happen when student do not have proper platform to find the internship

and need to find manually the internship place.

b) The student did not have any platform to find a company

• Some other platform need another requirement to use the function and student

need time to find the internship and difficult to use the platform

c) Company do not have proper platform to offer internship

• Company do not have proper channel to put information about internship and

offer for student. Some company need to do manually all the process and find

the student for internship.

2
 1.3 OBJECTIVES

There are several objectives for this proposal, this objective is to solve the problem that has

been state before:

1. To design and develop a platform for student to find the proper internship and company

to offer the internship

2. To implement the new mobile application (hybrid) technique to help student and

company offer an internship.

3. To produce an application that can be accessed anywhere and anytime.

3
 1.4 SCOPES

The scope is going to outline and function of this application system and make implementation

easier. The scope of this system is divided into three (3) which are an admin scope, student

scope, and company scope.

Student

1. Able to manage profile

2. Able to make own digital CV

3. Able to search internship company

4. Able to view company information

5. Able to apply for internship

6. Able to view status internship

7. Able to make a daily report

Company

1. Able to manage company profile

2. Able make own company CV

3. Able to view student they apply

4. Able to approve student internship

5. Able to view student digital CV

6. Able to make a daily report about student

7. Able to view status internship

4
Admin

1. Able to manage profile

2. Able to view student status

3. Able to view student digital CV

4. Able to apporove student internship

5. Able to view company

6. Able to view company digital CV

7. Able to view report internship

8. Able to view repot company

5
1.5 LIMITATION OF WORK

The constraint is a condition that the system outcome must meet. A constraint can involve

hardware, software, time, or policy. System constraint also defines project scope. All

constraint should be identified early to avoid future problem.

1. This project only focuses on a student who needs to find internship company. Not for

other user.

2. Due to limitations in research mobile application hybrid and this is new technology,

some difficulties, and obstacles to achieve goals of project recognized. This will take

time to make research about hybrid mobile application.

6
 1.6 EXPECTED RESULT

This internship application is able to help the student to find the suitable internship company

with details of internship and company that have internship program can be in this application

to offer their internship to the student. This project also implements new mobile application

hybrid to support this application. Besides that, this application can be access anywhere and

anytime.

7
1.7 MILESTONE

Milestone Date Status Responsible

Topic Discussion and Week 1 Completed All students semester 6

Determination

Project Title Proposal Week 2 Completed All students semester 6

Proposal Writing – Week 3 Completed All students semester 6

Introduction

Proposal Writing – Week 4 & Week 5 Completed All students semester 6

Literature Review

Proposal Progress Week 6 Completed All students semester 6

Presentation & Evaluation

Discussion & Correction Week 7 Completed All students semester 6

Proposal & Proposed

Solution Methodology

Proposed Solution – Week 8 Completed All students semester 6

Methodology (Continued)

Proof of Concept Week 9 Completed All students semester 6

Drafting Report of the Week 10 & Week Completed All students semester 6

Proposal 11

Submit draft of report to Week 12 Completed All students semester 6

supervisor

Seminar Presentation Week 13 Completed All students semester 6

8
Report Correction Week 14 Completed All students semester 6

Final Report Submission Week 15 Completed All students semester 6

9
1.8 GANTT CHART

10
 CHAPTER 2

LITERATURE REVIEW

2.1 INTRODUCTION

A literature review discusses published information in particular subject area, and sometimes

information in a particular subject area within a certain period. It can be just a simple summary

of the source, but it usually has an organizational pattern to combines both summary and

synthesis. People can use it as a guideline or a sample to upgrade or to develop a new better

system compared to the old one.

The main objective of literature review is:

- It presents the literature in an organize way.

- It surveys the literate in your chosen area of study.

- It synthesis the information in that literature into a summary.

- It critically analyses the information gathered by identifying gaps in current knowledge

by showing limitations of theories and point of view and by formulating areas for

further research and reviewing area of controversy.

Nowadays, there are many ways technologies and technique can be used to apply internship

as long as there is internet connection. The efficiency depends on the technology used and

what environment to use so that the decision making is perfect and suitable. Furthermore,

cost, coverage, and any other factor plays an importance role to success of the project.

11
Below are some of the research and development that has been carried out by certain

developer and also different approach between them to complete their project.

12
2.2 SUMMARY OF LITERATURE REVIEW

2.2.1 Development of Mobile Application for Internship Program

Author / Year Title Method Process / Advantage Disadvantage

Description

Shutchapol Development - Model Develop a - Provides

Chopvitayakun of Mobile View mobile useful guidance

- 2014 Application Controller application for from each

for (MVC) seniors or last- intern’s advisor,

Internship Pattern. year students in case of

Program - Mobile who enroll the emergency.

Management transactional internship - It can

Using the processing program at summarize all

Concept of system. each tertiary transactional

Model View school data then

Controller (undergraduate calculate each

(MVC) school) and do internship

Pattern onsite practice cumulated

at real field hours from the

sties, real field practice

organizations session for each

and real individual

workspaces. intern.

13
2.2.2 Android Application to Enhance Performance of Internship

Author / Year Title Method Process / Advantage Disadvantage

Description

Shutchapol Android - Cloud This work - Interaction

Chopvitayakun Application computing modified between users

– 2014 to Enhance - Android Internship and Cloud

Performance native Program server through

of Internship development Management Internet

Program - Mobile or IPM on its connection.

Implementing Cloud database and - This new

Cloud web server application can

Computing sections in to manage the

Platform and Mobile and internship

Infrastructure Database program of

cloud server. senior students

Moreover, the who enroll a

developers course of

can also internship more

advocate, efficiently.

modify and

create more

features to this

application via

the Internet as

well. Thanks

14
 to the great

benefits of

Cloud

computing

framework.

15
2.2.3 Software Engineering Issues for Mobile Application Development

Author / Title Method Process / Advantage Disadvantage

Year Description

Anthony I. Software - Research Native and -There remain a

Wasserman - Engineering agenda. hybrid (mobile large number of

2010 Issues for - Small web) complex issues

Mobile survey of applications – where further

Application mobile most embedded work is needed.

Development developers devices use In addition, there

[1], using only software is a mobile

available installed “angle” to almost

mobile directly on the every aspect of

developer device, but software

forums to mobile devices engineering

solicit often include research, where

respondents. applications the

that invoke characteristics of

services over mobile

the telephone applications and

network or the their operating

Internet via a environments

web browser present a new or

and affect data different set of

and displays on research issues

the device.

16
2.3 RESEARCH ON EXISTING SYSTEM AND APPLICATION

Fi-Int: Find An Internship

Figure 2.1: Fi-Int Application

Fi-Int helps its users to know all the sites or portals where one can apply for internship.

It benefits the people looking for internship all over the globe. It consists of Indian as well as

Global internships. It has been developed to help the users who do not know the various portals

where they can apply for varied internships. It covers all areas of study, both technical and non-

technical. Student of any country will benefit from this as there is something for everyone out

there.

17
Some tips are also given to prepare and catch the eye of the recruiters. User friendly interface

of the app makes it easy to use and animations are used to make it more attractive.

18
2.4 ADDED VALUE

❖ MySQL

MySQL is an open source relational database management system (RDBMS).

SQL is the abbreviation for Structured Query Language. MySQL is the world’s

most popular open source database, enabling the cost-effective delivery of reliable,

high-performance and scalable Web-based and embedded database applications.

This application used MySQL Workbench and phpMyAdmin as the database

server. MySQL Workbench is a unified visual tool for database architects,

developers, and DBAs. MySQL Workbench provides data modeling, SQL

development, and comprehensive administration tools for server configuration, user

administration, backup, and much more. MySQL Workbench enables a DBA,

developer, or data architect to visually design, model, generate, and manage

databases. It includes everything a data modeler needs for creating complex ER

models, forward and reverse engineering, and also delivers key features for

performing difficult change management and documentation tasks that normally

require much time and effort. MySQL Workbench delivers visual tools for creating,

executing, and optimizing SQL queries. The SQL Editor provides color syntax

highlighting, auto-complete, reuse of SQL snippets, and execution history of SQL.

The Database Connections Panel enables developers to easily manage standard

database connections.

19
 CHAPTER 3

METHODOLOGY

3.1 INTRODUCTION

In this chapter, it will explain the specific details on the methodology being used in

order to develop this project. In order to make sure the project is in the right path, methodology

plays an importance role as a guide for the project complete and working well as plan. There

is different type of methodology that is used for different type of application. It is important to

choose the right and suitable methodology for the development of an application thus it is

necessary to understand the application functionality itself. In order to ensure the effective of

the MyIntern application, good identification is required before the development process

begins. By using Mobile Application Development Life Cycle (MADLC) model, there are

seven phases involve.

20
3.2 PROJECT METHODOLOGY

Methodology is the process, step or stages used to collect information and data for the purpose

of making decisions. The methodology is chosen from the software development life cycle

model (SDLC). A good planning and methodology must be used to accomplish the objectives

of this project. Iterative and incremental model has been chosen as the methodology to develop

this application. In this model, the project is designed, implemented and tested incrementally

with improvement is added each time until the project is finished. The benefits of iterative and

incremental development are it has the opportunity and improving the product step by step.

Hence, it easier to manage risk and can track the defects at early stages. This avoids the

downward flow of the defects. Besides, in iterative model less time is spent on documenting

and more time is given for designing. The flexibility of the model makes the project easy to

implement at a very little cost because of the frequency of new increments that are produced.

Hence, iterative and incremental model is saving of time and cost.

The phase in Mobile Application Development Life Cycle model are: Identification

Phase, Design, Development, Prototyping, Testing, Development and Maintenance. All the

methods and processes undertaken in Mobile Application Development Life Cycle are more

visible.

21
 Identification Development Prototyping
Design Phase
Phase Phase Phase

Maintenance Deployment
Testing Phase
Phase Phase

Figure 3.1: Mobile Application Life Cycle

3.2.1 IDENTIFICATION PHASE

In this first phase, ideas are collected and categorized. The main objective of this phase

is to come out with new idea and improvements to the current complaint system.

The existing systems on any of the standards platforms are searched to establish the

novelty of the idea. If a similar application exists in the market, the popularity of the application

and the features supported are studied and compared. The differences with the existing

system(s) are documented. If no similar application exists in and mobile application, then the

idea with its core functionality should be documented. The other important task in this phase

is to define the time required to develop the MyIntern application. The initial requirement

gathering should also be completed.

3.2.2 DESIGN PHASE

In this phase, the idea for MyInten application is development into an initial design of

the application. The feasibility if developing the application on all mobile platform is

determined. Alternatively, the specific target mobile platform is identified (example

smartphone with Android 5.0 Lollipop (API 20)).

22
 The application functionality is breaking down into module and into prototype i.e.,

combination of modules which are to be released in the prototype design. The functional

requirement is defined. For example: login, apply internship, view status, update profile, reject

internship and etc. The software architecture of the application is created. Then the prototype

and associated modules are defined. A very importance part of the design phase is to create the

storyboard for the user interface interaction: this storyboard described flow of the application.

3.2.3 DEVELOPMENT PHASE

In this phase, the application is coded. Coding for different module of the same

prototype can proceed in parallel. The development process can be in two stages: Coding for

Functional Requirement and Coding for UI requirement. The code is developed first for the

core functionalities. Parallel development can be done for module of the same prototype that

are independent of each other. Subsequently, these modules can be integrated. In the second

stage, user interface is designed so that it can be supported on as may mobile operating system

platform as possible; it is not good practice to have different look and feel the same application

in different platforms. The minimum set of interface components in all mobile OS platform

should be used in the design.

3.2.4 PROTOTYPING PHASE

In this phase, the functional requirement of each prototype is analyzed; the prototype is

tested and sent to the supervisor for feedback. After feedback is received from the supervisor,

the required changes are implemented through the development phase. When the second

prototype is ready, it is integrated with the first prototype, tested and the send to the client. The

23
development, prototyping and testing phase are repeated until the final prototype is ready. The

final prototype is sent to the supervisor for a final feedback.

3.2.5 TESTING PHASE

Testing is one of the most important phases of any development lifecycle model. The

testing of the prototype is performed on an Android Virtual Device or any simulator followed

by testing on the real device, for example in the case of Android operating system development,

should be performed on multiple operating system versions, multiple models od smartphone

with variable screen size.

3.2.6 DEPLOYMENT PHASE

Development is the final phase of the development process. After the testing is completed and

the final feedback is obtained from the supervisor, the application us ready for the deployment.

The application is uploaded to the appropriate application store/market for user consumption.

Before the application us deployed, the following steps are to be checked.

• Register as a developer on the respective application developer’s website by paying the

annual fee, if necessary, for respective OS.

• Check the rules and regulations of the application store for the deployment of an

application.

• Refine the application, for example, by removing all the log files and comment.

• Design the icon and wallpaper.

Create the file format required on operating system platform

24
3.2.7 MAINTENANCE PHASE

The maintenance is the final phase of this model and this maintenance is a continuous process.

Feedback is collected from users and required changes are made in the form of bug fixes or

improvements. Appropriate security patches, performance improvements, additional

functionality, new user interface should be provided at regular intervals in the form of updates

to the application. The maintenance phase also includes the marketing of the application:

advertising and highlighting its unique features. If any application required a backend server:

this server and related operating system must be maintained as well.

25
3.3 DEVELOPMENT PHASE

In the application development process, the requirement such as software and hardware

are the most importance requirement to ensure that all system development work smoothly

without any interruption and problem. There are several requirements that were used to

complete this project which include:

3.3.1 HARDWARE

Minimum hardware requirement needed in this development of this application are:

I. Notebook: Acer A515-51G

• Processor: Intel Core i5-8250U, 3.4GHz

• Memory: 8GB Ram

• Storage: 120GB SSD + 1TB HDD

• Operating System: Windows 10 Home Premium

II. Android Mobile Phone: Xiaomi Redmi Note 2

• Used to run, deploy and testing application

• Android version 5.1.1 or later.

26
3.3.2 SOFTWARE

Software requirement of this project are:

I. Android Studio

• This software is used by Cordova to get some plugin.

II. Cordova

• This software is used to create and build android project.

III. Xampp for Windows

• This software used to manage connection between Apache and MySQL.

IV. MySQL

• This software used to create system database application.

27
3.4 SYSTEM DESIGN

Modelling and design are a diagram that built to scale which is represent the detail in

order to explain more about the system functioning in designing of database, the interface that

are build and the way of implementation method in this system. System design is explained by

Framework Design, Context Diagram (CD) and Data Flow Diagram (Level 0 and 1) and Entity

Relationship Diagram (ERD). Data modelling is needed because it can facilitate interaction

among the designer, application programmer and the end user. Early modelling and analysis

help stakeholders to understand their needs and problems with potential solutions.

3.4.1 CONTEXT DIAGRAM

Figure 3.2: Context Diagram for MyIntern Application

28
 In Context Diagram, it explains the flow of the system based on character and main

process that involve on the system functional. It just tells the main function of the

system/application. As we can see from the Figure 3.1, there are 4 actor that involves on this

application. The first actor is students that is our user to use this application. The student can

add apply to company, update profile, make daily report and view company detail.

The second actors that involve in this system are company. Company must register first

and will be approve by admin. Company must fulfil their company detail first, view student

profile, view apply record, approve apply record, update company profile.

The third actor is supervisor. Supervisor also need to register into system and will be

approve by admin. Supervisor can view student profile that relate to the supervisor and can

view company profile, apply detail of student and daily report from student and company.

The last actor is admin. Role of admin is to approve company that legal and exist to

enter the system and approve supervisor that legal and exist with some requirement that provide

from them.

29
3.4.2 DATA FLOW DIAGRAM (DFD) LEVEL 0

Figure 3.3: Data Flow Diagram Level 0 for MyIntern Application

Data Flow Diagram or DFD is a diagram that shows the flow of the data that through on this

application. DFD use to show the data that will save on the database with specific table that

created in the database. Figure 3.2 show the DFD of MyIntern Application. The flows of the

data are showing only the main function that involves the flow data in the application.

Student (users) can register to system by provide the information given and application

will register the student. Student can login the system by provide information to system and

application will authenticate the login process. The system will retrieve student information

after student login. After login process, student can make apply for internship. Student will be

provided all the company that register in system and student can sort by their speciality. Apply

record will be store in ApplyRecord data store. Student also can update profile, cancel apply

30
internship, view apply record from ApplyRecord data store. Student can make daily report and

view report from this application and this will store in DailyReport data store.

Company need to register first before use this system and will be approve by admin and

the approve will update company status in Company data store. After company has been

approve by admin, company need to login first and complete their company profile that will be

store in Company data store. Company can view apply record from ApplyRecord data store,

company also can view student information that relate to apply record. Company can update

profile, cancel apply.

Supervisor also need to register first to system before use and will be approve by admin.

Supervisor need to complete profile in system. Supervisor will have relation with student that

under their supervision and supervisor can view which company student apply from

ApplyRecord data store and student daily report from DailyReport data store.

Admin role is only to approve company and supervisor with some information that

given from them. Approval will update status in Company data store and Supervisor data store

and they will visible in the system.

31
3.4.3 DATA FLOW DIAGRAM (DFD) LEVEL 1 (MANAGE USER)

Figure 3.4: Data Flow Diagram Level 1 for Manage User Process

After student has done making registration. Supervisor will approve that student is

belong to him, this to make sure non-related student exist in the system.

32
3.4.4 DATA FLOW DIAGRAM (DFD) LEVEL 1 (MANAGE INTERN)

Figure 3.5: Data Flow Diagram Level 1 for Manage Intern Process.

Student need to apply the internship and process will call all the detail from database based in

which student is login. Process will take detail student from table Student, StudAddress,

StudAcademic, and this process also take company detail to show for student and company

address from table Company and CompAddress.

Student can update internship apply and the detail internship will store in ApplyRecord table.

Student also can cancel the internship if internship is not approve ye

33
3.4.5 ENTITY RELATIONSHIP DIAGRAM

Figure 3.6: Entity Relationship Diagram MyIntern Application

Entity Relationship Diagram or ERD is a data models tools that used in analysis to

describe the data requirement and assumptions in the system from a top-down perspective. It

also a set the stage for the design of databases later in evolutionary/iterative stage.

34
 CHAPTER 4

IMPLEMENTATION AND RESULT

4.1 INTRODUCTION

An implementation and result are to construct the product as design specifications

developed in previous phase, methodically verified to ensure that they are error-free

and fully meet user requirements. Implementation and result should be done before a

system is fully utilized. System implementation consider that the hardware and software

system components are installed, the selected software is configured and tested, the

software may be customized to meet local functional requirement, data mapping, signed

off and becoming a fully operational production system.

35
4.2 PROTOTYPE

Figure 4.1 Main Homepage

36
4.2.1 ADMIN MODULE

Figure 4.2 Admin Login Page

Figure 4.3 Admin Homepage

37
Figure 4.4 Company Details View

Figure 4.5 Student Details View

38
4.2.2 COMPANY MODULE

Figure 4.6 Company Login Page

Figure 4.7 Company Homepage

39
Figure 4.8 Company Internship Offer Details

Figure 4.9 Company Internship Update

40
Figure 4.10 Company Internship Offer Form

Figure 4.11 Company Student Report

41
Figure 4.12 Company Profile Update Form

42
4.2.3 STUDENT MODULE

Figure 4.13 Student Login Page

Figure 4.14 Student Homepage

43
Figure 4.15 Student Internship Details

Figure 4.16 Student Confirm Apply

44
Figure 4.17 Student Internship Report

Figure 4.18 Student Profile Update

45
4.2.4 STUDENT MODULE (Mobile Application View)

Figure 4.19 Student Login Form

46
Figure 4.20 Student Internship Status

47
Figure 4.21 Student Internship List

48
Figure 4.22 Student Profile Details

49
4.3 TECHNIQUE

HYBRID TECHNIQUE IMPLEMENTATION

Figure 4.23 Hybrid Mobile Application Technique

50
4.4 CHAPTER SUMMARY

In this chapter, the prototype of the interfaces was shown to know how the system is actually

functioning. The technique implementation of hybrid mobile application is also shown in order

to know how the hybrid technique is implemented throughout this application.

51
 CHAPTER 5

TESTING

5.1 INTRODUCTION

This chapter will discuss about the module testing in the system. Testing
encompasses all the processes involved in getting system to operate properly and making
necessary changes. System testing depending on the testing method employed, can be
implemented at any time in the development process, however the more test effort is
employed after the requirements have been defined and coding process has been completed.
Testing may be performed on each of the modules before the system can be released.
Testing should be done throughout the implementation process.

52
5.2 ADMIN MODULE

5.2.1 LOGIN

ADMINISTRATOR’S LOGIN

Test Case Name: Administrator’s Login

Step Procedure Expected Result

1 Admin input admin username and Input text received

password.

2 Admin click “Login” button Login page loaded.

System will be redirected

to homepage admin.

Pre-condition: correct admin ID and password

5.2.2 MANAGE COMPANY

APPROVE COMPANY

Test Case Name: Approve Company

Step Procedure Expected Result

1 Admin click view button View company profile

page loaded

53
 2 Admin click “Approve” button System show popup that

company has been

approve and email send

into company

Pre-condition: Admin must login system

5.2.3 MANAGE STUDENT

Approve Student

Test Case Name: Approve Student

Step Procedure Expected Result

1 Admin click View button View student profile

page loaded

2 Admin click “Approve” button System show popup that

student has been approve

and email sent to student

Pre-condition: correct admin ID and password

54
5.3 COMPANY MODULE

5.3.1 REGISTER

COMPANY REGISTRATION

Test Case Name: Company Registration

Step Procedure Expected Result

1 Company fill the registration form. Input text received

2 Company click “Register” button Register page loaded.

System will be redirected

to login page.

Pre-condition: Company must fill the registration form

5.3.2 COMPANY LOGIN

COMPANY LOGIN

Test Case Name: Company Login

Step Procedure Expected Result

1 Company input company email and Input text received

password.

55
 2 Company click “Login” button Login page loaded.

System will be redirected

to homepage company.

Pre-condition: correct company username and password

5.3.3 INTERNSHIP OFFER

COMPANY REGISTRATION

Test Case Name: Company Registration

Step Procedure Expected Result

1 Company fill the offer form. Input text received

2 Company click “Offer” button Homepage loaded with

popup details that

internship offer has been

save into system

Pre-condition: Company must login system

56
5.3.4 APPROVE STUDENT

Approve Student

Test Case Name: Approve Student

Step Procedure Expected Result

1 Admin click View button View student profile

page loaded

2 Admin click “Approve” button System show popup that

student has been approve

and email sent to student

Pre-condition: List of students was shown

57
5.4 STUDENT MODULE

5.4.1 REGISTER

STUDENT REGISTRATION

Test Case Name: Student Registration

Step Procedure Expected Result

1 Student fill the registration form. Input text received

2 Student click “Register” button Register page loaded.

System will be redirected

to login page.

Pre-condition: Student must fill the registration form

5.4.2 APPLY INTERNSHIP

APPLY INTERNSHIP

Test Case Name: Apply Internship

Step Procedure Expected Result

1 Student click to “Apply” button Internship details loaded

after clicked button

58
2 Student click “Apply” button Popup will show student

has apply for internship

and email has send to

related company

Pre-condition: Student must login into system

59
 CHAPTER 6

DISCUSSION AND CONCLUSION

6.1 INTRODUCTION

This chapter discuss on the project contributions, constraints of project and its

development, future works that can be taken into considerations and eventually conclusion to

conclude the project.

6.2 PRODUCT CONTRIBUTION

The contribution of this application system for student who need to find the internship

by saving their time in doing and finding their intern. MyIntern application will be used by

administrator, student and company. The major contribution of the project can be summarized

as this application system is to help company to offer their internship for student and help

student to save time and know where to find the internship. Without MyIntern all the process

need to make by manual and take time and cost to find the internship. Due to this project is

well developed in mobile application platform hence student can easily access this application

whenever they are.

60
6.3 PORJECT CONSTRAINT

Each and every system must have some constraints that maybe appear on the construction

phase or design phase. These constraints will affect the development process. The limitations

for this project is when to implement the system into mobile application because it requires

developer to have much knowledge and understanding about how to develop mobile

application. Next, this application can only be used by student who want to seek internship

company. For student who want to use this application, they must have student certification

letter by their university themselves and wait for the confirmation by the administrator. The

functions in this application system also are quite rough and tumble. Although it is quite

difficult when developing this project, but at the same time new knowledge and experience are

also gained.

6.4 FUTURE WORKS

Every developer has the aims to improve their system in future when they explore more

knowledge and technologies. For this application system, the future work that comes is to

implement geo location plug-in into searching the company location module so that the

application can pin point the location of the internship and ease the student to find the location

that located. Besides, implement post notifications to user which are student, company and

administrator by email or notification reminder so that user can easily notify the status of the

application system.

61
6.5 CONCLUSION

As a conclusion, MyIntern aimed to help student find their proper internship and for the

companies to offer internship in a short period. This application system is to achieve a

remarkable level of perceived innovation and creativity for student to find the internship easily

by using mobile application as a platform.

62