{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

soft_engg_lecture19 - Software Engineering Asim Banerjee...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering Asim Banerjee 30 th March 2010 [email protected]
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 2 Lecture Seating Plan (Sample) #1 #2 #3 #4 #5 #6 #7 #8 #9 Stage #10 #11 #12 #13 #20 #21 #24 #23 #22
Background image of page 2
IT314 - Software Engineering 3 Software Quality Assurance The tasks include: Periodic Audits Verification and Validation Inspection and Reviews NOTE: 1.Each task should be defined with an entry and exit criterion. 2.The documents that govern the development, verification, validation, use and maintenance of the software should be identified. 3.How the documents are to be checked for adequacy also should be specified in the QAP.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 4 Software Quality Everyone agrees that software quality is important, but in order to achieve the same one has to explicitly define what is meant by software quality create a set of activities that will help ensure that every work product exhibits high quality perform quality assurance activities on every software project use metrics to develop strategies for improving the software process and as a consequence the quality of the end product
Background image of page 4
IT314 - Software Engineering 5 Whose Responsibility? Everyone involved in the software engineering process is responsible for quality NOTE : 1. The project team has a Quality Team Leader (QTL) who is responsible for ensuring adherence to the quality process by the project team members. 2. For the organization, it is the Quality Coordinator (QC) who is responsible for ensuring adherence to the quality process by the entire organization.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 6 SQ Assurance - Importance One can do it right or one can do it over again. Emphasizing on quality in all software engineering activities reduces the amount of rework. This in turn results in lower costs and improved time-to-market NOTE : This is in spite of the fact that there are costs associated with ensuring quality.
Background image of page 6
IT314 - Software Engineering 7 Steps In Quality Assurance 1. Define “software quality” 2. Identify the set of activities that will ensure the achievement of the defined software quality NOTE : The activities would filter out errors of work products before they are passed on
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 8 SQA Work Products The software quality assurance plan (SQAP) is created to define the project’s SQA strategy During analysis, design and coding the primary SQA work product is the formal technical review summary report During testing, test plans and procedures and test reports are produced Other work products associated with process improvement may also be generated
Background image of page 8
IT314 - Software Engineering 9 Quality Assurance Plans (QAP) (1/2) To ensure that the final product is of high quality, some quality control activities must be performed throughout the development.
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}