Professional Documents
Culture Documents
INTRODUCTION
This project titled “Marriage Bureau” itself shows the general idea about the
project specification. It is very difficult to imagine the existence of marriage without
meeting the two persons face to face, so this problem is replaced by computerized
updating and results are made very conveniently in a simple and planned manner. This
project is very convenient to implement by registering on website in a simple way for end
user, and it does not require much assistance to operate formal meetings. Existing system
works manually take care of all above essential features.
This software provides a better way to register, update and maintain a person’s
data about his personal, family, and horoscope details very well that reflects their
personality. The way it works is in the following manner: I have works on Modules as
follows:
Objectives of project:-
The main Objectives of our project are as follows:
To provide free registration so that anybody can easily create their account on
website.
To make the best matrimonial site especially in Madhya Pradesh where user can
easily find their life partners.
To save the user’s time in finding the right people within few steps.
To become leader in providing matrimonial services to find the perfect life
partner and soul mate among the all religion and Community on the web
comprising quality eligible singles.
To provide a platform for all its Members to interchange information that
would promote their common matrimonial objectives.
Aims at bringing compatible, prospective individuals together and
welcomes all single adults seeking serious relationship, marriage.
1
Page 2 of 46
The scope of the project is wider in the bride and groom match making. It is best
suited for the two persons to find their life partners in a very easy way. We decide that
there is those information should be shown that is important. When user wants to search
about other member profile, he must know about that with the help of this website. Now
the scope of our project had been decided that the web site is provide the all the necessary
information which is related to bride and groom match making just like family and
horoscope information, which is most considerable thing according to our culture. It is
capable to provide the successful user or member profiles among multiple user
simultaneously and able to convey the messages to the right and appropriate users or
members without intermixing of the messages wrongly.
Abbreviations
ADODB :
VB : Visual Basics
RS : Record Source
CS : Connection Source
Theoritical Background:-
Earlier in the bride and groom match making when there was no time for people
to meet each others, people felt inconvenient in reading and understanding biodata
contents and then contacting each other. So there is a thirsty need of a tool or product,
which provides an easy way to communicate between the two.The aim of our project is to
develop a system which satisfies all the needs of users while matching and searching their
life partners. That is if a person who doesn’t knows to whom he can search and contact,
then by filling some forms he gets his desired profile in well indented manner. This is the
main motive of our project. This project helps individuals to determine all the
information related to person and provide a way to take appropriate decision. This leads
to development of “Marriage-Bureau”.
2
Page 3 of 46
Problem Definition
Finding a partner at one place is not possible in most day to day life.
Existing system is manual and hence requires lot of paper movement.
Errors can be found in manual paperwork of match matching.
Difficulty in obtaining information on short notice.
Inconsistent information and lack of data integrity.
Validation of data is difficult due to manual entry.
Unauthorized access to information due to lack of security.
No one deals with the divorcee, widowed/widower.
Complete control through in identify, filter and contact potential partners is not
allowed in most of the matrimonial.
3
Page 4 of 46
Problem Solution :
4
Page 5 of 46
REQUIREMENT ANALYSIS
Requirement analysis is a software engineering task that bridges the gap between
system level requirements and software design. Requirement engineering activities result
i9n the specification of the software’s operational characteristics (functions, data and
behavior), indicates software’s interface with outer system elements, establish constraints
that the software must meet. Requirement analysis allows the software engineer (analyst)
to refine the software allocation build models of data, functional and behavioral domains.
That will be treated by the software. Requirement analysis provides the software designer
with a representation of information, function, and behavior that can be translated to data,
architecture, interface and component level designs.
Requirement Specification :
5
Page 6 of 46
6
Page 7 of 46
Login:- In this use case only the end user i.e. owner of marriage bureau is
allowed to login in the software other people are not allowed to login.
Service According To Purpose:-In this the end user will use all the services
such as submitting his client details ,show other clients details to other, deleting client
details etc.
Search Requirement:- In this user can search the requirements of his client
according to his wish either with respect to caste , qualification ,living city, age and
many more.
Submit Information:- under this head the user can fill the details of his/her
agent to the database for future use to show his data to other clients.
The user can also add castes which are not in the database, he may also add
qualifications like B.E.,M.B.A etc.
Log Out:- by this use case the user can get out of his software. Its the end of the
software.
7
Page 8 of 46
Methodology Adopted:
The incremental model combines elements of the linear sequential model (applied
repetitively) with the iterative philosophy of prototyping. Referring to the figure the
incremental applies sequences in a staggered fashion as calendar time progresses. Each
linear sequence produces a deliverable “increment” of the software. For example work
processing software developed using the incremental paradigm might deliver basic file
management, editing, amend document production functions in the first increment; more
sophisticated editing and document production.
Capabilities in the second increment; spelling and grammar checking in the third
increment;and the advance pagelay out in the second increamentwith other extra
specifications.
8
Page 9 of 46
When an incremental model is used, the first increment is often a core product,
that is, basic requirements are addressed, but many supplementary features remain
undelivered. The core product is used by the customer (or undergoes detailed reviews).
As a result of use and/or evaluation, a plan is a product to better meet the needs of the
customer and delivery of additional features and functionality. This process is repeated
following the delivery of each increment, until the complete product is produced.
The incremental process model is iterative in nature. But unlike prototyping, the
incremental process focuses on the delivery of an operational product with each
S y s te m / I n fo
increment. Early increments are stripped down version of the final product, but they do
provide capability that serves the user and also provide a platform for evaluation by the
user…
E n g in e e r in
9
Page 10 of 46
Details Of Software:
The knowledge of system domain is a crucial part of any project. It gives us the
Information about the essential features of any project, such as information about
Platform, environment, hardware and software requirements.
PlatformSpecification:
This project is totally based on the Microsoft .NET 3.0 platform. Users must
have .NET 3.0 installed on their systems to use this project.
Environment Used
Software Requirement:
Software requirement for this project will be
10
Page 11 of 46
Team Structure
There are basically three types of project teams namely:-
Democratic Decentralized (DD)
Controlled Decentralized (CD)
Controlled Centralized (CC)
The best team structure depends on the management style of the organization,
the number of people who will populate the team and their skill levels, and the overall
problem difficulty. The team structure for the development of the “MARRIAGE
BUERO” is democratic decentralized, this is ensured by the fact that the team is working
to build this system comprises of four members aided by the guidance of a project-guide
and a co-guide. Decisions on problem will be made by consensus among the group
members. Communication among the members is horizontal. All these are suited to
development of this project.
SYSTEM DESIGN
ER DIAGARM:-
11
Page 12 of 46
Architecture
Design is a sequential representation of something to be built. The result of a
design process is called the ‘Design Model’ or the ‘Design of System’. The software
12
Page 13 of 46
design process often has two levels. One of which decides the modules for the
system, their specification and interconnections. This is known as system design or
top level design. The other one, known as detailed design or logic design, decides the
internal design of the module.
Architecture Design
Architectural design represents the structure of the data and the programs
that are required to build a computer based system.
It considers the architectural style that the system will take the structure
and the properties of the component that constitute the system.
Architectural Representation
Architectual Design
This basically follows the three tire architecture.
Presentation Tier : used to format and present the information to the user.
13
Page 14 of 46
Business Tier : used to implement the logic that will drive the system and the reason
the reason why the system exists.
Data Tier : in charge of storing the data (databases) and other external services that the
system may use.
Class Diagram:
14
Page 15 of 46
Activity Diagram
CUSTOMER
15
Page 16 of 46
AGENT
16
Page 17 of 46
17
Page 18 of 46
ADMIN
IMPLEMENTATION
18
Page 19 of 46
SAMPLE CODING
PERSONAL INFORMATION
Public Class Formpersonalinfo
Public rs As ADODB.Recordset
Public cs As ADODB.Connection
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
cs = New ADODB.Connection
rs = New ADODB.Recordset
cs.Open("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\shradha
mam\MINOR_PROJECT_2010\DATABASE\mar.mdb")
End Sub
Private Sub display()
If Not rs.BOF And Not rs.EOF Then
textBox1.Text = rs.Fields("application_number").Value
textBox2.Text = rs.Fields("applicant_name").Value
textBox3.Text = rs.Fields("permanent_address").Value
textBox4.Text = rs.Fields("local_address").Value
textBox5.Text = rs.Fields("city").Value
textBox6.Text = rs.Fields("state").Value
textBox7.Text = rs.Fields("pincode").Value
textBox8.Text = rs.Fields("phone_home").Value
textBox9.Text = rs.Fields("mobile").Value
textBox10.Text = rs.Fields("email").Value
DateTimePicker1.Value = rs.Fields("date").Value
End If
End Sub
19
Page 20 of 46
End If
End If
End Sub
If rs.State = 0 Then
rs.Open("select * from applicant", cs, ADODB.CursorTypeEnum.adOpenDynamic,
ADODB.LockTypeEnum.adLockOptimistic)
End If
rs.AddNew()
textBox1.Text = " "
textBox2.Text = " "
textBox3.Text = " "
textBox4.Text = " "
textBox5.Text = " "
textBox6.Text = " "
textBox7.Text = " "
textBox8.Text = " "
textBox9.Text = " "
textBox10.Text = " "
'End If
'rs.AddNew()
End Sub
20
Page 21 of 46
rs.Fields("pincode").Value = textBox7.Text
rs.Fields("phone_home").Value = textBox8.Text
rs.Fields("mobile").Value = textBox9.Text
rs.Fields("email").Value = textBox10.Text
rs.Fields("date").Value = DateTimePicker1
rs.Update()
MsgBox("Data Updated", MsgBoxStyle.Information, "Confirmation")
End Sub
End Sub
End Sub
End Sub
End Class
REQUIREMENT FORM
Public Class Formrequirement
Public rs As ADODB.Recordset
21
Page 22 of 46
Public cs As ADODB.Connection
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
cs = New ADODB.Connection
rs = New ADODB.Recordset
cs.Open("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\shradha
mam\MINOR_PROJECT_2010\DATABASE\mar.mdb")
End Sub
End If
End Sub
22
Page 23 of 46
tempstr = ComboBox1.Text
choice = "one"
End Sub
23
Page 24 of 46
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where religion='" & tempstr & "' and
record.a_num=family.a_num and record.a_num=applicant.a_num", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "two"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where caste='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "three"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where gender='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "four"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where age='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "five"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where height='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "six"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where weight='" & tempstr & "' and
record.application_number=family.application_number and
24
Page 25 of 46
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "seven"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where marrital_status='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "eleven"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where state='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "nine"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where qualification='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
Case "ten"
If rs.State = 1 Then
rs.Close()
End If
rs.Open("select * from record,applicant,family where occupation='" & tempstr & "' and
record.application_number=family.application_number and
record.application_number=applicant.application_number", cs,
ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)
display()
End Select
End Sub
25
Page 26 of 46
End Sub
End Sub
End Class
REGISTRATION FORM
Imports System.Windows.Forms
Public Class MDIParent1
Formcaste.Top = 0
Formcaste.Left = 0
Formcaste.Show()
End Sub
26
Page 27 of 46
Formdeleterecord.Show()
End Sub
End Sub
End Sub
End Sub
End Class
Input and Output Screen Design:
Login Page:-
27
Page 28 of 46
28
Page 29 of 46
Home Page:-
29
Page 30 of 46
Family Information:-
General Information:-
30
Page 31 of 46
Search RequirementForm:-
31
Page 32 of 46
32
Page 33 of 46
Database Snapshots:-
33
Page 34 of 46
TESTING METHODOLOGY
System testing is the stage of implementation, which is aimed at
ensuring that the system works accurately and efficiently before live operation
commences. In principle, system proving is an on-going activity throughout
the project. The logical design and physical design should be continually
examined to ensure that they work correctly when implemented. Thus the
system test is implemented should be confirmation that all is correct and an
opportunity to show the user that the system works. The program should be
tested individually, using test data design. The complete system and its
environment must be to the satisfaction of the system analyst and the user.
In the technique the close examination of the logical parts through the
software are tested by cases that exercise specifies sets of condition or loops.
All logical parts of the software are checked once errors that can be correct
34
Page 35 of 46
Testing approaches
Unit Testing: -
Integration Testing: -
This is done to verify the software as a whole. Ideally, if unit testing is
throughout this type of testing should find mostly interface error that would
not have been easily during unit testing?
Validation Testing: -
Validation testing was performed to assure that all functional and
performance requirements are met.
System Testing: -
35
Page 36 of 46
transaction recoveries from failure etc. system testing is done to ensure that
system satisfies all the user requirements.
Testing Principles: -
36
Page 37 of 46
Integration Testing: -
37
Page 38 of 46
CONCLUSION
A Marriage Bureau system is designed for finding appropriate and suitable
matches keeping the desired qualities of the concerned party as main objective.
Applicants with age above 21 for male and 18 for female apply with their complete bio-
data and requirements for desired match. Marriage bureau is an organization, which
works for the society to make an easy way for the marriage. Searching a perfect partner
for life is a typical task for each human being. Sometimes, it becomes more complex
when we have no complete information about a particular bride & groom.
The purpose of this document is to develop a Marriage Bureau System which has
better data security, better data storage and retrieval, better user interface and additional
useful features which are not present in the current existing Marriage Bureau System.
This software is developed for reducing the efforts of the bureau & to simplify its
task of finding a perfect match. In this project, we find perfect match for a person based
on certain criteria such as religion, caste, job profile & city, personal appearance,
qualification, area etc.
Overall Description:
Product Function:
38
Page 39 of 46
particular criteria.
of computers.
automation of task.
consistent.
Limitations of Project
This project cannot have the photo and video of the customer.
Future Enhancements
Referances
Google: directory
[http://www.falgunimehta.com/]
[http://www.bharatmatrimony.com/]
Shaadi.com
Shaadi Point104, vikram Tower, sapna sangeeta Road, Indore,
Shivam Marriage Bureau, Khatiwala Tank, Indore,
40
Page 41 of 46
USER MANUAL
This project is totally based on the Microsoft .NET 3.0 platform. Users must
have .NET 3.0 installed on their systems to use this project. This is not An Web
application, but it is a Desktop Application.
In this project first of all you must have .NET 2008 OR .NET 2010 installed on
your computer along with MS-ACCESS 2007 to run this project on your computer.
Steps to LOGIN-
41
Page 42 of 46
42
Page 43 of 46
43
Page 44 of 46
44
Page 45 of 46
Now enter the USER-ID as “admin” and PASSWORD as “admin”.you will get
thescreenas s
45
Page 46 of 46
Now you can go to “MENU BAR” and do your work of your choice i.e.
submitting new customer enrty ,looking for a profile , deleting and adding new
caste etc.
46