38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
|
## ADDED Requirements
|
||
|
|
|
||
|
|
### Requirement: User registration
|
||
|
|
The system SHALL allow new users to create accounts with email and password.
|
||
|
|
|
||
|
|
#### Scenario: Successful registration
|
||
|
|
- **WHEN** user provides valid email, password, and confirms password
|
||
|
|
- **THEN** system creates a new user account
|
||
|
|
- **AND** system sends email verification
|
||
|
|
|
||
|
|
#### Scenario: Duplicate email
|
||
|
|
- **WHEN** user attempts to register with an existing email
|
||
|
|
- **THEN** system returns error "Email already registered"
|
||
|
|
|
||
|
|
### Requirement: User login
|
||
|
|
The system SHALL authenticate users with email and password credentials.
|
||
|
|
|
||
|
|
#### Scenario: Successful login
|
||
|
|
- **WHEN** user provides correct email and password
|
||
|
|
- **THEN** system creates authenticated session
|
||
|
|
- **AND** redirects to dashboard
|
||
|
|
|
||
|
|
#### Scenario: Invalid credentials
|
||
|
|
- **WHEN** user provides incorrect password
|
||
|
|
- **THEN** system returns error "Invalid credentials"
|
||
|
|
- **AND** does not create session
|
||
|
|
|
||
|
|
### Requirement: Role-based access control
|
||
|
|
The system SHALL support organizer and participant roles with different permissions.
|
||
|
|
|
||
|
|
#### Scenario: Organizer access
|
||
|
|
- **WHEN** user with organizer role accesses event management
|
||
|
|
- **THEN** system allows full event CRUD operations
|
||
|
|
|
||
|
|
#### Scenario: Participant access
|
||
|
|
- **WHEN** user with participant role accesses event management
|
||
|
|
- **THEN** system restricts to read-only and registration only
|