Quality Assurance

Question 1

What is Quality?

Answer 1

Quality is the totality of features and charateristics of a product or service which bear on its ability to satisfy a given need.

Question 2

What are Quality objectives?

Answer 2

Right order - Right people - professional standards - controlled manner.

Question 3

What are Quality techniques?

Answer 3

Requirements driven testing - walkthrough and inspections - post project reviews - service level agreements (sla).

Question 4

Why is Testing necessary?

Answer 4

Because software systems are everywhere, failed software may result in financial loss, wasted time, loss of repoutation, injury or death. Therefore, testing reduces the risk of software failure.

Question 5

What are the three main causes of defects?

Answer 5

Error (human action that product an incorrect fault) - Defect (flaw in the system that can cause it to fail) - Failure (deviation of system from its expected delivery).

Question 6

What are the five fundamental test processes?

Answer 6

Test Planning and Control - Test Analysis and Design - Test Implementation and Execution - Evaluating Exit Criteria and Reporting - Test Closure Activities.

Question 7

What is risk-based Testing?

Answer 7

It is virtually impossible to Test everything therefore we must use a targeted approach that is based on RISK.

Question 8

What is requirements driven Testing?

Answer 8

Testing will be based off the requirements in the test basis. In UML FR are expressed as Use Cases, therefore the Test Basis is a set of Use Cases.

Question 9

What is Black-Box Testing?

Answer 9

Testing, either functional or non-functional, without reference to the internal structure of the component or system.

Question 10

What is White-Box Testing?

Answer 10

Testing based on an analysis of the internal structure of the component or system.

Question 11

What is a Test Condition?

Answer 11

An item or event of a software that can be verified by one or more tests.

Question 12

What is a Test Case?

Answer 12

A set of input values, execution pre-conditions, expected results and execution post-conditions developer for a particular test condition.

Question 13

What is Input Data in Testing?

Answer 13

Input required to test the condition.

Question 14

What is Base Data in Testing?

Answer 14

Stored data.

Question 15

Can Tests be derived from a Main Flow?

Answer 15

Yes - by analysing the flow and consider the input data and the base data.

Question 16

What is a Test Procedure?

Answer 16

Created to support test cases. They should include instructions for grouping of test cases, intiating tests, executing tests, recording test results, termianting tests, inspecting the results.

Question 17

What is Testing in Agile?

Answer 17

It takes form of anumber of ‘acceptance criteria’ which are nnotated at the back of the user story. Tests verify and determine when the user story is done. It is called test-driven requirements engineering.

Question 18

How can we Test NFRs?

Answer 18

Testing NFRs is difficult prior to release, NFRs are subject to the SLAs signed with operations.

Question 19

What are some charateristics of Informal Reviews?

Answer 19

A review with no formal process, inexepensive, recordings are optional. Usually called buddy reviews or desk checks.

Question 20

What are some charateristics of Walkthroughs?

Answer 20

Contain formal elements, scenarios and dry runs take place. These are open ended sessions. Purpose is to learn and gain an understanding.

Question 21

What are some charateristics of Technical Reviews?

Answer 21

There are some formal elements, it is documented and defined. Ideally led by a moderator. Main purpose is to discuss the product, make decisions, evaluate alternatives, find defects, solve problems.

Question 22

What are some charateristics of Inspections?

Answer 22

A formal process based on rules, checklists and entry/exit criteria, led by a moderator with defined roles.

Question 23

What are the key activities in Inspections?

Answer 23

Planning - kick-off - individual preparation - review meeting - rework - follow-up

Question 24

What are the key roles in Inspections?

Answer 24

Moderator/leader - author - reviewers - manager - scribe

Question 25

What are the objectives of a Post Project Review?

Answer 25

Review the development project, document lessons learnt, document probblem areas, prepare a post project report.

Question 26

What is the typical information gathered in a Post Project Review?

Answer 26

Information on approach, techniques, communications, technology, project management, estimating, risks and issues, user involvmenent.

Question 27

What is a Post Project Review Report?

Answer 27

Report produced to document the finidngs. Requires stakeholder agreement. It will aim to realise benefits of system, avoid reinventing the wheel, improve estimates and plans, re-use what worked, avoid what didn’t work, correct any mistake.

Question 28

What is a Service Level Agreement (SLA)?

Answer 28

Document that descibres the relationship between two parties, the service provider and the service user.

Question 29

What happens if an SLA is used properly?

Answer 29

Identify and define user needs, provide a framework for understanding, simplify complex issues, reduces areas of conflict, encourage dialogue in the event of disputes, eliminate unrealistic expectations.

Question 30

What are the factors addressed by SLA?

Answer 30

Services to be delivered, performance, tracking and reporting, problem management, legal compliance and resolution, customer duties and responsabilities, security, IPR, termiantion.