Re: [Fisterra-devel] Revision: requirements of shop register

[Sergio V. S. <sv...@ig...>]

On Xov, 2005-04-28 at 18:36 +0200, Eloy Froufe P=C3=A9rez wrote:
> Window 1 of UC 7 =E2=86=92 Listing of incidents
> ---------------------------------------
>=20
> The shop chief uses this window to select the incident that he want to
> manage. This windows has two parts, the filters and the table of
> results. The filters are:
>=20
>      1. Incident date
>      2. Incident type
>      3. Incident state
>      4. Cashier name
>      5. Shop register number.
>=20
> The data of the results table are:
>=20
>      1. Incident date and time
>      2. Incident type
>      3. Incident state
>      4. Cashier name
>      5. Shop register number.
>      6. Shop register name.
>=20
> The shop chief can select a incident and manage its in the window 2.
>=20
>=20
> Window 2 of UC 7 =E2=86=92 Detail of incident
> -------------------------------------
>=20
> This window allows the shop chief to manage a incident, selected in
> the
> window 1, the data of this window are:
>=20
>      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.

Should we consider the incidents as another kind of Document?

What about other types of incidents?

What is "in current state" state?

What is "deleted" state?

Is there any schema of incident state transitions? I mean, how does an
incident change its state?

What document are the incidents associated to?

Bye.