Académique Documents
Professionnel Documents
Culture Documents
PORTAL
Submitted by:
Jose joy
Jiss George
St.Michaels
college
Divine
jose
Cherthala
PROJECT REPORT
INTRODUCTION
What is Matrimonial Web Application?
The main objective of Matrimonial Web Application is to provide Grooms and Brides
with excellent matchmaking experience by exploring the opportunities and resources to meet true
potential partner. Keeping our objective in mind, we have created a world renowned online
matchmaking services that will touch the souls of millions of people all over the globe.
It helps the user by providing profiles of perspective Bride or Groom and other
information regarding them online.
User 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 online matrimonial easier.
Since internet is a pivot for modern business, our project which is based on internet
paves a path for modernization in trade.
Matrimonial Web Application will allow a new user to register and after successfully
registration user can get email confirmation, after completing registration users profile will be
visible to other users.
Matrimonial website whichis provide platform to a lot of Bride/Groom for finding their
perfect match. There are different sectors like Registration, Partner, Search, etc. So the
Bride/Groom can get their interest for find their partner. Bride/Groom can directly search Partner
according to their required criteria. The Bride/Groom can use match By Email functionality so
he/she can get directly E-mail alert for the match which fulfill their required criteria.
(11)
Creating album
(12)
(13)
(14)
(15)
Paid Membership
(16)
Search Module.
(17)
The application will have to be completed using Visual Studio 2008 and SQL Server 2008R2
with help of other office productivity tools.
The application testing criteria and installation requirements will be part of the detailed
application architecture document.
PROJECT LIFECYCLE
MODEL
SPIRAL MODEL:
The spiral model is a software development process combining elements of both design and
prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts.
Also known as the spiral lifecycle model (or spiral development), it is a systems development
method (SDM) used in information technology (IT). This model of development combines the
features of the prototyping and the waterfall model. The spiral model is intended for large,
expensive and complicated projects.
The Model:
The spiral model combines the idea of iterative development (prototyping) with the systematic,
controlled aspects of the waterfall model. It allows for incremental releases of the product, or
incremental refinement through each time around the spiral. The spiral model also explicitly
includes risk management within software development. Identifying major risks, both technical
and managerial, and determining how to lessen the risk helps keep the software development
process under control.
The spiral model is based on continuous refinement of key products for requirements definition
and analysis, system and software design, and implementation (the code). At each iteration
around the cycle, the products are extensions of an earlier product. This model uses many of the
same phases as the waterfall model, in essentially the same order, separated by planning, risk
assessment, and the building of prototypes and simulations.
The spiral lifecycle model allows for elements of the product to be added in when they become
available or known. This assures that there is no conflict with previous requirements and design.
This method is consistent with approaches that have multiple software builds and releases and
allows for making an orderly transition to a maintenance activity. Another positive aspect is that
the spiral model forces early user involvement in the system development effort. For projects
with heavy user interfacing, such as user application programs or instrument interface
applications, such involvement is helpful.
Starting at the center, each turn around the spiral goes through several task regions:
Project profile
Project Title
Objective
Of
System
Operating
Systems
Hardware
Requirement
Software
Requirement
Front End
Back End
:
:
Others
Microsoft Visio
.Net Framework
PURPOSE:
Matrimonial website which is provide platform to a lot of Bride/Groom for finding perfect
match. There are different sectors like Registration, Login, Search, etc. So the Bride/Groom can
get their interest for find their partner. Bride/Groom can directly search Partner according to their
required criteria. The Bride/Groom can use match By Email functionality so he/she can get
directly E-mail alert for the match which fulfill their required criteria.
It helps the user by providing profiles of perspective Bride and Groom and other
information regarding them online.
User 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 online matrimonial easier.
Since internet is a pivot for modern business, our project which is based on internet paves
a path for modernization in trade.
System
Technology
Language
Database
TECHNOLOGY AND
HARDWARE USED
Thread Management
Code Verification
Remoting
All .NET applications are compiled into Intermediate Language code (MSIL). When
executed on the CLR, MSIL is converted into native machine code specific to the operating
platform. This process is done by a Just in Time (JIT) compiler. The code executed by the CLR is
called as Managed Code. This code is type safe and thoroughly checked by the CLR before being
deployed. The .NET runtime also provides a facility to incorporate existing COM components
and DLL's into a .NET application. Code that is not controlled by the CLR is called Unmanaged
Code.
The .NET Framework is further comprised of Common Type System (CTS) and Common
Language Specification (CLS). The CTS defines the common data types used by .NET
programming languages. The CTS tells you how to represent characters and numbers in a
program. The CLS represents the guidelines defined by for the .NET Framework. These
specifications are normally used by the compiler developers and are available for all languages,
which target the .NET Framework.
Introduction to ASP.NET:
Features of ASP.NET:
(1) Component Infrastructure.
FEASIBILITY STUDY
FEASIBILITY STUDY:
Feasibility study is a process to check possibilities of system development. It is a method to
check various different requirements and availability of financial & technical resources.
Before starting the process various parameters must be checked like:
All the above conditions must be satisfied to start the project. This is why in depth analysis of
feasibility is carried out.
There are three different ways feasibility can be tested:
1) Economical Feasibility
2) Technical Feasibility
3) Operational Feasibility.
Economical Feasibility:
In economic feasibility, analysis of the cost of the system is carried out. The system
should be only developed if it is going to give returned the current manual system
user can get the price only by purchasing the newspapers. In addition if he/she wants
to see archives of particular equity then he has to refer to all the old newspapers. For
research reports he has to buy another magazine. So Instead of buying no of
magazines user has to just go online and with a single click he can get whatever
information he wants. So our project of online share news passes the test of economic
feasibility.
Technical Feasibility:
It is basically used to see existing computer, hardware and software etc., weather it
is sufficient or additional equipments are required? Minimum System Requirement
is such that it can be affordable by of the user who is having computer. All the user
requires is compatible browser and .net framework installed so our system is fully
technical feasible.
Operational Feasibility:
Once the system is designed there must be trained and expert operator. If there are
not trained they should give training according to the needs of the system.
From the users perspective our system fully operational feasible as it just
requires some knowledge of computer. Operators only need add daily prices of
various equities and there are enough validations available so operator does not
require any special technical knowledge. So our system also passes the test of
operational feasibility.
Tier 1
Presentation
Tier
Tier 2
Database Tier
Database Access
TABLE DESIGN
TABLE DESIGN
Table:admin_login
Data
type
Field Name
Null
Description
Lid
Int
No
User_nm
Varchar
No
Password
Varchar
No
Table:Bank_Details_cc
Data
type
Field Name
Null
Description
Cc_id
Int
No
Stores the id
Card_no
Varchar
No
Card_type
Varchar
No
Card_exp_month
Varchar
No
Card_exp_year
Varchar
No
Pin_code
Varchar
No
Name_on_card
Varchar
No
Credit_limit
Numeric
No
Avail_bal
Int
No
Table:Chat_Box
Data
type
Field Name
Null
Description
To_uid
Varchar
No
From_uid
Varchar
No
Messages
Varchar
Yes
Table:Contact_us
Data
type
Field Name
Ct_id
Int
Null
No
Description
Stores the contact id
Name
Varchar
No
Mobile
Varchar
No
Email id
Varchar
No
Details
Varchar
Yes
Ct_date
DateTime
No
Table:Express_interest
Field Name
Data
type
Null
Description
To_uid
Varchar
No
From_uid
Varchar
No
Messages
Varchar
Yes
Table: feedback
Field Name
Data
type
Null
Description
fd_id
Varchar
No
Name
Varchar
No
Comment
Varchar
Yes
Feed_date
Datetime
No
Table:image_gallery
Data
type
Field Name
Null
Description
Img_id
Int
No
Images
Varchar
No
Pro_id
Int
No
Table: Profile
Data
type
Field Name
Null
Description
pro_id
Int
No
Profile_creator
Varchar
No
Names
Varchar
No
Marital_status
Varchar
No
Body_type
Varchar
No
Age
Varchar
No
Physical_status
Varchar
No
Height
Varchar
No
Weight
Varchar
No
Mother_tongue
Varchar
No
Religion
Varchar
No
Caste
Varchar
No
Gothram
Varchar
No
Zodiac
Varchar
No
Star
Varchar
No
Eating_habit
Varchar
No
Drinking_habit
Varchar
No
Smoking_habit
Varchar
No
Country
Varchar
No
City
Varchar
No
State
Varchar
No
Education
Varchar
No
Occupation
Varchar
No
Employeed_in
Varchar
Yes
Salary
Varchar
No
Mobile_no
Varchar
No
Images
Varchar
No
About_me
Varchar
Yes
Require_details
Varchar
Yes
Membership
Varchar
No
Paid_status
Varchar
No
Start_date
Varchar
No
End_date
Datetime
No
Email_id
Varchar
No
Password
Varchar
No
Gender
Varchar
No
Profession
Varchar
No
Address
Varchar
No
Pincode
Varchar
No
Phoneno
Varchar
No
Paid_date
Datetime
No
Login_status
Int
No
Table:Search_setting
Data
type
Field Name
Null
Description
Pro_id
Int
No
Caste
Varchar
No
salary
Varchar
No
Education
Varchar
No
Occupation
Varchar
No
maritalstatus
Varchar
No
Table:send_msg
Field Name
Data
type
Null
Description
To_uid
Varchar
No
From_uid
Varchar
No
Messages
Varchar
Yes
Table:success_story
Field Name
Data
type
Null
Description
Usr_id
Varchar
No
Story
Varchar
No
Ad_date
Datetime
no
Table: zone-master
Field Name
Data
type
Null
Description
Country
Varchar
No
State
Varchar
No
city
Varchar
No
CODING STANDARD
Checks for Normal Working
To Be
Checked
?
Yes
Yes
Yes
Yes
Integer
Yes
Float, Double
Yes
Percentage
Yes
Yes
Yes
Yes
Yes
Yes
Basic Validations
Maximum allowed length property is set?
Yes
Yes
Yes
Spell check
Yes
Yes
Boundary Value Analysis (for highest order value and lowest order
Yes
value)
Date Format (dates must be converted from SQL only) NEVER DISPLAY
Yes
12:00:00 AM
Is page validation enabled? [must be done for user entry fields]
Yes
ER-DIAGRAM
The set of Entities of the same type are called as Entity Set.
A graphical model of the data needed by the system, including think about which
information is stored and the relationship among them, produced in structured analysis and
information engineering.
The relational approaches to system development places a great deal of emphasis on data
storage requirements include the data entities, their attributes and the relationship among the data
entities. The model used to define the data storage requirements is called the Entity Relationship
Diagram.
On the Entity Relationship Diagram, a rectangle represents data entities, and lines
connecting the rectangle show the relationship among data entities.
Attributes
1.
Admin Table:
ADMIN
LOGIN
Ad_id
Ad_name
Ad_passwo
rd
2.
Bank_Details Table:
Pin_code
Name_on_c
Card_exp_
CC_ID
BANK
Avail_bala
Card_exp_
DETAILS
Card_no
Credit_limi
Card_type
3.
Profile Table:
State
Login_stat
us
address
membersh
ip
Email_id
City
name
Pro_id
Caste
Mobile_no
country
gothram
PROFILE
Drinking_habbi
ts
Smoking_habbi
ts
zodiac
images
star
education
salary
height
occupation
weight
4. Search
password
Profile Table:
Pro_id
Caste
Education
SEARCHPR
OFILE
Occupatio
n
Maritial_status
5. Feedback Table:
Feedback_id
Names
FEEDBACK
Comment
Feed_date
Profile_id
images
to_id
message
id
Pro_id
passwr
d
Caste
User Login
With
Search
image
Image_id
d
Pro_id
Enters
With
Profile
Image
Salary
name
caste
Success
Has
Pro_id
Story
date
User_id
Symbol:
Sr.
No.
1
Symbol
Name
External
entity
2
Process
3
Dataflow
Description
An external entity is
source or destination
of data flow which is
outside the area of
study.
A process shows a
transformation or
manipulation or
multiplication of data
flow within the
system.
A data flow shows the
flow of information
from source to
destination .A data
flow is represented by
a line with
arrowheads
Showing the flow.
Regist
ration
Regist
ration
Search
1
Registe
r
Add
Add
Educ
ation
New User
Resul
3
Search
User
Search
Informatio
n
old user
Password
2
Login
Reject
Regist
ration
User
Edit
Verification
Response
Email id
Educ
ation
Update
data
U
p
d
Regist
ration
Respon
APPLICATION
NAVIGATION
0
HOME
PAGE
REGISTER
PAGE
LOGIN
PAGE
CONTACT
US PAGE
FEEDBACK
PAGE
SUCCESS
STORY
5
ADMIN
LOGIN
USER LOGIN
LOGIN
PAGE
OPEN USER PROFILE
My Profile
PAGE
Make
Payment
Messages
PAGE
Logout
PAGE
Search
PAGE
Upload
Image
Update Me
PAGE
0
ADMIN
LOGIN
Paid
Member
Non-Paid
Member
Password
Reset
Feedback
PAGE
Logout
PAGE
ACTIVITY DIAGRAM
ACTIVITY DIAGRAM:
INPUT VALIDATION
DISPLAY RECORDS:
SEARCH RECORDS:
UPDATE RECORDS:
CASE DIAGRAM
CASE DIAGRAMS
EVENT TABLE
EVENT TABLE
A table that list events in tabular format that is in rows and key pieces of information about each
event in columns is known as event table.
While developing the list of events, the analyst should note additional information about each
event for later use.
This information is entered in an event table.
An event table comprises of rows and columns.
Each row in an event table records information about one event.
And each column is about its key piece of information about that event.
Trigger:
An occurrence that tells the system that has occur, either the arrival of data needing or of a
point in time.
Source:
An external agent or actor that is supplies data to the system.
Activity:
Behavior of that the system performs when an event occur.
Response:
An output produce by the system, that goes to a destinations.
Destination:
An external agent or an actor that is receives data from system.
Sr.
No
.
Event
Trigg
er
Source
Activit
y
Respo
nse
Designat
ion
Click on
Admin
Admin
Display
Admin
page
Form
open
Admin
Click on login
User
Display
User
profile
Form
open
User
Click on
Feedback
User
Display
Feedback
form
Form
open
User
Click on
Contact us
User
User
Click on
Register
Display
contact
us form
Display
Registrati
on form
Form
open
Form
open
User
Click on
Success
Story
To
open
admin
page
To
open
profile
of user
To
send
feedba
ck
To
contac
t
To
create
new
user
profile
To see
the
story
Form
open
User
Click Update
me
User
Form
open
User
Click on
generate
Display
the list in
table
Admin
Click on
Upload photo
10
Click on find
password
11
Click on
logout
12
Click on
message
To edit
user
profile
To
genera
te paid
memb
er list
To
upload
picture
s
To
send
user
back
To exit
to the
profile
To
expres
s
interes
t
Display
Form of
success
story
Display
update
form
Retrieve
data
13
Click on
To
User
User
Admin
User
Display
Picture
upload
Form
open
User
Admin
Retrieve
data
Open
dialog
box
Admin
Admin and
user
Form
open
Admin and
user
User
Display
the home
page
Display
the send
message
form
Form
open
User
User
Display
Form
User
TESTING PLAN:
Similar to the project plan, due to confidentiality issues, we cannot provide details test plan to the
development team. We will still add the core components that make up our test plan.
References
Introduction
Features to be tested
Approach (strategy)
Test deliverables
Environmental needs
Responsibilities
Approvals
Glossary
TESTING STRATEGY:
Test More and Test Frequent is organizations tagline for testing. A typical screen in asp.net is
tested at four levels before it goes for production.
Level 1 is generally the work to be tested by other developers or other interns (this is typical first
level of testing where focus is not on requirement but end user testing) Ratio: 0% end user: 100%
Technical
Level 2 is level where a senior programmer comes into the testing cycle of the screen that was
unit tested by the developer in this phase the onus is to test software for technical requirements
specified.
Project Plan.
Methodology.
CONTENT TESTING:
Errors in Web Application content can be as trivial as minor typographical error as incorrect
information, improper organization or validation of intellectual property laws. Content Testing
attempt to uncover this and many other problems before the user encounter them.
To uncover semantic errors in any content object represented as navigation occurs, and
DATABASE TESTING:
Modern Web Application does much more than present static content objects. In many
application domains, Web Application interface with sophisticated database management system
and build dynamic content object that are created in real time using the data acquired from a
database.
Database Testing for Web Application is complicated by a variety of factor.
1) The original client side request for information is rarely presented in the form that can be input
to a database management system.
2) The database may be remote to the server that houses the Web application.
3) RAW data acquired from the database must be transmitted to the Web application Server and
properly formatted for subsequent transmittal to the client.
4) The dynamic content objects must be transmitted to the client in a form that can be displayed
to the end user.
Client layer-user
interface
Server layer- WebApp
- data
Management
d
Database
[Layers of interaction]
INTERFACE TESTING:
Interface design model is reviewed to ensure that generic quality criteria established for all user
interfaces have been achieved and that application specific interface design issue has been
properly addressed.
Links: -
Each link is tested to ensure that the proper content object or function is reached. The
Web engineer builds a list of all linksassociated with interface layout. And then executes
eachindividually.
Forms: At a microscopic level, tests are performed to ensure that labels correctly identified
fields within the form and that mandatory fields are identified visually for the user. The server
receives all information content within the form and their no data are lost in the transmission
between client and server. Appropriate defaults are used when the user does not select from a
pull down menu or set of buttons.Browser function dont corrupt data enter in a form and Scripts
that perform error checking on data entered work
message.
Client side scripting:Black box tests are conducted to uncover any error in processing As the script is
executed . These tests are coupled with forms testing because script input is often derived from
data provided as part of forms processing
Dynamic HTML:Each Web page that contains dynamic HTML is executed to ensure that the dynamic
display is correct. In addition a compatibility test should be conducted to ensure that the dynamic
HTML is work properly in the environmental configuration that support the Web application.
Test conforms to a checklist of functionality and features that are defined by the interface
mechanism. Boundary test is minimum and maximum number of items that can be placed in to
shopping chart. Test to determine persistence of shopping chart contents. Test to determine
whether the Web Application can be record shopping chart content at some future date.
USABLITY TESTING:
Usability test may be designed by Web engineering team. Define a set of usability testing
categories and identify goal for each. Design test that will enable each goal to be evaluated.
Select participants who will conduct test. Instrument participants interaction with Web
Application while testing is conducted.Develop a mechanism for assessing the usability of the
Web Application.
AestheticsDo layout color, typeface, and related characteristics lead to ease of use ?
Display CharacteristicsDoes the Web Application make optimal use of screen size and resolution?
Time SensitivityCan important features, functions and content be used in a timely manner?
AccessibilityIs the Web application accessible to people who have Disabilities?
COMPATIBILITY TESTING:
Web application must operate within environment that differs from one another. Different
computer, display device, OS, browser and network connection speed can have significant on
Web application operation. Different browser some time produced slightly different results,
regardless of the degree of HTML standardization within the Web application.
The Web Engineering team derives a series of compatibility, validation tests, derived
from existing interface tests, navigation tests, performance tests and security tests.
TESTING METHOD:
Testing is presents an interesting anomaly for the software engineering activities, the engineer
attempts to build software from an abstract concept to a tangible product. Now comes testing.
The engineer creates a series of test case that are initiated to "demolish" the software that has
been build. Infect, testing is the one step in the software process that could be viewed
(psychologically, at least) as destructive rather than constructive.
Models of Testing:There are different Models of testing. On the basis of testing methods there are two types
of testing:
1. Black-box testing.
2. White-box testing
Black-box tests are used to demonstrate that software functions are operational, that input is
properly accepted and output is correctly produced, and that integrity of external information is
maintained.
White-box tests are used to examine the procedural details. It checks the logical paths by test
case. It can also checks the conditions, loops used in the software coding. It checks that loops are
working correctly on defined boundary value.
WHITE-BOX TESTING:
White-box testing sometimes called glass-box testing, is a test case design method that users the
control structure of the procedural design to drive the test case.Always we are thinking that there
is no necessary to execute or checks the loops and conditions. And large number of errors is
uncovered. With using white-box testing methods, we have checked that; all independent paths
within a function have been executed at least
once.
All logical decisions are their true and false side. All loops working correctly at their boundary
values and within their specified conditions.
In our coding we test that all the loops works truly in each module. The one
technique of white-box testing is basis path testing. It contains two parts, one is flow graph
notation and the second is cyclometer complexity. In flow graph notation we are checking logical
control of flow. By using cyclometer complexity we find complexity of our project structure.
BLACK-BOX TESTING:
Black-box testing focuses on the functional requirements of the software. That is black-box
testing enables the software engineer to drive sets of input conditions that will fully exercise all
functional Requirements for the program. Black-box testing is not an alternative to white-box
testing techniques. Rather, it is a complementary approach that is likely to uncover a different
class of errors than white-box methods.
We use in our coding to find errors in the following categories:
Interface errors
Errors in database
Performance errors
Unlike white-box testing, which is performed earlier in the testing process, black-box testing
tends to be applied during later stages of testing. Because black-box testing purposely disregards
control structure, attention is focused on the information domain.
By applying black-box techniques, we derive a set of test cases that satisfy following criteria .
Test cases that reduce, by a count that is greater then one, the number of additional test cases
must be designed to achieve reasonable testing.
Other related test cases ensure that adopters received the proper Development Release Document
plus other build related information (drop point, etc.). The objective is to determine if further
testing is possible. If any Level 1 test case fails, the build is returned to developers un-tested.
Level 2 - Smoke Tests
The objective is to determine if further testing is possible. These test cases should
emphasize breadth more than depth. All components should be touched, and every major feature
should be tested briefly by the Smoke Test. If any Level 2 test case fails, the build is returned to
developers un-tested.
Level 2a - Bug Regression Testing
Every bug that is Open during the previous build, but they marked as Fixed, Needs
Re-Testing for the current build under test, is need to be regressed, or re-tested. Once the
smoke test is completed, all resolved bugs need to be regressed. It should take between 5
minutes to 1 hour to regress most bugs.
Level 3 - Critical Path Tests
Critical Path test cases must pass by the end of every 2-3 Build Test Cycles. They do not
need to be tested every drop, but must be tested at least once per milestone. Thus, the Critical
Path test cases must all be executed at least once during the Iteration cycle, and once during the
Final Release cycle.
Level 4 - Standard Tests
Test Cases that need to be run at least once during the entire test cycle for this release.
These cases are run once, not repeated as are the test cases in previous levels. Functional testing
and detailed Design Testing (Functional and Design Test Cases, respectively).These can be tested
multiple times for each Milestone Test Cycle (Iteration, Final Release, etc.).
Standard test cases usually include Installation, Data, GUI, and other test areas.
These are Test Cases that would be nice to execute, but may be omitted due to time
constraints.
Bug Regression:
Bug Regression will be a central tenant throughout all testing phases. When a Severity 1 bug
fails regression, adopters testing team should also put out an immediate email to development.
The Test Lead will be responsible for tracking and reporting to development and product
management the status of regression testing
GANTT CHART
Gantt chart is the Graphical Representation about the progress of the project.
Gantt chart shows the details about the how much time taken for any task.
Gantt chart is a type of bar chart that illustrated the project schedule. It shows the
start & finish of the project.
Gantt chart shows the time taken by the task for each phase. Gantt chart decides
the standard of the system. It is a useful tool for planning & scheduling projects.
Gantt chart contains two columns. First is task and other is month (timing). In the
task columns there are five options or phase find in the months columns shows
the progress of the project.
Testing Phase:
Planning
Execution
PERT CHART
Identify any other tasks that can be started simultaneously with task #2.
Align these tasks either above or below task #2 on the working surface.
Continue this process until all component tasks are sequenced.
REQUIREMENT
SPECIFICATION
Requirement Specification
Software Specification:-
Operating System
Front End
Back End
Web Browser
Google Chrome
Web Server
1.36 GHz
RAM
512 MB
Screen revolution
Supported Architecture
2. Maximum Recommended:Processor
2.2 GHz
RAM
1024 MB or more
Screen revolution
Supported Architecture
STRUCTURED TREE
DIAGRAM
Matrimonial Web
HOME
REGIS
Log
LOGIN
User
CONT
FEED
ADMI
Log
SUCCESS
CONCLUSION
Conclusion:
Matrimonial Web Application is to provide Grooms and Brides with excellent matchmaking
experience by exploring the opportunities and resources to meet true potential partner.
Matrimonial website which is provide platform to a lot of Bride/Groom for finding perfect
match. There are different sectors like Registration, Partner, Search, etc. So the Bride/Groom can
get their interest for find their partner. Bride/Groom can directly search Partner according to their
required criteria. The Bride/Groom can use match By Email functionality so he/she can get
directly E-mail alert for the match which fulfill their required criteria. It helps the user by
providing profiles of perspective Bride or Groom and other information regarding them
online.
Matrimonial web application provides facility like quick tour. This is a module that contains the
flow of the website .Here user can have a idea how he can commit himself in the website.
Matrimonial web application provides facility to change preference about partner.
This application provide facility like edit profile, update photo and delete photo, hide profile,
create album, send express interest, send personal message, apply for loan to the user.