Quality Assurance: Software Quality Assurance Made Easy pdfdrive com

Procedures To An Existing Company
The introduction of the software quality assurance procedures rely on the risks
involved and the company’s size. If the organization is large and the projects are
high-risk, the management must consider a more formal quality assurance
process. On the other hand, if the risk is lower, the implementation of quality
assurance may be a step-at-a-time procedure. The processes of quality assurance
maintain balance with productivity.
If the project or the company is small, an ad-hoc process may be more
appropriate. The success of the software development relies on the team leaders
and developers. More importantly, there must be enough communications
between software testers, managers, customers, and developers. Requirement
specifications must be complete, testable, and clear. There must be procedures
for design and code reviews, as well as retrospectives. Common approaches used
are Agile, Kaizen, and Deming-Shewhart Plan-Do-Check-Act methods.
It is important to evaluate documents, code, specifications, plans, and
requirements. To do this, it is necessary to prepare issues lists, checklists,
inspection meetings, and walkthroughs. This process is what IT people refer to
as verification. On the other hand, validation occurs after verification and
includes actual testing of the application. A walkthrough is evaluation in an
informal meeting. There is no need to prepare for it.
An inspection is more formal than a walkthrough and attended by at most eight
people including a reader, a recorder, and a moderator. Usually, an inspection’s
subject is a test plan or requirements specification so that the attendees will
know the software’s problems. The attendees must read the document before
attending an inspection so they will find the problems prior to the meeting. It is
difficult to prepare for an inspection but it is an effective and least costly way to
ensure quality.

---