Software Requirement Specification

for

MATRIMONIAL WEB SERVICE

Prepared by

Group No. : 8

Niranjan K M160061CA
Bijith Raj B M160053CA
Bhaskar Behera M160054CA
Akash Kumar M160048CA
Rishabh Prakash M160042CA
Arpith Nilekani M160066CA

CONTENTS
1 INTRODUCTION

1.1 DOCUMENT PURPOSE……………………………………………………………...

1.2 PRODUCT SCOPE………………………………………………………………….
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW……………………….
1.4 DEFINITION,ACRONYMS AND ABBREVIATION……………………………....
1.5 REFERENCES AND ACKNOWLEDGEMENTS………………………………...

2 OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE………………………………………………………..

2.2 PRODUCT FUNCTIONALITY……………………………………………………..
2.3 USERS AND CHARACTERISTICS………………………………………………
2.4 OPERATING ENVIRONMENT……………………………………………………
2.5 DESIGN AND IMPLEMENTATION CONSTRAINTS…………………………..
2.6 USER DOCUMENTATION………………………………………………………..
2.7 ASSUMPTIONS AND DEPENDENCIES………………………………………..

3 SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACE REQUIREMENTS…………………………………..

3.2 FUNCTIONAL REQUIREMENTS……………………………………………….
3.3 BEHAVIOUR REQUIREMENTS………………………………………………...

4 OTHER NON-FUNCTIONAL REQUIREMENTS

4.1 PERFORMANCE REQUIREMENTS…………………………………………...

4.2 SAFETY AND SECURITY REQUIREMENTS………………………………...
4.3 SOFTWARE QUALITY ATTRIBUTES………………………………………...

1.INTRODUCTION
1.1 Document Purpose
The purpose of the document is to find the match between bride/groom according to
their age, religion or caste. The basic purpose of SRS is to describe the complete
behaviour of the software proposed.

1.2 Product Scope

Most of the Indian parents prefer to arrange marriages.As India most popular country there is an
availability of plenty of potential users who may use this service.This service will provide a platform to the
user to find their perfect match.

1.3 Intended Audience and Document

Overview
This document is intended for the developers, client, and mentors.The next chapter Overall
description gives an overview of the functionality of the product.It describes the informal
requirements and it used to established a context for the technical requirements specification in
the subsequent chapters.The third chapter requirements specification of this document is written
primarily for the developers and describes in technical terms the details of the functionality of
the product.The last chapter of this documents describes the non-functional requirements of the
product.All the chapters of the document describe the same software product but are intended
for the different audience.

1.4 Definitions, Acronyms and

Abbreviations
User Refers to the individuals searching for their life partner and are registered
to this service.

Admin Refers to the individual who is handling this website.

1.5 References and Acknowledgments

[1] Software Engineering by Somerville 9th edition.
[2] www.jeevansathi.com
[3] www.manorama.com
 2.OVERALL DESCRIPTION

2.1 Product Perspective

The webpages are present to provide user interface on the user side. The user can search for
their potential matches whose profiles are stored in the database.

2.2 OVERALL DESCRIPTION

2.2.2 Product Functionality

This application provides a set of functions

a) Admin Module
The admin module has three main functions: Login, Report Generation and
Logout.

b) User Registration Module Here a new user can register for the website. The user can
create a user id, a password, enter their personal details, upload photos and perform
Other basic registration functions. The user can also choose a premium paid account
which provides certain added features.

c) Login Module
If a user is already registered, he/she can login by entering their user id and
password.

d) Creating Album
 Here the user can upload an album containing their photos.

e) Search Module
Here the user can search for their desired partners based on certain filters like
religion, age, location etc.

f) Sending Express Interest

On liking a profile, the user can send an “express interest” to notify the other
person that the user is interested in establishing a connection between them.

g) Sending Personal Message

If the person accepts the “express interest”, the user can send a personal
message to them. If the user is a premium member, then they can directly send a
personal message without even sending an “express interest”.

h) Profile Management Module

Here the user can edit their profiles. They can edit their information, add photos,
add albums and delete albums and so on.

i) Compatibility Questions
The user can set some personal questions to be answered by a potential match.
The user can rate those answers. The person is graded after those answers.
This can be sorted to find the highest rated matches.

2.3 Users and Characteristics

User: The user is the individual searching for their potential spouse. They can create their user
profile, search for potential matches, answer their compatibility questions, send “express
interests” and send personal messages.

Admin: The administrator can view all the profiles and generate reports.

2.4 Operating Environment

Any system which has a web browser and an internet connection is required for the
implementation of this application.

2.5 Design and Implementation Constraints

Some limitations are to be taking into consideration related to reliability and security. The
system should be designed in such a way that no third party must be able to access or edit your
account. The service must also be available at all times, and must be resistant to database,
network and other failures. The users also do not have direct access to the database. Also there
is not cash payment for premium users. Only online payment is possible.

2.6 User Documentation

A specific documentation should be prepared for the maintenance of the application and
should describe the application in the simplest way.

2.7 Assumptions and Dependencies

● Administrator has the authority to remove a fake account if enough reports are
acquired.

3.SPECIFIC REQUIREMENTS

3.1 External Interface Requirements

3.1.1 User Interface

The user needs to register by providing their details. After registration the user must
login. The users who are logged in will be able to see the following buttons.
Search: This allows the user to search for a potential candidate
Edit Profile: This allows the make changes to edit his/her profile.
View Matches: This allows the user to view the people with whom they have already matched.
Compatibility Questions: This allows the user to set questions to be answered by people who
visit their profile.
Compatibility Matches: This shows an ordered list of the matches based on the grading given
by the users.

3.1.2 Software Interfaces

Server-side software
● Server-side scripting tools: PHP
● Database tools: MySQL

Client-side Software
● Compatible Operating System: Any Operating System with an internet connection
and web browser.

Software used for development

● Languages: HTML, CSS, JavaScript

3.1.3 Communication Interfaces

PHP acts as a communication interface between user and database.

3.2 Functional Requirements

3.2.1 Registration

Use Case Name Registration

XRef 3.3.2

Trigger None

Precondition The user must fill all the mandatory field.

Basic Path 1.The user fills the details and upload the photo.
2.Clicks the Registration option.
3.If all the details are correct and upload photo size is less than
500kb.The user is registered.
 4.Otherwise,The user have to Register again.
5.User can clear all the field and again start the register process.

Alternative Paths None.

Postcondition None.

3.2.2 Login

Use Case Name Login

XRef 3.3.3

Trigger The user clicks the Login option.

Precondition The user must register first.

Basic Path 1.The user enters the Username and Password

2.Clicks the Login option.
3.If both Username and Password are correct,The user is logged in.
4.Otherwise,the user clicks on forget password option and a security
Question is displayed.
5.The user can set the password and login by answering the security
question correctly.

Alternative Paths None.

Postcondition None.

3.2.3 Creating Album

Use Case Name Creating Album

XRef 3.2.3

Trigger The user clicks the Create album option.

Precondition The user must logged in.

Basic Path 1.The user can upload new photo in the album.
2.The user can rename the photo name.
3.The user can also remove the photo from the album.

Alternative Paths None.

Postcondition A new album will be displayed. .

3.2.4 Searching

Use Case Name Searching

XRef 3.3.6

Trigger The user clicks the search option.

Precondition The user must logged in.

Basic Path 1.The user have to type in search bar.

2.The user can use the filters by
Country,State,City,Religion,Profession and Age.

Alternative Paths None.

Postcondition The results will be displayed..

3.2.5 Sending Express Interest

Use Case Name Sending Express Interest

XRef 3.3.8

Trigger The user clicks the Express interest option.

Precondition The user have to searched first.

Basic Path 1.The User sends an Express Interest.

Alternative Paths None.

Postcondition The other person will receive it. .

3.2.6 Sending Personal Messages

Use Case Name Sending Personal Messages

XRef 3.3.7

Trigger The user clicks the Chat option.

Precondition The other person must have accepted the sent Express Interest.

Basic Path 1.The user can chat through the message box.
2.If user has premier account then he/she not needs to send the
Express Interest.

Alternative Paths None.

Postcondition The other person will receive the message.

3.2.7 Compatibility Questions

Use Case Name Compatibility Questions

XRef 3.3.5

Trigger The user clicks the Ask question option.

Precondition The user must logged in first.

Basic Path 1.The user can set certain question to help figure out their desired
partner.
2.Providing marks to the question based on the answer can be useful
in ranking the candidate.
3.Based on the marks user can sort the candidate and he/she can
select the better partner.

Alternative Paths None.

Postcondition None.

3.3 Behaviour Requirements

3.3.1 Use Case View

3.3.2 Registraion Use Case
Description
Before using the system the user must have to register in the system.He have to fill up the form
and enter the details in the form provided.

3.3.3 Login Use Case

Description
The existing users are giving his/her userid&password to access their accounts.
If they are successfully login they can edit or update their accounts.

3.3.4 Edit Profile

Description

The user can also edit his/her personal profile in the system but first he/she have to login in the
system

3.3.5 Compatibility Questions

Description

Each user can set certain questions to help figure out their desired partner.Providing marks to
the question based on the answers can be useful in ranking the candidates.Automatic ordering
of the candidates based on the marks will be helpful to select the ideal candidate.

3.3.6 Searching
Description
After login in ,the user can search their partners by the filters provided in the
system like religion,caste,age etc.

3.3.7 Sending Personal Message

Description
If the person accepts the “express interest”, the user can send a personal
message to them. If the user is a premium member, then they can directly send a
personal message without even sending an “express interest”.

3.3.8 Sending Express Interest

Description
On liking a profile, the user can send an “express interest” to notify the other
person that the user is interested in establishing a connection between them.

3.4 Admin Use Case View

3.4.1 Login
Description
Admin can login to system and they can manage the users.

3.4.2 Report Generation

Description
The admin can generate the reports about the users using the system.
3.4.3 Delete Account
Description
The admin can remove the accounts if the particular account is reported by many number of
users.

4.OTHER NON-FUNCTIONAL REQUIREMENTS

4.1 Performance Requirements

Some Performance requirements identified is listed below:

● Good memory space is required.
● Should be error free and perform fast.
● Large amount of data should be handled easily.

4.2 Safety and Security Requirements

Some of the factors that are identified to protect the application from are described below:
● Database backups can be done regularly.
● Check data integrity for critical variables.
● Encryption technique provides security to the account.
● Administrator and the user, who have their own username and password have the only
right to access the service.

4.3 Software Quality Attributes

4.3.1 Portability Requirement

The application can be used on any mobile, pc or laptop having an internet connection and a
web browser.

4.3.2 Reliability
● All the data for user stored must be in the database.
● Avoid incorrect storage of records in the database.

4.3.3 Maintainability

Regular backups can be useful for the maintainability of the service

4.3.4 Usability Requirement

Some of the usability requirements identified for this system are listed below: • A logical
interface is essential to use an application in an easy way, speeding up common tasks.