16it476.docx
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View 16it476.docx as PDF for free.
More details
- Words: 1,622
- Pages: 9
IT Sem-6
Online Matrimonial System
SOFTWARE REQUIREMENT SPECIFICATION FOR ONLINE MATRIMONIAL SYSTEM 16IT425 – SAGAR AKBARI
16IT425
1
IT Sem-6
Online Matrimonial System
Contents: 1. Introduction 1.1. Purpose 1.2. Scope 2. General Description 2.1. Basic Description 2.2. Feasibility Study 2.2.1. Technical Feasibility 2.2.2. Operational Feasibility 2.2.3. Implementation Feasibility 2.2.4. Economic Feasibility 2.2.5. Resource Feasibility 2.2.6. Market Feasibility 3. Functional Requirement 3.1. Modules 3.1.1. Registration 3.1.2. Login 3.1.3. User Info 3.1.4. Payment 3.1.5. Searching 3.1.6. Chatting 3.2. Users 4. Non-Functional Requirement 4.1. Security 4.2. Reliability 4.3. Availability 4.4. Portability 4.5. Reusability 5. Interface Requirement 5.1. Hardware 5.2. Software
16IT425
2
IT Sem-6
Online Matrimonial System
1. INTRODUCTION 1.1. PURPOSE Matrimonial Website which provides a platform to a lot of bride/groom to find their perfect match. The matrimonial site will help even the parents of the bride and groom to search for the life partners of their children. People can directly search for their match and after payment can contact any person of their liking and start chatting online.
1.2. SCOPE It will help connect two people wanting to get married of any caste, religion or colour. They can search for their match and start chatting with them once they find one.
2. GENERAL DESCRIPTION 2.1. BASIC DESCRIPTION This system allows an individual to go to a website and search for bride/groom for themselves or their daughter/son. Once they have made an account, they can add information about themselves and start looking at profiles of other people registered on the website. After payment, they can start contacting and chatting with the people they match with.
2.2. FEASIBILITY STUDY 2.2.1. TECHNICAL FEASIBILITY The user just needs a internet connected device with a browser with which s/he can access the website. There will be a database in the backend which will store all the data and have matching algorithms stored on cloud server. This is highly feasible.
2.2.2. OPERATIONAL FEASIBILITY The user can only search for people from the database according to the filters they set and only after they have done payment can they have the contact info for the person of their liking. Therefore, this is operational feasible.
2.2.3. IMPLEMENTATION FEASIBILITY This is easy to implement as the users only need a device with a working internet connection and a browser and account on the website which are stored on database on a cloud server. 16IT425
3
IT Sem-6
Online Matrimonial System
2.2.4. ECONOMIC FEASIBILITY The cloud servers are very cheap to maintain. The user has to pay only one time for getting the contact info of their matches.
2.2.5. RESOURCE FEASIBILITY The resources needed are only a device with working internet connection and a browser and an email id or mobile no for registration.
2.2.6. MARKET FEASIBILITY This system is useful for all people looking to find a bride/groom. Even parents who want to marry their children can use this system to find bride/groom for their children.
3. FUNCTIONAL REQUIREMENTS 3.1. MODULES 3.1.1. REGISTRATION The consumer will go to the website and will register using a verified email address or mobile no. and provide basic information such as name, address and password. The admin must be able to register new managers into the system.
3.1.2. LOGIN The consumer can login anytime into the system using the registered email and password. The managers login to contact new people and send messages to the users regarding various offers. The admin logs in to make the necessary changes to the database.
3.1.3. USER INFO The consumer has to add their user info such as their biodata and other details which can be used as filters for shortlisting people with similar choices. The managers are able to see the contact information and payment history and suggest offers to various users accordingly.
16IT425
4
IT Sem-6
Online Matrimonial System
3.1.4. PAYMENT The consumer has to make a one-time payment of Rs. 3999 for contacting their matches. The user can make the payment using net banking, online wallet or using credit/debit card. The managers are responsible
3.1.5. SEARCHING The consumer can search according to their choices and add additional filters to shortlist their choices. Also, users who have shortlisted them are shown in the list.
3.1.6. CHATTING The user can chat with their matches once they have made payment. The user can share other documents as well as use emotes while chatting.
3.2. USERS 3.2.1. ADMIN There is an authorization process. If you login as an admin, you will be redirected to the admin homepage and if you are a simple user you will be redirected to simple account homepage. Admin can perform the following functions:
Add/Delete/Update account
Withdrawal/Deposit/Statement transactions
Account Information
User Details List
Active/Inactive account
View Transaction History
3.2.2. USER A simple user can access their account and add their user info and make payment and see their transaction history and search and chat and can change their user info.
16IT425
5
IT Sem-6
Online Matrimonial System
3.2.3. MANAGER A manager can use or access the bank management system for checking out the user’s transactions and notify the user via email or message through user’s mobile no. and contact new people regarding the website.
4. NON-FUNCTIONAL REQUIREMENTS 4.1. SECURITY The payment is done using third party secured payment gateway thus minimising risk of online monetary fraud. The users are given access to various parts of the site according to their payment status as well as their user type.
4.2. RELIABILITY All the data is stored is stored on the cloud servers which are very reliable. The only problem may be the internet connection as the website can’t be opened without an internet connection.
4.3. AVAILABILITY The user can access the website from any location in the world as long as a device with internet connection is available and the user can login with the correct username and password.
4.4. PORTABILITY The website can be opened from any device such as computer, laptop, tablet, phone as long as it is connected with the internet and a browser is installed on it.
4.5. REUSABILITY The database can be used to give ads to the users. The modules of login, registration and user info can be reused on any website.
5. INTERFACE REQUIREMENT 5.1. HARDWARE REQUIREMENT
Rented cloud server
Workstation for maintain the website
5.2. SOFTWARE REQUIREMENT
16IT425
6
IT Sem-6
Online Matrimonial System
MySQL database to store user data
Website development using Bootstrap
Backend using AJAX or NodeJS
6. DATA DICTIONARY 6.1. REGISTRATION/LOGIN TABLE
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
Username
Varchar (10)
Primary Key
To Store User Name
3
Password
Varchar (10)
Not Null
To Store Password
4
User Type
Varchar (10)
Not Null
To Store User Type
5
Email
Varchar (40)
Not Null
To Store Email ID
6
Mobile No
INT (10)
Not Null
To Store Mobile No
6.2. USER INFO TABLE Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
Username
Varchar (10)
Foreign Key
To Store the User Name
3
F_Name
Varchar (10)
Not Null
To Store First Name
4
L_Name
Varchar (10)
Not Null
To Store Last Name
5
Email
Varchar (40)
Foreign Key
To Store Email ID
6
Mobile No
INT (10)
Foreign Key
To Store Mobile Number
7
Address_Line_1
Varchar (40)
Not Null
To Store Line 1 of Address
8
Address_Line_2
Varchar (40)
Not Null
To Store Line 2 of Address
9
City
Varchar (10)
Not Null
To Store City
10
State
Varchar (10)
Not Null
To Store State
11
Country
Varchar (10)
Not Null
To Store Country
12
Languages
Varchar (30)
Not Null
To Store Languages Known
13
Caste
Varchar (30)
Not Null
To Store Caste
16IT425
7
IT Sem-6
Online Matrimonial System
14
Marital Status
Varchar (20)
Not Null
To Store Marital Status
15
Height
Float
Not Null
To Store Height
16
Weight
Float
Not Null
To Store Weight
17
Zodiac
Varchar (20)
Not Null
To Store Zodiac Sign
18
Education
Varchar (40)
Not Null
To Store Education Status
19
Occupation
Varchar (40)
Not Null
To Store Occupation
20
Salary
Float
Not Null
To Store Salary
21
Images
Clob
Not Null
To Store Images
22
Biodata
Varchar (200)
Not Null
To Store Biodata
6.3. PAYMENT TABLE
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
Username
Varchar (10)
Foreign Key
To Store the User Name
3
Mobile No
INT (10)
Foreign Key
To Store Mobile Number
4
Email
Varchar (40)
Foreign Key
To Store Email
5
Paid Status
Varchar
Not Null
Stores the paid status of user
6
Start_Date
Datetime
Not Null
Stores the start date of account
7
End_Date
Datetime
Not Null
Stores the end date of account
8
Payment_Date
Datetime
Not Null
Stores the date of payment
6.4.
SEARCH SETTING
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Primary Key
To Store Serial Number
2
Username
Varchar (10)
Foreign Key
To Store the User Name
3
Caste
Varchar (30)
Not Null
To Store Caste
4
Marital Status
Varchar (20)
Not Null
To Store Marital Status
5
Height
Float
Not Null
To Store Height
6
Zodiac
Varchar (20)
Not Null
To Store Zodiac Sign
16IT425
8
IT Sem-6
Online Matrimonial System
7
Education
Varchar (40)
Not Null
To Store Education Status
8
Occupation
Varchar (40)
Not Null
To Store Occupation
9
Images
Clob
Not Null
To Store Images
6.5.
Chat Table
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
From
Varchar (20)
Foreign Key
Stores the name of sender
3
To
Varchar (20)
Not Null
Store the name of receiver
4
Messages
Varchar
Not Null
To Store messages
16IT425
9
Online Matrimonial System
SOFTWARE REQUIREMENT SPECIFICATION FOR ONLINE MATRIMONIAL SYSTEM 16IT425 – SAGAR AKBARI
16IT425
1
IT Sem-6
Online Matrimonial System
Contents: 1. Introduction 1.1. Purpose 1.2. Scope 2. General Description 2.1. Basic Description 2.2. Feasibility Study 2.2.1. Technical Feasibility 2.2.2. Operational Feasibility 2.2.3. Implementation Feasibility 2.2.4. Economic Feasibility 2.2.5. Resource Feasibility 2.2.6. Market Feasibility 3. Functional Requirement 3.1. Modules 3.1.1. Registration 3.1.2. Login 3.1.3. User Info 3.1.4. Payment 3.1.5. Searching 3.1.6. Chatting 3.2. Users 4. Non-Functional Requirement 4.1. Security 4.2. Reliability 4.3. Availability 4.4. Portability 4.5. Reusability 5. Interface Requirement 5.1. Hardware 5.2. Software
16IT425
2
IT Sem-6
Online Matrimonial System
1. INTRODUCTION 1.1. PURPOSE Matrimonial Website which provides a platform to a lot of bride/groom to find their perfect match. The matrimonial site will help even the parents of the bride and groom to search for the life partners of their children. People can directly search for their match and after payment can contact any person of their liking and start chatting online.
1.2. SCOPE It will help connect two people wanting to get married of any caste, religion or colour. They can search for their match and start chatting with them once they find one.
2. GENERAL DESCRIPTION 2.1. BASIC DESCRIPTION This system allows an individual to go to a website and search for bride/groom for themselves or their daughter/son. Once they have made an account, they can add information about themselves and start looking at profiles of other people registered on the website. After payment, they can start contacting and chatting with the people they match with.
2.2. FEASIBILITY STUDY 2.2.1. TECHNICAL FEASIBILITY The user just needs a internet connected device with a browser with which s/he can access the website. There will be a database in the backend which will store all the data and have matching algorithms stored on cloud server. This is highly feasible.
2.2.2. OPERATIONAL FEASIBILITY The user can only search for people from the database according to the filters they set and only after they have done payment can they have the contact info for the person of their liking. Therefore, this is operational feasible.
2.2.3. IMPLEMENTATION FEASIBILITY This is easy to implement as the users only need a device with a working internet connection and a browser and account on the website which are stored on database on a cloud server. 16IT425
3
IT Sem-6
Online Matrimonial System
2.2.4. ECONOMIC FEASIBILITY The cloud servers are very cheap to maintain. The user has to pay only one time for getting the contact info of their matches.
2.2.5. RESOURCE FEASIBILITY The resources needed are only a device with working internet connection and a browser and an email id or mobile no for registration.
2.2.6. MARKET FEASIBILITY This system is useful for all people looking to find a bride/groom. Even parents who want to marry their children can use this system to find bride/groom for their children.
3. FUNCTIONAL REQUIREMENTS 3.1. MODULES 3.1.1. REGISTRATION The consumer will go to the website and will register using a verified email address or mobile no. and provide basic information such as name, address and password. The admin must be able to register new managers into the system.
3.1.2. LOGIN The consumer can login anytime into the system using the registered email and password. The managers login to contact new people and send messages to the users regarding various offers. The admin logs in to make the necessary changes to the database.
3.1.3. USER INFO The consumer has to add their user info such as their biodata and other details which can be used as filters for shortlisting people with similar choices. The managers are able to see the contact information and payment history and suggest offers to various users accordingly.
16IT425
4
IT Sem-6
Online Matrimonial System
3.1.4. PAYMENT The consumer has to make a one-time payment of Rs. 3999 for contacting their matches. The user can make the payment using net banking, online wallet or using credit/debit card. The managers are responsible
3.1.5. SEARCHING The consumer can search according to their choices and add additional filters to shortlist their choices. Also, users who have shortlisted them are shown in the list.
3.1.6. CHATTING The user can chat with their matches once they have made payment. The user can share other documents as well as use emotes while chatting.
3.2. USERS 3.2.1. ADMIN There is an authorization process. If you login as an admin, you will be redirected to the admin homepage and if you are a simple user you will be redirected to simple account homepage. Admin can perform the following functions:
Add/Delete/Update account
Withdrawal/Deposit/Statement transactions
Account Information
User Details List
Active/Inactive account
View Transaction History
3.2.2. USER A simple user can access their account and add their user info and make payment and see their transaction history and search and chat and can change their user info.
16IT425
5
IT Sem-6
Online Matrimonial System
3.2.3. MANAGER A manager can use or access the bank management system for checking out the user’s transactions and notify the user via email or message through user’s mobile no. and contact new people regarding the website.
4. NON-FUNCTIONAL REQUIREMENTS 4.1. SECURITY The payment is done using third party secured payment gateway thus minimising risk of online monetary fraud. The users are given access to various parts of the site according to their payment status as well as their user type.
4.2. RELIABILITY All the data is stored is stored on the cloud servers which are very reliable. The only problem may be the internet connection as the website can’t be opened without an internet connection.
4.3. AVAILABILITY The user can access the website from any location in the world as long as a device with internet connection is available and the user can login with the correct username and password.
4.4. PORTABILITY The website can be opened from any device such as computer, laptop, tablet, phone as long as it is connected with the internet and a browser is installed on it.
4.5. REUSABILITY The database can be used to give ads to the users. The modules of login, registration and user info can be reused on any website.
5. INTERFACE REQUIREMENT 5.1. HARDWARE REQUIREMENT
Rented cloud server
Workstation for maintain the website
5.2. SOFTWARE REQUIREMENT
16IT425
6
IT Sem-6
Online Matrimonial System
MySQL database to store user data
Website development using Bootstrap
Backend using AJAX or NodeJS
6. DATA DICTIONARY 6.1. REGISTRATION/LOGIN TABLE
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
Username
Varchar (10)
Primary Key
To Store User Name
3
Password
Varchar (10)
Not Null
To Store Password
4
User Type
Varchar (10)
Not Null
To Store User Type
5
Varchar (40)
Not Null
To Store Email ID
6
Mobile No
INT (10)
Not Null
To Store Mobile No
6.2. USER INFO TABLE Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
Username
Varchar (10)
Foreign Key
To Store the User Name
3
F_Name
Varchar (10)
Not Null
To Store First Name
4
L_Name
Varchar (10)
Not Null
To Store Last Name
5
Varchar (40)
Foreign Key
To Store Email ID
6
Mobile No
INT (10)
Foreign Key
To Store Mobile Number
7
Address_Line_1
Varchar (40)
Not Null
To Store Line 1 of Address
8
Address_Line_2
Varchar (40)
Not Null
To Store Line 2 of Address
9
City
Varchar (10)
Not Null
To Store City
10
State
Varchar (10)
Not Null
To Store State
11
Country
Varchar (10)
Not Null
To Store Country
12
Languages
Varchar (30)
Not Null
To Store Languages Known
13
Caste
Varchar (30)
Not Null
To Store Caste
16IT425
7
IT Sem-6
Online Matrimonial System
14
Marital Status
Varchar (20)
Not Null
To Store Marital Status
15
Height
Float
Not Null
To Store Height
16
Weight
Float
Not Null
To Store Weight
17
Zodiac
Varchar (20)
Not Null
To Store Zodiac Sign
18
Education
Varchar (40)
Not Null
To Store Education Status
19
Occupation
Varchar (40)
Not Null
To Store Occupation
20
Salary
Float
Not Null
To Store Salary
21
Images
Clob
Not Null
To Store Images
22
Biodata
Varchar (200)
Not Null
To Store Biodata
6.3. PAYMENT TABLE
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
Username
Varchar (10)
Foreign Key
To Store the User Name
3
Mobile No
INT (10)
Foreign Key
To Store Mobile Number
4
Varchar (40)
Foreign Key
To Store Email
5
Paid Status
Varchar
Not Null
Stores the paid status of user
6
Start_Date
Datetime
Not Null
Stores the start date of account
7
End_Date
Datetime
Not Null
Stores the end date of account
8
Payment_Date
Datetime
Not Null
Stores the date of payment
6.4.
SEARCH SETTING
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Primary Key
To Store Serial Number
2
Username
Varchar (10)
Foreign Key
To Store the User Name
3
Caste
Varchar (30)
Not Null
To Store Caste
4
Marital Status
Varchar (20)
Not Null
To Store Marital Status
5
Height
Float
Not Null
To Store Height
6
Zodiac
Varchar (20)
Not Null
To Store Zodiac Sign
16IT425
8
IT Sem-6
Online Matrimonial System
7
Education
Varchar (40)
Not Null
To Store Education Status
8
Occupation
Varchar (40)
Not Null
To Store Occupation
9
Images
Clob
Not Null
To Store Images
6.5.
Chat Table
Sr.No
Name
Datatype
Constraint
Description
1
Sr.No
INT
Not Null
To Store Serial Number
2
From
Varchar (20)
Foreign Key
Stores the name of sender
3
To
Varchar (20)
Not Null
Store the name of receiver
4
Messages
Varchar
Not Null
To Store messages
16IT425
9
More Documents from "sec"
Test.docx
December 2019 14
16it425 Oms.docx
December 2019 19
Is & Cyber Law - Copy.docx
December 2019 22
16it429(se).docx
December 2019 20
Se Practical 2 (sample Srs Document).docx
December 2019 15