Changeset 10754 for main/eko-disco-specs
- Timestamp:
- 18 Nov 2013, 08:36:20 (11 years ago)
- Location:
- main/eko-disco-specs/trunk/use-cases
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
main/eko-disco-specs/trunk/use-cases/contract-add.rst
r10753 r10754 3 3 Use-Case: Add a Contract 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/contract-manage.rst
r10753 r10754 3 3 Use-Case: Manage Contract Data 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/contract-remove.rst
r10753 r10754 3 3 Use-Case: Remove a Contract 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/customer-add-by-anon.rst
r10753 r10754 3 3 Use-Case: Add a Customer by Anonymous User (self-registration) 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/customer-add-by-mg.rst
r10753 r10754 1 1 .. _label-mg-customer-add: 2 2 3 Use-Case: Add a Customer ny user3 Use-Case: Add a Customer by officer 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description 15 7 ----------------------------------------------------------------------- 16 8 17 A customer is manually added to the system by user.9 A customer is manually added to the system by authorized user. 18 10 19 11 Actor(s) -
main/eko-disco-specs/trunk/use-cases/customer-edit-basedata.rst
r10753 r10754 3 3 Use-Case: Edit Basic Customer Data 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/customer-remove.rst
r10753 r10754 3 3 Use-Case: Remove Customer 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/meter-reading.rst
r10753 r10754 1 1 Use Case: Reading a Meter 2 2 *********************************************************************** 3 4 .. Description of a use case5 .. The description must be formulated as seen from system (not: actors)6 .. Describes those changes an (outside) actor can notice7 .. Short and abstract as possible, as long as necessary.8 .. Each use case must have at least one actor involved9 .. Each use case must have a trigger and a result10 11 3 12 4 Short Description -
main/eko-disco-specs/trunk/use-cases/service-add.rst
r10753 r10754 3 3 Use-Case: Add a service 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/service-manage.rst
r10753 r10754 3 3 Use-Case: Modify a Service 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. 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 5 14 6 Short Description -
main/eko-disco-specs/trunk/use-cases/service-remove.rst
r10753 r10754 3 3 Use-Case: Remove a Service 4 4 *********************************************************************** 5 6 .. Description of a use case7 .. The description must be formulated as seen from system (not: actors)8 .. Describes those changes an (outside) actor can notice9 .. Short and abstract as possible, as long as necessary.10 .. Each use case must have at least one actor involved11 .. Each use case must have a trigger and a result12 13 5 14 6 Short Description
Note: See TracChangeset for help on using the changeset viewer.