in the software design portion of this document. All test procedure will test for the following: Software operates and handles any exceptions generated during operation time All function requirements meet defined standards Implementation design takes into account unusual operation modes Implementation does not produce any unintended results. 19.2 Test Environment The primary test environment to test software will be AVR Studio 5 Integrated Development Environment. The IDE features full support for developing and debugging embedded Atmel AVR applications with an embedded C compiler, assembler, and simulator. This was ran in a Windows XP-32 bit environment. Testing will be conducted at two levels, the first level will be tested by the primary developers, testing Functions as they are implemented. The second set of testing will be done by the entire development team for quality assurance and to perform redundancy testing of implementation, functionality, and overall implementation of COLLide-3 AVM, to ensure this product meets all design specifications. The secondary testing was done with the AVM module in hardware. This was done at the final stage of project development and only after all other milestones has been met, this is to catch any errors that may not be observable under simulation and to get a real world sample of what AVM will have to work in. 19.3 Stopping Criteria Testing procedures was done in an iterative fashion. Functionality essential to successful operation and required features were primary test procedures, secondary test procedures consisted of non-functional requirements as listed in software design. Stopping criteria can only be achieved by 100% completion of ALL primary test procedures. Requirements will be tested by Q&A testers each release version to ensure functionality and adherence to all obligations. All other test procedures will first be tested at the unit level by the developer. Once the implemented functionality has been validated by the developer it will undergo
in the software design portion of this document. All test procedure will test for the following: Software operates and handles any exceptions generated during operation time All function requirements meet defined standards Implementation design takes into account unusual operation modes Implementation does not produce any unintended results. 19.2 Test Environment The primary test environment to test software will be AVR Studio 5 Integrated Development Environment. The IDE features full support for developing and debugging embedded Atmel AVR applications with an embedded C compiler, assembler, and simulator. This was ran in a Windows XP-32 bit environment. Testing will be conducted at two levels, the first level will be tested by the primary developers, testing Functions as they are implemented. The second set of testing will be done by the entire development team for quality assurance and to perform redundancy testing of implementation, functionality, and overall implementation of COLLide-3 AVM, to ensure this product meets all design specifications. The secondary testing was done with the AVM module in hardware. This was done at the final stage of project development and only after all other milestones has been met, this is to catch any errors that may not be observable under simulation and to get a real world sample of what AVM will have to work in. 19.3 Stopping Criteria Testing procedures was done in an iterative fashion. Functionality essential to successful operation and required features were primary test procedures, secondary test procedures consisted of non-functional requirements as listed in software design. Stopping criteria can only be achieved by 100% completion of ALL primary test procedures. Requirements will be tested by Q&A testers each release version to ensure functionality and adherence to all obligations. All other test procedures will first be tested at the unit level by the developer. Once the implemented functionality has been validated by the developer it will undergo
Senior%20Design%20Paper%202.docx