RESUME BUILDER

APPLICATION
 OBJECTIVE

• Develop an Intranet Application for automating

the process of Resume Writing

•This would be facilitating the employees to make

and print their resumes in a proper format.

•It will be facilitating the higher management to

search the employees depending upon their skills
sets and other attributes.
 FEATURES AND SERVICES
LOGIN

ADMINISTRATOR EMPLOYEE

View Resume And Print Enter information into

Resume Of Employee In
PDF Format.
Search for a particular
employees according to
search criteria.
their Resume / Edit
Resume.
Print their resume as a
PDF Document.
 COMONENTS OF RESUME
THE
RESUME
Biographical Data References

Objective Awards /
Certificates

Employment History
Skill Area

Education History
 FEASIBILITY STUDY

•The feasibility study is carried out to test whether the proposed

System is worth implemented.

• Feasibility study is the test of proposed system regarding its

work ability.

The key consideration involved in the feasibility study is:

•Technical

•Economic

•Behavioral

•Operational
•Technical Feasibility
Technical Feasibility center on the existing computer system and to
what extent it can support the proposed system addition.

• Behavioral Feasibility
People are inherently resistant to change and computers have been
known to facilitate change. An estimate should be made of how
strong a reaction the user staff is likely to have towards the
development of computerized system.
•Economical feasibility

This software is technically feasible therefore it is very cost

effective and can be run on any computer. Hence, economical
feasible.
There is no need to purchase extra software & hardware. Any
person or organization which is using any traditional
development environment can use this user friendly
development environment instead of that at no extra cost.

•Operational feasibility
This project meets the operating requirement of
the professional programmer. This test asks if the
system will work when it is installed. There are
sufficient supports for the project from user. User
may welcome, may change that will bring about a
more operational and useful system.
 SCOPE OF APPLICATION

SOFTWARE SCOPE

•Reusability

Reusability is possible as and when require in this application. We

can update it next version. Reusable software reduces design,
coding and testing cost by amortizing effort over several designs.

Reducing the amount of code also simplifies understanding, which

increases the likelihood that the code is correct.
We follow up both types of reusability:
Sharing of newly written code within a project, and
reuse of previously written code on new projects.
•Understandability
A method is understandable if someone other than the creator of the
method can understand the code (as well as the creator after a time
lapse). We use the method, which small and coherent helps to
accomplish this.

•Cost-effectiveness
Its cost is under the budget and make within given time period. It is
desirable to aim for a system with a minimum cost subject to the
condition that it must satisfy the entire requirement. Scope of this
document is to put down the requirements, clearly identifying the
information needed by the user, the source of the information and
outputs expected from the system.

 
 REQUIREMENTS
1. Hardware requirements

Number Description Alternatives (If available)

1 PC with 2 GB hard-disk and Not-Applicable

256 MB RAM

2. Software Requirements
Number Description Alternatives (If available)
1 PHP
2 SQl Server 2000 Oracle 8
3 Windows 2000 Alternatively, Windows 98 with
IIS Server Installed.
 3. FUNCTIONAL REQUIREMENTS
Requirement Essential / Description of Remarks
Desirable the
Requirement
The system should have a Essential A login box The logins are
login should appear assigned by the
when the system mail-admin
is invoked.
The system should have Essential Help about the Some tips on
help screens various features ofwriting a neat
the system should resume can be
be provided in given in the
sufficient detail in help section.
a Q&A format.
Requirement Essential / Description of Remarks
Desirable the
Requirement
The system should ‘lock’ Desirable This feature will Since the
the login id if wrong improve the application is
password is entered 3 robustness of the going to be
times in a row used only by
application
the employees
of the
organization,
this feature is
not essential.
However, if
time is there,
this will be
implemented
Requirement Essential / Description of Remarks
Desirable the
Requirement
The System Should Essential This feature is
enable the user to Logout. necessary for the
Security purpose.

The System should show Desirable Making the There should be

proper error messages in Application no unhandled
case of an error Robust and more exception. The
User friendly. application
should never
hang due to an
unhandled
error.
4. User Characteristics
Every user should be comfortable of working with computer and
net browsing. He must have basic knowledge of English too.

5. Constraints
•GUI is only in English.
•Login and password is used for identification of customer and there
is no facility for guest.
•This system is working for single server.
•We will use server space for our project, hence we can
access through single machine or a number of simultaneous user.
• Another importance is, in case of system crash we will not be
needed backup as we can get it from server.
 DATABASE TABLES
1. LOGIN TABLE :
Field Name Data type Valid values forRemarks
the field

Username Text Should be 20 All users will have

characters long and their username and
cannot contain administrator will
special characters have login ADMIN

Password Text Must be atleast 6 All users will get

characters and password by the
should not exceed admin which they
by 15 characters can change and
update later.
2. DATABASE 2 :
Field Name Valid values for the Remarks
field
Employee Number It will be numerical starting This is the key field of the
with EMP database as it is unique for an
employee in the organization.
This may also serve as the
login for the system.

Name Up to 15 characters in length. Special characters like

Will Have First Name , last underscore are not allowed.
name and middle name

Role Pre-defined set (like The reporting hierarchy is

engineers/managers/etc)
based on the role of the
person. For example, an
engineer reports to a manager,
a manager reports to a
business manager etc
Field Name Valid values for the Remarks
field
Email Id Up to 25 characters in This field should also be
length (including the unique for a person
domain name) because no two employees
in an organization can have
the same email id.

Age Will be numeric

Phone Number Should contain STD code Will contain al phone
And should not be more number that is residence,
than 10 digits in case of office, mobile number
mobile
Address Should be valid address The address should contain
and must contain all details city , state , pin code etc.

Objective Should not be more than This field contains the

200 characters. objective of your resume
Field Name Valid values for the Remarks
field
Summary Should not be more than This field contains the
500 characters summary of the resume.
Educational History Should contain percentage This field contains all the
and passing year educational information of
10,10+2, graduation and if
post graduation with
percentage and passing
year.
Employment History Should have date of service It contains all the detail
not more than the current about the previous
or joining date employer of the employee
Awards Should be verified This field contains the
descriptions of awards the
employee has got
Field Name Valid values for the Remarks
field
Certifications These can be international It contains all the
or company description about the
certifications the employee
has got
Skills Will be multiple valued It has all the description
about the skills which a
employee has and can be
useful for the company
Publications Should contain the It contains the papers or
publication date and articles if any published by
magazine name the employee
References Should have field whether It contains information
the reference if employee about the employee’s
here or outsider referencee
USE CASE DIAGRAM
 USE CASE TABLE
Use Case Login # Help

Actors System Administrator and Employee

Description System administrator and employee will need

to enter user name and password before they
can access the system for security reasons

Pre-condition Login screen is active prompting user to enter

user name and password or goto to the help
screen.
Flow Enter username Enter password
Of Password confirmation
If password correct go to user logged in
Events
If password is wrong go to error message
OR
Press F1 or click “HELP” button for help
 DATA FLOW DIAGRAMS

Resum
User e Administrator
Builder

Level-0 DFD
LEVEL 1
LEVEL - 2 MAIN WINDOW
LEVEL - 2 SEARCH
LEVEL - 2 LOGIN / HELP
LEVEL - 2 PRINT
LEVEL - 2 HELP
E-R DIAGRAM
SNAPSHOTS

LOGIN WINDOW
MAIN WINDOW
HELP WINDOW
CONTACT INFORMATION WINDOW
ADRESS WINDOW
OBJECTIVE WINDOW
EDUCATIONAL HISTORY WINDOW
EMPLOYMENT WINDOW
AWARDS WINDOW
SKILLS WINDOW
LICENSE AND CERTIFICATE WINDOW
REFERENCE WINDOW
PUBLICATIONS WINDOW