Web Forum - class of applications for communication site visitors. Planning of such database that to contain all information about an user is the name, last name, address, number of reports and their content, information about an user and his friends.
Краткое сожержание материала:

Размещено на

National Research University

Higher School of Economics

Perm Branch

Faculty Business Informatics

Department Information Technologies in Business

Research Proposal

Creating a Data Mart for an Online E-Book Store

Student Linar_R._Ibragimov

Group Bi-10-2

Perm 2013

1. Introduction

Web Forum - class of applications for communication site visitors. Forum offers a set of topics for discussion. his job is to create users in those sections and the subsequent discussion within these themes. Individual subject, in fact, is a thematic guestbook. A common hierarchy Forum is Sections > topics > posts. Typically, messages carry information "author - Topic - the content - the date / time." Message and all replies to it forms a "branch" or "topic"

The aim of this work was to design an example of such a database. All information about user, such as name, surname, address, post address, number of messages and their content, as well as information about the user and his friends.

2. Description of the subject area

2.1 A summary of the forum

database web forum

This database stores information about users of the forum. It will be used for viewing all user actions from the time of its registration. Also, you can add a user.

This database contains the basic elements of the Forum such as users, themes, messages, and other. A full list is shown in Table of objects

Table of objects

№	Object	Description
1	User	Because forums are designed for communication between people, "user" is the key object database. He has a connection with almost all the other objects. Table "user" contains profile information about the users of the Forum, from the name, ending with the current status.
2	User's friends	Object "Friend" is closely connected to the "user"..
3	Violations of user	Sometimes users may not comply with the rules of the forum so there is a system of penalties. This object is created so that the administrator could know the "history of violations of the user"
4	User's online history	Allows you to view user's online history
5	Topics	Users create "Theme" for what to discuss any particular topic or news, in a specially prepared virtual space.
6	Messages	Message this text that contains certain meaning that the user would like to pass other forum users.

2.2 Description directories

The necessary directories:

1) Countries: Information about the countries where users live..

2) Status: Information of the current status of the user.

3. Planning of database

The database should include the following sections:

· Information about user

· Information about topics

· Information about messages

· Information about violations

· Information about user's online history

· Information about User's friends

The database will have the following attributes:

· Information about user

- «ID» - a unique key that identifies the corresponding object.

- «Name», «Nickname» - attributes determine personality of the user in real life and in the forum.

- «Adress», «e-mail» - contact Information.

- «Pass» - personal data with which the user logs in to the forum.

- «Country», «Status», «Regestration date» - characteristics of the user.

· Information about topics

- «ID» - a unique key that identifies the corresponding object.

- «Topic name» - topic name

- « The author » - the author who created the topic.

- «Number of replies», « Time», «Open/Closed» - characteristics of Topics.

· Information about messages

- «ID» - a unique key that identifies the corresponding object.

- « The author » - the author who created the message.

- «Тема» - topic, where this message is.

- «Content" - the text field that contains the message text.

- «Time» - time when the message was written.

· Information about violations

- «User" - the user who made the violations.

- «Topic" - Topic where a punishment has occurred.

- «Description violations " - an explanation of issue of violations.

- «Content" - the text field that contains the message text.

· Information about user's online history

- «User code» - a unique key that identifies the corresponding object.

- «Start Time", "End Time" - characterize the the length of the sessions.

· Information about User's friends

- «Man" - a unique key that identifies the corresponding object.

- «Friend» - nickname by another user

3.1 The transition to the first normal form

Pic 1

For the transition to the first normal form we should ensure that on the intersection of rows and columns have only one meaning. We use the method of exclusion repeating groups: fill the empty cells of the table duplicates the relevant information about the recurring groups and define the primary key of the result.

3.2 The transition to the second normal form

Suppose the following links::

Messages and topics on the forum a lot, but each message or theme have their only carrier, so communication will be 1: N. One at the the user code, N at a field and the author's name in other tables.

Each message belongs to a certain topic. The punishment occurs in one of the forum. Link will be 1: N. One at the Topics, N at the fields with the code Topics in other tables..

3.3 The transition to the second normal form

In connection, the following functional dependencies: Violations > Theme, Theme > Message > Message violation.

Dependence Violation > Message is transitive, therefore, the link is not in 3NF.

So, the table is divided into two tables. violations: Theme and Subject: Message.

Pic 2

Thus we have the final form of the scheme:

Pic 3

4. Application development

4.1 Description of tables, fields, input conditions

· Table users:

- ID-key field, the counter

- name - type string

- country - the type of country that refers to the reference countries. Not a required field.

- Nickname - type string.

- Password - type string.

- E-mail - type string.

- date - the type of date.

- Address - type string, not required.

- Status - refers to the directory. Not a required field.

· Table of Topics:

- ID - key field meter.

- name - type string.

- Author - field to link the user to the table, the type of user.

- The number of responses - the type integer.

- open / closed - type string.

- Time - the type of date..

· Table of Messages

- ID - key field meter.

- topic - Type topic.