Page 1 of 82

Please Complete all areas of this form, Sign and attached to each submitted
project. Submit the project according to the instructions provided in your
Course Outline.

A.STUDENT/S TO COMPLETE

Name of the Project / System: POS System (Point of Sale)

Course Name : DiTEC

Batch Number : 189

Name of the Lecturer : Mr. Nuwan Hirantha

Date Due: Date Submitted:

Name of the Student :

Reg.No Student ID Name Signature

00098106 E116875 Ravidu Fernando

DITEC : 189 POS SYSTEM

 Page 2 of 82

ACKNOWLEDGEMENT

Performing Our Assignment, I had to take the guideline of

some respectful Person to deserve our greatest gratitude. I
would like to show our gratitude to;

• Mr. Nuwan Hirantha

DITEC : 189 POS SYSTEM

 Contents
Page 3 of 82

Acknowledgment………………………………………………………………………..
Contents………………………………………………………………………………………
Coffee Shop Introduction…………………………………………………………….
Introduction…………………………………………………………………………………
Environment of the current system …………………………………………….
Project Scope………………………………………….....................................
Requirements Analysis………………………………………………………………..
• Observation of current procedure

Requirement Gathering………………………………………………………………
• Functional requirement
• Non-Functional requirement

System Design……………………………………………………………………………..
• Design Methodology
• Use Case Diagram
• Class Diagram

Data Base Design……………………………………..…………………………………

• ER Diagram
• Database Design (Screenshots)

Software Development……………………………………………………………….
• UI Design
• Cording

Software Testing…………………………………………………………………………
• What Is Testing
• Testing Type (Black Box Testing)
• Software Testing (Screenshots)

Deployment………………………………………………………………………………..
Conclusion…………………………………………………………………………………..
Software Softcopy……………………………………………………………………….
DITEC : 189 POS SYSTEM
 Page 4 of 82

Coffee Shop Introduction

In this Coffee Shop is an establishment that

primarily give of various types of coffee and
desserts. Specially espresso, latte, Iced tea and
cappuccino. Some coffeehouses may serve cold
drinks, such as milk shake, as well as other non-
caffeinated beverages. A coffeehouse may also
serve food, such as light snacks, sandwiches,
muffins, fruit, or pastries. Coffeehouses range from
owner-operated small businesses to large
multinational corporations. Some coffeehouse
chains operate on a franchise business model,
with numerous branches across various countries
around the world.

DITEC : 189 POS SYSTEM

 Page 5 of 82

Introduction
This document is intended to give a complete planning of a POS system for a newer
Coffee shop. This plan is designed to ensure those features work up to the mark.
How to handle this software and all its features are contained in this Document. The
following paragraphs will discuss the purpose of the plan and the scope of testing.

The environment of the current system

At the start of my project, I collected information about the current environment of
the system. It was the manual system. They were manually updating the bills in the
logbooks. They were forming written logs for every action. For customer information,
Discounts, payments etc.

This system must perform the following functions :

➢ Log in.
➢ Can place unlimited orders with customer details.
Example :
o Customer Mobile Number.
o Customer Name.
o Order Details ( Date, Time, Amount, and Coffee Categories )
o Serving methods ( Dine or Take out )
o Payment types ( Cash or Card )

➢ There are four types of Coffee, four types of iced Coffee, and four types of Cakes.

➢ Can add various types of coupons ( discounts )

o Requires Manager Access to Apply Discounts.
o There are six discounts and if can gives totally free also.

➢ Search customer’s details when any time it’s requested.

➢ Edit customer’s details.
➢ Delete customer’s details.
➢ Reduce Manual operations and functions via this.

Project Scope
• By a POS System managing customer information and updating the food varieties is a
better idea for any newer shops.

• Login module: The login module will help authenticate users’ accounts who have
login ID passwords and can only login into the POS System.
• Computerized systems allow for greater efficiency in performing specific tasks both
accurately and more rapidly than doing the task. Computerized systems also offer
storage capacity efficiency.

For examples;

• A Computerized system’s hard drive taking up a relatively small amount of space can
store a large collection of business or personal documents. A paper-based system in
the contract would take up a least one and usually more file cabinets for storage of
the same document collection.

DITEC : 189 POS SYSTEM

 Page 6 of 82

Requirements Analysis
An analyst must collect information about the system that has
problems. The information will provide the basic for both a
feasibility study and an in the depth analysis of the system to
produce a solution. The analyst seeks answers to questions.

Observation of current procedure

The system analysts can learn lot by simply watching what
happens in the existing system. It is possible to see exactly what
is done. So that the analyst obtains reliable information. Little
planning is necessary because it does not involve working directly
with other people. It may relatively quick and cheap to carry out.

Negative points of the current system

1. All the bills have written by the physical paper, and it

can have been damaged.
2. Anyone can access data without permission
3. Take more time to update written logs one by one
4. Need a physical space to store data
5. Very old bills will be hard to find
6. Some bills have already been lost
7. Cannot update information Easily

DITEC : 189 POS SYSTEM

 Page 7 of 82

REQUREMENT GATHERING

The requirement generally divides into two types. They are

functional and non-functional requirements.

FUNCTIONAL REQUIREMENTS

Any requirement which is specifies what the system should do is a

functional requirement. The functional requirement will describe a
particular behavior function requirement system when certain conditions
are met.
• Authentication and authorization – When logging into the system,
only authorized persons should have access to relevant parts of
the system.
• Place new order – Ability to place a new order.
• Give a discount to the customer – Before giving a discount to the
Customer need Manager access.
• Add customer information – Ability to create a new order with
customer information.
• Can Change a payment type – If the customer has a card, He can
pay by card otherwise pay by cash.
• Search existing customers – Ability to search customer information
and order details.
• Update existing customers – Ability to change customer
information in a database.
• Delete existing customers - Ability to remove customer
information in a database.

NON-FUNCTIONAL REQUIREMENTS
• Any requirement which specifies how the system performs a
certain function is a nonfunctional requirement. This Generally
specifies the system quality attributes of the characteristics.
• Performance – Users who access the software should be able to
work the seamlessly
• Reliability – Software should work properly in a specified
environment and for a given amount of time.
• Security – Unauthorized access to the system and software itself
should be prohibited.
• Usability – software should be easy to navigate and easy to learn.
• Maintainability – The possibility to evolve the software to meet the
changing customers.

DITEC : 189 POS SYSTEM

 Page 8 of 82

DITEC : 189 POS SYSTEM

 Page 9 of 82
System Design
Design Methodology
Waterfall Model

Requirement
analyzing and
Definition

Software and System

Design

Implementation and
unit testing

Integration and
system testing

Delivery

Maintenance

Requirement analysis and definition.

• Gathering required information and make limitations to achieve the goals of both uses
and in a way that both parties can understand.

System and software design.

• This phase establishes overall system architecture. This includes representing the
software system function in a form that may be transformed into one or more programs.

Implementation and unit testing.

• In the phase software design is realized as set of programs or units. In unit testing
verification of units to their specifications are carried out.

Integration and system testing.

• Here mainly the individual programs or units. In unit testing verifications of units to their
specifications are carried out.

Operations and Maintenance.

• This phase takes the longest time because after the software is installed to ensure that
all the problems have been resolved and other improvements are done according to the
requirement of the user.

DITEC : 189 POS SYSTEM

 Page 10 of 82

System Design

Use Case Diagram

DITEC : 189 POS SYSTEM

 Page 11 of 82

System Design

Use Class Diagram

DITEC : 189 POS SYSTEM

 Page 12 of 82

Database Design

DITEC : 189 POS SYSTEM

 Page 13 of 82

Database Design

Entity-Relationship Model

DITEC : 189 POS SYSTEM

 Page 14 of 82

Database Design

1. SQL Design
Table 1 (Login)

DITEC : 189 POS SYSTEM

 Page 15 of 82

Database Design

1.1 SQL Design

Table 2 (Customers Details)

DITEC : 189 POS SYSTEM

 Page 16 of 82

Software Development
C# Design with Cording

DITEC : 189 POS SYSTEM

 Page 17 of 82

Login Form UI Design

Login

Exit

Login

Exit

DITEC : 189 POS SYSTEM

 Page 18 of 82

Access Form UI Design

All Orders

POS System

POS
System

All
Orders

DITEC : 189 POS SYSTEM

 Page 19 of 82

POS System Form UI Design

Back

New Page Log Out

Info

Exit

How to Place an Order with Correct Steps in this POS System.

1. Greet the Customer and select customer needs.
2. Confirm the Customer Order.
3. If you want to give a customer discount to the customer, put a tick on the Manager
Access box, and then the Coupon button will be enabled.
4. Press the Coupon Button, Then the Manager access form will be displayed input the ID
and password, Then select the Coupon which you want. After adding a discount, the Form
will be back to the main Form.
5. Pressing the Amount Button, you can check the total amount of the order with a discount
or without.
6. Press the Customer Button, Then the customer information form will be displayed, and
you will be able to input the Customer Information. After inputting Customer information,
the Form will be back to the main Form.
7. Go to the Payment option as the final task. Then the customer can pay the order via cash
or card.

DITEC : 189 POS SYSTEM

 Page 20 of 82

DITEC : 189 POS SYSTEM

 Page 21 of 82

• If you need to add a Discount to the customer ,Then press coupon button and follow these
steps, Otherwise straight Forward to Amount Button (No.5)
• You must need Manager Password to Access this discount form
•

Manager Access Form

• After Clicked Coupon Button, This Form will be opened

1 2

DITEC : 189 POS SYSTEM

 Page 22 of 82

DITEC : 189 POS SYSTEM

 Page 23 of 82

Coupon Form
• After login complete, Coupon form will be displayed as this

Coupons

DITEC : 189 POS SYSTEM

 Page 24 of 82

DITEC : 189 POS SYSTEM

 Page 25 of 82

DITEC : 189 POS SYSTEM

 Page 26 of 82

Customer Information Form

• When you have Clicked the Customer Button, This Form
will be Displayed.

Create an Order

DITEC : 189 POS SYSTEM

 Page 27 of 82

• When you have created the order, Form will be back to the main form
and press the payment button after this (No.7).

DITEC : 189 POS SYSTEM

 Page 28 of 82

Payment Form
• When you have Clicked the Payment Button, This Form will be Displayed

1 4

2
5

DITEC : 189 POS SYSTEM

 Page 29 of 82

DITEC : 189 POS SYSTEM

 Page 30 of 82

Log Out

New Page

Back

Info

Exit

DITEC : 189 POS SYSTEM

 Page 31 of 82

Database Form UI Design

1
Back

1
Back

DITEC : 189 POS SYSTEM

 Page 32 of 82

DITEC : 189 POS SYSTEM

 Page 33 of 82

DITEC : 189 POS SYSTEM

 Page 34 of 82

DITEC : 189 POS SYSTEM

 Page 35 of 82

DITEC : 189 POS SYSTEM

 Page 36 of 82

What is software testing definition?

Software testing is the process of evaluating and verifying that a

software product or application does what it is supposed to do.
The benefits of testing include preventing bugs, reducing
development costs, and improving performance.

Testing Type

In the approach the program is assumed to be a Blackbox where

the processing logic unit cannot be seen. This means that what is
happening inside the program is not important to the person who
is carrying out the testing. The tester is worried about the output
that the program producers. Therefore, the aim of testing is to
check whether the program producers. Therefore, the aim of
testing is to check whether the program producers the correct
output for every single input.

DITEC : 189 POS SYSTEM

 Page 37 of 82

Unit Testing
• Unit testing is a software development process in which the
smallest testable parts of an application, called units, are
individually and independently scrutinized for proper operation.
Integration Testing
• Type of software testing in which the different units, modules or
components of a software application are tested as a combined
entity.
System Testing
• In a working environment, a data processing application may
involve anything between a handful hundreds of programs, all of
which must interact to provide a service to the user. Testing in
such an environment involves not only testing each individual
program but also testing the flow of data through the system.
Essentially this is only a larger version of the procedure used in
testing a single program because we are still testing several
modules (in this case each is a program), the sequence in which
they operate and the communicate of data between them.

Test Plan

The description should include

• The Identify of the component to be tested
• The purpose of the test
• Test data to be used
• The conditions under which the test is to be carried out
• Test expected out come

DITEC : 189 POS SYSTEM

 Page 38 of 82

TABLE OF CONTENTS

1. Introduction

2. Objectives and Tasks

3. Scope

4. Testing Strategy

5. Features To be Tested

6. Types of testing done

7. Major Deliverables

DITEC : 189 POS SYSTEM

 Page 39 of 82

INTRODUCTION
This document is intended to give a complete planning of a systematic
strategy for software testing of the Coffee Shop. Coffee Shop is composed of
numerous features. This test plan is designed to ensure those features work
up to the mark. Both directly and indirectly affected elements will be
addressed here. In the following paragraphs will discuss the purpose of the
plan and its scope of testing.

OBJECTIVES AND TASKS

This test plan document supports the following objectives:

• Identify the exiting project information.

• Identify the approach that should be followed.
• Identify the features that should be tested.
• Recommend and describe the testing strategies to be employed.
• Identify the required resources.
• Identify the risks associated with the test strategy.
• List the deliverable elements of the test activates.

SCOPE
This Document will mainly provide the blueprint of high-level testing
approaches of Coffee Shop. It will validate major system functions against
the requirements. The interfaces used by the following user roles of the
system, and each user roles ‘functionality will be tested.
User roles:
1. Manager
2. Salesman
3. Customer

DITEC : 189 POS SYSTEM

 Page 40 of 82

TESTING STRATEGY
Testing will be done manually. It will cover the main requirements of the
different roles participating in the site. I will be focusing only on the features
mentioned in the Features to be tested due to the limited time I have.

FEATURES TO BE TESTED
The following is a list of the areas to be focused on during testing of the
application:
• Login
• Take an Order
• Confirm the Order
• Add a discount
• Get the Customer information
• Accept the payment
• Place an order
• Update Customer Information
• Delete Customer Information
• Logout

TYPES OF TESTING DONE

• Black Box testing

MAJOR DELIVERABLES
• Test Plan
• Test Cases
• Test Result

DITEC : 189 POS SYSTEM

 Page 41 of 82

Test Cases

1. Log in Page

Test case 1.0

Input the correct username and password
Expected output:
The user gets access to the Next Page
Actual output:

DITEC : 189 POS SYSTEM

 Page 42 of 82

Test case 1.1

Input the incorrect username and correct password
Expected output:
The user doesn’t get access to the Next Page
Actual output:

DITEC : 189 POS SYSTEM

 Page 43 of 82

Test case 1.2

Input the correct username and incorrect password
Expected output:
The user doesn’t get access to the Next Page
Actual output:

DITEC : 189 POS SYSTEM

 Page 44 of 82

Test case 1.3

Input the incorrect username and incorrect
password
Expected output:
The user doesn’t get access to the Next Page
Actual output:

DITEC : 189 POS SYSTEM

 Page 45 of 82

Test case 1.4

The Exit Button
Expected output:
Exit The Application
Actual output:
The application has closing

DITEC : 189 POS SYSTEM

 Page 46 of 82

2. POS System 5. All Orders

Test case 2.0

The POS System Button
Expected output:
The user will access the POS System
Actual output:

DITEC : 189 POS SYSTEM

 Page 47 of 82

Test case 2.1

Refresh Button
Expected output:
The POS System Page will be Refreshed
Actual output:

DITEC : 189 POS SYSTEM

 Page 48 of 82

Test case 2.2

Log Out Button
Expected output:
Back to the Login Page
Actual output:

DITEC : 189 POS SYSTEM

 Page 49 of 82

Test case 2.3

Back Button
Expected output:
Back to the Main Menu
Actual output:

DITEC : 189 POS SYSTEM

 Page 50 of 82

Test case 2.4

Select Info Button
Expected output:
It is showing Coffee Queen Webpage Address

DITEC : 189 POS SYSTEM

 Page 51 of 82

Test case 2.4 Actual output:

Test case 2.5

Select Exit Button
Expected output:
POS System will be Exit

DITEC : 189 POS SYSTEM

 Page 52 of 82

Test case 2.5

Test case 2.5 Actual output:

DITEC : 189 POS SYSTEM

 Page 53 of 82

Test case 2.6

Select any food varieties
Expected output:
The user can view items which are ordered on
the right-side in yellow box
Actual output:

DITEC : 189 POS SYSTEM

 Page 54 of 82

Test case 2.6 Actual output:

Test case 2.7

If you think it’s enough, then Select Confirm Button
Expected output:
The user will not be able to select foods anymore
and confirm button will be disabled.

DITEC : 189 POS SYSTEM

 Page 55 of 82

Test case 2.7 Actual output:

Test case 2.8

Select Manager Access
Expected output:
Coupon Button will be Enabled

DITEC : 189 POS SYSTEM

 Page 56 of 82

Test case 2.8 Actual

output:

Test case 2.9

Select Coupon Button
Expected output:
Manager access page will be displayed.

DITEC : 189 POS SYSTEM

 Page 57 of 82

Test case 2.9 Actual output:

Test case 3.0

Input the incorrect username and incorrect
password
Expected output:
The user doesn’t get access to the Discount page

DITEC : 189 POS SYSTEM

 Page 58 of 82

Test case 3.0 Actual output:

Test case 3.1

Input the correct username and correct password
Expected output:
The user gets access to the Discount page
Actual output:

DITEC : 189 POS SYSTEM

 Page 59 of 82

Test case 3.2

Select any Discount Button
Expected output:
Discount will be added to the bill then discount
page will be closed and back to the POS System
Actual output:

DITEC : 189 POS SYSTEM

 Page 60 of 82

Test case 3.3

Select Amount Button
Expected output:
Amount Button will be disabled, Total amount with
discount amount, discount type will be shown on
the right side of the yellow box and Customer
Button will be enabled
Actual output:

DITEC : 189 POS SYSTEM

 Page 61 of 82

Test case 3.4

Select Customer Button
Expected output:
 Customer Registration page will be shown with
Customer Order details
Actual output:

DITEC : 189 POS SYSTEM

 Page 62 of 82

Test case 3.5

Input customer Details and click order now button
Expected output:
 Oder has processed and its self-back to the POS
System
Actual output:

DITEC : 189 POS SYSTEM

 Page 63 of 82

Test case 3.6

Select the Payment Button
Expected output:
 Payment page will be Displayed with total amount
Actual output:

DITEC : 189 POS SYSTEM

 Page 64 of 82

Test case 3.7

If customer has cash, Put the tik into the Cash.
Expected output:
 Select cash amount group will be Enabled
Actual output:

DITEC : 189 POS SYSTEM

 Page 65 of 82

Test case 3.8

Select amount of cash customer gave to you.
Expected output:
 Amount of cash will be added to the cash amount box
Actual output:

DITEC : 189 POS SYSTEM

 Page 66 of 82

Test case 3.9

Select Check Balance Button on the right side
Expected output:
 Customer amount minus from the Total amount and
it has shown in the Balance Box
Actual output:

DITEC : 189 POS SYSTEM

 Page 67 of 82

Test case 4.0

If customer has card, Put the tik into the Card
Expected output:
 Card accepted button will be enabled
Actual output:

DITEC : 189 POS SYSTEM

 Page 68 of 82

Test case 4.1

Select card accepted button
Expected output:
 “No Balance” will be shown in the Balance Box and
Order Confirm Button will be enabled
Actual output:

DITEC : 189 POS SYSTEM

 Page 69 of 82

Test case 4.2

Select Order Confirmed Button
Expected output:
 New Page of the POS System will be shown
You can place a New Order

DITEC : 189 POS SYSTEM

 Page 70 of 82

Test case 4.2 Actual output:

DITEC : 189 POS SYSTEM

 Page 71 of 82

2. POS System 5. All Orders

5. All Orders Page (Database)

DITEC : 189 POS SYSTEM

 Page 72 of 82

Test case 5.0

Select Back Button
Expected output:
 Back to the Main Menu
Actual output:

2. POS System 5. All Orders

DITEC : 189 POS SYSTEM

 Page 73 of 82

Test case 5.1

Input a correct Order Number and select the Search
Button
Expected output:
 The correct customer details referred to the Order
number will be displayed

DITEC : 189 POS SYSTEM

 Page 74 of 82

Test case 5.1 Actual output:

Test case 5.2

Input an incorrect Order Number and select the
Search Button
Expected output:
 A message box will be displayed to say the invalid
data

DITEC : 189 POS SYSTEM

 Page 75 of 82

Test case 5.2 Actual output:

DITEC : 189 POS SYSTEM

 Page 76 of 82

Test case 5.3

Updating an existing customer detail (Save Button)
Expected output:
 The user will be displayed a question box to confirm
the changes. If the answer is Yes (5.3.1) changes will
be updated. If the answer is No (5.3.2) the customer
detail will not be updated
Actual output:

DITEC : 189 POS SYSTEM

 Page 77 of 82

Yes (5.3.1)

No (5.3.2)

DITEC : 189 POS SYSTEM

 Page 78 of 82

Test case 5.4

Select the Refreshed Button
Expected output:
 Page will be Refreshed
Actual output:

DITEC : 189 POS SYSTEM

 Page 79 of 82

Test case 5.5

 Click delete button to delete customer detail by
customer order number
Expected output:
 The user will be displayed a question box to
confirm the changes. If the answer is Yes (5.4.1)
customer detail will be deleted. If the answer is
No (5.4.2) the customer detail will not be deleted
Actual output:

DITEC : 189 POS SYSTEM

 Page 80 of 82

No (5.5.2)

Yes (5.5.1)

DITEC : 189 POS SYSTEM

 Page 81 of 82

DEPLOYMENT

Software deployment includes all the steps, processes, and

activities that are required to make a software system or update
available to its intended users. Today, most IT organizations and
software developers deploy software updates, patches, and new
applications with a combination of manual and automated
processes. Some of the most common activities of software
deployment include software release, installation, testing,
deployment, and performance monitoring.

Problems Faced when developing the system

• Time Management was difficult

• Difficulty to find a suitable design

CONCLUSION

❖POS system enable people to efficiently manage

their business using software and equipment,
designed to electronically deal with the
processes linked to a retail or restaurant
business.

DITEC : 189 POS SYSTEM

 Page 82 of 82

CHART
Number of Days 1 to 30

3 2

12

11

Requirements Analysis
System and software designing
Cording
Implemention and unit testing
Integration and system testing

• I started my program on 6th of November 2022.

• I finished my program on 4th of December 2022.

DITEC : 189 POS SYSTEM