A Project Presentation Placement Cell Submitted By...
Transcript of A Project Presentation Placement Cell Submitted By...
A Project Presentation
On
Placement Cell
Submitted By
Patel Monika B (13084231152)
Salvi pinky R (13084231250)
Department of computer science
Ganpat University,Ganpat Vidyanagar – 384012
M.Sc.(CA&IT)Semester-III
Submitted To
Internal Guide:Mr.Narenadr Patel
Group No:82
PROJECT PROFILE
Project Name:- Placement Cell
Objective:- This website is specialy developed for the student
who has completed their study, and want to get
good job for their career.
Platform:- Web Base Application
Front end:- ASP.NET with C# (.net Framework 4.0)
Back end:- SQL Server 2008
Supporting Tool:- Microsoft Office 2007, Visual Studio 2010
Project Internal guide:- MR. Narendra Patel
Developed by:- Patel Monika B
Salvi pinky R
Time Duration:- 90 Days
REQUIREMENT SPECIFICATION
This website is specialy developed for the student who has completed their study, and want
to get good job for their career
EXISTING SYSTEM:-
• The existing system provide less facility and time consuming process for placement the job.
• Student have to go the collage and fill the manual registration form..
• They maintain several registers for recording the entry of daily transactions such as job
detail, job apply, etc.
NEED FOR NEW SYSTEM
We developed this website mainly for the student who completed their study and
want to get good job according their qualification and experience.
• The latest job of private user can see and if user want to get the job according to
their qualification then he/she can apply for the job using apply form.
• The student can fill online registration form and apply online form the job.
[A].ADMIN
Admin can upload and add the new job detail with full description.
Admin can add the content detail of the company.
Admin can show student detail who are already registered.
Admin can edit and delete the job information.
Admin can see the student detail and if admin want to delete the detail he can delete.
[B].REGISTERED USER
Registered user can see the latest available jobs and see full description of the jobs.
Registered user can fill the apply form for the applying the job.
Registered user can upload his/hers photos and document.
Registered user can give his/ her feedback.
Registered user can edit or delete the his/her profile information.
FUNCTIONAL SPECIFICATION
USER SPECIFICATION
1.REGISTRATION
[A]. ADMIN
Admin doesn’t require registration.
He is in inbuilt user.
[B].REGISTERED STUDENT
Without registration user can also see the job but not apply for the job.
So, user have to register and login in to the system.
2.JOB MODULE
[A]. ADMIN
Admin can add the job and also edit or delete the job.
[B].REGISTERED STUDENT
Registered user can see the available jobs and to apply for the job..
MODULE SPECIFICATION
3.USER MANAGEMENT
[A]. ADMIN
Admin can view and delete unauthorize users.
4.PROFILE MANAGEMENT
[A].REGISTERED STUDENT
Registered user can edit his/her profile.
5.FEEDBACK MANAGEMENT
[A].REGISTERED STUDENT
Registered user can give his/ her feedback.
[B]. ADMIN
Admin can view and delete feedback.
6.LOGIN
Admin and user can login with correct username
and password.
MINIMUM HARDWARE REQUIREMENT
Server Side
Client Side
HARDWARE & SOFTWARE REQUIREMENT
Processor:- 1.0 GHz
Hard Disk:- 10 GB free space
RAM:- 2 GB
Processor:- 633 MHz
Hard Disk:- 5 GB free space
RAM:- 1 GB
MINIMUM SOFTWARE REQUIREMENT
Server Side
Client Side
Operating System:- Windows Server 2003
Web Server:- IIS 6.0
Front-End Tools:- Asp.net 4.0 framework with c#
Back-End Tools:- SQL Server 2008
Other Tools:- Microsoft Office 2007,
Operating System:- Window Xp or Any compatibal
OS.
Web Browser:- Internet Explorer 6.0 all the
Compatible
Visit Site
Is
Registed
Need
Registration
No
Registration Login
Yes
View Job
Admin
Yes
A B
User
C
No
Start
Post New Job
Log out
Company
Select Job
Apply For Job
A B
STOP
Manage Job
Search Job
Manage User Application Status
Manage Application Profile
Manage Interview
C
Timeline Chart
A
C
T
I
V
I
T
I
E
S
Development
Phase
Days Durati
on
Day 3 Month(90 Days)
0-15 15-30 30-45 45-60 60-75 75-90
Requirement
Gathering
10
Analysis 15
Designing 20
Coding 25
Testing 10
Implementation 10
Documentation 80
Total 90 Days
Admin_
Id
Admin Manage
Name
Company
C_id
manage
User
U-id
Name E-mail
Mob no
Manage Jobs
J-id Job type Job
name
Has
upload
1 M
M
M
1 M
M
1
has Application
A-Id U-Id J_Id
Manage
apply
M
M
1
M
M
1
User
Admin
Post New Job
Manage Job
Manage User
Manage Application
Manage Interview
Search job
Company
Select job
Apply For Job
Profile
View Site
Company
Logout
Login
Post new Job Manage Job Manage User Manage
Application
Manage
Interview
No [Vaild?]
Yes
10.2.1 Activity Diagram for Admin
View Site
Search Job
Logout
Login
Select Job Apply For Job Interview Call Application
Status
[Vaild?]
Yes
10.2.2 Activity Diagram for User
No
Experience Profile
Admin
- Username
- password
+ Login()
+ Registration()
Company
- C_id
- Co_name
+ add()
+ view()
Registration
- Reg_id
- Email_id
- password
+ add()
+ cancel()
Tbl_Jobs
-Jobs_id
- Job name
- Post
+ Post add()
+ Delete()
- city_id
- city_name
+ add()
+ view()
+delete()
City
1
*
M
1
1
1
- User_id
-User_name
Tbl_user
+apply()
+get_job
- int_id
-job_name
-Stud_name
Tbl_interview
+take interview()
+give job()
*
*
*
*
* *
Admin System Database
1:Login 1.1: Authentication
1.1.1:Acknowledgement 1.1.1.1:Login or Wrong Password
2:Manage Caterair 2.1:Operation
2.1.1:Acknowledgement 2.1.1.1:Update Caterair
3:Manage User 3.1:Operation
3.1.1:Acknowledgement 31.1.1:Update User
4:Manage Jobs 4.1:Operation
4.1.1.1:Update jobs 4.1.1:Acknowledgement
7:Logout
7.1:Logout Successful
5:Manage JobsType 5.1:Operation
5.1.1.1:Update Ad Type 5.1.1:Acknowledgement
6:Manage aaply job 6.1:Operation
6.1.1.1:Update apply job 6.1.1:Acknowledgement
User System Database
1:Login 1.1: Authentication
1.1.1:Acknowledgement 1.1.1.1:Login or Wrong Password
2:Change Profile 2.1:Operation
2.1.1:Acknowledgement 2.1.1.1:View For Change Profile
3:Change Password 3.1:Operation
3.1.1:Acknowledgement 31.1.1:View For Change Password
4:view Jobs 4.1:Operation
4.1.1.1:View For jobs 4.1.1:Acknowledgement
7:Logout
7.1:Logout Successful
5:apply jobs 5.1:Operation
5.1.1.1:apply for jobs 5.1.1:Acknowledgement
System
Admin
Database
1.Login
2.Manage Caterair
3.Manage User
4.Manage jobs
5 Manage jobs Type
6 Manage applied User
7.Logout
1.1.1.1 Login or wrong password
2.1.1.1 Update Caterair
3.1.1.1 Update User
4.1.1.1 Update Jobs
5.1.1.1 Update Jobs Type
6.1.1.1 Update applied User
7.1.1.1 Logout Successfully
Operation/
Authentication
Acknowledgement
10.5.1 Collaboration Diagram for Admin
System
User
Database
1.Login
2.Change Profile
3.Change Password
4. View jobs
5.Apply for job
6.Logout
1.1.1.1 Login or wrong password
2.1.1.1 View For Change Profile
31.1.1:View For Change Password
4.1.1.1:View For job
5.1.1.1 view applied detail
6.1.1.1 Logout Successfully
Operation/
Authentication
Acknowledgement
10.5.2 Collaboration Diagram for User
33
Table name :- Tbl_Registration
Table Description :- To keep detail of Registration
Foreign Key :- User_Code
Sr. No. Field Name Data Type/Size
Constraint Discription
1 User _Code Numeric(4) Foreign Key store user code.
2 Title Char(4) Not Null It desire title.
3 First_Name Char(20) Not Null Store the first name.
4 Last_Name Char(20) Not Null Store the last name.
5 Address Char(100) Not Null Store the address.
6 City Char(20) Not Null Store the city.
7 State Char(20) Not Null Store the state.
8 Contact_No Numeric(10) Not Null Store the contact no.
Co ti ue…
34
9 Email _Id Char(60) Null First name of user.
10 Qualification Char(20) Not Null Add qualification.
11 Stream Char(20) Not Null Desire stream.
12 Passing _Year Numeric(4) Not Null Store the passing year.
13 Class Char(20) Not Null Desire class.
14 Birth _Date Date(10) Not Null Store the birthdate.
15 Age Numeric(2) Not Null Store the age.
16 Experience Numeric(2) Not Null Store the experience.
17 Designation Char(20) Not Null Add designation.
18 Date Date(10) Not Null Store date.
35
Table name :- Tbl_Compose_Message
Table Description :- To keep detail of Compose Message
Foreign key :- User_Code
Sr. No. Field Name Data Type/Size
Constraint Discripction
1 User_Code Numeric(4) Foreign Key Store the user code.
2 Date Date(10) Not Null Store the date.
3 Send_To Char(60) Not Null It will send the message.
4 Message Char(100) Not Null Store information of job
seeker’s essage.
5 Type Char(20) Not Null Type of the message.
36
Table Name :- Tbl_Job_Master_Details
Table Description :- To Keep detail of Company
Primary Key :- Job_Code
Sr.No Field Name Data Type/Size
Constrains Discription
1 Job_Code Numeric(4) Primary Key Store the job code.
2 Job_Title Char(4) Not Null Store the title.
3 Company_Name Char(20) Not Null Store the company name.
4 City Char(20) Not Null Store City of company.
5 Area Char(20) Not Null Store area of company.
6 Minimum_Salary Numeric(7) Not Null Store minimum salary.
7 Maximum
_Salary
Numeric(7) Not Null Store maximum salary.
8 Experience Numeric(2) Not Null Store experience.
9 Qualification Char(20) Not Null Add qualification.
37
Table Name :-Tbl_Job_Criteraea_Master_Details
Table Description :-To Keep detail of Client
Foreign Key :-User_Code
Sr.no Field Name Data Type/Size
Constrains Discription
1 User _Code Numeric(4) Foreign Key Store user code.
2 Location Char(20) Not Null Current location of
job seeker.
3 Desire _Job Char(20) Not Null Desire job.
4 Work _Experience Numeric(7) Not Null Store experience.
5 Minimum_ Accepted
_Salary
Numeric(7) Not Null Store minimum
salary.
6 Maximum_ Salary Numeric(7) Not Null Store maximum
salary.
7 Old _Designation Char(20) Not Null Add designation.
System testing is a criterion of software quality assurance and represents the ultimate review of specified designing
and coding.
System testing reveals the presence of errors in the Website developed.
Testing is the process of executing a program with the intent of finding an error.
A good test case is one that has a high probability for finding a yet undiscovered error.
A successful test is one that uncovers the hidden errors.
Unit Testing:-
In unit testing each & every program is tested individually using dummy records to see weather that program produce
satisfied output and validation also.
Program Testing:-
The staff of premises tests program. Testing is used to establish that the results obtained by execution of a
program with arbitrary inputs are in accord with formally defined output specification.
Code Testing:-
The code testing strategy examines the logic of the program. Code testing strategies indicate whether the code meets its
specification. It does not guarantee against software fairer.
Testing
Post Implementation Review
• After the system is implemented and conversion is completed, a review of system
is usually conducted by users and analyst this is called post implementation review.
• The most fundamental concern post implementation review is determining
whether the system has met its objective; that is analysts want to know if the
performance level of users has improved and if the system is producing the result
intended. If neither is happening, one may question
• Whether the system can be considered successful.
Future Enhancement
• Not a single website is ever considered as complete forever firstly because
there is always something new requirement also are growing day by day.
• We want to improve our home page, as it is the main thing which attracts
all users.
• We will also provide advertisement in future.
• We will also provide videos in future in our system.
Bibliography
Reference Books:
1. ASP.NET 3.5 Stephen Walther
2. ASP.NET 2.0(BLACK BOOK) Dreamtech
Reference Websites:
www.jobindia.com
www.monster.com