System Constraints
Registered by
Sylvain Falardeau
Description of the basic constraints to take into account when designing and testing the system.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
- All components and services use network encrypted connections.
- The system should not have a single point of failure that can disrupt the authentication and authorization of users. Limiting authentication and authorization management for a short period is acceptable.
- A catastrophic pillar failure should be repairable in less than an hour.
- The authentication security level should be equal or superior to traditional password.
- Is performing acceptably with 10K users in the database (indexes, etc.).
- Support for 200 real users.
- Support for 400 hosts.
(?)
