MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008

SYSTEM 160260107009
160260107011

1
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

CERTIFICATE

This is to certify that the project entitled “MATRIMONIAL MANAGEMENT

SYSTEM” is a bonefited report of the work carried out by Gunjan Giri, Meet Jha,
Twinkle Khetwani under the guidance and supervision for the award of the
degree of Bachelor of Computer Engineering at Kalol Institute of Technology and
Research - Gandhinagar, Gujarat.
To the best of my knowledge and belief, this work embodies the work of candidate
himself/herself, has duly been completed, fulfills the requirement of the ordinance relating
to the Bachelor degree of the university and is up to the standard in respect of content,
presentation and language for being referred to the examiner.
Mrs. Jaiminee Patel

Lecturer,

CE & IT Department,

LDRP ITR, Gandhinagar

Prof. Shilpa Serasiya

H.O.D.

2
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

-:ACKNOWLEDGEMENT:-

I take this opportunity to humbly express our thankfulness to all those concerned
with my project.

First of all I am thankful to KITRC for undertaking this project. I am sincerely

indebted to Mrs. JAIMINEE PATEL for giving me the opportunity to work on
this project. Her continuous guidance and help have proved to be a key to my
success in overcoming the challenges that I have faced during my project work.
Her support made the project a pleasantly memorable one .Without her help at all
stages in spite of her own work load; the completion of the project would not have
been possible.

I express my sincere gratitude to Prof. SHILPA SERASIYA for his valuable

guidance and positive feedback.

There are so many persons without whose help I would never have conceived and
learnt , to whom I would like to express my gratitude – my friends , colleagues,
and of course CE Department of KITRC.

Last but not least I am thankful to almighty GOD and my PARENTS for giving
me such a good atmosphere to work hard and to succeed.

With regards,

GUNJAN GIRI (160260107008)

MEET JHA (160260107009)
TWINKLE KHETWANI (160260107011

3
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

-:INDEX:-
1) Introduction………………………………………………………...........(7-11)
Project Profile………………………………………………………........ (8-9)
Project Summary…………………………………………………………. (10)
Project Purpose………………………………………………………...... (11)
Project Goals……………………………………………………….......... (11)
Project Scope……………………………………………………….......... (11)

2) Project Management…………………………………………………….(12-17)
Project Planning & Scheduling……………………………………… (13)
Risk Management………………………………………………………… (14)
Estimation ……………………………………….………………………….. (15-16)

3) System requirement study.…...……………………………………… (17-18)

User characteristics..……………………………………………………… (18)
Hardware Requirements………………………………………………… (18)
Software Requirements…………………………………………………. (18)

4) Tools and technology………………………………………………………(19-20)

Software…………………………………………………………………........ (20)
Hardware..……………………………………………………………………… (20)

5) System analysis..……………………………………………………………..(22-44)
Use case diagram..………………………………………………………….. (22)
Class diagram..………………………………………………………………... (23-25)
Activity diagram………………………………………………………......... (26-31)
Sequence diagram……………………………………………………………. (32-35)
Dataflow diagram…………………………………………………………….. (36-41)
E-R diagram……………………………………………………………………... (42-44)

4
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

6) Testing …………………………………………………………………………….(46-48)
Testing Plan ……………………………………………………………………. (46)
Testing Strategy………………………………………………………………. (46-47)
Testing Method……………………………………………………………….. (47-48)

7) Conclusion………………………………………………………………………..(49-50)
Future Enhancement and conclusion………………………………… (50)

8) Bibliography………………………………………………………………………..(51)

5
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

 Abstract:-
 Online matrimonial application system is in the process of
interconnecting all the branches and to develop a custom made
software which covers functions like matrimonial management and
processing of a matrimonial agency. The system not only takes care
of registration but also contemplate on workflow, customer service,
customer history, employee history and near paperless operation .

 The main aim of this application referred as online matrimonial

application system is to computerize a matrimonial company.

 At the end of the study a model that describes how event

matrimonial strategy development in matrimony organisations can
be seen to follow certain stages is developed.

6
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

1.INTRODUCTION

 Project Profile
 Project Summary
 Project Purpose
 Project Goals
 Project Scope

7
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

1.1.PROJECT PROFILE

PROJECT TITLE Matrimonial Management

ORGANIZATION Kalol Institute Of Technology And Research Center

TOOLS Hardware

 Dual Core Processor

 1 GB RAM
 80 GB Hard disk space

Software

 Wamp server
 Apache server

STARTING DATE

ENDING DATE

TEAM SIZE 3 person

8
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

TEAM MEMBERS GUNJAN GIRI

MEET JHA

TWINKLE KHETWANI

GUIDED BY MRS. JAIMINEE PATEL

Submitted To: KALOL INSTITUTE OF TECHNOLOGY AND

RESEARCH CENTER,KALOL

9
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

1.2)PROJECT SUMMARY:=
 Project Title

Matrimonial Management

 Documentation Tools
Microsoft Office XP Professional

Wamp server

 Project Guide
Mrs. Jaiminee Patel

 Submitted By
GUNJAN GIRI(160260107008)

MEET JHA(160260107009)

TWINKLE KHETWANI(160260107011)

 Submitted To

Kalol Institute of Technology and Research Centre

10
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

1.3).PROJECT PURPOSE:=
 It helps the user by providing profiles of perspective Bride or Groom and other
information regarding them online.
 We can develop website by ourself..
 People may easily know about his/her life partner.
 To get the soulmate through this website..

1. 4).PROJECT GOALS:-
 It helps the user by providing profiles of perspective Bride or Groom
and other information regarding them online.
 You get to meet the one keenly looking for a groom or bride such as
you.

1. 5).PROJECT SCOPE:-
 People would be able to find their life partners.
 Being a web-application and accessible from everywhere from the any place
of the world, it allows for interaction between members from any place over
the continent

11
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

2…

Project Management

 Project Planning and scheduling

 Risk Management
 Estimation

12
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

2. PROJECT PLANNING AND SCHEDULING

 Project Development Approach and Justification:-

 The system development approach that we select is to deliver software a bit at a time
(Incrementally), repeating parts of the development process for each delivery
(iteration).
 Project Activities :-

 The major activity in the project includes the following tasks:

 To determine the methodology for the construction of the project.
 To determine the model of the software through which the project will be
identified.
 Determining the first face goals from the aim of the project.
 Designing the software development life cycle for the project.
 Identify the number of phases in the software development life cycle of the
project.

 Project Management:-

Matrimonial Management System

 Planning, scheduling and tracking of project:-

 The project planning consists of:

13
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

 Selection of Suitable software development model.

 Risk Management Plan, which involves the risk identification and risk
assessments.

-:Project Scheduling:-

 Generalized project scheduling tools and technique can be applied with little
modification to software projects.
 Program evolution and review techniques (PERT) and critical path method (CPM) are
two project scheduling method that can be applied to software development. Both
techniques are driven by information already developed in earlier project planning
activities:

 Estimate of effort.
 A decomposition of the product function.
 The selection of appropriate process model and task set.
 Decomposition of tasks.

2.2.RISK MANAGEMANT
Creating a Task Management System is a difficult undertaking. Lots of things can go
wrong and frankly, many often do. It’s for this reason that being prepared understanding the risks
and taking proactive measure to avoid or manage them is a key element of good software project
management.

14
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Risk Probability Effect

Change of requirements which High Serious

require proposal of major Moderate Serious
design rework.

Scheduling slippage: The time

required for the development of High Serious
software is underestimated, so
schedule slippage will occur

The size of software is High Tolerable

underestimated

Power
High Tolerable
Failure

15
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Identification:-
 The followings are the possible risks, which is associated with project. We have
identified mainly technical and project risks.

 Technical Risks:-

 Our software doesn’t work on all operating system.

 It cannot work if proper system is not installed.

 Project Risks:-

 Scope might have been wrongly defined and the project might go in the wrong direction.
 The time limits might not have been properly calculated as per the scope. If the project
was not properly scheduled, or if the scope was ill defined, it might not be possible to
finish the project at the right time.
 Scope creep could occur. The expectations and requirements have increased or may be
changed.
 Certain technical problems have remained unsolved.

 Risk Analysis and Planning:-

 To handle the risks we have prioritized it. The damaging risks can be handled first and then most
likely risks. Since the risk related to the schedule slippage arise primarily due to the intangible
nature of the software, so we had to do the visibility of software requirements documentation
and reviewing the relevant documents during the developments. Every phase can be broken
into the reasonably sized tasks and milestones can be scheduled for these tasks.

16
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

3…
System Requirement Study

 User Characteristics
 Hardware Requirement
 Software Requirement

17
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

 User Characteristics

 User of the System requires the basic knowledge of the computer. No

experience is required for the System user.
 System design will be as per user requirements and hence it will be
easy for the user to interact with the System.


 SOFTWARE REQUIREMENT
 Front End : - PHP
 Designing Tool :- Adobe Dream viewer
 Back End Tool : - MY.SQL Server
 Operating System: -Windows XP or higher

 HARDWARE REQUIREMENT
• Processor : 1.3 GHz or higher with 1GB RAM

Minimum disk Space : 1.5 GB

18
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

4…

Tools & Technology

 SOFTWARE
 HARDWARE

19
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

 SOFTWARE
 We have selected PHP application development tool for creating our system as it is very
much student friendly as the developer can do designing.
 As a back-end tool we select SQL because of its great advantages in data base
management field. It is very well easy to use and simply we can create tables. All types
of required constrains can be added efficiently.
 Front End Tool:- Wamp server 2.5/Apache

 HARDWARE

 We have used the hardware that which is the basic requirement for using the Wamp
server 2.5 properly.
 We have used the following hardware specification so that we could get the optimized
performance.

20
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

5…

System Analysis
 Use Case Diagram
 Class Diagram
 Activity Diagram
 Sequence Diagram
 Dataflow Diagram
 E-R Diagram

21
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

USE CASES FOR MATRIMONIAL MANAGEMENT

SYSTEM

User
Login

Add Photos

Create Profile

Add
Contact
Details

logout

Figure 9.14: Use Case Diagram

22
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

CLASS DIAGRAM (USER LEVEL)

User

ProfileID: int

UserName: string
Step1 () Matrimonial
1..* Access 0..
Management
Step2 () 1
Step1 ()
Member Login ()
Step2 ()
Admin Users ()
Matrimonial 1 Access 1..*
Member Login ()
Management
Datastore Admin Users ()
ProfileID: int

UserName: string

ID:int

Step1 ()

Step2 ()

Member Login ()

Admin Users ()

23
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

CLASS DIAGRAM FOR REGISTER

User

ProfileID: int

UserName: string

AddBlogPosts () Matrimonial Management

1..* 0..1
(Register)
ViewBlogs ()

AddBlogComments () Access Profile DisplayProfile ()

ViewBlogComments () SaveRegisterProfile ()

1 1..*
Matrimonial Management
Datastore
Get/Save Profile

ProfileID: int

UserName: string

ID:int

GetRegisterData ()

SaveRegisterData ()

24
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

CLASS DIAGRAM FOR ADMIN

Admin

Approver_code: int

ApproveRegisterProfile () Matrimonial Management

1..* 0..1
RejectRegisterProfiles () (Admin Section)
Access Admin DisplayLatestMessagePost ()
ApprovePhotos ()
SavePost ()
RejectPhotos ()
(status: 1-approved, 2-
reject)

DisplayLatestPhotos ()

SavePhotos ()

Matrimonial Datastore 1..* (status:1-approved, 2-reject)

1
(Advertisement)

Get/Save

Approver_code: int

Dt_Approval: date

Get () int
Status:

Save ()

Figure 9.20: Class Diagram For Admin

25
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

ACTIVITY DIAGRAM
ACTIVITY DIAGRAM FOR MATRIMONIAL MANAGEMENT

Enter UserID and Password

Display
Matrimonial Validate UserID
Management and Password
login screen

Validated = false

Validated = true

Select Enter the

Matrimonial Matrimonial
Management Management

Figure 9.36: Activity Diagram For Matrimonial Management

26
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

ACTIVITY DIAGRAM FOR MATRIMONIAL MANAGEMENT PARTITIONED

ACCORDING TO ACTORS

System

Display
Matrimonial Validate Enter the
Websitelogin UserID and Matrimonial
screen Password Website

Validated = false Validated = true

User

Select
Enter UserID
Matrimonial
and
Management
Password

Figure 9.37: Activity Diagram For Matrimonial Management Partitioned According To Actors

27
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

ACTIVITY DIAGRAM FOR MATRIMONIAL MANAGEMENT SUBSYSTEMS

Select
Register
section

Select Profile
Section
Display
Selected
Display
Section
Matrimonial
Management Select Admin
Main Page Section

Select
Member
Section

Figure 9.38: Activity Diagram For Matrimonial Management Subsystems

28
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

ACTIVITY DIAGRAM FOR MATRIMONIAL MANAGEMENT SUBSYSTEMS

PARTITIONED ACCORDING TO ACTORS

System

Display Display
Matrimonial Selected
Management Section
Main Page

Select
Registersecti
on

Select Profile
Section

Select Search
Section

Select
Member
Section
User

Figure 9.39: Activity Diagram For Matrimonial Management Subsystems

Partitioned According To Actors

29
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

ACTIVITY DIAGRAM FOR REGISTER SYSTEM (TO VIEW)

Select
Register View

Display
Display Select User
Selected
Register Main View
View Register
Page
Select a
Select Profile
Profile
View

Select
View/Edit
Profile
Add Profile
Save Updated Edit and
Profile Submit
View Profile
Display
Details of
Selected
Profile
Figure 9.40: Activity Diagram For Register System (To View)

30
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

ACTIVITY DIAGRAM FOR ADMIN (REGISTER, PHOTO, CONTACT US SECTION)

Select
Register

Select Photo
Display
Display Selected
Employee Section
Select
corner Admin
Contact Us Select
Page
Register/Photo/C
ontactUs

Reject
Message to Select
User Approve/
“Rejected
Display on Reject
MMS Main
Approve
Page
Figure 9.41: Activity Diagram For Admin (Register, Photo, Contact Us Section)

31
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

SEQUENCE DIAGRAM FOR MATRIMONIAL

MANAGEMENT SYSTEM

User Matrimonial MMS

Management Database
System System

| | |
|
Login
| | |
|
ProfileID and Password
| | |
| Fetch ProfileID
and Password
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | Data |
|
| | |
|
| | |
|
| | |
|
| | Verify |
|
| | ProfileID and |
| Check () ==
| | Password |
| Validated
| | |
|
| | |
|
| | |
|
| | |
|
| Enter MMS | |
|
| | |
|
| | |
|
| | |
| Check () ==
| | |
| Invalid.
| | |
|
| Msg “Invalid” | |
|
| | |
|
| | |
|
| | |
| Figure 9.32: Sequence Diagram For Matrimonial Management System
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| | 32 |
|
| |
|
|
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

SEQUENCE DIAGRAM FOR Search

User Matrimonial MMS

Management (Profile)
(Database)

View
| | |
Profile Fetch data
| | |

| | |

| | Data |
| | |
| | |
| | |
| Display | |
| | |
Profile
| | |
| | |
| | |
| | |
| | |
| Add Profile | |
| | |
| | |
| | |
| | Save Profile |
| | |
| | |
| Response | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| Figure 9.33: Sequence| Diagram For Search |
| | |
| | |
| | |

| | |
33
| | |
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

SEQUENCE DIAGRAM FOR PHOTOS

User Matrimonial Matrimonial

Management (Register Management
Profile) (Database)

Register Profile
| | |
Insert data
| | |

| | |

| | |
Data
| | |
| | |
| | |
| | |
Add
| | |
| | |
Photos
| | |
| | |
| | |
| | |
| | |
| | |
| Add Photos | |
| | |
| | |
| | |
| | Save Photos |
| | |
| | |
| | |
| Response | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Figure 9.34 Sequence Diagram For Photos
| | |

| | |
34
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

SEQUENCE DIAGRAM FOR ADMIN

Admin Matrimonial Management MMS

(Register/Search) (Database)

| View () | |
Fetch data ()
| | |

| | Data |
Display ()
| | |
| | |
| | |
| | |
| | |
Check () =Approve
| | |
Status (1)
| | |
| | |
| | |
| | |
| | |
| | |
Check () =Reject
| | |
| | |
Status (2)
| | |
| | |
| | |
| Response (“Rejected”) | |
| | |
| | |
| | |
| | |
| | |
| | |
| Figure 9.35: Sequence |Diagram For Admin |
| | |
| | |
| | |
| | |
| | |
| | |
35
| | |
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Data Flow Diagrams

Context Level Diagram (Level 0 DFD)

Figure 9.22: Context Level Diagram (Level 0 DFD)

36
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Context Level Diagram (Level 0 DFD) For Admin

Figure 9.23: Context Level Diagram (Level 0 DFD) For Admin

37
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Data Flow Diagram level: 1.0

User

Register
(Free)

Bride/Groom Search MMS

finder
Data

MMS database

Figure 9.24 : Data Flow Diagram level: 1.0

38
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Data Flow Diagram level: 1.1

Member
Register

User MMS

Admin

Create
User/Read

Figure 9.25 : Data Flow Diagram level: 1.1

39
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Data Flow Diagram level: 1.2

Bride/Groom
Finder

MMS

Verify Request

Member Login

User Detail with

Contact Detail

Contact them

Marriage
Data Flow Diagram level: 2.0

40
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

Admin

MMS

Create
MMS database
Admin

Check User Yes

Profile

Delete MMS database

Figure 9.27: Data Flow Diagram level: 2.0

41
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

E-R Diagram
The Entity-Relationship(ER) models a conceptual data model, capable of describing the
data requirements for a new information system in a direct ,easy to understand graphical
notation, to express their understanding of what the planned database is intended to do and how
it might work, and to communicate about the database through a common language

SYMBOL USED RELATIONSHIP

Ellipse

-shows attribute

Rectangle

-Entity class

Double ellipse

-multivalve attribute

Dotted ellipse

A Decision Node: Is used to represent a test

condition to ensure that the control flow or object
flow only goes down one path

Connector to connect entities and relationship among

them.

42
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

E-R Diagram For User

UserName Password
UserName Password

Type Admin

Common Login
Common_
Admin
Register_
Admin
Register_Comm
onLogin

Category
MobileNo

Name EmailID
Day ID

Month

SponcerID

Register

SponcerName
PackageDetails
Year
UniqueID

AccountN
Password
o
Activation
UserName

43
 MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

E-R Diagram For Admin

CasteID Name

UserName Password

Activatio ID Caste
n

Register
Admin

Admin_
Caste

Admin_regist
er

Category
ReligionID Name

Admin_
Religion
Religio
n

Admin_
Religion
Religio
n

ReligionID Name

Figure 9.16: E-R Diagram For Admin

44
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

6…

Testing

 Testing Plan
 Testing Strategy
 Testing Methods

45
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

6.1)TESTING PLAN:-
 Development of a complex client/server three tier application requires that a methodology be
developed for more effective application or software testing and quality assurance. Testing is
made to find errors in the application. The strategy adopted for the testing in our application.

6.2)TESTING STRATEGY:-

“Testing cannot show the absence of defect. It can only show that software

errors are present.”

 Testing is the process of executing a program with the explicit intention of finding errors
that is, making the program fail. Testing is very crucial and most expensive phase of the
software development. Before delivering the system, the process of rigorous testing is
done to check that software works as it is expected and meets its specifications. For that
two testing strategies are there Code Testing & Specification Testing. We have used both
of them at different levels of code development.

 TESTING (WHITE BOX TESTING)

 The code-testing strategy examines the logic of the program. To follow this testing
method, test cases should be developed that result in executing every instruction in the
program or module; that is, every path through the program is tested. A path is a specific
combination of conditions that is handled by the program.
This testing is used at initial stage of the development, as code volume is very less at this
stage. It checks only the aspects are implemented correctly or not.

46
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

But this strategy does not indicate the code meets its specifications nor does it determine
weather all aspects are even implemented. So with this, another strategy is also used.

 SPECIFICATION TESTING (BLACK BOX TESTING)

 In this strategy, the specifications stating what the program should do and how it
should perform under various conditions are examined. Test cases are developed for
each condition or combination of conditions
 The analyst does not look into the program to study the code and is not concerned
about weather every instruction or path through the program is tested. This is more
efficient method, since it focuses on the way software is expected to be used.

6.3)TESTING METHODS:-

 Different types of testing method are used,

 UNIT TESTING:-
 In it analyst tests the program making up a system. The software units in a system
are the modules and routines that are assembled and integrated to perform a
specific function.
 It focuses on modules, independently of one another, to locate errors. This enables
the tester to detect errors in coding and logic that are contained within the module
alone.

 Bottom-Up Unit Testing:-

 It can be performed from the bottom up, starting with the smallest and lowest-
level modules and proceeding one at a time. For each module in bottom-up

47
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

testing, a short program executes the module and provides the needed data, so that
the module is asked to perform the way it will when embedded within the larger
system.

 Top-Down Unit Testing:-

 As the name implies, begins with the upper-level modules. However, since the
detailed activities usually performed in lower-level routines are not provided,
stubs are written. A sub is a module can be called by the upper-level module and
that, when reached properly, will return a message to the calling module,
indicating a proper interaction occurred.

 SYSTEM TESTING:-
 System testing does not test the software per se but rather the integration of each
module in the system. It also tests o find discrepancies between the system and its
original objective, current specifications and system documentation.
 The primary concern is the compatibility of individual modules. Analysts are
trying to find areas where modules have been designed with different
specifications.

48
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

8…

Conclusion

49
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

FUTURE ENHANSEMENT AND CONCLUSION

 The Matrimonial management system is a full-featured ready to

implement matrimonial management system that allows you to
create the look that you want, and the powerful functionality that
the system offers. It’s easy and inexpensive to start and manage
it in the long term.

 The Matrimonial management system is a full-featured ready to implement matrimonial

management system that allows you to create the look that you want, and the powerful
functionality that the system offers.
 It’s easy and inexpensive to start and manage it in the long term.

50
MATRIMONIAL MANAGEMENT ENROLLMENT NO: 160260107008
SYSTEM 160260107009
160260107011

9…

Bibliography
 WEBSITE:-

 www.phptutorial.com

 www.w3school.com

 BOOK:-

 The Joy of PHP Programming: A Beginner's Guide – by Alan Forbes.

 PHP & MYSQL Novice to Ninja – by Kevin Yank.

 Head First PHP & MYSQL – by Lynn Breighley& Michael Morrison.

 Learning PHP, MYSQL, JavaScript, and CSS: A Step-by-Step Guide to Creating

Dynamic Websites – by Robin Nixon.

51