aisu
aisu
MINI PROJECT
Submitted by:
AISWARYA PRASAD
Reg No:220021026176
OCTOBER-2024
Campus Placement Recruitment System
MINI PROJECT
Submitted by:
AISWARYA PRASAD
Reg No:220021026176
OCTOBER-2024
ST. THOMAS COLLEGE
KOZHENCHERRY, PATHANAMTHITTA, KERALA-689641
(Affiliated to Mahatma Gandhi University, Kottayam)
BONAFIDE CERTIFICATE
This is to certify that the project work titled “CAMPUS PLACEMENT RECRUITMENT
SYSTEM” done by AISWARYA PRASAD [Register No:220021026176] is submitted in
partial fulfilment of the requirement for the degree of BSc. Computer Science, awarded
by Mahatma Gandhi University, and has been carried out under our supervision.
External Examiner
ACKNOWLEDGEMENT
I thank God almighty for guiding me throughout the Mini-Project. I would like to thank
all those who have contributed to the completion of the Mini-Project and helped me with
valuable suggestions for improvement.
I express my deep-felt gratitude to Dr. George K. Alex, Principal of St. Thomas College,
Kozhencherry for his warm support with regard to the work and to the management for
providing the facilities required.
I would like to place my deep sense of gratitude to my Mini-Project guide Mr. Anup
George Varghese, Head of the Department, B.Sc. Computer Science, St. Thomas College,
Kozhencherry for his sincere guidance and his help during the project work.
I am sincerely thankful to Mrs. Grace Mathew, Lecturer in B.Sc. Computer Science for
her valuable suggestions.
I also thank to all the teachers Ms. Jinsa Joy, Mrs. Parvathy Unnikrishnan,
Mrs.Deepamol K.S, Mr. Abin Geo Samuel and all other staff members in my department
who helped me directly or indirectly.
Furthermore, I would like to thank all others especially my parents and friends. This
project report would not have been a success without their valuable suggestions and moral
support from them throughout the mini-project
Campus Placement Project Report
Abstract
solution designed to streamline and enhance the process of campus placements for educational
institutions and students alike. This innovative system offers a feature-rich platform that
connects students, educational institutions, and potential employers, creating a seamless and
The proposed system enables students to search for upcoming placement opportunities, apply
for positions that match their qualifications and interests, and conveniently view the results of
placement processes. Additionally, even after graduating, students can access and review
placement details, providing ongoing career support. This platform not only simplifies
placement processes but also fosters transparency, accessibility, and improved communication
CONTENTS
1. INTRODUCTION……………………………………………………1
1.1 INTRODUCTION………………………………………………….2
2. REQUIREMENT ANALYSIS……………………………………….6
3. SYSTEM DESIGN……………………………………………………21
3.1 INTRODUCTION…………………………………………………...22
3.2 INPUT DESIGN……………………………………………………..23
3.3 OUTPUT DESIGN…………………………………………………..23
3.4 DATA FLOW DIAGRAM…………………………………………...24
3.5 DATABASE TABLES……………………………………………….28
4. SYSTEM TESTING…………………………………………………..30
5. SYSTEM IMPLEMENTATION……………………………………...39
6. FUTURE SCOPE………………………………………………………44
7. CONCLUSION..………………………………………………………..46
8. SOURCE CODE………………………………………………………..48
9. SCREEN SHOTS……………………………………………………….59
10. BIBLIOGRAPHY……………………………………………………...66
LIST OF TABLES
Placement...................................................................................................28
Registers.....................................................................................................28
Staff............................................................................................................29
Student………............................................................................................29
LIST OF FIGURES
LEVEL0.......................................................................................................25
LEVEL1.......................................................................................................25
LEVEL1.1....................................................................................................26
LEVEL1.2....................................................................................................26
LEVEL1.3....................................................................................................27
Chapter1:Introduction
1.1 INTRODUCTION
The online campus placement recruitment system is a platform between job seeker(student
and job provider(placement staff). The Student or Job seeker can easily find and apply for
job by login into system. The Employer or company can easily get expert employee from
our job portal site by posting a job. The job portal website is a common place between job
seeker and company. When job seeker can login in his account then he can get notification
of company lists which match with his profile or education detail. So job seeker can easily
apply to this job and he can also send message to company for other inquiry. When
company login in account, company or employer can get alert of job seeker lists which
match with all criteria for posted job
System Modules
Admin
• Login
• Create Student
• View Student Details
• Approve Student Details
• Manage Placement Login
Placement Staff
• Login
• Create Placement
• Update/Delete Placement
• Update Placement Results
• Manage News
User
• Register
• Login
• Search Placement
• Apply Placement
• View Placement Results
• My Profile
Module Description
Admin:
1. Login:
o Admins can securely log in to the admin panel to access their administrative
functions and manage the placement system.
2. Create Student:
o Admins can create student profiles, inputting their essential details into the
system.
3. View Student Details:
o Admins can access and view detailed student profiles, facilitating management
and support.
4. Approve Student Details:
o Admins review and approve student profiles, ensuring the accuracy and
legitimacy of the information.
5. Manage Placement Login:
o Admins can manage and provide access credentials to placement staff, enabling
them to administer placement activities.
Placement Staff:
1. Login:
o Placement staff members can securely log in to access the placement
management features.
2. Create Placement:
o Placement staff can create placement opportunities, including job postings with
detailed information about positions, requirements, and deadlines.
3. Update/Delete Placement:
o Placement staff can edit or remove placement opportunities as needed to keep
information accurate and up-to-date.
4. Update Placement Results:
o Placement staff can update and manage placement results, providing
transparency and timely feedback to students.
5. Update New:
o Placement staff can update and manage news updates providing information
and timely update to students about placements
User:
1.Register:
2.1 INTRODUCTION
System Study is a general term that refers to an orderly, structured process for
identifying and solving problems. We call system Study process lifecycle methodology,
since it relates to four significant phases in the lifecycle of all business information system.
The system is studied to the minute details and analyzed.
Analysis implies the process of breaking something into parts so that the whole
may be understood. The definition of the system analysis includes not only the process of
analysis but also that of synthesis, which implies the process of putting together to form a
new whole.
All activities associated with each life cycle phase must be performed, managed
and documented. Hence, we define system analysis as the performance, management,
documentation of the activities related to the life cycle phases of a computer- based
business system. In the study phase a detailed study of the project is made and clear picture
of the project is in mind. In the design phase the designing of the input, output and table
designs are made. Development phase is where the physical designing of the input- output
screens and coding of the system is done. System implementation actually implements the
system by making necessary testing.
The existing campus placement system at many educational institutions often faces several
challenges:
1. Manual Process:
o The placement process is often manual and paper-based, involving physical
job postings, application forms, and notices on bulletin boards.
2. Limited Information Accessibility:
o Students have limited access to comprehensive information about upcoming
placement opportunities, including job descriptions, company details, and
eligibility criteria.
The proposed "Campus Placement Recruitment System" aims to address these challenges
and introduce a more efficient and user-friendly platform:
1. Digital Platform:
o The proposed system will be entirely digital, providing an online platform
accessible to administrators, placement staff, and students.
2. Comprehensive Placement Information:
o The system will offer detailed information about placement opportunities,
including job descriptions, company profiles, application deadlines, and
eligibility criteria.
3. Online Application Process:
o Students can apply for placements online through the system, eliminating the
need for physical forms and streamlining the application process.
4. Real-time Updates:
o The platform will provide real-time updates on placement activities, including
interview schedules, shortlisted candidates, and results.
5. User Profiles:
o Users (students) can create and manage profiles, which store their academic
records, resumes, and preferences to streamline the application process.
Technical Feasibility:
There are a number of technical issues, which are generally raised during the feasibility
stage of the investigation. A study of function, performance and constraints gave me the
ability to achieve acceptable system. The software required for this system is:
PHP
MY SQL
Financial Feasibility:
The analysis raises financial and economic questions during the preliminary
investigation to estimate the following:
The cost to conduct a full systems investigation.
The cost of hardware and software for the class of application of the
project being considered.
To be judged feasible, a proposal for the specific project must pass all these tests, otherwise
it is not considered as a feasible project. I gathered the details regarding the financial
aspects incorporated in the system to make it cost efficient.
Operational Feasibility
Suppose for a moment that technical and economic resources are both judged
adequate. The systems analyst must still consider the operational feasibility of the
requested project. Operational feasibility is dependent on human resources available for
the project and involves projecting whether the system will operate and be used once it is
installed. If users are virtually led to the present system, see no problems with it, and
generally are not involved in requesting a new system, resistance to implementing the new
system will be strong. Chances for it ever becoming operational are low.
Requirement analysis involves studying the current system to find out how it
works and where improvements could be made. A clear idea about the existing system is a
must for making improvements where it is required. Proper planning and collection of data
serves the purpose. The popularity of this document is to describe all the requirements for
the popularity of the website DreamCareer .This website gives all the information related
to casting call. In our busy life, we cannot go to each department or offices. This problem
will manage this site. It will help to avoid in correction and missing data.
Software Requirements:
PHP is a server scripting language, and is a powerful tool for making dynamic and
interactive Web pages quickly , PHP is a widely-used, free, and efficient alternative to
competitors such as Microsoft's ASP. PHP is used to interact with the MySQL database
and to generate dynamic web pages. The original release of PHP was designed and created
by Rasmus Lerdorf back in the middle of the 90s as a way of making various common
web tasks easier and less repetitive. Back then, the main goal was to have the minimum
amount of logic as was possible in order to achieve results, and this led to PHP being
HTML-centric - that is, PHP code was embedded inside HTML.
2.4.1 FEATURES
The first popular version of PHP was called PHP/FI 2.0, for Personal
Home Page / Form Interpreter, and, despite its parsing inconsistencies, managed to attract
a fair few converts, including myself. The main issue with this version was that the PHP/FI
parser was largely hand-written, and so users often encountered scripting errors that were
not technically errors - they were just the PHP/FI parser screwing up. Furthermore, the
parser was absolutely tied to the Apache web server, and was hardly renowned for its
speed.
and Andi Gutmans re-wrote PHP from the ground up using standard “compiler compiler"
tools like Flex and Bison. This made the parser itself all but bulletproof, which in turn
gave sanity back to many PHP users!
PHP 3 also finally made the language extensible - something that was
seriously lacking from prior versions. Particularly keen developers were able to write their
own modules for the language, adding functionality at the core level. The parser itself,
though, was still tied to Apache, and, although speed was improved a great deal from
PHP/FI, it still was not anything to shout about.
The only downside to upgrading to PHP 3 was that the language was a lot stricter -
some code that worked on PHP/FI would no longer work after upgrading. The language
was still young, though, so not many were affected.
The all-round improvement brought about by the PHP/FI to PHP 3 upgrade
brought in many new users eager to jump from the Perl ship to a system that was easier
to use. At the time, there was no doubt at all that Perl was faster to execute, except perhaps
among PHP zealots, however PHP still kept its lead in speed of development, and that
was the key selling point.
and this only added extra fuel to the fire of PHP's growth. By the time PHP 3 was replaced
in the middle of 2000, it was installed on over 2,500,000 web-site domains, as compared
to 250,000 just 18 months before.
major differences to PHP 3 in all aspects. Extensive work had been done to ensure that
backwards compatibility with older PHP scripts would remain - upgrading from PHP 3 to
PHP 4 was much smoother than the PHP/FI to PHP 3 upgrade.
Perhaps the most important change made for PHP 4 was the switch to
what is called the Zend Engine. The Zend Engine, created by Zend, a company founded
by Zeev Suraski and Andi Gutmans (the name Zend is a contraction of ZEev and aNDi)
to promote PHP in the corporate environment, allowed much more flexibility than had
ever been seen before in PHP. The engine took over the core of PHP and introduced
reference counting, whereby all resources used in scripts (database connections, files, etc)
are tracked automatically by the engine, and freed when no longer used to minimize
memory usage and ensure there were no memory leaks.
source code, interpreted it, executed it, read another, interpreted it, executed it, read
another, etc. This meant that code was often reread and re-interpreted twice or more,
entirely unnecessarily.
PHP 4, with its new "compile first, execute later" paradigm read your entire script in and
compiled it to byte code before execution, which produced a large speed increase - the
average speed increase was about 100%, with some benchmarks showing up to a fifty-fold
increase in speed when PHP 4 was pushed to its limits.
Furthermore, because PHP 4 compiled the entire script before executing it, it became
possible to optimize and cache the compiled code before execution. We will be looking at
how this works later on in the book.
Since the release, PHP has continued its advance unabated - at the time of writing, the
current version of PHP 4 is 4.3.9, and PHP is installed on 9,500,000 web servers around
the world. PHP is the most popular Apache module available, surpassing even mod_perl,
and continues to grow in popularity.
HTML Relationship
When used to output HTML content, PHP is embedded inside HTML in code islands, as
opposed to in Perl, where HTML code is embedded inside the Perl script. The most
common way to open and close PHP code blocks is by <?php and ?>. Here is an example
of a simple page, shown in Perl first then in PHP - don't worry about what the code means
for now:
#!/usr/bin/perl print
"<HTML>\n"; print
"<BODY>\n"; print
"<P>Welcome,
$Name</P>\n"; print
"</BODY>\n"; print
"</HTML>\n";
<HTML>
<BODY>
</BODY>
</HTML>
As you can see, the PHP version is only a line shorter, but infinitely much easier to read
because the majority of the page is just HTML. Some modules for Perl (particularly
CGI.pm) help, but PHP continues to have a big lead in terms of readability. If you really
wanted to, you could write your PHP script like the Perl script: switch to PHP mode and
print everything out from there. However, it tends to get messy - as you can see!
Apart from editing legibility, another advantage to having most of the page in straight
HTML is that it makes editing with commercial IDEs possible
whereas products like Dreamweaver and FrontPage trash Perl's print statements.
One key advantage to using PHP as opposed to some other solutions is that PHP code is
all executed at the server, with the client only receiving the results of the script. What this
means is that users never see your PHP source code because they are never sent it - they
only see what you want them to see.
PHP uses a blend of interpretation and compilation in order to provide the best mix of
performance and flexibility to programmers.
Behind the scenes, PHP compiles your script down to a series of instructions (called
opcodes) whenever it is accessed. These instructions are then executed one by one until
the script terminates. This is different from conventional compiled languages such as C++
where the code is compiled down to native executable code then that executable is run
from then on. Instead, PHP re-compiles your script each time it is requested.
This constant recompilation may seem a waste of processor time, but it is actually not all
that bad because you no longer need to worry about hand recompiling your scripts when
you make any changes. On the flip side, many scripts take longer to compile than they do
to execute!
Furthermore, it provides very quick feedback during development. If you have an error
somewhere in your file, PHP will refuse to compile the page until you have fixed the
problem, and you are able to step through execution of your code line by line until you
find the problem.
The speed hit of regular compilation is nullified entirely by the use of PHP accelerators.
One major advantage to having interpreted code is that all memory used by the script is
managed by PHP, and the language automatically cleans up after every script has finished.
This means that you do not need to worry about closing database links, freeing memory
assigned to images, and so on, because PHP will do it for you. That is not to say you should
be lazy and make PHP do all the work - good programmers clean up themselves, and let
PHP work as backup in case something is missed.
PHP offers a great deal of flexibility as to how you want to output your content. In general
use, PHP is embedded inside HTML in code islands started with <?php and ended with
?>.
You can reverse this by writing your whole script as one big PHP code island and printing
HTML as necessary. Going back to the example shown previously, we can make our PHP
code look almost identical to the Perl code by printing the HTML from inside our PHP
code:
<?php
print "<HTML>\n";
print "<BODY>\n";
print"<P>Welcome,$Name</P
>\n";
print "</BODY>\n";
print "</HTML>\n";
?>
"Print" is a simple function that outputs a chunk of text, enclosed in quotation marks, to
the client. "\n" means "start new lines in the source code", and it serves to lay the source
code out nicely. For the longest time, a debate raged on message boards and mailing lists
as to whether it was faster to drop out of "PHP mode" to output large amounts of HTML,
or whether it was just as fast to stay in PHP mode. The truth is that it is horses for courses
- you will find little or no speed difference either way.
PHP also has great output buffering features that further increase your control over the
flow of output. An output buffer can be thought of as a storage hole where you can queue
up content for outputting. Once you start a buffer, any output you create is automatically
put into that buffer, and is not seen unless the buffer is closed and flushed - that is, sent to
your visitor.
The advantage to this output queuing is two-fold. First, it allows you to clean the buffer if
you decide not to output the current output queue in the buffer. When a buffer is cleaned,
all the output stored in there is deleted as if it were never there, and output for that buffer
is started from scratch.
Secondly, output buffering allows you to break the traditional ordering of web pages - that
of headers first and content later. Owing to the fact that you queue up all your output, you
can send content first, then headers, then more content, then finally flush the buffer. PHP
internally rearranges the buffer so that headers come before content.
Output buffering is covered in much more depth later. The base of the PHP language is
very simple, having just enough to set and retrieve variables, work with loops, and check
whether a statement is true or not. The real power behind PHP comes with its extensions
- add-ons to the base language that give it more flexibility. There are hundreds of
extensions to PHP, and they can be broken down into five distinct types: core, bundled,
PECL, third party, and DIY.
• Core extensions are extensions that are bundled with PHP itself, and enabled by
default. For all intents and purposes they are part of the base language, because,
unless you explicitly disable them (few people do, and sometimes you cannot),
they are available inside PHP. For example, the mechanism to handle reading and
saving files in PHP is actually handled by an extension that is automatically
compiled into PHP.
• Bundled extensions are extensions that are bundled with PHP, but not enabled by
default. These are commonly used, which is why they are bundled, but they are not
available to you unless you specifically enable them. For example, the mechanism
to handle graphics creation and editing is handled by an extension that is bundled
with PHP, but not enabled by default.
• PECL stands for "PHP Extension Code Library", and is as a subset of the PHP
Extension and Application Repository, PEAR. PECL (pronounced "pickle") was
originally created as a place where rarely used or dormant bundled extensions
could be moved if they were no longer considered relevant. PECL has grown a lot
since its founding, and is now the home of many interesting and experimental
extensions that are not quite important enough to be bundled directly with PHP.
• Third-party extensions are written by programmers like you who wanted to solve
a particular problem that was unsolvable without them creating a new extension.
There is a variety of third-party extensions available out there, with the sole
difference between a third-party extension and a PECL extension is that there are
various rules about having code being submitted to PECL. Third-party extensions
are frequently unstable, and often just downright crazy. That is not to say they are
bad - give them a shot and see what you can do.
• Finally, Do-It-Yourself (DIY) extensions are simply extensions you created
yourself. PHP has a remarkably rich extension creation system that makes it quite
simple to add your own code as long as you know C. Later on we'll be going
through the task of creating your first extension from start to finish. Note that
creating your own extension requires that you have the ability to compile PHP - this is
not a problem if you use Unix, but is very difficult for Windows users without the
correct software.
PHP was originally created by Rasmus Lerdorf, and he oversaw production of the first
release and PHP/FI 2.0. PHP 3 was rewritten from the ground uby Zeev Suraski and Andi
Gutmans, and the three of them are the "language architects" behind PHP. In the PHP
group, the developers who primarily work on development of the language core, there are:
Thies C. Arntzen, Stig Bakken, Shane Caraveo, Andi Gutmans, Rasmus Lerdorf, Sam
Ruby, Sascha Schumann, Zeev Suraski, Jim Winstead, and Andrei Zmievski. Each of them
has worked exceptionally hard, along with the help of many others, to put PHP where it is
today. Two other groups of people deserve special mention: Jouni Ahto, Alexander
Aulbach, Stig Bakken, Rasmus Lerdorf, Egon Schmid, Lars Torben Wilson, and Jim
Winstead collectively make up the PHP Documentation Team, who have done such an
excellent job with the PHP manual. In addition, Ilia Alshanetsky, Stefan Esser, Moriyoshi
Koizumi, Sebastian Nohn, Derick Rethans, Melvyn Sopacua, and Jani Taskinen run the
Quality Assurance for PHP, making sure each release comes out as bug-free as possible.
If you have a little time on your hands, visit http://www.php.net/credits.php and read the
full credits online yourself - you will see that PHP really is a community effort built by the
collective desire to build the best language possible.
MYSQL
MySQL is the world's most popular open source database software, with over 100 million
copies of its software downloaded or distributed throughout its history. With its superior
speed, reliability, and ease of use, MySQL has become the preferred choice for Web, Web
2.0, SaaS, ISV, Telecom companies and forward-thinking corporate IT Managers because
it eliminates the major problems associated with downtime, maintenance and
administration for modern, online applications .Many of the world's largest and fastest-
growing organizations use MySQL to save time and money powering their high-volume
Web sites, critical business systems, and packaged software including industry leaders
such as Yahoo!, Alcatel-Lucent, Google, Nokia, YouTube, Wikipedia, and Booking.com.
2.4.2 FEATURES
The flagship MySQL offering is MySQL Enterprise, a comprehensive set of production-
tested software, proactive monitoring tools, and premium support services available in an
affordable annual subscription.
MySQL is a key part of LAMP (Linux, Apache, MySQL, PHP / Perl / Python), the fast-
growing open source enterprise software stack. More and more companies are using
LAMP as an alternative to expensive proprietary software stacks because of its lower cost
and freedom from platform lockin.
The MySQL database is owned, developed and supported by Sun Microsystems, one of
the world's largest contributors to open source software. MySQL was originally founded
and developed in Sweden by two Swedes and a Finn: David Axmark, Allan Larsson and
Michael "Monty" Widenius, who had worked together since the 1980's. More historical
information on MySQL is available on Wikipedia
• The best and the most-used database in the world for online applications
• Easy to use
• Continuously improved while remaining fast, secure and reliable
What is a database?
Database Terminology
The database contains tables, each table contains many rows and columns. Each row
contains data about one single entity. This is called a record. Each column contains one
piece of data that relates to the record, called an attribute. An attribute, when referring to
a database is called field.
The kind of structure, the database gives as a way to manipulate this data: SQL. SQL is a
powerful way to search for records or make changes. Almost all DBMS use SQL.
The machine where MySQL runs and stores the data is called MySQL server. To connect
to the server, we have several setup options. First, we can have the MySQL client and
MySQL server o our desktop. Second, we can have the MySQL client on our desktop
while the MySQL server is on another machine that we connect. Finally, our desktop can
be any machine connecting to another machine with a mySQL client, which in turn
connects to a MySQL server, either on the same machine or another.
Hardware Requirements:-
Processor : Intel 5
Software Requirements: -
3.1 INTRODUCTION
For the design of DreamCareer, has given for developing an efficient system, which
is user friendly as well as high in performance. It has been assured that the system will
have the functions and promises of the proposed system. Design phase acts as a bridge
between the software requirement specification and the implementation phase, which
satisfies the requirements.
The major step in design is the preparation of input forms and the design of all the
major output forms in a manner acceptable to the user in all aspects. The base lies in the
complete understanding of the system. The data flow diagrams explicitly specify the
process flow. Table design or database design is the next major step. Extreme care has to
be given here and several concepts of normalization have to be applied at many levels.
Program specification comes next. Here we specify various aspects of the program and
also will explain in detail the major components used in the program. The overall process
flow is also explain in much detail. Various validation rules and constraints such as data
format checking are applied during data input. The companies or seekers that registered to
the application are validated by administrator. To ensure security strict checking of
password and username had done.
Level 0
Level 1
Level 1.1
Level 1.2
Level 1.3
registers
staff
student
The purpose of system testing is to identify and correct errors in the candidate system.
Testing is an important element of the software quality assurance and represents the
ultimate review of specification, design and coding. The increasing visibility of the
software as a system element and the costs associated with a software failure are motivated
forces for well planned, through testing.
Software testing is a critical element of software quality assurance
and represents the ultimate quality review of specifications, design and code generation.
Once the source code has been generated, the program should be executed before the
customer gets it with the specific intend of fining and removing all errors, test must be
designed using disciplined techniques. Testing techniques provides the systematic
guidance for designing tests. To uncover the errors in the program behaviour function and
performance the following steps to be done:
* Execute the integral logic of the software components.
* Execute the input and output domains of the program to uncover errors
The turn error is used to refer the difference between the actual output of the software
and the correct output. Fault is a condition that causes the software to fail to perform its
required function.
Software reliability is defined as the required function. Software reliability is defined as
the probability that the software will not undergo failure for a specified time under
specified condition. Failure is the inability of a system or a component to perform a
required function according to its specification. Different levels of testing were employed
for software to make an error free, fault free and reliable. Basically in software testing four
type of testing methods are adopted.
Unit testing
Integration testing
Validation testing
System testing
Content Testing
Content testing checks that users can easily understand all items that appear on Software
and, importantly, that they are able to correctly interpret the information they read.
Accordingly, it identifies any problem areas that may require simplification or re-writing.
Testing methodology is tailored to provide bespoke testing scripts, questionnaires and data
analysis instruments for all clients and it delivers rich qualitative user feedback plus
quantitative data as follows:
• Individual performance ratings for each page against a number of critical, generic
comprehension indicators
• Individual performance ratings for each page based on its ability to address specific
information and communication objectives pertinent to the client
• At-a-glance, comparative performance data for all topics
• Overall success scores (OSS) for all topics
This tests the whole end to end scenario (which simulates exactly what the user would be
doing). This (for the most part) goes through all the mouse clicks and keyboard presses
the user goes through to get an action done. If we extend the previous example this would
be invoking the same action except that this time instead of using any test hooks it would
be using the keyboard shortcut and instead verify the actual displayed results on the
application.
User Interface testing is a process to test Real Estate user interface and to detect
if application is functionally correct. USER INTERFACE testing involves carrying set of
tasks and comparing the result of same with the expected output and ability to repeat same
set of tasks multiple times with different data input and same level of accuracy. USER
INTERFACE Testing includes how the Real Estate handles keyboard and mouse events,
how different GUI components like menu bars, toolbars, dialogs, buttons, edit fields, list
controls, images etc. reacts to user input and whether or not it performs in the desired
manner. Implementing USER INTERFACE testing for your application early in the
software development cycle speeds up development, improves quality and reduces risks
towards the end of the cycle. USER INTERFACE Testing can be performed both manually
with a human tester or could be performed automatically with use of a software program.
Navigation Testing
Navigation testing confirm that all internal and external links of Real Estate are working
properly. There is no any broken link or orphan page in application. Functional,
integration, system, regression, performance and load testing come under black box
testing. Functional, integration testing is done in white box also, once the first layers of
the Software have been examined, it is time to perform simple tests to probe the quality of
the global Software navigation. Good Software will provide consistent, well-executed
navigation and should provide alternative navigation schemes, such as Software maps,
indexes, and search engines. First, look to make sure that placement of navigation is
consistent from page to page. Subtle shifting may occur, so try browsing the site extremely
fast and notice whether the menu items bounce or jump position slightly from page to
page. Even this minor variation can break the perceived stability of a site. Next, look to
see how robust the navigation is and whether multiple forms of Software navigation are
supported. Numerous navigation execution questions should be asked during this phase.
The current location clearly indicated with labels or link path indicators. The Software
have text links at the bottoms of pages. Alternative text used for graphical navigation
buttons. The Software require excessive scrolling.
Performance Testing
Black box-testing
Black box testing focuses on the functional requirements of the software. That is black box
testing enables the software engineer to derive sets of input conditions that will fully
exercised all functional requirements for a program. Black box testing attempts to find
errors in the following categories,
Regression Test
Quality is usually appraised by a collection of regression tests forming a
suite of programs that test one or more features of the system, a regression test is written
and the results are generated. If the results are in error, then the offending bug is corrected.
A valid regression test generates verified results. These verified results are called the ``gold
standard.'' This term is borrowed from financial markets where paper money issued by
governments was backed by real gold. Ideally, the validity of a test result is driven by the
requirement document; in practice, the implementation team is responsible for validity
interpretation.
The tests are collected, as well as their gold-standard results, into a
regression test suite. As development continues, more tests are added, while old tests may
remain valid. Because of new development, an old test may no longer be valid. If this is
the case, the old test results are altered in the ``gold standard'' to match the current
expectations. The test suite is run generating new results. These new results are then
compared with the gold-standard results.
If they differ, then a potential new fault has entered the system. The fault is corrected and
the development continues. This mechanism detects when new development invalidates
existing development, and thus prevents the system from regressing into a fault state. There
are four major focuses of regression testing used to assure quality.
Internal Testing
Unit Testing
In unit testing the analyst tests the programs making up a system. Unit testing gives
stress on the modules independently of one another, to find errors. This helps the tester in
detecting errors in coding and logic that are contained within that module alone. The errors
resulting from the interaction between modules are initially avoided. Unit testing can be
performed from the bottom up, starting with smallest and lowest-level modules and
proceeding one at a time. For each module in bottom-up testing a short program is used to
execute the module and provides the needed data, so that the module is asked to perform
the way it will when embedded within the larger system. Unit testing deals with testing a
unit as a whole. This would test the interaction of many functions but confine the test
within one unit. The exact scope of a unit is left to interpretation. Supporting test code,
sometimes called scaffolding, may be necessary to support an individual test. This type of
testing is driven by the architecture and implementation teams. This focus is also called
black-box testing because only the details of the interface are visible to the test. Limits
that are global to a unit are tested here.
In software testing, one particular test may need some supporting software. This software
establishes an environment around the test. Only when this environment is established can
a correct evaluation of the test take place. The scaffolding software may establish state and
values for data structures as well as providing dummy external functions for the test.
Different scaffolding software may be needed from one test to another test. Scaffolding
software rarely is considered part of the system.
Sometimes the scaffolding software becomes larger than the system software being tested.
Usually the scaffolding software is not of the same quality as the system software and
frequently is quite fragile. A small change in the test may lead to much larger changes in
the scaffolding.
Application Testing
Application testing deals with tests for the entire application. This is driven by the
scenarios from the analysis team. Application limits and features are tested here.
The application must successfully execute all scenarios before it is ready for general
customer availability. After all, the scenarios are a part of the requirement document and
measure success. Application testing represents the bulk of the testing done by industry.
Unlike the internal and unit testing, which are programmed, these test are usually
driven by scripts that run the system with a collection of parameters and collect results. In
the past, these scripts may have been written by hand but in many modern systems this
process can be automated.
Most current applications have graphical user interfaces (GUI). Testing a GUI to
assure quality becomes a bit of a problem. Most, if not all, GUI systems have event loops.
The GUI event loop contains signals for mouse, keyboard, Window, and other related
events. Associated with each event are the coordinates on the screen of the event. The
screen coordinates can be related back to the GUI object and then the event can be
serviced. Unfortunately, if some GUI object is positioned at a different location on the
screen, then the coordinates change in the event loop. Logically the events at the new
coordinates should be associated with the same GUI object. This logical association can
be accomplished by giving unique names to all of the GUI objects and providing the
unique names as additional information in the events in the event loop. The GUI
application reads the next event off of the event loop, locates the GUI object, and services
the event.
The events on the event loop are usually generated by human actions such as typing
characters, clicking mouse buttons, and moving the cursor. A simple modification to the
loop can journal the events into a file. At a later time, this file could be used to regenerate
the events, as if the human was present, and place them on the event loop.
The GUI application will respond accordingly. A tester, using the GUI, now executes
a scenario. A journal of the GUI event loop from the scenario is captured. At a later time
the scenario can be repeated again and again in an automated fashion. The ability to repeat
a test is key to automation and stress testing.
Stress Testing
Stress testing deals with the quality of the application in the environment. The
idea is to create an environment more demanding of the application than the application
would experience under normal work loads. This is the hardest and most complex category
of testing to accomplish and it requires a joint effort from all teams.
A test environment is established with many testing stations. At each station, a
script is exercising the system. These scripts are usually based on the regression suite.
More and more stations are added, all simultaneous hammering on the system, until the
system breaks. The system is repaired and the stress test is repeated until a level of stress
is reached that is higher than expected to be present at a customer site. Race conditions
and memory leaks are often found under stress testing. A race condition is a conflict
between at least two tests. Each test works correctly when done in isolation. When the two
tests are run in parallel, one or both of the tests fail. This is usually due to an incorrectly
managed lock.
Integration Testing
This testing level can be simply defined as integrating and then testing. i.e., here,
many unit tested modules are combined into subsystems, which are then tested. Integration
testing aims at whether the modules can be integrated properly. Hence, the emphasis is on
testing interfaces between modules. This testing activity can be considered testing the
design.
• Stage Implementation
• Direct Implementation
The proposed new system is implemented directly and the user starts working
on the new System. The shortcoming, if any, faced are then rectified later. Parallel
Implementation
The old and the new system are not used simultaneously. This helps in comparison
of the results from the two systems. Once the user is satisfied and his intended
objectives are achieved by the new system, he stop using the old one. My project
was implemented on approach of prototype model whose functionality was
increased day by day, as the client was given full liberty in choosing his needs and
gets to the maximum benefit out of the system developed.
Implementation is the stage of the project when the theoretical design is turned
into a working system. The implementation stage is a systems project in its own
right. It includes careful planning, investigation of current system and its
constraints on implementation, design of methods to achieve the changeover,
training of the staff in the changeover procedure and evaluation of changeover
method.
The first task in implementation is planning- deciding on the methods and time-
scale to be adopted. Once the planning has been completed, the major effort is to
ensure that the programs in the system are working properly. At the same time
concentrate on training the staff. When the staffs have been trained, the complete
system, involving both computer and user can be executed effectively.
System testing check the readiness and accuracy of the system access update
and retrieve data from new files. Once the program becomes available, the test data
are read into the computer and processed. In this system, conventional Parallel Run
was conducted to establish the efficiency of the system.
Data from one or more previous periods for the whole or part of the system is
run on the new system after results have been obtained from the old system and
both are compared. It is performed till the completion of one system life cycle.
When the changeover has taken place there will be a need for amendment to
correct or improve the new system. When the user wants to add any new records,
some fields will automatically get their default values. If the user desires to change
these default values he can do it.
TYPES OF MAINTENANCE
Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance
The project work involves the complete requirements specification and the
description of the project itself. The coding done using Oracle is the total coding
work done in order to make the application program a useful project.
Standing as developer of this website , I put forward the following suggestion to expand the
scope of the same.
*Optimized searching
*Mobile Application
The efficiency of the system can be improved by applying minor modifications. It would be
necessary to make corrections in the program depending on the changes in the system and the
user’s advanced need.
Chapter 7: Conclusion
7.1 Conclusion
The application titled “Campus Placement Recruitment System” developed is designed in
such a way that any further enhancement can be done with ease. The system has the
capability for easy integration with other systems. New modules can be added to the existing
system with less effort. I put as much as my effort to develop this system-based application
titled “Campus Placement Recruitment System” that is easily accessible , informative and
helpful .
It has been designed in such a way that it is easy to modify, can be updated efficiently
and accurately. On realizing the importance of systematically documentation all the processes
are implemented using a software engineering approach.
Working in a live environment enables one to appreciate the intricacies involved in the
System Development Life Cycle (SDLC). I have gained a lot of practical knowledge from
this project, which I think shall make us in a good state in the future.
Once again, I would like to thank everyone who was somehow or other related with the
successful completion of this project.
index.php
<?php
$conn=mysqli_connect("localhost","root","","placement");
if(isset($_POST['submit'])){
$n=$_POST['name'];
$a=$_POST['age'];
$g=$_POST['gender'];
$e=$_POST['email'];
$pw=$_POST['password'];
$data=mysqli_query($conn,"insert into
staff(Staff_Name,Age,Gender,Email,Password)values('$n','$a','$g','$e','$pw')");
?>
<script>alert('Registration successful')</script>
<?php
}
?>
<body>
<div class="main">
<section class="signup">
<!-- <img src="images/signup-bg.jpg" alt=""> -->
<div class="container">
<div class="signup-content">
<form method="POST" id="signup-form" class="signup-form">
<h2 class="form-title">Create account</h2>
<div class="form-group">
<input type="text" class="form-input" name="name" id="name"
placeholder=" Name"/>
</div>
<div class="form-group">
</div>
</section>
</div>
registration.php
<?php
$conn=mysqli_connect("localhost","root","","placement");
if(isset($_POST['submit'])){
$n=$_POST['name'];
$e=$_POST['email'];
$pn=$_POST['phno'];
$b=$_POST['batch'];
$y=$_POST['year'];
$pw=$_POST['password'];
$data=mysqli_query($conn,"insert into
student(Name,Email,Phone_number,Batch,Year,Password,rights)values('$n','$e','$pn','$b','$y',
'$pw','student')");
?>
<script>alert('Registration successful')</script>
<?php
}
?>
<body>
<div class="main">
<section class="signup">
<!-- <img src="images/signup-bg.jpg" alt=""> -->
<div class="container">
<div class="signup-content">
</div>
<div class="form-group">
<input type="submit" name="submit" id="submit" class="form-submit"
value="Sign up"/>
</div>
</form>
<p class="loginhere">
Have already an account ? <a href="../login/index.php" class="loginhere-
link">Login here</a>
</p>
</div>
</div>
</section>
</div>
addplacement.php
<?php
$conn=mysqli_connect("localhost","root","","placement");
if(isset($_POST['submit'])){
$n=$_POST['name'];
$o=$_POST['organisation'];
$d=$_POST['date'];
$np=$_POST['num_of_participants'];
$data=mysqli_query($conn,"insert into
placement(Placement_name,Organisation,Date,Num_of_participants)values('$n','$o','$d','$np'
)");
?>
<script>alert('Registration successful')</script>
<?php
}
?>
<body>
<div class="main">
<div class="container">
<div class="signup-content">
<div class="signup-img">
<img src="images/signup-img.jpg" alt="">
</div>
<div class="signup-form">
<form method="POST" class="register-form" id="register-form">
<h2>Register here</h2>
<div class="form-row">
<div class="form-group">
<label for="name">Job:</label>
<input type="text" name="name" id="name" required/>
</div>
<div class="form-group">
<label for="organisation">Company:</label>
<input type="text" name="organisation" id="organisation" required/>
</div>
</div>
<div class="form-group">
<label for="date">Date:</label>
<input type="date" name="date" id="date" required/>
</div>
<div class="form-group">
<label for="num_of_participants">Vacancy:</label>
<input type="text" name="num_of_participants" id="num_of_participants"
required/>
</div>
<div class="form-submit">
<input type="submit" value="Reset All" class="submit" name="reset"
id="reset" />
<input type="submit" value="Submit Form" class="submit"
name="submit" id="submit" />
</div>
</form>
</div>
</div>
</div>
</div>
myplace.php
<?php
session_start();
$Email=$_SESSION['Email'];
$conn=mysqli_connect("localhost","root","","placement");
?>
<body>
<section class="ftco-section">
<div class="container">
</div>
</div>
<div class="row">
<div class="col-md-12">
<div class="table-wrap">
<table class="table">
<thead class="thead-dark">
<tr>
<tr>
<th></th>
<th> Name</th>
<th>Email</th>
<th>Phone number</th>
<th>Course</th>
<th>Year</th>
<th>Job</th>
<th>Company</th>
<th>Date</th>
<th>Result</th>
<th> </th>
</tr>
</thead>
<tbody>
<?php
if(isset($data)){
while($res=mysqli_fetch_array($data))
?>
</tr>
<?php
?>
</tbody>
</table>
</div>
</div>
</div>
</div>
</section>
Home Page
Student Registration
Admin Login
Staff Registration
View Staff
Staff Login
Placement Registration
Placement List
Student Login
BOOKS REFERENCE:
1. PHP and MYSQL Web Development,3rd E, Luke welling,Laur
2. PHP 5 Fast and Easy Web Development, Julie Maloni
3. PHP and MYSQL, W Jason Gilmore
4. PHP: The Complete Reference, Steven Holzner, McGraw Hill Professional, 2008
Web Reference
5. www.w3schools.com/php
6. www.mysqltutorial.com
7. www.wikipedia.org