SA580 and SA590 Flashcards
- Who originated the phrase fitness for use within the quality movement?
Joseph Duran originated the phrase fitness for use.
Slide 16
- What are Ishikawa diagrams useful for?
Ishikawa diagrams, also known as fishbone diagrams, are useful for exploring (brainStorming) the possible causes of a problem.
Slide 22
- Who coined the phase quality is free and what did he mean by it?
The American quality pioneer Phillip Crosby coined the term, and he meant by it that the cost of non-conformance(not acheiving quality goals) often far exceeds the cost of conformance (achieving quality goals) meaning that assuring quality can actually save money in the long run.
Slide 24
- Give some examples of cost of conformance.
Planing, training, process validation, inspections, walkthroughs and testing are all examples of the cost of conformance.
Slide 32
- How are quality and grade different?
Quality is the degree to which requirements has been satisfied; grade is a category or rank of product or service.
- Give some examples of non-conformance. Which one is most prevalent in software development?
Rework is the major cost of non-conformance in software development. Additional costs of non-conformance are complaint handling, liability judgements, product recalls, damaged customer relations and loss of business.
Slide 32
- How does the cost to correct errors made in scope change depending on when they are discovered?
The cost to correct errors made in scope goes up exponentially with later phases in which they are discovered.
Slide 38
- What role does testing ply in software quality assurance?
Testing is an integral part of quality assurance in software development, but it is important to recognize the quality cannot be tested into a software product. It must be built into the product from the start.
Slide 59
- Contrast validation with verification in software quality assurance.
Validation focuses on prevention, whereas verification focuses on detection. It is sometimes said that validation is concerned that we are building the right product. Verification focuses on whether we build the product right.
Slide 60
- Would testing be considered a validation or verification event?
Testing is a verification technique.
Slide 62
- Would inspections and walkthroughs be considered a validation or verification event?
Inspections and walkthroughs are a part of validation (prevention).
Slide 63
- How would you describe the overall testing strategy for software?
In general testing should begin with “in the small” (unit testing) and move “toward the large” through integration testing to system testing to acceptance testing).
Slide 68
- On what general principle are test cases chosen?
Test cases should be chosen to provide as much coverage of critical areas and functionality within the software as possible, realizing that you can test all possible cases in an enterprise sized program.
Slide 70
- What is regression testing and why is it necessary?
Regression testing (sometimes called negative testing) tests the larger program or system into which a new or modified unit or module has been inserted. It is necessary because a working system can be made unsafe by inadvertent (unintended) changes to the system when apparently unrelated are introduced.
Slide 77
- What is acceptance testing and who should be involved in doing it?
Acceptance testing is testing done with or by the customer to decide if the system is acceptable that is, did it meet requirements as demonstrated by predetermined acceptance criteria. Slide 81
- What is an assumption?
An assumption is factor that, for planning purposes, is considered to be true, real, or certain without proof or demonstration.
Slide 5
- What is an constraint?
A constraint is an applicable limiting factor, which will affect the execution of the project or a process.
Slide 7
- What is a risk?
A risk is an uncertain event or condition that, if it occurs, has an effect on a project’s objectives.
Slide 9
- Why is it important that all assumptions be made explicit?
Assumptions should be made explicit to ensure that the team can evaluate its possible impact.
Slide 13
- How should assumptions be treated relative to constraints and risks?
Because they are built into the project’s plan, assumptions should be treated potential failure points in a project and tracked. Constraints are known conditions that should be accommodated. Risks should be placed on a risk register and managed. The failure of an assumption can also be treated as a risk if there is a high level of uncertainty about its validity.
Slide 14
- What is the danger of ignoring constraints?
Ignoring constraints denies the team the opportunity to build accommodations into project planning.
Slide 16
- What is meant by “project-level” assumptions and constraints?
Project-level assumptions and constraints apply to the entire project or a significant part of it, unlike requirement-level assumptions and constraints that apply only to specific requirements.
Slide 19
- What are context -free questions and why are they useful?
Context-free questions that should be posed about any IT project. They can help prevent you from omitting some important questions early in the project planning.
Slide 24
- What categories ( assumptions, constraints risks) should be used for recording dependencies or expectations about normal work practices?
Depenencies, expectations about normal work practices, and methodology expectations should not be recorded in any of these categorie. These should be communicated by direct communications with the appropriate parties or recorded in more appropriate locations within project documentation.
Slide 43-45
- Summarize the relationship between project assumptions and risks.
If the level of uncertainty for an assumption is high enough, we could add its failure as a risk. This should be done w itch some thought however, because there is a cost with tracking and managing a risk.
Slides 58-61 and 72-73
- What is the preferred format for writing riisks?
Risks should usually be written using an IF…THEN format. This communicates both the cause and possible impact of a risk event.
Slide 57
- Summarize the relationship between project assumptions and constraints.
Assumptions can arise when constraint accommodations are considered.
Slide 78-79
