1

Online Matrimonial Application System

SOFTWARE REQUIREMENT SPECIFICATION SUBMITTED TO

MANIPAL UNIVERSITY,
MANIPAL

(A Deemed University)

FOR THE PARTIAL FULLFILLMENT OF THE DEGREE OF

MASTER OF COMPUTER APPLICATION

By

Prakash.A 080919055

Gopal Krishna 080919081

Sushant Kumar Das 070919058

Guided By:

Tojo Thomas
Poornima

Software Requirements Specifications Documen

 2

Table of Contents
Purpose 2
Scope 3
Definitions, Acronyms, and Abbreviations. 3
1.4 References 4
1.5 Overview 4

2. The Overall Description 4

2.1 Product Perspective: 4

2.3 User Characteristics: 5
2.5 Assumptions and Dependencies: 5

3. Specific Requirements 5
3.1 External Interfaces 5
3.1.1 User Interfaces 5
3.1.2 Hardware Interfaces 6
3.1.3 Software Interfaces 6
Functional Requirement 6
3.4 Software System Attributes 8
3.4.1 Usability 8
3.4.3 Availability 8
3.4.4 Security 8
3.4.6 Portability 9

1 Introduction
Purpose

The main objective of this document is to illustrate the requirements of the

project Online Matrimonial Applicaton System(OMAS). The document
gives detailed description of the both functional and non functional
requirements proposed by the client. The document is developed after a number
of consultations with the client and considering the complete requirement
specifications of the given Project. The final product of the team will be
meeting the requirements of this document.

Software Requirements Specifications Documen

 3

Scope

Project Title : ONLINE MATRIMONIAL APPLICATION

SYSTEM.
Date : 09-09-2010 Prepared By : Prakash, Gopal
krishna,Sushant
Project Justification:
This project is basically about the website where in users can get online
information about life partner.This organization is in business of matchmaking for
individuals looking for their life partner.
Product Characteristics and Requirements :

1. Secured database.
2. User tracking
3. Search feature
4. Chating feature
5. Users will get a notification mail to remind them in case their matches in
the site,they will get the mail from our operator.
Project Management Deliverables:
Project plan, Scope statement, Project charter, Training manuals
Product-related deliverables :
Research reports ,design documents, software code, test plan
Project Success Criteria: Our main goal is to complete this

project within allotted dead line, capturing the benefits and meet

the requirements of the users.

Definitions, Acronyms, and Abbreviations.
ORE-Online Matrimonial Application System.
GUI-Graphical User Interface.
RAM - Random Access Memory.
SRS : Software Requirement Specification.
• Agent: Registered Users.
• Maintainability - is the ease and speed with which any maintenance activity can be
carried out on an item of equipment.
• Fault Tolerance –Fault-tolerant describes a computer system or component designed so
that, in the event that a component fails, a backup component or procedure can
immediately take its place with no loss of service.

Software Requirements Specifications Documen

 4

• Portability- is the task of doing any work necessary to make the computer program run
in the new environment.
• Reliability - extent to which program performs with required precision.
• Usability - effort required to learn, operate, prepare input, and interpret output.

1.4 References
The SRS document uses the following documents and web sites as references:
-An Integrated Approach To Software Engineering - Pankaj Jalote
http://www.zillow.com/
http://www.trulia.com/

1.5 Overview
The SRS will provide a detailed description of the Online Matrimonial Application
System. This document will provide the outline of the requirements, overview of the
characteristics and constraints of the system.

1.5.1 Section 2: This section of the SRS will provide the general factors that affect the
product and its requirements. It provides the background for those requirements. The
items such as product perspective, product function, user characteristics,assumptions and
dependencies are described in this section.

1.5.2 Section 3: This section of SRS contains all the software requirements mentioned
in section 2 in detail sufficient enough to enable designers to design the system to satisfy
the requirements and testers to test if the system satisfies those requirements.

1.5.3 Section 4: This section of the SRS contains ER diagram,Schema diagram,DFD.

2. The Overall Description

2.1 Product Perspective:

The proposed Online Matrimonial Application System(OMAS) which is being
developed is a System that will provide a information about person nothing but life
partner.He/She can find his/her life partner based on his/her qualification,height,cast and
second marriage.

2.2 Product Functions:

The OMAS System real time information about life partner in the site. The
Product functions are more or less the same as described in the product perspective. The

Software Requirements Specifications Documen

 5

functions of the system include the system providing different type of services based on
the type of users.
• The website provides login facility to the users.
• The Operator should be provide the updated information about person who are
register to this site.
• Provisions for the users to set previlages.He/She can fix priorities also for his
searching.
• The customer can get the information about person thats matches to his/her profile.

2.3 User Characteristics:

There are basically 3 types of users:

• Administrator: Administrator will be able to do anything they want like adding new
agents/users to the system and Permit them with proper access rights.User id and password is
given to the agent by administrator.
• Operator: They are the core users and are able to update the user details according to the
plot/s or building/s that they buy or registered.
• Customer : Users can send mail about their requirnments.

2.4 Design and Implementation constraints:

Each customer must keep their password as confidential. More over the customer
must have individual user names for creating a login in the OMAS system. Only
Administrator can control customer addition and deletion in the system.

2.5 Assumptions and Dependencies:

• The users have sufficient knowledge of computers.

• The users know the English language, as the user interface will be provided in English
• Each User must have a User Id and password
• There is only one Administrator.

3. Specific Requirements
3.1 External Interfaces
3.1.1 User Interfaces

GUI (Graphical User Interface) : This section should include a set of Msg
Box to guide the users in order to illustrate User interface features.

Software Requirements Specifications Documen

 6

3.1.2 Hardware Interfaces

• Any processor above 2.4 GHz

• Hard Disk : 40 GB Or Above
• RAM : 512 MB Or Above

3.1.3 Software Interfaces

• Front End : Net Beans 6.9

• Back End : My sql 5.0 and above.
• Operating System : Windows 2000/Windows XP/Windows Vista
• Platform: J2EE
• Web Servers: Tomcat 6.0
• Web Browsers: Mozilla firefox/Internet Explorer

Functional Requirement

3.2.1 Creation of new User:

Introduction: This process will provide a user account.
Input: User id, user password and other personal details.
Processing: It will store the User id and password if appropriate in the User database.
Output: Appropriate Msg displayed telling account created.

3.2.2 User verification:

Introduction: This process will verify the user id and password.
Input: User id and user password.
Processing: It will verify the User id and password from the User database.
Output: Appropriate Msg displayed based on Verification of User id and password

3.2.3 Deleting User:

Introduction: Delete Existing User.
Input: User id/username.
Processing: Deletion of existing User.
Output: Existing user deleted from Database.

3.2.4 Search Process:

Introduction: Search on cast,qualification,height and second marriage etc.
Input: Search option.

Software Requirements Specifications Documen

 7

Processing: Search based on criteria in database.

Output: Availability and locality with its complete details

3.2.5 Add New Customer:

Introduction:Introducing a new customer.
Input:Username,password and customer details with attractive photo.
Processing: Insertion of new customer details in the database.
Output: New Information gets stored in the Database.

3.2.6 paid user registration:

Introduction: Allows the users to finalise their choice as per their budget.
Input: User Id, password and requirements.
Processing: Search and mailing.
Output: update availability in database.

3.2.9 Following Constraints must be satisfied to meet the Functional

Requirements

• A customer can access profile only which meets his/her requirments .

• An one operator can maintain only 10 person not more then that.
• While performing the search operation any of the criteria must be specified
• user’s account must be updated accordingly.

3.3 Performance Requirements:

It specifies the performance constraints on the software system. There are 2 types of
performance requirements. They are:

3.3.1 Static Requirements: No of Users:

• Customer: has access to browse and find his/her life partner.

• Operator: has access to post advertisements.match the profile.
• Administrator : Access both the above modules.

Software Requirements Specifications Documen

 8

3.3.2 Dynamic Requirements:

• Response time of the search operation should be less then Five second 90% of the
times
• The performance of the overall system should be fast and error free, with built
in error checking and correction facilties.

3.4 Software System Attributes

3.4.1 Usability
• Since all users are familiar with the general usage of GUI, no specific training is
required.
• The system is user friendly and self-explanatory.

3.4.2 Reliability and Fault Tolerance:

Requirements about system behavior in the face of certain kinds of faults is
specified.
• System is reliable for giving correct search results about the books to the users.
• It is fault tolerant because if the system does not find the requested books an
appropriate message is displayed to the users on the screen.

3.4.3 Availability

The system is available 100% for the user and is used 10 hrs a day and 345 days a
year. The system shall be operational 10 hours a day and 7 days a week.

3.4.4 Security
•The system shall check all user-supplied input for malicious content (e.g.,
escape characters, inappropriate markup, and buffer overflow attacks).

• Access shall be controlled with usernames and passwords.

• Passwords shall be checked for quality.

3.4.5 Maintainability

A new developer shall reasonably be able to understand all internal logic of

Component name within 3days

Software Requirements Specifications Documen

 9

3.4.6 Portability

Library Circulation And Management System is potable to system that supports

following

• Any processor above 2.4 GHz

• Hard Disk : 40 GB Or Above
• RAM : 512 MB Or Above
• System must be installed with Net Beans 6.9 and Mysql,Tomcat server.

3.5 Design Constraints:

3.5.1 Standard Compliance: This specifies the requirements for the standards the
system must follow
• Crystal reports must be produced to the users.
• Reports must include database field, formula field, summaries, subtotals and date picker

3.5.2 Hardware Compliance: The software may have to operate on some existing or
predetermined hardware, thus imposing restrictions on the design

• System must support Windows 98 or higher version operating system

• System must have minimum of 512 MB RAM & above.
• System must have hard disk of 40 GB memory
.
3.6 Process Model:
The project undertaken by us is been done under supervision.The requirements and
specifications are well-defined.So the process model we thought to follow is Heirarchical
Model.

3.7 Development Approach:

We used Top Down Approach for the developement of our project. In this approach
hierarchical structure is followed so the complexity is divided into different modules.This
approach requires that the specifications and requirements of the system are clear and everything
is known in advance. Implementation starts from the top of the hierarchy and proceeds to the
bottom of the hierarchy.

3.8 Team Structure:

Software Requirements Specifications Documen

 10

The team structure chose by us is egoless team structure as all team members are
in one level i.e. no one is above or below from any team member. This type of team
structure has the advantage that there is free flow of information between all
programmers and personal factors are less so every one is concerned only about the
successful completion of the project on time.

3.9 Role Of Team Members

User Module: The management of customer details, gathering other requirements and
testing will be handled by Sushant Kumnar das.
Operator Module : The task of registering Users on a paid service base and Coding
shall be handled by Gopal Krishna.
Administrator Module: Testing of both user and operator Module,Detailed designing
will be done by Prakash.A

Data flow diagram:

Use case diagram:

Software Requirements Specifications Documen