Home

System Test Plan (Wireless Blood Pressure Monitoring System)

1. e Account is successfully created when e Account not created successfully meaning entering valid data errors have occurred in the process at some y point e Advice is displayed is calculated correctly e Advice is not shown or does not match the data e Reading is successfully taken and the results e Reading does not get to the database or is are stored in the database stored incorrectly Bluetooth connection fails User cannot see result on the website for a whatever reason March 25 2014 70 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 8 6 Validation Tests Table 8 5 Validation Tests Pass Fail Criteria ee Fail Criteria 4 4 e Account is successfully created and e Account cannot be created errors when trying information is edited without issue to resume the setup of a patient account or issues with trying to edit account information AE e Patient sees advice that is correct based on e Patient cannot see advice or the patient s their blood pressure data advice does not accurately reflect their blood pressure data and other data EI m 34 e Phone should connect to the BPM within 10 e Phone does not successfully connect within seconds and the phone should connect to the these times server within 30 seconds March 25 2014 71 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 9 Test Deliverables 9 1 Overview This section will describe what the team
2. i 17 Security STT 18 Other UI eee ria 20 Chent ayer Data Flow aan 25 Client Layer Requirement Mapping seen nemen nnne 26 Transport Layer Data FIOW i teet rtt rrr emitter tene etra aera dat 27 Transport Layer Requirement Mapping eese een en rennen 28 Business Logic Layer Data Flow EE 29 Business Logic Layer Requirement Mapping esee emen 30 Data Storage Layer Data Flow eir aaa rali 31 Data Storage Layer Requirement Mapping eene enne 32 lobi ME EUR 34 Browser Display Unit R iacit rn terere ici caia 34 Web Validation Unit Tests decr tecta perte dadas Footer ipte nb te de dide ngo tias 34 Chart Generation Unit Tests eerte eid ete ene 35 Application Ul Unit Tests inet c e 35 BPM Validation Unit Tests acilia 35 Data Packet Processing Unit Tests eiie eer entretenu raten aa eaae 35 Bluetooth Communication Unit Tests 36 Request Encryption Unit Tests eiie nite ica 36 Response Decryption Unit L ests pini einer ias 36 Client Server Communication Unit TestS ene nenn nemen 36 Request Decryption Unit Tests eterne rin tne bera ener er ie eti aad EE 37 Permission Authentication Unit Tests i 37 Response Encryption Unit Tests errar emen rennen nre nennen 37 Request Delegation Unit Tests iiie ea 37 Analysis Controller Unit TEStS visiere rinitni ai 38 Analysis Command Unit Tests 38 Data Pr
3. Sever Log Any error message that is being generated by the server because of bugs defects Stack Trace Any stack trace or error logs output generated by testing environment program Tester Comments Any comments the tester wish to provide for future reference or explanation 9 4 Test Code The code for all automated testing shall be provided and document for future regression testing This code will include any codes written for unit component and integration testing All code will be properly commented and documented and delivered with the final product March 25 2014 73 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 10 Test Schedule Table 10 1 Test Schedule Task Name Planned Start Date Planned Due Date Hardware Testing Thu 3 27 14 Mon 3 31 14 Blood Pressure Monitor Testing Tue 3 25 14 Mon 3 31 14 Database Testing Tue 3 25 14 Mon 3 31 14 Server Testing Tue 3 25 14 Mon 3 31 14 Account System Test Fri 3 28 14 Fri 4 4 14 Login System Test Fri 3 28 14 Fri 4 4 14 Android Application Test Fri 3 28 14 Fri 4 4 14 Graph System Test Wed 4 2 14 Sat 4 5 14 System Integration Test 1 Wed 4 2 14 Mon 4 7 14 System Validation Test Fri 4 25 14 Thu 5 1 14 March 25 2014 74 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 11 Approval Table 11 1 Approval Table Name Role Sigature EA Mike O Dell Project Supervisor Benjamin Bloom Team Member aiae aaa Sabreen Team Member
4. This is intended to ease deployment onto the client s intended web servers Web Service The web service will be able to be able to be 3 Moderate Software Update modified without having to reboot the operating Effects system or web server e g Apache There is no guarantee that the web application itself will not restart Web Service The web service shall have a portal for the system 3 Moderate Administration Layer administrators to manage the basics of the web portal so that the source of the web application does not need to be modified and redeployed This includes website wide notifications alerts the ability to enable disable certain services and enabling disabling the entire web application March 25 2014 17 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 2 6 Security Requirements Table 2 6 Security Requirements Data Transport The web service shall encrypt all data particularly 1 Critical Encryption PHI that is transmitted between the blood pressure monitor and the data collecting web server This requirement is primarily focused on the level of the communication between monitor client and the web server and not the WLAN connection see 8 5 Integrity The system will attempt to prevent any PHI that will 2 High be collected and stored from the user from unauthorized modification or corruption and ensure its validity This requirement may rely on storage encryption section 8
5. 24 Client Layer Component Test ID Subsystem Imput Output Test Risk o nt retro O 0460 Web IO e HTML elements e Boolean True False Check that invalid datais High Processing not being accepted lg pe ee SIS WOR BPM UI e User input e Updated display Check that subsystem High response correctly to user actions n ee ima I 3 4 2 Transport Layer Component Test Table 3 25 Transport Layer Component Test Output n C VIR Network e Http Request e HTTP Response Check that data is being High Transport sent between the client and the server B ias March 25 2014 41 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 3 4 3 Business Logic Layer Component Test Table 3 26 Business Logic Layer Component Test m BLSC 1 IN Data e AnalysisDataPool e AnalysisControll Check that analysis High Lon Analysis object er object results match the input data BLRC 1 3 4 4 Data Storage Layer Component Test Table 3 27 Data Storage Layer Component Test ID Subsystem Input Output Test Risk o PARES IE Database e DataCommand s Encrypted Check that data being High Security object DataCommand stored is encrypted and object data being retrieved is decrypted uk LU rM March 25 2014 42 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 3 5 Integration Tests Table 3 28 Integration Tests LID Features Input Output Test Risk I
6. 3 Data Analysis Controller Controller E B Storage Controller Database Interface Database Figure 2 1 Architecture Diagram March 25 2014 21 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 3 1 Client Layer The Client Layer is meant to deal with all things related to the portions of the system that users will interact with specifically the BPM and the website The layer takes its name from the client portion of the Client Server model upon which we are basing our architecture and will act similarly to a client in the Thin Client model This layer s main focus is providing a consistent user friendly interface that will allow users to consume the data that they need as well as to input information and receive the output that results from this In addition this layer will handle some basic processing of input that needs to be handled on the client end of the system either for safety or performance purposes such as validating input to eliminate bad data as well as processing the signals from the pressure sensors in the cuff and responding appropriately The Client Layer will take in input directly from the user or hardware whether that be sensor data configuration changes blood pressure readings or others and will either directly respond to the user or hardware or will pass the data down to the Transport Layer at which point it will wait for the Transport Layer to send response data for it to display 2 3 2
7. 4 and authorization protocols section 8 2 to deter unauthorized modification Storage Encryption All PHI data that is being stored or archived will be 2 High encrypted and intended for storage of a minimum of five years In general the data will be encrypted using symmetric encryption of at least AES 128 strength The encrypted data can only be decrypted and accessible by users with the appropriate keys The keys will further be protected using a form of public key encryption This requirement would also further enforce the protocols of authorization section 8 2 on PHI data 8 Disposal Guarantee PHI data when found necessary to remove from the 4 Low system will be effectively purged This guarantees that when the system removes the data from its oversight it would be thoroughly deleted from itself and all of the system s underlying dependencies If a Authorization The collected PHI data will only be accessible to Critical authorized personnel using audited access controls Mechanisms will be designed and implemented to ensure that data can be accessed only by appropriate users This requirement may rely on storage encryption section 8 4 to prevent unauthorized access as well as on the web hosting vendor to comply with the HIPAA Business Associate section 8 7 to maintain control over low level access to the web server s functionality 8 1 8 2 8 3 A data backup system is implemented section 8 7 then this re
8. Account Creation 3 13 Patient Account Creation 3 14 Patients Doctor 3 15 Doctor Limit 3 16 Doctor Editing 3 17 Patient Editing 3 18 View Charts and Graphs 3 19 Annotations 3 20 Patient Viewing Profile March 25 2014 Wireless Blood Pressure Monitor Doctors will be able to create their own account on the web service Doctors will create patient profiles and have them connected to their own The doctor will enter medical information and other key information about the patient s health The system with the doctor s permission will then send an email to the patient s email address with temporary login information The patient will then change their login credentials add their personal information if they wish and confirm the changes A person who wishes to use this system as a patient must be affiliated with a doctor or caretaker who has an account on the web service A patient may only have one doctor account tied to their account on the web service If the patient wishes to have more doctors view their data those doctors will have to use the patient s viewing account to see the information Doctor accounts can have their information edited by the account holder Profile information email password full name can be edited by the given patient Medical information will be edited by the patient s doctor All registered users on the site will be able to view various charts and graphs on the website that descri
9. Flow Description HTTPServletRequest and HTTPServletResponse Object Ld d DINIS Un N m HTTPServletRequest and HTTPServletResponse Object HTTPServletRequest and HTTPServletResponse Object Data that has been formatted in JSON keck KZ Boolean response of true or false March 25 2014 27 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 4 2 1 Transport Layer Requirement Mapping Table 2 11 Transport Layer Requirement Mapping BRENO delia Di ba dues RO e Am 3 5 User Authentication X x x x x x 3 7 View Results 3 8 Multiple Readings 3 9 Result Transmission and Storage X X X X X x 3 1 Web Service x x x x x x 3 11 Account Types X 3 12 Doctor Account Creation X x x x 3 13 Patient Account Creation X X x x 3 14 Patient s Doctor x 3 15 Doctor Limit x 3 16 Doctor Editing X x x x 3 17 Patient Editing X X X x 3 18 View Charts and Graphs x x 3 19 Annotations x x 3 2 Patient Viewing Profile x x 3 21 Create Alerts X X 3 22 View Alerts x x 3 23 Messaging System x x 3 24 Multiple Users x 3 25 Login to Access Data x x 3 26 HIPAA x x x x x x 3 27 Advice System x x 3 28 Manual Upload x x 8 1 Data Transport Encryption x x X X 82 Authorization X x x 8 3 Integrity X x x x x x 8 4 Storage Encryption 8 5 Disposal Guarantee 8 6 WLAN Connection Security X X x x x 8 7 Data Backup March 25 2014 28 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 4 3 Business Logic Layer Da
10. Il Account Creation D Advice 13 Blood Pressure Reading March 25 2014 e Form with account information e User home page Advice button click User advice page e Login credentials e Bluetooth address e BP reading e Login success message or error e Pairing success message e BP reading e Graph 43 Tester will enter account information System should validate input send to server store data and respond with the account s home page Tester will log into system and click on Advice button System will send request to server check that tester has role permission for that page gather tester s data analyze the data and send back advice Tester will login on the system s application They will then click the Start button on the BPM take their blood pressure pair the BPM with their phone send the data to their phone and then transmit the data to the server Finally the tester will login on the website click on the Graphs link and see the new reading added to their latest charts High High High Beta Blockers System Test Plan Wireless Blood Pressure Monitor 3 6 System Validation Tests Table 3 29 System Validation Tests iii ER RH E I e 3 5 e BP reading Tester will take a blood pressure High e 3 6 e Transmission reading and send it to their phone e 3 7 message and then to the server If 3 8 e Health alert necessary an alert will be sent to 939 optional th
11. Transport Layer The Transport Layer as its name suggests handles transporting data from the client to the server and back in our architecture from the Client Layer to the Business Logic Layer Its main purpose is to make sure that this data reaches its destination in a safe and secure manner To do this the layer has to deal not only with the actual transporting of the data through the use of various network protocols but also with securing the data to make sure that everything going through the network cannot be intercepted and used in harmful ways It also needs to make sure that the data being delivered to the receiver is able to be used which means going through another layer of security after transporting it to restructure the data to make it useful The Transport Layer takes its name from the major functions it provides It takes a request from the Client Layer and passes it to the Business Logic Layer and it gets a response from the Business Logic Layer and passes it back to the Client Layer To put it in simple terms it packages the materials ships them and then un package them This is one of the simpler layers of the system s architecture but due to the team s emphasis on security and privacy it is a key layer and because of the team s choice to structure the architecture in a Client Server fashion this layer provides the crucial connection between the two 2 3 3 Business Logic Layer The Business Logic Layer is tasked with doing
12. X X Beta Blockers System Test Plan Wireless Blood Pressure Monitor 3 Test Items 3 1 Overview The following section will provide details about how the team plans to test the system Starting with the hardware going to unit tests and then gradually moving up to include more components at every stage the team will ensure that each portion of the system is working individually and in collaboration with each other to ensure that the system is functioning properly and to verify that the system meets the standards set forth at the beginning of the project HARDWARE SYSTEM E VERIFICATION Application UI BPM User Interface Blood B Data Packet Processor Monitor eo E i Web User Interface i Weblo Processing BPM Validation Browser Display Chart Generation S Client Client Security L 1 d BlooData Network Transport f Transport Wireless Blood Pressure Monitor d System semersecaty E Request Delegation j System Controller Analysis Control li 1 D Web Validation Request Encryption Response Decryption Client Server Comm E Request Decryption i Response Encryption Analysis Command ata Analysis Page Generator i Response Controller Data Preparer Storage Delegation Storage Controller Cryptography mg g Database Security Data Storage Database Get 1 Databas
13. data is successfully loaded BLDP3 March 25 2014 68 e Incorrect no web page shown e Incorrect text is show e Incorrect nothing is shown e Animation not shown or incorrect e Bad input is let through e Incorrect no chart is display e Elements do not respond appropriately e Text does not display correctly e Incorrect response message is displayed e Data is not sent e Valid input is flagged as invalid or invalid input is being accepted e Problems translating or handling invalid packets e Phone does not receive packets or packets are corrupted e Packets not encrypted e Packets not decrypted e Server is unreachable or data is not being sent properly e Packets not decrypted e Requests are forwarded when user does not have permissions or error pages are being sent to legal users e Packets not encrypted e Request is directed to an incorrect servlet e Errors occur while constructing DataPool e Command objects are constructed that should not have been or fail to be constructed when they should have been e Errors with the storing of results e Incorrect results e Objects fail to get formatted or do not fit the needed format e Incorrect pages or pieces of data are being returned e Errors with the generating of JSP pages Beta Blockers System Test Plan Wireless Blood Pressure Monitor BLDC1 e Correct command objects are built e Command objects are constructed that should not have been or fa
14. device will be operated via battery power 3 Moderate Batteries will not be packaged with the device Connection Cable Connection cable will be provided to manually 5 Future upload the data on to a computer and uploaded to the website if wifi is not available User Manual A user manual will be provided with the product 2 High The manual will contain detailed information regarding the product website and how to operate the device E h La March 25 2014 13 Beta Blockers System Test Plan 2 2 3 Performance Requirements Wireless Blood Pressure Monitor Table 2 3 Performance Requirements SRS No 5 51 5 2 3 5 4 5 5 5 6 5 7 5 8 Storage Conditions Operating Conditions Operational Battery Life WLAN Authentication Latency WLAN Connection Failure Response Time Web Authentication Latency Blood Pressure Monitor Consistency Regarding Battery Life Blood Pressure Monitor Accuracy March 25 2014 The blood pressure monitor shall maintain the performance requirements specified in this document after being stored for 24 hours at 21 C 70 F give or take 10 C variance and at a relative humidity lower than 90 noncondensing The blood pressure monitor shall maintain the safety and performance characteristics specified in this document during operation over the following ranges of environmental conditions a Temperatures between 11 C and 31 C b Relative humidity under
15. e Keyboard e Text display UI Application e Touch input e Text dialog UI Table 3 6 BPM Validation Unit Tests BPM e Text field e Error message if Validation invalid e None if valid Table 3 7 Data Packet Processing Unit Tests Data e Byte packet e Hexadecimal integer Packet representing the byte Processing March 25 2014 35 Wireless Blood Pressure Monitor Request graph for High particular patient Touch elements on the High android screen Type into text fields and High input is displayed on the android screen Click send data button High and responds with a success or fail message Input invalid data into High field submit Input valid data into field submit Input Valid byte packets High and verify translation to hexadecimal is accurate Input Invalid byte packets and verify that the invalid bytes are handled correctly and proper message is displayed Beta Blockers System Test Plan Table 3 8 Bluetooth Communication Unit Tests Bluetooth e Byte stream e Byte packet Communication Table 3 9 Request Encryption Unit Tests Request e HttpConnection e Encrypted Encryption object HttpConnection object Table 3 10 Response Decryption Unit Tests Response e Response e Web page or data to Decryption Decryption be decrypted Table 3 11 Client Server Communication Unit Tests Client Server e Encrypted e Encrypted web Communication HttpConnection page or data to be object sent to
16. in and retrieved from the database Without the Data Storage Layer either the Business Logic Layer would have to pick up the slack resulting in a very complex and dense layer or there would be no interfacing with the database meaning that no data could be saved and any features that rely on long term data would be lost The Data Storage Layer is the heart of the system it determines who gets what data and distributes it to keep the system functional The Data Storage Layer can only be accessed through the Business Logic Layer These two layers work together to form the core of the server model one would see in a Client Server Model The Business Logic Layer handles what the server needs to do The Data Storage Layer handles what the server needs in order to do that The Business Logic Layer will send the Data Storage Layer a request that states what the Business Logic Layer needs to do what process it wants to run and any input data that would accompany this the Data Storage Layer figures out exactly what the Business Logic Layer needs to do this it interacts with the database to get or store this data and is pushes the data or the database response back to the Business Logic Layer 2 4 Detailed Design Specification The DDS further breaks down the architecture specified in the ADS This is the furthest the architecture and the design of the system get broken down which result in the smallest components of the system modules These modules li
17. in different area and time the time it takes to connect to the wifi in that region As well as test the android application in definite non connectable are and verify that the application properly notify the user of connection failure Bluetooth Connection Description The android application interface to the BPM will take no longer than 10 seconds to attempt a successful connection After 10 seconds the android application will cease the connection activity and notify the end user of the current status of the Bluetooth connection Risk Medium Test Approach The team will execute multiple connection tests in different area and time the time it takes to connect to the wifi in that region As well as test the android application in definite non connectable are and verify that the application properly notify the user of connection failure Blood Pressure Cuff Accuracy Description The blood pressure measurements obtained using the monitor shall not deviate more than 10 at any measurement range from an existing commercial blood pressure monitor Risk High Test Approach The team will run multiple test sessions on the blood pressure cuff Each reading will be compared to another standard blood reading machine or manual method and ensure that the cuff have a consist accurate and reasonable reading March 25 2014 52 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 5 Safety Requirements 5 5 1 5 5 2 Blood Pre
18. noncondensing 90 The blood pressure monitor shall maintain the performance characteristics specified in this document for at least 30 minutes while running the measurement acquisition process continuously The blood pressure monitor interface to the end user s wireless local area network WLAN will take no longer than 10 seconds to attempt a successful connection After 10 seconds the blood pressure monitor will cease the connection activity The blood pressure monitor interface to the end user s wireless local area network WLAN will take no longer than 10 seconds intervene appropriately and notify the end user of the current status of the WLAN connection The blood pressure monitor interface to the internet and to the web service will take no longer than 30 seconds to attempt a login After 30 seconds the system will cease the login activity The blood pressure monitor will still be able to take consistent readings until the device detects that the battery s voltage is too low to continue normal operation The variation in blood pressure readings shall be confined to within 15 accuracy The blood pressure measurements obtained using the monitor shall not deviate more than 10 at any measurement range from an existing commercial blood pressure monitor 2 High 2 High 2 High 2 High 2 High 2 High 2 High 2 High 14 Beta Blockers System Test Plan Wireless Blood Pressure M
19. parer Unit Tests 38 Page Generator Unit e uie ptio iaia 39 Data Controller Unit Tests nei ciance 39 Cryptosraphy Unit Tests 39 Database Get Unit KEE 40 Database Update Unit Tests eicere tinere re aor tg ti vere cuca ga Saito 40 Chent Layer Component L estate lia 41 014 6 Beta Blockers System Test Plan Wireless Blood Pressure Monitor Table 3 25 Transport Layer Component Test 41 Table 3 26 Business Logic Layer Component Test en rennen 42 Table 3 27 Data Storage Layer Component Test eene rennen 42 Table 3 28 Integration Tests P 43 Table 3 29 System Validation Tests eene nennen nnne rennen enne 44 Table 4 1 Table 7 1 Table 8 1 Table 8 2 Table 8 3 Table 8 4 Table 8 5 her eil c 46 Suecess and Failure Metrics eL een ten Hee npe nrbe an phase O SN npa eue gna Rs 66 Hardware Tests Pass Fail Criteria ii 67 Unit Tests Pass Fail Criteria Loire tiere re Leere n teet n et a I rn FERE pner Ux 68 Component Tests Pass Fail Criteria sostenida nhe re etae ha 70 Integration Tests Pass Fail Criteria cre er reiner ENEE 70 Validation Tests Pass Fail Criteria i 71 Table 11 1 Approval Table 75 March 25 2014 7 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 1 Introduction 1 1 Document Overview The System Test Plan STP provides
20. that its functionality is HIPAA compliant 19 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 2 7 Other Requirements Table 2 7 Other Requirements Web Browser The web interface shall be accessible and usable 1 Critical Compatibility through popular web browsers for the user caretaker physician and administrators Such web browsers would include Internet Explorer Mozilla Firefox Google Chrome and Safari Blood Pressure The blood pressure monitor device s source code 1 Critical Monitor Source shall be compatible with Windows 7 development Compatibility environments for implementation deployment and maintenance 9 3 Web Service Source The source code of the web service functionality Critical Compatibility shall be compatible with Windows 7 and popular Linux development environments for implementation deployment and maintenance Smartphone Device Any implementation of functionality for mobile 4 Low Constraint devices mainly smartphones will be constrained to Android 3 0 and Unix type operation systems This is due to their accessibility and availability of their tools The choice of Android 3 0 and up is due to fl their available and compatible feature set for this project 9 5 Multiple Health The website will be able to support many different 5 Future Modules for Website sets of data from many different pieces or hardware such as blood sugar readings or weight measurements to al
21. Alabedredha Stren ren March 25 2014 75 Beta Blockers
22. Blood Pressure Monitor 5 7 Security Requirements STL 5 7 2 5 7 3 Integrity Description The system will attempt to prevent any PHI that will be collected and stored from the user from unauthorized modification or corruption and ensure its validity This requirement may rely on storage encryption section 8 4 and authorization protocols section 8 2 to deter unauthorized modification Risk High Test Approach The team will test to make sure each data inputted into the database will be the same as when it s retrieved for both unencrypted and encrypted insert update s Authorization Description The collected PHI data will only be accessible to authorized personnel using audited access controls Mechanisms will be designed and implemented to ensure that data can be accessed only by appropriate users This requirement may rely on storage encryption SRS section 8 4 to prevent unauthorized access as well as on the web hosting vendor to comply with the HIPAA Business Associate section 8 7 to maintain control over low level access to the web server s functionality Risk Critical Test Approach The team will test access restriction of each user type guest patient and doctor Each user type will test its individual functionally and ensure each user type has access to their specific user type Storage Encryption Description All PHI data that is being stored or archived will be encrypted and intended for storage of a mi
23. Department of Computer Science and Engineering University of Texas at Arlington Beta Blockers Wireless Blood Pressure Monitor System Test Plan Tan Jungmann Hao Nguyen Scott Phan Benjamin Bloom Sabreen Alabedredha System Test Plan Wireless Blood Pressure Monitor Table of Contents il able of Contents aiar Ae 2 Document Revision History ao 4 EE ed caccia 5 PASTOR KEE 6 UN ege Te e EE 8 LL Document Overview P 8 1 2 Product OvervieW band aaa anale 8 1 re een 8 PSI I 10 MM S 10 2 2 System Requirements Specification ii 10 2 3 Architectural Design Specification esee 21 2 4 Detailed Desien SpecifiCationi oreet ne iaia 23 De WSU GINS orcs bag EE 33 De OVI NASW esac innate 33 3 2 Hatdware A a 34 33 Unit Tests M EET 34 34 Component Tests IEEE 41 3 3 Integration L NEEN 43 3 6 System Validation Test ras et deter itte teer pe i laica 44 Z RISKS centeno cU iine ilm MP E M EE 46 K O M 46 4 1 Table of RISES ias assa Lm 46 5 Features to Be Tested uiui tiende a ao 47 SNO OUI LE 47 5 2 Customer Requirements etit Fe iaia 47 5 3 Package Requirements iaia E 51 3 Safety Requirements rica ea Sued thus ou vue aed dic 53 5 6 Maintenance and Support Requirements nennen ne
24. Send AnalysisController High DataController Httpservletrequest and Httpservletresponse objects ensure that correct page or data is dispatched Send AnalysisController High DataController Httpservletrequest and Httpservletresponse objects ensure that data is being loaded into the response correctly Beta Blockers System Test Plan Wireless Blood Pressure Monitor Table 3 19 Page Generator Unit Tests ID Module Output B wu ccn Een 3 3 4 Data Storage Layer Unit Test Table 3 20 Data Controller Unit Tests LD Module Input a Test Risk E sen col ESS E DOA Data e StorageDataPool e DataController Send StorageDataPool High Controller object object ensure that results being stored correctly Table 3 21 Cryptography Unit Tests JD T Module Eee i T Output Test Risk E NALE M BI 110 Cryptography e DataCommand e DataCommand Send DataCommand object object with object to get PHI data decrypted data ensure that data being returned is properly decrypted March 25 2014 39 Beta Blockers System Test Plan Wireless Blood Pressure Monitor Table 3 22 Database Get Unit Tests ID Module Input Output Test Risk ni LE E MI ae Table 3 23 Database Update Unit Tests ID Module Output o e Cit R ce ita ae March 25 2014 40 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 3 4 Component Tests 3 4 1 Client Layer Component Test Table 3
25. Test Plan Wireless Blood Pressure Monitor 5 3 Package Requirements 5 3 1 5 3 2 5 3 3 5 3 4 Blood Pressure Cuff Description The product will be packaged with a standard blood pressure cuff The cuff will weigh between Y 1 pound and will be fitted for arm circumference of 9 14 inches Risk High Test Approach The team will weigh the cuff and verify that the weight is with 2 1 pound and fit the cuff on various arms of members on our team and a few selected individual to cover all arm width Android Application Description An android application will be provided via Google play store The application will allow the user to interact with the blood pressure cuff to authenticate take blood pressure reading and send the readings to the website Risk High Test Approach The team will install the android application on multiple phones After which we will initiate multiple tests by login to the android application take multiple blood pressure reading with the application and send the readings from the application to the server After which the team will verify that the readings have been properly saved into the database Software Packaging Description All software will be installed prior to packaging No set up will be required by the Patient Risk High Test Approach The team will have the sponsor test our system by creating an account on our web services and download our application From which we will have the sp
26. aint of the project as well as full compliance with HIPPA standard cannot be met with our current development time Manual Upload of Information Description In the case where a patient s wireless connection goes down or begins to suffer problems the device will store the patient s readings for a set amount of time The patient will then be able to manually upload the readings using a computer if they feel that the wireless connection will not resume working in the near future March 25 2014 57 Beta Blockers System Test Plan Wireless Blood Pressure Monitor Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested 6 3 Package Requirement 6 3 1 6 3 2 6 3 3 6 3 4 Blood Pressure Monitor Description The product will come packaged with a monitor which is attached to the cuff Tt will be the interaction point between the patient and the system The patient can authenticate take blood pressure reading view current readings in the session and send blood pressure readings to the website The Monitor will be a 3 x 4 inch display and will weigh no more than 6 ounces Reason This requirement will not be tested due a design choice of the team to construct a android application instead of building a monitor Android Phone Description The product will require an Android phone which will not be packaged with the product The phone will use the Android application to interact with
27. allow the team to make a final determination as to whether the product is acceptable or not 2 2 1 Customer Requirements Table 2 1 Customer Requirements 3 1 Non invasive Blood Pressure Monitor will take readings in a non 1 Critical E Measurements invasive manner Oscillometric Method Blood Pressure Monitor will use the oscillometric 1 Critical method to evaluate blood pressure Automatic Blood Pressure Cuff will automatically inflate and 1 Critical Inflation Deflation deflate Cuff Location The Blood Pressure Cuff will be worn on the upper 1 Critical or lower arm 3 5 User Authentication An authentication system will be used before 1 Critical EE all sessions to ensure user security Blood Pressure The device will measure the blood pressure of the 1 Critical Reading user it is attached to 3 7 View Results Users will be able to view their results on the 1 Critical A monitor Multiple Readings Users will be able to record and submit multiple 2 High readings in a session Result Transmission The monitor will transmit the blood pressure results 1 Critical and Storing to the website s database for storage 3 10 Web Service A web service will be created to display results 1 Critical handle users and house other features 3 11 Account Types The web service will support two types of accounts 1 Critical patients and doctors March 25 2014 10 Beta Blockers System Test Plan 3 12 Doctor
28. be the patient s blood pressure conditions overall health and other factors assuming that they have access to said patients information Patients registered on the site will be able to make notes about particular readings of theirs on the website to relay information such as changes in their health or lifestyle All patients will have a viewing profile a way in which friends family members other doctors or anyone else the patient wishes to give access to can view how the patient is doing and other information This profile is separate from the standard Patient profile it will be tied to the account with a separate set of login credentials and it is extremely limited in functionality The patient will be able to change the login credentials for this at any time to restrict access 1 Critical 1 Critical 1 Critical 1 Critical 3 Moderate 1 Critical 1 Critical 2 High 3 Moderate 11 Beta Blockers System Test Plan 3 21 Create Alerts 3 22 View Alerts 3 23 Messaging System 3 24 Multiple Users 3 25 Login to Access Data 3 26 HIPPA 3 27 Advice System 3 28 Manual Upload of Information March 25 2014 Wireless Blood Pressure Monitor Alerts can be created either automatically by the system if it detects a problem or a concerning trend or by a patient if they want to alert their doctor about something which will be sent to the doctor for later viewing Doctors will be able to
29. ce will be limited to 12 volts The device will also only use DC type power as its primary source of electrical power Eligible Users The blood pressure monitor shall not be intended for 2 High neonatal users It will be only intended for those who understand how to operate the device safely Blood Pressure The blood pressure monitor primarily the wearable 2 High Monitor components shall not be able to easily induce Mechanical Safety physical injury to the user through its physical form March 25 2014 16 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 2 5 Maintenance and Support Requirements Table 2 5 Maintenance and Support Requirements 7 1 User Manual A general user manual will be created that will 2 High instruct the end user on how to safely operate the blood pressure monitor and access his or her information on the website Blood Pressure The battery on the blood pressure monitor shall be 2 High Monitor Battery replaceable as it will be found on the consumer Replacement marketplace The battery shall also be able to be removed easily from the device by the targeted audience without compromising the safety and performance requirements Web Service The web service software shall be able to be 2 High Software Portability deployed via an automated script that sets up the server software e g Apache MySQL etc and preloads system templates such as database schemas and defaults
30. ctors to easily track patients with a wide variety of conditions or concerns Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested March 25 2014 62 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 6 8 3 Advanced Authentication Capabilities Description The monitor will have advanced authentication capabilities to better ensure that the correct person is wearing the device at all times Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested 6 8 4 Remote Control for Blood Pressure Monitor Description The blood pressure monitor will come with a control that will be used to control the system allowing for more portability and removing the need for a phone or a large box to support the system Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested March 25 2014 63 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 7 Testing Approaches 7 1 Overview The following section will detail how the team plans to organize their efforts in order to test the system in an efficient and controlled manner This will include tools that will be used to test the system the process the team will go through to execute a test and other things that will be needed in order to test the system as quickly and correctly as possible 7 2 Strategy Due to the com
31. cuff will weigh between Y 1 pound and will be fitted for arm circumference of 9 14 inches 4 2 Blood Pressure The product will come packaged with a monitor 1 Critical Monitor which is attached to the cuff It will be the interaction point between the patient and the system The patient can authenticate take blood pressure reading view current readings in the session and send blood pressure readings to the website The Monitor will be a 3 x 4 inch display and will weigh no more than 6 ounces Android Phone The product will require an Android phone which 2 High will not be packaged with the product The phone will use the Android application to interact with the blood pressure monitor device Android Application An android application will be provided via Google 2 High play store The application will allow the user to interact with the blood pressure cuff to authenticate take blood pressure reading and send the readings to the website Software Packaging All software will be installed prior to packaging No 1 Critical set up will be required by the Patient Website The team will create a website that will receive 1 Critical blood pressure readings from the device These readings will be displayed on the website in chart and graph format The patient will be able to annotate view advice regarding the readings send and receive alert messages as well as contact their doctor through the website 4 7 Battery The
32. decided to give a ranking of our results A rating of fail will be given if the feature does not meet the requirements laid out in the SRS A rating of pass will be given if the feature meets our sponsor s expectations for basic functionality A rating of excellent will be given if the feature exceeds the expectations of our sponsor Here are the metrics we will be using Table 7 1 Success and Failure Metrics Security features Core functionality 100 passing g rating A failure rating on any Complexity of Algorithms pi DI Not acceptable to sponso March 25 2014 66 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 8 Item Pass Fail criteria 8 1 Overview The following section will detail how the team will determine if individual tests pass or fail This will allow the team to clearly dictate what is acceptable and what is not in regards to a given portion of the system so that the success or failure of a test is clearly defined 8 2 Hardware Tests Table 8 1 Hardware Tests Pass Fail Criteria Hardware Pass criteria Fail Criteria E m ees Database e Can successfully connect and send SQL e Unable to connect to the database statements to the database e Receive corrupted data from the e The correct result sets or exceptions are database returned SS E E March 25 2014 67 Beta Blockers System Test Plan 8 3 Unit Tests Table 8 2 Unit Tests Pass Fail Criteria Wireless Blood Press
33. details regarding how the Wireless Blood Pressure Monitoring System will be tested to ensure that requirements have been met and the final product is of acceptable quality Using the team s SRS ADS and DDS as references the team can construct tests and testing criteria that are specifically designed to prove the functionality and quality of a given component of the system whether the component be a small portion of the overall system such as a module a slightly larger component like a subsystem or an entire layer or even the system as a whole Together these tests should prove that the system functions as it is meant to as specified by the ADS and the DDS and that the product provides the functions and services that were required by the customer the requirements as specified in the SRS 1 2 Product Overview The Wireless Blood Pressure Monitoring System is meant to provide doctors and patients an easy way to exchange data and information about a patient s health By using the product s Bluetooth enabled blood pressure monitor and an Android phone patients will be able to measure their blood pressure and send the data wirelessly to the system s server The system s web service will then be able to display the data in various forms different charts and graphs tables etc give the patient information about their general health basic advice alerts in case of concerning trends and provide a way for the patient s doctor to be able to vi
34. e Database Interface Database Update i l Figure 3 1 Relational Diagram March 25 2014 33 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 3 2 Hardware Tests Table 3 1 Hardware Tests LID Hardware ___Input___ Output BPM e Send button e Data packet Push send button data High packets are sent to the android application Md i e Http Request e Http Response Send page request confirm High that sever has responded 3 3 Unit Tests 3 3 1 Client Layer Unit Test Table 3 2 Browser Display Unit Tests JD Module Input T Output Test Risk Browser e Mouse e Correct web page Click hyperlink High Display e animation Browser e Keyboard e Text display Type into form fields High Display Browser e Mouse e Correct web page Click submit button High Display e Animation Browser e Mouse e Animation Click element on web page High Display Table 3 3 Web Validation Unit Tests D Module Input Output Test Risk AWAR Web e Form elements e Boolean false if Input invalid data into High Validation invalid field submit e Boolean true if valid Input valid data into field submit March 25 2014 34 Beta Blockers System Test Plan Table 3 4 Chart Generation Unit Tests Chart e JSON objects e Chart element based Generation e JSON arrays on patient data Table 3 5 Application UI Unit Tests Application e Touch input e Correct views UI e Animation Application
35. e 5 6 will then login to their account e 8 1 and time how long it takes to e 8 2 successfully authenticate March 25 2014 45 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 4 Risks 4 1 Overview Testing is meant to help find and fix problems in a project so that the final product is functional and acceptable to users However problems can occur during the process of testing which can be just as bad as the problems that it intends to fix In order to avoid causing more issues and possibly doing irreversible damage to the product the team has identified certain risks that need to be addressed and avoided as much as possible The following section will discuss some of these risks 4 1 Table of Risks Each risk has been assigned a severity rating of high moderate or low Severe risks have the possibility of hindering the testing process by preventing the team from testing certain parts of the systems More moderate risks will slow down testing to a degree but can be worked around Risks with little severity will most likely have little impact on the testing process Table 4 1 Risk Table Management Plan BPM stops functioning properly Server no Testing can be done locally but Code carefully and make sure server is in longer integration becomes a problem the proper environment functions and delivery of the final product is put at risk Fixing errors causes further problems ist Problems
36. e doctor s profile Tester will 2 310 be able to see result on the BPM 321 and the website The doctor will 322 see an alert for the tester if s generated 8 2 e 8 3 V2 e 3 5 e User home page Tester will create a doctor High e 3 10 e Error message account if a doctor or finish 3 11 creating a patient account if a e310 patient doctor will begin setting 053 3 up patient accounts Tester will e 3 14 then go to the Edit Account page 3 16 and edit information about the 3 17 account Tester will verify that i the account data has been e 8 1 82 encrypted and stored in the E database e 8 3 s 8 4 V3 e 3 5 e Chart page Tester will login to their account High e 3 10 and click on the Chart link e 3 18 Tester will then select various e 3 19 graphs and ensure that they are MEN accurate Tester will select a 8 2 reading on the chart enter an 23 annotation and submit The tester should then see the annotation when selecting that reading v4 e 3 5 e Advice page Tester will login to their account High e 3 10 and click on the Advice link e 3 27 System will then gather the e 8 1 tester s health data and analyze it e 8 2 for any concerning trends or DE readings The tester will then see the results of the analysis March 25 2014 44 Beta Blockers System Test Plan Wireless Blood Pressure Monitor e 3 5 e Time taken Tester will pair the BPM withan Low 054 Android phone and time how e 5 5 long it takes to connect Tester
37. elves if they so choose March 25 2014 8 Beta Blockers System Test Plan Wireless Blood Pressure Monitor Because of the sensitive nature of much of the data the system is collecting security will play a major part in the system Data encryption permission assignments secure transferring of data across the network and other security features need to be in place so that doctors and patients will feel safe when using the system and so that the system is HIPAA compliant March 25 2014 9 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 References 2 1 Overview The tests and test plans documented in the TPS have been designed to fit the elements of the system specified in previous documents the SRS ADS and DDS The system will be tested to ensure that it fits the requirements specified in the SRS and that the components of the system function properly and interact correctly as detailed in the ADS and the DDS The following sections will provide the key portions of those documents that need to be considered when designing the test plan 2 2 System Requirements Specification The SRS details the requirements for the project that have been set by the various stakeholders team members sponsors etc These requirements specify things such as general functionalities and features as well as more detailed things such as latency times and safety features Testing to ensure that our system meets these requirements will
38. ew this information to allow them to easily keep track of their patients blood pressure without having to schedule appointments 1 3 Project Scope The Wireless Blood Pressure Monitoring System will be able to transfer a patient s blood pressure reading to the system s servers by using the provided blood pressure monitor and an Android phone with the system s application installed Doctors will have the ability to create a profile for themselves on the web service as well as profiles for their patients though it is ultimately the patient who will be in control of their own profile Various charts and graphs will be generated from the provided data in a way that will allow both patients and doctors to more easily visualize different trends and statistics so that it may be easier to recognize problems and make adjustments accordingly An advice system shall be put in place that will look at the patient s blood pressure results as well as other data that may have been collected about them new prescriptions existing conditions etc and make general observations and give feedback to the patient based on the data though these are meant to be general suggestions and should not be substituted for a doctor s advice An alert system shall be provided that will alert a patient s doctor that a patient may be at risk if the system detects a concerning trend or a problem based off of various calculations Patients will also be able to generate alerts thems
39. g normal use Reason This specific feature testing has been done by the manufacture due to budget and time constraint the team will not test this feature March 25 2014 59 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 6 4 6 Blood Pressure Monitor Startup Delay Description The blood pressure monitor shall be able to boot up from a cold start to a ready state for the user within 30 seconds Reason This specific feature testing has been done by the manufacture due to budget and time constraint the team will not test this feature 6 5 Safety Requirement 6 5 1 6 5 2 6 5 3 Maximum Cuff Pressure Description For devices intended for public home or other unsupervised use a means of limiting cuff pressure shall be provided so that the maximum cuff pressure will never exceed 300 mmHg For devices intended for use under professional supervision a means of limiting cuff pressure shall be provided so that the maximum cuff pressure will never exceed 300 mmHg or 30 mmHg above the upper limit of the instrument s manufacturer specified operating range whichever is lower In addition the device shall incorporate means to ensure that cuff pressure will not be maintained above 15 mmHg for longer than 3 minutes min Reason This specific feature will be tested by everyday use within the normal environment of our test area Any further climate testing we have chosen to withhold testing due to possible destruction of t
40. h 25 2014 Description Data Packet with raw blood pressure reading c ser inputs ser inputs extracted from elements User inputs HTML elements forms buttons etc that contains user inputs JavaScript chart element to be inserted into the web page HttpConnection Object that contains the user request 25 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 4 1 1 Client Layer Requirements Mapping Table 2 9 Client Layer Requirement Mapping Data 3 5 User Authentication X D D D 3 7 View Results X X 3 8 Multiple Readings X X 3 9 Result Transmission and Storage X X 3 1 Web Service X x x x 3 11 Account Types X 3 12 Doctor Account Creation X 3 13 Patient Account Creation X 3 14 Patient s Doctor X 3 15 Doctor Limit X 3 16 Doctor Editing X x 3 17 Patient Editing x 3 18 View Charts and Graphs X 3 19 Annotations X x 3 2 Patient Viewing Profile X 3 21 Create Alerts X x 3 22 View Alerts x 3 23 Messaging System X X 324 Multiple Users X 3 25 Login to Access Data X X X x 3 26 HIPAA X x X x 3 27 Advice System X 3 28 Manual Upload x x 8 1 Data Transport Encryption 8 2 Authorization X 8 3 Integrity X X X X X X x 8 4 Storage Encryption 8 5 Disposal Guarantee 8 6 WLAN Connection Security 8 7 Data Backup March 25 2014 26 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 4 2 Transport Layer Data Flow Table 2 10 Transport Layer Data Flow Data
41. he advice and within our time and budget is not an option As this requirement cannot be tested regressively we entrust the quality of this feature to the manufacture of the product with which we purchased the device from Eligible Users Description The blood pressure monitor shall not be intended for neonatal users It will be only intended for those who understand how to operate the device safely Reason This requirement will not be tested because this is a requirement directed toward our user and we cannot directly test who will be using our device after release of our product Electrical Safety Description The blood pressure monitor shall not be able to deliver a harmful shock to its user The voltage range throughout the device will be limited to 12 volts The device will also only use DC type power as its primary source of electrical power Reason This specific feature testing has been done by the manufacture due to budget and time constraint the team will not test this feature March 25 2014 60 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 6 5 4 Blood Pressure Monitor Mechanical Safety Description The blood pressure monitor primarily the wearable components shall not be able to easily induce physical injury to the user through its physical form Reason This specific feature testing has been done by the manufacture due to budget and time constraint the team will not test this feature 6 6 Maintenance a
42. hey rely partially on how the user handles the product The following section details the features that will not be tested in the product to be delivered 6 2 Customer Requirement 6 2 1 6 2 2 6 2 3 6 2 4 Patient Viewing Profile Description All patients will have a viewing profile a way in which friends family members other doctors or anyone else the patient wishes to give access to can view how the patient is doing and other information This profile is separate from the standard Patient profile it will be tied to the account with a separate set of login credentials and it is extremely limited in functionality The patient will be able to change the login credentials for this at any time to restrict access Reason This requirement will not be part of the upcoming release of the project therefore cannot be tested Messaging System Description Doctors and patients can send messages to one another to be read later like an email system as a way of addressing things not covered by the alert system and the annotation system Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested HIPAA Description Product will comply with all HIPAA standards as well as other standards that apply to medical data to ensure customer privacy This will be covered in detail in the Security Requirements section Reason This requirement will not be fully tested because of the time constr
43. ied in this document during operation over the following ranges of environmental conditions a Temperatures between 11 C and 31 C b Relative humidity under 90 noncondensing Reason This specific feature will be tested by everyday use within the normal environment of our test area Any further climate testing we have chosen to withhold testing due to possible destruction of the advice and within our time and budget is not an option Operational Battery Life Description The blood pressure monitor shall maintain the performance characteristics specified in this document for at least 30 minutes while running the measurement acquisition process continuously Reason This specific feature testing has been done by the manufacture due to budget and time constraint the team will not test this feature Blood Pressure Monitor Consistency Regarding Battery Life Description The blood pressure monitor will still be able to take consistent readings until the device detects that the battery s voltage is too low to continue normal operation The variation in blood pressure readings shall be confined to within 15 accuracy Reason This specific feature testing has been done by the manufacture due to budget and time constraint the team will not test this feature Blood Pressure Monitor Mechanical Robustness Description The blood pressure monitor shall be able to maintain its performance and safety requirements when being physically handled durin
44. il to be constructed when they should have been e Data needing encryption is properly e Data is not correctly encrypted encrypted look in database to confirm GS eee BLDG1 e Data is retrieved from the database e The system fails to retrieve the data o BE March 25 2014 69 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 8 4 Component Tests Table 8 3 Component Tests Pass Fail Criteria Test ID SEM UI responds appropriately e UI responds incorrectly CWD e Invalid data is rejected e Invalid data is accepted GAN e Charts are being generated o Errors generating charts CBUI1 e UI responds appropriately e UI responds incorrectly CBI TCS1 e Data going to server is encrypted data e Errors encrypting or decrypting TSS1 e Data going to client is encrypted data e Errors encrypting or decrypting going to client is decrypted going to server is decrypted o E 138 e Analysis results match the data being e Analysis gives incorrect results input DANSE e The correct data and database messages Incorrect data unexpected error messages or are being received other issues arise DSDS1 Lotto e Data is being stored and retrieved e Problems interacting with the database issues successfully getting or storing data errors when connecting etc 8 5 Integration Tests Table 8 4 Integration Tests Pass Fail Criteria
45. ing accessed object Request e Httpservletrequest e DataPool object s Send HTTP Request High Delegation e Httpservletresponse ensure correct object DataPools being successfully constructed March 25 2014 37 Beta Blockers System Test Plan Table 3 16 Analysis Controller Unit Tests Analysis e AnalysisDataPool Controller object Analysis e AnalysisDataPool Controller object e AnalysisCommand objects e AnalysisController object Table 3 17 Analysis Command Unit Tests Analysis e AnalysisDataPool Command object Table 3 18 Data Preparer Unit Tests Data Preparer Data Preparer Data Preparer March 25 2014 e AnalysisController e DataController e AnalysisController e DataController e Httpservletrequest e Httpservletresponse objects e AnalysisController e DataController e Httpservletrequest e Httpservletresponse objects e AnalysisCommand object with set result attribute e JSON Object e JSON Array e Web page e JSON Objects e Httpservletrequest e Httpservletresponse 38 Wireless Blood Pressure Monitor Send AnalysisDataPool High ensure that correct command objects are built based on patient data Send AnalysisDataPool High ensure that results being stored correctly Send Medium AnalysisDataPool ensure that result is correct based on data Send AnalysisController High and DataController ensure that objects are formatted correctly
46. ion of the blooData device has implemented oscillometric measuring methods for blood pressure Automatic Inflation Deflation Description Blood Pressure Cuff will automatically inflate and deflate Risk High Test Approach The team will test the blooData device upon initial request to take a blood pressure reading will automatically inflate deflate without any further instructions March 25 2014 47 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 2 4 5 2 5 5 2 6 5 2 7 5 2 8 Cuff Location Description The Blood Pressure Cuff will be worn on the upper or lower arm Risk High Test Approach User Authentication Description An authentication system will be used before all sessions to ensure user security Risk High Test Approach The team will run multiple test cases on the blooData application to ensure that the system will require the user to login before starting a blood pressure reading session Blood Pressure Reading Description An authentication system will be used before all sessions to ensure user security Risk High Test Approach The team will run multiple test cases on the blooData application to ensure that the system will require the user to login before starting a blood pressure reading session View Results Description Users will be able to view their results on the blooData application Risk High Test Approach The team will start a blood pressure reading session take
47. ke the layers and subsystems they are derived from each have their own purpose and responsibilities and by each doing their proper task and interacting with each other the system should then operate in the way it is intended Because these modules are the smallest components of the system it is crucial that these be tested to ensure that they are functioning properly as it is impossible to ensure that the larger components of the system work without first proving that the modules that male them up work March 25 2014 23 Beta Blockers System Test Plan Wireless Blood Pressure Monitor di amp j Web UI Browser Display BPM IO Processing Bluetooth Communication Web IO Processing rsio Client Security Network Transport Client Server Communication Server Security remo d Response Encryption System Controller Request Delegation Database Security Figure 2 2 Detailed Design Diagram Data Analysis Response Controller x Storage Controller Database Interface Data Controller Database Update Database March 25 2014 24 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 4 1 Client Layer Data Flow Table 2 8 Client Layer Data Flow Data Flow 2 N C3 eee CITIES clle SIE NET S KA C10 C11 C12 C13 C14 C15 Marc
48. low for a robust web service that will allow doctors to easily track patients with a wide variety of conditions or concerns Advanced The monitor will have advanced authentication 5 Future Authentication capabilities to better ensure that the correct person is Capabilities wearing the device at all times Remote Control for The blood pressure monitor will come with a control 5 Future Blood Pressure that will be used to control the system allowing for Monitor more portability and removing the need for a phone or a large box to support the system March 25 2014 20 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 3 Architectural Design Specification The ADS documents the high level architecture for the product the general concept of the various components of the system and how they will interact with one another While the components in the ADS are not broken down as far as they could be they do show how the larger more general parts of the system are supposed to work In order to ensure that the system functions properly and that it is producing acceptable results the team must test these components to verify that each one is working as it should and that the interactions between the components are behaving correctly Patient VY Web User Interface Interface BPM IO Processing Web IO Processing Client Security T1 72 Network Transport T3 T4 Server Security System Response
49. may exist that despite Low Create tests that check that security is fully test the team s best efforts slipped adequate for this project security through the tests Will not always affect the testing or the delivery but may affect the acceptability of the product All planned tests do not get run March 25 2014 46 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 Features to Be Tested 5 1 Overview The following features have been derived from the System Requirement Specification and will be thoroughly tested for compliance and to ensure the system has satisfied both function and nonfunctional requirements These sections will cover what feature is to be tested a brief description requirement and the approaches to testing the requirement as well as the risk level associated with the failure of the test 5 2 Customer Requirements 5 2 1 5 2 2 5 2 3 Non Invasive Measurements Description The blooData device will be able to take blood pressure measurement in a non invasive method Risk High Test Approach The team and sponsor will do multiple blood pressures reading session After which we and the sponsor will evaluate the invasiveness of the cuff Oscillometric Method Description The blooData device will use the oscillometric method to evaluate blood pressure Risk High Test Approach The team before construction of the device will ensure that the blood pressure cuff used in the construct
50. mitted between the blood pressure monitor and the data collecting web server This requirement is primarily focused on the level of the communication between monitor client and the web server and not the WLAN connection see section 8 5 Risk High Test Approach The team will ensure the data is sent through HTTPS and all packets will be check for encryption with a 3 party tool March 25 2014 55 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 8 Other Requirements 6 8 1 5 8 2 Web Browser Compatibility Description The web interface shall be accessible and usable through popular web browsers for the user caretaker physician and administrators Such web browsers would include Internet Explorer Mozilla Firefox Google Chrome and Safari Risk Low Test Approach The team will visit the various pages of the website using different browsers and ensure that the key features of the website are functioning and displaying as they were meant to The animations and other features will be tested as much as possible although guaranteeing that every item works for all supported browsers will be almost impossible Web Service Source Compatibility Description The source code of the web service functionality shall be compatible with Windows 7 and popular Linux development environments for implementation deployment and maintenance Risk High Test Approach The team shall load the source code on to different compu
51. multiple blood pressures send them to the blooData application and verify that the readings are properly displayed on the applications Multiple Readings Description Users will be able to record and submit multiple readings in a session Risk High Test Approach The team will start a blood pressure reading session Upon completion of the initial reading the system will allow for a second blood pressure reading After multiple blood pressure readings have been completed the user will be able to submit all the readings to the blooData application March 25 2014 48 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 2 9 5 2 10 52 11 5 2 12 Result Transmission and Storing Description The blooData application will transmit the blood pressure results to the website s database for storage Risk High Test Approach The team will execute multiple blood pressure reading sessions and manually submit them Upon submission we will verify that all sessions have been properly saved to the database Account Types Description The web service will support two types of accounts patients and doctors Risk High Test Approach The team will run multiple test to manually and automatically create doctors and patient accounts and ensure that website will properly create and register the accounts into the database Account Editing Description Profile information email password full name can be edited by the give
52. n patient Medical information will be edited by the patient s doctor Risk High Test Approach The team will create new accounts and login to existing account and edit personal profile information and verify that the changes to the account has been properly changed in the database View Charts and Graphs Description All registered users on the site will be able to view various charts and graphs on the website that describe the patients blood pressure conditions overall health and other factors assuming that they have access to said patients information Risk High Test Approach The team will login to existing account and click on the charts web page and view the blood pressure reading displayed in charts graph format We will verify that the readings displayed on the charts are valid and are properly labeled and marked on the charts graph March 25 2014 49 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 2 13 5 2 14 5 2 15 Annotations Description Patients registered on the site will be able to make notes about particular readings of theirs on the website to relay information such as changes in their health or lifestyle Risk High Test Approach The team will login to existing account and click on the charts web page Select a blood pressure reading chart select a blood pressure reading and input a unique annotation to the blood pressure reading The process will be repeated multiple time and afte
53. nd Support Requirement 6 6 1 6 6 2 Web Service Software Update Effects Description The web service will be able to be able to be modified without having to reboot the operating system or web server e g Apache There is no guarantee that the web application itself will not restart Reason This requirement will not be tested because of by our design we will have separate version of code to both run on our server and modify on our local machine Web Service Administration Layer Description The web service shall have a portal for the system administrators to manage the basics of the web portal so that the source of the web application does not need to be modified and redeployed This includes website wide notifications alerts the ability to enable disable certain services and enabling disabling the entire web application Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested 6 7 Security Requirement 6 7 1 WLAN Connection Security Description The wireless network connection between blood pressure monitor and the WLAN router shall communicated through an encryption of at least a symmetric encryption of AES 128 strength Reason This requirement will be met through the designing of our database schema and further secure programing technique in our server side code March 25 2014 61 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 6 7 2 6 7 3 Da
54. ng the test e Expected Outputs Expected Output produce with regards to the input provided to the component after execution of the test e Actual Outputs Actual Output produce from the input provided to the component after execution of the test e Result of Test Pass Fail Final evaluation of the test Pass or Fail e Tester Comments Any comments the tester wish to provide for future reference or explanation for the results of the test run e Bug ID A unique ID assign to each Bug detected by this test case March 25 2014 72 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 9 3 Bugs and Defects All bugs and defects that are found during testing will be documented and achieved Each Bug or Defect will be recorded with the following Bug ID A unique ID assign to each Bug Test Case ID The test case ID that generated the bug defects Name of Tester Name of the person that executed the test Time Stamp Time of which the bug defect was detected Severity The level of priority of the given fault bug High Medium Low Status The current status of the bug defect pending resolved removed Description A general description of the bug defect Inputs All inputs used during the test Expected Outputs Expected Output produce with regards to the input provided to the component after execution of the test Actual Outputs Actual Output produce from the input provided to the component after execution of the test
55. nimum of five years In general the data will be encrypted using symmetric encryption of at least AES 128 strength The encrypted data can only be decrypted and accessible by users with the appropriate keys The keys will further be protected using a form of public key encryption This requirement would also further enforce the protocols of authorization section 8 2 on PHI data Risk High Test Approach March 25 2014 54 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 7 4 57 9 Disposal Guarantee Description PHI data when found necessary to remove from the system will be effectively purged This guarantees that when the system removes the data from its oversight it would be thoroughly deleted from itself and all of the system s underlying dependencies If a data backup system is implemented section 8 7 then this requirement will be implemented completely on this system as well This means that the backups must be thoroughly cleansed of or recompiled without the appropriate data Risk Low Test Approach The team will delete all records of the specified patient doctor who wish to be removed from our record Each record corresponding to the patient doctor will be deleted from the database and the team wills manual check the database to ensure no information is missed during the cascading delete Data Transport Encryption Description The web service shall encrypt all data particularly PHI that is trans
56. nnen nennen 53 March 25 2014 2 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 51 Sec rity AE aa 54 5 8 Other Requirements aaa ia a 56 6 Features Not To Be Testeado eee RR 57 Ge OVERVIEW EIE 57 Te E e EE 57 6 3 Package E VE 58 6 4 Performance LS UTI 1 aio 59 6 5 Safety Requirement 55er t merit re dee Fees clica eer din eee e dedo E n Cha oe digas laca dogs e ud 60 6 6 Maintenance and Support Reouirement iene enne nennen 61 6 7 Security Requirement lardo ara alato 61 6 5 Other Requirement err aaa aaa 62 Fy Testing Approaches P i 64 HOS EE 64 E RES 64 To Configuration e 65 KE TOOS lati al RS AA id 65 TS Core Euncti onalities teret AA ie 65 TO EE 66 8 Item Pass Fail criteria aeree eet Ee eet sas Pela res dE Edge ere 67 8 1 OVerVIe wu dere tU taxes a 67 5 2 Hardware Tests ee O 67 5 3 Unit Tests edem eoe p tete toad ote tet tanen e eet e etate redeam ERR d 68 8 4Component i nb leale all aiar 70 8 5 Integration Pests iii e ette e dee e a Fede a iria be iaia 70 5 6 Validation ests et ie aa ii ar 71 9 Test Deliverables ent tenete thee xe i ehe ex eee db ee cr sada reinado aee tr audes 72 PEON aA nno olii a 72 VK EE 72 9 3 Bugs and Defects arniarna iaraa aa 73 DA Test Code zii te tina DL aaa EEG alla alcalina aaa 73 IO Test Schedule oce ret rte eo ila 74 PVA Pprov all aereo aet etre ep due Ia p Rx e te Pere vetada 75 March 25 2014 3 Beta Blocker
57. onitor Blood Pressure The blood pressure monitor shall be able to boot up 3 Moderate Monitor Startup Delay from a cold start to a ready state for the user within 30 seconds March 25 2014 15 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 2 4 Safety Requirements Table 2 4 Safety Requirements SRS No Maximum Cuff For devices intended for public home or other 1 Critical Pressure unsupervised use a means of limiting cuff pressure shall be provided so that the maximum cuff pressure will never exceed 300 mmHg For devices intended for use under professional supervision a means of limiting cuff pressure shall be provided so that the maximum cuff pressure will never exceed 300 mmHg or 30 mmHg above the upper limit of the instrument s manufacturer specified operating range whichever is lower In addition the device shall incorporate means to ensure that cuff pressure will not be maintained above 15 mmHg for longer than 3 minutes min Cuff Pressure An easily accessible and clearly labeled means of 1 Critical Release allowing the user to deflate the cuff shall be provided During the rapid exhaust of the pneumatic system with fully opened valve the time for the pressure reduction from 260 mmHg to 15 mmHg shall not exceed 10 s 6 3 Electrical Safety The blood pressure monitor shall not be able to 2 High deliver a harmful shock to its user The voltage range throughout the devi
58. onsor take User Manual Description A user manual will be provided with the product The manual will contain detailed information regarding the product website and how to operate the device Risk Low Test Approach The team will verify that the device used in storing the manual has properly stored the documentation by manual extracting the manual from the device Verify that it is indeed our documentations and is the correct version of release March 25 2014 51 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 5 4 Performance Requirements 5 4 1 5 4 2 5 4 3 5 4 4 Web Authentication Latency Description The android application interface to the end user s wireless local area network WLAN will take no longer than 10 seconds to attempt a successful connection After 10 seconds the android application will cease the connection activity Risk High Test Approach The team will execute multiple connection tests in different area and time the time it takes to connect to the wifi in that region WLAN Connection Description The android application interface to the end user s wireless local area network WLAN will take no longer than 10 seconds to attempt a successful connection After 10 seconds the blood pressure monitor will cease the connection activity and notify the end user of the current status of the WLAN connection Risk Medium Test Approach The team will execute multiple connection tests
59. pressed nature of this projects timeframe the team will be unable to follow the conventional testing layout The team will be testing during the development of the system Features will be developed tested then integrated together in pieces then finally assembled together and tested as a whole The testing will focus more on the objects being created and passed through the system The testing will begin in hardware which consists of three components the BP monitor the web server and the database Each will be testing in turn to determine that they are functioning correctly and will work properly within the project This will be followed by module testing and component testing As the modules are developed they will each be tested to ensure they are processing their respective object and data correctly Once the modules and components pass there testing they will be hooked together and put through integration testing Integration testing will be performed by testing features A particular feature will be run 1f it fails the team will know that one of the modules involved is not working properly Once the entire system has passed integration testing it will move to acceptance testing All stakeholders will examine the functionality of the products and verify that it meets the requirements Tests will be tracked on an Excel spreadsheet The document will be divided into the different sections to be tested When a test is created it will be placed in
60. quirement will be implemented completely on this system as well This means that the backups must be thoroughly cleansed of or recompiled without the appropriate data March 25 2014 18 Beta Blockers System Test Plan WLAN Connection Security 8 7 Data Backup 8 8 Business Associate March 25 2014 Wireless Blood Pressure Monitor The wireless network connection between blood 4 Low pressure monitor and the WLAN router shall communicated through an encryption of at least a symmetric encryption of AES 128 strength The data collected by the web portion of the system 5 Future will be backed up in case of an emergency or accidental deletion situation The backup must be securely handled i e encrypted and placed under an access control paradigm The system will have a HIPAA Business Associate 5 Future Agreement with every vendor that has access to the data The vendor in the scope of the project is the company that will host the system s web application The web hosting company will have all the data that is being transferred and stored so putting an agreement in place will ensure that the company will follow the HIPAA requirements for the data and the servers This guarantees that the web hosting company will provide an infrastructure that meets HIPAA compliance requirements The development team will then be responsible for applying secure programming methodologies to design and manage the website so
61. r finish of annotation the team will click each of the readings and validate that each of the annotations have been properly saved and linked to the correct reading Create Alerts Description Alerts can be created either automatically by the system if it detects a problem or a concerning trend or by a patient if they want to alert their doctor about something which will be sent to the doctor for later viewing Risk High Test Approach The team will run multiple manually insert multiple blood pressure readings into a patient account half of which will be healthy and unhealthy readings Upon insertion of the blood pressure reading the team will login to the doctor account and verify that the system has alerted the doctor account on the unhealthy readings of that patient Then the team will also login to the patient account and be able to set various alert on healthy readings Advice System Description The website will be able to give patients health information advice and general suggestions to keep their blood pressure in check by looking at general patterns and user information Risk High Test Approach The team will enter multiple blood pressure readings into an account login to the account and request advice Upon receiving advice notification from our system the team will verify the semantics of the advice according to the medical data inputted into the account March 25 2014 50 Beta Blockers System
62. s System Test Plan Wireless Blood Pressure Monitor Document Revision History Revision Revision Number Date 03 24 2014 Version to be reviewed by peers 4 1 2014 Updated version that reflects peer critique Description Rationale March 25 2014 4 Beta Blockers System Test Plan Wireless Blood Pressure Monitor List of Figures Figure 2 T Architecture DIAgram e e odii sg nasi nate aa 21 Figure 2 2 Detailed Design Diagram iaia 24 Figure 3 1 Relational Diagram aiar 33 Figure 7 1 Test Document Excel Example concibe 64 March 25 2014 5 Beta Blockers System Test Table 2 1 Table 2 2 Table 2 3 Table 2 4 Table 2 5 Table 2 6 Table 2 7 Table 2 8 Table 2 9 Table 2 10 Table 2 11 Table 2 12 Table 2 13 Table 2 14 Table 2 15 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 3 8 Table 3 9 Table 3 10 Table 3 11 Table 3 12 Table 3 13 Table 3 14 Table 3 15 Table 3 16 Table 3 17 Table 3 18 Table 3 19 Table 3 20 Table 3 21 Table 3 22 Table 3 23 Table 3 24 March 25 2 Plan Wireless Blood Pressure Monitor List of Tables ilit dli cerra nte 10 Package tu 1 nan e RUE don RE ia sopas APER RUE REPE ganda gabi eene EE Tae Ede 13 Pertormance Requirements iii nidad ibas 14 Safety REQUITEMENTS iii abia ca 16 Maintenance and Support Requirements
63. ssure Cuff Mechanical Safety Description he blood pressure monitor primarily the wearable components shall not be able to easily induce physical injury to the user through its physical form Risk High Test Approach The team will each individually wear the cuff and evaluate the quality of the comfort Cuff Pressure Release Description An easily accessible and clearly labeled means of allowing the user to deflate the cuff shall be provided During the rapid exhaust of the pneumatic system with fully opened valve the time for the pressure reduction from 260 mmHg to 15 mmHg shall not exceed 10 s Risk High Test Approach The team will run multiple reading sessions and prematurely stop the cuff before its full pressure point and after its full pressure point 5 6 Maintenance and Support Requirements 5 6 1 Web Service Software Portability Description The web service software shall be able to be deployed via an automated script that sets up the server software e g Apache MySQL etc and preloads system templates such as database schemas and defaults This is intended to ease deployment onto the client s intended web servers Risk High Test Approach The team will package the web service software database script and server configurations We will then load them into different machines and test to validate that each machine can replicate our service on them March 25 2014 53 Beta Blockers System Test Plan Wireless
64. ta Backup Description The data collected by the web portion of the system will be backed up in case of an emergency or accidental deletion situation The backup must be securely handled i e encrypted and placed under an access control paradigm Reason This requirement will not be test because a full database backup will not be available in our release Business Associate Description The system will have a HIPAA Business Associate Agreement with every vendor that has access to the data The vendor in the scope of the project is the company that will host the system s web application The web hosting company will have all the data that is being transferred and stored so putting an agreement in place will ensure that the company will follow the HIPAA requirements for the data and the servers This guarantees that the web hosting company will provide an infrastructure that meets HIPAA compliance requirements The development team will then be responsible for applying secure programming methodologies to design and manage the website so that its functionality is HIPAA compliant Reason This requirement will not be tested due to time and budget constraint 6 8 Other Requirement 6 8 1 Multiple Health Modules for Website Description The website will be able to support many different sets of data from many different pieces or hardware such as blood sugar readings or weight measurements to allow for a robust web service that will allow do
65. ta Flow Table 2 12 Business Logic Layer Data Flow StorageDataPool object 00000 AnalysisDataPool object Response data if new page not required BS10 Translated web page alysisCommand object An AnalysisDataPool object same sent in March 25 2014 29 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 4 3 1 Business Logic Layer Requirement Mapping Table 2 13 Business Logic Layer Requirement Mapping A Request Analysis Analysis Data Page Req No R t N SCH ARE Delegation Controller Command Preparer Generator 3 5 User Authentication x x x x x 3 7 View Results 3 8 Multiple Readings 3 9 Result Transmission and Storage x x x x 3 1 Web Service x x x x x 3 11 Account Types x 3 12 Doctor Account Creation x x x 3 13 Patient Account Creation x x x 3 14 Patient s Doctor x 3 15 Doctor Limit x 3 16 Doctor Editing x x x 3 17 Patient Editing x x x 3 18 View Charts and Graphs x X X 3 19 Annotations X x x 3 2 Patient Viewing Profile x x x 3 21 Create Alerts x X X x x 3 22 View Alerts x x x 3 23 Messaging System x x x 3 24 Multiple Users x 3 25 Login to Access Data x x 3 26 HIPAA x x x 3 27 Advice System x X X X X 3 28 Manual Upload x 8 1 Data Transport Encryption 8 2 Authorization x 8 3 Integrity x x x x x 8 4 Storage Encryption 8 5 Disposal Guarantee 8 6 WLAN Connection Security 8 7 Data Backup March 25 2014 30 Beta Blockers System Test Plan Wireless Blood Pressure Moni
66. ters with different OS including Window 7 and Linux and ensure that the source code can be properly modified and ran in the given environment Smartphone Device Constraint Description Any implementation of functionality for mobile devices mainly smartphones will be constrained to Android 3 0 and Unix type operation systems This is due to their accessibility and availability of their tools The choice of Android 3 0 and up is due to their available and compatible feature set for this project Risk Medium Test Approach The team will test install the android application on multiple android devices The devices will each run android version 3 0 and the team will ensure that the application will work on all smart phone devices for advance and new android devices this test will not be applicable March 25 2014 56 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 6 Features Not To Be Tested 6 1 Overview Despite the team s best efforts portions of the project will either not be delivered or will not be able to be tested due to time and budget constraints Certain features were set aside for a future release date in order to ensure that the rest of the project was fully functional and acceptable to users Some components of the project cannot be tested because failing the test would leave the team in a worse position than simply not testing them Some features cannot be fully tested due to their complexity or because t
67. the blood pressure monitor device Reason This requirement will not be tested because this requirement is for required by the user to use our product Battery Description The device will be operated via battery power Batteries will not be packaged with the device Reason This requirement will not be tested because this is a requirement directed toward our user Connection Cable Description Connection cable will be provided to manually upload the data on to a computer and uploaded to the website if wifi is not available Reason This requirement will not be part of the upcoming release of the project there fore cannot be tested March 25 2014 58 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 6 4 Performance Requirement 6 4 1 6 4 2 6 4 3 6 4 4 6 4 5 Storage conditions Description The blood pressure monitor shall maintain the performance requirements specified in this document after being stored for 24 hours at 21 C 70 F give or take 10 C variance and at a relative humidity lower than 90 noncondensing Reason This specific feature will be tested by everyday use within the normal environment of our test area Any further climate testing we have chosen to withhold testing due to possible destruction of the advice and within our time and budget is not an option Operation Conditions Description The blood pressure monitor shall maintain the safety and performance characteristics specif
68. the bulk of the work on the server side of the architecture Specifically it will be doing data process for the system such as data analysis and formatting This layer is the brain of the system it figures out what the client is requesting completes the request and returns any response necessary The layer does not deal with getting data or with the saving or storage of data Its goal is to amass the information necessary from other sources process the information and push the newly processed data back up to the Transport Layer Some of this data will come from the Transport Layer as mentioned previously Other data will come from the Data Storage Layer The Business Logic Layer is not concerned with what actual data is needed from the Data Storage Layer it will send the Data Storage Layer a request that specifies which process it needs to run along with any input needed and the Data Storage Layer will respond with whatever data is needed to complete that process or an error message if need be If the Business Logic Layer just needs to store more data in the database it will send the data to the Data Storage Layer to handle and will expect a confirmation message in response March 25 2014 22 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 3 4 Data Storage Layer The Data Storage Layer is the lowest layer of our system and it has a very simple but very important job The Data Storage Layer must dictate how data is stored
69. the client March 25 2014 36 Wireless Blood Pressure Monitor e Send data to High Bluetooth and verify the byte stream has been properly packaged Send HTTP Request Medium check request packets on client Send HTTP Medium Response check response packets on client Send HTTP request Medium make sure server receives request and make sure client receives HTTP response Beta Blockers System Test Plan Wireless Blood Pressure Monitor Table 3 12 Request Decryption Unit Tests Request e Encrypted e Unencrypted Send HTTP Request Medium Decryption HTTPServletRe HTTPServletReques check request quest object t object packets on server e HTTPServletRe e HTTPServletRespon sponse object se object Table 3 13 Permission Authentication Unit Tests Permission e Unencrypted e Forwards to e Send request with Hig Authentication HTTPServletRequest Request valid role h object Delegation e Send request with e HTTPServletRespons e Error page invalid role e object Table 3 14 Response Encryption Unit Tests Response e HTTPServletRequest e Encrypted Send HTTP Medium Encryption object HTTPServletRequest Response check e HTTPServletResponse object response packets object e HTTPServletResponse On server object Table 3 15 Request Delegation Unit Tests Request e Httpservletrequest e DataController Send HTTP Request High Delegation object e AnalysisController ensure correct servlet e Httpservletresponse objects be
70. the document using the following format Test ID Test Desription Inputs _ Expected Outputs Tester Date Result BugID Test Request Delegator to ensure Page requested charts Servlet should build ChartStorage DataPool BLRD2 building DataPools correctly UserlD testA12 and ChartAnalysisDataPool lan Jungmann 4 11 2014 Fail cwv1 Figure 7 1 Test Document Excel Example March 25 2014 64 Beta Blockers System Test Plan Wireless Blood Pressure Monitor All inputs for each test will be documented All tests will be assigned to a specific person There will be a section to make any necessary comments related to the test itself and any further clarification needed to be made about the result of the test This testing log will be kept online where all team members can access it Whenever a defect is discovered the team will put the affected section through regression testing These will consist of the same tests that were used to test integration The features that the corrected section is part of will be tested If the feature functions correctly it will pass regression testing 7 3 Configurations Many of the documented tests will need to be run multiple times to ensure that the feature being tested is working properly under different conditions Certain modules will need to be tested with different sets of input to verify that they are responding properly which can range from changing one or
71. tor 2 4 4 Data Storage Layer Data Flow Table 2 14 Data Storage Layer Data Flow Data Flow DS1 DS2 DS3 ResultSet Object DSS Database command object w encrypted data DS7 ResultSet Object DS10 Updated Database command object DS11 StorageDataPool object Database command object w encrypted data March 25 2014 31 Beta Blockers System Test Plan 2 4 4 1 Data Storage Layer Requirement Mapping Table 2 15 Data Storage Layer Requirement Mapping Req No Requirement Name 3 5 User Authentication 3 7 View Results 3 8 Multiple Readings 3 9 Result Transmission and Storage 3 1 Web Service 3 11 Account Types 3 12 Doctor Account Creation 3 13 Patient Account Creation 3 14 Patient s Doctor 3 15 Doctor Limit 3 16 Doctor Editing 3 17 Patient Editing 3 18 View Charts and Graphs 3 19 Annotations 3 2 Patient Viewing Profile 3 21 Create Alerts 3 22 View Alerts 3 23 Messaging System 3 24 Multiple Users 3 25 Login to Access Data 3 26 HIPAA 3 27 Advice System 3 28 Manual Upload 8 1 Data Transport Encryption 8 2 Authorization 8 3 Integrity 8 4 Storage Encryption 8 5 Disposal Guarantee 8 6 WLAN Connection Security 8 7 Data Backup March 25 2014 32 Data Controller X PA X SS Sg om oW m oW m a oW oW x oW d x d ww E Wireless Blood Pressure Monitor Cryptography DB Get DB Update X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
72. two key values such as logging into the system to entering a completely different set of complex data such as the analysis system This will be handled mostly at the Unit Testing level to ensure that the modules are working under all circumstances Web pages will be tested using different browsers to ensure that they are functioning in the correct manner under all of the supported web browsers When running tests that require multiple configurations the team will analyze the given modules algorithms and functions to generate different sets of input that should check the different results that are to be expected The input will be documented as well as the output so that the team is aware of on what input the module is having problems if an error occurs 7 4 Tools The team is planning to use the following tools to aid in testing e Wireshark e JUnit e TestLink e Excel 7 5 Core Functionalities e Take a blood pressure reading e Create an account e Log into the system e Advice system e Alert system e Chart generation March 25 2014 65 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 7 6 Metrics Some of the metrics for success that our team will be using are different from the traditional percent complete layout Our project has several features that have varying levels of complexity For example the advice system which can start very simple but has the potential to become very extensive For these features we have
73. ure Monitor CBD1 CBD2 CBD3 CBD4 AA CCG1 CAU1 CAU2 CAU3 e The correct web page is shown e Correct text is displayed e Correct web page or animation is shown e Animation is shown e Validation performs correctly e Correct charts are displayed e Elements respond appropriately e Text displays correctly e Correct View is displayed e Correct response message is displayed e Valid input is allowed through bad input is stopped e Translation occurs successfully and invalid packets are handled properly e Packets are being received by the phone CBV1 CDPP1 CBC1 TRQEI TRSD1 TCSC1 e Packets are encrypted properly e Packets are decrypted properly e Data is flowing to the server and back to the client e Packets are decrypted properly e Requests are being forwarded to servlets with correct permissions and error pages are being sent with incorrect permissions e Packets are encrypted properly e Request goes to the correct servlet TRQDI 7 57 D DM D CCG CAU DM TROE Wee TRQD1 TPA1 TRSEI SS Sp e DataPool is successfully constructed e The correct command objects are built based on the input BLACL1 ENOJO e Results are being generated and stored correctly e Results of the command match the input and are correct e Objects are all in the correct format BLACMI BLDP1 BLDP2 e The correct page or piece of data is returned e JSP is able to generate thus all
74. view alerts and the issue they pertain to Doctors and patients can send messages to one another to be read later like an email system as a way of addressing things not covered by the alert system and the annotation system The blood pressure monitor will be able to support multiple users on the same device Users will have to log into the website in order to view any data Product will comply with all HIPAA standards as well as other standards that apply to medical data to ensure customer privacy This will be covered in detail in the Security Requirements section The website will be able to give patients health information advice and general suggestions to keep their blood pressure in check by looking at general patterns and user information In the case where a patient s wireless connection goes down or begins to suffer problems the device will store the patient s readings for a set amount of time The patient will then be able to manually upload the readings using a computer if they feel that the wireless connection will not resume working in the near future 2 High 2 High 4 LOW 4 Low 1 Critical Critical Critical 5 Future 12 Beta Blockers System Test Plan Wireless Blood Pressure Monitor 2 2 2 Package Requirements Table 2 2 Package Requirements SRS No 41 Blood Pressure Cuff The product will be packaged with a standard blood 1 Critical pressure cuff The
75. will deliver with the system in regards to their testing efforts This will provide supervisors sponsors and customers with interest in the project with a general concept of what to expect in terms of documentation logs and other files that will be used to test the system and keep track of the results 9 2 Deliverables 9 2 1 System Test Plan This document will be provided overview of what is to be tested how it will be approaches and overall detail of the requirement of the test plan 9 2 2 Test Cases Specifications Each test case specification will include the follow items e Test Case ID A unique ID assign to each test case e Description A general description of what component of the system is being tested e Valid input range A range of inputs that is expected to be accepted by the component e Valid output range A range of outputs that is to be expected to be product by the component with regards to the Valid input range e Invalid input range A range of inputs that is semantically not expected to not be accepted by the component e Process A step by step instruction on the execution of the test 9 2 3 Test Case Result Each of the following test cases result will be documented with the following items after execution e Test Case ID A unique ID assign to each test case e Date of Test Date of which the test was executed e Name of Tester Name of the person that executed the test e Inputs All inputs used duri

System Test Plan (Wireless Blood Pressure Monitoring System)

Contents

Download Pdf Manuals

Related Search

Related Contents