Presentation on theme: "Brought to you by Team CodeEx Team MembersNet ID Mahabubul Adam Abdullah."— Presentation transcript:
Brought to you by Team CodeEx Team MembersNet IDE-mail Mahabubul Alammxa149230alam.email@example.com Adam Howardamh141830adam.firstname.lastname@example.org Abdullah Moyeenaam065000abdullah.email@example.com Fall 2014, CS/SE 6361 Interim Project Phase I Dr. Lawrence Chung The University of Texas at Dallas
Agenda The “As-Is” Scenario Problem Identification Goals Development Process RE Process Stakeholders Roles Functional Requirements Non-Functional Requirements Mockup The “To-Be” Scenario Requirements Creeping Rate Why Team CodeEx
Scene 1: Family at the Dinner Table Son: Why aren’t you eating dad? Dad: I’m again not feeling well… Son: What’s troubling you?
Dad: Umm… I have an uncomfortable feeling in my belly… and a burning sensation that moves to my chest again. Son: Again? Has this been going on for sometime? Dad: Umm… yes… maybe… I think it happened twice last week… your mom probably remembers better. Son: Mom? Mom: Yes, dad has been complaining about this discomfort for… umm… last two weeks I guess… I’m not sure exactly…
Son: What have you been eating that may have caused the pain? Dad: Umm… I don’t remember… I think I get it when I drink coffee… but I’m not going to stop drinking coffee. Son: You should keep a diary of your discomforts dad. Dad starts a diary but often forgets to log his activities. Eventually he stops, because keeping a journal just isn’t convenient.
Scene 2: Dad & Son at Doctors Office Doctor: Hello Mr. H. Good to see you! How have you been? Dad: Hello Doc. Good to see you too. I’m okay. Doctor: So... you were here a month and a half ago. How’s that headache of yours you complained about during your last visit? Did the medicines help? Dad: Umm… I think they are coming at a lesser frequency now… I’m still not sure where do they come from! But I have a new problem now…
Son: Ya, dad was complaining of heartburn last night. But he couldn’t give any details. Its has been going on for more than a few weeks. Doctor: Mr. H, let me ask you a few questions to get to the bottom of this… Dad: Umm… Uh… I think… Doctor: Mr. H. If that is the case, I will have to order some tests. Please come back and see me with the results in 2 weeks.
Doctor’s Advice? Dad might be suffering from Acid Reflux. The Doctor advised Dad to take antacid when he has heartburn. Try avoiding foods such as: Citrus fruits Chocolate Caffeinated drinks (COFFEE) or alcohol Spicy, fatty, or fried foods Garlic and onions Tomatoes
45% of U.S. adults are dealing with at least one chronic condition.  49% say they keep health information in their heads.  34% say they record it on paper.  21% say they use some form of technology  Just 29% of ER patients Required emergency attention.  In 2012, 15.4 million caregivers provided an estimated 17.5 Billion hours of unpaid care, valued at more than $216 Billion.  (CDC) 90% of U.S. adults own a cell phone; 58% of U.S. adults own a smartphone.  61.9% of US Smartphone Market belongs to Android, Worldwide its 84.7%.  58.6% of All Android Smartphones shipped costs less than $200.   Pew Research Institute, 2013.  Truven Health Analytics Study, 2013.  CDC Report 2012.  IDC Report 2014. Some Facts
Problem Identification A lot of people live with chronic illnesses which are manageable if tracked properly. As people age, the frequency of symptoms increase and becomes harder to keep a track of. Forgetfulness adds to the complexity and makes it harder for doctors to sometimes diagnose an otherwise simple/common illness.
Desired solution Need a CONVENIENT way to keep an accurate record of the activities leading up to a health related episode, so trends and contributing factors can be identified. This history can help identify possible triggers which can be useful in lifestyle modifications to reduce future occurrence of illness. This data can possibly aid doctors in diagnosis during medical visits.
Software Development & Requirements Engineering
Goals Develop a smartphone app that will allow the user to: Record and track activities in one’s daily lifestyle e.g. meals, medication, stress level, physical activity. Log health related episodes such as headaches, upset stomach, depression, aches and pains, anxiety, etc. This history can provide insight for the user to adjust their lifestyle or optionally be shared with healthcare providers to aid in a faster and more accurate diagnosis.
Domain Patient with Illness – The person using the App who wants to determine the root cause of their illness Medical Professional – Review the history data during a medical visit Family Member or Friends – Person helping the patient use the app or reviewing the history data. Ex. A daughter helping her disabled father
Team Roles End User – people who will use the App. Domain Expert – person knowledgeable in areas of chronic illnesses & their management and related industry practices. Requirements Engineer – will work with relevant parties to elicit, understand, analyse, and document the requirements. Software Engineer – will perform the duties of Developer & QA Project Manager – Responsible for successful planning, execution, monitoring, control and closure of the project.
Development Process By developing this product through iterative cycles and in small incremental portions, the team can take advantage of what is learned in class and apply it to the project. Iterative and Incremental Development
RE Process – Spiral Model Following the spiral model allowed us to go back and refine our requirements
Eliciting Requirements All Team members assuming the key roles
Software Functional Requirements UNIQUE ID DESCRIPTION FR_001MTT shall display the home screen when the application is launched FR_002MTT shall display a list of selectable triggers FR_003MTT shall have the controls to add a new trigger category FR_004MTT shall have the controls to delete an existing trigger category FR_005MTT shall have the controls to edit an existing trigger category FR_006MTT shall have the controls to add a new trigger FR_007MTT shall have the controls to delete an existing trigger FR_008MTT shall have the controls to edit an existing trigger FR_009MTT shall display a list of selectable symptoms FR_010MTT shall have the controls to add a new symptom FR_011MTT shall have the controls to delete a symptom MTT: My Trigger Tracker
Software Functional Requirements (cont.) UNIQUE IDDESCRIPTION FR_012 When a trigger or symptom is recorded, MTT shall save the date of the entry FR_013 When a trigger or symptom is recorded, MTT shall save the time of the entry FR_014 When a trigger or symptom is recorded, MTT shall save the optional text for the entry FR_015 When a symptom is recorded, MTT shall save an optional numerical value for the entry FR_016 MTT shall have the ability to graph logged trigger data FR_017 MTT shall have the ability to graph logged symptom data FR_018 MTT shall have the ability to generate a report of the history data
Software Non-Functional Requirements UNIQUE IDDESCRIPTION NFR_001 The MTT App shall work in the Android Operating System v 4.0 or later for Mobile Phones. NFR_002The MTT App shall be quickly understandable (the learning time should be very low). NFR_003The MTT Interface shall be simple and intuitive with large icons. NFR_004The navigation of the MTT interface shall be seamless and evident to all users. NFR_005Logging a Symptom and/or Trigger shall be quick with few steps. NFR_006Deleting a Symptom/Trigger shall be quick with few steps NFR_007History & Trend Reports shall be generated quickly. NFR_008History & Trend Reports shall be easy to read and understand. NFR_009The MTT App shall be customizable with User and Doctor Information. NFR_010The MTT App shall accurately record & retrieve Symptom & Trigger Data.
MOCKUPS The Smartphone App designed to help take control of one’s illness
Home Screen The MTT Home Screen provides an easy & intuitive interface that is self evident at the very first glance. Touch the Symptom icon to log an illness Symptom e.g. Headache, Heartburn, upset stomach etc. Touch the Trigger icon to log a Trigger Event e.g. meals, medication, stress level, physical activity, etc. Touch the Reports icon to review historical data. Touch the settings icon to configure/customize the app.
Logging a Symptom The MTT Symptom Screen provides an easy & intuitive interface to quickly log a health related symptom. Select from a predefined list of Symptoms or add a new one, on the fly. Record the severity level of your complaint, on a customizable scale. Every entry is automatically time stamped. Optionally you can set the date and time, if you need to log a symptom that happened previously.
Logging a Trigger The MTT Trigger Screen provides an easy & intuitive interface to quickly log a Lifestyle event that is potentially a Trigger for your symptoms. Select from a predefined list of Type of Trigger such as Food, Exercise, Drink etc. or add a new one, on the fly. Select from a predefined list of Triggers for your selected category, such as Chocolate under Food or add a new one, on the fly. Every entry is automatically time stamped. Optionally you can set the date and time, if you need to log a trigger from a previous time.
Reports - Trend The Trend Reports Screen Displays the Trend and Correlation between trends and symptoms for a selectable date range. You can also upload the report to your Google Drive. On this screen is a sample Trends Report that reveals the following facts: The User Has a correlation between eating chocolate and experiencing heartburn. A correlation exists between the number of times the user eats chocolate and the intensity of their heartburn. There is no correlation between the user’s coffee drinking habits and them experiencing heartburn.
Reports - History The History Reports Screen Displays the History of Tracked Triggers & Events for a selectable date range. You can also upload the report to your Google Drive. On this screen is a sample History Report that details lists in detail the time of all the user’s tracked and logged activities (triggers) and any symptoms the user experienced. This can be particularly useful for a doctor to diagnose a chronic illness, maybe avoiding expensive diagnostics tests.
Settings Screen The settings screen allows the user the customize different aspects of Trigger and Symptom data, for example defining categories of Trigger or Severity levels for Symptoms. Reports can also be formatted from here. Simple maintenance tasks, such as backing up the data – useful to migrate to a different phone and/or resetting the App data can also be performed here.
Scene 1: Family at the Dinner Table Son: Why aren’t you eating dad? Dad: I’m again not feeling well… Son: What’s troubling you? Dad: It’s that uncomfortable feeling in the stomach, and subtle pain in the upper abdomen, again. Son: Again! Has this been going on for sometime?
Dad: Yes, it happened twice last week. Son: What have you been eating dad? What did you eat for lunch today? Dad: Here… I have everything logged into “My Trigger Tracker”! Son: I see, you are probably having heartburn and you ate chocolate again! just take some antacid – that’s what the Dr. gave you last time!
Scene 2: Dad at Doctor’s Office Doctor: Hello Mr.H. Good to see you! You haven’t been here in a while! Dad: Yes, I am here just for my annual physical. Doctor: So... You are not having the frequent heartburn or stomach ache any more? Dad: Now that I keep track of all my symptoms and triggers, I able to avoid things like chocolate and overall feel a lot better.
Dad: Here, I actually brought a printout of the complete history for the last 6 months. This App “My Trigger Tracker” has literally changed my life! Doctor: Wow Mr. H! This is awesome! What was the name of the app again? I will tell my other patients to start using this. Btw, What kind of phone do I need to run this App? Any Android phone released after 2012 will work!
Life after “My Trigger Tracker” Most of Dad’s Chronic Conditions are under control with a few lifestyle changes. Family time is so much more fun! Mom has switched from iPhone to an Android phone, so that she can use
Handling Change Based on the analysis of our established Requirements and the associated difficulty, we expect to be able to handle a 5.5% change with the current manpower & time.
Why team CodeEx? We clearly identified a problem that our Product will solve. We followed the spiral model to identify the requirements. For a mobile platform, we focused on usability and understand-ability. We Our product has the potential to add true value to the user’s life. The App will be offered as a “Freemium” in the Google Play store.