6.

IMPLEMENTATION
The implementation is the final and important phase. It
involves User training, system testing and successful running of
the developed system. The users test the developed system
when changes are made according to the needs. The testing
phase involves the testing of the developed system using
various kinds of data. An elaborate testing of data is prepared
and system is tested using the tests data. Implementation is the
stage where theoretical design turned into a working system.
Implementation is planed carefully to propose system to avoid
unanticipated problems. Many preparations involved before
and during the implementation of proposed system. The
system needed to be plugged in to the organizations network
then it could be accessed from anywhere, after a user logins
into the portal. The tasks that had to be done to implement the
system were to create the database tables in the organization
database domain. Then the administrator was granted his role
so that the system could be accessed. The next phase in the
implementation was to educate the system. A demonstration
of all the functions that can be carried out by the system was
given to examination department person, who will make
extensive use of the system.
6.1 TESTING
Testing strategy
A test strategy is an outline that describes the testing approach
of the software development cycle. This includes the testing
objective, methods of testing new functions, total time and
resources required for the project, and the testing
environment. Design documents describe the functionality of
the software to be enabled in the upcoming release.

Software testing can be stated as the process of validating and

verifying that a software program/application/product:
1) Meets the requirements that guided its design and
development:
2) Works as expected and
Software testing, depending on the testing method employed
can be implemented at any time in the development process.
However, most of the test effort traditionally occurs after the
requirements have been defined and the coding process has
been completed. Although in the agile approaches most of the
test effort is, conversely, on-going. As such, the methodology of
the test is governed by the software development methodology
adopted.
Different software development models will focus the test
effort at different points in the development process. Newer
development models, such as agile, often employ test driven
development and place an increased portion of the testing in
the hands of the developer, before it reaches a formal team of
testers. In a more traditional model, most of the test execution
occurs after the requirements have been defined and the
coding process has been completed.
The following are the testing methodologies :
System testing
Unit testing
Module testing
Integration testing

6.1 System Testing

The testing phase involves the testing of the developed system
using various kinds of data. An elaborated testing of data is
prepared and a system is tested using the test data. While
testing, errors are noted and corrections remade, the
corrections are also noted for future use. It includes a vast
variety of test put together to develop an active application
which can be used under varied stress and load situation. The
GUI is also tested with performance and error handling testing.
6.2 Unit Testing
 Testing is a set of activities that can be planned in advance and
conducted systematically. The proposed system is tested in
parallel with the software that consists of its own phases of
analysis, implementation, testing and maintenance. Following
are the tests conducted on the system. During the
implementation of the system each module of the system was
tested separately to uncover errors within its boundaries. User
interface was used as a guide in the process. Unit testing may
reduce uncertainty in the units themselves and can be used in a
bottom-up testing style approach. By testing the parts of a
program first and then testing the sum of its parts, integration
testing becomes much easier.
6.3 Module Testing
A module is composed of various programs related to that
module. Module testing is done to check the module
functionality and interaction between units within a module. It
checks the functionality of each program with relation to other
programs within the same module. It then tests the overall
functionality of each module. Modules being the integral part
of the system have to interact with each other efficiently and
without errors, because error here would bring the complete
system to a stand still. The server would run out of responses
thus causing a massive system crash.
6.4 Integration Testing
 The purpose of integration testing is to verify functional,
performance, and reliability requirements placed on major
design items. Integration testing is a systematic technique for
constructing the program structure while conducting tests to
uncover errors associated with interfacing. The objective is to
take unit-tested module and build a program structure that has
been dictated by design. Test cases are constructed to test that
all components within assemblages interact correctly, for
example across procedure calls or process activations, and this
is done after testing individual modules, i.e. unit testing. The
overall idea is a "building block" approach, in which verified
assemblages are added to a verified base which is then used to
support the integration testing of further assemblages.
4.7 Database Description
Database Database Description
Name
Admin This stores the various attributes like admin
user id, username, password, type and email
addresses of all the admin users.
category This saves the attributes of categories of
products featured on the companys web page
as category id, name, rank , status.
Content This saves the attributes of content of pages
namely Home, About us and Contact us like
content id, title, meta_title , meta_keyword,
type, link, description.
Department This saves the attributes like id, name, meta
title, meta keyword, meta description and
description of various aspx pages linked on the
mainframe of the website.
Experience This saves the options presented for the
experience field to be filled by the applicant on
the web page for job application form.
Jobapplication This saves the data presented by all the
applicants belonging to various fields on the job
application form like first name, last name,
email address, phone number, age, gender,
address, qualification, experience and current
 salary.
Menu This saves the attributes of various links on the
control panel of the administrator side like the
link name, linked aspx page, parent id and rank.
Product This saves the attributes of various products in
different categories and their descriptions.
qualification This saves the options presented for the
qualifications field to be filled by the applicant
on the web page for job application form.

Tables used

Data Flow Diagrams

DFD level 0
DFD level 1
DFD level 2
CLASS diagrams
4.6Sequence Diagrams
Sequence Diagram 1
Sequence name: creation and storage of profile at applicant user
information module.

Sequence description:shows the sequential interaction of

various processes while the creation and updating of applicant
profile from the front end of the site.

Sequence Diagram 2
Sequence name : searching, short listing, viewing and
recruitment of applicant from admin user module

Sequence description:
: shows the sequential interaction of various processes while
the applicants are searched from the database, shortlisted,
their profiles are viewed and resumes downloaded for
recruitment
Modules:
Module description
We have developed four modules to finally get to the main
working site. These four modules work in an integrated
environment to give the end used, administrator exactly what
he has fired as query.
User module
Applicant information module
Administration module
Application management module.

User Module
This is the basic structure of the website containing all the
necessaryinformation about the company. This has multiple
links to othermodules which have been created in order to
facilitate the user andthe administrator.
Applicant Information Module
This is the module designed to update the database. Here
theapplicants submit all their professional and personal details
regardingthe job or internship they seek.This module saves the
details in a specified format so that thedatabase is updated in
an analogous way for every applicant. All thedata entered by
the applicant is arranged in tables and can beretrieved as and
when required by the administrator.It also has been
incorporated to pay the applicant fees online usingthe
applicant information forms.This information module makes a
pool of applicant available all the time for the HR department
of thecompany making it extremely viable for the heads to cling
on towhenever there is a need or vacancy.
Administrative Module
This module is the control panel of the whole site. The
administrator haspower rights like update, delete, view, restrict
other administratorpowers to access the data.This module
manages other module which is used for dynamic updatesof
the site, changes to be offered in the site etc.Administrator can
access applicants profile any time, can shortlistvarious
applicants according to required need using the
appropriatesearch filters. This module also has been
incorporated with feature toretrieve, download and save the
resume files from the database
Application Management Module
This is the module which comes into picture during the
finalizationprocess of the application. Who to call for interview, selected
candidateto be marked as employed candidate of the company,
restoring theinformation of the applicant in a separate database for
future reference.This module specially acts as a catalyst to the final
process of recruitment or internship in the company.