The document outlines the development of a web-based Training and Placement Cell portal aimed at improving student placement processes by storing and managing student and company information. It addresses issues with the existing manual system, such as time consumption and paperwork, by introducing features like student and company logins, event management, and data integrity measures. The proposed system enhances user experience, reduces redundancy, and facilitates easier access to important placement-related information.

1. TRAINING AND PLACEMENT CELL PORTAL
SUBMITED BY
PANASA RAMAIAH

2. PROBLEM STATEMENT
The 'Training and Placement' is developed to maintain the details of student information, trace the
details of student also maintain the information about the company availability. Using this project
user may know all the details which are provided by the ‘Training and Placement’. Users can view
the availability of company and dates of passing. the tpo officers to control the upload events and
send notifications. all the customers have some common services like adjusting the password,
upgrading details, looking for details, checking the important points, mailing to the supervisor, and
studying the substance submitted by admin if the consumer is a student.

3. 1. The earlier program is not computerized
2. All transactions in the system are performed personally sustaining records.
3. in the earlier program positioning official has to gather student details for placements. Signing these scholar
details requires lots of time
4. Positioning official and pupils have to consult each other straight if any data is needed. If any new
organization come for placements, positioning official and his team has to search the scholar details and they
have to get the eligible prospects for that specific organization placement
EXISTING SYSTEM

4. DRAWBACKS IN THE EXISTING SYSTEM
1. IT CONSUMES MORE TIME.
2. PAPER WASTAGE.
3. REPEATED WORK IS OBTAINED IN THE SYSTEM
4. REDUCE STORAGE AREA

5. PROPOSED SYSTEM
1. Training and Placement Cell is fully advanced, which removes most of the disadvantages of the present
system
2. Training and Placement Cell is web based application which can be seen through the entire company and
external as effectively with proper login provided.
3. This technique may be used as a software for the TPO to control the student data with regards to
placement
4. All the customers have some common services like adjusting the password, upgrading details, looking for
details, checking the important points, mailing to the supervisor, and studying the substance submitted by
admin if the consumer is a student.
5. The supervisor has to accomplish the services like putting activities, achievements and he can reply to the
messages sent by users.
6. They can add components, search for scholar details, and he has the best to approve the students

6. ADVANTAGES
1. Reduce the paperwork and storage area
2. Improve accuracy in results
3. Improve output of operations
4. Allow easy navigation through cv’s and company information

7. FUNCTIONAL REQUIREMENTS
1 STUDENT LOGIN:
1. View Profile
2. Forget password
3. Update Profile
4. View Training Events
5. View Placement Events
2.TPO LOGIN:
1. Upload Training Events
2. Upload Placement Events
3. View Training Events
4. View Placement Events

8. 5. Send Notifications
6. Get Student Information
7. Change Password
3.STAFF LOGIN:
 get Student Information
 View Events
 Change Password

9. NON –FUNCTIONAL REQUIREMENTS
1. Usability
2. High Availability
3. Security
4. Performance
The web site must have a simple ,user-friendly interface so customers can save time and confusion

10. USE CASE DIAGRAM
The use case diagrams describe system functionality
as a set of tasks that the system must carry out and
actors who interact with the system to complete the
tasks.
.

11. SEQUENCE DIAGRAM
A sequence diagram describes an interaction among a set
of objects participated in a collaboration(or scenario),
arranged in a chronological order; it shows the objects
participating in the interaction by their "lifelines" and the
messages that they send to each other.
STUDENT LOGIN

12. STUDENT CHANGE PASSWORD

13. STUDENT CHANGE PASSWORD

14. STUDENT CHANGE PASSWORD

15. STUDENT PROFILE VIEW

16. TPO CHANGE PASSWORD

17. TPO LOGIN

18. VIEW TRAINING EVENTS

19. ENTER PLACEMENT EVENTS

20. ENTER TRAINING EVENTS

21. STAFF LOGIN

22. STAFF CHANGE PASSWORD

23. STAFF CHANGE PHONE NUMBER

24. STAFF CHANGE GMAIL

25. E-R DIAGRAM
An entity-relationship diagram (ERD) is a data modeling technique that graphically
illustrates an information system's entities and the relationships between those
entities. An ERD is a conceptual and representational model of data used to represent
the entity framework infrastructure.

27. CLASS DIAGRAM
A class diagram in the Unified Modeling
Language (UML) is a type of static
structure diagram that describes the
structure of a system by showing the
system's classes, their attributes,
operations (or methods),and the
relationships among objects.

28. MODULES:
1. TPO
2. Student
3. Staff

29. TPO
The TPO module has an authority to add student and Company to the system and provide their valid
user-id and password. The main user of the TPO module is TPO of the college. TPO of the college
will able to update details such as college name, college address, establish year, emp_id, branch,
number of student, email_id, contact number, web address, etc. The various events related to the
training and placement program is uploaded to the system by entering subject means event name and
text that contain detailed information about event. The user can able to change their password by
using change password field. Event option shows the event name, date of event, information about
the event. Company options display the company name and website of that company. The field about
us in the menu bar contains information about the admin module. After the completion of task user
will logout successfully by clicking on logout field at the top menu bar.

30. STUDENT
Student module deals with information of student. Student who has added by the
administrator to the system successfully can only able to access the system with their
valid user name and password provided by the administrator. First student should
login into the system by entering user name and password. Student can able to update
his information such as name, branch, year, aggregate marks, contact number, email,
etc. by clicking on Update Details option and also upload their CV. The change
password field is used by the student if he needs to change his password as same in
the admin module. After completing task successfully by click on the Logout, student
can successfully logout from the system.

31. COMPANY
Initially Company must need to login to the system by entering valid user_id and password provided
by the administrator module. The recruiter updates his details like his company name, working
criteria and information about itself. The Company will see the details about the college posted by
the tpo module to the system. The Company will also able to see the student details as name, branch,
aggregate marks, passed out year etc .Company can change his password if he required by using the
change password field. Mailing and messaging option is also available in Company module that
contain email /messages received and send by the TPO. The menu bar at the top can consist of same
field as previous module except that the about us field can contains information about the Company
module. By clicking on logout field the Company can successfully logout from the system

32. DATA INTEGRITY
Integrity Constraints are used to apply business rules for the database tables . The Constraints can be
specified immediately after the column definition.
Data Integrity is used to maintain accuracy and consistency of data in the table
1. .Primary Key
2. .Unique key
3. .default

33. STUDENT DATA BASE

34. Variable Datatype Constraint
Regno nvarchar(50) Primary key
Name nvarchar(50) not null
Password nvarchar(50) not null
Gmail nvarchar(50) not null
Branch nvarchar(50) not null
Phone nvarchar(50) Default null
Hobbies nvarchar(max) Default null
progLa nvarchar(max) Default null
Web nvarchar(max) Default null
Databases nvarchar(max) Default null
Peraddress nvarchar(max) not null
CourseSSC nvarchar(50) Default null
PercentageOfSSC nvarchar(50) Default null
inter_Dioploma nvarchar(50) Default null
PercentageOfInter nvarchar(50) Default null
CourseDEGree nvarchar(50) Default null
PercentageDegree nvarchar(50) Default null
CoursePG nvarchar(50) Default null
PercentagePg nvarchar(50) Default null
ProfileImage Image Default null

35. PLACEMENT EVENTS DATABASE DETAILS
Variable Datatype Constraint
Roll number Int Not null
Mode Of Event nvarchar(max) Not null
From date Date Not null
To date Date Not null
Title nvarchar(max) Default null
Purpose nvarchar(max) Default null
Target audience nvarchar(max) Default null
Link nvarchar(max) Default null

36. TRAINING EVENT DATABASE DETAILS
Variable Datatype Constraint
Rollnumber Int Not null
ModeOfEvent nvarchar(max) Not null
From date Date Not null
To date Date Not null
Title nvarchar(max) Default null
Purpose nvarchar(max) Default null
Target audience nvarchar(max) Default null
Link nvarchar(max) Default null

37. STAFF & TPO DATA BASE DETAILS
Variable Datatype Constraint
Username nvarchar(50) Primary key
Password nvarchar(max) Not null
Gmail nvarchar(50) Not null
Branch nvarchar(50) Not null
Mobile nvarchar(20) Default null
3.3.2 Staff Database
TPO database
Variable Datatype Constraint
Username nvarchar(50) Primary key
Password nvarchar(50) Not null
3.3.3 TPO Database

38. State diagrams
Staff state diagram Tpo state diagram

39. Student state diagram

40. USER INTERFACE DESIGN

41. STUDENT LOGIN

42. STUDENT HOME PAGE

43. STUDENT PROFILE VIEW

44. STUDENT TRAINING EVENTS CHECK

45. STUDENT CHANGE PASSWORD

46. STUDENT CHANGE EMAIL

47. STUDENT CHANGE PHONE NUMBER:

48. TPO LOGIN

49. TPO UPLOAD TRAINING EVENTS

50. TPO SEND MAIL:

51. COMPANY LOGIN

52. COMPANY CHANGE PASSWORD

53. STAFF LOGIN

54. STAFF CHECK TRAINING DETAILS

55. STAFF VIEW TRAINING DETAILS

56. STAFF CHANGE MAIL

57. SYSTEM ARCHITECTURE

58. Test cases
Test cases can be divided in to two types. First one is Positive test cases and second one is negative
test cases. In positive test cases are conducted by the developer intention is to get the output. In
negative test cases are conducted by the developer intention is to don’t get the output.

59. TPO TEST CASES
S
.No
Test case Description Actual value Expected value Result
1 Enter the username and
password
Verification of
login details.
Login Successfully true
2 Upload training events
,placement events
Enter event start
date , end date
and description
Update event start
date , end date
and description
into database
successfully
true
3 Change Password Enter old
password, and
new password
Successfully
change password
true

60. STUDENT TEST CASES
S
.No
Test case Description Actual value Expected value Result
1 Enter the username
and password
Verification of
login details.
Login
Successfully
true
2 View training events
,placement events
Enter event start
date , end date
and description
Display event
start date , end
date and
description from
database
successfully
true
3 Change Password Enter old
password, and
new password
Successfully
change
password
true

61. STAFF TEST CASES
S .No Test case Description Actual value Expected value Result
1 Enter the username
and password
Verification of
login details.
Login Successfully true
2 Upload training events
,placement events
Enter event start
date , end date
and description
Update event start
date , end date
and description
into database
successfully
true
3 Change Password Enter old
password, and
new password
Successfully
change password
true

62. Thank you