source: main/eko-disco-specs/trunk/use-cases/contract-manage.rst @ 11107

Last change on this file since 11107 was 10781, checked in by Henrik Bettermann, 11 years ago

Shorten use case titles.

Link data entities to use cases only if necessary/interesting.

File size: 2.0 KB
RevLine 
[10749]1.. _label-uc-contract-manage:
2
[10781]3Manage Contract Data
[10749]4***********************************************************************
5
6Short Description
7-----------------------------------------------------------------------
8
[10780]9A contract is modified by an officer.
[10749]10
11Actor(s)
12-----------------------------------------------------------------------
13
[10753]14Officer
[10749]15
16
17Trigger(s)
18-----------------------------------------------------------------------
19
20- Imports (modifying existing data)
[10753]21- Web form(s) submitted by authorized user
[10749]22
23
24Result(s)
25-----------------------------------------------------------------------
26
27- Contract data of the given contract is modified.
28
[10780]29- Any optional supplementary contract can be booked for the new contract.
[10749]30
31
32Incoming Data
33-----------------------------------------------------------------------
34
[10753]35- Contract ID, names and values of parameters to change
[10749]36
37Outgoing Data
38-----------------------------------------------------------------------
39
[10753]40- Message about contract modification
41- (optional) Regarding customer is informed by email or SMS.
[10749]42- Log message
43
44
45Precondition(s)
46-----------------------------------------------------------------------
47
48- Contract ID must exist.
49- Submitting user must be authorized to perform the operation.
50
51
52Postcondition(s)
53-----------------------------------------------------------------------
54
55- The contractual parameters were checked for validity.
56
57
58Invariant(s)
59-----------------------------------------------------------------------
60
61
62Essential Steps
63-----------------------------------------------------------------------
64
65- System receives contract ID and any optional parameters
66  specifying the data to change in the contract.
67- Data is validated.
68- If passed-in parameters are invalid, user is offered a possibility
69  to fix the invalid data.
70- System updates the given contract.
71
72
73Open Issues
74-----------------------------------------------------------------------
75
76
77
78Remarks
79-----------------------------------------------------------------------
80
81
82.. raw:: latex
83
[10780]84      \
Note: See TracBrowser for help on using the repository browser.