Difference between revisions of "PubMan Func Spec Organizational Unit Management"
Jump to navigation
Jump to search
Line 24: | Line 24: | ||
===Post-Conditions / Results=== | ===Post-Conditions / Results=== | ||
*The new organizational unit in the state “open” is created. | *The new organizational unit in the state “open” is created. | ||
===Discussion=== | |||
[[Talk:PubMan_Func_Spec_Organizational_Unit_Management#UC_PM_OUM_01 Create organizational unit]] | |||
==UC_PM_OUM_02 Edit organizational unit== | ==UC_PM_OUM_02 Edit organizational unit== |
Revision as of 09:02, 22 January 2008
|
UC_PM_OUM_01 Create organizational unit[edit]
The user creates a new organizational unit and specifies the position in the organizational unit structure.
Status/Schedule[edit]
- Status: in specification
- Schedule:R3
Triggers[edit]
- The user wants to create a new organizational unit.
Actors[edit]
- Service Administrator
Pre-Conditions[edit]
- None
Flow of Events[edit]
- 1. The user chooses to create an organizational unit.
- 2. The system displays an organizational unit details view.
- 3. The user enters the data for the new organizational unit.
- 4. (Optionally) The user selects one or more parent organizational units in the organizational unit structure.
- 5. The user confirms the creation.
- 6. The system checks if an organizational unit with the given name already exists under the same parent.
- a. An organizational unit with the given name does not exist under the same parent.
- b. Otherwise the system displays an error message (MSG_PM_OUM_01), continue with 3.
- 7. The system creates and stores a new organizational unit in state “open” and the relations to the parent organizational units. The system displays a success message (MSG_PM_OUM_02). The use case ends successfully.
Post-Conditions / Results[edit]
- The new organizational unit in the state “open” is created.
Discussion[edit]
Talk:PubMan_Func_Spec_Organizational_Unit_Management#UC_PM_OUM_01 Create organizational unit
UC_PM_OUM_02 Edit organizational unit[edit]
The user changes data of an organizational unit.
Status/Schedule[edit]
- Status: in specification
- Schedule:R3
Triggers[edit]
- The user wants to edit the data of an organizational unit.
Actors[edit]
- Service Administrator
Pre-Conditions[edit]
- An organizational unit is selected.
Flow of Events[edit]
- 1. The user chooses to edit the selected organizational unit.
- 2. The system displays the details of the selected organizational unit in an edit view.
- 3. (Optionally) The user changes the data for the organizational unit.
- 4. (Optionally) The user changes the parent organizational units.
- 5. The user confirms the changes.
- 6. The system checks if an organizational unit with the given name already exists under the same parent.
- a. An organizational unit with the given name does not exist under the same parent.
- b. Otherwise the system displays an error message (MSG_PM_OUM_01), continue with 3.
7. The system stores the changes and displays a success message (MSG_PM_OUM_02). The use case ends successfully.
Post-Conditions / Results[edit]
- The changed organizational unit is stored.