source: main/eko-disco-specs/trunk/use-cases/customer-edit-basedata.rst @ 10750

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

Some use-cases, etc.

File size: 2.2 KB
RevLine 
[10749]1.. _label-uc-customer-edit-basedata:
2
3Use-Case: Edit Basic Customer Data
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
17Basic customer data like contact data or login credentials are
18modified.
19
20Actor(s)
21-----------------------------------------------------------------------
22
23Customer
24
25
26Trigger(s)
27-----------------------------------------------------------------------
28
29- Imports (modifying existing data)
30- Web form(s) submitted by authorized user.
31
32
33Result(s)
34-----------------------------------------------------------------------
35
36- Customer base data are modified.
37
38
39Incoming Data
40-----------------------------------------------------------------------
41
42- Contact data | password | user name | user id
43
44Outgoing Data
45-----------------------------------------------------------------------
46
47- Message about successful/failed changes.
48- Log message
49
50
51Precondition(s)
52-----------------------------------------------------------------------
53
54- Submitting user is authorized to do the requested modifications.
55
56
57Postcondition(s)
58-----------------------------------------------------------------------
59
60Any entered data is valid.
61
62
63Invariant(s)
64-----------------------------------------------------------------------
65
66
67Essential Steps
68-----------------------------------------------------------------------
69
70- Sending user authorization is checked.
71- System receives infos about
72  - what data fields of which user should be set to which values.
73  - submitting user
74- Data is modified in system
75- User gets informed about operation success/fail.
76- if operation fails, possibility to change input data is offered
77
78
79Open Issues
80-----------------------------------------------------------------------
81
82
83
84Remarks
85-----------------------------------------------------------------------
86
87
88.. raw:: latex
89
90      \pagebreak[4]
Note: See TracBrowser for help on using the repository browser.