Beruflich Dokumente
Kultur Dokumente
computer retailer
Wang, Jianping
MSc Information Systems
School of Computing
2002/2003
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Summary
This project is about the requirements and design of a 'customer-friendly' e-shop for a computer retailer. A
prototype is required to demonstrate some of the features in the design. By focussing on the requirements of the
customers, the prototype aims to demonstrate the essential features for supporting the buying process and for
offering advice on the purchase.
A Chinese company which sells assembled computer has been chosen as the study case.
The RUP approach has been used for the development of the prototype. The design/build/test cycle was
conducted twice.
A three-tier architecture was adopted for the prototype, using ASP, JavaScript and Microsoft Access database.
The following functions were implemented in the final prototype:
Select and order: to support customers in selecting and ordering the products.
Products query: to help customers in finding the products that are partly remembered;
Show relevant components: to show the components that are relevant to user type of the customer The user
types include big business customer, small business customer and family customer.
Show the most popular products being visited and show the most popular products being sold -to provide
useful advice to customers.
Show latest news: to provide the latest news to the customers Check order state: to help customers to
check the state of the order after the purchase.
The result of the evaluation showed that the prototype can give customers strong support when they were
buying assembled computers from a computer retailer.
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Acknowledge
Dr. Lydia Lau
Firstly my thanks must go to Lydia Lau, my project supervisor, for her advice, and individual guidance and
suggestions, comments, ideas and help. I learned not only technology but also character of people from her.
Dr. Eric Atwell
My project assessor, who gave me very useful advice on how to do the project
Mrs Ann Robert
Project Officer, who gave me some useful help
My classmates and friends
I would also take the opportunity to thank my classmates and friends ,who gave me their time to assist in the
various stages of this project
Wang, Jianping
MSc Information Systems
II
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Content table
Chapter 1: Project Introduction
1.1 Background
1.2 Objectives
1.4 Deliverables
1.5.2 E-shop
Chapter 2: Approach
3.1 Induction
10
11
11
13
13
13
14
14
14
14
16
16
18
4.2.1 Usability
19
4.2.2 Performance
19
4.2.3 Security
20
Wang, Jianping
MSc Information Systems
III
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
20
20
21
5.2.1 Principle
21
5.2.2 Layout
22
23
24
5.3.2 Login
24
25
26
27
28
29
30
31
31
32
32
32
34
36
6.5 Database
36
6.6 Testing
39
Chapter 7: Evaluation
40
40
7.1.1. Criteria
40
7.1.2 Results
40
43
7.1.1. Criteria
43
7.1.2 Results
43
Wang, Jianping
MSc Information Systems
IV
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Chapter 8 Conclusion
43
8.1 Achievements
43
44
45
Reference
Appendix A: Reflection upon the project experience
Appendix B: Objectives, deliverables and agrees marking scheme
Appendix C: A copy of interim report sheet
Appendix D: Reference books and URL
Appendix E: Current model
Appendix F: Vision
Appendix G: use case description
Wang, Jianping
MSc Information Systems
46
47
48
50
52
53
54
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
1.2 Objectives
Analyse the requirements of a 'customer-friendly' e-shop for a computer retailer.
Translate the requirements into a high-level design for the e-shop and prioritise the requirements.
Produce a prototype using an incremental and iterative approach
Evaluate the prototype.
1.4 Deliverables
A project report.
A prototype
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
As Winfield (2002) mentioned, the key components of the value chain can be very different for different
industries and even among different business within a particular industry. But the generic value chain for
Internet commerce includes the following four components as Winfield (2002) described.
Attract customers
The first component of the generic internet commerce value chain is to attract. By this we mean whatever step
we take to draw customers into the primary site, whether by paid advertise on other web site, electronic mail,
print, or other forms of advertising and marketing. The point of this phase is to make an impression on
customers and draw them into the detailed catalogue or other information about products and services for sale.
Interact with customers
The second component is interact. By this we mean turning customer interest into orders. This phase is
generally content oriented and includes the catalogue, publication, or other information available to the
customer over the internet. The content may be distributes by many different mechanisms, such as the World
Wide Web or electronic mail. In some cases there may be links between Internet commerce and content
distribute by other media, such as CD-ROMs.
Editorially, content may change infrequently or frequently. Technically, content may be static or dynamic.
Act on customer instructions
The next component in the commerce value chain is act. Once a buyer has searched through a catalogue and
wishes to make a purchase, there must be a way to capture the order, process payment, handle fulfilment and
other aspects of order management.
React to customer inquiries
Finally, after a sale is complete, the customers may have some questions or difficulties that require service.
For example, a transaction system that keeps track of all of a customers purchases can generate a statement
summarizing them. Customers who are wondering whether or not their orders have been shipped might check
back with the system.
1.5.2 E-shop
According to Whitely (2000), For e-Commerce applications that are selling goods or services the internet
application, held on the server is an E-shop. The infrastructure of the e-shop can be very simple or it maybe
very complex. The basic element of an e-shop is a web-page that offers or advertise the goods for sale and
provides a means for the shopper to make s purchase. At very simplest e-shop. Or online advert, could simply
list the products for sale or the services offered and invite the customer to phone, fax or e-mail their order But
the complex e-shop can include many more features. These can include as Whitely (2000) mentioned as
follows:
Customer registration
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Some e-shops ask the customers to register and then store the customer details on a database. This then allows
the vendor to tailor its information for specific customer and saves the customer typing in details again on
future visits.
Dynamic web pages
A dynamic web page is built for each user when the web browser requests it. The dynamic web page may be
built by reading a database in which case the page can include. For instance, the latest price and possibly
whether the goods are in stock.
Personalised web pages
If the user has registered with the site the system can generate a page for that specific customer.
A shopping basket/cart
Customer in a conventional shop is likely to collect a number of products. Goods can be selected and placed
in the electronic basket. Facilities are made available for the contents of the basket to be reviewed and
unwanted goods can be returned to the shelves. When the shopping is complete the customer then makes
payment for the goods in the basket.
Additional information
The e-shop need to let the customer know what the product or service is The customer can have additional
information not normally available in a conventional shop. Example of this are: the win ship that gives a detail
assessment of each vintage; bookshops that provide customer review; music sites that can play a sample of the
recording that is for sale
Community
Bulletin boards are one such device in this area.
Multiple payment options
The current norm for online payments is a credit card and most e-shops will want to accept all major credit
cards. Some e-vendors also have /accept debit cards-cash and so on.
Encryption
Most e-shops use an encryption system to secure to the transmission of personal and payment details.
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Online deliver
Electronic products such as software, information and music can be delivered online. Where it is appropriate,
the use of online delivery cut the costs of distribution and avoids the customer having to wait for the goods to
arrive.
Loyalty schemes
Some e-shop are introducing loyalty schemes. Each purchase made attracts a number of points and the points.
Accumulated electronically by the vendor, can eventually be used for discount or free goods.
Online help
Having used the Internet for sales it can also be used for after sales. The web page can be used for product
instructions and self-diagnosis pages all of which can be updated when the need arises. The customers can also
use e-mail for online help.
Shopping mail
E-shop may be set up as a part of an online mail. Like their conventional equivalent the online mail is designed
to attract customers because there is a range of stores. E-malls can help out the individual vendor with shared
payment infrastructure.
1.5.3 Customer-centred theory
Chandler (2003) mentioned, Many website have products that people cant find. It is clear that a big gap exists
between how online store are organized and how customers want to shop for products. This results in
unsuccessful searches and abandoned shopping carts. Shoppers give up when they cant find what they are
looking for easily and quickly.
Most website lack a customer-focused approach. Web developers often design e-commerce website that are
database driven rather than customer driven. Database-driven websites are organized around products than an
online store has for sale and are designed for efficiencies of code. Customer-driven websites are based on how a
customer shops for products on the website and are designed after understand customer needs.
customers expect more from this new technology. Information should be specially developed and tailored to
online shopping and must be kept current.
Chapter 2: Approach
This project uses United Process, which is an increment and iterative approach to develop the system.
This chapter includes three parts. The first part introduces the theory of the incremental and iterative approach
and why the developer uses the approach. The second part introduces how to use the approach to make out a
project schedule. The third part describes the executed project schedule in the project.
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Not having much experience of architecture requirements, the developer can begin to seek core architecture in
the inception phase that satisfies the key requirements, overcomes the critical risks, and resolves the central
development problems. Then in the elaboration phase he can refine it.
Handing changing requirements
Jacobson (1998) mentioned, There are gaps between the developer and the users, users and users.
Commonly, after using the system the user will have new requirements because it is difficult for a user to know
all requirements before he uses the system. So it is better to provide him a system as soon as possible to get his
requirements even if the system is not perfect. Then the users new requirements can be taken into account
which is for getting requirements
Achieving continuous integration
Jacobson (1998) mentioned Frequent builds force developers to closure at regular intervals-closure in the form
of a piece of excitable software even if developers fail to achieve the planned result in an early iteration, they
still have time to try again and improve the models in subsequent internal releases.
In this project the developer is a novice and high risks exist that he might fail to achieve the planned result in an
early iteration. Therefore he needs the chance to improve the models in subsequent internal releases.
2.2 Planed project schedule
As a result of using incremental and iterative approach, a project schedule can be produced as shown in table
2.2. The schedule corresponds to the stages of RUP as follows:
Inception: From stage 1 to 2, the developer defines the scope of the system.
Elaboration: From stage 2 to 6, the developer captures most of the remaining requirements and formulates
functional requirements as use case. At the same time a sound architectural foundation is established.
Construction: From stage 7 to13, the developer builds a prototype.
Transition: In stage14, the developer corrects the flaws from testing.
This schedule has the following functions:
Mitigating risks of requirements
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
In stage 2, two weeks are scheduled for the developer to understand the necessary requirements. afterwards in
stage 7 and stage 14, the system is adjusted by refining requirements.
Getting a robust architecture
The objective of stage 3 to 5 is to get a robust architecture. Till stage 5, the cost of time is still short so that it is
affordable to condust the iterations that assure the architecture is robust.
Handing changing requirements
In stage 6, the developer builds UI prototype to help users to check if the systems functional and nonfunctional requirements can achieve the users requirements. Then in stage 7 further refinement can be
conducted.
Achieving continuous integration
In the stages from 8 to 13, the developer begins to construct the system. If the developer fails to achieve the
planned result, in stage 14 he can still refine the system based on field tests.
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Task
Description
Weeks
Reading material
Business
modelling
and
10
11
12
requirements capture
3
Analysis
level
UML
modelling
4
Design
model
architectural
solution
prototype
6
Build UI prototypes
Requirements elaboration
E-R model
10
Build modules
11
12
13
14
X
X
tests
15
16
Report writing
Wang, Jianping
MSc Information Systems
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
3.1 Introduction
Ningbo Quanda Computer Company(QD) is a small company ,which locates in the inner-city of Ningbo,
Zhejiang, China. It has 17 staff and the annual turnover of 2001 and 2002 is about 3,000,000 respectively.
It provides various kinds of electronic products ranging from high-end to low-end and relevant services. This
project will concentrate on QDs business related to compatible computers, which are assembled by QD itself,
peripheral equipments and relevant services. The relevant services include installing software for computers,
updating computers, repairing computers and so on.
Thanks to advertisements and past customers introduction, QD has a lot of customers now. They can be
divided into three main types: big business customer, small business customer and family customer.
Big business customer
The main business customer includes two big companies, each of which has more than 9,000 staff, and more
than 30 sub-companies distributed all over Ningbo. They are both industry users. One is electric company and
the other is bank. About 20% of turnover and 40% profit of QD come from the two big companies in 2001.
Every time they buy few kinds of configuration because it is easier for maintenance. But each configuration
includes at least 50 computers. Commonly, after the two big business customers buy products, they will
distribute the products to their sub-companies. The distance between QD to these sub-companies is from 300
meters to 150 kilometres. When they buy computers, they buy maintenance services at the same time. QD
provides on-site technology support.
This kind of user has three characters: firstly, they need to buy computers frequency because they always need
to abandon some old computers and buy new ones to replace them. Secondly, they care for reliability and ontime service more than price. Finally, the usage of the computers is simple.
Small business customer
About 20% of turnover and 15% profit of QD come from about 100 small companies in 2001. Most of them are
private companies. Usually, this kind of company has less than 100 staff. Each time they buy less than 10
computers. They usually use computers for management, and each computer usually will be used together with
many peripheral equipments.
After they buy the computers, in a long time, they will not buy computers again, but they will buy some
peripheral equipment such as modems, printers, scanners and so on, and update some components later.
This kind of customers cares for the computers extendedness more than other property. For example, they like
there are many interfaces in the main board so it can be used with many peripheral types of equipment.
Family customer
Wang, Jianping
MSc Information Systems
10
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
QD has many family customers who locate all over Ningbo. Most of them are student parents because most
schools require students to have they own computers. Commonly, family customers are not professional and
they will buy computers just once for their own use. Since they will put the computer in their accommodation,
so they not only think that the computer is a machine but also think it is a kind of furniture. It means they not
only care for the performance, price, but also care for the appearance. At the same time, because the computer
for a family is not very cheap, they care for service, for example whether and how the computer can be repaired
in time when it breaks down. Furthermore, because most of the user are students, they always like to try new
software or disassemble the computer for research., the user always encounter many problems when they just
bought the computer home.
11
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
have to wait for the components to be assembled, software to be installed, and tests to be made. Commonly it
takes customers nearly a whole day from when they go to the company to they buy the products back.
The process is especially inconvenient for family customers because they have to use their spare time to buy
computers. Big and small business customers waste much time as well although the process is in their office
hour.
It is inconvenient for customer to search for products
Firstly, the customer has to see the products on site. Secondly, there is a distance from the company to its
warehouse and every time the engineer cannot just bring all of products. Thirdly, some users remember just a
part of the products name which they want to buy, but it is not easy for QDs engineer to understand. So it will
cost some time to find if there are the products as the customer required.
It is not easy to for customers to maintain their computers
One problem is that it is easy for big business customers to lose drive program of components because in the
big company, the computers will be transferred from one area to different area and from one person to other
person.
The other problem is when the operating system is updated, how users can get the diver program of the
components.
Now if the customers need to get the diver program they have to come to QD.
.
It is not convenient for user to get advice
As mentioned in the background of this report, customers need referent information. Commonly, there are two
kinds of information customers care for.
What kind of products that other customers are interested. Commonly, every customer knows some information
about some products before they begin to select. Maybe it is from their own experience, maybe from their
friends. Anyway, if many people are interested in the product, it should have some advantages.
Secondly, the more customers buy the product, the better service and discount the product offers. The reasons
are as follows: firstly, the more amount of this kind of product imported by QD, the higher discount QD can ask
from its provider. So the customer can get higher discount. Secondly, the more amount of this kind of product
sold, the more the QDs engineers are familiar with it. They can offer people better service.
But now, in order to get these two kinds of information, the user has to go to QD. But even they arrive QD, the
information is not so accurate because it is difficult for QD to statistic the visit times and record the dealing
times timely.
It is not convenient for user to know the latest news on time
Wang, Jianping
MSc Information Systems
12
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
QD always gives some discount to customers for specific products or in specific periods. But it is not easy to let
customers get the news on time because customers havent enough time and motivation to go to QD frequently.
Thus the company will lose the potential chances.
13
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Furthermore, it is good for QD to book products because they get the order on time.
Wang, Jianping
MSc Information Systems
14
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
e-shop
big b ussiness
cus tomer
c ustomer
small business
customer
hot products being visited
Input news and rank them
Account system
Wang, Jianping
MSc Information Systems
15
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
4.1.2 How the functional requirements help resolve the problems
The table 4.1.2 shows that how the functional requirements help resolve the problems mentioned in section 3.3.
For example, in order to resolve the problem of inconvenient for customer to search for products the
customer-friendly e-shop has the products query function.
The problems (as in section The function of customer-friendly e3.3)
shop
Selection and purchase is not Select and order
convenient for customers
Check order state
It
is
inconvenient
customer to search
products
16
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
17
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Customers can download the software they need from the e-shop. The software was catalogued so that user can
easily find the things they are interested. It is useful for customer to get the useful software on time.
Automatic E-mail
Customers receive one to one service through this function. After the customer registers, his characters and
interests will be stored in database. For example, the customer is a customer of a big company and he want to
know the processors information. Then after the retailer input information about processor for customers of big
company, the customer will receive the e-mail.
4.2 Non-Functional Requirements
Functional requirements care what system can do. Non-functional requirements care what are the systems
qualities. The non-functional requirements include usability, performance and security. In this project, we get
Non-Functional Requirements by reading, questionnaire and interview.
4.2.1 Usability
According to Dennis(2003), usability is focused on helping the users cognitive processes to help them perform
the tasks they want to do. The table 4.2.1 shows the requirements of usability in this project.
Wang, Jianping
MSc Information Systems
18
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Items
Requirements
Ease of learning
A user who has never seen the user interface before can
learn it sufficiently well to accomplish basic tasks, e.g.
can use the system to order one product in 20 minutes.
Efficiency of use
Memo ability
Error frequency and severity When customers use the system, they will not meet
serious error after they explore all of the functions. The
serious error means not only inconvenient for using but
also affect the business. For example, when a customer
order a product, the system breaks out, so he dont know
if he has booked it or not.
Subjective satisfaction
Wang, Jianping
MSc Information Systems
19
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Capacity requirements: The maximum of simultaneous users at peak use times about 200.
Capacity requirements: The system will store data on about 50,000 customers for a total less than 2 meg of
data.
4.2.3 Security
Dennis(2003) mentioned Security is ability to protect the information system from disruption and data loss,
whether caused by an intentional act. The requirements of security are as follows.
System value estimates: The QDs manager estimates that QD will lose 6000 yuan/per-day the if the e-shop
cant work.
Access control: Customers can access all of data.
Encryption and authentication: Authentication will be needed for user access.
Virus control: The files will be checked when it is uploading to the e-shop.
20
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Dennis (2003) points out:the client is responsible for the presentation logic, whereas the server is
responsible for the data access logic and data storage. The application logic may reside on the client, reside on
the server, or be split between both. Under this case it is complicated for software development because all
applications in client server-computing have two partsclient side software and server side software. It is also
not easy for updating because it needs to change the software in both sides.
The system uses three-layer architecture. The most important advantage of this architecture is that it is much
easier to be understood and maintained. The detailed advantages can be summarised as follows:
Scalability: In QD, the e-shop and account system will be put on different servers. But the e-shop needs data of
account system. On the other side, in future, QD may develop other systems to support its business, which will
be put on other servers. The three-tier architecture allows application components across multiple servers,
which is capable of making the system more scalable.
Reliability: It is easier to add more application servers or database servers to let redundancy in three tire
architecture. At the same time, if something wrong takes place the affect will be limited in one layer and the
error will be easy to be found.
Flexibility: Since the different layers separate from each other, when some changes take place in one layer
others need not to be changed. It makes the prototype more flexible. For example, if the database needs to be
changed from Microsoft access to SQL server, the application layer need not to be changed since the
application, which uses JavaScript and SQL, also support SQL server.
Reusability: Separating the prototype into multiple layers makes it easier to implement re-usable components.
.
21
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Aesthetics
Interface should be functional and inviting to users through careful use of white space, colour, and fonts. There
is often a trade-off between including enough white space to make the interface look pleasing without losing so
much space that important information does not fit on the screen.
User experience
Although ease of use and ease of learning often lead to similar design decision, there is sometimes a trade-off
between the two. Novice users or infrequent users of software will prefer ease of learning, whereas frequent
users will prefer ease of use.
Consistency
Consistency in the interface design enables users to predict what will happen before they perform a function. It
is one of the most important elements in ease of learning, ease of use, and aesthetics.
Minimal user effort
The interface should be simple to use.
5.2.2 Design
According to section 5.2.1, the developer designs the interface as follows
Layout
The screen is divided into four boxes. The top box is the navigation area through which all prospected user
issues can be navigated through the system. The left box provides support function of purchase such as
registration. The right box provides information of purchase. For example, customer can find the useful
information of products. The middle box displays result. For example, if a customer registers, the box will
display if he or she register successfully or not. Figure 5.2.2 illustrated the whole layout
Wang, Jianping
MSc Information Systems
22
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Menu box
Support
function
(e.g. register,
query)
box
Display
results
box
Product
information
for
purchase
box
23
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
register screen
customer
Cus tom er DB
register
5.3.2 Login
The registration process begins when a user inputs his username. Firstly, the user needs to input the username
and password, which are composed of characters or numbers. Then he presses confirm button. The system
will compare the username and password in database to check if the information input is correct or not. If the
information is correct, then the system will show the user login successful information. If the information is not
correct, the system will show what is wrong with the username and password, for example the username does
not exist or the password is wrong.
If the login is successful, the users login time and the users login IP will be recorded into the database.
2. username()
password()
3 username()
pass word()
4. correct or not
customer
Login sc reen
Login
Customer DB
Login result
24
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
logged in, the selection window will be shown and the new product with its price and quantity will be shown in
the new window.
The user can select the amount of the new product he wants to buy then he can press the confirm button to
confirm the selection. After he presses the confirm button, the selected product will be added to the shopping
cart and appears in the selection window. At the same time, it will be stored into the database.
The user can revise the products in the shopping cart by double clicking the products name to get rid of it or
press the clear button to clear all of the products in the shopping cart. At the same time, the database will be
revised.
If the user just selects and puts the products into the shopping cart but doesnt order, the shopping cart will save
the products the user selected. Then next time when the user begins to select some new products, the shopping
cart will be restored to let user put new products.
If the customer wants to order the product, he presses confirm button. Then the order screen will be shown
with the products list. Next the user can press the confirm button to continue the order process, after that the
automatic order number will be given and the receivers telephone number, address, e-mail and name are
required. If the user inputs wrong information, he can click clear button to rewrite the information. If it is
correct then he can press confirm button to confirm it. Then the receivers name and the address will be
shown. At the same time, the order information will be stored into the database and the shopping cart
information will be deleted. The whole process of selection and order finished.
Wang, Jianping
MSc Information Systems
25
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Customer
select screen
Customer DB
shoppi ng c art
choose amount and
confirm
Clear result
basket DB
Clear
Order
Order DB
Order screen
confirm order
order screen
Diagram 5.3.3
recei ver DB
Wang, Jianping
MSc Information Systems
26
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
customer
product DB
c atal og scre en
5.3.4 Show the catalog information relevant to the user type
Wang, Jianping
MSc Information Systems
27
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
cu stomer
product DB
catalog screen
Diagram 5.3.4 Show the components and products information relevant to the user type
Wang, Jianping
MSc Information Systems
28
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Custom er
Query screen
Order DB
show results
Diagram 5.3.6
Wang, Jianping
MSc Information Systems
29
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
main page
custome r
product DB
Wang, Jianping
MSc Information Systems
30
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
customer
main page
product DB
Wang, Jianping
MSc Information Systems
31
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
component
1..*
product
*
*
0..1
order
basket
1..*
0..*
receiver
0..*
1
1..*
product-and-basket
customer
32
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Wang, Jianping
MSc Information Systems
33
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Wang, Jianping
MSc Information Systems
34
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
registe
login
order
query
Product list
Product
query
Show Components
relevant to user type
Top
product
being
visited of
the
component
Latest
products
Top
product
being
visited
Top
product
being
sold
Latest
news
Top
product
being sold
of the
component
Select
and order
products
dim conn
dim connstr
dim db
db="database/database.mdb"
Set conn = Server.CreateObject("ADODB.Connection")
connstr="driver={Microsoft Access Driver (*.mdb)};dbq=" & Server.MapPath(db)
conn.Open connstr
%>
Secondly using sessions to check if the user has logged in or not
if session("user_name")="" then response.write "
" response.write "You haven't log in or you haven't
Please log in if you want to order something!" response.end end if
Thirdly access data from database
Wang, Jianping
MSc Information Systems
35
signed
in"
response.write
"
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
The candidate database includes Oracle, mySQLSql Server and Microsoft access.
Among this database, Oracle is the most stable and can be best maintained product. But it is also the most
expensive one. At same time, it also requires higher performance of hardware and system software. The
maintenance of it is the most complicate. QD cannot afford it.
Wang, Jianping
MSc Information Systems
36
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
As for MySql, it is one of the cheapest one. But it is quite young product, and not so popular as other three
products. It was not so familiar by most of developers. So there are some problems such as stability,
maintenance and cost of developing. As a result, it can be given up.
So
the
most
Feature
database size
database size
objects in a database
user name length
password length
table name length
column name length
index name length
Number of concurrent users
columns per table
table size
number of indexes in a table
number of columns in an index
bytes per row
number of tables in a query
columns
per
SELECT
statement
nested subqueries
number
of
enforced
relationships
SQL statement size
SQL Select
Price
The
feature
is as
Not Supported
Supported
1,048,516 TB
2,147,483,647
128
128
128
128
128
limited by available memory
1024
limited by available storage
250
16
8060
256
4096
255
32
50
253
32
follows:
approximately 64,000
yes
low
Table 6.5.1 Compare of SQL server 2000 and Microsoft access 2000
(From http://databasejournal.com/features/msaccess/article.php/2204341)
In the implementation, the access database is selected. The reasons are follows:
A. The prototype is for a small retailer and the retailer does not want to spend much money to do it.
B. The scalability, security and robustness system requirements are not high because it doesnt
include payment system, which supports customer to pay money in Internet.
C. QD has brought Microsoft access for its account system.
D. The Microsoft access is enough for e-shop requirements for example, the requirements of the maximum of
simultaneous users at peak use times is 200.But access support 255.
E. Both of Access and SQL server support SQl select. If the retailer needs to update Microsoft access to SQL
Server, the
applications can be not changed.
Wang, Jianping
MSc Information Systems
37
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
There are two main types of data storage formats: files and database. Files are electronic lists of data that have
been optimized to perform a particular transaction. A database is a collection of grouping of information that
are related to each other in some way.For example(e.g.., common fields.)
In the prototype there is a databases using in the project. Customers can access all of the fields of the databases.
The relationship is shown in the figure 6.5.2.
Wang, Jianping
MSc Information Systems
38
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
39
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
After the system tests, the developer found 10 potential customers to test the system and found some problems,
then he revised the system. For example more than 50% of them misunderstood the user type names of small
business customer ,then he change the name to customer of small companies, then the misunderstanding
was got rid of.
Finally, the developer confirm that the system is completed.
Chapter 7: Evaluation
The evaluation includes two parts: the prototype evaluation and the project evaluation. When we begin to
evaluate, firstly, we should have a criteria and then evaluate how much the prototype and project meet the
criteria. The developer divides the match degree into ten levels from 0 to 10. If the item is total unavailable,
then it got score of 0. If the item total matches the requirements, then the item got 10. . The developer finds 6
persons to interview and each person gives mark for each item, which the developer asked him or her. After
getting rid of the highest and lowest score, the developer calculates the average score. The reason for getting rid
of the highest and lowest score is to prevent joking.
7.1 Evaluating The Prototype
7.1.1 The criteria
To evaluate the prototype, the criteria are the prototype requirements and design. We need to check how much
the system satisfies all of the functional requirements and non-functional requirements
7.1.2 Results
7.1.2.1 Evaluation of the functional requirements
According to section 4.1,the developer interviewed 6 persons and they evaluated the items. The summary of the
results is shown in table 7.1.2.1
Items
User registration
10
10
User login
10
10
Show
relevant 10
components and types
based on customer types
Wang, Jianping
MSc Information Systems
40
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
10
Products Query
9.5
Total score
70.5(about 88%)
70.5(about 88%)
Items
Ease of learning
9.5
Efficiency of use
10
Memo ability
9.9
Total score
47.9(about 96%)
Layout
Content awareness
10
Aesthetics
User experience
8
9
Consistency
Total score
53(about 88%)
Wang, Jianping
MSc Information Systems
41
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Speed
requirements
Capacity
requirements
10
Capacity
requirements
10
The developer
Total score
29(about 96%)
System
estimates
Results
evaluation
value 8
of The person
evaluates
prototype
Access control:
The developer
Virus control
The developer
Total score
15(about 50%)
who
the
42
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Chapter 8 Conclusion
8.1 Achievements
The project is the requirements and design of a customer-friendly e-shop for a computer retailer.
The RUP was used as the approach. By using it,the developer produced the project schedule, which has the
functions of iteration and increment. The executed schedule is similar to the planed schedule. The follows is the
detail.
By reading materials, comparing with different e-shops, using questionnaire and interview methods, the
developer got the functional requirements and non-functional requirements of the retailer.
According to the requirements, the design of prototype was made out. The three-tire architecture was selected
as the architecture and the E-R relation diagram was selected to design database tier.
Then according to the prototype design, the developer began to implement the prototype. The ASP and
JavaScript were chosen as developing language and the Microsoft access was selected as database.
After finishing the implementation, the tests were taken place. All of errors in the prototype were adjusted.
Then after testing, the evaluation was given to the prototype and the project. Most of marks give by the
potential customers of the prototype are more than 80%.
Wang, Jianping
MSc Information Systems
43
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
The evaluation results show that both of the approach and the project are successful in each stage
44
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
REFERENCE
Wang, Jianping
MSc Information Systems
45
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Wang, Jianping
MSc Information Systems
46
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Wang, Jianping
MSc Information Systems
47
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Wang, Jianping
MSc Information Systems
48
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Hill, 2000.
10. amazon.co.uk
11 www.dell.com
12 www.comp.leeds.ac.uk/in31 In31 2002/2003 lecture 17
13. http://www.martinfowler.com/articles/newMethodology.html#N40035D
14 http://www.corba.ch/e/3tier.html
15 http://www.chinaz.com/download
Wang, Jianping
MSc Information Systems
49
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
16 http://www.uk-shop-online.co.uk/department-stores/detail-argos.htm
17 http://www.21tx.com/src/asp/dzsw/000140810121444.htm
1, Dennis, Alan. Systems analysis design / Alan Dennis, Barbara Wixom, New York : J. Wiley, c2003.,2nd
2, H.M.Deitel,P.J.Deitel, K.Steinbuhler: e-business & e-commence for mangers:prentice-hall,Inc:2001
3, Turban, Efraim.: Introduction to E-commerce / Efraim Turban. Upper Saddle River, N.J. ; London :
Prentice Hall, 2002.
4, Jacobson, Ivar : The unified software development process / Ivar Jacobson, Grady Booch, James
Rumbaugh.: Addison Wesley Longman, 1998.
5, Chandler, Kreta: Customer-centered design : a new approach to Web usability / Kreta Chandler, Karen
Hyatt. Upper Saddle River, N.J. ; London : Prentice Hall PTR, c2003.
6 Michele Marchesi(Eds.) Extreme programming and agile processes in software engineering : 4th
international conference, XP 2003, Genova, Italy, May 25-29, 2003 : proceedings / Michele Marchesi,
Giancarlo Succi (eds.). Berlin ; London : Springer, c2003.
7. Kruchten, Philippe. The rational unified process / Philippe Kruchten Reading, Mass. : Addison-Wesley,
c1999.
8. John ward and Joe Peppard: Strategic Planning for Information Systems: Cranfield School of
Management, Cranfield,Bedfordshire,UK
9, Treese, G. Winfield. Designing systems for Internet commerce / G. Winfield Treese, Lawrence C.
Stewart.: Addison-Wesley, c1998.
10.
Wang, Jianping
MSc Information Systems
50
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
13.http://www.martinfowler.com/articles/newMethodology.html#N40035D
14 http://www.corba.ch/e/3tier.html
Wang, Jianping
MSc Information Systems
51
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
customer
QD's s taff
Go to QD
Discuss with
QD's engineer
Introduce and recommend
configurati on and products
Plan to order it
Find them?
y
Accept?
y
Let QD's engineer to
assemble the c omput er
Assemble the com puter and
install relevant software
up date syst em
give update softw are
to customer
rece ive the software
and inst all it
Wang, Jianping
MSc Information Systems
52
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Appendix F Vision
customer
QD's staff
Plan to order it
Y
Ass emble the com puter a nd
ins tall relevant software
Send to t he
c ustomer
download and
ins tall it
Wang, Jianping
MSc Information Systems
53
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Appendix G: Use case description
*
User registration
Primary Actor:
Customer
Other Actors:
None
This use case begins when the user begins to register. Users are allowed to input the basic information such as
username, password, confirm password address, telephone number, e-mail address, postcode, real name and so on.
Alternative Paths:
(Other paths through the use
case
which
successful
result
in
outcome
None
course
of
events,
If the username has existed, the system will remind the user that the username has been used and the user has to
which
result
unsuccessful
typically
in
an
outcome
when
something
goes wrong)
Assumptions:
Every customer has e-mail address, telephone number and he prefers to tell QD.
Pre-conditions:
Post-conditions:
The information will be stored into the database if the registration is successful.
Each customer can only registers once and he has a unique username. After registration, users can log in and then
Rules list)
Related Non-Functional
Interface friendly
requirements Usability,
Performance, Security:
(Any non-functional
requirements that are specific
to this Use Case rather than
the system as a whole)
Project:
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
54
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
User login
(using www.comp.leeds.ac.uk/in21/UCDForm.doc) and an interaction diagram for the Basic Flow of Events.
*
User login
Primary Actor:
Other Actors:
None
This use case begins when the user begins to login. User inputs his username and password, and then submits. If
the username and password are correct, he will successfully login.
which
result
successful
in
outcome
None
course
of
events,
If the username or password is wrong, the system will remind the user, for example username does not exist or
which
result
unsuccessful
typically
in
an
outcome
when
password is empty.
something
goes wrong)
Assumptions:
Pre-conditions:
Post-conditions:
After the user logs the system will store the information in to the database.
Users can select and order products only after they login.
Non-Functional
Usability,
Performance, Security:
(Any
non-functional
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
55
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
The customers can be divided into several types. After the user chooses a type, he can get the relevant information and service of this type.
Use Case Name:
Customer
None
Actors perspective)
Basic Course of Events:
This use case begins after the user selects user type and enters the main page. The page will show the components
that he can buy, the numbers of each component type based on his user type and the total number of all the
product types.
Alternative Paths:
(Other paths through the use case
which
result
in
successful
basic
course
of
Some products belong to not only one kind of user type, so the same products may be shown in different ways.
events,
If there is no component or product in the database , the system will remind the user.
typically
when
The staff of QD has other system to update the products and renew the times being visited.
Pre-conditions:
Post-conditions:
When the user chooses a type of component, all of the types belong to the component will be shown and can be
selected.
Non-Functional
requirements
Interface friendly
Usability,
Performance, Security:
(Any non-functional requirements
that are specific to this Use Case
rather than the system as a whole)
Project:
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
56
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Use Case Name:
Customer
None
Customer can get the latest information of the hot products being visited
Actors perspective)
Basic Course of Events:
This use case begins after user chooses user type and goes into the main page. The page will show the 5 products,
which have the most times being visited.
On the other side, after the user chooses the type of the component, the system will show the five products having
the most times being visited relevant to this kind of product.
Alternative Paths:
(Other paths through the use case
which
result
in
successful
basic
course
of
None
events,
typically
when
The staff of QD has other system to update the products and renew the times being visited.
Pre-conditions:
Post-conditions:
After the user click products, the times of the product being visited will be updated.
Non-Functional
Interface friendly
Usability,
Performance, Security:
(Any non-functional requirements
that are specific to this Use Case
rather than the system as a whole)
Project:
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
57
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Show the most popular products being sold
Use Case Name:
Customer
None
Customer can get the latest information of hot products being sold
This use case begins after user chooses user type and goes into the main page. The page will show the 5 products, which has the
highest sales.
On the other side, after the user chooses the type of the component, the system will show the products with the highest sales
relevant to this kind of product.
Alternative Paths:
(Other paths through the use
case which result in a successful
outcome typically variations to
None
which
unsuccessful
result
in
outcome
an
The staff of QD has other system to update the products and renew the quantity of products being sold.
Pre-conditions:
Post-conditions:
After the user buys products, quantity of the product being sold will be updated.
Non-Functional
requirements
Interface friendly
Usability,
Performance, Security:
(Any
non-functional
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
58
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Select and order
Use Case Name:
Customer
None
This use case begins when the user selects the product he likes. He can choose the amount he wants to order. Then if he wants to
buy something else, he can repeat the selection process.
After he finishes selection, he can check the list and begin to order. He needs to input the receivers address, name, telephone
number and so on. At the same time, he will get an order number which can be used to check order state later.
Alternative Paths:
Select from latest products, hot products being visited, hot products being sold
If the user dislikes buying the products, he can clear any or all the products he has selected.
which
unsuccessful
result
in
outcome
If the customer has selected some products but he does not want to buy this time, he can store them and order next time.
an
Pre-conditions:
Post-conditions:
After the user orders the products, the quantity of the product being sold will be updated.
The customer and the receiver need not to be the same person.
Rules list)
Related
Non-Functional
requirements
Usability,
Performance, Security:
(Any
Interface friendly
The picture of the product can be shown
non-functional
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
59
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Products Query
Use Case Name:
Products Query
Customer
None
User can find product by inputting part of the name of the product
This use case begins when the user inputs part of the name of the product he likes. The product will be found and then the user
can select the product.
None
If the user knows nothing about the product and inputs nothing, the system will list all of the products.
which
unsuccessful
result
in
outcome
an
User knows the product and just cant remember the full name of the product.
Pre-conditions:
Post-conditions:
Related Business Rules:
(Reference to your Business
Rules list)
Related
Non-Functional
requirements
Usability,
Performance, Security:
(Any
Interface friendly
The picture of the product can be shown
non-functional
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
60
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Check order state
Use Case Name:
Customer
None
This use case begins when the user wants to check his order state. User inputs the order number and then gets the information
about the state of the order he made. There are two types of order states, one is that the order is being handled and the other is
Alternative Paths:
None
If the user inputs wrong order number, the system will remind the user that the order number is wrong. And the user needs to
which
unsuccessful
result
in
outcome
an
Pre-conditions:
The user has ordered some products and got an order number.
Post-conditions:
Related Business Rules:
(Reference to your Business
The staff of QD should input the information about the result of the order in time.
Rules list)
Related
Non-Functional
requirements
Interface friendly
Usability,
Performance, Security:
(Any
non-functional
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
61
The requirements and design of the 'customer-friendly' e-shop for a computer retailer
Latest news
The news is classified into several levels and shown in order of importance. After the user clicks the title of the news, the details will be shown.
Use Case Name:
Latest news
Customer
None
Users can get the latest news in time and know the priority of the news
This use case begins when the user enters the website. The news is shown to the user, the more important the news is, the higher
position the news appears.
None
None
which
unsuccessful
result
in
outcome
an
Pre-conditions:
The QDs staff input news in time and rank them in terms of importance.
Post-conditions:
Related Business Rules:
(Reference to your Business
Rules list)
Related
Non-Functional
requirements
Interface friendly
Usability,
Performance, Security:
(Any
non-functional
The requirements and design of the 'customer-friendly' e-shop for a computer company
Author:
Wang Jianping
Date:
26/10/03 08:11
Wang, Jianping
MSc Information Systems
62