Homework 1 PDF

Preview

Summary

Homework 1, CIS 3374, Dr. Peiqin Zhang ...

Description

CIS 3374 9/13/2018 Homework 1: Sandia Medical Devices 1. Who are RTGM’s stakeholders? Should NMHS’s patients be included in defining the system requirements? Why or why not? Should RTGM interact with medical professionals other than physicians? Why or why not? (30 pts) Stakeholders include: 

Patients (users of the monitoring device and of the phone application)



Doctors (users of the information transmitted)



Other hospital medical staff (those who enter patient medical information on phone app)



Medical equipment engineers (developers of the mobile monitoring equipment)



Technical staff (developers of the central server system, and the database)



Project team members (developers of the actual phone app itself)

Patients should be included in defining system requirements for those areas that impact their use. This includes the medical device (comfort, wear ability, maintenance) and the phone app (installing, executing, user interface screen). Overall patients are some of the most important stakeholders, for the product is used and tested on them to help the process run smoothly. Other medical professionals other then physicians may need to be involved. This would include medical staff that are involved in the design of the device (is it sensitive enough to read glucose levels, etc.). Other medical professionals may want to research results for medical studies. As such they will dictate what data should be captured. 3. What are the primary functional requirements for the system as described so far in the case? (35 pts) 5 functional requirements include: Enter user (patient) information Test monitoring device Receive monitor-device data Send monitoring data to server Receive data from server

Alert patient (user) or abnormal situation 5. Briefly describe some possible nonfunctional requirements for RTGM. (35 points) Non-functional requirements: qualities which must be maintained by the software during development (also known as quality requirements) Usability 

The user interface must be very easy and user-friendly (patients’ age/experience/knowledge may vary)



Online Tech Support should be available to patients who are less tech-inclined (easily accessible) – RTGM system

Reliability 

Have as little downtime as possible, emergency situation can happen anytime – error in system could result in the loss of a patient’s life.



The System should have a form of back up, fail-safe technology that where a timer can be added. This way the patient can be alerted from a signal sent to the mobile phone device.



Have quick recoveries; if there is some sort of incorrect processing, how the system detects this incorrect processing and how it recovers from these issues – if system fails, should be indicated on the mobile phone.

Performance 

How much load the system can handle at one given time (Should be able to handle X amount of simultaneous client sessions at once in order to be a successful working system)



How long is the response time to corresponding button presses when using the mobile device? (The ease of use for the patient)

Security 

System server contains some private information held by the patients which can be sensitive: need heavy security



How will access to the app be controlled and protected? System must follow HIPAA rules and regulations



Will data be encrypted locally? Password protected? What process will the data be sent over to make sure it is sent securely?



Don’t want any interference between monitoring devices

The “+” requirements 

Design constraints: What must the hardware and software adhere to?



What are the requirements for each phone OS? Will Android and iOS hit the market at the same time? Use the same amount of memory? Will a certain OS be

more important to focus on? Some sort of updates as they move along?...