FEA24-user-management 1.0
| Feature ID | FEA24 |
| Subsystem the feature is part of | Server |
| Responsible person | Justus Hänninen |
| Status | Under review |
Description
A system for managing end users' hash values for the service.
User requirements
- System admin should be able to check the active hashes in a database
- System admin should be able to create, replace, delete and update hashes.
Technical requirements
- Hash values should be easy to create and access.
- System admin should be able to set a specific hash value for an end user.
Security requirements
- Access to the hash values should be restricted to authorized personnel at JAMK university.
- The hash values should be stored in a secure place and made sure that they don't end up to any unwanted users.
User acceptance
- The user management feature should meet the requirements and expectations of JAMK university personnel.
- The user management feature should be tested and validated by JAMK university personnel before being released.
Restrictions, requirements and use cases related to this feature
| Use Case 1 | |
| Requirement ReqID | |
| Requirement ReqID |
Preliminary user stories
- #123 US304 - As a product owner, I want service to have limited amount of "tokens" that end user has available filling
- #118 US309 - As a adminuser, I would like to able "CRUD" end user specific hash value using command line tool or Admin UI
- #120 US307 - As a adminuser, I would like to set end user specific hash value using cli tool or UI
User interface mock-up
- End-user's UI
Testing / possible acceptance criteria
Write down some notions for testing
| Testcase | Test source | Responsible |
|---|---|---|
| Testcase 1 | Requirement ID? | |
| Testcase 2 | Requirement ID? | |
| Testcase 3 | Requirement ID? | |
| Testcase 4 | Requirement ID? | |