Quality Assurance: Software Quality Assurance Made Easy pdfdrive com

Chapter 6: The Software Quality Assurance Plan
SQA plan includes all procedures to ensure a high standard of quality within the
software development process. It compares the actual quality against the planned
quality during the development process. The management usually acts
appropriately if the actual quality does not meet the required level of quality.
The plan offers guidelines and framework for developers so that they can make
the code maintainable and understandable. It provides procedures for planning,
writing, designing, documenting, testing, maintaining, and storing software.

---

Steps to Create a Software Quality Assurance Plan
First, create the SQA plan.
Second, seek plan acceptance from management. It is important for management
to participate in the process for the plan to be successful. The management must
be responsible for the provision of all required resources to ensure software
quality. Its level of commitment must be high so every affected department
within the organization can easily approve the plan. After approval, the SQA
plan then undergoes configuration control.
During the approval process, the management gives the SQA plan administrator
control over software quality. Often, software developers usually take control of
software quality. The management must be able to explain to its staff its views
regarding software quality vis-à-vis the cost of the SQA plan. There must be a
formal project estimate about costs so that the formal plan is both economic and
with sense.
Third, seek development acceptance from the major users of the plan. Software
development and maintenance staffs must agree to cooperate in order to
implement the SQA plan successfully. The team members must commit to
follow the plan after its acceptance.
The success of the implementation relies on the managers and team members
involved in the software development. In small project teams, everyone must