CHAPTER FIVE
SYSTEM TESTING AND INTEGRATION
Implementation is the act of carrying
an undertaking into effect. Testing cannot be successfully completed without a successful
implementation, hence testing and implementation work hand in hand.
Implementation is the actual conversion of the existing system to the newly
designed system thereby putting the new system into operation. Installing the
new system into a machine is a stage in the implementation process. When it is
absolutely clear that the new system meets all the users sets of requirement
(system specification), the old system may be abandoned for the new one.
Training the users is another important aspect of implementation, because it is
after the users have been trained to handle the new system that they can
actually use it to process their various transaction requirements.
5.1 IMPLEMENTATION TECHNOLOGY
The objective of this
project is to develop an online store. When the user types in the URL of the
supermarket Store in
the address field of the browser, a Web Server is
contacted to get the requested information. In the .NET Framework, XAMP acts as
the Web Server. The sole task of a Web Server is to accept incoming HTTP
requests and to return the requested resource in an HTTP response. The first
thing XAMP does when a request comes in is to decide how to handle the request.
Its decision is based upon the requested file's extension. For example, if the
requested file has the .asp extension, XAMP will route the request to be
handled by asp.dll. If it has the extension of .aspx, .ascx, etc, it will route
the request to be handled by ASP.NET Engine.
The PHP Engine then gets the requested file, and if
necessary contacts the database through ADO.NET for the required file and then
the information is sent back to the Client’s browser. Figure 5.1 shows how a
client browser interacts with the Web server and how the Web server handles the
request from client.
5.2 MYSQL
DATABASE
In this project, MySQL
is used as the backend database. MySQL is an open source database management
system. The features of MySQL are given below:
Ø MySQL is a relational database management system. A
relational database stores information in different tables, rather than in one
giant table. These tables can be referenced to each other, to access and
maintain data easily.
Ø MySQL is open
source database system. The database software can be used and modify by anyone
according to their needs.
Ø It is fast,
reliable and easy to use. To improve the performance, MySQL is multithreaded
database engine. A multithreaded application performs many tasks at the same
time as if multiple instances of that application were running simultaneously.
In being multithreaded
MySQL has many advantages. A separate thread handles each incoming connection
with an extra thread that is always running to manage the connections. Multiple
clients can perform read operations simultaneously, but while writing, only
hold up another client that needs access to the data being updated. Even though
the threads share the same process space, they execute individually and because
of this separation, multiprocessor machines can spread the thread across many
CPUs as long as the host operating system supports multiple CPUs.
Multithreading is the key feature to support MySQL’s performance design goals.
It is the core feature around which MySQL is built. MySQL database is connected
to ASP.NET using an ODBC driver. Open Database Connectivity ODBC) is a widely accepted
application-programming interface (API) for database access. The ODBC driver is
a library that implements the functions supported by ODBC API. It processes ODBC
function calls, submits SQL requests to MySQL server, and returns results back
to the application. If necessary, the driver modifies an application's request
so that the request conforms to syntax supported by MySQL.
5.3 INTEGRATING THE WEBSITE AND DATABASE
Customers ordering from
an e-commerce website need to be able to get information about a vendor’s
products and services, ask questions, select items they wish to purchase, and
submit payment information. Vendors need to be able to track customer inquiries
and preferences and process their orders. So a well organized database is
essential for the development and maintenance of an e-commerce site. In a
static Web page, content is determined at the time when the page is created. As
users access a static page, the page always displays the same information.
Example of a static Web page is the page displaying company information. In a
dynamic Web page, content varies based on user input and data received from
external sources. We use the term “data-based Web pages” to refer to dynamic
Web pages deriving some or all of their content from data files or databases. A
data-based Web page is requested when a user clicks a hyperlink or the submit
button on a Web page form. If the request comes from clicking a hyperlink, the
link specifies either a Web server program or a Web page that calls a Web
server program. In some cases, the program performs a static query, such as
“Display all items from the Inventory”. Although this query requires no user
input, the results vary depending on when the query is made. If the request is
generated when the user clicks a form’s submit button, instead of a hyperlink,
the Web server program typically uses the form inputs to create a query. For
example, the user might select five products to be purchased and then submit
the input to the Web server program. The Web server program then services the
order, generating a dynamic Web page response to confirm the transaction. In
either case, the Web server is responsible for formatting the query results by
adding HTML tags. The
Web
server program then sends the program’s output back to the client’s browser as
a Web page.
5.4 WEB
PAGE PROGRAMMING OPTIONS
An e-commerce organization can create data-based Web pages by using
server-side and client-side processing technologies or a hybrid of the two.
With server-side processing, the Web server receives the dynamic Web page
request, performs all processing necessary to create the page, and then sends
it to the client for display in the client’s browser. Client-side processing is
done on the client workstation by having the client browser execute a program
that interacts directly with the database.
No comments:
Post a Comment