TABLE OF CONTENTS - Kutztown University of Pennsylvaniafaculty.kutztown.edu/tan/csc354/Datafiles/TechnicalDocs/... · 2018-09-17 · table of contents t a b l e o f c o n t e n t

1 1

TABLE OF CONTENTS

TABLE OF CONTENTS 2

ACRONYMS AND GLOSSARY 4

1.0 INTRODUCTION 5 1.1 PURPOSE OF DOCUMENT 5 1.2 HIGH LEVEL PRODUCT OVERVIEW 6

2.0 PROJECT CONSIDERATIONS 7 2.1 IDENTIFIED RESOURCES 7 2.2 POSSIBLE TOOLS 8 2.3 OPEN ISSUES AND QUESTIONS 9 2.4 LONG-TERM PLANS FOR FUTURE RELEASES AND FEATURES 9

3.0 PROJECT SCOPE 10 3.1 SYSTEM ARCHITECTURE DIAGRAM 11

4.0 HARDWARE PERSPECTIVE 12 4.1 TOOLS 12 4.2 HARDWARE STRUCTURE DIAGRAM AND DESCRIPTION 12

5.0 USER PERSPECTIVE 13 BROWSER VERSION 14 APP VERSION (MOBILE) 15 APP VERSION(TABLET) 15

5.1 USER PROFILE 16 BROWSER VERSION 16 APP VERSION (MOBILE) 17 APP VERSION(TABLET) 17

5.2 USER INTERFACE MAP 18 BROWSER VERSION 18 APP VERSION(MOBILE) 19 APP VERSION(TABLET) 20

6.0 FUNCTIONAL REQUIREMENTS 21 BROWSER VERSION 21

2

APP VERSION(MOBILE) 26 APP VERSION(TABLET) 29

6.1 DATABASE 30 BROWSER VERSION 30 APP VERSION (MOBILE) 31 APP VERSION (TABLET) 32

7.0 NON-FUNCTIONAL REQUIREMENTS 34 BROWSER VERSION 34 APP VERSION(MOBILE) 35 APP VERSION(TABLET) 36

8.0 USE CASE DIAGRAM 37 BROWSER VERSION 38 APP VERSION(MOBILE) 39 APP VERSION(TABLET) 40

9.0 USE CASE DESCRIPTIONS 41 BROWSER VERSION 41

FULLY DEVELOPED USE CASE DESCRIPTION: CREATE A TASK INSTRUCTION 41 FULLY DEVELOPED USE CASE DESCRIPTION: CREATE PORTFOLIO 43

APP VERSION(MOBILE) 44 FULLY DEVELOPED USE CASE DESCRIPTION: VIEW TASK INSTRUCTION 44

APP VERSION(TABLET) 46 FULLY DEVELOPED USE CASE DESCRIPTION: UPDATE PATIENT’S VITAL STATUS 46

3

ACRONYMS AND GLOSSARY

The following are acronyms and glossary explaining words used throughout the document.

Table AB_0-1: Acronyms & Glossary

Acronyms & Glossary Full Name and Explanation

AC Applied Computing

AI Artificial Intelligence

CNA Certified Nursing Assistant

CNO Chief Nursing Officer

LTC-TMS Long-Term Care-Task Management System

MCU Ming Chuan University

TMS Task Management System

UML Unified Modeling Language

Director Director of Nursing

Staff Include all the actors working at long-term care center in LTC-TMS (CNA, CNO and Director)

Family patient’s family or relatives, also the user of the app version of LTC-TMS

Patient patients who are in long-term care center

App(Mobile) Users CNA and Family

App(Tablet) User CNA

Browser Users Director and CNO

4

1.0 INTRODUCTION

1.1 Purpose of Document

This Software Requirements Specification document outlines the way that Long-Term Care-Task Management System(LTC-TMS) is intended to work by using detailed descriptions of the requirements.

Section 2.0 details the identified resources, required tools for future development. Unresolved issues will be addressed in Section 2.3(Open Issues and Questions) which will be updated as the project proceeds.

Section 3.0 provides project scope and system architecture diagram. Project scope delivers the development team’s goals and function changes from TMS to LTC-TMS v1.1. System architecture diagram describes the overall system flow.

Section 4.0 includes the hardware tools, hardware structure diagram and description. There details the description of the communication between hardwares and the features of each hardware.

Section 5.0 provides the user profile, user interface map and functionalities that application will need in order to work, from a user’s perspective.

Section 6.0 describes the functional requirements as well as services offered by LTC-TMS. For example, the task instructions should be simple to use for CNA/Family and should guide them through each step. This section will also outline the perspectives of Browser users, Director/CNO, App(Mobile) users, CNA/Family, and App(Tablet) user, CNA, about the system.

Section 7.0 includes Non-functional Requirements, which are the Quality Attributes that will be tracked during the project, including usability testing, responsiveness, and compatibility. The purpose of the non-functional requirements is to improve the services provided and encourage adoption by users.

Section 8.0 and 9.0 outlines Use Cases from the perspective of Browser, App(Mobile), and App(Tablet) users. The Use Cases correspond to the Functional Requirements from Section 4.0. Their purpose is to provide a clear picture of the requirements for each action users may perform while using the app.

5

1.2 High Level Product Overview

High Level Product overview consist of two parts: Browser Overview:

● Capable of creating and modifying task instruction, announcement and event ● Capable of creating memo ● Capable of retrieving daily status record, vital status record and AI status record ● Director takes up the responsibility of the CNO if he/she is not available ● Designed purposely to be used by the Director and CNO only ● The Director is the only one given the privilege to create and modify portfolio. ● The Director is the only one given the privilege to create the accounts. ● The CNO create and modify task instructions for use by CNA and Family. ● Medical data is key-in by Director.

App(Mobile) Overview:

● CNA and Family can view task instruction. ● Family can get daily status record, vital status record, and AI status record of the

patient. ● Family can only view the patient's portfolio while CNA can only view their own

portfolio. ● Both Family and CNA cannot create or modify portfolio, and task instruction. ● Both Family and CNA can input feedback. ● All data accessed are acquired from the database.

App(Tablet) Overview:

● CNA can input daily status and vital status of patients. ● CNA can view AI status of patients.

6

Hardware Overview:

● A micro bit bracelet are designed for patients to wear as to retrieve real time data of a patients(e.g. position, steps, heartbeat rate) through radio frequency.

● Another micro bit will be attached to a Raspberry Pi (through serial port e.g. USB) composed into a RF(Radio Frequency) reader and install at every section into LTC center.

● The Raspberry Pi would send the data to database by WIFI once it received the data.

2.0 PROJECT CONSIDERATIONS Below is a lists of all the resources and tools, along with the issues and future updates

of the LTC-TMS. The project is limited to this scope unless otherwise decided by the team. Every new addition is always agree upon by both the browser and app team.

2.1 Identified Resources

The following list of resources is what the MCU-AC department will be utilising during design and development.

● International college’s Applied Computing iCube(lab) ● A Sony Xperia Tablet Z with Android 4.1.2 ● An iPad with iOS 9.3.5 ● One breadboard connection line package ● Two Raspberry Pi accessories T-GPIO expansion board T-Cobbler plus + 40p

rainbow cable + 400 hole breadboard packages ● Two Sharp GP2Y1014AU PM2.5/dust/air quality sensors ● Two DHT11 temperature and humidity sensors ● Two MCP3008 convertors ● Two Grove shield for micro:bit ● Two Grove finger clip heart rate sensors with shell

The following list will be the existing resources that YSTEL technology company provides during design and development.

● Two Raspberry Pi 3 Model B (Including Memory Card 16G + Shell + Power cable) ● Four Micro:bit (Including Micro USB + Power set)

7

2.2 Possible Tools

Below are all the lists of the required tools and mediums that facilitate and enhance the smoothness of LTC-TMS project.

● Firebase Real-Time Database ● Firebase cloud server ● Text Editor:

- Atom (JavaScript, Html, CSS) - Google Editey (Html,CSS) - IDLE (Python 3.6.4) - App Inventor 2 (JavaScript) - Swift (Xcode) - JavaScript Blocks Editor - Mu Python - JSON editor

● Communication:

- Line (texting) ● Code Repository:

- Github ● Video Meetings:

- Skype - Google Hangouts

● File Sharing: - Google Drive

● Media used: - Youtube - Google search

8

2.3 Open Issues and Questions

The first possible issue that will be encountered by the users of the LTC-TMS will be the traditional difference in the work field. At the moment, CNA are much more familiar and comfortable using paperwork while executing their duties. However, CNA will need to adapt to the changing environment by using a digital system for their work. However, it is uncertain whether the change to using digital device will affect and reduce their working efficiency.

Also, there are issues and concerns whether LTC-TMS consists of all the necessary functions that a Care Center would need at the moment. This might raise questions as to the effectiveness and usefulness of the functions that LTC-TMS will provide.

2.4 Long-Term Plans for Future Releases and Features

This system is intended to support the LTC center in their daily work. Considering the system is created successfully, developers are expected to accomplish the following functions:

● To allow functions in LTC-TMS to expand(e.g. Input new data through app, more sensors, self-calculating for statistic data)

● Easily accessible by users (Provide Artificial Intelligent supports) ● Featuring voice to text function ● Provide more languages

9

3.0 PROJECT SCOPE The LTC-TMS tends to reduce long-term care center staff’s paperwork, digitize data,

increase data retrieving efficiency, efficient hierarchy communication, and increase productivity. Also for Family to check the patient’s status more convenience.

To achieve these goals, the development team firstly decided to implement hardwares to receive datas automatically instead of manually key-in by CNA. Secondly, the development team decided to develop an tablet app version for CNA to achieve the goals of checking and key-in the patient’s status anytime at the ward. Thirdly, there is one more application would be developed for both CNA and Family, where Family could check the patient’s status and CNA could check the working hour and working schedule. Both of the user could check center schedule, announcement, task instruction and input feedback. Fourthly, browser version are intended to provide Website application for Director and CNO in the Long-term Center. The web-application would provide platform for Director and CNO to monitorize and utilize the condition of the center through the information system.

To conclude, the new functions for LTC-TMS v1.1 are listed below.

● Available for more devices and browsers (Android, IOS, Chrome) ● Provide bi-languages (English, Chinese) ● Provide CNO personal Memo ● Provide CNO and Director monitoring(Status Record) ● Provide staff and patient portfolio ● Provide two Android and IOS mobile app ● Provide one Android tablet app ● Provide Family and CNA monitoring (Status Record) ● Provide CNA input status record ● Provide center schedule and announcement ● Provide CNA working schedule and working hours ● Provide App(Mobile) users feedback platform ● Provide auto-measurement through sensors

10

3.1 System Architecture Diagram

To begin with the tools the development team use in this system. Firstly, the hardwares include raspberry pi, micro:bit, heart beat rate sensor, air quality sensor, and temperature and humidity sensor. Secondly, the server and database are firebase. Firebase provides both server and database service. Lastly, the PC, mobile, and tablet provide for the end users.

The following diagram shows the communication between the devices’ and hardwares’ data binding with the servers, and the database. The initial request sent from the user’s end device through web application. Server receives the request and interacts with the database developed by using JavaScript. On the other hand, server of app version(mobile and tablet) are developed using App Inventor 2 and Swift. The database will respond to the request from the server by retrieving the proper data. In addition, the hardware would send the data to database through WIFI automatically once it got data. To conclude, the data flow would be hardware to database to end users.

Figure AB_1-1: System Architecture Diagram

11

4.0 HARDWARE PERSPECTIVE 4.1 Tools

● Two Raspberry Pi 3 Model B (Including Memory Card 16G + Shell + Power cable) ● Four Micro:bit (Including Micro USB + Power set) ● Two Sharp GP2Y1014AU PM2.5/dust/air quality sensors ● Two DHT11 temperature and humidity sensors ● Two MCP3008 convertors ● Two Grove shield for micro:bit ● Two Grove finger clip heart rate sensors with shell ● Two Raspberry Pi accessories T-GPIO expansion board T-Cobbler plus + 40p

rainbow cable + 400 hole breadboard packages ● One breadboard connection line package

4.2 Hardware Structure Diagram And Description

Figure AB_1-2: Hardware Structure of LTC-TMS

12

The following is the description of the above diagram: The right side is the sender and plays the slave role, the development team would

make the heart beat rate sensor and micro:bit together like a bracelet for patient to wear. Sensor will send data to micro:bit by I2C then micro:bit send to the middle side’s micro:bit by radio frequency. The micro:bit includes G sensor and radio frequency. So in this part the data which will be sending includes step count, position and heart beat rate. The middle side is the receiver and plays the master role, the micro:bit would receive data from slave micro:bit and send to raspberry pi by USB, the temperature and humidity sensor and air quality sensors will send data to raspberry pi by I2C. Raspberry pi will send data to firebase by WIFI once it got data. The whole master set will be set in each ward in the long-term care center. Thus, wherever a patient make a movement, the data would continue to receive accurately.

The left side is the database. Once database got the data, it could provide all the data to the end users of browser, mobile app and tablet app.

5.0 USER PERSPECTIVE

The following lists the services provided by the LTC-TMS through the perspective of browser version users (Director/CNO), app version(mobile) users (CNA/Family), and app version(tablet) user (CNA). These are outline in accordance to how they interact with the system while executing their duties.

13

Browser Version Director Perspective:

The Development team will be responsible for giving the Director the ability to access the LTC-TMS browser system while giving the following services:

● View daily status record ● View vital status record ● View AI status record ● View feedback ● Create accounts (Both browser and app users) ● Create and Edit portfolio ● Create and Edit announcement ● Create and Edit event ● Create and Edit task Instruction ● Create and Edit memo ● Assign task instruction ● Upload and Delete working schedule ● Upload and Delete working hour

CNO Perspective:

The CNO is given the privilege to perform and use the following services from LTC-TMS:

● View portfolio ● View daily status record ● View vital status record ● View AI status record ● View feedback ● Create and Edit announcement ● Create and Edit event ● Create and Edit task instruction ● Create memo ● Assign task instruction ● Upload and Delete working schedule ● Upload and Delete working hour

14

APP Version (Mobile)

CNA Perspective:

The CNA receives information from database, and view and send information by utilizing the following services:

● View task instruction ● View CNA portfolio ● View announcement ● View center schedule ● View working hour data ● View working schedule ● Input feedback

Family Perspective:

A Family receives information from database, and view and send information by utilizing the following services:

● View daily status record ● View vital status record ● View AI status record ● View task instruction ● View patient portfolio ● View announcement ● View center schedule ● Input feedback

APP Version(Tablet) CNA Perspective:

The CNA receives information from database, and view and send information by utilizing the following services:

● View AI status record ● Input daily status record ● Input vital status record

15

5.1 User Profile Browser version of LTC-TMS is intended for two main groups of Users (Director and

CNO). In addition, the mobile app version of LTC-TMS is intended for CNA and Family. Besides, the app version(tablet) of LTC-TMS is only for CNA to use as a workstation. However, it is expected that a user might be less likely to be skilled and required more time adapting to the application even with the required training. In order to appropriately fulfill the needs of the users, the application’s design will be simplified.

Browser Version

LTC-TMS browser version is intended for Director and CNO to work on. The Director and CNO will focus more on inputting information into the system for view. Both Director and CNO will mainly have similar functions regarding the use of the LTC-TMS browser version. However, CNO is given most of the privilege to work on the system on a daily basis. The Director will act in place of the CNO to perform most of the functions only if the CNO is not available. (For example, CNO will make use of the function “create a new announcement” on a daily basis. However if the CNO is not available, Director will make use of the function to create a new announcement instead). Also the major difference between the Director and CNO is that the Director is given the authority to create and edit information in the portfolio, CNO is only given the authority to view an existing portfolio. Director:

Will mainly be able to create and edit portfolios. They will input all the personal information for both staff and patients separately according to the designed format. Besides, within the portfolio page, Director are able to create an account for each staff and patient. Moreover, a Director is allowed to create and edit announcement and task instructions. In addition, is also allowed to assign task instruction to a specific group or individuals. In addition, Director is allowed to review the feedback/suggestion from App users (CNA and Family). However, as mentioned above, Director would only input information when the need arise. Thus, given the highest authority in the LTC-TMS. However, Director is limited to his/her personal account. Director are not allowed to access CNO account. Lastly, Director must be able to have basic knowledge on computer skill set such as typing, uploading files, using web browser and understanding on the LTC-TMS browser version capability. CNO:

The CNO is not able to create or edit any portfolio. He/she is only given the authority to view portfolio. CNO will be able to create and edit announcement and task instructions. In addition, they are able to assign the task instruction too. In addition, during assigning task instructions CNO are allowed to distribute to a specific users such as a group of CNA/Family or individuals. Nonetheless, CNO are also allowed to view the feedback/suggestion from App users. However, CNO is not allowed to access Director’s account. Furthermore, CNO must have the basic knowledge about computer skills such as accessing into browsers, typing, uploading files from the computer and knowing and understanding the browser interface of LTC-TMS.

16


The users of LTC-TMS app version(mobile) is intended for two main users( Family and CNA). Family and CNA will generally have a similar function while using the app. However, it is expected that patient’s Family will be more comfortable to check on the patient status while CNA are capable to do efficient checking on the informations of their job. Furthermore, CNA and Family both are allowed to input feedback on app. Family:

Are able to view the patient’s status, patient’s portfolio, task instruction, announcement and center schedule and input feedback. Besides, the task instruction is utilized to conduct learning session as if the Family are unfamiliar with some emergency work procedure. However, Family should be able to adapt on how to use a mobile devices with different operating system based on what they currently use in the center.

CNA:

Are able to view their own portfolio, task instruction, announcement and center schedule and input feedback. In addition they could view working hours and working schedule. Moreover, CNA should be able to adapt on how to use a mobile devices with different operating system based on what they currently have available.

APP Version(Tablet)

The only users of LTC-TMS app version(tablet) is a CNA. A CNA will experience a similar function while using the tablet’s app. However, it is expected that CNA will be more convenient and efficient to do check up and input the patient status.

CNA:

Are able to input patients’ daily and vital status record. In addition, a CNA is also able view AI status record. Furthermore, a CNA should be able to understand how to use a tablet devices with different operating system based on what is currently available.

17

5.2 User Interface Map

Browser Version

The following Figure B_1-1 displays the user interface map of the LTC-TMS browser version. The box describes the web-page designed while the arrows illustrates the menu path throughout the application. Basically in this diagram, it shows the interconnection between different screens in the browser version.

Figure B_1-1: User-Interface Map of LTC-TMS

18

APP Version(Mobile)

Figure A_1-1 and Figure A_1-2 displays the user interface map of the LTC-TMS application. The detailed diagram exemplifies the boxes as screens and the thin black arrows illustrates the menu path throughout the application. The big hollow white arrow gives a statement of the respective screen or screens it is pointing towards. Generally, this diagram shows the interconnection between different screens in the application.

Figure A_1-1: User-Interface Map of LTC-TMS (Mobile)

19

APP Version(Tablet)

Figure A_1-2: User-Interface Map of LTC-TMS (Tablet)

20

6.0 FUNCTIONAL REQUIREMENTS The following tables present a listing of the functional requirements for this

application. The functional requirements are listed for each version by Category, Requirement ID, Requirement, Description, and finally Priority (1 has to be in LTC-TMS and 3 being not as important, but nice to have).

Browser Version

Table B_1-1: Functional Requirements of LTC-TMS Browser version

Category Requirement

ID Requirement Description Priority

Create and Edit Portfolio

1 Director must be able to create portfolio.

When a new staff/patient join the care center, Director should be able to create Portfolio.

1

2 Director must be able to edit existing portfolio.

When a patient/staff changes their information, Director should be able to edit the Portfolio.

1

3 Director must be able to view an existing portfolio.

When Director demand to view portfolio, Director should be able to review staff’s/patient’s Portfolio.

2

4 Director must be able to embed picture(s) into the portfolio.

Given that a new staff/patient join the care center, Director must upload the person’s picture.

1

5 Director must be able to upload portfolio.

When Director finishes typing in to create/edit a patient or staff Portfolio, Director should be able to upload the updated Portfolio.

1

6 CNO must be able to view an existing portfolio.

Given that CNO has a demand on a person information, CNO should be able to review existing staff/patient Portfolio.

2

7 Director must be able to remove an existing portfolio.

When a staff/patient quits the care center, Director should be able to remove an existing portfolio.

1

21



Create and Edit Announcement

8 Director/CNO must be able to create Announcement.

Given that a news needed to be delivered, Director and CNO must be able to create new Announcement.

1

9 Director/CNO must be able to edit existing Announcement.

Given there is an error in the published announcement, Director and CNO must be able to edit an Announcement.

1

10 Director/CNO must be able to delete existing Announcement.

Given there is an unwanted announcement, Director and CNO must be able to delete an Announcement.

1

Create and Edit Memo

11 Director/CNO must be able to insert Memo.

Inserting Memo for Director’s/CNO’s personal reminders and work logging.

1

12 Director/CNO must be able to edit Memo.

Editing Memo for changes made from Director’s/CNO’s personal reminders and work logging.

1

13 Director/CNO must be able to delete Memo.

Deleting Memo allows Director/CNO to delete unwanted Memo.

1

View Status Record

14

Director/CNO must be able to view daily status record, vital status record and AI status record.

After CNA have submitted patients daily and vital status record of the day, Director and CNO must be able to view the daily and vital status record.

1

15 Director/CNO must be able to select a group of patients filtered by room numbers.

When Director/CNO have to input the daily status and vital status records, Director and CNO must be able to find every patient’s name list according to room number. Thus, they could work on the checkbox.

2

22



Create and Edit Event

16 Director/CNO must be able to create event.

When there is a new event for the care center, Director and CNO must be able to create a new event

1

16 Director/CNO must be able to edit event.

When an event is inaccurate, Director/CNO must be able to edit an event.

1

17 Director/CNO must be able to key in event’s date.

After an event is created, Director/CNO must be able to set event’s date.

1

18 Director/CNO must be able to edit event’s date.

When there is an error in the date of an event, Director and CNO must be able to edit the event’s date.

1

19 Director/CNO must be able to delete Event

When an event is expired or invalid, Director and CNO must be able to delete an existing event.

1

Upload Work Schedule and Working Hour

20 Director/CNO must be able to upload file(s)

After a file of work schedule has been created, Director and CNO must be able to upload the file.

1

21 Director/CNO must be able to delete uploaded file(s).

After file expired/out of date, Director/CNO are allow to remove the file from the website.

1

23



Create and Edit Task Instruction

22 Director/CNO must be able to create Task Instruction.

When a lesson or command needed to be delivered, Director and CNO must be able to create new task instruction.

1

23 Director/CNO must be able to add main steps to a task.

After a task has been created, Director and CNO must be able to add main step to a certain task when needed.

1

24 Director/CNO must be able to add detail steps to a task.

After a main step have been created, Director and CNO must be able to add a detail step to each main step correspondingly.

1

25 Director/CNO must be able to remove task instruction.

Given that a task instruction is useless, Director and CNO should be able to remove task instruction.

1

26 Director/CNO must be able to remove main steps from a Task instruction.

When a main step is inaccurate, Director and CNO should be able to delete that main step.

1

27 Director/CNO must be able to remove detail steps from a task instruction.

When a detail step is inaccurate and wished to be removed, Director and CNO must be able to delete a detail step.

1

28 Director/CNO must be able to embed image(s) into a task instruction.

Given that a step requires an image to explain, Director and CNO must be able to upload an image when necessary.

2

29 Director/CNO must be able to embed videos into a task instruction.

Given that the steps required a demonstation, Director and CNO should be able to upload videos.

3

30 Director/CNO must be able to access task instruction from database.

When Director/CNO wishes to edit task instruction, Director and CNO must be able to retrieve task instruction data from database.

1

31 Director/CNO must be able to edit task.

When Task information is inaccurate, Director/CNO should be able to change a task information.

1

24



Create and Edit Task Instruction

32 Director/CNO must be able to edit main steps.

Given that there are mistakes in main step, Director/CNO should be able to modify the main step information.

1

33 Director/CNO must be able to edit detail steps.

When a detail step of a task is inaccurate/invalid, Director/CNO must be able to edit the detail step

2

Assign Task Instruction

Status

34 Director/CNO must be able to alter task visible/invisible status.

In case Director/CNO does not wish to publish a task instruction, Director and CNO must be able to switch a task instruction to invisible and vice versa.

2

35

Director/CNO must be able to distribute task instruction to a specific groups or individuals.

Director/CNO wishes to send a task instruction to a specific group of users/individuals.

2

View Task Library

36 Director/CNO must be able to view Task Library.

After Director/CNO completed the task instruction and demands on reviewing, Director and CNO should be able to review task instruction from the task library.

2

Login 37 Director/CNO must be able to log in with the provided account.

Director/CNO with an account must be able to login.

1

Query Function 38 Director/CNO is able to search for information using keyword.

Director/CNO is able to search for information by inserting keyword on the query function

3

Voice Output 39

Director/CNO is able to listen to the information when click on the sound icon.

Director/CNO is able to listen to a voice version of the information when click on the sound icon.

3

Scan QR Code 40 User is able to scan QR code from the home page.

User is able to scan QR code from the home page to go to the app version of LTC-TMS in both English and Chinese version.

2

View Help and Support

41 Director/CNO is able to view the help and support page.

Director/CNO is able to view the help and support page when they want to view comments and suggestions from users.

2

25

APP Version(Mobile)

Table A_1-1: Functional Requirements of LTC-TMS App version(Mobile)



User Log-in

1 A Family/CNA must be able to login into the system.

Family/CNA will be provided with default login info which can be changed to enable secure login.

1

Tasks

Instruction Viewing

2 A Family/CNA must be able to select the instruction type.

All task instructions are created from the browser page and this enables a Family/CNA to select the instruction type.

1

3 A Family/CNA must be able to view the page of tasks instruction list.

System will list out task instruction viewing in the page.

1

4 A Family/CNA must be able to view tasks instruction.

A task instruction is composed with text, video and into a pdf file.

1

Daily Status Record

Viewing

5 A Family/CNA must be able to view Daily Status Record page

Users are able to select “Daily Status Record” at hamburger menu page.

1

6 A Family must be able to access a Status Record page by date.

In the page, users need to select a date in order to let the app to show the status record data for the selected date.

1

7 A Family/CNA must be able to view status record with a selected date.

After users select a date, status record data will be shown to Family.

1

26



Announcement board

Viewing 9

A Family/CNA must be able to enter home page and view the announcement board.

App will retrieve announcement board information from the database that is created in the LTC-TMS browser version.

1

Portfolio Viewing

10 A Family/CNA must be able to enter and view portfolio page.

App will retrieve portfolio information from the database stored using the LTC-TMS browser version for view by a CNA for each patient the need arise for view but can’t modify while Family can only view their patient’s only.

1

Center schedule Viewing

11 A CNA must be able to enter home page and view schedule.

Home page will show a simple table that include events for 5 day(past 2 days/today/next 2 days).

1

12 A CNA must be able to view all the center schedules for the month.

If a CNA click on the Center schedule on home page, the app will direct to another page with a calendar for the month. Users can switch to different months for the center schedule.

1

Working schedule Viewing

13 A CNA must be able to view working schedule for the month.

CNA can select work schedule in menu page, the app will direct to working schedule page, which allow CNA to switch months and view data.

1

Working hour data

Viewing 14

A CNA must be able to view the number of hours they work for the month.

CNA can select work schedule in menu page, the app will direct to working hour page, and also allow CNA to switch months and view data.

1

Feedback Sending

15 A Family/CNA must be able to send feedback.

Family/CNA is able to submit the feedback to the database which is also forwarded to CNO/Director.

1

16 A Family/CNA’s ID must be captured along with the feedback sent back.

Each feedback is entitled to a user, for CNO/Director to locate and reply the user.

1

Voice Output 17

A Family/CNA is able to listen to the information when click on the sound icon as voice.

Family/CNA is able to listen to a voice version of the information when click on the sound icon.

3

27

APP Version(Tablet)

Table A_1-2: Functional Requirements of LTC-TMS App version (Tablet)



patient from a room selection

1 A CNA must be able to select a patient from the room.

When the CNA initiate the tablet version, he/she needs to select a patient from a room in order to update the selected patient’s status.

1

Daily Status Updating

2 A CNA must be able to select the checkboxes provided.

The checkboxes on the tablet version help the CNA to validate status of a patient.

1

3 A CNA must be able to input data.

The CNA needs to be able to fill in data to the fields provided on the tablet version.

1

4

A CNA must be able to sign his/her name before submitting the data to the database.

Each batch of data submitted to the database is entitled with the CNA in charge.

1

5 A CNA must be able to receive the confirmation of the data entered.

Before the data being stored in the database, the CNA receives the pop-up confirmation dialogue to ensure the correctness of the inputted data.

1

Vital Status Updating

6 A CNA must be able to update vital status hence the privilege to input data.

The CNA needs to be able to fill in data to the fields provided on the tablet version.

1

7

A CNA must be able to sign his/her name before submitting the data to the database.

Each batch of data submitted to the database is entitled with the CNA in charge.

1

8 A CNA must be able to receive the confirmation of the data entered.

Before the data is stored in the database, the CNA receives a pop-up confirmation dialogue to ensure the correctness of the inputted data.

1

AI Status Viewing

9 A CNA is able to view the patient’s automated recorded status.

There are sensors placed in the center as well as on the patient’s wearables, the CNA are able to view the collected data of the patient which is organized and displayed on the tablet version.

1

28

6.1 Database

The below Table B_1-2, Table A_1-3 and Table A_1-4 lists the functional requirement that must be met by the database.

Browser Version

Table B_1-2: Lists of Database Functional Requirement

V/X Requirement Description Implementation

Create Portfolio Allow Director to create new portfolio for new staff and patient.

Remove Portfolio Allow Director to remove existing portfolio.

Edit Portfolio Allow Diretor to change information from the existing portfolio.

Upload Photo Allow Director to upload photo into the portfolio.

View Portfolio Allow CNO to view the existing Portfolio.

Create Announcement

Allow Director/CNO to create new announcement.

Remove Announcement

Allow Director/CNO to remove existing announcement.

Edit Announcement

Allow Director/CNO to update the existing announcement.

View Announcement

Allow Director/CNO to view the existing announcement.

Create Task Instruction

Allow Director/CNO to create task instruction.

Remove Task Instruction

Allow Director/CNO to remove task instruction.

Edit Task Instruction

Allow Director/CNO to update information in the task instruction.

Add main step Allow Director/CNO to add main step to a task instruction.

29


Remove main step Allow Director/CNO to remove main step from the task instruction.

Edit main step Allow Director/CNO to update information in the main step.

Add detail step Allow Director/CNO to add detail step from task instruction.

Remove detail step Allow Director/CNO to remove the detail step from task instruction.

Edit detail step Allow Director/CNO to change information in the detail step.

Add image Allow Director/CNO to add an image to a main or detail step.

Remove image Allow Director/CNO to remove an image from a main or detail step.

Add audio Allow Director/CNO to add an audio record into the main and detail step.

Remove audio Allow Director/CNO to remove an audio record from a main and detail step.

Add video Allow Director/CNO to add a video into a main and detail step.

Remove video Allow Director/CNO to remove a video from a main and detail step.

Change order of steps

Allow Director/CNO to specify the order of steps for a task.

Assign a Task instruction

Allow Director/CNO to publish the Task instruction from Library.

AssignController() Publish (set true)

Unassign a Task instruction

Allow Director/CNO to unpublish the Task instruction from Library.

AssignController() Unpublish (set false)

Upload file Allow Director/CNO to add files into the working schedule and working hour.

Remove file Allow Director/CNO to remove files from the working schedule and working hour.

Create Event Allow Director/CNO to create an event list.

30


Edit Event Allow Director/CNO to change and update the event’s information.

Remove Event Allow Director/CNO to remove event.

Create Memo Allow Director/CNO to create a memo for daily records.


Table A_1-3: Functional Requirements (Mobile)


Verified ID Make sure CNA/Family input the right ID, that is, they are able to login if input ID is correct.

View Portfolio Portfolio created using the browser version is stored in the database, and can only be view by CNA/Family.

View Announcement

Announcement is available for view only by CNA/Family as app users.

View Task Instruction

Task instruction are stored in the database and is accessible for view purpose only by CNA/Family.

View Center Schedule

The Center Schedule is retrieved from the database and is only available for view purpose by CNA/Family as prescribed.

View Working Schedule

Working Schedule is access from the database in view mode only by CNA/Family.

View Daily Status Record

Daily status can only be view by CNA/Family in the App(Mobile) version after been stored in the database.

View Vital Status Record

CNA/Family can only view vital status and it is retrieve from the database.

Write feedback Report

CNA/Family can write feedback report which is saved in database and received by Director/CNO for response.

31

APP Version(Tablet)

Table A_1-4: Functional Requirements (Tablet)


Update Daily Status Record

The CNA updates the daily status record and saves it into the database for reference.

View Daily Status Record

Daily vital status is viewed by CNA after confirmation of storage in the database.

Update Vital Status

saily vital status is updated using App(Tablet) version by a CNA and is stored in the database.

View Vital Status The vital status updated is sent to the CNA that did the job to view and also stored in the database for confirmation and reference respectively.

Patient from a room selection

patients within a room are able to easily selected using the App(Tablet) version for status update or view utilising the database.

Receive AI Status

The AI status of a patient is received from sensors with the functional capabilities of the App(Tablet) version and data stored in the database automatically.

View AI Status AI status is available for view by the CNA/Family after receive of status from sensors.

32

7.0 NON-FUNCTIONAL REQUIREMENTS

Browser Version

Non-functional requirement is requirements that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. As Table B_1-3 shows the LTC-TMS browser system non-functional requirement specified by the browser team.

Table B_1-3: Non-functional requirement

Requirement Purpose How the requirement will be measured

Security

Security is one of the important factor for the LTC-TMS. It is important for LTC-TMS to have security as to ensure the user’s information are secure. Besides, the system required a proper security protocol to secures the personal identifiable information(PII) which prevent releasing it to unauthorized users.

Development team will implement confidential measures on the application.

Reliability

The difficulty of making a reliable application system is crucial. When users interact with the system, it is required for the system to send and retrieve data as fast as possible.Thus, the time required for user to wait will be shorten as much as possible.

The development team will conduct experiments on figuring out the Mean Time Between Failure (MTBF). Thus, the development team may required to do maintenance or update in a fixed schedule.

Usability

Practices must be implemented on using the LTC-TMS as to minimize time consumption on accessing the system application.

The development team will attempt to create user-friendly interface by inputting manual guide and simplify application control access.

33

APP Version(Mobile)

Three(3) non functional requirements are chosen for the app version (mobile) for LTC-TMS which are reliability , privacy and compatibility. These non-functional requirements play a vital role in the successful performance and maintenance of an application. Immediate response times are necessary for LTC-TMS. In addition, LTC-TMS app version must be able to handle new and different versions of iOS and android.

Table A_1-5: Non-functional Requirements (Mobile)

Requirement Purpose How The Requirement Will Be Measured

Reliability

The app version(Mobile) is design in a way to ensure that the software is able to executes the functions designed consistently with the minimum neglectable failures. This is one of the greatest priorities.

Using the LTC-TMS app version feedback function will help to know how reliable the system has been and ensure timely corrections to bugs or errors.

Privacy

LTC-TMS app version(Mobile) is designed for Family/CNA to view data in order to get important information of patient or the Long-term care Center. The data is submitted by CNO or Director from LTC-TMS browser version. Therefore it is a priority to protect personal and other relevant information from unauthorized access.

To view all the information which are provided by LTC-TMS app version, users must login with their own ID. The content which are displayed differ from user to user.

Compatibility

LTC-TMS app version(Mobile) will meet the expectations for the end users by creating the application so that it is compatible with different operating systems.

LTC-TMS app version will be developed using app inventor 2 and swift. The firebase database will be implemented to allow easy coordination between the app, browser and tablet version regarding data access.

34

APP Version(Tablet)

Three non functional requirements are chosen to describe the quality attributes of the App Version(Tablet). Generally, the measure of our software product quality characteristics are not limited to those mentioned here but are considered during development.

Table A_1-6: Non-functional Requirements (Tablet)

Requirement Purpose How The Requirement Will Be Measured

Performance The LTC-TMS App Version(Tablet) is designed in a way to handle its operational capacity, with a high throughput and great response time. These are all essential measures of the system efficiency.

Several tests will be conducted before the final delivery of the product and also there will be testing duration at the time of delivery to acquire feedback in time before the final delivery. Feedbacks and reports will help to measure performance of the system.

Usability The LTC-TMS App Version( Tablet) is design with simplicity in mind for users. This will enable them learn, operate, prepare status inputs outputs through the interaction with the system. The intended users of the system will be trained on how to user the system to execute duties.

To ensure this requirement is met, users perception of the product will be considered in terms of usage. Feedbacks and reports will be recommended.

Integrity The LTC-TMS App Version( Tablet) is designed to make sure that users concern for accuracy and authenticity of data is addressed and the data is also completely free from corruption.

There will be regular checks to ensure data accuracy and authenticity and also good security measures to avoid data from been corrupted.

Scalability The LTC-TMS App Version( Tablet) is a product that is designed with the mind for a necessary expansion in times of functions, processing power and so on.

The ease with which new functions are added without negative impact on the processing power and other requirements is seen as a good measure for scalability.

35

8.0 USE CASE DIAGRAM Use case diagram shows an Actor and it’s represented as a stick figure. The Use Case

itself will be named in an oval rectangle. The Association Line will connect the actor to the Use Case they have a relationship with. The System Boundary represents all Use Cases in a specific Subsystem. The subsystem is a list of major components (Use Cases) for a part of a system. In this scenario, a subsystem represents functional requirement categories.

Figure AB_1-3: Standard UML-based Use Case Diagram

36

Browser Version

The figure B_1-2 shows a complete use case diagram for the LTC-TMS. Use cases describe activities that LTC-TMS in browser platform could performs which illustrate the interactions between actor(s) and the system. The following would be the description of the use case diagram:

Director and CNO both are able to use this system to create or edit announcement, track memo, create or edit event list for special activities or treatment, taking care of the working schedule and working hour of each worker in the LTC center by uploading working schedule and working hour files, view the daily status record, vital status record and A.I status record of each patient, create task instruction to teach or command CNA workers in the center (or guardian) through LTC-TMS, and re-view help and support page. Edit the task instruction, accessing the stored task instruction in the Library are available for both actors, and of course both actors do have Login function for security purpose.

The difference between Director and CNO are their privileges on handling a portfolio. Director is able to view the staff/patient portfolio, along with creating a new staff/patient portfolio and editing an existing staff/patient portfolio. However, CNO are only given the privilege of viewing an existing staff/patient portfolio.

Figure B_1-2: Use Case Diagram of LTC-TMS

37

APP Version(Mobile)

Figure A_1-3 shows a complete use case diagram for the LTC-TMS app version(mobile). Readers are able to understand more of the system function through the use case diagram and get a clear picture of the system. CNA and Family can both access this system(tablet version can only be accessed by CNA). Both can view task instruction, schedule, announcement, and portfolio but cannot create, edit or modify. The following would be the description of each use case:

CNA can view the status record, working hours data, and working schedule. Also, they can view their own portfolio. Task instruction which is created by either the Director or CNO through web version is distributed to the CNA and Family. A Family can view only the patient's status record.

Overall, user can achieve specific goals that are provided by the systems and learn from new informations that will be updated daily by CNO or Director.

Figure A_1-3: Use Case Diagram of LTC-TMS-Users

38

APP Version(Tablet)

The tablet is a workstation that is placed in each room of the patient’s room for use by the CNA. Therefore, a CNA can select an individual patient from a room to update his/her daily status, vital status or view a patient’s AI status from sensors. Below, Figure A_1-4 is the use case diagram for the LTC-TMS app version(tablet).

Figure A_1-4: Use Case Diagram of LTC-TMS (Tablet)

39

9.0 USE CASE DESCRIPTIONS Descriptions of Use Case Description for View Task Instruction that have to do with the

database system of browser team.

Browser Version

Fully Developed Use Case Description: Create a Task Instruction In the table B_1-4 below shows a fully developed use case description of creating a

task instruction. The table explains the use case description through different aspects including scenario, triggering event and etc. In this use case it involve CNO and Director who are both actors. The scenario set for this use case is that a new task instruction need to be added. The triggering event is an actor wanting to deliver a lesson or command to the other staff.

Table B_1-4. Fully Developed Use Case Description for Create a Task Instruction

Use Case Name Create a Task instruction

Scenario There is a new task instruction are going to be added.

Triggering Event CNO/Director wants to deliver a lesson or command to the workers and families.

Brief Description CNO/Director create, edit or delete task instruction and the system store the updated task instruction into the database. The system display all the stored task instruction in Library page.

Actors CNO, Director

Related Use Cases View Task Library

Stakeholders CNO, Director

Pre-Conditions 1. There must be an instruction to add. 2. Must be logged-in.

Post-Conditions 1. Task instruction are stored in the database. 2. Task instruction can be viewed in library page.

40

Use Case Name Create a Task instruction

Flow of Activities

Actor System

1. CNO/Director has to select and click the Task Editor from the navigation bar.

1.1 System retrieves Task Editor page from the database. 1.2 System displays Task Editor page for the actor to view.

2. CNO/Director directs the mouse to the treeview box and right click.

2.1 System displays drop-down menu selection of add new task. 2.2 System selects add new task to begin.

3. CNO/Director selects add new task.

3.1 System displays new empty editable task page. 3.2 Select the editable task page

4. CNO/Director inserts task information and click submit

4.1 System selects Task from the library. 4.2 System inserts new information in task and submit.

Exception Condition

1.Data loss during transportation during poor connectivity 2. Webpage format failure.

41

Fully Developed Use Case Description: Create Portfolio

Table B_ 1-5 is a fully developed use case description explaining create portfolio. The table explained that the actor (CNO) need to create new portfolio for a new patient or staff member. The table further explain its description through different aspects including pre-condition, post-condition and a lot other aspects.

Table B_ 1-5: Fully Developed Use Case Description for Create Portfolio

Use Case Name Create Portfolio

Scenario Creating a staff/patient portfolio.

Triggering Event New staff/patient join the LTC center.

Brief Description

CNO create, modify or delete staff portfolio and patient portfolio. System store portfolio into database.

Actors CNO

Stakeholders Director, CNO, patient

Pre-Conditions 1. A staff or patient joins the LTC center. 2. The staff or patient should have his identity prove.

Post-Conditions 1. New staff/patient information are recorded and stored. 2. The new staff/patient information could be search and view in the future. 3. New account were created.

Flow of Activities

Actor System

1. Select portfolio section in the navigation bar.

1.1 System retrieves the portfolio page from the database. 1.2 System displays the portfolio page.

2.1 Click either the staff or patient box choice regardingly. 2.2 Click the add button in order to create a new portfolio.

2.1 System displays existing staff/patient portfolio page. 2.2 System displays a new portfolio page for either staff/patient regardingly.

3. Insert information and click upload button when finished.

3.1 System uploads the new information page into the database.

42

Exception Condition

1. New staff/patient is not able to join the LTC center. 2. New staff/patient information is invalid or illegitimate.

APP Version(Mobile)

Fully Developed Use Case Description: View Task Instruction

Table A_1-7 shows the fully developed use case description for the “view task instruction”. The Scenario for this use case assumes that users enter the hamburger menu page, and click the task instruction. Users can view the task instruction steps by steps. In this use case, the preconditions show that existing objects must already exist before the use case can be viewed. The postcondition describes the state of the system at the end of the use case.

Table A_1-7: Fully Developed Use Case Description for View Task Instruction (Mobile)

Use Case Name View Task Instruction

Scenario Let users view the task instruction.

Triggering event Users login and view the given task instruction.

Brief Description

The system provides a list of tasks to be viewed on the task instruction page. After selecting a task instruction, the system will direct to a page that display the title of the selected “task instruction” and a “Proceed” button. After clicking “Proceed” button, due to different environment of the devices, some will download the task instruction pdf file, others will display directly.

Actors CNA and Family.

Stakeholders CNA and Family.

Pre-Conditions 1. User_ID must exist to enable login. 2. Users must login. 3. Device must be able to open and display pdf file correctly

Post-Conditions 1. System has to output the task instruction. 2. Staff received notification due to the creation of a task instruction. 3. System stored the task instruction into library.

43


Flow of Activities

Actor System

1.Users select hamburger icon(at menu bar).

1.1 System direct to menu page. 1.2 System list out buttons.

2.Users select task instruction button.

2.1 System direct to task instruction page. 2.2 System list out task instructions.

3. Users select a specific task instruction

3.1 System direct to detail task instruction page. 3.2 System display a “Proceed” button.

4. Users press the “Proceed” button

4.1 System direct to a web link through the default browser. 4.2 The browser will download the file or display the file directly.

Exception Conditions

1. If the type-in ID is wrong, the user will not be able to login LTC-TMS. 2. If there is no internet connection, the user can’t login. 3. If the selected type of task instructions do not exist file.

44

APP Version(Tablet)

Fully Developed Use Case Description: Update the patient’s Vital Status

Table A_1-8 shows the fully developed use case description for the “update the patient’s vital status”. The CNA is able to update a patient’s vital status on tablet. In this use case, the preconditions show that existing objects must already exist before the use case can be viewed. The postcondition describes the state of the system at the end of the use case.

Table A_1-8: Fully Developed Use Case Description for Update a patient’s Vital Status (Tablet)

Use Case Name Update the patient’s Vital Status

Scenario CNA required to input patients vital status according to a specific time.

Triggering event Recording are required after CNA checked on patient’s vital status.

Brief Description

CNA select a patient from a room, and from status selection page, select the vital status page. CNA input the vital status records, signs his/her staff ID before data submission, and the system sends the data into the database.

Actors CNA

Stakeholders CNA

Pre-Conditions 1. CNA has to collect the raw data of the patient’s vital status.

Post-Conditions 1. Vital status data must be delivered and updated into the database. 2. CNA must fill up their staff ID in order to submit the vital status records.

45


Flow of Activities

Actor System

1.1 CNA select a room number. 1.2 CNA select a patient within the room.

1.1 System displays candidates within the selected room number. 1.2 System directs CNA to status selection page.

2.1 CNA select the vital status page from status selection page.

2.1 System redirects user to vital status page.

3.1 CNA input the raw data into the fields of vital status page along with his/her staff ID and submit. 3.2 CNA selects confirm on the alert box.

3.1 System alerts CNA with selection of confirmation on submission or further edit data. 3.2 System updates the data into the database and directs CNA back to status selection page.

Exception Conditions

3.1 The CNA did not input his/her staff ID or inputs an invalid staff ID.

46

Documents

TABLE OF CONTENTS - Kutztown University of Pennsylvaniafaculty.kutztown.edu/tan/csc354/Datafiles/TechnicalDocs/... · 2018-09-17 · table of contents t a b l e o f c o n t e n t