PUSBALATHA
PUSBALATHA
By
T.KAVIYARSU
(Reg.No:0620315005)
2017-2020
DEPARTMENT OF COMPUTER SCIENCE,
Dr. ZAKIR HUSAIN COLLEGE,
ILAYANGUDI-630 702
V.RINI BHAVADHARANI.,
Asst.prof of computer science, Date:
Dr. Zakir Husain College,
Ilayangudi-630 702.
BONAFIDE CERTIFICATE
CERTIFICATE
Signature
(V.RINIBHAVADHARANI)
DECLARATION
I hereby declare that this work has not carried out from any other project work
and has not been submitted for similar degree.
M.AYISHA SITHIKKA
V.PUSHBALATHA
ACKNOWLEDGEMENT
First of all I think god who has given power and knowledge to complete the
project successfully.
We thank the god almighty for his grace and without whose blessings we would
have not completed this work.
M.AYISHASITHIKKA
V.PUSHBALATHA
CONTENTS
Chapter I: Introduction
• Abstraction
• Synopsis
• Problem definition
• Problem description
Chapter II: System Analysis
• Existing system
• Proposed system
Chapter III: Hardware and Software Requirements
• Software specification
Chapter IV: Design and Development
• Architectural design
• Data flow diagram
Chapter V: Details of the Software
Chapter VI: Testing
Chapter VII: Implementation and Evaluation
Chapter VIII: Appendix
• Table structure
• Form components
• Screen interface
• Coding
• Output
Chapter IX: Conclusion
Chapter X: Bibliography
CHAPTER-I
INTRODUCTION
ABSTRACT:
The ‘Training and Placement cell’ is developed to maintain the details of student
information, trace the details of student also maintain the information about the
company availability. Using this project user may know all the details which are
provided by the ‘Training and Placement’. Users can view the availability of company
and dates of passing. In the same way in this project one more user is involved he is
most important person who is able to controlling all the information and also
makes the necessary changes when they raised is called ‘Administrator’. He can
do the updates and set the job information regarding the company and change the
users name and passwords such type of all these things are made by the
administrator level.
SYNOPSIS:
Training and placement cell is C# .Net used to find the placements around you
and this final year project allows you to directly apply for the drive and the
company who is conducting the drive will see your request and if they interested in
your profile they will accept the request.
This procedure is very much easy and time saving for those who are attending
drives. In this application, the admin will log in and add the companies by giving
all the necessary details. The admin can view the user requests if any registered
user’s login and view the drives and send a request for a drive.
Now the admin can accept the user requests by seeing his details in user details
like his percentage in Engineering etc. Before accepting the user admin will search
the user by the name he can find the details of user like Resume etc. This
application will help the user in finding right jobs to apply.
PROBLEM DEFINTION:
The aim of this project is to develop an online for training and placement
department of our college. The system is an application that can be accessed
throughout the college with proper login provided. This system can be used as an
application for the Training and the Placement officers (TPO) of the college to
manage the student information with regard to placement. Student login should be
able to upload their information in the form of CV. The application provides the
facility of maintaining the details of the students. It also provides a requested list of
candidates to recruit the students based on given query. Administrator logging in
may also search any information put up by the students.
1. Admin
2. User
Admin:
Admin will login into the application by giving username and password and
admin can view the registered users in the application and their basic information
about academics. Admin Will post the Drive notices if any campus placements or
drives taking place in the college. Admin can also search the registered users and
admin can view the users resume by clicking on the users. Admin can accept the
drive requests from the user.
User:
The user will register and login into the application by giving username and
password. The user will see the drive uploaded by the admin. If the user is
Interested in the drive he can send the request for the drive and if admin accepts
the user request he can attend the drive.
CHAPTER-II
SYSTEM ANALYSIS
The system study is usually concerned with system involving input and output
processos. System can be regarded as a set of interacting elements responding to
inputs to produce required outputs.manually generated reports do not provide
satisfactory information and it cannot be done in time. Due to involvement of lot of
manual works,the updating process over the records is a tedious one.
EXISTING SYSTEM:
In the existing system, we need to search for jobs on different websites and we
may not know whether they are correct or not so there may chance of misguiding
users. In the existing system if the recruiter needs to the user resume by the details
given by him.
PROPOSED SYSTEM:
In the Proposed System, the registered user can directly view the jobs, which
are posted by admin. If the user is interested, he can directly send the request. If the
recruiter wants to see the user resume he can just directly search the user and he
can find the username.
CHAPTER-III
SOFTWARE REQUIREMENTS:
FEASIBILITY STUDY:
Feasibility Study is a preliminary study undertaken to determine
and document a project's viability. The term feasibility study is also used to refer to
the resulting document. These results of this study are used to make a decision
whether to proceed with the project, or table it. If it indeed leads to a project being
approved, it will — before the real work of the proposed project starts — be used
to ascertain the likelihood of the project's success. It is an analysis of possible
alternative solutions to a problem and a recommendation on the best alternative.
Economic feasibility
Technical feasibility
Operation feasibility
ECONOMIC FEASIBILITY:
TECHNICAL FEASIBILITY:
This involves questions such as whether the technology needed for the
system exists, how difficult it will be to build, and whether the firm has enough
experience using that technology. The assessment is based on an outline design of
system requirements in terms of Input, Processes, Output, Fields, Programs, and
Procedures. This can be qualified in terms of volumes of data, trends, frequency of
updating in order to give an introduction to the technical system. The application is
the fact that it has been developed on Windows XP platform and a high
configuration of 1GB RAM on Intel Pentium dual core processor. This is
technically feasible.
OPERATION FEASIBILITY:
CHAPTER-IV
DESIGN AND DEVELOPEMENT
Process
Flow of data
Data Storage
ARCHITECTURAL DESIGN:
X percentage
X passing year
Admin
Training Placement
Description
Contact no Address
Admin
User
DOB Gender
Email
EDUCATIONAL DETAIL(DFD):
TRAINING AND PLACEMENT CELL
Admin
User
Educational detail
SYSTEM DESIGN:
DATA DESIGN:
The overall objective in the development of database technology has been to
treat data as organizational resource and as an integrated whole database
management system allow the data to be protected and organized separately from
other resource. Database can be defined as an “integrated collection of data”.
Database is a crucial factor in the performance of system both in term of system
timings and in the case with which the system can be maintained or modified.
Data store could have been implicit or explicit in the logical system selected
by the user. The designer now has to take those logical store and physical file from
them if the data management software can centralized access to the data from the
program; it is possible to treat the data as a separate resource. The organization of
the data in a database aims three major objectives namely data integration, data
integrity and data dependence.
INPUT DESIGN:
In this project various resources like textboxes, dropdown list, link buttons etc
are used for accepting user inputs. The main type of inputs to this project is files
which can be a text file or image file. The other inputs to this project include file
names, destination user name, integer values for splitted into packets and
transferred to the specified destination. Destination user name is the user who is
going to reassemble the splitted packets.
Taking into account, all the above needs of the input designing, the new
process designing could have the following features. In all cases processing should
be automatic and manual work should be kept minimum. Similarly, the user input
should also be kept minimum or least extend possible. By giving the above input
calculations should be automatic. The auto calculation is the motto of this new
process, while providing the auto calculation the result with minimum time
operation, should be accurate and free from errors.
OUTPUT DESIGN:
Output design generally to refers the result and information’s that are
generated by the system for many end-users; output is the main reason for
developing the system and the basis on which they evaluate the usefulness of the
application. The basis requirements of output are that it should be accurate, timely
and appropriate, in terms of content, medium and layout for its intended purpose.
The important task of any system lies in the capability of producing high
quality output and report. Computer output is the most important and direct source
of information to the user. A goo output design contains all required information
and well formatted for the better visualization and avoids the complexity in
displaying the data this system was developed by keeping in mind and paper output
is displayed for the user accurately.
In this project is the reassembly file that was received by the user all the
destination and the messages found in the client’s inbox and the report that was
generated which shows the number of packets transferred along with
CHAPTER-V
DETAILS ABOUT SOFTWARE:
DOTNET:
The .Net frame work is a comprehensive platform that can be a little difficult
to describe. It has been described as a Development Platform an execution
environment and the operating system among other things. In fact in some aside
from embracing the web, Microsoft .NET acknowledges and responds
C# DOT NET:
C# is a multi-paradigm programming language encompassing imperative,
declarative, functional, generic, object-oriented (class-based), and component-
oriented programming disciplines. It was developed by Microsoft within
the .NET initiative and later approved as a standard by Ecma (ECMA-334)
and ISO (ISO/IEC 23270). C# is one of the programming languages designed for
the Common Language Infrastructure. C# is intended to be a simple, modern,
general-purpose, object-oriented programming language. Its development team is
led by Anders Hejlsberg.
The C# language is disarmingly simple, with only about 80 keywords and a dozen
built-in data types, but C# is highly expressive when it comes to implementing
modern programming concepts. C# includes all the support for structured,
component-based, object-oriented programming that one expects of a modern
language built on the shoulders of C++ and Java. The C# language was developed
by a small team led by two distinguished Microsoft engineers, Anders Hejlsberg
and Scott Wiltamuth. Hejlsberg is also known for creating Turbo Pascal, a popular
language for PC programming, and for leading the team that designed Borland
Delphi, one of the first successful integrated development environments for
client/server programming. At the heart of any object-oriented language is its
support for defining and working with classes. Classes define new types, allowing
you to extend the language to better model the problem you are trying to solve. In
C# everything pertaining to a class declaration is found in the declaration itself. C#
class definitions do not require separate header files or Interface Definition
Language (IDL) files.
MS-ACCESS:
Microsoft Access is a Database Management System (DBMS) from Microsoft
that combines the relational Microsoft Jet Database Engine with a graphical user
interface and softwaredevelopment tools. It is a part of the Microsoft Office suite
of applications, included in the professional and higher editions. This is an
introductory tutorial that covers the basics of MS Access.The SQL language is sub-
divided into several language elements, including:
Database File:
It is a file which stores the entire database. The database file is saved to your hard
drive or other storage devices.
Datatypes:
Datatypes are the properties of each field. Every field has one datatype like text,
number, date, etc.
Table
A Table is an object which stores data in Row & Column format to store
data.
Query
Queries answer a question by selecting and sorting and filtering data based
on search criteria.
Queries can pull from one or more related Tables and other Queries.
Types of Query can be SELECT, INSERT, UPDATE, DELETE.
Form
A form is a database object that you can use to create a user interface for a
database application.
Forms help you to display live data from the table. It mainly used to ease the
process of data entry or editing.
Report
Macros:
Macros are mini computer programming constructs. They allow you to set up
commands and processes in your forms, like, searching, moving to another record,
or running a formula.
Modules:
Modules are procedures(functions) which you can write using Visual Basic for
Applications (VBA).
MS Access Datatypes:
Type of
Description Size
Data
Short Text Text, including numbers which does not Up to 255 characters.
need calculation. (e.g., Mobile
numbers).
This data type is used for lengthy text or Maximum 63, 999
Long Text
alphanumeric data. characters.
Numeric data type used for storing
Number 1, 2, 4, 8, and 16 bytes.
mathematical calculations.
Store Date/time for the years 100
Date/Time 8 bytes.
through 9999.
It allows you to store currency values
Currency and numeric data with one to four 8 bytes.
decimal places.
Assign a unique number or assigned by
Auto Microsoft Access when any new record Four bytes (16 bytes if it is
Number is created. Usually used as the primary set as a Replication ID).
key
Yes/No It only stores logical values Yes and No.1 bit
It stores files, such as digital photos.
Attachmen Up to 2 GB Data can be
Multiple files can be attached per
t stored.
record.
OLE OLE objects can store audio, video, Up to 2 GB data can be
objects other Binary Large Objects. stored.
Text or combinations of text and Each part of a Hyperlink
Hyperlink numbers stored. That text is used as data type allows you to store
hyperlink address. a maximum 2048 characters.
You can create an
Helps you to create an expression that
Calculated expression which uses data
uses data from one or more fields.
from one or more fields.
CASE TOOLS
The description of a use case defines what happens in the system when the use
case is performed. In essence, the use-case model defines the outside (actors) and
Inside (use case) of the system’s behavior. Use cases represent specific flows of
events in the system. The use cases are initiated by actors and describe the flow of
events that these actors set off. An actor is anything that interacts with a use case:
It could be a human user, external hardware, or another system. An actor
represents a category of user rather than physical user. Several physical users can
play the same role. For example, in terms of a Member actor, many people can be
members of a library, which can be members of a library, which can be represented
by one actor called Member.
Sequence Diagram:
Sequence diagram are easy and intuitive way of describing the behavior of a
system by viewing the interaction between the system and its environment. A
sequence diagram shows an interaction arranged in a time sequence. It shows the
objects participating in the interaction by their lifelines and the messages they
exchange, arranged in a time sequence. A sequence has two dimensions: the
vertical dimension represents time, the horizontal represents different objects
Collaboration:
Collaboration is a recursive process where two or more people or organizations
work together in an intersection of common goals — for example, an intellectual
endeavor that is creative in nature by sharing knowledge, learning and building
consensus. Most collaboration requires leadership, although the form of leadership
can be social within a decentralized and egalitarian group. In particular, teams that
work collaboratively can obtain greater resources, recognition and reward when
facing competition for finite resources. Collaboration is also present in opposing
goals exhibiting the notion of adversarial collaboration, though this is not a
common case for using the word. Structured methods of collaboration encourage
introspection of behavior and communication. These methods specifically aim to
increase the success of teams as they engage in collaborative problem solving.
Forms, rubrics, charts and graphs are useful in these situations to objectively
document personal traits with the goal of improving performance in current and
future projects.
Class:
Activity:
CHAPTER-VI
SYSTEM TESTING
Testing is the stage of implementation, which is aimed at ensuring that
the system works accurately and efficiently before live operation
commences. The logical design and physical design is thoroughly and
continually examined on paper to ensure that they will work when
implemented.
Unit testing
Integration testing
UNIT TESTING:
Unit testing is under taken when a module has been coded and
successfully reviewed. This can be done by two methods:
Test cases are designed from an examination of the input/output values only and no
knowledge of designing or coding is required the following are the two main
approaches of designing black-box test cases
b) Equivalence Class Partitioning:
INTEGRATON TESTING:
Purpose:
CHAPTER-VI
APPENDIX
TABLE STRUCTURE:
CONTENT DATATYPE
Course training Text
Salary Text
Contact no Text
Address Text
Description Text
DOB Text
Gender Text
Address Text
Contact no Text
Email Text
EDUCATIONAL DEATAIL:
CONTENT DATATYPE
UG Text
PG Text
X percentage Text
CODING:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace placement
{
public partial class cv : Form
{
OleDbConnection cnn;
public cv()
{
InitializeComponent();
}
}
private void cv_Load(object sender, EventArgs e)
{
string connectionstring = null;
connectionstring = @"Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=D:\senthil\placement\placement.mdb";
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace placement
{
public partial class Form1 : Form
{
OleDbConnection cnn;
public Form1()
{
InitializeComponent();
}
string sql;
OleDbCommand command;
cnn.Open();
sql ="insert into
request(username,usertype,request)values('"+textBox1 .Text +"','"+textBox2 .Text
+"','"+comboBox2 .Text +"')";
command = new OleDbCommand(sql, cnn);
command.ExecuteNonQuery();
MessageBox.Show("Request sent");
welcome obj1 = new welcome();
obj1.ShowDialog();
cnn.Close();
}
}
}
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
namespace placement
{
public partial class login : Form
{
public login()
{
InitializeComponent();
}
}
}
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace placement
{
public partial class placementreport : Form
{
OleDbConnection cnn;
OleDbDataAdapter da;
public placementreport()
{
InitializeComponent();
}
}
}
}
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace placement
{
public partial class studentreg : Form
{
OleDbConnection cnn;
public studentreg()
{
InitializeComponent();
}
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace placement
{
public partial class traininginfo : Form
{
OleDbConnection cnn;
public traininginfo()
{
InitializeComponent();
}
}
}
}
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Data.OleDb;
namespace placement
{
public partial class traininginfo : Form
{
OleDbConnection cnn;
public traininginfo()
{
InitializeComponent();
}
}
}
}
SCREEN INTERFACE:
CHAPTER-IX
CONCLUSION:
BIBILIOGRAPHY:
www.dotnetspider.com
www.c#corner.com
www.planetsourcecode.com
Book Name :