Download
architecture review board foundations commitment review n.
Skip this Video
Loading SlideShow in 5 Seconds..
Architecture Review Board Foundations Commitment Review PowerPoint Presentation
Download Presentation
Architecture Review Board Foundations Commitment Review

Architecture Review Board Foundations Commitment Review

174 Views Download Presentation
Download Presentation

Architecture Review Board Foundations Commitment Review

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Architecture Review BoardFoundations Commitment Review Team 11 Surgery Assist

  2. ARB FCR steps • Surgery Assist Overview • Teaminformation • WinWin Agreements • OCD • Prototype • Architecture • Life Cycle Plan • Feasibility Evidence • QFP

  3. Surgery Assist Overview • Surgery Assist is a website that provide interactions between doctors and Surgery Centers. • Main activities available online: SC can post their surgical slots online, doctors can search and submit reservation, SC can approve or decline request and send notification to doctors. • Goal for the current project:To offer a specialized reservation solution that optimally connects doctors and SCs to improve the scheduling process and fill vacant surgical slots.

  4. Team’s strong points & weak points operational view • Strong Points • Our team members are all hardworking and cooperative • We know each other very well for two years • We maintain the same goal and can always reach an agreement. • We all respect other team member’s work and are very willing to help others. • Week Points • None of us have taken the Software engineering related course before or have experience in the Software management. • Some members’ course load is heavy

  5. Team’s strong points & weak points technical view • Strong Points • We are all major in Computer Science which ensures us a good understanding in the the technology field. • Most of us are Java programmer and familiar with web based technology • Week Points • Not Familiar with AWS platform

  6. Concerns & possible solutions • Since it’s a two semesters project , some of us may not be able to complete the project for the next semester • Solution: To make our current work clear and understandable which help our successors to complete the whole project. • It's not clear how difficult it is to implement some technical functions. • Solution: Learn and understand the implementation feasibility before we start to do the real work

  7. WinWin Agreements • Reservation management: Activities about the reservations. • Profile management: To record Doctor/SC’s information. • Alert management: To make notification email of important activities. • Search : To search the required information. • Surgical slot posting management: Enable SC post their surgical slot. • Payment: To implement payment online. • System monitor: Enable project owner to track and control the activities.

  8. WinWin Agreements Reservation management • As a doctor I can make a surgical slot reservation request. • As a doctor I can view/cancel a submitted surgical slot reservation request. • As a surgery centerI can view/confirm/decline a reservation request. • As a doctor / SC I can sync reservations with my Google calendar.

  9. WinWin Agreements Profile management • As a doctor / SC, I can create/update my profile. • As a doctor / SC, I can log in/off the system. • As a doctor / SC I can fetch my password if I forgot about it. • As a doctor / SC I can view doctor/ SC profiles • As a doctor / SC I can upload files (video, image)

  10. WinWin Agreements Alert management • As a doctor / SC I can set up a reminder for surgery schedule. • As a maintainer I can receive a email notification when a doctor makes a payment • As a SC I can receive a email notification when a doctor makes/cancels a reservation • As a SC I can receive a email notification when I confirm/decline a doctor reservation request • As a doctor/SC I can receive a email notification when my profile has been registered. • As a doctor I can receive a email notification when my surgery reservation is confirmed/declined • As a doctor I can receive a email notification when I make/cancel a surgical slot reservation request.

  11. WinWin Agreements Search • As a doctor, I can search for the surgery center by name/location/time. • As a doctor I can pick the top five SC according to my preference. • As a doctor I can search the surgical slot of a surgery center.

  12. WinWin Agreements Surgery Slot posting management • As a surgery center I can post a surgery slot. • As a doctor I can search the surgical slot of a surgery center.

  13. WinWin Agreements Payment • As a maintainer I can change the payment information. • As a doctor / SC I can make a payment.

  14. WinWin Agreements System monitor: • As a maintainer I can modify the role of a doctor/SC. • As a maintainer I can view/create/update/delete profiles of every doctor/SC. • As a maintainer I can verify the validity of a doctor/SC's identification. • As a maintainer, I can view/generate an activity report.

  15. WinWin Agreements Priority of all agreements:

  16. WinWin AgreementsSort based on the score

  17. WinWin Agreements Priority • Alert Management • Reservation Management. • Profile Management • Search • Surgical Slot posting management • Payment • System Monitor

  18. Operational Concept • SurgeryAssist System is a specialized web based online reservation system that optimally connects surgeons and outpatient surgery centers to improve the scheduling process and fill vacant surgical slots. • For outpatient surgery centers seeking to have their surgery rooms optimally filled, thereby covering the large operating costs from underutilization of their facility. • For surgeons seeking surgical slots who are frustrated with the current antiquated scheduling system. System Purpose

  19. Operational Concept Shared Vision

  20. Operational Concept Proposed New System- workflow

  21. Operational Concept Proposed New System - features

  22. Operational Concept Benefit Chain Diagram

  23. Operational Concept System Boundary

  24. Operational Concept Element Relational Diagram

  25. Operational Concept Core Capabilities

  26. Operational Concept Constraints and Goals

  27. Prototype • Goals: • To mitigate high-risk items. • To prove that the suggested solutions are viable • “To simulate interactions between users and applications” ——from ICSM-EPG

  28. Prototype • HIGH-RISK items: • Reservation process usability and complexity: • If either doctors or surgery centers think Surgery Assist' s reservation process is too complex to improve current working sufficiency, means our system is less attractive to customers, this will break our assumption in program model and lead to a severe result • Surgery center and doctors' identification: • If either side's identification is not fully validated, means there exists some faked surgery centers and invalid doctors, who tried to use this system illegally or irresponsibly, this will tarnish our reputation and lose customs.

  29. Prototype • Mock-up prototype of flow diagram to simplify and visualize the process. • A license field is required when sign up as a doctor or a surgery center. While more

  30. Prototype • Functional Prototype: • 1 Login Page Prototype • WC_2753: As a doctor / surgery center, I can log in/off the system.

  31. Prototype • 2 File upload • WC_2423:As a doctor / surgery center I can upload files (video, image) • An important add-on to the current profile creation module.

  32. Prototype • 3 Basic Search and Display by Map • WC_2739: As a doctor, I can search for the surgery center by name/location. • In addition, try to test the interoperability with Google Map

  33. Prototype • 3 Basic Search and Display by Map

  34. Prototype • 3 Basic Search and Display by Map

  35. Prototype • 3 Basic Search and Display by Map

  36. Prototype • Google Map: • Chosen NCS to display the location of the searched result. • Basic Used API: • Google.maps.map class • Google.maps.marker class • Geocoding service. • Distance service.

  37. Prototype • Suggested Solutions as to NCS / NDI: • Google Calendar API • Java Google Calendar API / libraries. • Javascript Google Calendar API • Google Calendar plugin.(JS) • https://developers.google.com/google-apps/calendar/v2/developers_guide_java • JDBC + MySql

  38. Prototype • Email Notification Module: • A button-clicked event is invoked on client-side and send a request to server to call a notification procedure. • Build our own email server, and use “mailto”to send the concerning stakeholder a notification email with a hyperlink. • Click the link sent to the stakeholder, log into the system and achieve the task.

  39. Architecture

  40. Architecture

  41. Architecture

  42. Architecture

  43. Architecture

  44. Architecture

  45. Architecture

  46. Architecture

  47. Architecture

  48. Architecture

  49. Architecture

  50. Architecture