Group 3 CSL451 Project ­ Tnp Cell Automation Application 

  Training and Placement Cell (TnP cell) of a college helps in the interaction of students and                               companies with the help of college administration for the placement process. Every year many                           companies visit their preferred college to hire students for different roles. These companies                         typically hire final year students for job and pre­final year students for internship. Currently this                             entire process is initiated by TnP officers as they send their Job Announcement Form (JAF) to                               companies. Once the company receives the JAF and is interested to hire from the college, it will                                 fill the details in JAF and send back to college by email or by post. After that TnP officers fix                                       schedule with companies and inform the students about the same. Students have to inform TnP                             cell whether they will be appearing for particular company or not. Similarly after the interview                             process is over, TnP cell has to inform students about their selection or rejection.  Our aim is to automate this entire process with a nice database solution. We need this kind of                                   application as this entire process is being repeated every year in every college. Many a time                               students don’t get proper information and loose chance to get a job offer. So we need to have a                                     application which provides these functionalities and have a database which stores all these                         details which can help companies as well as TnP officers. The user base of the application are                                 students of a college, companies who want to hire the students from the college and Tnp Cell                                 officers of the college. In our application all the students and administrators will be having their                               account using which they can access our application whereas a company will have to create its                               account using its own credentials. In our application, we will be having following features/views:  Company View  

● An unregistered company use our application to send the request to hire to the TnP                             Officer by filling out the details of the JAF.  

● The company is registered and provided with login details. ● A registered company can send out the request for conducting the interview by providing                           

the exact details including the preferable timing, date. ● A registered company fix interview schedule with TnP officers. ● A registered company will see the list of students who have applied for their interview,                             

they can see their exact details as well resumes.  ● A registered company can update list of selected students for further rounds or list of                             

final selected students.   Student View 

● All registered students for the TnP Cell will be provided with a username and password. 

● Registered students can update their profile by adding CGPA, resume etc. ● A student logged into the system will be able to see the schedule of the companies who                                 

are coming to the campus. They can apply to the companies for which they are eligible. ● A student will get to know of his selection or rejection if any.  

 Administrator View Administrators will log into the system and can see the following notifications.  

● Request from the unregistered companies to get registered. ● Request from the registered companies to conduct interview. ● Request from the unregistered students to get registered. 

 Administrators gets following functionality as well: 

● Accepting/Rejecting request of a company to hire students from the college. ● Scheduling of visit of the company. ● Addition/Removal of a student. ● Updating the placement status of a student, whether he has been placed in any company                             

or not. ● Banning a student or company from the placement process. 

  To provide all these functionalities, our database will model following aspects: 

● Every company will be having a unique ID assigned to it by the our system. ● Every company will be having a name, address.  ● Every company will be having a status field which represents whether it has the approval                             

from the TnP cell to hire. Status can take only three values approved, rejected and                             pending. The default status is pending and it can be changed by Tnp Cell Representatives. 

 The company’s Job Application Form(JAF) contains Unique Application ID, Name of Company,                       Location of Jobs, Application Date, Contact Details, Job Details, Criteria, Selection Process. A                         company can visit only once for recruitment in an academic session. It can happen that its                               recruiting process lasts several days. 

● Selection process consists of whether short listing based on resume or not, Number of                           Technical Rounds, Process Details. Process Details is multivalued and it can take values                         HR Round, written Test and  Group Discussion.  

● Contact Details consists of Contact Person’s Name, email address and phone number.                       There can be more than one Contact Person and should not be any empty field in contact                                 details. 

● Job details consists of job designation, salary range, location. There can be more than one                             jobs offered by a company. Same job designation can have different location. Salary                         range consists of minimum salary and maximum salary.  

● Criteria consists of minimum CGPA, minimum 10th percentage, minimum 12th                   percentage. A company can leave these fields blank which means there is no minimum                           criteria to appear for that company. 

● A company can specify which are the degrees and departments it is hiring from.    There is schedule of companies. The schedule consists only those companies whose status is                           approved and date(s) of recruitment have been finalized. There is visiting date(s) and time                           assigned to each company.   The students will be having following aspects stored in our database: 

● His/her name which can have first name, middle name, last name. ● Unique roll number or entry number (related to college). ● Unique email ids. ● His/her CGPA, 10th percentage, 12th percentage, department. ● Resume in a pdf format. ● Number of backlogs which will be having value 0 if the student has cleared all the                               

courses so far. ● A student can apply in any number of companies if companies’ criteria is satisfied. 

 There can be several administrators where everyone will be having following details:  

● His/her name which can have first name, middle name, last name. ● Unique email id. ● Designation. ● Contact numbers, a single administrators can have multiple contact numbers. 

   There can be many interesting queries that can be performed using our application. Some of                             them are as follows: 

● A student can view which all companies are recruiting below a certain CGPA, which are                             the companies visiting on a particular date, which are the companies offering salary                         above a certain number. 

● A company after getting registered and finalising can view students in order of CGPA. ● Administrator can calculate some statistics like what is the average salary offered so far,                           

which students are yet to be placed, which were the companies offering salary more than                             a certain number and which were the students recruited by this company. 

  

­­­­­­­­­­­­­­­­­­­­­­­­­­­ Second Phase Submission (ER Diagram and UI Design)­­­­­­­­­­­­­­­   The conceptual design phase of the application includes identifying the entity and relationship                         sets of the application.  Entity Sets :­   

1) student 2) company 3) admin 4) interview 

 Relationship Sets :­  

1) conducts (between a company and an interview) 2) interested (between a student and an interview) 

  Design Decisions:  

1.) Entity set student stores detail corresponding to every student. Entry number of a                         student forms the primary key of the student entity set. Every student will be having a                               password to login on the TnP webpage. Student will be having name as a composite                             attribute which contains first name, middle name and last name. It also stores his/her                           email address, department and CV. CV is a multivalued attribute which stores CGPA,                         10th percentage, 12th percentage, courses done which will be used while deciding                       whether the student is eligible to sit in a particular interview. It also contains a link to                                 the pdf file of student’s resume. 

 2.) Entity set admin contains only aid (admin ID) and password. Admin will be having all                             

the rights to approve any company to visit the campus. Admin can also ban a                             particular student to appear in the interview. 

 3.) Entity set company will be identified with their unique company ID (cid). It also stores                             

password which will be used by the company to login on our TnP webpage. It also                               contain company name, type which is multivalued attribute which contain domain of                       the company. It will contain multi valued attribute hiring branch which store details of                           branches for which it will be recruiting. It will contain a complex attribute contact HR                             name, HR email and HR phone no. Company entity set will be having a approval                             

status which can take values pending, approved, rejected. This approval status will be                         modified by admin. 

4.) We also have a weak entity set interview which depends on company. It is related to                               company by conducts. In this date, time and type forms the discriminator. It will also                             have number of rounds. It will contain eligibility to appear in the interview which                           contains minimum CGPA, 10th percentage, 12th percentage. It will also contain                     degree which denotes which degree the company is interested in recruiting like                       B.Tech, M.Tech etc. It will also contain multi valued attribute job containing                       designation, salary and location. We have specified option to denote whether the                       company will be shortlisting from resume or not. 

 5.) Relationship set interested relates students and interviews. It is a many to many                         

relationship from student to interview. It also have a descriptive attribute which status                         which stores the result of the interview whether the student got placed or rejected. 

 6.) Relationship set conducts is an identifying relationship. It relates weak entity set                       

interview to strong entity set company. It is having one to many relationship from                           interview to company. It also has a descriptive attribute status contains whether the                         company has been approved by the admin to conduct the interview on the specified                           date or not. Here interview is having total participation. 

                       

E­R Diagram :­  

            UI Diagrams :­  

1) Figure 1 ­ Welcome Page 

 

  2)  Figure 2 ­ Student Log In  

   3) Figure 3 ­ Company Log In  

  4) figure 4 ­ Company Sign Up  

 

5) figure 5 ­ Admin Log In

 

6) figure 6 ­ Student Profile

  7) figure 7 ­ Student Apply  

  

8) figure 8 ­ Student Applied Interviews  

  9) figure 9 ­ Student Status  

  

10 ) figure 10 ­ Company Schedule Interview  

                 

11) figure 11 ­ Company Scheduled Interviews  

             

12) figure 12 ­ Administrator View Students 

  13) figure 13 ­  Administrator View Companies  

    

14 ) figure 14 ­ Administrator view Requests  

  15 ) Student Profile View  

   

16)  Company Profile View  

                        

Flow Diagram :­  

   

                         

 _____________________________Phase 3 Submission_______________________________  Note : ­E­R Diagram has been updated above to account for the details of administrator who made the changes.  We have updated our initial E­R diagram. We have included relationship set approves that relates company and admin. It is included to store detail of which admin has approved which company. One admin can participate several time in a approve relationship. Whereas a company can not participate more than once. As we are storing the detail of the company whose status are yet to be  approved or not approved, so company is having partial participation.  We have also included relationship set changes between admin and student. This is required to  store the changes that admin makes in a student profile. This will be having partial participation from both the admin and student. Here changes also have a multivalued descriptive attribute having change type and change desc. This will store all the changes made by admin for a student.   Using the updated E­R diagram, we figured all  functional dependencies and reduced the final relational schema into BCNF. As we have reduced our relational schema to BCNF, so it is also in 3NF.                   

    Relational Schema in BCNF :  

           

   Functional Dependencies:  1.) For student entity set, various functional dependencies are of the form  

Entry_number ­­­­­­>  * email ­­­­­­­> * where * can be any attribute (or combination of attribute) present in student entity set.  

 Here as Entry_number is a superkey and email is also one of the candidate key, so we don’t need to further reduce student entity set. It is already in BCNF. Student entity set is having a multivalued attribute courses_done, so we make a separate table for that.  2.) For company entity set, functional dependencies are of the form  

cid ­­­­­­­­> * hr_email ­­­­­­­­­­> * where * can be any attribute (or combination of attributes) present in company entity 

set.  Here as cid is a superkey and hr_email is also one of the candidate key, so we don’t need to further reduce student entity set. It is already in BCNF. Company entity set is having multivalued attributes type and hiring_branch, so we have made 2 separate tables for them.  3.) Interview is a weak entity set which depends on company via conducts, so we have created a relation following the rules for weak entity set.  This have all the functional dependencies of the form : 

date, time, type, cid ­­­­­­­­­­> * where * can be any attribute (or combination of attributes) present in interview entity 

set.  Here also as date, time, type, cid forms a superkey, so we don’t need to further reduce it  as it is already in BCNF.  4.) In case of admin entity set, only functional dependency is  

aid ­­­­­­­> password  

Here aid is the superkey so it is also in BCNF.