Re: [Fisterra-devel] Analysis: shop register

[Alejandro C. <ac...@ig...>]

On Thu, Apr 21, 2005 at 10:58:59AM +0200, Eloy Froufe Pérez wrote:
>
> [...]
> 
> Window 1 ???Selection of the articles to refund
> ---------------------------------------------
> 
> The Information staff passes the purchase ticket by the reader or
> introduces the number of the ticket, the application shows this window
> with the ticket data. This window contains 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 article
>      3. Description of the article
>      4. Quantity
>      5. Price
>      6. PVP
>      7. Refund, is a boolean field indicates that the client refunds
>         this article
>      8. Refunded quantity, it can not greater than the bougth quantity
> 
> The staff of information selects the articles of the ticket and the
> quantities that the client want to refund, then he accept the operation
> and the application prints the refund ticket, the client takes it and go
> to the shop register. 
> 

I have some questions about this use case and its windows: can I refund a
ticket more than once? I asume the selection of the article will be done
adding the number of units on a column, won't it?

>
> [...]
> 
> Window 1 of UC 5 ??? Listing of shop registers closings
> -----------------------------------------------------
> 
> The shop chief can view all shop registers closings of the present day.
> This windows has two parts, the filters and the table of results. The
> filters are:
> 

I would remove the restriction about the present day, I think we can keep
opened shop registers without problem. It is a responsability of the cashier
to hand the drawer to the chief or keep it. This would simplify the
application and I think allow more options to the users. Of course the
system must warn the user when he is going to close a shop leaving an opened
drawer. I think we should also add a way to view all shop and register
closings, sometimes we will want to browse the old movements of the money.

> 
> [...]
> 
> When the shop chief finish the cheking of the shop, the application
> shows the generated quantity the present day. The shop chief will
> indicate the quantity that he want send to the bank and the application
> calculate the quantity that remains in the shop.
> 

I think we have to define the amount of money that we will leave in the
drawers, but just as a quick window process, therefore we could change it on
the the window 2 of this use case. This way the drawers could have different
amounts and the users could have a main shop register in order to have money
to do planned payments tomorrow. This way the amount that would be
withdrawed of the shop will be: total amount at the shop today - amount on
the drawers.

>
> [...]
> 
> The shop chief use this window to associate a unsquate to a ticket,
> because the cashier could introduce the quantity badly in the dataphone.
> The shop chief introduces a unsquare quantity and select the ticket that
> causes the unsquare, the application saves the unsquare associated to
> the ticket.
> 

I think there should be windows to list the tickets incidents, and to point
out that the problem is solved with the bank, not just in this situation but
on any problem with a ticket. Maybe one use case with a list and a detail
that allow the user to handle the state of the document.

Greetings.

-- 

Alejandro Garcia Castro
mailto: ac...@ig...
http://www.igalia.com