Documente Academic
Documente Profesional
Documente Cultură
inspection Part 1
Tor Stlhane
Part 2
Tests and inspections some data Inspection as a social process two experiments and some conclusions
Introduction
Adams data - 1
Mean Time to Problem Occurrence years
Product 1 2 1.6 0.7 0.7 5 1.2 1.5 16 2.1 3.2 50 5.0 4.3 160 10.3 9.7 500 17.8 18.2 1600 28.8 28.0 5000 34.2 34.3
3
4 5 6 7 8 9
0.4
0.1 0.7 0.3 0.6 1.1 0.0
1.4
0.3 1.4 0.8 1.4 1.4 0.5
2.8
2.0 2.9 2.1 2.7 2.7 1.9
6.5
4.4 4.4 5.0 4.5 6.5 5.6
8.7
11.9 9.4 11.5 9.9 11.1 12.8
18.0
18.7 18.4 20.1 18.5 18.4 20.4
28.5
28.5 28.5 28.2 28.5 27.1 27.6
33.7
34.2 34.2 32.0 34.0 31.9 31.2
Adams data 2
The main information that you get from the table on the previous slide is that Some defects are important because they will happen quite often. Most defects are not important since they will happen seldom. How can we tell the difference?
A limit result
The following relation holds under a rather wide set of conditions:
e MTTF t t N0
The initial number of defects N0 must be estimated e.g. based on experience from earlier projects as number of defects per KLOC.
Area of competence
Understanding Observe
Man
Good at handling variations in written material General observations, multifunctional
Machine
Bad at handling variations in written material Specialized, good at observing quantitative data, bad at pattern recognition
Reasoning
Memory
Information handling
Consistency Power Speed
Inspection processes
Inspections 1
The term inspection is often used in a rather imprecise manner. We will look at three types of inspection: Walkthrough Informal inspection also called informal review Formal inspection also called formal review or just inspection The first two types are usually project internal while the last one is used as a final acceptance activity for a document.
Inspections 2
For all types of inspections: The quality of the results depends on the experience and knowledge of the participants. Garbage in Garbage out It might be a good idea to involve customer representatives.
Product document
Individual checking
Logging meeting
Change requests
Walkthrough
Kick-off
Individual checking
Logging meeting
Distribution of resources
Typical Activity Range % value % Planning 35 4 Kick-off 47 6 Individual checking 20 30 25 Logging 20 30 25 Editing 15 30 20 Process brainstorming 15 30 16 35 4 Leader overhead, follow up, entry, exit
Planning
Important planning points are: Who should participate in the inspections
Who is interested? Who have time available for preparation and meetings? Who has the necessary knowledge concerning application, language, tools, methods?
Kick-off
Important activities here are: Distribution of necessary documents:
Documents that shall be inspected Requirements Applicable standards and checklists
Assignment of roles and jobs Setting targets for resources, deadlines etc.
Individual checking
This is the main activity of the inspection. Each participant read the document to look for Potential errors - inconsistencies with requirements or common application experience Lack of adherence to company standards or good workmanship
Logging meeting
The logging meeting has three purposes: Log issues already discovered by inspection participants Discover new issues based on discussions and new information that arises during the logging meeting. Identify possible improvement to the inspection or development process.
Testing processes
Testing
We will look at three types of testing: Unit testing does the code behave as intended. Usually done by the developer Function verification testing also called systems test. Does the component or system provide the required functionality? System verification testing also called acceptance test. Does the hardware and software work together to give the user the intended functionality?
2. Identify dependencies between tests 3. Identify acceptance criteria for test suite 4. Run tests and check results against
Acceptance criteria for each test Acceptance criteria for the test suite