St.

Lawrence College
Affiliated To
Tribhuvan University
Institute of Science and Technology

Internship Report
On
Front End Web Development
At
Touchstone Infosys Pvt. Ltd.

In partial fulfilment of the requirements for the Bachelor’s Degree in Computer

Science and Information Technology

Submitted to
Department of Computer Science and Information
Technology St. Lawrence College
Institute of Science and
Technology Tribhuvan University

Under the Supervision of

Mr. Tika Dahal

Submitted by
Tul Bahadur Rai (7387/072)
 MENTOR’S RECOMMENDATION

I hereby recommend that this report has been prepared under my supervision by Tul
Bahadur Rai on “Front End Web Development of Dental Appointment System” in
partial fulfillment of the requirements for the degree of BSc. in Computer Science and
Information Technology, be processed for evaluation.

..........................................

Mrs. Tulasa Khakurel

Technical Director
Internship Mentor
Touchstone Infosys Pvt. Ltd., Kathmandu
 SUPERVISOR’S RECOMMENDATION

I hereby recommend that this report has been prepared under my supervision by Tul
Bahadur Rai in partial fulfillment of the requirements for the degree of BSc in Computer
Science and Information Technology be processed for evaluation.

…………………..……….
Mr. Tika Dahal
Faculty, St. Lawrence College
(Supervisor)
 CERTIFICATE OF APPROVAL

We certify that we have read this dissertation work and in our opinion, an internship report
submitted by Tul Bahadur Rai is satisfactory on the scope and quality as a dissertation in
the partial fulfillment for the requirement of Bachelors of Science in Computer Science and
Information Technology.

Evaluation Committee

Mr. Tika Dahal Mr. Rajeev Khadka

Faculty, St. Lawrence College Head Of Department,
Computer Science and
Technology

Internal Examiner External Examiner

 ACKNOWLEDGEMENT

This intern report is prepared in the partial fulfillment of the requirements for the degree of
Bachelor in Computer Science and Information Technology. The satisfaction and success
of completion of this task would be incomplete without heartfelt thanks to people whose
constant guidance, support and encouragement made this work successful.

Firstly, I would like to give my gratitude towards my mentor Mrs. Tulasa Khakurel,
senior Web developer, for her unquestionable support. Without her support and
encouragement, it would have been difficult to work on.

I would also like to thank supervisor Tika Dahal who is also the program co-ordinator of
St. Lawrence College, for his invaluable encouragement, guidance and ever willingness to
spare time from his otherwise busy schedule.

I would like to dedicate our hearty gratitude to Touchstone Infosys Pvt. Ltd for providing
us with an opportunity to do internship at this reputed organization with full support and
cooperation. I would also like to thank Mrs. Tulasa Khakurel, Senior Project Manager
and entire mentors for their unquestionable support.

At the end, I would like to express my sincere thanks and appreciation to all my colleagues,
family and others who have helped me directly or indirectly during this internship period.

Tul Bahadur Rai

T.U. Exam Roll No: 7387/2072

i
 ABSTRACT

Dental Clinic Appointment System (DCAS) is a web based application that helps patient to
make an appointment with the dentist at dental clinic. Only the patient that have been registered
in DCAS be able to use the system. It is run by highly qualified and experienced health
professionals. This website covers Admin panel, Doctor panel, Receptionist panel and Patient
panel. User can perform search by doctor specialty, gender, and doctor name. User can
browse through doctors profile and view their specialty information. The register user can
choose and book an appointment at the flexible time and date. They can confirm or cancel
their reservation. And also allow dental clinic’s staff are able control and maintain patient
information through a computerized process.

This report provides an insight on the internship work carried out as the back end developer
of Dental Clinic Appointment System. This Dental Clinic Appointment System project was
originally developed in Code Igniter framework and thus the report includes the project re-
written in Laravel.

Keywords: Dental Clinic Appointment System, Flexible, Code Igniter , Laravel

 Table of Contents
ACKNOWLEDGEMENT...........................................................................................................i

ABSTRACT................................................................................................................................ ii

LIST OF TABLES.....................................................................................................................vi

LIST OF FIGURES.................................................................................................................. vii

LIST OF ABBREVIATIONS..................................................................................................viii

CHAPTER 1

INTRODUCTIO

1.1 Introduction to Internship.....................................................................................................1

1.1.1 Introduction to Project...............................................................................................1

1.1.2 Scope of Project.........................................................................................................2

1.1.3. Limitation of Project.................................................................................................2

1.1.4. Brief Introduction of Organization...........................................................................2

1.1.3.1. Introduction.........................................................................................................2

1.1.3.2. Contact Information............................................................................................3

1.1.5. Internship Duration and Planning.............................................................................3

1.2 Statement of Problem...........................................................................................................4

1.3 Objective.............................................................................................................................. 4

1.3.1 Objectives of Internship.............................................................................................4

1.3.2 Objectives of Project..................................................................................................5

1.4 Roles and Responsibility......................................................................................................5

1.5 Motivation............................................................................................................................5

1.5.1 Motivation for choosing Touchstone Infosys Pvt. Ltd..............................................5

1.5.2 Motivation for choosing Web Development on Laravel...........................................5

1.6 Report Organization............................................................................................................. 7

CHAPTER 2
SYSTEM

ANALYSIS
2.1 Requirement Analysis.......................................................................................................... 8

2.2.1 Functional Requirements...........................................................................................8

2.2.2 Non Functional Requirements.................................................................................10

2.2 Feasibility Analysis............................................................................................................ 10

2.2.1 Technical Feasibility................................................................................................10

2.2.2 Operational Feasibility.............................................................................................10

2.2.2 Economic Feasibility...............................................................................................10

2.3 ER Diagram........................................................................................................................11

2.4 Dataflow Diagram.............................................................................................................. 13

2.5 Technical Requirements..................................................................................................... 14

2.5.1. Hardware Requirements..........................................................................................14

2.5.2. Software Requirements...........................................................................................14

CHAPTER 3

SYSTEM

DESIGN

3.1 Architectural Design...........................................................................................................15

3.2 Database Design................................................................................................................. 15

3.3 Process Design....................................................................................................................17

CHAPTER 4

IMPLEMENTATION

4.1 Tools Used..........................................................................................................................18

4.1.1 Front End Tools.......................................................................................................18

4.2 Development Methodology................................................................................................ 20

CHAPTER 5

TESTING

5.1 Browser Compatibility Testing.......................................................................................... 21

5.2 Functionality Testing ……………………………………………………………………21

5.2 Responsive Testing........................................................................................................22-23

5.3 Unit Testing........................................................................................................................23

CHAPTER 6

CONCLUSIO

6.1 Conclusion..........................................................................................................................24

6.2 Lessons Learnt....................................................................................................................24

References

Appendix: Screenshots
 LIST OF TABLES

Table 1.1: Contact Details of an Organization...........................................................................3

Table 1.2: Internship Duration....................................................................................................3

Table 5.1: Test Result for Login..............................................................................................22

 LIST OF FIGURES

Figure 2. 1: Use Case Diagram of the Project............................................................................9

Figure 2. 2: ER Diagram of DCAS..........................................................................................11

Figure 2. 3: ER Diagram of DCAS Receptionist Panel...........................................................12

Figure 2. 4: Context Diagram of DCAS...................................................................................13

Figure 2. 5: Level-1 DFD of DCAS.........................................................................................14

Figure 3. 1: Architectural Design of the System......................................................................15

Figure 3.2: Database Schema for DCAS..................................................................................16

Figure 3.3: System Workflow..................................................................................................17

 LIST OF ABBREVIATIONS

BSc CSIT Bachelor in Science in Computer Science and Information Technology

DCAS Dental Clinic Appointment System

CSS Cascading Style Sheet

DFD Dataflow Diagram

ER Entity Relationship

HTML Hypertext Markup Language

MVC Model View Controller

PHP Hypertext Pre Processor

RDBMS Relational Database Management System

TU Tribhuvan University

XML Extended Markup Language

TSI Touchstone Infosys
 CHAPTER 1

INTRODUCTION

1.1 Introduction to Internship

An “internship” is defined by the National Society for Experiential Education (NSEE) as: “a
carefully monitored work or volunteer experience in which an individual has intentional
learning goals and reflects actively on what he or she is learning throughout the experience”.
Internship can simply be described as the transition from study to work which is necessary
component in order to develop a student's skill, making them more advanced and diligent
when they finally have the opportunity to be a part of working world. An internship program
is quite different to a job as the main objective of intern is to look for "hand on" work
experience in the real world aligned to the academic studies of students. The only goal of
internship is to fulfill the missing link between academic studies and work experience.

1.1.1 Introduction to Project

A web-based application is any application that uses a web browser as a client. The term may
also mean a computer software application that is coded in a browser supported programming
language (such as JavaScript, combined with a browser-rendered markup language like
HTML, PHP) and reliant on a common web browser to render the application executable.
Web applications are popular due to the ubiquity of web browsers, and the convenience of
using a web browser as a client, sometimes called a thin client. The ability to update and
maintain web applications without distributing and installing software on potentially
thousands of client computers is a key reason for their popularity, as is the inherent support
for cross-platform compatibility.
The DCAS has been developed to override the problems prevailing in the practicing manual
system. Moreover this system is designed for the particular need of the company to carry out
operations in a smooth and effective manner. The application is reduced as much as possible
to avoid errors while entering the data. It is a user-friendly system. DCAS can lead to error
free, secure, reliable, and fast management system.
The system will be developed to realize the functionality of the system to help the patients at
dental clinic. DCAS is developed using the HTML, CSS/Bootstrap, JAVASCRIPT , PHP ,
MySQL, AJAX, Laravel.

1
1.1.2 Scope of Project
The system can be implemented in private dental clinic. The aim of this system is to manage
the patient’s information and appointment. The chance of loosing data can be minimized. All
the required reports can be generated. Only admin can update the database. Other users will
only be able to view the records.

1.1.3. Limitation of Project

A software solution is never 100% perfect and error free. Like other software systems, this
system is also not perfect. Since, the system is re-written the changes in features and modules
varies accordingly and it needs to be modified according to the client requirements.
Currently, the system is in developing phase and is not live yet. The system still consists of
some bugs and flaws that can be seen which needs further research to make it more functional
and accurate than the current.

1.1.4. Brief Introduction of Organization

1.1.4.1. Introduction
Touchstone Infosys (TSI) is a global professional services company, providing a broad range
of services and solutions in strategy, consulting, digital and technology. It is situated in Old
Baneshwor, Kathmandu. TSI believe in empowering with information, building relationships
and taking social responsibilities. To make software easier for people to use and operate, it
performs a huge level of testing and debugging through qualified professionals and native
users. The main strategy is to discover and analyze the project to find the best possible
solution for a product that contains all the possible current technologies and methodologies
and test them in developer and user level.

TSI mission is to provide a digital solution for website, CMS, e-commerce, and web
application. For each of the solution it focuses on making it efficient, user friendly as well as
cost effective. TSI works with languages and technologies like Node.js, PHP with Laravel,
MySQL, WordPress and some other development tools.

2
1.1.4.2 Contact Information
Following are the contact details of the Touchstone Infosys Pvt. Ltd.
Table 1.1: Contact Details of an Organization

Address Old Baneshwor-10, Kathmandu

Phone No: 01-4460878

Email [email protected]

Website www.touchstoneinfosys.com

1.1.5 Internship Duration and Planning

As per the requirement of the curriculum of B. Sc. CSIT. 8th Semester, the minimum
requirement of internship period is 10 weeks/180 hours. It consists of different phase of
training or tasks performed with a specific objective for each phase. Each phase shows the
progress of intern in internship. It also consists of information about how and when interns
will accomplish objectives of each task. Here is my internship duration in table 1.2.

Table 1.2 Internship Duration

Office Hour 10:00 am – 5:00 pm

Working Hour 7 Hours per day

Working Days 6 days a week

Position Web Developer

Total Duration 3 months

Mentor Mrs. Tulasa Khakurel

1.2 Statement of Problem
Making an appointment with the dentist is the one of the procedure to use the
facilities in the dental clinic. Usually, when the patients wish to make an appointment,
they have to go to the clinic. In the situation, sometime it will because the problems
occurred.
As all of us know, people are busy with their daily life routines; they do not have
enough time to go to the clinic to make an appointment with the dentist if they got the
problem about their teeth. Some of the problem here is where the patients need to go to
the clinic to make an appointment with the dentist. So, they must spend the time from
their daily life. For patients that live far from the clinic, it more difficult to them to go to
clinic just to make an appointment. It is because, if the patients are a worker, they must
spend the time within their office hour to go to clinic to make an appointment. The time
that was taken to move from office to hospital will affect their time. Sometimes, it will
increase the pressure, stress and fatigue from that move. Other then time constraint, the
patients also must spend their money to go to clinic.
To develop the system at dental clinic, I need to have some information about the
system requirement that currently use at the clinic, so that an enhancement of the system
can be analyzed. The current system that used in dental clinic is using a manual system
where the patients have to go to the clinic to make an appointment. For the
enhancement, patients do not need to attend to the clinic for making an appointment with
the dentist. They just send a message to clinic management to make an appointment via
their mobile phone.

1.3 Objective
The internship program was done to fulfill the academic requirement of B. Sc. CSIT 8 th
Semester. An internship provides a variety of benefits for the young workers who want to
broaden their chances for landing in a job and jump-starting their careers. The main
objectives of the internship project were to understand how the application works in real
time.
The following are the internship objectives that were to be achieved:

1.3.1 Objectives of Internship

 To assist students in focusing their interests, thus aiding in their professional career.
 To give students the opportunity to re-examine their career objectives and explore the
 variety of opportunities in the field of computer networking.
 To be technically and organizationally eligible to work in the future after the completion
of academic degree.
 To be able to work in team, maintain good public relation and develop strategic problem
solving skills.

1.3.2 Objectives of Project

 The goal of this system is to improve the management of the public dental clinic.
 Hospital in appointment and records management also the objective of this project is to
ensure the workflow in the clinic will be more systematic and organize.
 Next is to assist people to make an appointment to get the dental services at the clinic
with online.
 To improve records keeping system for the organization.

1.4 Roles and Responsibility

During the internship tenure, Author was provided with comfortable work space at the
organization. For the three month duration of internship, author had a placement in Web
Application Development under the supervision and mentorship of Mrs. Tulasa Khakurel. The
author was guided with the organizational resources by supervision team. All the facilities and
resources were given to the author by the organization so as to carry out the works and do
certain activities like researches, development and any other tasks smoothly.
The roles and responsibilities are given to the author during internship are as follows:
 Use the search-ask-learn paradigm while learning various technologies for project
development.
 Complete the tasks assigned by the supervisor.
 Update the supervisor on regular basis.
 Focus on developing a professional solution compared to a working solution.
Understand the working patterns of the organization.
1.5 Motivation
1.5.1 Motivation for choosing Touchstone Infosys Pvt. Ltd.
Touchstone Infosys (TSI) is a global professional services company, providing a broad range
of services and solutions in strategy, consulting, digital and technology. It is a privately held
company based in Kathmandu, Nepal, offering offshore partnership to clients in information
management systems to local and international clients. It provides a digital solution for
website, CMS, e-commerce, web application and works with languages and technologies like
Node.js, PHP, WordPress and other developmental tools. It’s a group of young, motivated,
and skilled people whose main goal is to provide their clients with an innovative solution
regarding web development and software development. Whether it’s a mobile application, a
content-rich responsive website, its work is built for scale, performance and longevity.

As per the requirement of the Tribhuvan University (TU), the final year students of B.Sc.
CSIT are required to complete a six credit (minimum ten weeks/180 hours long) internship as
a part of the course requirement. Internship is one of medium that helps to break down the
bars between the professional and the student life. Since, an internship is the course
curriculum of TU, every student perusing BSc. CSIT need to do the internship in any area of
their interest. So, the first motivation for choosing TSI was to fulfill my academic
requirements. Besides
this, working as an intern in the organization I also got the opportunity to work in real-time
projects which motivated me to work more towards my area of interest.

1.5.2 Motivation for choosing Web Development on Laravel

Web development is a smoothing path to develop an application. It’s not just about one thing,
to start with the web development one needs to have good hand in HTML, CSS, and
JavaScript along with other programming language like PHP, JAVA, etc. Laravel is one of
the open source Php framework that is popularly used by the web developers because of its
simplicity, beautiful and expressive syntax which is easy to learn and maintain for the
developers developing innovative products and increasing their service quality. There are a
lot of off-the-shelf solutions for web development but among them laravel is the one that
gives the solution for scalable web application with unique interface and functionality that
can be easily classified. It also supports the MVC (Model, View, Controller) architecture
which helps in improving the overall performance, better documentation and offer multiple
functionalities.

1.6 Report Organization

Chapter 1: Introduction puts emphasis on Overview, Problem Statement, Objectives, Scope
and Limitation of the project.
Chapter 2: Requirement and Feasibility Analysis the important sections such as,
Requirement Analysis and Feasibility Analysis. Requirement Analysis explains Functional
and Non- functional requirements of the project, and Feasibility Analysis explains why/how
the project is practical to be implemented.
Chapter 3: System Design gives the design of the system developed so that it can be used
during the project implementation.
Chapter 4: Implementation provides an indication of how the system is implemented, what
tools / platforms have been used.
Chapter 5: Testing clarifies the system workflow.
Chapter 6: Conclusion marks an end to the document by summing up the entire project and
also opening the door further for research in improving the developed system. The lesson
learnt is also included in this chapter.
 CHAPTER 2

SYSTEM ANALYSIS

Generally, System development comprises of two major phases: System Analysis and System
Design. In System Analysis, the details of the existing system or proposed one is understood
and decided whether proposed system is desirable or not and decided whether the existing
system needs improvements. System analysis helps to understand the proposed system
architecture, working and goals. Thus, System Analysis can be summarized as the process of
investigating a system, identifying problems and using the gathered information to improve
existing system or develop the proposed one.

By interacting with clients, studying the documents provided by the clients, discussing with
the senior developers and studying the existing system we analyze the requirements of the
system to be developed for the clear view of how the system should be and how it should be
working so as to fulfill user requirements.

2.1 Requirement Analysis

This section presents complete set of functional and nonfunctional requirements. Functional
requirements are listed first according to their relationship to the overall system. The non-
functional requirements are listed after functional requirements. The functional requirements
have been specified using natural language description using UML analysis model.

2.2.1 Functional Requirements

Functional Requirements defines what the system must do. It defines the behaviors or
functions of a system, flows, business rules and other requirements of a system along with its
output. The functional requirements are discussed below:
 The users must login/register into the system.
 A user shall be able to search the appointments lists for all clinics.
 The system shall generate each day, for each clinic, a list of patients who are expected to
attend appointments that day.
 2.2.1.1. Use Case Diagram
Use case diagram is representation of user’s actions or interaction with system which can
perform in collaboration with one or more external users of the system. In this application,
the super admin adds and manages the admins, the added admins will then add manager,
course and packages then access the records and certificates, the manager then manages the
learner and access records and certificates, the learners view course details, purchase the
package, take exams and then access records.

activate
time schdeule account

services

login/logout

doctor admin
update profile

new user
register

appointment
patients receptionist

bill

Figure 2. 1: Use Case Diagram of the Project

2.2.2 Non Functional Requirements
Non-functional requirements define how the system should be. It covers all the remaining
requirements which are not covered by functional requirements. DCAS website is easy to use
and works without downgrading the performance. It follows some of the properties like
scalability, reliability, user-friendly, maintainability and usability

2.2 Feasibility Analysis

Feasibility Study is used to determine the viability of an idea. It is often used before the
actual implementation of the project. The objective of such a study is to ensure a project is
legally and technically feasible and economically justifiable. It tells us whether a project is
worth the investment.

2.2.1 Technical Feasibility

Technical feasibility involves evaluation of the hardware and the software requirements of
the proposed system. This application is developed using Visual Studio Code or Sublime text
editor, XAMPP, and MYSQL for database. Google Chrome and Mozilla Firefox are used to
run the application for facilitating user interface. So this system is technically feasible. All the
necessary hardware and software required for developing and installing the system are
available.

2.2.2 Operational Feasibility

Operational feasibility is dependent on human resources available for the project and involves
projecting whether the system will be used if it is developed and implemented. Our system
makes the maximum use of available resources including people, time and flow of forms. Our
system provides reliable services to the potential users and the user needs to be familiar with
using the application. This will enhance reduction in cost and increase in benefits for the
learners.

2.2.2 Economic Feasibility

Economic feasibility is the cost and logistical outlook for a business project or endeavor. We
considered various factors affecting the systems economic value and performance and
implemented the best one. The application is a web based for patient to make appointment
and so it is economically
feasible which means we can make the use of it at feasible cost and get much more benefit
from it. It requires not many resources except what we already have along with our
knowledge.

2.3 ER Diagram
ER-diagram represents how actually the database is designed. The relationships
among several existing entities are represented by means of E-R diagram. ER are also used in
conjunction with the Data Flow Diagrams (DFDs) in order to map out the information flow
of the system.

user_name fname mname

id

password
email lname

user_type
user 1 has dentist address
1

id
phone
user_name is_active
user_name 1

gender specialist

End_time
has
M
id timetable
user_name Start_time

dob
Day
fname
patient user_name
1 has
M
mname
patient_id
M
patient_note
lname
address doctor_note
phone gender Doctor_id
appointment
Day
id

Time
finished
type
cancelled
 Figure 2. 2: ER Diagram of DCAS

mname
user_name fname

lname
password id
email

user_type address
user 1 has 1 receptionist

id
phone

is_active user_name
user_name M

specialist
gender

invoiceno
patient_na has
me date
patient_id name
M
M

services
id bill summary gtotal id
1

discount
issued_by has
1
payable_amou
vat M
nt

id sub_services rate
has

M services_id name

sbill_id total
bill

id
quantity

particular rate

Figure 2. 3: ER Diagram of DCAS Receptionist Panel

2.4 Dataflow Diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects .A DFD is often used as a preliminary step
to create an overview of the system, which can later be elaborated.
• Process: A process takes data as input, execute some steps and produce data as output.
• External Entity: Objects outside the system being modeled, and interact with processes
in system.
• Data Store: Files or storage of data that store data input and output from process.
• Data Flow: The flow of data from process to process.

admin

Register
Verify doctor
services
& receptionist
& subservices

Schedulte time table

Schedule
appointment
Attends
doctor DCASB patient
appointment
Get
prescription
Provide
prescription

Check the a Register Print

ppointment details patients bill

receptionist

Figure 2. 4: Context Diagram of DCAS

The figure 2.3 shows the context diagram of the system. Different functionalities for various
users are represented. The users here are admin, dentist, patient, and receptionist. Every users
are assigned with the specific and designated tasks. For example, the admin is
responsible for the verification of dentists, receptionists and manage the services that are
provided to the user/patient, and services are also manage by the receptionist. Similarly,
Figure 2.5 shows the level-1 DFD of DCAS where the data stores and processes make up the
system along with the types of user.

2
Add services
Add services services d2 services
View services
View services

1
Verify dentist Not verified dentist
request d1 user
&receptionist & receptionist
admin Store the status
verified

3
Store schedule
Time
Schedule time d3 table
dentist Time table
View schedule
View schedule

Check the available time

4 Return the available time
Schedules
Save appointment
patient appointment appointment
View appointment View appointment d4 appointme
nt

Return services
Request
services
5
Create bills
Save bills
receptionist billing
Generate bills Billing Return bills d5

Figure 2. 5: Level-1 DFD of DCAS

2.5 Technical Requirements

2.5.1. Hardware Requirements
 The standard input devices like keyboard and mouse are to get input. The outputs are
generated and displayed on the screen.

2.5.2. Software Requirements

 Platform : Windows
 Programming Language : PHP
 Front End : Bootstrap/HTML/CSS/JavaScript, AJAX
 Back End: MySQL, Laravel
 CHAPTER 3

SYSTEM

DESIGN

Systems design is the process of defining elements of a system like modules, architecture,
components and their interfaces and data for a system based on the specified requirements.

3.1 Architectural Design

The system architectural design is shown below:

Bil Appointment
Schedule appointment

View own
Print the bill
appointment
Assign &
View

Receptionist Doctor Patients

Manage receptionist
Manage Doctor Schedule
their time
Based on day
Time Schedule
Admin

Services

Figure 3. 1: Architectural Design of the System

The architectural design of the system as shown above describes the view, models, behavior,
and structure of the overall system. The system follows a 3-tier architecture which is
composed of presentation tier, logical tier and data tier and for this, we have used MVC
pattern.

3.2 Database Design

Database design is the part of system development. The database design is divided into 3 steps:
 Conceptual database design
 Logical database design
 Physical database design
(Auer, 2006)
 dentist

PK id time_table
User
services PK id
FK user_name
PK id
PK id FK dentist_id
fname

email
name day
mname

password
lname start
sub_services
username
gender end
PK id
user_type
dob is_active
FK service_id
is_active
address
name appointment
receptionist phone
rate PK id
PK id specialist
FK dentist_id

FK user_name
patient FK patient_id

fname PK id
patient_note

mname FK user_name
doctor_note

lname
bill_detaile fname day

gender
PK id mname time

dob
FK sbill_id lname finished

address
particular gender cancelled

phone
rate dob ty pe

quantity address

total phone
bill_summary

PK id

FK issued_by

FK patient_id

patient_name

date

invoice_no

gtotal

discount

vat

payable_amou
nt

Figure 3.2: Database Schema for DCAS

The figure 3.2 represents all the tables and data structure along with the relationship between
them that are used in the project.

3.3 Process Design

Figure 3.3 shows the flow chart of the project. It shows that the users first login to the system
then according to their roles, they perform various activities.

user

Log into the

system

-Add Time
-Add Services
Schedule
Doctor Check Role Admin -Activate
-Check
Accounts
Appointment

Receptionist
Patient

-Check
appointment
-Register
-Schedule
Patient
appointment
-Print Bill

Stop

Figure 3.3: System Workflow

 CHAPTER 4

IMPLEMENTATION

The logical design of the system had to be built in the physical working system in the
implementation phase. MySQL is used as the backend database technology for implementing
the Html, CSS and Bootstrap are used for the front design of the system whereas the Laravel
framework is used as the programming part of the application.

4.1 Tools Used

4.1.1 Front End Tools
Front end development, also known as the client side development is the practice of
producing HTML, CSS and JavaScript for the website or web application so that a user can
see and interact with them directly. I was involved in the web development using PHP
framework Laravel as a backend tool, MySQL as a database, HTML as a markup, CSS as a
stylesheet, and Bootstrap as the CSS framework. The user interface was made more dynamic
by using client side script JavaScript

 HTML
HTML or the Hypertext Markup Language, is the standard markup language used to create
the web pages. HTML tags mostly come in pairs consisting of the start tag (<head>) and the
end tag (</head>) within the angle brackets. HTML documents are read by the web browsers
and are composed into audible or visible web pages. The browser does not display the HTML
tags but used the tags to interpret the contents of the pages. It forms the building blocks for
all the websites.
In this project, the HTML is used to create forms for users, profile, organization and
usergroup, its edition and update. The navigation bars for the respective models are also made
using the HTML.
 CSS
Cascading Style Sheet (CSS) is a style sheet language that is used to format the layout of the
web pages. CSS separates the document contents written in HTML or similar markup
languages from the document presentation including elements such as color, font, layouts,
etc. Such separation of documents provides more flexibility and control in the specification of
the presentation and improve content accessibility. Multiple style sheets can also be imported.
In this project, the navigation, header and footer sections are given the custom designs using
different CSS class and its properties.

 JavaScript
JavaScript (sometimes abbreviated JS) is a prototype-based scripting language that is
dynamic, weakly typed. JavaScript is a client side scripting language meaning that JavaScript
code is written into an HTML page. When a user requests an HTML page with JavaScript in
it, the script is sent to the browser and it's up to the browser to do something with it. It is used
to make webpage more interactive, check or modify the contents of forms, change images,
open new windows and write dynamic page content.
In the project DCAS, JavaScript is used for the dynamic function like responses of buttons
clicks.

 AJAX
Ajax  stands for Asynchronous JavaScript and XML is a set of web development techniques
using many web technologies on the client side to create asynchronous web applications.
With Ajax, web applications can send and retrieve data from a server asynchronously (in the
background) without interfering with the display and behavior of the existing page. By
decoupling the data interchange layer from the presentation layer, Ajax allows web pages
and, by extension, web applications, to change content dynamically without the need to
reload the entire page. In practice, modern implementations commonly utilize JSON instead
of XML.

 Bootstrap
Bootstrap is a free and open-source collection of tools for creating websites and web
applications (About, 2017). In this project Bootstrap is used to make the website responsive
to run on all type of devices. Bootstrap gives CSS and JavaScript to control the presentation
of content in HTML. I implemented Bootstrap CSS framework as it contains HTML- and
CSS
based design templates for typography, forms, buttons, and navigation and other interface
components

4.2 Development Methodology

Waterfall model is followed for developing the system. The different phases that are required
in this development methodology are requirement analysis, system design, implementation,
testing, development and maintenance. The Project Manager and senior developers analyze
all the functional and non-functional requirement of the system that needs to be developed.
Knowing the requirements for the system we get a clear understanding and view about what
the system is supposed to be.
After knowing the requirements for the system, now we define the overall architecture of the
system through designs like, ERD, DFD, Database schemas, etc. Php laravel framework is
used for the implementation and testing of the system. For the data storage MySQL is used
while XAMPP server for deployment.
 CHAPTER 5

TESTING

5.1 Browser Compatibility Testing

Browser compatibility test is the test done to ensure that site runs on all browsers i.e. chrome, safari
etc. these browsers run on different platforms so it is very important ensure that the theme is all
platform friendly.

S.N Test Case Test Browser Expected Result Actual Result Remarks

1 C1 Google Chrome Successful Successful Pass

2 C2 Opera Mini Successful Successful Pass

3 C3 Safari Successful Successful Pass

4 C4 Mozilla Firefox Successful Successful Pass

Table 4

5.2 Functionality Testing

Functionality testing involves checking links, pages, widgets, buttons, forms etc. This type of testing
can be performed by client also. Functionality testing is firstly done by developer and then after client
does it. Client first sees if all the requirement that they proposed meets or not and then feedbacks the
developer.

S.N Test Case Test Description Input Test Data Expected Result Actual Result Remarks

1 T-01 Visit View available Display available Display Pass

information information available
DCAS site
information
2 T-02 Login Fill username Redirect to Display the Pass
and password concern user concern
dashboard dashboard
3 T-03 Bill Fill and Click Display bills Get Bill Pass
Print bill
4 T-04 Appointment User fill the Appointment is Appointment is Pass
appointment created Schedule
5.3 Responsive Testing
Responsive testing is very important because theme should give majority of the users as they open the
site throughout the various devices like laptop, mobiles, tablets etc. In most of the cases, WordPress is
also responsive by default.

Fig:Mobile View

Fig: Tablet View

 Fig: Desktop View
5.4 Unit Testing
In unit testing, several modules and functions are individually tested. Some of unit testing performed
in testing of the themes are:

Test Case 1 (Top Header Section)

Test Successful

Test Case 2 (Left Menu) Test Case 3(Left bar Responsive)

Test Successful Test Successful

 CHAPTER 6

CONCLUSION

6.1 Conclusion
In current context, the increasing information Technology has built up the software
development trend. So to follow the trend internship provides a bridge for the industrial
environment for the undergraduate to learn and experience the real world. Internship has
helped in adapting well to working under pressure. Working with multiple features in a single
week long sprint and handling immediate and urgent bugs have assisted in enhancing
professionalism to meet deadlines. The technical tasks that were undertaken during the
internship period have helped the intern in improving software development and debugging
skills. It has helped in gaining knowledge about various technical tools and frameworks used
in software development and the process that should be followed for proper development
completion. Working as an intern in one of the popular IT companies of Nepal, has boosted
the confidence and has polished the professional as well as soft skills of the intern in the IT
sector. As whole, this report includes project and the internship experiences, findings,
knowledge and the technical skills.

6.2 Lessons Learnt

Through the internship from Touchstone Infosys, the lessons learnt were:
 Importance of time management and working with multiple features under pressure to
meet deadlines.
 Immediate handling of urgent bugs and fixing them.
 Understanding the differences between theoretical and practical knowledge.
 Working in team with coordination and cooperation to make quality decisions.
 Working as software developer can be considered as a potential career
References

About us. (2018). Retrieved from Touchstone Infosys:

http://www.touchstoneinfosys.com./index.php/about/

Auer, L. (2006, 08 22). Database Design and System Design. Retrieved from www2.amk.fi:

http://www2.amk.fi

Ian. (2006, 06 06). what is database schema. Retrieved from Database.guide:

http://database.guide/what-is-a-database-schema/

Kotak, M. (2017, jan 5). why laravel web development is best php framework. Retrieved from

Medium: https://medium.com/@maulikkotakstar/why-laravel-web-development-is-

best-php-framework-53b1f6b78d9e

Nilanchala. (2017, April 24). Introduction to laravel php framework features and version

history. Retrieved from stacktips: http://stacktips.com/tutorials/laravel/intro-to-

laravel- php-framework-and-features
Appendix: Screenshots
1. Login Page

Figure 1: Login Page

2. Admin Dashboard

Figure 2:Admin Dashboard

3. Add Service Form

Figure 3:Add Service Form

4.Dentist Dashboard

Figure 4 :Dentist Dashboard

5. Receptionist Dashboard

Fig 5: Receptionist Dashboard

6. Patient Dashboard

Figure 6: Patient Dashboard