• Name *

  • Company

  • Email *

  • IM (Skype)

  • Message *

Thank you for contacting us !

Software Quality Control activities.

The Software Quality Control (SQC) process is regulated by SQA and implies possible product defects detection. It is applied to check whether the project follows all the necessary processes and procedures.

The two main activities, SQC includes, and their sub activities are, as follows:

1. Requirements, design, code, deployment, test plan, test cases reviews.
2. Unit, integration, system and acceptance testing.

Testing strategies.

Finally, we’ve reached the Testing part of our article, and it already won’t come as a surprise for us that Testing means something different from SQA or SQC, though being a part of them. It is a set of activities designed to examine a system in order to find defects and evaluate some of its properties, as well as detect gaps or errors. Testing can be performed manually and automatically, as the combination of both is the most often used method.

Now that you’ve come to testing, you should choose the appropriate testing strategy, depending on your system and development process types.

Top-down testing.

This method allows design errors detection and, as a result, validation and availability to users at the early stage.

The strategy name speaks for itself. Here the high system levels are tested first and then the turn of the detailed components comes, the process continuing recursively until the end of the lowest-level components.

Bottom-up testing.

This strategy is the top-down testing antagonist, as testing begins at the hierarchy lowest levels and going up to the main module.

Bottom-up testing perfectly works with object-oriented systems when you need to test separate objects and then unite them in a collection, that is to be tested in the same way.

To Sum Up:

So, as we see, SQA and SQC are entirely different in terms of process and objectives, Testing being an integral part of SQC. The SQA is a process-focused, prevention-oriented set of actions, related to all products that will ever be created by a process, covering process definition and implementation, audit and training, while the SQC is a product-focused, detection-oriented series of actions, related to a specific product, that includes reviews and testing.

This might seem too complicated, but let me just remind you why software quality is the crucial thing in development: if your product doesn’t work the way users expect it to work, you lose your potential customers and your reputation and money go with them. Software quality is fully worth attention, time and resources dedicated to its assurance and control, isn’t it?


Enjoy page content? Please spread the word :)

Follow by Email