Page | 1

Contents
Project Proposal .............................................................................................................. 5
1. Current Business Introduction ............................................................................ 5
a. History ................................................................................................................ 5
b. Current Process ................................................................................................. 5
c. Issues ................................................................................................................. 7
1.1. Proposed System Scope ................................................................................... 8
a. System to be developed ..................................................................................... 8
b. Estimated cost and Duration ............................................................................ 10
Chapter 1- Introduction / Background of the system ..................................................... 13
a. Current Business Introduction .......................................................................... 13
History ........................................................................................................................ 13
Process ...................................................................................................................... 14
Issues ........................................................................................................................ 16
b. Proposed System Scope .................................................................................. 18
1. System to be developed ................................................................................... 18
Literature Review .......................................................................................................... 21
a. Methods ........................................................................................................... 21
Structured Systems Analysis and Design Method (SSADM) ..................................... 21
The Dynamic Systems Development Method (DSDM) .............................................. 21
Comparison between SSADM and DSDM ................................................................. 22
Strengths and Weaknesses of DSDM ........................................................................ 22
Strengths and Weaknesses of SSADM ..................................................................... 23
Recommendation ....................................................................................................... 23
b. Languages ....................................................................................................... 23
Hypertext Preprocessor (PHP)................................................................................... 23
ASP.NET.................................................................................................................... 24
Comparison between PHP and ASP .......................................................................... 24
Strengths and Weaknesses of PHP ........................................................................... 25
Strengths and Weaknesses of ASP ........................................................................... 26
Recommendation ....................................................................................................... 26
c. Database .......................................................................................................... 26

Page | 2
 MySQL ....................................................................................................................... 26
Microsoft SQL Server (MSSQL) ................................................................................. 27
Comparison between MySQL and MSSQL ................................................................ 28
Strengths and Weaknesses of MySQL ...................................................................... 29
Strengths and Weaknesses of Microsoft SQL Server ................................................ 29
Recommendation ....................................................................................................... 30
d. Comparison of Similar Products....................................................................................30
Chapter 2 – Analysis ..................................................................................................... 42
1. Analysis ........................................................................................................... 42
a. Functional Requirements ................................................................................. 42
b. Non Functional Requirements.............................................................................. 43
c. MoSCoW Prioritization ..................................................................................... 45
d. Reasons for functions ...................................................................................... 45
2. Use cases ........................................................................................................ 48
a. System Architecture – Initial Class Diagram .................................................... 49
b. System Architecture – Component Diagram .................................................... 50
Chapter 3 – Design ....................................................................................................... 51
a. Structural Model (Detailed Class Diagram) ...................................................... 52
b. Behavioral Model (Sequence Diagrams) ......................................................... 53
i. Sequence Diagram for Purchase ..................................................................... 53
ii. Sequence Diagram for Order ........................................................................... 54
Chapter 4 – Risk Management Configuration Management.......................................... 55
a. Risk Management.........................................................................................................55
b. Risk Matrix....................................................................................................................61
c. Configuration Management Directory Structure...........................................................62
Chapter 5 – Testing.....................................................................................................................63
5.1 Test Schedule................................................................................................................63
Chapter 6 – Implementation........................................................................................................77
1. Deployment Diagram (Implementation)...........................................................................77
2. Data Migration.................................................................................................................78
3. Training............................................................................................................................82
Chapter 7 – Conclusion...............................................................................................................88

Page | 3
 Evaluation against Aims and Objectives.............................................................................88
Evaluation against Similar System Comparison...................................................................90
Evaluation against Justifications Made.................................................................................92
Evaluation against Project Plan............................................................................................95
Future Amendments............................................................................................................96
References..................................................................................................................................97
Appendix......................................................................................................................................99
Requirements Catalogue...................................................................................................99
Use Case descriptions.......................................................................................................100
Detailed Class Definitions..................................................................................................102
Test Script.................................................................................................................................104
User Guide................................................................................................................................213
System Code.............................................................................................................................224

Page | 4
 Project Proposal

I. Current Business Introduction

a. History

ME (Myanmar Elepha shoes and slipper Co. Ltd) is a largest shoes store headquartered
in Yangon, Myanmar that sells shoes from slippers to athletic shoes to boots and shoe
accessories, including insoles, socks, shoelaces, shoe horns, shoe polish, etc. Myanmar Elepha
was founded by 5 founders in January 2001 to sell different kinds of shoes, boots and slippers.
ME sells high quality footwear for the entire family, specializing in athletic shoes, orthopedic
shoes, designer women’s shoes, toddler, children shoes, formal men’s shoes, slippers, sandals
and accessories. In 2001 there is only one main retail store, located at No.103 Pyay Road next
to KBZ bank, Kamayut Township, Yangon. In 2005, ME start opened its branches in Bogyoke
Market and Sein Gayhar supermarket. From 2008 to 2016, due to rapidly increasing sales, ME
expanded branches with 10 locations in Yangon and Mandalay. There are eight branches in
Yangon shopping centers such as Junction Square, Junction City, Taw Win Centre, Gamone
Pwint(San Yeik Nyein), Hledan Centre, Junction Maw Tin, Ocean shopping mall and Dagon
Centre and two branches in Mandalay.

b. Current Process

 Purchase from supplier

Myanmar Elepha retail store operations involve a number of operational processes

performed on a continual basis by different members of a retail store team. Shoes and
slippers are ordered directly from overseas. Alibaba, Nike, Inc and C&A Shoes are the
main suppliers since 2001 and U Kyaw Zin Oo who is the leader of Timber Land Company
join the company as a partner in 2003. Retail employees regularly take stock of inventory
they have on hand, inventory in storage areas.

Page | 5
 Customer Service

Customer Service is the core element of retail store operations and holds the entire
workflow together. The fundamental purpose of retail store is to provide an outlet for
customers to view, handle and purchase items, which means all activities in a retail store
ultimately revolve around customer service. ME give sufficient services to customers.
Giving a cup of tea is one of the services of ME retail store when the customers come to
the store.

 Payment

Manual system is currently used as payment for ME retail store. Cash sales are tracked
and recorded in a bookkeeping system. Cash receipts include more than just bills and
coins, checks and credit card also are considered cash sales for the purpose of
bookkeeping. Paper, notebook, pen and pencil are always used by the cashier. A look at
a receipt tells the amount of cash collected, the type of product sold, the quality of product
sold, and how much sales tax was collected.

 Promotion

Due to rapidly increasing competitors, ME started doing sales promotion in 2014.

Promotion are always held on Burmese and international holidays. Shoes and slippers are
sold with the latest lowest price on promotion days. Lucky draws and some small activities
such as game competitions are also included in promotion. Promotions are often
announcing in newspapers, magazines, on the TV and radio, on the internet and on packs.

 Delivery

ME delivery process start executing in 2014. Customers can order shoes and slippers by
phone. They can search various types, brands and colors in Myanmar Elepha Facebook
page and newspaper advertisements. Foot’s size is needed to told to staffs and changing
shoes back is allowed for inconvenience of shoes sizes. Customers have to wait for 3 or
4 days for their orders. In current system, the retail store has integrated a single payment
system cash on delivery.

Page | 6
c. Issues

 Payment problems

Using manual payment system can reduce cost but it may take several minutes for staffs
to account. Manual system has the disadvantage of decreased efficiency and time
management when compared with computerized system. Customers have to wait for a
long time when the cashier records the items in the book and write the receipt of product.
Furthermore, the potential for human error is greater when the staffs are manually
accounting procedures.

 Delivery issue

Consumers often ask ME about orders when the delivery time is longer than they
expected. One of the major issues is the logistical complexity, which consumes huge
amount of capital and time to solve it. It’s important that customers have realistic
expectations of when to expect their orders. Delivery times hidden in small print of the
delivery terms isn’t enough. Sometimes ME lost loyal customers’ information which are
recorded in the book. Manual recording system always give headache to the company
when the ordered item is ready to deliver.

 Order Issue

Nowadays, too many online shops and deliveries are rapidly increased and today’s youths
are mainly focus on online shopping. The company’s profit was obviously sink when the
online shopping become popular. As the ME retail store currently process offline shopping
and customers can order the products only by phone or email. Sometime, the staff didn’t
receive the order email and the customers thought that their order emails were
successfully sent to the company. When the ordered items were not arrived to them, they
started contacting to the company and the issues were begun. There is neither online
website nor Facebook chat box for customers to orders the products. ME still using
traditional delivery system. Single payment system is currently used for ordering the
products. Online payment system is not available yet.

Page | 7
1.1. Proposed System Scope

a. System to be developed

Supplier Registration
In the business field, relationship between suppliers and retailer is very important.
In order to firm the relationship and develop the business, supplier registration is an
essential requirement for retailer. This process and system will protect both organization
and business partner as the retailers adapt to changes in federal compliance and billing
regulations. Existing and potential vendors are required to register online so ME can
leverage the single, centralized system to enhance ME’s vendor interaction. Supplier
information give company and representatives exposure to the buyers and allow ME to
maintain important information for ME existing and potential vendors.

Purchase
Purchasing is a very important process in retail business. On the other hand, the
retailer need to purchase the products from the supplier easily. ME currently order and
purchase products from oversea. ME needed to use the computerize system to contact
the supplier easily and conveniently. Finding and qualifying suppliers was one of the most
frequent responses. All the challenges procurement professionals face with suppliers,
simply finding them was the biggest one. Still, some supplier may not offer discounts or
insist that certain surcharges be included in the price. So that, ME need to find the right
suppliers who could provide the product they need according to ME’s specifications.

Product Registration
ME need to develop the product registration process. Product information is
needed to collect easily for the retailer. It is a valuable business asset that can be bought,
sold, transferred or licensed like any other property. It also provides the basis for taking
legal action and add value to the product. The time and money saved on data entry
administrative tasks can be used for better the event, contact more sponsors, prepare
more activities, reply faster to customers. Stock in and stock out monthly update records
are tracked in the product registration.

Page | 8
Customer registration
Online customer registration should be developed for ME retail business.
Customers can sign up online when and where is most convenient for them in just a few
minutes without having to print, manually fill out and send paper forms. Online registration
provider will ensure ME have all the necessary information to answer immediately to any
of the payment related questions a customer might have. Instead of writing a cheque or
counting cash at the front line, customer can simply enter their credit card detail online to
securely complete their transaction in seconds. Once the payment is processed,
customers will then receive a receipt confirming they are signed up for their desired event
and their payment has been securely processed and accept. With flexible pricing options,
customers can be incentivized and rewarded with discount if they sign up by a specific
date. The main reason for customer register is to avoid warranty claim issues.

Delivery
The ordered items must be delivered in promise time and the computerized system
should be developed. Delivery date and time should be recorded in the computer because
computerized system is more secure than manual system. Customer’s information is very
important when the ordered item is delivered to him/her. Computerized system can restore
and backup the old and new customer’s information so that it is easy to use.

Order

Today’s customers are influenced and controlled by online shopping. ME retail

store is willing to do online website and application for old and new customers. It is more
convenient for busy customers who cannot give enough time to shop. Customers can
order the products only by telephone and online ordering system is not available yet. So
that, ME retail store willing to do online shopping page for new and old customers in order
to order the products conveniently. In order to develop ME shoes and shoe accessories
retail store, manual systems should be reduced and computerized systems to be
developed. When the cashier complete tasks manually, the possibility of error increases
largely. It is easy for a human to transpose numbers to make other seemingly minor
mistakes that could have far-reaching consequences. Computers, on the other hand,
simply follow through with commands, making it less likely a mistake will occur. First of all,
payment system is a fundamental system to be developed. Customers have to wait while

Page | 9
 the cashier writes cash sales and customer details. Computerized system eliminates many
cumbersome and time consuming manual processes.

Aims and Objectives

Aims of the project are

 To increase company’s profit

 To get more and more customers
 To get customers’ trust and loyalty
 To get biggest name among the competitors
 To stand company long last

Objectives of the project are

 Analysis the system to reduce errors

 Change manual system to computerized system for payment
 Create online shopping website and application
 Develops the payment system for delivery
 Develops design for get attraction
 Implement coding for the system
 Execute testing for finding errors
 Perform training to understand about the system

b. Estimated cost and Duration

Project Duration
The project must take for 9 months durations. See Work Breakdown structure for
detail information.

Page | 10
Page | 11
Estimated Cost

Software Cost

No Name Unit Price Total Amount

1 Word 5 USD 700 USD 3500
2 Browser 2 Free Free
3 MySQL 1 USD 2000 USD 2000
4 Sublime Text 2 USD 80 USD 1600

Hardware Cost

No Name Unit Price Total Amount

1 Desktop 5 USD 700 USD 3500

2 Laptop 2 USD 800 USD 1600

3 Thermal Printer 3 USD 400 USD 400

4 Projector 1 USD 500 USD 500

5 Barcode scanner 3 USD 250 USD 750

Page | 12
 Chapter 1- Introduction
I. Introduction/ Background of the system

a. Current Business Introduction

History

ME (Myanmar Elepha shoes and slipper Co. Ltd) is a largest shoes store headquartered
in Yangon, Myanmar founded in January 2001 by 5 founders, U Aung Soe Khine, Daw Myat Noe
Pwint, U Min Khant Tun Naing, U Kaung Htet Naing and Daw Pwint Phyu Lei Naing that sells
shoes from slippers to athletic shoes to boots and shoe accessories, including insoles, socks,
shoelaces, shoe horns, shoe polish, etc. ME sells high quality footwear for the entire family,
specializing in athletic shoes, orthopedic shoes, designer women’s shoes, toddler, children shoes,
formal men’s shoes, slippers, sandals and accessories. There are various types of shoes and
slippers brands including NIKE, ROXY, NEW BALAN, VANS, CONVERSE, ADIDAS,
BIRKENSTOCK, EARTH ORIGINS, PROPET, K-SWISS, NATURALIZER and so on. Shoes
accessories include Aglet, Buckle, Crampons, Dubbin, Greeper laces, Lock lacers, Shoe polish,
Shoehorn, Shoelaces, sock, shoe tree, snow skates, shoe buckle and so on. In 2001, in its first
year in business, ME sold 300 pairs of running shoes grossing $1000. By 2002 the fledgling store
had acquired a full-time employee, and sales reached $ 4000. Within a few years, ME had hired
five staffs for marketing products. ME’s marketing commercial for its products received
widespread critical acclaim. In 2003, ME got bestselling product award from Thailand. In 2001
there is only one main retail store, located at No.103 Pyay Road next to KBZ bank, Kamayut
Township, Yangon. In 2005, ME start opened its branches in Bogyoke Market and Sein Gayhar
supermarket. From 2008 to 2016, due to rapidly increasing sales, ME expanded branches with
10 locations in Yangon and Mandalay. There are eight branches in Yangon shopping centers
such as Junction Square, Junction City, Taw Win Centre, Gamone Pwint(San Yeik Nyein), Hledan
Centre, Junction Maw Tin, Ocean shopping mall and Dagon Centre and two branches in
Mandalay. ME’s goal is to get the biggest name among the competitors and increase more and
more customers in the future.

Page | 13
Process

 Purchase from supplier

Myanmar Elepha retail store operations involve a number of operational processes

performed on a continual basis by different members of a retail store team. Suppliers are
essential to almost every business. Without suppliers the retailer has no idea what he will
be paying for the products. Consequently, he will not know how much profit he can make
or if indeed he can make any profit at all. Shoes and slippers are ordered directly from
overseas. Alibaba, Nike, Inc and C&A Shoes are the main suppliers since 2001 and U
Kyaw Zin Oo who is the leader of Timber Land Company join the company as a share
partner in 2003. ME buy shoes and accessories from Nike, Inc that supply worldwide
shoes retail stores. The rest comes from high-quality supplier in the EU, Brazil and
Thailand. Shoes and shoe accessories are ordered from C&A Shoe and slippers are
ordered from Alibaba Co Ltd. The relationship between share partners go without a hitch.
Share partner and company leader has a mutual understanding from the beginning of the
business year to today. Customizing company procedures to suit the own management
styles and the specific needs of their individual outlets, managers place orders with
suppliers either on a regular basis or when they reach an optimum re-order point for a
specific item to ensure their outlets are always fully stocked.

 Customer Service

Customer Service is the core element of retail store operations and holds the entire
workflow together. The fundamental purpose of retail store is to provide an outlet for
customers to view, handle and purchase items, which means all activities in a retail store
ultimately revolve around customer service. ME give sufficient services to customers.
Giving a cup of tea is one of the services of ME retail store when the customers come to
the store. Patience is not only a virtue in customer service, it is a necessary skill in order
to deliver excellent service. The retail store also helps customers to find what they are
looking for without a problem. ME always allow customers to present their entire case
before speaking, listen to what the customer is saying to try to determine the real issue
and take the time to review the information with the client to be sure. ME’s customer
service associate also knows when it is necessary to send the issue to a higher level and

Page | 14
 stays on the line with the client until someone at the next level picks up the phone.
Moreover, ME staffs used to smile as saying goodbye and encourage the customer to
come again.

 Payment

Manual system is currently used as payment for ME retail store. Cash sales are tracked
and recorded in a bookkeeping system. Bookkeeping for ME involves tracking sales,
expenses, payables, receivables and inventory. ME always track the quantity and cost of
all incoming shipments as well as the quantity and sales price of each item sold. Cash
receipts include more than just bills and coins, checks and credit card also are considered
cash sales for the purpose of bookkeeping. Paper, notebook, pen and pencil are always
used by the cashier. ME sort and store all paperwork, receipts and payments in 12
separate months. A look at a receipt tells the amount of cash collected, the type of product
sold, the quality of product sold, and how much sales tax was collected. All transaction
dates and payment details are always recorded and weekly income and expenditure
records are always summarized.

 Promotion

Today, consumers have become more deal oriented. In the current economy, consumers
are demanding lower prices and better deals. Sales promotion can help attract today’s
more economy-oriented consumers. Due to rapidly increasing competitors, ME started
doing sales promotion in 2014. Promotion are always held on Burmese and international
holidays. Shoes and slippers are sold with the latest lowest price on promotion days. Lucky
draws and some small activities such as game competitions are also included in
promotion. Buy-One-Get-One-Free which is one of the selling technique to attract
customers. This is known as a PREMIUM sales promotion. For shoes accessories,
customers can get one free if they buy one. Website and social media are the main
supporters of ME sales promotion. Promotions are often announcing in newspapers,
magazines, on the TV and radio, on the internet and on packs.

Page | 15
 Delivery

ME delivery process start executing in 2014. Orders are accepted by phone and email
and customers can search various types, brands and colors in Myanmar Elepha Facebook
page and newspaper advertisements. Customers need to choose to have their order
delivered to any branch of ME stores within an estimated 3-6 working days for free.
Customers need to told their foot’s sizes to staffs and changing shoes back is allowed for
inconvenience of shoes sizes. Customers have to wait for 3 or 4 days for their orders.
Once the customers’ order has arrived at store the company will send them an email or
text informing them that their orders are ready for collection. When their orders will be
arrived to their home, customers have to bring a copy of their order confirmation email or
text message and one of the following forms of ID: A Photo ID such as driving license, or
a utility bill with their name and address on which matches the name and billing address
used when placing their orders. In current system, the retail store has integrated a single
payment system cash on delivery.

Issues

 Payment problem

Single payment system is currently used for ordering the products. Online payment
system is not available yet. Using manual payment system can reduce cost but it may take
several minutes for staffs to account. Manual system has the disadvantage of decreased
efficiency and time management when compared with computerized system. A lack of
security is another common disadvantage to manual accounting. Company is unable to
prevent employees from reviewing sensitive data in paper ledgers and journals. Files
copied and stored on a computer may also be less secure. Accounting processes that use
paper journal and ledgers or similar tools requires copious time to complete task.
Customers have to wait for a long time when the cashier records the items in the book
and write the receipt of product. Moreover, the potential for human error is greater when
the staffs are manually accounting procedures. Common errors are entering information
into incorrect accounts, transposing figures or recording information backwards. Staffs
researching error will often spend several hours to locate and correct error. Staffs
sometimes carelessly write the customer’s name or payment details incorrectly in the

Page | 16
 receipt. Company occasionally faces such kinds problems. In addition, traditional backup
system can waste copious amount of time for customers.

 Delivery issue

Consumers often ask ME about orders when the delivery time is longer than they
expected. One of the major issues is the logistical complexity, which consumes huge
amount of capital and time to solve it. It’s important that customers have realistic
expectations of when to expect their orders. Delivery times hidden in small print of the
delivery terms isn’t enough. Sometimes ME lost loyal customers’ information which are
recorded in the book. Manual recording system usually give headache to the company
when the ordered item is ready to deliver. Human error also plays a role in inaccurate
records; manual recording can be tiresome and tedious, causing bookkeepers to make
mistakes. Sometimes, some records that keep in the book are lost and ruined because of
the small accident by careless staffs. The missing customers’ information couldn’t help the
staff to deliver the items easily and conveniently. And also, the staff couldn’t deliver the
order items if he doesn’t know exactly where to deliver.

 Orders issue

Nowadays, too many online shops and deliveries are rapidly increased and today’s youths
are mainly focus on online shopping. The company’s profit was obviously sink when the
online shopping become popular. The ME retail store currently process offline shopping
and customers can order the products only by phone or email. Sometime, the staff didn’t
receive the order email and the customers thought that their order emails were
successfully sent to the company. When the ordered items were not arrived to them, they
started contacting to the company and the issues were begun. Furthermore, customers
currently have to find the shoe’s size, color, price and design in newspaper and Facebook
page. Generally, it is a little bit difficult for the customers in discovering the products they
wanted among many variety of ME products and brands in newspaper and Facebook
page. There is only one staff for replying the customers’ orders. Only one staff cannot
reply all the orders in the same time so that more staff are required for ME. There is

Page | 17
 neither online website nor Facebook chat box for customers to orders the products. ME
still using traditional delivery system.

b. Proposed System Scope

I. System to be developed

Supplier Registration
In the business field, relationship between suppliers and retailer is very important.
In order to firm the relationship and develop the business, supplier registration is an
essential requirement for retailer. This process and system will protect both organization
and business partner as the retailers adapt to changes in federal compliance and billing
regulations. Existing and potential vendors are required to register online so ME can
leverage the single, centralized system to enhance ME’s vendor interaction. Supplier
information give company and representatives exposure to the buyers and allow us to
maintain important information for ME existing and potential vendors.

Purchase
Purchasing is a very important process in retail business. On the other hand, the
retailer need to purchase the products from the supplier easily. ME currently order and
purchase products from oversea. ME needed to use the computerize system to contact
the supplier easily and conveniently. Finding and qualifying suppliers was one of the most
frequent responses. All the challenges procurement professionals face with suppliers,
simply finding them was the biggest one. Still, some supplier may not offer discounts or
insist that certain surcharges be included in the price. So that, ME need to find the right
suppliers who could provide the product they need according to ME’s specifications. The
need for increased access to accurate data seems to correspond with an increasing
reliance on software and tech tools in the supply chain. Impulse buying, making emotional
decisions based on the preference of suppliers and literally phoning in an order are often
the most common causes of procurement errors, especially if the company is a rapidly
growing startup. When a company launches, decision-makers usually want to ensure
everything is ordered and in place all at once. Hitting the ground running often means
ignoring the cautionary steps in a procurement process and may result in cost overruns in
inventory before revenue streams can compensate for these purchases. A good,

Page | 18
comprehensive procurement system allows for both prompt orders and more thoughtful
decision making.

Product Registration
ME need to develop the product registration process. Product information is
needed to collect easily for the retailer. It is a valuable business asset that can be bought,
sold, transferred or licensed like any other property. The system provides an insightful
reporting into payments received and due, refunds given, multi-event analysis and all other
reporting tools essential to efficiently manage a successful event. It also provides the basis
for taking legal action and add value to the product. The time and money saved on data
entry administrative tasks can be used for better the event, contact more sponsors,
prepare more activities, reply faster to customers. Stock in and stock out monthly update
records are tracked in the product registration. It makes the retailer to understand when
stock is going in and out and can also help lower costs, speed up fulfillment, and prevent
fraud. Product Registration is important to maintaining the right balance of stock in the
warehouse.

Customer registration
Online customer registration should be developed for ME retail business.
Customers can sign up online when and where is most convenient for them in just a few
minutes without having to print, manually fill out and send paper forms. Online registration
provider will ensure ME have all the necessary information to answer immediately to any
of the payment related questions a customer might have. Instead of writing a cheque or
counting cash at the front line, customer can simply enter their credit card detail online to
securely complete their transaction in seconds. Once the payment is processed,
customers will then receive a receipt confirming they are signed up for their desired event
and their payment has been securely processed and accept. With flexible pricing options,
customers can be incentivized and rewarded with discount if they sign up by a specific
date. Customers gets the ability to be informed straight to their inbox whenever a new
event of their interest is launched, without having to look for it. Customer register is to
avoid warranty claim issues. The manufacturer can easily contact the customers, if the
customers are registered as an owner of one of the products. Moreover, the retailer
already has all of the customer information and proof of purchase so that if something
breaks or is recalled, they can send his new product or needed products to fix certain
items.

Page | 19
Delivery
The ordered items must be delivered in promise time and the computerized system
should be developed. Delivery date and time should be recorded in the computer because
computerized system is more secure than manual system. Customer’s information is very
important when the ordered item is delivered to him/her. Computerized system can restore
and backup the old and new customer’s information so that it is easy to use. Computerized
system can also record the customer order date and payment date so that the staff can
know the exact date of customer’s order and payment. Beside that the staff also know the
exact customers’ address so that he can deliver the ordered items in promise time. Thus,
staff must record customer information by computerized system. So that the customer
information can’t be able to be ruined and no more delay work time will be wasted.

Order

Today’s customers are influenced and controlled by online shopping. ME retail

store is willing to do online website and application for old and new customers. It is more
convenient for busy customers who cannot give enough time to shop. Customers can
order the products only by telephone and online ordering system is not available yet. So
that, ME retail store willing to do online shopping page for new and old customers in order
to order the products conveniently. And also, customers don’t need to find the shoe’s size,
color and design in newspaper and Facebook page. They can easily search the product
detail in the search box by clicking keywords. Besides that, customers don’t need to send
order email to the company and no more issue will be happened. Some online shoppers
commonly use a credit card or a PayPal account in order to make payments and some
shoppers enjoy billing to mobile phones and some prefer to cash on delivery. However,
ME also willing to do the online payment system for order. ME also require a staff who will
reply customer’s order on Facebook. Manual systems must be reduced and computerized
systems should be developed for the improvement of the company. The possibility of error
increases largely when the manual tasks are completed by the cashier. It is easy for a
human to transpose numbers to make other seemingly minor mistakes that could have
far-reaching consequences. Computers can do all tasks including payments, printing
receipts for customers and recording customers’ info. Computers, on the other hand,
simply follow through with commands, making it less likely a mistake will occur. First of all,
payment system is a fundamental system to be developed. Customers have to while the

Page | 20
 cashier writes cash sales and customer details. It may waste the amount of important time
especially for busy customers. A computer can do in seconds what may take human hours
to do. The advantages of computerized system include fast, complex reporting. Using
accounting software, it becomes much easier for different individuals to access accounting
data outside of the office, securely. Computerized systems can produce invoices,
purchase orders and other documents more quickly. The system will require staff to be
trained to use new skills, which can make them feel more motivated. The latest data can
be saved and stored in offline locations so it is safe from natural and man-made disasters
like earthquakes, fires, floods, arson and terrorist attacks. In case of a disasters, the
system can be quickly restored on other computers.

Literature Review
a. Methods

Structured Systems Analysis and Design Method (SSADM)

Structured systems analysis and design method(SSADM), is the methodology of

projecting and analysis of information systems. It is structured and completely difficult to use. It
can produce exact and well-documented information systems when it is used skillfully. SSADM is
computer application development method which is widely used in the UK. It is often used as a
requirement for government computing projects. SSADM divides into modules, stages, steps and
tasks. A framework is provided for describing projects in order to manage the project.

The Dynamic Systems Development Method (DSDM)

DSDM is an agile software development methodology which is used by information

system professionals to develop software's projects which is derived from RAD
methodology. It is a framework of representing much of the recent knowledge about project
management. The software development community rooted DSDM, but the convergence of
software development, process engineering and thus the DSDM framework has been changed
by the business development project in order to become a general framework for complicated
problem resolving tasks. It is an incremental method which is generally based on the Rapid
Application Development(RAD) methodology. It looks perfectly appropriate for software

Page | 21
development that place a high significance on the user interface or usability parts of products.
DSDM fixes cost, quality and time at the beginning.
Comparison between SSADM and DSDM
SSADM
 Is based on the traditional structured
programming techniques
 Suitable for big project
 Does not involve client
 High cost of change
 View programming as construction
 Heavy process and documentation
 Focus on completing modules at
different large milestones
 Use upfront research to inform design
 Provide detailed and elegant
deliverables to developer
Strengths and Weaknesses of DSDM
Strength
 Iterative-incremental process
 Early and frequent releases
 Smooth transition from stage to stage
 Design-based development
 Carefully worked-out process
 Reversibility of changes
 Active user involvement
 Flexible and configurable process
DSDM
 Is based on RAD
 Suitable for small project
 Clients are highly involved in the
development of the project
 Low cost of change
 View programming as design
 Light process and documentation
 Focus on completing stories in short
iteration
 Cannot do all research up front
 Smaller deliverable produced much
more frequently
Weakness
 Licensing cost
 Relatively high obstacle to entry
 Culture shift in organization
 Adopts a dynamic, project led
approach to both data structures and
processes
 Does not concentrate on the
fundamental importance of corporate
data management
 Stringent constraints on time and
resources
 Lack of formalism
Page | 22
Strengths and Weaknesses of SSADM

Strength
 Multiple angles of analysis
 Less chance for misunderstanding
 Project planning improved
 Identifies clearly defined stages and
modules
 Maintenance is made easier
 Remove redundancies
 Coherent design
Weakness
 Time-consuming and possibly
expensive
 Not flexible
 Lack of user involvement
 No user involvement in design
process
 Hard to define boundaries of a system
 Does not include documentation for
each steps
 Requirements will not change during
the development of a project

Recommendation

In summary, DSDM is the most convenient method for the project. It is a useful approach
that helps to develop a robust system. The methodology helps keep a project from falling and
also helps in developing requirement satisfied systems. The results of development are clearly
and rapidly visible. Basic functionality is delivered hastily, with more functionality being delivered
at usual intervals. It can collaborate effectively with customers’ requirements. System aims at
budget and specific delivery. The ability of the users in order to affect the project’s direction.

b. Languages

Hypertext Preprocessor (PHP)

PHP originally derived from Personal Home Page, but now stands for the recursive
acronym PHP: Hypertext Preprocessor. PHP is a server-side scripting language used to create
dynamic and interactive HTML Web pages. It also used as a general-purpose programming
language. PHP code can be inserted into the HTML of a Web page. When a PHP page is
accessed, the PHP code is read or “parsed” by the server the page resides on. The output from

Page | 23
the PHP functions on the page are typically returned as HTML code, which can be read by the
browser. A lot of syntax of PHP is borrowed from other languages such as C, Java and Perl.
However, PHP has a number of unique features and specific function as well. An HTML page
includes a PHP script is given a file name suffix of “.php” “.php7,” or “.phtml”. Like ASP, PHP can
be thought of as “dynamic HTML pages,” since content will vary based on the results of
interpreting the script. PHP is very easy for beginner and also offers many advanced features for
programmers. PHP is free and offered under an open source license.

ASP.NET

ASP.NET is an open-source server-side web development tools offered by Microsoft

which provides a programming model, a comprehensive software infrastructure and various
services required to build up robust web applications for PC, as well as mobile devices. Programs
like Visual Studio.NET and Visual Web Developer allow Web developer to create dynamic
websites using a visual interface. It allows programmers to build dynamic web sites, web
applications and web services. Programmers can write their own code and script and incorporate
it into ASP.NET website as well. ASP.NET is built on the Common Language Runtime(CLR),
allowing programmers to write ASP.NET code using any supported .NET language. ASP.NET
works on top of the HTTP protocol, and uses the HTTP commands and policies to set a browser-
to-server bilateral communication and cooperation. The ASP.NET application codes can be
written in any of programming languages such as C#, Visual Basic.Net, Jscript, J#.

Comparison between PHP and ASP

PHP
 an open source technology which can
used for free
 a mix between a programming
language and a web framework
 PHP will work well in any kind of
platform and server
 an easier language for beginners to
pick up.
 PHP code run much quicker
ASP.NET
 a Microsoft platform that is expensive
in price
 a straight application framework
 ASP.NET can be used only with
Internet Information Server (IIS)
 doesn’t allow irregularities in its code
while still being able to run

Page | 24

 no additional steps are required to
see the changes
 most tools associate with the program
are mostly open source software and
don’t need to pay for them.
 C/C++ as a bese language and most
syntax are similar to each other
 Can run in Windows, Solaris, Unix
and Linux
Strengths and Weaknesses of PHP
Strength
 PHP has large support community of
programmer
 PHP is great for large projects like
Facebook, White House website
 PHP is highly effective at accessing
and communicating with various
database
 It’s highly scalable and can be easily
customized according to users’ need
 Low cost, easy to learn, code and pick
up
 PHP has both procedure programming
language and OOP language features
 ASP uses an overhead server and is
uses a COM based architecture
 needs to be compiled each time the
code is modified
 need to buy additional tools to work
with its program.
 Syntax and interface of Visual Basic
Programming
 Only works with Windows based
program
Weakness
 It is generally not suitable for making
desktop application
 Compared to other languages, PHP
applications tend to run slower
 It allows customization that causes
bugs and poor coding
 PHP error handling is traditionally
considered poor which mean it can
take more time to discover
 Not suitable for large application
 Confusing between arrays and hash
tables
Page | 25
Strengths and Weaknesses of ASP

Strength
 It is owned by Microsoft
 It informs developer if they made any
mistake in coding before compile
 ASP.NET is highly scalable
 An excellent UI for developer
 Support all programming languages
and works well with either app or C#
 Works extremely well with Windows
 Fast development with a lot of pre-
coded options
 Excellent platform for excellent
applications
Weakness
 Coding using ASP.NET is complicated
and it requires lot of learning and effort
 Smaller support community
 It operates only on a Microsoft server
 Based on closed source technology
 Not as good as PHP for website
development
 It is expensive in price because of its
Microsoft license
 Will have to be compiled, thus
increasing the development time
 Tools that can be used with ASP.NET
are not available for free

Recommendation

There are many reasons that developer should use PHP for server side programming,
firstly it is a free language with no licensing fees so the company can save the budget. PHP can
also interact with several different database languages including MySQL. PHP can also run on
Windows, Linux and Unix servers. PHP also has very good online documentation with a good
framework of functions in place. This makes the language quite easy to learn and very well
supported online. The developers are able to do a lot of things with their website by learning the
simple functions.

c. Database

MySQL

MySQL pronounced either “My S-Q-L” or “My Sequel”, is an open source relational
database management system which is based on the structure query language(SQL). It is used

Page | 26
for adding, removing and modifying information in the database. MySQL is used by WordPress
to store and retrieve all of users’ blog information. It runs as a server and allows multiple users to
manage and create numerous databases. MySQL is the world’s most popular open source
database. MySQL has become the leading database choice for web-based applications, used by
high profit web properties including Facebook, Twitter, YouTube, Yahoo! and many more. MySQL
runs on virtually all platforms, including Linux, UNIX, and Windows. Although it can be used in a
wide range of applications, MySQL is most often associated with web-based applications and
online publishing and is a central component of an open source web application software stack
called LAMP.

Microsoft SQL Server (MSSQL)

Microsoft SQL Server is a relational database management system or RDBMS developed

by Microsoft that supports a wide variety of transaction processing, business intelligence and
analytics applications in corporate IT environments. These applications may run on the same or
a different computer. It is used to manage and store information. It’s one of the three market-
leading database technologies, along with Oracle Database and IBM’s DB2. SQL is a special-
purpose programming language designed to handle data in a relational database management
system. A database server is a computer program that provides database services to other
programs or computers as defined by the client-server model. Therefore, a SQL Server is a
database server that implements the Structured Query Language (SQL). SQL Server is tied to
Transact-SQL (T-SQL), an implementation of SQL from Microsoft that adds a set of proprietary
programming extensions to the standard language. SQL Server supports different data types,
including primary types such as integer, float, decimal, char, varchar, binary, text among others.
It also allows user-defined composite types (UDTs) to be defined and used. It also makes server
statistics available as virtual tables and views. There are many different version of Microsoft SQL
Server, catering for different workloads and demands.

Page | 27
Comparison between MySQL and MSSQL
MySQL MSSQL
 It was owned and sponsored by a  It is owned by Microsoft
single for-profit firm, the Swedish
company MySQL AB, now owned by
Oracle Corporation
 It is available for free since MySQL is
an open source.
 MySQL does not support XML
 It requires very less disk space
 It is a simple language that can be
easily used by beginners
 It can be installed in Linux and Unix
 MySQL offers only updateable views
 MySQL provides only table level
security
 Auto tuning is not supported in MySQL
 It does not contain management tools
based on GUI
 It is not an open source and payment
has to be made to use SQL Server
 SQL Server supports XML
 It requires more disk space
 It is a complex language that requires
more understanding to work with
 It does not work with Linux and Unix
 SQL Server offers indexed views
which are much more powerful,
performance wise.
 SQL Server provides column level
security
 Auto tuning is supported in SQL
Server
 It provides management tools based
on GUI
Page | 28
Strengths and Weaknesses of MySQL
Strength
 MySQL is an open source software
and free to use it.
 It has great performance on simple
queries
 It is an easy database to work with
 It is less expensive than most other
database options on the market
 MySQL products remain solid
 Easy to setup and configure
Strengths and Weaknesses of Microsoft SQL Server
Strength
 Witness can be any edition of SQL
server
 Database level High Availability
 High safety only require Standard
Edition
 Auto tuning is supported in SQL
server
 SQL Server provides triggers
Weakness
 Stored procedure and trigger is limited
 It suffers from poor performance
scaling
 MySQL is not for large sized data
 It is oracle-owned
 It is not as mature as other relational
database management systems
 Designed for large MySQL farms
Weakness
 MS SQL is a closed source and the
developer has to purchase it
 Cannot mirror system databases
 Database must be in full recovery
 High performance requires Enterprise
Edition
 SQL server can cost a lot depending
on the options and equipment needed
to host the database application
Page | 29
  Stored procedures and full join facility  Require to learn a difficult language
are offered in SQL Server and setup for the Microsoft SQL Server
environment

Recommendation

Compare to Microsoft SQL Server, MySQL is recommended to be used because it has

many benefit than MSSQL. Firstly, MySQL is an open source and free to use it. A good benefit of
using MySQL is that it is easy to find help. If the developers get stuck on something, there are
countless places to find their solution. There are tens of thousands of tutorials, help docs and
discussions about it. Furthermore, anyone can learn the basics and get up and running very
quickly with MySQL. The user doesn’t have to spend as much time and money either training
existing staff, or hiring developer with fancy certifications. MySQL can also handle everything from
a megabyte of data to terabytes. For the above reason, MySQL is more convenient for the
developers to use.

d. Comparison of Similar Products

SNEAKERHEAD.com

Page | 30
 http://www.sneakerhead.com

Sneakerhead.com is an internet retail store located in California devoted to offering

unique customer service, fashionable footwear, and an exceptional experience. They are fervent
about sneakers and continually attempt to carry the finest selection available anywhere including
athletic shoes, limited editions, retro classics and lifestyle models. They sell various types of
brands including Nike, Air Jordan, Puma, Timberland, Adidas and a sophisticated customer
service system, Sneakerhead.com has one of the best reputations among online sneaker
retailers.

Famous footwear

www.famousfootwear.com

Famous Footwear is the place for athletic and casual shoes for the whole family
from hundreds of name brands. Customer will find styles for women, men and kids from
brands like Nike, Converse, Vans, Sperry, Madden Girl, Sketchers, ASICS and more. With
over 1,000 stores nationwide and even more selection online at Famous.com. Establish
in 1960 as a single store, “Famous” is regarded as both a forerunner and champion of the
trend towards the establishment of discount shopping malls in America. Famous Footwear

Page | 31
 is a leading family footwear destination for the famous brands the customers know and
love.

Navigation

In this website, dark color is used in the heading and In this website, the heading is designed by red color
white color is used in the navigational text. In this and the navigational text use white color. The text’s
navigation, drop down menu such as NEW color is matched with the background color and it

ARRIVALS, MEN’S, WOMEN’S, KID’S, APPAREL, make the visitors to see the menu buttons clearly.

GEAR, SALE and BLOG are also included. When Drop down menu such as WOMAN, MEN, GIRLS,
the users move their mouse to a menu items, BOYS, ACCESSORIES, BRANDS, SALE,

different types of brands are appeared. However, too INSPIRATION are also included. Various kinds of
many brand types can be difficult for visitor to search categories are also appeared, when the users move
the types of shoes that they wanted. Heavy drop their mouse to a menu items. In order to make the
down menus takes more than an instant to load upon visitors to read and scan easily and clearly, the items
the hover. are grouped into categories

Home Page

Page | 32
 Famous footwear uses the colorful high quality
For Homepage, SNEAKERHEAD use the slideshow
images to lift the look of their website. They advertise
image to advertise the age of their company,
the colorful pictures of famous brands such as Nike
different types of shoes brands and their company’s
and Converse. Best sellers of the products are also
customer service. Below the slideshow image,
shown in the home page of Famous Footwear. The
various types of new arrivals shoes are advertised
images are matched with the background color and it
with pictures and relevant prices. However,
attract the visitor to buy their products. Their choice
slideshow images often times ignore a visitors need
of images embodies the style and understated
for control and setting their own reading pace. And
elegance of the brand, and the close-up of the famous
also auto-advancing photos in a slideshow may be
brand shoes adds a sensory element that ties into the
very distracting for readers.
brand's promotion of fine fabrics.

Design
Element

For SNEAKERHEAD, the first thing the visitors see This website uses simple design so that visitors can
is the logo. It is large enough for visitors to clearly see the texts, images, prices and categories.
immediately know what site they are viewing. It And also, the font color is matched with the
directly attracts the user’s eyes though a sequence background. The colors that are designed in this
of steps. Using bold and subtle colors is a simple website naturally draws the users’ attention.
way to tell the visitors where to look. Furthermore, Furthermore, the bright color is used in the navigation
different types of fonts say different things about so that the menu buttons are clear to be seen. The
design. purpose of this design is to catch the users’ eyes and
hold their attention instantly.

Page | 33
Color

In this website, the dark color is used in the In this website, the navigation is designed by red color
navigation, the background is designed by grey color and white color is used in the background. The black
and the white color is used for the text. The color that color and blue color are used for the text. Brighter
is used in the background makes complexity for the colors lead the user to feel more energetic as a result
visitors. On the other hand, the background color of their design, which is particularly effective when
does not match with the images of products. they are trying to advertise a product or invoke an
emotional response. The background color for the
screen influences the level of readability.

Page | 34
Menu
Display

In this website, drop-down menus are used to pull all For Famous footwear, they use drop-down menu to
of the brands’ pages in a certain category together in organize categories of footwear and accessories and
one organized element. SNEAKERHEAD’s drop- pull together categories out of sidebar. Furthermore,
down menu is very wide, large in size and styling, so the hover is used in drop-down menu and the drop
it is easy to keep the mouse in focus. Moreover, the down disappears immediately after the user moves
shoes are divided into brands, apparel, gender and the mouse pointer away from the menu. There is no
age. In addition, the drop-down menu color is multiple level in hover menu and the visitors have to
matched with the background color and it make the click their choice. The text color that is used in the
visitors to see the products clearly. drop-down menu doesn’t match with the background
color.

Page | 35
Search Box

In this website, the search box is hidden behind in The search box in FAMOUS footwear looks simple
the magnifying-glass icon. When the users move and submit button is easy to understand for both
their mouse to the magnifying icon, large and wide experienced and inexperienced users. And also the
search box will be appeared. When the users type search box is visible for visitors because it allows the
one keyword in the search box, relevant brands and users to narrow their search by categories. But the
pictures are dropped down. Search is important auto-suggestion seems poor because the user have
function for most of the website so, it can be the to type at least 3 or 4 keywords in the search box and
fastest route to discovery for users. Hidden search then relevant brands with images will be dropped
box makes search feature less noticeable and down.
increases the cost of interaction. However, auto-
suggestion mechanism speeds up the search
process and usable for the customers.

Registration

Page | 36
 In this website, users have to click the registration For Famous footwear, the registration button is in the
icon in the navigation and when the users move their navigation and the users have to click the button to
mouse to the icon, drop-down buttons such as Login, sign up their account. When the users come to the
My Profile, Login Information, My Orders, My website, it should be immediately clear where they go
Reviews, Gift Card, Reward Points, to login and sign up. The registration button in this
SNEAKERHEAD Membership and Sign up button website seems quite small so that the users cannot be
will be appeared. The registration type is simple and able to see clearly. The registration type is a long
quick. The users have to type personal information registration process. The users have to input the
and password to save their account. email, personal information and password step by
step.
Product
Display

Page | 37
The image on the SNEAKERHEAD visually
In this website, they use 5 or more than 5 high-quality
communicate the detail of the product to visitors.
images in one product for different views and zoom is
They use an image that is high-resolution and
not available and the visitors have to click down-arrow
zoom-able, and place it above the fold. And also
in size chart to choose the shoes sizes. Customer
there are 5 images in one product for users to look
Reviews and available color are jointly describe with
in different views. The size chart is also simply and
prices. Famous footwear also have browsing
clear to choose.This website also correctly inform
refinements which shows up alongside categories
the visitors if the shoes size is available or not in size
when the visitors have entered the product-listing
chart. Moreover, they also tell the customers
page and display specific criteria such as size, colour
everything they need to know about the product
and brands.
being sold on the website. Live Chat is also available
which provides customers with chats console
allowing them to seek help regarding products and
services being sold by a business.

Page | 38
Shopping
Cart

The shopping cart in SNEAKERHEAD is a full page Like SNEAKERHEAD, FAMOUS footwear is also a
cart where customers can view all of their items right full page cart. Color, size and delivery method are
on the page with the cart. A link to the shopping cart included in product description. Removable button is
is conveniently located at the top right-hand corner also involved in this shopping cart. In order summary,
of the page. It also calculate the subtotal of the Subtotal and estimated tax will be calculated to find
product automatically. There is also large and clearly estimated total. Well-styled and nicely placed
understandable ADD TO BAG buttons for guiding checkout button is also described in order summary.
the users in the right path. Futhermore, the continue In addition, it also show the kind of payment the
shopping link button is placed below the table of a customers accept
full page shopping cart making it easily searchable
for customers. It also allows removal of an item on
the same page.
Delivery
Service

Page | 39
Ordering from SNEAKERHEAD.com is simple, fast For Famous footwear, online ordering is a step by step
easy and secure. Customers can order the products process. Shoes sizes are required to choose when the
by choosing their sizes and clicking them to their customers order the products. Customers have to

shopping cart. Then, they can click the Checkout click Checkout button to order the products. Famous

button below the shopping cart items to fill in their footwear provides a guest checkout option to its users

shipping information. In checkout process, the which means shoppers are not required to enter a
visitors have to register as a return customer or a truckload of information into forms or create an
guest. Billing Address, Shipping Address, Shopping account to purchase a product from Famous footwear.

Method and Payment method are involved in Personal information such as shipping address, First
checkout progress. When the customers fill in their Name, Last Name, Street Address, Apt/Suite/Etc
shipping information, they have to choose the (Optional), City, State, ZIP, Phone Number and Email
shipping method from the drop down menu. Address are required to fill in the shipping information.
Moreover, they also have to choose the type of credit Famous footwear also offers different shipping speed

Page | 40
 card, fill in the information and security code. Before options such as ‘Standard’, ‘Expedited’ and ‘Rush’
the customers send the orders, they need to check and charges the customer accordingly. Futhermore, it
that their billing address is the same as their shipping also make sure that customers know exactly how
address. Email address is required to fill and they will much they are paying as they go through the checkout
receive an order confirmation email when the process. This feature ensures customers they are not
customers orders the items. Order by phone is also being saddled with any hidden charges. Also, it shows
available in SNEAKERHEAD.com. Customers can shipping charges beneath each product in the cart. In
call 1-866-339-7463 during their normal business payment process, users are required to provide
hours (Monday-Friday:8am-5pm PST and payment details. Famous footwear designed their
Saturday:8am-1pm PST) to order the products. checkout page this way to avoid confusing shoppers
and to save their time.

Conclusion

As a comparison of these two websites, there are some strengths and weakness of both
websites. SNEAKERHEAD use dark and grey background color which makes complexity for the
users. Moreover, the texts that are used in the navigation is not big enough for the visitors to see
clearly. There are too many different types of brands in the drop-down menu which will be difficult
for visitors to search the products they wanted. The slideshow image can improve the advertising
of the products but it may be very distracting for readers. In Famous footwear, the navigation uses
the bright color so that the users can see the button clearly and simply. In order to advertise their
product, they use colorful high-quality images which attracts the customers’ eyes. And also the
images are matched with the background color. This website uses the simple design so that the
visitors can see the texts, images, prices and categories. The search box looks simple and submit
button is easy to understand. The search box is also visible for users but auto-suggestion features
is poor. The registration type looks simple and clear but it takes a certain amount of time to
complete because it is a step-by-step process. To sum up, Famous footwear is more simple,
usable, clear and convenient than SNEAKERHEAD.com and it is recommended to be used.

e.

Page | 41
 Chapter 2 – Analysis
I. Analysis

a. Functional Requirements

Supplier Registration
Supplier registration is a formal process of collecting information of suppliers and
services in order to purchase products. The retailers will send the supplier contact form to
complete that will request basic information about the company.

Purchase
It is the formal process of buying products and services from suppliers or
wholesalers.

Product Registration

Product registration is the process in which, after collecting supplier information in

the database, the retailers have to record the product which should be bought and which
should be sold to the customers. In the other hand, retailer have to fill the information in
the registration form to purchase products from suppliers.

Customer Registration
Customer registration is the process in which, after buying a product, the
customers send their personal information and the product detail to the company or retail
store that sold it. If customers want to buy the product then they must be registered,
unregistered users can’t go to the shopping cart. Users are allowed to input the basis
information such as username, password, telephone number, email address, postcode,
real name and so on.

Order

Order is a process of ordering products from a retail store or a company through a

web page or app. 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.

Page | 42
 Delivery

Delivery is a process of taking goods which the customer order directly from a
company or retail store to the doorstep according to the personal information on the
customers’ order list

b. Non Functional Requirements

i. Global

 Performance

The system ability to meet latency, throughput and resource utilization

requirements. Performance requirement focus on performance issues such as
response time, capacity, and reliability. In order to improve web page’s
performance, minimizing the number of round trips is one of the most important
thing. Reducing scripts and putting them at the bottom of the page can also
improve website performance. Reducing server response time is one of the way
to speed up the site.

 Usability

Usability is the system that assesses how easy user interfaces are to use. The
users are ability to learn the system and complete the tasks. Using beautiful
photography on the website is one of the way to improve the usability and help
make the experience of browsing and shopping more enjoyable.

 Scalability

Scalability is the system’s ability to handle a large amount of data. It is the ability
of a website to continue to function well when it is change in size or volume in order
to meet a user need

Page | 43
  Security

Security is the ability to prevent the information system from disruption and data
loss whether caused by an intentional act. The system must automatically log out
all customers after period of inactivity. The system should not leave any cookies
on the customer’s computer containing the user’s password.

ii. Individual

 Order

Online order can be one of the non-functional requirement if it is not usability. The
first problem that often happen is the response time. Sometime checkout process
can take quite a long time for a website to send a customer’s information to the
credit card processor and receive a response whenever a customer tries to place
an order. Half of internet users expect a page to load in under 2 seconds and are
prone to leave if it takes 3 seconds. And during the 2-10 seconds that it takes to
completely process an order, sometimes customer gets impatient and hits the
submit button again. A customer’s order can come through multiple times and their
credit card can be charged multiple times. In addition, some of customers who
experience problems with a website’s speed will not return for another purchase,
while some are likely to buy from another online store.

 Login

Customers login to the system by entering personal details and select login name
password that will be later user for login into admin area for the shopping. This use
case begins when the user begins to login. User have to inputs his username and
password, and then submits.

Page | 44
  Delivery

Delivery process can be also included in non-functional requirement. The

checkout process needs to be as simple, smooth and quick as possible. If the
online business sites make the user fill out too many forms or perform too many
complicated or repetitive actions, the impatient customer will annoy at checkout
process and leave. Some people are not okay with paying high shipping rates.
High shipping costs increase the price and take away customers’ motivation.
Furthermore, every online shopper expects fast and frees shipping that too in
lowest price.

c. MoSCoW Prioritization

High functional requirement Must Should Could Would

 Supplier Register 
 Purchase 
 Product Register 
 Customer Register 
 Order 
 Delivery 

d. Reasons for functions

Supplier Registration
Supplier Registration is an important process when the retailer starts to purchase
products. It is the system which collect, centralize, and credential vendor information.
The supplier registration process saves time for the staff and make it easier to connect
with the high-performing, global suppliers that the company need. A supplier registration
provides a single access point for current suppliers to update their information, as well as
a means for new suppliers to register to participate in the program. When updates are
needed, the supplier enters the information once, and it is pushed out to all companies
connected to the database. Therefore, supplier registration is a must.

Page | 45
Purchase
Purchasing plays an important role in getting the lowest possible price. This was
often at the expense of a positive relationship with the supplier and usually a trade off with
quality. Nowadays, purchasing is known as having an overpowering impact on the bottom
line of the organization. It has a direct impact on the two forces that drive the bottom line:
sales and costs. Thus, why purchasing process is a must.

Product Register

Product Registration plays an important role in collecting product information for

retailer. One of the advantages of product registration is a valuable business asset that
can be bought, sold, transferred or licensed like any other property. It also provides the
basis for taking legal action and add value to the product. Stock in and stock out monthly
update records can be viewed in the product registration. Therefore, product register is a
must.

Customer Register

The main reason for customer register is to avoid warranty claim issues. Most
products from electronics to kitchen appliances to baby gear all come with warranties of
some sort. When an online product registration is attempted, the consumer would be given
the choice to set the date right by uploading a scanned invoice which would later be
attempted by supported person. Every now and then products have some sort of recall.
The manufacturer can easily contact the customers, if the customers are registered as an
owner of one of the products. Moreover, the manufacturer already has all of the customer
information and proof of purchase so that if something breaks or is recalled, they can send
his new product or needed products to fix certain items.

Order

Ordering process is an important link in any sale process. Order is a must because
it is an efficient method of processing customer orders leads to increased sales. Related
with ordering process is exceptional customer service. Manual processing of orders and
inquiries take up time and money. However, effective order processing reduces time
consumption and overheads. Furthermore, ordering process directly affects the bottom
line.

Page | 46
 Delivery

Delivery plays an important role in the shopping experience of all online shopping
websites. Delivery services should be especially in online business because it increases
not only sales but also customer reachability. Without a delivery strategy, the company
could end up with an unprofitable business. However, some of the customers abandon
the delivery options in the shopping cart because shipping costs made the total purchase
more than expected.

Evaluation

In short, some functional requirements and non-functional requirements are mentioned in chapter
4. Moscow Prioritization and reasons for functions are also described in this chapter. Description
of functional and non-functional and the way to improve them are mentioned above. The table of
Moscow prioritization is also described in this chapter. In Moscow prioritization, high functional
requirement such as purchase, product register, order, delivery, payment and promotion are
included. And also, reasons for functions such as purchase, product register, order, delivery,
payment and promotion are described.

Page | 47
II. Use Cases
Myanmar Elepha Online POS System

Register Supplier

Purchase Product

Register Product

Register Customer

Customer Staff
Order items

Deliver Items

Explanation
A use case class diagram is one of the diagram which is included in the Unified Modeling
Language(UML). It is a diagram which can summarize the details of the system. In use
case, the actors are used to describe the user that interact with the application or system.
The line called association in the use case diagram represent a connection between actors
and use cases. The ovals called use cases are used to describe the different uses which
a user might have. The box with the use cases and the lines is called system boundary
box which sets a system scope.

See the Use Case Descriptions in Chapter 8 Appendix Page no. 100

Page | 48
III. Architecture

a. System Architecture – Initial Class Diagram

Customer

1 * 1
Order Delivery
*
Region
*
1 *
1
* 1

OrderDetail StaffID

Size
*
1
1
ProductDetail
Type *

*
1 1
Brand
*

Product 1

* Colour
*
1 1
*

PurchaseDetail

*
1

Purchase Supplier

* 1

Page | 49
 Explanation
Like Use Case Diagram, Initial Class diagram is also included in the Unified Modeling
Language. It is used to represent the classes that will actually be programmed, the
interactions between classes and objects. Classes are represented by a rectangle that
involves the class name which is the first row in the class shape. The straight line with the
multiplicity called association which is one of the relationship between two classes. The
multiplicity on the straight line allows for statement about the number of objects which are
included in an association.

b. System Architecture – Component Diagram:

Explanation
A component is used to describe as a static implementation view of a system. A horizontal
line from the component box with a small circle used to describe the interfaces where a
component produces information. Half circle on the straight line used to describe the
interfaces where a component needs information to operate its main function. This
diagram is not for the whole system but for the customer process. The transactions create
a network of relationships between the component of the Point of sales system.

Page | 50
 Chapter 3 – Design
I. Structural Model (Detailed Class Diagram)

Page | 51
 Customer
-CustomerID : String
-CustomerName : String
-Address : String
-Email : String
-Password : String
-Gender : String
-Phone : Integer
-RegDate : Date
+addCustomer()
+removeCustomer()
+updateCustomer()
Region
-RegionID : String
-RegionName : String 1 *
-Charges : Integer
+addRegion()
+updateRegion()
Size
-SizeID : String
-Size : Integer
+addSize()
+editSize()
+removeSize()
Type
-TypeID : String
-Type : Integer
+addType()
+editType()
+removeType()
See the Detailed Class Diagram Definition in Appendix Page 102
Order
-CustomerID : String
-OrderID : String
-Date : Date Delivery
-TotalAmount : Integer
-DeliveryID : String
-RegionID : String
-StaffID : String
1 * -Status : String
-DeliveryDate : Date
-DeliveryID : String
-Deliverystatus : String
-Paymentype : String * 1
-Transpotation : String
-BankAccount : String
+updateDelivery()
-DeliveryAddress : String
-Phone : Integer
+placeOrder() *
+editOrder()
1
1
* StaffID
-StaffID : String
Order Detail -Name : String
-Phone : Integer
--Order_ID : String
-Address : String
--ProductDetailID : String
-Role : String
--Quantity : Integer
--Amount : Integer +addStaff()
+updateStaff()
+calcPrice()
*
1
1 *
ProductDetail
-ProductDetailId : String
-ProductID : String
-SizeID : String
-Colour : String
-Quantity : Integer
-Price : Integer
1 * +addProductDetail()
+updateProductDetail()
1
*
Brands
Product -Brand_Id : String
-ProductID : String -BrandName : String
-ProductName : String +addBrand()
-BrandID : String * 1 +updateBrand()
-Description : String +editBrand()
-Image : String
+displayProduct() Colour
+updateProduct() -ColourID : String
+getProductDetail() -ColourName : String
* 1
+addColour()
1 +updateColour()
* +editColour()
PurchaseDetail
-PurchaseID : String
-ProductDetailID : String
-Quantity : Integer
-Amount : Integer
-PurchasePrice : Integer
+addPurchaseDetail()
+editPurchaseDetail()
*
1
Supplier
Purchase
-SupplierID : String
-PurchaseID : String
-Name : String
-Date : Date
-Phone : Integer
-Supplier : String
-Address : String
-TotalAmount : Integer * 1 -Email : String
+addPurchase()
+addSupplier()
+updatePurchase()
+updateSupplier()
Page | 52
 Explanation

Detailed class diagram is related with the initial class diagram. In initial class diagram,
there is no attributes and methods in the classes but the detailed class diagram shows
attributes and methods in order to represent the detailed system. Attributes which is the
second row in the class shape are used to describe a characteristic of a class. In the third
row there is a method which is a behavioral feature owned by a class and it shows the
signatures of operations. Like Initial class, there are association lines with multiplicity
which represent the connection between two classes.

II. Behavioral Model (Sequence Diagrams)

i. Sequence Diagram for Purchase

Supplier Product Purchase

Top Package::Supplier Top Package::Staff

Record Supplier's Information

Confirm

Choose Supplier

Confirm

Check Product

Confirm

Purchase Product

Confirm

Page | 53
ii. Sequence Diagram for Order

Customer Product Order Payment Delivery

Top Package::Customer Top Package::Staff

Register Customer

Confirm

Register Product

Confirm

Select the product

Confirm

Order Product

Confirm

Make Payment

Confirm

make Delivery

Confirm

Explanation

Like Use Case Diagram and Detailed Class Diagram, Sequence diagram is also included
in Unified Modeling Language. It is a type of interaction because it represents how a group
of objects operate together. The rectangle box with the dashed vertical line is called
Lifeline symbol which describe the sequential events that occur to an object. The long
rectangle box is the activation box and it shows the time required for an object to finish a
task. The actor symbol in Sequence diagram describe entities which interact with the
system. A straight line with an arrowhead called Synchronous message symbol means
that a sender has to wait for a response to a message before it continues. A dashed line
with a line arrowhead called reply message symbol and it is used to represent replies to
call.

Page | 54
Chapter 4 Risk Management and Configuration
Management

I. Risk Management

a. Identify Critical Success Factors of a project

 Top level management

This means the experienced and professional project manager should handle and
manage the project requirement. The project manager would have to provide
oversight functions to the project team. He has to select resources who will be
allocated to project and will be assigned work.

 A clearly defined project scope and project charter

Project charter and project scope will be clearly defined and articulated by project
manager and project planner. Project scope is the part of project planning that
involves determining and documenting a list of specific project goals,

deliverables, features, functions, tasks, deadlines, and ultimately costs. In

the other word, it is what needs to be achieved and the work that must be
done to deliver a project. It is essential to pin down the scope immediately
in a project’s life cycle as it can greatly impact the schedule or cost (or both)
of the project down the track.

 Resources should be clearly observed

Project manager and team members should carefully observe the related
resources for the project. Web designs and coding are the important role in this
project so that project manager should take references from other online store
website design in order to develop this project. The project manager should
narrow and focus his search to exclude less relevant results and should evaluate
what he finds, so he can decide what to include in the project. Furthermore, he
should keep tracking of the sources he intend to use.

Page | 55
  Team members should stay updated

Project manager should make sure that regularly update the schedule with his
team to check progress and make necessary changes. Email notifications are set
up at either the global level or individual projects. Team members can use email
notifications and the message board to be notified of changes to activities, and
update other team members about activity specific information. Project Managers
not only need to stay in the loop, they also need to know as many aspects of that
loop as possible and quickly. Moreover, team members should use a centralized
system to manage all collaboration and communication makes teams much more
efficient and makes it possible to get accurate, real –time updates.

 Project Schedule

The planning phase of project requires well defined project charter and project
scope. To begin the project plan, the project manager must identify all tasks
required to reach the end goal and establish a strategy for performing each task.
Estimating how long a task is going to take can be tricky but is important if the
project manager is going to create a realistic project schedule. The project
manager should identify tasks that must be completed before other tasks can
begin and tasks that can be done whilst other tasks are being performed because
this will cut down the time needed. Project manager should also keep team
members informed about change in project schedule.

b. Major Sources of Risk

 Environmental Risk

Environmental risk occurs in almost everywhere which can cause unexpected

costs in resolving and preventing data damage. All of the data that are stored in
the database can be damage anytime by the potential threat of adverse effects
such as storm, tornado, tropical cyclone, typhoon, earthquake and so on. Every
project carries some environmental risk. If there is no backup for essential data,
there will be a big issue for the project and it will not be done successfully.

Page | 56
 Poor Management

During the planning process, poor definition and planning can cause serious
issues in many areas of the project involving the lack of business support, poor
estimates, poor management and poor scope control. Some of the project
manager doesn’t have good management skill and, consequently, they couldn’t
handle the project. In some situations, the manager has good managing skill,
although they have no vision for the possible risk. As a result, he couldn’t manage
and solve each of the issues which may come out from the project. As a project
gets larger, the project needs excellent project manager who has good vision for
the future risk to be successful.

 Lack of leader involvement

One of the biggest problem in management is not meeting with the team
members and ignore the roles and responsibilities of management. Project
leader needs to meet with his team members once a week and set goals upfront.
If he absents on his duty time, project will not be done on specific time. For
example, when the team members will make critical decisions expert advice, the
project leader won’t participate in the meeting. If the project leader doesn’t focus
on the project, the team member will not be able to do the entire work in exact
time. In the other word, the project leader won’t be able to control the project and
team members.

 Problem and errors detected late

Coding errors definitely cause the delay problem that need to be consider.
Dividing work across too many coding detection causes waiting time that leads
to the project delay. When there are too many errors in the coding process, the
project will not be done on the specific date. If the deadline for the project is too
close and the error fixing for the coding is not done, the team member won’t
probably focus on it and he can make some mistakes. As a result, it is likely that
in the rush to meet the deadline, stressed-out team members may produce low
quality website leading to the project delay risk.

Page | 57
  Inadequate technical approaches

The lack of electricity is one of the issue that needed to be consider in major
source of risk. Technical products and tools should be supported in order to get
electricity. If the electricity problem occurs in the project, it will not be done on
specific time. Poor supporting of the technical requirement have been occurring
in some countries. If the company didn’t support technical products, the project
will not be produced in the high quality. That will lead to the damage of the project
and it will not be succeeded.

c. Personal

 Wrong Grade

Hiring a bad employee may be inevitable, sometimes candidates might have

great CV and interview skillfully, however, it may not be appropriate for the
project role. This mistake can cause serious problem for organization. If the
company hire the low grade employee, they couldn’t do their job effectively. Due
to the lack of skills or motivation, the employee will not create high quality project.
This can lead to the issue on the results of the project and the overall
performance of the team.

 Wrong Training

The training to the employee is not an easy task. Everyone learns in completely
different ways and training staff need to know how to make it easier. Time is the
most precious thing and training staff need to manage their training time to
improve the employees’ skills. Employee who don’t receive adequate training
may have difficulty performance standard. Trainers with bad morale couldn’t
improve the employee skill. As a result, the project will be created with poor
quality and it will lead to the major issue of the project.

 Wrong Expertise

Some business man willing to hire friends and family and the businesses look
like ongoing family reunion. Their desire to help out a family member doesn’t
always align with the need to hire great employee. Sometime, the company hire

Page | 58
 the great employee who doesn’t fit with the project. Some business man doesn’t
interest the experienced candidate and only wants to talk about how quickly
he/she can do the project. They sometimes hire the candidate who doesn’t have
the experience in project. He may be excellent in other fields but he couldn’t do
the project quickly otherwise he couldn’t create a good quality project.

 Too many/few people

Having too many employees in the company seems like a problem to have. If the
company hire too many employees including good grade and bad grade, the
project will not be produced with good quality. Moreover, the project leader
cannot manage all of the employee in the short duration. Hiring a few employees
doesn’t seem good and it can also lead to the issue of the project. Project with
complex coding cannot be completely done with few people otherwise they will
not be able to complete the project on the specific time.

d. Technical

 Requirement Changes

The requirement which is defined in the first phase change as the project
progresses can lead to the serious issue with the project. Because of the
development progresses and prototypes, the problem may usually occur.
External environment changes which require reshaping of the original business
problem can also cause the unwanted issues. It is also depending on the project
manager and if he doesn’t aware of these possibilities and doesn’t have backup
plans, he won’t be able to deal with these changes. Thus, a project manager
should have a clearly defined process for receiving, analyzing and combining
change request to solve this situation.

 Poor requirements

Some of the project have high level, vague, and generally unhelpful
requirements. Most of the project fails because of the bad requirements. The
quality of requirements can have a lot of impact on the outcome of the project.
Once the project fails, money and time are wasted on unnecessary work.

Page | 59
 Consequently, the developer cannot test the whole project completely if the
project team use the poor requirement. It depends on the cases where the
developers, having no input from the user, build what they believe is needed,
without having any real knowledge of the business. The lack of sponsor also
causes the poor requirement issues. Therefore, the developers must know what
they need to do, which requirements have to be collected and be able to specify
it precisely. Project sponsor must also involve in the business project in order to
provide high-quality requirements.

 Problem Error Detected – inconsistent Design, missing component, inadequate

time for testing

During project, some of the possible error detected issue will be happened. A
good-looking design and intuitive interface go a long way in establishing trust
with the visitors. Layout of the website should be consistent enough as it shows
the overall outlook of the website. The main problem often happens in most of
the project is that the project members couldn’t manage their time. So, when the
project deadline is near, they may create website design hastily. Consequently,
they will miss project component and couldn’t complete the testing process.
Testing is such an important process in the project and if the tester doesn’t
complete the project testing on time, the project will not be successfully done and
it can lead to the major problem for the whole team.

II. Risk Matrix

Low 0% 30% Medium 31% 60% High 61% 100%

Title and Risk Potential Risk owner Actions Action

description Status impact Log

Environmental Low High Programmer or Programmer need to 0

risk system analyst backup all the data related
to the project

Page | 60
Poor Medium High Project Good Management skill 0
Management Manager training is needed for
project manager
Lack of leader High High Project Leader Should change the project 0
involvement leader if he ignore the
Problem and Medium Medium Programmer Should manage the time 0
errors detected for testing to reduce
late coding error
Inadequate Low Low Electrical Need to support electricity 0
technical Engineer
approaches
Wrong Grade Medium High Project leader Need to know the details 0
of the employees before
the job interview for them
Wrong Medium High Trainers Need to know much about 0
Training training skills and must
improve a lot for the
employee
Wrong Low Medium Project Leader Should hire employees 0
Expertise who are expert in handling
the project.
Too many/few Medium High Project Leader The project leader should 0
people know much about the
employees before he hire
them.
Requirement High High Project should have a clearly 0
Changes Manager defined process for
receiving, analyzing and
combining change request
Poor Medium High Developer Sponsor should involve to 0
Requirement support good quality
requirements

Page | 61
 Problem Error High High Tester, Tester need to check the 0
Detected Developer website every day in order
to reduce the errors
issues. Developers must
perceive the improvement
of the website design and
component.

III. Configuration Management – Directory Structure

a. Program

b. Project documentation

Page | 62
 Chapter 5 – Testing

5.1 Test Schedule

Module 1: Customer Registration

Test Description Date Tester

Script
1.1 Customer ID are automatically add to a table within 13 March Aung Soe Khine
a customer database when customer register in 2018
the customer registration form.
1.2 Customer cannot skip without filling in the Name 13 March Aung Soe Khine
field. 2018
1.3 Customer cannot skip without filling in the 13 March Aung Soe Khine
Address field. 2018
1.4 Customer cannot skip without filling in the Email 13 March Aung Soe Khine
field. 2018
1.5 Email must be in email format. 13 March Aung Soe Khine
2018
1.6 Customer cannot skip without filling in the 13 March Aung Soe Khine
Password field. 2018
1.7 Customer is not allowed to skip to fill in the Phone 13 March Aung Soe Khine
field. 2018
1.8 A customer’s email cannot register twice. 13 March Aung Soe Khine
2018
1.9 All customer information should be saved 13 March Aung Soe Khine
accurately in customer table in database when 2018
customer click Register button.
1.10 All of filled text box should be empty when 13 March Aung Soe Khine
Customer click Clear button. 2018

Page | 63
Module 2: Customer Login

Test Description Date Tester

Script
2.1 Customer can log in successfully if he fill correct 13 March Aung Soe Khine
Email and Password in Sign In Form. 2018
2.2 Customer cannot log in successfully if he fill 13 March Aung Soe Khine
incorrect Email and Password. 2018
2.3 Customer cannot skip without filling in the Email 13 March Aung Soe Khine
field 2018
2.4 Email must be in Email format 13 March Aung Soe Khine
2018
2.5 Customer cannot skip without filling in the 13 March Aung Soe Khine
Password field 2018
2.6 Customer is not allowed to click Sign In button 13 March Aung Soe Khine
when the fields are empty. 2018
2.7 All filled text box should be empty when Clear 13 March Aung Soe Khine
button is clicked 2018
2.8 The page will go to Brand page once he/she login 13 March Aung Soe Khine
2018
2.9 The page will go to Display page once he/she log 13 March Aung Soe Khine
out 2018

Page | 64
Module 3: Admin Registration

Test Description Date Tester

Script
3.1 Admin ID are automatically add to a table within a 13 March Aung Soe Khine
admin database. 2018
3.2 Admin cannot skip without filling in the Name field 13 March Aung Soe Khine
2018
3.3 Admin cannot skip without filling in the Email field 13 March Aung Soe Khine
2018
3.4 Email must be in Email format 13 March Aung Soe Khine
2018
3.5 Admin cannot skip without filling in the Password 13 March Aung Soe Khine
field 2018
3.6 Admin cannot skip without filling in the Phone field 13 March Aung Soe Khine
2018
3.7 The page should go to the Admin Login Page when 13 March Aung Soe Khine
admin click “I am already a member” button. 2018
3.8 Customer is not allowed to click Sign In button 13 March Aung Soe Khine
when the fields are empty. 2018
3.9 All filled text box should be empty when Clear 13 March Aung Soe Khine
button is clicked 2018

Page | 65
 3.10 An admin’s email cannot register twice. 13 March Aung Soe Khine
2018
3.11 All admin information should be saved accurately 13 March Aung Soe Khine
in customer table in database when admin click 2018
Register button.

Module 4: Admin Login

Test Description Date Tester

Script
4.1 Admin can log in successfully if he fill correct 13 March Aung Soe Khine
Email and Password in Sign In Form. 2018
4.2 Admin cannot log in successfully if he fill incorrect 13 March Aung Soe Khine
Email and Password. 2018
4.3 Admin cannot skip without filling in the Email 13 March Aung Soe Khine
field. 2018
4.4 Email must be in Email format. 13 March Aung Soe Khine
2018
4.5 Admin cannot skip without filling in the Password 13 March Aung Soe Khine
field 2018
4.6 Admin is not allowed to click Sign In button when 13 March Aung Soe Khine
the fields are empty. 2018
4.7 All filled text box should be empty when Clear 13 March Aung Soe Khine
button is clicked 2018
4.8 The page will go to Brand page once he/she 13 March Aung Soe Khine
login 2018
4.9 The page will go to Display page once he/she log 13 March Aung Soe Khine
out 2018

Page | 66
Module 5: Brand Registration

Test Description Date Tester

Script
5.1 Brand ID are automatically add to a table within a 13 March Aung Soe Khine
brand database. 2018
5.2 Admin cannot skip without filling in the Brand 13 March Aung Soe Khine
Name field 2018
5.3 Admin cannot skip without filling in the Country 13 March Aung Soe Khine
field 2018
5.4 Admin can edit the brand name once he/she click 13 March Aung Soe Khine
the Edit button in the brand listing table 2018
5.5 Admin can delete the brand name once he/she 13 March Aung Soe Khine
click the Delete button in the brand listing table. 2018

Module 6: Color Registration

Test Description Date Tester

Script
6.1 Color ID are automatically add to a table within a 13 March Aung Soe Khine
color database. 2018
6.2 Admin cannot skip without filling in the Color field 13 March Aung Soe Khine
2018
6.3 Admin can edit the color once he/she click the 13 March Aung Soe Khine
Edit button in the color listing table 2018
6.4 Admin can delete the color once he/she click the 13 March Aung Soe Khine
Delete button in the color listing table. 2018

Page | 67
Module 7: Size Registration

Test Description Date Tester

Script
7.1 Size ID are automatically add to a table within a 13 March Aung Soe Khine
size database. 2018
7.2 Admin cannot skip without filling in the Size field. 13 March Aung Soe Khine
2018
7.3 Admin can edit the size once he/she click the Edit 13 March Aung Soe Khine
button in the size listing table. 2018
7.4 Admin can delete the size once he/she click the 13 March Aung Soe Khine
Delete button in the size listing table. 2018

Module 8: Type Registration

Test Description Date Tester

Script
8.1 Type ID are automatically add to a table within a 14 March Aung Soe Khine
type database. 2018
8.2 Admin cannot skip without filling in the Type field. 14 March Aung Soe Khine
2018
8.3 Admin can edit the type once he/she click the 14 March Aung Soe Khine
Edit button in the type listing table. 2018
8.4 Admin can delete the type once he/she click the 14 March Aung Soe Khine
Delete button in the type listing table. 2018

Page | 68
Module 9: Staff Registration

Test Description Date Tester

Script
9.1 Staff ID are automatically add to a table within a 14 March Aung Soe Khine
staff database. 2018
9.2 Admin cannot skip without filling in the Staff 14 March Aung Soe Khine
Name field. 2018
9.3 Admin cannot skip without filling in the Staff 14 March Aung Soe Khine
Phone field. 2018
9.4 Admin cannot skip without filling in the Staff 14 March Aung Soe Khine
Address field. 2018
9.5 Admin can edit the staff once he/she click the 14 March Aung Soe Khine
Edit button in the staff listing table. 2018

9.6 Admin can delete the staff once he/she click the 14 March Aung Soe Khine
Delete button in the staff listing table. 2018

Page | 69
Module 10: Supplier Registration

Test Description Date Tester

Script
10.1 Supplier ID are automatically add to a table within 14 March Aung Soe Khine
a supplier database. 2018
10.2 Admin cannot skip without filling in the Supplier 14 March Aung Soe Khine
Name field. 2018
10.3 Admin cannot skip without filling in the Supplier 14 March Aung Soe Khine
Phone field. 2018
10.4 Admin cannot skip without filling in the Supplier 14 March Aung Soe Khine
Address field. 2018
10.5 Admin cannot skip without filling in the Supplier 14 March Aung Soe Khine
Email field. 2018
10.6 Email must be in Email format 14 March Aung Soe Khine
2018

10.7 Admin cannot skip without filling in the Company 14 March Aung Soe Khine
field. 2018

10.8 Admin can edit the supplier once he/she click the 14 March Aung Soe Khine
Edit button in the supplier listing table. 2018

10.9 Admin can delete the supplier once he/she click 14 March Aung Soe Khine
the Delete button in the supplier listing table. 2018

Page | 70
Module 11: Product Registration

Test Description Date Tester

Script
11.1 Product ID are automatically add to a table within 14 March Aung Soe Khine
a product database. 2018
11.2 Admin cannot skip without filling in the Product 14 March Aung Soe Khine
Name field. 2018
11.3 Admin cannot skip without filling in the Price 14 March Aung Soe Khine
field. 2018
11.4 Admin cannot skip without filling in the Quantity 14 March Aung Soe Khine
field. 2018
11.5 Admin cannot skip without filling in the Images 14 March Aung Soe Khine
field. 2018

11.6 Admin cannot skip without filling in the 14 March Aung Soe Khine
Description field. 2018

11.7 Admin cannot skip without filling in the Review 14 March Aung Soe Khine
field. 2018

11.8 Admin can edit the product once he/she click the 14 March Aung Soe Khine
Edit button in the product listing table. 2018

11.9 Admin can delete the product once he/she click 14 March Aung Soe Khine
the Delete button in the product listing table. 2018

Page | 71
Module 12: Purchase Product

Test Description Date Tester

Script
12.1 Sub Total is automatically add to a Purchase 14 March Aung Soe Khine
Details once Admin add ProductID, Price and 2018
Quantity.
12.2 Admin cannot skip without choosing in the 14 March Aung Soe Khine
ProductID field. 2018
12.3 Admin cannot skip without filling in the Price 14 March Aung Soe Khine
field. 2018
12.4 Admin cannot skip without filling in the Quantity 14 March Aung Soe Khine
field. 2018
12.5 Admin can remove the Purchased Products once 14 March Aung Soe Khine
he/she click the Clear All button in the Purchase 2018
Details table.
12.6 Admin can purchase the Product once he/she 14 March Aung Soe Khine
choose supplier and click the Purchase button in 2018
the Purchase Details table.
12.7 Admin can clear the Purchase Detail once he/she 14 March Aung Soe Khine
click Clear All button in the Purchase Details table. 2018

Page | 72
Module 13: Purchase Search

Test Description Date Tester

Script
13.1 Admin can search the purchased product by ID 14 March Aung Soe Khine
once he/she choose PurchaseID and click Search 2018
button.
13.2 Admin can search the purchased product by Date 14 March Aung Soe Khine
once he/she click Search by Date radio button, 2018
choose purchased date and click Search button.
13.3 Admin can view all purchased product once he/she 14 March Aung Soe Khine
click Show All button. 2018
13.4 Admin cannot search purchased product by ID if 14 March Aung Soe Khine
he/she click Search by Date radio button. 2018
13.5 Admin cannot search purchased product by date 14 March Aung Soe Khine
if he/she have click Search by ID radio button. 2018
13.6 Admin cannot search purchased product if he/she 14 March Aung Soe Khine
choose wrong purchased date. 2018

13.7 Admin can view and print Purchase Detail Report 14 March Aung Soe Khine
once he/she click View Detail in the Purchase 2018
Search Details table.
13.8 Admin can clear the Purchase ID and Purchase 14 March Aung Soe Khine
Date that he has filled in the text box once he/she 2018
click Clear button.

Page | 73
Module 14: Order Search

Test Description Date Tester

Script
14.1 Admin can search the ordered product by ID once 14 March Aung Soe Khine
he/she choose OrderID and click Search button. 2018
14.2 Admin can search the ordered product by Date 14 March Aung Soe Khine
once he/she click Search by Date radio button, 2018
choose purchased date and click Search button.
14.3 Admin can view all ordered product once he/she 14 March Aung Soe Khine
click Show All button. 2018
14.4 Admin cannot search ordered product by ID if 14 March Aung Soe Khine
he/she click Search by Date radio button. 2018
14.5 Admin cannot search ordered product by date if 14 March Aung Soe Khine
he/she have click Search by ID radio button. 2018
14.6 Admin cannot search ordered product if he/she 14 March Aung Soe Khine
choose wrong purchased date. 2018

14.7 Admin can view and print Order Detail Report once 14 March Aung Soe Khine
he/she click View Detail in the Order Search 2018
Details table.
14.8 Admin can clear the Order ID and Order Date that 14 March Aung Soe Khine
he has filled in the text box once he/she click Clear 2018
button.

Page | 74
Module 15: Checkout

Test Description Date Tester

Script
15.1 Customer cannot checkout without filling contact 14 March Aung Soe Khine
phone. 2018
15.2 Customer cannot checkout without filling delivery 14 March Aung Soe Khine
address. 2018
15.3 Customer can remove the product that he added 14 March Aung Soe Khine
in the Shopping Cart Details table. 2018
15.4 Customer can remove all the product that he 14 March Aung Soe Khine
added by clicking Empty Cart button in the 2018
Shopping Cart.
15.5 Customer can go to the Display page by clicking 14 March Aung Soe Khine
Product Display button in the Shopping Cart. 2018
15.6 Customer can successfully order the product by 14 March Aung Soe Khine
filling contact phone and delivery address and 2018
clicking the Checkout button in the Shopping Cart.

Page | 75
Test Script
Unit Test 1 Test Case: Data entry for customer Designed by:
registration Aung Soe Khine
Data Source: Customer Registration Objective: To check that Customer Tester: Aung Soe
Form Registration form works accurately. Khine

Test Description Test Procedure Expected Actual

Case Result Results
1.1 Customer ID is automatically CustomerID will not be shown in the Customer ID See
add to a table within a form. Fill the other fields that remain in will be Fig 1.1
customer database when the form. Then click Save button and shown in the and
customer register in the check the ID field in database. database. 1.2
customer registration form.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)
See the rest testing in the Chapter 8 Appendix Page No.104

Page | 76
 Chapter 6 Implementation

I. Deployment Diagram (Implementation)

<<Database Server>

shoespos_db <<Desktop>>
TCP/IP
Window OS

Mozilla Fiefox
<<Mobile Phone>>
TCP/IP

Web Browser

<<WebServer MySQL>
TCP/IP

TCP/IP
-customer registration
-product registration
-product display
-staff registration TCP/IP
-brand registration Internet
-supplier registration <<Printer>>
-purchase product
-purchase detail
-purchase search
Print Driver
-shopping cart
-checkout

Explanation

A deployment diagram is one type of diagram created with the Unified Modeling
Language(UML). It is used to illustrate an aspect of the system itself. In this project, the
deployment diagram as the physical deployment of information generated by the website
program on hardware component. The first node and second node are execution
environment node. The first node used to describe the database server which represent
the data stored by the system. The second node used to describe the web servers

Page | 77
 including customer registration, product registration, product display, staff registration,
brand registration, supplier registration, purchase product, purchase detail, purchase
search, shopping cart, checkout. The cloud means the internet which is used to connect
with the web server. The third node is a device node and it is used to described the
mobile phone and the component is web browser. The fourth node (second device node)
is used to present desktop and the components for the second device node are Window
OS and Mozilla Firefox. Printer is described in the fifth node and the component is print
driver. The headers described in the nodes are called artifacts and the communication
line between two nodes are called communication path. TCP/IP is described as
communication paths for all nodes and the cloud.

II. Data Migration

The process of relocating stored digital information between data devices such as
computers, data storage systems or file formats while changing storage, database or
application is called data migration. This is the outcome of new system or location for the
data. Data migration occur for a variety of reasons, which include restoring or upgrading
servers or storage equipment, system implementation, maintenance, a change of data
centers, software upgrades and data consolidation projects. Data migration can reduce
human resources from dull tasks and accomplished to achieve an automated migration.

Data Migration Procedure

1. Planning for premigration

Data Migration is a complex process so it must be planned before transferring

data from one place to another. The data must be evaluated which is being moved
for stability. When the project team members are going to plan the data migration
process, they should identify what they’re migrating. Identifying this information
will help them to get knowledge going to the project.

Page | 78
2. Project Initiation

The project team must identify and brief stakeholders who are affected by the
outcome, negatively or positively, or those who can affect the outcomes of a
proposed intervention and manage them throughout the life cycle at the beginning
of the project. Categorizing stakeholders will help to get a more specified
investigation on the effect and importance.

3. Backup all data

The project team should backup all of the data to the cloud especially the files
which would be required to migrated. If any problems such as corrupt, incomplete,
or missing files throughout migration, the team will be able to correct the error by
restoring the original data. Data migration might take weeks, sometimes several
months. Therefore, the project team won’t have admission to that information for
the duration of the migration process if they didn’t backup or take a copy of the
data.

4. Migration design

The source and target objects mapping should be decided and outlined. The main
task in migration design stage is to define the technical architecture and design
of the migration processes. Furthermore, the team will also have to define the
testing progresses and the way of transition to the production system. At first, the
migration should be mapped out by specification as opposed to coding the map
which will be more cost-effective. One of the difficult task is creating manual
mapping using excel spreadsheet. If the team use excel spreadsheets, mapping
specifications built cannot be easily managed. Plans for next steps is necessary
to put down on paper including timelines, technical details and approval
requirement.

Page | 79
5. Build and test

It is a formal process of coding the migration logic and testing the migration with
a mirror of the production environment. In this stage, one of the typical method is
to follow when a migration is developed in order to subset the data and one
category of data is tested at a time. Testing is taken away within a test framework
which can be created for the purpose. Testing start by checking the components
separately in small subsets to make sure the transformations, mapping and data
cleansing are working. Subsequently, the data volumes are increased and finally
all of the components are linked together into a single migration job.

6. Execute of the data migration plan

The plan for migration will help the project team to ensure the right system
authorization are applied to allow for effective data migration and take out all data
migration to aim from source system. This data must be cleaned in order to protect
target system, then it must be transformed into the proper format for transfer. After
all, cleaned and deduplicated data must be loaded into the target system data
migration rules and map which is already laid out. In order to discover and solve
any problem occur, the team members should closely monitor the own data
migration throughout the process.

7. Production

The final stage is to shut down and dispose of old systems. There will be ongoing
data quality enhancement. Data quality issues may be identified and will require
to correct in several of the source system because not all source will be retired.
Ongoing improvement may also be required to manage by project team and the
data quality of the new system should be monitored after shutting down old
system.

Page | 80
No Description Start Date End Date Responsible Predecessors
person
1 Planning for 13.4.2018 1.5.2018 Data
premigration migration
project lead
2 Project Initiation 13.4.2018 1.5.2018 Data 1
engineer
3 Backup all data 13.4.2018 1.5.2018 Data 2
engineer
4 Migration design 13.4.2018 1.5.2018 Data 3
mapping
specialist
5 Build and test 13.4.2018 1.5.2018 Data 4
migration
specialist
6 Execute of the data 13.4.2018 1.5.2018 Data 5
migration plan management
consultant
7 Production 13.4.2018 1.5.2018 Data 6
management
consultant

Page | 81
III. Training

Training Title Admin Registration

Type of User All registration staffs including data entry

staffs in management level

Location KMD

Date February 13, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the admin

name and password in to the system for
each user group. How to delete them from
the system.

Page | 82
Training Title Product Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 14, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the product

name, brand, price, colour, quantity and
product images in to the system for each
user group. How to delete them from the
system.

Training Title Brand Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 15, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the brand

name, country and active/inactive in to the
system for each user group. How to delete
them from the system.

Page | 83
Training Title Colour Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 16, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register, update the colour in to the

system for each user group. How to delete
it from the system.

Training Title Purchase Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 17, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to purchase the product, add price

and quantity in to the system for each user
group.

Page | 84
Training Title Size Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 18, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the product

size in to the system for each user group.
How to delete it from the system.

Training Title Supplier Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 19, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the supplier

name, phone, address, email and
company name in to the system for each
user group. How to delete them from the
system.

Page | 85
Training Title Staff Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 20, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the staff name,

phone, address, email and staff role in to
the system for each user group. How to
delete them from the system.

Training Title Type Registration

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 21, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to register and update the product

type in to the system for each user group.
How to delete it from the system.

Page | 86
Training Title Purchase Search

Type of User All registration staffs including data entry

staffs in product management level

Location KMD

Date February 22, 2018

Time 9:00 am to 10:00 am

Tool PC on which the program is installed

Description How to search and view the details of

purchase product from the system for each
user group.

Page | 87
 Chapter 7 Conclusion
Evaluation
Evaluation against Aims and Objectives

- Aims and Objectives

First of all, the main aim of the project is to increase the company profit and to
provide the company economy. The profit should be developed by this project and if
the company get more profits, the ME retail store will become more successful. In
order to increase company’s profit, the company need to get more and more
customers. ME retail store also need to get customers’ trust and loyalty. Moreover, ME
also aim to get the biggest name among the competitors. If the company don’t get the
name among other competitors, the development of the company will not be
successfully done. The last main aim is to stand company name long last due to the
development of the company.
In order to make the aim come true, the system should be firstly analysis for
reducing the errors. Analyzing process is one of the essential process in the project
and any other fields. For payment, manual system should be change to the
computerized system. Today the world becoming smaller and smaller and technology
is advancing at a phenomenal pace. Through the various industries and market,
technology has helped today’s workforce work smarter. Not only are the cashiers
faster but also they are more productive in the workflow. The ME company willing to
create online shopping website and application in order to develop the company profit
more and more. The company also willing to develop not only the payment system for
delivery but also for design of website. Today business purchases are replacing
electronic payments or payment cards instead of using cash and checks. So, the
customers will be able to buy the products faster, more secure and traceable
transactions, if the company change the manual payment into electronic payment. For
attraction to the company, the design of the website should be developed.
Furthermore, the company also want to implement coding for the system and execute
testing for finding errors. The last and important objective for the project is to perform
training for the employee to understand more about the system.

Page | 88
- What have been done

Due to the important aims of the project, analyzing the system have been
done. To reach the successful step of the development of the project,
computerized system for the payment have been changed from the manual
system. Technology has become an influential factor in everyday lives and people
simply can’t live without it. According to this project, the ME store have been
created online shopping website. In order to create the website, the programmer
need to develop the code for the website. The coding for the system have been
implemented. Finally, the testing has been executed for finding errors.

- Problems Encountered

Every stage of the project will have at least a problem. During the process
of the project, some problems encountered. The coding for the project are not
familiar with the programmer so that the resources had to search in the internet
and learn to develop the programming skills. Moreover, the company also had to
take a survey of old customer who can use the electronic payment during the
process of changing of manual system into computerized system. Furthermore,
the design for the website is the most difficult process for the programmer.

- Lessons Learnt
Every project will have a lesson that will have to learn and compile. In this
project, there are many unfamiliar process that need to be learnt. Collecting the
project requirement and estimating their cost is such an unfamiliar process which
is necessary to learn. Project team didn’t have an experience of this process and
they have to this by researching the similar process in the business websites and
blogs. The lesson for this process is the team need to know much knowledge about
project requirement and have skill in estimating the cost of each product. The most
difficult process in this project is the website design process and the project team
have learnt many lessons. In order to solve this problem, the template for the
website design had to be searched and downloaded. First of all, the team have
learnt much about the CSS design. Then, they also knew how to create the
required forms of the website. They also learnt about the creation of background
images and product display images.

Page | 89
Evaluation against Similar System Comparison

- Functional Comparison

The ME project team have learnt much about the similar website comparison which
were mentioned in Chapter 3. After comparing two similar websites, the project team
realize that other developers wisely use the color which seems special for the users in
the navigation. Likewise, the team also used the unique color and perfect logo in this
website. Furthermore, other developers divide the categories for the products,
however, the project team didn’t develop the product category due to the insufficient
time. The project team have got the idea of linking each category to the respective
page once the user clicks the buttons in the navigation for the entry form pages that
they have already created. For the home page otherwise the display page, the project
team have got the concept of adding slide show images which can be attracted the
customers. So thus, they added the colorful slideshow images in the home page. After
analyzing the menu display of the two similar websites, the team have got the idea of
creating drop-down menu in the navigation category. The team added drop down
menu in the admin page. For the customer registration, both SneakerHead.com and
Famousfootwear.com divided customer first name and last name in the sign up form.
However, the users only need to fill full name in ME sign up form and the team
developed more information including address, gender and phone number. The
shopping cart function is very important in the online retail store and the ME team have
linked the shopping cart function with the product detail page after observing two
similar websites. The ME products will be added to the shopping cart when the
customers click add button in the product detail page. Checkout process is related with
the shopping cart because the customers have to click checkout button in the shopping
cart page. Both two similar websites have secure functions for checkout process
because they created the processes step by step. In their websites customers have to
choose to checkout as a returning customer or a guest. Moreover, billing information,
shipping information, shipping method, payment information and order review
processes are also included in their websites. Not only customer information and
purchased product details but also security questions are included in their websites.
Due to the lack of time for the project, the ME project team only created the checkout
process with simple information such as SalesID, Sales Date, Customer Name, Total

Page | 90
 Amount, Total Quantity, Card type, Payment Type, Contact Phone and Delivery
Address and no security question are included in ME website.

- Usability Comparison

In order to develop the website, the project teams must firstly start with defining who
the users are. The project team secondly talk to them to find out what their goals are
when visiting the sites. User scenarios which demonstrate in which situation people
visit the site to find what kind of content should be also defined. The final decision
should be also result in a more user-friendly website for any users. Essentially, this
project focus on the user who like to use beautifully colorful website. There are many
brands which offers sportswear and equipment for different sports in this website. On
the top left, there is a search field allowing the users to search any shoes, slippers and
shoe accessories. Once, the customer come to the website, they can either easy to
browse in the navigation by product names and types. Below the search field, there is
the top navigation menu. The project team used fresh and modern design. The logo
which is at the top left is telling the visitors where they are. The project team tried to
create very elegant appearance. There are also good looking and colorful slide show
images to attract the users. White and clear background is also created by the project
team in this website. Also the information described in the web page are easy to read
because the project team carefully make clear headings, link text, bold text and
bulleted lists.

Page | 91
Evaluation against Justifications Made

- Language

 Selected Languages

In order to interact with many different database languages including MySQL, PHP
language was used in this project. The project team would like to use a free
language with no licensing fees so they chose PHP language. Not only it is cheap
but also it is easy to create a website using PHP. Both PHP and MySQL are
compatible with an Apache server which is also free to license. It is such a
language which can be learnt easily by observing simple functions.

 Problems Encountered

PHP language is such an unfamiliar language for the HND student so the students
had learnt the functions involved in the PHP language. Some of the PHP code
seems strange for the project team so they carefully research and observe about
the PHP coding in the internet. Some of the coding error occurred during the
project. Some errors are solved by researching on the internet and some are
solved by the developers.

 Lessons Learnt

From PHP language, some simple and complex functions are learnt. The solution
for the coding error issues were also learnt. Some unknown facts about PHP
language were also learnt from the internet resources. Not only PHP language but
also other languages such as ASP.NET and HTML were also acquired from the
online resources.

Page | 92
- Database

 Selected Database

After comparing two databases (MySQL and MSSQL), MySQL is selected to be

used in this project. Microsoft SQL Server cost a lot for the options and equipment
needed to host the database application and the project team wouldn’t like to use
much money. So, MySQL is such an appropriate database for the developers
because it is less expensive than other database options. Furthermore, PHP was
chosen to be used in this project so MySQL is such an important database to
interact with the PHP. It is also suitable database which is easy to setup and
configure.

 Problems Encountered
At the first time of using the MySQL database, there was a problem for the project
team. They don’t know how to create a table and have no knowledge about the
database function. This project is not an easy case for the team and the database
is a part of the system. Like PHP language, it is also an unfamiliar process for the
project team. They didn’t know how to setup and configure the options.
Consequently, it took a long time to complete the project.

 Lessons Learnt
The project team especially learnt how to create a database and the connection
between MySQL and PHP. The facts and options from the MySQL database were
also learnt by the team. The strength and weakness of MySQL is also important to
be known for the project and hence the team had to research in the internet. The
project team also learnt about the functions involved in this database. They also
learnt how to import and export the database.

Page | 93
- Methodology

 Selected Methodology

After comparing two methods (DSDM and SSADM), DSDM was chose to be used
in the project. DSDM is such a flexible and configurable process to be selected in
this project. The result of development is clearly and rapidly visible so it is easy to
use. DSDM also has specific approach to determine how important each
requirement is to iteration. DSDM is one of the most convenient method for the
project because it has more advantages than SSADM and it is also suitable for
the developers.

 Problems Encountered

DSDM methodology also have the similar problem to the PHP language. Like PHP
language, DSDM is also unfamiliar language to the project team. They didn’t know
some facts about the methodology so this is one of the main problem which was
encountered. As a result, they couldn’t write the project documentation easily and
it took a long time to complete it. So, they have to do some researches from the
internet.

 Lessons Learnt
Some advantages and disadvantages of DSDM were learnt. Not only DSDM
method but also SSADM method were acquired from the internet resources. The
team also learnt how to concentrate the information about unfamiliar methods in
order to manage the time for the project. Some knowledge about comparison of
the methodology was also learnt from some resources.

Page | 94
Evaluation against Project Plan

- Whether the project is on track with the plan

The project is not an easy process for the beginner so there are a lot of the difficulties
encountered in each stage of the project. Whatever there are so many issue during
the progress, the project is on track with the plan. For analysis process it was
successfully done with company information and meeting. Usecase, class and
sequence diagram were also successfully done in design process. In implementation
process, purchase software, software installation, webpage outline, website design,
coding and final stage were had too many issues during the progress but at last they
were successfully solved by the project team. Testing process including coding testing,
webpage testing and the speed of webpage testing was also successfully done.
Training process is such an important process in this project and the employees were
also trained well by the team.

- What was complete on time

Some processes were complete on time but some were not. Analysis process was
successfully completed on time because it is such an important process and it is
required to be done on time. Usecase diagram, Class Diagram and Sequence Diagram
are also fundamental in the design progress and it was also completed on time.
Moreover, testing is the main part of the project and it was completed on time due to
the simple requirement such as snipping tool for this progress. The employees who
are hired in this project were also trained on time due to the exact training schedule
for the training progress.

- What was not complete on time and why

The estimated time for the project is just nine months but it takes one more month to
finish it. It was not complete on time because of some coding errors. The team had to
find some coding error during the process of implementation process. It made them
not to complete the project on time and it can lead to the major problem. Because of
the insufficient time for the project, the employees had left to do some process when

Page | 95
 the deadline is near. Due to the poor time management for the project, some of the
implementation processes were left to complete on time.

- Lessons Learnt

Firstly, the project team have learnt that time management is the fundamental part of
the project. They learnt that how to manage the time skillfully and pay attention to the
number of the times. They have also known that balance is the key to success the
project. They have learnt that how to balance the time for each stage of the project.
Some coding error made the team members to become confuse but they have got
experience and come across this issues. Not only coding error but also project
planning process have been learnt by the project team. In Design process, the team
members have also acquired usecase diagram, class diagram, sequence diagram.
They have also realized how to solve the issues in each stage of the process.

Future Amendments

- Program

The functions and options in the website are satisfactory for the project team but they
are still need to be developed. The customer can currently use the desktop version
and mobile version is not available right now. The ME retail store willing to develop the
mobile version in the future. Some customers want to use mobile version and the
company would like to fulfil their request. Furthermore, in the checkout process, the
users can only purchase with a few payment card and ME retail store also willing to
add more credit card options to be chosen.

- Design

For design process, the company want to add more ideas for system design. The
project team want to create more site maps, hierarchy diagrams, wireframes and use
case diagrams for the system design. The team also would like to develop more ideas
in use case diagram which shows users interaction with the system. A sitemap is very
useful in creating a website and it will help the developer in creating a clear structure
for the site and will help him categorize information. The team members also willing to
create a sitemap for the project. The project team wasn’t satisfied with the CSS design

Page | 96
 and they want to develop more creative background color and slideshow images which
might be match with the brand profile. Otherwise, the team have future aims to add
more creative design which seems more perfect for the users.
- Report

Having some difficulties and experiences during the project, the project team want to
develop the website in the future. For the beginning of the hierarchy for elements within
a page, storyboard is needed to add in the project. It helps clearly define the grid and
structure of the site. So the team wants to add the storyboard in the future project.
website wireframe is one of the essential diagram which should be develop by the
team because it will help the team to create a prototype of the future website. Prototype
also need to develop in order to understand the functions and detailed design of a
system. The project team would like to create a prototype for the future project.
Moreover, the team want to use time box methodology in order to build and evolve
prototype with this tools

References

http://www.conceptdraw.com
www.techopedia.com
www.sqa.org.uk
http://www.selectbs.com
http://searchsoftwarequality.techtarget.com
www.solutionsiq.com
www.wikidot.com
www.linkedin.com
http://sharif.edu
www.bluelinemedia.co.uk
https://minerva.leeds.ac.uk

http://mywifequitherjob.com

https://www.bayt.com/en/specialties/q/140830/what-are-the-disadvantages-of-sales-promotions/

Page | 97
https://blog.resellerclub.com/why-is-promotion-important-for-a-business/

https://support.bigcommerce.com

http://getfetchit.com/why-its-imporant-for-businesses-to-have-a-delivery-system/

https://www.handshake.com/blog/what-is-inventory-control/

http://www.activenetwork.sg/event-management-resources/articles/top-10-benefits

https://www.totallycommunications.com/latest/how-to-define-the-scope-of-a-project/

http://zilicus.com/Resources/blog-2014/6-Steps-To-Effective-Project-Management.html

https://blog.highq.com/enterprise-collaboration/8-steps-for-a-successful-project-management-
schedule

https://explore.easyprojects.net/blog/keeping-people-up-to-date-part-2

https://www.sswm.info/humanitarian-crises/prolonged-encampments/planning-process-
tools/exploring-tools/stakeholder-identification

https://nordic-backup.com/blog/7-steps-data-migration-plan/

http://www.datacenterjournal.com/steps-successful-data-migration/

https://www.netapp.com/us/info/what-is-data-migration.aspx

https://www.cio.com/article/2391872/project-management/8-common-project-management-mistakes-
and-how-to-avoid-them.html

https://www.techrepublic.com/article/poor-planning-is-project-management-mistake-number-one/
http://calleam.com/WTPF/?page_id=2338/

https://www.techrepublic.com/article/poor-planning-is-project-management-mistake-number-
one/

https://www.cio.com/article/2391872/project-management/8-common-project-management-
mistakes-and-how-to-avoid-them.html

http://smallbusiness.chron.com/effects-lack-employee-training-42687.html

https://www.techrepublic.com/article/five-common-errors-in-requirements-analysis-and-how-to-avoid-
them/
https://www.lucidchart.com/pages/uml-sequence-diagram

Page | 98
Appendix

Requirements Catalogue

No Requirement Description Acceptant Criteria

1 Register Supplier Supplier registration is the process Staff
of collecting key information from
outside suppliers of goods and
services and entering that
information into a system to
manage the relationship.
2 Purchase Product Purchasing is the formal process of Staff
buying products from suppliers.
When the retailers order the
product from suppliers, they have
to register and define the products.
Then, they can purchase the
product that they would like to.
3 Register Product Product registration is the process Staff
of putting product information
which should be bought from
supplier and which should be sold
to customer.
4 Register Customer Registration is the Customer
Customer process of sending information
about customer. So that, the
ordered product can be delivered
easily to the customer’s address.
5 Order Items Order is the agreement of the Customer
purchase when the customer order
the products by phone or email.
When the customers order
products, they firstly view products

Page | 99
 and if they like one of the them they
start purchasing the product and
placing order.
6 Deliver Items Delivery is the formal process of Staff
taking goods to the customers by
the staff. In delivery procedure,
they process out of stock order and
return. They also collect the return
items which are inconvenience for
customers. Then, they deliver
items and also gift items.

Use case descriptions

I. Register Supplier

Usecase :Register Supplier

Actor :Staff

Def : Register Supplier

Supplier registration is the process of collecting key information from outside suppliers of
goods and services and entering that information into a system to manage the relationship.

II. Purchase Product

Usecase: Purchase Product

Actor : Staff

Def : Register Product

Define Product

Purchase

Purchasing is the formal process of buying products from suppliers. When the retailers
order the product from suppliers, they have to register and define the products. Then, they
can purchase the product that they would like to.

Page | 100
III. Register Product

Usecase: Register Product

Actor : Staff
Def : Store product information
Product registration is the process of putting product information which should be bought
from supplier and which should be sold to customer.

IV. Register Customer

Usecase: Register Customer

Actor : Customer
Def : Register customer’s information
Customer Registration is the process of sending information about customer. So that, the
ordered product can be delivered easily to the customer’s address.

V. Order Items

Usecase: Order items

Actor : Customer
Def : View Products
: Purchase products
: Place Order
: Check Order Status
: Return Item
: Maintain Accountant Information
Order is the agreement of the purchase when the customer order the products by phone
or email. When the customers order products, they firstly view products and if they like
one of the them they start purchasing the product and placing order.

Page | 101
VI. Delivery Items

Usecase: Deliver Items

Actor : Staff
Def : Process Order
: Process Out of Stock Order
: Process Return
: Collect Return Item
: Deliver Items
: Deliver Gift Item
Delivery is the formal process of taking goods to the customers by the staff. In delivery
procedure, they process out of stock order and return. They also collect the return items
which are inconvenience for customers. Then, they deliver items and also gift items.

Detailed Class Definitions

1. Class Name-Customer

Attribute -CustomerName, CustomerID, Address, Email/password, Gender, Phone

Description- Stores password-protected information about a customer’s identity, order

history, and current order status.

2. Class Name-Order

Attribute - CustomerID, OrderID, Date, TotalAmount, RegionID, Status, DeliveryID,

Payment

Description - Stores customer’s order information

3. Class Name-Region
Attribute -RegionID, RegionName, Charges
Description -Stores Region Information for delivery

Page | 102
4. Class Name-Delivery
Attribute -DeliveryID, StaffID, DeliveryDate, Deliverystatus, transpotation
Description -Stores the information about delivery

5. Class Name-StaffID
Attribute - StaffID, Name, Phone, Address,Role
Description -Stores the information about staff

6. Class Name-Purchase
Attribute -PurchaseID, Date, Supplier, TotalAmount
Description -Stores the information about purchase

7. Class Name-ProductDetail
Attribute -ProductDetailID ProductID, SizeID, Colour, Quantity, Price
Description -Stores the detail information about Product

8. Class Name-Product
Attribute -ProductID, ProductName, BrandID, Description, Image
Description -Stores the product’s information

9. Class Name-Purchase Detail

Attribute -PurchaseID, ProductDetailID, Quantity, Amount, PurchasePrice
Description -Stores the detail information about purchase

10. Class Name-Brand

Attribute -Brand_ID, Brandname
Description -Stores Brand information

11. Class Name -Colour

Attribute -ColourID, Colour

Description -Stores Colour information

Page | 103
12. Class Name - Type

Attribute -TypeID, Type

Description -Stores Type information

13. Class Name- Size

Attribute -SizeID, Size
Description -stores products’ size information

14. Class Name-Order detail

Attribute -OrderID, ProductDetailID, Quantity, Amount
Description -stores the detail of customer’s order

15. Class Name-Supplier

Attribute -SupplierID, Name, Phone, Address, Email
Description -Stores the information about supplier

Page | 104
 Test Script

Test Description Test Procedure Expected Result Actual

Case Result
1.2 Customer cannot skip Skip the Name field and fill the Must warn that Name See Fig
without filling in the rest fields in customer registration Text Box should be 1.1 and
Name field form. Then click Save button. filled out 1.2

Before Testing

Fig (1.1)
After Testing

Page | 105
 Test Description Test Procedure Expected Result Actual Result
Case
1.3 Customer cannot skip Skip the Address field and fill the Must warn that See Fig 1.1
without filling in the rest fields in customer registration Address text box and 1.2
Address field form. Then click Save button. should be filled out

Fig (1.2)

Before Testing

Page | 106
 Fig (1.1)
After Testing

Fig (1.2)

Page | 107
 Test Description Test Procedure Expected Result Actual
Case Result
1.4 Customer cannot skip Skip the Email field and fill the rest Must warn that See Fig 1.1
without filling in the fields in customer registration Email text box and 1.2
Email field form. Then click Save button. should be filled out

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 108
 Test Description Test Procedure Expected Result Actual
Case Result
1.5 Email must be in Fill the Email field without @ and Must warn that See Fig 1.1
email format fill the rest fields in customer Customer should and 1.2
registration form. Then click Save enter an email
button. address.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 109
 Test Description Test Procedure Expected Result Actual
Case Result
1.6 Customer cannot skip Skip the Password field and fill the Must warn that See Fig 1.1
without filling in the rest fields in customer registration Password text box and 1.2
Password field form. Then click Save button. should be filled out

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 110
 Test Description Test Procedure Expected Result Actual
Case Result
1.7 Customer cannot skip Skip the Phone field and fill the rest Must warn that See Fig
without filling in the fields in customer registration form. Phone text box 1.1 and
Phone field Then click Save button. should be filled out 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 111
 Test Description Test Procedure Expected Result Actual
Case Result
1.8 A customer’s email Fill the customer’s data that is already Must warn that See Fig
cannot register twice. exist in the database. Then click Save Customer Email is 1.1 and
button. already exist 1.2

Before Testing

Fig (1.1)

After Testing

Fig (1.2)

Page | 112
 Test Description Test Procedure Expected Result Actual
Case Result
1.9 All customer information should Fill the customer’s information All Customer See Fig
be saved accurately in in the customer registration information 1.1 and
customer table in database form. Then click Save button. should be saved 1.2
when customer click Register in database
button.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 113
 Test Description Test Procedure Expected Result Actual
Case Result
1.10 All of filled text box should be Fill the customer’s All Customer See Fig
empty when Customer click information in the customer information should be 1.1 and
Clear button registration form. Then empty in the customer 1.2
click Clear button. registration form
Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 114
 Unit Test 2 Test Case: Data entry for Designed by:
Customer Sign In Aung Soe Khine
Data Source: Customer Sign In Objective: To check that Tester: Aung Soe Khine
Form Customer Sign In form works
accurately
Test Description Test Procedure Expected Actual
Case Result Results
2.1 Customer can log in Fill Email and Password in the Must show See Fig
successfully if he fill correct Sign In Form. Then click Sign In Sign In success 1.1 and
Email and Password in button. message 1.2
Sign In Form

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 115
 Test Description Test Procedure Expected Result Actual
Case Result
2.2 Customer cannot log in Fill incorrect Email and Must show that See Fig
successfully if he/she fill Password in the text box. Customer Signin 1.1 and
incorrect Email and Password. Then click Sign In button. incorrect message 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 116
 Test Description Test Procedure Expected Result Actual
Case Result
2.3 Customer cannot skip without Fill the password field in Must warn that Email See Fig
filling in the Email field the Sign In form and skip text box should be 1.1 and
the Email field. Then click filled out 1.2
Sign In button.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 117
 Test Description Test Procedure Expected Result Actual
Case Result
2.4 Email must be in Email Fill the Email field without @ and Must warn that See Fig
format
fill password in customer sign in customer should enter 1.1 and
form. Then click Save button. an email address 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 118
 Test Description Test Procedure Expected Result Actual
Case Result
2.5 Customer cannot skip without Fill the Email field in the Must warn that See Fig
filling in the Password field Sign In form and skip the Password text box 1.1 and
Password field. Then click should be filled out 1.2
Sign In button.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 119
 Test Description Test Procedure Expected Result Actual
Case Result
2.6 Customer is not allowed to Be empty in the Sign In Must warn that all the See Fig
click Sign In button when the form. Then click Sign In fields should be filled 1.1 and
fields are empty. button. out 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 120
 Test Description Test Procedure Expected Result Actual
Case Result
2.7 All filled text box should be Fill the customer’s All Customer See Fig
empty when Clear button is information in the Sign In information should be 1.1 and
clicked form. Then click Clear empty in the Sign In 1.2
button form

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 121
 Test Description Test Procedure Expected Result Actual
Case Result
2.8 The page will go to Fill the customer’s information Must go to See Fig
Customer Home page in the Sign In form. Then click Customer Home 1.1 and
once he/she login Sign In button page. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 122
 Test Description Test Procedure Expected Result Actual
Case Result
2.9 The page will go to Display Just click the Sign Out Must show Logout message. See Fig
page once he/she log out button in the Must go to Display page. 1.1 and
navigation. 1.2
Before Testing

Fig (1.1)

After Testing

Fig (1.2)

Page | 123
 Unit Test 3 Test Case: Data entry for Customer Designed by:
Sign In Aung Soe Khine
Data Source: Admin Registration Form Objective: To check that Admin Tester: Aung Soe Khine
Registration form works accurately.

Test Description Test Procedure Expected Actual

Case Result Results
3.1 Admin ID are automatically add Admin ID will not be shown in the Admin ID will See Fig
to a table within an admin form. Fill the other fields that remain be shown in 1.1
database when Admin register in the form. Then click Save button the database. and 1.2
in the Admin Registration form. and check the ID field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 124
 Test Description Test Procedure Expected Result Actual
Case Result
3.2 Admin cannot skip Skip the Name field and fill the Must warn that Name Text See Fig
without filling in the rest fields in admin registration Box should be filled out. 1.1 and
Name field form. Then click Save button. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 125
 Test Description Test Procedure Expected Result Actual
Case Result
3.3 Admin cannot Skip the Email field and fill the Must warn that Email Text Box See Fig
skip without rest fields in admin registration should be filled out. 1.1 and
filling in the form. Then click Save button. 1.2
Email field

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 126
 Test Description Test Procedure Expected Result Actual
Case Result
3.4 Email must be in Fill the Email field without @ and fill the Must warn that Admin See Fig
Email format rest fields in admin registration form. should enter an email 1.1 and
Then click Save button. address. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 127
 Test Description Test Procedure Expected Result Actual
Case Result
3.5 Admin cannot skip Skip the Password field and fill the rest Must warn that See
without filling in the fields in admin registration form. Then Password text box Fig 1.1
Password field click Save button. should be filled out and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 128
 Test Description Test Procedure Expected Result Actual
Case Result
3.5 Admin cannot skip Skip the Phone field and fill the rest Must warn that See
without filling in the fields in admin registration form. Then Phone text box Fig 1.1
Phone field click Save button. should be filled out and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 129
 Test Description Test Procedure Expected Result Actual
Case Result
3.7 The page should go to the Skip all the fields in Admin The page should go See
Admin Login Page when admin Registration form. Then click to the Admin Login Fig 1.1
click “I am already a member” “I am already a member” form. and 1.2
button. button.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 130
 Test Description Test Procedure Expected Result Actual
Case Result
3.8 Customer is not allowed to click Skip all the fields in Admin Must show all the See
Sign In button when the fields Registration form. Then click fields should be Fig 1.1
are empty. Save button. filled out and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 131
 Test Description Test Procedure Expected Result Actual
Case Result
3.9 All filled text box should Fill the admin’s information in All Admin’s information See
be empty when Clear the Admin Registration form. should be empty in the Fig 1.1
button is clicked Then click Clear button Admin Registration form and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 132
 Test Description Test Procedure Expected Result Actual
Case Result
3.10 An admin’s email cannot Fill the admin’s data that is Must warn that admin See
register twice. already exist in the database. email is already exist. Fig 1.1
Then click Save button. and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 133
 Test Description Test Procedure Expected Result Actual
Case Result
3.11 All admin information should be Fill the admin’s information All Admin See
saved accurately in admin table in in the admin registration information should Fig 1.1
database when admin click form. Then click Save button be saved in the and 1.2
Register button. database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 134
 Unit Test 4 Test Case: Data entry for Designed by:
admin login Aung Soe Khine
Data Source: Admin Login Form Objective: To check that Tester: Aung Soe Khine
Admin Login form works
accurately.
Test Description Test Procedure Expected Actual
Case Result Results
4.1 Admin can log in successfully if he Fill Email and Password in Must show See Fig
fill correct Email and Password in the Admin Login Form. Then Admin Signin 1.1 and
Sign In Form click Login button. success 1.2
message

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 135
 Test Description Test Procedure Expected Result Actual
Case Result
4.2 Admin cannot log in successfully Fill incorrect Email and Must show Admin See
if he fill incorrect Email and Password in the text box. Signin incorrect Fig 1.1
Password. Then click Sign In button and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 136
 Test Description Test Procedure Expected Result Actual
Case Result
4.3 Admin cannot skip without Fill the password field in the Sign Must warn that See
filling in the Email field. In form and skip the Email field. Email text box Fig 1.1
Then click Sign In button. should be filled out and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 137
 Test Description Test Procedure Expected Result Actual
Case Result
4.4 Email must be in Fill the Email field without @ and fill Must warn that admin See
Email format. password in customer sign in form. should enter an email Fig 1.1
Then click Save button. address and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 138
 Test Description Test Procedure Expected Result Actual
Case Result
4.5 Admin cannot skip Fill the Email field in the Sign In form Must warn that See
without filling in the and skip the Password field. Then Password text box Fig 1.1
Password field click Sign In button. should be filled out and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 139
 Test Description Test Procedure Expected Result Actual
Case Result
4.6 Admin is not allowed to Be empty in the Sign In form. Must warn that all the See
click Sign In button when Then click Sign In button. fields should be filled out Fig 1.1
the fields are empty. and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 140
 Test Description Test Procedure Expected Result Actual
Case Result
4.7 All filled text box should be Fill the customer’s All Admin information See
empty when Clear button is information in the Sign In should be empty in the Fig 1.1
clicked form. Then click Clear button Sign In form and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 141
 Test Description Test Procedure Expected Result Actual
Case Result
4.8 The page will go to Fill the admin’s information in the The page should go to See
Brand page (Admin Sign In form. Then click Sign In the Brand page if he/she Fig 1.1
page) once he/she button click Sign button and 1.2
login

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 142
 Test Description Test Procedure Expected Result Actual
Case Result
4.9 The page will go to Just click the Sign Out Must show Logout message. See Fig
Display page once button in the navigation. Must go to Display page. 1.1 and
he/she logout 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 143
 Unit Test 5 Test Case: Data entry for Designed by:
brand registration Aung Soe Khine
Data Source: Brand Registration Form Objective: To check that Tester: Aung Soe Khine
Brand Registration form
works accurately.
Test Description Test Procedure Expected Actual
Case Result Results
5.1 Brand ID are automatically add to BrandID will not be shown in BrandID will be See Fig
a table within a brand database. the form. Fill the other fields shown in the 1.1 and
that remain in the form. Then database. 1.2
click Save button and check
the ID field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 144
 Test Description Test Procedure Expected Result Actual
Case Result
5.2 Admin cannot skip Skip the Brand Name field Must warn that Brand Name See Fig
without filling in the Brand and fill the other fields. should be filled out. 1.1 and
Name field Then, click the Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 145
 Test Description Test Procedure Expected Result Actual
Case Result
5.3 Admin cannot skip Skip the Country field and Must warn that Country field See Fig
without filling in the fill the other fields. Then, should be filled out. 1.1 and
Country field click the Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 146
 Test Description Test Procedure Expected Result Actual
Case Result
5.4 Admin can edit the brand Click the edit button in the The page should go to the See Fig
name once he/she click brand listing table and then Brand update page and 1.1 and
the Edit button in the update the brand information must show that New 1.2
brand listing table Brand successfully saved.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 147
 Test Description Test Procedure Expected Result Actual
Case Result
5.5 Admin can delete the Click the delete button in the Must show that Brand See Fig
brand name once he/she brand listing table. successfully delete. 1.1 and
click the Delete button in 1.2
the brand listing table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 148
 Unit Test 6 Test Case: Data entry for Designed by:
color registration Aung Soe Khine
Data Source: Color Registration Form Objective: To check that Color Tester: Aung Soe Khine
Registration form works
accurately.
Test Description Test Procedure Expected Actual
Case Result Results
6.1 Color ID are automatically add to ColorID will not be shown in ColorID will be See Fig
a table within a color database. the form. Fill the field that shown in the 1.1 and
remain in the form. Then click database. 1.2
Save button and check the ID
field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 149
 Test Description Test Procedure Expected Result Actual
Case Result
6.2 Admin cannot skip Skip the Colour field. Then, Must show that Colour See Fig
without filling in the Color click the Save button . field should be filled out 1.1 and
field 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 150
 Test Description Test Procedure Expected Result Actual
Case Result
6.3 Admin can edit the color Click the edit button in the The page should go to See Fig
once he/she click the Edit Color listing table and then the Color update page 1.1 and
button in the color listing update the color. and must show that new 1.2
table. colour successfully save.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 151
 Test Description Test Procedure Expected Result Actual
Case Result
6.4 Admin can delete the Click the delete button in the Must show that Colour See Fig
color once he/she click Color listing table. successfully delete 1.1 and
the Delete button in the 1.2
color listing table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 152
 Unit Test 7 Test Case: Data entry for type Designed by:
registration Aung Soe Khine
Data Source: Size Registration Form Objective: To check that Size Tester: Aung Soe Khine
Registration form works
accurately.
Test Description Test Procedure Expected Actual
Case Result Results
7.1 Size ID are automatically add to a SizeID will not be shown in the SizeID will be See Fig
table within a type database. form. Fill the field that remain shown in the 1.1 and
in the form. Then click Save database. 1.2
button and check the ID field in
database.
Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 153
 Test Description Test Procedure Expected Result Actual
Case Result
7.2 Admin cannot skip Skip the Size field Then, click Must warn that Size field See Fig
without filling in the Size the Save button should be filled out 1.1 and
field. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 154
 Test Description Test Procedure Expected Result Actual
Case Result
7.3 Admin can edit the size Click the edit button in the Size The page should go to See Fig
once he/she click the listing table and then update the Size update page 1.1 and
Edit button in the size the color. and must show that new 1.2
listing table. size successfully save.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 155
 Test Description Test Procedure Expected Result Actual
Case Result
7.4 Admin can delete the size Click the delete button in the Must show that Size See Fig
once he/she click the SIze listing table. successfully delete 1.1 and
Delete button in the size 1.2
listing table.

Before Testing

Fig (1.1)

After Testing

Fig (1.2)

Page | 156
 Unit Test 8 Test Case: Data entry for type Designed by:
registration Aung Soe Khine
Data Source: Type Registration Form Objective: To check that Type Tester: Aung Soe Khine
Registration form works
accurately.
Test Description Test Procedure Expected Actual
Case Result Results
8.1 Type ID are automatically add to TypeID will not be shown in TypeID will be See Fig
a table within a type database. the form. Fill the field that shown in the 1.1 and
remain in the form. Then click database. 1.2
Save button and check the ID
field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 157
 Test Description Test Procedure Expected Result Actual
Case Result
8.2 Admin cannot skip Skip the Type field Then, click Must warn that type field See Fig
without filling in the Type the Save button should be filled out. 1.1 and
field. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 158
 Test Description Test Procedure Expected Result Actual
Case Result
8.3 Admin can edit the type Click the edit button in the The page should go to See Fig
once he/she click the Type listing table and then the Type update page 1.1 and
Edit button in the type update the type. and must show that New 1.2
listing table. Type successfully save.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 159
 Test Description Test Procedure Expected Result Actual
Case Result
8.4 Admin can delete the Click the delete button in the Must show that Type See Fig
type once he/she click Type listing table. successfully delete. 1.1 and
the Delete button in the 1.2
type listing table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 160
 Unit Test 9 Test Case: Data entry for staff Designed by:
registration Aung Soe Khine
Data Source: Staff Registration Form Objective: To check that Staff Tester: Aung Soe Khine
Registration form works
accurately.
Test Description Test Procedure Expected Actual
Case Result Results
9.1 Staff ID are automatically add to a StaffID will not be shown in StaffID will be See Fig
table within a staff database. the form. Fill the field that shown in the 1.1 and
remain in the form. Then click database. 1.2
Save button and check the ID
field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 161
 Test Description Test Procedure Expected Result Actual
Case Result
9.2 Admin cannot skip Skip the Staff Name field and Must warn that Staff See Fig
without filling in the Staff fill the other fields. Then, click Name should be filled 1.1 and
Name field. the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 162
 Test Description Test Procedure Expected Result Actual
Case Result
9.3 Admin cannot skip Skip the Staff Phone field and Must warn that Staff See Fig
without filling in the Staff fill the other fields. Then, click Phone should be filled 1.1 and
Phone field. the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 163
 Test Description Test Procedure Expected Result Actual
Case Result
9.4 Admin cannot skip Skip the Staff Address field Must warn that Staff See Fig
without filling in the Staff and fill the other fields. Then, Address should be filled 1.1 and
Address field. click the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 164
 Test Description Test Procedure Expected Result Actual
Case Result
9.5 Admin can edit the staff Click the edit button in the The page should go to See Fig
once he/she click the Edit Staff listing table and then the Staff update page 1.1 and
button in the staff listing update the staff and must show that New 1.2
table. Staff successfully save

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 165
 Test Description Test Procedure Expected Result Actual
Case Result
9.6 Admin can delete the Click the delete button in the Must show that Staff See Fig
staff once he/she click Staff listing table. successfully delete. 1.1 and
the Delete button in the 1.2
staff listing table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 166
 Unit Test 10 Test Case: Data entry for Designed by:
supplier registration Aung Soe Khine
Data Source: Supplier Registration Form Objective: To check that Tester: Aung Soe Khine
Supplier Registration form
works accurately.
Test Description Test Procedure Expected Actual
Case Result Results
10.1 SupplierID are automatically add SuppierID will not be shown in SupplierID will See Fig
to a table within a staff database. the form. Fill the field that be shown in the 1.1 and
remain in the form. Then click database. 1.2
Save button and check the ID
field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 167
 Test Description Test Procedure Expected Result Actual
Case Result
10.2 Admin cannot skip Skip the Supplier Name field Must warn that supplier See Fig
without filling in the and fill the other fields. Then, name should be filled 1.1 and
Supplier Name field. click the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 168
 Test Description Test Procedure Expected Result Actual
Case Result
10.3 Admin cannot skip Skip the Supplier Phone field Must warn that supplier See Fig
without filling in the and fill the other fields. Then, phone should be filled 1.1 and
Supplier Phone field. click the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 169
 Test Description Test Procedure Expected Result Actual
Case Result
10.4 Admin cannot skip Skip the Supplier Address Must warn that supplier See Fig
without filling in the field and fill the other fields. address should be filled 1.1 and
Supplier Address field. Then, click the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2

Page | 170
 Test Description Test Procedure Expected Result Actual
Case Result
10.5 Admin cannot skip Skip the Supplier Email field Must warn that supplier See Fig
without filling in the and fill the other fields. Then, email should be filled out. 1.1 and
Supplier Email field.. click the Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 171
 Test Description Test Procedure Expected Result Actual
Case Result
10.6 Email must be in Email Fill the Email field without @ Must warn that admin See Fig
format and fill other fields in supplier should enter an email 1.1 and
registration form. Then click address. 1.2
Save button.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 172
 Test Description Test Procedure Expected Result Actual
Case Result
10.7 Admin cannot skip Skip the Company field and fill Must warn that company See Fig
without filling in the the other fields. Then, click the should be filled out. 1.1 and
Company field. Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 173
 Test Description Test Procedure Expected Result Actual
Case Result
10.8 Admin can edit the Click the edit button in the The page should go to See Fig
supplier once he/she click Supplier listing table and then the Supplier update 1.1 and
the Edit button in the update the supplier. page and must show 1.2
supplier listing table. that New Supplier
successfully save.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 174
 Test Description Test Procedure Expected Result Actual
Case Result
10.9 Admin can delete the Click the delete button in the Must show that New See Fig
supplier once he/she click Supplier listing table. Supplier successfully 1.1 and
the Delete button in the save. 1.2
supplier listing table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 175
 Unit Test 11 Test Case: Data entry for Designed by:
product registration Aung Soe Khine
Data Source: Product Registration Form Objective: To check that Tester: Aung Soe Khine
Product Registration form
works accurately.
Test Description Test Procedure Expected Actual
Case Result Results
11.1 Product ID are automatically add ProductID will not be shown in ProductID will See Fig
to a table within a product the form. Fill the field that be shown in the 1.1 and
database. remain in the form. Then click database. 1.2
Save button and check the ID
field in database.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 176
 Test Description Test Procedure Expected Result Actual
Case Result
11.2 Admin cannot skip Skip the Product Name field Must warn that product See Fig
without filling in the and fill the other fields. Then, name should be filled 1.1 and
Product Name field. click the Save button out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 177
 Test Description Test Procedure Expected Result Actual
Case Result
11.3 Admin cannot skip Skip the Price field and fill the Must warn that price See Fig
without filling in the Price other fields. Then, click the should be filled out. 1.1 and
field. Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 178
 Test Description Test Procedure Expected Result Actual
Case Result
11.4 Admin cannot skip Skip the Quantity field and fill Must warn that quantity See Fig
without filling in the the other fields. Then, click the should be filled out. 1.1 and
Quantity field. Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 179
 Test Description Test Procedure Expected Result Actual
Case Result
11.5 Admin cannot skip Skip the Image fields and fill Must warn that image See Fig
without filling in the the other fields. Then, click the files should be selected. 1.1 and
Images field. Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 180
 Test Description Test Procedure Expected Result Actual
Case Result
11.6 Admin cannot skip Skip the Description field and Must warn that See Fig
without filling in the fill the other fields. Then, click description should be 1.1 and
Description field. the Save button filled out. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 181
 Test Description Test Procedure Expected Result Actual
Case Result
11.7 Admin cannot skip Skip the Review field and fill Must warn that review See Fig
without filling in the the other fields. Then, click the should be filled out. 1.1 and
Review field.. Save button 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 182
 Test Description Test Procedure Expected Result Actual
Case Result
11.8 Admin can edit the Click the edit button in the The page should go to See Fig
product once he/she click Product listing table and then the Product update page 1.1 and
the Edit button in the update the product. and must show that New 1.2
product listing table. Product successfully
save

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 183
 Test Description Test Procedure Expected Result Actual
Case Result
11.9 Admin can delete the Click the delete button in the Must show that New See Fig
product once he/she click Product listing table. Product successfully 1.1 and
the Delete button in the deleted. 1.2
product listing table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 184
 Unit Test 12 Test Case: Data entry for Designed by:
purchase product Aung Soe Khine
Data Source: Purchase Product Form Objective: To check that Tester: Aung Soe Khine
Purchase product form works
accurately.
Test Description Test Procedure Expected Actual
Case Result Results
12.1 Sub Total is automatically add to Sub Total will not be shown in Sub Total will See Fig
a Purchase Details once Admin the form. Fill the fields that be shown in the 1.1 and
add ProductID, Price and remain in the form. Then click Purchase 1.2
Quantity in the Purchase form. Save button and check the Details.
Sub Total in Purchase Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 185
 Test Description Test Procedure Expected Result Actual
Case Result
12.2 Admin cannot skip Skip the ProductID box and fill Must show that No See Fig
without choosing in the the other fields. Then, click the Product Information 1.1 and
ProductID box. Save button found. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 186
 Test Description Test Procedure Expected Result Actual
Case Result
12.3 Admin cannot skip Skip the Purchased Price Must warn that See Fig
without filling in the field and fill the other fields. Purchase price cannot 1.1 and
Purchased Price field. Then, click the Save button be zero. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 187
 Test Description Test Procedure Expected Result Actual
Case Result
12.4 Admin cannot skip Skip the Purchased Quantity Must warn that See Fig
without filling in the field and fill the other fields. Purchase quantity 1.1 and
Purchase Quantity field. Then, click the Save button cannot be zero. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 188
 Test Description Test Procedure Expected Result Actual
Case Result
12.5 Admin can clear all Purchased Click the Clear All Must show that no See Fig
Products once he/she click the button in the Purchase purchase record found 1.1 and
Clear All button in the Purchase Details table. in the Purchase Details. 1.2
Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 189
 Test Description Test Procedure Expected Result Actual
Case Result
12.6 Admin can purchase the Product Choose the Supplier in Must show that no See Fig
once he/she choose supplier the box and click the Purchase Process 1.1 and
and click the Purchase button in Purchase button in the Completed. 1.2
the Purchase Details table. Purchase Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 190
 Test Description Test Procedure Expected Result Actual
Case Result
12.7 Admin can remove the Purchase Click the Clear All Mustn’t show the See Fig
Product once he/she click button in the Purchase product in the Purchase 1.1 and
Remove button in the Purchase Details table. Detail Table. 1.2
Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 191
 Unit Test 13 Test Case: Data entry for purchase Designed by:
search Aung Soe Khine
Data Source: Purchase Search Objective: To check that Purchase Tester: Aung Soe Khine
Form search form works accurately.

Test Description Test Procedure Expected Result Actual

Case Results
13.1 Admin can search the Choose the PurchaseID that remain Must show See
purchased product by ID in the box. Then click Search button Purchase Fig 1.1
once he/she choose and check the purchase info in information by and 1.2
PurchaseID and click Purchase Search Details table. Purchase ID.
Search button.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 192
 Test Description Test Procedure Expected Result Actual
Case Result
13.2 Admin can search the Choose the PurchaseDate that Must show See Fig
purchased product by Date remain in the box and click Search Purchase 1.1 and
once he/she click Search by date radio button. Then click information by 1.2
by Date radio button, Search button and check the Purchase date.
choose purchased date purchase info in Purchase Search
and click Search button. Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 193
 Test Description Test Procedure Expected Result Actual
Case Result
13.3 Admin can view all Click Show All radio button. Must show all Purchase See Fig
purchased product once Then click Search button and information. 1.1 and
he/she click Show All check the purchase info in 1.2
button. Purchase Search Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 194
 Test Description Test Procedure Expected Result Actual
Case Result
13.4 Admin cannot search Choose PurchaseID and Click Must warn that no See Fig
purchased product by Search by date radio button. Purchase Record 1.1 and
ID if he/she click Search Then click Search button and Found. 1.2
by Date radio button. check the the purchase info in
Purchase Search Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 195
 Test Description Test Procedure Expected Result Actual
Case Result
13.5 Admin cannot search Choose PurchaseDate and Must warn that no See Fig
purchased product by Click Search by ID radio button. Purchase Record 1.1 and
date if he/she have click Then click Search button and Found. 1.2
Search by ID radio check the the purchase info in
button. Purchase Search Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 196
 Test Description Test Procedure Expected Result Actual
Case Result
13.6 Admin cannot search Choose Wrong PurchaseDate and Must warn that no See Fig
purchased product if Click Search by Date radio button. Purchase Record 1.1 and
he/she choose wrong Then click Search button and Found. 1.2
purchased date. check the the purchase info in
Purchase Search Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 197
 Test Description Test Procedure Expected Result Actual
Case Result
13.7 Admin can view and print Click View Detail in the Must show the print See Fig
Purchase Detail Report once Purchase Search invoice for the Product 1.1 and
he/she click View Detail in the Details table. Purchase. 1.2
Purchase Search Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 198
 Test Description Test Procedure Expected Result Actual
Case Result
13.8 Admin can clear the Purchase ID and Click Clear Must clear the PurchaseID See Fig
Purchase Date that he has filled in the button in the and Purchase Date in the 1.1 and
text box once he/she click Clear button. Search Option. text box 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 199
 Unit Test 14 Test Case: Data entry for Designed by:
order search Aung Soe Khine
Data Source: Order Search Form Objective: To check that Order Tester: Aung Soe Khine
search form works accurately.

Test Description Test Procedure Expected Result Actual

Case Results
14.1 Admin can search the ordered Choose the OrderID that Must show Order See Fig
product by ID once he/she remain in the box. Then click information by 1.1 and
choose OrderID and click Search button and check the Order ID. 1.2
Search button. order info in Order Search
Details table..

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 200
 Test Description Test Procedure Expected Result Actual
Case Result
14.2 Admin can search the Choose the OrderDate that Must show Order See Fig
ordered product by Date remain in the box and click information by Order 1.1 and
once he/she click Search Search by date radio button. date. 1.2
by Date radio button, Then click Search button and
choose purchased date check the order info in Order
and click Search button. Search Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 201
 Test Description Test Procedure Expected Result Actual
Case Result
14.3 Admin can view all Click Show All radio button. Must show all Order See Fig
ordered product once Then click Search button and information. 1.1 and
he/she click Show All check the order info in Order 1.2
button. Search Details..

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 202
 Test Description Test Procedure Expected Result Actual
Case Result
14.4 Admin cannot search Choose OrderID and Click Must show that no sales See Fig
ordered product by ID Search by date radio button. Record Found. 1.1 and
if he/she click Search Then click Search button and 1.2
by Date radio button. check the the order info in Order
Search Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 203
 Test Description Test Procedure Expected Result Actual
Case Result
14.5 Admin cannot search Choose OrderDate and Click Must show that no sales See Fig
ordered product by date Search by ID radio button. Record Found. 1.1 and
if he/she have click Then click Search button and 1.2
Search by ID radio check the the order info in
button. Order Search Details..

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 204
 Test Description Test Procedure Expected Result Actual
Case Result
14.6 Admin cannot search Choose Wrong OrderDate and Must show that no See Fig
ordered product if Click Search by Date radio sales Record Found. 1.1 and
he/she choose wrong button. Then click Search button 1.2
purchased date. and check the order info in Order
Search Details.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 205
 Test Description Test Procedure Expected Result Actual
Case Result
14.7 Admin can view and print Order Click View Detail in the Must show the print See Fig
Detail Report once he/she click Purchase Search invoice for the Product 1.1 and
View Detail in the Order Search Details table. Purchase. 1.2
Details table.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 206
 Test Description Test Procedure Expected Result Actual
Case Result
14.8 Admin can clear the Order ID and Click Clear Must clear the PurchaseID See Fig
Order Date that he has filled in the text button in the and Purchase Date in the 1.1 and
box once he/she click Clear button. Search Option. text box 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 207
 Unit Test 15 Test Case: Data entry for Designed by:
checkout Aung Soe Khine
Data Source: Checkout Form Objective: To check that Tester: Aung Soe Khine
Checkout form works
accurately.
Test Description Test Procedure Expected Result Actual
Case Results
15.1 Customer cannot checkout Skip the Contact field and fill Must warn that See
without filling contact phone. the other fields. Then, click contact phone Fig 1.1
the Checkout button. should be filled out. and 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 208
 Test Description Test Procedure Expected Result Actual
Case Result
15.2 Customer cannot checkout Skip the Delivery Must warn that contact See Fig
without filling delivery address. Address field and fill the phone should be filled 1.1 and
other fields. Then, click out. 1.2
the Checkout button..

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 209
 Test Description Test Procedure Expected Result Actual
Case Result
15.3 Customer can remove the Click the Remove Mustn’t show the product See Fig
product that he added in the button Shopping Cart information in the 1.1 and
Shopping Cart Details table. Details table. Shopping Cart Details. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 210
 Test Description Test Procedure Expected Result Actual
Case Result
15.4 Customer can remove all the Click the Empty Cart Must show that no See Fig
product that he added by clicking button in the Shopping shopping cart is empty. 1.1 and
Empty Cart button in the Cart Details table. 1.2
Shopping Cart.

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 211
 Test Description Test Procedure Expected Result Actual
Case Result
15.5 Customer can go to the Display Click the Product Must go to the product See Fig
page by clicking Product Display Display button in the display page. 1.1 and
button in the Shopping Cart. shopping cart. 1.2

Before Testing

Fig (1.1)
After Testing

Fig (1.2)

Page | 212
 Test Description Test Procedure Expected Result Actual
Case Result
15.6 Customer can successfully order the Fill the delivery address Must show See Fig
product by filling contact phone and and contact phone in the Checkout process 1.1 and
delivery address and clicking the Checkout info. Then click complete and go to 1.2
Checkout button in the Shopping Checkout button in the the sales invoice
Cart. shopping cart. page.

Before Testing

Fig (1.1)

After Testing

Fig (1.2)

Page | 213
User Guide

Customer Registration

2 3

1. Fill all the customer fields.

2. Click Save button in order to add the customer information in the database.
3. Click the Clear button to remove all the customer information that are already filled in
the fields.

Page | 214
Customer Login

1. Fill all customer field.

2. Click Sign in button in order to login the user account.

Admin Registration

3 4

1. Fill all the admin fields

2. Click Save button in order to add the admin information in the database.
3. Click the I am already a member to go to the admin login page.
4. Click the Clear button to remove all the admin information that are already filled.

Page | 215
 Admin Signin

1. Fill all customer field.

2. Click Sign in button in order to login the user account.
3. Click the Clear button to remove all the admin information that are already filled.

Sign Up and Sign In page guideline

2 1

1. Customer registration page

2. Customer Login page
3. Admin registration page

Page | 216
Brand registration

1. Fill all brand fields.

2. Click Save button to register brand.

Color registration

1
2

1. Fill the color field.

2. Click Save button to register color

Page | 217
Size registration

1. Fill the size field.

2. Click Save button to register size.

Type registration

1. Fill the type field.

2. Click Save button to register type.

Page | 218
 Staff Registration

v
2 3

1. Fill all the staff fields.

2. Choose Staff Role in the box.
3. Click Save button to register the staff.

Supplier Registration

c
v
c
2 v

c
v

1. Fill all the supplier fields.

2. Click Save button to register the staff.

Page | 219
Product Registration

3
1
c
c
v
v
v
2 4
v
c
c5 6 v
v v
vc c
vv v
v v
v type, color, brand and size in the box.
1. Choose
2. Fill Product Name, Price and Quantity in the field.
3. Choose image file from pc.
4. Fill Description and Review in the fields
5. Click Save button to register the product.
6. Click Clear button to remove all the text and image files that are remained in the box

Page | 220
Purchase

c2
v
vc
3
vv
vc
vv
v
1. Choose Product in the box. v

2. Fill Purchase Price and Quantity in the field.

3. Click Add button to purchase the product.

Purchase Search (Search by PurchaseID)

1 c
v
c2 v
v
v
vc
vv
v
v

1. Click Search by ID radio button.

2. Choose PurchaseID in the box.
3. Click Search button to search the purchase information.

Page | 221
Purchase Search (Search by PurchaseDate)

1
3 4 5

c
c c c
v
v v v
2 v
v v v
v
v v v

c
v
v
v
1. Click Search by Date radio button.
2. Choose Purchase Date in the box.
3. Click Search button to search the purchase information.
4. Click Show All button to see all purchase information.
5. Click Clear button to remove all the text that are remained in the box.

Order Search (Search by OrderID)

1
c
v
2
c v
v v
vc
vv
v
1. Click Search by ID radio button.
v
2. Choose Order ID in the box.
3. Click Search button to search the order information.

Page | 222
Order Search (Search by Order Date)

1
3

c
c
2 v
v
v
v
v
v
c
v
v
v

1. Click Search by Date radio button.

2. Choose Order Date in the box.
3. Click Search button to search the order information.
4. Click Show All button to see all order information.
5. Click Clear button to remove all the text that are remained in the box.

Page | 223
Checkout

c
1 v
v
v
2 c
v 4
v
c 5v 6
v c
v v
v c vc
v vv
v v
v v

1. Choose Credit card type.

2. Choose payment type.
3. Fill Customer Contact phone.
4. Fill Customer Delivery address.
5. Click Checkout button to order the product.
6. Click Cancel button to clear the fields that are already filled out.

Page | 224
System Code

No Form Function Description

1. Customer Sign CheckEmail To check the email not to duplicate.
Up Form Save() To record the info in the database.
AutoID() To generate UserID automatically.
Clear() To remove all filled info in the fields.
2. Customer Login CheckUser() To check the user email which is not in
the database.
CheckPassword() To check the user password which is not
in the database.
Signin() To login into the customer page.
Clear() To remove all filled info in the fields.
3. Admin Sign Up checkAdminEmail() To check admin email not to duplicate.
Save() To record the info in the database.
AutoID() To generate AdminID automatically.
Clear() To remove all filled info in the fields.
4. Admin Login CheckUser() To check the admin email which is not in
the database.
CheckPassword() To check the admin password which is
not in the database.
Signin() To login into the admin page.
Clear() To remove all filled info in the fields.
5. Brand CheckBrand() To check the brand not to duplicate.
Save() To record the info in the database.
AutoID() To generate BrandID automatically.
Edit() To update the Brand details.
Delete() To delete the Brand details.
6. Color CheckColor() To check the color not to duplicate.
Save() To record the info in the database.
AutoID() To generate ColorID automatically.
Edit() To update the Color details.
Delete() To delete the Color details.

Page | 225
7. Type CheckType() To check the type not to duplicate.
Save() To record the info in the database.
AutoID() To generate TypeID automatically.
Edit() To update the Type details.
Delete() To delete the Type details.
8. Size CheckSize() To check the size not to duplicate.
Save() To record the info in the database.
AutoID() To generate SizeID automatically.
Edit() To update the Size details.
Delete() To delete the Size details.
9. Supplier CheckName() To check the name not to duplicate.
Registration CheckEmail() To check the email not to duplicate.
Save() To record the info in the database.
AutoID() To generate SupplierID automatically.
Edit() To update the supplier information.
Delete() To delete the supplier information.
10. Staff CheckName() To check the name not to duplicate.
Registration CheckEmail() To check the email not to duplicate.
Save() To record the info in the database.
AutoID() To generate StaffID automatically.
Edit() To update the staff information.
Delete() To delete the staff information.
11. Product CheckProductName() To check product name not to duplicate.
Registration AutoID() To generate ProductID automatically.
Save() To record the info in the database.
Edit() To update the product information.
Delete() To delete the product information.
12. Purchase Add() To add the product into the purchase
details.
CalculateQuantity To calculate the total quantity
automatically.
CalculateAmount() To calculate the total amount
automatically.

Page | 226
 CalculateTax() To calculate the government tax
automatically.
CalculateNetAmount() To calculate the net amount
automatically.
ClearAll() To clear all the product info that are
added in the purchase details.
Remove() To remove only one product info that is
added in the purchase details.
13. Order Shoppingcart() To add the product into shopping cart.
Remove() To remove only one product info that is
added in the shopping cart.
Clearall() To clear all the product info that are
added in the shopping cart.
Checkout() To order the product
CalculateAmount() To calculate total amount automatically.
CalculateQuantity() To calculate total quantity automatically.
AutoID() To generate UserID automatically.

Page | 227