Medication & Appointments tracking application

Name ID
Abdullatif Alsuwaidan 161033
Ghnader Almea 161337
Mubarak Alhujilan 162026

Page 1 of 9
OUTLINE:

1. INTRODUCTION:
1.1- Need
1.2- Objective
1.3- Overview

2. REQUIREMENT SPECIFICATION:
2.1- Features
2.2- Non-Functional Requirements
2.2.1- Cost
2.2.2- Security
2.2.3- Social and Cultures
2.2.4- Useability
2.2.5- Availability
2.3- Functional Requirements
2.3.1- Enumerated Functional Requirement

3. DIAGRAM:

3.1- State Diagram

3.2- Activity Diagram
3.3- Use Case Diagram
3.4- Schema Diagram

Page 2 of 9
1. INTRODUCTION

This document will cover the medication and appointments tracking application. This

application will be designed and launched on both ios and Android systems. The application

will remind the patient that he/she took the medicine on time and the remaining amount of

medicine, as well as remind the regular appointments of the hospital visit.

The responsibilities of the stakeholders will be detailed in the stakeholders and user profiles

section. the application and its features will be explained by the State Diagram, Activity

Diagram, Use Case Diagram, Schema Diagram.

1.1- Need

The Medication and Appointments tracking application a highly needed app that will

help so many elderlies and patient to help them live a better life. It helps these segments to take

their medicine on time as it has a reminder feature to remind them of the proper times of taking

their medicine and reminding the patient before the medicine stock ends. Moreover, the

application reminds them of the proper times of visiting their respective clinics or hospital so

that they will not miss their appointments with the doctors. So, it is of crucial importance for

them.

1.2- Objective

Our objective is to assist patients and the elderly by reminding them to take their medications

on time, remind them before the prescription supply runs out, and by reminding them of

hospital review dates.

Page 3 of 9
1.3- Overview

The requirements and high-level design document have three sections, the first being

the introduction which includes the need, the objective and Stakeholder and User Profiles, the

second section which includes the requirement specifications, and the third section that

includes the diagrams.

2. REQUIREMENT SPECIFICATIN

The Medication and appointment tracking application works to remind the user of their

appointment and notify them both when to take their medications and when to attend

appointments and even show nearby hospitals and pharmacies for emergence conditions.

2.1- Features

• The application will remind the patient to take the medicine on time.

• It should notify user of appointments.

• It should notify the user before stock of medicine finished.

• It should show the medications you use.

2.2- Non-Functional Requirements

This section describes the limitations that should be considered while implementing the

application to meet the desired needs. Those constraints include: Cost, Security, social and

cultural, Usability, and Availability.

2.2-1. Cost

REQ-1: The total cost of developing and publishing the application is between $4000-$7000.

2.2-2. Security

Page 4 of 9
REQ-2: The patient must be required to verify their identity via a personal log-in or PIN in

order to access the application.

2.2-3. Social and Cultures

REQ-3: The application support both English and Arabic languages.

2.2-4. Useability

REQ-4: The app should use simple screen layouts designed for readability and ease of access.

2.2-5. Availability

REQ-5: The application shall available on both ios and Android systems.

2.3- Functional Requirements

2.3.1- Enumerated Functional Requirements

The functional requirements outlined below justify the most critical technical

requirements of our system. They provide the system with the specific functionalities that it is

supposed to perform.

REQ-6: The application shall set reminders for appointments and when to take medicine.

REQ-7: The application shall calculate the total number of drugs left by your usage to

determine whether you need a new packet or not.

REQ-8: The application shall set reminders for take medicine on time and hospital review

appointment.

REQ-9: The application shall show location for nearby hospital and pharmacies for emergency.

REQ-10: The application shall require patient to login using their username and password to

be able to use all features.

Page 5 of 9
3. DIAGRAM

3.1- State Diagram

3.2- Activity Diagram

Page 6 of 9
3.3- Use Case Diagram

Page 7 of 9
3.4- Schema Diagram

Page 8 of 9
 Recourses:

1- Software Engineering (Writing Requirements), Lab Assignment 7, KCST.

2- System Analysis and Design with UML version2, 4th Edition.
3- Write a Software Requirements Specification (SRS Document), perforce.com.

Page 9 of 9