Matrimony SRS

1
Matrimony Site Documentation

Introduction
In These Project we basically focus on all the world of people who want to find
their life partner. Our site is made for connect the all these from all over the
world. In this website we provide facilities for all age of member. To provide
suitable match for brides and grooms for
Keralite Christians across the world. No payments to be made by anyone for use o
f application.
Payment to be made to person assisting if so required. We are providing these fa
cilities for people and they can find easily information & news related the diff
erent religions. At these time people want information for any kind of thing & h
ere people can also find upcoming events.
SRS Document
Purpose
The purpose of this project is providing a platform to people for connecting fro
m worldwide. Still there is no any platform for connect on internet through the
website. We are providing these facilities for people and they can find easily i
nformation & news related the different religions. At these time people want inf
ormation for any kind of thing & here people can also find upcoming events.
Scope
Our website provides matrimonial services to all people. In this website provide
matrimonial section where people can register him/her profile and easily find l
ife partner & also you can see news, events and also connecting to different peo
ple to latest information & news.
Background
This Website is based on ASP.NET with c# include 3.5 .NET framework with the sec
urities of managing the accounts and the resources. The Sql Server is used as da
tabase. This website in inspired by the websites which are available on the net
with the new features included. 1
D-Team IT Solutions Pvt. Ltd | Prepared By: SHIBIN V.M
2
Methodology
CLASSICAL WATERFALL MODEL
Software is developed during this phase and at the end of life cycle the product
becomes ready to deliver to customer.
1. Feasibility study
Its main aim is to determine whether it is physically and technically feasible o
r not. It involves analysis of problems and collection of all relevant informati
on. Collected data are analyzed to arrive at following.
-an abstract problem definition -format of different strategies for solving prob
lem. -evaluation of different solution strategies.
Thus during this phase very high level decisions are made.
2. Requirement Analysis
Its aim is to understand exact requirement of customer and to document them prop
erly. There are two activities involved here. i. Requirement gathering &analysis
First requirements are gathered and then analyzed. All relevant
information is then collected from customers to clearly understand needs. Then a
nalysis is done to remove incompleteness and inconsistency.
ii.
Requirement specification Requirements from above stage are organized into softw
are
2
requirement specification document (SRS).SRS to be reviewed and approved by cust
omer. It forms basis of all carrying out all development activities. D-Team IT S
olutions Pvt. Ltd | Prepared By: SHIBIN V.M
3
3. Design
Its goal is to transform requirement specified in SRS into structure suitable fo
r implementation in programming language. In traditional design approach there a
re two activities. i. Structure analysis prepares detail analysis of different f
unction to be supported by system and identification of data flow. Each function
is sub divided and decomposed into sub function. ii. Structure design consists
of architectural design. Where system is decomposed into modules.data structure&
algorithms are designed and documented.
4. Coding &testing
Its aim is to translate software design into source code. To write good programs
coding standards are formulated. It indicates standard ways of laying out progr
am codes, communicating naming conventions, templates for function and modules e
tc. so each component is implemented as a program module. -next each module is u
nit tested. Each module is tested from isolation of other modules then debugging
and documenting it. The correct working of each module is determined individual
ly.
5. Integration &System testing
Different modules are integrated in planned manner. This is done incrementally o
ver number of steps. During each steps previously planned modules are added to p
artially integrated system. It includes 3 kinds of activities
i. ii. iii.
testing: performed by development team. testing: done by friendly set of customers
. Acceptance testing: done by customer himself 3
4
6. Maintance
It involves performing following activities. i. Corrective maintenance Correctin
g errors not discovered during developing product.
Perfective maintenance Improving the implementation and enhance the functionalit
y of the system as per customer needs. iii. Adaptive maintenance Required for pa
rting the software to work in new environment.
ii.
Functional Requirements
View of Database This system provides the view of the entire database, or partia
l view based on the level of the user in the hierarchy. Depending on the databas
e that is selected, the in-built queries might vary. So accordingly the system s
upports number of reports, graphical analysis, based on the users requirement whi
ch will be generally needed to check the trend analysis by the product group. .
Search Depending on the database that is selected, the user can search for speci
fic information regarding a particular entity i.e. this entity could be a BEs pro
gress report database or any internal user for user details database. Accordingl
y there is a facility through which the different parameter values can be search
ed for a particular entity.
Add Depending on the database that is selected, the user can add information of
a new entity. Accordingly the system allows for the creation of new entity and t
akes up relevant related information and save it into the appropriate database.
4
5
Update Depending on the database that is selected, the user can modify some deta
ils under certain parameters for an existing entity. Accordingly the system allo
ws for modifying the details of a certain parameter related to an existing entit
y in a database.
Delete Depending on the database that is selected, the user can delete the recor
d of a particular entity from the database based on certain department policies.
Accordingly the system allows for setting the 'flag' field for the entity under
consideration to 'unset' status, which would be indicative to the system that t
he particular entity should no longer be considered while performing the availab
le set of operations under related Database or the entity should be permanently
deleted from the database.
System Features
Front end (customer storefront) o Members registration o Member account o Member
Search o See Events o News o Feedback o Chatting, emailing
Back end (administrative tools) o Login o Managing User Account o Adding new con
tent o Viewing/Editing/deleting existing content o Adding new members o Viewing/
Editing/deleting existing members o Adding/viewing/deleting existing events D-Te
am IT Solutions Pvt. Ltd | Prepared By: SHIBIN V.M 5
6
o Adding/viewing/deleting latest news o Special offers o Communication o Definin
g Polls o Reports
Front End (Customer Area) Connecting to Application with Valid URL User home pag
e-All features availability y Registration
Taking Login Name Taking Password Taking confirm Password Taking first name Taki
ng middle name Taking last name Taking e-mail in the e-mail format Taking phone
number (Mandatory) Taking date of birth Taking address including city, state zip
& country Submitting the form Resetting the form Marital registration
y Login
Taking user name Taking Password Providing forgot password option Submitting e-m
ail address and getting user info through our mail ID. Submission of the Login A
ll entered categories and products availability.
y Users Area
Search People Taking input values and finding Displaying results in another scre
en if not found providing message. D-Team IT Solutions Pvt. Ltd | Prepared By: S
HIBIN V.M 6
7
View Profile When search is found then desired users profile is displayed but gue
st user cant see all regarding information. For this purpose he/she has to regist
er themselves first. Update Profile Registered user can update/view/delete their
profile after logged in with login Id and password. Viewing news Selecting disp
layed news item and getting that news. Feed back Based on the facility or view o
f the site, user can also send feedback.
Back end (Administrative Tools) Requirements Connecting to Admin interface with
valid URL
Login operation [Taking User ID & Password] Providing forgot password option & s
ending user information through e-mail. Admin home page All features availabilit
y Update Admins profile Admin can also update/view profile. Adding new member Adm
in has rights to add new member in this website.
Viewing/Deleting member Admin can view all the registered user by users Age, Cast
, Sub Cast, Religion, Gender, etc. as well as Admin can also delete the specifie
d user or deactivate/activate that users account. Viewing/Deleting Feedback Admin
can also view feedback provided by the visitor and user of that website. Also r
eply them by mailing facility. Special offers Adding special offer defining [mis
sing requirements] Viewing & Deleting the special offer details. D-Team IT Solut
ions Pvt. Ltd | Prepared By: SHIBIN V.M
7
8
Adding news Adding news giving priority published date & title. Adding image Add
ing description Saving the details & resetting the details. Viewing/Editing/ del
eting the news. Adding polls Taking poll question Answer options each in separat
e line. Saving & resetting the details
Adding Events Admin can also organize new events for members.
Synchronization Making a backup of contents/users account and important informati
on (export database into a SQL Importing products & categories from SQL file.)
Non-Functional Requirements
Reliability Reliability of the system is very important. As it would be accessed
several times in a day by different users across the hierarchy, it is entirely
robust and reliable.
Maintainability The system is designed to be easily maintainable and get the lea
st complaints from users, along with minimum downtime. 8
Extensibility D-Team IT Solutions Pvt. Ltd | Prepared By: SHIBIN V.M
9
The system is designed to be extensible to changes. A change might be a result o
f either a change in the user requirements or required adherence to some new pol
icy of the product group.
Performance Requirements The system can be used as a web application and targets
various users across the hierarchy. So it is expected to be robust i.e. up and
running all the time.
Business Process Analysis The system is developed taking care of certain standar
d rules that form in a way a major development directive and system descriptor.
Some of the important rules are as follows:
Any deletion in database should be soft in nature It specifies that a record is
not permanently deleted from the database and hence it is deactivated. This woul
d be of help during incidences of accidental deletion and other cases of databas
e references.
Session Control It refers to the practice of session removal and session retaini
ng while navigating through various screens during user interaction.
MILESTONES AND DELIVERABLES Milestones: When planning a project series of milest
ones should be generated where a milestone is end point of software process acti
vity. At each milestone there should be a formal output such as report that can
be represented to management. Milestones report need not be large document. They
may be a short report of achievement in project activity. The milestones are th
e project result, which are not directly supplied to the customer. 9
10
Deliverables: The deliverables are the project results that are provided to the
customer. It is usually delivered at the end of some major project phases. Miles
tones may be result that are used by the project manager to check project progre
ss but which are not delivered to the Clients.
MILESTONES Identify the Scope and Objective Feasibility Study Requirement Collec
tion Analysis Phase Design Specification phase (Including Database Design) Codin
g and implementation Testing and bug fixing Release STUDY OF SYSTEM
DELIVERABLES Synopsis Feasibility Study report User requirement System requireme
nt Analysis Report Database created Table Relationship Diagram Form Designed App
lication Deployed application
DURATION Start date - End date
Doing system analysis identifies the overall role of software in a larger system
. It is necessary to take a harder look at softwares role To understand the unspe
cific requirement that must be achieved to build high quality software. It invol
ves the following steps: Study of current system Problems and weaknesses of curr
ent system Requirements of new system User requirements System requirements D-Te
am IT Solutions Pvt. Ltd | Prepared By: SHIBIN V.M 10
11
The manual task is human dependent, so prone too many errors as well as it consu
mes more time. A feasibility study is a preliminary study undertaken to determin
e and document a project's viability. The results of this study are used to make
a decision whether to proceed with the project, or table it. If it indeed leads
to a project being approved, it will - before the real work of the proposed Pro
ject starts - be used to ascertain the likelihood of the project's success. It i
s an analysis of possible alternative solutions to a Problem and a recommendatio
n on the best alternative. Three types of project feasibility have been consider
ed: Operational Feasibility: The following factors suffice for considering the g
iven project as operational Feasible. Sufficient support from the user. Acceptan
ce from the user side for active involvement and interest in project. Technical
Feasibility. The following factors suffice for considering the given project as
Technically Feasible. The system developed in .net technology which is well know
n and today we can easily get the technical help of .net technology from the int
ernet. The system development in .net technology is specified by client.
Financial and Economical Feasibility. The following factors suffice for consider
ing the given project as Financially Feasible. The system does require investmen
t which provided by client. The system will perform according to client requirem
ent and Economical will not
much expensive.
Implementation Feasibility This system is developed using Visual Studio .NET 200
8 as front end and MySQL as back end. The softwares are available in the develop
ment company.
11
12
Economic Feasibility Economic feasibility is very important in development of th
e software for any company. Because it gives an idea, whether the project going
to be developed can be 2completed at a cost affordable both by the client and de
veloper. The availability of the required hardware and software used to develop
our project makes it economically very feasible. As this a live project installa
tion cost for software is also considered. Despite this project is economically
feasible. Requirement validation is concern with showing that the requirements a
ctually define the system which the customer wants. It has much in common with a
nalysis as it is concerned with finding problems with the requirements. Requirem
ents validation is important because errors in a requirement document can lead t
o excessive rework costs when they are subsequently discovered during developmen
t or after the system is in service. The cost of making a system change resultin
g from a requirements problem is much greater than repairing design and coding e
rrors. The reason for this is that a change to the requirements usually means th
at the system design and that the system must be retested. During the requiremen
ts validation process, different types of checks should be carried out in the re
quirements document. Some of the different checks are listed below on which we c
an perform requirement validation.
V1 V2 V3 V4 V5 V6 V7
Does the requirement meet a standard customer need? Is the requirement necessary
? Is requirement tasted only once? Is requirement consistent with other requirem
ents? Is requirement complete? Is requirement checked to ensure that they can be
implemented using existing technology? Can requirement be implemented in the gi
ven time frame? 12
13
R1 R2 R3 R5
System should react as per the type of the user logged in. System should maintai
n project information in 4-level hierarchy. Dependency checks should be made bef
ore deleting any record. Facility for the generation of reports that provide nec
essary information and summary. Report containing all the requirements (function
al and non-functional) of the project should be generated. Static help should be
provided for easy understanding of the user.
R6 R7
Requiremen ts R1 R2 R3 R4 R5 R6 R7
V1
V2
V3
V4
V5
V6

V7

13
14
*MODULES SPECIFICATION ADMINISTRATOR Term Purpose Input(s) Description To valida
te the administrator. Input username and password for further execution to conti
nue for administrator. Output(s) On successful login, administrator is allowed t
o access the system with his own rights. Administrator user will have following
rights in the system: Add or modify the Products . Delete the Product. Maintain
Order and Assesories.
Process
External Events Temporal Events Fieldof Report Constraint Comments
The data must be validated
14
15
USER Term Purpose Input(s) Output(s) Description To validate the user. Input use
rname and password for further execution to continue for user. On successful log
in, user is allowed to access system with his rights. User will have following r
ights in the system:

Update the profile Search Product and Get information about Product. Send the me
ssage to the Administartor(if any confusion) Buy the Product.
Process

External Events Temporal Events Fields Report Constraint Comments of
The data must be validated
15
16
Guest
Term Purpose Input(s) Output(s)
Description To see the all information related to this hostel
Guest will have following rights in the system:
Register guest
Process
if any doubt the send the mail to the administrator. See all the information about
Product. to give the feedback
External Events Temporal Events Fields Report Constraint Comments Fields Report
Constraint Comments of
Cant buy Product Untill He/She doing Registration.
of 16
17
Functional Oriented Design
Data Flow Diagrams
Context Level Diagram:
Update Account Information Manage Account Give suggestion Search People Add cont
ent, application
ADMIN
Manage Users Acknowledgement Success/failure notification Success/Failure Notifi
cation
Registration Detail
Matrimony .com
USER
login detail Acknowledgement Acknowledgement Success/failure notification Succes
s/failure notification
17
18
First Level Diagram for User:
Registration detail
User
Register 0.1 Registration
User name & Password
Verify user login
0.2 Log in
Matrilogin
Acknowledgement
Goes for Profile statics
0.3 Profile (Updating)
Update profile
Marital Register
Acknowledgement
Input searching detail
0.4 Search
Marital Register
0.5 Feedback
Suggestion
18
19
First Level Diagram of Admin
Username & password
Admin
0.1 Log in
Verify log in
Matrilogin
Acknowledgement
Goes Account Statics
0.2 Manage Account
Admin Detail
0.3 Manage & Add/delete Users
Register
0.4 Search user
Register
0.5 View& Manage Feedback
Suggestion
19
20
2nd level diagram: User:
Registration detail
User
Error message
0.1 Registration
Register
Done successfully
Need to be registered
User name & Password
Verify user login Invalid Login
0.2 Log in
Matrilogin
Log in successfully
Goes for Profile statics
Error message
0.3 Profile (Updating)
Update profile
Marital Register
Acknowledgement
Input searching detail Result not found
0.4 Search
Searching Detail Marital Register Done successfully
Error Message
0.5 Suggestion
Give Feedback
20 Suggestion
Done successfully
21
2nd level diagram: Admin:
Username & password
Admin
Invalid Log in
0.1 Log in
Verify log in
Matrilogin
Acknowledgement
Goes Account Statics
Error message
0.2 Manage Account
Update info
Admin Detail
Done successfully
Error Message
0.3 Manage & Add Users
Registration detail
Register
Done successfully
Result not found
0.4 Search User
input data
Register
Result found
0.5 View, Manage Feedback
Suggestion
21
22
0.3.1 Add User
User detail done successfully Select user Register Deleted successfully Select u
ser done successfully deactivated successfully
0.3.2 Delete User
Register
Select user
0.3.3 Deactive User
0.3.4 Deactive User
22
23
Data Dictionary:
List of tables: Sr.No. 1 2 3 4 5 Table Name MaritalRegister matrilogin Register
Suggestion Admin detail Description Information about the matrimonial users Info
rmation regarding login information. Information about vastipatrak information I
nformation about user feedback & suggestions Information about Admin
Table Structure: 1.Marital Register Field Comment SrNo Username Emailid Father N
ame Gaam Gender Date Year Month Maritalstatus Height Weight Complexion image To
uniquely identify user Name of User Emailid of User Father name of User Village
of User Gender Date Year month Users status Enter height Enter weight Complexion
Image will display
Data Type Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Va
rchar Numeric Numeric Varchar image
Length 5 20 30 20 20 5 10 10 10 10 10 10 20 Max
Constraints Foreign Key Not Null Not Null Not Null Not Null Not Null Not Null No
t Null Not Null Not Null Not Null Not Null Not Null Not Null
2.matrilogin Field SrNo Username Password confirmpassword securityQue securityan
s
Comment To identify the User Username Users password Users password For security p
urpose For security purpose
Data Type Int Varchar Varchar Varchar Varchar Varchar
Length 5 20 20 20 50 50
Constraints Foreign Key Not Null Not Null Not Null Not Null Not Null
23
24
3.Register Field Comment SrNo To identify the User Firstname Name of user Middle
name Middlename Last Name Surname of user Gender Gender Address Address Nativep
lace Nativeplace City City State State Country Country Zipcode Enter zipcode Pho
ne Enter phone User Id Enter Id for User Email Id User Email Id Password User Pa
ssword User type Type of User
Data Type Int Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Va
rchar Int Int Varchar Varchar Varchar Varchar
Length 5 20 20 20 10 Max 50 20 20 20 6 10 30 30 20 20
Constraints Primary Key Not Null Not Null Not Null Not Null Not Null Null Not Nu
ll Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null
4.Suggestion Field Id Subject Name Email Msg
Comment To identify suggestion Enter subject Name of user Email of user Message
of user
Data Type Int Varchar Varchar Varchar Varchar
Length 5 20 20 30 100
Constraints Primary Key Not Null Not Null Not Null Not Null
24
25
Object Oriented Diagram
Sequence Diagram of User
P.L
Enter Registration Detail Error Message Registration Detail Registration Approve
d Log in Detail Invalid Log in Verify Login Detail Successfully Logged In Update
Profile Updated Successfully Search People If [Yes] Result Found Send Message/E
mail Done Successfully Verify Details
B.L
D.B
Result not found Else Give Suggestion Submitted successfully Logout request Succ
essfully logged out
25
26
Sequence Diagram of Admin
P.L
Log in Detail Invalid Log in Verify Login Detail Successfully Logged In Change P
assword Updated Successfully Search People If [Yes] Result Found Send Message Do
ne Successfully Verify Details
B.L
D.B
Result not found Else Add new user Updated successfully Delete/Deactive selected
user Deleted/Deactivated successfully Update Application Done successfully Logo
ut Request Registration detail
26
Logged out successfully
27
Class Diagram
Matrimony.com
Forums
About US
Login
Registration
Contact us
Both can Log in
Admin
User
Can register
Operation
1 *
.
various operation
Search
27
By Name
By Astrology
By Cast
By Religion
By Gender
28
STATE DIAGRAMS
(1) Input validation:
28
29
(2) Display records:
(3) Search records:
29
30
(4) Add records:
(5) Update records:
30
31
31

Matrimony SRS

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Matrimony SRS

Transféré par

Droits d'auteur :

Formats disponibles

1

Matrimony Site Documentation

Vous aimerez peut-être aussi