source: main/eko-disco-specs/trunk/use-cases/customer-remove.rst @ 10749

Last change on this file since 10749 was 10749, checked in by uli, 11 years ago

Some use-cases, etc.

File size: 2.3 KB
RevLine 
[10749]1.. _label-uc-customer-remove:
2
3Use-Case: Remove Customer
4***********************************************************************
5
6.. Description of a use case
7.. The description must be formulated as seen from system (not: actors)
8.. Describes those changes an (outside) actor can notice
9.. Short and abstract as possible, as long as necessary.
10.. Each use case must have at least one actor involved
11.. Each use case must have a trigger and a result
12
13
14Short Description
15-----------------------------------------------------------------------
16
17A customer with all connected data is removed from the system.
18
19Actor(s)
20-----------------------------------------------------------------------
21
22Staff member
23
24
25Trigger(s)
26-----------------------------------------------------------------------
27
28- Imports (deleting existing data)
29- Web form(s) submitted by authorized user.
30
31
32Result(s)
33-----------------------------------------------------------------------
34
35- A customer and all connected data was removed and archived.
36
37
38Incoming Data
39-----------------------------------------------------------------------
40
41- Customer id, authorization data of submitting user
42
43Outgoing Data
44-----------------------------------------------------------------------
45
46- Message about successful/failed changes.
47- Archive entry of data removed from system with extra info
48  (when/who).
49- Log message
50
51
52Precondition(s)
53-----------------------------------------------------------------------
54
55- Submitting user is authorized to do the requested modifications.
56
57
58Postcondition(s)
59-----------------------------------------------------------------------
60
61Any entered data is valid.
62
63
64Invariant(s)
65-----------------------------------------------------------------------
66
67
68Essential Steps
69-----------------------------------------------------------------------
70
71- Sending user authorization is checked.
72- System receives infos about
73  - what data fields of which user should be set to which values.
74  - submitting user
75- Data is modified in system
76- User gets informed about operation success/fail.
77- if operation fails, possibility to change input data is offered
78
79
80Open Issues
81-----------------------------------------------------------------------
82
83
84
85Remarks
86-----------------------------------------------------------------------
87
88
89.. raw:: latex
90
91      \pagebreak[4]
Note: See TracBrowser for help on using the repository browser.