Training & Placement Information System

Indian Institute of Management Kozhikode

Submitted by:
(Section E)
Megha Anand Pravin P Prem Sarath Priyesh Wankhede Sujit Kumar Mandi Sukriti Jain PGP/15/289 PGP/15/303 PGP/15/304 PGP/15/305 PGP/15/322 PGP/15/323

Contents
1. Introduction
1.1 Objective 1

1.2 Scope of Project

2. Requirements Analysis
2.1 Problem Definition 2.2 Goal 2

2.3 Functional Requirements 2.4 Non-Functional Requirements 2.5 Interface Requirements 2.6 Installation Requirements 2.7 Feasibility Study

2 2 2 2 3 3

3. Design
3.1 Data Flow Diagrams 3.2 Use Case Analysis 3.3 High Level Design 4 8
12

4. Implementation & Testing

4.1 Unit Testing

4.2 Integration Testing

14 17

Introduction
The management of placement has long been supported by paper-based systems, databases, spreadsheets and E Mail communications. But in todays fast-moving world most of these are rendered redundant as being inflexible to changes they cannot respond quickly, especially during out-of-term. They are also staff intensive. Many placement web sites convey information but lack the interactive features to allow action on the information provided. Our project intends to create web based software for managing the placement process in colleges and helping the student and placement team in saving time, enhancing efficiency, and ensuring greater transparency. As per the empirical evidence the use of interface saves the precious man hours which can be better utilized in more important tasks.

Objective

This project aims at developing a web based interface which would increase the efficiency and effectiveness of the placements process happening at the institute. Through an online medium the students and companies can manipulate and maintain their data without the interference of placements team which will be ultimately authorized by the placements officer.

There are going to be three main users of this system: Student, Companies, and Placement Committee. Student: This is the primary actor in our system. The software provides following main operations for the Student: (i) Register for placements (ii) Edit his/her details (iii)View information of the companies Companies: This is also one of the primary actor in our system. The software provides following main operations for the companies: (i) Register for the recruitment process (ii) View Students profile (iii)Edit information regarding itself Placements Committee: Following are the main functions of the Placements Committee: (i) Regulate information of Student and Companies (ii) Inspect the various functioning of the system in terms of quality and flexibility (iii)Facilitate Authentication of the members at various levels 4

Scope

ANALYSIS
3.1 Requirement Analysis
For the successful completion of any project, requirement analysis is a must, much of the clients satisfaction depends on this phase of project development. If the requirements are gathered and analyzed properly, the final product will come up to the expectation of the client.

3.1.1 Problem Definition

To develop an online interface for the placements committee by means of which students and companies can register themselves for the recruitment process. It should be designed in such a way so as to aid in the placements process and to keep a track on the overall process.

3.1.2 Goal

The goal of this project is to develop a web interface to help the placements committee in effective recruitment process

3.1.3 Functional Requirements

Following are the functional requirements of our proposed system: (i) Register the Students: The students can register themselves with all their information for the placements process. He/she can also view information on the companies coming for recruitment. (ii) Register the Companies: The companies can register themselves with all their information for the placements process. It can also view information on the profile of the students participating for recruitment (iii) Maintain a consistent and real-time information database: The Placements Committee members should be able to authorize the data about the company and the students and they have all the right to modify them.

3.1.4 Non Functional requirements

Following are the non-functional requirements of our proposed system: (i) Efficient software to manage database (ii) An easy and efficient Graphical User Interface (iii) The final system should be scalable for any further enhancements (iv) The final system should be easy to run and manage

3.1.5 Interface Requirements

There will be 3 interfaces: User and Software (i) User Interfaces: The TPI System will have the following users: (a) Companies (b) Student 5

(c) Placements Committee. (i) Software Interfaces: The TPI System will have the following software interfaces: (a) Tomcat Server for hosting the web interface (b) Microsoft Access for maintaining the database.

3.1.6 Installation requirements

Following are the installation requirements for proper functioning of system: (i) The Java 1.5 or above platform, Standard Edition, to compile and run the java classes (ii) Apache Tomcat Server (iii) Internet/Intranet Connection

3.2 Feasibility study

In feasibility study we consider 3 types of feasibilities which are as follows: (i) Technical feasibility: This is technically feasible project because Java has the capability to capture time based text and transmit it which can be programmed to take text input from a source of our choice and transmit the reply to a destination computer in a specified format. In this project: (a) For authentication purpose, JDBC will be used. (b) For GUI, Java will be used. Resource Availability:- Software resources were completely available. (i) Economical Feasibility: Since software requirements of the system are very nominal. We just require a computer terminal and software like JAVA and Apache Tomcat which is available on websites free of cost. (ii) Operation Feasibility: We can easily say that it is operationally feasible because it does not concern with other software and working of the computer terminal. It also does not take any considerable time for taking input and saving the information received.

DESIGN
Data Flow Diagrams:
Compan Placement and Studen Training View Information Register Company Student y tInformation System Level Zero DFD:

In Level Zero, the company has to register itself into the Training, Placement and Information system for recruiting at the institute and the company can view the information of any particular student. Also the student needs to register into the system for participating in the placements process and he/ she can view the companies coming in for the hiring season.

Compan Studen Get View Student and Company Information Student and Company Database y t Registere d

Level One DFD:

At level one, the student and the company gets registered and the information is then stored in the database after which the students and companies can view each others information. The Circle Get Registered depicts the process of registration procured by both the students and the company. This information gets stored in the Student/Company database which is called a datastore in DFD diagrams and this information is used up by the View Student/Company Information process for further viewing of data

Control Flow for entity Placement Team:

EnterLOGININFO COMPANY INFO Enter Student ID STUDENT Enter Student RECRUITMENT Display Edit STA Company EN INVALID VALIDVerify ID VERIFICATION INFO ID RT D

Description of the Control Flow:

Step 1: The placement team member (user) logins to the Training, Placement and I Information System Step 2: The identity of the user is verified Step 3: If the user is authentic then the user is provided access to the system otherwise the user is reverted back to the login page. Step 4: Once the user is identified then he/she is directed to the specific page viz. Company, Student or Recruitment Information page. Step 5: Now for viewing or editing the student, company or recruited student info user enters their respective information viz. company ID, student ID or Student number. Step 6: Their respective identities are then verified and if found valid the data is then either displayed or presented for editing. Step 7: The flow ends.

Use-Case Analysis
Use cases describe the system from the user's point of view. Use cases describe the interaction between a primary actor (the initiator of the interaction) and the system itself, represented as a sequence of simple steps. Actors are something or someone which exists outside the system under study, and that take part in a sequence of activities in a dialogue with the system to achieve some goal. Actors may be end users, other systems, or hardware devices. Each use case is a complete series of events, described from the point of view of the actor. Use Case Diagrams for Training and Placement System are as follows: (i) Context level Use Case Diagram of Training and Placement System

Description: The figure above depicts the context level diagram of the Training and Placements system, which shows the primary actors of the system and the main functions that they perform. (a) Student: A Primary Actor of the system who will register and then appear for placements (b) Companies: A Primary Actor of the system who will first register itself and then will come to the campus for the recruitment process 9

(c) Placement Comm.(Administrator): A Primary Actor of the system who will monitor the whole placement process and will have the access rights to modify students and companies database.

(i) Detailed Use-Case As per Training and Placement Information system the Use Cases are developed for: (a) Student(Fig 3.2) (b) Company(Fig 3.2) (c) Placements Team(Fig 3.4) (a) Detailed Use-Case for Actor Student

Fig 3.2- Use-case Description for Actor Student

Use Case

Pre-Condition

Enter None Details for registration

Post Condition Student will be registered into the placements database

Normal flow

Alternative Flow Student will enter No alternative the necessary flow details he is asked for and will get registered.

10

View Company Details

None

Student aware of details of company coming recruitment

is Student will get a None the list of all the the companies visiting the for campus for recruitment

(b) Detailed Use-Case for Actor Company

Fig 3.3- Use case Description for Actor Company

Use Case

Pre-Condition

Enter None Details for registration

Post Condition Company will be registered into the placements database

Normal flow

Alternative Flow Company will No alternative enter the flow necessary details he is asked for and will get registered.

11

View Students Profile

None

Company will Company will None be aware of the get a list of all batch profile. the students participating for the placements process

(c) Detailed Use-Case for Actor Placements Team

Figure 3.4- Use-case Description for Actor Placements Team

Use Case

Post Condition Edit Placement Modifications Student/Company Member must will be made Details be logged in successfully

Pre-Condition

Normal flow

Place Notifications

Placement Notifications Member must placed if any be logged in

Alternative Flow The members No alternative enters flow student/compan y ID or searches in a predefined order Members will None be placing any notifications regarding the placements process

12

Search Placement Student/Comp Student/Company Member must any searched be logged in

By giving an None input of ID, the members can search a company/stude nt

High Level Design:

It contains the description of all the modules of the project in a brief way 1. Login: This module aids in helping the placement committee members to login into the main system for performing authorized operations. The module asks for username and password and after successful match from the database logs the member in. Inputs: User id Password Processing:Upon insertion of the entries stated above it will check the validity of authorization. If member is authorized then continue processing else Suspend processing and Generate Error message Invalid UserId or Password. Output:The placement member is logged into the main home web page.

2. Student Registration: The student for appearing in the placements process has to first register himself with the TPI system. The student has to enter various details like his name, dob, gender, PGP Roll No, year, CG, contact no. After entering all this details the student gets registered with the system. Inputs:A screen for the addition of students information will appear asking for PGP Roll No, name, type of placement, CG, contact, email, date of birth. After entering all this data the student will be registered in the system. Input: Student information. Processing: The students details will be entered into students database. 13

Output: The student is registered in the database; will be displayed and student will be registered Company Registration: The Companies for conducting a recruitment session at the college should register prior to the placement season. The company has to various enter information like the annual compensation offered, its contact no, website and expected date of visiting the campus.

Inputs:A screen for the addition of recruiters details will appear. The recruiter is required to enter details like name of the organization, criteria for selection, annual compensation, registered office address, contact number of the HR, website, email etc. Output:Screen will display message as The recruiter is registered in the database and recruiter will be registered. Viewing Recruited Students: This module is developed to give information about those candidates who are already recruited and mentions about the candidates name, recruiting company and some other details too. Input: -Output: List of recruited students Searching & Modification to Student and Company Database: Only the Placements Chairman and members of the committee are authorized to make any changes to the main database containing the students and companies information. Input: Company ID or Student ID Processing: Editing of any information will be done by the web interface and it will reflect changes in the database at real time. Output: Student/Company searched or Modifications being made to Student/Companys data

14

Testing
Test Test Case Description Case ID Operation Inputs Given Performed 1. Submit button 1.No input given clicked on 2.Only username login page given 3.Only password given 4.Invalid username or invalid password given 5.Valid username and valid password given Expected Result Actual Result Result

Access Denied Access Denied Access Denied Access Denied

Access Denied Access Denied Access Denied Access Denied

Test Case Passed Test Case Passed Test Case Passed Test Case Passed

Access Granted

Access Granted

Test Case Passed

6.1Unit Testing
Testing of Login Module

Testing of Student Module

Test Case ID 1. Test Case Description Operation Performed Register Student Inputs Given 1.All inputs are null Error Message 2.Roll number not Error Message given Error Message Test Case Passed Error Message Test Case Passed Expected Result Actual Result Result

15

3.String input for aggregate field 4.Student name not given 5.Wrong input given in date field 6.All inputs are entered correctly 2. Update Student 1.All inputs are null 2.Roll number not given 3.String input for aggregate field 4.Student name not given 5.Wrong input given in date field 6.All fields Updated Correctly

Error Message Error Message Error Message Error Message Accepted Error Message Error Message Error Message Error Message Error Message Error Message

Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed Accepted Test Case Failed

Accepted Test Case Passed Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed Accepted Test Case Failed

3.

Delete Student

Successfully Updated 1.Clicked on delete Corresponding link Entry Deleted

Successfully Successfully Updated Updated Corresponding Test Case Passed Entry Deleted

Testing for Company Module

Test Case ID 1. Test Case Description Operation Performed Register Company Inputs Given 1.All inputs are null 2.Company name not given 3.String input given for package field 4.Wrong input given in date field 5.Wrong input given in date field 6.All inputs are entered Error Message Error Message Error Message Error Message Error Message Accepted Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed Accepted Test Case Failed Expected Result Actual Result Result

Error Message Test Case Passed Accepted Test Case Passed 16

2.

Update Company

correctly 1.All inputs are Error Message removed 2.Company name is removed 3.String input given for package field 4.Wrong input given in date field 5. Wrong input given in date field 6.All fields Updated Correctly 1.Clicked on delete link Error Message Error Message

Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed

Error Message Error Message Successfully Updated Corresponding Entry Deleted

Accepted

Test Case Failed

Error Message Test Case Passed Successfully Updated Test Case Passed

3.

Delete Company

Corresponding Test Case Passed Entry Deleted

Testing for Recruited Student Module

Test Case ID 1. Test Case Description Operation Inputs Given Performed Enter Recruited 1.All inputs are Student null 2.Roll number not given 3.Roll number not in student database 4.String input for Package field 5.Student name not given 6.Wrong input given in join date field 7.All inputs are entered correctly Expected Result Actual Result Result

Error Message Error Message Error Message

Error Message Test Case Passed Error Message Test Case Passed Error Message Test Case Passed

Error Message Error Message Error Message Accepted

Error Message Test Case Passed Error Message Test Case Passed Accepted Accepted Test Case Failed Test Case Failed

17

2.

Update Recruited Student

3.

Delete Recruited Student

1.All inputs are removed 2.Roll number removed or not in student database 4.String input for Package field 5.Company name removed or not in company database 6.Wrong input given in or removed from join date field 7. All fields Updated Correctly 1.Clicked on delete link

Error Message Error Message

Error Message Test Case Passed Error Message Test Case Passed

Error Message Error Message

Error Message Test Case Passed Error Message Test Case Passed

Error Message

Accepted

Test Case Failed

Successfully Updated Corresponding Entry Deleted

Successfully Test Case Passed Updated Corresponding Test Case Passed Entry Deleted

6.2 Integration Testing

Test Test Case Cas Description e ID 1.1 Clicked on submit button of login page 1.2 2.1 Clicked on submit button of login page Clicked on enter student information link Clicked on submit button on student addition screen Expected Result Homepage displayed (home.jsp) Actual Result Result Cause Measures Taken

3.1

Control remains Test Case Connection DSN on login page Failed not created established, DSN not created Homepage Homepage Test Case displayed displayed Passed (home.jsp) (home.jsp) Control Control goes to Test Case should go to Student/registra Passed Student/regist tion.jsp ration.jsp Successfully Error Page Test Case Connection DSN registered Failed not created established, DSN not created 18

3.2

4.1

Clicked on submit button on student addition screen Clicked on submit button on company addition screen Clicked on submit button on company addition screen Clicked on submit button on recruited student addition screen Clicked on submit button on recruited student addition screen Clicked on DELETE link on Student information screen

Successfully registered Successfully registered

Successfully registered Error Page

Test Case Passed Test Case Connection DSN Failed not created established, DSN not created Test Case Passed Test Case Connection DSN Failed not created established, DSN not created Test Case Passed 1.Foreign Key set 2.On Delete Cascade set

4.2

Successfully registered Successfully registered

Successfully registered Error Page

5.1

5.2

Successfully registered

Successfully registered

6.1

6.2

Clicked on DELETE link on Student information screen

7.1

Clicked on SEARCH link on Homepage

Correspondin g Student information deleted from student database as well as from recruited student database. Correspondin g Student information deleted from student database as well as from recruited student database. Control should go on Student/ssearc h.html

Corresponding Test Case entry deleted Failed from student database but not from recruited student database

1.Foreign Key not declared 2.On Delete Cascade not implemente d

Corresponding Test Case Student Passed information deleted from student database as well as from recruited student database.

Control remains Test Case Correct link Correct link on same page Failed path not path set given in jsp code 19

7.2

Clicked on Control SEARCH link should go on on Homepage Student/ssearc h.html 8.1 Clicked on Successfully SUBMIT Updated button Update student screen 9.1 Clicked on Correspondin DELETE link g Company on Company information information deleted from screen Company database as well as from recruited student database. 9.2 Clicked on Correspondin DELETE link g Company on Company information information deleted from screen Company database as well as from recruited student database. 10.1 Clicked on Correspondin SUBMIT g Student button on information Student updated in Update screen student database as well as in recruited student database. 10.2 Clicked on Correspondin SUBMIT g Student button on information Student updated in Update screen student database as well as in recruited student database.

Control should go on Student/ssearch. html Successfully Updated

Test Case Passed Test Case Passed

1.Foreign Key not declared 2.On Delete Cascade not implemente d

1.Foreign Key set 2.On Delete Cascade set

Corresponding Test Case entry deleted Failed from Company database but not from recruited student database

Corresponding Company information deleted from Company database as well as from recruited student database. Corresponding entry updated in student database but not in recruited student database

Test Case Passed -

Test Case 1.Foreign Failed Key not declared 2.On Update Cascade not implemente d

1.Foreign Key set 2.On Update Cascade set

Corresponding Test Case Student Passed information updated in student database as well as in recruited student database.

20

21