178
edits
Changes
no edit summary
When coming up with the design of a subsystem, QA plays an extremely important role. The phase involves making multiple decisions based on trade-offs.
<br>
Over the course of years, the reason for any such decision can get lost. This is where documentation in the form of regular updates, minutes of review meetings and [[ Concept Phase |design review documents]] come into play.
<br>
An exhaustive list of all the interfaces of the system, along with the details regarding the exact nature of the interface need to be noted systematically and categorised with IDs in the [[ Development Phase #Integration Plan |Interface Control Document]] (ICD) which would be reviewed by the concerned members. All of these practices in addition to maintaining the quality of the system, also help in passing down the knowledge gained by the team to future members ensuring that time is not wasted re-learning what was already known to the team members at one point.
<br>
Another effective method of relaying such information is through concise Skill Development Modules, which compile all the resources to learn a particular skill in one place, and can be completed within a fixed period of time, after which proficiency can be tested through a test at the end of the module.