B2C的电子商务网站【外文翻译】

外文翻译

原文

B2C E-COMMERCE WEBSITE

Material Sourse：University of Craiova Faculty of Mathematics and Computer Science Email: boboila@central.ucv.ro Author: Boboila Cristea

The World Wide Web represents a new frontier towards a global industry, leading the way for new businesses. Commerce now deals with a whole different concept: electronic commerce (e-commerce). This kind of commerce provides new means for a large variety of products to reach different markets across the world. This application was designed and implemented for a hypothetical firm called Oxygen, in order to supply a manageable website for online selling, thus reaching new customers in a whole new target market. The website has an appealing interface and allows clients from across the globe to view the company’s products and buy them using cash on delivery or a credit card. The application has an administration module, permitting the owner of the shop to easily add or delete items, and to review orders.

Keywords:E-Commerce;WorldWideWeb;Websites;ApacheHTTPServev;Databases

1 Introduction

The application is intended to provide an online shop for a hypothetical firm Oxygen. However, there is no restriction regarding the products sold. The owner has the possibility of adding anything he wants, from small objects, like pens, to large ones, like a LCD TV. The app administrator can insert or remove item categories. Each category may have other subcategories, thus the task of grouping the items becomes easier and well-structured. For this application I have used the Apache HTTP Server, MySQL for working with the database and PHP as the server side script in order to provide dynamic content (Welling & Thomson, 2001). MySQL is currently the most used DMBS (Database Management System) online, being very simple to use in terms of manipulating information onto a relational schema (Timofte, 2002).

2 Website Database 2.1 Database Diagram

The database is called “magazin” and consists of eight tables. We can observe in the next figure the database diagram.

2.2 Tables Description

Table users - this table contains information regarding a client that has registered into the system. It stores a unique username, a password for the account, a unique e-mail address and also the address of the client. The client has the facility of paying for an order with a credit card. This sort of information is also stored in this table (Macklup, 1991). Table recuperari - this table contains two fields. One field represents the e-mail address of a customer that had forgotten his/her password and the other a key generated by the application in order to check that the solicitant of the new password is indeed an actual client. This key will be sent to that e-mail address. If the client responds to the email with the key, the system will generate a password and send it to the user (Odlyzko, 2001).

Figure 1 Database Diagram

Table admin - we can observe in Figure 1 that there is only one field. The purpose of this table is to indicate which of the users from the table users has administration rights .An administrator can add/delete new items or view/accept/reject orders made by users.

Table produse_spec - this table contains product specifications for a product. Every product can have none or many specs, which are stored in this table.

Table comenzi - a user can place as many orders as he likes. An order is stored here, with info like the user who made it, the date of the order, the total price and payment option. The order has a status. When placed, a new order has the status “pending”. After it has been reviewed by the administrator it can have the status “approved” or “rejected” in which case we will store in this table the reason for the denial of the order, to later present it to the user.

Table categorii - in order for the shop to be well-structured, we have to organize the items into categories. Each category can have products or many subcategories with products.

Table comenzi_produse - this table stores information concerning to the product that correspond with a certain order (Roşu-Hamzescu, Mitu, 2001).

3 Structural Design

3.1 Website Module Interaction Diagram

The application has two main modules: the user interface module and the administration module. These modules depend on the existence of the database “magazin”. In Figure 2 we can observe the interaction between the modules, regarding the DB (Loshin & Vacca, 2004).

Figure 2: Module Interaction Diagram

3.2 User Interface Module Prospect

This module consists of many PHP modules (Năstase, Năstase, 2002). There

are a few modules that are stored in aseparate directory, INC. All off these are included in the rest of the interface. We will explain the modules first:

Module sus.php - this module is responsible for supplying the header for the other modules in the user interface. It displays the Oxygen logo and links to the contact and how to buy page.

Module jos.php - this module simply displays in all the modules the footer (the copyright to be more specific).

Module login.php - if the user inputs in the login form a correct combination of username and password, the login form is substituted with account options links (logout, order history, account details and to change password). This operation logs in the user into the system.

Module cosdecumparaturi.php - I implemented here a class that symbolizes a shopping cart. This class will be used to store information on the products that the customer wants to buy. It provides methods for adding, deleting and manipulating the quantity of a product. It will store data like the products ids, their price and quantities.

Module util.php - this module is the most important module of the application. It contains definitions of functions that fully interact with the DB. Functions for logging in, checking if a user is logged and logging out are implemented here. There are also all the functions needed to manipulate information from the database, including functions that are needed by the administration module.

The modules that deal with the actual user interface are stored in the root directory. Their functionality is based on the util.php and cosdecumparaturi.php modules. We will explain them next:

Module index.php - this module displays shopping cart overview with two buttons that can redirect to the shopping cart manipulation module and one that can empty the cart, the catalog that contains the main categories, a loginform or account options if the user is correctly logged into the system, and at last two buttons for creating a newuser and for retrieving a forgotten password. These are present in the rest of the modules, though there are some exceptions. As we will present other modules it will be specified if any of these aren’t the same.

Module logout.php - after a user is done with his actions, he can log out of the system using the logout link. Module catalog.php - when a user clicks on a main category he will be redirected to this catalog module. The category’s picture is shown. If the category contains products, they will be displayed along with a link to

the produs.php module and add to cart button; if there are subcategories they will be displayed along with the picture and number of products contained. A subcategory becomes a category when it is clicked.

Module produs.php - When a product link is clicked, this module is responsible to output the product information stored in the database and a button for adding the product into the shopping cart. Module cosulmeu.php - a user can modify the content of the basket. He can remove or change the quantities of a product. This page displays a schema for the operations needed to complete an order. The client can go back to shopping or he can continue the order process.

Module comanda.php - this is the second in the order process after viewing the cart items. This module is only accessible if the user has successfully logged in. If so, the shopping cart content is showed alongside with a button that links to the cart manipulation module, the address of delivery with a button that links to the account details manipulation module and a form for choosing the payment option.

Module plaseazacomanda.php - accessible only from the comanda.php module, this is responsible for adding a new order into the database, in compliance with the shopping cart content.

Module contulmeu.php - a client can modify his details here, for example if he wants to change the delivery address or to add a credit card. This is accessible only if the client has successfully logged in.

Module comenzi.php - a client can view the details of his order here. He can see the actual orders or the ones he has completed in the past. If an order is denied, he can see the reason here and try to remedy the problem. Further he can reconfirm the order using the module reconfirmare.php or cancel it using anuleaza.php, both of these being available through links. This is accessible only if the client has successfully logged in.

Module schimbaparola.php - a client can change his account password if he wishes. This is accessible only if the client has successfully logged in.

Module register.php - a new client can browse the catalog and add products to the shopping basket. If he wants to place the order but he doesn’t have an account he can click the link for creating one, thus leading to this module. There is a form that has to be completed with personal information, choosing a username and password and providing his email. Optionally he can add a credit card to his account for online purchasing.

3.3 Administration Module Prospect

The PHP modules needed for the administration are stored in a separate directory ADMIN. The administrator can reach this module simply by specifying the path to this directory in the URL (ex.: oxygen.ro/admin). Many of the modules just perform an action to update the database and then return to modules that also display information (Kleinberg & Lawrence, 2001).

Module index.php - this module displays a login form. If the user has successfully logged in and his username can be found in the “admin” table, then he is redirected to the admin.php module.

Module admin.php - this module outputs the number of products, categories, subcategories, users and orders. There is also a menu with links to the products, users and orders manipulation modules.

Module produse.php – the admin can see a list of the main categories alongside with the subcategories, that can be selected and deleted using the module delc.php. Here the administrator can specify a new category name and a picture for it, and using addc.php he can add the new category. Clicking on a category leads to the same module, but there are other options like adding a subcategory (addc.php) or adding/modifying/deleting (produs.php/addp.php/delp.php).

Module produs.php - a product can be modified. This module displays the product information which can be modified and updated using the PHP module actualizeaza.php. Specification can also be inserted here.

Module users.php - this module displays the list of users, and the possibility of deleting them using the module delu.php. Also, it is specified if the user has a credit card and if he has any orders.

Module comenzi.php - this module displays the orders grouped into “pending”, “confirmed” and “denied”. Clicking on the edit button will let the administrator use the detaliicomanda.php module, responsible for outputting the order details.

Module detaliicomanda.php - an order is shown here. The administrator cans approve/deny/ /delete an order using confirma.php/refuza.php/sterge.php. When an order is denied the administrator can specify the reason why it was denied. When the user click on the order details in his account he can see the reason and try to remediate the problem if he wishes, or to cancel the order.

Module logout.php - this module logs out the administrator from the administration area, redirecting him to the index.php module located in the root directory.

3.4 Install Note

Copy the application files into the htdcos directory. Using the phpMyAdmin application, the database “magazine” must be created. In the SQL directory there can be found a text file containing the structure of the database in SQL language. Thus, the database can be up and running in no time (Timofte, 2002).

After the query, the administrator must visit the page and use the register.php module to create the administrator account. He must specify the username admin.

4 Conclusion

Computers, communication networks, and a wide variety of newer, rapidly developing technologies are increasingly important ways in which individuals, companies, and organizations of all kinds conduct business (Boboila, 2007). These technological changes present challenges that must be faced not only by technologists but also by lawyers, policy-makers, economists, entrepreneurs, ethicists, and other stakeholders. Potential topics to be addressed from both technical and non-technical points of view include but are not limited to: internet business management; web searching, as a technology and as a business; B2B, B2C, and C2C technology and business models (Camp, 2000).

译文

B2C的电子商务网站

资料来源：克拉约瓦大学数学与计算机系 邮箱: boboila@central.ucv.ro

作者：巴宝莉．克丽丝特尔

万维网代表了一个为全球产业带路的新前沿、新业务。现在商品交易的另一个完全不同的概念：电子商务。这种商业模式提供了一种新的销售手段：达到世界各地的产品销售。该模式提供一个可控制的网络在线销售，从而达到另一种全新的目标市场。该网站须具有一个很有吸引力的网站界面，并且允许来自世界各地的客户在该网站上查看公司的产品并且可以购买他们的产品。付款方式可以是一手交钱，一手交货也可以直接通过信用卡网上支付。该商店的主人可以通过网站后台管理容易地增加或删除产品条目，并通过管理模块审核不同的命令等应用。

关键词：电子商务；全球资讯网；HTTP服务器；网站；数据库 1 引言

这个应用程序旨在提供一个网上在线商店。目前还没有关于销售产品的，业主可以在该网站上添加任何他想要销售的产品，如笔、液晶电视等等。该网站管理员可以随意的增加或删除产品类别。每个产品类别可能有其它子范畴，这样的项目其任务会变得更为简便，组织结构也会更加良好。在应用该程序时，我们通过HTTP服务器，My SQL数据库和团队合作过的PHP作为服务器端脚本，目的是提供动态的产品信息内容。My SQL是目前最常用的DMBS（数据库管理系统），在非常简单的角度上被使用操纵信息关系模式(Timofte,2002)。

2 网站数据库 2.1 数据库图

该数据库被定义为“magazin”，一共由八张表格组成。我们能在接下来的数据库框图可以观察到。

2.2表描述

用户表—这个表格中储存客户注册到系统中的信息。它储存一个客户唯一的用户名，该帐户下的密码，该客户唯一的电子邮件地址和其通讯地址。客户可以用自己的信用卡通过网上银行来支付其所购买的商品。这类信息也会被储存在这张表格中(Macklup, 1991)，表recuperari—这个表格包含两个领域。一个是代表客户忘记了其自身的密码的电子邮件地址，另一个关键的应用所产生的信息是为了检查新密码请求者确实是真正的客户。这把钥匙将被发送到该请求者的电子邮件中。如果得到该客户的邮件回应的，则该系统将会产生一个新的秘密给该请求者 (Odlyzko,2001)。

图1 数据库关系图

管理员表—我们可以观察到在图1中只有一个领域。管理员表中的用户有管理权责。一个管理员可以添加/删除新物品或浏览接受/拒绝其他用户的请求。

produse_spec表—这个表格包含一个产品的规格说明。每一个产品都可以有一个或多个规格说明储存在这表格中。

Comenzi表—一个用户可以无数量下自己喜欢的的订单。该份订单信息被就存放在这张表格中，该订单信息包括下该订单的客户名称，定购的日期，该订单总价格和付款的选项。该份订单有一个状态。最开始，新订单将处在一个被管理员审核的位置。在它已被审查通过后,管理员在批准或拒收这份订单后，将该订单信息发送给用户。

Categorii表—为了网上商店能有一个很好的结构。每个类别都可以有许多个子类别。

comenzi_produse表—这张表格中储存的信息是对应与一个特定的顺序的产品信息(Roşu-Hamzescu, Mitu, 2001)。

3 结构设计

3.1 网站交互图模块设计

这个应用程序有两个主要功能模块：用户界面模块和管理员模块。这些模块主要依赖于数据库“magazin”。在图2中，我们可以观察到各个模块之间的相互关系(Loshin & Vacca, 2004)。

图2 模块交互图

3.2用户界面模块前景

该模块有是由多个PHP模块组成(Năstase, Năstase, 2002)，这几个模块都被存储在一个的目录里。所有这些模块都被包括在了接口中。首先，我们将解释下这些模块：

模块sus.php—该模块负责为用户界面模块提供头文件。它体现该模块的标志、连结的关系和购买流程说明。

模块jos.php—这模块简单的显示在所有的模块的页脚中(版权，说得更具体)。

模块login.php—如果用户在登录模块中输入一个正确的用户名和密码，登入模块是代替账户选择链接(退出，历史记录，帐号细节和改变密码)。这模块在用户进入系统时便可执行。

模块cosdecumparaturi.php—在这模块中实施了一个类，它象征着购物车。这个类是用来存储客户想要买的产品信息。提供了一个增加、删除产品数量的方法。该模块中所有的功能需要从数据库中增加数据信息，包括管理模块中所需要的功能。

模块util.php—这模块是所以模块中最重要一个应用。它包含了在数据库中所定义的相互影响的功能结构。当一个用户登录或注销时，起到检测用户身份的功能。还有所有的功能需要操纵信息的数据，需要包括函数，由管理模块。

模块中实际用户界面都被储存在根目录中。他们的功能是基于util.php和cosdecumparaturi.php两个模块建立的。下面我们将解释这两个模块：

模块index.php —这个模块带有两个按钮来定义购物车的概况，既可以重定向到购物车操纵模块和也可以清空购物车，目录包含主要的类别，一个登录模块或帐号选项，如果用户正确的登录系统，那么在最后,这两个按钮分别是用于创建一个新账户的和检索被遗忘的密码。这些目前都处在一个空余的模块,尽管也有一些例外。当我们将呈现其它模块，如果这些模块是不一样的，那边它将会被指定。

模块logout.php—在一个用户完成他的行为，他可以使用退出链接来退出系统。

模块catalog.php—当一个用户点击主要范畴，他将被会被转到这个目录模块，显示已被详细标注出的图片信息。如果类包含产品，那么他们就会随着一个链接而链接到produs.php模块并且将自动添加到购物车模块；如果有子范畴，他们就会显示产品的照片和一些产品的数量。当它被点击，一个范畴将变成它的一个分支。

模块produs.php—当一个产品模块链接被点击，该模块就负责输出储存在数据库中的产品信息并且现实一个用户可以将随意将产品添加到购物车中的按钮。

模块cosulmeu.php—一个用户可以更改其购物车里产品信息。他可以删除或更改产品数量。客户可以返回继续购物或者他也可以完成购物进行付款。

模块comanda.php—在浏览完购物车中的信息后，这是订单处理过程中的第二个模块。这个模块仅限于用户已经成功登录网站。成功登录后，购物车模块中包含一个交货按钮与一个选择付款按钮。

模块plaseazacomanda.php—只有通过comanda.php模块，才能从数据库中添加订单信息，最后完成客户网上购物功能。

模块contulmeu.php—一个客户可以再该模块修改他自身信息内容，举个例子，如果他想改变送货地址或添加一张信用卡。只有当客户已成功地登录就可以修改这些信息内容。

模块comenzi.php——一个客户可以在这里查看他的订单细节。他可以看到实际订单或那些他在过去完成的订单。如果一个订购量被否认，他可以这里看到原因并可以试着去解决这个问题。他可以使用模块reconfirmare.php对他的订单进进行再次确认或通过使用anuleaza.php模块进行订单的取消等操作，这些操作只有当客户登录后才能被实现。

模块schimbaparola.php—如果一个客户已成功地登录，该客户可以根据他自己的意愿来改变他的帐户密码。

模块register.php —一个新客户也可以在购物篮中浏览产品目录，并添加产品。如果他想重新排列货物，但是他没有一个帐户，他可以点击上面的链接，为其创造一个，从而来实行这个模块。客人可以通过选择一个用户名和密码，并提供他的电子邮件，来完善个人资料。注册完信息后，客户可以随意地增加一个信用卡以实现在线购买。

3.3管理模块前景

PHP模块中的管理模块将被存储在一个目录—ADMIN中。管理员可以通过指定到此目录的路径网址(URL)中的主机名来简单地实现这个模块通 (例:oxygen.ro /管理)。许多模块仅执行更新数据库，然后返回到模块中显示信息这一个动作(Kleinberg & Lawrence, 2001)。

模块index.php—这模块显示一个登录的形式。如果用户已经成功登录和那么可以发现他的用户名将在管理员表中出现，然后他将转向的admin.php模块。

模块admin.php—这个模块的输出产品的数量、种类、细分产品的用户和订单。也一个有链接到的产品的菜单、用户和命令处理模块。

模块produse.php—管理员可以看见一张分有主要类别名单，配合的子范畴，即可以通过使用delc.php模块可以选择增加和删除。通过这个模块管理员可以指定一个新的类别名字和效果,并利用addc.php他可以添加新的范畴。但也有一些其他的选项，如选择添加一个分支(addc.php)或添加/修改/删除(produs.php / addp.php / delp.php)。

模块produs.php —产品模块可以被修改。这个模块显示产品的信息，这些信息可以通过使用actualizeaza.php模块来修改和更新，规格也可插在这里。

模块users.php——这个模块显示用户的名单，， 通过使用模块delu.php删除可能的用户。同样,用户可以被指定如果该用户有信用卡，或者有任何订单。

模块comenzi.php——该模块显示了订单被确认之前的信息。管理员可以点击编辑按钮来使用detaliicomanda.php模块,管理员通过该模块来负责订单的细节问题。

模块detaliicomanda.php——订单信息将在这被显示。管理员可以通过confirma.php/refuza.php/sterge.php模块来增加/删除/拒绝批准客户的订单。当一个订单被否认了管理员可以通过该模块来查询订单被拒绝的原因。当用户在他的帐下点击订单的细节问题按钮他就可以看到订单被拒绝的原因，如果他希望,或者取消订单，客户可以试图调整的问题。

日志模块logout.php—管理员可以通过这个模块，重定向到他的index.php模块位于根目录。

3.4安装注意

将应用目录复制到htdcos中，利用phpMyAdmin应用，数据库“magazine”必须被创造。在SQL目录能找到一个包含数据库的用SQL语言编写的结构文本文件。因此，数据库可以及时的启动和运行(Timofte,2002年)。查询后，管理员必须所访问该页面并使用register.php模块创建管理员帐户。他必须具备一个固定的用户名。

4 结论

计算机网络的发展，各式各样的设备更新，快速发展的科学技术是个人、公司、组织等各种商务活动得以正常进行的的重要途径 (Boboila,2007年)。目前，这些技术上的变化所需要面临的挑战不仅仅是技术人员还可以是律师、决策者、经济学家、企业家、伦理学家、和其他一些利益相关者。其潜在的问题从技术和非技术角度得以被解决，包括互联网业务管理、B2B、B2C、C2C技术和商业模式和网页搜寻可以作为一项技术和一门生意。(Camp, 2000)。