Availability Tactic

https://people.ece.ubc.ca/matei/EECE417/BASS/ch05lev1sec2.html

• Timestamp: recording login and logout time; whenever a user updates some info (Isha)
• Retry: If something went wrong, try again. If wrong again, log them out (Kaitlyn)
• Condition Monitoring: Helps with retry, constantly check for conditions & equipment status (Myfanwy)
• Increase Competence Set
• Removal from service.

Your responsibility:

Each of us has to work on 1 availability tactic and implement it + describe it in wiki

Design Patterns:

• state pattern: how login currently is (Myfanwy)
• chain of responsibility: telling a patient where they need to go i think
• Template design pattern- Patient symptom calculation (Isha)
• Observer design pattern (Treesa)
• Command pattern (Kaitlyn)

Your responsibility:

Each of us needs to pick a design pattern and implement it + describe that in wiki. Just post in discord which one are you choosing

Code that needs to be done, !!! = most important stuff:

• Database !!! (Cameron)
• Hosting !!!
• Fix login & Create account !!! (Myfanwy)
• Patient symptom input (Mostly JS, some HTML) !!! (Kaitlyn)
• Patient symptom calculations (ie where should they go) (JS only) (can have very very simplified ver for now) (Isha)
• Pharmacist/Chemist view (input prescriptions) (HTML mostly, some JS) (Kaitlyn)
• Dr/Nurse/Hospital view (send prescriptions to pharmacist, hospital/office availability, see incoming patients reported, etc) (Mostly JS, some HTML) !!! (Treesa)
• Automatically(?) do hospital wait times, could be in hospital view as well, unsure (JS, some HTML, not too sure) (lowest prio)

Your responsibility:

Pick 1 (or more) bullet points to implement, please pick !!!/highlighted ones first!