Software Quality Assurance in software engineering

Image
Software Quality Assurance (SQA):-  SQA is a set of activity assuring quality in software engineering process. Altimetry result in quality in software products. It include a following activities:- Process definition & implementation Auditing  Training  SQA is a process that insure hat developed software needs & compiles with defined or standardized quality specification. SQA is an on going process with in the SDLC that routinely checks the developed software to insure its needs desired quality measured. SQA helps to insure the development of high quality software. SQA practices are implementation in most type of software development regardless of underline software development model are being used. In a border sense SQA incorporate an implement software testing methodology to test software. SQA process test for quality in each phase of development until the software is completed. SQA genially works on one or more industries standards that helps in building software quality guid

Software Inspection, Inspection Process, Stages of Inspection Process, Role of Inspection, Software engineering

Software Inspection:-

 Inspection in software engineering refers to peer review of any work product by trained individual who looks for defect using a well defined process. An inspection is one of the most common sort of review practices found in software projects. The goal of the inspection is to identify defect. Commonly inspected works products include software requirements specification & test plan. In an inspection, a work product is selected for review the work product in an inspection the meeting by reading the work product & noting each defect.

                                                                                                                In an inspection, a defect is any part of the work product that will keep an inspector from approving it.

Ex:- If the team is inspecting software requirements specification each defect will be text in the document which an inspector disagree.

Inspection Process:- 

The inspection process was developed in the mead 1970's & it has letter been entombed & modify. The process should have entry criteria that determine if the inspection process is ready to began. This prevent the unfinished work product from entering the inspection process.

Different stages of Inspection Process:-

  • Planning:- The inspection is planned by the moderator.
  • Overview Meeting:- The author describes the background of the work product.
  • Preparation:- Each inspection examming the work product to identify possible defect.
  • Inspection Meeting:- During this meeting the reader reads through the work product, part by part & the inspector point out of the defect of every part.
  • Rework:- The author makes change to the work product according to the action plan from the inspection meeting.
  • Follow Up:- The changes by the author are checked to make sure everything is correct.

Inspection Role:-

  • Author:- The person who created the work product is being executed.
  • Moderator:- This is the leader of the inspection. The moderator plans the inspection & cordinate it.
  • Reader:- The person reading through the document one item at a time. The other inspector then point out the defect.
  • Recorder or Scribe:- The person that document the defect that are found during the system.
  • Inspector:- The person that examming the work product to identify the possible defect.


 

Comments

Popular posts from this blog

Computer Added Software Engineering (CASE), features of Computer Added Software Engineering (CASE), Computer Added Software Engineering (CASE) tools in Software engineering

Types of attributes in DBMS, derived, single valued, simple, multivalued, stored, composite