1. SaveMe Project Report - 2 SYSM 6309 Advanced Requirements Engineering – Spring 2015 PROJECT TEAM Kathyayini Kattamanchikxk127230@utdallas.edu Faizal Khaderfxk140730@utdallas.edu Mathew Reynoldsmmar059000@utdallas.edu

2. Agenda “As-Is” o Problem Identification Requirements Engineering o Goals o Domain o Stakeholders & Roles o Development Process o Requirements Engineering Process – Spiral Model “To-Be” o Requirements Model – 4 Variable Model o Functional Requirements o Non – Functional Requirement Solutions Context o Class Diagram o Problem Interdependency graph o Solutions Interdependency graph o App Screens Why team “Save Me” Demo – Q&A

3. As-Is

4. Scenario I am 74 yrs. old and live alone. I went out my front door to pick up my daily newspaper, when I bent over to get it, I fell. I simply could not pick myself up. My iPhone, which was on my hand as well, fell down the front porch. Could not reach it either. My legs just would not work!! I live on 5 acres, no one could hear me if I yell.

5. Problem Identification There are lots in the elderly community who live alone. Home safety hazards such as poor lighting and loose carpeting The elderly usually have poor eyesight Elderly people are often subject to falls While living with someone may not prevent a fall, it usually means that the victim of a fall gets immediate attention

6. Requirements Engineering

7. Goals Develop a smartphone App, which when running in background will get activated when the phone gets a hard sudden jerk, like the person using it falling down, with the phone in the pocket or the phone thrown off his/her hands The App should immediately provide an easy to call emergency method The App should have a mechanism to initiate an automated call, after a period of delay that the owner is not able to reach to the fallen down phone device

8. Domain Old and helpless people living alone, but still being able to use a Smartphone Expectant mothers People who just came out of a serious surgery, left home alone in a condition with less mobility

9. Stakeholders & Roles Stakeholders are the end users (old and people with less mobility) who will be benefited by this Smartphone app Also the contacts who respond to the App in situations of emergency The project will use roles as – o Requirements Engineer o Software Engineer o Testing Engineer

10. Development Process An iterative development process will be followed by starting with a beta release of the concept, looking for marketability and then re- planning for enhancements.

11. Requirements Engineering Process - Spiral Model Planning: o We will be determining the objectives and constraints Risk Analysis: o Analyze alternatives and attempts to identify and resolve the risks involved Development: o Product development and testing product. Assessment: o Customer evaluation

12. To-Be

13. Scenario I remembered that I had “SaveMe” with me. The alert got kicked off automatically, I could hear my son screen mom....mom!, but was too far away to respond. Shortly EMS/ambulance, my niece and son arrived. All ended well and I thank “SaveMe” for the prompt help. God Bless you all!

14. Requirements Model - 4 Variable Model Environment - Monitored Variables o Detect Phone falls/Phone gets a sudden jerk System – Input o Phone’s acceleration o Internal representation using Phone’s accelerometer System – Output o Activate the App o Display Alert Screen o Place/Cancel Call Environment - Controlled Variables o Place call to emergency number listed o Play Pre-recorded Message

15. Functional Requirements IDDescriptionWeight age FRS-001 The App shall deliver the base functionality of being dormant and getting activated on the event when the phone instrument receives a jerk. 15% FRS-002 The App shall get into a countdown timer and beep for a specified time period. 10% FRS-003 The App shall call a predefined emergency number and play back a message, asking for help. 15% FRS-004 The App shall provide a button to easily click and call an emergency number. 10% FRS-005 The App shall provide a mechanism to deliberately get to an alert mode with ease. 10% FRS-006The App will deliver a functionality, where the contacts listed in the emergency call list are evaluated by their geographic location for distance from the user. The one nearest to the App user will be given higher priority while making the emergency call. N/A FRS-007The App will provide a list of emergency numbers and will loop through the list until one of them answers. This will happen in addition to leaving the message in the voicemail inbox if nobody answers the call. N/A

16. Non-Functional Requirements IDDescriptionWeighta ge NFRS-001 The App shall work on all devices iPhone 4S and upward models. 30% NFRS-002 The App shall have an simple intuitive to use interface.5% NFRS-003 The App shall have a high visible buttons, easy to read for the old aged. 5% Total = FRS + NFRS = 100%  The App will allow requirements to be changed or extended for the phase-1 release, with the total change weightage not exceeding 20% as a scope creeping rate.

17. App Highlights Our team has successfully developed an app that runs on Apple iPhone 4S and above. [NFRS-001] App consists of activated screen, alert screen with Cancel, Call button and count down timer [NFRS-002] Text through out the App is Times New Roman 32 Font size [NFRS- 003] User launches the App, backgrounds it by double pressing the Home button (if needed) [FRS-001] App continues to operate in the back ground [FRS-001]

18. App Functionality - Scenario 1 User drops the phone, or any hard jerk to the phone which takes the acceleration of the phone in any direction (x/y/z) greater that 9.81 m/s [FRS-001] Save Me app gets activated and ‘Activated Screen’ is displayed [FRS- 001] Alert Screen is displayed with Cancel and Call buttons along with count down timer (configurable) of 10 seconds and a beep [FRS- 002] Pressing cancel before count down timer expires, App back grounds [FRS-005]

19. Contd., Cancel is not pressed before countdown timer expires, a call to the emergency contact number is placed automatically [FRS-003] o Pre-recorded message is played upon answering the call (OR) pre- recorded message is left in answering machine. Call disconnected, app returns to back ground

20. Contd., User presses Call button before count down timer expires [FRS-004] Call is placed to the emergency contact o Pre-recorded message is played upon answering the call (OR) pre- recorded message is left in answering machine Call disconnected, app returns to back ground

21. Solutions Context

22. Class Diagram

23. Problem Interdependency graph

25. Solutions Interdependency graph - Tracebility

27. App Screens – App Icon

28. Activated Screen The ‘Activated Screen’ (with the picture of the lady falling down) will also be a button, which when pressed will allow the user to be taken automatically to the ‘Alerted screen’ (next slide)

29. Alerted Screen This screen provides multiple actions o Cancel Button – Cancels the alert and takes the user back to the ‘Activated Screen’ o Phone Button – Emergency number can be immediately called by clicking this button, with out waiting for the countdown. o Countdown Timer – Counts down and at the end automatically calls the emergency number to play a automated help message.

30. Why team ‘Save Me’ A problem that is evident got identified and analyzed to find an appropriate solution The team followed the well prescribed requirement engineering processes in the likes of iterative spiral model for achieving the project goals A simple to use solution for the problem got conceived in the shortest time possible The solution created has a potential to grow and be used in saving lives The team has created a solution that creates an alerting service with no additional hooks, and can be offered free of charge to the public.

31. Demo – Q&A