source: main/eko-disco-specs/trunk/use-cases/contract-add.rst @ 11114

Last change on this file since 11114 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.2 KB
RevLine 
[10749]1.. _label-uc-contract-add:
2
[10781]3Add a Contract
[10749]4***********************************************************************
5
6Short Description
7-----------------------------------------------------------------------
8
[10753]9A contract is added for some customer.
[10749]10
11Actor(s)
12-----------------------------------------------------------------------
13
[10780]14Officer, Customer
[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- A new contract was created with unique contract ID.
28
[10780]29- Any optional supplementary contract can be booked for the new contract.
[10749]30
31
32Incoming Data
33-----------------------------------------------------------------------
34
35- Customer ID, service ID, respective contractual parameters (like:
36  start of service, end of service, picked payment methods, etc.)
37
38Outgoing Data
39-----------------------------------------------------------------------
40
[10753]41- Message about contract creation
[10749]42- Log message
43
44
45Precondition(s)
46-----------------------------------------------------------------------
47
48- Customer ID must exist and be valid for new contracts.
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 customer ID, service ID and any optional parameters
66  specifying the contract to create.
67- Passed in service is requested to create a new contract with
68  passed-in parameters (contractual details) set (inludes validating
69  the passed in data).
70- If passed-in parameters are invalid, user is offered a possibility
71  to fix the invalid data.
72- System creates the new contract connecting it to the given
73  customer ID.
74
75
76Open Issues
77-----------------------------------------------------------------------
78
79
80
81Remarks
82-----------------------------------------------------------------------
83
84
85.. raw:: latex
86
[10780]87      \
Note: See TracBrowser for help on using the repository browser.