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. We provide different section
like matrimonial section,Education section & also gave all the information about
activities like events, cultural activities, social activities and all. Here we provide
other facilities like News & also upcoming Events.

SRS Document
Purpose
The purpose of this project is providing a platform to people for connecting from
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 information &
news related the different religions. At these time people want information for any
kind of thing & here people can also find upcoming events.

Scope
Our website provides free services to all people. In this website provide matrimonial
section where people can register him/her profile and easily find life partner & also
you can see news, events and also connecting to different people to latest information
& news.

Background
This Website is based on ASP.NET with c# include 3.5 .NET framework with the
securities of managing the accounts and the resources. The Sql Server is used as
database. This website in inspired by the websites which are available on the net with
the new features included.
 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 or not. It involves analysis of problems and collection of all
relevant information. Collected data are analyzed to arrive at following.

-an abstract problem definition

-format of different strategies for solving problem.
-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 properly. 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 analysis is done to remove incompleteness and inconsistency.

ii. Requirement specification

Requirements from above stage are organized into
software requirement specification document (SRS).SRS to be reviewed and approved
by customer. It forms basis of all carrying out all development activities.
3. Design
Its goal is to transform requirement specified in SRS into
structure suitable for implementation in programming language. In traditional design
approach there are two activities.
i. Structure analysis prepares detail analysis of different function 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 program codes, communicating naming conventions, templates for function
and modules etc. so each component is implemented as a program module.
-next each module is unit tested. Each module is tested from isolation of other
modules then debugging and documenting it. The correct working of each module is
determined individually.

5. Integration &System testing

Different modules are integrated in planned manner. This is
done incrementally over number of steps. During each steps previously planned
modules are added to partially integrated system. It includes 3 kinds of activities

i. α –testing: performed by development team.

ii. β –testing: done by friendly set of customers.
iii. Acceptance testing: done by customer himself

6. Maintance
It involves performing following activities.

i. Corrective maintenance
Correcting errors not discovered during developing product.

ii. Perfective maintenance

 Improving the implementation and enhance the functionality of the
system as per customer needs.

iii. Adaptive maintenance

Required for parting the software to work in new environment.

Functional Requirements
View of Database
This system provides the view of the entire database, or partial view based
on the level of the user in the hierarchy. Depending on the database that is
selected, the in-built queries might vary. So accordingly the system supports
number of reports, graphical analysis, based on the user’s requirement which
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 specific
information regarding a particular entity i.e. this entity could be a BE’s progress
report database or any internal user for user details database. Accordingly there
is a facility through which the different parameter values can be searched 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
takes up relevant related information and save it into the appropriate database.

Update
Depending on the database that is selected, the user can modify some details
under certain parameters for an existing entity. Accordingly the system allows
for modifying the details of a certain parameter related to an existing entity in a
database.
 Delete
Depending on the database that is selected, the user can delete the record 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 the
particular entity should no longer be considered while performing the available
set of operations under related Database or the entity should be permanently
deleted from the database.

System Features
Front end (customer storefront)
o Member’s 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 content
o Viewing/Editing/deleting existing content
o Adding new members
o Viewing/Editing/deleting existing members
o Adding/viewing/deleting existing events
o Adding/viewing/deleting latest news
o Special offers
o Communication
o Defining Polls
 o Reports

Front End (Customer Area)

Connecting to Application with Valid URL User home page-All features
availability

• Registration
Taking Login Name
Taking Password
Taking confirm Password
Taking first name
Taking 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

• Login
Taking user name
Taking Password
Providing forgot password option
Submitting e-mail address and getting user info through our mail ID.
Submission of the Login
All entered categories and products availability.

• User’s Area
Search People
Taking input values and finding
Displaying results in another screen if not found providing message.

View Profile
When search is found then desired user’s profile is displayed but guest
user can’t see all regarding information. For this purpose he/she has to
register themselves first.

Update Profile
Registered user can update/view/delete their profile after logged in
with login Id and password.
 Viewing news
Selecting displayed news item and getting that news.

Feed back
Based on the facility or view of 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 & sending user information through
e-mail.

Admin home page – All features availability

Update Admin’s profile

Admin can also update/view profile.

Adding new member

Admin has rights to add new member in this website.

Viewing/Deleting member
Admin can view all the registered user by user’s Age, Cast, Sub Cast,
Religion, Gender, etc. as well as Admin can also delete the specified user or
deactivate/activate that user’s account.

Viewing/Deleting Feedback
Admin can also view feedback provided by the visitor and user of that
website. Also reply them by mailing facility.

Special offers
Adding special offer defining [missing requirements]
Viewing & Deleting the special offer details.

Adding news
Adding news – giving priority published date & title.
Adding image
Adding description
Saving the details & resetting the details.
Viewing/Editing/ deleting the news.

Adding polls
Taking poll question
 Answer options each in separate line.
Saving & resetting the details

Adding Events
Admin can also organize new events for members.

Synchronization
Making a backup of contents/user’s account and important information
(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 least complaints
from users, along with minimum downtime.

Extensibility
The system is designed to be extensible to changes. A change might be a result
of either a change in the user requirements or required adherence to some new
policy 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 standard 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 would be of help during incidences of accidental deletion
and other cases of database references.

Session Control
It refers to the practice of session removal and session retaining while navigating
through various screens during user interaction.

MILESTONES AND DELIVERABLES

Milestones:
When planning a project series of milestones should be generated where a
milestone is end point of software process activity. 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 the project result, which are
not directly supplied to the customer.
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. Milestones may be
result that are used by the project manager to check project progress but which
are not delivered to the Clients.
 DURATION
MILESTONES DELIVERABLES Start date - End
date
Identify the Scope and Objective Synopsis
Feasibility Study
Feasibility Study
report
User requirement
Requirement Collection
System requirement
Analysis Phase Analysis Report
Design Specification phase Database created
Table Relationship
(Including Database Design)
Diagram
Coding and implementation Form Designed

Testing and bug fixing Application

Release Deployed application

STUDY OF SYSTEM

Doing system analysis identifies the overall role of software in a larger system.
It is necessary to take a harder look at software’s role – To understand the
unspecific requirement that must be achieved to build high quality software. It
involves the following steps:
 Study of current system
 Problems and weaknesses of current system
 Requirements of new system
 User requirements
 System requirements
The manual task is human dependent, so prone too many errors as well as it
consumes more time. A feasibility study is a preliminary study undertaken to
determine 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
Project starts - be used to ascertain the likelihood of the project's success.
It is an analysis of possible alternative solutions to a Problem and a
recommendation on the best alternative.
Three types of project feasibility have been considered:
  Operational Feasibility:
The following factors suffice for considering the given project as operational
Feasible.
 Sufficient support from the user.
 Acceptance 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 known and today we
can easily get the technical help of .net technology from the internet.
 The system development in .net technology is specified by client.

 Financial and Economical Feasibility.

The following factors suffice for considering the given project as Financially
Feasible.
 The system does require investment which provided by client.
 The system will perform according to client requirement and Economical
will not much expensive.
Implementation Feasibility

This system is developed using Visual Studio .NET 2008 as front end and
MySQL as back end. The softwares are available in the development company.

Economic Feasibility

Economic feasibility is very important in development of the 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
developer. The availability of the required hardware and software used to
develop our project makes it economically very feasible. As this a live project
installation cost for software is also considered. Despite this project is
economically feasible.
 Requirement validation is concern with showing that the requirements
actually define the system which the customer wants. It has much in common
with analysis as it is concerned with finding problems with the requirements.
Requirements validation is important because errors in a requirement
document can lead to excessive rework costs when they are subsequently
discovered during development or after the system is in service. The cost of
making a system change resulting from a requirements problem is much greater
than repairing design and coding errors. The reason for this is that a change to
the requirements usually means that the system design and that the system must
be retested.

During the requirements validation process, different types of checks should

be carried out in the requirements document. Some of the different checks are
listed below on which we can perform requirement validation.

V1 Does the requirement meet a standard customer need?

V2 Is the requirement necessary?
V3 Is requirement tasted only once?
V4 Is requirement consistent with other requirements?
V5 Is requirement complete?
Is requirement checked to ensure that they can be implemented using
V6
existing technology?
V7 Can requirement be implemented in the given time frame?

R1 System should react as per the type of the user logged in.
R2 System should maintain project information in 4-level hierarchy.
R3 Dependency checks should be made before deleting any record.
Facility for the generation of reports that provide necessary information
R5
and summary.
Report containing all the requirements (functional and non-functional) of
R6
the project should be generated.
R7 Static help should be provided for easy understanding of the user.
Requiremen
V1 V2 V3 V4 V5 V6 V7
ts
      
R1
      
      
R2
      
     
R3 
     
      
R4
      
      
R5
      
     
R6
     
      
R7
      
*MODULES SPECIFICATION
ADMINISTRATOR

Term Description
Purpose To validate the administrator.
Input username and password for further execution to continue for
Input(s)
administrator.
On successful login, administrator is allowed to access the system with his
Output(s)
own rights.
Administrator user will have following rights in the system:

 Add or modify the Products .

 Delete the Product.
Process  Maintain Order and Assesories.


External
-
Events
Temporal
-
Events
Fieldof
-
Report
Constraint The data must be validated
Comments

USER
Term Description

Purpose To validate the user.

 Input username and password for further execution to continue for
Input(s)
user.
Output(s) On successful login, user is allowed to access system with his rights.
User will have following rights in the system:
 Update the profile
Process  Search Product and Get information about Product.
 Send the message to the Administartor(if any confusion)
 Buy the Product.
External
-
Events
Temporal
-
Events
Fields of
Report
Constraint The data must be validated
Comments

Guest

Term Description
Purpose To see the all information related to this hostel
Input(s)
Output(s)
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 of
-
Report
Constraint Can’t buy Product Untill He/She doing Registration.

Comments

Fields of -
Report
Constraint
Comments
 Functional Oriented Design
Data Flow Diagrams

Context Level Diagram:

Update Account Information

Manage Account Give suggestion
Search People
Add content, application
Manage Users Registration Detail
ADMIN USER
Acknowledgement Jivan login detail
saathi.co.in
Success/failure notification Acknowledgement
Acknowledgement
Success/Failure Notification
Success/failure notification

Success/failure notification
 First Level Diagram for User:

Registration detail
Register
User 0.1
Registratio
n

User name & Password

Verify user login

Matrilogin
0.2 Acknowledgement
Log in

Goes for Profile statics

Update profile
0.3 Marital Register
Profile Acknowledgement
(Updating)

Input searching detail

0.4
Search Marital Register

0.5 Suggestion
Feedback
 First Level Diagram of Admin

Username & password

Admin Verify log in
0.1 Matrilogin
Log in Acknowledgement

Goes Account Statics

0.2
Manage
Admin Detail
Account

0.3
Manage &
Add/delete
Register
Users

0.4 Register
Search user

0.5
View& Manage Suggestion
Feedback
 2nd level diagram:

User:
Registration detail
User 0.1
Error message Registratio Register
n Done successfully

Need to be registered User name & Password

Verify user login

Invalid Login Matrilogin
0.2 Log in successfully
Log in

Goes for Profile statics

Update profile
Error message 0.3 Marital Register
Profile Acknowledgement
(Updating)

Input searching detail

Result not found 0.4 Searching Detail

Search Marital Register
Done successfully

Error Message Give Feedback

0.5
Suggestion
Suggestion Done successfully
 2nd level diagram:

Admin:

Username & password

Admin Verify log in
Invalid Log in 0.1 Matrilogin
Log in Acknowledgement

Goes Account Statics

Error message 0.2 Update info

Manage Admin Detail
Account Done successfully

0.3
Error Message Manage & Registration detail
Add Register
Users Done successfully

Result not found input data

0.4
Register
Search User Result found

0.5
View, Manage Suggestion
Feedback
 0.3.1
Add User

User detail done successfully

Select user Select user 0.3.3

0.3.2
Register
Delete
Register
User Deactive
Deleted successfully done successfully
User
Select user deactivated successfully

0.3.4
Deactive User
Data Dictionary:

List of tables:

Sr.No. Table Name Description

1 MaritalRegister
2 matrilogin
3 Register
4 Suggestion
5 Admin detail
Information about the matrimonial users
Information regarding login information.
Information about vastipatrak information
Information about user feedback & suggestions
Information about Admin

Table Structure:

1.Marital Register
Field Comment Data Type Length Constraints

SrNo To uniquely identify user Int 5 Foreign Key

Username Name of User Varchar 20 Not Null
Emailid Emailid of User Varchar 30 Not Null
Father Name Father name of User Varchar 20 Not Null
Gaam Village of User Varchar 20 Not Null
Gender Gender Varchar 5 Not Null
Date Date Varchar 10 Not Null
Year Year Varchar 10 Not Null
Month month Varchar 10 Not Null
Maritalstatus User’s status Varchar 10 Not Null
Height Enter height Numeric 10 Not Null
Weight Enter weight Numeric 10 Not Null
Complexion Complexion Varchar 20 Not Null
image Image will display image Max Not Null

2.matrilogin
Field Comment Data Type Length Constraints
SrNo To identify the User Int 5 Foreign Key
Username Username Varchar 20 Not Null
Password User’s password Varchar 20 Not Null
confirmpassword User’s password Varchar 20 Not Null
securityQue For security purpose Varchar 50 Not Null
securityans For security purpose Varchar 50 Not Null
3.Register
Field Comment Data Type Length Constraints
SrNo To identify the User Int 5 Primary Key
Firstname Name of user Varchar 20 Not Null
Middle name Middlename Varchar 20 Not Null
Last Name Surname of user Varchar 20 Not Null
Gender Gender Varchar 10 Not Null
Address Address Varchar Max Not Null
Nativeplace Nativeplace Varchar 50 Null
City City Varchar 20 Not Null
State State Varchar 20 Not Null
Country Country Varchar 20 Not Null
Zipcode Enter zipcode Int 6 Not Null
Phone Enter phone Int 10 Not Null
User Id Enter Id for User Varchar 30 Not Null
Email Id User Email Id Varchar 30 Not Null
Password User Password Varchar 20 Not Null
User type Type of User Varchar 20 Not Null

4.Suggestion
Field Comment Data Type Length Constraints
Id To identify Int 5 Primary Key
suggestion
Subject Enter subject Varchar 20 Not Null
Name Name of user Varchar 20 Not Null
Email Email of user Varchar 30 Not Null
Msg Message of user Varchar 100 Not Null

Object Oriented Diagram

Sequence Diagram of User

 P.L B.L D.B
Enter Registration Detail

Error Message
Registration Detail

Registration Approved

Log in Detail

Invalid Log in
Verify Login Detail

Successfully Logged In

Update Profile

Updated Successfully

Search People Verify Details

If [Yes] Result Found

Send Message/Email

Done Successfully

Result not found

Else

Give Suggestion

Submitted successfully

Logout request

Successfully logged out

Sequence Diagram of Admin

P.L B.L D.B

 Log in Detail

Invalid Log in
Verify Login Detail
Jivansathi.com Successfully
Logged In

Change Password

Updated Successfully

Search People Verify Details

If [Yes] Result Found

Send Message

Done Successfully

Result not found

Else

Add new user Registration detail

Updated successfully

Delete/Deactive selected user

Deleted/Deactivated successfully

Update Application

Done successfully

Logout Request

Logged out successfully

Class Diagram
 Forums

About US Login Registration Contact us

Both can
Log in

Admin User

Operation Can register

.
1 * various operation

Search

By Name By Astrology By Cast By Religion By Gender

STATE
DIAGRAMS
(1) Input validation:
 [Prompt For Correcrion ]
Enter I /PData

[Data Valid ] [DataInvalid ]

Valid Data FromUser Invalid Data Entered by User

(2) Display records:

Fetch Record from Database

Display Data on form No Data in to Database

(3) Search records:

 Enter Search Criteria

[Data Valid ] [Data not Valid ]

find data fromthe database Search fails

(4) Add records:

Array Passed by I/p validate

Add data in to database

(5) Update records:

 User Issues Update Command

Update Records in to Database

Store updated data in to database

Implementation:
Code for Login Operation

SqlConnection con = new SqlConnection

(ConfigurationManager.ConnectionStrings
["ConnectioString"].ConnectionString);
DataSet ds = new DataSet();
DataSet ds1 = new DataSet();
SqlDataAdapter da = new SqlDataAdapter();
SqlCommand cmd = new SqlCommand();

protected void Page_Load(object sender, EventArgs e)

{
}
protected void btnlogin_Click(object sender, EventArgs e)
{
object id = weblib.main.Scalar("select UserType from Register
where username='" + txtlgusername.Text + "'and
password='" + txtloginpassword.Text + "' ");

if (id != null)
{
if (id.Equals("user"))
{
DataSet ds = new DataSet();
ds = weblib.main.getTable("select FirstName from
Register where username='"+txtlgusername.Text+"'and
password='"+txtloginpassword.Text+"' ");

Session["username"] = ds.Tables[0].Rows[0]
[0].ToString();

Response.Redirect("~/RegisteredUser/memberregister.aspx");
}
 else if (id.Equals("admin"))
{
DataSet ds1 = new DataSet();
ds1 = weblib.main.getTable("select FirstName from
Register where username='" + txtlgusername.Text +
"'and password='" + txtloginpassword.Text + "' ");
Session["username"] = ds1.Tables[0].Rows[0]
[0].ToString();
Response.Redirect("~/Admin/adminhomepage.aspx");

}
}
else
{
lblinvalid.Visible = true;
txtlgusername.Text = "";
}

}
}

Table Standard Controls

Control Suffix Example

Button Btn UserNameBtn
Calender Cal UserNameCal
Check Box Chk UserNameChk
File Upload Fup UserNameFup
Label Lbl UserNameLbl
List Box Lst UserNameLst
Literal Lr lUserNameLr
Panel Pnl UserNamePnl
Radio Button Rb UserNameRb
Textbox Txt UserNameTxt
View Vw UserNameVw

Table Data controls

Control Suffix Example

DataList Dl UserNameDl
FormView Fvw UserNameFvw
SqlDataSource Sqlds UserNameSqlds
 XmlDataSource Xmlds UserNameXmlds

Table Database Controls

Control Suffix Example

Data Reader Dr UserNameDr
DataSet Ds UserNameDs
DataView Dv UserNameDv
OdbcCommand Cmd UserNameCmd
OdbcConnection Con UserNameCon
OdbcDataAdapter Da UserNameDa
OledbCommand Cmd UserNameCmd
OledbConnection Con UserNameCon
OledbDataAdapter Da UserNameDa
OracleCommand Cmd UserNameCmd
OracleConnection Con UserNameCon
OracleDataAdapter Da UserNameDa
SqlCommand Cmd UserNameCmd
SqlConnection Con UserNameCon
SqlDataAdapter Da UserNameDa
Data Column Dc UserNameDc
Data Row Drw UserNameDrw
Data Table Dt UserNameDt

Test Cases and Test Results

Table Login Module

Obtained
Sr.No Scenario Expected Result
Result
“Invalid Username or
Username is correct, Password is
1 Password” messge is TRUE
incorrect.
displayed.
“Invalid Username or
Username is incorrect, Password is
2 Password” message is TRUE
correct.
displayed.
 “Invalid Username or
Incorrect values for username and TRUE
3 Password” message is
password are submitted.
displayed.
Navigates to the next page
Correct values for username and password
4 based on the user who is TRUE
are submitted.
logging in.

Table for Registration Module

Sr. No Scenario Expected Result Obtained

Result
1 Firstname, Middlename, “Please Enter Name” message is TRUE
Last Name, field is empty. displayed.
2 Gender field is not selected. “Please Enter Gender” message is TRUE
displayed.
3 Birth Date field is empty. “Please Enter your birth date” TRUE
message is displayed.
4 Address field is empty. “Please Enter Your Address” message TRUE
is displayed.
5 City field is empty. “Please Enter City” message is TRUE
displayed.
 6 State field is not selected. “Please select state” message is TRUE
displayed.
7 Country field is not selected “Please select country” message is TRUE
displayed.
8 Zipcode field is empty. “Please enter zipcode” message is TRUE
displayed.
9 Phone field is empty. “Please enter phone number” TRUE
message is displayed.
10 User id field is empty. “Please enter user id” message is TRUE
displayed.
11 Email id field is empty. “Please Enter Emailid” message is TRUE
displayed.
12 Password field is empty. “Please Enter Password” message is TRUE
displayed.
13 User id is invalid. “Please Enter Valid Emailid” message TRUE
is displayed.
14 User id already registered. “Emailid Already Exist” Please Enter TRUE
Another Emailid” message is
displayed.
15 All fields are properly “Registration done successfully” TRUE
entered and submit button is message is displayed.
clicked.
16 On clicking Cancel button. All fields values are cleared. TRUE

Table for searching module

Obtained
Sr.No Scenario Expected Result
Result
“Please enter gender” message is
1 Gender field is empty. TRUE
displayed.

“Please select religion” message is

2 Religion field is not selected. TRUE
displayed.
 “Please select age” message is TRUE
3 Age field is not selected.
displayed.

Cast/Sub cast field is not “Please select cast/sub cast”

4 TRUE
selected. message is displayed.

All fields are clearly entered and “Search result found” message is
5 TRUE
clicking submit button. displayed.

6 On clicking cancle button All fields values are cleared. TRUE

Table for Mail sending module

Sr. No Scenario Expected Result Obtained

Result
1 To Address is empty. “Please Enter ToAddress” message is TRUE
displayed.
2 Body is empty. “Please Enter Body” message is TRUE
displayed.
3 To Address is invalid. “Please Enter Valid Email id” message TRUE
is displayed.
4 All field values are “Message Sent successfully” message is TRUE
proper and click on displayed.
Send button.
5 Click on Cancel button. All field values are cleared. TRUE
Table for Profile Updation

Sr. No Scenario Expected Result Obtained

Result
1 Firstname, Middlename, “Please Enter Name” message is TRUE
Last Name, field is empty. displayed.
2 Gender field is not selected. “Please Enter Gender” message is TRUE
displayed.
3 Birth Date field is empty. “Please Enter your birth date” TRUE
message is displayed.
4 Address field is empty. “Please Enter Your Address” message TRUE
is displayed.
5 City field is empty. “Please Enter City” message is TRUE
displayed.
6 State field is not selected. “Please select state” message is TRUE
displayed.
7 Country field is not selected “Please select country” message is TRUE
displayed.
8 Zipcode field is empty. “Please enter zipcode” message is TRUE
displayed.
9 Phone field is empty. “Please enter phone number” TRUE
message is displayed.
10 Email Id is empty “Please enter your email id” message TRUE
is displayed.
11 Password field is empty. “Please Enter Password” message is TRUE
displayed.
14 All fields are properly “Registration done successfully” TRUE
entered and submit button is message is displayed.
clicked.
15 On clicking Cancel button. All fields values are cleared. TRUE