Testing and quality assurance

TABLE OF CONTENTS

Table of Contents 1 Application overview 3 1.1 Objectives of the Study 4 1.1.1 General Objective 4 1.1.2 Specific Objectives 4 1.2 Assumptions for the project scope 4 1.3 Constraints for the project scope 4 1.4 Scope of the project 5 1.5 Target users 5 1.6 Research questions for the project 5 1.7 Information gathering 5 1.8 Functional requirements 6 1.9 Nonfunctional requirements 6

CHAPTER ONE

The app is a health management app that guides the user on healthy eating tips, work outs and gives statistics of the user lifestyle based on information the user feeds into the system. On installing the app, the user is required to provide their age, height, weight, gender and race. Based on this information the system does analytics and provides daily, weekly and monthly report of the user’s lifestyle in terms of exercising, how healthy their diet is and gives recommendation tips to improve on. The application will also be a source of user medical health information, where the user will be able to record any health incident indicating the how they feel, the meal they had taken or drink before the incident, the activity they were doing, date and time. Upon visiting a medical doctor the patient can easily refer to the application and give a medical history to the doctor without skipping necessary details. The system will also give alerts on upcoming health seminars near the user. The system will also provide daily health news on upcoming health diet, new work out exercises, medical research, medical breakthrough, health risks, and health warnings issued in case of disease out breaks. The system will also have the capability to remind the user to go for medical checkups through reminders. With lifestyle diseases such as cancer, it is recommended for men to go for check-up once in a year while for women twice in a year. The application will be able to give the user such reminders. The system will be able to learn user pattern over a period of time and can suggest to the user a certain food they take at a specific time or exercise.

The main objective of the project will be to create an application that can help users manage their health and keep a check on their lifestyle choices in terms of diet choices and exercising.

i. Collection of a user’s daily health lifestyle trend

ii. Provide analysis of individual’s health lifestyle

iii. Offer tips on improving individual’s health based on their health lifestyle.

iv. Act as an information tool to keep individual updated on upcoming health events.

v. Keep the user informed of developments in the health sector.

vi. Remind users to go for medical check-ups.

vii. Act as an information tool for a user’s medical history.

i. The user is willing to have their information stored by the application

ii. The user is ready to accept assistance in managing their health.

i. The application has focus on an individual’s health.

ii. The information collected by the application shall only be accessible to the user and only he can share the information at will.

The project will focus on how to better manage an individual’s health through mobile application.

The target users of the app are all smart phone users in the world. The health risks facing the world population increase on a daily basis due to poor lifestyle choices. The application is aimed to help individuals watch their health before a visit to the doctor forces them to do so.

i. How often do you exercise?

ii. What is your daily diet composition?

iii. How often do you go for medical check-ups?

iv. How regularly do you go for medical check-ups?

The researcher will use questionnaires as the main tool for collection of data. A questionnaire is a research instrument consisting of a series of questions and other prompts for the purpose of gathering information from respondents. A questionnaire is commonly used to obtain important information about the population. Each item in the questionnaire will be developed to address a specific objective, such that a research question or hypothesis providing the information required for the project. The questionnaire will be composed of structured (closed- ended) and unstructured (open – ended questions). Structured or close-ended questions will be the questions with a list of all possible alternatives from which respondents will select the answer that best describes the situation. Unstructured or open –ended questions are questions which give the respondent complete freedom of response. These free responses permit the respondent to answer in his/her own way. They allow great depth of response.

This are the requirement describing what the system should do. To elaborate upon registering on the app, where the user feeds in his/her personal information including age, weight, height, the system should give a breakdown of the user data such as users B.M.I. Throughout the day the user feeds the meals they have consumed and any exercises done during the day. The system should respond with an analysis of the user’s lifestyle for the day, providing suggestions on what to stop and what to increase. The system will provide health news to the user on a daily basis. The news will be alerts on upcoming health events around the user such as health seminars. Based on this information the system does analytics and provides daily, weekly and monthly report of the user’s lifestyle in terms of exercising, how healthy their diet is and gives recommendation tips to improve on. The application will also be a source of user medical health information, where the user will be able to record any health incident indicating the how they feel, the meal they had taken or drink before the incident, the activity they were doing, date and time. Upon visiting a medical doctor the patient can easily refer to the application and give a medical history to the doctor without skipping necessary details. The requirement shall be verified during functional and acceptance testing.

This are the requirements place constraint on how the system should be. They fall under usability, security, privacy, portability and stability. Under usability the app shall be easy to use with simple, easy to use and user friendly interface. The layout shall be self-explanatory in such a way that looking at a certain interface already tells you what it does. This shall be tested during usability and functional testing.

The application shall be secure using encryption to store user data on the device database. The information being entered by the user is very sensitive to the user and hence the information must be protected from unauthorized access. Even the user can not be able to access the database files on their own device. This shall be tested during functional testing.

The application shall ensure privacy of user data by requiring login password in order to access the application. This ensure that even when a user’s phone is accessed by another person without the password the live longer application cannot be accessed. This shall be tested during functional testing.

The application shall be stable with crush and lag being handled appropriately. In the event the application crushes may be due to slow network the application should redirect the user appropriately with appropriate error message. This shall be tested during performance and functional testing.

The application shall run on all android devices irrespective of size and operating system. This shall be tested during functional, system, performance and usability testing.

References

Fuggetta, A., & Di Nitto, E. (2014, May). Software process. In Proceedings of the on Future of Software Engineering (pp. 1-12). ACM.

Van Lamsweerde, A. (2009). Requirements engineering: From system goals to UML models to software (Vol. 10). Chichester, UK: John Wiley & Sons.

Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in software engineering (Vol. 5). Springer Science & Business Media.

Matthews, B., & Ross, L. (2014). Research methods. Pearson Higher Ed.

Loucopoulos, P., & Karakostas, V. (1995). System requirements engineering. McGraw-Hill, Inc..

Beizer, B. (1984). Software system testing and quality assurance. Van Nostrand Reinhold Co..