Menu
▾
▴
[Fisterra-devel] Revision: requirements of shop register
|
From: Eloy F. <ef...@ig...> - 2005-04-28 16:36:05
|
Hi,=20
Next, i send a new revision of the shop register requirements that th=
e
Fisterra Team will implement.=20
If you think that we should add, delete or change anything in the sho=
p
register tell us it .
*********************************************************************=
**
Requirements of shop register
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
This section specifies the requirements of the shop register that wil=
l
be implemented on the Fisterra project.=20
Basically, the operation of the shop register is:=20
* A client arrives to the shop, takes a set of items and goes t=
o
the shop register.
* The cashier, that has been identified by the system previousl=
y,
passes each item through a bar code reader.
* The application calculates the total price.
* The cashier select the payment method.
* Finally the cashier returns the remaining money to the client=
.
The client can refund the items in the next X days. The client must g=
o
to Information counter, where he receives a refund ticket, then he mu=
st
go to the shop register where the cashier returns him the money. The
method of refund is the same that the client used when he bougth the
items, so that if the client paid with credit card the refund is with
credit card.=20
The shop register contains 7 use cases:=20
* UC 1: Shop register =E2=86=92 Cashie
* UC 2: Refund of items =E2=86=92 Staff of information
* UC 3: Cash management =E2=86=92 cashier
* UC 4: Checking of shop register =E2=86=92 Cashier
* UC 5: Checking of shop =E2=86=92 Shop chief
* UC 6: Items management =E2=86=92 Shop chief
* UC 7: Incidents management =E2=86=92 Shop chief
* UC 8: Consult cash of the shop registers =E2=86=92 Shop chief
=20
=20
Use case 1: Shop register =E2=86=92 Cashier
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This use case allows the cashier to charge the items that a client wa=
nt
to purchase. The cashier passes the items through the reader of the b=
ar
code and it will be included in the ticket. If the client takes sever=
al
units of the same item the cashier can pass only one through the read=
er
of bar code and to multiply by the number of units.
This use case must allow to mantain tickets on waiting state, so that
the cashier can create other ticket and then to recover the previous
ticket.
The possible payment methods are:
1. Cash.
2. Credit card.
3. Gift cheque: it can not return money.
4. Combination of the previous payment methods.
A client can pay with several methods, so that the cashier have to
select the payment method, using a function key.=20
If the payment method is cash, the cashier has to indicate the quanti=
ty
handed by the client and the application calculates the quantity to
return.
When a client want to refund one or various items has to go to
Information office, there he receive a refund ticket and then he has =
to
go to the shop register, where the cashier gives him the money.=20
The refund ticket of the client has a bar code, the cashier passes th=
e
tickect through the reader of bar code, then the application shows th=
is
ticket with the items refunded by the client, the quantity of each on=
e
and the refund method. The cashier accepts the operation and two
tickects will be printed, one for the client and another is stored
associated with the refund ticket.
The operation of the shop register is:
The bar code of the item is readed in other window. The cashier can
multiply by the number of units, introduces for example 4 * and then
passes the item through the reader of bar code, so that the 4 items
appear in a new line of the ticket.
The cashier will pass each item through the bar code reader and it wi=
ll
be added to the ticket in a new line. The application will add the pr=
ice
of all items and will show the total price. By default, the applicati=
on
shows the given quantity with the calculated total price, if the clie=
nt
gives other quantity the cashier has to change it.
Window 1 of UC 1 =E2=86=92 Shop register
--------------------------------
This is the window of the shop register, it is divided in 3 parts.
The first part shows the information:
1. Document: type of document that the cashier is managing, if t=
he
cashier is charging it is 'ticket'. But the cashier can pass =
a
refund ticket through the reader of bar code, in this case it=
is
'refund ticket'. The application has to recuperate this docum=
ent
and to show it in the window. The documents that the cashier =
can
read are:=20
* Ticket.
* Refund ticket.
2. Date: generation date of the document
3. Cashier: name of the cashier.
4. Shop register: number of shop register.
The second part of the window has the ticket lines, the data of each
are:
1. Line number
2. Internal code of the item
3. Description of the item
4. Number of units
5. Price by unit
6. Total price of the line =3D Number of units * price.
The third part contains the fields:
1. Bar code: when the cashier passes the item through the reader=
of
bar code its code appears in this field. If the client takes
more than 1 unit of the same item, the cashier can introduce =
the
number of units, then the multiply symbol (*) and then the it=
em
code. If the cashier doesn't specify the number of units befo=
re
to pass the item through the bar code reader it is assumed th=
at
the number of units is 1.
2. Number of items that the cashier passed through the reader of
bar code.
This window must allow to leave a ticket on waiting state, and then t=
o
recuperate, using a function key. When the cashier use this function =
key
the application changes from a ticket to other.
The cashier can delete a line of the ticket, first selects the line a=
nd
then uses a function key to delete it.
When the cashier recuperates a document by its code can add, delete o
update it depending on the document type:
1. Tickets: can update it if it was not saved.
2. Refunds: can not update it
=20
=20
Window 2 of UC 1 =E2=86=92 Client payment
---------------------------------
This window is used by the cashit to charge the client ticket. The da=
ta
are:
1. Total price of the ticket: the cashier uses a function key to
finish the insertion of items.
2. Money given by the client: by default, it is shown with the
total price, if the client gives other quantity the cashier m=
ust
change it.
3. Payment methods: the client can use several payment methods
simultaneously, by default is "cash". This window must contai=
n a
row for each payment method, where the cashier must introduce
the quantity of each payment method that the client wants. By
default, the cash quantity must be the total price of the
ticket, but the cashier can change it. The cashier selects th=
e
payment methods using a function key for each one. If the
payment method selected is "Credit card" the cashier must pas=
s
the credit card through the card reader to obtain its data. T=
he
application has to check that the sum of all payment methods
quantities is equal or greater than the total price of the
ticket.
4. Money to return: it is calculated by the application (money
given by the client - total price).
=20
If it is a refund the return quantity should be the total price of th=
e
refund ticket.
Use case 2: Refund of items =E2=86=92 Staff of information
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
The client can refund the items in the next X days. The client must g=
o
to Information counter where gives the purchases ticket, the staff
passes the bar code of the ticket through the reader.=20
The application recovers the ticket information and shows it in the
monitor and the staff selects the refunded items.=20
The application prints a refund ticket. The client takes the refund
ticket and goes to the shop register where the cashier returns him th=
e
money. The method of refund is the same that the client used when he
bougth the items, so that, if the client paid with credit card the
refund is with credit card. The refund ticket must have the refund
method, it is obtained from purchase ticket=20
Window 1 of UC 2 =E2=86=92Selection of the items to refund
---------------------------------------------------
The Information staff passes the purchase ticket through the reader, =
the
application shows this window with the ticket data. This window conta=
ins
2 parts: ticket header and the tickets lines
The ticket header contains:
1. Number of ticket.
2. Date of the ticket.
3. Name of the cashier.
4. Number of shop register.
5. Payment method of the ticket.
The ticket lines contains:
1. Line number
2. Bar code of the item
3. Description of the item
4. Quantity
5. Price
6. PVP
7. Refunded quantity, it can not greater than the bougth quantit=
y
The staff of information selects the items of the ticket and the
quantities that the client want to refund, then he accepts the operat=
ion
and the application prints the refund ticket, the client takes it and=
go
to the shop register.=20
Use case 3: Cash managment =E2=86=92 cashier
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This use case allows the cashier to retire or add cash to the shop
register.
Window 1 of UC 3 =E2=86=92 Cash management=20
----------------------------------
The cashier uses this window when the shop chief indicates that the
cashier must retire or add cash to the shop register.
The cashier performs this operation using a function key from the sho=
p
register window.
The shop chief has to enter his password before this window appear. I=
f
the shop chief does not enter his password the chashier can not perfo=
rm
this operation.
The window has a 2 field only, where the cashier introduces the
operation type (add or retire) and the cash quantity.
The cashier accept the operation and the applicaton print two documen=
ts,
the data are:
1. Name of the shop
2. Date and time of the withdrawal
3. Number and description of the shop register
4. Name of the cashier
5. Operation type (adition or withdrawal)
6. Cash quantity
7. Signature of the cashier, it contains the signature label and
the name of the cashier
8. Signature of the shop chief
If the shop has a shop register central, it can be implemented as a
special shop register, in this case the cash management will be:
1. Add of cash: The shop chief performs a operation of cash
withdrawall of central shop register and a operation of cash
addition in a certain shop register.
2. Retire of cash: The shop chief performs a operation of cash
withdrawall of a certain shop register and a operation of cas=
h
addition in a central shop register.
Other possibility is that the shop chief has a virtual shop register
associated, when he performs a cash withdrawal the cash quantity is
added to his virtual shop register and if the shop chief performs a c=
ash
addition the cash quantity is substracted of his virtual shop registe=
r.
It allows has a greater control of cash flow.
Use case 4: Checking of shop register =E2=86=92 Cashier
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
The cashier when finish his turn has to do the shop register closing,=
it
is:=20
The cashier counts the money of the shop register, introduces in the
application this quantity, the credit card balance, the sum of gift
cheques, and finally can enter a observation.=20
Window 1 of UC 4 =E2=86=92 Checking of shop register
--------------------------------------------
This window is used by the cashier when he wants to close his shop
register, the application must check that there is not delayed ticked
when tries to close the shop register. The data are:
1. Date and time
2. Cashier
3. Shop register
4. Cash balance: the cashier introduces the cash of the shop
register
5. Credit card balance: sum of all credit card payments - sum of
all credit card refunds. The cashier introduces this quantity=
.
6. Gift cheques quantity: The cahier has to sum all gift cheques
and to introduce this quantity.
7. Observation: the cashier can introduce a observation in this
field.
When the cashier has introduced this data and accepted, the applicati=
on
must print the close document, its data are:
1. Date and time
2. Cashier
3. Shop register
4. Cash balance
5. Credit card balance
6. Gift cheque quantity
7. Place of signature of shop chief
8. Place of signature of the cashier, it must include the cashie=
r
name.
Then the cashier has to give this document to the shop chief, so that
checks this data and performs the shop closing.
Use case 5: Checking of shop =E2=86=92 Shop chief
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This use case allows the shop chief to check each shop registers, aft=
er
the cashiers closes the shop registers.
The shop chief must have a summary for each shop register, with the
cash, the balance of credit card and the gift cheques. The applicatio=
n
must show the data introduced by the cashier and the data calculated =
by
the application. The shop chief has to check that these data are equa=
l,
and the money given by the cashier is equal to the introduced quantit=
y
by the cashier in the application. If everything is correct the shop
chief accepts and the shop register is closed definitively. If exists=
a
unsquare can be that the cashier counted badly the money of the shop
register, in this case the shop chief must introduce the quantity aga=
in,
the application must save the old data and the new data. Then if stil=
l
the unsquare exists, the shop chief can introduce a observation.
Window 1 of UC 5 =E2=86=92 Listing of shop registers closings
-----------------------------------------------------
The shop chief can view all shop registers closings of a certain day.
This windows has two parts, the filters and the table of results. The
filters are:
1. Closing day
2. Number of shop register
3. Description of the shop register
4. Name of the cashier
The data of the results table are:
1. Number of shop register
2. Description of shop register
3. Name of the cashier
4. Invoiced quantity by the cashier.
5. Closing time
6. Total unsquare of the closing.
The shop chief has to check each closing of shop register, the checke=
d
closing has to be marked of different color.
A cachier can do several closings the same day.
The shop chief uses this window to view all closings of shop register=
s,
then he must check each one using the window 2.
This window must also show the not closed shop registers.
Window 2 of UC 5 =E2=86=92 Datail of the shop register closing
------------------------------------------------------
This window shows the data of a shop register closing, the data are:
1. Cashier name
2. Number and description of shop register
3. Date and time of closing
4. Table with 3 columns, the intrduced quantity by the cashier, =
the
calculated quantity by the application and the differences. T=
his
table must to have 3 rows:
* First row: is the cash quantity of the shop register.
The first cell is the introduced quantity by the
cashier, the second cell is the calculated quantity b=
y
the application, the third cell is the unsquare
quantity.
* Second row: is the quantity of credit card operations=
.
The first cell is the introduced quantity by the
cashier, the second cell is the calculated quantity b=
y
the application, the third cell is the unsquare
quantity. This window has a button that opens other
window that allows to view the detail of all credit c=
ard
tickets (payments and refunds) of that closing, it is
the window 3.=20
* Third row: is the gift cheques. The first cell is the
introduced quantity by the cashier, the second cell i=
s
the calculated quantity by the application, the third
cell is the unsquare quantity.
The shop chief can change the introduced quantity by the cashier, the
application must save this change and its author.
The shop chief can introduce in this window an observation relationat=
ed
with a unsquare.
When the shop chief acceps:
* If the cash unsquare is not 0, the application must create a
incident of 'cash unsquare' type, associated to the shop
register closing.
* If the credit card unsquare is not 0, the application must
create a incident of 'credit card unsquare' type, associated =
to
the shop register closing.
* If the gift cheques is not 0, the application must create a
incident of 'gift cheque unsquare' type, associated to the sh=
op
register closing.
=20
=20
Window 3 of UC 5 =E2=86=92 Listing of credit card tickets
-------------------------------------------------
This window allows to view a listing of all credit card tickets of th=
e
cashier closing selected in the window 1. This window appears when th=
e
shop chief clicks on the button of view the credit card tickets of th=
e
window 2.=20
The shop chief use this window to associate a unsquate to a ticket,
because the cashier could introduce the quantity badly in the datapho=
ne.
The shop chief introduces a unsquare quantity and select the ticket t=
hat
causes the unsquare, the application saves the unsquare associated to
the ticket.
This window contains two parts, the first is the header, the data are=
:
1. Cashier name
2. Shop register
3. Date
The second part contains a table with the data:
1. Number of ticket
2. Time of the ticket
3. Total price of the ticket
4. Unsquare.
When the shop chief founds the unsquare he annotates the unsquare
quantity, accepts and retuns to the previous window. The application
must create a incident of 'credit card ticket unsquare' type, associa=
ted
to the unsquared ticket, and with the unsquare quantity.
Use case 6: Items management =E2=86=92 Shop chief
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This use case allows the shop chief to insert, update, delete,
reactivate or consult the items that are solded in the shop and set
their present sell prices.
The data of each item are:
1. Internal code
2. Description
3. Trade mark
4. List of bar codes, each item can have several bar codes and o=
ne
by default
5. Weight in grams
6. Height, width, depth in centimeters
7. Subfamily: Each item belongs a subfamily, each subfamily belo=
ngs
a family and each family belongs a section
8. Type tax: each item has a type tax, it can be a percentage or=
a
fixed quantity
9. Present sell price. If a item has not a sell price it can not=
be
sold in the shop.
This use case allows the shop chief:
1. Insert, update, delete, reactivate, and set the present sell
price of the items using a script that reads the information
from a XML file.
2. Consult the items of the shop and their present prices, it is
the window 1.
The script has to read the XML file and performs the indicated
operations in each item contained in this file. For example, the form=
at
of this file can be:=20
<item action =3D "add">
<internal_code>12</internal_code>
<description>Water bottle 1.5 L</description>
<trade_mark>WATER MARK 1.5 L</trade_mark>
<barcode_list>
<barcode is_default =3D "YES">21342423</barcode>
<barcode>43523143</barcode>
</barcode_list>
<subfamily>Waters</subfamily>
<weight>1500</weigth>
<heigth>30</heigth>
<width>10</width>
<depth>10</depth>
<type_tax>IVA 16 %</type_tax>
<sell_price>0.30</sell_price>
</item>
<item action =3D "update">
<internal_code>12</internal_code>
<sell_price>0.35</description>
</item>
<item action =3D "delete">
<internal_code>12</internal_code>
</item>
<item action =3D "reactivate">
<internal_code>12</internal_code>
</item>
=20
=20
The add operations of the XML file has to include all item attributes=
.
The update operations of the XML file has to include the internal cod=
e
of the item and the attributes that shop chief want to change. The sh=
op
chief will use this operation type to set the present item price, it
will be the new price until the shop chief changes it again.
The delete operations of the XML file can not delete the items of the
BD, only mark is as inactive, this operations contains only the inter=
nal
code of the item that the shop chief want to delete.
The reactivate operations of the XML file allow to activate a item th=
at
was previously deleted, this operation contains only the internal cod=
e
of the item that the shop chief want to reactivate.
Window 1 of UC 6 =E2=86=92 Listing of items
-----------------------------------
This window allows the shop chief to consult the items of the shop an=
d
their prices. This windows has two parts, the filters and the table o=
f
results. The filters are:
1. Internal code of the item
2. Description of the item
3. Trade mark
4. Bar code
5. Item deleted: boolean that indicated if the item was deleted.
6. Section, family and subfamily, it must a tree that allows to
add, delete or move sections, families and subfamilies
The data of the result table are:
1. Internal code of the item.
2. Description of the item.
3. Default bar code.
4. Weight, height, width, depth.
5. Default bar code.
6. Is deleted: it indicates if the item was deleted.
7. Present sell price.
8. Type tax of the item
=20
=20
Use case 7: Incidents management =E2=86=92 Shop chief
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
This use case allows the shop chief to manage the incidents. There ar=
e 4
types of incidents:=20
* Cash unsquare: this incidents are created when the shop chief
performs a "Checking of shop" and exists an cash unsquare. Th=
is
incident is associated to the shop register closing.
=20
* Gift cheque unsquare: this incidents are created when the sho=
p
chief performs a "Checking of shop" and exists an gift cheque
unsquare. This incident is associated to the shop register
closing.
=20
* Credit card unsquare: this incidents are created when the sho=
p
chief performs a "Checking of shop" and exists an credit card
unsquare. This incident is associated to the shop register
closing.
=20
* Credit card ticket unsquare: this incidents are created when =
the
chief performs a "Checking of shop", exists an credit card
unsquare, and the shop chief select a credit card ticket that
has a unsquare, this incident is associated to the credit car=
d
ticket.
=20
=20
Window 1 of UC 7 =E2=86=92 Listing of incidents
---------------------------------------
The shop chief uses this window to select the incident that he want t=
o
manage. This windows has two parts, the filters and the table of
results. The filters are:
1. Incident date
2. Incident type
3. Incident state
4. Cashier name
5. Shop register number.
The data of the results table are:
1. Incident date and time
2. Incident type
3. Incident state
4. Cashier name
5. Shop register number.
6. Shop register name.
The shop chief can select a incident and manage its in the window 2.
Window 2 of UC 7 =E2=86=92 Detail of incident
-------------------------------------
This window allows the shop chief to manage a incident, selected in t=
he
window 1, the data of this window are:
1. Time and date of the incident
2. Type of the incident
3. Number and name of the shop register and the name of the
cashier. It is the shop register and the cashier that caused =
the
unsquare.
4. Unsquared quantity
5. Observation: the shop chief can introduce a observation
associated to the incident.
6. Incident state: The shop chief can change the state of a
incident, the possible states are: active, in current state,
finalized and deleted.
=20
=20
Use case 8: Consult cash of the shop registers =E2=86=92 Shop chief
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This use case allows the shop chief to consult the present cash of th=
e
openeded shop registers. The shop chief uses this information to deci=
de
if a cashier must add or retire cash of his shop register.
Window 1 of UC 8 =E2=86=92 Listing of shop registers=20
--------------------------------------------
The shop chief uses this use case to view the present cash quantity o=
f
each shop register. This window contains a listing with all opened sh=
op
registers, the data of each shop register are:
* Number of shop register
* Description of shop register
* Name of the cashier
* Present cash quantity in the shop register
This window must have a button that allows refresh the cash quantity =
of
each shop register
*********************************************************************=
***
greetings.
--=20
Eloy Froufe P=C3=A9rez
Computer Science Engineer
Telf: +34 981 91 39 91
Fax: +34 981 91 39 49
mailto: ef...@ig...
IGALIA, S.L. http://www.igalia.com
|