Search Sathi

A
Major Project
Submitted
In partial fulfillment
For the award of the Degree of
Bachelor of Technology
In Department of Computer Science & Engineering

Supervisor
Naveen Hemrajani
Assoc. Professor
SGVU, Jaipur

Submitted By:
Akanksha Pandey
Enroll.No:SGVU091012266

Department of Computer Science & Engineering

Suresh Gyan Vihar University
Mahal, Jagatpura, Jaipur
November 2012

Candidates Declaration
I hereby that the work, which is being presented in the Dissertation, entitled Search Sathi in
partial fulfillment for the award of Degree of Bachelor of Technology in Deptt. of Computer
Science & Engineering and submitted to the Department of Computer Science& Engineering,
Suresh Gyan Vihar University is a record of my own investigations carried under the Guidance
of Mr. Sandeep Bhargav Department of Computer Science & Engineering
I have not submitted the matter presented in this Dissertation any where for the award of any
other Degree.

(Name and Signature of Candidate)

Akanksha Pandey
Enrolment No: SGVU091012266
Counter Singed by
Sandeep Bhargava
CSE Dept
Suresh Gyan Vihar University

ACKNOWLEDGEMENT

The satisfaction and euphoria that accompany the successful completion of any task would
be incomplete without mentioning the names of people who made it possible, whose constant
guidance and encouragement crowns all efforts with our success.
It is not possible to write a report without the assistance of few supporting hands. We
acknowledge my debt to Mr. Sandeep Sir, Computer Science Department , who guided us and
corrected at each step during the writing process of the report. We thanks for their support and
guidance.
It was a wonderful and enlightening experience for us, as undergraduate student to be
exposed to industry work methods. We also cannot forget the help and support of all our Family
members and our friends who have helped us in every step of the way.
Akanksha Pandey
VII th sem
(IVth yr)

Table of Content
1. Introduction
2. Software requirement Specification
System Study
Existing System
Drawbacks in the Existing System.........................
3. System Analysis
Proposed System.
Need for the Proposed System
Feasibility Study..
Objective of proposed System.
Objective
Scope
4. Overview
D.B.M.S..
An Introduction to MYSQL.
An Introduction to JSP..
An Introduction to JavaScript.
An introduction to Apache Tomcat..
5. DFD
6. ERD
7. Database Design
Database Tables...............................................
8. Output Screen
Output of Pages
9. SQA Plan
Purpose
Scope
Risk Management
10. Testing
11. Conclusion
Scope for further development
12. Refrences

I NTRODUCTION
The Basic problem in searching a good life partner in this world is the times
spending and the travelling cost effective. This project (Online Matrimonial System) is a useful
website for a person of any religion who wishes to find a suitable life partner for himself\herself.
This website is very useful as it provides a fast searching of numerous
suitable profiles. He/she can create his/her profile and can communicate with the existing
members of site . Also since it will be available through internet it will be possible for the user to
see their profile anywhere.
The System Administrator can also update the data through internet. The Administrator can
delete those members account who wants to delete there account. The Administrator can send
perfect match to the member who submit the request for life partner.

SOFTWARE REQUIREMENT SPECIFICATION

System Study
Online Matrimonial is growing as the internet emerges as the best Technology which provides
a fast and efficient access to any information about anything. Difficulty in Keeping the details of
each user and their partners, delay in sending messages to them and
spending so much money for finding a good life partner causes the appearance of this website.
The Project concentrates on to surmount these difficulties.
Existing System
The existing system was an automated system but it was found to be inefficient in meeting
the growing demands of population and different online matrimonial take a lot of time and
money for searching a suitable match. But still they are not able to provide a good life partner of
any country, religion, caste and profession.
Drawbacks in the existing system
The existing system is not user-friendly system.
Disadvantage of the existing system is that for creating a profile it takes a lot of time and
money. For searching a good life partner according to your search criteria some time takes a lot
of time and sometimes there are no profile according to your.
Lack of security of the existing system was found to be another drawback. The existing
system does not implement restriction for users to access the data.

Objective and Scope of proposed system

Objective
The purpose of this document is to describe the design of the project named ONLINE
MATRIMONIAL SYSTEM .The purpose of design documentation is to express the vision for the
project, describe the contents, and present a plan for implementation.
A design document is a bible from which the producer preaches the goal, through which the
designers champion their ideas, and from which the artists and programmers get their
instructions and express their expertise.
SCOPE
The scope of this document is to design all the functionality which
is provided by the project.

Overview of DBMS:-Database system provides the centralized control of its

operational data that is one of its most valuable assets. In any
enterprise with a database system there will be someone identifiable
person who has this central responsibility for the operational data
and is known as DATABASE ADMINISTRATOR.
The advantages of having centralized control of the data
are
1. Redundancy can be eliminated:
In non-database system each application has its own private file. This
can often lead to considerable redundancy in stored data, with
resultant waste of storage space. These private files can be
eliminated, if the DBA has the necessary overall control on the
database system.
2. Inconsistency can be avoided:
Suppose that a student from the department SMS has taken a paper
from DCA then these two values will be in two tables in the database
of both the department. Then there will be some occasion on which
the two entries will not agree. At this stage the database is said to be
inconsistence.
3. The data can be shared:
The data can be shared among different application if we are using
a database system.

An Introduction to the MYSQL

MYSQL is a high performance, relational database server based on
MYSQL. It is built on CLIENT/SERVER architecture, which means a frontend or client
component, and a back end, or server component. MYSQL
server forms the back-end component in this architecture and is responsible
for providing all the standard DBMS functions. The client component, for
which there are many different possibilities, is responsible for providing all
of the user interface and application-processing function. The language used
to communicate between clients and MySQL.

An Introduction to JSP
JSP technology is the interface between HTML and JAVA .The JSP
tech. provides a seem less connection with JAVA and presents easy to
use.java like programming construct that can be scripting with HTML
files. This technology provides dynamic way to construct web pages.
A JSP page contains standard markup language elements,
such as HTML tags, just like a regular web page. A JSP page also
contains special JSP elements that allow the server to insert dynamic
content in the web page.
ADVANTAGES OF JSP
JSP supports both scripting and element-based dynamic content.
Allows developing custom tag libraries.
JSP pages are precompiled for efficient server processing.
JSP pages can be used in combination with servlets that handle the business
High Security.
Can run on any J2EE compatible web Server.
It can run on any OS that have J2EE compatible web server.
JSP separates the dynamic and static parts.
High Quality tool supports.
JSP supports N tier Application.
Write Once, Run Everywhere.
JSP is vender Neutral.

About Apache Tomcat:

Apache Tomcat is a servlet container developed by the Apache Software
Foundation (ASF). Tomcat implements the Java Servlet and the Java Server Pages (JSP)
specifications from Sun Microsystems, and provides a "pure Java" HTTP web Server
environment for Java code to run. Tomcat should not be confused with the Apache web server,
which is a C Implementation of an HTTP web server; these two web servers are not bundled
together. Apache Tomcat includes tools for configuration and management, but can also be
configured by editing XML configuration files.

Components
Tomcat version 4.x was released with Jasper (a redesigned JSP engine), Catalina (a
redesigned servlet container) and Coyote (an HTTP connector).

Data Flow Diagram:

Level 0 :

10

Level 1:

11

Entity Relationship Diagram

12

Database Screen Shots

13

14

15

Snap Shots

16

17

18

19

20

21

22

23

24

25

26

27

28

29

Software Quality Assurance

Purpose
The purpose of this Software Quality Assurance (SQA) Plan is to establish the goals,
processes, and responsibilities required to implement effective quality assurance functions for
the Marriage registration The Marriage RegistrationSoftware Quality Assurance Plan provides
the framework necessary to ensure a consistent approach to software quality assurance
throughout the project life cycle. It defines the approach that will be used by the SAM and
Software Quality (SQ) personnel to monitor and assess software development processes and
products to provide objective insight into the maturity and quality of the software.
Scope
The Scope of the project is that once can purchase the goods online. It means there is a
website for the shop, user can visit the site and see all the items of the shop with its price. If they
want to purchase then they select the item after selecting the item they can paid either by Credit
card or by Bank draft. The customer fills his full address .On the site to receive his goods. When
will the shop owner get the Bank draft Or particular amount then he will sent their ordered item
to their address. After purchasing and before payment if customer wants then they can cancel
the Items or add more quantity. This site is used such that any shop can register. The shop
owner will login on the site and they can See all the available items and all the sold items.
RISK MANAGEMENT
Specify the methods and procedures employed to identify, assess, monitor, and control areas of
risk arising during the portion of the software life cycle covered by the SQA Plan.
SQA will review and evaluate the technical risk analysis and any risk reduction plan. SQA
reporting will confirm that the identified risks are managed in accordance with the provisions of
the projects risk management plans, and that associated action items are reported, managed,
and followed through to closure.

30

Testing

Introduction
Terminology
1. Mistake a human action that produces an incorrect result.
2. Fault [or Defect] an incorrect step, process, or data de nition in a program.
3. Failure the inability of a system or component to perform its required function within the speci ed
performance requirement.
4. Error the di erence between a computed, observed, or measured value or condition and the
true, speci ed, or theoretically correct value or condition.
5. Speci cation a document that speci es in a complete, precise, veri able manner, the requirements, design, behavior, or other characteristic of a system or component, and often the
procedures for determining whether these provisions have been satis ed.
Testing Objectives
Direct objectives
1. To identify and reveal as many errors as possible in the tested software.
2. To bring the tested software, after correction of the identi ed errors and retesting, to an
acceptable level of quality.
3. To perform the required tests e ciently and e ectively, within the limits budgetary and scheduling
limitation.
Indirect objectives
1. To compile a record of software errors for use in error prevention (by corrective and preventive
actions).
2. To discuss the distinctions between validation testing and defect testing.
3. To describe the principles of system and component testing.
4. To describe strategies for generating system test cases.
5. To understand the essential characteristics of system.
Testing Goals
1. Fault identi cation: what fault caused the failure?
2. Fault correction: change the system.
3. Fault removal: take out the fault.

Testing Process
31

Component (or unit) testing

Testing of individual program components; Usually the responsibility of the component
developer (except sometimes for critical systems).
Integration testing
Involves building a system from its components and testing it for problems that arise from
com-ponent interactions.
Top-down integration
Bottom-up integration
System testing
Testing of groups of components integrated to create a system or sub-system; The
responsibility of an independent testing team; Tests are based on a system speci cation.
Acceptance testing
Pilot test: install on experimental basis
Alpha test: in-house test
Beta test: customer pilot
Parallel testing: new system operates in parallel with old system
Testing Approaches:
Black box testing
Black box testing also called functional testing and behavioral testing, focuses on determining
whether or not a program does what it is supposed to do based on its functional requirements.
No knowledge of internal structure of code.
White-box testing
White box testing is testing that takes into account the internal mechanism of a system or
compo-nent. White-box testing is also known as structural testing, clear box testing, and glass
box testing.
Test Plan
A test plan documents the strategy that will be used to verify and ensure that a product or
system meets its design speci cations and other requirements. A test plan is usually prepared by
or with signi cant input from Test Engineers.
Depending on the product and the responsibility of the organization to which the test plan
applies, a test plan may include one or more of the following:
Design Veri cation or Compliance test - to be performed during the development or
approval stages of the product, typically on a small sample of units.
32

Manufacturing or Production test - to be performed during preparation or assembly of

the product in an ongoing manner for purposes of performance veri cation and quality
control.
Acceptance or Commissioning test - to be performed at the time of delivery or
installation of the product.
Service and Repair test - to be performed as required over the service life of the product.
Regression test - to be performed on an existing operational product, to verify that existing functionality didn't get broken when other aspects of the environment are changed
(e.g., upgrading the platform on which an existing application runs).

33

Conclusion
It has helped us in gaining valuable information on the web page
design principle, handling the user interface in powerful way to
access the various pages across the application.
More than anything this project has given us great satisfaction
in having designed an application, which processes information from
departments to the students and vice-versa, As well to the
administration. And in one place, which saves precious time and
transfers the users needs into a software solution.
Scope for further Development:
There is a scope for further development in our project in
terms of functionality for student in which they can choose their
elective paper through internet and also from other departments
paper if not available in their department.

34

References
1.

Software Engineering (6-th edition)

Ian Summerville
2. DATABASE SYSTEM C.J.DATE
3. Java Server Pages (Nick Todd) Developers Handbook

37

37