Table of Contents



Software Requirements SpecificationVersion 2.2App TeamTyler BartnickDuong DoanAndrew ReichardRyen ShearnPeter ShivelyPhillip YoderCSC 354Dr. TanTable of Contents TOC \o "1-3" \h \z \u Table of Contents PAGEREF _Toc529778739 \h iREVISION HISTORY PAGEREF _Toc529778740 \h iii1.0 INTRODUCTION PAGEREF _Toc529778741 \h 11.1 Purpose of Document PAGEREF _Toc529778742 \h 11.3 Explanatory Material: Acronyms & References PAGEREF _Toc529778743 \h 22.0 PROJECT CONSIDERATIONS PAGEREF _Toc529778744 \h 42.1 Identified Costs PAGEREF _Toc529778745 \h 42.2 Possible Tools PAGEREF _Toc529778746 \h 42.3 Open Issues and Questions PAGEREF _Toc529778747 \h 52.4 Long-Term Plans for Future Releases and Features PAGEREF _Toc529778748 \h 52.5 Standards and Regulatory Considerations PAGEREF _Toc529778749 \h 63.0 PROJECT SCOPE PAGEREF _Toc529778750 \h 73.2 CNO Perspective PAGEREF _Toc529778751 \h 73.3 CNA Perspective PAGEREF _Toc529778752 \h 83.4 Family Perspective PAGEREF _Toc529778753 \h 93.5 Common User Perspective PAGEREF _Toc529778754 \h 94.0 SYSTEM ARCHITECTURE DIAGRAM PAGEREF _Toc529778755 \h 105.0 FUNCTIONAL REQUIREMENTS PAGEREF _Toc529778756 \h 125.1 Family Mobile Functional Requirements PAGEREF _Toc529778757 \h 125.2 CNA Mobile Functional Requirements PAGEREF _Toc529778758 \h 135.3 Tablet Functional Requirements PAGEREF _Toc529778759 \h 155.4 Database/Hardware Functional Requirements PAGEREF _Toc529778760 \h 165.5 Browser Functional Requirements PAGEREF _Toc529778761 \h 206.0 NONFUNCTIONAL REQUIREMENTS PAGEREF _Toc529778762 \h 306.1 APP Version Mobile PAGEREF _Toc529778763 \h 306.2 APP Version Tablet PAGEREF _Toc529778764 \h 307.0 USE CASE DIAGRAM PAGEREF _Toc529778765 \h 327.1 Mobile Use Case Diagram PAGEREF _Toc529778766 \h 337.2 Tablet Use Case Diagram PAGEREF _Toc529778767 \h 358.0 USE CASE DESCRIPTIONS PAGEREF _Toc529778768 \h 36REVISION HISTORYTable 1 is the up-to-date revision history chart. As changes to this document are made, the chart will be edited to include it.VersionDateDescriptionEditor1.010/26/2018Added:3.0 Project Scope3.1 Director Perspective3.2 CNO Perspective3.3 CNA Perspective3.4 Family Perspective3.5 Common User PerspectiveTyler Bartnick1.110/28/2018Added: Section 1.1 Purpose of Document1.2 High Level Product Overview1.3 Explanatory Material: Acronyms and References2.1 Identified Costs2.2 Possible Tools2.3 Open Issues and Questions2.4 Long-Term Plans for Future Release and Features2.5 Standards and Regulatory Considerations Phillip Yoder10/28/2018Added:4.0 Functional RequirementsPeter Shively1.210/29/2018Updated: 1.2 High Level Product Overview 2.1 Identified CostsRyen Shearn1.310/30/2018Added:3.6 System Architecture DiagramTyler Bartnick1.410/31/2018Modified:4.0 Functional RequirementsAdded:7.0 Use Case DescriptionsPeter ShivelyAdded:5.0 Nonfunctional RequirementsDuong DoanAdded:7.0 Use Case Diagram7.1 Mobile Use Case Diagram7.2 Tablet Use Case DiagramAndrew Reichard2.011/5/2018Modified:2.1 Identified Costs Table 2.3 Open Issues and Questions2.4 Long-Term Plan for Future Releases and Features2.5 Standards and Regulatory Considerations3.1 Director PerspectiveRyen Shearn2.111/11/2018Modified: 6.0 Nonfunctional Requirements 6.1 App Version (Mobile)6.2 App Version (Tablet)8.0 Use Case DescriptionDuong Doan11/11/2018Modified:1.1 Purpose of Document1.3 Explanatory Material: Acronyms and References2.0 Project Considerations2.2 Possible Tools2.5 Standards and Regulation Considerations3.2 CNO Perspective3.3 CAN Perspective3.4 Family PerspectiveAdded:3.0 Project Scope (description)Modified: Section numbering >5.x5.0 Functional Requirements5.1 Family Mobile Functional Requirements5.2 CNA Mobile Functional Requirements5.3 Tablet Functional Requirements8.0 Use Case DescriptionsPeter Shively11/11/2018Modified:7.0 Use Case Diagram7.1 Mobile Use Case Diagram7.2 Tablet Use Case DiagramAndrew Reichard2.211/12/2018Updated:Footers of all Figures and TablesRyen ShearnTable 1: Revision History1.0 INTRODUCTION1.1 Purpose of DocumentThe purpose of this Software Requirements Specification (SRS) is to give detailed information on how the Long-Term Care – Task Management System (LTC-TMS) functions by providing descriptions of the many aspects involved with making the project work.Section 2.0, Project Considerations, gives details about the resources needed for the LTC-TMS, like prices and how many are needed. It also has a section about issues or any currently identified issues that the project might run into.Section 3.0, Project Scope, goes into detail about what the end users can do depending on who they are. The directors, CNOs, CNAs, and family members all have different actions they can take once they are signed in. At the end of this section is a list of similar actions that end users can do, regardless of position.Section 4.0, System Architecture Diagram, provides a diagram to visually show the relations ship between the browser, app, and hardware to the Firebase database.Section 5.0, Functional Requirements, describes the requirements for the different versions of the project to be functional and a priority number to make sure its importance is made clear.Section 6.0, Non-Functional Requirements, describes what requirements that are used to improve the system and make it easier for someone to use.Section 7.0, Use Case Diagrams, visually demonstrate each action that can be completed depending on the user's perspective.Section 8.0, Use Case Description, provides details to the use case diagrams shown in sections 7.0.1.2 High Level Product OverviewThe high-level product overview summarizes the functionality of the LTC-TMS for each version of the app and the hardware components that interact with it: Browser Overview: Browser version is only accessible to the Director and CNO of LTCCan create and modify task instructions, announcements, memos, and eventsRetrieve daily status record, vital status record and AI status record from databaseDirector creates and modifies patient and staff portfoliosCNO can create and modify task instructionsDirector can create patients’ medical dataApp (Mobile) Overview:CNA and family members can view the task instructions for the patients’ needs.Family members can view the portfolio, daily status, vital status, and AI status records of the A can view their own portfolio Family members and CNAs can submit feedback via the app.All pertinent information is retrieved from the A and family can view announcements CNA and family can view center scheduleApp (Tablet) Overview:CNA can enter the daily and vital status of the As view the patients’ AI status.Hardware Overview:A micro bit bracelet that is modified to be for the patients to wear so that it can retrieve data in real time and transmit through radio frequencyA different micro bit is attached to a Raspberry Pi, through its USB port, transformed into a radio frequency reader and installed at every section of the LTC centerThe Raspberry Pi will send the data to the database through WI-FI once it receives the data1.3 Explanatory Material: Acronyms & ReferencesBelow is a list of acronyms and terms used within this document:?CNA – Certified Nursing Assistant is one of the staff members who will have direct contact with the patients. CNO – The Chief Nursing Officer is a staff member in more of an administrative role at the health facility.LTC – Long Term Care?specifies the type of facility where the product will be deployed.TMS – Task Management System?is the component of the product that will assist patients in performing daily tasks.MCU – Ming?Chuan?University?is the partner school developing the product alongside the students at Kutztown University.KU – Kutztown University is the partner school developing the product alongside the students at Ming Chuan University.SRS – Software Requirements Specifications is this document that describes how the LTC –TMS functions with detailed information on how it functions.TOS – Terms of Service is a document written by the development team to ensure that the system is not used incorrectly misused and keeps the developers out of legal trouble.SSN – Social Security Number is a number assigned to residents of the United States for identification purposes.2.0 PROJECT CONSIDERATIONSWhat follows are the resources, tools, issues, and future updates of the LTC-TMS. The project will stay in this scope unless the project teams decide to expand or reduce it. Any new additions are to be agreed upon by all parties involved, that includes the client, the app, and browser teams.2.1 Identified CostsBelow is a list of resources that the teams will be using during the development of the project.ItemQuantity Total Cost ($)Microbit: 83-176344164.42T-GPIO Expansion Board and 40-pin Rainbow Cable2Included with Raspberry PiTemperature and Humidity sensor: DHT11210.59Air Quality Sensor: SHARP GP2Y1014AU0F213.54Heart Rate Sensor: 101020082259.88Battery for Microbit2Included with MicrobitGrove Shield for Micro-Bit226.29Microchip MCP3008 8-Channel 10-Bit A/D Converters 419.24Silicone Case for the Microbit (pack of 2)113.61Rechargeable Batteries AAA (pack of 4)122.58Battery Charger111.65Table 2: App Hardware CostsThe Kutztown University Computer Science Department will provide two Raspberry Pi models for the teams to use.2.2 Possible ToolsBelow is a list of tools that are used to construct the LTC-TMS project and different mediums in which the each team uses to communicate details to each other:Database:Firebase Real-Time DatabaseFirebase cloud serverText Editors:Google Editey is a group text editor based in the Google drive and works similarly to Google documents and Google sheets.App Inventor 2 is the application used for Android app development.Swift (XCode), is the application used for iOS app development.JSON editor is a web-based text editor that lets the user view, edit or validate JSON munication:Slack is used to communicate between the different KU teams and for the team members to communicate within the app team.Line is used to message between the MCU and KU app teams.Google Hangouts is used to have video conferences with between the MCU and KU app teams.Code Sharing:GitHub is a website that allows one to host and store the different versions of their code.File Sharing:Google Drive is a service owned by Google that allows file storage and sharing over the internet.Microsoft OneDrive is a service owned by Microsoft that allows file storage and sharing over the internet.2.3 Open Issues and QuestionsA potential issue that may arise is the negative impact on staff employees by transitioning from physical forms of information recording to digital forms. There is a new learning curve that may prove to be challenging for staff. This can lead to increased time for logging information, instead of shorter. There’s also the issue that the system will not be able to perform all the tasks that the center needs it to do, possibly missing certain functions or types of information inputs that were not thought of by the teams. Determining how to design the system to be HIPPA compliant also is an open issue. 2.4 Long-Term Plans for Future Releases and FeaturesThe system is designed to support the LTC center staff in their daily workflow. Once the system is successfully created, the developers must implement the following: The future expansion of the LTC-TMS with new and improved functionalityThe application is accessible and simple to use for all usersSpeech-to-text and text-to speech functionalityAvailable in several languages2.5 Standards and Regulatory ConsiderationsAttention to detail is important when using a database. All possible steps will be taken to ensure that users’ and clients’ sensitive information, like SSN or credit card numbers, is safe. The TOS will be created to demonstrate how to use the system correctly and state that if the system is used maliciously, the responsible user(s) will be prosecuted. All personal information entered into the system will not be shared to any third-parties, unless permission is granted by the user. Non-personal information, like app reviews, may be collected by developers to enhance the system.3.0 PROJECT SCOPEThis section is here to explain the different perspectives of the LTC-TMS. The actions made available to the user differ depending on who is using it. Directors and CNOs are restricted to the browser version while CNAs and family members are restricted to the app versions. 3.1 Director PerspectiveThe Director of the LTC facility is granted full access to the LTC-TMS through the browser version. Their main responsibility is to create user accounts and portfolios for staff and patients and post announcements. They can also create and assign tasks to LTC facility staff. The full list of authorized actions for a director are listed below:View daily status record on a per-patient basisView vital status record on a per-patient basisView system status recordView user-submitted feedbackCreate and edit user portfoliosCreate and edit announcementsCreate and edit eventsCreate and edit tasksCreate and edit personal memosAssign task(s) to specific user or group of usersGenerate reports of the patientsAnalyze reports of the patientsCreate and delete work schedule for LTC facility staffCreate and delete LTC facility schedule3.2 CNO PerspectiveThe CNO of the LTC facility is given limited access to the LTC-TMS through the browser version when compared to the Director, but more when compared to the CNAs and family. Their main responsibility is to give the CNAs their tasks and the hours.The full list of authorized actions for the CNO are listed below:View user portfoliosView daily status record on a per-patient basisView vital status record on a per-patient basisView system status recordView user-submitted feedbackCreate and edit announcementsCreate and edit eventsCreate and edit tasksCreate and edit personal memosAssign task(s) to specific user or group of usersGenerate reports of the patientsAnalyze reports of the patientsCreate and delete work schedule for LTC facility staffCreate and delete LTC facility schedule3.3 CNA PerspectiveThe CNA has a unique role regarding the system in question. The CNA’s perspective will vary based on which version of the app they are using. CNAs are required to use the tablet version of the app to do their day-to-day work. However, CNAs may also use the app designed for families to view a given patient’s data without editing existing data or inputting additional data as they would in the tablet version.Based on the version of the app in use, the full list of authorized actions for the CNA are listed belowMobile AppView daily status recordView vital status recordView system status recordView completed tasks for patientView patient portfolioView LTC facility scheduleInput and submit feedbackTablet AppView system statusInput and submit daily status record on a per-patient basisInput and submit vital status record on a per-patient basis3.4 Family PerspectiveA family member of a patient that has been granted access to a patient’s data should be able to view stored data pertaining to that patient. Based on the version of the app in use, the full list of authorized actions for the family members are listed belowView daily status recordView vital status recordView system status recordView announcements for LTC facilityView completed tasks for patientView patient portfolioView LTC facility scheduleInput and submit feedback3.5 Common User PerspectiveRegardless of interface (mobile/tablet app or website) used, all users should be able to do the following:LoginAccess resources and data for which user is authorizedLogout4.0 SYSTEM ARCHITECTURE DIAGRAMFigure 1 (following page) is the System Architecture Diagram for the LTC-TMS. The diagram shows the relationship and dependency that the devices have with the Firebase service. All data for the system will be sent to and received from Firebase. This is true for the website and all applications. The hardware component for the system will include a micro:bit for each patient that reads vital sign data and wirelessly sends that data to a slave raspberry pi, which in turn, relays that data to a master raspberry pi for storage in Firebase.190506661150Figure SEQ Figure \* ARABIC 1: System Architecture DiagramFigure SEQ Figure \* ARABIC 1: System Architecture Diagram19050281940005.0 FUNCTIONAL REQUIREMENTSTables 5-1 (family mobile), 5-2 (CNA mobile), 5-3 (tablet), 5-4 (database/hardware), and 5-5 (browser) are the current functional requirements for the LTC-TMS project. Category represents a larger scope than one individual requirement, Requirement ID is an identification number assigned to each requirement. The Requirement column is a listing of the requirements themselves, with the description being how the teams intends to facilitate the requirement. The priority number given to each requirement indicates the necessity for it to be in the project, with 1 being a base requirement, 2 as something that would be very beneficial to have in the application, and 3 as a requirement that would be nice to have, but not a necessity.5.1 Family Mobile Functional RequirementsTable 5-1 is the table of functional requirements for the mobile version of LTC-TMS with a family member as the intended user. CategoryRequirement IDRequirementDescriptionPriorityUser Login1Family must be able to login to the system.Family will be provided with default login info which can be changed to enable secure login.1Tasks Instruction Viewing2Family must be able to select the instruction type.All task instructions are created from the browser page and this enables Family to select the instruction type.13Family must be able to view the page of tasks instruction list.System will list task instructions on the page.14Family must be able to view task instructions.A task instruction is composed with text, video and a PDF file.1Daily Status Record Viewing5Family must be able to view Daily Status Record pageUsers are able to select “Daily Status Record” at hamburger menu page.16Family 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.17Family must be able to view status record with a selected date.After selecting a date, the status record data will be shown to family.1Announcement Board Viewing8Family must be able to enter home page and view the announcement board.App will retrieve announcement board information from the LTC-TMS database, that is generated in the browser version.1Portfolio Viewing9Family must be able to enter and view portfolio page.App will retrieve portfolio information from the database that is created using the LTC-TMS browser. Family can only view the portfolio for their family member.1Feedback Sending10Family must be able to send feedback.Family is able to submit the feedback to the database which is also forwarded to CNO/Director.111Family 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.1Voice Output12Family is able to listen to the information when they click on the sound icon as voice.Family are able to listen to a voice version of the information when click on the sound icon.2Voice Input13Family is able to input information using their voice.Family are able to speak into the device to input data in fields when tapping the microphone icon.1Table 5-1: Family Mobile Functional Requirements5.2 CNA Mobile Functional RequirementsTable 5-2 is the table of functional requirements for the mobile version of LTC-TMS with a CNA as the intended user. CategoryRequirement IDRequirementDescriptionPriorityUser Login1A CNA must be able to login to the A will be provided with default login info which can be changed to enable secure login.1Tasks Instruction Viewing2A CNA must be able to select the instruction type.All task instructions are created from the browser page and this enables a CNA to select the instruction type.13A CNA must be able to view the page of tasks instruction list.System will list task instructions on the page.14A CNA must be able to view task instructions.A task instruction is composed with text, video and a PDF file.1Daily Status Record Viewing5A CNA must be able to view Daily Status Record pageUsers are able to select “Daily Status Record” at hamburger menu page.16A CNA 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.17A CNA must be able to view status record with a selected date.After selecting a date, the status record data will be shown to family.1Announcement Board Viewing8A CNA must be able to enter home page and view the announcement board.App will retrieve announcement board information from the LTC-TMS database, that is generated in the browser version.1Portfolio Viewing9A CNA must be able to enter and view portfolio page.App will retrieve portfolio information from the database that is created using the LTC-TMS browser. 1Center Schedule Viewing10A CNA must be able to view all the center schedules for the month.Home page will show a sample table that include events for 5 days (past 2 days/today/next 2 days)111A CNA must be able to view all the center schedules for the month.If a CNA clicks on the Center schedule on home page, the app opens the calendar for the current month. Users can switch to different months for the center schedule.1Working Schedule Viewing12A CNA must be able to view working schedule for the A can select the work schedule in menu page, which opens the working schedule page. The CNA is able to switch months and view data.1Working hour data Viewing13A CNA must be able to view the number of hours they work for the A 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.1Feedback Sending14A CNA must be able to send A is able to submit the feedback to the database which is also forwarded to CNO/Director.115A 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.1Voice Output16A CNA is able to listen to the information when they click on the sound icon as A is able to listen to a voice version of the information when click on the sound icon.2Voice Input17A CNA is able to input information using their A are able to speak into the device to input data in fields when tapping the microphone icon.1Table 5-2: CNA Mobile Requirements5.3 Tablet Functional RequirementsTable 5-3 is the table of functional requirements for the tablet version of LTC-TMS. The CNA is the expected user.CategoryRequirement IDRequirementDescriptionPriorityPatient from a room selection1A 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.1Daily Status Updating2A CNA must be able to input data.The CNA needs to be able to fill in data to the fields, and select appropriate checkboxes provided on the tablet version.13A CNA must be able to identify themselves before submitting the data to the database.Each batch of data submitted to the database is identified with the CNA in charge.14A 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 dialog box to ensure the accuracy of the data.1Vital Status Updating5A 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.16A CNA must be able to identify themselves before submitting the data to the database.Each batch of data submitted to the database is identified with the CNA in charge.17A 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 dialog box to ensure the accuracy of the data.1AI Status Viewing8A 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.1Voice Input9A CNA is able to input information using their voice.A CNA is able to speak into the device to input data in fields when tapping the microphone icon.1Table 5-3: Tablet Functional Requirements5.4 Database/Hardware Functional RequirementsTable 5-4 is the table of functional requirements for the Database and Hardware components of LTC-TMS. CategoryRequirement IDRequirementDescriptionPriorityDatabase1Create a new instance of Firebase.Although KU and MCU are both using Firebase for the project, KU will have their own instance of Firebase to have their own independent data for testing and processing.1Database2Implement the database’s structure in JSON format, which consists of key and value pairs.The same JSON structure will be utilized as MCU for transparency of the LTC-TMS project.1Database3Bridge communication with the LTC-TMS system.The database administrators will permit communication to the LTC-TMS system so that data is accessible to the browser website and mobile applications.1Database4Add a data field to the database. The database consists of JSON documents that are turned into JSON objects by Firebase. ?These objects take in and properly store incoming data from an application. These JSON documents organize the data into key and value pairs (data fields). If a new type of data is needed to be stored in the system then a new data field will be added into the database via the proper JSON document. 2Database5Remove a data field from the database. The database consists of JSON documents that are turned into JSON objects by Firebase. ?These objects take in and properly store incoming data from an application. These JSON documents organize the data into key and value pairs (data fields). If part of an application is discontinued and the data it was sending to the database is no longer needed then the data field will be deleted via JSON document. 2Reporting6Generate report from LTC-TMS system.Generate a daily, weekly, and/or monthly report. The report may include text or bar charts. The report will be in PDF format.2Reporting7Send report via email in PDF format.Send the report via email from the LTC-TMS system.2Reporting8Store reports in the database.Store report history inside of database.2Hardware9Build the wearable device for patient to record their vitals.Constructing the wearable technology for the patient will be fulfilled using the hardware components purchased.1Hardware10Assemble the raspberry pi with a case for each room. Each room will have a raspberry pi that will receive the data from the wearable device the patient has and send it to the database.1Hardware11Maintain the hardware.This will involve ensuring the battery is charged and wearable is functioning for the CNA to use with the patient.1Hardware12Log data from the sensors.When sensors are being used, the DB/HW team will be responsible for ensuring the proper data is being captured (e.g. heart rate sensor recording heart rate, not another vital).1Hardware13Send data to the DB over Wi-Fi.The hardware device will be capable of sending patient vitals (data) over Wi-Fi connection to the database.1Hardware14Sensor will send data to micro:bit via radio frequency.Patient vital data will be sent over radio frequency from the sensors to the micro:bit1Hardware15Ensure that micro:bit and sensor use the same radio frequency.Each sensor will be channeled to the same radio frequency as the micro:bit.1Hardware16Ensure the patient does not inadvertently break the device.The wearable sensors will be worn in a location that would not be in the way of the patients day to day life3Hardware17Ensure the security of the hardware device.The CNA and CNO will monitor the device throughout the day, ensuring it does not leave the room.2Notifications18Family and CNA must be able to receive notifications via the mobile app. If CNO/Director makes any changes or post then the system will generate a notification in the browser version. Then the app will retrieve notification and sent to Family and CNA3Notifications19Alerts and Notifications displays on mobile notifications bar must be seen viewable by the Family/CNA.While the alert/ notification is displayed on the notification bar the system generates a notification within the system.3Table 5-4: Database/Hardware Functional Requirements5.5 Browser Functional RequirementsTable 5-5 is the table of functional requirements for the browser version of LTC-TMS.CategoryRequirement IDRequirementDescriptionPriorityCreate and Edit Portfolio1Director must be able to create a portfolio.When a new staff/patient joins the Facility, Director should be able to create Portfolio.12Director must be able to edit existing portfolio.When a patient/staff changes their information, Director should be able to edit the Portfolio.13Director must be able to view an existing portfolio.Director should be able to review the staff/patient Portfolio.24Director must be able to embed picture(s) into the portfolio.Given that a new staff/patient joins the care center, Director must upload the person’s picture.15CNO must be able to view an existing O should be able to review existing staff/patient Portfolio.26Director must be able to remove an existing portfolio.When a staff/patient quits the facility, Director should be able to remove an existing portfolio.1Create and EditAnnouncement7Director must be able to create an Announcement.When Director wants to deliver news, they must be able to create a new Announcement18CNO must be able to create an Announcement.When CNO wants to deliver news, they must be able to create a new Announcement19Director must be able to edit existing Announcement.Given there is an error in the published announcement,Director must be able to edit an Announcement.110CNO must be able to edit existing Announcement.Given there is an error in the published announcement,CNO must be able to edit an Announcement.111Director must be able to delete existing Announcement.Given there is an unwantedAnnouncement, Director must be able to delete an Announcement.112CNO must be able to delete existing Announcement.Given there is an unwantedAnnouncement, CNO must be able to delete an Announcement.1Create and Edit Memo13Director must be able to create a MemoIf Director needs a personal reminder, they must be able to create a memo.114CNO must be able to create a MemoIf CNO needs a personal reminder, they must be able to create a memo.115Director must be able to edit a Memo.Given that a memo must be changed, Director must be able to edit memos.116CNO must be able to edit a Memo.Given that a memo must be changed, CNO must be able to edit memos.117Director must be able to delete a Memo.Deleting Memo allows Director to delete unwanted Memo.118CNO must be able to delete a Memo.Deleting Memo allows CNO to delete unwanted Memo.1View Status Record19Director must be able to view the daily status record.After CNA submitted a patient’s daily status record of the day, Director must be able to view it.120CNO must be able to view the daily status record.After CNA submitted a patient’s daily status record of the day, CNO must be able to view it.121Director must be able to view vital status record.After CNA submitted a patient’s vital status record of the day, Director must be able to view it.122CNO must be able to view vital status record.After CNA submitted a patient’s vital status record of the day, CNO must be able to view it.123Director must be able to view AI status record.After CNA have submitted patients AI status record of the day, Director must be able to view it.124CNO must be able to view AI status record.After CNA have submitted patients AI status record of the day, CNO must be able to view it.125Director must be able to select a group of patients filtered by room numbersWhen Director has to input status records, Director must be able to find every patient's name listed according to the room number.226CNO must be able to select a group of patients filtered by room numbersWhen CNO has to input status records, CNO must be able to find every patient's name listed according to the room number.2Create and Edit Event27Director must be able to create an event.When there is a new event for the facility, Director must be able to create a new event.128CNO must be able to create an event.When there is a new event for the facility, CNO must be able to create a new event.129CNO must be able to edit an event.When an event is inaccurate, Director must be able to edit an event130CNO must be able to edit an event.When an event is inaccurate, CNO must be able to edit an event131Director must be able to key in event's dateAfter an event is created, Director must be able to set event's date132CNO must be able to key in event’s dateAfter an event is created, CNO must be able to set event's date133Director must be able to edit an event's dateWhen there is an error in the date of an event, Director must be able to edit the event's date.134CNO must be able to edit an event’s date.When there is an error in the date of an event, CNO must be able to edit the event's date.135Director must be able to delete event.When an event is expired or invalid, Director must be able to delete an existing event.136CNO must be able to delete event.When an event is expired or invalid, CNO must be able to delete an existing event.1Upload Work Schedule and Working Hour37Director must be able to upload file(s).Given that a work schedule file is to be uploaded, Director must be able to upload the file.138CNO must be able to upload file(s).Given that a work schedule file is to be uploaded, CNO must be able to upload the file.139Director must be able to delete uploaded file(s).After file expired/out of date, Directors are allowed to remove the file from the website.140CNO must be able to delete uploaded file(s).After file expired/out of date, CNO are allowed to remove the file from the website.1Create and Edit Task 41CNO must be able to create a new task.When a lesson or command needed to be delivered, Director must be able to create new task instruction.142CNO must be able to create a new task.When a lesson or command needed to be delivered, CNO must be able to create new task instruction.143Director must be able to add main steps to a task.After a task has been created, Director must be able to add the main step to a certain task when needed.144CNO must be able to add main steps to a task.After a task has been created, CNO must be able to add the main step to a certain task when needed.145Director must be able to add detail steps to a task.After the main step has been created, Director must be able to add a detail step to each main step correspondingly.146CNO must be able to add detail steps to a task.After the main step has been created, CNO must be able to add a detail step to each main step correspondingly.147Director must be able to remove task.Given that a task is no longer needed, Directors should be able to remove task instruction148CNO must be able to remove task.Given that a task is no longer needed, CNO should be able to remove task instruction149Director must be able to remove the main steps from a task.When a main step is not needed, Director should be able to delete that main step.150CNO must be able to remove the main steps from a task.When a main step is not needed, CNO should be able to delete that main step.151Director must be able to remove detailed steps from a task.When a detailed step should be removed, Director must be able to delete a detail step.152CNO must be able to remove detailed steps from a task.When a detailed step should be removed, CNO must be able to delete a detail step.53Director must be able to embed image(s) into a task.If an image can help explain a step, Director must be able to upload an image.254CNO must be able to embed image(s) into a task.If an image can help explain a step, CNO must be able to upload an image.Create and Edit Task 55Director must be able to embed video(s) into a task.Given that the steps for a given task require a demonstration, Director should be able to upload a video.256CNO must be able to embed video(s) into a task.Given that the steps for a given task require a demonstration, CNO should be able to upload a video.257Director must be able to access a task from the database.When Director wishes to edit a task, Director must be able to retrieve the task data from the database.158CNO must be able to access task from the database.When CNO wishes to edit a task, CNO must be able to retrieve the task data from the database.159Director must be able to edit a task.When a task’s information needs to be changed, Director should be able to change a task information.160CNO must be able to edit a task.When a task’s information needs to be changed, CNO should be able to change a task information.161Director must be able to save unfinished tasks as draft.Saving tasks before completion would give flexibility to Director to work on a task at different times262CNO must be able to save unfinished tasks as draft.Saving tasks before completion would give flexibility to CNO to work on a task at different times263Director must be able to save completed tasks to the Task LibraryOnce a task is completed, it must be saved to the Task Library.164CNO must be able to save completed tasks to the Task LibraryOnce a task is completed, it must be saved to the Task Library.65Director must be able to create a new keyword for a taskKeywords allow tasks to be found without knowing their full name266CNO must be able to create a new keyword for a taskKeywords allow tasks to be found without knowing their full name267Director must be able to choose an existing keyword for a taskPreset keywords allow tasks to be found without knowing their full name using common keywords.268CNO must be able to choose an existing keyword for a taskPreset keywords allow tasks to be found without knowing their full name using common keywords.269Director/CNO must be able to edit the main steps of a task.Given that the main steps of a task need to be changed, Director must be able modify the main steps.170Director/CNO must be able to edit the main steps of a task.Given that the main steps of a task need to be changed, CNO must be able modify the main steps.1Create and Edit Task 71Director should be able to reorder the main steps when creating a taskThe Director can switch step positions instead of deleting and rewriting the step.272CNO should be able to reorder the main steps when creating a O can switch step positions instead of deleting and rewriting the step.273Director should be able to reorder the main steps when editing a taskThe Director can switch step positions instead of deleting and rewriting the step.274CNO should be able to reorder the main steps when editing a O can switch step positions instead of deleting and rewriting the step.275Director must be able to edit detailed steps.When the detailed steps must be changed, Director must be able to edit the detailed step.276CNO must be able to edit detailed steps.When the detailed steps must be changed, CNO must be able to edit the detailed step.277Director should be able to reorder detailed steps when creating a task.The Director can switch step positions instead of deleting and rewriting the step.278CNO should be able to reorder detailed steps when creating a task.The CNO can switch step positions instead of deleting and rewriting the step.279Director should be able to reorder detailed steps when editing a task.The Director can switch step positions instead of deleting and rewriting the step.280CNO should be able to reorder detailed steps when editing a task.The CNO can switch step positions instead of deleting and rewriting the step.2Assign Tasks81Director must be able to distribute a task to specific groups or individuals.Director wishes to send a task to a specific group of users/individuals.182CNO must be able to distribute a task to specific groups or O wishes to send a task to a specific group of users/individuals.183Director must be able to cancel assigned tasksIn the event a task is no longer applicable to its assignee(s), the Director should be able to un-assign the task.284CNO must be able to cancel assigned tasksIn the event a task is no longer applicable to its assignee(s), the CNO should be able to un-assign the task.2View Task Library85Director must be able to view Task Library.After a task is created, Director should be able to view it in the task library.186CNO must be able to view Task Library.After a task is created, CNO should be able to view it in the task library.1Login87Director must be able to log in with the provided account.Director with an account must be able to login to the browser version of LTC-TMS.188CNO must be able to log in with the provided O with an account must be able to login to the browser version of LTC-TMS.1Logout89Director must be able to logout of their session.Director must be able to logout from the browser version of LTC-TMS. 190CNO must be able to logout of their O must be able to logout from the browser version of LTC-TMS.1Query Function91Director is able to search for information using keywords.Director is able to search for information by inserting keyword on the query function392CNO is able to search for information using O is able to search for information by inserting keyword on the query function3Voice Input93Director is able to dictate information to be translated to text.Director’s speech will be translated to text.394CNO is able to dictate information to be translated to O’s speech will be translated to text.3Voice Output95Director is able to listen to the information when the sound icon is clicked.Director is able to listen to a voice version of the information the sound icon is clicked.296CNO is able to listen to the information when the sound icon is O is able to listen to a voice version of the information the sound icon is clicked.Show QR Code97User 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.2View Help and Support98Director is able to view the help and support page.Director is able to view the help and support page when they want to view comments and suggestions from users.299CNO is able to view the help and support O is able to view the help and support page when they want to view comments and suggestions from users.2100Director is able to submit feedback on the system.Director is able to add comments and suggestions for the system.3101CNO is able to submit feedback on the O is able to add comments and suggestions for the system.3Language102Director should be able to choose the language in which they want to view the system.Director would be able to select the language they prefer which would increase usability3103CNO should be able to choose the language in which they want to view the O would be able to select the language they prefer which would increase usability3Browser Support104Director must be able to use the system on Chrome browser.Director should be able to use the system on the browser of their choice including Chrome 1105CNO must be able to use the system on Chrome O should be able to use the system on the browser of their choice including Chrome1106Director must be able to use the system on Firefox browser.Director should be able to use the system on the browser of their choice including Firefox. 1107CNO must be able to use the system on Firefox O should be able to use the system on the browser of their choice including Firefox.1108Director must be able to use the system on Safari browserDirector should be able to use the system on the browser of their choice including Safari. 1109CNO must be able to use the system on Safari browserCNO should be able to use the system on the browser of their choice including Safari.1110Director must be able to use the system on Internet Explorer browserDirector should be able to use the system on the browser of their choice including Internet Explorer. 1111CNO must be able to use the system on Internet Explorer browserCNO should be able to use the system on the browser of their choice including Internet Explorer.1112Director must be able to use the system on Edge browserDirector should be able to use the system on the browser of their choice including Edge. 1113CNO must be able to use the system on Edge browserCNO should be able to use the system on the browser of their choice including Edge.1Table 5-5: Browser Function Requirements6.0 NONFUNCTIONAL REQUIREMENTSNonfunctional requirements that specify how the application must behave. Nonfunctional requirements contribute to the quality of the application. 6.1 APP Version MobileThree nonfunctional requirements are reliability, privacy, and usability.?These nonfunctional requirements are important?for users’ experience of the application.??RequirementPurposeHow?the?Requirement Will be MeasuredReliabilityThe app version?(Mobile)?is design to perform all the available functions and features within the app consistently and with smallest possible time-out error.Reliability is measured by the downtime from second to minutes. The system should not be down for more than 15 minutes out of 24 hours. Users might use the?LTC-TMS app version feedback feature?to?notify about possible bugs or errors.?PrivacyThe app?version (Mobile) lets Family and Patients?view the?patients’?health records. It also let the CNA view their tasks and their schedule.Only family members with consent from patients can use the application. The users must login with their username and password to use the app to access sensitive information.UsabilityThe?app version (Mobile) is designed?with simple layout and easy to navigate through the app for users.Usability will be measured by the effectiveness, Effectiveness = (number of tasks completed successfully)/(total number of tasks undertaken) x 100% ?Table 6-1: Non-functional requirement?(Mobile)6.2 APP Version TabletPerformance, security, and reliability are three non-functional requirements for App Version (Tablet). The application relies on these nonfunctional requirements to assure users a safe, reliable, and quality application.RequirementPurposeHow?the?Requirement Will be MeasuredPerformanceThe App Version (Tablet) is designed?for CNA to enter?patients’?daily heath record. Performance is necessary to save time.Performance will be?measured from millisecond to second to complete a specific task. SecurityThe App Version (Tablet)?is designed for CNA to enter patients’ daily health A must sign in with their ID and password. Lockouts after 5 repeated failed attempts. Tablets can only be used inside care center premises.ReliabilityAll the functions in the App Version (Tablet) works as intended with minimum to no error.Reliability is measured by the downtime from second to minutes. The system should not be down for more than 15 minutes out of 24 hours.Table 6-2: Non-functional Requirements (Tablet)7.0 USE CASE DIAGRAMRevision: The Use Case Diagram is used to help readers understand the system functions and what they can do. The notation used in use case diagrams are a stick figure (actor), an association line, a system boundary, and the Use Case. The actor is a displayed as a person using the system. The system boundary is to show that each Use Case can be executed while in that system. The Use Case shows a specific requirement or action the system can do. An association is a line that connects the actor and Use Case, showing that that user can do that action. Figure 7-1: Standard Use Case Diagram7.1 Mobile Use Case DiagramMobile VersionThe Mobile version of LTC-TMS will be used by CNAs and the patient’s families on iOS and Android devices. Within the Mobile version, families and CNAs are able to select task instruction types and view task instructions on the task instruction page. Families and CNAs are able to view the Daily Status Record page and select status records to view. In addition, families and CNAs are able to view and enter portfolio information and view the announcement board on the home page. The CNA is able to view the center’s schedule, working schedule, and number of hours worked for the month. The families and CNAs are able to send feedback. Finally, families and CNAs are able to listen to information by clicking on the sound icon and use speech-to-text. Figure 7-2, below, is the Use Case Diagram for the Mobile Version.Figure 7-2 Mobile Version Use Case Diagram7.2 Tablet Use Case DiagramTablet VersionThe Tablet version of LTC-TMS will be used only by the CNAs. Within the Tablet version, the CNA is able to select an individual patient and input data associated with the patient. The CNA is also able to update the patient’s vital status and view patient records. Before the update and information can be submitted, the CNA must also confirm their identity. Once submitting the information, the CNA will then receive a confirmation that the data was entered correctly. Figure 7-3, below, is the Use Case Diagram for the Tablet Version.Figure 7-3 Tablet Version Use Case Diagram8.0 USE CASE DESCRIPTIONS Table 8-1 is a fully developed use case description of a CNA viewing a task instruction document in the mobile app. The table follows the use case starting with the scenario and ends with the post-conditions.Use Case NameView Task in Mobile AppScenarioView a task in the mobile app.Triggering EventCNA needs to display patient task instructions.Brief DescriptionTask Instructions are made available to assist patients in performing tasks. After opening the application, logging into the application, and selecting the appropriate option from the hamburger menu, the CNA is able to show the patient the instructions.ActorsCNA, FamilyStakeholdersCNA, FamilyPre-ConditionsCNA must have valid login credentials.Task instructions have to be in the A has logged in.Post-ConditionsSystem has to output the task instructions requested by the user.Use Case NameView Task in Mobile AppFlow of ActivitiesActorSystemCNA selects hamburger icon.System displays menu page.System lists menu A selects “Task Instruction” menu buttonSystem displays Task Instruction pageSystem displays list of Task A selects desired task instructionSystem displays detailed Task Instruction page.System displays a “Proceed” A selects the “Proceed” buttonSystem opens an HTTP(S) link through the default web browser of the device.Default web browser will download or display the file.Exception ConditionsNo Internet access prevents login and database retrieval.Login credentials are invalid.Desired Task Instruction has not been uploaded by CNO/Director.Table 8-1: Use Case Description of View Task in Mobile AppTable 8-2 shows the fully developed use case description for the “update the patient’s vital status”. The CAN is able to update a patient’s vital status on tablet. The table follows the use case starting with the scenario and ends with the post-conditions.Use Case NameInput Patient’s VitalsScenarioCNA required to input patents vital status.Triggering EventRecording is required after CNA checked on patient’s vital status.Brief DescriptionCNA selects a patient and a room number. From the selection page, CNA selects the vital status page. CNA inputs the vital status records, signs his/her staff ID before submits the data. Then the system sends the data to the database.ActorsCNAStakeholdersCNAPre-Conditions1. CNA has to collect the raw data from the patient. Post-Conditions1. CNA must fill out his/her staff ID2. Vital status must be delivered and stored in the database. Use Case NameInput Patient’s VitalsFlow of ActivitiesActorSystem1.1 CNA selects a room number 1.2 CAN selects a patient 1.1 System displays patient(s) within the selected room number1.2 System directs CNA to status selection page.2.1 CNA select the vital status page from status selection page2.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 submit3.2 CNA selects confirm on the alert box.3.1 System alerts CAN with selection of confirmation on submission or edit data.3.2 System sends the data to the database and directs CAN back to status selection page. Exception Conditions3.1 CNA did not fill in his/her staff ID or inputs an invalid staff IDTable 8-2: Use Case Description of Input Patient VitalsTable 8-3 shows the fully developed use case description for the “view LTC Facility Announcements”. The director sends out a notification that can be viewed on the mobile app by the CNA and families. The table follows the use case starting with the scenario and ends with the post-conditions.Use Case NameView LTC Facility AnnouncementsScenarioEvent or special occasion that is going to happen at the LTC facility.Triggering EventThe director writes and publishes the announcement from the browser version.Brief DescriptionThere is some sort of event or special occasion the Director wants all the family members and CNAs to know about and sends out a notification describing it.ActorsCNA, FamilyStakeholdersCNA, FamilyPre-Conditions1) There is an event or special occasion that is going to happen.2) The director has written and sent out the notifications.3) CNA or family member has logged in.Post-Conditions1) System must output the announcement.Use Case NameView LTC Facility AnnouncementsFlow of ActivatesActorSystemCNA or family selects hamburger icon1.1 System displays menu page.1.2 System lists menu A or family selects “Announcements” menu button2.1 System displays Announcements page2.2 System displays list of past A or family selects newest or desired announcement.3.1 System displays the selected announcement.3.2 System has a “go back” A or family selects “go back” button.4.1 System will go back to announcements page.Exceptions ConditionsNo internet access prevents login and database retrieval.Login credentials are invalid.Table 8-3: Use Case Descriptions of View LTC Facility Announcements Table 8-4 is a fully developed use case description of Families sending patient feedback in the mobile app. The table follows the use case starting with the scenario and ends with the post-conditions.Use Case Name Send feedbackScenario Family sends feedback of patient care on the mobile app.Triggering Event Family needs to be on the feedback page.Brief Description The Family will send feedback on the patient’s care.Actors FamilyStakeholders FamilyPre-Conditions Family is on the feedback screenFamily ID must be input to confirm identity Post-Conditions The system sends the feedback to the CNAs. Use Case NameSend feedbackFlow of ActivitiesActorSystemFamily selects feedback. 1.1 System displays the feedback page.Family types feedback in textbox. 2.1 System acquires the feedback in the textbox.Family clicks on “send feedback” button. 3.1 Feedback gets sent to the CNA.Exceptions ConditionsNo internet access prevents login and database actions.Login credentials invalid.Table 8-4: Use Case Description of Families Sending Feedback ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download