1.

Revisiting the Problem

INTRODUCTION This project is aimed at developing an online application for the Training and Placement Dept. of the college. The system is an online application that can be accessed throughout the organization and outside as well with proper login provided. This system can be used as an application for the TPO of the college to manage the student information with regards to placement. Students logging should be able to upload their information in the form of a CV. Visitors/Company representatives logging in may also access/search any information put up by Students. The placement cell ventures to be a bridge between the students and the prospective employers.

PURPOSE: Computer based information the system are designed has to to pass in access of the improve to the result. to It existing student has

system. Whatever and user It

information, TPO Improve quick

he or she can inform online. friendly interface the facility having of

accuracy

authenticated the details

documents. students. It

provides

maintaining

will reduce the paper work and utilize the maximum

capabilities of the

Setup and organization as well as it will save time and money which are spending in making reports and collecting data. It can be accessed throughout the organization and system can be outside used as as an well with proper for lo gin to

provided. This

application

college

manage the student

information with regards to placement.

PROBLEM STATEMENT:

Now a days, Student joins the college for the placement as well as for better training for their future. But there is manual training has going on there might be lot of

problem student as well as placement manager has to face. All the transactions are done manually. Fake entries can be there. System is more error - prone & time consuming. Difficulty in managing data of students. Large of piles of records are to be maintained. TPOs have to collect the information to recruit students and notify students various companies who want about them. It is a time

time to time

consuming activity of company requirements.

managing , updating and informing specific student for specific

SCOPE Project companies. Students system has scope has a big scope to do. We can of access previous Students can maintain about In placement. sector their This can

information and can update it. Notifications are sent to students about the information improvement / amendments. future,

communicate with each other online. All currently active enquires can also be added in the website to view if online. This application can be modified from time to time as per the changing requirement of the user with lesser cost also the The backend of with be the the application application can be changed also be as per the into storage and requirement of the application and to provide more security level features. limitation can looked enhancement can made as per user requirement . All though this project is

made only for a particular institute and supports a particular operating system platform , the wide application area of the project surpasses this small drawback. Hence proving its worth.

ABSTRACT This project report is intended to serve as a guide to the web application developing on Training and placement cell. I have tried to follow the principles and rules as suggested by the software engineers as far as possible, in order to make this application a Successful one.

The report starts with a comprehensive introduction to the project undertaken as its very FIRST PART. It includes objectives and scope of the project; about the front-end tool used i.e. ASP.NET and the back-end tool i.e. MS SQL SERVER2008 The SECOND PART presents and discusses the theoretical background of the project. The THIRD PART encompasses all the problems of the Web application that includes what is expected from the software, the demands and the requirements of the end-users. The FOURTH PART discusses the hardware and software requirements of the user machines. The FIFTH PART contains the data flow diagrams. The SIXTH PART contains the Screenshots. The SEVENTH PART is the user manual section. The Eight part is the annexure for the topic that includes some details about the organization, the data dictionary, definitions, acronyms and abbreviations used in the report. The final section is the reference part that contains a list of the books and reports that were referred during the development of the project and the report as well.

The emphasis in this report is to document the important concepts and techniques used for the successful development of this project.

I do hope fervently that, through this report, the readers will get a real picture of what the project is all about. I also wish that may this software satisfies all the needs and requirements of the organization, for which it is meant.

1.3 Project Plan Adherence

The project plan is in continuation as per the details shown in the Gantt chart Fig 1.1.The coding phase is under work and all the earlier phases are completed in accordance to the diagram shown below. The Analysis, Feasibility Study, and Design phases are discussed in more detail in the following sections of the Synopsis.

04/01/2012 24/01/2012 14/02/2012 04/03/2012 26/03/2012 16/04/2012 15/05/2012

Analysis

Feasibility Study

Design

Coding

Testing

Implementation

Duration(days)

Gantt Chart

3.Design
In designing database, various dependencies have been kept in consideration. Rules of normalization were followed to make the databases non-redundant and consistent.

3.1 Database Design

The description of these tables is given below :-

Project_Info
LIST OF TABLE LOGIN TABLE FIELDNAME USERNAME PASSWORD DATA TYPE NVARCHAR NVARCHAR SIZE 50 20

STUDENT REGISTER TABLE FIELDNAME FIRST NAME LAST NAME FATHER NAME GENDER ADDRESS DATE OF BIRTH DATA TYPE NVARCHAR NVARCHAR NVARCHAR NVARCHAR NVARCHAR DATE SIZE 50 50 50 50 250

USER NAME EMAIL PASSWORD CONFIRM PASSWORD

NVARCHAR NVARCHAR NVARCHAR NVARCHAR

50 50 20 20

COURSE HIGH YEAR INTERMEDIATE YEAR GRADUATION YEAR PERCENTAGE BATCH STREAM MOBILE NO

NVARCHAR INT INT NVARCHAR FLOAT INT NVARCHAR BIGINT

50

50

50

COMPANIES FIELDNAME COMPANY NAME DESCRIPTION CONTACT NO EMAIL ID DATA TYPE NVARCHAR NVARCHAR BIGINT NVARCHAR 50 SIZE 50 50

WEBSITE URL

NVARCHAR

50

COMPANY DETAILS FIELDNAME ID COMPANY NAME DATE POST VENUE PERCENTAGE NO OF BACKLOGS TIME PLACEMENT PROCESS DEPARTMENT PACKAGE BATCHYEAR DATA TYPE INT NVARCHAR DATE NVARCHAR NVARCHAR INT INT NVARCHAR NVARCHAR NVARCHAR NVARCHAR NVARCHAR 50 250 50 50 50 50 50 50 SIZE

STAFF FIELDNAME DATA TYPE SIZE

STAFF ID STAFFNAME DATE OF JOINING DEPARTMENT CONTACT NO EMAIL ID ADDRESS DESIGNATION

INT NVARCHAR NVARCHAR NVARCHAR BIGINT NVARCHAR NVARCHAR NVARCHAR 50 250 50 50 50 50

SELECTED STUDENTS FIELDNAME S NO ROLLNO OF CANDIDATES NAME OF CANDIDATES BRANCH DATE NAME OF COMPANY BATCH SALARY PACKAGE DATA TYPE INT INT NVARCHAR NVARCHAR DATE NVARCHAR NVARCHAR FLOAT 50 50 50 50 SIZE

PLACED STUDENTS FIELDNAME ID ROLLNO NAME BRANCH DATE BATCH PACKAGE POST EDUCATION SALARY PACKAGE DATA TYPE INT INT NVARCHAR NVARCHAR DATE NVARCHAR NVARCHAR NVARCHAR NVARCHAR FLOAT 50 50 50 50 50 50 SIZE

3.2 Process Design

ER Diagram
An Entity-Relationship Model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often relational, and its requirements in a topdown fashion. Diagrams created using this process are called entity-relationship diagrams, or ER diagrams or ERDs for short. Some of the various symbols used in the ERDs are shown below, followed by the list of entities and the ER Diagram of Project Tracking System.

Entity

Primary Key Attribute

Non Key Attribute

Relation