Software Quality Assurance

1
Software Quality Assurance

• Software Engineering (CS577B)
• Individual Research Presentation
• Presented by
• Mustanshir Kanchwalla
• 18th April 2007

2
Overview

• Points
• Definitions of SQA Testing
• Software Quality Assurance Activities
• SQA during Software Development Life Cycle
• Elaboration on Testing
• Black Box Testing
• White Box Testing
• References

3
Definitions

• SQA Defined as a planned and systematic
  approach to the evaluation of the
  quality of and adherence to software
  product standards, processes, and
  procedures.
• Testing A process of establishing confidence
  that a program does what it is
  supposed to do.
• OR
• In short, we can say that it is a
  process of finding errors in a program.

4
Software Quality Assurance Activities

• Product evaluation
• Assures standards are being followed.
• Assures that clear and achievable standards exist
  and then evaluate compliance of the software
  product to the established standards.
• Product evaluation assures that the software
  product reflects the requirements of the
  applicable standards.
• Process Monitoring
• Ensures that appropriate steps to carry out the
  process are being followed and it does that by
  comparing the actual steps carried out with those
  in the documented procedures.
• Audit
• Assures that proper control procedures are being
  followed, that required documentation is being
  maintained and the developers status reports
  accurately reflect the status of the activity.

5
SQA during Software Development Life Cycle

• Software Concept and Initiation Phase
• SQA should be involved in both writing and
  reviewing the Management Plan in order to assure
  that the processes, procedures, and standards
  identified in the plan are appropriate, clear,
  specific, and auditable.
• Software Requirements Phase
• SQA assures that software requirements are
  complete, testable, and properly expressed as
  functional, performance, and interface
  requirements.
• Software Architectural Design Phase
• Assuring adherence to approved design standards
  as designated in the Management Plan and software
  requirements are allocated to software
  components.

6
SQA during Software DevelopmentLife Cycle
contd(2)

• Software Detailed Design Phase
• Assuring that approved design standards are
  followed, allocated modules are included in the
  detailed design and results of design inspections
  are included in the design.
• Software Implementation Phase
• SQA in this phase requires the results of all
  coding and design activities as well as status of
  deliverable items. It also requires non
  conformance reporting.
• Software Integration and Test Phase
• Assuring readiness for testing of all deliverable
  items.
• Assuring that all tests are run according to test
  plans and procedures and that any non
  conformances are reported and resolved.
• Assuring that test reports are complete and
  correct and documentation is ready for delivery.

7
SQA during Software Development Life Cycle
contd(3)

• Software Acceptance and Delivery Phase
• Assuring the performance testing and user
  acceptance testing of the final system, and that
  all deliverable items are ready for delivery.
• Software Maintenance Phase
• As this phase includes enhancement and correction
  of the system, SQA conducts the appropriate
  phase-specific activities.

8
Elaboration on Testing

• Software testing can be viewed as a sub-field of
  Software Quality Assurance but typically it can
  exist independently as well. By Software testing,
  SQA can assure software completeness and
  readiness for delivery. Only after sufficient
  testing can SQA assure a high end quality
  product.
• Testing Techniques
• Black Box Testing
• White Box Testing

9
Black Box Testing

• Also known as functional testing.
• Data Driven or Input Output Driven Testing.
• The Test Engineer is completely unconcerned
  about the internal behavior and structure of
  program.
• So, tester does not need to know any specific
  programming language.
• Testing is done from point of view of the
  user and not the designer.

10
White Box Testing

• Also known as glass box, structural, clear box
  and open box testing.
• Requires explicit knowledge of the internal
  workings of the items being tested.
• White box testing uses specific knowledge of
  programming language.

11
References
SQA http//satc.gsfc.nasa.gov/assure/agbsec3.
txt
http//en.wikipedia.org/wiki/Software_Quality_Assu
rance Testing http//en.wikipedia.
org/wiki/Software_testing
http//www.softwareqatest.com/
12

• Questions?
• Thank You