INDEX

1. Project Profile 1. Overview.

13

Scope of Project............................................................. 2. Feasibility study........................................................................... 3. Modules...................................................................................... 4. Generation of Reports................................................................... 2. Roles & Responsibility 3. Software & Hardware Requirement 4. System Analysis 5.1 5.2 5.3 5.4 22 44 54

Problem Definition........................................................... Fact Finding Techniques.................................................... Risk Analysis................................................................... Process Model............................................................ 80

5. System Design 6.1 6.2 6.3 6.4 6.5 6.6

Data Dictionay............................................................... Use-Case Diagram....................................................... Class Diagram................................................................. Activity Diagram.............................................................. State Diagram.......................................................... Data Flow Diagram.......................................................... 110

7. Layouts

7.1 7.2

Form Layouts................................................................... Report Layouts................................................................ 145

8. Software Metric 8.1

Estimation....................................................................... 154

9. System Testing 9.1 9.2 9.3 9.4 Testing

Principle..............................................................

Testability....................................................................... Model of Testing.............................................................. Test Strategy............................................................ 158

10. Future Enhancement

11. User Manual

159

12. Bibliography

160

Chapter 1 INTRODUCTION

1.2 PROJECT DETAIL

1.2.1 Project Definition Matrimonial Web Application. 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 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. 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) Image Uploading module (4) Creating album (5) Sending Express Interest (6) Sending Personal messages (7) Marriage Loan (8) Paid Membership (9) Search Module. (10) Quick Tour. (11) Directory. 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 2005 and SQL Server 2005 with help of other office productivity tools such as (Microsoft Front page 2003, Microsoft Visio 2003, Microsoft Project 2003 etc.) The application testing criteria and installation requirements will be part of the detailed application architecture document. 1.2.2 About Project Project profile Company Name Website Project Title Objective Of System : FUSION INFORMATICS PVT. LTD. : www.fusioninformatics.com : Matrimonial Web Application. : 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. Operating Systems Hardware Requirement : Microsoft Windows XP Professional With SP2 : Pentium 90 MHZ or Faster and 96 MB Ram (Client) Pentium 133 MHZ or Faster and 128 Ram (Server) Software Requirement Front End Back End Others : Microsoft Visual Studio .Net : Microsoft Visual Studio Asp.Net : Microsoft SQL Server : Guided By Microsoft Visio .Net Framework

: Director: Mr. Dhaval Shah

1.3 PURPOSE

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

1.4 SCOPE
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. . 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.

1.5 OBJECTIVE

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. What are the purposes of Matrimonial Web Application? 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.

1.6 TECHNOLOGY AND LITERATURE REVIEW

Operating System Technology Language Database

Window-xp .Net 2005 with 2.0 architecture Asp.net MS-SQL 2005 server Table 1.1 Technology and OS

1.6.1 The .net framework A frame work is commonly though 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. 1.6.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

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.

Fig 1.1 .Net architecture

1.6.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 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. If your component uses only CLS features in the API that it exposes to other code (including derived classes), the component is guaranteed to be accessible from any programming language that supports the CLS. Components that adhere to the CLS rules and use only the features included in the CLS are said to be CLS-compliant components. The CLS was designed to be large enough to include the language constructs that are commonly needed by developers, yet small enough that most languages are able to support it. In addition, any language constructs that makes it impossible to rapidly verify the type safety of code was excluded from the CLS so that all CLS-compliant languages can produce verifiable code if they choose to do so

1.6.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. Developers using the CLR write code in a high level language such as C# or VB.Net. At compile-time, a .NET compiler converts such code into MSIL (Microsoft Intermediate Language) code. At runtime, the CLR's just-in-time compiler (JIT compiler) converts the MSIL code into code native to the operating system. Alternatively, the MSIL code can be compiled to native code in a separate step prior to runtime. This speeds up all later runs of the software as the MSIL-to-native compilation is no longer necessary. Although some other implementations of the Common Language Infrastructure run on non-Windows operating systems, the CLR runs on Microsoft Windows operating systems. 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

10

1.6.5 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 that 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.plementations. 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 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. The project is the starting point for authoring applications, components & services in Visual Studio.NET 2005.It eats as a container that manages your source code, data connections & references. A project is organized as part of a solution, which can contain multiple projects that are independent of each other. C# project file has .asproj extension where as solution file has .sln extension.

11

In order to write code against an external component, your project must first contain a reference to it. A reference can be made to the following types of component. (1) .NET class libraries or assemblies (2) COM components (3) Other class libraries of projects in the same solution (4) XML web services Features of ASP.NET: (1) Component Infrastructure. (2) Language Integration. (3) Internet Interoperation. (4) Simple Development. (5) Simple Deployment. (6) Reliability. (7) Security 1.6.6 Introduction to Micro Soft 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. All of data processing is involved with the operations of storing and retrieving data. A database, such as Microsoft SQL Server, is designed as the central repository for all the data of an organization. The crucial nature of data to any organization underlines the importance of the method used to store it and enable its later retrieval. Microsoft SQL Server uses features similar to those found in other databases and some features that are unique. Most of these additional features are made possible by SQL Servers tight integration with the Windows NT operating system. SQL Server 12

contains the data storage options and the capability to store and process the same volume of data as a mainframe or minicomputer. Like most mainframe or minicomputer databases, SQL Server is a Database that has seen an evolution from its introduction in the mid-1960s until today. Microsofts SQL Server is founded in the mature and powerful relational model, currently the preferred model for data storage and retrieval. Unlike mainframe and minicomputer databases, a server database is accessed by users-- called clients--from other computer systems rather than from input/output devices, such as terminals. Mechanisms must be in place for SQL Server to solve problems that arise from the access of data from perhaps Hundreds of computer systems, each of which can process portions of the database independently from the data on the server. Within the framework of a client/server database, a server database also requires integration with communication components of the server in order to enable connections with client systems. SQL server also contains many of the front-end tools of PC databases that traditionally havent 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 fro the storage, retrieval, and administration of the database.

13

Chapter 2 ABOUT THE SYSTEM

14

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

15

For This Application, we will provide following capabilities: (a) Admin Module. The main functions of admin of are as mentioned below. 1) Login 2) Report generation 3) Logout Report of all members Report of free members and paid members User management

(b) User Registration Module. In this module when user fill-ups first three registration form user will get a member id and will also get conformation message on his/her Email id. After getting member id user will use his/her member id to login, and user can modify his/her profile, fill-up remaining form of registration, image upload, create album . (c) Image Uploading module. User can change his/her photo, Image uploading is done after registration only, so user must have member id for image uploading. (d) Creating album. User can create album.

16

(e) Search Module. This five types of search available for user.. Advance Search, Quick Search, Search by City, Search by Id, Search by Profession,

(f) Sending Express Interest. Here after searching the profile user can send a express interest to a profile of his liking .The messages here will be pre-defined here . (g) Sending Personal messages. Here after searching the profile user can send a Personal Message to a profile of his liking .For this functionality user must be a paid member. (h) Marriage Loan. Here user can apply for marriage loan .For this to happen user have to fill up the form for loan specifying his need for loan and loan amount . (i) Paid Membership. Some of the facilities can only be done by only paid members .And they are like Send a personal message ,viewing album of user, viewing contact information.

17

(j) Profile Management Module. After login user will be redirected to the page containing his information .User can edit ,update and delete the profile if no longer he wants to retain it . (k) 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. (l) Directory. This is a module that contains the details like hotels, beauticians .Here user can have best options for appropriate category to chose among them.

2.2 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?

18

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. 2.2.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.2.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.

19

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

2.3 SOFTWARE MATRICES

2.3.1 Estimation:In Web engineering, the metrics have three goals: 1 2 3 To provide the indication of the quality from the technical point of view. To provide the basis for effort estimation. To provide an indication of the success from the business point of view.

20

2.3.2 Application Authoring And Design Tool :-

Suggested measure Structuring effort

Description Time to structure Web App and/or device architecture.

Interlinking effort Interfacing planning

Time to interlink pages to build the Apps. Time taken to plan Web Application Interface.

Interface building

Time

taken

to

implement

Web

Application Link-testing effort . Media-testing effort

interface.

Time taken to test all links in Web Application Time taken to test all media in Web Application.

Total effort

Structuring effort + Interlinking effort + Interface Planning + Interface Building

21

PAGE AUTHORING

Text effort

Time taken to author or reuse text in Page.

Page-linking effort

Time taken to author links in page. Time taken to structure page.

Total page effort

Text effort + Page-linking effort + Page structuring effort

MEDIA AUTHORING

Media Effort files. Media-digitizing effect Total Media Effort PROGRAM AUTHORING Programming effort

Time taken to author or re-use media Time taken to digitize media. Media Effort + Media-digitizing effort.

Time taken to author HTML, PHP or language implementations.

Re-use effort

Time to reuse / modify existing.

22

2.3.3 Calculation :-

Structuring effort Interfacing planning Interlinking effort Interface Building Link-testing effort Media-testing effort Total Effort Text Effort Page-linking effort Page structuring effort Total Page Effort Programming Effort Reuse effort

6-PDay 3-PDay 3-PDay 6-PDay 3-PDay 3-PDay (6+3+3+6+3+3)=24-PDay 6-PDay 4-PDay 6-PDay (6+4+6)days=16-PDay 40-PDay 10-PDay

Chapter 3

23

ANALAYSIS

24

3.1 E-R DIAGRAM

25

26

3.2 DATA FLOW DIAGRAM

3.2.1 Level 0

27

3.2.2 Level 1 3.2.2 1 Data Flow Diagram For User

28

3.2.3 Level 1 3.2.2 1 Data Flow Diagram For Admin

29

3.3 USE CASE DIAGRAM

3.3.1 Admin Use Case :Admi n can Add or Updat Admi e the n can record send s the mail to the Admi custo n can mer delete the record s.

Add/Update Records

Sending Mail

Admin

Delete Records

1.0 Use case Name

Admin 1.1 Basic Flow Admin starts this use case. It provides the capability for the admin to verify different procedures. He can perform various types of operations like edit, update, delete, sending the mail etc.

30

2.0 Flow of Events

2.1 Basic Flow Admin perform the four main activity like store the information of the customer, sending the mail to the customer, searching for perfect matching etc. Customer Information:The admin maintain the information about the customer in the database whenever he/she fill up the form. Sending the mail:The admin will send the email to the customer according to its requirement for male/female. He will also send the mail if any new thing is introduce in our system. Add/Update/Delete records:The admin can add, update or delete the records in the database. 2.2 Alternate Flows 2.2.1 Invalid Password An invalid password is entered. The user can re-enter a password or terminate the use case. 2.2.2 Invalid Username:

31

The system informs the user that the username is invalid. The user can re-enter the username or terminate the use case.

3.0 Special Requirements

There are no special requirements for this use case.

4.0 Preconditions
There are no special requirements for this use case.

5.0 Post Conditions

There are no post conditions.

6.0 Extension Points

There are no extension points.

32

3.3.2 User Use Case :User can regist er himse User lf/hers can elf in login the to the syste syste m User m can edit his/he r User profil e. can search the record for male/f emale .

Registration

Login

User

Edit Profile

Searching

1.0 Use case Name

User. 1.1 Brief Description

User can perform several operations on the system like registration, login. He or she can also edit his or her profile, searching facility is also there.

33

2.0 Flow of Events

2.1 Basic Flow User can perform mainly four activities. Registration:Before using this system the user must have to register in the system. He have to fill up the form and enter his/her profile in the database. Login:The existing users are giving his/her userid & password to access their accounts. If they are successfully login then they can edit or update their accounts. Edit profile:The user can also edit his/her personal profile in the system but first he/she have to login in the system. 2.2 Alternate Flows 2.2.1 Invalid Password An invalid password is entered. The user can re-enter a password or terminate the use case.

34

2.2.2 Invalid Username: The system informs the user that the username is invalid. The user can re-enter the username or terminate the use case.

3.0 Special Requirements

The user must be first login to access his accounts.

4.0 Preconditions
The user must be first login to access his accounts.

5.0 Post Conditions

There are no post conditions.

6.0 Extension Points

There are no extension points.

35

3.4 SEQUENCE DIAGRAM

36

37

38

3.5 ACTIVITY DIAGRAM

I/P Validation

39

Display Records

40

Search Records

Add Records

41

Update Record

42

3.6 CLASS DIAGRAM (1) Admin class diagram:-

43

(2) User Class Diagram

44

(3) Login Class Diagram

45

Chapter 4 DESIGN

46

4.1 SYSTEM REQUIREMENT SPECIFICATION

R1: Admin login page R.1.1 For report generate. Input: contain three type of report generation. 1.Report of paid member. 2.Report of free member. 3.Report of all member. R.1.2 For send or read mail. Input: Click on link of mail. 1.Send mail. 2.Read mail. R2: Login page R.2.1 For unregistered person, registration process Input: Flow: form Click on link for new registration. Control is redirected to registration form and after fill up the Click on link of report generate.

Output: Control is redirect to the screen of report generate, which

Output: Control is redirect to the screen of mail, which contain two link

Output: Registration is done for new user

47

and after click on the register button data of new user is stored into database and an email is sent to the user R.2.2 For registered person, login process Input: Flow: MemberId and password. If MemberId and Password correct then user will get his/her profile. user can do update profile, create album, change photo, hide profiletoure, apply for loan after correct login. R.2.3 If Password is forgotten than redirect to retrieve page Input: Click on link for forgotten password email id on that page. An email will be sent to user with memberid and password

Output: Get the screen of verify MemberId and Password.

Output: Get the screen for retrieving password and enter member id and

R.2.4 If session is expired than redirect to login page Input: Return URL

Output: Get Login Page R.2.5: For search partner Input: Click on search button.

Output: Control is redirect to the search screen.

48

R3: Directory Input: Click on directory button.

Output: Get the screen of directory. Flow: Select category and city so user can search address, for different type of category like hotels, caters, jewelry shop, beauticians, in different city if matched with database, if not matched than user gets matched not found screen.

R4: Quick Tour Input: Click on link of quick tour.

Output: Control is redirect to the screen of quick tour.

49

4.2 DATA MODELING

4.2.1 Data Dictionary

Register:

50

Name Memberid Membershiptype Domain Fname Lname Age Agemonth Agedate Ageyear Gender Maritalstatus Children Childrenstatus Religion Country City Employee Email Password1 Height Weight Bodytype Complexion Physicalstatus Bloodgroup Education Occupation Income Eatinghabits Smoke Drink Mothertongue Cast Subcast Gothra Star Raasi Horoscope Manglik Residentstate Residentcity Address Countrycode Areacode Phoneno Mobileno Aboutmyself Familyvalue Familystatus Familytype Fatheroccupation Motheroccupation Familyorigin

Null ? No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Type Int Text Text Nvarchar(50) Nvarchar(50) Int Text Int Int Text Text Int Text Text Text Text Text Nvarchar(50) Varchar(50) Int Int Text Text Text Text Text Text Numeric(18,2) Text Text Text Text Text Nvarchar(50) Nvarchar(50) Text Text Text Text Text Text Nvarchar(MAX) Nvarchr(50) Nvarchr(50) Nvarchr(50) Nvarchr(50) Nvarchr(MAX) Text Text Text Text Text Nvarchar(50)

Description Primary key Paid or free member Domain of user User name Last name of user Age Month of birth Date of birth Date of year Male or female Married or not Have children or not Children living with his/her or not Religion of user Country of user City of user Government or private employee Emailid Password Height in cm Weight in k.g Type of body(average,heavy,slim) Complexion(fair,very fair,dark) Normal or physically challenged Bloodgroup Education Profession of user Annual income Vegetarian or not Smokes or not Drink or not Mothertongue Cast Subcast Gothra Horoscope information Horoscope information Horoscope information Horoscope information State of resident City of resident Living address Phone Code of living country Area code Landline Contact number Mobile number About user Familyvalue(orthodox,traditional,moderate,liberal) Status of family(middle,upper,rich) Type of family(joint,nuclear,other) 51 Profession of father Profession of mother Origin of family

Success_Story: Name Female Male Id Email Story Loan Name Fullname Dateofmonth Dateofday Dateofyear Landlineno1 Landlineno2 Mobileno Emailid Needforloan Loanamount City Employeetype Organization Occupation Income MemberId No No No No No No No No No No No No No No No No Null? Type Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Nvarchar(50) Description Name of User Month Date Year Contact Number1 Contact Number2 Mobile Number Email Id Reason for loan Amount City Type of Profession Name of Organization Occupation Annual Income Primary Key No No No No No Null? Type Nvarchar(50) Nvarchar(50) Int Nvarchar(50) Nvarchar(MAX) Description Female Male Primary Key EmailID Success Story

Msg_Express_Interest: Name Msgfrom Msgto Msg No No No Null? Type Int Int Nvarchar(MAX) Description Received Messages Sent Messages Messages

52

Msg_Personal_Paid:

Name Msgfrom Msgto Msg No No No

Null?

Type Int Int Nvarchar(MAX)

Description Received Messages Sent Messages Messages

53

4.3 TABLE RELETIONSHIP

54

4.4 FRONT END INTERFACE

In front end interface I have first design the interface and after complete designing have implemented it using ASP . Here in user interface main two users are there, administrator and normal user. Administrator has authority to generate report, delete profile, update information for directory. And a normal user can search partner, registration, profile management. Admin Login Page at run time: This is the admin login page. After successfully login user can authenticate to system. Admin can generate report for all member, paid member, free member. Also update information for directory, delete profile of user.

55

List of all members :

56

CONVERTING FREE MEMBERS TO PAID MEMBERS :

57

Site statistics

58

Update Information Page For Directory at run time: This is the update information page for directory. After successfully login of admin it can authenticate to system. Only Admin can update information for directory. For that admin have to fill-up information like category, city, category name, phone no, address.

59

Update Done Page For Directory at run time: This is the update done page for directory.

60

Edit, Delete profile page at run time: This is the edit, delete profile page. After successfully login of admin it can authenticate to system. Only Admin can edit, delete profile of registered user. Admin have to click on delete link for delete profile of registered user. Admin can see information like id, user name, emailid, password, of registered user.

61

Delete Profile Entry By Admin at run time:

After successfully login of admin it can authenticate to system. Only Admin can edit, delete profile of registered user. Admin have to click on delete link for delete profile of registered user.

62

Login Page at run time: Any user who wants to use the functionality of Matrimonial Web Application through this system, he has to logs into via the given page. Any user whether the administrator or the normal user, he has to login first and get authenticate. Only those users can enter in this system which is created by the administrator. If user are not registered then it can do his/her registration by clicking on new registration link button. User can go to other page like loan, search, quick tour, directory just click on the link button of respective page shown at side bar.

63

64

First Registration Page At Run Time: This is the first registration page. It provides facility to user for fill-up his/her personal information. User can see the success story of user who met by this web site.

65

66

Second Registration Page At Run Time: This is the second registration page. It provides facility to user for fill-up his/her physical attributes information. User can see the success story of user who met by this web site.

67

Third Registration Page At Run Time: This is the third registration page. It provides facility to user for fill-up his/her sociooccupational information. User can see the success story of user who met by this web site.

Fourth Registration Page At Run Time:

68

This is the fourth registration page. It provides facility to user for fill-up his/her home truths information. User can see the success story of user who met by this web site.

Fifth Registration Page At Run Time:

69

This is the fifth registration page. It provides facility to user for fill-up his/her family details information.

Sixth Registration Page At Run Time:

70

This is the sixth registration page. It provides facility to user for fill-up his/her hobbies and interests information.

71

72

Seven Registration Page At Run Time: This is the seventh registration page. It provides facility to user for fill-up his/her partner preference information.

73

74

Congratulation Page At Run Time: This is the congratulation page. User can get this page after complete fill-up first three registration form. User can see his/her memberid on this page. If user want to complete his/her profile now the user need to click on complete your profile now link. If user want complete his/her profile later then user need to click on complete your profile later link.

75

Profile Page At Run Time: This is a user Profile form where user can manage his profile and it contains various links like for creating album ,image upload, personal messages ,express interest, delete photo.

76

User Detail Profile page At Run Time: This is a user details Profile page form where user can manage his profile this is done after successfully login of user. User can modify information about his/her personal details, physical attributes, socio-occupational information, home truths, contact details, family information, primary information, social information, education, location

77

78

Image Upload page At Run Time: This is image upload page form where user can change photo of profile. this is done after successfully login of user.

79

Result Page Of Image Upload At Run Time: This is result page of image upload .

Create Album Page At Run Time: 80

This is page for create album. This is done after successfully login of user. User can create album for user have to need to click on link of create album. User can add up to five photo in his/her album.

Change Password at run time

81

Express Interest Page At Run Time:

82

This is the express interest page. Here after searching the profile user can send a express interest to a profile of his/her liking .The messages here will be pre-defined here . .

83

Personal Message

84

Personal Message And Express Interest Page At Run Time: Here user can see the messages he has sent to other members and received from the other members.

85

Search Option Page At Run Time: This is the search option page. It provides facility to user to search about partner. This page contain five type link for search, like quick search, advance search, search by id, search by profession, search by location.

86

Quick Search Page At Run Time: This is the quick search page. It provides facility to user to quick search about partner. For quick search about partner user have to fill-up information like age range, domain, gender, religion, of search partner .

87

Quick Search Result Page At Run Time: This is the quick search result page. It provides information like memberid, name, gender of partner. if user want to know more about search partner then user need to click on details button.

88

Details Of Searched Partner Page At Run Time: This is the details of searched partner page. It provides details searched partner. Only paid member can see this information. information about

89

90

Advance Search Page At Run Time: This is the advance search page. It provides facility to user to advance search about partner. For advanc search about partner user have to fill-up information like age range, domain, gender, interest, height, mother tongue, religion, cast, manglik, eating habit, education, citizen ship,country, resident status of search partner .

91

Advance Search Result Page At Run Time: This is the advance search result page. It provides information like memberid, name, gender of partner. if user want to know more about search partner then user need to click on details button

92

Search By Id Page With Result At Run Time: This is the search by id page. Here user enter member id and click on search button it will get information like memberid, name, gender of partner. if user want to know more about search partner then user need to click on view details link.

93

Search By Location Page At Run Time: This is the search by loacation page. It provides facility to user to search about partner by location wise. For search by location about partner user have to fill-up information like age range, maritalstatus, gender, country, city of search partner .

94

Search By Location Result Page At Run Time: This is the search by location result page. It provides information like memberid, name, gender of searched partner. if user want to know more about search partner then user need to click on details button

95

Search By Profession Page At Run Time: This is the search by profession page. It provides facility to user to search about partner by profession wise. For search by profession about partner user have to fill-up information like age range, marital status, gender, country, education, profession of search partner .

96

Quick Tour Page At Run Time: 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.

97

Wedding Directory Page At Run Time: This is a module that contains information like name, address and contact number for apparels, astrologist, beauticians, caterers, entertainment, florists, gifts, hotels, jewelers, tours and travels.

98

Result Page At Run Time:

99

Paid Membership form :

100

Marriage Loan

101

4.5 APPLICATION NAVIGATION

102

103

104

105

106

107

108

109

Chapter 5 IMPLEMENTATION

110

IMPLEMENTATION PLANNING.

5.1 IMPLEMENTATION ENVIRONMENT

111

5.2 SECURITY FEATURE

In this application all data transaction is doing under HTTP secure protocol In this application Login id and password verification is required. User should Login with authenticated memberid and password as well as user should verified his/her password. Failure to do this will not allow to user to access the application

5.3 CODING STANDARD

Checks for Normal Working a. Does your screen save data in the database? b. Does your screen save correct data in the database? c. In update does your screen load correct data? d. Fields are showing the data in correct format? [USE REGULAR EXPRESSIONS DEFINED AS PER TESTING STANDARDS] 1. Date a) Should always be selectable in addition to manual entry 2. Integer 3. Float, Double 4. Percentage 5. For web site entry field, populate by default with value (http://www.) 6. All email entry fields should be multiple email addresses enabled

To Be Checked?

112

e. Will your screen crash if wrong data type is entered? f. Does your screen sequence is working? g. If the logic updated / approved?

a. b. c. d. e. f.

Basic Validations Maximum allowed length property is set? Validation for Required field is done? Validation for Integer, Float, Double, Date, Time is done? Spell check Type Check / Type Safety Boundary Value Analysis (for highest order value and lowest

order value) g. Date Format (dates must be converted from SQL only) NEVER DISPLAY 12:00:00 AM h. Is page validation enabled? [must be done for user entry fields]

User Interface Checks a. Caption of each label is correct, do you have read caption twice? Captions must not be in bold. b. Tab sequence is set correctly? i. On load, focus should go to first data entry field. Only in Search focus should go to first search result on search , on load, set focus to fist search field c. Panel heading are right? Make sure you have used CSS class for DIV formatting d. Main heading of the screen is Right? Look at application bar in browser window. e. Menu heading is correct? f. If the screen is part of a screen sequence / wizard than:

To Be Checked?

113

User Interface Checks 1. Have you given Steps as heading s to make sequence understood? 2. Next / Back Button should be at one fixed location 3. Wizard should have consistent size for all steps. 4. Make sure all elements in all wizard steps are consistent. a) For example, if you are using left side part of data entry fields, then align same width for it on all wizard steps (60% for data entry & 40% for search of list panel) g. Fields are having width as per their length in the database? h. Fields are well aligned? i. Always follow the rule of left to right with increasing indent. ii. Images should be well aligned and text should be centre aligned to image, NOT TOP OF BOTTOM. iii. IF YOU HAVE MULTIPLE lines of text to be aligned, 1. User should not move his mouse all over screen to click one button to another i. Is the screen look good and well formatted? j. Default values are given as per requirement? i. Highlight compulsory fields with * and put an Note on screen in light grey color that * Indicates Compulsory Fields ii. All static information fields must be in specific color variants

To Be Checked?

114

User Interface Checks iii. ENTER KEY SHOULD PERFORM CORE SCREEN OPERATION ON EACH SCREEN. IT SHOULD BE DEFAULT BUTTON, 1. After save / update , if you are focusing back to same screen, in case you retain same record, move focus to first editable field on screen or for new records, move focus to first field as well. iv. Images / logos should have tooltip + alternate text v. Each grid should have paging size between [`10-25] per page + exception handling code in bind for no page scenario vi. Sorting should be enabled for all columns in grid vii. SCREENS SHOULD BE CENTRE ALIGNED to eliminate screen size issues viii. Width of screen should be maximum to 980 PX ix. TARGET 1024 X 768 resolution x. USE HTML formatting in alert boxes when you want to display confirmation messages xi. Sequence of Fields should be pleasing to eye [do not make your screen look like khichdi of controls) give user some breathing space

To Be Checked?

115

User Interface Checks xii. User minimum colors. xiii. Help Button should be at top right corner of the form (not application) and screen # + Type : <application / paint> should be added to each screen xiv. PROVIDE HELP WITH EXAMPLE, remain objective in help text. xv. User focus will go from left to right, use left section of your page for more important information. xvi. Wherever you use images, use legends on screen. xvii. Each dropdown should be default sorted xviii. Each grid should be sorted by default [as per field availability] xix. If you happen to open something in new window, use an image to indicate that. xx. Search result should be consistent xxi. PAGE SHOULD NEVER SCROLL HORIZONTALLYNEVER EVER xxii. USE ARIAL / VERDANA FONT xxiii. Warning messages should be informative. xxiv. Each page should have breadcrumb [hyperlink enabled]

To Be Checked?

116

User Interface Checks xxv. If the requirement is Data should be shown in Capital, then adequate measures are done? xxvi. Show results found on each search screen 1. If there are no results, show 0 results found, and set focus to first field of data entry on the screen. Even if you cannot control back button behavior for now, DO NOT ENTICE USER TO USE BACK BUTTON, provide back link on screen itself where required. CLOSE APPLICATION IF BACK BUTTON IS PRESSED ON ANY OF THE SCREENS. Also, disable submit button after it is clicked once. POPULATE FIELDS WITH DEFAULT VALUES [for example, First Name field data entry should read, Enter First Name and as soon as focus is there, remove that text]

To Be Checked?

117

5.4 STORED PROCEDURE

After creating database I have created stored procedure for select,insert,update and delete.With the help of the stored procedure access should be fast and we dont have need to compile it.we can run it directly.I have created stored procedure inserting all data of the table with value type and than I have created query for select,update,delete,insert in their procedure.

5.5 DATA ACCESS LAYER

Data Access Layer: When working with data one option is to embed the data-specific logic directly into the presentation layer. This may take the form of writing ADO.NET code in the ASP.NET page's code portion or using the SqlDataSource control from the markup portion. creating a connection to the database, issuing SELECT, INSERT, UPDATE, and DELETE commands, and so on should be located in the DAL.The presentation layer should not contain any references to such data access code, but should instead make calls into the DAL for any and all data requests.I have created data access layer for Fill() and Get() methods.Get is done by two ways. GetStory(),which will return information about the success story or user who met by this site. GetMessage(), which will return information about a message for particular type of membership.. These methods, when invoked, will connect to the database, issue the appropriate query, and return the results. These methods could simply return a DataSet or DataReader populated by the database query, but ideally these results should be returned using strongly-typed objects.

118

In strongly-typed DataTable, will have each of its columns implemented as properties, resulting in code that looks like: DataTable.Rows[index].columnName.Figure illustrates the workflow between the different layers of an application that uses Typed DataSets.

To retrieve the data to populate the DataTable, I used a TableAdapter class, which functions as my Data Access Layer. For our story DataTable, the TableAdapter is containing the methods Getstory(), Getstorybyid(memberid), and so on that I can invoke from the presentation layer. The DataTable's role is to serve as the strongly-typed objects used to pass data between the layers. I have a Typed DataSet with a single DataTable (message) and a strongly-typed DataAdapter class (FmsgTableAdapter,PmsgTableAdpter) with a GetMessage() method. In my application I have used pattern for inserting, updating, and deleting data, this pattern involves creating methods that, when invoked, issue an INSERT, UPDATE, or DELETE command to the database that operates on a single database record. Such methods are typically passed in a series of scalar values (integers, strings, Booleans, DateTimes, and so on) that correspond to the values to insert, update, or delete. The patterns use the TableAdapter's InsertCommand, UpdateCommand, and DeleteCommand properties to issue their INSERT, UPDATE, and DELETE commands to the database.

119

Figure Each Insert, Update, and Delete Request Is Sent to the Database Immediately

5.6 BUSINESS LOGIC LAYER

The DAL cleanly separates the data access details from the presentation layer, it does not enforce any business rules that may apply. So I have to Create Business Logic Layer (BLL). these business rules into a Business Logic Layer (BLL) that serves as an intermediary for data exchange between the presentation layer and the DAL.In BLL the rules like value cant be null, some field changed only by admin and so on BLL will be composed of classes, one for each TableAdapter in the DAL; each of these BLL classes will have methods for retrieving, inserting, updating, and deleting from the respective TableAdapter in the DAL, applying the appropriate business rules. The BLL classes can accessed declaratively (as can the Typed DataSet) by using the ObjectDataSource. I have created Dataadapter object than creating methods for Adddata(),Updatedata(),Deletedata().In this method creating Objects for dataset and

120

datarow and with the help of the datarow object getting/updating/deleting data and for that I have used Try and Catch method.

121

Chapter 6 TESTING

122

6.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. 1.1.1 Test plan identifier 1.1.2 References 1.1.3 Introduction 1.1.4 Test items (functions) 1.1.5 Application risk issues. 1.1.6 Features to be tested 1.1.7 Features not to be tested 1.1.8 Approach (strategy) 1.1.9 Item pass/fail criteria 1.1.10 Entry & exit criteria 1.1.11 Suspension criteria & resumption requirements 1.1.12 Test deliverables 1.1.13 Remaining test tasks 1.1.14 Environmental needs 1.1.15 Staffing and training needs 1.1.16 Responsibilities 1.1.17 Planning risks and contingencies 1.1.18 Approvals 1.1.19 Glossary

123

6.2 TESTING STRATEGY

Test More and Test Frequent is organization s 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.

124

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.

125

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 enduser

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.

126

Client layer-user interface

Server layer- WebApp

Server layerData transformation

Server layer - data Management

Database layer data access

sd 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 extract or formats user data.

127

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 logous to unit testing For example, 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.

128

Links: Each link is tested to ensure that the proper content object or

Function is reached. The Web engineer builds a list of all links associated with interface layout. and then executes each individually. 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 serverAppropriate 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 contain 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:-

129

Test conforms to a checklist of functionality and features that are defined by the interface mechanism. Boundary test minimum and maximum number of item 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 mechanism easy to understand and use?

LayoutAre navigation mechanism, content and function place in a manner that allows the user to find them quickly? ReadabilityIs text well written and under stable?

130

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 AccessibilityIs the Web application accessible to people who have Disabilities? manner?

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.

131

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

132

WHITE-BOX TESTING: White-box testing some times 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 so 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 on their true and false side. A11 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 blackbox 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 133

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 was Open during the previous build, but marked as Fixed, Needs Re-Testing for the current build under test, will need to be regressed, or retested. 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.

134

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 Spec and Design Spec 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.

135

6.4 TEST CASES

6.4.1 Test Cases Test Case No. Test Case Action 1 Checks system behavior when credentials provided by admin are correct. Click on allmember link by admin. Result page which contain information about only all member. Pass

Input Expected output Pass/Fail

136

137

6.4.2 Test Cases Test Case No. Test Case Action 2 Checks system behavior when credentials provided by admin are correct. Click on paidmember link by admin. Result page which contain information about only paid member. Pass

Input Expected output Pass/Fail

138

6.4.3 Test Cases Test Case No. Test Case Action 3 Checks system behavior when credentials provided by admin are correct. Click on statistic link by admin. Result page which contain total member, total male member, total female member, free member, paid member. Pass

Input Expected output

Pass/Fail

139

140

6.4.4

Test Cases 4 Checks system behavior when credentials provided by the user are correct. In Login page user enter correct credentials in respected text fields. User profile page. Pass

Test Case No. Test Case Action

Input Expected output Pass/Fail

141

142

6.4.5

Test Cases 5 Checks system behavior when credentials provided by the user are not correct. In Login page user enters incorrect credentials in respected text fields. Login page with message saying that credentials are incorrect.. Pass

Test Case No. Test Case Action

Input Expected output Pass/Fail

143

6.4.6 Test Cases Test Case No. Test Case Action 6 Checks system behavior when credentials provided by user the are not correct. If user enters in-correct credentials in respected text fields of register pages. Same register page with alert message Pass

Input Expected output Pass/Fail

144

6.4.7 Test Cases Test Case No. Test Case Action 7 Checks system behavior when credentials provided by the are correct. Click on details button for see more information about user . Redirect to the hide profile error message page if membership type of logged user is free type. Pass

Input Expected output

Pass/Fail

6.4.8 Test Cases

145

Test Case No. Test Case Action

8 Checks system behavior when credentials provided by user are correct. If user click on profile details button in result page of search. Redirect to the page which contain message like prolix has been hidden by profile owner. Pass

Input Expected output

Pass/Fail

146

6.4.9 Test Cases Test Case No. Test Case Action 9 Checks system behavior when credentials provided by user are incorrect. User enters incorrect credentials in respected text fields of EmailId. Register page with message saying that credentials are incorrect.. Pass

Input Expected output Pass/Fail

6.4.10 Test Cases

147

Test Case No. Test Case Action

10 Checks system behavior when credentials provided by the user are correct. In quick search page user enters required information for quick search. Display result according to match with information given by user. Pass

Input Expected output Pass/Fail

6.4.11 Test Cases Test Case No. Test Case Action 20 Checks system behavior when credentials provided by the user are correct. In wedding directory page user select correct category and city. Display result according to match with information given by user. Pass

Input Expected output Pass/Fail

148

149

Chapter 7 CONCLUSION AND FUTURE EXTENSION

150

7.1 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 will provide platform to a lot of Bride/Groom for finding perfect match. There are different sectors like Registration, Partener , 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 fulfil their required criteria. It helps the user by providing profiles of perspective Bride or Groom and other information regarding them online. Matrimonial web application provide 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 provide 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.

7.2 FUTURE EXTENSIONS

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.

151

BIBLIOGRAPHY

Books
ASP.NET(Black Book). Professional ASP.NET(Wrox Publication). C# Vijaymukhi. ASP.NET Complete Reference. Software engineering Concepts By Roger S.Presman UML IN A NUTSHELL By Alhir Fundamentals of Software Engineering By Rajib Mall SQL Server 2005 (Wrox Publication).

Web Sites www.bharatmatrimonial.com www.shadi.com www.jeevansathi.com www.patelvivah.com www.simplymary.com

152