32 lines
1.1 KiB
Markdown
32 lines
1.1 KiB
Markdown
|
## ADDED Requirements
|
||
|
|
|
||
|
|
### Requirement: Users can be managed
|
||
|
|
The system SHALL provide an interface for administrators to manage system users.
|
||
|
|
|
||
|
|
#### Scenario: View user list
|
||
|
|
- **WHEN** administrator navigates to /master-data/users
|
||
|
|
- **THEN** system displays a list of users
|
||
|
|
- **AND** list includes username, role, status, and department
|
||
|
|
|
||
|
|
#### Scenario: Create new user
|
||
|
|
- **WHEN** administrator clicks "New User" button
|
||
|
|
- **THEN** system opens user creation form
|
||
|
|
- **AND** form includes fields for username, email, role, password
|
||
|
|
- **AND** system saves user on form submission
|
||
|
|
|
||
|
|
#### Scenario: Edit user
|
||
|
|
- **WHEN** administrator clicks edit on a user
|
||
|
|
- **THEN** system opens user edit form
|
||
|
|
- **AND** allows modification of user attributes
|
||
|
|
- **AND** updates user on form submission
|
||
|
|
|
||
|
|
#### Scenario: Delete user
|
||
|
|
- **WHEN** administrator clicks delete on a user
|
||
|
|
- **AND** administrator confirms deletion
|
||
|
|
- **THEN** system removes user from database
|
||
|
|
- **AND** prevents deletion of own account
|
||
|
|
|
||
|
|
#### Scenario: Search users
|
||
|
|
- **WHEN** administrator enters search term
|
||
|
|
- **THEN** system filters user list by username, email, or role
|