Quality

Quality

1. Software Quality

   • Functional and performance requirements explicitly established.
   • Explicitly documented development standards.
   • The implicit characteristics that are expected from every professionally developed software.
   • Quality Factors
     • Correctness
     • Reliability
     • Maintainability
     • Usability
     • Flexibility
     • Testability
     • Interoperability
     • Portability
     • Integrity
     • Reusability
     • Efficiency
   • Software Quality Assurance
     • SQA is a set of activities required to provide adequate confidence the processes are defined and they are continuously improved in order to develop a product or service that meets the requirements, and it is ready to be used.
     • Characteristics
       • Help establish process
       • Establish measure programs to evaluate process.
       • Identify process weakness and improve them.
       • Manager responsibility
       • Assess control quality process
       • Related with all process’ products.
     • Activities
       • Procedure definition
         • Configuration Management
         • Nonconformities Report
         • Corrective Actions Report
         • Testing
         • Formal Inspections
       • Standards Definitions
       • Improve methodologies and analysis, design, program, and testing tools.
       • Review and inspection procedures
       • Test Strategy definition
       • Controls
       • Measurement definition
       • Process Audit
       • Validate and Verify
   • Software Quality Control
     • SQC is defined as the process and methods used to compare the product's quality against the requirements and applicable standards and the action that is taken when nonconformities are detected.
     • It does not deal with the processed used to create a product. Instead, it examines the quality of the end product and the outcome.
     • Activities
       • Keep a process under control.
       • Eliminate the bug causes in the different stages of the SDLC
     • Characteristics
       • Related to a specific product.
       • Verify if a particular attribute exists or not in a specific product.
       • Identify defects and its main goal is correct them

2. Verification vs Validation

   • Verification ensures that the product is designed to offer all functionality to the customer.
     • Are we building the product right?
   • Validation is determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs.
     • Did we build the right product?

3. SQA vs SQC

   • SQA Everyone on the team involved in developing the product is responsible for quality assurance.
   • SQC is usually the responsibility of a specific team that tests the product for defects.
   • QA is a set of activities for ensuring quality in the processes by which products are developed.
   • QC is a set of activities for ensuring quality in products. The activities focus on identifying defects in the actual products produced.

4. Software Testing

   • It is the process of evaluating a system or components of a system manually or automatically to verify that it satisfies specific requirements or to verify differences between current and expected results.
   • Objectives
     • To prevent defects by evaluate work products such as requirements, user stories, design, and code.
     • To verify whe ther all specified requirements have been ful filled.
     • To check whether the test object is complete and validate if it works as the users and others take holders expect.
     • To build confidence in the level of quality of the test object.
     • To find defects and failures thus reduce the level of risk of in adequate software quality.
     • To provide sufficient information to stake holders to allow them to make informed decisions, especially regarding the level of quality of the test object.
     • To comply with contractual, legal, or regulatory requirements or standards, and/or to verify the test object’s compliance with such requirements or standards.

5. Static Testing vs Dynamic Testing

   • Static Testing
     • Static Testing is a type of software testing in which software application is tested without code execution. Manual or automated reviews of code, requirement documents and document design are done in order to find the errors.
       • Requirement specifications
       • Design document
       • Source Code
       • Test Plans
       • Test Cases
       • Test Scripts
       • Help or User document
       • Web Page content
   • Dynamic Testing
     • It checks for functional behavior of software system. The main objective of this testing is to confirm that the software product works in conformance with the business requirements.

6. Testing and Debugging

   • Executing tests can show failures that are caused by defects in the software.
   • Debugging is the development activity that finds, analyzes, and fixes such defects.

7. The ability of a set of inherent characteristics of a product, system, or process to fulfill requirements of customers and other interested parties.