Dating website Design

1 Introduction

The emergence of dating sites has provided a great convenience for people to expand their circle of friends. People through the Internet not only have their own circle of friends, but also to save the time and effort to participate in social activities. Now many friends at home and abroad, although it can meet the needs of people to make friends, but most of these sites do not guarantee the confidentiality of user information, such as any users browsing to these sites can browse the user information on this site, comments on its information. This approach makes the network security of registered users of these sites less secure. How to automatically filter the comments from non-friends, how to ensure that the privacy of their own information will be a problem for many users to consider.

This article discusses the dating site is based on the user needs of the design. It differs from other dating sites in that it: non-members of this website can not browse the information of members of the website, temporary members can only get some of the basic functions of the site, such as only to browse other members of the information, can manage personal information, personal homepage, publish a personal log, check friends invitation Records, manage albums, However, it is not allowed to add a friend request to other members, and not to leave a message for other member information. Temporary members must pay a certain fee to the webmaster to upgrade to full membership, only to enjoy the site of all services. On the other hand, non-web members can not use the site, to ensure the confidentiality of the site's user information. 2 System Analysis 2.1 Requirements Analysis

This article discusses the design of the dating site is to: on the one hand can facilitate the user to expand their circle of friends, on the other hand can guarantee the security of private information users. To design an efficient dating system, you must consider the problem with the viewpoint of systems engineering. In the system analysis stage, both the designer and the user should work closely together to collect and analyze the content of the information in the data management and the user's request for processing. According to user needs, the system introduced in this paper divides the website design into two modules: User module and backstage manager, including user module, member login, member registration, personal portal, personal log management, personal photo album management, personal file management, making friends management (view friends record, find, add friends). Background management functions include: admin login, user audit management, user personal portal small function parts management.

The system developed using Microsoft's Windows 2003 as a server, using SQL Server 2005 as a database, using IIS as an Internet server, the foreground using ASP.net 3.5来 development, choose C # as the development language, development tools using visual Studio.NET 2008, the website design uses three layer architecture to develop. 2.2 System Architecture Analysis

The design of the Web site is based on B/s three-tier architecture, that is, the presentation layer, the business layer, the data layer.

The main four sections are as follows:

1 database project file: mainly contains the data tables, views and stored procedures used by the system. The database used is SQL Server 2005.

2 Business Project file: The project folder contains multiple class libraries, some class libraries contain entity classes, data access classes and multiple business logic classes, and some class libraries contain only business processing classes. Entity classes provide a uniform interface for accessing fields in a datasheet; Data access classes are used to manipulate entity classes, mainly including statements of SQL statements and basic operations of the database, business logic classes handle the business logic of the entire system, and each class contains the logical operational methods required by business entities, such as adding friends, background auditing , access to friend information and so on.

3 Web project files: For the interface display, responsible for direct interaction with the user, including all users and the system's interactive experience, that is, the system's. aspx pages, user controls, topics, and other files.

4 Common project files: mainly encapsulates some of the public classes used in the system, common control settings, transaction processing, design patterns, webpart settings, for Business processing classes and page display class to provide data processing interface.

The main operational processes in the three-tier architecture are: The user transmits the request to the business logic layer through the presentation layer, the business logic layer completes the relevant business rules and logic, and accesses the database through the data access layer to obtain the data, then returns in reverse order and displays the data in the presentation layer. function Analysis of main module of 2.3 system

It has been mentioned in the system requirement analysis that the design of this system is divided into two parts: User and backstage management. These two modules are made up of many sub modules.

User module mainly includes: User login, user registration, personal homepage, personal log management, buddy management. The individuals are mainly composed of several WebPart, including personal log, personal information management, Personal homepage widget Add, personal homepage visit rate, Personal homepage message, personal latest events, etc. Personal log management includes: Create personal log, edit personal log, personal log list view, delete personal log. Friend management includes: Invite friends, add friends, make Friends record management (you can agree or reject friends invitations, you can see the Friend list).

Background management includes: admin login, personal homepage small function parts Management, website homepage information release, registered user information audit.

Non-website members must register before entering this website, in which registration can be completed in the following three ways. The first way is, directly login to the home page, click on registration, according to the needs of the site to fill out personal information, through the webmaster audit to become a temporary member; The second way is, there is a formal member of the invitation, the user directly click on the invitation mailbox link, enter the registration page, At this time, the user's user name (that is, email address) has been automatically filled in, registered users fill out other registration information, after the webmaster audit to become a full member; The third way is to apply for the user to obtain a registration code by paying, according to the registration process to fill in the registration information, After the webmaster audit to become a full member.

After the official login to the system can be based on the name, hobby, graduation school, work industry, and so on to find the user, browse the user's basic information, if the user to meet their needs can send friends invitation. If the official member wants to invite the non-this website user to become the website member, may send the mail to it, invites it to join. All Web site members can view their own dating records in this system, including Friends request information, non-friend request plus friend information and personal friends list. design and implementation of main module of 3 system

The main function of the system is to provide registered user role management and find add friends, in the implementation of the data and control binding to display data, adopted. NET to implement the operation of the database in the LINQ technology. The following focuses on the design and implementation of the main module. 3.1 Friend Management module

1 to see friends record: You can see who add their own friends, you can choose to refuse or agree according to demand.

2 Find Add Friends: Users can be based on the name, hobby, graduation school, work industry, and so on to find the registered members of the system, browse the basic information of the member, and then according to their own needs can send invitations to the member, and wait for the results of the request. Full members can also invite non-members of this web site to join the system, the invited users fill out the registration information, through the background after the audit to become a temporary member of the website, both sides appear in each other's friends list, temporary members can be upgraded to become a full member. Members can view their own dating records and may choose to agree or reject other user requests. But temporary members can only find friends, view other user information, can agree or reject other members of the invitation, but can not add friends. When you click "Find", it is to send a request to the server, by reading the parameters of the Request object we judge, the implementation is through a number of conditional judgment statements to achieve. The access to the database, the system utilizes the IntelliSense function of LINQ, makes the code implementation become simpler.

When you do a buddy search, the site runs a picture like Figure 4.

Find the code to use the LINQ operations database in the buddy implementation as follows:

foreach (var info in baseinfo)

{//Filter data, using LINQ IntelliSense to implement

Ienumerablevuser = from detail in vuserdetails

where detail. id.tostring () = = info. Account.tostring ()

by detail. Enterdutydate Descending Select detail;

Vuserdetailslist = Ienumerablevuser.tolist ();

3.2 Register User information Audit module

The administrator manages all the application information in the background and verifies the registration information, and processes such information according to the audit results. The status of all applicants is pending approval, after the background audit, by the administrator to send an acceptance or rejection of the mail to the applicant's application mailbox, the mailbox is the user login to the system account, the application user login to their registered mailbox, click Activation can become a full member or temporary member.

Before the registration information is audited, the admin admin interface is shown in Figure 5:

After the audit to become a temporary membership code as follows:

To ensure the confidentiality of the code, we use letters to replace the variables in the source program implementation, each letter representing the meaning as shown in the code

public void Confirmregister (Guid id,bool Pass)

{

if (pass)

{//A represents the user information entity, B represents the membership management class, C invites the mail entity, D personal Homepage business logic class

A account = B.instance.getaccount (ID);

C Invitationemail = b.instance.getinvitationemailbyregisteraccount (ID);

if (null!= invitationemail)

{//e A WebPart Business processing class for your personal home page

Basicinfo basicinfo = D.instance.getbasicinfobyaccount (Invitationemail.account, "");

E.instance.saverelationship (ID, Basicinfo.account, friendsstatus.accept, "", "passive");

E.instance.saverelationship (Basicinfo.account,id,friendsstatus.accept, "", "Active");

if (account. Email.equals (Invitationemail.email))

{

Account. IsActive = true; B.instance.modifyaccount (account);

}

}

Assign roles, F for registered user registration codes

Role role = new role ();

List registerrecordlist = d.instance.getregisterrecordbyaccount (ID);

if (1 = registerrecordlist.count)

{

Registerrecordlist[0]. Codestatus = g.effective;

D.instance.modifyregisterrecord (Registerrecordlist[0]);

Role = B.instance.ensurerole (H.formal);

}

else {role = B.instance.ensurerole (h.temporary);}

Roleassign assign = new roleassign ();

Assign. Id = Guid.NewGuid (); Assign. Account = account. Id;

Assign. role = role. Id;

B.instance.addroleassign (assign);

If it's a buddy request, add a two-person buddy relationship.

B.instance.sendvalidationemail (account); Send Authentication Message

}

else {//delete user registration information

......;

Send reject mail, I for membership management logic class

I.instance.sendrejectnotice (ID, "rejectregisterapplication");

}

} 4 Closing remarks

The content of this paper is mainly related to the requirements of the dating site analysis, system architecture, and the main modules are analyzed and coded to achieve. This system mainly realizes the function is the website member may look for the friend, add friends, you can get the latest news of friends, published personal log, modify and improve personal information, webmaster can audit the application request, audit results can be successfully sent to the registered user's registered mailbox, but with the increasing demand of users, The function of the system still needs to be perfected continuously. The system needs to add the function for: the information sharing among members, the management of the Member friend Address Book, the information communication between the members.