Internship Report

An Internship Report submitted

for the partial fulfillment of the degree of

Bachelor of Engineering in

Electronics and Instrumentation

Session 2023 -2024

Guided By: Submitted By:

Mr.Ajay Verma sir Anjali Bamne

20E8008

DE20220

Department of Electronics and Instrumentation

engineering

Institute of Engineering & Technology

Devi Ahilya Vishwavidyalaya, Indore (M.P.)

www.iet.dauniv.ac.in

April 2024
]

Report Approval Sheet

The internship report on “mera bharat” submitted by ANJALI

BAMNE(20E8008) is approved as partial fulfillment for the award of Bachelor of
Engineering in Electronics and Instrumentation degree by Devi Ahilya
Vishwavidyalaya, Indore.

Internal Examiner External Examiner

IET-DAVV

Director

Institute of Engineering & Technology

Devi Ahilya Vishwavidyalaya,

Indore (M.P.)
 ABSTRACT
This project is an HTML,CSS or PHP based application that can be accessed
by anyone who want information of Travel. This is an integrated applications that
contains both User Component and Managerial Component. All the records must be
updated regularly to give user correct and helpful information. The main purpose is
to help travel companies to manage customer and hotels etc. the system can also be
used for both professional and business trips. The proposed system maintains
centralized repository to make necessary travel arrangements and to retrieve
information easily.

TRAVEL WEBSITE When people leave their usual environment, they come into
contact with new people, new sights, new experiences, and new ideas.

That exposure allows individuals to learn more about themselves and the world
around them, creating greater internal and societal awareness.

For Travel Unity, travel experiences go beyond those involved airplane travel.

For us, travel includes:

 local experiences, like going to a restaurant in a different neighborhood, visiting a

cultural institution to see the exhibits or for an event, or joining a local tour
 regional experiences, like day trips or camping
 short and long-term relocation for school or work.
 Candidate Declaration

I hereby declare that the work which is being presented in this internship report in
partial fulfillment of degree of Bachelor of Engineering in Electronics and
Instrumentation at Institute of Engineering and Technology , Devi Ahilya
Vishwavidyalaya, Indore is an authentic record of our own work carried out under
the supervision and guidance of Poonam Pawar(HR Manager) , Second Digital
Solutions Pvt. Ltd.

We are fully responsible for the matter embodied in this internship report in case of
any discrepancy found in the internship report and the internship report has not been
submitted for the award of any other degree.

Date:

Place:

ANJALI BAMNE
 ACKNOWLEDGEMENTS

We are using this opportunity to express our gratitude to everyone who

supported us throughout the project. We are thankful for our aspiring guidance,
invaluably constructive criticism and friendly advice during the project. We are
sincerely grateful to them for sharing their truthful and illuminating views on a
number of issues related to the assignments.
We express our warm thank to our Head of Department Ajay Verma sir for
their support and guidance.
We would also like to thank my assignment guide Mr. Ajay Verma sir and all
the people who provided me with the facilities being required and conductive
condition for my project.

ANJALI BAMNE
BE 4TH YEAR

20E8008
TABLE OF CONTENTS Page No
Internship Certificate i
Report Approval Sheet ii
Candidate Declaration iii
Acknowledgements iv
Abstract v
Chapter 1 Introduction
1.1 Overview and issues involved 1
1.2 Problem Definition 2
1.3 Solution domain 3
Chapter 2 Literature Survey
2.1 Methodology 4-8
2.2 conceptual requirement 9-10
2.3 feasibility analysis 10-14
Chapter 3 Analysis & Design
3.1 Software Requirements 15-16
3.2 Hardware Requirements 16-17
3.3 Analysis Diagrams 17
3.4 Design Diagrams 18
Chapter 4 Implementation and Testing
4.1 Implementation Diagrams 19-20
4.2 Test Cases 20-23
4.3 Challenges/Solutions
Chapter 5 Conclusion
 Chapter1- Introduction

1.1 Overview and issues involved

TRAVEL WEBSITE When people leave their usual environment, they come into contact with new people,
new sights, new experiences, and new ideas.

That exposure allows individuals to learn more about themselves and the world around them, creating
greater internal and societal awareness.

For Travel Unity, travel experiences go beyond those involved airplane travel.

For us, travel includes:

 local experiences, like going to a restaurant in a different neighborhood, visiting a cultural institution to see
the exhibits or for an event, or joining a local tour
 regional experiences, like day trips or camping
 short and long-term relocation for school or work.

1.2 Problem Definition

Existing System
• In the present system a customer has to approach various agencies to find details of
places and to book tickets.
• A customer may not get the desired information from these offices and often the
customer may be misguided.
Disadvantages ofthe Existing System
• This often requires a lot of time and effort.
• It is tedious for a customer to plan a particular journey and have it executed properly

Considering the great impact of system analysis on the overall project development a systematic a
detailed analysis was conducted for the development of production management and analysis
system. Study was conducted to determine the initial scope of the system. Preliminary investigation
comprising of request Clarification feasibility study etc were carried out.
The current search method is manual and it was a failure, as it could not meet the entire requirement
of the prospect clients. During analysis we studied manual system to find out their functionality
deficiencies. The fact-finding activities on system study produce detail that describes current
operation and point to areas where improvement is needed or possible. To evaluate the existing
system analysis considers the current system capacity including the people, equipment, storage
space, time and procedure involved.
During analysis of the manual search we have identified many drawbacks as following-
  Manual process requires as more resources like manpower, documents and other expenses related to
manpower. Registers maintain ace, storage space ,and to Handel this register more and timely
information is needed.
 Searching time increase and it is complicated task because we have to search all the available
register for getting successful and complete information.
 Manual system is dependent system as it has number of people and must work together for running
system successfully.
 For manual search customer have to go shop.

The entire operation in the organization on was manual. There was an urgent need to switch over to an
interactive visual environment. The change to the visual environment from the manual environment was
seen as sufficiently beneficial to the organization in the long run. Also the detailed analysis of the
production was required, which involves in minute data keeping and calculations as. Thus there was
need of an accomplished . Easy to use, providing report with better clarity for analysis.

1.3 SOLUTION DOMAIN

Proposed System
• The proposed system is a web-based application and maintains a centralized
repository of all related information.
• Users can decide about places they want to visit and make bookings online for travel
and accommodation.

Advantages ofthe Proposed System

• This often requires a less amount of time and less effort.
• It is easy for a customer to plan a particular journey and have it executed properly.

Chapter2- Literature Survey

2.1 Methodology

SOFTWARE ENGINEERING PARADIGM APPLIED

Software Engineering is essentially a set of steps that comprise of methods, tools and processor. These steps
are referred to as software engineering paradigms.
THE FOLLOWING POINTS EMERGE WITH THESE PARADIGMS
1. For a developer to be produced what these paradigms.
2. It is necessary to have some mechanism of systematically capturing the details of what is
required.
3. It is important to a review mechanism, so that every logical point the client can check
whether the progress is indeed as per his requirement and if there any deviation it can be
corrected right there.
4. It is necessary to have properly documented requirement.
We have adopted waterfall model to make our project
Following Points Emerge with these PARADIGMS
For a developer to be able to produce these paradigms,
It is necessary to have some mechanism of systematically capturing the details of what is required.
It is important to review a mechanism of systematically, so that every logical point the client can
check whether the progress is needed as per his/her requirement and if there are any deviation it can be
corrected right there.
It is necessary to have properly documented requirement.
We have adopted waterfall model to make our project-
The project follows linear sequential software development model.
The development of the application is achieved by using the control based construction approach.
Control is given by ASP.NET .
The application is developed within a short period of time.

Software Development Models

There are various software development models or methodologies. They are as follows:
1. Waterfall Model
2. V Model
3. Incremental Model
4. RAD Model
5. Agile Model
 6. Iterative Model
7. Spiral Model
8. Prototype Model

Waterfall Model Design

he Waterfall Model was the first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must
be completed before the next phase can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential flow. This means
that any phase in the development process begins only if the previous phase is complete. In this waterfall
model, the phases do not overlap.

Waterfall Model - Design

The Waterfall Model was the first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must
be completed before the next phase can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential flow. This means
that any phase in the development process begins only if the previous phase is complete. In this waterfall
model, the phases do not overlap.
Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure success of
the project. In "The Waterfall" approach, the whole process of software development is divided into
separate phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the next
phase sequentially.

The following illustration is a representation of the different phases of the Waterfall Model.
 Advantage Of Waterfall Model
Some of the major advantages of the Waterfall Model are as follows −
 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review
process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well document

SYSTEM DESIGN
System design provides the understanding and procedural details necessary for implementing into
the system study. Emphasis in on installing the performance requirements into design specification. The
design phase is a transition from user-oriented documents (system proposals) to a decremented oriented to
the programming or database personal.
2.2 Conceptual Requirements
2.3 Feasibility Analysis
FEASIBILITY STUDY
Depending on the result of the initial investigation the survey is now expanded to a more detail
feasibility study. “FEASIBILITY STUDY” is a test of system proposal according to its workability, impact
of the organization, ability to meet needs and effective use of the resources. It focuses on these major
questions-
1. What are the user’s demonstrable needs and how does a candidate system meet them?
2. What resources are available for given candidate system?
3. What are the likely impacts of the candidates systems on the organization?
4. Whether it is worth to solve the problem?
During feasibility analysis for the project following primary area of interest are to be
considered. Investigation and generating ideas about a new system does this.

STEPS IN FEASIBILITY ANALYSIS

There are eight steps involved-
1. From a project team and appoint a project leader.
2. Prepare system flowcharts.
3. Enumerate potential proposed system.
4. Define and Identify characteristics of proposal system.
5. Determine and evaluate performance and cost effective of each proposed system.
 6. Weight system performance and cost data.
7. Select the best proposed system.
8. Prepare and report final project directive to management.

TECHNICAL FEASIBILITY
A study of resources availability that may affect the ability to achieve an acceptable system. This
evaluation determines whether the technology needed for the proposed system is available or not.

 Can the work for the project be done with current equipment existing software technology
available personal?
 Can the system be upgraded if developed?
 If new technology is needed then what can be developed?
 This is concerned with specified equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may include.

FRONT-END AND BACK-END SELECTION

An important issue for the development of the project is the selection of suitable front-end and back-
end. When we decided to develop the project, we went through an extensive study to determine the most
suitable that suits the need of the organization as well as helps in development of the project. The aspects of
our study included the following factors-
FRONT-END SELECTION:
1. It must have a GUI that assist employees that are not from IT background.
2. Scalability and extensibility.
3. Flexibility
4. Robustness
5. According to the organization requirement and the culture.
6. Platform Independent
BACK-END SELECTION:
1. Multiple user support
2. Efficient data handling
3. Provide inherent future for security
 4. Popularity
5. Efficient data retrieval and maintenance
6. Secured Procedure
7. Operating system compatible
8. East to install
9. Various drivers must be available
10. Easy to implant with the front-end.

ECONOMICAL FEASIBILITY

Economic justification is generally the “bottom line” consideration for most system. Economic
justification includes a broad range of concerns that includes post benefits analysis. In this we weight the
cost and benefits associated with the candidate system and if it suits the basic purpose of the organization i.e.
profit making, the project is making to the analysis and design phase.

2.3 COST ESTIMATION

Cost Estimation Of Project
Estimation is the process of finding an estimate, or approximation, which is a value that can be used for
some purpose even if input data may be incomplete, uncertain, or unstable.
Estimation determines how much money, effort, resources, and time it will take to build a specific system or
product. Estimation is based on-

 Past Data/Past Experience

 Available Documents/Knowledge
 Assumptions
 Identified Risks
The four basic steps in Software Project estimation are-

 Estimate the size of the development product

 Estimate the effort in person-months or person-hours.
 Estimate the schedule in calendar months. Estimate the project cost in agreed country.
Observation On Estimation

 Estimation need not be a one-time task in a project. It can take place during-
o Acquiring a Project
o Planning the Project
o Execution of the project as the need arises.
  Project scope must be understood before the estimation process begins . it will be helpful to have
historical Project data.
 Project metrics can provide a historical perspective and valuable input for generation of quantitative
estimates.
 Planning requires technical managers and the software team to make an initial commitment as it
leads to responsibility and accountability.
 Past experience can aid greatly.
 Use at least two estimation techniques to arrive at the estimates the and reconcile the resulting
values. Refer Decomposition Techniques in the next section to learn about reconciling estimates.
 Plans should be iterative and allow adjustments as time passes and more details are know.

General Project Estimation Approach

Thr project estimation approach that is widely used in Decomposition technique. Decomposition
techniques take a divide and conquer approach. Size, Effort and Cost Estimation are performed in a
stepwise manner by breaking down a project into major functions or related software Engineering
activities.
Step 1: Understand the scope of the software to be built.
Step 2: Generate an estimate of the software size.

 Start with statement of scope.

 Decompose the software into functions that can each be estimated individually.
 Calculate the size of each function.
 Derive effort and cost estimates by applying the size values to your baseline productivity
metrics.
 Combine function estimates to produce an overall estimate for the entire project.
Step 3: Generate an estimate of the effort and cost. You can arrive at the effort and cost estimates by
breaking down a project into related software engineering activities.

 Identify the sequence of activities that need to be performed for the project to be completed.
 Divide activities into tasks that can be measured.
 Estimate the effort ( in person hours/days)required to complete each task.
 Combine effort estimates of tasks or activity to produce an estimate for the activity.
 Obtain cost units (i.e. , cost/unit effort) for each activity from the database.
 Compute the total effort and cost for each activity.
 Combine effort and cost estimates for each activity to produce an overall effort and cost estimate
for the entire project.

Chapter3- Analysis & Design

3.1 Software Requirements

 USER REQUIREMENT

 Requirement Analysis
 Requirement Specification
Requirement analysis includes the following activities

REQUIREMENT ANALYSIS-
REQUIREMENT INVESTIGATION- Using a variety of tools skills i.e. various fact-finding
techniques, requirements investigations was carried out and the resultant features documented for further
analysis.
The Following Fact Finding Techniques were used-
 INTERVIEWS: Unstructured interview methods was used which included a question and answer
format to acquire information about the system, the respondent being the user of the proposed
system, the respondent being the user of the proposed system thus, the facts about the actual
requirements about the actual requirements and the expected results etc, were gathered.
 OBSERVATIONS: Because we have to design a network administrator controls so we choose
VB.NET have the class information use to connect the Network and Socket information.

REQUIREMENT SPECIFICATION:
The description of new features for a system carried out in the following three interrelated parts:
 ANALYSIS FOR ACTUAL DATA:

The data collected during the fact finding study was examined thorouly to determine whether the
new system to meet the demands of client what the system should consist of.

 IDENTIFICATION OF ESSENTIAL REQUIREMENTS:

-How the present system works-

-How they represent their data to the external users,

 SELECTION OF REQUIREMENT FULFILMENT STRATERGIES-

Various methods and processes the would be used to achieve the stated requirements was discussed
and selected, thus forming the basis for system design.

3.2 hardware requirements

HARDWARE SPECIFICATION
S.No. HARDWARE SERVER-SIDE CLIENT-SIDE

1. RAM 4 GB 4GB

2. Processor Intel core Intel core

3. Hard-Disk 8 GB 8 GB

4. Floppy Drive 1.44 MB 1.44 MB

5. Monitor Color Color

6. Mouse Serial Serial

3.3 Analysis Diagrams

3.4 Design Diagrams

Chapter 4- Implementation &Testing

4.1 Implementation diagram.

4.2 Test Cases

Testing is a process of executing a program with the indent of finding an error. Testing is a crucial
element of software quality assurance and presents ultimate review of specification, design and
coding.
System testing is an important phase. Testing represents an interesting anomaly for the software.
Thus a series of testing are performed for the proposed system before the system is ready for user
acceptance testing.
A good test case is one that has a high probability of finding an as undiscovered error. A successful
test is one that uncovers an as undiscovered error.
Testing Objectives:
1. Testing is a process of executing a program with the intent of finding an error.
2. A good test case is one that has a probability of finding an as yet undiscovered error.
3. A successful test is one that uncovers and undiscovered error.
Testing Principles:
1. All the test should be traceable to end user requirements.
2. Test should be planned long before testing begins.
3. Testing should begin on a small scale and progress towards testing in large.
4. Exhaustive testing is not possible.
5. To be most effective testing should be conducted by a independent third party.
The primary objective for test case design is to derive a set of tests that has the highest livelihood for
uncovering defects in software. To accomplish this objective two different categories of test case
design techniques are used. They are

 White Box Testing

 Black Box Testing
White-Box Testing:
White box testing focus on the program control structure. Test case are derived to ensure that all
statements in the program have been executed at least once during testing and that all logical
conditions have been executed.
Black-Box Testing:
Black box testing is designed to validate functional requirements without regard to the internal
workings of a program. Black Box testing mainly focuses on the information domain of the
software, deriving test cases by partitioning input and output in a manner that provides through
test coverage. Incorrect and missing functions, interface errors in data structures, error in
functional logic are error falling in this category.
Test Strategies:
A strategy for software testing must accommodate low-level tests that are necessary to verify
that all small source code segment has been correctly implemented as well as high-level tests
that validate major system functions against customer requirements.
Testing Fundamentals:
Testing is a process of executing program with the intent of finding error. A good test case is one
that has high probability of finding an undiscovered error. If testing is conducted successfully it
uncovers the errors in the software defects present.
Testing Information Flow:
Information flow for testing flows the pattern. Two class of input provided to test the process.
The software configuration includes a software requirements specification, a design specification
and source code.
Test configuration include test plan and test cases and test tools. Tests are conducted and all the
results are evaluated. That is test results are compared with expected results. When erroneous
data are uncovered, an error is implied and debugginh commences.
Unit Testing:
Unit testing is essential for the verification of the code produced during the coding phase and
hence the goal is to test the internal logic of the modules. Using the detailed design description
as a guide, important paths are tested to uncover error with in the boundary of the modules.
These tests were carried out during the programming stage itself. All units of Vienna SQL were
successfully tested.
Integration Testing:
Integration testing focuses on unit tested modules and build the program structure that is dictated
by the design phase.
System Testing:
System testing tests the integration of each module in the system. It also tests to find
discrepancies between the system and its original objective, current specification and system
documentation. The primary concern is the compatibility of individual modules. Entire system is
working properly or not will be tested here, and specified path ODBC connection will correct or
not, and giving output or not are tested here these verifications and validations are done by
giving input values to the system and by comparing with expected output. Top-down testing
implementing here.
Chapter 5- Conclusion

5.1 Conclusion
The package is designed in such a way that future modifications can be done easily. The following
conclusions can be deduced from the development of the project.

 Automation of the entire system improves the efficiency.

 It provides a friendly graphical user interface which proves to be better when compared to the
existing system.
 It gives appropriate access to the authorized customers depending on their permissions.
 It effectively overcomes the delay in communication for table booking.
 Updating of information becomes so easy.
 System security, data security and reliability are the striking features.
 The system has adequate scope for modification in future if necessary.
REFRENCES(START IN NEW PAGE)
1. Video references
 https://youtu.be/R1djM9B0ay0
 https://youtu.be/1SnPKhCdlsU

2. Website references
 https://web.dev/learn/?gclid=CjwKCAjw0a-SBhBkEiwApljU0h-
Q2dtzc2zBTdtpgZLxSivnvU-
HcgOMM6FFFylabMJeidjXqGN_axoCkXcQAvD_BwE#principles
 https://www.tutorialspoint.com/asp.net/index.htm