architecture review board foundations commitment review

1

Architecture Review Board

Foundations Commitment Review

Team 11 Surgery Assist

2

ARB FCR steps Surgery Assist Overview Team information

WinWin Agreements OCD Prototype Architecture Life Cycle Plan Feasibility Evidence QFP

3

Surgery Assist OverviewSurgery 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 PointsWe 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 PointsNot Familiar with AWS platform

6

Concerns & possible solutionsSince it’s a two semesters project , some of us

may not be able to complete the project for the next semesterSolution: 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 AgreementsReservation management

1. As a doctor I can make a surgical slot reservation request.

2. As a doctor I can view/cancel a submitted surgical slot reservation request.

3. As a surgery center I can view/confirm/decline a reservation request.

4. As a doctor / SC I can sync reservations with my Google calendar.

9

WinWin AgreementsProfile management

1. As a doctor / SC, I can create/update my profile.2. As a doctor / SC, I can log in/off the system.3. As a doctor / SC I can fetch my password if I

forgot about it.4. As a doctor / SC I can view doctor/ SC profiles5. As a doctor / SC I can upload files (video, image)

10

WinWin AgreementsAlert management

1. As a doctor / SC I can set up a reminder for surgery schedule.2. As a maintainer I can receive a email notification when a doctor makes a

payment3. As a SC I can receive a email notification when a doctor makes/cancels a

reservation4. As a SC I can receive a email notification when I confirm/decline a doctor

reservation request5. As a doctor/SC I can receive a email notification when my profile has been

registered.6. As a doctor I can receive a email notification when my surgery reservation is

confirmed/declined7. As a doctor I can receive a email notification when I make/cancel a surgical slot

reservation request.

11

WinWin AgreementsSearch

1. As a doctor, I can search for the surgery center by name/location/time.

2. As a doctor I can pick the top five SC according to my preference.

3. As a doctor I can search the surgical slot of a surgery center.

12

WinWin AgreementsSurgery Slot posting

management1. As a surgery center I can post a surgery slot.2. As a doctor I can search the surgical slot of a

surgery center.

13

WinWin AgreementsPayment

1. As a maintainer I can change the payment information.

2. As a doctor / SC I can make a payment.

14

WinWin AgreementsSystem monitor:

1. As a maintainer I can modify the role of a doctor/SC.

2. As a maintainer I can view/create/update/delete profiles of every doctor/SC.

3. As a maintainer I can verify the validity of a doctor/SC's identification.

4. As a maintainer, I can view/generate an activity report.

15

WinWin AgreementsPriority of all agreements:

16

WinWin AgreementsSort based on the score

17

WinWin AgreementsPriority

1. Alert Management2. Reservation Management.3. Profile Management4. Search5. Surgical Slot posting management6. Payment7. 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 ConceptShared Vision

20

Operational ConceptProposed New System- workflow

21

Operational ConceptProposed New System -

features

22

Operational ConceptBenefit Chain Diagram

23

Operational ConceptSystem Boundary

24

Operational ConceptElement Relational Diagram

25

Operational ConceptCore Capabilities

26

Operational ConceptConstraints and Goals

27

PrototypeGoals:

To mitigate high-risk items.To prove that the suggested solutions

are viable “To simulate interactions between

users and applications” ——from ICSM-

EPG

28

PrototypeHIGH-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

PrototypeFunctional Prototype:1 Login Page Prototype

WC_2753: As a doctor / surgery center, I can log in/off the system.

31

Prototype2 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

Prototype3 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

Prototype3 Basic Search and Display by Map

34

Prototype3 Basic Search and Display by Map

35

Prototype3 Basic Search and Display by Map

36

PrototypeGoogle Map:

Chosen NCS to display the location of the searched result.

Basic Used API:Google.maps.map classGoogle.maps.marker classGeocoding service.Distance service.

37

PrototypeSuggested Solutions as to NCS / NDI:

Google Calendar APIJava Google Calendar API / libraries.Javascript Google Calendar APIGoogle Calendar plugin.(JS)https://developers.google.com/google-apps/

calendar/v2/developers_guide_java

JDBC + MySql

38

PrototypeEmail 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

51

Architecture

52

Architecture

53

Architecture

54

Architecture

55

Architecture

56

Life Cycle PlanOverall StrategyThe Surgery Assist is Net-Centric Service. We need to use a lot of services. For instance, Google maps, Paypal and Amazon etc. Data stored on service host’s servers. Patching on service provider’s side; mostly does not require installation on client side. Change on the server side can result in the client side. The integration could be done merely in code, without additional installation of external components.Team follows ICSM to develop the system.

57

Life Cycle PlanYu Fang-Project Manager/Life Cycle PlannerYu Zhang-Software Architect/PrototyperHeguang Liu-OCE/Software ArchitectWanghai Gu-Life Cycle Planner/OCEZhen Li-Feasibility Analyst/ Requirement EngineerLonfeng Jia-Prototyper/ Feasiblity AnalystXiheng Yue-IIV&V/Quality Focal Point

58

Life Cycle Plan(Project plan on Foundation Phase) Foundations phase Duration: 10/21/13- 12/02/13 Concept: They assess project status, feasibility evidence, life cycle content,

operational concept, prototype and components, system architecture. Also, they plan and manage detail project plan, record project progress, manage project quality by verifying and validate work products using Defect Tracking System, fix defects, develop prototype, develop software architecture.

Deliverables: Development Commitment Package, Draft Development Commitment Package, Progress Report, Project Plan and Project Effort Reports, Release Description, System and Software Architecture Description, System and Software Requirements Definition, Software Components, UML Model

Milestone: Development Commitment Review, Architecture Review Board Strategy: One Incremental Commitment Cycle

59

Life Cycle Plan(Valuation Phase)

David Vosicher-Client/MaintainerMake client feedback form,Assess prototype and components

60

Life Cycle Plan(Valuation Phase)

Yu Fang-PM/LCPRecord progress report,Make detailed project plan on next phase Organize WinWin condition requirement.Assist with Life Cycle plan

61

Life Cycle Plan(Valuation Phase)

Yu Zhang-SA/PrototyperMake UML model,Assess system architecture,Define technology-independent architecture,Define technology-dependent architecture,Make system and software architecture description

62

Life Cycle Plan(Valuation Phase)

Heguang Liu-OCE/SAComplete system transformation strategies as coordinated with operational stakeholdersComplete operational and organizational transformationsMake additional prototypes and further elaboration of the existing prototypes

63

Life Cycle Plan(Valuation Phase)

Wanghai Gu-LCP/OCEPlan achievable budgets and schedules with respect to the architecture in the SSAD and detailed development plans for the Development phase.Identify detailed plan for 1st…N iterations in Section 6.1Prepare for Development Commitment Review and Rebaselined Development

64

Life Cycle Plan(Valuation Phase)

Zhen Li-FA/REDescribe feasibility evidence,Assess feasibility evidence Define System and Software requirements

65

Life Cycle Plan(Valuation Phase)

Longfeng Jia-Prototyper/FAMake client feedback form,Develop prototype,Assess prototype and components,Analyze and prioritize capabilities to prototype

66

Life Cycle Plan(Valuation Phase)

Xiheng Yue-IIV &V/QFPConstruct traceability matrix,Record on Bugzilla repository,Verify and validate work projects,Track defects

67

Life Cycle Plan(Resource Estimation)

68

Feasibility Evidence NDI/NCS Alternatives

69

Feasibility Evidence NDI/NCS Evaluation & Analysis Results

70

Feasibility Evidence NDI/NCS Evaluation & Analysis Results

71

Feasibility Evidence Business Case- Program Model

72

Feasibility Evidence Business Case-Cost Analysis

73

Feasibility Evidence Business Case-Market Trend

74

Feasibility Evidence Business Case-Cost Analysis (Hardware/Software)

75

Feasibility Evidence Business Case-Benefit Analysis

76

Feasibility Evidence Business ROI Analysis

77

Feasibility Evidence Reservation process usability and complexity:

too complex to improve current reservation process ->our system is less attractive to customers

Major Risks

Mitigation - Use simple and clean UI, build system

easy to operate. - Negotiate and try to make the process as

simple and easy as possible.

Surgery center and doctors‘ identification: either side’s identification is not fully validated ->illegally or irresponsibly use -> disrepute and lost customs

Mitigation

- Use simple and clean UI, build system easy to operate.

- Negotiate and try to make the process as simple and easy as possible.

78

Feasibility Evidence Designed tool may not interact with the

surgery center database as planned: Each center may have their own operating platform and SurgeryAssist may need to customize the web version tool to interface with those systems.

Major Risks

Mitigation

- Design the tool(Google Calendar) to fit the most popular operating platforms used by the ASCs.

- For centers that use non-compatible platform, SurgeryAssist will implement a strategy to customize and will assign more resources ahead of time.

79

Feasibility Evidence Capability Feasibility evidence

80

Feasibility Evidence LOS Feasibility evidence

81

Feasibility Evidence LOS Feasibility evidence



82

Feasibility Evidence Personas

83

Feasibility Evidence Personas

84

Feasibility Evidence Personas

85

OCD (goal)

User Requirements Architect (use-case diagram)

OC-1 WC_2774, WC_2763, WC_2734, WC_2429

UC-14, UC-15, UC-16, UC-09, UC-08, UC-10, UC-31

OC-2 WC_2754, WC_2753, WC_2736, WC_2426, WC_2423

UC-01, UC-02, UC-03, UC-04, UC-05, UC-06, UC-28

OC-3 WC_2434, WC_2422, WC_2419, WC_2418, WC_2415, WC_2410, WC_2409

UC-27, UC-32

OC-4 WC_2739, WC_2432, WC_2428

UC-07

OC-5 WC_2775, WC_2761 UC-11, UC-12, UC-13OC-6 WC_2276, WC_2425 UC-26, UC-30OC-7 WC_2767, WC_2766,

WC_2765, WC_2764UC-25, UC-20, UC-21, UC-22, UC-19, UC-17, UC-18,

QFP: Traceability Matrix

86

Quality Management Strategies

Identify Defect Prevention StrategiesIdentify Defect Detection StrategiesIdentify Defect Removal Tracking StrategiesIdentify Level of Service Achievement MonitoringIdentify Process AssuranceIdentify IIV&V Coordination Strategy

87

Using Dropbox store latest documents and project website store milestone documents. Keeping record of version history in each individual document.

Instant messenger software like QQ to help communicate with each other and keep the consistency within the team.

Quality Management Strategies

Currently Adopted Technique:Prevention strategies:

Win-win, ICSM Standard, Prototyping, Dry Run

Detection strategies: Completeness Checking, Consistency Checking, Traceability Checking, Peer Review, Grading

88

5 team activities recorded11 component assignments recorded4 defects recorded

Bugzilla Statistics

89

Defect Identification ReviewPeer review and IIV&V were used on document section and UML model. Also gained some help form grading and client feedback to identify some defects.

Defect StatusWe don't organize the win-win condition well so it waste some time during the win-win session to delete the duplicate ones

Resolved and Verified

Lack of familiarity with the current system architecture and framework

Resolved and Verified

The AWS web hosting for current web system is not working properly

Confirmed, waiting feedback

Fail to organize risks properly in the prototype presentation.

Confirmed, waiting feedback

90

Configuration Management Strategies

Define product element identificationIdentify configuration items and rationaleIdentify configuration change managementDefine project library managementIdentify resources, personnel and tool

91

How to Handle Change Request