Vous êtes sur la page 1sur 82

MATRIMONIAL WEB

PORTAL

Submitted by:
Jose joy
Jiss George
St.Michaels
college
Divine
jose
Cherthala

PROJECT REPORT

INTRODUCTION
What is Matrimonial Web Application?
The main objective of Matrimonial Web Application is to provide Grooms and Brides
with excellent matchmaking experience by exploring the opportunities and resources to meet true
potential partner. Keeping our objective in mind, we have created a world renowned online
matchmaking services that will touch the souls of millions of people all over the globe.

The purposes of the Matrimonial Web Application are:

The main purpose of this application is to facilitate matchmaking business by


applying the information in the field.

It helps the user by providing profiles of perspective Bride or Groom and other
information regarding them online.

User can get information regarding their dream life partner at his/her home at his/her
convenience.

This application also provides a search utility which helps those users who have a
certain criteria of qualities in mind to make online matrimonial easier.

Since internet is a pivot for modern business, our project which is based on internet
paves a path for modernization in trade.

Matrimonial Web Application will allow a new user to register and after successfully
registration user can get email confirmation, after completing registration users profile will be
visible to other users.
Matrimonial website whichis provide platform to a lot of Bride/Groom for finding their
perfect match. There are different sectors like Registration, Partner, Search, etc. So the
Bride/Groom can get their interest for find their partner. Bride/Groom can directly search Partner
according to their required criteria. The Bride/Groom can use match By Email functionality so
he/she can get directly E-mail alert for the match which fulfill their required criteria.

For This Application, we will provide following capabilities:


(1) Admin Module.
(2) User Registration Module
(3) All match module
(4) User Login module
(5) Chat box module
(6) Contact us module
(7) Success Story module
(8) Feedback module
(9) User profile module
(10)

Image Uploading module

(11)

Creating album

(12)

Sending Express Interest

(13)

Sending Personal messages

(14)

User Update Module

(15)

Paid Membership

(16)

Search Module.

(17)

Non Paid Member details module

The application will have to be completed using Visual Studio 2008 and SQL Server 2008R2
with help of other office productivity tools.
The application testing criteria and installation requirements will be part of the detailed
application architecture document.

PROJECT LIFECYCLE
MODEL

SPIRAL MODEL:
The spiral model is a software development process combining elements of both design and
prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts.
Also known as the spiral lifecycle model (or spiral development), it is a systems development
method (SDM) used in information technology (IT). This model of development combines the
features of the prototyping and the waterfall model. The spiral model is intended for large,
expensive and complicated projects.

The Model:

The spiral model combines the idea of iterative development (prototyping) with the systematic,
controlled aspects of the waterfall model. It allows for incremental releases of the product, or
incremental refinement through each time around the spiral. The spiral model also explicitly
includes risk management within software development. Identifying major risks, both technical
and managerial, and determining how to lessen the risk helps keep the software development
process under control.
The spiral model is based on continuous refinement of key products for requirements definition
and analysis, system and software design, and implementation (the code). At each iteration
around the cycle, the products are extensions of an earlier product. This model uses many of the
same phases as the waterfall model, in essentially the same order, separated by planning, risk
assessment, and the building of prototypes and simulations.
The spiral lifecycle model allows for elements of the product to be added in when they become
available or known. This assures that there is no conflict with previous requirements and design.
This method is consistent with approaches that have multiple software builds and releases and
allows for making an orderly transition to a maintenance activity. Another positive aspect is that
the spiral model forces early user involvement in the system development effort. For projects
with heavy user interfacing, such as user application programs or instrument interface
applications, such involvement is helpful.
Starting at the center, each turn around the spiral goes through several task regions:

Determine the objectives, alternatives, and constraints on the new iteration.


Evaluate alternatives and identify and resolve risk issues.
Develop and verify the product for this iteration.
Plan the next iteration.

Why we use spiral model?

It is simple and easy to use.


Easy to manage due to the rigidity of the model each phase has specific deliverables
and a review process.
Phases are processed and completed one at a time.
Works well for smaller project where requirements are very well understood.

Project profile
Project Title
Objective

Of

Matrimonial Web Application.

Matrimonial Web Application will allow a new user to

System

register and after successfully registration user can get


email confirmation, after completing registration users
profile will be visible to other users.

Operating

Microsoft Windows 7 Home Premium

Pentium 90 MHZ or Faster and 96 MB Ram (Client)

Systems
Hardware
Requirement

Pentium 133 MHZ or Faster and 128 Ram (Server)

Software

Microsoft Visual Studio Asp .Net 2008

Requirement
Front End
Back End

:
:

Microsoft Visual Studio 2008


Microsoft SQL Server 2008 R2

Others

Microsoft Visio

.Net Framework

PURPOSE:
Matrimonial website which is provide platform to a lot of Bride/Groom for finding perfect
match. There are different sectors like Registration, Login, Search, etc. So the Bride/Groom can
get their interest for find their partner. Bride/Groom can directly search Partner according to their
required criteria. The Bride/Groom can use match By Email functionality so he/she can get
directly E-mail alert for the match which fulfill their required criteria.

The purposes of the Matrimonial Web Application are:

The main purpose of this application is to facilitate matchmaking business by applying


the information in the field.

It helps the user by providing profiles of perspective Bride and Groom and other
information regarding them online.

User can get information regarding their dream life partner at his/her home at his/her
convenience.

This application also provides a search utility which helps those users who have a certain
criteria of qualities in mind to make online matrimonial easier.

Since internet is a pivot for modern business, our project which is based on internet paves
a path for modernization in trade.

TECHNOLOGY AND LITERATURE REVIEW:


Operating

Window 7 Home Premium

System
Technology
Language
Database

Microsoft Visual Studio 2008 with 3.56 architecture


Asp.net
MS-SQL server 2008 R2

TECHNOLOGY AND
HARDWARE USED

The .net framework:


A frame work is commonly thought of as a set of class libraries that aid in the
development of applications. The .net framework is more than just a set of classes. The .net
framework is targeted by compliers using a wide variety of applications. Including everything
from small components that run on handheld devices to large Microsoft ASP.ET application that
span web farms, where multiple web serves act together to improve the performance fault
tolerance of a web site. The .NET framework is responsible for providing a basic platform that
these applications can share. This basic platform includes a runtimes set of services that oversee
the execution of applications. A key responsibility of the runtime is to manage execution so that
software written by different programming languages uses classes and other types safely.

Microsoft .net framework architecture:

Microsoft's .NET Framework is comprised of two main components - the Common


Language Runtime (CLR) and the .NET Framework class libraries. The CLR is the real
foundation of the .NET Framework. It is the execution engine for all .NET applications. Every
target computer requires the CLR to successfully run a .NET application that uses the .NET
Framework. The main features of CLR include:

Automatic Memory Management

Thread Management

Code Compilation & Execution

Code Verification

High level of security

Remoting

Structured Exception Handling

Interoperability between Managed and Unmanaged code.

Integration with Microsoft Office System

All .NET applications are compiled into Intermediate Language code (MSIL). When
executed on the CLR, MSIL is converted into native machine code specific to the operating
platform. This process is done by a Just in Time (JIT) compiler. The code executed by the CLR is
called as Managed Code. This code is type safe and thoroughly checked by the CLR before being
deployed. The .NET runtime also provides a facility to incorporate existing COM components
and DLL's into a .NET application. Code that is not controlled by the CLR is called Unmanaged
Code.
The .NET Framework is further comprised of Common Type System (CTS) and Common
Language Specification (CLS). The CTS defines the common data types used by .NET
programming languages. The CTS tells you how to represent characters and numbers in a
program. The CLS represents the guidelines defined by for the .NET Framework. These
specifications are normally used by the compiler developers and are available for all languages,
which target the .NET Framework.

Introduction to ASP.NET:

Although so Microsoft Visual Basic.NET is a powerful but simple language aimed


primarily at developers creating web applications for the Microsoft .NET platform. It inherits
many of the best features of C++ and Microsoft Visual Basic, but with some of the
inconsistencies and anachronisms removed, resulting in cleaner and logical language. VB also
contains a variety of useful new innovations that accelerate application development, especially
when used in conjunction with Microsoft Visual Studio .NET.
The Common Language Runtime provides the services that are needed for executing any
application thats developed with one of the .NET languages. This is possible because all of
the .NET languages compile to a common Intermediate Language. The CLR also provides the
common type system that defines those data types that are used by all the .Net languages. That
way, you can use same data types regardless of what.NET language youre using to develop your
application implementations.

Features of ASP.NET:
(1) Component Infrastructure.

(2) Language Integration.


(3) Internet Interoperation.
(4) Simple Development.
(5) Simple Deployment.
(6) Reliability.
(7) Security

Introduction to Microsoft SQL Server:


Microsoft SQL Server is a relational database management system developed by Microsoft. As
a database, it is a software product whose primary function is to store and retrieve data as
requested by other software applications, be it those on the same computer or those running on
another computer across a network (including the Internet). There are at least a dozen different
editions of Microsoft SQL Server aimed at different audiences and for different workloads
(ranging from small applications that store and retrieve data on the same computer, to millions of
users and computers that access huge amounts of data from the Internet at the same time). Its
primary query languages are T-SQL and ANSI SQL.

SQL Server 2008 R2:


SQL Server 2008 R2 (10.50.1600.1, formerly codenamed "Kilimanjaro") was announced at
TechEd 2009, and was released to manufacturing on April 21, 2010. SQL Server 2008 R2 adds
certain features to SQL Server 2008 including a master data management system branded as
Master Data Services, a central management of master data entities and hierarchies. Also Multi
Server Management, a centralized console to manage multiple SQL Server 2008 instances and
services including relational databases, Reporting Services, Analysis Services & Integration
Services.
SQL Server 2008 R2 includes a number of new services, including PowerPivot for Excel and
SharePoint, Master Data Services, Stream Insight, Report Builder 3.0, Reporting Services Add-in
for SharePoint, a Data-tier function in Visual Studio that enables packaging of tiered databases as
part of an application, and a SQL Server Utility named UC (Utility Control Point), part of
AMSM (Application and Multi-Server Management) that is used to manage multiple SQL
Servers.
The first SQL Server 2008 R2 service pack (10.50.2500, Service Pack 1) was released on July
11, 2011.
The second SQL Server 2008 R2 service pack (10.50.4000, Service Pack 2) was released on July
26, 2012.

FEASIBILITY STUDY

FEASIBILITY STUDY:
Feasibility study is a process to check possibilities of system development. It is a method to
check various different requirements and availability of financial & technical resources.
Before starting the process various parameters must be checked like:

Estimated finance is there or not?

The man power to operate the system is there or not?

The man power is trained or not?

All the above conditions must be satisfied to start the project. This is why in depth analysis of
feasibility is carried out.
There are three different ways feasibility can be tested:

1) Economical Feasibility
2) Technical Feasibility
3) Operational Feasibility.

Economical Feasibility:
In economic feasibility, analysis of the cost of the system is carried out. The system
should be only developed if it is going to give returned the current manual system
user can get the price only by purchasing the newspapers. In addition if he/she wants
to see archives of particular equity then he has to refer to all the old newspapers. For
research reports he has to buy another magazine. So Instead of buying no of
magazines user has to just go online and with a single click he can get whatever
information he wants. So our project of online share news passes the test of economic
feasibility.

Technical Feasibility:
It is basically used to see existing computer, hardware and software etc., weather it
is sufficient or additional equipments are required? Minimum System Requirement
is such that it can be affordable by of the user who is having computer. All the user
requires is compatible browser and .net framework installed so our system is fully
technical feasible.

Operational Feasibility:
Once the system is designed there must be trained and expert operator. If there are
not trained they should give training according to the needs of the system.
From the users perspective our system fully operational feasible as it just
requires some knowledge of computer. Operators only need add daily prices of

various equities and there are enough validations available so operator does not
require any special technical knowledge. So our system also passes the test of
operational feasibility.

ARCHITECTURE AND DESIGN OF THE


PROJECT
Since the application will have client server architecture, it will have two-tier architecture.

Tier 1
Presentation
Tier

User Interface-GUI Components

Tier 2
Database Tier

Database Access

TABLE DESIGN

TABLE DESIGN
Table:admin_login
Data
type

Field Name

Null

Description

Lid

Int

No

Stores the admin id

User_nm

Varchar

No

Stores the admin name

Password

Varchar

No

Stores the admin password

Table:Bank_Details_cc

Data
type

Field Name

Null

Description

Cc_id

Int

No

Stores the id

Card_no

Varchar

No

Stores the card number

Card_type

Varchar

No

Stores the type of card

Card_exp_month

Varchar

No

Stores cards expiry month

Card_exp_year

Varchar

No

Stores cards expiry year

Pin_code

Varchar

No

Stores card pin code

Name_on_card

Varchar

No

Stores user name on the card

Credit_limit

Numeric

No

Stores limited amount of card

Avail_bal

Int

No

Stores available balance amt


in card

Table:Chat_Box
Data
type

Field Name

Null

Description

To_uid

Varchar

No

Stores the receivers email ids

From_uid

Varchar

No

Stores the senders email ids

Messages

Varchar

Yes

Stores the text messages

Table:Contact_us
Data
type

Field Name
Ct_id

Int

Null
No

Description
Stores the contact id

Name

Varchar

No

Stores the user name

Mobile

Varchar

No

Stores the contact number

Email id

Varchar

No

Stores the users e-mail id

Details

Varchar

Yes

Stores the details

Ct_date

DateTime

No

Stores the contact date and


time

Table:Express_interest
Field Name

Data
type

Null

Description

To_uid

Varchar

No

Stores the receivers email ids

From_uid

Varchar

No

Stores the senders email ids

Messages

Varchar

Yes

Stores the text messages

Table: feedback
Field Name

Data
type

Null

Description

fd_id

Varchar

No

Stores the feedback id

Name

Varchar

No

Stores the name of user

Comment

Varchar

Yes

Stores the comments

Feed_date

Datetime

No

Stores the date of feedback

Table:image_gallery

Data
type

Field Name

Null

Description

Img_id

Int

No

Stores the id of image

Images

Varchar

No

Stores the image

Pro_id

Int

No

Stores the user id

Table: Profile
Data
type

Field Name

Null

Description

pro_id

Int

No

Stores the user profile id

Profile_creator

Varchar

No

Stores the data of profile


creator

Names

Varchar

No

Stores the name of user

Marital_status

Varchar

No

Stores the data of marital


status

Body_type

Varchar

No

Stores the data of body type

Age

Varchar

No

Stores the age of user

Physical_status

Varchar

No

Stores the physical status of


user

Height

Varchar

No

Stores the height of user

Weight

Varchar

No

Stores the weight of user

Mother_tongue

Varchar

No

Stores the mother tongue of


user

Religion

Varchar

No

Stores the religion of user

Caste

Varchar

No

Stores the caste of user

Gothram

Varchar

No

Stores the gothram of user

Zodiac

Varchar

No

Stores the zodiac of user

Star

Varchar

No

Stores the star of user

Eating_habit

Varchar

No

Stores the habit of user

Drinking_habit

Varchar

No

Stores the habit of user

Smoking_habit

Varchar

No

Stores the habit of user

Country

Varchar

No

Stores the country of user

City

Varchar

No

Stores the city of user

State

Varchar

No

Stores the state of user

Education

Varchar

No

Stores the qualification of user

Occupation

Varchar

No

Stores the occupation of user

Employeed_in

Varchar

Yes

Stores the employee status of


user

Salary

Varchar

No

Stores the salary data of user

Mobile_no

Varchar

No

Stores the contact no of user

Images

Varchar

No

Stores the profile image of


user

About_me

Varchar

Yes

Stores the data about user

Require_details

Varchar

Yes

Stores the detail of user

Membership

Varchar

No

Stores the info about


membership

Paid_status

Varchar

No

Stores the paid status of user

Start_date

Varchar

No

Stores the start date of


account

End_date

Datetime

No

Stores the end date of account

Email_id

Varchar

No

Stores the email id of user

Password

Varchar

No

Stores the password of user


a/c

Gender

Varchar

No

Stores the gender of user

Profession

Varchar

No

Stores the profession of user

Address

Varchar

No

Stores the address of user

Pincode

Varchar

No

Stores the address pin code

Phoneno

Varchar

No

Stores the phone no of user

Paid_date

Datetime

No

Stores the date of payment

Login_status

Int

No

Stores the login status of user

Table:Search_setting
Data
type

Field Name

Null

Description

Pro_id

Int

No

Stores the users profile id

Caste

Varchar

No

Stores the caste of user

salary

Varchar

No

Stores the salary of user

Education

Varchar

No

Stores the education of user

Occupation

Varchar

No

Stores the occupation of user

maritalstatus

Varchar

No

Stores the marital status of


user

Table:send_msg
Field Name

Data
type

Null

Description

To_uid

Varchar

No

Stores the receivers email ids

From_uid

Varchar

No

Stores the senders email ids

Messages

Varchar

Yes

Stores the text messages

Table:success_story

Field Name

Data
type

Null

Description

Usr_id

Varchar

No

Stores the user id

Story

Varchar

No

Stores the success story

Ad_date

Datetime

no

Stores the upload date of


story

Table: zone-master
Field Name

Data
type

Null

Description

Country

Varchar

No

Stores the name of country

State

Varchar

No

Stores the name of state

city

Varchar

No

Stores the name of city

CODING STANDARD
Checks for Normal Working

Does your screen save data in the database?

To Be
Checked
?
Yes

Does your screen save correct data in the database?

Yes

In update does your screen load correct data?

Yes

Fields are showing the data in correct format?

[USE REGULAR EXPRESSIONS DEFINED AS PER TESTING


STANDARDS]
DateShould always be selectable in addition to manual entry

Yes

Integer

Yes

Float, Double

Yes

Percentage

Yes

For web site entry field, populate by default with value

Yes

All email entry fields should be multiple email addresses enabled

Yes

Will your screen crash if wrong data type is entered?

Yes

Does your screen sequence is working?

Yes

If the logic updated / approved?

Yes

Basic Validations
Maximum allowed length property is set?

Yes

Validation for Required field is done?

Yes

Validation for Integer, Float, Double, Date, Time is done?

Yes

Spell check

Yes

Type Check / Type Safety

Yes

Boundary Value Analysis (for highest order value and lowest order

Yes

value)
Date Format (dates must be converted from SQL only) NEVER DISPLAY

Yes

12:00:00 AM
Is page validation enabled? [must be done for user entry fields]

Yes

ER-DIAGRAM

Entity Relation Diagram:


The Entity Relationship Diagram (Model) is based on perception of a real world that
consists of a collection of basic objects called as Entity and relationships among these objects.
Entities in database are described as set of attributes.

A Relationship is an association among several Entities.

The set of Entities of the same type are called as Entity Set.

The set of Relationships of same type are called as Relationship Set.

A graphical model of the data needed by the system, including think about which
information is stored and the relationship among them, produced in structured analysis and
information engineering.

The relational approaches to system development places a great deal of emphasis on data
storage requirements include the data entities, their attributes and the relationship among the data
entities. The model used to define the data storage requirements is called the Entity Relationship
Diagram.
On the Entity Relationship Diagram, a rectangle represents data entities, and lines
connecting the rectangle show the relationship among data entities.

Notations used in ER-Diagram:


=

Represents Data Entity.

Attributes

Connection between two or more entities.

Represents the relationship.

= Connection between two or more entities.

1.

Admin Table:
ADMIN
LOGIN
Ad_id
Ad_name
Ad_passwo
rd

2.

Bank_Details Table:

Pin_code
Name_on_c
Card_exp_

CC_ID

BANK
Avail_bala
Card_exp_
DETAILS

Card_no
Credit_limi
Card_type

3.

Profile Table:
State

Login_stat
us
address

membersh
ip
Email_id

City
name

Pro_id
Caste

Mobile_no
country
gothram

PROFILE

Drinking_habbi
ts

Smoking_habbi
ts

zodiac

images

star
education

salary

height

occupation
weight

4. Search

password

Profile Table:
Pro_id
Caste

Education

SEARCHPR
OFILE
Occupatio
n
Maritial_status

5. Feedback Table:

Feedback_id
Names

FEEDBACK

Comment
Feed_date

6. Image Gallery Table:


IMAGE
GALLERY
Image id

Profile_id
images

7. Send Message Table:


SEND
MESSAGE
form_id

to_id
message

8. Success Story Table:


SUCCESS
STORY
Add_date
user_id
story

Relation between Tables:


Name

id
Pro_id

passwr
d

Caste

User Login
With

Search

image
Image_id
d

Pro_id

Enters

With

Profile
Image
Salary

name
caste

Success

Has

Pro_id

Story
date

User_id

DATA FLOW DIAGRAM

Data Flow Diagram:


A Data flow diagram (DFD) is a graphical system model that shows all of the main requirements
for an information system in one diagram inputs and outputs, processes, data storage. A DFD
describes what data flows rather than how it is processed. Everyone working on the development
project can see all aspects of the system working together at once with DFD. That is one reason
for its popularity. The DFD is also easy to read because it is graphical model.
The DFD is mainly used during problem analysis. End user, management and all
information system workers typically can read and interpret the DFD with minimal training.

Symbol:
Sr.
No.
1

Symbol

Name

External
entity

2
Process

3
Dataflow

Description
An external entity is
source or destination
of data flow which is
outside the area of
study.
A process shows a
transformation or
manipulation or
multiplication of data
flow within the
system.
A data flow shows the
flow of information
from source to
destination .A data
flow is represented by
a line with
arrowheads
Showing the flow.

Searching for Partners


Weddings.com
User

Regist
ration

Regist
ration

Search

1
Registe
r

Add

Add

Educ
ation

New User

Resul

3
Search

User

Search
Informatio
n

old user
Password

2
Login

Reject

Regist
ration

User

Edit
Verification

Response

Email id

Educ
ation

Update
data
U
p
d
Regist
ration

Respon

APPLICATION
NAVIGATION

HOME PAGE NAVIGATION

0
HOME
PAGE

REGISTER
PAGE

LOGIN
PAGE

CONTACT
US PAGE

FEEDBACK
PAGE

SUCCESS
STORY

5
ADMIN
LOGIN

USER LOGIN

LOGIN
PAGE
OPEN USER PROFILE

My Profile
PAGE

Make
Payment

Messages
PAGE

Logout
PAGE

Search
PAGE

Upload
Image

Update Me
PAGE

LOGIN PAGE NAVIGATION

0
ADMIN
LOGIN

Paid
Member

Non-Paid
Member

Password
Reset

Feedback
PAGE

Logout
PAGE

ADMIN LOGIN PAGE NAVIGATION

ACTIVITY DIAGRAM

ACTIVITY DIAGRAM:

INPUT VALIDATION

DISPLAY RECORDS:

SEARCH RECORDS:

UPDATE RECORDS:

CASE DIAGRAM

CASE DIAGRAMS

Admin case diagram:

User Case Diagram:

Login Case Diagram:

EVENT TABLE

EVENT TABLE

A table that list events in tabular format that is in rows and key pieces of information about each
event in columns is known as event table.
While developing the list of events, the analyst should note additional information about each
event for later use.
This information is entered in an event table.
An event table comprises of rows and columns.
Each row in an event table records information about one event.
And each column is about its key piece of information about that event.

Attributes of Event Table:

Trigger:
An occurrence that tells the system that has occur, either the arrival of data needing or of a
point in time.
Source:
An external agent or actor that is supplies data to the system.
Activity:
Behavior of that the system performs when an event occur.
Response:
An output produce by the system, that goes to a destinations.
Destination:
An external agent or an actor that is receives data from system.

Sr.
No
.

Event

Trigg
er

Source

Activit
y

Respo
nse

Designat
ion

Click on
Admin

Admin

Display
Admin
page

Form
open

Admin

Click on login

User

Display
User
profile

Form
open

User

Click on
Feedback

User

Display
Feedback
form

Form
open

User

Click on
Contact us

User

User

Click on
Register

Display
contact
us form
Display
Registrati
on form

Form
open

Form
open

User

Click on
Success
Story

To
open
admin
page
To
open
profile
of user
To
send
feedba
ck
To
contac
t
To
create
new
user
profile
To see
the
story

Form
open

User

Click Update
me

User

Form
open

User

Click on
generate

Display
the list in
table

Admin

Click on
Upload photo

10

Click on find
password

11

Click on
logout

12

Click on
message

To edit
user
profile
To
genera
te paid
memb
er list
To
upload
picture
s
To
send
user
back
To exit
to the
profile
To
expres
s
interes
t

Display
Form of
success
story
Display
update
form
Retrieve
data

13

Click on

To

User

User

Admin

User

Display
Picture
upload

Form
open

User

Admin

Retrieve
data

Open
dialog
box

Admin

Admin and
user

Form
open

Admin and
user

User

Display
the home
page
Display
the send
message
form

Form
open

User

User

Display

Form

User

TESTING PLAN:
Similar to the project plan, due to confidentiality issues, we cannot provide details test plan to the
development team. We will still add the core components that make up our test plan.

Test plan identifier

References

Introduction

Test items (functions)

Application risk issues.

Features to be tested

Features not to be tested

Approach (strategy)

Item pass/fail criteria

Entry & exit criteria

Suspension criteria & resumption requirements

Test deliverables

Remaining test tasks

Environmental needs

Staffing and training needs

Responsibilities

Planning risks and contingencies

Approvals

Glossary

TESTING STRATEGY:
Test More and Test Frequent is organizations tagline for testing. A typical screen in asp.net is
tested at four levels before it goes for production.
Level 1 is generally the work to be tested by other developers or other interns (this is typical first
level of testing where focus is not on requirement but end user testing) Ratio: 0% end user: 100%
Technical
Level 2 is level where a senior programmer comes into the testing cycle of the screen that was
unit tested by the developer in this phase the onus is to test software for technical requirements
specified.

Ratio: 80% Technical: 20% end user


Level 3 is where a tester will come into picture. The tester will test the software for both end user
as well as technical point of view.
The ratio here is: 50% Technical: 50% end user
Level 4 is where we make the code at Release-Ready. Here screen is tested to the core and each
and every standard must be followed and verified.
Ratio here is: 80% User Testing 20% Technical
This allows us to text a screen at four levels and at the end of four weeks when the screen goes to
production, it is generally bug free because more people have looked at this screen from different
viewpoints.
References available while testing:

Project Plan.

System Requirements specifications.

High Level design document.

Detail design document.

Development and Test process standards.

Methodology.

Low level design.

Also organization has Separate module to store all bugs


So each screen is released for testing as a build and all information for that screen (till release) is
maintained using this particular build.

CONTENT TESTING:
Errors in Web Application content can be as trivial as minor typographical error as incorrect
information, improper organization or validation of intellectual property laws. Content Testing
attempt to uncover this and many other problems before the user encounter them.

Content Testing Objectives


There are three types of objectives.

To uncover syntactic errors in text-based documents, graphical representation and other


media.

To uncover semantic errors in any content object represented as navigation occurs, and

To find errors in organization or structure of content that is presented to the end-user

DATABASE TESTING:
Modern Web Application does much more than present static content objects. In many
application domains, Web Application interface with sophisticated database management system
and build dynamic content object that are created in real time using the data acquired from a
database.
Database Testing for Web Application is complicated by a variety of factor.
1) The original client side request for information is rarely presented in the form that can be input
to a database management system.
2) The database may be remote to the server that houses the Web application.

3) RAW data acquired from the database must be transmitted to the Web application Server and
properly formatted for subsequent transmittal to the client.
4) The dynamic content objects must be transmitted to the client in a form that can be displayed
to the end user.

Client layer-user
interface
Server layer- WebApp

Server layerServer layer

- data

Management

Database layer data


access

d
Database
[Layers of interaction]

In figure testing should be ensure that,


1. Valid information is passed between the client and server from the interface layer
2. The Web application process script correctly and properly extracts or formats user data.
3. Queries are passed to a data management layer that communicates with database access
routines.
4. User data are passed correctly to a server side data transformation function that format
appropriate queries.

INTERFACE TESTING:

Interface design model is reviewed to ensure that generic quality criteria established for all user
interfaces have been achieved and that application specific interface design issue has been
properly addressed.

Interface testing strategy:


The overall strategy for interface testing is to (1) Uncover error related to specific Interface
mechanisms (2) uncover errors in the way the interface implements the semantics of navigation,
Web Application functionality, or content display. To accomplish this strategy, a number of
objectives must be achieved.
Interface futures are tested to ensure that design rules, aesthetics, and related visual content are
available for the user without error. Individual interface mechanisms are tested in a manner that
is a logout to unit testing for examples; tests are designed to exercise all forms, client-side
scripting, dynamic HTML.Each interface mechanism is tested within the context of a use-case or
NSU for a specific user category. The interface is tested within a variety of environments to
ensure that it will be compatible.

Testing Interface Mechanisms:


When a user interacts with a Web Application, the interaction occurs through one or more
interface mechanisms.

Links: -

Each link is tested to ensure that the proper content object or function is reached. The
Web engineer builds a list of all linksassociated with interface layout. And then executes
eachindividually.

Forms: At a microscopic level, tests are performed to ensure that labels correctly identified
fields within the form and that mandatory fields are identified visually for the user. The server
receives all information content within the form and their no data are lost in the transmission
between client and server. Appropriate defaults are used when the user does not select from a
pull down menu or set of buttons.Browser function dont corrupt data enter in a form and Scripts
that perform error checking on data entered work

Properly and provide meaningful error

message.

Client side scripting:Black box tests are conducted to uncover any error in processing As the script is
executed . These tests are coupled with forms testing because script input is often derived from
data provided as part of forms processing

Dynamic HTML:Each Web page that contains dynamic HTML is executed to ensure that the dynamic
display is correct. In addition a compatibility test should be conducted to ensure that the dynamic
HTML is work properly in the environmental configuration that support the Web application.

Application specific interface mechanisms:-

Test conforms to a checklist of functionality and features that are defined by the interface
mechanism. Boundary test is minimum and maximum number of items that can be placed in to
shopping chart. Test to determine persistence of shopping chart contents. Test to determine
whether the Web Application can be record shopping chart content at some future date.

USABLITY TESTING:
Usability test may be designed by Web engineering team. Define a set of usability testing
categories and identify goal for each. Design test that will enable each goal to be evaluated.
Select participants who will conduct test. Instrument participants interaction with Web
Application while testing is conducted.Develop a mechanism for assessing the usability of the
Web Application.

The following test categories and objective illustrate


establish testing:
Interactivity
Are interaction mechanisms easy to understand and use?
LayoutAre navigation mechanisms, content and function place in a manner that allows the user to find
them quickly?

ReadabilityIs text well written and under stable?

AestheticsDo layout color, typeface, and related characteristics lead to ease of use ?

Display CharacteristicsDoes the Web Application make optimal use of screen size and resolution?
Time SensitivityCan important features, functions and content be used in a timely manner?
AccessibilityIs the Web application accessible to people who have Disabilities?

COMPATIBILITY TESTING:
Web application must operate within environment that differs from one another. Different
computer, display device, OS, browser and network connection speed can have significant on
Web application operation. Different browser some time produced slightly different results,
regardless of the degree of HTML standardization within the Web application.
The Web Engineering team derives a series of compatibility, validation tests, derived
from existing interface tests, navigation tests, performance tests and security tests.

TESTING METHOD:
Testing is presents an interesting anomaly for the software engineering activities, the engineer
attempts to build software from an abstract concept to a tangible product. Now comes testing.
The engineer creates a series of test case that are initiated to "demolish" the software that has
been build. Infect, testing is the one step in the software process that could be viewed
(psychologically, at least) as destructive rather than constructive.

Models of Testing:There are different Models of testing. On the basis of testing methods there are two types
of testing:
1. Black-box testing.
2. White-box testing
Black-box tests are used to demonstrate that software functions are operational, that input is
properly accepted and output is correctly produced, and that integrity of external information is
maintained.
White-box tests are used to examine the procedural details. It checks the logical paths by test
case. It can also checks the conditions, loops used in the software coding. It checks that loops are
working correctly on defined boundary value.

WHITE-BOX TESTING:
White-box testing sometimes called glass-box testing, is a test case design method that users the
control structure of the procedural design to drive the test case.Always we are thinking that there
is no necessary to execute or checks the loops and conditions. And large number of errors is
uncovered. With using white-box testing methods, we have checked that; all independent paths
within a function have been executed at least

once.

All logical decisions are their true and false side. All loops working correctly at their boundary
values and within their specified conditions.
In our coding we test that all the loops works truly in each module. The one
technique of white-box testing is basis path testing. It contains two parts, one is flow graph
notation and the second is cyclometer complexity. In flow graph notation we are checking logical
control of flow. By using cyclometer complexity we find complexity of our project structure.

BLACK-BOX TESTING:
Black-box testing focuses on the functional requirements of the software. That is black-box
testing enables the software engineer to drive sets of input conditions that will fully exercise all
functional Requirements for the program. Black-box testing is not an alternative to white-box
testing techniques. Rather, it is a complementary approach that is likely to uncover a different
class of errors than white-box methods.
We use in our coding to find errors in the following categories:

Incorrect or missing functions

Interface errors

Errors in database

Performance errors

Initialization and termination errors.

Unlike white-box testing, which is performed earlier in the testing process, black-box testing
tends to be applied during later stages of testing. Because black-box testing purposely disregards
control structure, attention is focused on the information domain.
By applying black-box techniques, we derive a set of test cases that satisfy following criteria .
Test cases that reduce, by a count that is greater then one, the number of additional test cases
must be designed to achieve reasonable testing.

Level 1 - Build Acceptance Tests

Other related test cases ensure that adopters received the proper Development Release Document
plus other build related information (drop point, etc.). The objective is to determine if further
testing is possible. If any Level 1 test case fails, the build is returned to developers un-tested.
Level 2 - Smoke Tests
The objective is to determine if further testing is possible. These test cases should
emphasize breadth more than depth. All components should be touched, and every major feature
should be tested briefly by the Smoke Test. If any Level 2 test case fails, the build is returned to
developers un-tested.
Level 2a - Bug Regression Testing
Every bug that is Open during the previous build, but they marked as Fixed, Needs
Re-Testing for the current build under test, is need to be regressed, or re-tested. Once the
smoke test is completed, all resolved bugs need to be regressed. It should take between 5
minutes to 1 hour to regress most bugs.
Level 3 - Critical Path Tests
Critical Path test cases must pass by the end of every 2-3 Build Test Cycles. They do not
need to be tested every drop, but must be tested at least once per milestone. Thus, the Critical
Path test cases must all be executed at least once during the Iteration cycle, and once during the
Final Release cycle.
Level 4 - Standard Tests
Test Cases that need to be run at least once during the entire test cycle for this release.
These cases are run once, not repeated as are the test cases in previous levels. Functional testing
and detailed Design Testing (Functional and Design Test Cases, respectively).These can be tested
multiple times for each Milestone Test Cycle (Iteration, Final Release, etc.).
Standard test cases usually include Installation, Data, GUI, and other test areas.

Level 5 - Suggested Test

These are Test Cases that would be nice to execute, but may be omitted due to time
constraints.

Bug Regression:
Bug Regression will be a central tenant throughout all testing phases. When a Severity 1 bug
fails regression, adopters testing team should also put out an immediate email to development.
The Test Lead will be responsible for tracking and reporting to development and product
management the status of regression testing

GANTT CHART

The Gantt chart

A Gantt chart is a horizontal bar chart developed as a production control tool in


1917 by Henry L. Gantt, an American engineer and social scientist

Gantt chart is the Graphical Representation about the progress of the project.
Gantt chart shows the details about the how much time taken for any task.

Gantt chart is a type of bar chart that illustrated the project schedule. It shows the
start & finish of the project.

Gantt chart shows the time taken by the task for each phase. Gantt chart decides
the standard of the system. It is a useful tool for planning & scheduling projects.

Gantt chart contains two columns. First is task and other is month (timing). In the
task columns there are five options or phase find in the months columns shows
the progress of the project.

Testing Phase:

Planning

Execution

PERT CHART

The Pert Chart


What it is?

A PERT (Project Evaluation & Review Techniques) chart is a graphic representation of a


projects schedule, showing the sequence of tasks, which tasks can be performed simultaneously.
The critical path of task that is must be completed on time in order of their project to meet its
completion deadline.
The chart can be constructed with a variety of attributes, such as earliest and latest start dates for
each task, earliest and latest finish dates for each task, and stack time between tasks.
A PERT chart can document an entire project or key phase of a project.
The chart allows a team to avoid unrealistic timetables and schedule expectations, to help
identify and shorten tasks that are bottlenecks, and to focus attention on most critical tasks.

When to use it?


Because it is primarily a project-management tools, a PERT chart is most useful for planning and
tracking entire projects or for scheduling and tracking the implementation phase of a planning or
improvement effort.

How to use it?


Identify all tasks or project components.
Make sure the team includes people with firsthand knowledge of the project so that during the
brainstorming session all component tasks needed to complete the project are captured.
Document the tasks on small note cards.
Identify the first task that must be completed.
Place the appropriate card at the extreme left of the working surface.
Identify any other tasks that can be started simultaneously with task #1.
Align these tasks either above or below task #1 on the working surface.

Identify the next task that must be completed.


Select a task that must wait to begin until task #1(or a task that starts simultaneously with task
#1) is completed. Place the appropriate card to the card showing the preceding task.

Identify any other tasks that can be started simultaneously with task #2.
Align these tasks either above or below task #2 on the working surface.
Continue this process until all component tasks are sequenced.

Identify task durations:


Using the knowledge of team member, reach a consensus on the most likely amount of time each
task will require for completion.
Duration time is usually considered to be elapsed time for the task, rather than actual number of
hours/days spent doing the work. Document is duration time on the appropriate task cards.

Construct the PERT chart:


Number each task, draw connecting arrows, and task characteristics such as duration, anticipate
start date, and anticipated end date.

Determine the critical path:


The projects critical path includes those tasks that must be started or completed on time to avoid
delays to the total project. Critical paths are typically displayed in red.
Note: most commercially available project management software will routinely generate a PERT
chart.

REQUIREMENT
SPECIFICATION

Requirement Specification
Software Specification:-

Operating System

Windows XP, Windows 7 and 8.

Front End

MS Visual Studio 2008

Back End

MS SQL Server 2008 R2

Web Browser

Google Chrome

Web Server

INTERNET INFORMATION SERVISE (IIS)

Hardware Specification:1. Minimum Requirement:Processor

1.36 GHz

RAM

512 MB

Screen revolution

1024X768 display 5400 RPM Hard disk

Supported Architecture

X86 and x64

2. Maximum Recommended:Processor

2.2 GHz

RAM

1024 MB or more

Screen revolution

1280X1024 display 5400 RPM Hard disk

Supported Architecture

X86 and x64

STRUCTURED TREE
DIAGRAM

Structured Tree Diagram:

Matrimonial Web

HOME

REGIS
Log

LOGIN
User

CONT

FEED

ADMI
Log

SUCCESS

CONCLUSION

Conclusion:

Matrimonial Web Application is to provide Grooms and Brides with excellent matchmaking
experience by exploring the opportunities and resources to meet true potential partner.
Matrimonial website which is provide platform to a lot of Bride/Groom for finding perfect
match. There are different sectors like Registration, Partner, Search, etc. So the Bride/Groom can
get their interest for find their partner. Bride/Groom can directly search Partner according to their
required criteria. The Bride/Groom can use match By Email functionality so he/she can get
directly E-mail alert for the match which fulfill their required criteria. It helps the user by
providing profiles of perspective Bride or Groom and other information regarding them
online.
Matrimonial web application provides facility like quick tour. This is a module that contains the
flow of the website .Here user can have a idea how he can commit himself in the website.
Matrimonial web application provides facility to change preference about partner.
This application provide facility like edit profile, update photo and delete photo, hide profile,
create album, send express interest, send personal message, apply for loan to the user.

Vous aimerez peut-être aussi