-
Notifications
You must be signed in to change notification settings - Fork 0
Requirements
Patient
FR1. The system shall allow the patient to book an appointment
FR2. The system shall allow the patient to review an appointment time
FR3. The system shall allow the patient to cancel their appointment
FR4. The system shall allow the patient to review the doctor's information.
FR6. The system shall allow the patient to update their information
FR7. The system shall allow the patient to review the map
FR8. The system shall allow the patient to login to the website
FR9. The system shall allow the patient to logout from the website
FR10. The system shall allow the patient to enable notifications
Dentist
FR11. The system shall allow the dentist to view appointments
FR12. The system shall allow the dentist to update bookable timeslots
FR13. The system shall allow the dentist to log in to the website.
FR14. The system shall allow the dentist to logout from the website
FR15. The system shall allow the dentist to update their information.
FR16. The system shall allow the dentist to publish the available slots on the map
FR17. The system shall allow the dentist to publish the notification
Admin
FR18. The system shall allow administrators to manage user accounts
FR19. The system shall allow administrators to see system logs
FR20. The system shall allow administrators to see patient statistics
FR21. The system shall allow administrators to see dentist statistics
FR22. The system shall allow administrators to see map
Quality Attribute Requirements
QAR1. The user interface shall be intuitive and easy to navigate, ensuring that both patients and dentists can perform their tasks without any delays. [Usability]
QAR2. The distributed system shall feel like one whole system to the users [Usability]
QAR3. The system shall have appropriate authentication systems for patients, dentists, and admins. [Security]
QAR4. The system shall have a low amount of latency, max 300ms. [Performance]
QAR5. The system shall handle concurrent requests. [Performance]
QAR6. The system shall be scalable to accommodate an influx of thousands of additional users. [Scalability]
QAR7. The system shall be modifiable such that an upgrade to a new front-end framework should take fewer than 2 work-weeks to implement for each user view [Modifiability].
QAR8. The system shall have availability of 99.9% uptime, as measured by ping-echo health check. [Availability]
QAR9. The system shall have unit tests in the continuous integration pipeline [Testability].
QAR10. The system shall work on all major web browsers [Interoperability].
Technical Constraints
TC1. The system must be composed of components running on independent machines
TC2. The stakeholders have asked that the project be easily scalable to accommodate an entire city of users.
Business Constraints
BC1. The project consists of three milestones (MS1, MS2, and MS3) of two weeks each, final release deadline on 2024-01-09 (Tue), and final presentation on 2024-01-09 (Wed).
BC2. The project team consists of five developers who must self-organize and work using an agile development process.
BC3. There will be an updated list of customer requirements in December 2023 which may change the scope of the project.
Domain Assumptions
DA1. Users can connect to the internet via popular web browsers such as Chrome.
DA2. Users want to have a web-based dentist-appointment booking system.