source: main/eko-disco-specs/trunk/use-cases/service-add.rst @ 17931

Last change on this file since 17931 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-service-add:
2
[10781]3Add a Service
[10749]4***********************************************************************
5
6Short Description
7-----------------------------------------------------------------------
8
9A service is added.
10
11Actor(s)
12-----------------------------------------------------------------------
13
[10753]14Officer
[10749]15
16
17Trigger(s)
18-----------------------------------------------------------------------
19
20- Imports (adding existing data)
[10753]21- Web form(s) submitted by authorized user
[10749]22
23
24Result(s)
25-----------------------------------------------------------------------
26
[10753]27- A new service is available for customers/officers.
[10749]28
29- Contracts can be created from the new service.
30
31
32Incoming Data
33-----------------------------------------------------------------------
34
35- Title
36- Description
37- Service terms (various data about what special options the new
38  service provides, constraints, etc.).
39
40
41Outgoing Data
42-----------------------------------------------------------------------
43
[10753]44- Message about service creation
[10749]45- Log message
46
47
48Precondition(s)
49-----------------------------------------------------------------------
50
51- Submitting user must be authorized to perform the operation.
52
53
54Postcondition(s)
55-----------------------------------------------------------------------
56
57- The new service is able to create contracts.
58
59
60Invariant(s)
61-----------------------------------------------------------------------
62
63
64Essential Steps
65-----------------------------------------------------------------------
66
67- System receives customer ID, service ID and any optional parameters
68  specifying the contract to create.
69- System creates a unique service ID.
70- Passed in terms, title, and description are validated.
71- If passed-in parameters are invalid, user is offered a possibility
72  to fix the invalid data.
73- System creates the new service.
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.