recording, all of this must occur at the times specified by the user, or default values already stored in memory. End: An experiment duration variable will dictate how long this experiment will last; this is so this AVM can be used on multiple experiments of varying length. When the end is reached, LED array must be turned off, Camera must be turned off, and any data being written to the SATA SDD must be finalized. Any file pointers must be properly closed and all active processes must be finalized. 16.3 Non-Functional Requirements: Non-Functional requirements represent a list of tasks that will be considered a supplement to the core requirements listed in the functional requirements; these are mostly for optimization and added features and for the sake of the software will be implemented once the Functional Requirements are fully operational. User Timing accuracy File Allocation Table To expand on the Non-Functional Requirements, the reason these tasks are considered non-functional is because they are deemed to be features in addition to the main point of this experiment, which is to record an experiment in space and save that data. User input can be achieved through reprogramming of the EEPROM with the new variables, Timing accuracy is not as critical as long as it happens within an acceptable boundary, and implementing a File allocation table might be to difficult to accomplish in the scope of this project. 17.0 Software management plan 17.1 Team Organization This team is comprised of 4 engineers Walter Castellon, Tri Tran, Mohammad – Amouri, and Josh Steele, of which in terms of software development will be split and given tasks according to each ones strengths and weakness. Since Tri and Josh have the most hardware experience they will focus on hardware
recording, all of this must occur at the times specified by the user, or default values already stored in memory. End: An experiment duration variable will dictate how long this experiment will last; this is so this AVM can be used on multiple experiments of varying length. When the end is reached, LED array must be turned off, Camera must be turned off, and any data being written to the SATA SDD must be finalized. Any file pointers must be properly closed and all active processes must be finalized. 16.3 Non-Functional Requirements: Non-Functional requirements represent a list of tasks that will be considered a supplement to the core requirements listed in the functional requirements; these are mostly for optimization and added features and for the sake of the software will be implemented once the Functional Requirements are fully operational. User Timing accuracy File Allocation Table To expand on the Non-Functional Requirements, the reason these tasks are considered non-functional is because they are deemed to be features in addition to the main point of this experiment, which is to record an experiment in space and save that data. User input can be achieved through reprogramming of the EEPROM with the new variables, Timing accuracy is not as critical as long as it happens within an acceptable boundary, and implementing a File allocation table might be to difficult to accomplish in the scope of this project. 17.0 Software management plan 17.1 Team Organization This team is comprised of 4 engineers – Walter Castellon, Tri Tran, Mohammad Amouri, and Josh Steele, of which in terms of software development will be split and given tasks according to each ones strengths and weakness. Since Tri and Josh have the most hardware experience they will focus on hardware
Senior%20Design%20Paper%201.docx