Project Report

On

“MATRIMONIAL WEBSITE”
Submitted to

Veer Bahadur Singh Pui’vanchal University,

Jaunpur
In partial fulfillment of the requirements of the degree of

Bachelor of Computer Applications

Prepared By: Project Supen’isor:

Shreya Tiwari Mr. Bipin Bihari

BCA Vth Semester Roll Number: 21141000988 (Asst. Professor)

2022 - 2023

Department of Computer Applications

Technical Education & Research Institute

Post Graduate College, Ghazipur- 233001 (U.P.)

1
 CERTIFICATE

This is to certify that Shreya Tiwari pursuing BCA

Vth Semester from this institute, has prepared the project report entitled

“MATRIMONIAL WEBSITE” in partial fulfillment of the requirements of the degree

of Bachelor of Computer Application from Veer Bahadur Singh Purvanchal University,

Jaunpur: for the session 2021-2022. This report is based on the project work imdertaken

by Shreya Tiwari at Technical Education & Research Institute, Ghazipur under the

supervi sion of Mr. Bipin Bihari and fulfils the requirements of regulations relating to the

nature and standard of BCA course of V.B.S. Purvanchal University, Jaunpur : Uttar

Pradesh.

I recommend that this project report can be sent for evaluation.

Mr. Bipin Bihari Dr. Ajit Pratap Singh Gautam

Assistant Professor Heacl Dept. Computer Application

 DECLARATION

I Shreya Tiwari hereby declare that this project report entitled 'Matrimonial Website" has been prepared by
me under the supervision of “Mr. Bipin Bihari".

This project report is my bonafide work and has not been submitted in any fonn to any University or Institute
for the award of any degree or diploma prior to the under mentioned date. I bear the entire responsibility of
submission of this project report.

Shreya Tiwari

BCA Vth Semester Department of Computer

Application Technical Education & Research

Institute P. G. College, Ghazipur

4
2
 PREFACE

Non-Technical Overview
What project is about?

This project is named as “Matrimonial Website” is a virtual marriage bureau, providing free
services to brides and grooms world-wide. One can make his/her account on this website with or without a
photograph (according to their convenience). They can interact with each-other virtually. Even their
parents can also handle their websites and receive mails of matching profiles.

Why is it?

My project “Matrimonial Website” is a virtual marriage website, is a real-time project to create

efficient software for online marriage. The website is designed to provide detailed information about the
person you are interested in for marriage. Online Matrimonial website provides the efficient amount of
details you need to know about someone with whom you can plan your future.

What problem does it soh e?

Old people know what life was like before the internet. When there were no internet connectivity,
matchmaking happened exclusively through middle-aged and aged women and men who made it their
business to find others, wives and husbands. They were good at this as they kept their ears to ground and
knew the ongoing of unmarried men and women. They used take photographs and bio-data of 5-6 youths
and used to visit houses.

But now when approx. 80% of the businesses, and markets have gone online. The need of those
middle-men has almost ended. Now everybody wants to keep their life private and don’t want to share
their plans with others. The advantage of using an online senice is it is more relevant for the person looking
for a life-partner.

Technical Overview:-
Descriptiou

In this project, we took the challenge to make a platform for young people where they can find their
perfect match just by scrolling through our website. There are three levels of roles with different levels of
control over the system:
-Role Admin

-Role user

Roles Overview

A brief overview of roles and level of control:-

> Admiu:-

The Admins will have the access to manage the details of the male, female, education, and
lifestyle. He will manage all the information about registered candidates. The project is totally built at the
administrative end, thus only the administrator is guaranteed access.

> User:-

The user will not have administrator access. He/she can only manage their data. Some functionalities
that they get are :- changing their display picture, searching for the male/female with many filtering and
sorting options, editing bio-data, adding and removing hobbies etc.

Prerequisites:-

List of dependencies you need before you run the project

-Language Used: PHP 7

-Database Used: MySQL

-User Interface Design: HTML, CSS

-Software: XAMPP/ WAMP/ MAMP/ LAMP (Anyone)

Installation
Step 1: Clone the Repositoiy.
Step 2: Exti'act the Folder into your XAMPP /litdocs/ Location Step 3: Open
XAMPP and Start Apache and MySQL
Step 4: Go to PHPMyAdiniii via http://localliost/phpmyadmiii/ Step 5: create a
new Database named MATRINIONY-sys Step 6: Click on MATRIMONY_sys

2
Database and Find Option called Impoit Step 7: Impoit File Database for COVID-
19 vaccination System. SQL Step 8: Go to http://localliost/ /
Step 9: login using the Admin Credentials ca tell them a tcli@gm ail, co m and
pass: 112233.

All done now. you are good to go!

1. Introduction

2. Initial requirement

3. System analysis
 3.1- Objectives

3.2- Existing System Description

33- Proposed System

3.4- Feasibility study with report

4. Software requirement specification

4.1- Objective

4.2- Scope

43- Requii'ements

43.1- F imctional requii'ement

43.2- Security requii'ement

4.4- Software requii'ements

4.5- Hardware requii'ement

4.6- Module description

5. System design

5.1- Software process model

5.2- Design approach

6. High level design

6.1- Data flow diagram

1
1
1. Iutroductiou

The matrimonial web application is a platfbnn where users can find their lifelong partners. The
users may register themselves, fill in their interests and view a list of other profiles with
matching interests. The main advantage of this application is that it facilitates easy interaction between
people looking to get married. The user needs to register and verify themselves before
using the website. The verification will be simple yet effective. The main obj ective of the Matrimonial
Web Application is to provide the bride and groom with an excellent matchmaking
experience by exploring the opportunities and resources to meet a true potential partner, the
content with your own material. Your introduction should clearly identify the subject area of

2. Purpose:-
The main purpose of this application is to facilitate matchmaking business by applying the information in
the field. It helps the user by providing profiles of perspective “Bride” and “Groom” and other information
regarding them onhne. The users can get information regarding their dream life partner at his/her home at
his/her convenience. This application also provides a search utility which helps those users who have a
certain criteria of qualities in mind to make onhne matrimonial easier. Since the internet is a pivot for
modem business, our project, which is based on the internet, paves a path for modernization.

What is a matrimonial website all about?

A matrimonial website is a platfonn where all married people seeking alliances meet, exchange infonnation
and find a perfect life-partner across the globe. One can find his/her prospective partner as per their choices
and remove problems that arise due to traditional methods for finding partners. Based on marriage seeking
registrations, a potential match is found and alerted to registered persons accordingly. This is the best
solution if you are looking to run a marriage sendees website. We have integrated many features which you
can use and take full advantage of

1
2
the marriage services. This is a very powerful onhne family management package system that we've developed
exclusively and user is friendly.

Interface Software Services has developed the perfect online engine for matrimonial agencies to get onhne with
business in less than four weeks. Our matrimonial web site development tools and integrated administrative software,
offers extensive control and flexibility to webmasters. The complete marriage web site manager includes features for
three types of users.
1. Visitors 2. Registered Members 3. Administrators 4. Moderators

1
3
 Hardware Requiremeut
Hard disk : 500GB

RAM : 16GB

Processor : Intel(R) Core(TM) i7-7700HQ CPU3.8GHZ

System type : 64-bit Operating System

Interface : Keyboard: Mouse: Display devices

Software Requiremeuts
Operating System : Window 10 (Genuine)

Operating System type: 64-bit OS

Web Designing : HTML: CSS: BOOTSTRAP

Client Side Scripting : Java script

Server Side Script
PHP 5.3.13 (Hypertext Pre-Processor)
:
Web Server : Apache 2.2.22

Database : MySQL 5.5.24

Web Browser : Google Chrome: Microsoft Edge

Editors VS Code

14
1
7
1. The main objective of Matrimonial Website is to provide grooms and brides with excellent match-making
experience by exploring the opportunities and resources to meet true potential partner. Keeping our objective in
mind: we have created a world-renowned match-making service that will touch the souls ofmilhons of people all over
the globe.

2. The Matrimonial Web Application will allow a new user to register and after successfully registration: user can
get an email confirmation: After completing registration: users' profile will be visible to other users.

3. To offer suggestions on a real-time basis and recomm end appropriate profiles to its members: thereby enhancing
their experience and helping them find a match based on their preferences. We have also deepened behavior-based
penalization. To improve engagement on our platform

3.2:- Existing System Description

Existing matrimonial systems are developed to search out the match between bride groom as per their age ： faith or
caste.Nowadays ： a lot of Matrimonial consultancies are listed. Most of these compani es work manually without
the help of a system. Checking of existing records, editing and other repositioning are done manually. It’s a time
consuming-process.

In today’s digital age ： people still tend to believe in the old agetraditions of
finding a partner. They meet a stranger who their parents hke and agree to spend the rest of their lives with them. A
relationship based on the couple’s mutual interests ： likes ： dislikes ： preferences: taste ： etc. tends to be an
everlasting bond between them. The stronger their bond： the more they grow in every way possible.

3.3:- Proposed system

The proposed system is designed to provide a chance to meet with serious alliance seekers. Matrimonial sites are not
like dating sites. They work with a serious puipose ： therefore only genuine members who are serious about finding
their life partners register their profiles with
1
9
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. Developer’s Requirement

Fii'st of all. the developer needs to know about the table schema. Entity-
Relationsliip Diagiam with the correspondent Data flow Diagiam. Tliese
documents are veiy necessaiy for the developer who is going to develop this
project

System Requirement

Hardware Requirement:

Haid disk :
RAM : 500GB
Processor : 16GB
Intel(R) Core(TM) i7-7700HQ CPU
System type : 3.8GHZ
64-bit Operating System Keyboai'd.
Iiiteiiace :
Mouse. Display devices

Software Requirements:

Operating System :
Window 10 (Genuine)
Operating System type:
64-bit OS

2
9
 Web Designing : HTML. CSS. BOOTSTRAP

Client side Scripting : Javasciipt

Seiver Side Script : PHP 5.3.13 (Hypertext Pre-Processor)

Web Server : Apache 2.2.22

Database : MySQL 5.5.24

Contiol Panel : XAMPP 2.2

Web Browser : Google Chrome. Microsoft Edge

Editors : Notepad++. Bracket 1.9.0 .VSCode

ECONOMICAL FEASIBILITY

As part of this, the costs and benefits associated with the proposed system are 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.. Since this project is developed for
academic puiposes, there is no need for financial stability in my project.

OPERATION AL 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.

Since this project is veiy small and it is developed for academic purposes, operational
feasibility is not required.

User’s System requirement

2
1
Software Requirement-

The User interface would be used to provide information necessary to generate a new claim also update information.

<• Operating System : Window/Android'Mac

<• Web Browser : Google Chrome'Microsoft Edge

Hardware Requirement

RAM 1GB

Hard Disk 10 GB

Display Devices : Di splay.'Print er

Processor AMD.INTEL/SNAP- DRAGON
:

2
2
4:- Software Requirement Specificatiou:-

A requirements specification for a Sofhvare System — is a complete description of the behavior of a system to be
developed. It includes a set of used cases That describes all the interactions the users will have with the software. In
addition to use cases: the SRS also contains non-functional (or supplementary) requirements. Non-fiinctional
requirements are requirements which impose constraints on the design or implementation (such as performance
engineering requirements, quality standards, or design constraints).

Requirement documentation is very important activity after the requirements ehcitation and analysis. This is the way
to represent the requirements in a consistent fonnat. This requirement document is called Software Requii'ement
Specification (SRS).

The software requirement specification is produced at the culmination of the analysis task.
This is the way to represent requirements in a consistent fonnat. It is a specification for a particular software
product, program or a set of programs that perform certain functions in a specific environment .The
functions and allocated to software as part of system engineering are refined by establishing a complete
infonnation description, a detailed functional and behavioral description, an indication of performance
requirements and design constraints, appropriate validation criteria, and other data pertinent to
requirements.
Software product, program or set of programs that perform certain functions in a specific environment.
There are two important cases regarding SRS: first one, SRS is used to define the needs and expectations of the users.
The second one, SRS, is written for different purposes and serves as a contract document between customer and
developer. This produces the probability of the customer being disappointed with the final product.
 Improved Network Performance.

Enhanced communication features.

4.1 - Objective:

A software requirement specification is literally the conversation of a specific point. It's difficult in
this instance to avoid the circular reference. A project's specifications consist of the body of information
that should guide the project developers, engineers, and designers through the work of creating the
software.
A software requirement specification document describes how something is supposed to be
done. A specifications document may list out all of the possible error states for a certain fonn, along with
all of the error messages that should be displayed. The specifications may also describe the steps of any
functional interaction, and the order in which they should be followed by the user. A requirements
document, on the other hand, would state that the software must handle error states reasonably and
effectively, and provide explicit feedback to the users.

4.2 - Scope:

The boundaries of software products are defined by a set of requirements. The software
development team designs, implements, tests, and delivers these requirements to you. A Requirem ent is an
atomic unit of a software product from the viewpoint of the user. As a rule, requirements are always
correct, unambiguous, verifiable, and traceable. Requirements are numbered and prioritized.

All Functional Requirements are then listed in a requirements attributes spreadsheet, where all necessary
attributes for each requirement are maintained. Changes to the project scope can be made only by issuing
new Specifications through a process called Change Requests. Each Change Request implies that changes
will be made to the Budget, Schedule, and Risks.

This project is most functional and easy to use solution for prioritizing, planning, managing and executing
projects. This project can be used in educational institutions where an analysis of various projects allotted
to various scholars is necessary, and also in MNC’s with shght modification to judge the performance of
employees. One can also gain some experience based on earlier projects in his upcoming assignments

2
7
4.3 - Requirements:

The software requirements specification is produced at the culmination of the analysis task. This is the way
to represent requirements in a consistent fbnnat. It is a specification for a particular software product .
program or a set of programs that perform certain functions in a specific environment .The functions and
allocated to software as part of system engineering are refined by establishing a complete infonnation
description, a detailed functional and behavioral description, an indication of perfonnance requirements
and design constraints, appropriate validation criteria, and other data pertinent to requirements.

4.3.1- Functional and On-Functional Requirements 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-fimctional needs place constraints on however the system can do,
therefore.
Practical needs specify an operation that a system or system part should be ready to perform.
It will be documented in varied ways in which, the foremost common ones are written descriptions
in documents and use cases.

A few of its practical needs are as given below：- Login Module:

2
8
Introduction:
Licensed users are allowed to access.

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

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

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

Registration module:
Introduction:
Solely Admin will access the page.

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

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

Output:
Worker gets theusemame and positive identification.

Report Module:
Introduction:
Solely Admin will access the page and check the report.

Input:
Bridegroom.

2
9
to data: provide different kinds of access requirements for different people : require the use of passwords
and cryptography techniques, and maintain a log of activities in system. Given the current security needs
even of common systems, they may also require proper assessment of security threats, proper
programming techniques: and use of tools to detect flaws like buffer overflow.

For the purpose of security process, I have added the login feature into my proj ect so as to keep it safe
from external problems. One can only interact with my project by giving it the suitable i.e. the accurate ID
and password.

4.4- Software Requirement

Software requirements play a very important role in the making and

development of a project, as it provide a suitable language as well as the perfect medium to implement our
program or project on the system, software requirement is very necessary for the implementation of a
program.

The Software requirements specification is produced at the culmination of the analysi s task. This is the
way to represent requirements in a consistent fonnat. It is a specification for a particular software product,
program or a set of programs that perform certain functions in a specific environm ent .The function and
allocation to software as part of system engineering are refined by establishing a complete information
description, a detailed functional and behavioral description, an indication of performance requirements
and design constraints, appropriate validation criteria, and other data pertinent to requirements.

Software product, program or set of programs that perform certain functions in a specific environment.
There are two important cases regarding SRS: first one, SRS is used to define the needs and expectations
of the users. The second one. SRS, is written for different purposes and serves as a contract document
between customer and developer. This produces the probability of the customer being disappointed with
the final product.

4.5- Hardware Requirement

The hardware requirements specification is produced at the culmination of the analysi s task. This is the
way to represent requirements in a consistent fonnat. It is a specification for a

3
1
particular hardware product, program or a set of programs that perform certain functions in a specific
manner.
In the designation of my proj ect hardware requirement is also very necessary •

Software Requirement Specification of my Matrimonial 'vebsite:-

-Y> Functional requii'ements of my Matrimonial Web site

Functional requirements capture the intended behavior of the system. This behavior may be expressed as
services: tasks or functions of the system is required to perform. This white sheet lays out important
concepts and discusses capturing functional requirements in such a way that they can drive architectin’al
decisions and be used to validate the architecture.

The following is a running list of possible Matrimonial Sy stem:-

1. Supports the activation of users.

2. Supports search and views profile.

3. Supports sending mail to an interesting profile.

4. Support knowing the profile-statistics.

5. Supports knowing who saw your profile.

Technical Specification

Security Requirement for COVID-19 Vaccination Management System :

The Matrimonial website is a project that will be run over the internet. So it is very necessary to

3
2
make this proj ect secure to prevent the accessibility of unwanted hackers or users. This project also
includes a Database that contains some sensitive information about users who have registered into our
website and our developers . That record must not be accessible by any other user. When a user is able to
access someone else's account, then heshe will be able to send messages to any profile and also be able to
leave any type of reply to the questions that can be dangerous for anyone who is part of this website. So in
this proj ect: the database will require more security.

There are some features that will require more security in this project : are listed below.

• Log in: Users should not be able to log in without having an existing account in this database. If
users does not have any existing account then he'she have to create his/her account by going
through the registration process.

• Profiles: Users will not be able to see other's profile without logging in.

• Wrong password: In case user have given three times wrong pas sword : an email will be sent to
their mail account which they have mentioned at the time of registration.

Output Requirement for Matrimonial Website:-

This web based project will be run on a browser. So at least one output device will be required to view the
pages to view the results of this project that will be ejected on the output screen. Some more output
requirements are given below.

• Background color- The background color of this website should be light in comparison to the
foreground color. “Sky blue" is the recomm ended color for the background.

3
3
• Font details- Font size must be 12px for the paragraphs and 16px for the title of the paragraph. Font style
should be the same on each and every page. The recomm ended font style is "Arial" for this project.

• Navigation Bar- Navigation bar should be on top of the web page. For small size screens : the navigation bar
can be maximized and minimize.

• Logo- Logo of the website must be present on each and every page. It should be small in size (height lOOpx
and width 200px).

• Responsive- All the web pages must be readable and look attractive on all screen size
devices.
3
5
4.6- Mo(hile Description

1. Admin
2. Members

Features of Admin
The admin is a superuser that have access to everything.

1. He can view User details

2. He can block or unblock a user
3. He can edit user det ails: family det ails: partner preferences
4. He can even delete a user

Members

1. Enter Personal details

2. Enter Family Details
3. Enter Partner Preferences
4. Now You will be logged in and at your dashboard you will see the list of all users of opposite sex.
5. In the left sidebar, you will find a section named as “My Matches '.
6. This section contains all the members based on your partner preferences.
7. Also you can send invitation to other users and if the user accepts your invitation you can send message to
each other.
8. Also a user can search other users in three ways .
9. We have advance search Features.
10. We have simple search features
11. We have search by ID features.
5 -System Design

System Design is the process of designing the architecture, components : and interfaces for a system so that
it meets the end-user requirements.

It’s a 'vide field of study in Engineering and includes various concepts and principles that will help you in

designing scalable systems. All these decisions are required to be taken carefully keeping in mind S cal

ability; Reliability, Availability, and Maintainability. System design goes through two phases of

development:

1. Logical Design
2. Physical Design
A data flow diagram shows the logical flow of the system. For a system it describes the
input (source), output (destination), database (data stores), and procedures (data flows) all in a fonnat that
meets the user requirements. When analysis prepares the logical system design, they specify the user needs
at a level of detail that virtually determines the infonnation flow into and out of the system and the
required data resources.

5.1- Software process model:- WATERFALL MODEL:-

The waterfall model is a popular version of the systems developm ent life cycle model for software
engineering. Often considered the classic approach to the systems development life cycle, the waterfall
model describes a development method that is hnear and sequential. Waterfall development has distinct
goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the water
has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it cannot
turn back. It is the same with waterfall development. Once a phase of development is completed, the
development proceeds to the next phase and there is no turning back.

The advantage of waterfall development is that it allows for departmentalization and managerial control. A

schedule can be set with deadhnes for each stage of development and a product can proceed through the

development process. Theoretically, be delivered on time. Development 38

3
9
moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at
operation and maintenance. Each phase of development proceeds in strict order, without any overlapping
or iterative steps.

The disadvantage of waterfall development is that it does not allow for much reflection or
revision. Once an application is in the testing stage, it is very difficult to go back and change something
that was not well-thought out in the concept stage. Alternatives to the waterfall model include joint
application development (JAD), rapid application development (RAD), synchronize and stabilize, build
and fix problems.

The waterfall model is a sequential design process, often used in software development processes,
in which progress is seen as flowing steadily downwards(like a waterfall).
4
1
5.2 -Design Approach:-

TOP DOWN DESIGN:-

The TOP DOWN approach starts from the highest level component of the hierarchy and proceed through to lower
levels. A top down design approach start by the maj or component of the system. Decomposing them into their lower
level component and iterative until the desired label of detail is achieved. Top down design method is in some fonn
of step wise refinement. Starting from a abstract design in each step the design is refine to more concrete level, until
we reach a level were no more refinement is needed.

A system consists of components, which have components of their own; indeed a system is a hierarchy of
components. The highest level component correspond to the total system. The top down approach from the highest
level component of hierarchy and proceeds through to lower levels. By contrast a bottom up approach starts with the
lowest level component of the hierarchy and proceeds through progressively higher levels to the top level
components.

The top down approach has been promulgated by many researches and has been found to be extremely useful for
design. Most design methodologies are based on the top down approach.

A top down approach suitable only if the specifications of the systems are clearly known and the system developm
ent is from scratch. However : if a system is to be built from an existing system, a bottom approach is more suitable :
as it starts from some existing components.
6.1 -Data Flow Diagram:-

The DFD was first developed by LARRY CONSTANTINE as the way of expressing system requirement
in a graphical fonn. A DFD is known as BUBBLE CHART has the purpose of clarifying system
requirement and identifying major transformation that will become programs in system design.So it is the
starting point of the design phase that functionally decompose the requirements specification down to the
lowest level of de Data Flow Diagram are commonly used during problem analysis. Data
DFDs are very useful in understanding a system and can be effectively used during analysis .A
DFD shows the flow of data through a system. It views as a function that transforms the input into
desired outputs. The DFD aims to capture the transformations that take place within a system to
input data so that the output data is produced.

Symbol Name Description

It is represented by a rectangle and simply depicts a source or

Entity
termination of the diagram by mapping real-world entities.

— It is represented by a circle and depicts how the data is handled

Process
and processed in the system.

Data It is represented by two parallel lines and depicts a location

Store where data is stored in the system.
Data It is represented by directional lines and depicts the flow of data Flow from one location to
another.
Matrimonial website Level 0 DFD

2
5
ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram that displays the
relationship of entity sets stored in a database. In other words, ER diagrams help to explain the logical
structure of databases. ER diagrams are created based on three basic concepts: entities : attributes and
relationships.

ER Diagrams contain different symbols that use rectangles to represent entities : ovals to define attributes and
diamond shapes to represent relationships.

At first look: an ER diagram looks very similar to the flowchart. Ho'vever: ER Diagram includes many
specialized symbols, and its meanings make this model unique. The purpose of ER Diagram is to represent
the entity framework infrastructure.

ER Model stands for Entity Relationship Model is a high-level conceptual data model diagram. ER model
helps to systematically analyze data requirements to produce a well-designed database. The ER Model
represents real-world entities and the relationships between them. Creating an ER Model in DBMS is
considered as a best practice before implementing your database.

ER modelling helps you to analyze data requirements systematically to produce a well-designed database. So :
it is considered a best practice to complete ER modeling before implementing your database.

2
7
The basic symbols used for tlie E-R constructs are:

Notation Use Symbols

Linking
attributes to
Lines
entity sets to
relationship sets

Ellipse
Representing
attributes
C)
Representing
Rectangle
entity set

(>
Represent
Diamond
relationship

Represents
Nested
multi valued
Ellipse
attribute
Dotted Represents
Ellipse derived
\ > ________
attributes

Represents
Nested
weak
Rectangle
entities

Line with Represents

in key ◦
Ellipse attribute

Double Represents

Lines total

relationship

Represents
Ellipse and
composite
Lines
attributes

Nested Represents

diamond identifying

relationship

2
9
3
0
 Represent

is a / has a
Triangle
relationship

Keys:

A key is a value which can always be used to uniquely identify an object instance. It becomes important to invent a
method to distinguish entity and relationships. The differences between entities must be expressed in terms of
attributes.

Super Key:

A Super Key is a set of one or more attributes which : taken collectively, allows us to identify uniquely an entity in
the entity set.

Candidate Key:

An attribute that uniquely identify a row is called Candidate Key. Candidate key is also referred to as Surrogate
keys.

Primaiy Key:

A candidate key to choose to identify rows uniquely is called a Primary key.

Alternate Key:

If there are multiple candidate keys in a table : then the keys which are not chosen as primary key will be called as
alternate key.

Composite Keys:

When the key that uniquely identifies the rows of the table is made up of more than one attribute it is called a
composite key.

3
1
ER Diagram for Matrimonial Website

3
5
Table schema

1. Religion
Constraint Name Type Reference Table (if any) Remarks

Religi on_ID Primary Key Unique

Column Name Data Type Width Not NuU Description

Religion Varchar 30 Yes Name Of Religion

2. Caste
Constraint Name Type Reference Table(if any) Remarks

CastelD Primary Key Unique

ReligionlD Foreign Key Religion

Column Name Data Type Width Not NuU Description

CastelD Int 4 Yes Identification

Caste Varchar 20 Yes Name Of Caste

ReligionlD Varchar 30 Yes Name Of

Country

3. Education:-
Constraint Name Type Referen e Table Remarks
c

(if any)
EducationlD Primary Key Unique

Column Name Data Type Width Not NuU Description

EducationlD Int 4 Yes Identification

 Education Varchar 30 Yes Name Of Education

4. Country

Constraint Name Type Reference Table (if any) Remarks

Country ID Primary Key Unique

Column Name Data Type Width Not Null Description

Country ID Int 4 Yes Identification

Country Varchar 30 Yes Name Of Country

5. State:-

Constraint Name Type Reference Table(if any) Remarks

StatelD Primary Key Unique

Country ID Foreign Key Country

Column Name Data Type Width Not NuU Description

StatelD Int 4 Yes Identification

Country ID Int 4 Yes Country

Identification

Country Varchar 30 Yes Name Of State

3
7
6. City:-

Constraint Name Type Reference Table Remarks

(if any)

CitylD Primary Key Unique

Country ID Foreign Key Country

StatelD Foreign Key State

Column Name Data Type Width Not Null Description

CitylD Int 4 Yes Identification

City Name Varchar 30 Yes Name Of City

Country ID Int 4 Yes Country Identification

StatelD Int 4 Yes State Identification

7. Citizeuship:-

Constraint Name Type Reference Table (if Remarks

any)

CitizenlD Primary Key Unique

Column Name Data Type Width Not NuU Description
CitizenlD Int 4 Yes Identification
Citizen Varchar 30 Yes Name Of Citizenship

3
8
 8. Bloo(l Group

Constraint Name Type Reference Table (if Remarks

any)

BloodID Primary Key Unique

Column Name Data Type Width Not NuU Description
BloodID Int 4 Yes Identification
BloodGroup Varchar Yes Name OfBlood Group
8

9. Lauguage:-

Constraint Name Type Reference Table (if Remarks

any)

LangID Primary Key Unique

Column Name Data Type Width Not NuU Description
LangID Int 4 Yes Identification
Language Varchar 30 Yes Name Of Language

3
9
 10. Occupation:-

Constraint Name Type Reference Table (if Remarks

any)

OccupationlD Primary Key Unique

Column Name Data Type Width NotNuU Description
OccupationlD Int 4 Yes Identification
Occupation Varchar 30 Yes Name Of Occupation

11. Heights

Constraint Name Type Reference Table (if Remarks

any)

Height ID Primary Key Unique

Column Name Data Type Width Not NuU Description
Height ID Int 4 Yes Identification

a
o
12. Registratiou:-

Constraint Name Type Reference Table (if Remarks

any)
RegistrationlD Primary Key Unique

ReligionlD Foreign Key Religion

CastelD Foreign Key Caste

Country ID Foreign Key Country

StatelD Foreign Key State

CitylD Foreign Key City

CitizenlD Foreign Key Citizenship

EducationlD Foreign Key Education_Category

BloodID Foreign Key Blood_Group

LangID Foreign Key Mother_Tongue

OccupationlD Foreign Key Occupation

Height ID Foreign Key Height

Column Name Data Type Width Not NuU Description

RegistrationlD Int 4 Yes Identification

Name Varchar 50 Yes Name

Age Int 4 Yes Age

Gender Varchar 10 Yes Gender

Marital_Status Varchar 20 Yes Marital Status

NoOLChildren Int 4 Yes No OfChildren

LivingStattus Varchar 20 Yes Living Status

ReligionlD Int 4 Yes Religion ID

CastelD Int 4 Yes Caste ID

S
1
Country ID Int 4 Yes Country ID

StatelD Int 4 Yes State ID

CitylD Int 4 Yes CitylD

CitizenlD Int 4 Yes Citizen ID

EducationlD Int 4 Yes Education ID

BloodID Int 4 Yes Blood ID

LangID Int 4 Yes Lang ID

OccupationlD Int 4 Yes Occupation ID

Height ID Int 4 Yes Height ID

Resid_Status Varchar 20 Yes Residentail Status

Employ Bit 1 Yes Employm ent

Email Varchar 50 Yes Email ID

Usemame Varchar 20 Yes Usemame

Password Varchar 20 Yes Password

Weight Varchar 20 Yes Weight

Complexion Varchar 20 Yes Complexion

Eating Habits Varchar 20 Yes Eating Habits

Sub caste Varchar 50 Yes Sub Caste

Horos_Match Varchar 20 Yes Horoscope Match

Address Varchar 50 Yes Address

Phone Int 8 Yes Phone

Mobile Int 8 Yes Mobile

Aboutme Varchar 100 Yes About me

ProfileFor Varchar 25 Yes Profile For

ProfileBy Varchar 25 Yes Profile By

FamilyType Varchar 50 Yes Family Type

FamilyStatus Varchar 50 Yes Family Status

S
2
NoOfSiblings Int 10 Yes No of Siblings

RegDate Date 8 Yes Registration Date

VisitCount Int 4 Yes Visits Count

Int_Sent Int 4 Yes Interest Sent

Int_Recieved Int 4 Yes Interest Recieved

Status Varchar Yes Status

20

S
3
13. Logiu Summarv:-

Constraint Name Type Reference Table (if Remarks

any)

RegID Foreign Key Registration Unique

Column Name Data Type Width Not NuU Description
RegID Int 4 Yes Identification
Login_Date Date 8 Yes Login Date
Login_Time Varchar 10 yes Login Time
Status Varchar 10 Yes Login Status

14. Photos:-

Constraint Name Type Reference Table (if Remarks

any)

Photo ID Primary key Unique

RegID Foreign Key Registration Unique
Column Name Data Type Width Not Null Description
Photo ID Int 4 Yes Photo ID
Photo Varchar 50 Yes Photo
PhotoDesc Varchar 25 yes PhotoDesc

RegID Int 4 Yes RegID

54
15. Interest Recieved:-

Constraint Name Type Reference Table (if Remarks

any)

RegID Primary key Unique

RegID Foreign Key Registration
FromReglD Foreign Key Registration
Column Name Data Type Width NotNuU Description
RegID Int 4 Yes RegID
RegID Int 4 Yes RegID
FromReglD Varchar 4 yes From RegID
Message Varchar 50 Yes Message

16. Interest Sent

Constraint Name Type Reference Table (if Remarks

any)

SendID Primary key Unique

RegID Foreign Key Registration
ToRegID Foreign Key Registration
Column Name Data Type Width Not NuU Description
SentID Int 4 Yes Sent ID
RegID Int 4 Yes Reg ID
ToRegID Int 4 Yes To Reg ID

Message Varchar 50 Yes Message

3
5
Low level design

The LLD stands for Low-Level Design, in which the designer will focus on the components hke a User interface
(UI).

The Low-level design is created by the developer manager and designers.

It is also known as micro-level or detailed design. The LLD can change the High-Level Solution into a detailed
solution.

The Low-level design specifics the detailed description of all modules : which implies that the LLD involves all the
system component's actual logic. It goes deep into each module's specification.

The Low-level design is created after the High-Level Design.

Modulation
A system is considered modular if it consists of discrete component show that each component can be implemented
separately, and a change to one component has minimal impact on other components.

Structure chart
The structure chart is one the most commonly used methods for system design, structures charts are used during
architectural design to document hierarchical structure : parameters and interconnection in a system.