Software Quality Assesment Coursework Example | Topics and Well Written Essays - 1000 words

Software Quality Assesment - Coursework Example This ensures that there is prevention of any unforeseen defects. When started from the beginning of the product manufacture, the involved parties are able to consult with each other and understand the defects that arise as they progress to several stages of production. Quality is a difficult and comprehensive idea that always is determined by several factors. This could either be from the transcendental point of view that views quality as an idea that is recognizable but hard to describe. From users’ point of view quality is the ability of a product to accomplish its reason for being manufactured. Manufacturers see quality as sticking to laid down product qualifications. the products point of view that views quality as been one and the same to with definite features of a software and finally the value based point of view that views quality in relation to how much the final user is willing and able to pay so as to acquire it. There are several ways that the quality of software is ensured during manufacturing process (Tian 2005). These are: Software Testing Software testing is a systematic process mainly dedicated to the detection software defects. The product being manufactured is put to test under conditions that can be manipulated. This could be in special control rooms within the company premise specially designed for this type of work. The main reason the manufacturers ensure that such an environment should be in a position to be manipulated is because the manufacturers intend to create several scenarios whereby things go wrong when they are not supposed to and then they find ways to deal with the problem. Software Verification and Validation The verification process is undertaken so that the product is cleared of unforeseen malfunctions right before the testing process commences. Verification is made up of evaluations, meetings, assessing plans, policies, check ups, specifications among other details. On the other hand, validation comes immediately after validation and is the definite analysis of the product to establish its short comings that might arise due to malfunctions. Test Case A test case is a document that outlines the contributions, actions or events and the probable reactions of software. This assists the manufacturers/programmers to find out whether all aspects of the products are in the expected working status. This document contains s specifics such as the test case identifier, name, purpose, test circumstances, procedure as well as the expected outcomes. Good Design A good design is achieved when the general make up of the product is understandable, effortlessly adjustable and easy to preserve. The perfect design of a product always relies on the final users requirements. There are those products meant for commercial use thus this are made more complicated and very efficient than those meant for private/home use. Software Inspection This is a process meant to uncover imperfections and problems especially in records stipulating specifications, coding, and test cases among other issues (Rombach 1993). It is imperative to understand that this process just detects a hitch and notifies the manufacturers however it is not a process for rectification of such a problem. Most of the time in software quality checking procedures, it is very cost effective. It is open to many observers but only a single reader, moderator and a single individual for taking notes is required. Walkthrough This is a spontaneous and off the record meeting that is meant for analyzing the product. This is always attended by the management of the