Project Milestone 4

Architecture Documentation Package

Architecture Package Review

1. Question Set Name: ## Capturing Stakeholder Concerns

Design Diagrams Modifications

Final Implementation of the Mr. ED System

Specify the remaining implementation goals for this last sprint. Implement them and comment on the completion. Describe what goals were in the previous sprints, why they were shifted, and when they were completed.

The following describes the goals in each sprint/milestone:

• Milestone 1: Obtain a clear idea of the project's system, identify primary actors, create and describe use case diagrams.
• Milestone 2: Develop a comprehensive plan for the code architecture, complete all required design diagrams, complete the full-stack development (front-end, back-end, database, and connections) for the login and registration pages.
• Milestone 3: Complete 80% of the system's code, implement design patterns and architectural tactics, and update design diagrams.
• Milestone 4: Complete the remaining features, minor bug fixes, and styling for this web application, write and review the architecture package, and update design diagrams.

Some goals in these milestones were moved to other milestones.

• Milestone 1: All goals were completed in Milestone 1.
• Milestone 2: There were difficulties with creating the connections between the front-end, back-end, and database in MongoDB. This task was shifted to and completed in Milestone 3. All other goals set for Milestone 2 were completed in Milestone 2.
• Milestone 3: All goals were completed in Milestone 3.
• Milestone 4: All goals were completed in Milestone 4.

A detailed description of the implementation goals for this last sprint are described below. All implementation goals set for Milestone 4 were completed.

• Doctor view: View the medical ticket details (priority, symptoms, emergency department, and medical information) and accept the ticket to treat the patient.
• Notify patient: Notify the patient on the "Patient Waiting" screen. When the nurse has set a priority to the patient's ticket, the patient will be notified what place in line they are in. If more patients enter the queue, the place in line will continue to be updated. In addition, the patient will be notified when the doctor is ready to see them.
• User authentication: Only allow certain user types to view/use certain pages. For example, Patients should only be allowed to access the "Enter Virtual Triage" page.
• Added multiple rest API routes, with GET and POST HTTP methods used.

The Mr. ED web application is now complete and fully functional.

** It is very important to note that this web application will not function without our MongoDB database. If needed, we can come to campus and demo it. **

Contribution Summary

• Ashley: Worked on the doctor view feature so the doctor can select and view medical ticket details. Performed testing on the web application. Completed documentation in the Wiki, including the Incremental Construction and a description of our final implementation. Conducted the review of the architectural package.
• Liam:
• Erich:
• Issac: