Software Quality Assurance
STAKEHOLDER EXPECTATIONS
*UPOD - Under Promise, Over Deliver *Be reasonable. *Keep in mind that unexpected problems will occur
Why do we do a review?
Stated goals: Identify components or areas that need improvement Identify components or areas that don't need improvement Find specific errors or defects Enforce organizational standards ; Unstated goals: Informational Educational Often the fastest way to learn!
Software Quality Assurance (SQA)
is a collection of activities during software development that focus on increasing the quality of the software being produced
Quality Assurance
is about work process, Quality assurance is the set of activities needed to establish and continuously improve processes that ensure a product confirms to technical requirements
Quality Control
is about work product, Quality control is repeating a set of quality processes established by quality assurance
What's a software artifact?
oftware artifacts include both the code itself, plus all associated project artifacts created during development of that piece of code. : So these are all software artifacts: ◦ Requirements document ◦ Specification document ◦ Design document ◦ Test plan ◦ User manual ◦ Interface sketches ◦ Actual software, i.e. code!
What is Quality?
satisfying the customer
Software Quality Models
to help us do a better job of saying when we have it
WHAT IS A STAKEHOLDER?
A stakeholder is any person who has a direct interest in the product. The specific kind of interest may vary based on the person and their role.
What is Selenium?
■ An open-source web testing framework.
Different types of reviews
◦ Formal vs. informal ◦ Technical vs. managerial
reviews subdivide into two types:
◦ Walkthroughs ◦ Inspections
KINDS OF STAKEHOLDERS
Customers ,Users, Project Management ,Upper Management ,Developers ,testers, Support staff, Assessors
Industry Standards
*IEEE Standards *ISO 9000
A (code) review
A (code) review is a group meeting whose purpose is to evaluate one or more software artifact(s)
CLASSES OF STAKEHOLDER
In software development, the split is usually between technical and non-technical stakeholders.
Three General Principles of QA
Know what you are doing? ◦ What is being built? ◦ How is it being built? Know what you should be doing? ◦ What are the requirements? ◦ What is the schedule? Know how to measure the difference
PEOPLE SKILLS
People skills are also something that can be learned. *No matter what field you end up in, people skills will serve you well.
What do you add to a Selenium command to make it wait?
Wait / pause
Costs of Quality
We pay for quality in two ways: 1- Quality of conformance 2- cast of per good unite of product
