DESIGN DOCUMENT

INTRODUCTION
This document describes the Sales Day software, which automates administrates tasks of data management for
smooth running of their day activities and provides accurate information as required .The purpose of this
document is to describe the design of the Sales Day software .There are four key sections within this document.
Section 1 discusses the data design decisions used in developing the system. Section 2 discusses the high-level
design of the system, identifying major system components and interfaces. Section 3 discusses the interface
design of the software. Section 4 completes the design, providing details related to the functioning of the
systems component parts.

PURPOSE:
A design document is a way for you to communicate to others what your design decisions are and why your
decisions are good decisions. A design will typically be considered good if it fulfills the requirements in a
meaningful way. If any aspect of the design cannot be justified, then it is probably worth reevaluating.

SCOPE
Since the existing system is completely manual so a computerized system is proposed. Computerization means
to change a manual system to a computer system. Sales day is the process of exploring, acquiring and reifying
user requirements through discussion with the problem owners, observation of the existing system, task analysis
and so on.The software Sales day of the store will remove the above mentioned errors and will provide help to
the whole staff in managing information of their products in a better way. Due to this software Sales day one
can ask queries and can enter data easily in the forms.

SYSTEM ARCHITECTURE
ARCHITECTURAL DESIGN

Develop a modular program structure and explain the relationships between the modules to achieve the
complete functionality of the system. This is the proposed system which is designed to solve the problems faced
by the organization. In this proposed system the data has been entered in the computerized form of every entry,
which will help to save the organization from facing different problems. A heightened focus on computerization
will affect workers in these sales and related occupations. For example, increased computerization of product-
line information and systems to record transactions will lead to greater computer use among sales personnel
Grocery clerks and store shelf stockers pack customers' purchases, price items, stock shelves with merchandise
and fill mail and telephone orders and the whole information should be stored in the database.

The proposed software sales day will meet the objectives, especially to enhance the efficiency of the system. For
this now the best system is to computerize the system.

• Wide range of Data: -

The proposed system will provide the capability of entering a wide range of data.

• Easy assessment of reports: -

The proposed system will provide the easy assessment of reports.

• Security provide: -

The proposed system will provide security.

• Help in Calculation: -

The proposed system will provide the help in calculation (calculating mark-up).

DATA DESIGN
DATA DESCRIPTION

Database systems have become an essential part of every day life in modern society. A database is a collection
of related data. It is the organized shape of data created is the format of rows and columns. Data can easily be
accessed, managed and updated in the databases.

DATA DICTIONARY:

Data dictionary is a set of meta-data which contains the definition and representation of data elements.It gives a
single point of reference of data repository of an organization.Data dictionary lists all data elements but does not
say anything about relationships between data elements.

ENTITY RELATIONSHIP DIAGRAM

Customer-
Employee
name
-name
Custome
others Employee
r-id others
-id

Customer
Pick Employee
thing

Check
and
calculate
the
amount

Exit
DFD DATA FLOW DIAGRAM

DIAGRAMLEVEL 0

order request

payment

0
Items
Shop goods Employee
Customers
detail

receipt
LEVEL 1

rd
swo Em ployee
& pas
C usto m er in i d
Log
Pu
rch
ase
di
t em

i ce
s

lot a

e
tion

A d d pr

pr ic
ifica

ss t
Ve r

t al
G ro

To
01 Log in 02 p urchase
Pay ment m ade by cas h or credit

C hec k upd ated inform atio n

ts duc
Edi t inform ation

e w pro
n
inf o rm a tio
b o ut n

D1 Lo g in d eta ils and

D2 P urch ased details
inform ation
at io n a
So ld ite m s
In fo rm
nt

t
cip
me

re
ay
fp
no
at io
r if ic
Ve

03 paym ent 04 M ainta in infor m a tionm 05 C hecking info rm ation

D3 Paym ent inform atio n D5 U pd ate in form ation

D4 M ain tenan ce details

PROCESS SPECIFICATION:

Process specification of customer order and employee:

• The employee will log in the database by providing valid ID and password.
• Employee will maintain the record of sold items.
• Only one customer at a time.
• The employee will sell the items which the customer wants to buy and will update the database
accordingly.
• Sold items will be updated in the item list.
• The system will display the result of the sold items.

Process specification of customer and item information:

• Customer’s ID, name, date and time of buying items will be saved in customer’s information.
• New customers can also in customer’s table.
• Sold items price and name should be added in the customer’s table.

STD STATE TRANSITIONDIAGRAM

Title :
S
tatec
h arto
fcus
tomero rder
andemplo y
e e
S
e llin
g
Login Emplo
yee ite m s S
oldIte
m s
e
m ploy
ee
Do : Addite
m nam e
Do : Logine
m ploy
ee andpric
einsoldlis
t
S
tart

Upd
Bu y
ing

ateite
items

m
Ite
m s
s
Cus
tome
r

Do :Re
cords
oldite
m s
Do :S
umtotalofs
old
items

Dis
playRe
sult

Do : dis
playresultof
soldite
m s
 Title : State Chart of
Customer and Item
information :

CUSTOMER
Do: Adddetailsof
Start customer
INFO SAVING

EMPLOYEE
Do: sell itemsandadd
information
ITEMINFO

CUSTOMERINFO Do: saveitemname

Do: saveid , nameand andprice
date /time Buy
item
Do: addnewcustomers

A
dd
Sold
item
info

in
fo
SOLDITEM
Do: check itemname
andprice
Do: addsolditemsinlist

ARCHITECTURAL STYLE

An architectural style is a set of principles. You can think of it as a coarse-grained pattern that provides an
abstract framework for a family of systems. An architectural style improves partitioning and promotes design
reuse by providing solutions to frequently recurring problems.
USECASE DIAGRAM

SHOP DATABASE

S.# 1 Login
S. # 2 Enter
«uses» product code
-End 2 *
«extends»
-End 4
* «extends»
S.# 1.1
Verification S.# 4 Enter
total price
S. # 3 Check
product details «uses»
«extends» «extends»

S.# 4.1 Add

S.# 3.1 Check S.# 3.2 Check product to sold items
brand name price
«uses»

S. # 4.2 Enter
«extends» Gross Total
-End 6 S. # 5 Check
Information
S.# 4.2.1 «extends»
*
Payment by cash
«extends» «extends»

-End 3 S.# 4.2.2

* 5
-End
-End 1 * S # 6 Enter S. # 7 Edit «uses» payment by credit card
product code product information
*
«extends»
«extends» «extends»

«extends»
S # 6.2 Check
Employee updates S.# 4.2.1.1
S # 7.1 Enter Verify cash payment
S # 6.1 Check product code
items
«extends»
«extends» «uses» «uses»
S # 7.2 open
product list
«extends»

«extends» «extends»
S # 6.1.1 check S # 6.2 .1 Check S # 7.1.1 show
total no price product list
«extends»

S # 7.2.1 Add
«extends» new product
«extends»
S # 6.2.2 Update
S # 6.1.2 check no price
of sold items S.# 4.2.2.1 Verify
credit card payment
S # 7.1.1.1 Add
product
S # 6.1.3 check no S # 7.1.1.2
of remaing items Delete product
LOGIN

Use Case ID: S#1

Req. Reference: It is the 1st Use Case named as Login
Purpose: To enter database
Actors: Employee
Description: This use case requires the employee information to enter the database.
Preconditions: The employee must have a valid login ID and password.
Post conditions: If the employee have a valid login ID and password only then he/she can enter the
database
Main Flow
1 The employee will open database 2 System will log the user inside the system
window
3 The employee will write the Login ID
and password and press enter

VERIFICATION

Use Case ID: S # 1.1

Req. Reference: Use case named as verification
Purpose: To verify the Login ID and password
Actors: Employee
Description: This use case is included by the Login use case which helps to verify the Login ID and
password
Preconditions: The employee must enter a Login ID and password
Post conditions: If the employee have a valid login ID and password only then he/she can enter the
database
Main Flow
1 After the employee has given the Login 2a The verification starts and if the Login ID and password
ID and password he/she should press are valid the employee will enter the database
enter

CHECK PRODUCT DETAILS

Use Case ID: S#3

Req. Reference: Use case named as Check product details
Purpose: To check product details of the specific product
Actors: Employee
Description: After the employee has given the valid product code he/she either will choose the
option Add product to sold list or Check product details. If he/she clicks on the button
saying Check product details he/she will be given the details of the specific product
whose code has be entered
Preconditions: Should enter correct product code and choose the right option saying Check product
details
Post conditions: The employee will be given options to go further
Main Flow
1 The employee will click on the button 2 The employee in return will be given further options
saying Check product details

CHECK PRICE

Use Case ID: S # 3.2

Req. Reference: This use comes under the product details
Purpose: The purpose of this use case is to check the updated price if the employee has any
doubts
Actors: Employee
Description: This use case is for updated information of the product price for the employee
Preconditions: The updated price of the product should be available
Post conditions: The product has been updated.
Main Flow
1 After the employee will press the button 2 The system in response will give the updated price of
Check product details he/she will be the specific product whose code was previously entered
given two options to choose and he/she
press the button Check updated price
ADD IN SOLD ITEMS

Use Case ID: S # 4.1

Req. Reference: Comes under the use case named as total price
Purpose: The purpose of this use case is to add the specific product in sold list along with its
price whose code has been entered previously
Actors: Employee
Description: After the employee has entered the product code he will be given with its price and then
it will add the specific product to the sold list along with its price if he/she wants to sell
that specific product
Preconditions: The employee should only press this button if he/she wants to sell the specific product
Post conditions: The product will be added in the sold list
Main Flow
1 The employee will press the button 2 The system in response will add the specific product to
saying Add in sold items the sold list along with its price which is extended in
the use case check items

CALCULATE RUNNING TOTAL

Use Case ID: S # 4.2

Req. Reference: This use case is included in the use case named Add product in sold list
Purpose: The purpose of this use case is to give the net total of the sold items
Actors: Employee
Description: The employee will enter the sold product to the sold list and if any more of the products
(more then one) are sold it will give the net total amount of the sold items of single
purchase by adding the prices of the sold items
Preconditions: Every item which is sold should be added in the sold list along with its price
Post conditions: Addition of all sold products by a specific customer
Main Flow
1 The employee will enter the button enter 2 The system in response will add the prices of the sold
gross total to check the net total amount items in a single purchase and show the net total
of the sold items in a single purchase amount

MAKE PAYMENT BY CASH

Use Case ID: S # 4.2.1

Req. Reference: This use case is extended in the use case named as enter gross total
Purpose: The purpose of this use case is to collect money from the customer as a cash
Actors: Employee
Description: The customer will tell the employee the gross total amount which he/she has to pay is a
cash
Preconditions: The employee should be informed by the customer that he/she will pay cash
Post conditions: The system will receive the payment as a cash
Main Flow
1 The employee will enter the button 2 the system in response will give control to the next use
payment by cash case that is verify cash payment

MAKE PAYMENT BY CREDIT CARD

Use Case ID: S # 4.2.2

Req. Reference: This use case is extended in the use case named as enter gross total
Purpose: The purpose of this use case is to collect money from the customer as with the help of a
credit card
Actors: Employee
Description: The customer will tell the employee the gross total amount which he/she has to pay is
through credit card
Preconditions: The employee should be informed by the customer that he/she will pay through credit
card
Post conditions: The system will receive the payment via credit card
Main Flow
1 The employee will enter the button 2 the system in response will give control to the next use
payment by credit card case that is verify credit card payment

VERIFY CASH PAYMENT

Use Case ID: S # 4.2.1.1

Req. Reference: This use case is included in the use case named as Payment by cash
Purpose: The purpose of this use case is to verify the cash payment given to the employee by the
customer and to hand over the receipt and the remaining money
Actors: Employee
Description: The employee when takes the cash from the customer and enters that amount and will
verify the cash payment if the amount given by cash is more then the gross total the
system will minus the cash amount from the gross total and will tell the remaining
money which has to be given back to the customer and will also issue a receipt
Preconditions: The cash amount of the customer should be entered correctly
Post conditions: The system will verify the amount paid
Main Flow
1 The employee will enter the cash amount 2 The system in response will verify the cash amount and
given by the customer will either minus the total amount of money the
customer has paid by the gross total if the customer has
paid more money or otherwise it will simply give a
receipt

VERIFY CREDIT CARD PAYMENT

Use Case ID: S # 4.2.2.1

Req. Reference: This use case is included in the use case named as Payment by credit card
Purpose: The purpose of this use case is to verify the credit card payment given to the employee
by the customer and to hand over the receipt
Actors: Employee
Description: The employee when takes the credit from the customer and swaps it through the
machine the amount which the customer has to pay will be deducted and a receipt will
be issued
Preconditions: The customer should inform that he/she will pay through credit card
Post conditions: The system will verify the amount paid
Main Flow
1 The employee will swap the credit card 2 The system in response will verify the credit card
given by the customer amount and will deduct the total amount of money the
customer has pay and will give a receipt

ENTER PRODUCT CODE

Use Case ID: S#6

Req. Reference: This use case is comes under the use case named as Check product information
Purpose: The purpose of this use case is to take the required product code and get the related
information and updates regarding it
Actors: Employee
Description: In this use case the system takes the code of the specific product and gives related
information about that product.
Preconditions: The employee must type know and type a valid code
Post conditions: The employee will be given further options
Main Flow
1 The employee will click on the button 2 A window will appear to enter the product code
 saying enter product code
3 The employee will write the product 4a If the product code is valid the window will give further
code and press enter options
4b If the product code is invalid the window will not give
further options and again the same window will appear
to enter the product name

CHECK ITEMS

Use Case ID: S # 6.1

Req. Reference: This use case comes under the use case named as Enter product code
Purpose: The purpose of this use case is to check the items
Actors: Employee
Description: This use case helps to check the items that how many items have been sold, how many
are remaining and the total number of items
Preconditions: The information about the items is already given by other use cases
Post conditions: The employee can access the extended use cases
Main Flow
1 The employee will click on the button 2 The system in response will let the employee access the
saying Check items information related to items

CHECK NO. OF SOLD ITEMS

Use Case ID: S # 6.1.2

Req. Reference: This use case is extended in the use case named as check items
Purpose: The main purpose of this use case is if the employee wishes to see the selling of his day
then he/she can press this button and access the information
Actors: Employee
Description: The employee if wishes to see the list of sold items with its prices can access it through
this use case
Preconditions: Every item which is being sold has to be added in this list along with its price, name
and code
Post conditions: The system will provide employee with no. of sold items
Main Flow
1 The employee will press the button 2 The system in response will open a list of sold items
saying Check no. of sold items along with its name, code and price

CHECK NO. OF REMAINING ITEMS

Use Case ID: S # 6.1.3
Req. Reference: This use case is extended in the use case named as check items
Purpose: The purpose of this use case is to give information to the employee regarding the items
that how many items are left for selling
Actors: Employee
Description: If the employee wishes to check the no. of remaining items to be sold he/she can access
this information through this use case
Preconditions: The total no. of items has been subtracted from the no. of sold items
Post conditions: The employee can access the information of no. of sold items
Main Flow
1 The employee will enter the button 2 The system in response will subtract the sold items
saying Check no. of remaining items from the total no. of items and show a list of remaining
no. of items along with a names, prices and codes

CHECK PRICE

Use Case ID: S # 6.2.1

Req. Reference: This use case is extended in check updates
Purpose: The purpose is to check price of an item
Actors: Employee
Description: When the employee want to know the price of the items whose name he/she has
previously entered. The employee will press this button and the system will show the
list products with price of that specific item
Preconditions: The name previously entered should be the desired name to check the price
Post conditions: Updated price is available to the employee
Main Flow
1 The employee will press the button 2 The system in response will show the list of products
saying Check price with the same name which was previously entered
along with its prices

SHOW PRODUCT LIST

Use Case ID: S # 7.1.1

Req. This use case is included in the use case named as enter product code
Reference:
Purpose: The purpose of this use case is to show the list of the product whose name has been
previously enter along with the code of those products
Actors: Employee
Description: The employee if wishes to see the same product along with its code numbers then he/she
has to press this button, the list of that product with its codes will appear
Precondition The code entered before should be valid
s:
Post The system will open the product list to add or delete product from it
conditions:
Main Flow
1 The employee will enter this button 2 The system in response will open a list of products
whose name was previously entered along with its code
numbers

ADD PRODUCT

Use Case ID: S # 7.1.1.1

Req. This use case is extended in the use case named as Show product list
Reference:
Purpose: The purpose of this use case is to add the same product in the specified product list
containing same products with different codes
Actors: Employee
Description: The employee will add product in the product list shown before in the spaces provided by
the system. To add product the employee will assign a code, price and brand name in the
list given
Precondition To add product, the list of product should be opened
s:
Post The addition of the product will be made in the existing list where the no. of this product
conditions: will be added in the total no. of items

Main Flow
1 The employee will press the button 2 The system in response will provide space for adding
saying Add product the product in the list and will demand for price, brand
name and code
3 The employee will add the price, brand 4 The system in response will occupy the spaces required
name and code for the product details

DELETE PRODUCT

Use Case ID: S # 7.1.1.2

Req. This use case is extended in the use case named as Show product list
Reference:
Purpose: The purpose of this use case is to delete the same product in the specified product list
containing same products with different codes
Actors: Employee
Description: The employee will delete product from the product list shown before in the spaces provided
by the system. To delete product the employee will delete code, price and brand name from
the list given
Precondition To delete product from the list the specific list of that product should be opened
s:
Post The desired product is deleted
conditions:
Main Flow
1 The employee will press the button 2 The system in response will delete the product for the
saying Delete product list and will demand for deleting price, brand name and
code
3 The employee will delete the price, brand 4 The system in response will leave the spaces occupied
name and code by the product details as it is
Special The product should be deleted for the list containing the same products
Requirements:
Assumptions: Check the availability of the product

OPEN PRODUCT LIST

Use Case ID: S # 7.2

Req. This use case is extended in the use case named as Edit product information
Reference:
Purpose: The purpose of this use case is to show existing product list to add new product
Actors: Employee
Description: The employee if wishes to add new products then this use case will open a product list to
add new product along with its name, Total no. of items, code, brand name, price and
product name
Precondition The code entered before should be valid
s:
Post The system will open the product list to add new product
conditions:
Main Flow
 1 The employee will enter this button 2 The system in response will open the product list to add
new product containing name, price, Total no. of items,
brand name and code

ADD NEW PRODUCT

Use Case ID: S # 7.2.1

Req. This use case is extended in the use case named as Open product list
Reference:
Purpose: The purpose of this use case is to add new product in the product list along with its name,
code, brand name, total no. of items and price
Actors: Employee
Description: The employee will add new product in the product list shown before in the spaces
provided by the system. To add new product the employee will assign a code, price, total
no. of items and brand name in the list given
Preconditions: To add new product in the list the existing list should be opened
Post The new product will be added in the existing list
conditions:

INTERFACE DESIGN
OVERVIEW OF USER INTERFACE

The proposed software will meet the objectives, especially to enhance the efficiency of the system. For this now
the best system is to computerize the software. The proposed system will provide the capability of entering a
wide range of data. The proposed system will provide the easy assessment of reports. The proposed system will
provide security. The proposed system will provide the help in calculation (calculating mark-up).

SCREEN IMAGES

a) MAIN FORM b) MAIN MENU FORM

c) CUSTOMER FORM h) QUERY MENU FORM

APPENDIX
USER MANUAL

TABLES
a) CUSTOMER TABLE b) ORDER_DETAIL TABLE

c) ITEM TABLE d) BILL TABLE

FORMS
a) MAIN FORM

b) MAIN MENU FORM

c) CUSTOMER FORM

d) CUSTOMER ORDER FORM

e) ITEM FORM
g) ORDER DETAILS FORM

h) QUERY MENU FORM

REPORT MENU FORM