Fig.

layout of Resume Builder – entity–relationship model

2.3 STUDENT CLASS AND CHARACTERISTICS

Student of the system should be able to Create the Resumes on the go as per Company Criteria’s.
Students Can be use this software at free of cost. The system will support two types of Student
privileges, Students and HR of That department. Students will have access to Create and Update
their Resume Data, and the Company HR will have access to both Students and Resume
management functions. The Student should be able to do the following functions:

• Make a new Resume

• Update the Data
• View their Resume

The HR Department should have following management functionalities:

• STUDENT FUNCTIONS.
• Get all Students Data who have make their Resume on that software.
• Get all Information.
• View and Update their Data.
2.4 OPERATING ENVIRONMENT

SOFTWARE REQUIREMENTS
Operating System: Window 10
Front End: JAVA sdk1.5
Back End: DATABASE: MYSQL

HARDWARE REQUIREMENTS
Machine: Pentium 4
Speed: 233 MHz and above
Hard Disk : 1GB
RAM: 256MB

2.5 SOFTWARE INTERFACES

Software’s used Description
We have chosen Windows 10 operating system for its best
Operating system support.
To save the Students records we have chosen MySQL
Database database.
To implement the project, we have chosen JAVA language
JAVA for its more interactive support.

3. OTHER NONFUNCTIONAL REQUIREMENTS

3.1 PERFORMANCE REQUIREMENTS
The steps involved to perform the implementation of Resume Builder data base are as listed
below.
A) E-R DIAGRAM
E-R Diagram constitute a technique for representing the logical structure of a database in a
pictorial manner.
ENTITIES: Which specify distinct real-world items in an application.
PROPERTIES/ATTRIBUTES: Which specify properties of an entity and relationships.
RELATIONSHIPS: Which connect entities and represent meaningful dependencies between
them.
 Fig. ER diagram of Resume Builder database

B) NORMALIZATION:
The basic objective of normalization is to be reduce redundancy which means that information is
to be stored only once. Normalization is the process of breaking down a table into smaller tables.
So that each table deals with a single theme. There are three different kinds of modifications of
anomalies and formulated the first, second and third normal forms (3NF) is considered sufficient
for most practical purposes. It should be considered only after a thorough analysis and complete
understanding of its implications.

3.2 TECHNICAL FEASIBILITY

Technical feasibility takes of the all the issues concerned with the design and the development
part of the project. It concerns itself with the software, hardware and the platform related issues.
The following are the technical specifications for our project.
The project would not require a lot of space for storage of static as well as dynamic content.

3.3 SECURITY REQUIREMENTS

Security systems need database storage just like many other applications. However, the special
requirements of the security market mean that vendors must choose their database partner
carefully.
3.4 CONCLUSION

Computerization is making the world work faster, so we needed an application which could help
people making their resumes at a faster pace than the traditional resume or CV making process.
This application will save a lot of time and effort in making resume or CV. It would make it
possible to make these on-the-go.