BANGALORE CITY UNIVERSITY

A PROJECT REPORT ON

“MANPOWER MANAGEMENT”

Submitted in the partial fulfilment for the requirement of V semester

Bachelor of Computer Applications

By

PRASHANTH KUMAR R (R1821223)

SUNIL KUMAR (R1821235)

Under the guidance of

Mrs. Anushueeba K

BISHOP COTTON ACADEMY OF PROFESSIONAL MANAGEMENT

YELAHANKA NEW TOWN, BANGALORE-64

2020-2021
 BANGALORE CITY UNIVERSITY

A PROJECT REPORT ON

“MANPOWER MANAGEMENT”

Submitted in the partial fulfilment for the requirement of V semester

Bachelor of Computer Applications

By

PRASHANTH KUMAR R (R1821223)

SUNEEL KUMAR (R1821235)

Under the guidance of

Mrs. Anusheeba K

BISHOP COTTON ACADEMY OF PROFESSIONAL MANAGEMENT

YELAHANKA NEW TOWN, BANGALORE-64

2020-2021
 CERTIFICATE

This is to certify that the project report entitled

MANPOWER
Submitted to Bishop Cotton Academy of Professional Management, Bangalore
City University in partial fulfilment for the requirement of the award of the
degree of BACHELOR OF COMPUTER APPLICATIONS is an original
work carried out by PRASHANTH KUMAR R (R1821223) and SUNEEL
KUMAR (R1821235) under the guidance of Mrs. Anusheeba K.

The matter embodied in this project is a genuine work done by the students and
has not been submitted whether to this University or to any other
University/Institute for the fulfilment of the requirement of any course of study.

Signature of the guide Signature of the HOD

Signature of Examiners
 DECLARATION

We hereby declare that this dissertation entitled “MANPOWER

MANAGEMENT” submitted to Bangalore City University in partial
fulfilment of the requirement for the award of Bachelors of Computer
Applications has been originally carried out by us under the guidance
of Mrs. S Kala. This work has been not submitted elsewhere for any
other degree.

PRASHANTH KUMAR R (R1821223)

SUNEEL KUMAR (R1821235)

 ACKNOWLEDGEMENT

No work can be completed successfully unless the path of wisdom is

illuminated by the luminous and excellent guidance. Dozens of people
have aided by devoting their help in preparing the project report.

We would like to express our gratitude to all those who gave us the
possibility to complete this project work. Especially, to our parents
for their support. We want to thank our institution for giving us the
permission to commence this project in the first instance.

We are deeply indebted to our guide Mrs. S Kala, Mr Vinod B

Maniyat, Head of the Department, Mrs. Anusheebha K, Assistant
Professor whose help, stimulating suggestion and encouragement
helped us in all the time of our project work.

Finally, we would like to thank our academic coordinates for the

cooperation to complete the project.
 ABSTRACT

“Manpower management” is designed to make the existing manual system automatic

with the help of computerized equipment and full-edged computer software, fulfilling their
requirements, so that their valuable data and information can be stored for a longer period
with easy access and manipulation of the same. The required software is easily available and
easy to work with. This web application can maintain and view computerized records without
getting redundant entries. The project describes how to manage user data for good
performance and provide better services for the client.
 CONTENTS

1. INTRODUCTION
1.1 OBJECTIVE
1.2 INTRODUCTION
1.3 MODULES OF THE PROJECT
2. SOFTWARE REQUIREMENT SPECIFICATIONS
2.1 SOFTWARE REQUIREMENTS
2.2 HARDWARE REQUIREMENTS
2.3 TOOLS AND TECHNOLOGIES USED
3. SYSTEM ANALYSIS
3.1 EXISTING SYSTEM
3.2 PROPOSED SYSTEM
3.3 FEASIBILITY STUDY
3.4 FUNCTIONAL REQUIREMENTS
3.5 NON- FUNCTIONAL REQUIREMENTS
4. SYSTEM DESIGN
5. SCREEN SHOTS
6. CODING
7. TESTING
8. IMPLEMENTATION
9. CONCLUSION
10. FUTURE ENHANCEMENT
11. BIBLIOGRAPHY
 CHAPTER 1
INTRODUCTION

CHAPTER 1
 INTRODUCTION
The proposed project “Manpower Management System” has been developed to
overcome the problems faced in the practicing of manual system. This software is built to
eliminate and in some cases reduce the hardships faced by the existing system. Moreover this
system is designed for particular need of the company to carry out its operations in a smooth
and effective manner.

This web application is reduced as much as possible to avoid errors while entering
data. It also provides error message while entering invalid data. It is user-friendly as no
formal knowledge is required to use the system.

Human resource challenges are faced by every organization which has to be overcome
by the organization. Every organization has different employee and payroll management
needs. Therefore I have design exclusive Employee and payroll Management System that are
adapted to the organization’s Managerial Requirements.

1.1 MODULES
1.1.1 Admin

The Admin gets logged in by valid username and password. Admin can add new
Employee, add new Department, add new Pay Grade for the employees. Admin can set the
‘from’ and ‘to’ date worked by an employee in a department with specific pay grade. The
Admin can generate an automated monthly salary of an employee. The admin can view all
the past records of any recorded employee.
1.1.2 Employee

The employee can login by valid username and password, Employee can get all the
information about the bonus points and the employee can take leave by filling the details
providing.
1.2 ER DIAGRAM
 CHAPTER 2

PROBEM DEFINITION

CHAPTER 2
 PROBLEM DEFINITION

MANPOWER MANAGEMENT SYSTEM is a web application for managing

Employees and their payroll.

This web application is designed to reduce or avoid as much as possible manual errors
while entering data. It also provides error message while entering invalid data. It is user-
friendly as no formal knowledge is required to use the system.
 CHAPTER 3

PROJECT OBJECTIVE AND GOAL

 CHAPTER 3

PROJECT OBJECTIVE AND GOAL

3.1 GOAL OF THE PROJECT

The goal of the project is to provide efficient and flexible web application which
can be used by the company to manage employees and their payroll with no redundant
entries in the system.

3.2 PROJECT OBJECTIVE

The purpose of the project is to describe the functionality and specifications of the
design of a web application for Managing Employees and their payroll. Now with the help of
this system the admin has the information on his finger tips and can easily prepare a good
record based on their requirements.
 CHAPTER 4
SYSTEM DESIGN
5.1.1 Relational Schema
Table Definition for P_Placement
Table

Fields Name Type Size

Place_No Long 4
Place_Date Date/Time 8
BioDataNo Integer 2
RegNo Integer 2
C_Code Integer 2
JobCode Integer 2
Salary Single 4
Commission1 Single 4
Commission2 Single 4
Total Single 4
Name Text 50
Reg_No Long 4

Indexes Name Fields Unique

placeno +Place_No;+Place_Date True

Table Definition for P_Jobs Table

Fields Name Type Size

Job_Code Integer 2
Job_Name Text 50
Job_Qualification Text 50
Job_Add_Info Text 80
 Indexes Name Fields Unique
Job_code +Job_Code True

Table Definition for P_company Table

Fields Name Type Size

c_code Integer 2
c_name Text 50
c_contact Text 50
c_area Text 50
c_city Text 50
c_state Text 50
c_fax Text 20
c_email Text 50
c_phone1 Text 10
c_phone2 Text 10
c_pin Text 8
c_std Text 12
c_address Text 100

Indexes (Name Fields Unique)

c_code +c_code True

Table Definition for P_Bio_Data Table:

Fields Name Type Size
BioDataNo Long 4
BioDate Date/Time 8
Status Text 20
Under Text 20
BioName Text 50
DOB Date/Time 8
Age Byte 1
Qualification Text 20
Major Text 20
Year_Pass Text 10
University Text 50
College Text 50
Address Text 200
Area Text 50
City Text 50
Pin Text 8
Phone Text 20
E_mail Text 50
Experience Text 5
Exp_Info Text 200
Prev_Company Text 200
Designation Text 50
Current_Salary Single 4
Exp_Salary Single 4
Exp_City Text 50
Exp_Area Text 50
C_Code Integer 2
P_Salary Single 4
A_Date Date/Time 8
S_Field1 Text 50
S_Field2 Text 50
S_Field3 Text 50
Company Text 50
Placement Text 50
job_code Integer 2
BioSex Text 10
Rfee Double 8

Indexes Name Fields Unique

biodatano +BioDataNo True
Table Definition for Job_Register Table:

Fields Name Type Size

Reg_No Long 4
Reg_Date Date/Time 8
C_Code Integer 2
Job_Code Integer 2
No_of_Persons Integer 2
No_of_Placed Integer 2
Reg_Status Text 20
Expected_Date Date/Time 8
Expected_Salary Single 4
Special_Info Text 100

Indexes Name Fields Unique

regno +Reg_No True

Table Definition for P_Interview Table

Fields Name Type Size

inter_no Long 4
letter Date/Time 8
inter_date Date/Time 8
inter_time Text 50
biodatano Long 4
job_code Integer 2
c_code Integer 2
conduct Text 50
1.1.2

1.1.3 Employee

The employee can login by valid username and password, Employee can get all the
information about the bonus points and the employee can take leave by filling the details
providing.
 CHAPTER 5
SCREEN SHOTS
 CHAPTER 6
CODING

8.1) CODING STRATEGIES

Coding is a process for categorizing the data. Develop a set of
codes using both codes that you predefine and ones that emerges from
the data. Predefined codes are categories and themes that you expect
to see based on your prior knowledge. Emergent codes are those that
become apparent as we review the data. Identify these, and create a
code for each. This type of coding allows for emergence of crucial but
previously uncovered issues and connections.

@import url('https://fonts.googleapis.com/css?family=Lobster');
@import url('https://fonts.googleapis.com/css?
family=Montserrat:400,700');

body{
margin: 0px;
}

header{
background: black;
color: white;
padding: 16px 20px 6px 40px;
height: 60px;
}

header h1{
display: inline;
font-family: 'Lobster', cursive;
font-weight: 400;
 font-size: 32px;
float: left;
margin-top: 0px;
margin-right: 10px;
}

nav ul {
display: inline;
padding: 6px;
float: right;
}

nav ul li{
display: inline-block;
list-style-type: none;
color: white;
float: left;
margin-left: 12px;

nav ul li a{
color: white;
text-decoration: none;
}

nav ul ul{
display: none;
position: absolute;
}

#navli ul li ul:hovar{
visibility: visible;
display: block;
}

#navli{
font-family: 'Montserrat', sans-serif;
}

.homered{
background-color: red;
padding: 30px 10px 22px 10px;
}

.divider{
background-color: red;
height: 5px;
}

.homeblack:hover{
background-color: blue;
padding: 30px 20px 18px 10px;

/*
=================================================
=========================
#FONT
================================================
========================== */
.font-robo {
font-family: "Roboto", "Arial", "Helvetica Neue", sans-serif;
}
/*
=================================================
=========================
#GRID
================================================
========================== */
.row {
display: -webkit-box;
display: -webkit-flex;
display: -moz-box;
display: -ms-flexbox;
display: flex;
-webkit-flex-wrap: wrap;
-ms-flex-wrap: wrap;
flex-wrap: wrap;
}

.row-space {
-webkit-box-pack: justify;
-webkit-justify-content: space-between;
-moz-box-pack: justify;
-ms-flex-pack: justify;
justify-content: space-between;
}
.col-2 {
width: -webkit-calc((100% - 60px) / 2);
width: -moz-calc((100% - 60px) / 2);
width: calc((100% - 60px) / 2);
}

@media (max-width: 767px) {

.col-2 {
width: 100%;
}
}

/*
=================================================
=========================
#BOX-SIZING
================================================
========================== */
/**
* More sensible default box-sizing:
* css-tricks.com/inheriting-box-sizing-probably-slightly-better-
best-practice
*/
html {
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
 box-sizing: border-box;
}

*{
padding: 0;
margin: 0;
}

*, *:before, *:after {
-webkit-box-sizing: inherit;
-moz-box-sizing: inherit;
box-sizing: inherit;
}

/*
=================================================
=========================
#RESET
================================================
========================== */
/**
* A very simple reset that sits on top of Normalize.css.
*/
/*body,*/
h2, h3, h4, h5, h6,
blockquote, p, pre,
dl, dd, ol, ul,
figure,
hr,
fieldset, legend {
margin: 0;
padding: 0;
}

/**
* Remove trailing margins from nested lists.
*/
li > ol,
li > ul {
margin-bottom: 0;
}

/**
* Remove default table spacing.
*/
table {
border-collapse: collapse;
border-spacing: 0;
}
/**
* 1. Reset Chrome and Firefox behaviour which sets a `min-
width: min-content;`
* on fieldsets.
*/
fieldset {
min-width: 0;
/* [1] */
border: 0;
}

button {
outline: none;
background: none;
border: none;
}

/*
=================================================
=========================
#PAGE WRAPPER
================================================
========================== */
.page-wrapper {
min-height: 100vh;
}

/*body {
font-family: "Roboto", "Arial", "Helvetica Neue", sans-serif;
font-weight: 400;
font-size: 14px;
}*/

h1, h2, h3, h4, h5, h6 {

font-weight: 400;
}

h1 {
font-size: 36px;
}

h2 {
font-size: 30px;
}

h3 {
font-size: 24px;
}
h4 {
font-size: 18px;
}

h5 {
font-size: 15px;
}

h6 {
font-size: 13px;
}

/*
=================================================
=========================
#BACKGROUND
================================================
========================== */
.bg-blue {
background: #F8F9F9;
}

/*
=================================================
=========================
#SPACING
 ================================================
========================== */
.p-t-100 {
padding-top: 100px;
}

.p-t-20 {
padding-top: 20px;
}

.p-b-100 {
padding-bottom: 100px;
}

/*
=================================================
=========================
#WRAPPER
================================================
========================== */
.wrapper {
margin: 0 auto;
}

.wrapper--w680 {
max-width: 680px;
}

/*
=================================================
=========================
#BUTTON
================================================
========================== */
.btn {
line-height: 40px;
display: inline-block;
padding: 0 25px;
cursor: pointer;
font-family: "Roboto", "Arial", "Helvetica Neue", sans-serif;
color: #fff;
-webkit-transition: all 0.4s ease;
-o-transition: all 0.4s ease;
-moz-transition: all 0.4s ease;
transition: all 0.4s ease;
font-size: 14px;
font-weight: 700;
}

.btn--radius {
-webkit-border-radius: 3px;
 -moz-border-radius: 3px;
border-radius: 3px;
}

.btn--green {
background: #57b846;
}

.btn--green:hover {
background: #4dae3c;
}

/*
=================================================
=========================
#DATE PICKER
================================================
========================== */
td.active {
background-color: #2c6ed5;
}

input[type="date" i] {
padding: 14px;
}
.table-condensed td, .table-condensed th {
font-size: 14px;
font-family: "Roboto", "Arial", "Helvetica Neue", sans-serif;
font-weight: 400;
}

.daterangepicker td {
width: 40px;
height: 30px;
}

.daterangepicker {
border: none;
-webkit-box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
-moz-box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
display: none;
border: 1px solid #e0e0e0;
margin-top: 5px;
}

.daterangepicker::after, .daterangepicker::before {
display: none;
}

.daterangepicker thead tr th {
padding: 10px 0;
}

.daterangepicker .table-condensed th select {

border: 1px solid #ccc;
-webkit-border-radius: 3px;
-moz-border-radius: 3px;
border-radius: 3px;
font-size: 14px;
padding: 5px;
outline: none;
}

/*
=================================================
=========================
#FORM
================================================
========================== */
input {
outline: none;
margin: 0;
 border: none;
-webkit-box-shadow: none;
-moz-box-shadow: none;
box-shadow: none;
width: 100%;
font-size: 14px;
font-family: inherit;
}

.input-group {
position: relative;
margin-bottom: 30px;
border-bottom: 2px solid #ccc;
}

.input-icon {
position: absolute;
font-size: 18px;
color: #ccc;
right: 8px;
top: 50%;
-webkit-transform: translateY(-50%);
-moz-transform: translateY(-50%);
-ms-transform: translateY(-50%);
 -o-transform: translateY(-50%);
transform: translateY(-50%);
cursor: pointer;
}

.input--style-1 {
padding: 9px 0;
color: #666;
}

.input--style-1::-webkit-input-placeholder {
/* WebKit, Blink, Edge */
color: #555;
}

.input--style-1:-moz-placeholder {
/* Mozilla Firefox 4 to 18 */
color: #555;
opacity: 1;
}

.input--style-1::-moz-placeholder {
/* Mozilla Firefox 19+ */
color: #555;
 opacity: 1;
}

.input--style-1:-ms-input-placeholder {
/* Internet Explorer 10-11 */
color: #555;
}

.input--style-1:-ms-input-placeholder {
/* Microsoft Edge */
color: #555;
}

/*
=================================================
=========================
#SELECT2
================================================
========================== */
.select--no-search .select2-search {
display: none !important;
}

.rs-select2 .select2-container {
width: 100% !important;
 outline: none;
}

.rs-select2 .select2-container .select2-selection--single {

outline: none;
border: none;
height: 34px;
}

.rs-select2 .select2-container .select2-selection--single .select2-

selection__rendered {
line-height: 34px;
padding-left: 0;
color: #555;
}

.rs-select2 .select2-container .select2-selection--single .select2-

selection__arrow {
height: 32px;
right: 4px;
display: -webkit-box;
display: -webkit-flex;
display: -moz-box;
display: -ms-flexbox;
display: flex;
 -webkit-box-pack: center;
-webkit-justify-content: center;
-moz-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
-webkit-box-align: center;
-webkit-align-items: center;
-moz-box-align: center;
-ms-flex-align: center;
align-items: center;
}

.rs-select2 .select2-container .select2-selection--single .select2-

selection__arrow b {
display: none;
}

.rs-select2 .select2-container .select2-selection--single .select2-

selection__arrow:after {
font-family: "Material-Design-Iconic-Font";
content: '\f2f9';
font-size: 18px;
color: #ccc;
-webkit-transition: all 0.4s ease;
-o-transition: all 0.4s ease;
 -moz-transition: all 0.4s ease;
transition: all 0.4s ease;
}

.rs-select2 .select2-container.select2-container--open .select2-

selection--single .select2-selection__arrow::after {
-webkit-transform: rotate(-180deg);
-moz-transform: rotate(-180deg);
-ms-transform: rotate(-180deg);
-o-transform: rotate(-180deg);
transform: rotate(-180deg);
}

.select2-container--open .select2-dropdown--below {
border: none;
-webkit-border-radius: 3px;
-moz-border-radius: 3px;
border-radius: 3px;
-webkit-box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
-moz-box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
border: 1px solid #e0e0e0;
margin-top: 5px;
overflow: hidden;
}
/*
=================================================
=========================
#TITLE
================================================
========================== */
.title {
margin-bottom: 37px;
}

/*
=================================================
=========================
#CARD
================================================
========================== */
.card {
overflow: hidden;
-webkit-border-radius: 3px;
-moz-border-radius: 3px;
border-radius: 3px;
background: #fff;
}

.card-1 {
-webkit-box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
 -moz-box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
box-shadow: 0px 8px 20px 0px rgba(0, 0, 0, 0.15);
}

/*.card-1 .card-heading {
background: url("../images/bg-head-02.jpg") center center/cover
no-repeat;
padding-top: 210px;
}*/

.card-1 .card-body {
padding: 0 90px;
padding-top: 55px;
padding-bottom: 65px;
}

@media (max-width: 767px) {

.card-1 .card-body {
padding: 0 40px;
padding-top: 40px;
padding-bottom: 40px;
}
}
 CHAPTER 7
TESTING

System testing is actually a series of different tests whose primary purpose is to fully exercise
the computer-based system. Although each test has a different purpose, all work to verify that
all the system elements have been properly integrated and perform allocated functions. The
testing process is actually carried out to make sure that the product exactly does the same
thing what is supposed to do. Testing is the final verification and validation activity within
the organization itself. In the testing stage following goals are tried to achieve:-

 To affirm the quality of the project.

 To find and eliminate any residue errors from previous stages.
 To validate the software as a solution to the original problem.
 To provide operational reliability of the system.

During testing the major activities are concentrated on the examination and modification of
the source code.

7.1) Unit Testing

Here each module that comprises the overall system is tested individually. Unit testing

focuses verification efforts even in the smallest unit of software design in each module. This

is also known as “Module Testing”. The modules of the system are tested separately. This

testing is carried out in the programming style itself. Unit testing exercise specific paths in a

module’s control structure to ensure complete coverage and maximum error detection. This

test focuses on each module individually, ensuring that it functions properly as a unit. Hence,

the naming is Unit Testing. In this step each module is found to work satisfactorily as regard

to the expected output from the module. This testing is done to check for the individual block

codes for their working. It is done so that when we carry out functional testing then the units

which are part of these functionalities should have been tested for working.

7.2) Integration
After successful completion of unit testing or module testing, individual functions are
integrated into classes. Again integration of different classes takes into place and finally
integration of front-end with back-end occurs.

 Integration of functions into classes

At the start of coding phase only the functions required in different parts of the
program are developed. Each of the functions is coded and tested independently. After
verification of correctness of the different, they are integrated into their respective
classes.

 Integration of different classes

Here the different classes are tested independently for their functionality. After
verification of correctness of outputs after testing each class, they are integrated
together and tested again.

 Integration of front-end with back-end

The front-end of the project provides an environment called the IDE (Integrated
Development Environment) that provides a platform for visual programming. With
the user diversion towards graphical user interfaces, computer programming
languages are also changing. Visual Basic is graphical user interface programming
language which has a bulk of inbuilt user friendly tools for understanding
programming language concepts. The back-end code is then integrated and tested.

7.3) Integration Testing

Data can be lost across interface. One module can have an adverse effect on
another. Sub functions when combined, should not reduce the desired major function.
Integration testing is a systematic technique for constructing the program structure. It
addresses the issues the associated with the dual problems for verification and
program construction. The main objective in this testing process is to take unit tested
modules and build a program structure that has been dictated by design. After the
software has been integrated, a set of high order tests are conducted. All the modules
are combined and tested as a whole. Here correction is difficult, because the isolation
of errors is complicated by the vast expense of the entire program.
7.4) Top down Integration

This method is an incremental approach to the construction of program structure. Modules

are integrated by moving downward, beginning with the main program module. Modules that
subordinate to the main program module are incorporated into the structure in either a depth
first or breadth first manner.

7.5) Bottom-up Integration

This method begins the construction and testing with the modules at the lowest level in
the program structure. Since the modules are integrated from bottom to up, processing
required for modules subordinate to a given level is always available. Therefore in this case
the need for stubs is eliminated. The following integration testing table shows the functions
that were combined into different classes and the class as a whole tested for its functionality.
This is important to check for error-free interaction between various classes, and maintenance
of data integrity.

7.6) Validation Testing

At the culmination of integration testing, software is completed and assembled as a package.

Interfacing errors are uncovered and corrected. Validation testing can be defined in many
ways. Here the testing validates the software function in a manner that is reasonably expected
by the customer.

7.7) Output Testing

After performing the validation testing, the next step is output testing of the proposed
system, since no system could be useful if it does not produce the required output in the
specified format. Therefore the output testing involves first of all asking the users about the
format required by them and then to test the output generated or displayed by the system
under consideration. The output format is considered in two ways:-

(1) On screen
(2) Printed format
7.8) User Acceptance Testing

User Acceptance of a system is the key factor to the success of any system.
Performance of an acceptance test is actually the user’s show. User motivation and
knowledge are critical for the successful performance of the system.
The system under consideration is tested for user acceptance by constantly in touch
with the prospective system users at time of developing and making changes wherever
required in regard to the following point:

 Input Screen design

 Output Screen design
 Menu driven system

7.9) White box testing

White box testing (clear box testing, glass box testing, and transparent box testing or
structural testing) uses an internal perspective of the system to design test cases based on
internal structure. It requires programming skills to identify all paths through the software.
The tester chooses test case inputs to exercise paths through the code and determines the
appropriate outputs. While white box testing is applicable at the unit, integration and system
levels of the software testing process, it is typically applied to the unit.

Though this method of test design can uncover an overwhelming number of test cases, it
might not detect unimplemented parts of the specification or missing requirements, but one
can be sure that all paths through the test object are executed. Using white box testing we can
drive test cases that:
 Guarantee that all independent paths within a module have been exercised at least
once.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds.
 Execute internal data structure to assure their validity.

7.10) Black box testing

Black box testing focuses on the functional requirements of the software. It is also
known as functional testing. It is a software testing technique whereby the internal workings
of the item being tested are not known by the tester. For example, in a black box testing on
software design the tester only knows the inputs and what the expected outcomes be and not
how the program arrives at those outputs.
 The tester does not ever examine the programming code and does not need any further
knowledge of the program other than its specifications. It enables us to derive sets of input
conditions that will fully exercise all functional requirements for a program. Black box
testing is an alternative to white box technique. Rather it is a complementary approach that is
likely to uncover a different class of errors in the following categories:-

 Incorrect or missing function

 Interface errors

 Performance errors

 Initialization and termination errors

 Errors in objects

7.11) Advantages

 The test is unbiased as the designer and the tester are independent of each other.
 The tester does not need knowledge of any specific programming languages.
 The test is done from the point of view of the user, not the designer.
 Test cases can be designed as soon as the specifications are complete.

7.12) Preparation of Test Data

Preparation of test data plays a vital role in the system testing. After preparing the test
data, the system under study is tested using that test data. While testing the system by using
test data, errors are again uncovered and corrected by using above testing steps and
corrections are also noted for future use.

7.13) Using Live Test Data

Live test data are those that are actually extracted from organisation files. After a
system is partially constructed, programmers or analysts often ask users to suggest data for
test form their normal activities.
It is difficult to obtain live data in sufficient amounts to conduct extensive testing and
although the realistic data that will show how the system will perform for the typical
processing requirement. Assuming that the live data entered are in fact typical; such data
generally will not test all combinations or formats that can enter the system.

7.14) Using Artificial Test Data

Artificial test data are created solely for test purpose, since they can be generated to
test all combinations of formats and values. In other words, the artificial data, which can
quickly be prepared by a generating utility program in the information systems department,
make possible the testing of all login and control paths through the program.

The most effective test programs use artificial test data generated by persons other
than those who wrote the programs. Often, an independent team of testers formulates a
testing paln, using the systems specifications.

7.15) Quality Assurance

Quality assurance consists of the auditing and reporting functions of management.

The goal of quality assurance is to provide management with the data necessary to be
informed about product quality, thereby gaining insight and confident that the product quality
is meeting its goals. That is an umbrella activity” that is applied throughout the engineering
process. Software quality assurance encompasses:-

 Analysis, design, coding and testing methods and tools

 Formal technical reviews that are applied during each software engineering
 Multithread testing strategy
 Control of software documentation and the change made to it.
 A procedure to ensure compliance with software development standards
 Measurements and reporting mechanisms
7.16) Quality Factors

An important objective of quality assurance is to track the software quality and assess the
impact of methodology and procedure changes on improved software quality. The factors that
affect the quality can be categorized into two broad groups:

 Factors that can be directly measured

 Factors that can be indirectly measured

These factors focus on three important aspects of a software products

 Its operational characteristics

 Its ability to undergo changes
 Its adaptabilities to a new environment
 Effectiveness or efficiency in performing its mission
 Duration of its use by its customer.

7.17) Generic Risks

A risk is an unwanted event that has negative consequences. We can distinguish risks
from other project events by looking for three things:

 A loss associated with the event

 The likelihood that the event will occur
 The degree to which we can change the outcome
 The generic risks such as the product size risk, business impact risks, customer-related
risks, process risks, technology risks, development environment risks, security risks etc.
this project is developed by considering all these important issues.

7.18) Security Technologies & Policies

The software quality assurance is comprised of a variety of tasks associated with

seven major activities:-

 Application of technical methods

 Conduct of formal technical reviews
 Software testing
 Enforcement of standards
 Control of change
 Measurement
 Record keeping and reporting
 MANUAL SYSTEM

Some demerits of the manual system are as follows

1. There is a delay in issuing the information while handling manually.

2. The valuable information is not accurate.
3. There is a lack of centralized information.
4. The time consumption is more while doing manually.
5. While doing manually the manipulation is difficult.
6. It is difficult for the organization to maintain voluminous database manually.
7.Communication gap exists because of the absence of centralized communication
networks.
To overcome all these difficulties, each and every organization go for Computerization.

COMPUTERISED SYSTEM

Some of the merits are:

1. It provides all information about cars and its dealers instantaneously.

2. It saves time of the people working in this organization. They can free from the
monotonous manual work.
3. Huge heap of paper documents can be avoided. So no need to maintain those
records.
4. It enhance the efficiency of the organization.
5. Data security is provided, by using password protection.
6. Interview Letter Automatically generating.
7.Update the last rate and details of the Placements, Job Register and Candidate
Register can be done easily.
 CHAPTER 8
IMPLEMENTATION
 Implementation is the stage in the project where the theoretical design is turned into a
working system and is giving confidence on the new system for the users that it will work
efficiently and effectively. It involves careful planning, investigation of the current system
and its constraints on implementation, design of methods to achieve the changeover, an
evaluation, of change over methods. The more complex system being implemented, the more
involved will be the system analysis and the design effort required just for implementation.

The implementations process begins with preparing a plan for the implementation of the
system. According to this plan, the activities are to be carried out, discussions are made
regarding the equipment and resources and the additional equipment has to be acquired to
implement the new system.

Implementation is the first and important phase. This is the most critical stage in achieving a
successful new system and in giving the users confidence that the new system will work is
effective. The system can be implemented only after thorough testing. This method also
offers the greatest security since the old system can take over if the errors are found or
inability to handle certain type of transactions while using the new system.
CHAPTER 9
CONCLUSION
The design document of the project naming “Placement Cell Management System” is an
efficient way of solving all the required function. We have such beneficial document that can
help us wherever we need it and it is a long term project sustaining the reliability and can be
maintained easily without any efforts. The testing cases applied during the implementation
are too less in amount and number, beside this, the debugging of the reported steps are too
easy.

The one of the wide feature of the designed project is that its maintenance either it is
perfective, adaptive or the corrective are suitable for any environment.

Our project is only a humble venture to satisfy the needs to manage their project
work. Several user friendly coding have also adopted. This package shall prove to be a
powerful package in satisfying all the requirements of the school. The objective of software
planning is to provide a frame work that enables the manager to make reasonable estimates
made within a limited time frame at the beginning of the software project and should be
updated regularly as the project progresses.
 CHAPTER 10
FUTURE ENHANCEMENT
Though our project is itself matured enough but still betterment is always an open door. In
this case also we can add some features to this software to make this software more reliable.

Information Technology Changes Everything. It has changed the way people live and work
and it will continue to revolution the way organization run their business. Virtually every
organization-large and small is in great position to take advantages of relational data base
management systems and secure exchange of information. This project has the features of
flexible modelling, methodology, support, is a application developed with Microsoft Visual
Basic 6.0, My SQL. More functionality can be added in this project by using Visual
Basic.Net 2008 as front end and Microsoft Access 2003 server as back end. By using both
these tools, more rich features can be added to our project which can make this project more
easier to use and more user friendly.

These are as follows:-

- Firstly, during the development of the project my prime object was to keep the
hardware & software requirement as minimum as possible so that it supports
maximum user base.
- Secondly, the searching procedure should be very strong like placement officer can search
student as fast as possible.
- Thirdly, modify the project with better approach with more graphics.
- Fourthly, the back-up procedure can be incorporated this application and communicate with
placement officer.
- Sixthly, placement officer can contact with both student and company through message.
Student and company can also send message to placement officer.
 CHAPTER 11
BIBLIOGRAPHY
 BIBLIOGRAPHY

 Oreilly by Robin Nikon

REFERENCES
- http://www.google.co.in

- http://www.wikipedia.com

- www.PHP Array-w3schools.com

- http://www.totorialspoint.com/mysql/

- Google for problem solving

- https://windows.php.net/download/

- http://docs.microsoft.com/fr

- http://www.codelobster.com/php_editing.html

- Reference
THANK YOU