Open main menu

Satellite Wiki β

Changes

Quality Assurance

92 bytes added, 10:35, 26 September 2020
no edit summary
“Space does not give you a second chance!” <br>
::-Manvi Dhawan, Project Manager at the time of Pratham launch
 
Achieving the reliability and the robustness of a satellite is a significant challenge. This is where having a robust set of quality assurance practices comes into play. Quality Assurance (QA) quite simply put - are a set of practices followed to maintain the quality of a system.
<br>
Achieving the reliability and the robustness of a satellite is a significant challenge. This is where having a robust set of quality assurance practices comes into play. Quality Assurance (QA) quite simply put - are a set of practices followed to maintain the quality of a system.
<br> <br>
Unlike the other subsystems of a student satellite, the task of enforcing quality assurance practices across all aspects of a system should not be supervised by a single subsystem or a group of people. Although organisations and space agencies across the globe have dedicated teams of people that deal solely with quality assurance practices for their respective missions, when it comes to a student team, however, such a setup would not be recommended. The reasons for which are enumerated below:
<br>
* A centralized repository consisting of all of the codes, and templates of documents/files to be created for the entire team.
* PCBs to be thoroughly checked and documented before and after fabrication by the Electrical and Communication subsystem
----
If you are done reading this page, you can go back to [[Starting a Student Satellite Project]].