Profile Builder5

PROFILE BUILDER
By
Jaydeep Patel
Jignesh rathod
COMPUTER SCIENCE AND ENGINEERING DEPARTMENT

Ahmedabad 382481
April 2010
1
PROFILE BUILDER
Major Project
Submitted in partial fulfillment of the requirements
For the 6 Semester
Master of Computer Application
By
Jaydeep Patel (07mca033)

Jignesh rathod
Guide
Rushabh Shah
COMPUTER SCIENCE AND ENGINEERING DEPARTMENT

Ahmedabad 382481
April 2010
2
CERTIFICATE
This is to certify that the Major Project entitled “Profile Builder”

submitted by JAYDEEP R PATEL towards the partial fulfillment of the
requirements for the Master of Computer Application of Nirma University
of Science and Technology, Ahmedabad is the record of work carried out
by them under my supervision and guidance. In my opinion, the
submitted work has reached a level required for being accepted for
examination. The results embodied in this major project, to the best of my
knowledge, haven’t been submitted to any other university or institution
for award of any degree or diploma.
Rushabh Shah Prof. D J Patel

Guide, Professor and Head,
MCA CSE Department,
Institute of Technology, Institute of
Technology,
Nirma University, Nirma University,
Ahmedabad Ahmedabad
3
ACKNOWLEDGEMENT
It gives us great pleasure in expressing thanks and profound gratitude to

our Faculty Guide, Rushabh Shah, Department of Computer Engineering,
Institute of Technology, Nirma University, and Ahmedabad for her
valuable guidance and continual encouragement throughout the Major
project. We are heartily thankful to her for her time to time suggestion
and the clarity of the concepts of the topic that helped us a lot during this
study.
We are also thankful to Prof D J Patel, Head, Department of CE, IT and

MCA Department, Institute of Technology, Nirma University, Ahmedabad
for his continual kind words of encouragement and motivation throughout
the Major Project. We are also thankful to Dr K Kotecha, Director, and
Institute of Technology for his kind support in all respect during our study.
We are also thankful to all faculty members of Department of MCA, Nirma

University, and Ahmedabad for their special attention and suggestions
towards the project work.
The blessings of God and our respective family members makes the way
for completion of major project. We are very much grateful to them.
The friends, who always bear and motivate us throughout this course, we
are thankful to them.
Jaydeep Patel (07MCA033)
4
ABSTRACT
5
ABSTRACT
What is Profile Builder?
The Recruitment Process System is aimed at developing a web-

based in which it can generate a profile of a student after entering all the
details by the student. This System is very much useful for the students,
for the placement coordinator and the placement officer of the collage in
which student need to add their information to create student their profile,
placement coordinator need to create account of student then also need to
search the student profile based on some criteria, and placement officer
who also need to create the account of the placement coordinator then
need to add new branch new course.
In this system the following are the main actors who use this
system:
1. Student
2. Placement coordinator
3. Admin
College administrator will give authorities to placement coordinators

to View and generate report of specific area of students. Placement
coordinators
can sorting profile based on criteria like technical skill , type of projects ,
aggregate percentage , etc. She/he can also generate PDF/word
document of profile.
Student can enter his/her personnel details, educational details,

carrier oriented details (like projects, seminars, industrial visits, co
6
curricular activities etc.)Based on that details resume(CV) of student will
automatically generated by system. Students will able to edit detail.
Also in this system the messages facility id provided where

placement coordinator can send a message to the student as well as
admin also can send message to the placement coordinator about the
update.
7
CONTENTS
Certificate
Acknowledgement
Abstract
Contents
List of figures
Chapter 1 Introduction Page number
1.1 Purpose 8
1.2 Scope 8
1.3 Product Perspective 8
1.4 Product Features 9
1.5 Operating Environment 9
1.6 Details of toolsets being used 9
Chapter 2 Analysis of the System
2.1 Feasibility Study 10

2.2 Functional requirements 12
2.3 Non-functional requirements 16
2.4 Performance requirements 16
2.5 External Interface Requirements 16
Chapter 3 Data dictionary 17
Chapter 4 Diagrams
3.1 Use Case Diagram 23

3.2 Data Flow Diagram 26
3.3 ER Diagram 30
Chapter 5 Snapshots
Chapter 6 Conclusion …
8
Chapter 7 References …
9
LIST OF FIGURES
Figure 1 Usecase Diagram page

number
1.1 Usecase Diagram for Administrator 23

1.2 Usecase Diagram for Coordinator 24
1.3 Usecase Diagram for Student 25
Figure 2 Data flow Diagram (DFD Diagram)
2.1 DFD level 0 26

2.2 DFD level 1 for Administrator 26
2.3 DFD level 1 for Coordinator 27
2.4 DFD level 1 for Student 27
Figure 3 Entity Relationship Diagram (ER Diagram) 30
10
INTRODUCTION
11
1. INTRODUCTION
1.1 Purpose
a. Purpose of this project is student can enter his/her

details which is need to system. Based on that details resume
(CV) of student will automatically generated by system .College
administrator will give authorities to placement coordinators to
view and generate report of specific area of student. Placement
coordinators can sort profile based on criteria like technical skill,
type of projects, aggregate percentage etc.
1.2 Scope
1.2.1 This system is very helpful to collages in which it needs get the
resume of student. So with use of this software they allow
student to enter details and can generate PDF/ word file of a
resume.
1.2.2 Also placement coordinator can create the account of the

student and search the student resume based on some criteria.
He also can send messages to the student about their update or
any information about the resume. Admin also can add new
branch new courses in the system as well as he can create the
account of the placement coordinator also.
1.3 Product Perspective
1.3.1 The Profile Builder System is a web based s system for the
colleges. It will provide functionality like student can add his all
the details in that according to that details students resume will
generate in PDF/word file. Also in this system the Administrator
12
can change the information of the Branch and courses, he can
add or delete new courses and branch in to the system, and also
can create the account of the placement coordinator. Also can
send the messages to the placement coordinator about any
update or any information also he can share with placement
coordinator through messages.
1.3.2 Placement coordinator also can create the account of student

and system also can generate the account of the student
automatically. Then placement coordinator also can search the
student profile based on some criteria like technical knowledge,
projects etc.
1.3.3 system also provide the facility in which after every end of
semester means after 6 months every students semester will be
changed automatically by the system.
13
1.4 Product Feature
1.4.1 There are three different types of users who use this product:
 Administrator:
He can view the all the students resume.
He also can create the account of the placement
coordinator and also can add new branches and
courses in to the system and also can send the
messages to the student as well as placement
coordinator.
 PLACEMENT CORDINATOR:
He can create the account of the

student .and can search the student profile
based on some criteria like student technical
skills, projects etc. he also can send a messages
to the student about their profile as well as any
update.
 STUDENT:
Student need to add all his information like

carrier objective , projects , seminar which he
delivered , co-curricular activities , reference
technical details , educational detail etc. based
on which his/her profile will be generated.
14
1.5 Operating environment
1.5.1 The system operates in Windows 95/98/XP/Vista environment.

Also it requires Google Chrome / Mozilla Firefox.
1.6 Details of toolsets being used
1.6.1 Following are the tools which are being used:
Platform
• Java
Database
• MySQL
Framework
• JQuery
Server
• Apache Tomcat 6.018
Technologies
• Internet (HTML, Java Script, JSP,
Servlets)
Tools
• Eclipse
• SQL(yog)
15
ANALYSIS OF THE SYSTEM
16
2. ANALYSIS OF THE SYSTEM
2.1 Feasibility study
An estimate is made of whether the identified user

needs may be satisfied using current software and hardware
technologies. The study considers whether the proposed
system will be cost-effective from a business point of view
and whether it can be developed within existing budgetary
constraints.
The result of this study should inform the decision

of whether to go ahead with a more detailed analysis. There
are 3 main factors, which determine the feasibility of the
project. They are as follow:
1. Technical Feasibility
2. Economica l Feasibility
3. Operational Feasibility
17
2.1.1 Technical Feasibility
The technical feasibility takes in to consideration the

technical requirement and their availability in the market. It
determines whether it is possible to develop the proposed
system with the present technology or not. The technical
possibilities of present system are as follows:
• The hardware is currently being used by the company.

• Proposed system doesn’ t require any technical details.
• The current setup is not so much sufficient for the
processing of all kind of task s.
• It needs low configuration computer system.
• The technical specification is easy available in the
market.
2.1.2 Economical Feasibility
The economical feasibility takes in to consideration of

the financial matter regarding the proposed system. The
organization measures the cost effectiveness of the proposed
system. The economical feasibility of the proposed system is as
follow:
• The organization is ready to invest in the proposed

system for latest technology and better result.
• If any of the staff of the firm know how to operate the
computer, them the firm doesn’ t need to recruit the
new person.
• The firm has to spend about nearly RS.4000 (say for
example) for the computer hardware and software.
18
• The organization is capable for the paying of the money
for the proposed system.
2.1.3 Operational Feasibility
The operational feasibility deals with the matter whether

the proposed system fulfills the requirement of the firm. This
feasibility determines whether the proposed system covers all
the aspect of the current system. The possibility of the
operational feasibility is as follow:
• The proposed system will fulfill the firm’s requirement.

• The proposed system covers all the aspect of the
working system.
• The expected users of the proposed system are
honestly eager for the new sy stem.
• The changes made in this system are quite beneficiary.
19
2.2 Functional requirements
Functional Requirements for the Recruitment Process System are

as follow:
1. Generic:
a. Login to the system through the first page of the application

b. Change the password after login to the application.
c. See his/her details and change it.
d. Help from the system.
2. Admin group:
a. Should be able to create a new Course with all details like

start year, number of seats, education system.
b. Should be able to create a new Branch like branch name.
c. Should be able to create a new Coordinator to every Branch
for each semester with details like name, contact number,
address etc.
d. Should be able to search already added Course/Branch or
Coordinator.
e. Send message to Coordinators or any students.
f. Should be able to view all the details of coordinators.
g. Should be able to remove the Coordinator from any branch.
3. Coordinator:
a. Should be able create new account for all student of that

branch.
b. Should be able to search on Student according to require
criteria like percentage, technical skills or roll number.
20
c. Coordinator has access to view all students account (his/her
branch only).
d. Coordinator can send message to admin as well as all
students.
4. Student:
a. He/she will be given initial username and password by

placement coordinators at college.
b. On first time login he/she will be asked to change the

password.(it must not same as initial or not like his/her roll
no., name etc.)
c. Student will able to enter details like (personnel, educational,

carrier oriented).
d. Student will able to edit those details.
e. Student can view his/her profile.
f. Should be able to generate PDF/word document of profile.
5. Other Details:
a. The student should have the following details:

i. System should generate a project number
sequentially.
ii. If student has more than one seminar number should
be in sequence and generated by system.
iii. If student already add project, seminar, industrial visit,
etc. details system should display next time
when student try to edit that particular details.
iv. Duplication of information of education is not allowed.
v. Empty field or not allow in filling up the information of
student resume.
vi. Valid details if enter as validation is on every field of
student page.
21
b. Coordinator details should have the following:
i. Admin crate coordinator account.

ii. System should not aloe coordinator to see other
branch student’s details.
iii. At a time of crating student account system should get
all the students details that are under that
particular coordinator.
iv. Coordinator has option to create account by auto or
manual.
v. In auto system takes base string for pass word and
user name. System should create all students
account automatic.
vi. If student account is already created and coordinator
tries to create more than one account for same
student system should over write the current
account.
vii. Coordinator can search all students according to
percentage, technical skills and roll number.
System search student according to search
criteria.
viii. System gets update from student into their account.
c. Coordinator search should have the following:
i. System should display all search criteria.

ii. This should display criteria of search according to
selected field.
iii. Display the details of all shortlisted students.
iv. Student full details should be vied by coordinator.
d. As soon as semester change according to start month all the

details of semester should be uploaded.
22
e. Coordinator should not allow seeing details of other branch
student profile.
f. Once branch or course is deleted system has backup of that
branch and course.
g. Valid entry should be allowed to enter at time of creating
new course.
2.3 Non - functional requirements
2.3.1 Security
i. Confidentiality
23
ii. Integrity: Extent to which data
and procedures are protected from
unauthorized changes.
2.3.2 Reliability
i. Non-deficiency: Degree to which

software doesn’t contain
undetected defects.
ii. Fault-tolerance: Degree to which
software works without system
failure.
2.3.3 Maintainability
i. Corrective: Finding and fixing faults.

ii. Adaptive: Modify software for a
change in requirement. New
functionality is added.
2.4 Performance requirements
24
• The system should allow multiple users to access their
accounts simultaneously.
• The failure rate of the application should be minimum
• The response time may be less than 2to5 seconds.
2.5 External Interface Requirements
2.5.1) Hardware Interfaces:
• Operating System : Windows 95/98/XP
• Processor : Core2Duo 2.93 GHz or higher
• RAM : 512 MB or more
• Hard Drive : 1 GB or more
2.5.2) Software Interfaces
 Database : MySQL
 Server : Apache Tomcat 6.018
 Tools : Eclipse, SQL(yog)
 Framework : JQuery
25
3. DATA DICTIONARY
3.1 Name of the tables
 account information coordinator

 account information student
 branch
 Co curricular Activity
 curricular
 courses
 declaration
 Class 10 details
 Class 12 details
 Extra Curricular Activity
 hobbies
 industrial visits
 language known
 messages
 Profile details
 projects
 references
 registration
 seminars
 skill information
 skill type
 technical skill
 user information
Fields, Indexes, Key Relationships of the tables
26
1) account_information_coordinator
Fields
Field Type Collation Null Key Default
id int(10) (NULL) NO PRI (NULL)
course_id int(10) (NULL) YES MUL (NULL)
branch_id int(10) (NULL) YES MUL (NULL)
year_or_sem int(4) (NULL) YES (NULL)
batch int(4) (NULL) YES (NULL)
disable text latin1_swedish_ci YES (NULL)
Indexes
Table Non Key Column
unique name name
account_info_coordinator 0 PRIMARY id
account_info_coordinator 1 FK_account_info id
account_info_coordinator 1 FK_account_info_branch branch_id
account_info_coordinator 1 FK_account_info_course course_id
Foreign Key Relationships
FK Id Reference Table Source Column Target Column
FK_account_info registration ìd` ìd`
FK_account_info_branch branch `branch_id` ìd`
FK_account_info_course courses `course_id` ìd`
2) account_information_student
Fields
roll_no text latin1_swedish_ci YES (NULL)
disable text latin1_swedish_ci YES (NULL)
coordinator_id int(10) (NULL) YES MUL (NULL)
Indexes
Table Non Key Column Index
27
unique name name type
account_info_student 0 PRIMARY id BTREE
account_info_student 1 FK_account_info_student id BTREE
account_info_student 1 FK_account_info_student2 coordinator_id BTREE
FK Id Reference Table Source Column Target
Column
FK_account_info_student registration ìd` ìd`
FK_account_info_student2 account_info_coordinator `coordinator_id` ìd`
3) branch
Fields
Id int(10) (NULL) NO PRI (NULL)
parent_course int(10) (NULL) YES MUL (NULL)
Name text latin1_swedish_ci YES (NULL)
number_of_seats int(3) (NULL) YES (NULL)
Indexes
unique name name
branch 0 PRIMARY id
branch 1 FK_branch parent_course
FK_branch Courses `parent_course` ìd`
4) carrier_objective
Fields
28
objective Text latin1_swedish_ci YES (NULL)
Indexes
unique name name
carrier_objective 0 PRIMARY id
5) Co Curricular Activity
Fields
id int(11) (NULL) NO MUL 0
description varchar(250) latin1_swedish_ci YES (NULL)
Indexes
unique name name
cca 1 FK_cca id
6) Curricular Activities
Fields
objective text latin1_swedish_ci YES (NULL)
Indexes
unique name name
co 0 PRIMARY id
FK Id Reference Source Target
Table Column Column
FK_co registration ìd` ìd`
29
7) Co Curricular
Fields
id int(11) (NULL) NO (NULL)
title text latin1_swedish_ci YES (NULL)
description text latin1_swedish_ci YES (NULL)
8) courses
Fields
name text latin1_swedish_ci YES (NULL)
branches text latin1_swedish_ci YES (NULL)
course_start_year int(4) (NULL) YES (NULL)
education_system text latin1_swedish_ci YES (NULL)
start_month int(2) (NULL) YES (NULL)
number_of_seats int(3) (NULL) YES (NULL)
number_year_course int(1) (NULL) YES (NULL)
delete_flag tinyint(1) (NULL) NO (NULL)
Indexes
unique name name
courses 0 PRIMARY id
9) css
Fields
30
per1 int(3) (NULL) NO (NULL)
Indexes
unique name name
css 0 PRIMARY id
css_ibfk_1 registration ìd` ìd`
10) Class 10 details
Fields
id int(11) (NULL) YES (NULL)
board varchar(40) latin1_swedish_ci YES (NULL)
percentage tinyint(2) (NULL) YES (NULL)
11) Class 12 details
Fields
id int(11) (NULL) YES MUL (NULL)
board varchar(30) latin1_swedish_ci YES (NULL)
percentage varchar(4) latin1_swedish_ci YES (NULL)
field varchar(4) latin1_swedish_ci YES (NULL)
stream varchar(3) latin1_swedish_ci YES (NULL)
Indexes
31
unique name name
data12 1 FK_12inf id
12) declaration
Fields
declaration text latin1_swedish_ci YES (NULL)
Indexes
unique name name
declaration 1 FK_declaration id
Table Column Column
FK_declaration registration ìd` ìd`
13) Extra Curricular Activities
Fields
id int(11) (NULL) NO MUL (NULL)
Indexes
unique name name
eca 1 FK_eca id
14) hobbies
Fields
32
Indexes
unique name name
hobbies 1 FK_hobbies id
Table Column Column
FK_hobbies registration ìd` ìd`
15) industrial_visits
Fields
name varchar(50) latin1_swedish_ci YES (NULL)
Indexes
unique name name
industrial_visits 1 FK_inds id
16) language known
Fields
id int(11) (NULL) NO (NULL)
language_name varchar(15) latin1_swedish_ci YES (NULL)
33
17) messages
Fields
student_id int(11) (NULL) YES MUL (NULL)
body text latin1_swedish_ci YES (NULL)
Indexes
unique name name
messages 1 FK_message student_id
Table Column Column
FK_message registration `student_id` ìd`
18) Profile details
Fields
fname text latin1_swedish_ci YES (NULL)
lname text latin1_swedish_ci YES (NULL)
address text latin1_swedish_ci YES (NULL)
contact_no int(12) (NULL) YES (NULL)
dob text latin1_swedish_ci YES (NULL)
email text latin1_swedish_ci YES (NULL)
gender tinytext latin1_swedish_ci YES (NULL)
mname text latin1_swedish_ci YES (NULL)
Indexes
unique name name
pdetails 0 PRIMARY id
34
FK_pdetails registration ìd` ìd`
19) projects
Fields
id int(11) (NULL) NO MUL 0
Indexes
unique name name
projects 1 FK_projects id
20) referencesss

details text latin1_swedish_ci YES (NULL)
Indexes
unique name name
referencesss 1 FK_references id
Table Column Column
FK_references registration ìd` ìd`
35
21) registration
Fields
username text latin1_swedish_ci YES (NULL)
password text latin1_swedish_ci YES (NULL)
security_question text latin1_swedish_ci YES (NULL)
ans text latin1_swedish_ci YES (NULL)
type text latin1_swedish_ci YES (NULL)
Indexes
unique name name
registration 0 PRIMARY id
22) seminars
Fields
Indexes
unique name name
seminars 1 FK_seminar id
36
23) skill_information
Fields
skill_type int(10) (NULL) YES MUL (NULL)
skill_name text latin1_swedish_ci YES (NULL)
Indexes
unique name name
skill_info 0 PRIMARY id
skill_info 1 FK_technical_skill skill_type
FK_technical_skill skill_type `skill_type` ìd`
24) skill_type
Fields
skill_type text latin1_swedish_ci YES (NULL)
Indexes
unique name name
skill_type 0 PRIMARY id
25) technical_skill
Fields
37
student_id int(10) (NULL) YES MUL (NULL)
skill_id int(10) (NULL) YES MUL (NULL)
Indexes
unique name name
technical_skill 1 FK_technical_skill2 student_id
technical_skill 1 FK_technical_skill3 skill_id
FK_technical_skill2 account_info_student `student_id` ìd`
FK_technical_skill3 skill_info `skill_id` ìd`
26) User information
Fields
address text latin1_swedish_ci YES (NULL)
contact_no text latin1_swedish_ci YES (NULL)
email_id text latin1_swedish_ci YES (NULL)
Indexes
unique name name
userinfo 1 FK_userinfo id
FK_userinfo registration ìd` ìd`
27) co_curricular_activity
38
Fields
discreption text latin1_swedish_ci YES (NULL)
4. Diagrams
4.1 Usecase Diagram
4.1.1 Usecase Diagram for Administrator
View
account
Coordinator
Discriptio
n
Create
Departmen
t
New
branch
Course
details
Student
/coordinato
39 r profile
Admin
View
Message
4.1.2 Usecase Diagram for Coordinator
View
Student
profile
Account
information
Edit/delete
Coordinator account
Send/ resive
Message
Search
student by
criteria
40
4.1.3 Usecase Diagram for Student
Log In
View/send
message
Update
student
profile
Student
Log Out
41
4.2 Data flow Diagram
4.2.1 DFD level 0
Admin
Branch details Create Course details Create/edit View/send

management coordinator Management branch Messages
Profile builder System
Level - 0
42
Create/edit View/send
View student Search View/send Edit student
student messages Login
account student message information
account details
Coordinator Student
4.2.2 DFD level 1 for Administrator
43
4.2.3 DFD level 1 for COORDINATOR
44
4.2.4 DFD level 1 for Student
45
4.3 Entity Relationship Diagram
46
47
5.
Snapshots
Admin view coordinator:
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
6. Conclusion
Throughout the process, it has been a great learning

experience. It has been a privilege of learning and going through
the entire software development lifecycle right from requirement
gathering phase.
This project widened our horizons of knowledge to a very

large extent. This project will always remain an integral part of my
resume and hopefully also of WWW.
Any work may be always not perfect there may be an

error or some defect in the work. We have taken enough care
to make the project user friendly and interactive. We hope that
our software “Profile Builder ” should be useful to user.
Even though we never claim that this system may fulfill

all the requirements of the users in every condition. This
application has been developed with a view to provide
maximum facility.
Lastly once more we are heartily thankful to all our

faculties who have helped us directly or indirectly to complete
this project in time. And we are also very thankful to our
project coordinator who helped us a lot in this project. We are
extremely grateful to “Rushabh Shah” for encouraging us to
experience the world of real life software development.
74
7.
References
1) The Complete Reference Java 2, 5th edition by “ Herbert Schildt ”
2) Java for the Web with Servlets, JSP, and EJB by “ Budi Kurniawan ”
3) Core Servlets and Java Server Pages by “ Marty Hall ”
4) information about the O'Reilly Java Servlet Programming book by

Jason Hunter and William Crawford
5) Learning JQuery 1.3 EBook by Jonathan Chaffer, Karl Swedberg
6) jQuery.in.Action.Feb.2008.Manning by BEAR BIBEAULT, YEHUDA KATZ
7) www.jquery.com
8) www.w3school.com
75

Profile Builder5

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Profile Builder5

Uploaded by

Copyright:

Available Formats

PROFILE BUILDER

COMPUTER SCIENCE AND ENGINEERING DEPARTMENT

Submitted in partial fulfillment of the requirements

For the 6 Semester

Master of Computer Application

Jaydeep Patel (07mca033)

COMPUTER SCIENCE AND ENGINEERING DEPARTMENT

This is to certify that the Major Project entitled “Profile Builder”

Rushabh Shah Prof. D J Patel

It gives us great pleasure in expressing thanks and profound gratitude to

We are also thankful to Prof D J Patel, Head, Department of CE, IT and

We are also thankful to all faculty members of Department of MCA, Nirma

Jaydeep Patel (07MCA033)

What is Profile Builder?

The Recruitment Process System is aimed at developing a web-

College administrator will give authorities to placement coordinators

Student can enter his/her personnel details, educational details,

Also in this system the messages facility id provided where

Chapter 2 Analysis of the System

2.1 Feasibility Study 10

Chapter 3 Data dictionary 17

3.1 Use Case Diagram 23

Figure 1 Usecase Diagram page

1.1 Usecase Diagram for Administrator 23

Figure 2 Data flow Diagram (DFD Diagram)

2.1 DFD level 0 26

Figure 3 Entity Relationship Diagram (ER Diagram) 30

a. Purpose of this project is student can enter his/her

1.2.2 Also placement coordinator can create the account of the

1.3 Product Perspective

1.3.2 Placement coordinator also can create the account of student

He can create the account of the

Student need to add all his information like

1.5.1 The system operates in Windows 95/98/XP/Vista environment.

1.6 Details of toolsets being used

1.6.1 Following are the tools which are being used:

2.1 Feasibility study

An estimate is made of whether the identified user

The result of this study should inform the decision

The technical feasibility takes in to consideration the

• The hardware is currently being used by the company.

2.1.2 Economical Feasibility

The economical feasibility takes in to consideration of

• The organization is ready to invest in the proposed

2.1.3 Operational Feasibility

The operational feasibility deals with the matter whether

• The proposed system will fulfill the firm’s requirement.

Functional Requirements for the Recruitment Process System are

a. Login to the system through the first page of the application

a. Should be able to create a new Course with all details like

a. Should be able create new account for all student of that

a. He/she will be given initial username and password by

b. On first time login he/she will be asked to change the

c. Student will able to enter details like (personnel, educational,

d. Student will able to edit those details.

e. Student can view his/her profile.

f. Should be able to generate PDF/word document of profile.

a. The student should have the following details:

i. Admin crate coordinator account.

c. Coordinator search should have the following:

i. System should display all search criteria.

d. As soon as semester change according to start month all the

2.3 Non - functional requirements