“RESUME BUILDER”

A Minor Project Report

Submitted in partial fulfillment of the requirements for the
Award of degree of Bachelor of Computer applications

2020 – 2023

Submitted by: - Guided by :-

Sarthak Malhotra Mr. Daljeet singh bawa

0201BCA045

Rudraksh Seth

0201BCA039

Laksh Gupta

0201BCA032
 STUDENT UNDERTAKING

This is to certify that the project titled “Resume Builder” submitted to

Bharati Vidyapeeth (Deemed to be University), Pune in partial fulfilment
of the requirement for the award of the degree of Bachelor of Computer
Applications is an original work carried out under the guidance of Mr.
Daljeet Singh Bawa. The matter embodied in this project is a genuine
work done by me and has been submitted neither to this University nor to
any other University for the fulfilment of the requirement of the course of
study.

Name of the Student:- Sarthak Malhotra

ERPID:0201BCA046

PRN No: 2020100255

Name of the Student:- Rudraksh Seth

ERPID:0201BCA039

PRN No: 2020100237

Name of the Student:- Laksh Gupta

ERPID:0201BCA032

PRN No: 2020100211

 Bharati Vidyapeeth  
(Deemed to be University) 
Institute of Management & Research, New Delhi 
A Grade Status Awarded by MHRD, Govt of India, re-accredited with Grade A+ by NAAC
An ISO 9001:2015 14001:2015 Certified Institute 
A-4, Paschim Vihar, New Delhi – 110063
__________________________________________________________________________________
Ref: Date:

CERTIFICATE FROM GUIDE

This is to certify that the minor project report titled “Resume Builder” Submitted to
Bharati Vidyapeeth (Deemed t o b e University) Institute of Management
and Research, New Delhi in partial fulfilment of the requirement for the award of
the Bachelor of Computer applications is an original work carried out by “Name of
the Student” under my guidance. To the best of my knowledge and belief the matter
embodied in this project is genuine work done by the student and has been submitted
neither to this University nor to any other University for the fulfilment of the
requirement of the course of study.

Mr. Daljeet Singh Bawa

( Project Guide)
 Bharati Vidyapeeth  
(Deemed to be University) 
Institute of Management & Research, New Delhi 
A Grade Status Awarded by MHRD, Govt of India, re-accredited with Grade A+ by NAAC
An ISO 9001:2015 14001:2015 Certified Institute 
A-4, Paschim Vihar, New Delhi – 110063
__________________________________________________________________________________
Ref: Date :

CERTIFICATE FROM DIRECTOR

This is to certify that the Project titled “ Resume Builder ” is an
academic work done by “ Sarthak Malhotra , Rudraksh Seth and
Laksh Gupta ” submitted in partial fulfilment of the requirement, for
the award of the Degree of Bachelor of Computer applications, from
Bharati Vidyapeeth (Deemed to be University), Pune. It has been
completed under the guidance of Mr. /Ms./Dr
The authenticity of the project work will be examined by the viva-voce
examiner, which includes data verification, checking duplicity of
information etc., and it may be rejected due to nonfulfillment of quality
standards set by the Institute.

Dr. Yamini Agarwal

Director
 ACKNOWLEDGEMENT

I would like to express my gratitude and appreciation to all those who

gave me the possibility to complete this report. A special thanks to our
Minor project Guide Mr.Daljeet Singh Bawa whose help, stimulating
suggestions and encouragement, helped me to coordinate our project
especially in writing this report topic and achieving the goal as well as his
encouragement to maintain our progress in track. I would to appreciate
the guidance given by other supervisor as well as the panels especially in
our project presentation that has improved our presentation skills by their
comment and tips.
 INDEX

CHAPTER 1 INTRODUCTION page no.

1.1 Introduction about Project

1.2 Need of Computerization of System/ Problem in existing system

1.3 Proposed Software (What would S/W accomplish?)

1.4 Importance of the Work/project

CHAPTER 2 SYSTEM ANALYSIS

2.1 Analysis Methodology /requirement gathering techniques

2.2 Feasibility Study

2.3 Choice of Platforms

2.3.1 Software used

2.3.2 Hardware used

CHAPTER 3 SYSTEM DESIGN

3.1 Process Model used

3.2 Database Design (ERD/Data Dictionary/ Table Design)

3.3 Functional Design (DFD)

3.4 Interface Design (Screen shots of forms)

3.5 Output Design (Screen Shots of Report)

CHAPTER 4 TESTING AND IMPLEMENTATION (OPTIONAL FOR BCA-II SEM)

4.1 Testing Methodology (Types)

4.2 Testing Methodology applied (Why)

 4.3 Test Cases

4.4 Test Data

4.5 Gap Analysis (Planned Vs Achieved)

4.6 Rework/ Retest

4.7 Hardware & Software Requirement

4.7.1 Hardware Requirement

4.7.2 Software Requirement

CHAPTER 5 CONCLUSION AND REFERENCES

5.1 Conclusion

5.2 Limitation of System

5.3 Future Scope for Modification

5.4 References/ Bibliography

ANNEXURES
A-1 Menu Flow Diagram

A-2 Sample Input

A-3 Sample Output

A-4 Program Code

A-5 Mentor Feedback Report

A-6 Plagiarism certificate

 CHAPTER 1 INTRODUCTION

1.1 Introduction about Project

1.2 Problem in existing system

1.3 Need of Computerization of System

1.4 Proposed Software (What would S/W accomplish?)

1.5 Importance of the Work/project

1.1 INTRODUCTION ABOUT THE PROJECT-

The Project title as “RESUME BUILDER” is a web based Application aimed for
managing the information i.e., educational, personal details of persons &
professional details of freshers as well as experienced employees of Noble
Organization.
1.2 Problem in Existing System
The existing system of the resume builder is prepared in the MS-Word Application
software. The Format which is designed is manual. But creating different resume
formats is not easy. To reduce the burden we have developed this software. The
different processes involved are:

1
1. Excess of Manual work: There is lots of manual work in existing system
because there are more chances of mistakes in handwritten work.
i. Increase Cost: One of the biggest
limitations of paper-based phonebook
management system is the associated
costs. Documentation, record keeping,
storage, etc. is a very costly process.
ii. Lack of Security: If the user done any
work manually so there are more
chances of spreading necessary
information and it is very important to
secure the personal data of any user.
Manually work can easily goes into
wrong hands and this creates a huge
problem in database system.
iii. Time Consuming: Managing manually is
very tough and takes a lot of time and
more chances of mistakes and there is a
need of more employees in the huge
information.
iv. Costly: Manual work can easily increase
the cost related to paper and time because
manual work is less secure and there are
chances of leaking of various information
related to admission.
v. Insufficient space: Manual can take up
a pictorial amount of storage space,
and the need of space will increase
as the number of the document

2
 expands. Because of this the
paperwork also increase and records
will also increase leads to insufficient
space.

1.3 Need of Computerization of System

1.3.1 Reduce time: This software mainly helps for reduce the time of
employees because paperwork takes a lot of time and there are
chances of mistakes in handwritten data. One of the objective
of this software is that it helps in reduce time and it helps the
employees very much in finding the data easily and providing
the helpful environment to them.
1.3.2 Reduce paper work: The another need of this software help to
reduce the paper work because finding accurate data in papers is
very difficult and it may create mistakes and there is need of
more employees in paper work but this software is easily
accessed by any administrator or a officer member who knows
the login id and password of the software program.
1.3.3 Effective: The another need of this software is that it is very
effective which means it achieves the desired output in less time,
it helps the user to maintain their record easily and helps in
finding the data in very effective manner, as we all know data
related to any organization is very crucial and any mistake is not
acceptable in these records.
1.3.4 Efficient: This software works in very efficient manner because
its helps in achieving the goal in very less cost. Moreover, this
software is very robust no outside user can use this program

3
 without knowing the id and password Make work easier: The
main objective of this software it helps in maintaining all records
in very easier way either its related to organization record or its
related to modification or deletion of any employee and inventory
record in database management system.

1.4 Proposed Software

The proposed system tries to solve the problems mentioned above. The main
objective of the proposed system is to provide information instantly as and when it is
required. The main objective is to make the RESUME BUILDER details more efficient.
This system should maintain different data files and resume formats, so that the data
can be retrieved easily and in an efficient manner. The system is very interactive. It
should ensure process integration to the desired extent, various reports should be
generated as the need be. This system should also ensure that there is no
redundancy in the recorded data.

1.4.1 Advantages of proposed system:

1. To store all details of the persons i.e. personal, educational, and skill details, so that it
provides better services to users.
2. The proposed system provides efficient management of resumes.

3. Because of computerization manual work is eliminated and manual errors can be overcome
easily.

1.5 Importance of the work/project-

The project is very simple and easy in design. The project requires very low system
properties . The system will work in almost all patterns.

It has the following importance:

4
⮚ Enhancement:

Project concentrations to improve and upgrading its efficiency and effectiveness.

⮚ Automation:

Project automates each and every activity of the manual system and increases its
throughput.

⮚ Accuracy:

Project provides user accurate result when the user required it.

⮚ User-Friendly:

Project has a very user-friendly interface. User can easily work on the project .
The software provides accuracy result.

⮚ Maintenance Cost:

Reduce the cost of maintenance.

5
 CHAPTER 2 SYSTEM ANALYSIS

2.1 Analysis Methodology /requirement gathering techniques

2.2 Feasibility Study

2.3 Choice of Platforms

2.3.1 Software used

2.3.2 Hardware used

6
2.1 Analysis Methodology /requirement gathering techniques

It is the task of creating a list of requirements (functional system, technical, etc.) from
the various end user like (customers, users, vendors, IT staff, etc.) that will be used as
the basis for the requirements definition. It is an important part of any project and
project management.

There are many types of requirements gathering techniques. Some of them are:

1. Facilitated sessions
In a facilitated session, you bring a larger group (five or more) together for a
common reason or purpose. Here we are trying to gather a set of common
requirements from the group in a faster manner than if you were to interview
each of them separately.
2. Questionnaires
Questionnaires are used to capture the requirements from end users in remote
locations or those who will have only major input into the complete
requirements. Questionnaires can also be used when you have to collect data
from dozens, hundreds, or thousands of people.
3. Use cases
Use cases are basically stories that describe how individual processes work. The
stories include people and describe how the solution works from the user
perspective. Although the use cases may need to be distilled later into the
more particular detailed requirements.
4. Brainstorming
On few projects, the requirements are not “uncovered” as much as they are
“discovered”. In other words, the solution is brand new and needs to be
developed as a set of ideas that people can agree to. After all the ideas are
developed, the participants prioritize the ones they think are the best for this
solution. The resulting consensus of best ideas is used for the basic
requirements.
7
We will do this task in our project so that efficiency and effectiveness of our project
will increase.

2.2 FEASIBILITY STUDY

As we all know that each and every project needs to have a feasibility study for the
complete understand ability of the entire system. Basically, it is an assessment of the
practicality of a proposed plan or system or method.

A project feasibility study is a comprehensive report that examines in detail about the
system. It is an evaluation of a proposed system or project to determine if it

(1) is technically feasible

(2) is feasible within the estimated cost

(3) will be profitable.

A feasibility study is a initial study understands before the real work of a project starts
to certain the likelihood of the project success.

2.2.1 ECONOMIC FEASIBILITY

The procedure is to determine the benefits and savings that are expected from a
customer side and compare it with the costs. If your profits outweighs costs, then the
decision is made to design and put into the system. We have designed a software
through which we can maintain the Item record so manual labour cost is reduced.
Otherwise, further changes are made in the proposed system.

There are some points which tell how our project is economic feasibility is
possible:

● It will reduce Manpower cost

● It will increase our profits by making this software
8
2.2.2 TECHNICAL FEASIBILITY

Technical feasibility is one of the earliest studies that must be regulate after the
project has been identified. In large engineering projects consulting agencies that have
abounded staffs of engineers and technicians conduct technical studies dealing with
the projects. our project is technical feasible as the user can perform various search
operations with different search criteria and this will ultimately reduce the time and
increase the efficiency. In this intermediate labour cost will reduced and improves
staff efficiency.

2.2.3 BEHAVIORAL FEASIBILITY:

. It is type of prediction that in future till now much extended the user staff
(stakeholder) are interested in computerized system. Basically, an estimation of
knowledge (maximum) of stakeholder.

. In the organization, management and their team are educated enough and knows the
value of time, money and energy.

. All them are doing this work as a mark of charity. Therefore, they would like to
waste their time in useless things.

2.2.4 OPERATIONAL FEASIBILITY

It is a measure of how accurately a system fix the problems, and takes merit of the
opportunities find during scope definition and how it assures the requirements
recognize in the requirements analysis phase of system development. In these manual
efforts will be reduced by providing this software.

9
2.3 CHOICE OF PLATFORM

2.3.1 HARDWARE REQUIREMENTS

 Processor : Intel i5-8250u Central Processing Unit

1.60 GHz

1.80 GHz

(8th Generation)

 Clock speed : 1000MHz

 System bus : 64 bits

 RAM : 8 GB of RAM

 HDD : 1 TB

2.3.2 SOFTWARE REQUIREMENTS

 Operating System : Microsoft Windows 10

 Programming language : Javascript, Bootstrap,

JQuery, Sweetalert

 Software : XAMPP

10
 CHAPTER 3 SYSTEM
DESIGN

3.1 Process Model used

3.2 Database Design (ERD)

3.3 Functional Design (DFD)

3.4 Interface Design (Screen shots of forms)

3.5 Output Design (Screen Shots of Report)

11
3.1 Process Model used

In our project , we use this Waterfall model because it can serve as a useful process
model in situations where requirements are fixed and work is to proceed to
completion in a linear manner.

• Requirement analysis – All the possible requirements of the systems are gathered
and

documented in a requirements specification document. We gather each and every

12
possible requirement of the customer.

• System design – The requirements of the first phase are being studied and then the

system is prepared. It helps in specifying the hardware and software requirements

and

helps in defining the architecture of the system. On the basis or requirements

gathered,

the car is shown available.

• Implementation – With inputs from the system design, the system is developed in

small programs called units which are being integrated. Each unit is developed and

tested for functionality performance. With the help of system design, suitable code
is

generated.

• Testing – The entire system is tested for any kind of faults or failures. Small units of

entire code is tested separately here.

• Deployment – Once the testing is being done, the product is being deployed in the

customer environment or released into the market.

• Maintenance – To enhance the product some better versions are released. So for
this,

maintenance is done to deliver the changes in the customer’s environment.

13
All these phases are linked to each other in which progress is seen as flowing
downwards

through the phases. The next phase is started only when the previous phase is being

completed.

3.2 Functional Design (Data Flown Diagram)

A data flow diagram (DFD) is a graphic representation of the "flow" of data through

an information system, modelling its process aspect. A DFD is often used as a initial
step to create an overview of the system, which can later be elaborated.

0 Level DFD

contact
management

Email people
management management
Phonebook
management
system

login address
management management

14
 3.2.1 ER DIAGRAM

User email
name
address

User role Login password

Log in
User
name
User

Has
User Phone

Admin
id/name
Admin password
administrator

User name
EmpUser email

User contact
Manage User info.

User email
add User role
address

user Quantity

Delete
contact address

15
3.3 Input Design

User role

user

16
17
3.4 Output Design

18
CHAPTER 4 TESTING AND
IMPLEMENTATION

4.1 Testing Methodology (Types)

4.2 Testing Methodology applied (Why)

4.3 Test Cases

19
 4.4 Implementation (Techniques)

4.5 Gap Analysis (Planned Vs Achieved)

4.6 Retest

4.7 Rework

4.8 Hardware & Software Requirement

4.8.1 Hardware Requirement

4.8.2 Software Requirement

4.9 Post implementation (implement technique)

4.1 Testing Methodology (Types)

Testing is a process of executing a program with the significance

of finding an error. A good test is one that has high
probability of finding the yet unfound error. Testing should
regularly uncover different classes of errors in a minimum
amount of time with a minimum amount of efforts .A
software composition that includes a software requirement
specification, a design specification and source code.

1. A software composition that includes a test plan and procedure, any testing
tool and test cases and their expected results.

20
 Testing is divided into several distinct operations:

1. Unit Testing

Unit test comprises of a set tests performed by an individual

program earlier to the integration of the unit into large
system. A program unit is usually the minor free functioning
part of the whole system. Module unit testing should be as
complete as possible to ensure that each representation
handled by each module has been tested. All the units that
makeup the system must be tested independently to assure
that they work as required. During unit testing some errors
were lifted and all of them were rectified and handled well.
The result was so simple satisfactory and it worked well.

2. Integration Testing

It is the phase in software testing in which specific software

modules are combined and tested as a group. It happen after
unit testing and before validation testing. Integration testing
takes as its input modules that have been unit tested, groups
them in big modules, keep tests defined in an integration test
plan to those aggregates, and delivers as its output the
coordinate system ready for system testing.

4.2 Testing Methodology Applied (Why)

The purpose of integration testing is to confirm functional,

performance, and reliability requirements placed on major
design items. These design items i.e., assembles are
exercised through their interfaces using testing, success and
error cases being pretend via relevant guideline and data
21
 inputs. Test cases are build to test whether all the elements
within assembles interact correctly or not, for example across
procedure calls or process activities, and this is done after
testing individual modules, i.e., unit testing. The idea of a
building block approach, in which confirm assembles are
added to a verified base which is then used to support the
testing of further assembles .Software Integration Testing is
executes according to the Software Development Life Cycle
(SDLC) after module and functional tests. The cross-
dependencies for software integration testing are: schedule
for integration testing, strategy and selection of the tools
used for integration, define the cyclomatic complexity of the
software and software architecture, reusability of modules
and life-cycle/ versioning management

4.3 Test cases.

4.3.1 Characterstics of a good test case -

*ACCURATE : EXTRACT THE PURPOSE.

*ECONOMICAL : NO UNECESSARY STEPS OR WORDS.

*TRACEABLE : CAPABLE TO TRACE THE REQUIREMENTS.

*REPEATABLE : CAN BE USED TO EXECUTE THE TEST OVER AND OVER.

*REUSABLE : CAN BE REUSED

4.3.2 Test case table

22
Test Case Test Test Steps Test Data Expected Actual Pass/Fail
ID Scenario Results Results

T101 Check Run Username= User shouldAs expected Pass

owner application rudraksh be able
login with Enter Password=abcd to login
valid Username
data Enter
Password

T102 Check Run Username= User shouldAs expected Pass

customer application rudraksh not be
login Enter able to
with Username Password=aaaa login
invalid Enter
data Password

T103 For add Enter you Enter your User As Pass

Choice choice: should excepted
accordingly 4 add

T104 For Enter you Enter your User As Pass

view, Choice choice: should excepted
search , accordingly 4 view,
update search ,
update

T105 For Enter you Enter your User As Pass

delete Choice choice: should excepted
accordingly 4 delete,

23
TEST CASE 101 : Check owner login with valid data

24
TEST CASE 102: Check customer login with invalid data

25
TEST CASE 103 : For add

26
27
28
TEST CASE 104 : For view, search ,update

search

29
Update

30
TEST CASE 105 : Deleting Contacts

31
32
4.4 Implementation

After testing of the system , proposed system is installed at the Shop. Implementation
is a process of switching the manual system with a newly developed system and
making it useful without disturbing the functionality of the organisation.

There are 3 types of implementation

1) Fresh Implementation

2) Replacement Implementation

3) Modified Implementation

4.5 Gap Analysis (Planned Vs

Archived)

 GAP analysis and its results, which reveals problems and issues of the process of
implementation of quality management system. Basic precondition for the success of
33
application of the quality management system application is the understanding of the
quality management system standard as the tool for achieving the vision of the
organization

The structure of introduced form of GAP analysis is retrospectively aimed at filling

differences in how the process of implementation of the management system should
have been performed in order to be linked to the vision and policies of the organization,
which are based on own research and experience of the author. 

4.6 REWORK/RETEST

If there is any error, it is important to rectify it.

Also, it should be rechecked and retested on different parameters after a specific

period of time.

Checking and making compatibility is also necessary.

4.7 Hardware & Software Requirement

4.7.1 HARDWARE REQUIREMENTS

Processor : Intel Pentium CPU N3540 @ 2.16GHz

RAM : 2 GB

HDD : 40 GB

4.7.2 SOFTWARE REQUIREMENTS

OS : Microsoft-(Windows 7, 8, 8.1, 10)

Front end : Java Runtime Environment (JRE),

Java Virtual Machine (JVM)

34
(Back-end) : MySQL

4.9 Post implementation

A post implementation review is an evaluation of a system in terms of the extent to

which the system accomplishes stated objective system accomplishes stated objective
and actual project cost exceeds initial estimates.

It is normally carried out the people who have an independent view point and are not
responsible for the development and maintenance of the system while evaluating a
system , the following points are normally considered.

1) Performance Evaluation

2) Cost Analysis

3) Time Analysis

4) User Satisfaction

5) Documentation Review Plan

6) Hardware Review Plan

7) Ease for modification

8) Failure Rate

35
CHAPTER 5 CONCLUSION AND
REFERENCES

5.1 Conclusion

5.2 Limitation of System

5.3 Future Scope for Modification

5.4 References/ Bibliography

36
 5.1 CONCLUSION

The project “ PhoneBook Management System” is completed, satisfying the need

design for specifications. The system provides a user-friendly interface. The software
is developed with modular approach. All modules in the system have been tested with
valid data and invalid data and everything work accordingly. Thus the system has
fulfilled all the target or goals identified and is able to replace the existing system.
The constraints are met and overcome successfully. The system is designed as like it
was chooses in the design phase. This software has a user-friendly screen that allow
the user to use without any inconvenience.

The application has been tested with live data and has provided a outstanding result.
Hence the software has proved to work efficiently.

5.2 LIMITATIONS OF SYSTEM

1. Existing system refers to the system that is being observe till now. The existing
system requires more computational time, more manual work, and the complexity
involved in Selection of features is high.

2. After inserting the data to database, staff need not to worry about the orders
received through the system and hence decrease the manual labour. But in early years
it is not easy for the staff to modify the whole records manually and it also increases
labour of the employees.

3. Existing system requires large paper work and even a small transaction require
many papers fill.

37
4. Loss of even a single paper led to difficult situation because all the papers are
connected with each other.

5. In existing system it is not easy to share data. Also the two departments in an
organization cannot interact with each other without the real movement of data.

5.3 Future Scope for Modification

To avoid all these limitations and make the working more perfectly the system needs
to be computerized.

with some more modification this phonebook can also be converted to a data
management software for customer employees detail by simply adding employee id ,
its salary etc .

5.4 References/ Bibliography

Some Java Programming learning books are:

i. Core_Java Vol-1_Fundamentals by Cay S. Horstmann.

ii. Effective_Java by Herbert Schildt.

iii. Java–The_full_Reference by Herbert Schildt.

Some of the java programming apps

iv. Java NetBeans 8.2

v. Eclipse
Some of the Database apps

vi. XAMPP

vii. SQLite3

viii. MySQL

38
Some websites are:

 https://www.javatpoint.com/java-tutorial

 https://www.tutorialspoint.com/java

CHAPTER 6 ANNEXURES

A-1 Menu Flow Diagram

A-2 Sample Input

A-3 Sample Output

A-4 Program Code

A-5 Mentor Feedback Report

A-6 Plagiarism certificate

39
 6.1 Menu Flow Diagram

PHONEBOOK MANAGEMENT
SYSTEM

Main Menu

Admin
person

View its detail

Add New Contact

List All Contact

40
Search For Contact
Update /edit contact

Delete Contact

Use case diagram

41
6.2 SAMPLE INPUT

42
43
Adding new contact

44
45
Login via admin/officer
46
List All Contact

47
Search for contact

48
Update contact

49
Deleting Contacts

50
51
52
login via user

53