Difference between revisions of "Administer Permissions and Settings"
From AccountIT
(Created page with " == Overview == {| class="wikitable" ! Use Case Title !! Administer Permissions and Settings |- | Project || XX |- | Short description || XX |- | Actor - primary || System Ad...") |
|||
| Line 4: | Line 4: | ||
! Use Case Title !! Administer Permissions and Settings | ! Use Case Title !! Administer Permissions and Settings | ||
|- | |- | ||
| − | | Project || | + | | Project || |
|- | |- | ||
| − | | Short description || | + | | Short description || The UC is to provide functionality to manage use accounts, such that users can perform required tasks within AccountIT. |
|- | |- | ||
| Actor - primary || System Administrator | | Actor - primary || System Administrator | ||
| Line 12: | Line 12: | ||
| Actor - secondary || | | Actor - secondary || | ||
|- | |- | ||
| − | | Pre-conditions || | + | | Pre-conditions || AccountIT is running and Actor has the required permissions to access the functionality. The Actor has selected this function in AccountIT. |
|} | |} | ||
== Basic Flow == | == Basic Flow == | ||
{| class="wikitable" | {| class="wikitable" | ||
| − | ! Steps !! Comments | + | ! Id !! Steps !! Comments |
|- | |- | ||
| − | | 1. | + | | 1. || The Actor selects a feature he wants to use || Examples of features are: "create user", "change user permissions", "delete user" |
|- | |- | ||
| − | | 2. | + | | 2. || The System requests Actor to provide parameters for requested feature || E.g. is "change user permissions" is selected, parameter would be "select user" for existing list of users. |
| + | |- | ||
| + | | 3. || The Actor enters require parameters || | ||
| + | |- | ||
| + | | 4. || The System provides access to the selected feature || The feature is displayed with appropriate controls (such as lists, edit boxes, etc.) | ||
| + | |- | ||
| + | | 5. || The Actor enters required information for selected feature and requests to save the changes || | ||
| + | |- | ||
| + | | 6. || The System saves the changes || The work flow after completing the feature needs to be defined as part of UX design | ||
|} | |} | ||
== Alternative Flows == | == Alternative Flows == | ||
| − | # | + | # (after 1): User does not have permission to particular feature. |
| − | # | + | # (after 1): Feature temporarily not available |
| − | # | + | # (after 3): The entered parameter does not validate |
| − | + | # (after 5): The entered information does not validate | |
| + | # (after 6): Saving information fails | ||
== Additional Comments == | == Additional Comments == | ||
| + | * Each distinct function in AccountIT can have own permissions settings enabling fine-grained control on access. | ||
| + | * | ||
== Document History == | == Document History == | ||
Revision as of 09:53, 17 August 2014
Overview
| Use Case Title | Administer Permissions and Settings |
|---|---|
| Project | |
| Short description | The UC is to provide functionality to manage use accounts, such that users can perform required tasks within AccountIT. |
| Actor - primary | System Administrator |
| Actor - secondary | |
| Pre-conditions | AccountIT is running and Actor has the required permissions to access the functionality. The Actor has selected this function in AccountIT. |
Basic Flow
| Id | Steps | Comments |
|---|---|---|
| 1. | The Actor selects a feature he wants to use | Examples of features are: "create user", "change user permissions", "delete user" |
| 2. | The System requests Actor to provide parameters for requested feature | E.g. is "change user permissions" is selected, parameter would be "select user" for existing list of users. |
| 3. | The Actor enters require parameters | |
| 4. | The System provides access to the selected feature | The feature is displayed with appropriate controls (such as lists, edit boxes, etc.) |
| 5. | The Actor enters required information for selected feature and requests to save the changes | |
| 6. | The System saves the changes | The work flow after completing the feature needs to be defined as part of UX design |
Alternative Flows
- (after 1): User does not have permission to particular feature.
- (after 1): Feature temporarily not available
- (after 3): The entered parameter does not validate
- (after 5): The entered information does not validate
- (after 6): Saving information fails
Additional Comments
- Each distinct function in AccountIT can have own permissions settings enabling fine-grained control on access.
Document History
| Date | Version | Description | User |
|---|---|---|---|
| 2014-08-16 | 0.1 | 1st draft | Arvinder Singh |