System Test Plan - The University of Texas at Arlington
Contents
1. Low March 24 2013 40 BehindtheCurtain Enterprises Wm IEE ASA System Test Plan v1 0 AVALANCHE 5 4 2 2 Description The system shall have a high success rate on packet transfers System should implement error detection receiver feedback and retransmission to the receiver Our team has evaluated this to be of low risk due to the fact that our Bluetooth module already has error checking built into the system 5 5 Safety Requirements 5 5 1 Electric Safety 5 5 1 1 Risk Low 5 5 1 2 Description The system shall be packaged in such a way that there is no risk of electrical shock to the user Our team has evaluated this to be of low risk due to the fact that safe PCB design is easy and standardized 5 6 Maintenance and Support Requirements 5 6 1 Code Documentation 5 6 1 1 Risk Low 5 6 2 2 Description Code shall be well documented with UML use cases and comments detailing information regarding variables and methods Our team has evaluated this to be of low risk due to the fact that code documentation is necessary to development 5 6 2 Testing 5 6 2 1 Risk Low 5 6 2 2 Description March 24 2013 41 BehindtheCurtain Enterprises Wm pP 0 o o SSA System Test Plan v1 0 AVALANCHE Verification process shall include detailed unit and module tests covering every aspect of implementation Our team has evaluated this to be of low risk due to the fact that we have written this System Test Plan to dict2. Department of Computer Science and Engineering the University of Texas at Arlington System Test Plan BehindtheCurtain Enterprises Project AVALANCHE Team Members Kyle Burgess Kyle Crumpton Austen Herbst Bilal Nawaz Jason Sprowl Last Updated 3 24 2013 7 00 pm System Test Plan v1 0 AVALANCHE Table of Contents Document Revision History eee kek kek erek k k ee kek kek ka kek kek Ke AK KAK kk K Ka kake HARA Ha kk He dese 5 EOL EIERE EEN 6 o tee e EE 7 A ee ee 8 1 1 Document OvervieW carita 8 PPN o o A E meaner a eer eee ere er ree rea 8 E ra 8 E toreo ooo sya RE EA E e PEO CP O a E 8 a A A 10 LLO a 10 2 2 System Requirement Spec a 10 2 3 Architect re EE reinir anada key sic 11 2 4 Detailed Design Sp cification ari a NA ER n 17 de Test HEMS rr ds 21 SL e sia iia 21 32 Relational Dira ani t 22 3 3 Hardware Tests idad 23 o E 23 3 5 Component ao 28 3 6 Integration Ti 31 3 System Verification Tesi 32 MA E 33 o ve dia uni E an ecm eee pea R nme rR 33 42 RISE Table aa 33 e De KEE He DNR EEN He 9 2 C st mer E E He March 24 2013 2 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 5 3 Packaging REIS EE 39 5 4 Performance Requirements qa 40 A PP ASETE cae ee EEES eee 41 5 6 Maintenance and Support Requirements dare dan zada 41 5 7 Other REQUIEM a da 42 6 Non Tested Req lrem T i 4c i 4xi445i50k0y4584155005144455 151454054 E
3. UG6 Real Time Random run data Gauge to accurately High Controller changing at timed render with input intervals values UG7 Configuration Mock sensor inputs Gauges and charts are Medium R8 Controller modified according to input data UG8 Help Controller Simulated user menu Correctly display hard Low selection coded text UG9 Configuration Mock user input single Correctly formatted Medium R8 Model sensor configuration single sensor settings configuration object UGI Drag amp Drop Simulated user hold and The widgets have High Controller drag input moved within the view UG2 Page Slider Simulated user swipe The grid view has High Controller input changed to a different view Table 3 2 GUI Layer Unit Tests 3 4 2 Data Processing Layer Unit Tests Test Module Expected Ri Associate ID Output Action d Risks UPI RealTimeBuilder Mock The configurations for Medium R8 ConfigurationModelMap the current run are set March 24 2013 24 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE object UP2 RealTimeBuilder Mock byte array and mock ConfigurationModelMap Correct GaugeModel SensorAggregateMode l and SensorSnapshotModel are generated High R4 R2 UP3 RealTimeBuilder Mock Gauge data point and transform constant Correctly formatted sensor data is generated High R4 R2 UP4 RealTime
4. SendData E Figure 2 3 Module Decomposition 2 4 2 Requirements Traceability Matrix March 24 2013 Local Storage AVALANCHE Network User Information Transfer gt Package User Data N3 y end Packaged Data 18 Cloud Storage Storage Decryption User Information Gauge Information BehindtheCurtain Enterprises AVALANCHE System Test Plan v1 0 9 5 Accurate Gauge Display 9 4 Salt and Hash Passwords X 9 3 Encryption of Web traffic 9 2 User Accounts 9 1 Statistics Database 6 4 Multi threading 6 2 Reliable Data Transfer 6 1 Real Time Output 4 4 Multi Gauge Graphical User N X XA X PX 4 9 Configuration Support Page 4 2 Interface to CAN Bus 4 7 Microcontroller Packed Output 4 6 Microcontroller Data Acquisition 4 4 Mobile iPhone App 4 3 Bluetooth Capability 4 2 Profile Each Run X X 4 1 Read Data From CAN BUS Get Raw Data Set Sync Status Package Data Send Data Notify MCU Wait For Sync Receive from MCU Send Data BLEGaugeAlarmService GaugeSerializer SensorSnapshotModel RealTimeBuilder SensorAgggregateModel GaugeModel PostBuilder RunListModel GaugeAnalysisModel SensorAnalysisModel Run Storage User Acco
5. 2 2 5 App Store Submissions 2 2 3 Performance Requirements 2 2 3 1 Real Time Output 2 2 3 2 Reliable Data Transfer 2 2 3 3 Mobile Cross Compatibility 2 2 3 4 Multi threading 2 2 4 Safety Requirements 2 2 4 1 Secured Fastening 2 2 4 2 Electric Safety 2 2 5 Maintenance and Support Requirements 2 2 5 1 Support Future Mobile Operating System 2 2 5 2 Code Documentation 2 2 5 3 Testing 2 2 5 4 Maintenance Cutoff Date 2 2 6 Other Requirements 2 2 6 1 Statistics Database 2 2 6 2 User Accounts 2 2 6 3 Encryption of Web Traffic 2 2 6 4 Salt and Hash Passwords 2 2 6 5 Accurate Gauge Display 2 3 Architecture Design Specification The architecture design specification outlines the planned architecture of the AVALANCHE system 2 3 1 Layer Overview March 24 2013 11 BehindtheCurtain Enterprises pu ASA System Test Plan v1 0 AVALANCHE Data Processing Local Storage Network Cloud Storage Bluetooth Data Acquisition Figure 2 1 Architecture Overview 2 3 1 1 GUI Layer The GUI Layer acts as the intermediary between users and Project AVALANCHE It displays the data from the physical gauge in a graphical form providing both sensor readouts and charts and metrics for past runs as well as parsing user input into the system 2 3 1 2 Data Processing Layer The Data Processing Layer processes raw data received from the physical gauge via the Bluetooth Layer and uses user inputted configuration data to format the device i
6. BLEGaugeAlar Mock Byte stream from Byte stream is High R5 m Bluetooth module received and split up into snapshots to be Service processed by RealTimeBuilder UP15 GaugeSerializer Mock GaugeModel to GaugeModel is Medium R6 R9 serialize serialized into a folder in the application storage UP16 RunListModel Mock run names The correct run list Low R7 with the specified run names is generated UP17 PostBuilder Mock run to analyze The High R9 GaugeAnalysisModel and the SensorAnalysisModel are created UP18 GaugeAnalysis Serialized GaugeModel The GaugeModel is High R13 data analyzed and the Model analytic information is stored in the GaugeAnalysisModel UP19 SensorAnalysis Serialized The High R13 SensorAggregateModel SensorAggregateMode Model data l is analyzed and the analytic information is stored in the March 24 2013 26 BehindtheCurtain Enterprises System Test Plan v1 0 COO ox ox AVALANCHE SensorAnalysisModel Table 3 3 Data Processing Layer Unit Tests 3 4 3 Bluetooth Layer Unit Tests See Hardware Tests for Bluetooth related testing 3 4 4 Data Acquisition Layer Unit Tests Test Module Expected Associated ID Output Action Risks UDI Encode Package CAN BUS interrupt Message Id and 8 one Low R11 R1 Data Byte sensor values UD2 Encode Package Pin 2 from Bluetooth Sensor Values are Low R11 R1 Data goes high placed in transmit queu
7. High R14 R6 Processing are generated R7 Layer 13 Data CAN Bus data SCI Data to Bluetooth Medium R1 R11 Acquisition Module Layer 14 Bluetooth SCI Data to Bluetooth Data transmitted via Medium Ra R11 Layer Module Bluetooth to mobile Device I5 Local Runs Data and User Runs Data and User Medium R6 Storage Account Information Account Information Layer saved successfully on local device 16 Network User Account Data and Data encrypted and Medium R10 Layer Run Storage from Local transferred to Cloud Storage Layer Storage Layer March 24 2013 BehindtheCurtain Enterprises Wm AAA System Test Plan v1 0 AVALANCHE I7 Cloud Runs Data and User Account Runs Data and User Medium R10 Storage Layer Information from the Account Information Network Layer saved successfully on Cloud I8 GUI Layer A user sign into their user The correct view data High R8 account and select either set configuration Real Time View or Post settings and user Run View account are displayed Table 3 14 Integration Tests 3 7 System Verification Tests Test ID Input Expected Output Risk Sv1 User starts processing a Sensor data is displayed to the user High run Sv2 User stops processing a Real Time models are saved Medium run SV3 User loads a run The run analytics are displayed High SV4 User connects hardware Hardware module begins receiving Low m
8. Builder beginProcessing The data being inputted begins to be saved Medium R4 R2 UPS RealTimeBuilder endProcessing The run is finalized and saved Medium R4 UP6 GaugeModel getInstance Make sure that only one instance of GaugeModel can exist at a time Low R13 UP7 GaugeModel serialize String file The object and all the sensor data is serialized to a run folder Medium R6 R7 R9 UP8 GaugeModel initFromFile String file The model and all of the sensor data is initialized from file Medium R6 R9 UP9 SensorAggregate Model serialize String file The metadata contained in the model as well as the SensorSnapshotModel s contained within are serialized to the file Medium R6 R9 UP10 SensorAggregate Model initFromFile String file The object and its snapshots are initialized from the file Medium R6 R9 March 24 2013 25 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE UP11 SensorSnapshot serialize Serialize the snapshot Medium R6 R9 and return a string Model UP12 SensorSnaphot initFromDataString Strin Initialize from the Medium R6 R9 g data String name string Model Stri ring type int ID UP13 BLEGaugeAlar Bluetooth device ID Device and mobile High RS m phone are synced Service UP14
9. C9S12C128 RSM Redline Gauge Remote Sensor Module SCI Serial Communications Interface TX Transfer RX Receive RTS Request to Send CTS Clear to Send UART Universal Asynchronous Receiver Transmitter STP System Test Plan DDS Detailed Design Specification ADS Architectural Design Specification SRS System Requirements Specification March 24 2013 9 AVALANCHE BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 2 References 2 1 Overview This section describes the requirements laid out in the SRS and design aspects laid out in the ADS and DDS that will be considered when designing tests cases for each phase of testing 2 2 System Requirement Specification The system requirement specification outlines the system requirements of the AVALANCHE system 2 2 1 Customer Requirements 2 2 1 1 Read Data from CAN BUS 2 2 1 2 Profile Each Run 2 2 1 3 Bluetooth Capability 2 2 1 4 Mobile iPhone App 2 2 1 5 Mobile Android App 2 2 1 6 Microcontroller Data Acquisition 2 2 1 7 Microcontroller Packaged Output 2 2 1 8 Interface to CAN BUS 2 2 1 9 Configuration Support Page 2 2 1 10 Multi Gauge Graphical User Interface 2 2 1 11 App Consistency 2 2 1 12 Hardware Identification 2 2 2 Packaging Requirements 2 2 2 1 User Manual 2 2 2 2 Secured Enclosure March 24 2013 10 BehindtheCurtain Enterprises Wm IEE ASA System Test Plan v1 0 AVALANCHE 2 2 2 3 Printed Circuit Board 2 2 2 4 Server Software 2
10. EEE Mi k n R EEL EEEE E EET LA EA AE Ea Eads 44 D2 _w rrr EEN 44 6 2 Customer Reg ire MENiS eesis d ne Pel dir 44 63 Packs Reir E 44 6 4 Performance Roq lf ei G IY rro coa 44 6 5 Safety Requirements i eee kek kek kek ee kek kek Ka keke KRA KE KA eee 44 6 6 Maintenance and Support Requirement E eee kek ekr e kek k k ek kk Keke 45 0 DIM aaa 45 Te A E E 46 Zal Da A mm A a eee 46 T2 Over ll Test Strategy E 46 T gt Methodology ri r r r re 46 E Se 47 Ts Testing Requires eno 47 8 Acceptance Criteria AAA O II A N Ken Sak N nA N 48 SL EE A T EE e deed 48 8 2 Hardware Testa cari 48 Sa Un Teta 48 SA Component aa 48 8 5 Jntegration KE i54 435 54 1x5iiyk0axe vas kin ye Hunar k na Fa VEENAR Weku a k Re W KA a Wa da weke a ete meets 49 86 System Verification Tesi 49 Ce EE 50 March 24 2013 3 BehindtheCurtain Enterprises p System Test Plan v1 0 AVALANCHE A E RAI POPP OO OR A EE Oe ee ec ree 50 EE 50 1 Me EE 52 10 1 METS Ee KR 10 2 SA 52 VAPOR 53 March 24 2013 4 BehindtheCurtain Enterprises TT System Test Plan v1 0 AVALANCHE Document Revision History Revision Revision E 3 20 Initial Draft 3 24 STP Review Draft Revised according to peer review March 24 2013 5 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE List of Figures Figure Title Page 2 1 Architecture Ov
11. Real Time Reliable Data Transfer Mobile Cross Compatibility March 24 2013 16 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE Statistics Database Encryption of Web Traffic Salt and Hash Passwords Accurate Gauge Display Table 2 2 Requirements Mapping 2 4 Detailed Design Specification The detailed design specification provides a more detailed breakdown of the AVALANCHE system than provided in the architecture design specification 2 4 1 Module Decomposition Chart The subsystems in the subsystem overview are broken down even further into modules with dataflows as described in Figure 2 3 March 24 2013 17 BehindtheCurtain Enterprises System Test Plan v1 0 User Interface Existing Gauge Drag amp Drop Controller GUI Layer Data Output Post Process Controles Configuration Model Page Slider Controller al Time Controller Preferences Controller et G19 d Configuration Controller Pop Out Menu G20 r Controller A Help Gontroller Data Processing P14 RealTimeBuilder Real Time Processing GaugeModel SensorAggregate Model SensorSnapshot Model Post Processing G14 GaugeAnalysis Model PostBuilder SensorAnalysis Model RunListModel Save Data al Package Data
12. ate how we are to test our final product 5 7 Other Requirements 5 7 1 Statistics Database 5 7 1 1 Risk Low 5 7 1 2 Description A remote server database will store the data gathered from the gauge sensors for later use Driver will be able to look back at the mobile application and go through the statistics of race Our team has evaluated this to be of low risk due to the fact that we have extensive database experience 5 7 2 User Accounts 5 7 2 1 Risk Low 5 7 2 2 Description The mobile application will allow users to create accounts and access race statistics and information Our team has evaluated this to be of low risk due to the fact that we have extensive database experience 5 7 3 Salt and Hash Passwords 5 7 3 1 Risk Medium 5 7 3 2 Description User passwords and sensitive details should be salted and hashed before being stored in server database March 24 2013 42 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE Our team has evaluated this to be of medium risk due to the fact that we may not have the development time to complete the requirement 5 7 4 Accurate Gauge Display 5 7 4 1 Risk Low 5 7 4 2 Description Any gauge data being displayed shall be as accurate as existing gauge Our team has evaluated this to be of low risk due to the fact that we are reading the data directly off of the existing gauge and have plenty of processing time to transmit the read data March 24 2013 43 Be
13. e Table 3 4 Data Acquisition Layer Unit Tests 3 4 5 Local Storage Layer Unit Tests Test Module ID Associated Risks Expected Output Action ULI Run Storage Folder Containing mock Run data saved Medium R6 runs UL2 User Account Mock User account model User account Medium Storage containing user information saved information Table 3 5 Local Storage Layer Unit Tests 3 4 6 Network Layer Unit Tests TestID Module Input Expected Associated Output Action Risks UNI Encrypt User Mock UserInformation EncryptedDataPackage Low R15 Information Object UN2 Encrypt Mock byte EncryptedDataPackage Low R15 Gauge Gaugelnformation Object containing Information Gaugelnformation March 24 2013 27 BehindtheCurtain Enterprises Wm AAA TTT TTT System Test Plan v1 0 AVALANCHE UN3 Package User EncryptedDataPackage Readable encrypted Medium R10 Data Object byte stream prepared to be transferred UN4 Send User Host Port ByteStream Successful transfer to Medium R10 Data Object server host port UNS Decrypt User EncryptedByteStream Decrypted Byte Stream Medium R16 Information Object user information UN6 Decrypt EncryptedByteStream Decrypted byte stream Medium R16 Gauge Object with gauge information Information Table 3 6 Network Layer Unit Tests 3 4 7 Cloud Storage Laye
14. eet our other Maintenance and Support Requirements we have no real way to verify that the following requirement has been met e Support Future Mobile Operating System 6 7 Other Requirements Although we are able to meet many of our Other Requirements we simply won t have a way to verify that the following requirement has actually been met e Encryption of Web Traffic March 24 2013 45 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 7 Overall Test Strategy 7 1 Overview Team BehindtheCurtain s overall test strategy shall detail the approach to testing the Project AVALANCHE prototype Testing procedures will be designed in such a way to ensure Project AVALANCHE meets all of the system requirements architectural design specifications and detailed design specifications The tests will cover a large scope from mock testing to integration testing 7 2 Overall Test Strategy The overall strategy will involve various use cases written by Team BehindtheCurtain and design test software with generated test data for each testing stage The test software will be broken into different stages including hardware testing software testing and server testing The test software will automate the testing process using different frameworks for each phase Each phase will have its own mock instance to unit test Integration testing will include individually testing the integration of each stage and vary based on the stage Hardwa
15. ered to MCU March 24 2013 14 BehindtheCurtain Enterprises Wm ASA System Test Plan v1 0 AVALANCHE 6 6 G GUI output to the user The GUI will only be able to display up to 12 sensors at one time G 7 z L1 Saved run data to be analyzed from local storage L2 Saved run data that is being transferred to the Network Cl Saved run data that has been requested by Post Processing Subsystem being transferred via the Network Layer Being sent from the cloud to the mobile device Current Configuration to Display N1 Run data to be sent over the internet using TCP Will be encrypted if data contains usernames or passwords N Run data being sent over the internet 2 N3 Decrypted run data to be post processed Transferred from the cloud to the mobile device N4 Run data to be saved in server database Transferred from the mobile device to the cloud Table 2 1 Data Elements March 24 2013 15 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 2 3 4 Requirements Mapping Req Requirement Data Bluetooth Data GUI Local Cloud Network Acquisition Layer Processing Layer Storage Storage Layer Layer Layer Layer po Bluetooth Capability Mobile iPhone App Mobile Android App Microcontroller Data Acquisition Microcontroller Packaged Output Interface to CAN BUS Configuration Support Page Multi Gauge Graphical User Interface BET App Consistency EEE
16. erview 12 2 2 Subsystem Overview 14 2 3 Module Decomposition 18 3 1 Relational Diagram 22 March 24 2013 6 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE List of Tables Table Title Page 2 1 Data Elements 15 2 2 Requirements Mapping 17 2 3 Requirements Traceability Matrix 20 3 1 Hardware Tests 23 3 2 GUI Layer Unit Tests 24 3 3 Data Processing Layer Unit Tests 27 3 4 Data Acquisition Layer Unit Tests 27 3 5 Local Storage Layer Unit Tests 27 3 6 Network Layer Unit Tests 28 3 7 Cloud Storage Layer Unit Tests 28 3 8 GUI Layer Component Tests 29 3 9 Data Processing Layer Component Tests 29 3 10 Data Acquisition Layer Component Tests 30 3 11 Local Storage Layer Component Tests 30 3 12 Network Layer Component Tests 30 3 13 Cloud Storage Layer Component Tests 31 3 14 Integration Tests 32 3 15 System Verification Tests 32 4 1 Risks 35 10 1 Test Schedule 52 11 1 Approvals 53 March 24 2013 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 1 Introduction 1 1 Document Overview This document covers the System Test Plan for Team BehindtheCurtain s Project AVALANCHE Included in this document will be the various test plans for Project AVALANCHE The details of this System Test Plan have been thoroughly explored and discussed and will be including Unit Testing Component Testing Integration Testing and System Validation Testing The tests covered in this System Test Plan cover req
17. es March 24 2013 51 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 10 Test Schedule 10 1 Overview This section of the System Test Plan gives the planned start and finish date for each test item laid out in section 3 10 2 Schedule Test Phase Expected Start Expected Finish Hardware 4 1 13 4 8 13 Unit 4 8 13 4 15 13 Component 4 15 13 4 19 13 Integration 4 19 13 4 24 13 System Verification 4 24 13 5 1 13 Table 10 1 Test Schedule March 24 2013 52 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 11 Approvals Name Position Signature Date Kyle Burgess Team BehindtheCurtain Project Lead Kyle Crumpton Team BehindtheCurtain Austen Herbst Team BehindtheCurtain Bilal Nawaz Team BehindtheCurtain Jason Sprowl Team BehindtheCurtain Mike O Dell Project Supervisor Brian Burgess Sponsor Table 11 1 Approvals March 24 2013 53 BehindtheCurtain Enterprises
18. ge Slicer Controller User Input Preferences Controller Pop Out Menu Controller Post Process Controller d 7 as Configuration Fz Controller Help Controlier Configuration Model Configuration P lt Model Map User Accounts Model Mobile Dev ce RealTimeBuilder GaugeModel Real Time Processing SensorAggregate Model SensorSnapshot Model BS Data Processing Post Processing GaugeAnalysis ES El caye Model SensorAnalysis Model BLEGaugeAlarm Service PE Device Memory Local Storage User Account Storage Send Data ES Transfer Data Receive From MCU BR LE 4 0 Module Bluetooth Layer Wait For Sync Sync Notify MCU Hardware Module CAN Bus Get Raw Data Read CAN Bus Data Acquisition Set Sync Status caper r H a Encode Package MC9S12 MCU Package Data Data Send Data Gauge Information User Information gt Package User Data E Transfer Network Layer Server Send Package Data User Information Decryption Gauge Information Run Storage Cloud Storage User Account Layer Storage Figure 3 1 Relational Diagram March 24 2013 22 BehindtheCurtain Enterprises OO ASA System Test Plan v1 0 3 3 Hardware Tests Test ID Hardware Input AVALANCHE Expected Output Risk HB1 Bluetooth Wait for Phone Pairs to Pin 2 drives 3 3 Volts Low Sync Module HB2 Bluetooth Notify None Pin 2 Drives 3 3 Volt
19. hindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 6 Non Tested Requirements 6 1 Overview This section lists and describes requirements that our team has set forth in our System Requirements Specification which due to insufficient test capability high risk or limited development time will not be able to be tested 6 2 Customer Requirements Although we will be able to meet and test many of our customer requirements due to limited development time our team will not be able to test the following two requirements e Mobile Android App e App Consistency 6 3 Packaging Requirements Although we will be able to meet and test many of our Packaging requirements due to limited development time our team will not be able to meet the following requirement e App Store Submissions 6 4 Performance Requirements Although we will be able to meet and test many of our Performance requirements due to limited development time our team will not be able to meet the following two requirements e Mobile Cross Compatibility e Multi Threading 6 5 Safety Requirements Although we will be able to meet our other safety requirements due to the fact that we don t have a suitable vehicle we will not be able to test the following requirement e Secured Fastening March 24 2013 44 BehindtheCurtain Enterprises e System Test Plan v1 0 AVALANCHE 6 6 Maintenance and Support Requirements Although we are able to m
20. ises System Test Plan v1 0 AVALANCHE 9 Test Deliverables 9 1 Overview Team BehindTheCurtain shall document all test cases results code and known defects A comprehensive report will be complied containing all of these items and submitted with the delivery of the project 9 2 Deliverables 9 2 1 System Test Plan The system test plan consists of test items risks features to be tested features verified by design overall testing strategy acceptance criteria test deliverables and test schedule This information will be derived from the System Requirement Specification Architecture Design Specification and Detailed Design Specification 9 2 2 Test Cases The test cases shall be documented and will include the following o Test ID o Input s o Expected Output s o Results o Further Action o Comments o Tester Signoff 9 2 3 Test Results All test cases results will be documented in detail and include the following o Result of the test pass or fail o Any returned errors or exceptions March 24 2013 50 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 9 2 4 Test Code All test code used in the project will be documented and included with the project closeout documentation 9 2 5 Known Defects If for any reason any defects are found in the code that can t be resolved by the time of delivery they will be documented in detail so they can be tracked for future development and bug fix
21. layers is secure and private and TCP to ensure that the data is transferred successfully between the layers 2 3 1 7 Cloud Storage Layer The Cloud Layer will be responsible for storing saved runs for later analysis The Cloud layer will encompass the database storage on the server The Cloud Storage Layer will be accessed by the Storage Layer directly through the Network Layer The Cloud Storage Layer will also store user account information on the database for access by any mobile device with the required applications 2 3 2 Subsystem Overview Each layer in the AVALANCHE System is broken down into smaller subsystems as defined by Figure 2 2 March 24 2013 13 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE Mobile Device Bluetooth Existing Gauge Hardware Module Figure 2 2 Subsystem Overview 2 3 3 Subsystem Overview The data flows illustrated by Figure 2 2 are defined in Table 2 1 Data Flow Description Real time unformatted byte stream data being pulled from the CAN Bus on the existing gauge describing the status of each gauge sensor A Real time unformatted sensor data that was pulled from the CAN Bus 2 A3 Gauge sensor data that has been packaged and formatted for Bluetooth transmission B Gauge sensor data that has been transmitted through the Bluetooth Layer 1 B2 Bluetooth protocol data for Bluetooth sync between the Data Processing and Bluetooth Layers B3 Sync State is deliv
22. nent Tests Test ID Subsystem Expected Output Action Risk Associated Risks CP1 Real Time Mock snapshot data array Real Time models are High R2 Processing generated in near real Subsystem time CP2 Real Time Mock Configurations are set Medium R8 Processing ConfigurationModelMap for all Real Time Subsystem models CP3 Sync Bluetooth protocol data The Bluetooth High R5 Subsystem connection is maintained CP4 Post User choice of run to load The correct run is Medium R6 R7 R9 Processing loaded and analyzed Subystem Table 3 9 Data Processing Layer Component Tests 3 5 3 Bluetooth Layer Component Tests See Hardware Tests for Bluetooth related testing March 24 2013 29 BehindtheCurtain Enterprises System Test Plan v1 0 3 5 4 Data Acquisition Layer Component Tests Test Module ID CD1 packageData CAN BUS interrupt Expected Output Action Message Id and 8 one Byte sensor values COO lt AVALANCHE Low Associated Risks R1 R11 3 5 5 Local Storage Layer Component Tests Test ID Subsystem CL1 Device Memory Input Mock data containing runs data and user account information Table 3 10 Data Acquisition Layer Component Tests Expected Output Action Folder containing runs data and user account data saved locally Low Associated Risks R6 3 5 6 Network Layer Componen
23. nput into an user readable form which is outputted to the user through the GUI Layer It will also send this data to be saved in the Local Storage Layer either locally or on the server via the Network Layer These saved runs will be able to analyzed by the Data Processing Layer to create charts graphs and metrics for run analysis by the user 2 3 1 3 Bluetooth Layer March 24 2013 12 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE The Bluetooth Layer will handle the Bluetooth pairing between the hardware module and the mobile device and will be responsible for transferring gauge sensor data from the Data Acquisition Layer to the Data Processing Layer over Bluetooth 2 3 1 4 Data Acquisition Layer The Data Acquisition Layer encompasses the hardware module and will be responsible for pulling gauge data off the CAN Bus and packaging that data for transfer over the Bluetooth Layer 2 3 1 5 Local Storage Layer The Local Storage Layer will be responsible for storing saved runs for later analysis The Local Storage Layer will encompass local device storage on the mobile phone The Local Storage Layer will be accessed by the Data Processing Layer directly through the mobile device file system 2 3 1 6 Network Layer The Network Layer is responsible for secure and reliable data transfer between the Data Processing and Cloud Storage Layer It will use AES and RSA encryption to make sure that all communication between the
24. nticipated result or operation 8 3 Unit Tests 8 3 1 Pass The module accepts valid inputs and gives an anticipated response for the provided input 8 3 2 Fail The module does not give an anticipated response for the provided input 8 4 Component Tests 8 4 1 Pass A component responds appropriately to all the inputs that apply to that specific component 8 4 2 Fail March 24 2013 48 BehindtheCurtain Enterprises Wm ASA System Test Plan v1 0 AVALANCHE One or more than one components do not responds appropriately to all the inputs that apply to that specific component 8 5 Integration Tests 8 5 1 Pass The integrated components that are responsible for working together communicate in the way anticipated when given a particular data as specified by System Requirements Specification 8 5 2 Fail The integrated components that are responsible for working together do not communicate in the way anticipated when given a particular data and do not operate in the way specified by System Requirements Specification 8 6 System Verification Tests 8 6 1 Pass The project AVALANCHE by team BehindtheCurtain fulfills the requirements and performs as described in the System Requirements Specification 8 6 2 Fail The project AVALANCHE by team BehindtheCurtain does not fulfill the requirements and does not perform as described in the System Requirements Specification March 24 2013 49 BehindtheCurtain Enterpr
25. ocessing Test memory use and set a management start Layer maximum run time if experiencing needed problems during long runs R5 Bluetooth Gauge data will Low Bluetooth Layer Allow the application to reliability not transfer reconnect in the event of March 24 2013 33 BehindtheCurtain Enterprises Wm AA System Test Plan v1 0 AVALANCHE Bluetooth connection loss R6 Runs are not User will not be Medium Local Storage Store runs in plaintext for loaded correctly able to analyze Layer easy reading and past runs compatibility with multiple devices R7 Run list not User will not be Low Data Processing Store run names in the generated able to see a list Layer applications property list correctly of past runs R8 Configurations User Low GUI Layer Save configurations in an not loaded configurations easy to read format and will be lost load at startup R9 Models not Runs will not be Low Data Processing Serialization models in serialized saved Layer plaintext for easy correctly debugging R10 File transfer Run transfer Medium Local Storage Use FTP for run transfer problems between server Layer Network and application Layer Server could fail Layer R11 Hardware Important Medium Data Acquisition Make sure to use correct component failure components Layer Bluetooth voltage during testing and could fail Layer order multiple par
26. odule to existing gauge CAN Bus interrupts SV5 User pairs mobile device to LCD display indicates synced status Low Bluetooth module Pin 2 goes high to alert MCU SV6 User stores data in cloud Data successfully stored into Medium MYSQL table on server SV7 User pulls run data from Data successfully pulled from Medium cloud MYSQL table on server SV8 User changes app The configurations are saved and Medium configurations retained Table 3 15 System Verification Tests March 24 2013 32 BehindtheCurtain Enterprises A i emm OOOO TTT System Test Plan v1 0 AVALANCHE 4 Risks 4 1 Overview This section attempts to identify any risks associated with the testing process for Project AVALANCHE It will also identify the severity and management plan for each risk 4 2 ID Risk Table Risk Severity Affected Components Management Plan R1 PCB malfunction PCB will have Medium Data Acquisition Order multiple PCBs to be replaced Layer Bluetooth Layer R2 Gauge output not Application will High Data Processing Test continuously in real time not be able to Layer throughout development be used as a for response time and gauge reliably make changes to design if needed R3 Network data loss File transfer and Medium Network Layer Use protocols with built in user RDT like FTP and HTTP authorization could malfunction R4 Memory Application will High Data Pr
27. on or part replacement 7 4 2 Medium Failure of this component will hinder the most important functionalities at a slight level A failure may yield design reconsideration or part replacement 7 4 3 Low Failure of this component does not hinder the most important functionalities of the system A failure may yield design reconsideration 7 5 Testing Requirements Team BehindtheCurtain requires automated testing and Unit Testing where applicable Automated potions will include the GUI server and hardware Non automated test cases will be broken down into step by step test cases to be executed by the members of Team BehindtheCurtain March 24 2013 47 BehindtheCurtain Enterprises Wm IIE DQ System Test Plan v1 0 AVALANCHE 8 Acceptance Criteria 8 1 Overview Team BehindtheCurtain is going to use the Acceptance Criteria with the aim of evaluating each test on a pass or fail criteria The pass fail basis will be used to understand the outcomes of a test All types of tests have different criteria to evaluate whether it has passed or failed The Acceptance Criteria is divided in accordance with the sort of test under evaluation namely hardware unit component integration and system verification 8 2 Hardware Tests 8 2 1 Pass The hardware performs and behaves as expected and delivers the anticipated result or operation 8 2 2 Fail The hardware does not perform and behave as expected and does not provide the a
28. r Unit Tests Test ID Module Expected Output Action Associated Risks UCI Run Storage Mock byte stream of Run Data successfully Low R10 decrypted run data saved in Cloud UC2 User Account Mock byte stream of User account data Low R10 Storage decrypted user account successfully saved in data Cloud Table 3 7 Cloud Storage Layer Unit Tests 3 5 Component Tests 3 5 1 GUI Layer Component Tests Test ID Module Expected Output Action Risk Associated Risks CG1 User Input Simulated user input The appropriate object Medium is modified or the view is changed CG2 Data Output Users view selection from The appropriate set of High menu graphs and charts is rendered March 24 2013 28 BehindtheCurtain Enterprises Wm AAA System Test Plan v1 0 AVALANCHE CG3 Data Output User selects gauge The gauge High R8 configuration preset from configuration is applied the preferences menu the current view and it s gauges and charts CG4 Configure Mock users account Account information High R8 configuration data correctly stored and attached to the correct configuration model map CG5 Configure Mock single gauge Single gauge data is High R8 configuration data correctly stored and attached to the correct configuration model map Table 3 8 GUI Layer Component Tests 3 5 2 Data Processing Layer Compo
29. r where other cellular devices with the app installed can also obtain the same data and visuals at a reduced delay time Our team has evaluated this to be low risk because it is such a critical requirement and our team has spent a significant amount of time learning OS development 5 2 5 Microcontroller Data Acquisition 5 2 5 1 Risk Low 5 2 5 2 Description Our hardware module shall have a microcontroller that reads the data in from the existing CAN BUS line Our team has evaluated this to be of low risk because of the sponsors existing system 5 2 6 Microcontroller Packaged Output 5 2 6 1 Risk Low March 24 2013 37 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 5 2 6 2 Description After the microcontroller has received the data from the CAN BUS line it shall process and put the data into packages that can be sent to the Bluetooth transmitter for data transmission Our team has evaluated this to be of low risk because of the sponsors existing CAN Bus message system 5 2 7 Interface to CAN BUS 5 2 7 1 Risk Low 5 2 7 2 Description AVALANCHE shall have a hardware interface that can tap into the existing line Our team has evaluated this to be of low risk due to the fact that our sponsor has already provided our team with a split CAN Bus line 5 2 8 Configuration Support Page 5 2 8 1 Risk Low 5 2 8 2 Description AVALANCHE shall have a user configuration page where they can input the same user inputs tha
30. re will be hand tested GUI application will be user tested and the server will be tested by the system administrator 7 3 Methodology Team BehindtheCurtain test plan for Project AVALANCHE will include Unit Testing Component Testing Integration Testing and System Verification Unit Testing will be the first phase of testing and include Mock Hardware Instances and Mock Server Instances Component Testing will be the next phase in which each subsystem will be individually tested to verify the quality assurance specified in the Detailed Design Specification Integration testing will begin only after each component has been individually tested and will test how each component interacts with one another inside each layer System Verification will require the following and be designed based on the use case e Input s e Expected Output s e Actual Output e Result pass fail e Problems March 24 2013 46 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 7 4 Testing Metrics Each test will have a priority associated with it determined by the metrics put forth by Team BehindtheCurtain The level of each test will be set based on the System Requirements Specification and the level of impact the respective component has on Project AVALANCHE The priorities will be defined as follows 7 4 1 High Failure of this component will greatly impact the most important system functionalities A failure will yield design reconsiderati
31. rom CAN Bus 5 2 1 1 Risk Low 5 2 1 2 Description Our product shall have a hardware module that will read its data from the existing gauges CAN BUS line Our team has evaluated this to be low risk due to the sponsors existing knowledge of CAN Bus interfacing 5 2 2 Profile Each Run 5 2 2 1 Risk Low 5 2 2 2 Description Our product shall be able to record all of the data transferred to the cellular device The gathered data shall be displayed to the user in a very visually satisfying fashion Our team has evaluated this to be low risk because the process of saving data is not a difficult task 5 2 3 Bluetooth Capability March 24 2013 36 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 5 2 3 1 Risk Medium 5 2 3 2 Description The hardware module shall have Bluetooth capability to transfer the data from the module to the phone Our team has evaluated this to be of medium risk due to the teams original lack of Bluetooth knowledge 5 2 4 Mobile iPhone App 5 2 4 1 Risk Low 5 2 4 2 Description Since we are using an iPhone as one of our supported devices we shall write an app in objective C that reads the transmitted data from the Bluetooth module processes the data and displays the information to the user in a visually stimulating fashion If there is a cellular connection to the internet at the racing site the Bluetooth connected phone shall transmit the already packaged data to a centralized serve
32. s Low MCU to MCU HB3 Bluetooth Receive SCI Packaged Data None Low From MCU HB4 Bluetooth Send Data SCI Packaged Data Data transmitted to Low mobile device HD1 Data Acquisition Get CAN BUS Data Structure Containing Low Raw Data Message ID and 8 Bytes of Sensor Data HD2 Data Acquisition Set Pin 2from Bluetooth Pin 1 of PORTA goes Low Sync Status goes High high and MCU pushes data onto the transmit queue HD3 Data Acquisition Send Structure Containing Transmit interrupt Low Data Message ID and 8 goes off when SCI Bytes of Sensor Data Transmit register 1s empty Next value on queue is transmitted 3 4 Unit Tests 3 4 1 GUI Layer Unit Tests Table 3 1 Hardware Tests Test Module Expected Associate ID Output Action d Risks UGI Drag amp Drop Simulated user hold and The widgets have High Controller drag input moved within the view UG2 Page Slider Simulated user swipe The grid view has High March 24 2013 23 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE Controller input changed to a different view UG3 Preferences Simulated user input The preferences menu High R8 Controller opens when selected UG4 Pop Out Menu Simulated 2 finger left to The main menu will High Controller right swipe be reviled UG5 Post Process Mock saved run data Gauge to accurately High Controller values render with input values
33. t Tests Test ID Subsystem Input Table 3 11 Local Storage Layer Component Tests Expected Output Action Associated Risks CN1 Encryption Mock UserInformation User information Low R15 Subsystem and Gaugelnformation encrypted in an EncryptedDataPackage object with Gaugelnformation CN2 Transfer EncryptedDataPackage Byte stream of Medium R10 Subsystem EncryptedDataPackage Object ready for transfer CN3 Transfer Byte Data successfully Medium R10 Subsystem encryptedDataPackage transferred to server Host name Host port CN4 Decryption Byte Readable User Medium R16 Subsystem encryptedDataPackage Information and Gauge data March 24 2013 Table 3 12 Network Layer Component Tests BehindtheCurtain Enterprises Wm AA Or LL lt lt System Test Plan v1 0 AVALANCHE 3 5 7 Cloud Storage Layer Component Tests Test ID Layer Expected Output Action Risk Associated RIS CCl Database Mock data containing runs Folder containing runs Medium R6 data and user account data and user account information data saved in cloud Table 3 13 Cloud Storage Layer Component Tests 3 6 Integration Tests Test ID Layer Expected Output Action Associated Risks Il Data Byte stream from Real Time models High R14 R9 Processing Bluetooth Layer containing gauge data R2 Layer and a saved run folder D Data Run to load Post Processing models
34. t the existing gauge also requires Our team has rated this to be of low risk due to the simplicity of the requirement 5 2 9 Multi Gauge Graphical User Interface 5 2 9 1 Risk Medium 5 2 9 2 Description The cellular devices shall have an appealing user interface that supports all existing sensor displays on the existing gauge The user interface shall be able to display multiple gauges per screen to accommodate for the vast quantity of data we need to display March 24 2013 38 BehindtheCurtain Enterprises TT System Test Plan v1 0 AVALANCHE Our team has rated this to be of medium risk due to the fact that the available screen size on the mobile device is very limited 5 2 10 Hardware Identification 5 2 10 1 Risk Low 5 2 10 2 Description Each hardware unit shall have a unique identification number so as to easily recognize a pairing when syncing with the app Our team has evaluated this to be of low risk due to the fact that the Bluetooth chips come pre configured with unique identification names 5 3 Packaging Requirements 5 3 1 User manual 5 3 1 1 Risk Low 5 3 1 2 Description The system shall be packaged with a user manual explaining how to use AVALANCHE Our team has evaluated this to be of low risk due to the fact that documenting the operating process is simple 5 3 2 Secured Enclosure 5 3 2 1 Risk Medium 5 3 2 2 Description The system shall be packaged with a secured enclosure which shall connec
35. t to the CAN Bus and hold the microcontroller which interfaces with the current standing system Our team has evaluated this to be of medium risk due to the fact that our team will have minimal time to create a secured enclosure between the close of the project and the creation of the printed circuit board March 24 2013 39 BehindtheCurtain Enterprises Wm IE ASA System Test Plan v1 0 AVALANCHE 5 3 3 Printed Circuit Board 5 3 3 1 Risk Medium 5 3 3 2 Description System will be delivered with a printed circuit board loaded with the embedded code to run AVALANCHE Our team has evaluated this to be of medium risk due to the fact that our team has no experience with constructing PCB s and has minimal development time 5 3 4 Server Software 5 3 4 1 Risk Low 5 3 4 2 Description AVALANCHE will include server software to host documented races users and possibly statistics Our team has evaluated this to be of low risk due to the fact that our team has a fair amount of networking experience 5 4 Performance Requirements 5 4 1 Real Time Output 5 4 1 1 Risk Low 5 4 1 2 Description The system shall be able to transmit data over Bluetooth to be output to the mobile device at a real time speed Our team has evaluated this to be of low risk due to the fact that we have calculated a necessary baud rate that is far less than what our microcontroller and Bluetooth module can handle 5 4 2 Reliable Data Transfer 5 4 2 1 Risk
36. ts as backup R12 PCB design Any ordered High Bluetooth Layer Test PCB design inadequate PCB using the Data Acquisition extensively before sending design will have Layer out order to be replaced R13 Inadequate unit Major bugs Low Project Set minimum code testing could go AVALANCHE coverage standard and undetected making sure to catch branches that are likely to fail R14 Integration tests Interfaces will High Project Make sure that each fail have to be re AVALANCHE person is implementing implemented their aspect of the project based on the design laid March 24 2013 34 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE out in the DDS R15 Data not properly Encryption Low Network Layer Use proven encryption encrypted framework will framework and standards have to be redone R16 Data not properly Decryption Low Network Layer User decryption decrypted framework will framework to match have to be encryption scheme redone March 24 2013 Table 4 1 Risks 35 BehindtheCurtain Enterprises OOOO lt lt System Test Plan v1 0 AVALANCHE 5 Testable Features 5 1 Overview This section of the System Test Plan lists all of the features that are to be tested to assure that the Avalanche system fulfills the requirements that the team has set forth in the System Requirements Specification 5 2 Customer Requirements 5 2 1 Read Data f
37. uirements specified in the SRS ADS and DDS 1 2 Purpose This purpose of this document is to detail plans for system verification as they relate to each component and integration as a whole The project will be verified on both a high level system architecture and on a low level which will cover our DDS Each requirement will be verified and given a testing priority which reflects the total impact the test has on the system ranging from high to low The primary purpose of the STP will be to verify that each requirement specified in the SRS is met on an acceptable level 13 Scope Project AVALANCHE exists as a modification to a racing gauge provided by Team BehindtheCurtain s sponsor The project is designed to take an existing racing gauge using an LCD screen and move it to a mobile application framework for ease of use and advanced user features Server software will also be provided as Project AVALANCHE includes a cloud storage feature The scope of the STP detailed in this document is to verify each requirement detailed in the SRS and assure proper system functionality as specified in the DDS This document will include details on how Project AVALANCHE will be Unit Tested Component Tested Integration Tested and Validated 1 4 Acronyms BLE Bluetooth Low Energy 4 0 CAN Bus Controller Area Network Bus March 24 2013 8 BehindtheCurtain Enterprises System Test Plan v1 0 iOS iPhone Operating System MCU Microcontroller Unit M
38. unt Storage User Information Gauge Information BehindtheCurtain Enterprises 19 March 24 2013 poousa muoX System Test Plan v1 0 AVALANCHE oi Gi GI o Run Storage User Account Storage Drag amp Drop Controller Page Slider Controller Preferences Controller Pop Out Menu Controller Post Process Controller Real Time Controller Configuration Controller Help Controller Configuration Model Configuration Model Map User Accounts Model Table 2 3 Requirements Traceability Matrix March 24 2013 20 BehindtheCurtain Enterprises 0 AAA System Test Plan v1 0 AVALANCHE 3 Test Items 3 1 Overview This section provides details about the different items that will be tested in the hardware unit component integration and system verification phases of testing All of the dependent tests in the earlier phases of testing must be passed before each test item can be tested correctly This relationship can be viewed below in Figure 3 1 Each phase of testing will attempt to verify both product correctness and adherence to the requirements set by the SRS document March 24 2013 21 BehindtheCurtain Enterprises System Test Plan v1 0 AVALANCHE 3 2 Relational Diagram Relational Diagram n System Hardware Unit Component Integration EA A P g Verifictation Drag and Drop Controller Pa
Download Pdf Manuals
Related Search