INTRODUCTION

1. INTRODUCTION

1.1Project Details: Broad specifications of the project work

 Project Definition
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.
 What is Matrimonial Web Application?
Matrimonial Web Application will allow a new user to register and after successfully
registration. After completing registration users profile will be visible to other users.
Matrimonial website which will 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.
For This Application, we will provide following capabilities:
(1) Admin Module
(2) User Registration Module
(3) Image Uploading module
(4) Search Module
(5) Success story
(6) Feedback

Considering the security and privacy aspects, Matrimonial Web Application will use
HTTPS protocol (A version of the HTTP protocol that includes data encryption for
security.)
The application will have to be completed using Visual Studio 2008 and SQL Server
2005 with help of other office productivity tools such as Microsoft Visio 2003.

1
L.J. Institute of Engineering and Technology
 INTRODUCTION

The application testing criteria and installation requirements will be part of the
detailed application architecture document.

1.2 Purpose
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.

1.3 Scope
 Matrimonial website which will provide platform to a lot of Bride/Groom for
finding perfect match.
 There are different sectors like Registration, 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.

1.4Technology and Literature Review

1.4.1 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

2
L.J. Institute of Engineering and Technology
 INTRODUCTION

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.

1.4.2 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

1.4.3 Common Language Specification

To fully interact with other objects regardless of the language they were
implemented in, objects must expose to callers only those features that are common to all
the languages they must interoperate with. For this reason, the Common Language
Specification (CLS), which is a set of basic language features needed by many
applications, has been defined. The CLS rules define a subset of the Common Type
System; that is, all the rules that apply to the common type system apply to the CLS,
except where stricter rules are defined in the CLS. The CLS helps enhance and ensure
3
L.J. Institute of Engineering and Technology
 INTRODUCTION

language interoperability by defining a set of features that developer can rely on to be

available in a wide variety of languages. The CLS also establishes requirements for CLS
compliance; these help you determine whether your managed code conforms to the CLS
and to what extent a given tool supports the development of managed code that uses CLS
features.

1.4.4 Common Language Runtime

The Common Language Runtime (CLR) is the virtual machine component of

Microsoft's .NET initiative. It is Microsoft's implementation of the Common Language
Infrastructure (CLI) standard, which defines an execution environment for program code.
The CLR runs a form of byte code called the Microsoft Intermediate Language (MSIL),
Microsoft's implementation of the Common Intermediate Language.

The virtual machine aspect of the CLR allows programmers to ignore many
details of the specific CPU that will execute the program. The CLR also provides other
important services, including the following:

• Memory management
• Thread management
• Exception handling
• Garbage collection
• Security

1.4.5 Introduction to ASP.NET

Microsoft, realizing that ASP does posses some significant shortcomings,

developed ASP.net. ASP.net is a set of components that provide developers with a
framework with which to implement complex functionality. Two of the major
improvements of ASP.net over traditional ASP are scalability and availability. ASP.net is
scalable in that it provides state services that can be utilized to manage session variables
across multiple web services in a server farm. Additionally, ASP.net possesses a high

4
L.J. Institute of Engineering and Technology
 INTRODUCTION

performance process model that can detect application failures and recover from them.
We use the fundamentals of programming with VB using Visual Studio .NET and .NET
framework.

Features of ASP.NET:
(1) Component Infrastructure.
(2) Language Integration.
(3) Internet Interoperation.
(4) Simple Development.
(5) Simple Deployment.
(6) Reliability.
(7) Security

1.4.6 Introduction to Microsoft SQL Server

Microsoft SQL Server enhances the performance, reliability, and scalability

provided by earlier releases of SQL Server by making the processes of developing
applications, managing systems, and replicating data easier than ever.

SQL server also contains many of the front-end tools of PC databases that
traditionally haven’t been available as part of either mainframe or minicomputer
databases. In addition to using a dialect of Structured Query Language (SQL), GUI
applications can be used for the storage, retrieval, and administration of the database.

5
L.J. Institute of Engineering and Technology
 INTRODUCTION

2. PROJECT MANAGEMENT

2.1 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.

There are three different ways feasibility can be tested

1) Economical Feasibility
2) Technical Feasibility
3) Operational Feasibility.
2.1.1 Economical Feasibility:
In economical 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 economical feasibility.

2.1.2 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.
2.1.3 Operational Feasibility:

Once the system is designed there must be trained and expert operator. If there
are not trained they should given training according to the needs of the system.

6
L.J. Institute of Engineering and Technology
 INTRODUCTION

From the user’s 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.

2.2 Project Planning

2.2.1 Project Development Approach and Justification

Waterfall Model has been adopted as an approach for development of project. Most of
the requirements of the project are fixed and already thought of very less functionality
updation is expected in future. So Waterfall model is the right approach for our project.

Justification:
As our application is a matrimonial website the requirements are much clear as we have
number of reference matrimonial websites which can be used as reference so by looking
that our requirements and functionalities that are to be implemented are clear.

As waterfall model is used for project whose requirements and functionalities are already
known and as our project falls in this category we have chosen waterfall model as an
approach to develop our project.

2.2.2 Project Plan

Project was well planned. Project began with gathering user requirements, than
diagrammatic representation of the functionalities was designed. Required Database was
designed and normalized as required. Code was written in such a way that maximum
functionality was coded with minimum possible lines of code.

2.2.3 Roles and Responsibilities

Following are our project members with their roles in the project and their
responsibilities.
Nirav Patel
Analysis and design Vishal Patel
Sulabh Gajjar

7
L.J. Institute of Engineering and Technology
 INTRODUCTION

Nirav Patel
Coding Vishal Patel
Sulabh Gajjar
Nirav Patel
Testing Vishal Patel
Sulabh Gajjar
Table 2.1 Roles And Responsibilities.

2.3 Project Scheduling

Project scheduling chart

Scheduling the project task is an important project planning activity .It involves
deciding which tasks would be taken up when.

Based on the planned duration of required tests and collection of resources to

complete those tasks projected completion date is calculated. We have prepared timeline
Chart shown as below fig.

Fig.2.1 Scheduling.

8
L.J. Institute of Engineering and Technology
 INTRODUCTION

3. SYSTEM REQUIREMENT STUDY

3.1 User Characteristics
Our system will be used by two types of users they are as follows

Admin User: This type of user will be responsible to manage whole site & also
content that will be published in site. This type of users will be given special training
for doing this if required.

Registered User : This type of user will be able to visit our site and navigate to
different pages to get information they will not be able to change any content on
website .They will be able to give feedback for improvement of website.

3.2 Hardware and Software Requirements.

Minimum software and hardware requirements to run our system are as follows.
3.2.1 Hardware requirements:
The system should have these hardware requirements:
The processor should be at least Pentium 3 or above
The processor speed should be greater than 400 MHz
The video device should support graphics
Ram should be or greater than 120 mb

3.2.2 Software requirements:

Any operating System (windows XP sp2, Vista, etc.)
Sql Server 2005 as dbms for managing database
Visual studio 2008

3.3 Constraints
3.3.1 Hardware Limitations
There must be a 64 MB on board memory
3.3.2 Interfaces to Other Applications
Not applicable.
3.3.3 Higher Order Language Requirements
ASP 3.0 (Language C#)
3.3.4 Reliability Requirements

9
L.J. Institute of Engineering and Technology
 INTRODUCTION

Our system will require a reliable web server which has minimum downtime so that
our website is up & running for maximum amount of time .There should be proper
facilities available for regular backups.

3.3.5 Safety and Security Consideration

Basic security mechanism which prevents any unauthorized access to the system must
be implemented and a mechanism to trace any unauthorized access should be there
also the log of users who visited our site must be maintained time to time.

3.4 Assumptions and Dependencies

Regulatory policies: It is a mandatory that no text book must be left empty or contains
insufficient data.
Hardware limitations: There must be a 64 MB on board memory
Control functions: The software must be very user-friendly and display appropriate error
messages.
Interfaces to other applications: Not applicable.
Parallel operations: It must support many users simultaneously.
Reliability requirements: Data redundancy and use of special/blank characters must be
avoided.
Safety/security considerations: The application must be exited always normally.
Higher order language requirements: ASP 3.0 (Language C#)

10
L.J. Institute of Engineering and Technology
 INTRODUCTION

4. SYSTEM ANALYSIS
4.1 Study of Current System
To update any content or any part of site it requires using FTP and changing the content
manually.

4.2 Problem and Weaknesses of Current System

The current system has following weaknesses.

1) User interface is not up to professional mark.

4.3 Requirements of New System

4.3.1 User Requirements

User requirement are specifies requirement of the user of the system. The user
requirements are:

 User can register and make an account. For that user has to fill up the registration
form and submit the information to the database.
 User searches for other user profiles from the homepage without registering using
simple search. User can also search after logging in to his account for more
detailed information.
 User can give feedback about the site using feedback option, which can be after
read by the administrator.

4.3.2 System Requirements

 Facility to delete profile after admin login.

 Easy to use for guest & admin users.
 Should work efficiently even on slow internet connections.
 Dynamic contents like success story etc are expected.

11
L.J. Institute of Engineering and Technology
 INTRODUCTION

For Object Oriented Approach.

4.4 Class Diagram:

12
L.J. Institute of Engineering and Technology
 INTRODUCTION

4.5 Use Case Diagram:

Fig.4.2 Use case Diagram

13
L.J. Institute of Engineering and Technology
 INTRODUCTION

4.6 Sequence and Collaboration Diagram:

14
L.J. Institute of Engineering and Technology
 INTRODUCTION

15
L.J. Institute of Engineering and Technology
 INTRODUCTION

16
L.J. Institute of Engineering and Technology
 INTRODUCTION

17
L.J. Institute of Engineering and Technology
 INTRODUCTION

18
L.J. Institute of Engineering and Technology
 INTRODUCTION

19
L.J. Institute of Engineering and Technology
 INTRODUCTION

20
L.J. Institute of Engineering and Technology
 INTRODUCTION

4.7 Data Flow Diagram

21
L.J. Institute of Engineering and Technology
 INTRODUCTION

4.8 ER Diagram

22
L.J. Institute of Engineering and Technology
 INTRODUCTION

4.9 Activity Diagram

Activity diagram for registration

23
L.J. Institute of Engineering and Technology
 INTRODUCTION

Activity diagram for user login

4.10 Features of New System.

The new system that is expected to replace this application is expected to have much
more features and good design.

The user interface is expected to be of professional level, users shall be able to give their
opinions in the Feedback consol and some dynamic contents are also expected to be
added.

24
L.J. Institute of Engineering and Technology
 INTRODUCTION

5. SYSTEM DESIGN
5.1 Database Design/Data Structure Design
5.1.1 Table and Relationship :

25
L.J. Institute of Engineering and Technology
 INTRODUCTION

5.2 Input Output & Interface Design:

5.1.2 Samples of Forms Reports & Interface
Home page:

Registration Form:

26
L.J. Institute of Engineering and Technology
 INTRODUCTION

Contact us:

Feedback Form:

27
L.J. Institute of Engineering and Technology
 INTRODUCTION

About us:

28
L.J. Institute of Engineering and Technology
 INTRODUCTION

User profile:

Search:

29
L.J. Institute of Engineering and Technology
 INTRODUCTION

30
L.J. Institute of Engineering and Technology
 INTRODUCTION

5.3 State chart diagram

State chart diagram for registration

State chart diagram for user login

31
L.J. Institute of Engineering and Technology
 INTRODUCTION

6. IMPLEMENTATION PLANNING

6.1 Implementation Environment (Single vs Multi user, GUI vs

Non GUI)
As the application is stand-alone application so there is a no multi user for our application
rather than a single user .User can do information entry whenever required and uses
different utilities and for that, a better GUI application is needed.

6.2 Program/Modules Specification

The main modules of the system are:

 Registration
In this module user can register a new account.
 Login
Here the user can log in to his/her account by inserting his/her user id and
password and see his profile page.
 Update Profile
User uses this module to update previously inserted information in profile.
 Search
In this module a user can search another user profiles by inserting appropriate
user keywords.
 Give Feedback
User can give feedback about the site in this module.
 Delete Profile
This module is for the administrator. Administrator can delete some specific
users’ profiles which have been noticed as fake profiles.
 View Feedback
In this module administrator can read the feedbacks given by the users.

6.3 Security Features

We have basically two types of user with different accessibility rights. They are at
are administrator and the Members. All have their own username and password and all
users have different rights to use an application.
There is account lockout policy to protect user’s account. If maximum number of
wrong password is made within a specified time window then the account will be locked
and will be unlocked by administrator by request.

32
L.J. Institute of Engineering and Technology
 INTRODUCTION

6.4 Coding Standards

Classes - Class names should always be a noun and, again, should be meaningful. Avoid
verbs.
class Search
{
...
}

Methods - Always use a verb-noun pair, unless the method operates on its containing
class, in which case, use just a verb.
public void GetPath();

Methods with return values - The name should reflect the return value.
public int GetImageWidth(Bitmap image);

Variables - Do not abbreviate variable names. Variable names should again be

descriptive and meaningful.
int quantityCount = 0;
int index = 0;
string temp = "";
Pascal Casing - Use PascalCasing for classes, types, methods and constants.
public class Search
{
public void BookName ();
}

33
L.J. Institute of Engineering and Technology
 INTRODUCTION

7. TESTING
7.1 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.

7.2 Testing Strategy

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.

Unit Testing

 Black box and white box testing.

 Module interfaces are tested for proper information flow.

34
L.J. Institute of Engineering and Technology
 INTRODUCTION

 Local data are examined to ensure that integrity is maintained.

 Boundary conditions are tested.
 Basis path testing should be used.
 All error handling paths should be tested.
 Drivers and/or stubs need to be developed to test incomplete software. 

Integration Testing

Top-down integration testing

 Main control module used as a test driver and stubs are substitutes for
components directly subordinate to it.
 Subordinate stubs are replaced one at a time with real components (following the
depth-first or breadth-first approach).
 Tests are conducted as each component is integrated.
 On completion of each set of tests and other stub is replaced with a real
component.
 Regression testing may be used to ensure that new errors not introduced.

Bottom-up integration testing

 Low level components are combined in clusters that perform a specific software
function.
 A driver (control program) is written to coordinate test case input and output.
 The cluster is tested.
 Drivers are removed and clusters are combined moving upward in the program
structure.

7.3 Testing Methods

Testing 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.

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

35
L.J. Institute of Engineering and Technology
 INTRODUCTION

 White-box testing

There exist several popular white-box testing methodologies:

 Statement coverage
 Branch coverage
 Path coverage
 Condition coverage
 Mutation testing
 Data flow-based testing
Statement coverage
Statement coverage methodology focuses on, designing test cases so that,
 Every statement in a program is executed at least once.
 No statement in the program should remain unreachable.
Branch coverage
Test cases are designed such that, different branch conditions
 Give true and false values in some execution.
 All branches are traversed.
Branch testing guarantees statement coverage. It is a stronger testing compared to the
statement coverage-based testing.
Path coverage
Design test cases such that, all linearly independent paths (LIP) in the program are
executed at least once. To understand the path coverage-based testing we need to learn
how to draw control flow graph of a program.
A control flow graph (CFG) describes,
 The sequence in which different instructions or statements of a program get
executed.
 The way control flows through the program.

Condition coverage
Test cases are designed such that, each component of a composite conditional expression
It help us to,
 Gives both true and false values.
 To check for all combination of conditions.

36
L.J. Institute of Engineering and Technology
 INTRODUCTION

 Black Box Testing:

Equivalence Partitioning
Black-box technique that divides the input domain into classes of data from which
test cases can be derived an ideal test case uncovers a class of errors that might require
many arbitrary test cases to be executed before a general error is observed

Equivalence class guidelines:

 If input condition specifies a range, one valid and two invalid equivalence classes are
defined
 If an input condition requires a specific value, one valid and two invalid equivalence
classes are defined
 If an input condition specifies a member of a set, one valid and one invalid
equivalence class is defined
 If an input condition is Boolean, one valid and one invalid equivalence class is
defined 

Boundary Value Analysis

Black-box technique that focuses on the boundaries of the input domain rather than its
center
BVA guidelines:
 If input condition specifies a range bounded by values a and b, test cases should
include a and b, values just above and just below a and b
 If an input condition specifies and number of values, test cases should be exercise
the minimum and maximum numbers, as well as values just above and just below the
minimum and maximum values
 Apply guidelines 1 and 2 to output conditions, test cases should be designed to
produce the minimum and maxim output reports If internal program data structures
have boundaries (e.g. size limitations), be certain to test the boundaries

7.4 Test Cases

Case 1. Admin Login
Condition Action
Correct user and correct Password Accepted
Correct user and incorrect Password Rejected
Incorrect user and incorrect Password Rejected
Incorrect user and correct Password Rejected

Table 7.1 Admin Login Test Case

37
L.J. Institute of Engineering and Technology
 INTRODUCTION

Case 2. E-mail id Validation

Condition Action
Correct e-mail id Accepted
Correct email id & incorrect length Rejected
Incorrect email id & correct length Rejected
Table 7.2 E-mail id validation Test Case

 Case 3. User Validation

Condition Action
Unique username, password length more Accepted
than 6 character and unique and valid
Email Id.
Conflicted username, password length Rejected
more than 6 character and unique and valid
Email Id.
Unique Username, password length less Rejected
than 6 character and unique and valid
Email Id.
Unique Username, password length more Rejected
than 6 character and conflicted or invalid
Email Id.
Table 7.3 Create User Test Case

38
L.J. Institute of Engineering and Technology
 INTRODUCTION

8. USER MANUAL
 Registration
In this module user can register a new account. For this user has to first select the
registration option from the home page and then fill up the registration form. In
the registration form there are some details about his/her personal information.

 Login
Here the user can log in to his/her account by inserting his/her user id and
password and see his profile page. Here the user can perform operations like
update profile, print profile, etc.

 Update Profile
User uses this module to update previously inserted information in registration
form or his/her profile data. Here user has to simply update the field he wants to
change and press the update button.

 Search
In this module a user can search another user profiles by inserting appropriate
user keywords. We have provided two types of search. User can use simple search
to search profiles from the home page. In simple search user don’t need to login to
his/her account. In other way the user can login to his/her account and use the
search functionality provided into his/her profile.

 Give Feedback
This functionality allows the user to give feedback about the website, which can
after be read by the administrator. User has to select give feedback option for that
and then he/she has to enter his/her name, email and his feedback about the
website. Then he has to simply submit the feedback.

 Delete Profile
This module is specifically designed for the administrator. Administrator can
delete some specific users’ profiles which have been noticed as fake profiles. For
this administrator has to login to administrator account. Here administrator can
see all the details of users’ accounts. Administrator has to just click the delete
option in left of the profile details.

 View Feedback
39
L.J. Institute of Engineering and Technology
 INTRODUCTION

This functionality is also designed for the administrator. Here administrator can
see the feedback given by the users and he can make changes according to the
requirements of the users.

 Change Password

Using this function a user can change the password for his/her account. For that
he has to select the change password option in the profile.

 Forgot Password
This function is used when some user has forgotten his/her password and wants to
retrieve the password. For this user has to select the forgot password option from
the homepage. Here the page requests the security question of the user and
corresponding answer to the question. Then this security question and answer are
matched in the database. If it matches the password is displayed on the screen.

 Change Photo

Using this function user can change the previously updated photo in the profile.
For this user has to select the change photo option in the profile and then browse
the photo from the his/her computer. User can also crop the photo and then upload
the photo.

40
L.J. Institute of Engineering and Technology
 INTRODUCTION

9. LIMITATION AND FUTURE ENHANCEMENT

Limitation:
Still this application has got its limitations like limited functionality and
somewhat week graphical front end; this is due to lack of time and experience with the
developers.

 The current system cannot provide paid membership.

Future Enhancement:
 It is possible to provide the web space to the users for creating his portal.
 It is possible to create our own mail server.
 It is possible to create chat server so that user can communicate with each other.
 It is possible to provide facility like create video album.

41
L.J. Institute of Engineering and Technology
 INTRODUCTION

10. CONCLUSION AND DISCUSSION

10.1 Self Analysis of Projects Viability
Every project work, does not matter software project or any other project, could
not be the result of sole effort; even though, developer team consists three member. We
think success of any project doesn’t depend only on better software development skills,
but also, zeal to listen and help the users. Only user interaction at development phase can
give you an idea to fulfill their requirements. Because, software product is of developer’s
up to the development or installation phase, but then after it is of user’s. We experienced
that do make the software for users not for fame of being better programmer or software
developer. Ultimately, users appraise your efforts not your peers.

10.2 Summary of Project Work

We have completed our project work based on using software engineering and
system analysis and design approach. Work that we have done with preplanning
scheduling related with time constrains and result oriented progress in project
development.

Our project starts in second week of January and completed this project at the end
of April. Initially, there were some problem regarding some phases but we have planned
to resolve those problems. We have divided our work in different phases and solved
problems and difficulties.

42
L.J. Institute of Engineering and Technology
 INTRODUCTION

11. REFERENCES

Books

 ASP.NET(Black Book).

 Professional ASP.NET(Wrox Publication).

 ASP.NET Complete Reference.

 Software engineering Concepts By Roger S.Presman

 Fundamentals of Software Engineering By Rajib Mall

 SQL Server 2005 (Wrox Publication).

Web Sites

 www.bharatmatrimonial.com

 www.shaadi.com

 www.jeevansathi.com

 www.simplymarry.com

43
L.J. Institute of Engineering and Technology