You are on page 1of 46

Page 1 of 46

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

Scope of the Project:-

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

In Registration Module, we provide facilities to enter useful information which


includes his/her personal and family and details that is required for the purpose of
developing marriage proposals.
In Admin Profile Module, we keep the records of users, their contact details and
other information.Admin can also check membership date so that he can intimate those
users whose time period is expiring according to their membership plan.

Problem Definition

The knowledge of the problem domain is the most important part of


any project. Because of it in our project “Marriage Bureau” we enlist certain
objectives for which we are working out. Some other matrimonial site &
organization provide name of required candidate according to only religion,
cast, age and sex. Candidate has to find good partner from the list of 100
and more bride /groom list.

What exactly is the problem?

 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 :

We will provide name of required candidate according to Religion, Cast, Age,


Sex, Personal Appearance, Job Profile, Marital Status, Family Back Ground etc. It shows
the list of bride or groom who will be according to specified criteria. Customer will get
list of selected candidate which will be best.

 Candidates can find the bridge/groom according to a place.


 Any record can be searched and viewed providing appropriate input.
 The filling of form is done on computer, hence no paperwork is done.
 There are fewer chances of errors as validation as whole thing is computerized.
 Information is obtained easily on short notice.
 Data integrity and Security is provided.
 Unauthorized access should be avoided and a membership is provided for further
advantage of users.
 A separate importance is given to divorced and widowed/widower.
 We provide customers complete control through easy to use interfaces and
features that can help them identify, filter and contact potential partners.
 Match making task is easier.

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 :

Requirements specification restates the requirement definition in technical terms


appropriate for the development of the system design. It is in the technical counterpart of
Requirement definition and is specified by the system analyst. It comes under the
category of Quality Function Development, which translates customer’s needs into
technical requirements of the system. In this project the user (bureau agent) wants to have
maximum details of the candidates so that he may show others the maximum details
about the other candidate whose requirement is being fulfilled by him/her. It basically
identifies three types of requirements describes as:

Use Case Specification :

5
Page 6 of 46

Use Case Diagram

6
Page 7 of 46

Use Case Description:

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.

SOFTWARE REQUIREMENT SPECIFICATION

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

Incremental development is particularly useful when staffing is unavailable for a


complete implementation by the business deadline that has been established for the
project. Early increments can be implemented with fewer people. If the core product is
well received, then additional staff (if required) can be added to implement the next
increment. In addition, increments can be planned to manage technical risks. For
example, a major system might require availability of new hardware that is under
development and whose delivery date is uncertain. It might be possible to plan early
increments in a way that avoids use of this hardware, thereby enabling partial
functionality to be delivered to end-users without inordinate delay.

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

MS windows GUI environment

Software Requirement:
Software requirement for this project will be

 Front end : VB.NET


 Back end : Microsoft Access 2007.
 Tools Required : Visual Studio 2008, command prompt

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:-

• ER MODEL FOR ENTITY APPLICANT

11
Page 12 of 46

ER MODEL FOR ENTITY RECORD

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

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button1.Click
rs.Open("select * from applicant", cs, ADODB.CursorTypeEnum.adOpenDynamic,
ADODB.LockTypeEnum.adLockOptimistic)
display()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button2.Click
If rs.State = 1 Then
If Not rs.BOF And Not rs.EOF Then
rs.MoveNext()
display()
End If
End If
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button3.Click
If rs.State = 1 Then
If Not rs.BOF And Not rs.EOF Then
rs.MovePrevious()
display()

19
Page 20 of 46

End If
End If
End Sub

Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button4.Click
If rs.State = 1 Then
If Not rs.BOF And Not rs.EOF Then
rs.MoveFirst()
display()
End If
End If
End Sub

Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button5.Click
If rs.State = 1 Then
If Not rs.BOF And Not rs.EOF Then
rs.MoveLast()
display()
End If
End If
End Sub

Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button6.Click

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

Private Sub Button7_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button7.Click
rs.Fields("application_number").Value = textBox1.Text
rs.Fields("applicant_name").Value = textBox2.Text
rs.Fields("permanent_address").Value = textBox3.Text
rs.Fields("local_address").Value = textBox4.Text
rs.Fields("city").Value = textBox5.Text
rs.Fields("state").Value = textBox6.Text

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

Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button8.Click
Me.Hide()
Formfamilyinfo.Show()

End Sub

Private Sub Button10_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button10.Click
rs.Delete()
MsgBox("Data Deleted", MsgBoxStyle.Information, "confirmation")
End Sub

Private Sub Button9_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button9.Click
Me.Hide()
MDIParent1.Show()
End Sub

Private Sub Button11_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button11.Click
Me.Hide()
MDIParent1.Show()
End Sub

Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs)

End Sub

Private Sub Label12_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Label12.Click

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

Private Sub display()


If Not rs.BOF And Not rs.EOF Then
TextBox1.Text = rs.Fields(0).Value
TextBox2.Text = rs.Fields("applicant_name").Value
TextBox3.Text = rs.Fields("caste").Value
TextBox4.Text = rs.Fields("religion").Value
TextBox5.Text = rs.Fields("nationality").Value
TextBox6.Text = rs.Fields("academic_qualification").Value
TextBox7.Text = rs.Fields("occupation").Value
TextBox8.Text = rs.Fields("monthly_income").Value
TextBox9.Text = rs.Fields("local_address").Value
TextBox10.Text = rs.Fields("permanent_address").Value
TextBox11.Text = rs.Fields("living_area").Value
TextBox12.Text = rs.Fields("marrital_status").Value
TextBox13.Text = rs.Fields("children").Value
TextBox14.Text = rs.Fields("no_of_children").Value
TextBox15.Text = rs.Fields("mobile").Value
TextBox16.Text = rs.Fields("email").Value
TextBox17.Text = rs.Fields("mother_tongue").Value
TextBox18.Text = rs.Fields("gender").Value
TextBox19.Text = rs.Fields("dob").Value
TextBox20.Text = rs.Fields("age").Value
TextBox21.Text = rs.Fields("height").Value
TextBox22.Text = rs.Fields("weight").Value
TextBox23.Text = rs.Fields("complexion").Value
TextBox24.Text = rs.Fields("phone_home").Value
TextBox25.Text = rs.Fields("name_of_father").Value
TextBox26.Text = rs.Fields("father_occupation").Value
TextBox27.Text = rs.Fields("mother_occupation").Value
TextBox30.Text = rs.Fields("name_of_mother").Value
TextBox36.Text = rs.Fields("total_sister").Value
TextBox31.Text = rs.Fields("married_sister").Value
TextBox32.Text = rs.Fields("sister_occupation").Value
TextBox33.Text = rs.Fields("total_brother").Value
TextBox28.Text = rs.Fields("married_brother").Value
TextBox29.Text = rs.Fields("brother_occupation").Value
TextBox35.Text = rs.Fields("joint_family").Value
TextBox34.Text = rs.Fields("total_members").Value

End If
End Sub

Private Sub ComboBox1_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles ComboBox1.SelectedIndexChanged

22
Page 23 of 46

tempstr = ComboBox1.Text
choice = "one"

End Sub

Private Sub ComboBox2_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles ComboBox2.SelectedIndexChanged
tempstr = ComboBox2.Text
choice = "two"
End Sub
Private Sub ComboBox3_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox3.SelectedIndexChanged
tempstr = ComboBox3.Text
choice = "three"
End Sub
Private Sub ComboBox4_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox4.SelectedIndexChanged
tempstr = ComboBox4.Text
choice = "four"
End Sub
Private Sub ComboBox5_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox5.SelectedIndexChanged
tempstr = ComboBox5.Text
choice = "five"
End Sub
Private Sub ComboBox6_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox6.SelectedIndexChanged
tempstr = ComboBox6.Text
choice = "six"
End Sub
Private Sub ComboBox7_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox7.SelectedIndexChanged
tempstr = ComboBox7.Text
choice = "seven"
End Sub
Private Sub ComboBox11_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox11.SelectedIndexChanged
tempstr = ComboBox11.Text
choice = "eleven"
End Sub
Private Sub ComboBox9_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox9.SelectedIndexChanged
tempstr = ComboBox9.Text
choice = "nine"
End Sub
Private Sub ComboBox10_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ComboBox10.SelectedIndexChanged
tempstr = ComboBox10.Text
choice = "ten"
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
Button1.Click

Select Case choice


Case "one"

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

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


Button3.Click
Me.Hide()
MDIParent1.Show()
End Sub

25
Page 26 of 46

Private Sub TextBox1_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs)


Handles TextBox1.TextChanged

End Sub

Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs)


Handles GroupBox1.Enter

End Sub
End Class

REGISTRATION FORM
Imports System.Windows.Forms
Public Class MDIParent1

Private Sub ShowNewForm(ByVal sender As Object, ByVal e As EventArgs) Handles


NewToolStripMenuItem.Click

Formcaste.Top = 0
Formcaste.Left = 0
Formcaste.Show()
End Sub

Private Sub OpenFile(ByVal sender As Object, ByVal e As EventArgs) Handles


OpenToolStripMenuItem.Click
Formoccupation.Show()
End Sub

Private Sub SaveToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles SaveToolStripMenuItem.Click
Formqualification.Show()
End Sub

Private Sub ATTRIBUTEINFORMATIONFORMToolStripMenuItem_Click(ByVal sender As


System.Object, ByVal e As System.EventArgs) Handles
ATTRIBUTEINFORMATIONFORMToolStripMenuItem.Click
Formgeneralinfo.Show()
End Sub

Private Sub GeneralToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles GeneralToolStripMenuItem.Click
Formpersonalinfo.Show()
End Sub
Private Sub OptionsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OptionsToolStripMenuItem.Click
Formsearchrecord.Show()
End Sub

Private Sub EDITRECORDToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles EDITRECORDToolStripMenuItem.Click
Formeditrecord.show()
End Sub

Private Sub DELETERECORDToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles DELETERECORDToolStripMenuItem.Click

26
Page 27 of 46

Formdeleterecord.Show()
End Sub

'Private Sub RedoToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles RedoToolStripMenuItem.Click
' Exitform.show()
'End Sub

Private Sub FAMILYINFORMATIONFORMToolStripMenuItem_Click(ByVal sender As


System.Object, ByVal e As System.EventArgs) Handles
FAMILYINFORMATIONFORMToolStripMenuItem.Click
Formfamilyinfo.Show()

End Sub

Private Sub REQUIREMENTToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles REQUIREMENTToolStripMenuItem.Click
Formrequirement.Show()
End Sub

Private Sub MDIParent1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)


Handles MyBase.Load

End Sub

Private Sub SEARCHEDToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles SEARCHEDToolStripMenuItem.Click
End Sub

Private Sub PERSONALINFORToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles PERSONALINFORToolStripMenuItem.Click
resultant1.Show()
End Sub

Private Sub UndoToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles UndoToolStripMenuItem.Click
End Sub
Private Sub LogoutToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles LogoutToolStripMenuItem.Click
Form()
End Sub

Private Sub EditMenu_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles


EditMenu.Click

End Sub
End Class
Input and Output Screen Design:

Login Page:-

27
Page 28 of 46

28
Page 29 of 46

Home Page:-

Customer Entry Pages:


Personnel Information:-

29
Page 30 of 46

Family Information:-

General Information:-

30
Page 31 of 46

Search RequirementForm:-

31
Page 32 of 46

Adding Caste /Qualification Form:-

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.

Test Methods & Strategies used along with test


cases

White box testing: -

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

using this techniques are typographical errors, logical expressions, which


should by executed once may be getting executed more than once error
resulting by using wrong controls and loops.

Black box testing: -

This method enables the software engineer to device sets of input


techniques that fully exercise all functional requirements for a program. Black
Box testing test the input, the output and the external data. It checks whether
the input data is correct and whether we are getting desired output.

Testing approaches

Unit Testing: -

This involves the testing of individual modules, which is usually


carried out ensure the validity of those particular modules. In this project each
of the modules was first individually tested for errors.

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: -

It is executing program to check logic changes made in it and with


intention of finding error. A system is tested for on online response; volume of

35
Page 36 of 46

transaction recoveries from failure etc. system testing is done to ensure that
system satisfies all the user requirements.

Testing & Results: -

Testing is a process of executing a program with the intent of finding


an error, eliminating errors to produce an error free software which meets the
specification .The objective of testing is to identify the faults as quickly as
possible after they occur and to identify the cause of the fault so that the
remedial steps can be taken .To make the project more robust, testing is the
vital part of any software development process.

Testing Principles: -

 All the tests should be traceable to the customer requirements.


 Tests should be planned long before the testing begins.
 Testing should begin in small and progress towards testing in
large.
 Exhaustive testing is not possible
 To be effective testing should be conducted by an independent
3 rd party.

Strategies for Successful Test Case design: -

Following are some important and specific strategies,


which must be used to make the Test Case Successful.

 Specify product requirement in a qualifiedly


manner long before testing starts.
 State and specify testing objective explicitly.

36
Page 37 of 46

 Understanding properly the user of software and develop a


profile for each categories.
 Develop a test plan that performs rapid cycle testing of all the
components of the software.
 Develop the software that is design to test itself.
 Use technical review of the software as a filter before test.
 Use technical review for both test as well as test case.
 Use continues improvement approaches for the testing process.

Integration Testing: -

Integration testing is a systematic technique for constructing the


program structure while conducting test to uncover errors associated with
interfacing. Black box test case design techniques are the most prevalent
during integration with a white box testing.

We followed top down approach, the project is developed and tested in


small segment where errors were easier to isolate and correct. Each menu
module was tested properly and then kept together. The entire path from main
menu to the each module was tested thoroughly. The complexity of the task
was greatly reduced since all modules have already been tested.

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

 The filling of form is done on computer, so there are fewer chances of

errors as validation can be put on input fields.

 Multiple records are viewed at a time.Any record can be searched and

viewed providing appropriate input.

 A query engine is developed to provide user; the information based on

particular criteria.

 Match making task is easier.

 Due to advance technology faster computers means more speedy work

 As the computers are highly accurate, accuracy in work is increased.

 Storage of large volume of data is facilitated due to high storage capacity

of computers.

 Decrease the load of the person involved in existing system due to

automation of task.

 Updating of information is easier.

 Generation of reports easily.

 Access any information individually.

 Easy and fast retrieval of information.

 Because of related databases provided by DBMS, the data will be

consistent.

 Overall time is saved and activities can be performed in parallel.

Limitations of Project

 Online functioning is restricted.


 Information gathering over application is not done automatically
39
Page 40 of 46

 This project is for personal use only.

 This project cannot have the photo and video of the customer.

Future Enhancements

Finally, each software is never really completed. There are always


betterments that can be made to it. Even if it is correct when first turned over
to users, there will almost always be changes required. Most common changes
occur because of new or different user requirement. For example, if our
competitor’s system suddenly has a new feature, we will probably need a
similar or better one for our transaction to survive.
Sometimes, after a few months of using a system, a user will realize
limitation or think of valuable new features that could be incorporated. Often
the external environment changes and the software needs appropriate
modification. Other areas of changes outgrow their system; systems are so
outmoded they or scrapped .We are also looking for development with the
storage of the customer photo ,video clips and the slideshow of all photos.

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

 Open the folder containing the EXECUTABLE FILE NAMED“WINDOWS


APPLICATION –MICROSOFT VISUAL STUDIO SOLUTION”.

 Now double click on this folder you will get a screen as

42
Page 43 of 46

 Now click on “GREEN COLOR BUTTON“ marked in circle with red


color and and u will get the “LOGIN PAGE” as-

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.

 That’s all with the user manual.

46

You might also like