MATRIMONIAL MANAGEMENT SYSTEM

INDEX
Sr.No Topic Name Page.NO
1 PROBLEM IDENTIFICATION DEFINITION & MODIFICATION 2
1.1 ABSTRACT OF PROJECT AND OVERVIEW OF PROBLEM 3
1.2 EXISTING SYSTEM 4
1.3 PROJECT PROFILE 5
1.4 TECHONOLOGY OVERVIEW 6

2 SYSTEM REQIUREMENT SPECIFICATION 9

2.1 REQUIREMENT GATHERING AND ANALYSIS 10
2.2SOFTWARE REQUIREMENT SPECIFICATION 12
2.3 FEASIBILITY STUDY 14

3 PROBLEM SOLUTION OUTLINE 15

3.1 MODULES DESCRIPTION 16

3.2 ENTITY RELATIONSHIP DIAGRAM 17

3.3 FLOW CHART 18
3.4 SOFTWARE AND HARDWAR SPECIFICATION 19
3.5 DATA FLOW DIAGRAM 20
3.6 DATA DICTIONARY 23
3.7 TIME LINE CHART 28
3.8 SCREEN SHOT 29

4 FUTURE DEVELOPMENT ONLINE

5 APPENDICES
5.1 BIBLOGRAPHY

1|Page
 MATRIMONIAL MANAGEMENT SYSTEM

CHAPTER 1:-
Problem identification definition and modification: -

2|Page
 MATRIMONIAL MANAGEMENT SYSTEM

1.1 ABSTRACT: -
The main aim of the Matrimonial Project in PHP is to provide a relation between
marriage Admin and Profile looking users. This online matrimonial site is mainly
developed to let individuals find their potential matches for marriage according
to their priorities set. This project allows the phrase ‘Marriages are made in
heaven’ to be rephrased as ‘Marriages are now made online’. This application
allows users to browse profiles of those who have registered themselves on this
site. This allows individuals to give their information such as Name, Gender,
Religion, Caste, Marital status, Current salary, Occupation etc. This application
also allows to upload photos of the individual registering and also allows to
upload a kundali picture of the individual. The person looking for marriage can
register and search for a profile that matches their requirement. This application
allows individual to search by gender, age, religion, caste, marital status and also
allows individual to view kundali which today is at highest priority in many cases.
When an individual selects a profile which matches his or her requirement, it
can the send an email indicating his or her interest and the email will be sent
along with the sender’s details. Thus this application allows individuals to let
others view its profile and also allows it to view others profile depending on the
priority set.

3|Page
 MATRIMONIAL MANAGEMENT SYSTEM
1.2 EXISTING SYSTEM: -
The existing system was an automated system but It was found to be inefficient in meeting
the growing demands of the population and different online matrimonial sites take a lot of
time and money for searching a suitable match. But still they are not able to provide a good
life partner

Drawbacks in the existing system

 The existing system is not a user-friendly system.
 Time Consuming to search for a Perfect Match.
 Lack of security.
 The existing system does not implement restriction for users to access the data

An online matrimonial system is designed to overcome the drawbacks of existing systems. It

also provides fast searching for a life partner and sending his/her contact or communicates
with the existing members. As both the members will agree they meet together for the
marriage. A person can search for a bride or a groom of any religion of any caste.

NEEDS OF NEW SYSTEM: -

1.Security: For Security purposes we are going to use the AES algorithm. AES is based on a
design principle known as a substitution-permutation network, combination of both
substitution and permutation, and is fast in both software and hardware. Unlike its
predecessor DES, AES does not use a Feistel network. AES is a variant of Rijndael which has a
fixed block size of 128 bits, and a key size of 128, 192, or 256 bits. By contrast, the Rijndael
specification per se is specified with block and key sizes that may be any multiple of 32 bits,
both with a minimum of 128 and a maximum of 256 bits.

2.Recommendation: This system will provide fast searching as we implement the Apriori
algorithm. Apriori is an algorithm for frequent item set mining and association rule learning
over transactional databases. It proceeds by identifying the frequent individual items in the
database and extending them to larger and larger item sets as long as those item sets appear
sufficiently often in the database.

3.Maintainability: There will be no maintenance requirement for the Secured Online

Matrimonial System. The database is provided by the administrator and user and therefore is
maintained by this Admin. This website is automated.

4.Portability: The system is developed to work on any environment so it can be portable.

5.Availability: This system will be available on any system.

4|Page
 MATRIMONIAL MANAGEMENT SYSTEM
1.3 PROJECT PROFILE: -

PROJECT PROFILE
Collage name: B.S.Patel Polytechnic
Semester: 5th semester
Department: Computer Engineering
Technology: PHP
GROUP NUMBER:

Group Members
Total Members: 6
Name And Enrolment Number: Sheth Agam
[18291341112]
Patel Shreya
[18291341113]
Suthar Shivam
[18291341117]
Vasava Bhavesh
[18291341120]
Patel mitul mukeshbhai
[18291341064]
Patel om kamleshbhai
[18291341067]
Guide Name
Internal Guide:

External Guide:

Project Particular
Project Front End: PHP

Project Back End: MY SQL

Operating System: Windows XP

5|Page
 MATRIMONIAL MANAGEMENT SYSTEM

1.4 TECHNOLOGY OVERVIEW: -

1) PHP:
PHP started out as a small open source project that evolved as more and more
people found out how useful it was. Rasmus Lerdorf unleashed the first version
of PHP way back in 1994.
 PHP is a recursive acronym for "PHP: Hypertext Preprocessor".
 PHP is a server side scripting language that is embedded in HTML. It is
used to manage dynamic content, databases, session tracking, even build
entire e-commerce sites.
 It is integrated with a number of popular databases, including MySQL,
PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
 PHP is pleasingly zippy in its execution, especially when compiled as an
Apache module on the Unix side. The MySQL server, once started,
executes even very complex queries with huge result sets in record-
setting time.
 PHP supports a large number of major protocols such as POP3, IMAP, and
LDAP. PHP4 added support for Java and distributed object architectures
(COM and CORBA), making n-tier development a possibility for the first
time.
 PHP is forgiving: PHP language tries to be as forgiving as possible.
 PHP Syntax is C-Like.

Common uses of PHP:

 PHP performs system functions, i.e. from files on a system it can create,
open, read, write, and close them.
 PHP can handle forms, i.e. gather data from files, save data to a file,
through email you can send data, return data to the user.
 You add, delete, modify elements within your database through PHP.
 Access cookies variables and set cookies.
 Using PHP, you can restrict users to access some pages of your website.

6|Page
 MATRIMONIAL MANAGEMENT SYSTEM
 It can encrypt data.

Characteristics of PHP:
Five important characteristics make PHP's practical nature possible −

 Simplicity
 Efficiency
 Security
 Flexibility
 Familiarity

2) MY SQL:
MySQL is the most popular Open Source Relational SQL Database Management
System. MySQL is one of the best RDBMS being used for developing various web-
based software applications. MySQL is developed, marketed and supported by
MySQL AB, which is a Swedish company. This tutorial will give you a quick start
to MySQL and make you comfortable with MySQL programming. MySQL is a fast,
easy-to-use RDBMS being used for many small and big businesses. MySQL is
developed, marketed and supported by MySQL AB, which is a Swedish company.
MySQL is becoming so popular because of many good reasons −
 MySQL is released under an open-source license. So you have nothing to
pay to use it.
 MySQL is a very powerful program in its own right. It handles a large
subset of the functionality of the most expensive and powerful database
packages.
 MySQL uses a standard form of the well-known SQL data language.
 MySQL works on many operating systems and with many languages
including PHP, PERL, C, C++, JAVA, etc.
 MySQL works very quickly and works well even with large data sets.
 MySQL is very friendly to PHP, the most appreciated language for web
development.
 MySQL supports large databases, up to 50 million rows or more in a table.
The default file size limit for a table is 4GB, but you can increase this (if
7|Page
 MATRIMONIAL MANAGEMENT SYSTEM
your operating system can handle it) to a theoretical limit of 8 million
terabytes (TB).
 MySQL is customizable. The open-source GPL license allows
programmers to modify the MySQL software to fit their own specific
environments.

8|Page
MATRIMONIAL MANAGEMENT SYSTEM

CHAPTER 2: -
System requirement specification: -

9|Page
 MATRIMONIAL MANAGEMENT SYSTEM

2.1 Requirement Gathering And Analysis:

FUNCTIONAL REQUIREMENT OF MATRIMONIAL MANAGEMENT SYSTEM:
The practical demand of this can be that it will what it’s meant for. A practical demand
describes what a package ought to do, whereas non-functional needs place constraints on
however the system can do, therefore. Practical needs specify an operate that a system or
system part should be ready to perform.

Login:
Introduction:
licensed users are allowed to access.

Input:
The user enters the User sort, Username and positive identification.

Process Definition:
Checks User sort, Username and positive identification is valid or not.

Output:
The user is directed to next page or shows the message box “Login Failed”.

Registration:
Introduction:
solely Admin will access the page.

Input:
Admin has the authority to produce username and positive identification for
brand spanking new users

Process Definition:
Checks same username and positive identification exists or not and conjointly
checks whether or not all the fields are entered.

Output:
worker gets the username and positive identification.

10 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
Report:
Introduction:
solely Admin will access the page and check the report.

Input:
Bride/groom

Process Definition:
It retrieve’s all the knowledge hold on from completely different tables.

Output:
requested report is generated.

View:
Input:
bride/groom name, DOB, age, faith caste, contact, address

Process Definition:
within the read module, the user will read bride/grooms info that has already
been saved. The user also can add new info or edit the current info.

Output:
New bride/grooms info is fed to the table.

Match:
Input:
sort, bride/grooms name

Process Definition:
The user will enter bride/grooms info and on one click will realize the right
match to the corresponding bride/groom.

11 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
2.2 SOFTWARE REQUIREMENT SPECIFICATION: -
1)Creation of new User:

Introduction: This process will provide a user account.

Input: User id, user password and other personal details.

Processing: It will store the User id and password if appropriate in the User
database.
Output: Appropriate Message displayed telling account created.
2)User verification:
Introduction: This process will verify the user id and password.
Input: User id and user password.
Processing: It will verify the User id and password from the User database.
Output: Appropriate Message displayed based on Verification of User id and
password
3)Deleting User:
Introduction: Delete Existing User.
Input: User id/username.
Processing: Deletion of existing User.
Output: Existing user deleted from Database
4)Search Process:

Introduction: Search on Advance Search, Quick Search, Search by City, Search

by ID, Search by Profession.

Input: Search option.

Processing: Search based on criteria in database.

Output: Availability and locality with its complete details

12 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
4)Add New Customer:

Introduction: Introducing a new customer.

Input: Username, password and customer details with attractive photo.
Processing: Insertion of new customer details in the database.
Output: New Information gets stored in the Database.
5)paid user registration:

Introduction: Allows the users to finalise their choice as per their budget.
Input: User Id, password and requirements.
Processing: Search and mailing.
Output: update availability in database.
User Interface:

Each part of the user interface intends to be as user friendly as possible. The
fonts and buttons used will be intended to be very fast and easy to load on web
pages. The pages will be kept light in space so that it won’t take a long time for
the page to load.
Hardware Interface:

Processor: Pentium 4 or above

RAM :1 GB or above
Hard disk :40 GB or above
Software Interface:
Operating System: Windows XP or above

Development tool: PHP

Data Base: MY SQL

Communication Interface:The Website system shall send an e-mail

confirmation to the customer when the user registration is success.

13 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
2.3 FEASIBILITY STUDY: -
A feasibility study is a short, focused study, which aims to answers number of
questions
Does the system contribute to the overall objectives ?
Can the system be implemented using current technology and within given cost
and schedule constrains?
Can the system be integrated with systems which are already in place?
The three tests of feasibility have been carried out.

Technical Feasibility
Economical Feasibility
Operational Feasibility

TECHNICAL FEASIBILITY:

In Technical Feasibility study, one has to test whether the proposed system can
be developed using existing technology or not. It is planned to implement the
proposed system using java technology. It is evident that the necessary
hardware and software are available for development and implementation of
the proposed system. Hence, the solution is technically feasible.

ECONOMICAL FEASIBILITY:

As part of this, the costs and benefits associated with the proposed system
compared and the project is economically feasible only if tangible or intangible
benefits outweigh costs. The system development costs will be significant. So
the proposed system is economically feasible.

OPERATION FEASIBILITY:

It is a standard that ensures interoperability without stifling competition and

innovation among users, to the benefit of the public both in terms of cost and
service quality. The proposed system is acceptable to users. So the proposed
system is operationally feasible.

14 | P a g e
MATRIMONIAL MANAGEMENT SYSTEM

CHAPTER 3: -
Problem solution outline: -

15 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.1 MODULES DESCRIPTION: -
The System consists of several modules to undergo, which covers the
information’s/details of all logged-in persons. This system allows the individuals
to get his/her information’s such as Name, Gender, Religion, Caste, Marital
status, Salary, Occupation etc., after Registration has made.
Admin Module:

 The user needs to Sign-in/login to create an user id in the matrimonial system.

 Admin module’s work is to publish the user id and to create a database for both the
paid members and free members using User management.
 Paid members can able to contact with their required profile whereas free members
cannot be able to contact with the required profiles but only they can able to view their
profile and hence this process can be done by using the Admin module.

– By this manner the report for the individuals has been generated.

Candidate Module:

 Candidate module is simply used to direct the candidate as well as to verifying the
data’s/information’s of the candidate.
 If the candidate is not registered it provides the registration link for registration to be
done.
 If the candidate is already registered it checks whether the details are correct or not.
 If the candidate forgets the password, it provides a link for his/her mail-id to get
logged-in back.

Service Module:

 Service module can provide service only for the paid candidates.
 The paid candidates are known to be a prime candidate, whereas the prime candidate
can able to have the contact number as well as mail-id of their partner.

Expectation Module:

 Expectation modules contains the particulars that the Grooms/Brides expects from
their partner such as qualification, salary etc.,

Search Module:

 Search module is used to search the Compatible pair for the Grooms/Brides.

16 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.2 ENTITY RELATIONSHIP DIAGRAM: -

Name Password id

Pro_id
Name

User login

Search Profile With

Pro_id

with Profile Enters

Image
Name
Salary
Image
Caste Gallery

Pro_id Image
Success Story
_id

Has

Usr_id

Date Story

17 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.3 FLOW CHART: -
Start

ADMIN MEMBER VISITOR

No
Registration Registration

No No
Login

Yes Login
Login

Activate Member Yes Yes

Account
Search Search

My Account My Account
Deactivate Member
Account View Profile
View Profile

Partner Alert
Partner Alert

Send Message
Edit Profile
Online Chat

Change
Edit Profile Password

Change
Password

Log Out

End
18 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.4 SOFTWARE AND HARDWAR SPECIFICATION: -

H/W System Configuration: -

System: - Pentium Dual Core.

Hard Disk: - 120 GB.

Monitor: - 15’’ LED

Input Devices: - Keyboard, Mouse

Ram: - 1 GB

S/W System Configuration: -

Operating system: - Windows 7.

Coding Language: - PHP

Database: - MYSQL

19 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.5 DATA FLOW DIAGRAM: -
1)Context Level: -

Registration
Admin Login
Manage Profile

Manage user Registration

Manage Advertisement Matrimonial Login
Manage Feedback Management Manage Profile
Manage Success Story System Post Feedback
Post Complain
Post Success Story

Search Partner User

20 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
Level 1:-

Search Partners Generate Search

Management Partners
Management

Registration Generate
Management Registration
Management

Contact Profile Generate Contact

Management Matrimonial Profile Management
Management
Generate
Photographs System
Photographs
Management
Management

Documents Support Generate

Management Documents Support
Management

Multiple Types
Generate Multiple
Management
Types Management

21 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
Level 2:-
Login Check
Admin to Roles
System of
Access

Manage search partners

details
Forget Check
Password credentials Manage registration details
Manage
Modules Manage contact profile
details

Manage photographs details

Manage documents support

Send details
Email to
User
Manage multiple types
profile

Manage report

Manage User
Manage System Admins Manage Roles of Users
Permission

22 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.6 DATA DICTIONARY: -
Admin: -
Id Field Name Data Type Size Constraint Description
1 Id Int 12 Auto primary key Admin id
2 Name Varchar 50 Not null Admin Name
3 Password Varchar 50 Not null Admin password
4 Email Varchar 50 Not null Admin email id
5 Mobile Varchar 50 Not null Admin number
6 Uid Varchar 50 Not null Admin Userid

23 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
Personal info: -
Id Field Name Data Type Size Constraint Description
1 Fname varchar 50 Not null User first name
2 Mname varchar 50 Not null User middle name
3 Lname varchar 50 Not null User last name
4 Gender varchar 50 Not null User gender
5 DOB Date Not null User date of birth
6 Matrial_status varchar 50 Not null User marital status
7 Children Int 12 Not null No of children
8 Religion varchar 50 Not null User religion
9 Mother_tongue varchar 50 Not null User mother
tongue
10 Cast varchar 50 Not null User caste
11 Age Int 12 Not null User age
12 Email varchar 50 Not null User email
13 Mobile Int 10 Not null User mobile no
14 Address varchar 100 Not null User address
15 City varchar 50 Not null User city
16 State varchar 50 Not null User state
17 Country varchar 50 Not null User country
18 About Text Not null
19 Profile photo varchar 150 Not null User profile photo
20 Cover photo varchar 150 Not null User cover photo
21 Password varchar 50 Not null User password
22 Userid Int 12 Primary key User id
23 Aid Int 12 Auto Personal id

24 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
General info: -
Id Field Name Data Type Size Constraint Description
1 aId Int 12 Not null Admin id
2 Height Int 12 Not null User height
3 weight Int 12 Not null User weight
4 Body Varchar 50 Not null
5 Complexion Varchar 50 Not null User complexion
6 Physical Varchar 50 Not null User physical
status
7 Blood Varchar 50 Not null User blood group
8 Eating Varchar 50 Not null
9 Smok Varchar 50 Not null
10 Drink Varchar 50 Not null
11 Hobby Varchar 50 Not null User hobby
12 Userid Int 12 Foreign Key User id

Professional info: -
Id Field Name Data Type Size Constraint Description
1 aId Int 12 Not null Admin id
2 Occupation Varchar 50 Not null User occupation
3 Occupation category Varchar 50 Not null
4 Emp Varchar 50 Not null
5 Income Varchar 50 Not null User income
6 Address Varchar 50 Not null User address
7 City Varchar 50 Not null User city
8 State Varchar 50 Not null User state
9 Country Varchar 50 Not null User country
10 Userid Int 12 Unique key User id

25 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM

Education info: -
Id Field Name Data Type Size Constraint Description
1 aId Int 12 Auto Education id
2 Edu sub Varchar 50 Not null User education subject
3 Edu category Varchar 50 Not null User education category
4 Userid Int 12 Foreign Key User id

Family info: -
Id Field Name Data Type Size Constraint Description
1 aId Int 12 Auto Family id
2 Ftype Varchar 50 Not null User family type
3 Fvalue Varchar 50 Not null User family value
4 Fstatus Varchar 50 Not null User family
status
5 Father occupation Varchar 50 Not null User father
occupation
6 Brother Int 12 Not null No. of brothers
7 Sister Int 12 Not null No. of sisters
8 Member Int 12 Not null No. of members
9 Userid Int 12 Foreign Key User id

26 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
Success story: -
Id Field Name Data Type Size Constraint Description
1 aId Int 12 Auto Success story id
2 Groom name Varchar 50 Not null
3 Bride name Varchar 50 Not null
4 Guser id Varchar 50 Not null
5 Buser id Varchar 50 Not null
6 Wedding date Varchar 50 Not null
7 Email Varchar 50 Not null
8 Mobile Varchar 10 Not null
9 Comment Text
10 Image Image

27 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
3.7 TIME LINE CHART
NO Activity Time
Month 1 Month 2 Month 3 Month 4
10 20 30 10 20 30 10 20 30 10 20 30
day day day day day day day day day day day day
1. Problem
definition and
modification
1.1 Abstract of
project
1.2 Existing system

1.3 Profile
1.4 Tech. overview

2. System
requirement
specification
2.1 Analysis

2.2 SRS

2.3 Feasibility
study

3. Problem
solution out-
line
3.1 Modules

3.2 E-R Diagram

3.3 Flow chart

3.4 Specification

3.5 DFD

3.6 Data
dictionary
3.7 Gantt chart

3.8 Screen shot

4. Designing

28 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM

3.8 SCREEN SHOT: -

 Login page: -

29 | P a g e
 MATRIMONIAL MANAGEMENT SYSTEM
 Registration page: -

30 | P a g e