training and placement suite

8/7/2019 TRAINING AND PLACEMENT SUITE

1/12

TRAININGAND

PLACEMENT SUITE

PROJECT INGHARGE PROJECT GUIDE


2/12

INTRODUCTION

Develop an Internet Application for Training and Placement Cellfor automating the process of Resume Writing, Information to

students through SMS, students registering in interested companies

for interviews. This would be facilitating the students to make and

print their resumes in a proper format. In addition, it will be

facilitating the higher management to search the students

depending upon their skills sets and other attributes.

The Basic Requirement is to have a centralized repository of all the

skill-holders in the organization so that a student with a particular

skill set can be immediately found in case of urgent requirement.


3/12

RESEARCH PAPERS


4/12


5/12


6/12


7/12


8/12

MOTIVATION

Students tend make their Resume in wrong format, so this suite

will provide them with no.of formats for their Resume. The studenthas to just enter the request information in the software and the

software will generate a proper acceptable resume. This software

will also help Training and Placement department to send students

information of upcoming companies via sms. The student will just

have to register once and select the companies they wish to

interview for. Training and Department can also list the name and

information of students who were placed in companies through

campus interviews.


9/12

PROBLEM DEFINATION

The Basic Requirement is to have a centralized repository of all the

skill-holders in the organization so that a student with a particular

skill set can be immediately found in case of urgent requirement.

This will also ease the work for Training and Placement Cell.


10/12

SOFTWARE

Generic Technology keywords

Databases, Programming

Specific Technology keywords

MS-SQL server, HTML, Active Server Pages, Visual Basic

Project type keywords

Analysis, Design, Implementation, Testing, User Interface


11/12

ACTIVITY PLAN

Number Milestone

Name

Milestone

Description

Timeline

Week no.

from the startof the project

Remarks

1 Requirements

Specification

Complete

specification of the

system (with

appropriateassumptions)

including the

information to be present in the

Resume. A document

detailing the sameshould be written and

a presentation on that

be made.

AUGUST Attempt should be made to

add some more relevant

functionality other than

those that are listed in thisdocument.

2 Technology

familiarization

Understanding of the

technology needed to

implement theproject.

SEPTEMBER The presentation should be

from the point of view of

being able to apply it tothe project, rather than

from a theoretical

perspective.

3 Implementation

of the front-endof the system

Implementation of

the main screengiving the login,

screen that follows

the login giving

various options,screens for each of

the options (resume

building, resumesearching etc).

OCTOBER During this milestone

period, it would be a goodidea for the team (or one

person from the team) to

start working on a test-

plan for the entire system.This test-plan can be

updated as and when new

scenarios come to mind.

4 High-level andDetailed

Design

Listing down all possible scenarios

(like Entering resumeinformation,Searching Resume

based on several

criteria) and then

coming up with flow-charts or pseudo code

to handle the

NOVEMBER The scenarios should mapto the requirement

specification (i.e., for eachrequirement that isspecified, a corresponding

scenario should be there).


12/12

scenario.

5 Database

creation

A database of at least

100 entries of

employees of allgrades and all

possible technicalskill-set should becreated. A Database

design document

should be made.

DECEMBER It is important to finalize

on the database at this

stage itself so thatdevelopment and testing

can proceed with theactual database itself.

6 Integrating the

front-end with

the database

The front-end

developed in the

earlier milestone willnow be able to

update the employee

leave database. Other

features like mailnotification etc

should be functional

at this stage. In short,the system should be

ready for integration

testing.

JANUARY

7 Integration

Testing

The system should be

thoroughly tested byrunning all the test

cases written for the

system (frommilestone 5).

FEBRUARY Another 2 weeks should be

there to handle any issuesfound during testing of the

system. After that, the

final demo can bearranged.

8 Final Review Issues found during

the previousmilestone are fixed

and the system is

ready for the finalreview.

MARCH During the final review of

the project, it should bechecked that all the

requirements specified

during milestone number 1are fulfilled (or

appropriate reasons given

for not fulfilling the same)

training and placement suite

Documents