Resume Builder
Resume Builder
ON
RESUME BULDER
To
(Assistant Professor)
Submitted By
Sumit kumar
UU2209000377
BCA-V
(Batch: 2022-2025)
ACKNOWLEDGEMENT
The most awaited moment of any endeavor is successful completion, but nothing can be done
successfully if done alone. Success is the outcome of contribution and consistent help of
many people, and we thank to those who have helped us in the successful completion of this
project. We would like to thank Director of USCS “Prof (Dr.) Sonal Sharma”, HOD of
USCS “Dr. Sameer Dev Sharma” for providing with all the necessary resources required to
complete this project. I am profusely thankful to the department, and my Project Mentor
“Mr. Deepak Bhatt”, Assistant Professor. He has been generous enough to provide me an
opportunity and accepting our candidature of the most valuable guidance and affordable
treatment given to us at every stage to boost our morale.
Student Name:
Sumit kumar
i
DECLARATION
I hereby declare that the project that the project report entitled ‘RESUME BUILDER’
submitted by Sumit kumar to Uttaranchal School of Computing Sciences, Uttaranchal
University. The project report was done under the guidance of Mr. Deepak Bhatt, Assistant
Professor- USCS. I further declare that the work reported in this project report has not been
submitted and will not be submitted, either in part or in full, for the award of any other degree
or diploma in this university or any other university or institute.
Sumit kumar
BCA IV-G
Roll No.: 56
ii
CERTIFICATE
This is to certify that Sumit Kumar, student of BCA 5 th semester session 2024-25 has
completed the project entitled: “RESUME BUILDER” using Advance Java language.
Her work is satisfactory to be submitted for the fulfillment of the award of degree of
BACHELOR OF COMPUTER APPLICATION.
iii
S.NO TITLE Page no.
i Acknowledgement i
ii Declaration ii
iii Certificate of originality iii
1 Introduction 1
2 Objective 2
3 System analysis 3
3.1 Identification of need 4
3.2 Preliminary investigation 5
3.3 Feasibility study 6
3.4 Project planning 7
3.5 Project Scheduling (Gantt Chart and Pert Chart) 9
3.6 Software Requirement Specification (SRS) 11
3.7 Data models 13
1 Flow chart 13
2 Context Flow Diagram (CFD) 14
3 DFD zero level 15
4 DFD first level 16
5 DFD second level 17
6 Use Case Diagram 19
7 State Diagram 21
8 Activity Diagram 22
9 ER Diagram 23
4 System design 24
4.1 Modularization Details 25
4.2 Data Integrity and Constraints 26
4.3 Database Design 27
4.4 User Interface Design 28
5 Testing 30
5.1 Testing Techniques and Testing Strategies used 31
5.2 Test Reports for Unit and System Test Cases 32
6 System Security Measure 34
7 Future scope 36
8 Coding 37
Bibliography
INDEX
iv
INTRODUCTION
A Resume builder is an online tool designed to assist Resume builder in creating
professional and effective Resumes. It simplifies the process of Resume creation by
providing pre-designed templates, customizable sections, and helpful tips. With a Resume
builder, individuals can easily input their personal information, work experience, education,
skills, and achievements into the template, resulting in a polished and well- structured
Resume. Resume builders offer a range of features that streamline the Resume writing
process.
These include spell-checking, formatting assistance. Many builders also provide industry-
specific templates and sample phrases to help tailor the Resume to a specific job or field.
Additionally, some Resume builders offer integration with job search platforms, allowing
users to directly. submit their Resumes to job openings. Overall, a Resume builder can save
users significant time and effort, enabling them to create professional Resumes without the
need for extensive design or formatting knowledge. It ensures that important details are
included. and presented in an organized manner, increasing the chances of catching the
attention. of employers and securing job interviews. A Resume builder is a valuable tool that
assists individuals in creating professional and compelling Resumes. In today's competitive
job market, having a well- crafted Resume is essential for securing employment
opportunities. A Resume builder simplifies the Resume creation process by providing
predesigned templates, helpful suggestions, and step-by-step guidance. It streamlines the
otherwise daunting task of organizing and presenting one's skills, qualifications, and work
experience in a clear and concise format.
1
OBJECTIVE
1. The aim of Resume Builder project is to provide a means by which candidates can
present themselves effectively through their resumes.
2. The main aim of this project is to secure and make privacy on related data over
manually data storage.
2
SYSTEM ANALYSIS
The system analysis of a Resume Builder encompasses a comprehensive evaluation of its
various components, functionalities, and operational aspects. It involves identifying
stakeholders, including law enforcement agencies, judicial entities, government bodies,
victims, witnesses, and the public. Requirements gathering is crucial, focusing on functional
aspects such as data entry, search and retrieval, analytics, reporting, and case management, as
well as non-functional considerations like security, reliability, and usability. The system
architecture is examined, including database design, user interface layout, integration points
with external systems, and security measures.
Data management strategies, including data collection, storage, processing, and retention, are
analyzed to ensure compliance with regulatory requirements and data protection laws.
Functional analysis delves into use cases, workflows, and task breakdowns to ensure
alignment with user needs and system capabilities. Usability and user experience
considerations are incorporated, along with security and privacy measures to safeguard
sensitive information.
Testing and validation procedures are outlined to ensure system functionality, integration,
security, and user acceptance. Implementation and deployment plans encompass rollout
strategies, training programs, and change management approaches. Maintenance and
evolution plans address ongoing system upkeep, enhancements, and lifecycle management.
Through a comprehensive system analysis, stakeholders can ensure the RB meets the needs
of law enforcement agencies, supports efficient crime prevention and investigation efforts,
and complies with regulatory requirements.
3
suspects, witnesses, and evidence, necessitating a centralized platform like a RB for efficient
data management.
These systems streamline data entry processes, ensuring accuracy and consistency while
minimizing the risk of errors. Crucially, they offer robust search and retrieval functionalities,
empowering law enforcement personnel to quickly access pertinent information based on
various criteria. Moreover, a RB facilitates comprehensive case management by enabling task
coordination, progress tracking, and documentation maintenance, fostering seamless
collaboration among investigators. Additionally, the analytical capabilities of a RB allow for
the identification of crime patterns and trends, informing data-driven decision-making and
resource allocation.
Security and compliance are paramount, with RBs implementing stringent measures to
safeguard sensitive data and ensure regulatory adherence. Integration with external systems
enhances interoperability, while user training and support ensure effective utilization.
Scalability and flexibility round out the needs, ensuring that the system can adapt to evolving
requirements and technological advancements, ultimately bolstering the efficiency, accuracy,
and effectiveness of crime record management for law enforcement agencies, thus
contributing to enhanced public safety and security.
Furthermore, it entails researching best practices and technological advancements in the field
of crime data management to inform the design and development of a RB tailored to the
specific requirements of the agency.
4
Additionally, preliminary investigations may involve conducting feasibility studies to assess
the viability of implementing a RB within budgetary and resource constraints. By conducting
this preliminary investigation, law enforcement agencies can lay the groundwork for the
successful implementation of a RB that enhances efficiency, accuracy, and effectiveness in
managing crime-related data, ultimately contributing to improved public safety and security.
5
associated with development, implementation, and ongoing maintenance, as well as the
potential return on investment.
Legal and regulatory considerations are crucial, ensuring compliance with data privacy laws,
evidence handling protocols, and other regulations. Schedule feasibility involves creating a
realistic timeline for implementation, considering potential risks and challenges that may
impact the project timeline. Finally, organizational feasibility examines the agency's
readiness for change, identifying potential barriers and developing strategies to promote user
acceptance and adoption of the RB. By conducting a comprehensive feasibility study, law
enforcement agencies can make informed decisions about whether to proceed with
implementing a RB and effectively plan for its successful deployment.
1. Scope Definition: Clearly define the scope of the RB project, including its objectives,
deliverables, and boundaries. Identify the functionalities and features that the system
will include, considering the needs of law enforcement agencies and stakeholders.
3. Resource Identification: Identify the resources required for the RB project, including
personnel, hardware, software, and budget. Allocate resources based on the project's
scope, timeline, and complexity, ensuring they are sufficient for successful
implementation.
6
5. Risk Assessment: Conduct a comprehensive risk assessment to identify potential
risks and uncertainties that may affect the project's success. Develop risk mitigation
strategies to address identified risks, minimizing their impact on the project timeline
and outcomes.
9. Training and Support: Develop a comprehensive training program for end-users and
administrators to ensure they are proficient in using the RB effectively. Provide
ongoing support and assistance to users, addressing any questions, concerns, or issues
that may arise during and after system implementation.
7
3.5. PROJECT SCHEDULING
Gantt Chart:
The Gantt Chart is a vital project management tool used to visually represent the timeline of
the Online House Renting System project. It outlines various phases and tasks, showing their
durations and key milestones, which helps stakeholders easily understand the project's
progress at a glance. This chart enables the project manager to track task dependencies and
resource allocation effectively, facilitating timely delivery of each project phase. By
providing a clear overview of tasks and their timelines, the Gantt Chart aids in identifying
potential bottlenecks, allowing for proactive adjustments to keep the project on track.
Overall, it serves as a critical reference point for both the project team and stakeholders to
monitor project status and ensure alignment with objectives.
8
Duration
42.5
37.5
32.5
27.5
22.5
17.5
12.5
7.5
2.5
Identification Feasibility System Anal- System De- Coding 27- Testing 06- Implementa-
of needs 16- Study 23-08- ysis 02-09- sign 10-09- 09-2024 05- 11-2024 17- tion 18-11-
08-2024 22- 2024 01-09- 2024 09-09- 2024 18-09- 11-2024 11-2024 2024 28-11-
08-2024 2024 2024 2024 2024
Duration 6 9 7 8 39 11 10
Pert Chart:
The PERT Chart (Program Evaluation Review Technique) is an essential tool for visualizing
the tasks and dependencies involved in the Online House Renting System project. It
illustrates the sequence of activities, helping to identify critical paths and estimate the
minimum time required for project completion. By representing tasks as nodes and their
relationships with arrows, the PERT Chart enhances project planning and supports effective
resource management. This visualization aids in understanding the interdependencies
between tasks, allowing project managers to allocate resources strategically and prioritize
tasks effectively. Additionally, the PERT Chart assists in risk management by highlighting
tasks that may impact the overall project timeline, enabling the team to address potential
delays proactively. Ultimately, it fosters improved communication among stakeholders by
providing a clear picture of the project’s workflow.
9
3.6. Software requirements specifications (SRS)
The SRS begins by defining the scope of the system, including its objectives, stakeholders,
and boundaries. It then delves into specific functional requirements, such as data entry, search
and retrieval, analytics, reporting, and case management, outlining the expected behavior and
interactions of the system. Non-functional requirements, such as security, reliability,
performance, and usability, are also detailed, specifying the quality attributes that the RB
must possess.
Additionally, the SRS addresses any legal and regulatory requirements, ensuring compliance
with data protection laws, evidence handling protocols, and other regulations. By providing a
10
comprehensive overview of the requirements for the RB, the SRS serves as a blueprint for
system development, guiding the design, implementation, and testing processes to ultimately
deliver a robust and effective crime record management solution.
Software used:
Frontend: HTML, CSS
Backend: JavaScript
Idle: NetBeans Version 11.2
Operating system: Window 10 above
Hardware used:
Processor – Intel core i5
RAM – 8 GB
Operating system – windows
Technology used:
Web deevelopment
11
3.7. DATA MODELS
1. Flowchart
12
13
3. DFD-Zero Level
14
4. DFD-First Level
15
5. DFD-Second Level
DFD-2.0.
16
6. Use Case Diagram
Use Case diagram Administrator view
17
Use Case Diagram viewers view
18
7. State Diagram
19
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
8.
Activity Diagram
20
9. ER-Diagram
21
22
SYSTEM DESIGN
The system design of a Resume Builder involves creating a blueprint for the architecture,
structure, and functionality of the system to effectively meet the requirements outlined in the
Software Requirements Specification (SRS).
The design encompasses various aspects, starting with the architectural design, which
outlines the overall structure of the system, including the database architecture, user interface
design, and integration points with external systems. Database design involves determining
the schema, tables, and relationships needed to store and manage crime-related data
efficiently, ensuring data integrity and security.
User interface design focuses on creating intuitive and user-friendly interfaces for different
user roles within the RB, such as law enforcement officers, administrators, and analysts. This
includes designing screens, forms, menus, and navigation paths to facilitate easy data entry,
search, and retrieval operations. Integration design involves defining interfaces and protocols
for seamless integration with external systems, such as fingerprint databases, CCTV
networks, and court records, enabling interoperability and data sharing.
Security design is crucial to safeguard sensitive crime data and ensure compliance with legal
and regulatory requirements. This includes implementing access controls, encryption
mechanisms, authentication mechanisms, and audit trails to prevent unauthorized access,
protect data confidentiality, and maintain data integrity.
Scalability and performance design considerations ensure that the RB can handle increasing
data volumes and user loads without sacrificing performance. This involves designing
scalable architecture, optimizing database queries, and implementing caching mechanisms to
improve system responsiveness and efficiency.
Finally, the system design includes error handling and recovery mechanisms to address
potential system failures, data corruption, or other issues that may arise during operation. By
carefully designing the architecture, user interfaces, integrations, security features, and
performance optimizations, the RB can effectively support law enforcement agencies in
managing and analyzing crime-related data, ultimately contributing to improved public safety
and security.
23
4.1. Modularization Details
The ResumeBuilder can be broken down into various independent modules that handle
specific functionalities. Some of these core modules include:
To ensure the integrity and quality of data, we define a set of constraints on the inputs within
the Resume Builder system.
24
2.1 NOT NULL Constraints
Ensure that certain fields must always have a value (i.e., cannot be empty or NULL). This is
useful for mandatory resume sections.
Ensure that certain fields or combinations of fields are unique across the database. This
avoids duplication and ensures that data like email addresses or resume titles are not repeated.
Example:
o email in the User Table should be unique (no two users should have the same
email).
o resume_title should be unique for each user in the Resumes Table (to avoid
having multiple resumes with the same title).
Ensure that the data entered in a field satisfies certain conditions or ranges. This can enforce
formats, value ranges, or logical rules.
Example:
o phone_number should contain only numeric characters and follow a specific
length or format.
o Experience Table: The experience_start_date should be before the
experience_end_date.
o Education Table: Graduation year should be a valid year (greater than the start
year, within reasonable ranges).
Enforce relationships between different tables to ensure that related data exists in the correct
order.
Example:
o Experience Table and Education Table reference the user_id in the User Table
to ensure that experience and education records belong to a valid user.
o Resume Table should reference a specific user and enforce referential
integrity.
The database design for a Resume Builder application is structured to manage various
entities and their relationships efficiently. At the core, the Users table holds essential user
details, such as name, email, and encrypted password. Each user can create one or more
resumes, which are stored in the Resumes table, with attributes like resume title, selected
template, and creation dates. The resumes are further detailed by several related tables:
25
Experience, Education, Skills, and Certifications, which store specific data about the user’s
work history, academic background, technical skills, and professional certifications. These
tables are all linked to the Resumes table through foreign keys, ensuring that each piece of
data is tied to a specific resume.
Additionally, the system tracks Languages spoken by the user and any User_Feedback
provided about the platform. To offer customization, a Templates table stores different
resume layouts, enabling users to choose the format for their resumes. When a resume is
exported (e.g., as a PDF or DOCX), details of the export are stored in the Exported_Resumes
table. This ensures the system maintains a history of all resume exports.
The User Interface (UI) Design for a Resume Builder should be intuitive, user-friendly, and
visually appealing to provide a smooth experience for users as they create and customize their
resumes. Here is a detailed breakdown of the key UI components and their design elements:
1. Homepage / Dashboard
The homepage or dashboard should offer an overview of the user's resume-building activities
and provide quick access to essential functions.
Navigation Bar: A fixed navigation bar at the top with links to:
o Home (Dashboard)
o My Resumes (Access and manage all resumes)
o Create New Resume (Start a new resume)
o Account Settings (User profile and preferences)
o Help/FAQ (Assistance)
o Logout
Welcome Section: A personalized greeting for the user, like "Welcome back, [User
Name]!".
Resume Overview: A grid or list of the user's existing resumes with a brief preview
(e.g., resume title, last edited date, template used). Each resume should have options
to:
o Edit (Take the user to the resume editor page)
o Delete (Remove the resume)
o Download (Export the resume in different formats like PDF, DOCX)
Call to Action: A prominent button to Create a New Resume, guiding users to start
building their first resume.
This is the core area where users can input data and design their resumes. The interface
should be clean and organized, with a split-screen layout, offering both the input fields and a
live preview of the resume.
26
Right Panel (Live Resume Preview):
o A dynamic view of the resume that updates as the user fills out fields. It
should reflect changes in real-time.
o Include options to Preview the resume in different formats (desktop, mobile)
to ensure responsiveness.
Save and Continue: Buttons to Save progress, with options for Draft or Final status.
27
TESTING
Testing for a Resume Builder application is crucial to ensure its functionality, usability, and
reliability. Below is a detailed overview of the types of testing that should be performed on a
Resume Builder application:
1. Functional Testing
Functional testing ensures that all features of the Resume Builder work as intended.
2. Usability Testing
Usability testing focuses on how easy and intuitive the Resume Builder is for users to
navigate.
Ease of Navigation:
28
o Ensure that users can easily navigate between sections (Dashboard, Resume Editor,
Export Page, Profile, etc.).
o Test that users can easily locate and understand key features such as "Create
Resume," "Edit," "Download," and "Export."
Error Messages:
o Verify that appropriate error messages are displayed when users input invalid data
(e.g., missing required fields, incorrect email format).
o Ensure that the system provides helpful guidance (e.g., form validation messages).
Help & Support:
o Test the availability and effectiveness of the Help/FAQ section and support
features.
Visual Consistency:
o Ensure that the UI is consistent across different sections (font styles, button
designs, and color schemes).
o Test responsiveness on different devices (desktop, tablet, and mobile) to ensure the
UI adapts properly.
3. Compatibility Testing
This testing ensures that the Resume Builder application works across various browsers,
operating systems, and devices.
Cross-Browser Testing:
o Test on popular browsers like Google Chrome, Firefox, Safari, and Edge to
ensure consistent behavior across them.
Cross-Device Testing:
o Test on various screen sizes, such as desktop monitors, tablets, and
smartphones, ensuring the resume builder is responsive and looks good on all
devices.
Cross-Operating System Testing:
o Test on different operating systems like Windows, macOS, and Linux to
ensure the application functions correctly.
4. Performance Testing
Performance testing ensures the application performs well under expected and peak usage
conditions.
Load Testing:
o Simulate multiple users accessing the platform at the same time to check if the
system can handle high traffic, especially during resume creation or export.
Stress Testing:
o Test the application under extreme conditions (e.g., thousands of simultaneous
users or large resume data) to ensure it doesn’t crash or fail.
Response Time:
o Ensure that resume creation, editing, and exporting operations are completed
within acceptable time limits (e.g., the time it takes to save or export a resume).
29
5. Security Testing
Security testing ensures that the resume builder is secure and user data is protected.
Data Protection:
o Ensure sensitive user data (e.g., passwords, personal details) is stored securely,
using encryption (e.g., bcrypt for passwords).
Authorization & Authentication:
o Test that unauthorized users cannot access or modify someone else’s resume.
o Test user authentication and verify proper session management (e.g., session
expiry, login/logout functionality).
Vulnerability Testing:
o Perform penetration testing to identify vulnerabilities such as SQL injection,
cross-site scripting (XSS), or cross-site request forgery (CSRF).
Privacy Compliance:
o Test that user data is not exposed publicly or to unauthorized users. Ensure
compliance with data privacy regulations (e.g., GDPR, CCPA).
6. Database Testing
Database testing ensures that the data is stored correctly and integrity is maintained.
Data Integrity:
o Verify that user data is correctly stored and retrieved from the database,
particularly when creating or updating resumes.
Data Consistency:
o Ensure that when a user makes changes (e.g., editing resume sections or
templates), the database is updated properly without duplication or corruption.
Backup & Restore:
o Test backup and restore functionality to ensure that data can be safely backed
up and restored in case of system failure.
7. Regression Testing
Regression testing ensures that new changes or features do not break existing functionality.
Feature Stability:
o Re-test previously working features (e.g., resume creation, editing, exporting)
after making updates or adding new features.
Bug Fixes:
o Verify that any previously identified bugs are resolved and that no new issues
have been introduced by the fixes.
8. Accessibility Testing
Keyboard Navigation:
30
o Ensure that the entire application is navigable using only a keyboard (e.g., for
users with motor disabilities).
Screen Reader Compatibility
Ensuring robust system security for a Resume Builder application is essential to protect
user data, prevent unauthorized access, and maintain overall integrity. Below are some key
security measures that should be implemented:
Enforce strong password requirements (e.g., minimum length, mixed case, numbers,
special characters) to ensure users create secure passwords.
Require users to change passwords periodically and prevent them from using
commonly used or weak passwords.
Implement two-factor authentication (2FA) to add an extra layer of security during the
login process. This can be done via email, SMS, or an authenticator app (e.g., Google
Authenticator).
Make MFA an optional but recommended security feature for user accounts,
especially for those with sensitive resume data.
Session Management:
Use secure session management practices such as generating random session tokens
that expire after a certain period of inactivity.
Ensure that sessions are securely handled, and implement session timeouts to log out
users after periods of inactivity.
Implement single sign-on (SSO) if applicable, to allow users to securely authenticate
via third-party services (e.g., Google, Facebook) while reducing the risk of storing
passwords.
Use role-based access control to manage different user permissions. For instance,
only administrators should be able to modify templates or manage user accounts,
while regular users should only have access to their own resumes.
2. Data Encryption
Encryption at Rest:
31
Store all sensitive user data (e.g., passwords, personal information, resumes) using
strong encryption techniques (e.g., AES-256). This ensures that even if the database is
compromised, the data remains unreadable without the decryption keys.
Encryption in Transit:
Use HTTPS (SSL/TLS) to encrypt data during transmission between the user's
browser and the server. This prevents interception of sensitive information, such as
login credentials or resume data, during communication.
Password Hashing:
Never store passwords in plaintext. Use secure hashing algorithms (e.g., bcrypt,
PBKDF2, or Argon2) with a salt to store password hashes. This protects users'
passwords even if the database is compromised.
Data Minimization:
Collect only the minimum amount of personal data necessary for users to create
resumes. Avoid storing unnecessary information, such as social security numbers,
unless absolutely required.
Implement strict access control mechanisms to ensure that only authorized users (e.g.,
account owners or admins) can access sensitive data.
Enable audit logs to track who accessed or modified certain data (e.g., resumes),
when, and from where. This can help in identifying potential security breaches or
suspicious activity.
Ensure that the system complies with data protection regulations such as GDPR
(General Data Protection Regulation) or CCPA (California Consumer Privacy Act).
Provide users with clear privacy policies and options to delete their accounts or
download/export their personal data in accordance with privacy laws.
32
FUTURE SCOPE
In future system will provide mail facility to editors. Editors can send mail to other
stations editor.
In future system will allow user is register complains online. In future system will
provide facility to send message.
The method of video conferencing can be added to make the project livelier
Users can view the progress of their complaint online.
The future technology user can view the case details and progress of the complaints
on their mobile phones.
33
CODING
HTML CODE
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Home Page</title>
</head>
<body>
<div class="container">
</a>
34
<div class = "bars">
</div>
</button>
</div>
</div>
</div>
</nav>
<h1 class = "lg-title">Only 2% of resumes make it pas the first round. Be in the top
2%</h1>
</div>
</div>
</header>
35
<div class="section-one">
<div class="container">
<div class="section-one-l">
</div>
<p class = "text">Getting that dream job can seem like an impossible task. We're
here to change that. Give yourself a real advantage with the best online resume maker: created by
experts, imporved by data, trusted by millions of professionals.</p>
</div>
</div>
</div>
</div>
</div>
<div class="container">
<div class="section-two-content">
36
<div class = "section-items">
</div>
<p class = "text">Use our resume maker with its advanced creation tools to tell
professional story that engages recruiters, hiring managers and even CEOs.</p>
</div>
</div>
<p class = "text">Resume writing has never been this effortless. Pre-generated
text, visual designs and more - all already integrated into the resume maker. Just fill in your details.</p>
</div>
</div>
37
<p class = "text">Our resume builder and its pre-generated content are tested
by recruiters and IT experts. We help your CV become truly competitive in the hiring process.</p>
</div>
</div>
</div>
</div>
</div>
<div class="container">
</div>
</div>
</footer>
</body>
</html>
CSS CODE
:root{
--bgcolor: #f4f4f4;
--resume-left-bgc: #fff;
--resume-right-bgc: #232941;
--green: #0ea73a;
--white: #fff;
38
--primary: #232941;
*{
margin: 0;
padding: 0;
box-sizing: border-box;
list-style: none;
text-decoration: none;
body{
background-color: #FDF6EC;
font-size: 14px;
color: var(--primary);
.wrapper{
display: flex;
align-items: center;
justify-content: center;
padding: 20px;
.resume_design{
width: 700px;
max-width: 100%;
display: flex;
39
box-shadow: 0 0 2px rgba(0,0,0,0.2);
.resume_design .resume_left{
background: var(--resume-left-bgc);
width: 400px;
padding: 30px;
.resume_design .resume_right{
background: var(--resume-right-bgc);
color: var(--white);
width: 300px;
margin-bottom: 30px;
margin-bottom: 0;
margin-bottom: 10px;
text-transform: uppercase;
color: var(--green);
display: inline-block;
border-radius: 20px;
40
font-weight: 900;
letter-spacing: 2px;
font-size: 12px;
margin-bottom: 10px;
margin-bottom: 0;
padding-left: 20px;
padding-bottom: 20px;
position: relative;
padding-bottom: 0;
content: "";
position: absolute;
top: 0;
left: -5px;
41
width: 8px;
height: 8px;
background: var(--green);
border-radius: 50%;
font-weight: 900;
font-size: 16px;
margin: 3px 0;
font-weight: 300;
position: relative;
position: absolute;
top: 0;
right: 0;
font-size: 10px;
color: var(--green);
font-weight: 900;
42
.resume_design .resume_right .profile_sec,
padding: 30px;
width: 180px;
height: 160px;
margin-top: 20px;
font-size: 26px;
text-transform: uppercase;
font-weight: 300;
font-weight: 900;
margin-top: 10px;
text-transform: uppercase;
font-size: 12px;
letter-spacing: 2px;
43
}
position: relative;
background: var(--green);
text-transform: uppercase;
background: var(--white);
color: var(--primary);
display: inline-block;
border-radius: 20px;
font-weight: 900;
letter-spacing: 2px;
font-size: 12px;
position: absolute;
top: -13px;
left: 50%;
transform: translateX(-50%);
display: flex;
align-items: center;
44
margin-bottom: 10px;
margin-bottom: 0;
margin-right: 10px;
margin-bottom: 3px;
font-weight: 900;
display: flex;
align-items: center;
margin-bottom: 10px;
margin-bottom: 0;
width: 100px;
height: 10px;
45
border-radius: 20px;
position: relative;
overflow: hidden;
position: absolute;
top: 0;
left: 0;
height: 100%;
background: var(--white);
h5{
font-weight: bold;
font-size: 20px;
margin-left: 15px;
h6{
font-family:inherit;
#PrintResume{
display: none;
margin-bottom: 20px;
width: 250px;
46
JAVA SCRIPT CODE
<!DOCTYPE html>
<html lang="en">
<head>
<title>Resume Generator</title>
integrity="sha384-BmbxuPwQa2lc/FVzBcNJ7UAyJxM6wuqIj61tLrc4wSX0szH/Ev+nYRRuWlolflfl"
crossorigin="anonymous" />
integrity="sha512-
5A8nwdMOWrSz20fDsjczgUidUBR8liPYU+WymTZP1lmY9G6Oc7HlZv156XqnsgNUzTyMefFTcsFH/
tnJE/+xBg=="
</head>
<body>
47
<div class="container">
<div class="card-header">
</div>
<div class="card-body">
<div class="contain">
<div class="row">
<div class="col-md-6">
<h3>Personal Information</h3>
<div class="form-group">
</div>
</div>
</div>
48
<div class="form-group mt-2">
</div>
</div>
</div>
</div>
<label for="">Education</label>
49
<div class="container text-center mt-2" id="aqAddButton">
Add
</button>
</div>
</div>
<label for="">languages</label>
Add
</button>
</div>
</div>
</div>
</div>
<div class="col-md-6">
<h3>Professional Information</h3>
<label for="">Objective</label>
50
<textarea id="objectiveField" rows="5" placeholder="Enter here" class="form-control"></textarea>
</div>
<label for="">Title</label>
</div> -->
</div>
Add
</button>
</div>
</div>
51
<div class="container text-center mt-2" id="skAddButton">
Add
</button>
</div>
</div>
<label for="">CERTIFICATIONS</label>
Add
</button>
</div>
</div>-->
</div>
</div>
</div>
</div>
Generate cv
</button>
</div>
52
</div>
</div>
aqOb.insertBefore(newNode, aqAddButtonOb);
function addNewEdField() {
newNode.classList.add("form-control");
newNode.classList.add("edField");
newNode.classList.add("mt-2");
newNode.setAttribute("rows", 3);
document.getElementById("cv-template").style.display = "block";
document.getElementById("btnN").style.display = "none";
window.print();
}</script>
<style>
53
OUTPUT
54
55
56
BIBLIOGRAPHY
1. Automobile Showroom Management: An Analytical Approach" by K.
Krishnamoorthy
2. Modern Automotive Showroom Management and Marketing" by Jeffrey F. Loeb
3. Effective Car Showroom Management: A Practical Guide" by Simon L. Dolan
4. Automotive Retailing: Today and Tomorrow" edited by Gianmaria Martini and Lino
Cinquini
5. Car Dealership Management: How to Buy and Run a Car Dealership" by Michael
Reynolds
6. The Ultimate Sales Machine: Turbocharge Your Business with Relentless Focus on 12
Key Strategies" by Chet Holmes
7. Marketing Management" by Philip Kotler and Kevin Lane Keller
8. Operations Management" by Nigel Slack, Alistair Brandon-Jones, and Robert
Johnston
9. Customer Relationship Management: Concepts and Technologies" by Francis Buttle
10. Inventory Management: Principles, Concepts and Techniques" by Adam Kolaski
57