TRAINING

AND
PLACEMEN
T SUITE

PROJECT INGHARGE PROJECT GUIDE

 INTRODUCTION

Develop an Internet Application for Training and Placement Cell

for 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.
RESEARCH PAPERS
 MOTIVATION

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

will provide them with no.of formats for their Resume. The student
has 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.
 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.
 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

 ACTIVITY PLAN
Number Milestone Milestone Timeline Remarks
Name Description
Week no.
from the start
of the project
1 Requirements Complete AUGUST Attempt should be made to
Specification specification of the add some more relevant
system (with functionality other than
appropriate those that are listed in this
assumptions) document.
including the
information to be
present in the
Resume. A document
detailing the same
should be written and
a presentation on that
be made.
2 Technology Understanding of the SEPTEMBER The presentation should be
familiarization technology needed to from the point of view of
implement the being able to apply it to
project. the project, rather than
from a theoretical
perspective.
3 Implementation Implementation of OCTOBER During this milestone
of the front-end the main screen period, it would be a good
of the system giving the login, idea for the team (or one
screen that follows person from the team) to
the login giving start working on a test-
various options, plan for the entire system.
screens for each of This test-plan can be
the options (resume updated as and when new
building, resume scenarios come to mind.
searching etc).
4 High-level and Listing down all NOVEMBER The scenarios should map
Detailed possible scenarios to the requirement
Design (like Entering resume specification (i.e., for each
information, requirement that is
Searching Resume specified, a corresponding
based on several scenario should be there).
criteria) and then
coming up with flow-
charts or pseudo code
to handle the
 scenario.
5 Database A database of at least DECEMBER It is important to finalize
creation 100 entries of on the database at this
employees of all stage itself so that
grades and all development and testing
possible technical can proceed with the
skill-set should be actual database itself.
created. A Database
design document
should be made.
6 Integrating the The front-end JANUARY
front-end with developed in the
the database earlier milestone will
now be able to
update the employee
leave database. Other
features like mail
notification etc
should be functional
at this stage. In short,
the system should be
ready for integration
testing.
7 Integration The system should be FEBRUARY Another 2 weeks should be
Testing thoroughly tested by there to handle any issues
running all the test found during testing of the
cases written for the system. After that, the
system (from final demo can be
milestone 5). arranged.
8 Final Review Issues found during MARCH During the final review of
the previous the project, it should be
milestone are fixed checked that all the
and the system is requirements specified
ready for the final during milestone number 1
review. are fulfilled (or
appropriate reasons given
for not fulfilling the same)